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 an entity to support a network slice and/or access to an application service for end devices. 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.

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 method, a network device, and a non-transitory computer-readable storage medium are described in relation to a hybrid network slicing service. The hybrid network slicing service may enable the initial configuration of a network slice according to network slice requests that may include customized and user-specified network performance criteria. The hybrid network slicing service may enable network slice requests to specify selection of network resources and use/availability based on entity-based criteria including end device and/or application specific associations. The hybrid network slicing service may optimize network slice configurations and generate network slice templates.

Abstract: A method, a network device, and a non-transitory computer-readable storage medium are described in relation to a hybrid network slicing service. The hybrid network slicing service may enable the initial configuration of a network slice according to network slice requests that may include customized and user-specified network performance criteria. The hybrid network slicing service may enable network slice requests to specify selection of network resources and use/availability based on entity-based criteria including end device and/or application specific associations. The hybrid network slicing service may optimize network slice configurations and generate network slice templates.

Abstract: A method, a network device, and a non-transitory computer-readable storage medium are described in relation to a hybrid network slicing service. The hybrid network slicing service may enable the initial configuration of a network slice according to network slice requests that may include customized and user-specified network performance criteria. The hybrid network slicing service may enable network slice requests to specify selection of network resources and use/availability based on entity-based criteria including end device and/or application specific associations. The hybrid network slicing service may optimize network slice configurations and generate network slice templates.

Abstract: Systems and methods described herein enable premium session retainability for differentiation of services with respect to network function failures. A first network function of a core network obtains a session retention indicator during establishment of a protocol data unit (PDU) session. The first network function calculates a compute footprint for the first network function to support the PDU session and any other premium sessions currently serviced by the first network function. An orchestration device receives the compute footprint and provisions a second network function based on the compute footprint. The first network function and the second network function perform data replication of state information for the PDU session to allow premium sessions to continue with no or minimal interruption in the event of a failover scenario.

Abstract: Systems and methods provide a short data, low latency service using a Multi-access Edge Computing (MEC) network. A network device receives, in a core network, an attach request from an end device and detect whether a packet size range for data transmissions from the end device is within a configured size threshold. The network device directs, when the packet size is within the configured size threshold, routing of the data transmissions via a control plane function of an edge network to a local instance of an application server in the edge network. The network device directs, when the packet size is over the configured size threshold, routing of the data transmissions via a user plane function of the edge network to a local instance of an application server in the edge network.

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 method, a device, and a non-transitory storage medium are described in which multi-tiered networks and resource utilization-based provisioning service is provided. A multi-tiered mobile edge computing network that includes multiple mobile edge computing networks that are multi-tiered based on distance from a network edge includes a network device that selects a location to provision an application service for an end device based on a total resource utilization value and a performance metric associated with one or multiple candidate mobile edge computing networks.

Abstract: An edge device may obtain, via a base station, one or more respective requests from one or more user devices to access content. The edge device may determine a total number of the one or more user devices and may determine that the total number of the one or more user devices satisfies a threshold. The edge device may determine, based on the total number of the one or more user devices satisfying the threshold, a latency requirement associated with the content and may determine whether the edge device can satisfy the latency requirement. The edge device may selectively cause, based on determining whether the edge device can satisfy the latency requirement, the edge device or a different edge device to send the content to the one or more user devices via the base station.

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: Systems and methods provide a short data, low latency service using a Multi-access Edge Computing (MEC) network. A network device receives, in a core network, an attach request from an end device and detect whether a packet size range for data transmissions from the end device is within a configured size threshold. The network device directs, when the packet size is within the configured size threshold, routing of the data transmissions via a control plane function of an edge network to a local instance of an application server in the edge network. The network device directs, when the packet size is over the configured size threshold, routing of the data transmissions via a user plane function of the edge network to a local instance of an application server in the edge network.

