Abstract: A user device operates a first data session using a first network slice. The user device obtains a trigger notification from a remote application that identifies a second network slice, and the user device determines that the first network slice and the second network slice are mutually exclusive. The user device ends the first data session on the first network slice and initiates a second data session on the second network slice.

Abstract: In one illustrative example, a user plane function (UPF) configured for use in a private 5G network of an enterprise may receive, from a user device, a domain name system (DNS) query associated with an application; send, to a DNS server, one or more corresponding DNS queries based on the DNS query; receive, from the DNS server, one or more DNS query responses which include an IP address and metadata including an application identifier for the application; and send, to a control plane function, a message for reporting which includes the application identifier. In response, a dedicated Quality of Service (QoS) Flow may be created for traffic for the application according to a selected QoS policy associated with the application identifier. For obtaining the metadata, the UPF may interact with a DNS server configured with Extension mechanisms for DNS (EDNS) or a DNS as Authoritative Source (DNS-AS) mechanism.

Abstract: An enterprise private network includes a simplified Third Generation Partnership Project (3GPP) core architecture for interworking between an Evolved Packet System (EPS) and a Fifth Generation (5G) system (5GS). The architecture includes an Evolved Packet Core (EPC) control plane (CP) (EPC CP) unit and a 5G core (5GC) CP (5GC CP) unit. The 5GC CP unit receives, from the EPC CP unit via an N26 interface, a message indicating a forward relocation request responsive to an indication of a handover of a Packet Data Network (PDN) connection at a user plane node from the EPS to the 5GS. The 5GC CP node establishes a Protocol Data Unit (PDU) session corresponding to the PDN connection based on PDN connection information in the message, which includes establishing a Quality of Service (QoS) Flow corresponding to an EPS bearer, and manages the PDU session at the user plane node.

Abstract: An enterprise private network includes a simplified Third Generation Partnership Project (3GPP) core architecture for interworking between an Evolved Packet System (EPS) and a Fifth Generation (5G) system (5GS). The architecture includes an Evolved Packet Core (EPC) control plane (CP) (EPC CP) unit and a 5G core (5GC) CP (5GC CP) unit. The 5GC CP unit receives, from the EPC CP unit via an N26 interface, a message indicating a forward relocation request responsive to an indication of a handover of a Packet Data Network (PDN) connection at a user plane node from the EPS to the 5GS. The 5GC CP node establishes a Protocol Data Unit (PDU) session corresponding to the PDN connection based on PDN connection information in the message, which includes establishing a Quality of Service (QoS) Flow corresponding to an EPS bearer, and manages the PDU session at the user plane node.

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: In one illustrative example, a user plane function (UPF) configured for use in a private 5G network of an enterprise may receive, from a user device, a domain name system (DNS) query associated with an application; send, to a DNS server, one or more corresponding DNS queries based on the DNS query; receive, from the DNS server, one or more DNS query responses which include an IP address and metadata including an application identifier for the application; and send, to a control plane function, a message for reporting which includes the application identifier. In response, a dedicated Quality of Service (QoS) Flow may be created for traffic for the application according to a selected QoS policy associated with the application identifier. For obtaining the metadata, the UPF may interact with a DNS server configured with Extension mechanisms for DNS (EDNS) or a DNS as Authoritative Source (DNS-AS) mechanism.

Abstract: A Network Exposure Function (NEF) relays a trigger from a remote application function to a user device and causes the user device to switch between mutually exclusive network slices. The NEF stores a mapping associating device modes with network slices. The NEF also determines that a user device is operating in a first device mode using a first network slice. The NEF obtains a trigger from the remote application function identifying the user device and a second device mode. The NEF determines that the second device mode is associated with a second network slice that is mutually exclusive to the first network slice. The NEF provides a notification to the user device, causing the user device to end a first data session on the first network slice and to initiate a second data session on the second network slice.

Abstract: In one illustrative example, a user plane (UP) entity for use in a mobile network may receive a data packet from a user equipment (UE) operative to communicate in one or more sessions via a serving base station (BS) (e.g. eNB or gNB) of the mobile network. The UP entity may detect, in a header (e.g. SRH) of the data packet, an identifier indicating a new serving BS or session of the UE. The identifier may be UE- or BS-added data (e.g. iOAM data) that is inserted in the header by the UE or BS. In response, the UP entity may cause a message to be sent to an analytics function (e.g. a NWDAF) to perform analytics for session or flow migration for the UE.

Abstract: A first data plane is established between a user equipment device and a gateway device, wherein the user equipment device comprises a 3rd Generation Partnership Project (3GPP) user equipment device, and wherein the first data plane comprises a 3GPP data plane. A second data plane is established between the gateway device and an anchor device, wherein the second data plane comprises a Proxy Mobile Internet Protocol version 6 (PMIPv6) data plane. Mobility management is performed for the user equipment device via communications between the gateway device and the anchor device.

