Authorization framework for NF(s) for sixth-generation core networks using distributed ledger
The authorization framework for 6G networks employs distributed ledger technology to address the challenges of security and complexity in distributed architectures by using decentralized identifiers for authentication and authorization, enhancing security and efficiency through transparent and distributed access control.
Patent Information
- Application Number
- PCT/IB2024/055096
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2023-05-26
- Filing Date
- 2024-05-24
- Publication Date
- 2024-12-05
AI Technical Summary
The increasing complexity and distribution of 6G networks pose challenges in ensuring security, managing traffic flow, maintaining low latency, and high quality of experience between network function service providers and consumers, particularly in distributed network architectures, where existing authorization frameworks like OAuth 2.0 and centralized NRFs are inadequate for zero-trust and defense-in-depth approaches.
An authorization framework utilizing distributed ledger technology to enable decentralized identifier (DID) based authentication and authorization, where network functions verify properties and create entries in a distributed ledger, allowing for transparent and secure service provisioning across the network, reducing reliance on centralized entities and enhancing security through zero-trust principles.
This framework enhances network security by distributing authentication and authorization processes, reducing the risk of single-point failures, improving transparency, and enabling more efficient and secure service provisioning in 6G networks by leveraging distributed ledger technology for integrity verification and access control.
Smart Images

