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:
An example method is provided in one example embodiment and may include receiving a request from a user equipment (UE) to access a wireless access network, wherein the UE is currently accessing one or more other wireless networks; determining by a Policy and Charging Rules Function (PCRF) whether a subscriber associated with the UE is authorized to access the wireless access network based, at least in part, on a profile for the subscriber; and communicating one of a wireless access rejection and a wireless access acceptance to the UE based on the determination. In some instances, the determining can include recovering the profile for the subscriber associated with the UE from a Subscriber Profile Repository (SPR) using an International Mobile Subscriber Identity (IMSI) for the subscriber.
Abstract:
The present technology is directed to establishing a connection between a client device within a 2G or 3G network and 5G core through an interworking function. The present technology can perform establishing a Gn-4G interworking function (IWF) between a client access network and a packet anchor network and performing one or more network functions through the Gn-4G IWF in providing a client of the client access network access to network services through the packet anchor network. The one or more network functions appear as one or more Gateway GPRS Support Node (GGSN) functions from the client access network (e.g., 2G or 3G network). The one or more network functions concurrently appear as one or more S4 Serving GPRS Support Node (SGSN) functions from the packet anchor network (e.g., 4G or 5G network).
Abstract:
The present technology is directed to establishing a connection between a client device within a 2G or 3G network and 5G core through an interworking function. The present technology can perform establishing a Gn-4G interworking function (IWF) between a client access network and a packet anchor network and performing one or more network functions through the Gn-4G IWF in providing a client of the client access network access to network services through the packet anchor network. The one or more network functions appear as one or more Gateway GPRS Support Node (GGSN) functions from the client access network (e.g., 2G or 3G network). The one or more network functions concurrently appear as one or more S4 Serving GPRS Support Node (SGSN) functions from the packet anchor network (e.g., 4G or 5G network).
Abstract:
A policy enforcement technique may be performed at a network node configured for exposure of services and capabilities, such as a service and capability exposure function (SCEF) or a network exposure function (NEF). In one illustrative example, the network node may receive a message which includes a request for background data transfer from an application server (AS) to a plurality of UEs of a group. The message may include mobile-terminated (MT) data to be delivered, a group ID associated with the group, a total bandwidth for the background data transfer for the group, and a transfer policy ID associated with a transfer policy. The network node may verify whether the total bandwidth for the background data transfer for the group is within a predefined aggregate bandwidth limit indicated in the transfer policy data. The network node may cause the background data to be sent to each one of the plurality of UEs via the mobile network, if the total bandwidth is within the predefined aggregate bandwidth limit. In some implementations, the network node may be configured to facilitate background data transfers and perform policy enforcement for transfers involving both IP data delivery and non-IP data delivery (NIDD).
Abstract:
A network function (NF) profile repository function (NPRF) is provided to receive, for each one of a plurality of NF instances of a plurality of different NF types, information associated with the NF instance and store the information in memory. The NPRF may then also receive, from an NF repository function (NRF), a message which indicates a request for information associated with one or more NF instances of an indicated NF type. In response, the NPRF may retrieve, from the memory based on the indicated NF type, information associated with the one or more NF instances. The NPRF may send, to the NRF, a message which indicates a response to the request, where the response includes retrieved information associated with the one or more NF instances.
Abstract:
In one embodiment, a method includes assigning a number of threads for user plane functions to a corresponding number of transmit queues for transmission of packets on a network interface, assigning additional threads exceeding the number of transmit queues to software transmission queues associated with the threads assigned to the transmit queues, identifying a load at each of the threads, dynamically updating assignment of the additional threads to the software transmission queues based on the load at the threads, and transmitting packets from the transmit queues for transmission on a network from a physical interface at a network device. An apparatus and logic are also disclosed herein.
Abstract:
Single sign-on (SSO) techniques of the present disclosure provide for enterprise application user identities that are bound to a mobile identity (e.g. IMSI) associated with a user equipment (UE) for authentication, using general bootstrapping architecture (GBA)/general authentication architecture (GAA) functionality in combination with identity provider (IDP) functionality (e.g. OpenID Connect), all of which may be provided in an enterprise network. The present techniques need not rely on GBA/GAA infrastructure of a mobile network operator (MNO), and have little or no impact or effect on the mobile network.
Abstract:
Subscription-based, user equipment (UE) event notification techniques for use in a mobile network are described. In one illustrative example, an event subscription request from an application server may be received at a network exposure function (NEF) entity of a 5G mobile network. The event subscription request may include a list of one or more subscribed events for a UE, which may include a UE attach event and/or a UE detach event. A context which indicates the one or more subscribed events may be created for the UE. Sometime during network operation, an indication of an occurrence of an event associated with the UE is received. The indication is received from a policy and charging function (PCF) entity when the UE is configured for IP data delivery, or from an access and mobility management function (AMF) entity when the UE is configured for non-IP data delivery (NIDD).
Abstract:
A network function (NF) entity in a communication network receives authentication data associated with a User Equipment (UE), determines the UE supports a blockchain registration procedure based on the authentication data, exchanges authentication messages with a Blockchain Roaming Broker (BRB) entity over a blockchain network interface, receives a blockchain authentication confirmation from the BRB entity, and registers the UE with the core network based on the blockchain authentication confirmation.