Abstract: A control plane (CP) entity is to adaptively reroute user plane traffic of a mobile node (MN) with use of a segment routing (SR) for IPv6. A message indicating an attachment of the MN to the mobile network is received selecting a first user plane (UP) anchor node. A first set of home network prefixes (HNPs) are allocated to the MN. An IP traffic flow using a first HNP prefix is established between the MN and a correspondent node (CN) along a first network path—defined at least in part by the first UP anchor node and an anchor node of the CN. In response to a handover of the MN, a message indicating a subsequent attachment of the MN is received selecting a second UP anchor node. The second UP anchor node is instructed to host the first HNP prefix previously allocated by the first UP anchor node.

Abstract: Various implementations disclosed herein enable programming user plane gateway controllers over enhanced N9 interfaces. In various implementations, a method of gateway controlling is performed by a computing device including one or more processors, and a non-transitory memory. In various implementations the method includes determining, by a first packet gateway controller connected to a first session manager device, that a user equipment moved to a geographical area that is served by a second session manager device. In some implementations, the method includes receiving, by the first packet gateway device, a set of information for a second packet gateway device. In some implementations, the method includes transmitting, by the first packet gateway device, a session establishment request via a first network interface to the second packet gateway controller using segment routing via a second network interface.

Abstract: A control plane (CP) entity is to adaptively reroute user plane traffic of a mobile node (MN) with use of a segment routing (SR) for IPv6. A message indicating an attachment of the MN to the mobile network is received selecting a first user plane (UP) anchor node. A first set of home network prefixes (HNPs) are allocated to the MN. An IP traffic flow using a first HNP prefix is established between the MN and a correspondent node (CN) along a first network path—defined at least in part by the first UP anchor node and an anchor node of the CN. In response to a handover of the MN, a message indicating a subsequent attachment of the MN is received selecting a second UP anchor node. The second UP anchor node is instructed to host the first HNP prefix previously allocated by the first UP anchor node.

Abstract: In accordance with various embodiments, a method is performed including establishing a first communication session between an application function and a user equipment assigned a first IP address. The method includes determining, by the application function, that the user equipment has changed location. The method includes, in response to determining that the user equipment has changed location, sending, by the application function, a request that the user equipment be assigned a second IP address. The method includes establishing a second communication session between the application function and the user equipment assigned the second IP address.

Abstract: A control plane (CP) entity is to adaptively reroute user plane traffic of a mobile node (MN) with use of a segment routing (SR) for IPv6. A message indicating an attachment of the MN to the mobile network is received selecting a first user plane (UP) anchor node. A first set of home network prefixes (HNPs) are allocated to the MN. An IP traffic flow using a first HNP prefix is established between the MN and a correspondent node (CN) along a first network path—defined at least in part by the first UP anchor node and an anchor node of the CN. In response to a handover of the MN, a message indicating a subsequent attachment of the MN is received selecting a second UP anchor node. The second UP anchor node is instructed to host the first HNP prefix previously allocated by the first UP anchor node.

Abstract: Policy enforcement may be provided. First, a Policy and Charging Enforcement Function (PCEF) server may receive a plurality of network policies along with validity information. The PCEF server may receive a first set of connectivity data associated with a subscriber session. Next, the PCEF server may analyze the first set of connectivity data to determine a first set of policies. The PCEF may then enforce those policies. The PCEF may further receive a second set of connectivity data associated with the subscriber session. The second set of connectivity data may indicate, for example, a change in radio access technology of the subscriber session or a change in location of a subscriber device. Next, the PCEF may analyze the second set of connectivity data to determine a second set of policies to enforce without interacting with a Policy and Charging Rules Function server. The PCEF may then enforce those policies.