Abstract: A system described herein may maintain information associating one or more tokens to one or more network slices associated with a network. The system may receive a request, from an application executing at a User Equipment (“UE”), for communication session information, where the request includes a particular token. The system may identify a particular network slice associated with the particular token based on the information associating the one or more tokens to the one or more network slices. The system may receive communication session information, associated with the particular network slice, from the network, and may provide the communication session information to the application. The application may use the communication session information to communicate with the network via the particular network slice. The application may use such communication session information without providing an application identifier to the network.

Abstract: A system described herein may receive monitoring information associated with a plurality of User Equipment (“UEs”) that receive service via a wireless network. The system may identify, based on the received monitoring information, a particular set of network configuration parameters to implement with respect to service provided to a particular UE, of the plurality of UEs, via the wireless network. The system may provide, to the wireless network, the identified set of network configuration parameters. Providing the identified set of network configuration parameters may include providing an identifier of the particular UE. One or more elements of the wireless network may implement the provided set of network configuration parameters, which may include modifying parameters of the service provided to the particular UE.

Abstract: A method, a device, and a non-transitory storage medium are described in which a network slice usage service is provided. The network slice usage service may allow a network device to obtain a network slice usage value of a network slice. The network device may calculate a network slice load value based on the network slice usage value. The network device may also provide the network slice load value to other network devices of a core network.

Abstract: A device, located in a core network associated with a radio access network (RAN), may include a processor configured to expose services or capabilities to application servers outside the core network, wherein the device is located in a core network associated with a radio access network (RAN). The processor may be further configured to receive a subscriber identifier message from a gateway device that established a connection to a user equipment (UE) device via the RAN, wherein the subscriber identifier message includes information identifying the UE device; receive a request from an application server associated with the connection for the information identifying the UE device; and provide the requested information identifying the UE device to the application server, in response to receiving the request from the application server.

Abstract: A device may receive user device application performance logs, radio access network (RAN) performance logs, and multi-access edge computing (MEC) compute logs, and may train a machine learning model with the user device application performance logs, the RAN performance logs, and the MEC compute logs. The device may identify application capacity requirements and MEC compute requirements associated with images of RAN coverage areas of RANs, and may generate labeled and normalized images of RAN coverage areas. The device may receive real time MEC compute data, RAN performance data, and user device application data, and may identify one of the labeled and normalized images of the RAN coverage areas that matches a RAN coverage area of a particular RAN. The device may predict an application capacity and MEC compute requirements for the particular RAN, and may perform one or more actions based on the application capacity and the MEC compute requirements.

Abstract: A User Equipment (“UE”) described herein may connect or request connection to a base station of a wireless network. The base station may implement multiple frequency bands, and connecting or requesting connection to the base station may include connecting or requesting connection via a particular frequency band of the multiple frequency bands. The UE may provide an indication of the particular frequency band to a core of the wireless network. The core may select a set of parameters for communications between the UE and the wireless network based on the indication of the particular frequency band. Additionally, or alternatively, the core may provide an indication of the particular frequency band to a device that provides a service to the UE via the wireless network, and the device may select parameters for the service based on the indication of the particular frequency band.

Abstract: A method may include receiving, by at least one network device and from a user device, a registration message including a service identifier and at least one of a network slice identifier or a network slice token. The method may also include determining, based on information included in the registration message, whether the user device is authorized to use a network slice associated with the service identifier. The method may further include setting up a data session to be serviced by the network slice, in response to determining that the user device is authorized to use the network slice.

Abstract: A method, a device, and a non-transitory storage medium are described in which a network slice usage subscription service is provided. The network slice usage subscription service may allow a network device to obtain network slice usage information and event notifications. The event notification may indicate when an end device is using a network slice and when the end device is no longer the network slice. The network device may include an application function (AF) device. The network device may use the event notification to perform an operation relating to the network slice and/or the end device.

