Abstract:
An example method is provided in one example embodiment and may include receiving a packet for a subscriber at a gateway, wherein the gateway includes a local policy anchor for interfacing with one or more policy servers and one or more classifiers for interfacing with one or more service chains, each service chain including one or more services accessible by the gateway; determining a service chain to receive the subscriber's packet; appending the subscriber's packet with a header, wherein the header includes, at least in part, identification information for the subscriber and an Internet Protocol (IP) address for the local policy anchor; and injecting the packet including the header into the service chain determined for the subscriber.
Abstract:
Presented herein are techniques to provide network slice admission control in a mobile network. In one example, a method may include obtaining, by an access management element of a mobile network, a registration request from a user equipment; determining, based on the registration request, for each of one or more network slices whether there is: available registration capacity for each network slice for the user equipment based on a registration quota configured for each network slice, available session capacity for each network slice based on a session quota configured for each network slice, and available bit rate capacity for each slice based on a maximum bit rate amount configured for each network slice; and providing, based on the determining, a registration indication to the user equipment for each network slice indicating whether the user equipment is or is not allowed registration for each of the network slices.
Abstract:
In a Fifth Generation (5G) network having an enhanced SBA (eSBA) architecture, a message with a header used to signal binding information (e.g. HTTP custom header for 3gpp-Sbi-Binding) may be received at a recipient NF (service) instance in a direct communication or via a service communication proxy (SCP) in an indirect communication. A binding indication comprising an address of an NF (service) instance may be obtained from the header. One or more alternative binding indications comprising one or more alternative addresses of one or more alternative NF (service) instances may also be obtained from the header. The one or more alternative NF (service) instances may be equivalent NFs (services) of the same NF (Service) Set as the NF (service) instance. The address may be used for communication of messages to the NF (service) instance, and the one or more alternative addresses may be used for load balancing or backup failure.
Abstract:
A control plane (CP) function for mobility management may receive, from a user equipment (UE), a message which indicates a registration request for registration to a network slice. The CP function may select, as an allowed slice ID, a first slice ID of a first network slice in which to register the UE. The first slice ID has a slice/service type (SST) value indicating an SST and a first slice differentiator (SD) value associated with a first level of service to be provided. The CP function may alternatively select, as the allowed slice ID, a second slice ID of a second network slice in which to register the UE based on unavailability of the slice type associated with the first level of service. The second slice ID has the SST value indicating the slice type and a second SD value associated with a second level of service to be provided.
Abstract:
A network function selectively supports a mobile device with network settings appropriate for the device context of the mobile device. The network function obtains a device profile for the mobile device, which identifies multiple device groups, with each device group being associated with a corresponding set of network settings. The network function selects a device group among the device groups in the device profile based on the device context of the mobile device. The network function directs at least one network function in the network to support the mobile device with a set of network settings corresponding to the selected device group.
Abstract:
Presented herein are techniques to facilitate resiliency, overload control, and/or the like for an Access and Mobility Management Function (AMF) in a Third Generation Partnership Project (3GPP) mobile network architecture. In one instance, a method is provided that includes initiating, by a buddy AMF, a heartbeat exchange with a primary AMF. The method may further include identifying a status condition for the primary AMF by the buddy AMF based on the heartbeat exchange and providing a status indication to a radio access network node by the buddy AMF based on the status condition for the primary AMF.
Abstract:
Techniques are described herein for network slice support of respective transport protocols. In one example, a session management function obtains, from a user equipment, a request for a network slice identifier in a network that includes a plurality of network slices each configured to support a respective transport protocol. In response to the request, the session management function identifies a first transport protocol of the respective transport protocols by which the user equipment is to communicate. Based on the first transport protocol, the session management function identifies a first network slice of the plurality of network slices by which the user equipment is to communicate. The first network slice is configured to support the first transport protocol. The session management function provides the network slice identifier to the user equipment. The network slice identifier corresponds to the first network slice.
Abstract:
Systems, methods, and computer-readable media for managing service calls over a network may include a signal routing engine with a maintained forwarding table for various network functions and micro-services in a services back end for the network. The signal routing engine can include a call conversion service for converting REST API calls to an internal network call protocol for increasing network function processing speeds, decreasing bandwidth usage, and improving network responsiveness and manageability.
Abstract:
Systems, methods, and computer-readable media for managing service calls over a network may include a signal routing engine with a maintained forwarding table for various network functions and micro-services in a services back end for the network. The signal routing engine can include a call conversion service for converting REST API calls to an internal network call protocol for increasing network function processing speeds, decreasing bandwidth usage, and improving network responsiveness and manageability.
Abstract:
Systems, methods, and computer-readable media for managing service calls over a network may include a signal routing engine with a maintained forwarding table for various network functions and micro-services in a services back end for the network. The signal routing engine can include a call conversion service for converting REST API calls to an internal network call protocol for increasing network function processing speeds, decreasing bandwidth usage, and improving network responsiveness and manageability.