Abstract:
Providing a multicast service includes maintaining multicast service information at an application server. The multicast service information describes a multicast service having an associated subscriber, and the multicast service is operable to deliver multicast content from a multicast source. A cell supporting a user device associated with the subscriber is determined, and creation of a bearer path for the multicast service is initiated. Delivery of the multicast content to the user device is enabled using the bearer path.
Abstract:
An apparatus for signaling information in a network environment is provided that includes an access gateway operable to establish one or more packet data protocol (PDP) links on behalf of an end user. The access gateway is operable to communicate a message associated with a change in quality of service, locale, or policy enforcement relating to a selected one of the PDP links to a client services packet gateway (CSPG). The CSPG responds to the message by providing an accounting command for the selected PDP link such that synchronization is achieved between accounting information and a state associated with the selected PDP link.
Abstract:
A system for efficiently reauthenticating a client of a network. In a specific embodiment, the system includes an authentication server and a Security GateWay (SGW) in communication with the client. The SGW includes reauthentication information associated with the client. In a more specific embodiment, the authentication server includes an Authentication, Authorization, and Accounting (AAA) server. The SGW further includes one or more routines for employing the reauthentication information to reauthenticate the client. The AAA server performs initial authentication of the client to enable client access to the network, which yields the reauthentication information. The reauthentication information includes one or more keys and/or counters, such as an authorization key, an encryption key, and a master key, which is/are predetermined by the AAA server.
Abstract:
Providing a multicast service includes maintaining multicast service information at an application server (50). The multicast service information describes a multicast service having an associated subscriber, and the multicast service is operable to deliver multicast content from a multicast source (12). A cell supporting a user device (20) associated with the subscriber is determined, and creation of a bearer path for the multicast service is initiated. Delivery of the multicast content to the user device is enabled using the bearer path.
Abstract:
Anchoring a communication session for a target mobile phone includes identifying a current access node operable to provide the target mobile phone access to a first network of a first network type. Potential access nodes operable to provide a mobile phone access to a second network of a second network type are identified. Whether the communication session can be handed off to a potential access node of the one or more potential access nodes is established. Anchoring of the communication session is initiated in the second network only if the communication session can be handed off to a potential access node of the one or more potential access nodes.
Abstract:
An Unlicensed Mobile Access (UMA) network architecture. In a specific embodiment, the network architecture includes a mobile station and an access point in communication with the mobile station. A UMA Controller (UNC) communicates with the access point. A Service GateWay (SGW) communicates with the UMA controller. The SGW includes functionality to route user-plane packets in the UMA. In a more specific embodiment, the functionality includes UNC user-plane functionality offloaded from the UNC to the SGW; Serving GPRS Support Node (SGSN) user-plane functionality; access-authentication functionality sufficient to enable the SGW to enable the SGW to bypass a legacy SGSN control plane; and/or Radio Network Controller (RNC) user-plane functionality sufficient to enable communications between the SGW and the RNC.
Abstract:
In one embodiment, while bei.ng connected, to the network (110), a security issue may be detected and associated with a device (104). The device may be placed on a blacklist for the security issue. The blacklist is a list that is used to deny service for the device when it attempts to connect. Thus, the device is disconnected from the. network. Identification information for the device is added to the blacklist at the authentication server (102). If the device attempts to reconnect to the network, the request is received at the authentication server. The authentication server can then check the blacklist and deny the request for access to the network if the identification information is on the blacklist. This denial is determined without sending the request to the HLR (108). Accordingly, the HLR is protected in that requests from a device that may be considered a security issue are not sent to the HLR.
Abstract:
Systems and/or methods of selectively terminating security in mobile networks are presented. User equipment (UE) can specify cipher termination location capabilities for encryping/decrypting data packets to a base station in a mobile network. The mobile network can subsequently determine at which node in the network to terminate the cipher in part according to the capabilities provided and deliver the determined location to the UE. The determined cipher termination location can be provided in response to a request to initiate communications, the initial request can specify the capabilities. The UE can utilize the location to support disparate types of networks and to intelligently deal with hand-offs and other functions of the mobile network.
Abstract:
In one embodiment, a network application may offload stateful operations to a user-plane application. In one embodiment, the network application receives state information for a user device. The network application then sends the state information to a user-plane application, which can maintain the state information. The network application may then offload a stateful operation to the user-plane application. For example, the network application may have the user-plane application perform stateful operations. Also, the network application may use the state information maintained at the user-plane application for error recovery after the network application fails. For example, the network application may recover the state information from the user-plane application after failure.
Abstract:
Techniques and systems for server farm load balancing and resource allocation are disclosed. In one embodiment, a method of load balancing can include: arranging servers into service groups; receiving an access request with information related to a differentiation between the service groups; selecting one of the service groups based on a mapping comparison to the information; and selecting one of the servers within the selected service group based on a hardware utilization comparison. The servers can include GPRS (General Packet Radio Service) Gateway Support Node (GGSN) or Remote Authentication Dial In User Service (RADIUS) servers, for example. The information can include an Access Point Name (APN) or Calling Station ID, for example.