Abstract:
Provisioning and access control for communication nodes involves assigning identifiers to sets of nodes where the identifiers may be used to control access to restricted access nodes that provide certain services only to certain defined sets of nodes. In some aspects provisioning a node may involve providing a unique identifier for sets of one or more nodes such as restricted access points and access terminals that are authorized to receive service from the restricted access points. Access control may be provided by operation of a restricted access point and/or a network node. In some aspects, provisioning a node involves providing a preferred roaming list for the node. In some aspects, a node may be provisioned with a preferred roaming list through the use of a bootstrap beacon.
Abstract:
A method, an apparatus, and a computer program product for wireless communication are provided. The apparatus may be an eNB. In one configuration the eNB may establish a connection to a remote apparatus, receive a message from the remote apparatus indicating that the connection is supporting one of background traffic or active traffic, determine whether the connection is supporting the background traffic or the active traffic using the message, and set a time value for a state timer related to an operating state of the remote apparatus based on whether the connection is supporting the background traffic or the active traffic. In another configuration the eNB may establish a connection to a remote apparatus and disable one or more modes of communication based on whether the connection is supporting the background traffic or the active traffic.
Abstract:
An indication is used to control how message service information is routed over different domains. For example, an access terminal may be configured with an indication that indicates that a message service is preferred to be invoked over an IP domain or that the message service is not be invoked over the IP domain. The access terminal then delivers message service information based on the value of the indication. In some cases, a network entity generates the indication and sends the indication to the access terminal. In some cases, a domain for delivery of message service information is selected based on a domain that was selected for particular type of traffic.
Abstract:
Providing for select Internet Protocol traffic offload (SIPTO) in a mobile communication environment is described herein. By way of example, SIPTO traffic can be facilitated via local packet gateways (P-GWs) that provide an interface to the Internet or a like data network, in addition to a centralized gateway GPRS support node (GGSN). Eligibility for SIPTO can be on a user equipment (UE) by UE basis; for instance, relying on stored subscription or account information to determine SIPTO eligibility. In particular aspects, eligibility for SIPTO can also be based on a packet network by packet network basis, or a combination of the foregoing. This enables flexibility in determining whether SIPTO can be established for a given UE in a given location, and can be based for instance on UE capability, subscription status information, data network capability, tariff rates, and so on, as well as different legal requirements of government jurisdictions.
Abstract:
A CS fallback procedure handles conflict that may arise when handover operations occur during CS fallback. If CS fallback is initiated for an access terminal and handover of that access terminal is then initiated before the CS fallback completes, the target for the handover is informed of the CS fallback so that the target may perform the appropriate CS fallback operations.
Abstract:
Systems, methodologies, and devices are described that manage employment of network (NW)-initiated resource allocation and user equipment (UE)-initiated resource allocation for a UE. To employ NW-initiated resource allocation, a core network can transmit an indicator to the UE indicating that Policy and Charging Control (PCC) is supported by a network associated with the UE. The UE receives the indicator and other information, such as indicator regarding whether the current access network supports NW-initiated resource allocation and whether the current application prefers NW-initiated resource allocation, determines that NW-initiated resource allocation is to be employed, and the core network initiates resource allocation for the UE. If any indicator is not received by the UE, or the UE receives an indicator that indicates PCC is not supported or not preferred, the UE determines that UE-initiated resource allocation is to be employed, and transmits a request for resource allocation to the core network.
Abstract:
Systems, methodologies, and devices are described that manage employment of network (NW)-initiated resource allocation and user equipment (UE)-initiated resource allocation for a UE. To employ NW-initiated resource allocation, a core network can transmit an indicator to the UE indicating that Policy and Charging Control (PCC) is supported by a network associated with the UE. The UE receives the indicator and other information, such as indicator regarding whether the current access network supports NW-initiated resource allocation and whether the current application prefers NW-initiated resource allocation, determines that NW-initiated resource allocation is to be employed, and the core network initiates resource allocation for the UE. If any indicator is not received by the UE, or the UE receives an indicator that indicates PCC is not supported or not preferred, the UE determines that UE-initiated resource allocation is to be employed, and transmits a request for resource allocation to the core network.
Abstract:
A CS fallback procedure handles conflict that may arise when handover operations occur during CS fallback. If CS fallback is initiated for an access terminal and handover of that access terminal is then initiated before the CS fallback completes, the target for the handover is informed of the CS fallback so that the target may perform the appropriate CS fallback operations.
Abstract:
Systems and methodologies are described that facilitate multiplexing communications from multiple downstream access points to one or more mobility management entities (MME). In particular, a concentrator component is provided that can establish a single transport layer connection with an MME along with multiple application layer connections over the single transport layer connection for each of multiple downstream access points and/or related mobile devices. The downstream access points and/or mobile devices can provide identifiers to the concentrator component, which can utilize the identifiers to track communications with the MME. In this regard, the MME can additionally include identifiers received from the concentrator component in subsequent communications to facilitate identifying the appropriate downstream access point and/or mobile device.
Abstract:
Systems and methodologies are described that facilitate fetching a native security context between network nodes in a core network after an inter-system handover of a mobile device. For instance, a mobility message that is integrity protected by a security context (e.g., the native security context, a mapped security context,..) can be obtained at a network node from the mobile device. Further, the network node can send a request to a disparate network node within a core network. The request can include information that can be used by the disparate network node to establish that the mobile device is authenticated. Moreover, the native security context can be received from the disparate network node in response to the request. Accordingly, the native security context need not be recreated between the network node and the mobile device.