Abstract: Presented herein are techniques to facilitate resiliency, overload control, and/or the like for an Access and Mobility Management Function (AMF) in a Third Generation Partnership Project (3GPP) mobile network architecture. In one instance, a method is provided that includes initiating, by a buddy AMF, a heartbeat exchange with a primary AMF. The method may further include identifying a status condition for the primary AMF by the buddy AMF based on the heartbeat exchange and providing a status indication to a radio access network node by the buddy AMF based on the status condition for the primary AMF.

Abstract: A control plane (CP) function for mobility management may receive, from a user equipment (UE), a message which indicates a registration request for registration to a network slice. The CP function may select, as an allowed slice ID, a first slice ID of a first network slice in which to register the UE. The first slice ID has a slice/service type (SST) value indicating an SST and a first slice differentiator (SD) value associated with a first level of service to be provided. The CP function may alternatively select, as the allowed slice ID, a second slice ID of a second network slice in which to register the UE based on unavailability of the slice type associated with the first level of service. The second slice ID has the SST value indicating the slice type and a second SD value associated with a second level of service to be provided.

Abstract: A power management system in an information handling system includes multiple power supply units (PSU). A PSU is designated as a rapid on active PSU. Efficiencies on operating voltage and load of the information handling system in regard to the rapid on active PSU are gathered. Maximum efficiency value and minimum efficiency value of the rapid on active PSU are determined and used to turn on and off one or more PSUs designated as ability to sleep when the maximum efficiency value is reached and turning off the one or more PSUs designated as ability to sleep based on the minimum efficiency value.

Abstract: Presented herein are techniques to facilitate secure communications with an Application Function (AF) for a client device that does not support Authentication and Key Management for Applications (AKMA) functionality. In one example, a method includes obtaining, by a user plane function (UPF), a first uplink data packet from a client device, wherein the first uplink data packet is to be communicated to an application; determining, by the UPF based on the first uplink data packet, whether the client device supports AKMA functionality; based on determining that the client device does not support the AKMA functionality, buffering at least the first uplink data packet by the user plane function and determining whether the application supports the AKMA functionality; and based on determining that the application supports the AKMA functionality, performing AKMA functionality by the UPF for the client device for data communications between the client device and the application.

Abstract: A control plane function node may be used in a Fifth Generation (5G) Non-Standalone (NSA) architecture having Radio Access Network (RAN) level interworking between a Long-Term Evolution (LTE) RAN and a 5G New Radio (NR). The node obtains usage report data which are based on traffic of a user equipment (UE) via primary and secondary Radio Access Technologies (RATs). The node also obtains secondary RAT usage report data which are based on traffic of the UE via the secondary RAT. The node constructs a message which indicates a request for charging based on the usage report data and the secondary RAT usage report data. In constructing the message, the node populates, in association with a corresponding rating group and usage data of the UE, an identifier of a flow or bearer associated with secondary RAT usage, together with the secondary RAT usage report data.

Abstract: A network node selectively encrypts messages between a user plane node and a control plane node in a network system. The user plane node and the control plane node negotiate a connection and indicate an encryption level for the connection. The encryption level is selected from an Information Element (IE) level, a message level, or a feature level. The user plane node and the control plane node selectively encrypt at least a portion of the messages between the user plane node and the control plane node based on the encryption level for the connection.

Abstract: A network function selectively supports a mobile device with network settings appropriate for the device context of the mobile device. The network function obtains a device profile for the mobile device, which identifies multiple device groups, with each device group being associated with a corresponding set of network settings. The network function selects a device group among the device groups in the device profile based on the device context of the mobile device. The network function directs at least one network function in the network to support the mobile device with a set of network settings corresponding to the selected device group.

Abstract: The present technology is directed to routing a user equipment (UE) to a network node, for example, a gNB or ng-eNB that supports a slice requirement of the UE. A first network node can receive a Radio Resource Control (RCC) connection request from a UE, and can determine that a slice requirement of the UE is not supported by the first network node. The first network node can further select a second network node that supports the slice requirement of the UE, and route the UE to connect to the second network node.

Abstract: A computing device may be configured to provide a shared N4 termination function for a plurality of Session Management Function (SMF) instances of an SMF Set and interface with one or more User Plane Function (UPF) instances. To achieve this, the computing device may operate a server configured with a Remote Procedure Call (RPC)-based protocol (e.g. gRPC Remote Procedure Call or “gRPC”) for a Packet Forwarding Control Protocol (PFCP) message service for serving a plurality of client stubs respectively situated at the plurality of SMF instances. The server may perform processing associated with each client stub by receiving an RPC-based protocol message which indicates a request, unpacking the RPC-based protocol message for obtaining PFCP message request data, and operating or interfacing with a PFCP message handling client for sending a PFCP message having the PFCP message request data to an indicated one of the UPF instances.

Abstract: A computing device may be configured to provide a shared N4 termination function for a plurality of Session Management Function (SMF) instances of an SMF Set and interface with one or more User Plane Function (UPF) instances. To achieve this, the computing device may operate a server configured with a Remote Procedure Call (RPC)-based protocol (e.g. gRPC Remote Procedure Call or “gRPC”) for a Packet Forwarding Control Protocol (PFCP) message service for serving a plurality of client stubs respectively situated at the plurality of SMF instances. The server may perform processing associated with each client stub by receiving an RPC-based protocol message which indicates a request, unpacking the RPC-based protocol message for obtaining PFCP message request data, and operating or interfacing with a PFCP message handling client for sending a PFCP message having the PFCP message request data to an indicated one of the UPF instances.

