Abstract: A network function (NF) entity in a communication network determines a User Equipment (UE) supports a blockchain authentication procedure, exchanges authentication messages with a Blockchain Authentication Function (BAF) entity over a blockchain network interface (e.g., based on the blockchain authentication procedure), receives a blockchain authentication confirmation from the BAF entity, and registers the UE based on the blockchain authentication confirmation.

Abstract: An example method is provided in one example embodiment and may include provisioning a user equipment (UE) with a list comprising one or more locations at which the UE is to report its location; reporting a location of the UE when the location is identified in the list; provisioning the UE with one or more access network selection policy based on the reported location of the UE; and applying at least one access network selection policy at the UE based on the location of the UE. The list comprising the one or more locations can be sent to the UE from an Access Network Discovery and Selection Function (ANDSF) server after the UE reports its location to the ANDSF server. The one or more access network selection policies can be permanent type and/or temporal type policies.

Abstract: A network function (NF) entity in a communication network receives session request data associated with a User Equipment (UE), which includes blockchain authentication data. The NF entity selects a Blockchain Authentication Function (BAF) entity based on the session request data, and exchanges at least a portion of the blockchain authentication data with the BAF entity over a blockchain network interface. The NF entity further receives authentication confirmation data from the BAF entity over the blockchain network interface, and establishes a data session associated with the UE based on the authentication confirmation data.

Abstract: In accordance with various implementations, a method is performed at a data plane node with one or more processors, non-transitory memory, and a control interface between a network function module associated with the data plane node and a switch associated with the data plane node. The method includes determining whether an offload capability is available for a data flow received at an ingress network interface of the data plane node. The method also includes determining whether the data flow satisfies offload criteria in response to determining that the offload capability is available. The method includes bypassing the network function module associated with the data plane node and providing the data flow to at least one of the switch associated with the data plane node or an egress network interface associated with the data plane node in response to determining the offload capability is available and the offload criteria is satisfied.

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: In accordance with various implementations, a method is performed at a data plane node with one or more processors, non-transitory memory, and a control interface between a network function module associated with the data plane node and a switch associated with the data plane node. The method includes determining whether an offload capability is available for a data flow received at an ingress network interface of the data plane node. The method also includes determining whether the data flow satisfies offload criteria in response to determining that the offload capability is available. The method includes bypassing the network function module associated with the data plane node and providing the data flow to at least one of the switch associated with the data plane node or an egress network interface associated with the data plane node in response to determining the offload capability is available and the offload criteria is satisfied.

Abstract: A network slice manager receives a workload mobility request to add network resources to a domain in the communication network, and authenticates a virtual network function (VNF) with a blockchain authentication function (BAF) over a blockchain network interface based on the workload mobility request. The network slice manager further receives an indication of a successful authentication from the BAF, and instantiates the VNF in the domain of the communication network based on the indication of the successful authentication. Notably, these authentication processes may be readily adapted to instantiate new network resources or migrate existing network resources between domains.

Abstract: A method is provided in one example embodiment and may include maintaining, by a Diameter Routing Agent (DRA), an availability status for a plurality of network elements; receiving a request associated with a user equipment (UE) session, wherein a first network element of the plurality of network elements is serving the UE session; determining that the first network element serving the UE session is unavailable; and re-establishing the UE session at a second network element of the plurality of network elements that is available, wherein the re-establishing is performed without terminating the UE session.

Abstract: An example method is provided in one example embodiment and may include generating a content token, wherein the content token is generated for a particular content type of a particular application service based on a trust relationship established between the particular application service and a mobile service provider; and embedding the content token in one or more packets of a plurality of packets sent to a user equipment (UE) for one or more Internet Protocol (IP) flows associated with the particular content type, wherein the content token is embedded in an unencrypted portion of each packet that is separate from an encrypted data payload portion of each packet.

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: Methods and apparatus for use in establishing a group session in a mobile network for subscribers associated with a group are described. In one illustrative example, an access and mobility management function (AMF) entity receives, from a user equipment (UE), a request for registration which includes network slice selection assistance information (NSSAI). The NSSAI includes a group identifier associated with a group of subscribers. The AMF entity sends, to a unified data management (UDM) entity, a request for subscriber data which includes the group identifier. The AMF entity receives, from the UDM, a response to the request for subscriber data which includes a plurality of subscriber identifiers corresponding to the subscribers of the group. For a group session, the AMF entity creates a context associated with the group identifier and stores the context locally.

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.

