Abstract: A method, a device, and a non-transitory storage medium are described in which an inter-operator mobility service is provided. The service may provide provisioning decisions and configurations that may include core devices that are shared between users of a first entity and users of a second entity, or are dedicated to the users of the second entity to support a network slice and/or access to an application service for end devices associated with the second entity. The service may manage access and use of radio frequencies associated with the first and second entities based on subscription information and location of the end devices associated with first and second entities. The service may further include enabling inter-network handovers associated with end devices associated with end devices associated with the second entity.

Abstract: A system includes one or more devices. The devices are configured to: receive a message indicating that a network slice has been deployed in a network, wherein the message includes information related to the network slice; send the information to an application that provides services to User Equipment (UE) devices subscribed to the network; and initiate updates to UE route selection policies (URSPs) in the network based on the information, allowing communications from UE devices to reach the network slice.

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 provisioning data identifying an application server and a user equipment. The device may provide a request for reachability data associated with the user equipment and may receive the reachability data. The device may cause a trigger for a packet and data identifying the application server to be provided to the user equipment. The device may receive, from the user equipment, the packet that includes a network address and a port identifier of a port of the user equipment. The device may provide, to a firewall associated with the application server, an identifier, the network address, and the port identifier. The device may cause, via the firewall, the reachability data, the network address, and the port identifier to be provided to the application server to enable the application server to provide data to the user equipment.

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.

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: 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: 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 user device may be provisioned with a list of paths for connecting to a network. A method may include determining that the user device has attached to a visited network and sending the visited network an indication of connectivity capabilities associated with the network. The method may include receiving an indication of one or more paths established from the visited network to the network based on capabilities of the visited network. The one or more paths may be included in the list of paths. The method may include transmitting data to or from the user device via a first path of the one or more paths.

Abstract: A system comprises a Network Exposure Function (NEF) and a Session Management Function (SMF). The MF may be configured to: receive, from the NEF, a first request to subscribe to a notification service offered by the SMF; send a create session request to a User Plane Function (UPF); receive a first response from the UPF to the create session request, wherein the first response includes binding information that pertains to an association between a User Equipment device (UE) identifier (ID) and Internet Protocol (IP) addresses; and send, as part of the notification service, a message that includes the binding information to the NEF.

Abstract: A system includes one or more devices. The devices are configured to: receive a message indicating that a network slice has been deployed in a network, wherein the message includes information related to the network slice; send the information to an application that provides services to User Equipment (UE) devices subscribed to the network; and initiate updates to UE route selection policies (URSPs) in the network based on the information, allowing communications from UE devices to reach the network slice.

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.

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 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 device obtains a list of a plurality of user devices from a first network device and receives a message intended for a destination user device from a second network device. The device obtains information indicating that the destination user device can receive messages that conform to a particular format from a third network device and converts the message to the particular format. The device determines a reachability of the destination user device based on the list of the plurality of user devices, after converting the message, and sends the message to the destination user device via the first network device based on the reachability. The device receives a delivery message from the destination user device and sends a notification message indicating successful delivery of the message to the second network device based on the delivery message.

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 receive property data associated with a coverage area of a mobile network, wherein the property data includes identification information and location information associated with the coverage area; receive load data associated with the coverage area; determine a load threshold associated with the coverage area; determine whether the load data satisfies the load threshold; identify, based on determining that the load data satisfies the load threshold, impacted user equipment associated with the coverage area, wherein the impacted user equipment is further identified based on the property data; identify an application network device associated with the coverage area and the impacted user equipment, wherein the application network device is further identified based on the property data; determine a corrective action based on the load data, the load threshold, and the application network device; and perform the corrective action in connection with the application network device.

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