Abstract: Systems and methods provide a short data, low latency service using a Multi-access Edge Computing (MEC) network. A network device receives, in a core network, an attach request from an end device and detect whether a packet size range for data transmissions from the end device is within a configured size threshold. The network device directs, when the packet size is within the configured size threshold, routing of the data transmissions via a control plane function of an edge network to a local instance of an application server in the edge network. The network device directs, when the packet size is over the configured size threshold, routing of the data transmissions via a user plane function of the edge network to a local instance of an application server in the edge network.

Abstract: A method, a device, and a non-transitory storage medium are described in which a mobile edge network-based intelligent routing service is provided. The intelligent routing service includes using default network devices to initially provide application services to end devices. The intelligent routing service further includes selecting and migrating the application services to a multi-layered mobile edge computing network when performance metrics associated with the application services are not satisfied. The intelligent routing service may determine whether performance metrics are satisfied based on performance metric information obtained from the serving nodes and the end devices.

Abstract: A computer device receives user parameters for an Over-The-Air (OTA) update campaign. The parameters include a number of user equipment (UE) devices to receive an OTA update, a device type to receive the OTA update, a file size of an OTA update file, and a service level agreement parameter for the OTA update campaign. The computer device generates an estimate for conducting the OTA update campaign based on the user parameters and predicted network conditions, provides the estimate to a user, and receives a request for conducting the OTA update campaign using the user parameters. The request includes identifiers for the UE devices and the OTA update file. The computer device generates, based on the request, a schedule to perform the OTA update on the UE devices in accordance with the service level agreement parameter, and instructs the UE devices to perform the OTA update based on the schedule.

Abstract: A computer device receives user parameters for an Over-The-Air (OTA) update campaign. The parameters include a number of user equipment (UE) devices to receive an OTA update, a device type to receive the OTA update, a file size of an OTA update file, and a service level agreement parameter for the OTA update campaign. The computer device generates an estimate for conducting the OTA update campaign based on the user parameters and predicted network conditions, provides the estimate to a user, and receives a request for conducting the OTA update campaign using the user parameters. The request includes identifiers for the UE devices and the OTA update file. The computer device generates, based on the request, a schedule to perform the OTA update on the UE devices in accordance with the service level agreement parameter, and instructs the UE devices to perform the OTA update based on the schedule.

Abstract: A system may receive user device information that includes a location associated with the user device and an identifier of a base station associated with the location and receives load information associated with the base station. The system may determine, based on the user device information and the load information, whether congestion is predicted and perform traffic throttling in response to determining the congestion is predicted. A schedule for adjusting the traffic throttling is determined and the traffic throttling is adjusted based on the schedule.

Abstract: Systems and methods provide a short data, low latency service using a Multi-access Edge Computing (MEC) network. A network device receives, in a core network, an attach request from an end device and detect whether a packet size range for data transmissions from the end device is within a configured size threshold. The network device directs, when the packet size is within the configured size threshold, routing of the data transmissions via a control plane function of an edge network to a local instance of an application server in the edge network. The network device directs, when the packet size is over the configured size threshold, routing of the data transmissions via a user plane function of the edge network to a local instance of an application server in the edge network.

Abstract: A Multi-access Edge Computing (“MEC”) controller may predict locations for a tracked UE at different future times, and may also predict content that the tracked UE may request at the different future times. The predictions may be based on MEC controller computing probabilities for the tracked UE being at the different locations at the different future times, and/or probabilities for the content that the tracked UE is likely to request at the different locations and/or future times. The MEC controller may identify a MEC device that provides extremely low latency service and/or optimally serves a network area that includes a predicted location. The MEC controller may issue a prefetch message to the MEC device that causes the MEC device to prefetch predicted content that the tracked UE is likely to request at the future time the tracked UE is likely to reach the predicted location.

Abstract: An edge device may obtain, via a base station, one or more respective requests from one or more user devices to access content. The edge device may determine a total number of the one or more user devices and may determine that the total number of the one or more user devices satisfies a threshold. The edge device may determine, based on the total number of the one or more user devices satisfying the threshold, a latency requirement associated with the content and may determine whether the edge device can satisfy the latency requirement. The edge device may selectively cause, based on determining whether the edge device can satisfy the latency requirement, the edge device or a different edge device to send the content to the one or more user devices via the base station.