Abstract: A method is provided in one example embodiment and may include maintaining, by a Diameter Routing Agent (DRA), an availability status for a plurality of network elements; receiving a request associated with a user equipment (UE) session, wherein a first network element of the plurality of network elements is serving the UE session; determining that the first network element serving the UE session is unavailable; and re-establishing the UE session at a second network element of the plurality of network elements that is available, wherein the re-establishing is performed without terminating the UE session.

Abstract: Methods and apparatus for use in reducing signal latency in a mobile network with use of localized Unified Data Management (UDM) entities are described. For example, the technique may employ a plurality of localized UDMs, where each localized UDM is associated with a unique location area. A localized UDM provides for storage of, in a localized Unified Data Repository (UDR), subscriber profile data associated with a subscriber of user equipment (UE). The subscriber profile data stored in the localized UDR may be a replica or copy of at least a subset of subscriber profile data for the subscriber stored in a UDR of a “centralized” UDM. Query access to the localized UDR may be provided for network functions (NFs) or subscriber/UEs. The replica or copy of subscriber profile data may be stored in the localized UDR for those subscribers having use in the location area.

Abstract: Methods and apparatus for use in reducing signal latency in a mobile network with use of localized Unified Data Management (UDM) entities are described. For example, the technique may employ a plurality of localized UDMs, where each localized UDM is associated with a unique location area. A localized UDM provides for storage of, in a localized Unified Data Repository (UDR), subscriber profile data associated with a subscriber of user equipment (UE). The subscriber profile data stored in the localized UDR may be a replica or copy of at least a subset of subscriber profile data for the subscriber stored in a UDR of a “centralized” UDM. Query access to the localized UDR may be provided for network functions (NFs) or subscriber/UEs. The replica or copy of subscriber profile data may be stored in the localized UDR for those subscribers having use in the location area.

Abstract: In accordance with various implementations, a method is performed at a data plane node with one or more processors, non-transitory memory, and a control interface between a network function module associated with the data plane node and a switch associated with the data plane node. The method includes determining whether an offload capability is available for a data flow received at an ingress network interface of the data plane node. The method also includes determining whether the data flow satisfies offload criteria in response to determining that the offload capability is available. The method includes bypassing the network function module associated with the data plane node and providing the data flow to at least one of the switch associated with the data plane node or an egress network interface associated with the data plane node in response to determining the offload capability is available and the offload criteria is satisfied.

Abstract: Disclosed is a method that includes periodically observing packets in a user plane according to at least one key performance indicator in a configuration file to yield an observation, wherein the observation represents a closed-loop demand of resources within the user plane. The method includes adjusting, via a scheduler in the user plane and based on the observation, a binding of cores to work items. The binding between cores and work items is dynamic and changeable to improve performance. The at least one key performance indicator can include one or more of a CPU utilization, latency and packet drops. The workload allocations can include work items that are individually scheduleable functions that operate on a queue of packets within the user plane.

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: 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: A method is provided in one example embodiment and may include receiving load information for a plurality of cells of a Radio Access Network (RAN); determining, for each of a plurality of user equipment (UE) in each cell, identification information for each UE and an Access Point Name (APN) to which each UE is connected; identifying, from a plurality of policy servers, each policy server that serves each APN to which each UE in each cell of the plurality of cells is connected; and sending, to each of a particular policy server, congestion information comprising: an identity for each cell having UE that are connected to each APN served by the particular policy server; the corresponding congestion level for each of the cells; and a per-cell UE list identifying each of a plurality of UE connected to each of APNs served by the particular policy server.