Abstract: A first network device may receive, from an application server, a first request for a dedicated bearer session for an application with a quality of service (QoS) and for a notification of an idle session for the application. The first network device may generate, based on the first request, a second request to be notified regarding expiration of an idle session timer for the application, and may provide the second request to a second network device. The first network device may receive, from the second network device and based on the second request, a notification of expiration of the idle session timer for the application, and may provide, to the application server, the notification of expiration of the idle session timer for the application.

Abstract: A method, a device, and a non-transitory storage medium are described in which a containerized network function (CNF) management service is provided. The service may provide for allocating discrete sets of CNF resources deployed as pods to provide application services to end devices; identifying at least one threshold resource value associated with a first number of the deployed pods which are activated to provide the application services; determining an anticipated nonsatisfaction of the at least one threshold resource value associated with the first number of the deployed pods; and invoking, for a period of time, horizontal pod autoscaling (HPA) via an application programming interface to activate a second number of the deployed pods to provide the application services, wherein the HPA is performed non-incrementally until at least one of the period of time has elapsed or each of the deployed pods has been activated to provide the application services.

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: A method, a device, and a non-transitory storage medium are described in which an capacity modification service is provided in relation to a virtual device. The capacity modification service may include a first virtual device of a host device that is able to a receive resource modification request directed to a second virtual device of the host device. The modification request may be received via user interface or application programming interface associated with the first and second virtual devices. The first virtual device may calculate resource values for resources of the prospective resource modification. The first virtual device may communicate the resource values to management layer of the host device, such as a container orchestrator. The container orchestrator may allocate the resources for the second virtual device based on the resource values.

Abstract: Systems and methods described herein include receiving, from a first network function, a request to receive a notification when a second network function becomes available after a failure. A status update may be received from the second network function indicating that the second network function is available. It may be determined that the second network function is in a stable state. A notification may be sent, to the first network function, that the second network function is available along with an indication of a time period in which to switch from accessing a third network function to accessing the second network function.

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 device may include a processor configured to register a network function, of a core network associated with a radio access network, in a network function repository for the core network. The processor may be further configured to obtain load information for the network function, wherein the load information indicates a load associated with the network function during a time period; determine that the load associated with the network function has reached a threshold based on the load information; and send an alert to an orchestration system to adjust a capacity for the network function, in response to determining that the load associated with the network function has reached the threshold.

Abstract: A device may include a processor configured to register a network function, of a core network associated with a radio access network, in a network function repository for the core network. The processor may be further configured to obtain load information for the network function, wherein the load information indicates a load associated with the network function during a time period; determine that the load associated with the network function has reached a threshold based on the load information; and send an alert to an orchestration system to adjust a capacity for the network function, in response to determining that the load associated with the network function has reached the threshold.

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 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: Systems and methods described herein include receiving, from a first network function, a request to receive a notification when a second network function becomes available after a failure. A status update may be received from the second network function indicating that the second network function is available. It may be determined that the second network function is in a stable state. A notification may be sent, to the first network function, that the second network function is available along with an indication of a time period in which to switch from accessing a third network function to accessing the second network function.

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: Systems and methods described herein include receiving, from a first network function, a request to receive a notification when a second network function becomes available after a failure. A status update may be received from the second network function indicating that the second network function is available. It may be determined that the second network function is in a stable state. A notification may be sent, to the first network function, that the second network function is available along with an indication of a time period in which to switch from accessing a third network function to accessing the second network function.

Abstract: A device may receive a request to establish a packet data network (PDN) session for a user device. The device may provide a first instruction to establish the PDN session for the user device with a temporary default bearer based on receiving the request. The temporary default bearer may be maintained for less than a duration of the PDN session. The device may receive an indication to release the temporary default bearer after providing the first instruction to establish the PDN session. The device may provide a second instruction to release the temporary default bearer and maintain one or more signaling sessions associated with the PDN session based on receiving the indication to release the temporary default bearer. The one or more signaling sessions, associated with the PDN session, may be maintained after the temporary default bearer has been released.

Abstract: A method, a device, and a non-transitory storage medium are provided to receive from an end device, a session establishment message pertaining to a voice service that restricts the end device to place a voice call to and receive a voice call from a designated call center; replace a uniform resource identifier of the designated call center included in the session establishment message, with an enterprise identifier included in subscription data pertaining to the end device; select, based on the enterprise identifier, another network device to transmit the session establishment message; and transmit the session establishment message to another device based on the selection.

Abstract: A method, a device, and a non-transitory storage medium are provided to receive from an end device, a session establishment message pertaining to a voice service that restricts the end device to place a voice call to and receive a voice call from a designated call center; replace a uniform resource identifier of the designated call center included in the session establishment message, with an enterprise identifier included in subscription data pertaining to the end device; select, based on the enterprise identifier, another network device to transmit the session establishment message; and transmit the session establishment message to another device based on the selection.

Abstract: A device may receive a request to establish a packet data network (PDN) session for a user device. The device may provide a first instruction to establish the PDN session for the user device with a temporary default bearer based on receiving the request. The temporary default bearer may be maintained for less than a duration of the PDN session. The device may receive an indication to release the temporary default bearer after providing the first instruction to establish the PDN session. The device may provide a second instruction to release the temporary default bearer and maintain one or more signaling sessions associated with the PDN session based on receiving the indication to release the temporary default bearer. The one or more signaling sessions, associated with the PDN session, may be maintained after the temporary default bearer has been released.

Abstract: A method, a device, and a non-transitory storage medium are provided to receive, from an end device, a registration message pertaining to a voice service that restricts the end device to place a voice call to and receive a voice call from a designated call center; obtain subscription data pertaining to the end device and including an enterprise identifier; determine whether the end device is authorized to use the voice service based on the enterprise identifier; transmit to the end device, an acceptance message indicating a registration of the end device when the end device is authorized; receive from the end device, a session establishment message; replace a uniform resource identifier of the designated call center included in the session establishment message, with the enterprise identifier; select, based on the enterprise identifier, another network device to transmit the session establishment message; and transmit the session establishment message based on the selection.

Abstract: A method, a device, and a non-transitory storage medium are provided to receive, from an end device, a registration message pertaining to a voice service that restricts the end device to place a voice call to and receive a voice call from a designated call center; obtain subscription data pertaining to the end device and including an enterprise identifier; determine whether the end device is authorized to use the voice service based on the enterprise identifier; transmit to the end device, an acceptance message indicating a registration of the end device when the end device is authorized; receive from the end device, a session establishment message; replace a uniform resource identifier of the designated call center included in the session establishment message, with the enterprise identifier; select, based on the enterprise identifier, another network device to transmit the session establishment message; and transmit the session establishment message based on the selection.

Abstract: A device may receive a request to establish a packet data network (PDN) session for a user device. The device may provide a first instruction to establish the PDN session for the user device with a temporary default bearer based on receiving the request. The temporary default bearer may be maintained for less than a duration of the PDN session. The device may receive an indication to release the temporary default bearer after providing the first instruction to establish the PDN session. The device may provide a second instruction to release the temporary default bearer and maintain one or more signaling sessions associated with the PDN session based on receiving the indication to release the temporary default bearer. The one or more signaling sessions, associated with the PDN session, may be maintained after the temporary default bearer has been released.