Abstract: The disclosure relates generally to supporting bonded services at non-anchor nodes. A non-anchor gateway device is configured to support service bonding for a user device and communication with an anchor node of the user device. The non-anchor gateway device is configured to associated a set of user device data plane connections of the user device to form a bonded session for the user device where the set of user device data plane sessions includes a first user device data plane connection associated with a first access network and a second user device data plane connection associated with a second access network. The non-anchor gateway device is configured to map user device traffic of the user device between the user device data plane connections of the bonded session and a user device data plane session between the gateway device and the anchor node for the user device.

Abstract: The disclosure relates generally to supporting bonded services at non-anchor nodes. A non-anchor gateway device is configured to support service bonding for a user device and communication with an anchor node of the user device. The non-anchor gateway device is configured to associated a set of user device data plane connections of the user device to form a bonded session for the user device where the set of user device data plane sessions includes a first user device data plane connection associated with a first access network and a second user device data plane connection associated with a second access network. The non-anchor gateway device is configured to map user device traffic of the user device between the user device data plane connections of the bonded session and a user device data plane session between the gateway device and the anchor node for the user device.

Abstract: The disclosure relates generally to supporting a maximum fill link capability for a bonded session. The maximum fill link capability may be configured to control allocation of user device traffic of a user device across multiple bearers of a bonded data plane session supported for the user device. The maximum fill link capability may be provided at a gateway device associated with the bonded data plane session, which may be a network gateway device for downstream user device traffic or a customer gateway device for upstream user device traffic. The maximum fill link capability may be configured to determine an allocation of the user device traffic of a user device data plane session to multiple bearers of the user device data plane session based on policy information associated with the user device data plane session and based on traffic monitoring performed for the user device traffic of the user device data plane session.

Abstract: Systems, methods, apparatus and mechanism for maintaining an existing UE control session attachment while changing bearers of a UE data session, such as migrating between UMTS and non-UMTS bearers terminating at a common gateway device.

Abstract: Methods, systems and apparatus for associating packets or traffic flows with service functions to be applied thereto such that repeated identification of the packets or traffic flows at each of multiple service delivery modules may be avoided.

Abstract: Systems, methods, apparatus and mechanism for maintaining an existing UE control session attachment while changing bearers of a UE data session, such as migrating between UMTS and non-UMTS bearers terminating at a common gateway device.

Abstract: A method and system for managing a backup service gateway (SGW) associated with a primary SGW, comprising periodically receiving from the primary SGW at least a portion of corresponding UE session state information, the received portion of session state information being sufficient to enable the secondary SGW to indicate to an inquiring management entity that all user sessions associated with a group of mobile devices supported by the primary SGW are in a live state; and in response to a failure of the primary SGW, assuming management of IP addresses and paths associated with the primary SGW and causing each UE supported by the failed primary SGW to reauthorize itself to the network.

Abstract: A method, system and apparatus for managing a backup service gateway (SGW) associated with a primary SGW, the backup SGW periodically receiving from the primary SGW at least a portion of corresponding UE session state information and in response to a failure of the primary SGW, assuming management of IP addresses and paths associated with the primary SGW, and in response to receiving control or data plane traffic associated with a UE, generating a Downlink Data Notification (DDN) message adapted to inform an MME that the UE is in a live state.

Abstract: Method, system and apparatus for identifying and binding together in one session multiple data bearing paths through various access technologies between a Packet Gateway (PGW) and Customer Premises Equipment (CPE) to form thereby a bonded service combining wireless and wireline bearers.

Abstract: A method, system and apparatus for reversion of UE sessions from a backup SGW or protect node to an operationally restored primary SGW or working node.

Abstract: A method, system and apparatus for reversion of UE sessions from a backup SGW or protect node to an operationally restored primary SGW or working node.

Abstract: A method, system and apparatus for managing a backup service gateway (SGW) associated with a primary SGW, the backup SGW periodically receiving from the primary SGW at least a portion of corresponding UE session state information and in response to a failure of the primary SGW, assuming management of IP addresses and paths associated with the primary SGW, and in response to receiving control or data plane traffic associated with a UE, generating a Downlink Data Notification (DDN) message adapted to inform an MME that the UE is in a live state.

Abstract: A method and system for managing a backup service gateway (SGW) associated with a primary SGW, comprising periodically receiving from the primary SGW at least a portion of corresponding UE session state information, the received portion of session state information being sufficient to enable the secondary SGW to indicate to an inquiring management entity that all user sessions associated with a group of mobile devices supported by the primary SGW are in a live state; and in response to a failure of the primary SGW, assuming management of IP addresses and paths associated with the primary SGW and causing each UE supported by the failed primary SGW to reauthorize itself to the network.