Abstract: Techniques are presented in which a new information element signaling priority of a management entity is included in a setup (e.g., S1-Setup) response or configuration update message sent by a management entity to a base station entity. The base station entity interprets this priority information along with the relative capacity information in an appropriate way to load-distribute the traffic/calls to highly preferable management entity instances (at a local site) when they are available, and switchover/failover to lower preference management entity instances (at a remote site) when there is a local site outage/failure or insufficient capacity in a geo-resilient pooled network.

Abstract: In a Fifth Generation (5G) network having an enhanced SBA (eSBA) architecture, a message with a header used to signal binding information (e.g. HTTP custom header for 3gpp-Sbi-Binding) may be received at a recipient NF (service) instance in a direct communication or via a service communication proxy (SCP) in an indirect communication. A binding indication comprising an address of an NF (service) instance may be obtained from the header. One or more alternative binding indications comprising one or more alternative addresses of one or more alternative NF (service) instances may also be obtained from the header. The one or more alternative NF (service) instances may be equivalent NFs (services) of the same NF (Service) Set as the NF (service) instance. The address may be used for communication of messages to the NF (service) instance, and the one or more alternative addresses may be used for load balancing or backup failure.

Abstract: A network slice controller obtains health information of an active network slice provided by a first vendor and health information of a set of backup network slices provided by a second vendor. The network slice controller evaluates, using a set of policies corresponding to management of the active network slice, the health information of the active network slice to determine whether the active network slice has failed. As a result of the failure of the active network slice, the network slice controller identifies one or more backup network slices of the set of backup network slices to serve as new active network slices. The network slice controller activates these one or more backup network slices to serve as the new active network slices for the network.

Abstract: Presented herein are efficient techniques through which a Third Generation Partnership Project (3GPP) Access and Mobility Management Function (AMF) may retrieve information for a Mobility Management Entity (MME) to support graceful mobility for various inter-Radio Access Technology (inter-RAT) mobility scenarios. In one example, a method includes determining, by an AMF, an inter-RAT mobility event for a user equipment; identifying, by the AMF, an MME associated with the inter-RAT mobility event based, at least in part, on MME information contained in a network database; and transferring context information for the user equipment between the AMF and the MME. In one instance, the network database may be a Network Repository Function (NRF) for a 3GPP Fifth Generation mobile network and the MME information may be associated with an MME network function type stored in the NRF.

Abstract: Presented herein are techniques to facilitate dynamic negotiation and compression of Packet Forwarding Control Protocol (PFCP) messages in a mobile networking environment. In one example, a method includes identifying, by a function, a negotiated compression algorithm to utilize for compressing one or more Packet Forwarding Control Protocol (PFCP) messages; determining whether a payload for a particular PFCP message is to be compressed based on at least one of system resources of the function and a size of the payload; based on determining that the payload is to be compressed, compressing the payload utilizing the negotiated compression algorithm to generate a compressed PFCP message; and setting a compression indication in a header of the compressed PFCP message.

Abstract: Techniques are described herein for network slice support of respective transport protocols. In one example, a session management function obtains, from a user equipment, a request for a network slice identifier in a network that includes a plurality of network slices each configured to support a respective transport protocol. In response to the request, the session management function identifies a first transport protocol of the respective transport protocols by which the user equipment is to communicate. Based on the first transport protocol, the session management function identifies a first network slice of the plurality of network slices by which the user equipment is to communicate. The first network slice is configured to support the first transport protocol. The session management function provides the network slice identifier to the user equipment. The network slice identifier corresponds to the first network slice.

Abstract: Techniques are described herein for network slice support of respective transport protocols. In one example, a session management function obtains, from a user equipment, a request for a network slice identifier in a network that includes a plurality of network slices each configured to support a respective transport protocol. In response to the request, the session management function identifies a first transport protocol of the respective transport protocols by which the user equipment is to communicate. Based on the first transport protocol, the session management function identifies a first network slice of the plurality of network slices by which the user equipment is to communicate. The first network slice is configured to support the first transport protocol. The session management function provides the network slice identifier to the user equipment. The network slice identifier corresponds to the first network slice.

Abstract: An example method is provided in one example embodiment and may include receiving traffic associated with at least one of a mobile network and a Gi-Local Area Network (Gi-LAN), wherein the traffic comprises one or more packets; determining a classification of the traffic to a service chain, wherein the service chain comprises one or more service functions associated at least one of one or more mobile network services and one or more Gi-LAN services; routing the traffic through the service chain; and routing the traffic to a network using one of a plurality of egress interfaces, wherein each egress interface of the plurality of egress interfaces is associated with at least one of the one or more mobile network services and the one or more Gi-LAN services.

Abstract: In one example, an indication that a user equipment participating in a Packet Data Network (PDN) session hosted by a Serving Gateway (SGW) and a PDN Gateway (PGW) is transitioning from a first Mobility Management Entity (MME) to a second MME is obtained. An indication that the SGW is co-located with the PGW and an identification of the SGW are obtained. Based on the indication that the SGW is co-located with the PGW and the identification of the SGW, it is determined that the SGW is reachable from the second MME. In response to determining that the SGW is reachable from the second MME, the SGW is selected to host the PDN session after the user equipment transitions from the first MME to the second MME.

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 one example, a first connectivity request for a first network connection between a user equipment and a first network is obtained. A control plane serving gateway node for the first network connection is selected. The control plane serving gateway node is co-located with a control plane packet data network gateway node configured to support a second network connection between the user equipment and a second network that is different from the first network. A second connectivity request for the second network connection is obtained. The second network connection is established with the control plane serving gateway node and the control plane packet data network gateway node.

