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 network function (NF) entity in a communication network receives User Plane Function (UPF) registration information for a plurality of UPFs, the registration information including a respective network attribute for each UPF. The NF entity associates each UPF with a corresponding network based on the respective network attribute, and map one or more User Equipment (UE) to the corresponding network based on a security policy to create a UE-to-network table. The NF further receives a request to establish a session for a subsequent UE, the request including a subsequent UE identifier, and determine an access permission for the subsequent UE to access the corresponding network based on the subsequent UE identifier and the UE-to-network table. The NF selects one UPF from the plurality of UPF to service the session for the subsequent UE based on the access permission, and an association between the one UPF and the corresponding network.

Abstract: A solution for selecting an optimal user Plane entity (with Control and User Plane Separation (CUPS)) per UE during seamless roaming. In one embodiment, a method is provide that is performed by a control plane entity in a mobile core network that supports inter public land mobile network (PLMN) roaming among two or more PLMNs. The method includes obtaining a create session request from an entity in a second PLMN to which a user equipment has roamed from a first PLMN; selecting a particular user plane entity among a plurality of user plane entities based on one or more user equipment related parameters; and establishing a session with the particular user plane entity to serve user plane traffic in the mobile core network for the user equipment.

Abstract: A Network Function (NF) entity in a telecommunication network receives blockchain credentials associated with UE and selects a Blockchain Charging Function (BCF). The NF entity further generates a Charging Data Record (CDR) corresponding to network resources, and sends a charging request based on the CDR (and policy rules) to the BCF entity over a blockchain network interface. The BCF entity sends a confirmation of the charging request, and the NF entity, based on the confirmation, provisions the network resources to the UE.

Abstract: Aspects of the disclosed technology provide ways to report User Equipment (UE) device locations in a 5G network for the purpose of redirecting application traffic from proximately located Data Networks (DNs). In one aspect, the disclosed technology encompasses a process for conveying User Equipment (UE) information to an Application Function (AF), the process includes steps for receiving, at an intermediate-User Plane Function (I-UPF) entity, User Equipment (UE) uplink data from a Radio Access Network (RAN), determining if sharing of location information or application information associated with the UE is restricted, and encapsulating first location metadata or application metadata in an SRv6 packet if the sharing of location information or application information is not restricted. Systems and machine-readable media are also provided.

Abstract: Aspects of the disclosed technology provide ways to report User Equipment (UE) device locations in a 5G network for the purpose of redirecting application traffic from proximately located Data Networks (DNs). In one aspect, the disclosed technology encompasses a process for conveying User Equipment (UE) information to an Application Function (AF), the process includes steps for receiving, at an intermediate-User Plane Function (I-UPF) entity, User Equipment (UE) uplink data from a Radio Access Network (RAN), determining if sharing of location information or application information associated with the UE is restricted, and encapsulating first location metadata or application metadata in an SRv6 packet if the sharing of location information or application information is not restricted. Systems and machine-readable media are also provided.

Abstract: A control plane (CP) entity is to adaptively reroute user plane traffic of a mobile node (MN) with use of a segment routing (SR) for IPv6. A message indicating an attachment of the MN to the mobile network is received selecting a first user plane (UP) anchor node. A first set of home network prefixes (HNPs) are allocated to the MN. An IP traffic flow using a first HNP prefix is established between the MN and a correspondent node (CN) along a first network path—defined at least in part by the first UP anchor node and an anchor node of the CN. In response to a handover of the MN, a message indicating a subsequent attachment of the MN is received selecting a second UP anchor node. The second UP anchor node is instructed to host the first HNP prefix previously allocated by the first UP anchor node.

Abstract: A control plane of a network, including radios of a radio access network controlled by the control plane and user plane functions controlled by the control plane, establishes first and second protocol data unit (PDU) connections each to handle the same flows of traffic for ultra-reliable low latency communications (URLLC) from user equipment to a data network through first and second source radios, respectively. Due to mobility of the user equipment, the control plane relocates the flows from the first and second source radios to first and second target radios, respectively. To relocate the flows, the control plane receives from the first target radio a notification that identifies flows that cannot be activated on the first target radio. In response to the notification, the control plane commands the first target radio to prioritize the flows that cannot be activated above remaining ones of the flows.

Abstract: Various implementations disclosed herein enable programming user plane gateway controllers over enhanced N9 interfaces. In various implementations, a method of gateway controlling is performed by a computing device including one or more processors, and a non-transitory memory. In various implementations the method includes determining, by a first packet gateway controller connected to a first session manager device, that a user equipment moved to a geographical area that is served by a second session manager device. In some implementations, the method includes receiving, by the first packet gateway device, a set of information for a second packet gateway device. In some implementations, the method includes transmitting, by the first packet gateway device, a session establishment request via a first network interface to the second packet gateway controller using segment routing via a second network interface.

Abstract: A control plane (CP) entity is to adaptively reroute user plane traffic of a mobile node (MN) with use of a segment routing (SR) for IPv6. A message indicating an attachment of the MN to the mobile network is received selecting a first user plane (UP) anchor node. A first set of home network prefixes (HNPs) are allocated to the MN. An IP traffic flow using a first HNP prefix is established between the MN and a correspondent node (CN) along a first network path—defined at least in part by the first UP anchor node and an anchor node of the CN. In response to a handover of the MN, a message indicating a subsequent attachment of the MN is received selecting a second UP anchor node. The second UP anchor node is instructed to host the first HNP prefix previously allocated by the first UP anchor node.

Abstract: A Network Function (NF) entity in a telecommunication network receives blockchain credentials associated with UE and selects a Blockchain Charging Function (BCF). The NF entity further generates a Charging Data Record (CDR) corresponding to network resources, and sends a charging request based on the CDR (and policy rules) to the BCF entity over a blockchain network interface. The BCF entity sends a confirmation of the charging request, and the NF entity, based on the confirmation, provisions the network resources to the UE.

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 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: Various implementations disclosed herein enable blockchain programming in NB-IoT devices. In various implementations, a method of blockchain authentication is performed by a computing device including one or more processors, and a non-transitory memory. In various implementations, the method includes maintaining a blockchain for a machine-to-machine network, wherein the machine-to-machine network is a narrowband internet of things network. In some implementations, the method includes receiving a request for a first set of data from the blockchain by a second device. In some implementations, the method includes determining based on the request, the first set of data from the blockchain by traversing a series of blocks from the blockchain. In some implementations, the method includes packaging the first set of data from the blockchain according to a protocol into a packaged data unit and transmitting the packaged data unit to the second device.

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: 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: In one embodiment, a method comprises communicating with a plurality of network elements via a first communication protocol to obtain state information of the plurality of network elements; receiving a request via a second communication protocol for a communication session to be established for a client computing device; selecting one or more network elements, wherein the selection is based on at least a portion of the state information of the network elements; and communicating identification information of the one or more network elements selected for use in the communication session.

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 embodiments, a method is performed including establishing a first communication session between an application function and a user equipment assigned a first IP address. The method includes determining, by the application function, that the user equipment has changed location. The method includes, in response to determining that the user equipment has changed location, sending, by the application function, a request that the user equipment be assigned a second IP address. The method includes establishing a second communication session between the application function and the user equipment assigned the second IP address.

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.