Abstract: A device may include a processor configured to establish a data traffic flow for a user equipment (UE) device and determine per flow descriptor attributes associated with the data traffic flow, wherein the per flow descriptor attributes identify at least a source, a destination, and a protocol associated with the data traffic flow. The processor may be further configured to determine at least one additional per flow descriptor attribute for the data traffic flow and send the per flow descriptor attributes and the at least one additional per flow descriptor attribute to a network exposure device of a core network, wherein the network exposure device is configured to communicate with servers outside the core network.

Abstract: A method, a network device, and a non-transitory computer-readable storage medium are described in relation to an integrated network slice encryption service. The integrated network slice encryption service may manage and provision encryption and/or decryption services associated with a third party and relative to a network slice and end device application associated with a service provider and application provider. The integrated network slice encryption service may provision end devices, core network devices, and application layer devices of an external network.

Abstract: A method, a device, and a non-transitory storage medium are described in which an uplink classifier and branching point service is provided. The service may include the management of user plane function devices or uplink classifier devices according to various architectures and connectivity among the user plane function devices or uplink classifier devices. The service may allow end devices situated in different locations to connect to different application service host devices and application service layer networks based on such management.

Abstract: A network device may select a first user plane function for establishing, with a user equipment, a protocol data unit session with a single flow and may receive an application function trigger associated with a first new flow for a first application of the user equipment. The network device may select a second user plane function for the first new flow and may create a first traffic filter for the first new flow. The network device may cause the first traffic filter to be provided to the user equipment so that first application traffic is routed, based on the first traffic filter, to the second user plane function and a first multi-access edge computing device associated with the second user plane function.

Abstract: A network device may receive Network Slice Selection Assistance Information (NSSAI) and network information from network components and from a set of Integrated Access and Backhaul (IAB) nodes; generate descriptions of, or updates to the descriptions of, routing paths based on the NSSAI and the network information; and send the descriptions or the updates to the IAB nodes. The routing paths may include one or more backhaul links between the IAB nodes, and the descriptions and the updates associate each of the routing paths with one or more Single-NSSAIs (S-NSSAIs).

Abstract: Embodiments described herein may provide for the return (e.g., reconnection) of a User Equipment (“UE”) to a first radio access network (“RAN”) to which the UE was connected, after the UE has been redirected to a second RAN based on the occurrence of an event. The event may include a voice call placed by or to the UE. The return of the UE to the first RAN may occur based on the occurrence of another event, such as the voice call being terminated.

Abstract: Disclosure are techniques for allocating aggregation devices in a lawful intercept system. In an embodiment, a method includes maintaining a list of point of interception aggregation (PAG) functions in a network function repository function (NRF) of a cellular network upon instantiation of the PAG functions; receiving a lawful intercept (LI) request; querying the NRF to determine a respective PAG function; and associating a point of interception (POI) function with the respective PAG function.

Abstract: A method, a device, and a non-transitory storage medium are described in which a dual connectivity path selection service is provided. The service may select a network path for dual connectivity. The service may use mapping information that may correlate network parameters and values to dual connectivity configurations. The service may compare parameters included in a configuration request pertaining to end devices with the mapping information for selection of a dual connectivity configuration.

Abstract: In some implementations, a first network device may be associated with a serving gateway control plane function of a core network. The first network device may send, via a first interface, an association message to a second network device that is associated with a session management function and a packet data gateway control plane function of the core network. The first network device may receive selection information from the second network device via the first interface. The first network device may select, based on the selection information, a third network device that is associated with a serving gateway user plane function of the core network. The first network device may cause the third network device to route traffic for a packet data network session associated with a user device.

Abstract: A network device receives location information for a user equipment device (UE), an application identifier (ID), and a latency requirement associated with a data session involving the UE. The network device retrieves from a database, based on the UE's location information, the application ID, and the latency requirement, Multi-Access Edge Computing (MEC) selection weight values associated with multiple MEC platforms. The network device selects a MEC platform, from among the multiple MEC platforms, based on the retrieved MEC selection weight values, and causes the data session to be established between the selected MEC platform and the UE.

Abstract: A computer device may include a memory storing instructions and processor configured to execute the instructions to host a network function container that implements a microservice for a network function in a wireless communications network, wherein the network function container is deployed by a container orchestration platform; host a service proxy container associated with the network function container, wherein the service proxy container is deployed by the container orchestration platform; and configure the hosted service proxy container to apply a wireless network policy to the microservice for the network function. The processor may be further configured to intercept messages associated with the microservice for the network function using the configured service proxy container; and apply the wireless network policy to the intercepted messages using the configured service proxy container.

