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: Systems and methods implement closed loop analytics feedback for a transport network. A network device, such as a Network Data Analytics Function (NWDAF), receives, from a commissioning network function, an analytic information request for analytic event information and sends, to the commissioning network function, an analytic report that is responsive to the analytic information request wherein the analytic report includes a unique analytic report identifier. The network device receives, from the commissioning network function, a feedback event message that includes the analytic report identifier and a change description for a network parameter change influenced by the analytic report.

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: A network device may receive an indication of movement of a user device, associated with multiple packet data unit (PDU) sessions, from a first radio access network (RAN) to a second RAN, and may maintain, based on the indication, a particular PDU session, of the multiple PDU sessions, associated with a default flow. The network device may release, based on the indication, the multiple PDU sessions other than the particular PDU session, and may handle the multiple PDU sessions, other than the particular PDU session, in accordance with a handling option.

Abstract: Systems and methods provide for network-based selection of a UE device's 5G operation mode. A network device in a wireless core network receives a policy query for a user equipment (UE) device. The UE device is capable of 5G non-standalone (NSA) and 5G standalone (SA) operation modes. The network device identifies one or more of subscription data for the UE device, stored network data associated with the UE device, or dynamic network data relevant to the UE device. The network device assigns, based on the identifying, a radio access technology/frequency selection and prioritization (RFSP) value for the UE device. The network device sends the RFSP value to an access management function in the wireless core network for controlling selection of the 5G NSA operation mode or 5G SA operation mode.

Abstract: A method may include receiving, from a user device, a registration request that includes a subscription concealed identifier (SUCI), identifying a network element to decode the SUCI and forwarding the SUCI to the identified network element. The method may also include decoding the SUCI to identify a subscription permanent identifier (SUPI), identifying a unified data management (UDM) device associated with the SUPI and transmitting an authentication request to the identified UDM device to obtain authentication information associated with the user device. The method may further include receiving the authentication information and authenticating the user device based on the received authentication information.

Abstract: A first network function (NF) instance sends a request for a session to a second NF instance. The first NF instance receives a response, from the second NF instance, that includes a binding header that includes a failover mode identifier, a designated number of retry attempts, and a retry mode. The first NF instance sends a second request for the session to the second NF instance. The first NF instance determines if an error or a timed out response has occurred subsequent to sending the second request to the second NF instance, and re-sends, in response to the error or timed out response, the second request based on the failover mode identifier, the designated number of retry attempts and the retry mode from the binding header.

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 first network device may receive, from a second network device, a first policy control create request and may provide, to the second network device, a common policy control request trigger. The first network device may receive a second policy control create request associated with a user equipment (UE) and may cause a UE policy to be provided to the UE. The first network device may receive, from a third network device, a third policy control create request and may provide a network device policy to the third network device. The first network device may receive, from the second network device, a policy control update request based on the common policy control request trigger and may generate an updated UE policy or an updated network device policy based on the policy control update request.

Abstract: A network device of a core network may maintain a mapping table that maps core network slices with quality of service (QoS) class identifiers (QCIs) based on service profile identifiers (SPIDs), and may receive, from a user device, a request for service with a particular QCI included in the QCIs of the mapping table. The network device may identify a particular SPID of the SPIDs in the mapping table based on the particular QCI of the service, and may generate a flow request based on the particular SPID. The network device may cause the flow request to be provided to a radio access network (RAN) associated with the user device, to cause the RAN to select a RAN slice for provision of the service to the user device.

Abstract: A device may receive, from a network device, a user equipment (UE) parameter update request notification indicating an update to a UE parameter of a universal subscriber identity module (USIM), and may generate an encrypted UE parameter update request. The device may cause the encrypted UE parameter update request to be provided to the USIM to cause the USIM to update the UE parameter and to generate an encrypted UE parameter update response. The device may receive, from the network device, the encrypted UE parameter update response, and may verify an authenticity of content of the encrypted UE parameter update response based on whether the encrypted UE parameter update response is signed by the USIM. The device may provide, to the network device, a result indicating whether the UE parameter is updated and whether the authenticity of the content of the encrypted UE parameter update response is verified.

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 method, a device, and a non-transitory storage medium are described in which a network slice selection service is provided. The service may include using route selection policies that includes radio frequency criteria for selection of a network slice. The service may include establishing an application session based on the route selection policies. The service may further include determining that a radio frequency of the network slice cannot be sustained. The service may include executing an application session release procedure and an application session establishment procedure. The procedures may include using cause data and context data pertaining to the initial application session to re-establish the application session via a different network slice and a different radio frequency based on the route selection policies.

Abstract: A device may receive, from an application function device (AF), a message intended for a destination user device, wherein the message conforms to a first format. The device may obtain, from a unified data management device (UDM), information indicating that the destination user device is capable of receiving messages that conform to a second format. The device may convert, based on the information indicating that the destination user device is capable of receiving messages that conform to the second format, the message from the first format to the second format. The device may send, after converting the message from the first format to the second format, the message to a short message service function device (SMSF) via a direct connection between the device and the SMSF, wherein the SMSF sends the message to the destination user device.

Abstract: A method, a device, and a non-transitory storage medium are described in which an inter-RAT PDN connection management service is provided. The service may include provisioning a packet data network (PDN) session based on network slice (NS) and access point name (APN) information received from an end device via a non-slice radio access device. The service may further include provisioning, during the PDU session, a network slice based on the NS and APN information in which core devices of the network slice are selected and the same as the core devices that supported the PSN session.

Abstract: A device receives a call invitation message with a Session Description Protocol (SDP) offer for establishing a call between a calling party and a called party and obtains a set of network fallback rules associated with the called party. The device determines, based on the set of network fallback rules, whether to reject the call and avoid network fallback from a first wireless network to a second wireless network. The device sends, based on the determination, a call denial message without an SDP answer, to reject the call and avoid the network fallback.

Abstract: A quality of service traffic steering approach for multi-access edge computing (MEC) environments is disclosed. In an embodiment, a network exposure function (NEF) or similar device (e.g., MEC controller or orchestrator) monitors a quality of service (QoS) of a data session between a user equipment (UE) and an application. The NEF then can determine when the QoS of the data session does not meet a requested service level agreement (SLA). When the SLA is not met, the NEF identifies a MEC host that meets the SLA using a database of MEC applications. Based on the identified MEC host, the NEF re-routes the data session to the MEC host.

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 method, a device, and a non-transitory storage medium are described in which policy delivery is provided. A network device of a core network may receive a registration request message that includes a request for an end device policy. The network device may perform a registration procedure and a policy procedure pertaining to an end device. The network device determines when the registration and the policy procedures are completed. The network device transmits a registration response that includes an end device policy to an end device.

Abstract: A method, a device, and a non-transitory storage medium are described in which an blockchain-based network information management service is provided. The service provides blockchain mechanisms that allows for the management and disbursement of network information among network devices of a RAN, a core network, and an application layer network. The service may define a structure for the network information that may be used by RAN devices, core devices, and application layer devices of different vendors and third parties.