Abstract: A device may include a processor configured to detect that an Internet Protocol Security (IPsec) tunnel from a user equipment (UE) device connected via a WiFi connection has become idle, based on the IPsec tunnel meeting an idleness criterion, and instruct the UE device to tear down the IPsec tunnel, in response to detecting that the IPsec tunnel from the UE device connected via the WiFi connection meets the idleness criterion. The device may be further configured to receive a mobile terminating call for the UE device; establish a new IPsec tunnel to the UE device via the WiFi connection, in response to receiving the mobile terminating call for the UE device; and forward the received mobile terminating call to the UE device via the established new IPsec tunnel.

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 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 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 device may include a processor configured to register a network function, of a core network associated with a radio access network, in a network function repository for the core network. The processor may be further configured to obtain load information for the network function, wherein the load information indicates a load associated with the network function during a time period; determine that the load associated with the network function has reached a threshold based on the load information; and send an alert to an orchestration system to adjust a capacity for the network function, in response to determining that the load associated with the network function has reached the threshold.

Abstract: A system described herein may provide a technique for a selection of an Interworking Function (“IWF”) that facilitates an interworking between a licensed wireless network and another wireless network, such as an unlicensed wireless network, based on a geographical location of a User Equipment (“UE”) that is connected to the licensed wireless network and the other wireless network. The IWF may be selected from a set of candidate IWFs based on respective locations of the candidate IWFs and the UE and/or a wireless access point associated with the other wireless network. The IWF may communicate with the UE, via the other wireless network, using one or more tunnels. The IWF may identify control plane and user plane traffic received via the tunnel(s), and may forward such communications to appropriate network devices of the licensed wireless network.

Abstract: A method, a device, and a non-transitory storage medium are described in which a registration area-based application exposure and network slice selection service is provided. The service may include the generation of multiple sets of allowed network slices based on a type of end device, current tracking area, and registration area information. The service may also include selecting one of the sets of allowed network slices based on a mobility pattern of the end device. The service may also translate allowed network slices, current tracking area and registration area information, and expose the translated information to an application function.

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 may include a processor configured to detect that an Internet Protocol Security (IPsec) tunnel from a user equipment (UE) device connected via a WiFi connection has become idle, based on the IPsec tunnel meeting an idleness criterion, and instruct the UE device to tear down the IPsec tunnel, in response to detecting that the IPsec tunnel from the UE device connected via the WiFi connection meets the idleness criterion. The device may be further configured to receive a mobile terminating call for the UE device; establish a new IPsec tunnel to the UE device via the WiFi connection, in response to receiving the mobile terminating call for the UE device; and forward the received mobile terminating call to the UE device via the established new IPsec tunnel.

Abstract: A method, a device, and a non-transitory storage medium are described in which an application management service is provided. The service may provide a coordination between network or platform level application management functions and application level application management functions that enables the management of an application service. The network or platform level application management functions may include autoscaling, load balancing, and ingress resource management. The application level application management functions may include throttling and circuit breaker functions.

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: Systems and method are provided for a temporary network slice usage barring service within a core network. A network device in the core network receives a slice barring information message for an application function (AF). The slice barring information message includes a unique subscriber identifier associated with a user equipment (UE) device to be barred from a network slice and indicates a barring expiration time. The network device stores barring parameters based on the slice barring information message. The barring parameters include a slice identifier associated with the AF, the unique subscriber identifier, and the barring expiration time. The network device sends a barring instruction message to another network device associated with the network slice. The barring instruction message includes the unique subscriber identifier and the barring expiration time. The other network device enforces temporary barring of the UE device from the network slice based on the barring instruction message.

Abstract: A network device may receive historical data identifying historical error data and error data categorizations associated with a first core network and may store the historical data in a data structure. The network device may receive a request associated with a user equipment and may receive error data from the first core network based on the request. The network device may receive network health data identifying load levels and health of the first core network and a second core network. The network device may determine possible cause data identifying causes associated with the error data based on the historical data, the error data, and the network health data. The network device may generate a cause code for the user equipment based on the possible cause data and may provide the cause code to the user equipment.