Abstract: Systems and methods described include receiving traffic associated with a multi-access edge computing (MEC) application hosted at a MEC network; determining an Internet Protocol (IP) address associated with the MEC application, wherein the IP address indicates a priority of the traffic associated with the MEC application; modifying a header of the traffic to include the IP address associated with the MEC application; transmitting the traffic to a wireless station; and routing the traffic based on the priority associated with the MEC application.

Abstract: A device, method, and system for forwarding, to a pod, a utility container associated with each of at least one network service for enabling a pre-registration of a network function (NF) with an NF registration function (NRF); sending, from the utility container, an authorization code to an NF authorization platform, wherein the authorization code is associated with the at least one network service; suspending a registration procedure for the NF with the NRF until the authorization code is forwarded from the NF authorization platform to the NRF; and resuming, responsive to a service registration request, the registration procedure based on a validation of the authorization code identified in the service registration request.

Abstract: A first component may receive a message from a anchor selection component in a network. The message may include information that identifies a session anchor in the network and indicates a location of the session anchor. The first component may identify a managing component in the network based on the information and signal the managing component. The signaling may cause the managing component to be configured to forward data, from a mobile terminal attached to the network over a wireless link, to the session anchor.

Abstract: A system described herein may provide a technique for maintaining and transferring context information for a Dual Connectivity (“DC”)-capable User Equipment (“UE”) and a secondary Next Generation Node B (“gNB”) in situations where the UE is connected to a primary gNB and the secondary gNB and is handed over to an evolved Node B (“eNB”). The context information may be provided to the eNB without releasing resources or tearing down bearers at the secondary gNB, such that the UE may seamlessly continue communicating with the secondary gNB while a primary connection associated with the UE is handed over from the primary gNB to the eNB.

Abstract: Systems and methods described herein provide for User Equipment (UE)-initiated authentication and authorization updates to Network Slice-Specific Authentication and Authorization (NSSAA). A network device in a core network receives a message from a user device outside of the core network, wherein the message includes a request to initiate a NSSAA procedure. The network device initiates the NSSAA procedure in response to the request. The systems and methods also provide for UE-initiated authorization revocation of NSSAA.

Abstract: A system described herein may provide a technique for providing updated address mapping information associated with a service mesh via which one or more containerized instances communicate. The system may include and/or implement an application programming interface (“API”) via which the service mesh may provide address mapping information, that includes public and private addresses associated with containerized instances that communicate via the service mesh. The updated information may be received on an ongoing basis, and may be provided to another system that has subscribed to receiving updated mapping information associated with one or more containerized instances.

Abstract: A network device receives location information for a user equipment device (UE), an application identifier (ID), and a latency requirement associated with a data session involving the UE. The network device retrieves from a database, based on the UE's location information, the application ID, and the latency requirement, Multi-Access Edge Computing (MEC) selection weight values associated with multiple MEC platforms. The network device selects a MEC platform, from among the multiple MEC platforms, based on the retrieved MEC selection weight values, and causes the data session to be established between the selected MEC platform and the UE.

Abstract: A computer device may include a memory storing instructions and processor configured to execute the instructions to host a network function container that implements a microservice for a network function in a wireless communications network, wherein the network function container is deployed by a container orchestration platform; host a service proxy container associated with the network function container, wherein the service proxy container is deployed by the container orchestration platform; and configure the hosted service proxy container to apply a wireless network policy to the microservice for the network function. The processor may be further configured to intercept messages associated with the microservice for the network function using the configured service proxy container; and apply the wireless network policy to the intercepted messages using the configured service proxy container.

Abstract: A packet destined for a Multi-access Edge Computing (MEC) network is received at a wireless station from a user device. A serving gateway (SGW) receives the packet from the wireless station via an S1U GTP tunnel and assigns an uplink S1U General Packet Radio Service (GPRS) Tunneling Protocol (GTP) tunnel endpoint identifier (TEID) to the packet. The SGW performs a network address translation (NAT) function on the packet based on the uplink S1U GTP TEID assigned to the packet to form a translated packet. The SGW transmits the translated packet to the MEC network.