Figure IB2024055096_05122024_PF_FP_ABST
Abstract
Description
AUTHORIZATION FRAMEWORK FOR NF(S) FOR SIXTH-GENERATION CORE NETWORKS USING DISTRIBUTED LEDGERField
[0001] Embodiments described herein relate generally to wireless and cellular technologies, and more specifically to an authorization framework for network functions for core networks, and even more specifically to an authorization framework for network functions for sixth-generation (6G) core networks using distributed ledger(s).Background
[0002] This section introduces aspects that may be helpful in facilitating a better understanding of the disclosure. Accordingly, the statements of this section are to be read in this light and are not to be understood as admissions about what is in the prior art or what is not in the prior art.
[0003] Fourth generation (4G) wireless mobile telecommunications technology, also known as Long Term Evolution (LTE) technology, was designed to provide high capacity mobile multimedia with high data rates particularly for human interaction. Next generation or fifth generation (5G) technology is intended to be used not only for human interaction, but also for machine type communications in so-called Internet of Things (loT) networks.
[0004] Third generation partnership project (3GPP) 5G technology is a next generation of radio systems and network architecture that can deliver extreme broadband and ultra-robust, low latency connectivity. Relative, for example to 4G technology, 5G technology improves a variety of telecommunication services offered to the end users and helps to support massive broadband that delivers gigabytes of bandwidth per second on demand for both the uplink and downlink transmissions. Next generation systems, which utilize the 5G architecture, utilize virtualized radio access network (RAN) functions and core network functions. 5G cellular technology can offer higher data transfer speeds, lower latency, and greater network capacity compared to previous cellular technologies like 4G.
[0005] The 5G system architecture is divided into two main components: the radio access network (RAN) and the core network. The RAN is responsible for wireless communication between devices and the network, while the core network handles the distribution of data to and from the RAN. The hardware used in 5G technology can include 5G base stations such assmall cells and massive MIMO (multiple-input, multiple-output) antennas that transmit and receive data more efficiently. Other hardware / components used in 5G include 5G modems and chipsets to allow 5G-enabled devices to connect to the 5G network and communicate with other devices. The use of fiber optic cable or other similar technologies can enable 5G networks to connect the base stations to the core network with reduced latency. Edge computing infrastructure in 5G allow computing tasks to be performed closer to the end-user, reducing latency and increasing efficiency. This requires edge computing infrastructure, including servers and data centers, located closer to the network edge. 5G uses a variety of spectrum bands, including low-band, mid-band, and high-band frequencies, to deliver higher speeds and better network coverage. The combination of advanced hardware and system architecture allows 5G networks to deliver faster, more reliable, and more efficient mobile communication than prior technologies, such as 4G and LTE technologies. However, as the number and complexity of interne t-of-things (loT) devices, machine-to-machine communications over cellular networks, vehicle-to-everything (V2X), and virtualized / cloud-based functions / nodes become available and are added to existing 5G networks, it will become increasingly challenging to ensure security, manage traffic flow, maintain sufficiently low latency and sufficiently high quality of experience (QoE) between network function (NF) service providers (NFP) and NF service consumers (NFC), and maintain network integrity and reliability at network edges. A more geographically, structurally, and logically distributed network would require additional distribution of security features and processes.
[0006] Sixth-generation (6G) technologies, system architectures, and hardware, may offer advantages relative to 4G and 5G technologies. For example, while 5G can often deliver peak data rates of up to about 20 Gbps, 6G is expected to offer even faster speeds, with peak data rates potentially reaching up to about 1 Tbps or faster.
[0007] 6G is also expected to have even lower latency than prior technologies, such as 5G, with response times potentially as low as a few microseconds. This is expected to enable realtime communication and applications that require near-instantaneous response times. 6G is expected to utilize higher frequency bands, including terahertz frequencies, which are currently not used for cellular communication. These higher frequency bands have much greater bandwidth than the frequency bands used for 5G, which will enable faster data transfer rates. 6G is also expected to integrate artificial intelligence (Al) and machine learning (ME) technologies more deeply into the network, enabling intelligent and autonomous communication between devices. Further, 6G is expected to be more energy-efficient than 5G, with technologies such as smart antennas, dynamic spectrum sharing, and intelligent powermanagement systems, all designed to reduce energy consumption and increase battery life. According to some use cases, 6G is expected to enable new forms of communication, such as holographic communication, which will allow users to communicate with each other in a three- dimensional (3D) space. Accordingly, 6G is expected to be a significant improvement over 5G, with faster speeds, lower latency, and more advanced technologies like Al and holographic communication.
[0008] In 5G networks, authorization for network services that are provided by NFPare enabled via Service Based Architecture (SBA) using OAuth 2.0 wherein a Network Repository Function (NRF) plays the role of central OAuth Server. These processes and procedures are more clearly defined and described in 3GPP TS 33.501, the entire disclosure of which is hereby incorporated herein by reference in its entirety for all purposes.
[0009] A NRF is a key component of the 5G SBA which maintains an updated repository of the profiles of NFs available in the respective core network. An NF (e.g., NFP) that provides services to other NFs (e.g., NFC) must register its profile with the NRF.
[0010] In 6G, it is envisioned that networks will be much more distributed, such as with respect to security efforts, which are expected to be implemented with according to zero trust and defense-in-depth approaches. Accordingly, there is a need for security approaches that accommodate increasingly distributed network architectures and processes.Brief Summary
[0011] Described herein are systems, methods, apparatuses, and computer program products are provided in accordance with example embodiments to provide for an authorization framework for network functions for core networks, such as for an authorization framework for network functions for 6G core networks using distributed ledger(s).
[0012] In one example embodiment, an apparatus is provided that comprises at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus at least to perform: sending a message to an entity of a communication network, the message comprising property information associated with the apparatus, a public key associated with the apparatus, and a network function unique identifier associated with the apparatus; and receiving, from the entity of the communication network, a response to the message, the response comprising a signed hash of the property information, an indication that the property information associated with the apparatus is accepted, and a decentralized identifier (DID) number associated with the apparatus, wherein the apparatus isconfigured to include the DID number in requests for service or data in order to expedite integrity verification of the requests for service or data and authentication of the apparatus.
[0013] In some embodiments, the entity of the communication network comprises a verifiable credentials (VC) issuer. In some embodiments, the apparatus comprises an NFC. In some embodiments, the NFCcomprises a Network Data Analytics Function (NWDAF). In some embodiments, the instructions, when executed by the at least one processor, further causes the apparatus to perform at least: sending, to an NFPof the communication system, a request for service or data, the request for service or data comprising the DID number associated with the apparatus and the property information associated with the apparatus; and receiving, in response to the request for service or data, from the NFP, with the service or data requested, an access token associated with the apparatus and / or the DID number. In some embodiments, the instructions, when executed by the at least one processor, further causes the apparatus to perform at least: sending, to an NFP, a subsequent request for service or data, the subsequent request for service or data comprising the access token associated with the apparatus and / or the DID number; and receiving, from the NFP, in response to the subsequent request for service or data, the service or data requested in the subsequent request sent to the NFP.
[0014] According to another embodiment, a method can be carried out by an apparatus comprising a processor and a memory storing instructions that, when executed by the processor, cause the apparatus to carry out the method. In some embodiments, the method can comprise sending, from an NFCin a communication network, to an entity of the communication network, a message comprising property information associated with the NFC, a public key associated with the NFC, and a network function unique identifier associated with the NFC; and receiving, at the NFC, from the entity of the communication network, a response to the message, the response comprising a signed hash of the property information, an indication that the property information associated with the NFCis accepted, and a decentralized identifier (DID) number associated with the NFC, wherein the NFCis configured to include the DID number in subsequent service or data requests in order to expedite integrity verification of the subsequent service or data requests and authentication of the NFC.
[0015] In some embodiments, the entity of the communication network comprises a VC issuer. In some embodiments, the NFCcomprises an NWDAF. In some embodiments, the method can further comprise sending, to an NFPof the communication system, a request for service or data, the request for service or data comprising the DID number associated with the NFCand the property information associated with the NFc; and receiving, in response to the request for service or data, from the NFP, with the service or data requested, an access tokenassociated with the NFCand / or the DID number. In some embodiments, the method can further comprise sending, to an NFP, a subsequent request for service or data, the subsequent request for service or data comprising the access token associated with the apparatus and / or the DID number; and receiving, from the NFP, in response to the subsequent request for service or data, the service or data requested in the subsequent request sent to the NFP.
[0016] According to another embodiment, an apparatus can be provided that comprises at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus at least to perform: receiving, from an NFCin a communication network, a message comprising property information associated with the NFC, a public key associated with the NFC, and a network function unique identifier associated with the NFC; verifying the property information, the public key, and the network function unique identifier associated with the NFC; and, in an instance in which the apparatus verifies the property information, the public key, and the network function unique identifier associated with the NFC, providing, to the NFC, a response to the message, the response comprising a signed hash of the property information, an indication that the property information associated with the NFCis accepted, and a decentralized identifier (DID) number associated with the NFC. In some embodiments, the apparatus is configured to carry out integrity verification of subsequent service or data requests from the NFCand authentication of the NFCbased upon the DID number included in the subsequent service or data requests.
[0017] In some embodiments, the instructions, when executed by the at least one processor, cause the apparatus to further perform at least: creating, based at least upon the property information, the public key, and the network function unique identifier associated with the NFC, a distributed ledger (DL) entry associated with the NFC, the DL entry including the DID number for the NFC; and including the DL entry in a DL stored at a DL server of the communication system. In some embodiments, the instructions, when executed by the at least one processor, cause the apparatus to further perform at least: causing a distributed ledger (DL) server in the communication system to create a DL entry associated with the NFCbased at least upon the NFCinformation, the public key, and the network function unique identifier associated with the NFc; and receive, from the DL server, the DID number for the NFC.
[0018] According to another embodiment, a method can be carried out by an apparatus comprising a processor and a memory storing instructions that, when executed by the processor, cause the apparatus to carry out the method. In some embodiments, the method can comprise receiving, at an NFPin a communication network, from an NFCin the communication network, a message comprising property information associated with the NFc, a public keyassociated with the NFC, and a network function unique identifier associated with the NFC; verifying, using the NFC, the property information, the public key, and the network function unique identifier associated with the NFC; and, in an instance in which the NFCverifies the property information, the public key, and the network function unique identifier associated with the NFc, providing, from the NFP, to the NFC, a response to the message, the response comprising a signed hash of the property information, an indication that the property information associated with the NFCis accepted, and a decentralized identifier (DID) number associated with the NFC. In some embodiments, the NFPis configured to carry out integrity verification of subsequent service or data requests received from the NFCand authenticate the NFCbased upon the DID number included in the subsequent service or data requests.
[0019] In some embodiments, the method can further comprise creating, based at least upon the property information, the public key, and the network function unique identifier associated with the NFC, a distributed ledger (DL) entry associated with the NFC, the DL entry including the DID number for the NFC; and including the DL entry in a DL stored at a DL server of the communication system. In some embodiments, the method can further comprise causing a distributed ledger (DL) server in the communication system to create a DL entry associated with the NFCbased at least upon the property information, the public key, and the network function unique identifier associated with the NFC; and receiving, from the DL server, the DID number for the NFC.
[0020] According to another embodiment, an apparatus can be provided that comprises at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus at least to perform: sending a message to an NFPin a communication network, the message comprising a service or data request, the message further comprising a decentralized identifier (DID) number associated with the apparatus; in an instance in which the service or data request is a first request for data or services between the apparatus and the NFP, receiving, from the NFP, a network function profile request for a network function profile associated with the apparatus; and preparing, in response to the network function profile request, a network function consumer profile response including network function properties associated with the apparatus.
[0021] In some embodiments, the instructions, when executed by the at least one processor, cause the apparatus to further perform at least: sending, to the NFP, the network function consumer profile response; and receiving, from the NFP, in response to the network function consumer profile response, an access token associated with the DID number. In some embodiments, the instructions, when executed by the at least one processor, cause the apparatusto further perform at least: sending a message to the NFP, the message comprising a service or data request, the message further comprising the DID number associated with the apparatus and the access token associated with the network function consumer properties previously provided by the apparatus to the NFP; and, in an instance in which the message includes a valid DID number associated with the apparatus and a valid access token associated with the network function consumer properties previously provided by the apparatus to the NFP, receiving, from the NFP, a service or data response comprising the access token and the service or data requested in the service or data request.
[0022] According to another embodiment, a method can be carried out by an apparatus comprising a processor and a memory storing instructions that, when executed by the processor, cause the apparatus to carry out the method. In some embodiments, the method can comprise sending, from an NFCin a communication network, to an NFPin the communication network, a message comprising a service or data request, the message further comprising a decentralized identifier (DID) number associated with the NFC; in an instance in which the service or data request is a first request for data or services between the NFCand the NFP, receiving, at the NFC, from the NFP, a network function profile request for a network function profile associated with the NFC; and preparing, in response to the network function profile request, a network function consumer profile response including network function properties associated with the NFC.
[0023] In some embodiments, the method can further comprise sending, to the NFP, the network function consumer profile response; and receiving, from the NFP, in response to the network function consumer profile response, an access token associated with the DID number. In some embodiments, the method can further comprise sending a message to the NFP, the message comprising a service or data request, the message further comprising the DID number associated with the apparatus and the access token associated with the network function consumer properties previously provided by the apparatus to the NFP; and, in an instance in which the message includes a valid DID number associated with the apparatus and a valid access token associated with the network function consumer properties previously provided by the apparatus to the NFP, receiving, from the NFP, a service or data response comprising the access token and the service or data requested in the service or data request.
[0024] According to another embodiment, an apparatus can be provided that comprises at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus at least to perform: receiving, from an NFCin a communication network, a message comprising a service or data request, the message furthercomprising a decentralized identifier (DID) number associated with the NFC; determining whether the DID number associated with the NFCis in a distributed ledger (DL) server; in an instance in which the DID number associated with the NFCis in the DL server, determining whether the message received from the NFCincludes a network function consumer profile comprising network function properties associated with the NFC; and, in an instance in which the message received from the NFCdoes not include a network function consumer profile comprising network function properties associated with the NFC, sending a network function consumer profile request to the NFC.
[0025] In some embodiments, the instructions, when executed by the at least one processor, cause the apparatus to further perform at least: receiving, from the NFC, a network function consumer profile response including network function consumer properties associated with the NFC; and integrity verifying the network function consumer properties associated with the NFCusing a public key issued by a verifiable credentials (VC) issuer and a signed hash from a DL entry associated with the NFCand stored at the DL server of the communication system.
[0026] According to another embodiment, a method can be carried out by an apparatus comprising a processor and a memory storing instructions that, when executed by the processor, cause the apparatus to carry out the method. In some embodiments, the method can comprise receiving, at an NFPin a communication network, from an NFCin the communication network, a message comprising a service or data request, the message further comprising a decentralized identifier (DID) number associated with the NFC; determining whether the DID number associated with the NFCis in a distributed ledger (DL) server; in an instance in which the DID number associated with the NFCis in the DL server, determining whether the message received from the NFCincludes a network function consumer profile comprising network function properties associated with the NFC; and, in an instance in which the message received from the NFCdoes not include a network function consumer profile comprising network function properties associated with the NFC, sending a network function consumer profile request from the NFPto the NFC.
[0027] According to another embodiment, an apparatus can be provided that comprises at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus at least to perform: sending a message to an NFPin a communication network, the message comprising a service or data request, the message further comprising a decentralized identifier (DID) number associated with the apparatus and an access token associated with network function consumer properties previously provided by the apparatus to the NFP; and, in an instance in which the message includes an access tokenassociated with network function consumer properties previously provided by the apparatus to the NFP, receiving, from the NFP, a response comprising the access token and the service or data requested in the service or data request.
[0028] According to another embodiment, a method can be carried out by an apparatus comprising a processor and a memory storing instructions that, when executed by the processor, cause the apparatus to carry out the method. In some embodiments, the method can comprise sending, from an NFCin a communication network, to an NFPin the communication network, a message comprising a service or data request, the message further comprising a decentralized identifier (DID) number associated with the NFCand an access token associated with network function consumer properties previously provided by the NFCto the NFP; and, in an instance in which the message includes an access token associated with network function consumer properties previously provided by the NFCto the NFP, receiving, at the NFC, from the NFP, a response comprising the access token and the service or data requested by the NFCin the service or data request.
[0029] According to another embodiment, an apparatus can be provided that comprises at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus at least to perform: receiving, from an NFCin a communication network, a message comprising a service or data request, the message further comprising a decentralized identifier (DID) number associated with the NFCand an access token associated with network function consumer properties previously provided to the apparatus by the NFC; in an instance in which the message includes an access token associated with network function consumer properties previously provided to the apparatus by the NFC, determining that the service or data request is not a first request for data or services between the NFCand the apparatus; in an instance in which the service or data request is not the first request for data or services between the NFCand the apparatus, verifying the access token; and, if the access token is verified, providing a response to the NFC, the response comprising the access token and the service or data requested in the service or data request.
[0030] According to another embodiment, a method can be carried out by an apparatus comprising a processor and a memory storing instructions that, when executed by the processor, cause the apparatus to carry out the method. In some embodiments, the method can comprise receiving, at an NFPin a communication network, from an NFCin the communication network, a message comprising a service or data request, the message further comprising a decentralized identifier (DID) number associated with the NFCand an access token associated with network function consumer properties previously provided to the NFPby the NFC; in aninstance in which the message includes an access token associated with network function consumer properties previously provided to the NFPby the NFC, determining that the service or data request is not a first request for data or services between the NFCand the NFP; in an instance in which the service or data request is not the first request for data or services between the NFCand the NFP, verifying the access token based on a public key associated with the NFCand issued by a verifiable credentials (VC) issuer; and, if the access token is verified, providing a response from the NFPto the NFC, the response comprising the access token and the service or data requested in the service or data request received at the NFP.
[0031] According to another embodiment, an apparatus can be provided that includes means for sending a message to an entity of a communication network, the message comprising property information associated with the apparatus, a public key associated with the apparatus, and a network function unique identifier associated with the apparatus; and means for receiving, from the entity of the communication network, a response to the message, the response comprising a signed hash of the property information, an indication that the property information associated with the apparatus is accepted, and a decentralized identifier (DID) number associated with the apparatus. In some embodiments, the apparatus is configured to include the DID number in requests for service or data in order to expedite integrity verification of the requests for service or data and authentication of the apparatus.
[0032] In some embodiments, the apparatus can further comprise: means for sending, to an NFPof the communication system, a request for service or data, the request for service or data comprising the DID number associated with the apparatus and the property information associated with the apparatus; and means for receiving, in response to the request for service or data, from the NFP, with the service or data requested, an access token associated with the apparatus and / or the DID number. In some embodiments, the apparatus can further comprise: means for sending, to the NFP, a subsequent request for service or data, the subsequent request for service or data comprising the access token associated with the apparatus and / or the DID number; and means for receiving, from the NFP, in response to the subsequent request for service or data, the service or data requested in the subsequent request sent to the NFP.
[0033] According to another embodiment, an apparatus can be provided that includes means for receiving, from an NFCin a communication network, a message comprising property information associated with the NFC, a public key associated with the NFC, and a network function unique identifier associated with the NFC; means for verifying the property information, the public key, and the network function unique identifier associated with the NFC; and means for, in an instance in which the apparatus verifies the property information, thepublic key, and the network function unique identifier associated with the NFC, providing, to the NFC, a response to the message, the response comprising a signed hash of the property information, an indication that the property information associated with the NFCis accepted, and a decentralized identifier (DID) number associated with the NFC. In some embodiments, the apparatus can be configured to carry out integrity verification of subsequent service or data requests from the NFCand authentication of the NFCbased upon the DID number included in the subsequent service or data requests.
[0034] In some embodiments, the apparatus can further comprise means for creating, based at least upon the property information, the public key, and the network function unique identifier associated with the NFC, a distributed ledger (DL) entry associated with the NFC, the DL entry including the DID number for the NFC; and means for including the DL entry in a DL stored at a DL server of the communication system. In some embodiments, the apparatus can further comprise means for causing a distributed ledger (DL) server in the communication system to create a DL entry associated with the NFCbased at least upon the property information, the public key, and the network function unique identifier associated with the NFC; and means for receiving, from the DL server, the DID number for the NFC.
[0035] According to another embodiment, an apparatus can be provided that includes means for sending a message to an NFPin a communication network, the message comprising a service or data request, the message further comprising a decentralized identifier (DID) number associated with the apparatus; means for, in an instance in which the service or data request is a first request for data or services between the apparatus and the NFP, receiving, from the NFP, a network function profile request for a network function profile associated with the apparatus; and means for preparing, in response to the network function profile request, a network function consumer profile response including network function properties associated with the apparatus.
[0036] In some embodiments, the apparatus can further comprise means for sending, to the NFP, the network function consumer profile response; and means for receiving, from the NFP, in response to the network function consumer profile response, an access token associated with the DID number. In some embodiments, the apparatus can further comprise means for sending a message to the NFP, the message comprising a service or data request, the message further comprising the DID number associated with the apparatus and the access token associated with the network function consumer properties previously provided by the apparatus to the NFP; and means for, in an instance in which the message includes a valid DID number associated with the apparatus and a valid access token associated with the network function consumerproperties previously provided by the apparatus to the NFP, receiving, from the NFP, a service or data response comprising the access token and the service or data requested in the service or data request.
[0037] According to another embodiment, an apparatus can be provided that comprises: means for receiving, from an NFCin a communication network, a message comprising a service or data request, the message further comprising a decentralized identifier (DID) number associated with the NFC; means for determining whether the DID number associated with the NFCis in a distributed ledger (DL) server; means for, in an instance in which the DID number associated with the NFCis in the DL server, determining whether the message received from the NFCincludes a network function consumer profile comprising network function properties associated with the NFC; and means for, in an instance in which the message received from the NFCdoes not include a network function consumer profile comprising network function properties associated with the NFC, sending a network function consumer profile request to the NFc.
[0038] In some embodiments, the apparatus can further comprise: means for receiving, from the NFC, a network function consumer profile response including network function consumer properties associated with the NFC; and means for integrity verifying the network function consumer properties associated with the NFCusing a public key issued by a verifiable credentials (VC) issuer and a signed hash from a DL entry associated with the NFCand stored at the DL server of the communication system.
[0039] According to another embodiment, an apparatus can be provided that comprises: means for sending a message to an NFPin a communication network, the message comprising a service or data request, the message further comprising a decentralized identifier (DID) number associated with the apparatus and an access token associated with network function consumer properties previously provided by the apparatus to the NFP; and means for, in an instance in which the message includes an access token associated with network function consumer properties previously provided by the apparatus to the NFP, receiving, from the NFP, a response comprising the access token and the service or data requested in the service or data request.
[0040] According to some embodiments, an apparatus can be provided that comprises: means for receiving, from an NFCin a communication network, a message comprising a service or data request, the message further comprising a decentralized identifier (DID) number associated with the NFCand an access token associated with network function consumer properties previously provided to the apparatus by the NFC; means for, in an instance in whichthe message includes an access token associated with network function consumer properties previously provided to the apparatus by the NFC, determining that the service or data request is not a first request for data or services between the NFc and the apparatus; means for, in an instance in which the service or data request is not the first request for data or services between the NFCand the apparatus, verifying the access token; and means for, if the access token is verified, providing a response to the NFC, the response comprising the access token and the service or data requested in the service or data request.Brief Description of the Drawings
[0041] Having thus described certain example embodiments of the present disclosure in general terms, reference will hereinafter be made to the accompanying drawings, which are not necessarily drawn to scale, and wherein:
[0042] FIG. 1 depicts an example system environment in which implementations in accordance with an example embodiment of the present disclosure may be performed;
[0043] FIG. 2 is a block diagram of a computing device configured in accordance with an example embodiment of the present disclosure;
[0044] FIG. 3 illustrates an example a communication system in accordance with an example embodiment of the present disclosure;
[0045] FIG. 4 illustrates an example service based architecture for a communication system in accordance with an example embodiment of the present disclosure;
[0046] FIG. 5 illustrates an example a communication system in accordance with an example embodiment of the present disclosure;
[0047] FIG. 6 is a block diagram of an example signaling and authentication approach in accordance with an example embodiment of the present disclosure;
[0048] FIG. 7 is a block diagram of an example signaling and authentication approach in accordance with an example embodiment of the present disclosure;
[0049] FIG. 8 illustrates an example workflow of various components of a communication system in accordance with an example embodiment;
[0050] FIG. 9 illustrates an example workflow of various components of a communication system in accordance with an example embodiment;
[0051] FIG. 10 illustrates an example workflow of various components of a communication system in accordance with an example embodiment;
[0052] FIG. 11 illustrates an example workflow of various components of a communication system in accordance with an example embodiment;
[0053] FIG. 12 illustrates an example workflow of various components of a communication system in accordance with an example embodiment; and
[0054] FIG. 13 illustrates an example workflow of various components of a communication system in accordance with an example embodiment.Detailed Description
[0055] Select embodiments of solutions, systems, networks, apparatuses, devices, components, methods, and computer program products are described in the present disclosure, with reference to some example embodiments. It is to be understood that these embodiments are described only for the purpose of illustration and help those skilled in the art to understand and implement the present disclosure, without suggesting any limitation as to the scope of the disclosure. The disclosure described herein can be implemented in various manners other than the ones described below.
[0056] In the following description and claims, unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skills in the art to which this disclosure belongs.
[0057] References in the present disclosure to “one embodiment,” “an embodiment,” “an example embodiment,” and the like indicate that the embodiment described may include a particular feature, structure, or characteristic, but it is not necessary that every embodiment includes the particular feature, structure, or characteristic. Moreover, such phrases are not necessarily referring to the same embodiment. Further, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is submitted that it is within the knowledge of one skilled in the art to affect such feature, structure, or characteristic in connection with other embodiments whether or not explicitly described.
[0058] It shall be understood that although the terms “first” and “second” etc. may be used herein to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another. For example, a first element could be termed a second element, and similarly, a second element could be termed a first element, without departing from the scope of example embodiments. As used herein, the term “and / or” includes any and all combinations of one or more of the listed terms.
[0059] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of example embodiments. As used herein, the singular forms “a”, “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms “comprises”,“comprising”, “has”, “having”, “includes” and / or “including”, when used herein, specify the presence of stated features, elements, and / or components etc., but do not preclude the presence or addition of one or more other features, elements, components and / or combinations thereof. As used herein, “at least one of the following: ” and “at least one of ” and similar wording, where the list of two or more elements are joined by “and” or “or”, mean at least any one of the elements, or at least any two or more of the elements, or at least all the elements.
[0060] As used in this application, the term “circuitry” may refer to one or more or all of the following:
[0061] (a) hardware-only circuit implementations (such as implementations in only analog and / or digital circuitry) and
[0062] (b) combinations of hardware circuits and software, such as (as applicable):
[0063] (i) a combination of analog and / or digital hardware circuit(s) with software / firmware and
[0064] (ii) any portions of hardware processor(s) with software (including digital signal processor(s)), software, and memory(ies) that work together to cause an apparatus, such as a mobile phone or server, to perform various functions) and
[0065] (c) hardware circuit(s) and or processor(s), such as a microprocessor(s) or a portion of a microprocessor(s), that requires software (e.g., firmware) for operation, but the software may not be present when it is not needed for operation.
[0066] This definition of circuitry applies to all uses of this term in this application, including in any claims. As a further example, as used in this application, the term circuitry also covers an implementation of merely a hardware circuit or processor (or multiple processors) or portion of a hardware circuit or processor and its (or their) accompanying software and / or firmware. The term circuitry also covers, for example and if applicable to the particular claim element, a baseband integrated circuit or processor integrated circuit for a mobile device or a similar integrated circuit in server, a cellular network device, or other computing or network device.
[0067] As used herein, the term “communication network” refers to a network following any suitable communication standards, such as Long Term Evolution (LTE), LTE-Advanced (LTE-A), Wideband Code Division Multiple Access (WCDMA), High-Speed Packet Access (HSPA), Narrow Band Internet of Things (NB-IoT), Code Division Multiple Access (CDMA), Frequency Division Multiple Access (FDMA), Time Division Multiple Access (TDMA), Frequency Division Duplex (FDD), Time Division Duplex (TDD), Multiple-Input Multiple-Output (MIMO), Orthogonal Frequency Division Multiple (OFDM), Discrete Fourier Transform spread OFDM (DFT-s-OFDM) and / or any other technologies currently known or to be developed in the future.. Furthermore, the communications between a terminal device and a network device in the communication network may be performed according to any suitable generation communication protocols, including, but not limited to, the first generation (1G), the second generation (2G), 2.5G, 2.75G, the third generation (3G), the fourth generation (4G), 4.5G, current and / or future fifth generation (5G) communication protocols and systems, future sixth generation (6G) communication protocols and systems, and / or any other protocols either currently known or to be developed in the future. Embodiments of the present disclosure may be applied in various communication systems. Given the rapid development in communications, there will of course also be future type communication technologies and systems with which the present disclosure may be embodied. It should not be seen as limiting the scope of the present disclosure to only the aforementioned system.
[0068] As used herein, the term “network device” refers to a node in a communication network via which a terminal device accesses the network and receives services therefrom. The network device may refer to a base station (BS) or an access point (AP), for example, a node B (NodeB or NB), an evolved NodeB (eNodeB or eNB), a NR NB (also referred to as a gNB), a Remote Radio Unit (RRU), a radio header (RH), a remote radio head (RRH), a relay, a low power node such as a femto, a pico, and so forth, depending on the applied terminology and technology.
[0069] The term “terminal device” refers to any end device that may be capable of wireless communication. By way of example rather than limitation, a terminal device may also be referred to as a communication device, user equipment (UE), a Subscriber Station (SS), a Portable Subscriber Station, a Mobile Station (MS), or an Access Terminal (AT). The terminal device may include, but not limited to, a mobile phone, a cellular phone, a smart phone, voice over IP (VoIP) phones, wireless local loop phones, a tablet, a wearable terminal device, a personal digital assistant (PDA), portable computers, desktop computer, image capture terminal devices such as digital cameras, gaming terminal devices, music storage and playback appliances, vehicle-mounted wireless terminal devices, wireless endpoints, mobile stations, laptop-embedded equipment (LEE), laptop-mounted equipment (LME), universal serial bus (USB) dongles, smart devices, wireless customer-premises equipment (CPE), an Internet of Things (loT) device, a watch or other wearable, a head-mounted display (HMD), a vehicle, a drone, a medical device and applications (e.g., remote surgery), an industrial device and applications (e.g., a robot and / or other wireless devices operating in an industrial and / or anautomated processing chain contexts), a consumer electronics device, a device operating on commercial and / or industrial wireless networks, and the like. In the following description, the terms “terminal device”, “communication device”, “terminal”, “user equipment” and “UE” may be used interchangeably.
[0070] As used herein, the terms “data,” “content,” “information,” and similar terms may be used interchangeably to refer to data capable of being transmitted, received and / or stored in accordance with embodiments of the present disclosure. Thus, use of any such terms should not be taken to limit the spirit and scope of embodiments of the present disclosure.
[0071] Third generation partnership project (3GPP) technologies are current and next generation radio systems, protocols, and network architectures that can deliver extreme broadband and ultra-robust, and low latency connectivity. Fifth generation (5G) protocols and networks are configured to virtualize various network elements and functions that were previously hardware-based, among other changes. Contemplated sixth generation (6G) protocols and networks will improve a variety of telecommunication services offered to the end users, distribute various functions away from centralized and / or singular functions or elements of the network, and will help to support massive broadband that delivers gigabytes of bandwidth per second on demand for both uplink and downlink transmissions. Next generation systems which utilize the 6G architecture will further utilize virtualized radio access network (RAN) functions and virtualized core network functions.
[0072] Embodiments will be illustrated herein in conjunction with example communication systems and associated techniques for providing data transport in communication systems. It should be understood, however, that the scope of the claims is not limited to particular types of communication systems and / or processes disclosed. Embodiments can be implemented in a wide variety of other types of communication systems, using alternative processes and operations. For example, although illustrated in the context of wireless cellular systems utilizing 3rd Generation Partnership Project (3GPP) system elements such as a 3GPP next generation system (6G), the disclosed embodiments can be adapted in a straightforward manner to a variety of other types of communication systems. While the present disclosure may be described in conjunction with a 6G communications system, the disclosure also applies to and comprises other networks and network technologies, such as 5G, 4G, LTE, 3G, etc. without limitation. To provide an explanation of the system architecture and distributed security differences anticipated between 5G and 6G networks and communication technologies, an explanation follows of example 5G networks and system architectures, followed by an explanation of example 6G networks and system architectures.
[0073] FIG. 1 depicts an example communication system environment (i.e., a system environment 100) in which implementations in accordance with an example embodiment of the present disclosure may be performed. In some embodiments, the system 100 can be a 5G network. The depiction of system environment 100 in FIG. 1 is not intended to limit or otherwise confine the embodiments described and contemplated herein to any particular configuration of elements or systems, nor is it intended to exclude any alternative configurations or systems for the set of configurations and systems that can be used in connection with embodiments of the present disclosure. Rather, FIG. 1, and the system environment 100 disclosed therein is merely presented to provide an example basis and context for the facilitation of some of the features, aspects, and uses of the methods, apparatuses, and computer program products disclosed and contemplated herein. It will be understood that while many of the aspects and components presented in FIG. 1 are shown as discrete, separate elements, other configurations may be used in connection with the methods, apparatuses, and computer programs described herein, including configurations that combine, omit, and / or add aspects and / or components.
[0074] As shown in FIG. 1 , the system environment includes one or more user equipment (UE) 102 configured to communicate wirelessly, such as via an access network, with a network 106. Although the user equipment may be configured in a variety of different manners, the user equipment may be embodied as a mobile terminal, such as a portable digital assistant (PDA), mobile phone, smartphone, pager, mobile television, gaming device, laptop computer, camera, tablet computer, communicator, pad, headset, touch surface, video recorder, audio / video player, radio, electronic book, positioning device (e.g., global positioning system (GPS) device), or any combination of the aforementioned, and other types of voice and text and multi-modal communications systems. System environment 100, as depicted in FIG. 1, also includes one or more access points 104a and 104b, such as base stations, including but not limited to node Bs, evolved Node Bs (eNB), or the like. A cellular access point, such as a base station, may define and service one or more cells. The access points may, in turn, be in communication with a network 106, such as a core network via a gateway, such that the access points establish cellular radio access networks by which the user equipment 102 may communicate with the network. The system environment 100 of FIG. 1 may include a plurality of different cellular radio access cells and / or networks or parts of such networks including, for example, a 6G radio access network, a 5G radio access network, an LTE (Long-Term Evolution) radio access network, a UMTS (universal mobile telecommunications system) radio access network, etc. In some example implementations, equipment and other infrastructureassociated with multiple different cellular radio access networks may be located at or near structures and / or other equipment associated with a particular access point, such as access point 104a and 104b.
[0075] In some implementations of system environment 100, the cellular radio access networks serviced by access points 104a, 104b, and any other access points in a given area are identical, in the sense that as user equipment 102 moves from an area serviced by access point 104a to an area serviced by access point 104b. The user equipment 102 is able to access the network 106 via a radio access network provided across access points. Although not shown, the system may also include a controller associated with one or more of the cellular access points, such as, base stations, for example, so as to facilitate operation of the access points and management of the user equipment 102 in communication therewith. As shown in FIG. 1, a system may also include one or more wireless local area networks (WLANs), each of which may be serviced by a WLAN access point 108 configured to establish wireless communications with the user equipment. As such, the user equipment may communicate with the network via a WLAN access point as shown in solid lines in FIG. 1 , or, alternatively, via a cellular access point as shown in dashed lines. The radio access networks as well as the core networks may consist of additional network elements as routers, switches, servers, gateways, and / or controllers.
[0076] In this regard, the implementation and / or allocation of a network slice within a network environment can be accomplished by an apparatus 200 as depicted in FIG. 2. The apparatus may be embodied by and / or incorporated into one or more UEs, such as user equipment 102, or any of the other devices discussed with respect to FIG. 1, such as access points 104a and / or 104b, one or more of WLAN access points 108, and / or devices that may be incorporated or otherwise associated with system environment 100. Alternatively, the apparatus 200 may be embodied by another device, external to such devices. For example, the apparatus may be embodied by a computing device, such as a personal computer, a computer workstation, a server or the like, or by any of various mobile computing devices, such as a mobile terminal, including but not limited to a smartphone, a tablet computer, or the like, for example.
[0077] In some embodiments, the system environment 100 may include one or more of the following network functions (NF): Authentication Server Function (AUSF), Access and Mobility Management Function (AMF), Data Network (DN), e.g. operator services, Internet access or 3rd party services, Unstructured Data Storage Function (UDSF), Network Exposure Function (NEF), Network Repository Function (NRF), Network Slice Selection Function(NSSF), Policy Control Function (PCF), Session Management Function (SMF), Unified Data Management (UDM), Unified Data Repository (UDR), User Plane Function (UPF), UE radio Capability Management Function (UCMF), Application Function (AF), User Equipment (UE), Next Generation-Radio Access Network (NG-RAN), 5G-Equipment Identity Register (5G- EIR), Network Data Analytics Function (NWDAF), and Charging Function (CHF). The system environment may further comprise the following network entities: Service Communication Proxy (SCP) and Security Edge Protection Proxy (SEPP).
[0078] Regardless of the manner in which the apparatus 200 is embodied, the apparatus of an example embodiment is configured to include or otherwise be in communication with a processor 202 and a memory device 204 and optionally the user interface 206 and / or a communication interface 208. In some embodiments, the processor (and / or co-processors or any other processing circuitry assisting or otherwise associated with the processor) may be in communication with the memory device via a bus for passing information among components of the apparatus. The memory device may be non-transitory and may include, for example, one or more volatile and / or non-volatile memories. In other words, for example, the memory device may be an electronic storage device (e.g., a computer readable storage medium) comprising gates configured to store data (e.g., bits) that may be retrievable by a machine (e.g., a computing device like the processor). The memory device may be configured to store information, data, content, applications, instructions, or the like for enabling the apparatus to carry out various functions in accordance with an example embodiment of the present disclosure. For example, the memory device could be configured to buffer input data for processing by the processor. Additionally or alternatively, the memory device could be configured to store instructions for execution by the processor.
[0079] As described above, the apparatus 200 may be embodied by a computing device. However, in some embodiments, the apparatus may be embodied as a chip or chip set. In other words, the apparatus may comprise one or more physical packages (e.g., chips) including materials, components and / or wires on a structural assembly (e.g., a baseboard). The structural assembly may provide physical strength, conservation of size, and / or limitation of electrical interaction for component circuitry included thereon. The apparatus may therefore, in some cases, be configured to implement an embodiment of the present disclosure on a single chip or as a single “system on a chip.” As such, in some cases, a chip or chipset may constitute means for performing one or more operations for providing the functionalities described herein.
[0080] The processor 202 may be embodied in a number of different ways. For example, the processor may be embodied as one or more of various hardware processing means includingprocessing circuitry, such as a coprocessor, a microprocessor, a controller, a digital signal processor (DSP), a processing element with or without an accompanying DSP, or various other processing circuitry including integrated circuits such as, for example, an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), a microcontroller unit (MCU), a hardware accelerator, a special-purpose computer chip, or the like. As such, in some embodiments, the processor may include one or more processing cores configured to perform independently. A multi-core processor may enable multiprocessing within a single physical package. Additionally or alternatively, the processor may include one or more processors configured in tandem via the bus to enable independent execution of instructions, pipelining and / or multithreading.
[0081] In an example embodiment, the processor 202 may be configured to execute instructions stored in the memory device 204 or otherwise accessible to the processor. Alternatively or additionally, the processor may be configured to execute hard coded functionality. As such, whether configured by hardware or software methods, or by a combination thereof, the processor may represent an entity (e.g., physically embodied in circuitry) capable of performing operations according to an embodiment of the present disclosure while configured accordingly. Thus, for example, when the processor is embodied as an ASIC, FPGA or the like, the processor may be specifically configured hardware for conducting the operations described herein. Alternatively, as another example, when the processor is embodied as an executor of software instructions, the instructions may specifically configure the processor to perform the algorithms and / or operations described herein when the instructions are executed. However, in some cases, the processor may be a processor of a specific device (e.g., a pass-through display or a mobile terminal) configured to employ an embodiment of the present disclosure by further configuration of the processor by instructions for performing the algorithms and / or operations described herein. The processor may include, among other things, a clock, an arithmetic logic unit (ALU) and logic gates configured to support operation of the processor.
[0082] The apparatus 200 may optionally include the communication interface 208. The communication interface 208 may be or comprise any means, such as a device or circuitry, embodied in either hardware or a combination of hardware and software, that is configured to receive and / or transmit data from / to a network and / or any other device or module in communication with the apparatus. In this regard, the communication interface may include, for example, an antenna (or multiple antennas) and supporting hardware and / or software for enabling communications with a wireless communication network. Additionally oralternatively, the communication interface may include the circuitry for interacting with the antenna(s) to cause transmission of signals via the antenna(s) or to handle receipt of signals received via the antenna(s). In some environments, the communication interface may alternatively or also support wired communication. As such, for example, the communication interface may include a communication modem and / or other hardware / software for supporting communication via cable, digital subscriber line (DSL), universal serial bus (USB) or other mechanisms.
[0083] Referring now to FIG. 3, communication networks, such as 5G networks, typically use a variety of mechanisms to authorize network services. The 5G system architecture consists of several key elements and functions that work together to provide advanced capabilities, such as faster speeds, lower latency, and increased connection reliability. A 5G network can include a access network (AN) or radio access network (RAN) that is responsible for managing radio access in the network. The AN / RAN can consist of base stations and antennas that provide wireless connectivity for the UE to other elements or functions of the 5G network. The 5G network can also include a core network (CN) that consists of several key elements or functions, including a user data management (UDM) function, an authentication server function (AUSF), a network slice selection function (NSSF), an access and mobility management function (AMF), a session management function (SMF), a policy control function (PCF), an application function (AF), a user plane function (UPF), and / or a data network (DN), among other elements or functions. Some or all of these elements or functions can be virtualized, stateless, hosted on virtual machines or servers, operating-system-level virtualized, containerized, hosted in multi-user spaces, can be application virtualized, network virtualized, storage virtualized, server virtualized, or desktop virtualized, can be hosted / stored on / at a cloud computing environment, and / or the like.
[0084] The UDM is typically responsible for managing the user profile and authentication information of the UE. The AUSF is typically responsible for providing authentication and authorization for the UE to access the network. The NSSF is typically responsible for selecting the appropriate network slice for the UE based on various criteria such as the service requirements, location, and network conditions. The AMF is typically responsible for managing the mobility of the UE within the network and for controlling access to the network. The SMF is typically responsible for managing the session and data flow between the UE and the core network. The PCF is typically responsible for enforcing the network policies for different services and applications. The AF is typically responsible for providing services and applications to the UE. The UPF is typically responsible for forwarding and routing the datapackets between the UE and the core network. DN may refer to external networks, such as the internet, which are used for data communication between the UE and the CN.
[0085] The NSSF can be operable for carrying out network slice authentication and authorization (NSAA) processes, which can be used in 5G for authorizing NFcs and NFps to receive services or data, and / or authorizes NFcs and NFps for access to resources of the 5G network. The NSAA process can include one or more authentication steps, one or more authorization steps, one or more policy enforcement steps, and one or more accounting steps. During authentication, the NFCor NFPprovides authentication credentials to the network, such as a username and password or digital certificate. The network verifies the credentials and grants access to the authorized entity. Once authenticated, the NFCor NFPrequests access to a specific network slice or service. The network verifies that the entity is authorized to access that slice or service based on its credentials and predefined policies. During policy enforcement, the network applies policies to determine the level of access that the NFCor NFPhas to the requested network slice or service. This can include determining Quality of Service (QoS) parameters, such as bandwidth and latency, that are allocated to the entity. During accounting, the network can track the usage of the network slice or service by the NFCor NFPand enforces any usage limits or billing policies.
[0086] The RAN can provides high-speed wireless connectivity to the UE, while the core network manages the authentication, mobility, and data flow of the UE within the network. The NSSF selects the appropriate network slice based on the user requirements, and the AF provides various services and applications to the UE. The UPF routes the data packets between the UE and the core network, and the DN provides external connectivity to the network.
[0087] The UE can refer to any end user device, such as smartphones, tablets, laptops, internet-of-things (loT) devices, vehicle-to-everything (V2X) devices, and / or the like, that are used by customers / subscribers to access 5G networks.
[0088] Some of the key processes involved in network service authorization in 5G include an Authentication and Authorization, Access Control, QoS Control, Network Slicing, Service Level Agreements (SLAs), and the like.
[0089] The first step in network service authorization is the authentication and authorization of the user or device that is attempting to access the network. In 5G, this is typically done using the Extensible Authentication Protocol (EAP) and the Authentication and Key Agreement (AKA) protocol, which are used to verify the identity of the user or device and to generate shared encryption keys.
[0090] Once a user or device has been authenticated and authorized, access control mechanisms are used to determine what network services they are allowed to access. In 5G, access control is typically done using the Policy and Charging Rules Function (PCRF), which defines the policies that govern network access and service usage.
[0091] In addition to access control, 5G networks also use QoS control mechanisms to ensure that network services are delivered with the appropriate level of performance. QoS control involves setting parameters such as network bandwidth, latency, and packet loss rates to ensure that network services are delivered with the appropriate level of reliability and performance.
[0092] Another key process in 5G network service authorization is network slicing. Network slicing allows network operators to partition the network into multiple virtual networks, each with its own set of resources and QoS parameters. This enables different types of network services to be delivered with the appropriate level of performance, while also allowing network operators to optimize network resource usage.
[0093] 5G networks use service level agreements (SLAs) to define the terms and conditions of network service delivery. SLAs specify the QoS parameters, service availability, and other performance metrics that must be met by the network operator, and provide a framework for measuring and reporting on network performance.
[0094] Referring now to FIG. 4, in some 5G networks, the SMF can be a primary element in a service-based architecture (SBA) for 5G technologies. The SMF can be responsible for interacting with the decoupled data plane, creating updating and removing Protocol Data Unit (PDU) sessions, and managing session context with the UPF. The UE and access nodes (e.g., eNB, gNB, etc.) may employ a Next Generation Application Protocol (NGAP) to carry Non Access Stratum (NAS) messages across the N1 or N2 reference interfaces in order to request a new session. The AMF can receive requests and often handles anything to do with connection or mobility management while forwarding session management requirements over the Ni l interface to the SMF. The AMF can determine which SMF is best suited to handle the connection request by querying the NRF. That interface and the Nil interface between the AMF and the specific SMF assigned by the NRF, can use the Service Based Interface (SBI) message bus, to which most or all Service-Base Application elements are connected. Messages received over the Ni l interface often represent a trigger to add, modify, or delete a PDU session across the user plane. The SMF can send messages to the UPF over the N4 reference interface using the Packet Forwarding Control Protocol (PFCP).
[0095] During session establishment or modification, the SMF also interacts with the PCF over the N7 interface and the subscriber profile information stored within the UDM function (N10), which assumes the role previously performed by the HSS. The PCF can provide the foundation of a policy framework which, along with the more typical QoS and charging rules, includes Network Slice selection, which is regulated by the NSSF. Decoupling other control plane functions from the user plane, while (together with the AMF) assuming the some of the functionality previously undertaken by the Mobile Management Entity (MME), the SMF performs the role of Dynamic Host Configuration Protocol (DHCP) server and IP Address Management (IP AM) system.
[0096] Together with the UPF, the SMF maintains a record of PDU session state using, e.g., a 24-bit PDU Session ID. The SMF sets configuration parameters in the UPF that define traffic steering parameters and ensure the appropriate routing of packets while guaranteeing the delivery of incoming packets, though a Downlink data notification. In 4G Evolved Packet Core (EPC) architectures, this is a serving gateway (SGW) to MME messages. The SMF is responsible for checking whether the UE requests are compliant with the user subscription and for connectivity charging, which is achieved by interacting with a Charging Function (CHF), as defined in 3GPP TS 32.255, the entire disclosure of which is hereby incorporated herein by reference.
[0097] In some embodiments, the AF can be a Network Function Consumer (or Network Function Service Consumer, NFC). In some embodiments, the AF can be a network data analytics function (NWDAF). In some embodiments, the AMF can be a Network Function Producer (or Network Function Service Producer, NFP). In the context of service, resource, and / or data provisioning between the NFPand NFC(e.g., between the AMF and AF), the AMF would typically send an OAuth token request to the NRF, and the NRF responds with an OAuth token after validating the profiles of AF and AMF. AMF validates the OAuth token before providing the services to AF. In some embodiments, one or more of the AF, AMF, NRF, or other elements or functions of the network can be similar to, comprise, or be embodied by the apparatus 200.
[0098] There can be NFs, such as Serving-Call Session Control Function (S-CSCF), which do not provide any service, but which can request the services of other NFs. Such NFs are called pure NF consumers. Such NFs often do not need to register their profile with the NRF. If they (pure NF consumers) want to get any service of the AMF, they send an OAuth token request to NRF and NRF provides OAuth token in response after validating the pure NF consumer profile. Generally, the AMF validates the OAuth token provided by AF beforeproviding the services. NF Profile contains static or fixed parameters such as Nflnstanceld, NetworkFunctionType etc., and dynamic parameters such as NFload which varies at runtime.
[0099] Since not all AF(s) (for example, S-CSCF) register their NF profiles at the NRF, such AF(s) may request an access token to be able to request the services of other network function service providers. One problem that can arise is how these kinds of AFs can be authorized by the NRF. For example, without an NF profile of an AF, the NRF cannot authorizes some parameters in the access token, and also cannot validate whether the parameters of the discovery request really belong to the AF, therefore, the NRF cannot validate the AF to get access to AMF resources.
[0100] In addition, it is not a mandatory requirement that all information elements (IES) defined in the SBA has been filled in with information presented in the Transport Layer Security (TLS) certificate. For example, it is merely suggested that the TLS certificate include information such as NF Type. Other kinds of information, such as slice information, set ID, vendor ID, etc., are not contained in the TLS certificate profile at all. So, there may be situations when certificates such as a TLS certificate are available for a NF consumer / provider, but information may not be sufficient for NRF to validate the NF consumer / provider. Another problem that can arise regards how the NRF can validate a AF / AMF request in all situations is also to be solved. Also, it may not always be possible to keep on adding NF static information into the TLS profile. Therefore, NRF may not be able to authorize the NF Profile registration request . For example, the NF profile may contain lots of parameters, such as slice, set ID, vendor ID, etc., whether these parameters are really belonging to the NF or not.
[0101] Another problem with the 5G SBA described above and illustrated in FIGs. 3 and 4 is that the OAuth is not typically mandatory to implement in the 5G network. In such cases, there is no mechanism at the NFP(e.g., AMF) to authorize the NFC(e.g., AF, NDWAF, etc.). The AF / NWDAF sends a service request to the AMF without OAuth token, then the AMF cannot validate the AF / NWDAF claims in the service request, for example if the AF / NWDAF claims that it is a part of slice X without OAuth token, the AMF cannot verify whether the AF / NWDAF actually belongs to slice X.
[0102] While these system architectural and protocol problems are evident within the 5G system, it is expected that these problems would be further exacerbated within a 6G system / network. As such, described herein are 6G networks may be more diverse than their predecessors and support ubiquitous instant communications, pervasive intelligence and the loT applications, flexible decentralized authentication and service authorization practices, local spectrum licensing, local spectrum sharing, increased infrastructure sharing, and intelligentautomated management underpinned by mobile edge computing, artificial intelligence (Al), short-packet communication, distributed ledger technologies, and blockchain technologies.
[0103] Referring now to FIG. 5, it is contemplated that 6G networks will be expected to provide a novel radio and access architecture for both communications and sensing purposes, artificial intelligence (Al) optimized wide area networks and data centers, and dynamic orchestration of personalized service provisioning. 6G system architecture is contemplated that include network programmability, deployment flexibility, simplicity and efficiency, security, robustness, reliability, and automation. 6G networks are expected to be agnostic to the type of cloud platform used, and will focus on shared data and requirements for statelessness and virtualization of network nodes, network entities, and network functions. Structurally, the 6G network architecture may include a heterogenous cloud environment (het-cloud) that runs applications in a distributed manner throughout the network, such as on-prem, far edge, edge, and core. Different hardware / software stacks can be implemented and clouds can be private, public, or hybrid. The virtualization and distribution of service provisioning across the 6G network is expected to require more distribution of network function service consumer authentication and authorization processes.
[0104] In 6G, since the network will be much more distributed, and since security efforts are being made to strive for zero trust and defense-in-depth approaches to be implemented, more distributed NF authentication and authorization processes will be needed to correct several security flaws in 5G and anticipate and prevent such security flaws in 6G.
[0105] Currently, 5G technologies and standard procedures currently have security flaws, such as in the 5G Core SBA security procedures. For example, 5G networks and procedures currently consider the NRF to be the most trusted entity, and all NFs register their profiles with the NRF. The NRF then verifies if the NF (e.g., NF service consumer, or NFC) is authorized to receive a service or not, such as based on profile information registered by the NF (e.g., NF service producer, or NFP) at the NRF. Thus, if the NRF is compromised, all the NFs in the same network (e.g., public land mobile network (PLMN) or visited PLMN (VPLMN)) could improperly access services they are not authorized to access. The fact that complete trust of the 5G Core network is relying on a single entity (i.e., NRF) goes against the principles of zero trust and makes the NRF a single point of failure for the 5G network architecture with regard to NF authorization and service provisioning.
[0106] Also, in 5G, once the NRF generates the access token with the corresponding claims, during the access token verification procedure, the NFPis only able to verify very limited information about the NFC. This is mostly because the NRF, when generating the accesstoken claims, does not include all the relevant information about the NFC. Currently, according to 3GPP TS 33.501 for example, only the NF Service Consumer Instance ID is included in the access token claims. Therefore, under 5G, the NFPhas limited verification ability with respect to the NFC.
[0107] Further, since it is actually the NFPin 5G that provides the services, and also the NFPthat knows best which NFCis authorized to receive those services, the NFPshould verify the NFCwhen the NFCis sending the service request along with the access token. However, under 5G, even if the NFCprovides an access token with a service request, the NFPmust provide this same information with an authorization request to the NRF, await an authorization response from the NRF, and only then can the NFPauthorize the NFCto receive the requested services. This creates other opportunities in the 5G architecture and procedures for security threats and attacks, such as by way of NRF spoofing, compromising the NRF, or the like. Under 6G, which is envisioned to be much more distributed, such as with regard to the security and service provisioning authorization procedures, distributing the NFCauthorization process responsibilities from the NRF to a plurality of NFPreduces the risk of the NRF being a single point of failure, reduces the single entity computing / signaling complexity required for authorization of NFC, and may mean that security threats or attacks against any one NFPcompromises only a small portion of system services and further may mean that only a small subset of the NFCin the network might improperly receive services they are not authorized to receive.
[0108] Additionally, in 5G systems, authorization for NFCis currently derived by policy(ies) of the PLMN / VPLMN. If an NFPwants to update its policy and wants to authorize an NFCbased on other criteria, then the entire 5G standard would need to be changed to allow NFPto change the associated NFPprofile and to allow the NFPto update criteria for NFCauthorization at the NRF. For example, if NFPwants to authorize an NFCbased on an NFCSlice Id, then the NFPwould need to update in the NRF the Allowed Slice List. However, this would require that the NFPhave access to and the ability to change the Allowed Slice List Parameter at the NRF. Currently, there is no provision or process in the 5G standards or 5G Core Network architecture for such NFp-to-NRF change to the criteria used by NRF for authorizing NFC. However, a system and standard that requires a wholesale change to the standard to allow for changes to NFCauthorization criteria is not an optimized approach because it requires a change request be filed to the 3GPP standards body, it requires that substantial work be carried out by one or more working groups to review and approve the change request, and then it requires a non-trivial change to the standards as well as any system, entity, hardware, product, or deviceusing the standard; not to mention that it would take significant time to implement any new policy in a PLMN or VPLMN.
[0109] In some embodiments, a Blockchain Ledger (BL) can be created with NF information and accessible to all NFs in an operator network. Each NF profile can be split into two sections, e.g., static and dynamic sections. The static part of the profile may contain a set of parameters (e.g., nflnstancelD, nflype, slice Ids, vendor id, Set id, etc) which are fixed and not changed dynamically. The dynamic part of the profile can contain other parameters (e.g, load) that vary over time. Each operator / O&M can configure the static profiles (set of parameters that don’t change) of all the NFs during their creation in the BL. The NRF may validate the NF parameters in NF profile during an access token request and profile registration by fetching the static profile from the BL. However, such an approach still uses an NRF-based authorization approach in which the NRF is verifying the contents of all NF Profiles, which leads to the various problems and issues described elsewhere herein, such as making the NRF a single point of failure and a singular, centralized point of attack for those wanting to compromise network traffic, service provisioning, and / or the NF authentication / authorization process(es).
[0110] Conversely, as described herein, various approaches are described in which the NRF is not a centralized point of authentication / authorization for NFs with regard to service provisioning. In some embodiments, the contents of the NF profile may be verified by the NRF, and therefore which avoids various of the security and other issues described herein with regard to the use of a centralized NRF or other network function / element for NF authentication / authorization and NF profile verification. For example, in some embodiments, a completely new framework and system architecture for NF / NF Profile authentication / authorization is described that addresses various of the current security vulnerabilities of the 5G Core. Embodiments of the described solution may leverage the properties of Distributed Ledger (DL) technologies to enable increased transparency in the system, enable zero trust and defense-in-depth approaches, and reduce unnecessary signaling between NFs, NFC, and other elements / functions of the network.
[0111] As used herein, the terms “usecase” or “use case” refer to example scenarios in which an NF Service Consumer (NFC), such as an NWDAF, is requesting to collect UE mobility data from an NF Service Producer (NFP), such as an AMF. However, other example scenarios are contemplated in which embodiments of the described approach and architecture can be used.
[0112] The present disclosure provides solutions for these and other problems identified by the inventors. Principle embodiments of the present disclosure will be described in detail below with reference to the accompanying drawings.
[0113] Described herein are systems, methods, apparatuses, and computer program products for a new framework and approach to authorization and authentication of network functions and service provisioning in a network. In certain embodiments, the disclosed approach uses properties of distributed ledger (DL) technologies to enable transparency in the system, distribute authentication and authorization processes across the network, and advance the principles of zero trust and defense-in-depth.
[0114] Described below are various non-limiting components in the described solution and architecture.
[0115] As used herein, the term “DID Number” may refer to an identifier that ties together NF profile information, NFs, service requests, and other elements or components. For example, the DID number can be used to fetch a particular entry or document from a server, e.g., from a distributed ledger (DL) stored at a particular server (e.g., DL Server).
[0116] As used herein the terms “DL Entry” and “DID Entry” may refer to an entry in the DL. The DL Entry or DID Entry can comprise a DID identifier, a public key, a signed hash, and / or other relevant information needed during the service request / provisioning processes or NF authentication / authorization processes, such that any other element can verify the integrity of the components of a DID file or the like based on the DL Entry or DID Entry.
[0117] As used herein, the terms “NF Properties” and “6G NF Properties” may refer to properties of an NF that can be used to authorize specific service / data requests. In some embodiments, an active entity may refer to a DID Entry or NF Properties therein to identify necessary information about properties of the associated NF that can be used to authorize specific service / data requests by / for that NF. In some embodiments, reference to the DID Entry / NF Properties therein can be made using the DID Number. In some embodiments, the properties of NF(s) that can be used to authorize the NF for specific service / data requests can comprise information such as an NF Type, an NF Unique ID, the network slice to which the NF belongs, PLMN information, geographical information about the NF or network, bearer information, information about the platform in / on which the NF is deployed, NF vendor information, and / or the like. Therefore, some or all of the information about an NF (e.g., an NFC) that is required for the NF to be granted authorization for a particular service / data can be considered part of the NF Properties and 6G NF Properties. However, the above-provided list of NF Properties are provided as select examples from among a larger set of known andcontemplated properties, features, functionalities, characteristics, or other information about an NF that can be used, either individually or in any combination, for determining whether to authorize the NF for receiving / providing particular services / data.
[0118] As used herein, the terms “VC Issuer” and “VC_Issuer” may refer to a verifiable credentials (VC) issuer that is configured to ensure that the information originally presented in a DID document (e.g., DID Entry) is correct and genuine, and only then, to sign the contents of the DID document. A DID document signed by a VC Issuer is thereafter interpreted to be / considered authenticated and correct by other entities / elements of the network. In some embodiments, the NRF can comprise or function as a VC Issuer. In some embodiments, the NRF can comprise or function as a VC Issuer. In some embodiments, select NFPor each NFPcan comprise or function as a VC Issuer. In some embodiments, an entirely separate element / function of the network can comprise or function as a VC Issuer.
[0119] As used herein, the term “DL Server” may refer to a server that hosts / stores at least a portion of the DL. The DL Server, when hosting the DL, can receive information about NFs, such as NF Profiles or NF Properties. The DL Server can store such information in one or more existing DID Entries, and / or can create one or more new DID Entries based on such received information. Alternatively or additionally, the DL Server can receive DID Entries and simply store the DID Entries that already contain / comprise such information about an NF. In some embodiments, the DL Server can receive queries or the like regarding DID Entries, NFs, NF Profiles, NF Properties, or the like. For example, an NFPcan query the DL Server for all or part of a DID Entry associated with a particular NFCusing a DID Number previously associated with the particular DID Entry in the DL, and the DL Server can be configured to return the requested DID Entry or portion thereof to the NFPin response.
[0120] In some embodiments, NF(s) deployed in a communications network (e.g., a 6G network) can initially have NF Properties information associated with each NF verified by a VC_Issuer, and can receive, once the NF Properties are verified by the VC_Issuer, a signed hash and / or access token from the VC_Issuer for a corresponding DID document, which is then included as a part of the DID Entry.
[0121] FIG. 6 illustrates an example approach in which an NFC(e.g., an NWDAF) requests services, resources, or data from an NFP(e.g., an AMF) in a communications network, such as a 5G or 6G network. The approach can be used by the NFC, e.g., to collect UE mobility data from a NFP(e.g., an AMF). The illustrated approach is particularly focused on an initial request procedure that is used when an NFCis making an initial request in the network, an initial request of a particular NFP, an initial request following a dormancy period or after a set duration oftime since a prior initial service / data request by that NFC, or an initial request by that NFCfor a particular (or particular type of) service, data, or resource. For example, an NFCmay have an outdated access token, a service / data request timer has elapsed, a service / data request counter has reached a predetermined threshold, or the access token used for prior service / data requests from the NFPmay otherwise be stale or outdated for other reasons.
[0122] Whether the initial service / data request is actually the first service / data request ever made by the NFC(in the network or of that particular NFP), or whether the initial service / data request is simply the first request following an access token / authentication / authorization reset or time-out event for the NFC, the NFCcan follow the following steps in order to be authenticated by the NFPand granted access to or otherwise provisioned the requested services, resources, and / or data.
[0123] As illustrated in FIG. 6, in step 1, an NFC(e.g., NWDAF) sends 6G NF properties information to a VC_Issuer for validation. The 6G NF Properties information can comprise or be part of an NF Profile. This NF Profile may also comprise the public key of the NFC(e.g., NWDAF) and / or an NF Unique Identifier.
[0124] In step 2, after successful verification on the content by the VC_Issuer, the VC_Issuer provisions a DL Entry in the DL Server. In some embodiments, the DL Entry can comprise at least a NF Unique Identifier (e.g., an NWDAF Identifier), a Public Key of the VC_Issuer, a Signed Hash for the 6G NF Properties information received from the NFC(e.g., NWDAF), and / or the like.
[0125] The DL Server can then create a unique DID Number corresponding to the DL Entry provisioned to the DL Server by VC_Issuer. The DL Server can be configured to provide the DID Number back to the VC_Issuer, to an NFP, an NFC, and / or other elements / functions of the network.
[0126] In step 3, the VC_Issuer can sign the DID Number, the DID Entry, or other DID documents using a private key associated with the VC_Issuer. The VC_Issuer can then send a signed hash and the DID number to the NFC, NFP, DL Server, and / or other elements of the system, along with a confirmation of the acceptance of the NF Properties associated with the NFc.
[0127] In some embodiments, the VC_Issuer can verify the contents of the NF Properties associated with the NFCbased upon any suitable information, such as TLS / mTLS certificates, which may include the NF Unique Identifier or the like associated with the NFC. In other embodiments, the VC_Issuer may one or more other credentials, certificates, identifiers, tokens, access type, encryption / protection information, network slice selection assistanceinformation (NSSAI), Single NSSAI (S-NSSAI), information provided by a policy control function (PCF), a service communication proxy (SCP) and / or a service routing function (SRF), a UE home PLMN identifier, a current visited PLMN identifier, and / or the like.
[0128] In optional step 4, if a DID Identifier / DID Number is not available, the NFC(e.g., NWDAF) can request the DID Identifier / DID Number from the DL Server, e.g., directly, by way of the NFP, or otherwise. The NFCcan make such a request for the DID Identifier / DID Number based on the NF Unique Identifier and / or hash previously received by the NFC.
[0129] In optional step 5, if a DID Identifier / DID Number is not available and the NFC(e.g., NWDAF) requests the same from the DL Server, the DL Server can search / query the DL for an entry, such as the DID Entry or the like, associated with the NFC. If a DID Entry or other record is found in the DL that is associated with the NFC, the DL Server can respond to the NFC(e.g., directly, by way of the NFP, or otherwise) and provide the DID Identifier / DID Number associated with or stored in the DID Entry.
[0130] In step 6, the NFC(e.g., NWDAF) can send a service / data request to the NFP(e.g., AMF), along with the DID Identifier / DID Number that was already known or provided in step 5 by the DL Server. The service / data request may also contain or be provided with an access token. For example, if the NFC(e.g., NWDAF) has received an access token from the DL Server, the NFP(e.g., AMF), or another element / function of the network, such as in response to a prior service / data request, the NFCcan include the access token it previously received to expedite authentication / authorization procedures at the NFP, NRF, VC_Issuer, DL Server, and / or other elements / functions of the network. Otherwise, if an access token has not been previously received by the NFC(e.g., NWDAF), the NFCcan send other information, credentials, or the like, along with the service / data request to assist with authentication / authorization procedures. For example, the NFCcan provide, with the service / data request, the NF Profile, the NF Properties, or the like.
[0131] If an access token is present in a data / service request received at the NFP(e.g., AMF) from the NFC(e.g., NWDAF), the NFPcan verify if the access token is valid. This verification of the access token can be done by way of simply comparing the provided access token to an access token stored at the NFPand already associated with the NFC.
[0132] Additionally or alternatively, this verification of the access token can be done by separate communication between the NFPand another element or function of the network, such as the VC_Issuer or the DL Server, which may have an access token stored therein that is associated with the NFCor the DID Identifier / DID Number associated with the NFC.
[0133] For example, in step 7, if the NFP(e.g., AMF) is not able to verify the access token or the access token is determined by the NFPto not be valid for whatever reason, the NFPcan send a request to the DL Server for the DID Identifier / DID Number associated with the NFCor DL Entry / DID Entry associated with the NFC.
[0134] In step 8. If the NFPrequests the DID Identifier / DID Number associated with the NFCor DL Entry / DID Entry associated with the NFCfrom the DL Server, and the DL Server is able to locate the correct DL Entry / DID Entry, the DL Server can respond to the NFPwith the DL or a subtree of the DL in response. The subtree of the DL can include only a portion of the DL, e.g., by assigning NFps, RANs, nodes, or the like to portions of the DL, such that the DL is contemporaneously transparent and auditable, but also distributed. This may also reduce the security risk of using a DL since compromising any one portion of the DL may not affect other portions of the DL.
[0135] The NFP(e.g., AMF) can verify that the DL Entry with the respective DID Identifier / DID Number is in the DL. This can be done by, e.g., comparing the DID Identifier / DID Number provided in the service / data request from the NFCto the DID Identifier / DID Number provided by the DL Server. Alternatively or additionally, if the DL Server provides all or some of the DL Entry / DID Entry for the NFCto the NFP, the NFPcan compare information therein, such as the NF Profile, the NF Properties, the NF Unique Identifer, and / or other information to that provided with the service / data request received from the NFc.
[0136] In step 9, if the NF Properties and / or NF Profile for the NFc (e.g., NWDAF) was not provided to the NFp (e.g., AMF) during step 6, the NFp can send a request to the NFc for the NF Properties and / or NF Profile for the NFc.
[0137] In step 10, in response to receiving the request from the NFPfor the NF Properties and / or NF Profile associated with the NFC, the NFCcan respond and provide its NF Properties and / or NF Profile. In some embodiments, the NF Properties and / or NF Profile can be statically associated with the NFC, while in other embodiments the NF Properties and / or NF Profile can be at least partially dynamically associated with the NFC. For example, the NF Properties and / or NF Profile provided by the NFCto the NFPcan be provided with regards to the particular service / data request, which may mean that the NF Properties and / or NF Profile may not be persistent across multiple service / data requests. However, in other embodiments, the NF Properties and / or NF Profile associated with the NFCcan be persistent across many or all service / data requests.
[0138] In step 11 , upon receiving the response from the NFCthat includes the NF Properties and / or NF Profile associated with the NFC, the NFPcan verify the integrity of the contents of the NF Properties / NF Profile. This can be done by using, for example, the signed hash present in the DL Entry. In other embodiments, this verification by the NFPcan be carried out using a public or private key previously exchanged between the NFCand one or more of the NFP, VC_Issuer, or DL Server. In embodiments in which the signed hash is signed by the private key of the VC_Issuer and is directly stored by the VC_Issuer in the DL Entry inside the DL Server, there may be increased confidence by the NFPthat if a malicious NFCor spoofed NFCtries to tamper with the contents, the NFPcan detect the tampering.
[0139] In step 12, if the NFPis able to successfully verify the integrity of the contents of the NF Properties / NF Profile provided either in step 6 or step 10, the NFPcan determine whether the NFCcan be granted access to the requested services, resources, and / or data. This determination by the NFPabout whether the NFCcan be granted access to the requested services, resources, and / or data can be based upon the NF Properties / NF Profile associated with the NFc. If the NFPdetermines that the NFCshould be granted access to the services, resources, and / or data requested in the service / data request, the NFPcan authorize such access for the NFC.
[0140] In legacy networks and systems, this determination and authorization for access for an NFCcan be carried out by the NRF, which presents many issues, such as those described above related to security concerns with the NRF being a single point of failure, and that the NRF being a single authentication / authorization source the resulting architecture and protocols result in very limited defense-in-depth due to a limited breadth and depth of the authorization / authentication structure.
[0141] However, in the described approach illustrated in FIG. 6, since the element / function of the network that is carrying out actual authentication / authorization of the NFCin response to service / data request is actually the NFP(e.g., AMF), which is the same entity producing and provisioning the service / data requested, the NFPcan itself directly check the contents of the NF Properties / NF Profile associated with the NFC, determine whether to grant access to the service, resource, or data being requested by the NFC, and then itself grant the NFCaccess to the service, resource, or data, or otherwise provide the same to the NFCwithout requiring further external signaling between the NFPand an NRF or another element or function of the network.
[0142] As such, in step 13, if the authorization by the NFPof the NF Properties / NF Profile for the NFCis successful, the NFPitself can generate an access token for the NFC. This access token generated by the NFPcan be signed using a private key of the NFP. In some embodiments, the access token (or access token claims) may include an NFCInstance Identifier, an NFCType,an indication of the service, resource, and / or data for which the access token is valid, an indication of the particular service / data request for which the access token is valid, an expiration time associated with the access token, the DID Identifier / DID Number associated with the NFC, an NFPInstance Identifier, an NFPType, a public key of the NFP, a current geographical area of the NFC, a geographical area limit for the NFC, a historical geographical area of the NFC, platform information for the NFC, and / or the like.
[0143] As shown in step 14 in FIG. 6, the NFP(e.g., AMF) can send a response to the NFC(e.g., NWDAF) that includes the existing access token or a new access token signed by a private key of the NFP. In some instances, the NFPcan also provide in that response to the NFCany requested data, information about requested services or resources, and / or the like. In other examples, the NFPcan indicate in the response to the NFCthat the NFCis now granted access to the services, resources, and / or data requested. In some instances, the NFCmay already know how to access the requested services, resources, and / or data, and may not need further information from the NFP, aside from an access token and an indication that access to the same is granted, in order for the NFCto commence access to or retrieval of the requested services, resources, and / or data. However, in other instances, the NFPmay provide such information in the response with the access token / new access token as needed for the NFCto commence access to or retrieval of the requested services, resources, and / or data.
[0144] Additionally or alternatively, steps 2 & 3 may make the issuer deposit the VC at the DL. In some embodiments, the VC_Issuer hands the NFc the DL Entry and the NFc itself deposites the DL Entry at the DL. In some embodiments, the VC_Issuer may not maintain a network connection with the DL. In some embodiments, the DL may only store DIDs and not the actual content of the DL Entry. In some embodiments, since the DL could be malicious and alter the DID, the VC within the DID may be signed by the VC_Issuer. In some embodiments, it may not be important in such instances whether the VC_Issuer itself, the NFc, or another network entity adds the DID (VC) to the DL. In some embodiments, the DL is considered trustworthy. In other embodiments, if the DL is malicious, the profiles of NFs stored in the DL may not be trustworthy.
[0145] The trust in the DL may be limited to ‘it keeps available, syncs and communicates fast enough’. In some embodiments, the DL is stored on the DL-Server, of which there can be many. Each operator can have their own DL Server. If one operator adds information to the DL (or a substructure of the DL), these updates are migrated to the other operator’s DL-servers. This way an NFc of one operator may get permission to access resources on another operator. In some embodiments, one purpose of the DL is to facilitate light weight information spreading(as opposed to a central entity). In some embodiments, the information itself is the VC, which is protected by a hash, a chameleon hash, and / or the like. In some embodiments, the VC are in the DID (or referenced to in the DID). In some embodiments, the DL-server may restrict DL Entry / DID writing and mapping because it is also able to write DL Entries / DIDs to the DL.
[0146] In some embodiments, the trust of ‘delivering information timely’ can be further differentiated from the trust of ‘not altering the information’. The DL-server may not be able to alter the information, but needs to be trusted to deliver the information in a timely fashion.
[0147] While FIG. 6 illustrates an example process for authentication / authorizing / granting access to services, resources, and / or data for an NFc as an initial request, whether it is actually the first ever request by the NFc or whether it is a first request after an access token reset / expiration event, an expedited or truncated process can be carried out in certain instances when a service / data request is a subsequent service / data request and the NFc already has a valid access token to provide to the NFp with its service / data request. An example of such a process is illustrated in FIG. 7.
[0148] As illustrated in FIG. 7, in step 1, an NFC(e.g., NWDAF) sends 6G NF properties information to a VC_Issuer for validation. The 6G NF Properties information can comprise or be part of an NF Profile. This NF Profile may also comprise the public key of the NFC(e.g., NWDAF) and / or an NF Unique Identifier.
[0149] In step 2, after successful verification on the content by the VC_Issuer, the VC_Issuer provisions a DL Entry in the DL Server. In some embodiments, the DL Entry can comprise at least a NF Unique Identifier (e.g., an NWDAF Identifier), a Public Key of the VC_Issuer, a Signed Hash for the 6G NF Properties information received from the NFC(e.g., NWDAF), and / or the like.
[0150] The DL Server can then create a unique DID Number corresponding to the DL Entry provisioned to the DL Server by VC_Issuer. The DL Server can be configured to provide the DID Number back to the VC_Issuer, to an NFP, an NFC, and / or other elements / functions of the network.
[0151] In step 3, the VC_Issuer can sign the DID Number, the DID Entry, or other DID documents using a private key associated with the VC_Issuer. The VC_Issuer can then send a signed hash and the DID number to the NFC, NFP, DL Server, and / or other elements of the system, along with a confirmation of the acceptance of the NF Properties associated with the NFc.
[0152] In some embodiments, the VC_Issuer can verify the contents of the NF Properties associated with the NFCbased upon any suitable information, such as TLS / mTLS certificates,which may include the NF Unique Identifier or the like associated with the NFC. In other embodiments, the VC_Issuer may one or more other credentials, certificates, identifiers, tokens, access type, encryption / protection information, network slice selection assistance information (NSSAI), Single NSSAI (S-NSSAI), information provided by a policy control function (PCF), a service communication proxy (SCP) and / or a service routing function (SRF), a UE home PLMN identifier, a current visited PLMN identifier, and / or the like.
[0153] In optional step 4, if a DID Identifier / DID Number is not available, the NFC(e.g., NWDAF) can request the DID Identifier / DID Number from the DL Server, e.g., directly, by way of the NFP, or otherwise. The NFCcan make such a request for the DID Identifier / DID Number based on the NF Unique Identifier and / or hash previously received by the NFC.
[0154] In optional step 5, if a DID Identifier / DID Number is not available and the NFC(e.g., NWDAF) requests the same from the DL Server, the DL Server can search / query the DL for an entry, such as the DID Entry or the like, associated with the NFC. If a DID Entry or other record is found in the DL that is associated with the NFC, the DL Server can respond to the NFC(e.g., directly, by way of the NFP, or otherwise) and provide the DID Identifier / DID Number associated with or stored in the DID Entry.
[0155] Since the NFCalready has a valid access token, the NFCcan skip some or all of steps 6-14 as discussed above with regard to FIG. 6. Instead, the NFCcan simply send a service / data request with the DID Identifier / DID Number and the valid access token to the NFP.
[0156] For example, in step 15, the NFC(e.g., NWDAF) can send a service / data request to the NFP(e.g., AMF), along with the DID Identifier / DID Number that was already known by the NFCor provided by the DL Server. The NFCcan include in / with that service / data request an access token associated with the NFCthat the NFCknows or believes is valid. If the NFPdetermines, after reviewing the access token in the service / data request from the NFCthat the access token that the NFCbelieves to be valid is not, in fact, valid, the process illustrated in FIG. 7 can be modified to look at least similar to that illustrated in FIG. 6, or entirely abandoned in favor of following the initial request procedure illustrated in FIG. 6.
[0157] In step 16, if the service / data request received at the NFPfrom the NFChas an access token, the NFPverifies the validity of the access token. In some embodiments, the access token (or access token claims) may include an NFCInstance Identifier, an NFCType, an indication of the service, resource, and / or data for which the access token is valid, an indication of the particular service / data request for which the access token is valid, an expiration time associated with the access token, the DID Identifier / DID Number associated with the NFC, an NFPInstance Identifier, an NFPType, a request counter value, a public key of the NFP, a current geographicalarea of the NFC, a geographical area limit for the NFC, a historical geographical area of the NFC, platform information for the NFC, and / or the like.
[0158] As such, verification of the validity of an access token by the NFPcan include an evaluation of one or more of the contents of the access token / access token claims, such as the NFcs DID Identifier / DID Number, the expiration time for the access token, the request counter value relative to a predetermined threshold or limit, and / or the like.
[0159] If the NFPis able to successfully verify the validity of the access token, the NFPcan determine that the NFCcan be granted access to the requested services, resources, and / or data. If the NFPdetermines that the NFCshould be granted access to the services, resources, and / or data requested in the service / data request, the NFPcan authorize such access for the NFC.
[0160] As noted above, since the element / function of the network that is carrying out actual authentication / authorization of the NFCin response to service / data request is actually the NFP(e.g., AMF), which is the same entity producing and provisioning the service / data requested, the NFPcan itself directly check the contents of the NF Properties / NF Profile associated with the NFC, determine whether to grant access to the service, resource, or data being requested by the NFC, and then itself grant the NFCaccess to the service, resource, or data, or otherwise provide the same to the NFCwithout requiring further external signaling between the NFPand an NRF or another element or function of the network.
[0161] As such, in FIG. 7, at step 16, if the verification by the NFPof the access token determines that the access token is valid, the NFPitself can authorize / grant access for the NFCto the requested services, resources, and / or data.
[0162] As shown in step 17 in FIG. 7, the NFP(e.g., AMF) can send a response to the NFC(e.g., NWDAF) that includes the existing access token or a new access token signed by a private key of the NFP. In some instances, the NFPcan also provide in that response to the NFCany requested data, information about requested services or resources, and / or the like. In other examples, the NFPcan indicate in the response to the NFCthat the NFCis now granted access to the services, resources, and / or data requested. In some embodiments, the NFCmay already know how to access the requested services, resources, and / or data, and may not need further information from the NFP, aside from an indication that access to the same is granted (and, optionally, the existing access token or a new access token), in order for the NFCto commence access to or retrieval of the requested services, resources, and / or data. However, in other embodiments, the NFPmay provide such information in the response with the access token / new access token as needed for the NFCto commence access to or retrieval of the requested services, resources, and / or data.
[0163] In some embodiments in which a particular NFPinstance is signing the access token, such as when the NFPis virtualized and requests are instance specific or instance limited, the persistence of the access token may be limited to that particular NFPinstance as it is an Instance ID-based access token. In other embodiments in which the access token is not signed by a particular NFPinstance or the NFPis not virtualized or is persistently virtualized, the access token may not be Instance ID-based, and therefore the NFCcan continue to use the access token with the NFPduring the second and subsequent service / data request procedures, without regard or with less regard for whether the NFPis virtualized and / or with less or not consideration of whether the NFPinstance is the same NFPinstance.
[0164] As illustrated in FIGs. 6 and 7 and described above, each of the described approaches solve for at least several of the existing authorization vulnerabilities in the 5G Core network, such as by enabling NFps to directly verify the contents of the NF Properties / NF Profile for NFcs, and enables NFps to grant authorization to NFcs directly based upon its own local policies.
[0165] Accordingly, if the NFChas what it believes is a valid access token, but the NFPhas changed its local policies without indicating the same to the NFCand / or other elements / functions of the network, then the NFPmay reject an NFcs service / data request that comprises what the NFc believes is a valid access token. For example, the NFPmay expand or reduce the NF Properties that it considers for determining whether to grant the NFCaccess to the requested services, resources, and / or data. The NFPmay, also or instead, change a threshold, value, characteristic type, NF property option, or other element of the NF Profile that it considers acceptable / allowable for purposes of granting NFcs access to all or select services, resources, and / or data. By localizing the authentication process to the NFP, the described approaches reduce overall signaling and decentralize the security protocols for service / data provisioning in the network. By localizing the service / data / resource authorization / grant process to the NFP, the described approaches increase overall autonomy at each NFPand provide for a more nimble, responsive security approach that no longer requires, in many instances, a formal change to the core standard in order for a particular NFP, or NFps writ large, to respond to changing threat conditions with dynamic security considerations and protocols.
[0166] According to other embodiments, the full NF Properties / NF Profile for the NFCcan be stored at the DL Server. This may be done during or after step 2. Then, in steps 7 and 8, as described above with regard to FIG. 6, the NFPcan query, download, retrieve, or otherwise access the full NF Properties / NF Profile for the NFCfrom the DL Server (e.g., by requesting the DL Entry / DID Entry from the DL Server). In that way, the NFCcan avoid sending the fullNF Properties / NF Profile in each service / data request or in each new service / data request, since repeatedly providing the full NF Properties / NF Profile for the NFCto various NFps could increase security / privacy risks and other concerns related to intercepted signaling, spoofed NFpS, or the like, and because reducing such signaling may reduce cost, increase efficiency of such service / data requests, and / or increase bandwidth by reducing the volume of service / request traffic in the NFCto NFPdirection.
[0167] Additionally or alternatively, the DL Server may store the full NF Properties / NF Profile for the NFCand then the NFCcan provide a portion of the full NF Properties / NF Profile in the service / data request, which the NFPcan use for determining whether to grant the service / data request for the NFCby way of a comparison of the provided portion of the full NF Properties / NF Profile to the full NF Properties / NF Profile stored at the DL Server or a portion thereof. Such a comparison of the provided portion of the NF Properties / NF Profile can be carried out by the NFP, the DL Server, the VC_Issuer, and / or another element or function of the network.
[0168] Referring now to FIG. 8, a method 300 is illustrated that is carried out by an apparatus comprising at least one processor and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus to carry out the method 300. In some embodiments, the apparatus can be similar to or comprise the apparatus 200 described above. The method 300 can include: sending, from a network function consumer (NFC) in a communication network, to an entity of the communication network, a message comprising property information associated with the NFC, a public key associated with the NFC, and a network function unique identifier associated with the NFC, at 301. The method 300 can further comprise receiving, at the NFC, from the entity of the communication network, a response to the message, the response comprising a signed hash of the property information, an indication that the property information associated with the NFCis accepted, and a decentralized identifier (DID) number associated with the NFC, at 302.
[0169] Referring now to FIG. 9, a method 400 is illustrated that is carried out by an apparatus comprising at least one processor and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus to carry out the method 400. In some embodiments, the apparatus can be similar to or comprise the apparatus 200 described above. The method 400 can include: receiving, at a network function producer (NFP) in a communication network, from a network function consumer (NFC) in the communication network, a message comprising property information associated with the NFC, a public key associated with the NFC, and a network function unique identifier associated with the NFC, at401. The method 400 can further include: verifying, using the NFP, the property information, the public key, and the network function unique identifier associated with the NFC, at 402. The method 400 can further include: in an instance in which the NFCverifies the property information, the public key, and the network function unique identifier associated with the NFC, providing, from the NFP, to the NFC, a response to the message, the response comprising a signed hash of the property information, an indication that the property information associated with the NFCis accepted, and a decentralized identifier (DID) number associated with the NFC, at 403.
[0170] Referring now to FIG. 10, a method 500 is illustrated that is carried out by an apparatus comprising at least one processor and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus to carry out the method 500. In some embodiments, the apparatus can be similar to or comprise the apparatus 200 described above. The method 500 can include: sending, from a network function consumer (NFC) in a communication network, to a network function producer (NFP) in the communication network, a message comprising a service or data request, the message further comprising a decentralized identifier (DID) number associated with the NFC, at 501. The method 500 can further include: in an instance in which the service or data request is a first request for data or services between the NFCand the NFP, receiving, at the NFC, from the NFP, a network function profile request for a network function profile associated with the NFC, at 502. The method 500 can further include: preparing, in response to the network function profile request, a network function consumer profile response including network function properties associated with the NFC, at 503.
[0171] Referring now to FIG. 11, a method 600 is illustrated that is carried out by an apparatus comprising at least one processor and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus to carry out the method 600. In some embodiments, the apparatus can be similar to or comprise the apparatus 200 described above. The method 600 can include: receiving, at a network function producer (NFP) in a communication network, from a network function consumer (NFC) in the communication network, a message comprising a service or data request, the message further comprising a decentralized identifier (DID) number associated with the NFC, at 601. The method 600 can further include: determining whether the DID number associated with the NFCis in a distributed ledger (DL) server, at 602. The method 600 can further include: in an instance in which the DID number associated with the NFCis in the DL server, determining whether the message received from the NFCincludes a network function consumer profile comprising networkfunction properties associated with the NFC, at 603. The method 600 can further include: in an instance in which the message received from the NFCdoes not include a network function consumer profile comprising network function properties associated with the NFC, sending a network function consumer profile request from the NFPto the NFC, at 604.
[0172] Referring now to FIG. 12, a method 700 is illustrated that is carried out by an apparatus comprising at least one processor and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus to carry out the method 700. In some embodiments, the apparatus can be similar to or comprise the apparatus 200 described above. The method 700 can include: sending, from a network function consumer (NFC) in a communication network, to a network function producer (NFP) in the communication network, a message comprising a service or data request, the message further comprising a decentralized identifier (DID) number associated with the NFCand an access token associated with network function consumer properties previously provided by the NFCto the NFP, at 701. The method 700 can further include: in an instance in which the message includes an access token associated with network function consumer properties previously provided by the NFCto the NFP, receiving, at the NFC, from the NFP, a response comprising the access token and the service or data requested by the NFCin the service or data request, at 702.
[0173] Referring now to FIG. 13, a method 800 is illustrated that is carried out by an apparatus comprising at least one processor and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus to carry out the method 800. In some embodiments, the apparatus can be similar to or comprise the apparatus 200 described above. The method 800 can include: receiving, at a network function producer (NFP) in a communication network, from a network function consumer (NFC) in the communication network, a message comprising a service or data request, the message further comprising a decentralized identifier (DID) number associated with the NFCand an access token associated with network function consumer properties previously provided to the NFPby the NFC, at 801. The method 800 can further include: in an instance in which the message includes an access token associated with network function consumer properties previously provided to the NFPby the NFC, determining that the service or data request is not a first request for data or services between the NFCand the NFP, at 802. The method 800 can further include: in an instance in which the service or data request is not the first request for data or services between the NFCand the NFP, verifying the access token based on a public key associated with the NFCand issued by a verifiable credentials (VC) issuer, at 803. The method 800 can further include: if the access token is verified, providing a response from the NFPto the NFC, the responsecomprising the access token and the service or data requested in the service or data request received at the NFP, at 804.
[0174] As described above, FIGs. 8-13 are flowcharts of various methods that can be carried out by, e.g., the apparatus 200, and / or according to a computer program product, according to example embodiments of the disclosure. It will be understood that each block of the flowchart, and combinations of blocks in the flowcharts, may be implemented by various hardware, firmware, processor, circuitry, and / or other devices associated with execution of software including one or more computer program instructions. For example, one or more of the procedures described above may be embodied by computer program instructions. In this regard, the computer program instructions which embody the procedures described above may be stored by a memory device 204 of an apparatus employing an embodiment of the present disclosure and executed by a processor 202 of the apparatus. As will be appreciated, any such computer program instructions may be loaded onto a computer or other programmable apparatus (e.g., hardware) to produce a machine, such that the resulting computer or other programmable apparatus implements the functions specified in the flowchart blocks. These computer program instructions may also be stored in a computer-readable memory that may direct a computer or other programmable apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture, the execution of which implements the function specified in the flowchart blocks. The computer program instructions may also be loaded onto a computer or other programmable apparatus to cause a series of operations to be performed on the computer or other programmable apparatus to produce a computer-implemented process such that the instructions which execute on the computer or other programmable apparatus provide operations for implementing the functions specified in the flowchart blocks.
[0175] A computer program product is therefore defined in those instances in which the computer program instructions, such as computer-readable program code portions, are stored by at least one non-transitory computer-readable storage medium with the computer program instructions, such as the computer-readable program code portions, being configured, upon execution, to perform the functions described above, such as, e.g., in conjunction with the communications flowcharts of FIGs. 6-7 or as part of the system of FIGs. 1, 3, 4, or 5. In other embodiments, the computer program instructions, such as the computer-readable program code portions, need not be stored or otherwise embodied by a non-transitory computer-readable storage medium, but may, instead, be embodied by a transitory medium with the computerprogram instructions, such as the computer-readable program code portions, still being configured, upon execution, to perform the functions described above.
[0176] Accordingly, blocks of the flowcharts support combinations of devices, equipment, firmware, software, and / or the like for performing the specified functions and combinations of operations for performing the specified functions for performing the specified functions. It will also be understood that one or more blocks of the flowcharts, and combinations of blocks in the flowcharts, may be implemented by special purpose hardware-based computer systems which perform the specified functions, or combinations of special purpose hardware and computer instructions.
[0177] In some embodiments, certain ones of the operations above may be modified or further amplified. Furthermore, in some embodiments, additional optional operations may be included. Modifications, additions, or amplifications to the operations above may be performed in any order and in any combination.
[0178] Many modifications and other embodiments of the disclosure set forth herein will come to mind to one skilled in the art to which the disclosure pertains, having the benefit of the teachings presented in the foregoing descriptions and the associated drawings. Therefore, it is to be understood that this disclosure is not to be limited to the specific embodiments disclosed and that modifications and other embodiments are intended to be included within the scope of the appended claims. Although specific terms are employed herein, they are used in a generic and descriptive sense only and not for purposes of limitation.
Claims
CLAIMS:
1. An apparatus comprising: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus at least to perform: sending a message to an entity of a communication network, the message comprising property information associated with the apparatus, a public key associated with the apparatus, and a network function unique identifier associated with the apparatus; and receiving, from the entity of the communication network, a response to the message, the response comprising a signed hash of the property information, an indication that the property information associated with the apparatus is accepted, and a decentralized identifier (DID) number associated with the apparatus, wherein the apparatus is configured to include the DID number in requests for service or data in order to expedite integrity verification of the requests for service or data and authentication of the apparatus.
2. The apparatus of claim 1, wherein the entity of the communication network comprises a verifiable credentials (VC) issuer.
3. The apparatus of claim 1, wherein the apparatus comprises a network function consumer (NFc).
4. The apparatus of claim 3, wherein the NFc comprises a network data analytics function (NWDAF).
5. The apparatus of claim 1, wherein the instructions, when executed by the at least one processor, further causes the apparatus to perform at least: sending, to a network function producer (NFp) of the communication system, a request for service or data, the request for service or data comprising the DID number associated with the apparatus and the property information associated with the apparatus; and receiving, in response to the request for service or data, from the NFp, with the service or data requested, an access token associated with the apparatus and / or the DID number.
6. The apparatus of claim 5, wherein the instructions, when executed by the at least one processor, further causes the apparatus to perform at least: sending, to a network function producer (NFp), a subsequent request for service or data, the subsequent request for service or data comprising the access token associated with the apparatus and / or the DID number; and receiving, from the NFp, in response to the subsequent request for service or data, the service or data requested in the subsequent request sent to the NFp.
7. A method comprising: sending, from a network function consumer (NFc) in a communication network, to an entity of the communication network, a message comprising property information associated with the NFC, a public key associated with the NFc, and a network function unique identifier associated with the NFc; and receiving, at the NFc, from the entity of the communication network, a response to the message, the response comprising a signed hash of the property information, an indication that the property information associated with the NFc is accepted, and a decentralized identifier (DID) number associated with the NFc, wherein the NFc is configured to include the DID number in subsequent service or data requests in order to expedite integrity verification of the subsequent service or data requests and authentication of the NFc.
8. The method of claim 7, wherein the entity of the communication network comprises a verifiable credentials (VC) issuer.
9. The method of claim 7, wherein the NFc comprises a network data analytics function (NWDAF).
10. The method of claim 7, further comprising: sending, to a network function producer (NFp) of the communication system, a request for service or data, the request for service or data comprising the DID number associated with the NFc and the property information associated with the NFc; and receiving, in response to the request for service or data, from the NFp, with the service or data requested, an access token associated with the NFc and / or the DID number.
11. The method of claim 10, further comprising: sending, to a network function producer (NFp), a subsequent request for service or data, the subsequent request for service or data comprising the access token associated with the apparatus and / or the DID number; and receiving, from the NFp, in response to the subsequent request for service or data, the service or data requested in the subsequent request sent to the NFp.
12. An apparatus comprising: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus at least to perform: receiving, from a network function consumer (NFc) in a communication network, a message comprising property information associated with the NFc, a public key associated with the NFc, and a network function unique identifier associated with the NFc; verifying the property information, the public key, and the network function unique identifier associated with the NFc; and in an instance in which the apparatus verifies the property information, the public key, and the network function unique identifier associated with the NFc, providing, to the NFc, a response to the message, the response comprising a signed hash of the property information, an indication that the property information associated with the NFc is accepted, and a decentralized identifier (DID) number associated with the NFc, wherein the apparatus is configured to carry out integrity verification of subsequent service or data requests from the NFc and authentication of the NFc based upon the DID number included in the subsequent service or data requests.
13. The apparatus of claim 12, wherein the instructions, when executed by the at least one processor, cause the apparatus to further perform at least: creating, based at least upon the property information, the public key, and the network function unique identifier associated with the NFc, a distributed ledger (DL) entry associated with the NFc, the DL entry including the DID number for the NFc; and including the DL entry in a DL stored at a DL server of the communication system.
14. The apparatus of claim 12, wherein the instructions, when executed by the at least one processor, cause the apparatus to further perform at least:causing a distributed ledger (DL) server in the communication system to create a DL entry associated with the NFc based at least upon the property information, the public key, and the network function unique identifier associated with the NFc; and receiving, from the DL server, the DID number for the NFc.
15. A method comprising : receiving, at a network function producer (NFp) in a communication network, from a network function consumer (NFc) in the communication network, a message comprising property information associated with the NFc, a public key associated with the NFc, and a network function unique identifier associated with the NFc; verifying, using the NFp, the property information, the public key, and the network function unique identifier associated with the NFc; and in an instance in which the NFc verifies the property information, the public key, and the network function unique identifier associated with the NFc, providing, from the NFp, to the NFc, a response to the message, the response comprising a signed hash of the property information, an indication that the property information associated with the NFc is accepted, and a decentralized identifier (DID) number associated with the NFc, wherein the NFp is configured to carry out integrity verification of subsequent service or data requests received from the NFc and authenticate the NFc based upon the DID number included in the subsequent service or data requests.
16. The method of claim 15, further comprising: creating, based at least upon the property information, the public key, and the network function unique identifier associated with the NFc, a distributed ledger (DL) entry associated with the NFc, the DL entry including the DID number for the NFc; and including the DL entry in a DL stored at a DL server of the communication system.
17. The method of claim 15, wherein the instructions, when executed by the at least one processor, cause the apparatus to further perform at least: causing a distributed ledger (DL) server in the communication system to create a DL entry associated with the NFc based at least upon the property information, the public key, and the network function unique identifier associated with the NFc; and receive, from the DL server, the DID number for the NFc.
18. An apparatus comprising: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus at least to perform: sending a message to a network function producer (NFp) in a communication network, the message comprising a service or data request, the message further comprising a decentralized identifier (DID) number associated with the apparatus; in an instance in which the service or data request is a first request for data or services between the apparatus and the NFp, receiving, from the NFp, a network function profile request for a network function profile associated with the apparatus; and preparing, in response to the network function profile request, a network function consumer profile response including network function properties associated with the apparatus.
19. The apparatus of claim 18, wherein the instructions, when executed by the at least one processor, cause the apparatus to further perform at least: sending, to the NFp, the network function consumer profile response; and receiving, from the NFp, in response to the network function consumer profile response, an access token associated with the DID number.
20. The apparatus of claim 19, wherein the instructions, when executed by the at least one processor, cause the apparatus to further perform at least: sending a message to the NFp, the message comprising a service or data request, the message further comprising the DID number associated with the apparatus and the access token associated with the network function consumer properties previously provided by the apparatus to the NFp; and in an instance in which the message includes a valid DID number associated with the apparatus and a valid access token associated with the network function consumer properties previously provided by the apparatus to the NFp, receiving, from the NFp, a service or data response comprising the access token and the service or data requested in the service or data request.
21. A method comprising :sending, from a network function consumer (NFc) in a communication network, to a network function producer (NFp) in the communication network, a message comprising a service or data request, the message further comprising a decentralized identifier (DID) number associated with the NFc; in an instance in which the service or data request is a first request for data or services between the NFc and the NFp, receiving, at the NFc, from the NFp, a network function profile request for a network function profile associated with the NFc; and preparing, in response to the network function profile request, a network function consumer profile response including network function properties associated with the NFc.
22. The method of claim 21, further comprising: sending, to the NFp, the network function consumer profile response; and receiving, from the NFp, in response to the network function consumer profile response, an access token associated with the DID number.
23. The method of claim 22, further comprising: sending a message to the NFp, the message comprising a service or data request, the message further comprising the DID number associated with the apparatus and the access token associated with the network function consumer properties previously provided by the apparatus to the NFp; and in an instance in which the message includes a valid DID number associated with the apparatus and a valid access token associated with the network function consumer properties previously provided by the apparatus to the NFp, receiving, from the NFp, a service or data response comprising the access token and the service or data requested in the service or data request.
24. An apparatus comprising: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus at least to perform: receiving, from a network function consumer (NFc) in a communication network, a message comprising a service or data request, the message further comprising a decentralized identifier (DID) number associated with the NFc;determining whether the DID number associated with the NFc is in a distributed ledger (DL) server; in an instance in which the DID number associated with the NFc is in the DL server, determining whether the message received from the NFc includes a network function consumer profile comprising network function properties associated with the NFc; and in an instance in which the message received from the NFc does not include a network function consumer profile comprising network function properties associated with the NFc, sending a network function consumer profile request to the NFc.
25. The apparatus of claim 24, wherein the instructions, when executed by the at least one processor, cause the apparatus to further perform at least: receiving, from the NFc, a network function consumer profile response including network function consumer properties associated with the NFc; and integrity verifying the network function consumer properties associated with the NFc using a public key issued by a verifiable credentials (VC) issuer and a signed hash from a DL entry associated with the NFc and stored at the DL server of the communication system.
26. A method comprising: receiving, at a network function producer NFp) in a communication network, from a network function consumer (NFc) in the communication network, a message comprising a service or data request, the message further comprising a decentralized identifier (DID) number associated with the NFc; determining whether the DID number associated with the NFc is in a distributed ledger (DL) server; in an instance in which the DID number associated with the NFc is in the DL server, determining whether the message received from the NFc includes a network function consumer profile comprising network function properties associated with the NFc; and in an instance in which the message received from the NFc does not include a network function consumer profile comprising network function properties associated with the NFc, sending a network function consumer profile request from the NFp to the NFc.
27. An apparatus comprising: at least one processor; andat least one memory storing instructions that, when executed by the at least one processor, cause the apparatus at least to perform: sending a message to a network function producer (NFp) in a communication network, the message comprising a service or data request, the message further comprising a decentralized identifier (DID) number associated with the apparatus and an access token associated with network function consumer properties previously provided by the apparatus to the NFp; and in an instance in which the message includes an access token associated with network function consumer properties previously provided by the apparatus to the NFp, receiving, from the NFp, a response comprising the access token and the service or data requested in the service or data request.
28. A method comprising: sending, from a network function consumer (NFc) in a communication network, to a network function producer (NFp) in the communication network, a message comprising a service or data request, the message further comprising a decentralized identifier (DID) number associated with the NFc and an access token associated with network function consumer properties previously provided by the NFc to the NFp; and in an instance in which the message includes an access token associated with network function consumer properties previously provided by the NFc to the NFp, receiving, at the NFc, from the NFp, a response comprising the access token and the service or data requested by the NFc in the service or data request.
29. An apparatus comprising: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus at least to perform: receiving, from a network function consumer (NFc) in a communication network, a message comprising a service or data request, the message further comprising a decentralized identifier (DID) number associated with the NFc and an access token associated with network function consumer properties previously provided to the apparatus by the NFc; in an instance in which the message includes an access token associated with network function consumer properties previously provided to the apparatus by the NFc,determining that the service or data request is not a first request for data or services between the NFc and the apparatus; in an instance in which the service or data request is not the first request for data or services between the NFc and the apparatus, verifying the access token; and if the access token is verified, providing a response to the NFc, the response comprising the access token and the service or data requested in the service or data request.
30. A method comprising: receiving, at a network function producer (NFp) in a communication network, from a network function consumer (NFc) in the communication network, a message comprising a service or data request, the message further comprising a decentralized identifier (DID) number associated with the NFc and an access token associated with network function consumer properties previously provided to the NFp by the NFc; in an instance in which the message includes an access token associated with network function consumer properties previously provided to the NFp by the NFc, determining that the service or data request is not a first request for data or services between the NFc and the NFp; in an instance in which the service or data request is not the first request for data or services between the NFc and the NFp, verifying the access token based on a public key associated with the NFc and issued by a verifiable credentials (VC) issuer; and if the access token is verified, providing a response from the NFp to the NFc, the response comprising the access token and the service or data requested in the service or data request received at the NFp.
31. An apparatus comprising: means for sending a message to an entity of a communication network, the message comprising property information associated with the apparatus, a public key associated with the apparatus, and a network function unique identifier associated with the apparatus; and means for receiving, from the entity of the communication network, a response to the message, the response comprising a signed hash of the property information, an indication that the property information associated with the apparatus is accepted, and a decentralized identifier (DID) number associated with the apparatus, wherein the apparatus is configured to include the DID number in requests for service or data in order to expedite integrity verification of the requests for service or data and authentication of the apparatus.
32. The apparatus of claim 31, further comprising: means for sending, to a network function producer (NFp) of the communication system, a request for service or data, the request for service or data comprising the DID number associated with the apparatus and the property information associated with the apparatus; and means for receiving, in response to the request for service or data, from the NFp, with the service or data requested, an access token associated with the apparatus and / or the DID number.
33. The apparatus of claim 32, further comprising: means for sending, to a network function producer (NFp), a subsequent request for service or data, the subsequent request for service or data comprising the access token associated with the apparatus and / or the DID number; and means for receiving, from the NFp, in response to the subsequent request for service or data, the service or data requested in the subsequent request sent to the NFp.
34. An apparatus comprising: means for receiving, from a network function consumer (NFc) in a communication network, a message comprising property information associated with the NFc, a public key associated with the NFc, and a network function unique identifier associated with the NFc; means for verifying the property information, the public key, and the network function unique identifier associated with the NFc; and means for, in an instance in which the apparatus verifies the property information, the public key, and the network function unique identifier associated with the NFc, providing, to the NFc, a response to the message, the response comprising a signed hash of the property information, an indication that the property information associated with the NFc is accepted, and a decentralized identifier (DID) number associated with the NFc, wherein the apparatus is configured to carry out integrity verification of subsequent service or data requests from the NFc and authentication of the NFc based upon the DID number included in the subsequent service or data requests.
35. The apparatus of claim 34, further comprising:means for creating, based at least upon the property information, the public key, and the network function unique identifier associated with the NFc, a distributed ledger (DL) entry associated with the NFc, the DL entry including the DID number for the NFc; and means for including the DL entry in a DL stored at a DL server of the communication system.
36. The apparatus of claim 34, further comprising: means for causing a distributed ledger (DL) server in the communication system to create a DL entry associated with the NFc based at least upon the property information, the public key, and the network function unique identifier associated with the NFc; and means for receiving, from the DL server, the DID number for the NFc.
37. An apparatus comprising: means for sending a message to a network function producer (NFp) in a communication network, the message comprising a service or data request, the message further comprising a decentralized identifier (DID) number associated with the apparatus; means for, in an instance in which the service or data request is a first request for data or services between the apparatus and the NFp, receiving, from the NFp, a network function profile request for a network function profile associated with the apparatus; and means for preparing, in response to the network function profile request, a network function consumer profile response including network function properties associated with the apparatus.
38. The apparatus of claim 37, further comprising: means for sending, to the NFp, the network function consumer profile response; and means for receiving, from the NFp, in response to the network function consumer profile response, an access token associated with the DID number.
39. The apparatus of claim 38, further comprising: means for sending a message to the NFp, the message comprising a service or data request, the message further comprising the DID number associated with the apparatus and the access token associated with the network function consumer properties previously provided by the apparatus to the NFp; andmeans for, in an instance in which the message includes a valid DID number associated with the apparatus and a valid access token associated with the network function consumer properties previously provided by the apparatus to the NFp, receiving, from the NFp, a service or data response comprising the access token and the service or data requested in the service or data request.
40. An apparatus comprising: means for receiving, from a network function consumer (NFc) in a communication network, a message comprising a service or data request, the message further comprising a decentralized identifier (DID) number associated with the NFc; means for determining whether the DID number associated with the NFc is in a distributed ledger (DL) server; means for, in an instance in which the DID number associated with the NFc is in the DL server, determining whether the message received from the NFc includes a network function consumer profile comprising network function properties associated with the NFc; and means for, in an instance in which the message received from the NFc does not include a network function consumer profile comprising network function properties associated with the NFc, sending a network function consumer profile request to the NFc.
41. The apparatus of claim 40, further comprising: means for receiving, from the NFc, a network function consumer profile response including network function consumer properties associated with the NFc; and means for integrity verifying the network function consumer properties associated with the NFc using a public key issued by a verifiable credentials (VC) issuer and a signed hash from a DL entry associated with the NFc and stored at the DL server of the communication system.
42. An apparatus comprising: means for sending a message to a network function producer (NFp) in a communication network, the message comprising a service or data request, the message further comprising a decentralized identifier (DID) number associated with the apparatus and an access token associated with network function consumer properties previously provided by the apparatus to the NFp; andmeans for, in an instance in which the message includes an access token associated with network function consumer properties previously provided by the apparatus to the NFp, receiving, from the NFp, a response comprising the access token and the service or data requested in the service or data request.
43. An apparatus comprising: means for receiving, from a network function consumer (NFc) in a communication network, a message comprising a service or data request, the message further comprising a decentralized identifier (DID) number associated with the NFc and an access token associated with network function consumer properties previously provided to the apparatus by the NFc; means for, in an instance in which the message includes an access token associated with network function consumer properties previously provided to the apparatus by the NFc, determining that the service or data request is not a first request for data or services between the NFc and the apparatus; means for, in an instance in which the service or data request is not the first request for data or services between the NFc and the apparatus, verifying the access token; and means for, if the access token is verified, providing a response to the NFc, the response comprising the access token and the service or data requested in the service or data request.
Citation Information
Cited By
Systems and methods for third-party agent broker automations
US20260052149A1