Abstract: In one illustrative example, a user plane function (UPF) configured for use in a private 5G network of an enterprise may receive, from a user device, a domain name system (DNS) query associated with an application; send, to a DNS server, one or more corresponding DNS queries based on the DNS query; receive, from the DNS server, one or more DNS query responses which include an IP address and metadata including an application identifier for the application; and send, to a control plane function, a message for reporting which includes the application identifier. In response, a dedicated Quality of Service (QoS) Flow may be created for traffic for the application according to a selected QoS policy associated with the application identifier. For obtaining the metadata, the UPF may interact with a DNS server configured with Extension mechanisms for DNS (EDNS) or a DNS as Authoritative Source (DNS-AS) mechanism.

Abstract: In one example, an Access Point (AP) configures a first mapping of a first cellular network connection to a first local access network group, and further configures a second mapping of a second cellular network connection to a second local access network group. The AP determines whether a user device is authorized to use the first cellular network connection or the second cellular network connection. If the user device is authorized to use the first cellular network connection, the AP associates, for the user device, a first user device identifier with the first local access network group. If the user device is authorized to use the second cellular network connection, the AP associates, for the user device, a second user device identifier with the second local access network group.

Abstract: Methods are provided for extending sponsored Wi-Fi guest access capability to other enterprise tools and/or access technologies such as private access networks including private LTE and 5G networks. The methods include a controller detecting a user equipment (UE) that is connected to a guest access service provided by a wireless local access network (WLAN) and generating a profile for the guest access service. The methods further include the controller providing, to the UE, the profile to cause the UE to connect to the guest access service provided by another access network.

Abstract: A Network Exposure Function (NEF) relays a trigger from a remote application function to a user device and causes the user device to switch between mutually exclusive network slices. The NEF stores a mapping associating device modes with network slices. The NEF also determines that a user device is operating in a first device mode using a first network slice. The NEF obtains a trigger from the remote application function identifying the user device and a second device mode. The NEF determines that the second device mode is associated with a second network slice that is mutually exclusive to the first network slice. The NEF provides a notification to the user device, causing the user device to end a first data session on the first network slice and to initiate a second data session on the second network slice.

Abstract: Presented herein are techniques to facilitate delivering standalone non-public network (SNPN) credentials from an enterprise authentication server to a user equipment (UE) using an Extensible Authentication Protocol (EAP) process. In one example, a method may include determining, by an authentication server of an enterprise, that a UE for the enterprise is to receive credentials to enable the UE to connect to a SNPN of the enterprise in which the determining is performed based, at least in part, on connection of the UE to an access network that is different than the SNPN for the enterprise; and performing an authentication process with the UE by the authentication server in which the authentication process includes providing the credentials to the UE via a first authentication message and obtaining confirmation from the UE via a second authentication message that indicates successful provisioning of the credentials for the UE.

Abstract: Techniques are described to provide ultra-reliability for cellular vehicle-to-everything (C-V2X) PC5 communications, including Network Assisted mode and Autonomous mode communications. In one example, a method includes receiving, by a radio unit of a system, a communication from a user equipment, such as a V2X-UE, wherein the communication comprises a data packet, a Layer 2 destination identifier, and an indication that the data packet is associated with a transmission type; determining whether transmission for the data packet is allowed for the transmission type; based on determining that transmission for the data packet is allowed for the transmission type, communicating a response to the UE, wherein the response provides a confirmation to the UE that the data packet was received by the radio unit and that the transmission type can be performed by the radio unit; and transmitting, by the radio unit, the data packet to one or more other UEs.

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: In one illustrative example, a user plane (UP) entity for use in a mobile network may receive a data packet from a user equipment (UE) operative to communicate in one or more sessions via a serving base station (BS) (e.g. eNB or gNB) of the mobile network. The UP entity may detect, in a header (e.g. SRH) of the data packet, an identifier indicating a new serving BS or session of the UE. The identifier may be UE- or BS-added data (e.g. iOAM data) that is inserted in the header by the UE or BS. In response, the UP entity may cause a message to be sent to an analytics function (e.g. a NWDAF) to perform analytics for session or flow migration for the UE.

Abstract: Systems and methods for providing access prioritization to a private Long Term Evolution (LTE) network operating in a Citizens Broadband Radio Service (CBRS) spectrum include receiving, at a network device of the private Long Term Evolution (LTE) network, a functional group associated with a user equipment (UE) and a traffic load of a cell of the private LTE network associated with the UE. An access priority associated with the functional group and the traffic load is determined and provided to a CBRS access point (AP) which controls access to the cell. The access priority indicates to the CBRS AP a priority with which the UE is allowed to access the cell and can include a high priority, a low priority, or no access indication.

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.