Abstract: A method, a device, and a non-transitory storage medium are described in which a mobile edge computing handover service is provided. The mobile edge computing handover service provides for the prospective provisioning of a target mobile edge computing network based on mobility information pertaining to an end device. The mobile edge computing handover service includes managing the provisioning of the application or service, content, and context information in relation to a source mobile edge computing network and the target mobile edge computing network.

Abstract: Systems and methods are provided for network slice selection during an initial connection. A wireless station receives, from a core network device, network slice data for each network slice available via the wireless station, wherein the network slice data includes a slice identifier and corresponding slice characteristics for each network slice. The wireless station receives, from a user equipment (UE) device, a registration request message that indicates a network slice characteristic required by an application being executed on UE device. The wireless station selects, based on the network slice data from the core network device and the network slice characteristic from the UE device, one of the slice identifiers for servicing the UE device.

Abstract: A method for authorizing a non-IP data delivery service may include receiving a request from a user equipment device (UE) to attach to an access network based on a generic non-internet protocol (IP) access point name (APN), and performing an initial service authorization of the UE for a non-IP data delivery (NIDD) service with the generic non-IP APN. The method may further include generating a specific non-IP APN by combining the generic non-IP APN with an APN originating identifying anchor (OIA), where the APN OIA identifies an organization associated with the NIDD service. The method may include performing a secondary service authorization of the UE within the access network using the APN OIA, and notifying an application server (AS) of the UE availability for the NIDD service using the generic non-IP APN.

Abstract: Systems and methods are provided for network slice selection during an initial connection. A wireless station receives, from a core network device, network slice data for each network slice available via the wireless station, wherein the network slice data includes a slice identifier and corresponding slice characteristics for each network slice. The wireless station receives, from a user equipment (UE) device, a registration request message that indicates a network slice characteristic required by an application being executed on UE device. The wireless station selects, based on the network slice data from the core network device and the network slice characteristic from the UE device, one of the slice identifiers for servicing the UE device.

Abstract: A method, a device, and a non-transitory storage medium are described in which a mobile edge computing handover service is provided. The mobile edge computing handover service provides for the prospective provisioning of a target mobile edge computing network based on mobility information pertaining to an end device. The mobile edge computing handover service includes managing the provisioning of the application or service, content, and context information in relation to a source mobile edge computing network and the target mobile edge computing network.

Abstract: Systems provide for provisioning, in a wireless network, in a network-service profile associated with a network-service subscriber, at least one of a power saving mode (PSM) parameter or an extended discontinuous reception (eDRX) parameter for use by a first user device; receiving a network service-related request from the first user device via an administrative non-IP packet data network (PDN) bearer established using a statically-allocated non-IP administrative access point name (APN); sending, via the PDN bearer, a first mobile terminated trigger delivery request (MT-TDR) including a bootstrap request trigger, generated by the network device, to the first user device; receiving, via the PDN bearer in response to the bootstrap request trigger, a first mobile originated originating delivery request (MO-ODR) bootstrap request; and sending, in response to the bootstrap request, a second MT-TDR including the at least one of the PSM parameter or the eDRX parameter.

Abstract: Systems and methods are provided for network slice selection during an initial connection. A wireless station receives, from a core network device, network slice data for each network slice available via the wireless station, wherein the network slice data includes a slice identifier and corresponding slice characteristics for each network slice. The wireless station receives, from a user equipment (UE) device, a registration request message that indicates a network slice characteristic required by an application being executed on UE device. The wireless station selects, based on the network slice data from the core network device and the network slice characteristic from the UE device, one of the slice identifiers for servicing the UE device.

Abstract: A method for authorizing a non-IP data delivery service may include receiving a request from a user equipment device (UE) to attach to an access network based on a generic non-internet protocol (IP) access point name (APN), and performing an initial service authorization of the UE for a non-IP data delivery (NIDD) service with the generic non-IP APN. The method may further include generating a specific non-IP APN by combining the generic non-IP APN with an APN originating identifying anchor (OIA), where the APN OIA identifies an organization associated with the NIDD service. The method may include performing a secondary service authorization of the UE within the access network using the APN OIA, and notifying an application server (AS) of the UE availability for the NIDD service using the generic non-IP APN.

Abstract: A method, a device, and a non-transitory storage medium are described in which a mobile edge computing handover service is provided. The mobile edge computing handover service provides for the prospective provisioning of a target mobile edge computing network based on mobility information pertaining to an end device. The mobile edge computing handover service includes managing the provisioning of the application or service, content, and context information in relation to a source mobile edge computing network and the target mobile edge computing network.

Abstract: Systems provide for provisioning, in a wireless network, in a network-service profile associated with a network-service subscriber, at least one of a power saving mode (PSM) parameter or an extended discontinuous reception (eDRX) parameter for use by a first user device; receiving a network service-related request from the first user device via an administrative non-IP packet data network (PDN) bearer established using a statically-allocated non-IP administrative access point name (APN); sending, via the PDN bearer, a first mobile terminated trigger delivery request (MT-TDR) including a bootstrap request trigger, generated by the network device, to the first user device; receiving, via the PDN bearer in response to the bootstrap request trigger, a first mobile originated originating delivery request (MO-ODR) bootstrap request; and sending, in response to the bootstrap request, a second MT-TDR including the at least one of the PSM parameter or the eDRX parameter.