Abstract: A device may receive data indicating a required quality of service (QoS), and may receive radio access network (RAN) information associated with a RAN, wherein the RAN information is provided by a centralized unit (CU) of the RAN. The device may provide the RAN information to a multi-access edge computing (MEC) platform, and may receive, from the MEC platform, a QoS request that requests the required QoS. The device may provide the QoS request to the CU, and may receive a QoS response to the QoS request. The device may provide the QoS response to a policy control function (PCF) of a core network, and may receive an indication of approval of the QoS response from the PCF. The device may cause, based on receiving the indication of approval, the required QoS to be implemented by the MEC platform and network devices associated with the core network.

Abstract: A network device receives a network service request, for network service in a mobile network, from a user equipment device (UE), where the network service request includes a first service identifier (ID) and a subscription concealed ID (SUCI). The network device sends, to a Network Function (NF) in the mobile network, a SUCI deconcealment request that includes the SUCI. The network device receives, from the NF, a deconcealed Subscription Permanent Identifier (SUPI) decrypted from the SUCI. The network device verifies a validity of the first service ID for the deconcealed SUPI, and sends a service authorization response to the UE based on verification of the validity of the service ID from the UE.

Abstract: In some implementations, a network device may receive an identifier associated with an application server. The network device may associate the identifier with a service profile associated with a network slice based on a quality of service associated with the network slice. The network device may provide, to a device associated with the application server, information indicating that the identifier is associated with the service profile. The network device may receive address information associated with the application server. The network device may associate the address information with the service profile. The network device may provide service profile information to a security device included in a core network to cause the security device to forward traffic transmitted by the application server toward a destination via the network slice. The service profile information may include an identifier associated with the service profile, the identifier, and the address information.

Abstract: A system described herein may receive a request to establish a communication session between a core network and a User Equipment (“UE”), determine that the requested communication session is associated with one or more admission control options and receive, from the UE, a selection of a particular admission control option of the one or more admission control options. The system may identify one or more actions associated with the particular admission control option. The one or more actions include rejecting the request to establish the communication session, or accepting the request to establish the communication session. The system may perform the one or more identified actions associated with the particular admission control option. The system may include an interface between an Access and Mobility Management Function (“AMF”) of the core network and a Network Slice Access Control Function (“NSACF”) of the core network.

Abstract: A method, a device, and a non-transitory storage medium are described in which a edge network exposure function service is provided. An edge network exposure function device may provide the edge network exposure function service. The edge network exposure function service may communicate with a radio access network, a mobile edge computing network, and a main edge network exposure function device to provide radio access network, end device, and control information. The edge network exposure function device may also facilitate handovers of an end device between mobile edge computing networks. The edge network exposure function device may be situated at the network edge and the main network exposure function device may be situated in a core network.

Abstract: A network device may provide, to a content server device, an upload policy for uploading data, and may receive a notification indicating that the user device is attached to a network associated with a network identifier. The network device may receive a request identifying data to be uploaded by a user device to the content server device, and may determine a time window, a data size, and the network identifier associated with the upload policy and the network. The network device may determine whether the request complies with the time window, the data size, and the network identifier, and may determine whether a quantity of tokens associated with the network identifier is zero. The network device may provide, to the user device, a response indicating approval of the data to be uploaded, and may receive an indication that uploading the data is complete.

Abstract: A method, a device, and a non-transitory storage medium are described in which a monitoring event handling service is provided. The service may include a non-stand-alone core device subscribing to a registration status for an end device with a stand-alone core device. The service may also include the non-stand-alone core device subscribing to a monitoring event service with the stand-alone core device on behalf of another non-stand-alone core network device. The stand-alone core device may monitor an event when the end device is stand-alone registered and may notify the non-stand-alone core device when the event occurs. The service may include the non-stand-alone core device notifying the other non-stand-alone core device when the event occurs.

Abstract: A system described herein may maintain information associating one or more tokens to one or more network slices associated with a network. The system may receive a request, from an application executing at a User Equipment (“UE”), for communication session information, where the request includes a particular token. The system may identify a particular network slice associated with the particular token based on the information associating the one or more tokens to the one or more network slices. The system may receive communication session information, associated with the particular network slice, from the network, and may provide the communication session information to the application. The application may use the communication session information to communicate with the network via the particular network slice. The application may use such communication session information without providing an application identifier to the network.

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 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 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: 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.