Abstract: When a packet data session is established for a user equipment (UE), a comparative assessment of load information factors from different sets of load information factors associated with a plurality of user plane function (UPF) instances may be performed. Each set of load information factors of a UPF instance may include predicted load information factors indicative of a predicted load at the UPF instance. A UPF instance may be selected for the packet data session of the UE based on the comparative assessment. The comparative assessment may additionally consider a predicted load contribution of the packet data session to be established for the UE. A data analytics function may utilize a model (e.g. a multiple linear regression model) to calculate predicted load contribution factors, where the model is derived based on historical usage data from previous sessions of one or more UEs, for example, data from charging data records (CDRs).

Abstract: Methods are provided to preemptively reconfigure a mobile network to respond to external emergencies. The method is performed at a network device of a service provider which provides access to a mobile network for wireless device. The method includes obtaining a message indicating an occurrence of a disaster. The message includes at least an emergency type and location information. The method further includes determining, based on the emergency type, a reconfiguration policy for reconfiguring the mobile network in an area indicated by the location information and reconfiguring the mobile network based on the reconfiguration policy. The method further includes authenticating a disaster application function and a notification message informing about an occurrence of a disaster.

Abstract: In one example, a Network Functions Virtualization Orchestrator (NFVO) obtains a radio service descriptor defining communication parameters for a radio in a virtual Radio Access Network (vRAN). Based on the radio service descriptor, the NFVO determines whether a virtual Distributed Unit (vDU) that is configured in accordance with the communication parameters and a virtual Centralized Unit (vCU) that is configured in accordance with the communication parameters are already instantiated in the vRAN. If it is determined that the vDU or the vCU is not already instantiated, the NFVO automatically instantiates the vDU or the vCU in the vRAN.

Abstract: A system is provided that includes one management cluster to manage network function virtualization infrastructure (NFVI) resources lifecycle in more than one edge POD locations, where resources include hardware and/or software, and where software resources lifecycle includes software development, upgrades, downgrades, logging, monitoring etc. Methods are provided for decoupling storage from compute and network functions in each virtual machine (VM)-based NFVI deployment location and moving it to a centralized location. Centralized storage could simultaneously interact with more than one edge PODs, and the security is built-in with periodic key rotation. Methods are provided for increasing NFVI system viability by dedicating (fencing) CPU core pairs for specific controller operations and workload operations, and sharing the CPU cores for specific tasks.

Abstract: In one example, a Virtual Network Function Manager (VNFM) obtains, from a monitoring agent that is configured to monitor a Virtual Network Function (VNF) for a presence of a technical issue with the VNF, an indication of the presence of the technical issue with the VNF. The monitoring agent is deployed at a remote site. Based on the indication of the presence of the technical issue with the VNF, the VNFM determines a resolution for the presence of the technical issue with the VNF. The VNFM automatically implements the resolution for the presence of the technical issue with the VNF.

Abstract: Techniques for policy management and enforcement using semantic data modeling are provided. A first declarative policy is received at a network node from a controller. A first semantic data query protocol (SDQP) transaction is generated by retrieving a first semantic data model associated with the network node, where the first semantic data model describes a configuration domain of the network node, and parsing the first declarative policy based on the first semantic data model to generate the first SDQP transaction. The first declarative policy is then implemented by executing the first SDQP transaction against a semantic database.

Abstract: A network function (NF) entity in a communication network receives User Plane Function (UPF) registration information for a plurality of UPFs, the registration information including a respective network attribute for each UPF. The NF entity associates each UPF with a corresponding network based on the respective network attribute, and map one or more User Equipment (UE) to the corresponding network based on a security policy to create a UE-to-network table. The NF further receives a request to establish a session for a subsequent UE, the request including a subsequent UE identifier, and determine an access permission for the subsequent UE to access the corresponding network based on the subsequent UE identifier and the UE-to-network table. The NF selects one UPF from the plurality of UPF to service the session for the subsequent UE based on the access permission, and an association between the one UPF and the corresponding network.