Abstract: A method, a device, and a non-transitory storage medium are described in which a mobile edge computing handover service is provided. The mobile edge computing handover service provides for the prospective provisioning of a target mobile edge computing network based on mobility information pertaining to an end device. The mobile edge computing handover service includes managing the provisioning of the application or service, content, and context information in relation to a source mobile edge computing network and the target mobile edge computing network.

Abstract: Systems and methods are provided for network slice selection during an initial connection. A wireless station receives, from a core network device, network slice data for each network slice available via the wireless station, wherein the network slice data includes a slice identifier and corresponding slice characteristics for each network slice. The wireless station receives, from a user equipment (UE) device, a registration request message that indicates a network slice characteristic required by an application being executed on UE device. The wireless station selects, based on the network slice data from the core network device and the network slice characteristic from the UE device, one of the slice identifiers for servicing the UE device.

Abstract: A device may determine a subscriber identifier associated with a subscriber device. The device may obtain a service indicator based on the subscriber identifier. The service indicator may identify a network service to which a subscriber, associated with the subscriber identifier, is subscribed. The device may obtain a charging data function (CDF) identifier based on the service indicator. The CDF identifier may identify a destination CDF for charging messages associated with the network service. The device may establish a communication session associated with the subscriber device and the network service. The device may transmit one or more charging messages, associated with the communication session, to the destination CDF identified by the CDF identifier.

Abstract: A device may determine a subscriber identifier associated with a subscriber device. The device may obtain a service indicator based on the subscriber identifier. The service indicator may identify a network service to which a subscriber, associated with the subscriber identifier, is subscribed. The device may obtain a charging data function (CDF) identifier based on the service indicator. The CDF identifier may identify a destination CDF for charging messages associated with the network service. The device may establish a communication session associated with the subscriber device and the network service. The device may transmit one or more charging messages, associated with the communication session, to the destination CDF identified by the CDF identifier.

Abstract: A device may determine a subscriber identifier associated with a subscriber device. The device may obtain a service indicator based on the subscriber identifier. The service indicator may identify a network service to which a subscriber, associated with the subscriber identifier, is subscribed. The device may obtain a charging data function (CDF) identifier based on the service indicator. The CDF identifier may identify a destination CDF for charging messages associated with the network service. The device may establish a communication session associated with the subscriber device and the network service. The device may transmit one or more charging messages, associated with the communication session, to the destination CDF identified by the CDF identifier.

Abstract: A device may determine a subscriber identifier associated with a subscriber device. The device may obtain a service indicator based on the subscriber identifier. The service indicator may identify a network service to which a subscriber, associated with the subscriber identifier, is subscribed. The device may obtain a charging data function (CDF) identifier based on the service indicator. The CDF identifier may identify a destination CDF for charging messages associated with the network service. The device may establish a communication session associated with the subscriber device and the network service. The device may transmit one or more charging messages, associated with the communication session, to the destination CDF identified by the CDF identifier.

Abstract: A provisioning system may receive requests, such as from third party service providers, to provision dedicated bearers for traffic associated with the service providers. For example, a service provider may request a particular quality of service (“QoS”) level for traffic sent between the service provider and one or more user devices. This QoS level may be higher than a “normal” QoS level that is ordinarily provided. The provisioning system may establish a bearer, such as a dedicated non-guaranteed bitrate (“non-GBR”) bearer between a packet data network (“PDN”) gateway (“PGW”) and the user device, and may transmit traffic, associated with the service provider, via the dedicated non-GBR bearer. A QoS agent, installed at the user device, may ensure that traffic, associated with the service provider, is sent from the user device via the dedicated non-GBR bearer (e.g., as opposed to another bearer with a lower QoS level).

Abstract: A system may receive, based on a generic access point name stored by a user device, a request to establish a network connection. The request may include a user device identifier that identifies the user device. The system may determine, based on the user device identifier, a specific access point name associated with the user device. The specific access point name may be different from the generic access point name. The system may determine, based on the specific access point name, information that identifies a gateway node for processing traffic associated with the user device. The system may cause the network connection to be established based on the user device identifier and the information that identifies the gateway node.

Abstract: A system may be configured to store a set of service-level agreements (“SLAs”) associated with a subscriber. The system may receive key performance indicator (“KPI”) information for traffic that traverses one or more nodes of a network; forecast, based on the SLA information and the KPI information, a violation of the particular SLA; take corrective action, based on the forecasting; and output, to the subscriber, derived information based on the KPI information. The derived information may be outputted after taking the corrective action, and may indicate that the particular SLA was not violated. The derived information may be outputted at a slower rate than a rate at which the KPI information is received by the system.

Abstract: A system may be configured to store a set of service-level agreements (“SLAs”) associated with a subscriber. The system may receive key performance indicator (“KPI”) information for traffic that traverses one or more nodes of a network; forecast, based on the SLA information and the KPI information, a violation of the particular SLA; take corrective action, based on the forecasting; and output, to the subscriber, derived information based on the KPI information. The derived information may be outputted after taking the corrective action, and may indicate that the particular SLA was not violated. The derived information may be outputted at a slower rate than a rate at which the KPI information is received by the system.