Abstract: In one illustrated example, automated or semi-automated system operations for Massive IoT (MIoT) deployment may involve the automatic assignment of external IDs, subscriber IDs (e.g. IMSIs), and mobile network IDs (e.g. MSISDNs) to IoT devices of a group, followed by the provisioning of assigned identities at the relevant network nodes and the IoT devices themselves. The process may continue seamlessly with network slice orchestration for the creation of a network slice instance (NSI) and the provisioning of its associated Network Slice Selection Assistance Information (NSSAI) and NSI ID at the relevant network nodes. Network Slice Selection Policies (NSSP) may be derived and sent to a policy function and subsequently to IoT devices of the group. Signaling efficiency may be achieved by performing operations on a group basis.

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: 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 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: In one illustrated example, automated or semi-automated system operations for Massive IoT (MIoT) deployment may involve the automatic assignment of external IDs, subscriber IDs (e.g. IMSIs), and mobile network IDs (e.g. MSISDNs) to IoT devices of a group, followed by the provisioning of assigned identities at the relevant network nodes and the IoT devices themselves. The process may continue seamlessly with network slice orchestration for the creation of a network slice instance (NSI) and the provisioning of its associated Network Slice Selection Assistance Information (NSSAI) and NSI ID at the relevant network nodes. Network Slice Selection Policies (NSSP) may be derived and sent to a policy function and subsequently to IoT devices of the group. Signaling efficiency may be achieved by performing operations on a group basis.

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: 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: 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: 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: 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: 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: 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: 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.

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 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: 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 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 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.