Abstract: Techniques are provided to inform a mobile packet core of the access network/radio access technology (AN/RAT) change with the use of in-band signaling along the user plane and hence reduce signaling between radio access network and mobile packet core network. A new extension header content is defined to signal the AN/RAT change information, Cell Group changes and acknowledging the same. Further still, a method is provided to handle AN change notification for split bearer scenarios by introducing a split bearer flag for the mobile packet core to be notified of the predominant access type serving the subscriber data session in 5G Non-Stand Alone (NSA) Option-3, Option-3A and Option-3X, so that static or dynamic configurations can be applied by the mobile core network accordingly.

Abstract: Techniques are provided to communicate the serving Radio Access Network (RAN) element information to the packet core network to enable operators to provide differential treatment for fifth generation (5G) subscribers. The techniques presented herein fill these gaps and help drive faster adoption of Dual Connectivity New Radio (DCNR) subscribers by service operator to offer customized policy and quota management to address different business requirements in the 5G Non-Stand Alone (NSA) architecture.

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: 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: 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 system is provided that includes one management cluster to manage network function virtualization infrastructure (NFVI) resources lifecycle in more than one edge POD locations, where resources include hardware and/or software, and where software resources lifecycle includes software development, upgrades, downgrades, logging, monitoring etc. Methods are provided for decoupling storage from compute and network functions in each virtual machine (VM)-based NFVI deployment location and moving it to a centralized location. Centralized storage could simultaneously interact with more than one edge PODs, and the security is built-in with periodic key rotation. Methods are provided for increasing NFVI system viability by dedicating (fencing) CPU core pairs for specific controller operations and workload operations, and sharing the CPU cores for specific tasks.

Abstract: In one example, a Network Functions Virtualization Orchestrator (NFVO) obtains a radio service descriptor defining communication parameters for a radio in a virtual Radio Access Network (vRAN). Based on the radio service descriptor, the NFVO determines whether a virtual Distributed Unit (vDU) that is configured in accordance with the communication parameters and a virtual Centralized Unit (vCU) that is configured in accordance with the communication parameters are already instantiated in the vRAN. If it is determined that the vDU or the vCU is not already instantiated, the NFVO automatically instantiates the vDU or the vCU in the vRAN.

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: In one embodiment, a method includes determining a first configuration information for configuring a user plane device of the first network slice associated with the control plane device, generating a first configuration identifier based on the first configuration information, sending, to the user plane device of the first network slice, the first configuration identifier and the first configuration information, receiving, from the user plane device of the first network slice, a second configuration identifier, wherein the second configuration identifier is generated by the user plane device of the first network slice based on the first configuration information received from the control plane device, and verifying, by comparing the first configuration identifier and the second configuration identifier, that the user plane device of the first network slice is configured using the first configuration information.

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: Techniques are provided that leverage inband metadata techniques for use in a mobile core network in order to create relevant third generation 3rd Generation Partnership Project (3GPP) control plane interfaces between virtual control plane and virtual user plane elements that can be used to instruct the virtual entities to perform various functions, collect telemetry and other data from the virtual entities and signal maintenance messages between control plane and user plane entities. One control plane interface can be used to perform holistic performance analysis functionalities and identify the better performing path and accordingly use primary path and warm paths for control plane exchanges.

Abstract: A first virtual machine executing on a centralized management node provides a first image file to a first computing entity arranged within a first point of delivery. The first image file includes a first boot configuration file or a first ramdisk file. A second virtual machine provides a second image file to a second computing entity arranged within a second point of delivery different from the first point of delivery. The second image file includes a second boot configuration file or a second ramdisk file. The first virtual machine provides a third image file to the first computing entity. The third image file comprises a first operating system installation file. The second virtual machine provides a fourth image file to the second computing entity. The fourth image file comprises a second operating system installation file.

Abstract: In one embodiment, a method includes determining a first configuration information for configuring a user plane device of the first network slice associated with the control plane device, generating a first configuration identifier based on the first configuration information, sending, to the user plane device of the first network slice, the first configuration identifier and the first configuration information, receiving, from the user plane device of the first network slice, a second configuration identifier, wherein the second configuration identifier is generated by the user plane device of the first network slice based on the first configuration information received from the control plane device, and verifying, by comparing the first configuration identifier and the second configuration identifier, that the user plane device of the first network slice is configured using the first configuration information.