Abstract: An edge network gateway, located in an edge network and connected to a core network, receives packets for a local breakout (LBO) Protocol Data Unit (PDU) session associated with a mobile subscriber. The edge network gateway sends, based on receipt of the packets for the LBO PDU session, a request for charging to a core network node, and forwards the packets for the LBO PDU session to a network or multi-access edge computing (MEC) data center connected to the edge network. The edge network gateway sends, via an online charging interface, charging data counts for the packets of the LBO PDU session to the core network node for reporting to an Online Charging System and charging to the mobile subscriber.

Abstract: A method for performing authorization for network function registration. The method includes instantiating a network function (NF) based on at least one micro-service; providing a software module with each of the at least one micro-service; sending, from each software module, an authorization code to a NF authorization platform, where the authorization code is associated with the micro-service; forwarding the at least one authorization code received at the NF authorization platform to an NF registration function (NRF); sending, from the NF, a service registration request to the NRF, where the service registration request includes each authorization code associated with the at least one micro-service; and registering the NF with the NRF, where the NRF validates each authorization code received from the NF.

Abstract: A system described herein may provide a technique for location-based handling of discovery requests in a service-based network in which different instances of network functions (“NFs”) may be deployed in geographically diverse locations. For example, a Network Repository Function (“NRF”) may maintain location information for the various NF instances and may respond to discovery requests by identifying particular NF instances based on locations associated with the discovery requests. For example, such discovery requests may include a “preferred-locality” parameter or some other indication of location associated with the discovery request, based on which the NRF may identify one or more NF instances to provide in response to the discovery request.

Abstract: Systems and method are provided for a temporary network slice usage barring service within a core network. A network device in the core network receives a slice barring information message for an application function (AF). The slice barring information message includes a unique subscriber identifier associated with a user equipment (UE) device to be barred from a network slice and indicates a barring expiration time. The network device stores barring parameters based on the slice barring information message. The barring parameters include a slice identifier associated with the AF, the unique subscriber identifier, and the barring expiration time. The network device sends a barring instruction message to another network device associated with the network slice. The barring instruction message includes the unique subscriber identifier and the barring expiration time. The other network device enforces temporary barring of the UE device from the network slice based on the barring instruction message.

Abstract: A device may include a processor configured to detect that an Internet Protocol Security (IPsec) tunnel from a user equipment (UE) device connected via a WiFi connection has become idle, based on the IPsec tunnel meeting an idleness criterion, and instruct the UE device to tear down the IPsec tunnel, in response to detecting that the IPsec tunnel from the UE device connected via the WiFi connection meets the idleness criterion. The device may be further configured to receive a mobile terminating call for the UE device; establish a new IPsec tunnel to the UE device via the WiFi connection, in response to receiving the mobile terminating call for the UE device; and forward the received mobile terminating call to the UE device via the established new IPsec tunnel.

Abstract: A system described herein may provide a technique for location-based handling of discovery requests in a service-based network in which different instances of network functions (“NFs”) may be deployed in geographically diverse locations. For example, a Network Repository Function (“NRF”) may maintain location information for the various NF instances and may respond to discovery requests by identifying particular NF instances based on locations associated with the discovery requests. For example, such discovery requests may include a “preferred-locality” parameter or some other indication of location associated with the discovery request, based on which the NRF may identify one or more NF instances to provide in response to the discovery request.

Abstract: Systems described herein provide techniques for establishing and modifying user plane communications sessions between Long-Term Evolution (“LTE”) User Equipment (“UE”) devices, connected to LTE base stations, and a Fifth Generation (“5G”) core network. An LTE-5G Interworking function (“LTE-5G IWF”) may logically generate a virtual 5G UE and/or 5G base station, map a LTE UE to the virtual 5G UE, and cause the establishment of a Protocol Data Unit (“PDU”) Session, at the 5G core network, with the virtual 5G UE. The LTE-5G IWF may provide PDU Session information to the LTE UE and base station to facilitate the establishment of user plane communications (e.g., via a tunnel) between the LTE UE and the 5G core network. The LTE-5G IWF may also receive modification parameters, such as Quality of Service (“QoS”) parameters, and provide instructions to the 5G core and/or to the LTE UE to handle traffic according to such parameters.