Abstract: Presented herein are techniques to provide data session continuity for parallel data sessions involving a multiple Universal Subscriber Identity Module (MUSIM) user equipment (UE). In one example, a method may include obtaining an indication that session continuity for a first session associated with a first data network and a first USIM of a UE is allowed with respect to a second USIM in which the UE communicates first traffic for the first session via the first USIM. The method may further include determining that second traffic for a second session is to be communicated via the second USIM of the UE and, based on the indication that session continuity for the first session is allowed with respect to the second USIM, providing service information to the UE for the first session to enable the UE to communicate both the first traffic and the second traffic via the second USIM.

Abstract: A control plane function node may be used in a Fifth Generation (5G) Non-Standalone (NSA) architecture having Radio Access Network (RAN) level interworking between a Long-Term Evolution (LTE) RAN and a 5G New Radio (NR). The node obtains usage report data which are based on traffic of a user equipment (UE) via primary and secondary Radio Access Technologies (RATs). The node also obtains secondary RAT usage report data which are based on traffic of the UE via the secondary RAT. The node constructs a message which indicates a request for charging based on the usage report data and the secondary RAT usage report data. In constructing the message, the node populates, in association with a corresponding rating group and usage data of the UE, an identifier of a flow or bearer associated with secondary RAT usage, together with the secondary RAT usage report data.

Abstract: The present technology is directed to routing a user equipment (UE) to a network node, for example, a gNB or ng-eNB that supports a slice requirement of the UE. A first network node can receive a Radio Resource Control (RCC) connection request from a UE, and can determine that a slice requirement of the UE is not supported by the first network node. The first network node can further select a second network node that supports the slice requirement of the UE, and route the UE to connect to the second network node.

Abstract: A mechanism is provided to ensure the same user plane anchor point is selected as a User Equipment (UE) moves across multiple access networks. The selected User Plane Function (UPF) identifier information, such as a Fully Qualified Domain Name (FQDN) is passed to the UE anchor points. This will allow the UE anchor points to exchange the already selected user plane information so that the new UE anchor point can choose the same UPF.

Abstract: Presented herein are techniques to facilitate resiliency, overload control, and/or the like for an Access and Mobility Management Function (AMF) in a Third Generation Partnership Project (3GPP) mobile network architecture. In one instance, a method is provided that includes initiating, by a buddy AMF, a heartbeat exchange with a primary AMF. The method may further include identifying a status condition for the primary AMF by the buddy AMF based on the heartbeat exchange and providing a status indication to a radio access network node by the buddy AMF based on the status condition for the primary AMF.

Abstract: A method enables communication between Session Management Function (SMF) and User Plane Function (UPF) instances which are separately deployed behind Network Address Translation (NAT) services. The method includes configuring an SMF or a UPF to initiate an association with a corresponding UPF or SMF. The SMF registers first information with a Network Repository Function (NRF) enabling the remote UPF to communicate with the SMF through a NAT service. The method further includes obtaining second information from the NRF enabling the SMF to communicate with the remote UPF through the NAT service. The method also includes sending an association request to the remote UPF based on the second information and receiving an association response from the remote UPF through the NAT service.

Abstract: A method enables communication between Session Management Function (SMF) and User Plane Function (UPF) instances which are separately deployed behind Network Address Translation (NAT) services. The method includes configuring an SMF or a UPF to initiate an association with a corresponding UPF or SMF. The SMF registers first information with a Network Repository Function (NRF) enabling the remote UPF to communicate with the SMF through a NAT service. The method further includes obtaining second information from the NRF enabling the SMF to communicate with the remote UPF through the NAT service. The method also includes sending an association request to the remote UPF based on the second information and receiving an association response from the remote UPF through the NAT service.

Abstract: Techniques are described for policy driven on-demand tunnel creation and deletion between end points in a software-defined wide area network (SD-WAN) having a hub-and-spoke topology. A software-defined networking (SDN) controller that facilitates cloud-based services of a service provider network that sets up the SD-WAN is configured to determine whether a tunnel between end-points is to be created or deleted based on information indicative of the traffic, such as amount, time, application generating the traffic, and the like, between end-points.

Abstract: A mechanism is provided to ensure the same user plane anchor point is selected as a User Equipment (UE) moves across multiple access networks. The selected User Plane Function (UPF) identifier information, such as a Fully Qualified Domain Name (FQDN) is passed to the UE anchor points. This will allow the UE anchor points to exchange the already selected user plane information so that the new UE anchor point can choose the same UPF.

Abstract: A method enables communication between Session Management Function (SMF) and User Plane Function (UPF) instances which are separately deployed behind Network Address Translation (NAT) services. The method includes configuring an SMF or a UPF to initiate an association with a corresponding UPF or SMF. The SMF registers first information with a Network Repository Function (NRF) enabling the remote UPF to communicate with the SMF through a NAT service. The method further includes obtaining second information from the NRF enabling the SMF to communicate with the remote UPF through the NAT service. The method also includes sending an association request to the remote UPF based on the second information and receiving an association response from the remote UPF through the NAT service.