Abstract: A control plane of a network, including radios of a radio access network controlled by the control plane and user plane functions controlled by the control plane, establishes first and second protocol data unit (PDU) connections each to handle the same flows of traffic for ultra-reliable low latency communications (URLLC) from user equipment to a data network through first and second source radios, respectively. Due to mobility of the user equipment, the control plane relocates the flows from the first and second source radios to first and second target radios, respectively. To relocate the flows, the control plane receives from the first target radio a notification that identifies flows that cannot be activated on the first target radio. In response to the notification, the control plane commands the first target radio to prioritize the flows that cannot be activated above remaining ones of the flows.

Abstract: A network slice controller obtains health information of an active network slice provided by a first vendor and health information of a set of backup network slices provided by a second vendor. The network slice controller evaluates, using a set of policies corresponding to management of the active network slice, the health information of the active network slice to determine whether the active network slice has failed. As a result of the failure of the active network slice, the network slice controller identifies one or more backup network slices of the set of backup network slices to serve as new active network slices. The network slice controller activates these one or more backup network slices to serve as the new active network slices for the network.

Abstract: Presented herein are techniques to facilitate dynamic negotiation and compression of Packet Forwarding Control Protocol (PFCP) messages in a mobile networking environment. In one example, a method includes identifying, by a function, a negotiated compression algorithm to utilize for compressing one or more Packet Forwarding Control Protocol (PFCP) messages; determining whether a payload for a particular PFCP message is to be compressed based on at least one of system resources of the function and a size of the payload; based on determining that the payload is to be compressed, compressing the payload utilizing the negotiated compression algorithm to generate a compressed PFCP message; and setting a compression indication in a header of the compressed PFCP message.

Abstract: In one embodiment, a method comprises communicating with a plurality of network elements via a first communication protocol to obtain state information of the plurality of network elements; receiving a request via a second communication protocol for a communication session to be established for a client computing device; selecting one or more network elements, wherein the selection is based on at least a portion of the state information of the network elements; and communicating identification information of the one or more network elements selected for use in the communication session.

Abstract: In one example, an indication that a user equipment participating in a Packet Data Network (PDN) session hosted by a Serving Gateway (SGW) and a PDN Gateway (PGW) is transitioning from a first Mobility Management Entity (MME) to a second MME is obtained. An indication that the SGW is co-located with the PGW and an identification of the SGW are obtained. Based on the indication that the SGW is co-located with the PGW and the identification of the SGW, it is determined that the SGW is reachable from the second MME. In response to determining that the SGW is reachable from the second MME, the SGW is selected to host the PDN session after the user equipment transitions from the first MME to the second MME.

Abstract: A solution for selecting an optimal user Plane entity (with Control and User Plane Separation (CUPS)) per UE during seamless roaming. In one embodiment, a method is provide that is performed by a control plane entity in a mobile core network that supports inter public land mobile network (PLMN) roaming among two or more PLMNs. The method includes obtaining a create session request from an entity in a second PLMN to which a user equipment has roamed from a first PLMN; selecting a particular user plane entity among a plurality of user plane entities based on one or more user equipment related parameters; and establishing a session with the particular user plane entity to serve user plane traffic in the mobile core network for the user equipment.

Abstract: Presented herein are efficient techniques through which a Third Generation Partnership Project (3GPP) Access and Mobility Management Function (AMF) may retrieve information for a Mobility Management Entity (MME) to support graceful mobility for various inter-Radio Access Technology (inter-RAT) mobility scenarios. In one example, a method includes determining, by an AMF, an inter-RAT mobility event for a user equipment; identifying, by the AMF, an MME associated with the inter-RAT mobility event based, at least in part, on MME information contained in a network database; and transferring context information for the user equipment between the AMF and the MME. In one instance, the network database may be a Network Repository Function (NRF) for a 3GPP Fifth Generation mobile network and the MME information may be associated with an MME network function type stored in the NRF.

Abstract: A solution for selecting an optimal user Plane entity (with Control and User Plane Separation (CUPS)) per UE during seamless roaming. In one embodiment, a method is provide that is performed by a control plane entity in a mobile core network that supports inter public land mobile network (PLMN) roaming among two or more PLMNs. The method includes obtaining a create session request from an entity in a second PLMN to which a user equipment has roamed from a first PLMN; selecting a particular user plane entity among a plurality of user plane entities based on one or more user equipment related parameters; and establishing a session with the particular user plane entity to serve user plane traffic in the mobile core network for the user equipment.

Abstract: A Centralized Self Organizing Network (C-SON) automation platform for managing a backhaul infrastructure in a telecommunication network. The C-SON automation platform monitors one or more backhaul utilization performance indicators corresponding to a backhaul infrastructure, which infrastructure transports data between one or more User Equipment (UE) connected to a small cell and a data network. The C-SON further receives subscriber data for at least one User Equipment (UE) and location data for the at least one UE from at least one Network Function (NF), and maps the at least one UE to a backhaul service flow and the small cell based on the subscriber data and the location data. The C-SON automation platform determines the backhaul utilization performance indicator exceeds a backhaul threshold limit for the backhaul service flow, and adjusts a bandwidth utilization of the backhaul infrastructure based on the backhaul utilization parameter exceeding the backhaul threshold limit.