Communication method, communication device, medium, and program product
Through blockchain technology and smart contracts, combined with symmetric keys and alliance chains, the security and efficiency problems of network function access and authorization of cross-operators in the 5G core network are solved, and safe and efficient network function authorization and authentication are achieved to meet the needs of the 5G core network. The security needs of modern mobile networks.
Patent Information
- Application Number
- CN202310581318.2
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2023-05-22
- Publication Date
- 2024-11-22
AI Technical Summary
In the service-oriented architecture of 5G core networks, openness and flexibility conflict with security, privacy and performance requirements, and new mechanisms are needed to meet the security needs of modern mobile networks, especially in network functionality access and authorization across operators In the scene.
Using blockchain technology, through distributed management of devices and trusted environment devices, symmetric keys are used for encryption and decryption, combined with smart contracts and alliance chains, the secure registration and authorization of network functional devices is realized, reducing the traditional point-to-point trust relationship. Complexity and guarantee the credibility and efficiency of functions.
It realizes safe and efficient authorization and authentication of network functions across operators, reduces the complexity of trust establishment among operators, ensures secure storage and cross-domain sharing of network function information, and improves the openness and transparency of the system.
Smart Images

Figure CN119012194A_ABST
Abstract
Description
Technical Field
[0001] The present application generally relates to the field of communications, and more particularly to a communication method, a communication device, a computer-readable storage medium, and a computer program product. Background Art
[0002] As technology develops, the fifth generation of mobile communication systems (5G) further expands performance, user experience, and flexibility. To achieve these goals, not only in-depth improvements to new wireless access are required, but also major changes to the 5G core network. Among them, the most profound change is to use the Service Oriented Architecture (SOA) principle as the basis of the 5G service-based architecture (SBA) and apply it to control plane signaling. SOA defines the architectural principles for implementing distributed systems based on service orchestration. The basic concept of service-oriented architecture includes three components: service consumers, service providers, and service registries. Service providers provide services that are called by service users. The service registry is a searchable service contract repository that defines the properties and policies of different services exposed by a specific service provider. Service users query the service registry and discover services based on the provided service contracts. 3GPP specifies the REST-based service architecture as the blueprint for SBA. In the service-based architecture of the 5G core network, services are represented as network function services. A group of related network function services constitutes a network function (NF).
[0003] Adopting a service-oriented architecture is conducive to improving efficiency and is usually also conducive to ensuring security. However, in system design, openness and flexibility often conflict with security, privacy and performance requirements. A balance must be struck between promoting technological innovation and ensuring security and stability. Such a large-scale architectural reform means that the communication mode between network elements will be completely different from before, so new mechanisms are needed to meet the security requirements of modern mobile networks. Summary of the invention
[0004] The embodiments of the present application provide a communication method, a communication device, and a computer-readable storage medium. Through the embodiments of the present application, distributed authentication and information sharing of network service functions are realized, and the secure operation of network function registration, access, authorization and other functions is guaranteed.
[0005] In a first aspect of the present application, a communication method is provided. The method comprises: receiving a registration request from a network function device at a network registration function device, the registration request comprising an identity of the network function device; obtaining an encrypted identity of the network function device based on the identity of the network function device; encrypting the registration request of the network function device using a symmetric key of the network registration function device and a trusted environment device; and sending a transaction request to a distributed management device, the transaction request comprising a certificate of the network registration function device, an encrypted registration request, an encrypted identity of the network function device, and a signature of the network registration function device on the transaction request. In this way, the registration request of the network function device can be securely transmitted to the blockchain network.
[0006] In some embodiments, the registration request may also include at least one of the following: the type of the network function device; the identity of the network to which the network function device belongs; the address of the network function device; or the services supported by the network function device. Thus, the information of the network function device can be stored in the blockchain network and shared by different nodes.
[0007] In some embodiments, the transaction request may also include an identifier of the registration contract that the network registration function device requests to call, thereby enabling the distributed management device to call the registration contract according to the identifier.
[0008] In some embodiments, the method may further include: generating an identity credential for the network function device based on determining that the network function device is legitimate; and sending the identity credential to the network function device. Thus, the network function device has the authority to register in the blockchain network.
[0009] In some embodiments, the registration request received from the network function device may be a first registration request, and the method may further include: sending a second registration request to the authentication device, the second registration request including the identity of the network registration function device and the signature of the network registration function device; and receiving a certificate of the network registration function device from the authentication device. Thus, the network registration function device can be registered with the blockchain network.
[0010] In some embodiments, the method may further include: using the certificate to perform interactive authentication with the trusted environment device; and generating a symmetric key between the network registration function device and the trusted environment device. Thus, the network registration function device and the trusted environment device can use the symmetric key to encrypt or decrypt, thereby ensuring the security of communication.
[0011] In some embodiments, the method may further include: receiving a registration success message from the distributed management device; and sending a registration success message to the network function device. Thus, the network function device can confirm that the registration is successful in the blockchain network.
[0012] In a second aspect of the present application, a communication method is provided. The method includes: receiving a first transaction request from a network registration function device at a distributed management device, the first transaction request including a certificate of the network registration function device, an encrypted registration request of the network function device, an encrypted identity of the network function device, and a signature of the network registration function device on the transaction request; determining whether the signature is legitimate based on the certificate; and sending a second transaction request to a trusted environment device based on determining that the signature is legitimate, the second transaction request including the identity of the network registration function device, the encrypted registration request of the network function device, and the encrypted identity of the network function device. In this way, the distributed management device can verify the legitimacy of the transaction request and send the transaction request to the trusted environment for processing, thereby ensuring the security of the transaction.
[0013] In some embodiments, the first transaction request and the second transaction request may further include an identifier of the registration contract that the network registration function device requests to call, so that the distributed management device can call the registration contract according to the identifier.
[0014] In some embodiments, the method may further include: receiving a registration success message of the network function device from the trusted environment device; and sending the registration success message to the network registration function device. Thus, the distributed management device can call the registration contract according to the identifier.
[0015] In a third aspect of the present application, a communication method is provided. The method includes: receiving a transaction request from a distributed management device at a trusted environment device, the transaction request including the identity of a network registration function device, an encrypted registration request of the network function device, and an encrypted identity of the network function device; determining a symmetric key between the trusted environment device and the network registration function device based on the identity of the network registration function device; decrypting the encrypted registration request using the symmetric key; and in response to determining that the transaction request is valid based on the encrypted identity, adding the network function device and the services supported by the network function device to a registration list. In this way, the transaction request can be securely processed in a trusted environment, and secure registration of the network function device is achieved.
[0016] In some embodiments, the transaction request may also include an identifier of the registration contract that the network registration function device requests to call and a signature of the network registration function device on the transaction request. Thus, the registration contract can be called according to the identifier.
[0017] In some embodiments, the registration request may include at least one of the following: the identity of the network function device; the type of the network function device; the identity of the network to which the network function device belongs; the address of the network function device; or the services supported by the network function device. Thus, the information of the network function device can be stored in the blockchain network and shared by different nodes.
[0018] In some embodiments, the encrypted identity of the network function device included in the transaction request may be a first encrypted identity, and further includes: calling a registration contract based on an identifier of the registration contract; obtaining a second encrypted identity of the network function device based on the identity of the network function device; and determining that the transaction request is valid based on determining that the first encrypted identity is the same as the second encrypted identity. Thus, the legitimacy of the transaction request can be confirmed, and thus security can be guaranteed.
[0019] In some embodiments, the method may further include: sending a registration success message of the network function device to the distributed management device, so that the network function device can confirm that the registration is successful in the blockchain network.
[0020] In a fourth aspect of the present application, a communication method is provided. The method comprises: at a second network function device, sending a service token request to a network registration function device, the service token request including the identity of the second network function device, the identity of the network to which the second network function device belongs, the identity of the first network function device requested by the second network function device, the type of service of the first network function device requested by the second network function device, and the identity of the network to which the first network function device belongs; and receiving a decrypted service token from the network registration function device. In this way, the second network function device can request a service provided by another network function device from the blockchain network, reducing the complexity of the interaction.
[0021] In some embodiments, the method may further include: using the public key of the trusted environment device to determine whether the decrypted service token is legitimate; based on determining that the service token is legitimate, sending a service request to the first network function device, the service request includes the identity of the second network function device, the type of the second network function device, the identity of the network to which the second network function device belongs, the identity of the first network function device, the type of the first network function device, and the service token; and receiving a service response message from the first network function device. Thus, the service token request of the second network function device can be securely transmitted to the blockchain network.
[0022] In a fifth aspect of the present application, a communication method is provided. The method comprises: receiving a service token request from a second network function device at a network registration function device, the service token request comprising the identity of the second network function device, the identity of the network where the second network function device is located, the identity of the first network function device requested by the second network function device, the type of service of the first network function device requested by the second network function device, and the identity of the network where the first network function device is located; encrypting the service token request using a symmetric key of the network registration function device and a trusted environment device; and sending a transaction request to a distributed management device, the transaction request comprising the encrypted service token request, the certificate of the network registration function device, and the signature of the network registration function device on the transaction request. In this way, the service token request of the network function device can be securely transmitted to the blockchain network.
[0023] In some embodiments, the transaction request may also include an identifier of the authorization contract that the network registration function device requests to call, thereby enabling the distributed management device to call the registration contract according to the identifier.
[0024] In some embodiments, the method may further include: receiving an encrypted service token from the distributed management device; decrypting the encrypted service token using a symmetric key of the network registration function device and the trusted environment device; and sending the decrypted service token to the network function device. Thus, the service token can be securely transmitted to the network function device.
[0025] In a sixth aspect of the present application, a communication method is provided. The method includes: receiving a first transaction request from a network registration function device at a distributed management device, the first transaction request including an encrypted service token request of the network function device, a certificate of the network registration function device, and a signature of the network registration function device on the transaction request; determining whether the signature is legitimate based on the certificate; and sending a second transaction request to a trusted environment device based on determining that the signature is legitimate, the second transaction request including the identity of the network registration function device and the encrypted service token request. In this way, the distributed management device can verify the legitimacy of the transaction request and send the transaction request to the trusted environment for processing, thereby ensuring the security of the transaction.
[0026] In some embodiments, the first transaction request and the second transaction request may further include an identifier of the authorization contract that the network registration function device requests to invoke, so that the distributed management device can invoke the registration contract according to the identifier.
[0027] In some embodiments, the method may further include: receiving an encrypted service token from the trusted environment device; and sending the encrypted service token to the network registration function device. Thus, the service token can be transmitted securely.
[0028] In the seventh aspect of the present application, a communication method is provided. The method includes: receiving a transaction request from a distributed management device at a trusted environment device, the transaction request including the identity of a network registration function device and an encrypted service token request of a second network function device; determining the symmetric key between the network registration function device and the trusted environment device based on the identity of the network registration function device; decrypting the encrypted service token request based on the symmetric key; determining whether the first network function device provides the service requested by the second network function device based on the service token request; and generating a service token for the second network function device based on determining that the first network function device provides the service requested by the second network function device. In this way, the transaction request can be securely processed in a trusted environment, and secure authorization of network function devices can be achieved.
[0029] In some embodiments, the transaction request may also include an identifier of the authorization contract that the network registration function device requests to invoke, so that the registration contract can be invoked according to the identifier.
[0030] In some embodiments, the service token request may include at least one of the following: the identity of the second network function device; the identity of the network to which the second network function device belongs; the identity of the first network function device requested by the second network function device; the type of service of the first network function device requested by the second network function device; or the identity of the network to which the first network function device belongs. Thus, the second network function device can request a service provided by another network function device from the blockchain network, reducing the complexity of the interaction.
[0031] In some embodiments, the service token may include at least one of the following: the identity of the second network function device; the identity of the first network function device; the life cycle of the service token; or the signature algorithm of the trusted environment device. Thus, the second network function device can request the service provided by the first network function device by means of the service token.
[0032] In some embodiments, determining whether the first network function device provides the service requested by the second network function device may include: invoking the authorization contract based on the identifier of the authorization contract; obtaining the encrypted identity of the first network function device based on the identity of the first network function device; determining the registration information of the first network function device based on the encrypted identity of the first network function device to obtain the services supported by the first network function device; and determining whether the services supported by the first network function device include the type of service of the first network function device requested by the second network function device. Thus, the service requested by the second network function device can be compared with the service supported by the first network function device.
[0033] In some embodiments, the communication method further comprises: encrypting the service token using a symmetric key; and sending the encrypted service token to the distributed management device. Thus, the service token of the second network function device can be securely transmitted to the second network function device.
[0034] In an eighth aspect of the present application, a communication device is provided. The communication device includes a processor and a memory storing instructions. When the instructions are executed by the processor, the communication device executes any method according to any aspect of the first to seventh aspects and their implementations.
[0035] In a ninth aspect of the present application, a chip is provided, which includes a processing circuit configured to execute any method of any aspect from the first aspect to the seventh aspect and any implementation thereof.
[0036] In a tenth aspect of the present application, a computer-readable storage medium is provided. The computer-readable storage medium stores instructions, which, when executed by an electronic device, cause the electronic device to execute any method of any aspect from the first to the seventh aspect and any implementation thereof.
[0037] In an eleventh aspect of the present application, a computer program product is provided, which includes instructions, and when the instructions are executed by an electronic device, the electronic device executes any method of any aspect from the first aspect to the seventh aspect and any implementation thereof.
[0038] It should be understood that the contents described in the summary of the invention are not intended to limit the key or important features of the present application, nor are they intended to limit the scope of the present application. Other features of the present application will become easily understood through the following description. BRIEF DESCRIPTION OF THE DRAWINGS
[0039] Figure 1A A schematic diagram of a network environment in which embodiments of the present application can be implemented is shown.
[0040] Figure 1B A schematic diagram of a 5G core network reference point architecture related to an embodiment of the present application is shown.
[0041] Figure 1C A schematic diagram of a 5G core network service-oriented architecture related to an embodiment of the present application is shown.
[0042] Figure 1D A schematic diagram of a system architecture in which embodiments of the present application may be implemented is shown.
[0043] Figure 2 The diagram illustrates an interactive signaling diagram for service authorization according to some embodiments of the present application.
[0044] Figure 3An example process of service authorization according to some embodiments of the present application is illustrated.
[0045] Figure 4 The diagram illustrates an example process of service authorization using a public chain structure.
[0046] Figure 5 An example process of network function registration according to some embodiments of the present application is illustrated.
[0047] Figure 6 An example process of token request authorization and network function service access according to some embodiments of the present application is illustrated.
[0048] Figure 7 The diagram illustrates a schematic flow chart of a method implemented at a network registration function device according to an embodiment of the present application.
[0049] Figure 8 A schematic flow chart of a method implemented at a distributed management device according to an embodiment of the present application is shown.
[0050] Fig. 9 A schematic flow chart of a method implemented at a trusted environment device according to an embodiment of the present application is shown.
[0051] Fig.10 A schematic flow chart of a method implemented at a network function device according to an embodiment of the present application is shown.
[0052] Fig.11 The diagram illustrates a schematic flow chart of a method implemented at a network registration function device according to an embodiment of the present application.
[0053] Fig.12 A schematic flow chart of a method implemented at a distributed management device according to an embodiment of the present application is shown.
[0054] Fig.13 A schematic flow chart of a method implemented at a trusted environment device according to an embodiment of the present application is shown.
[0055] Fig.14 A simplified block diagram of an example device showing a possible implementation of an embodiment of the present application.
[0056] Fig.15 A simplified block diagram of an example device showing a possible implementation of an embodiment of the present application.
[0057] The same or similar reference numerals are used throughout the drawings to designate the same or similar components. DETAILED DESCRIPTION
[0058] The embodiments of the present application will be described in more detail below with reference to the accompanying drawings. Although certain embodiments of the present application are shown in the accompanying drawings, it should be understood that the present application can be implemented in various forms and should not be construed as being limited to the embodiments described herein. Instead, these embodiments are provided to provide a more thorough and complete understanding of the present application. It should be understood that the drawings and embodiments of the present application are only for exemplary purposes and are not intended to limit the scope of protection of the present application.
[0059] In the description of the embodiments of the present application, the term "including" and similar terms should be understood as open inclusion, that is, "including but not limited to". The term "based on" should be understood as "based at least in part on". The term "one embodiment" or "the embodiment" should be understood as "at least one embodiment". The terms "first", "second", etc. may refer to different or the same objects. Other explicit and implicit definitions may also be included below.
[0060] The embodiments of the present application may be implemented according to any appropriate communication protocol, including but not limited to cellular communication protocols such as third generation (3G), fourth generation (4G), fifth generation (5G) and future communication protocols (e.g., sixth generation (6G)), wireless local area network communication protocols such as Institute of Electrical and Electronics Engineers (IEEE) 802.11, and / or any other protocol currently known or developed in the future.
[0061] The technical solutions of the embodiments of the present application are applied to communication systems that follow any appropriate communication protocols, such as: General Packet Radio Service (GPRS), Global System for Mobile Communications (GSM), Enhanced Datarate for GSM Evolution (EDGE), Universal Mobile Telecommunications Service (UMTS), Long Term Evolution (LTE) system, Wideband Code Division Multiple Access (WCDMA), Code Division Multiple Access 2000 (CDMA2000), Time Division-Synchronization Code Division Multiple Access (TD-SCDMA), Frequency Division Duplex (FDD) system, Time Division Duplex (TDD), fifth generation (5G) system (e.g., New Radio (NR)) and future communication systems (e.g., sixth generation (6G) system), etc.
[0062] For the purpose of illustration, the embodiments of the present application are described below with the 5G communication system in 3GPP as the background. However, it should be understood that the embodiments of the present application are not limited to the communication system, but can be applied to any communication system with similar problems, such as wireless local area network (WLAN), wired communication system, or other communication systems developed in the future.
[0063] The term "terminal" or "terminal device" used in this application refers to any terminal device that can communicate with network devices or with each other by wire or wirelessly. Terminal devices may sometimes be referred to as user equipment or UE. Terminal devices may be any type of mobile terminal, fixed terminal or portable terminal. Terminal devices may be various wireless communication devices with wireless communication capabilities. With the rise of Internet of Things (IOT) technology, more and more devices that did not previously have communication capabilities, such as but not limited to household appliances, vehicles, tools and equipment, service equipment and service facilities, have begun to obtain wireless communication capabilities by configuring wireless communication units, so that they can access wireless communication networks and accept remote control. Such devices have wireless communication capabilities because they are configured with wireless communication units, and therefore also fall into the category of wireless communication devices. As an example, the terminal device may include a mobile cellular phone, a cordless phone, a mobile terminal (MT), a mobile station, a mobile device, a wireless terminal, a handheld device, a client, a subscription station, a portable subscription station, an Internet node, a communicator, a desktop computer, a laptop computer, a notebook computer, a tablet computer, a personal communication system device, a personal navigation device, a personal digital assistant (PDA), a wireless data card, a wireless modem (Modulator demodulator, Modem), a positioning device, a radio broadcast receiver, an e-book device, a gaming device, an IoT device, a vehicle-mounted device, an aircraft, a virtual reality (VR) device, an augmented reality (AR) device, a wearable device (for example, a smart watch, etc.), a terminal device in a 5G network or any terminal device in an evolved public land mobile network (PLMN), other devices that can be used for communication, or any combination of the above.
[0064] The term "network node" or "network device" used in this application is an entity or node that can be used to communicate with a terminal device, for example, it can be an access network device. The access network device can be a device deployed in a wireless access network to provide wireless communication functions for mobile terminals, for example, it can be a radio access network (RAN) network device. The access network device may include various types of base stations. The base station is used to provide wireless access services for terminal devices. Specifically, each base station corresponds to a service coverage area, and the terminal device entering the area can communicate with the base station through wireless signals to receive the wireless access service provided by the base station. There may be overlaps between the service coverage areas of the base stations, and the terminal device in the overlapping area can receive wireless signals from multiple base stations, so that multiple base stations can provide services for the terminal device at the same time. Depending on the size of the service coverage area provided, the access network device may include a macro base station providing a macro cell, a micro base station for providing a micro cell, a micro base station for providing a micro cell, and a micro base station for providing a micro cell. In addition, the access network equipment may also include various forms of relay stations, access points, remote radio units (RRU), radio heads (RH), remote radio heads (RRH), etc. In systems using different wireless access technologies, the names of access network equipment may be different, such as evolved NodeB (eNB or eNodeB) in the Long Term Evolution (LTE) network, NodeB (NB) in the 3G network, gNB or NR NB in the 5G network, and so on.
[0065] Figure 1A FIG. 1 is a schematic diagram of a network environment 100 in which embodiments of the present application may be implemented. Figure 1AAs shown, the system may include a network function device 110, two network registration function devices 120 and 130, two distributed management devices 140 and 150, and two trusted environment devices 160 and 170. In some embodiments, the network function device 110 may be implemented as a network function service consumer, the network registration function devices 120 and 130 may be implemented as network function storage functions NRF, the distributed management devices 140 and 150 may be implemented as distributed nodes Peer of the blockchain network, and the trusted environment devices 160 and 170 may be implemented as trusted computing environments TEE deployed on each Peer node. In some embodiments, the network registration function devices 120 and 130 may belong to different operators, and a network function device belonging to the same operator as the network registration function device 120 may request services provided by a network function device belonging to another operator. How to implement service authorization will be described in further detail below. It should be understood that Figure 1A The number shown in is only an example. In implementation, any appropriate number of devices may be included according to the scale and architecture of the network, and this application does not impose any limitation on this.
[0066] It should be understood that the communication system 100A can be applied to various scenarios. For example, the application scenarios of the communication system 100A include but are not limited to LTE systems, 5G systems or new wireless (New Radio, NR) and future communication systems, such as the sixth generation mobile communication system. The embodiments of the present application are not limited to this, and it should be understood that the above communication can follow any appropriate communication technology and corresponding communication standards. In addition, Figure 1A The device names involved are only examples and are not intended to be limiting. In future communication architectures, they may be implemented as devices with the same functions.
[0067] Figure 1B A schematic diagram of a 5G core network reference point architecture 100B related to an embodiment of the present application is shown. Logical entities with different interfaces and dependencies have been defined previously, and all network elements are decomposed into separate network functions. Each network element is interconnected through a point-to-point interface. This architectural design that continues the previous generations of mobile networks is called a reference point architecture. Figure 1BAs shown, the 5G core network reference point architecture 100B may include UE, (radio) access network (R) AN, User Plane Function (UPF), Data Network (DN), Access and Mobility Management Function (AMF), Session Management Function (SMF), Policy Control Function (PCF), Application Function (AF), Network Slicing Service Function (NSSF), Authentication Server Function (AUSF) and Unified Data Management (UDM). Each network function can only communicate with a network function with a specified reference point. For example, the UE can only send Non-Access Stratum (NAS) messages to the AMF, or send data and wireless signaling messages to the (R) AN.
[0068] The fifth generation of mobile communication systems further expands performance, user experience and flexibility. To achieve these goals, not only in-depth improvements to new wireless access are required, but also major changes to the 5G core network. Among them, the most profound change is to use service-oriented architecture principles as the basis for 5G SBA and apply them to control plane signaling. SOA defines architectural principles for implementing distributed systems based on service orchestration. The basic concept of service-oriented architecture includes three components: service consumers, service providers and service registries. Service providers provide services that are called by service users. The service registry is a searchable service contract repository that defines the properties and policies of different services exposed by a specific service provider. Service users query the service registry and discover services based on the provided service contracts. 3GPP specifies the service architecture based on Representation State Transfer (REST) as the blueprint for SBA. In the service-oriented architecture of the 5G core network, services are represented as network function services. A group of related network function services constitutes a network function (NF).
[0069] The main benefits of adopting a service-oriented architecture are threefold. First, telecom providers can rely on current mature business accumulation and rich tools to promote the creation of new services and accelerate future innovation. Second, by combining standardized and industry-proven technologies, it is possible to avoid defining a complete signaling protocol from scratch, which is not only conducive to improving efficiency but also generally conducive to ensuring security. Finally, the core network elements are decoupled into separate network function services and deployed as stateless services, and the service state is stored in the core network's unstructured data storage function (UDSF), which is also in line with the goals of network function virtualization (NFV). The service-oriented architecture should allow the network to adapt to changing loads while enabling operators to seamlessly manage and maintain increasingly diverse network function deployments. In general, the adoption of a service-oriented architecture has the following benefits: the ability to update production networks, scalability, modularity and reusability, and openness.
[0070] However, a key requirement of mobile network operators for 5G is to introduce new services and functions in a more flexible way, with minimal impact on other entities in the network, and comprehensive virtualization for cost-effective deployment. In the 5G service-based architecture (SBA), point-to-point interfaces are replaced by a common bus that connects all network functions, such as Figure 1C shown. Figure 1CA schematic diagram of a 5G core network service-oriented architecture related to an embodiment of the present application is shown. Control plane functions such as AUSF, AMF, SMF, NSSF, NEF, NRF, PCF, UDM, or AF use service-oriented interfaces to interact. For example, the service-oriented interface provided by AUSF to the outside is Nausf; the service-oriented interface provided by AMF to the outside is Namf; the service-oriented interface provided by SMF to the outside is Nsmf; the service-oriented interface provided by NSSF to the outside is Nnssf; the service-oriented interface provided by NEF to the outside is Nnef; the service-oriented interface provided by NRF to the outside is Nnrf; the service-oriented interface provided by PCF to the outside is Npcf; the service-oriented interface provided by UDM to the outside is Nudm; the service-oriented interface provided by AF to the outside is Naf. All control plane network functions in the 5G core network use REST-based services to provide one or more functions that can be discovered, requested, or subscribed to by other network functions. To achieve these goals, the 5G service-oriented architecture further defines two new functional entities: Network Registration Function (NRF) and Network Exposure Function (NEF). NRF provides network function service discovery, management, authorization and other functions. NEF exposes network function services from within the network to authorized external applications to adjust network configuration, monitor machine type communication equipment, etc.
[0071] During the service registration and deregistration phase, NRF records the available network function instances and supported services, and enables network functions to discover each other and the services they provide in the network. As a service registry, NRF also provides and maintains service contracts in network function instances represented by configuration files. Network functions can be divided into service consumers who request services and service producers who provide services. The network function service itself is defined as a capability that enables the network function to be open to another authorized network function through a service-based interface. Network function service authorization is performed by the service producer. The authorization of a service consumer is executed according to the policies negotiated by the network function, service operator, etc., and limits the types and sources of network functions that can access the services provided by the service producer.
[0072] The service-oriented architecture further changes the protocol stack on the basic IP connection between network functions. Unlike the Stream Control Transmission Protocol (SCTP) and DIAMETER protocols used in previous mobile networks, the control plane signaling in the 5G core network is built on the Transport Control Protocol (TCP) and Hypertext Transfer Protocol (HTTP / 2). In particular, the HTTP / 2 protocol plays a key role in network function services. Communication between network function services is achieved by calling the REST-based application programming interface (API) under the HTTP / 2 routing mechanism, and HTTP / 2 on TCP is used as the protocol for calling the API. Network elements in the access network, such as RAN and UE, and user-plane network function communication still use designated reference points. In the service-oriented architecture, the point-to-point interface in the reference point architecture is mapped to a service-based interface (SBI), and each network function provides a corresponding service-based interface for the network function as a service consumer to call the service. In order to specify the consistency of network functions, OpenAPI 3.0 is used as the service contract definition language for all service-based interfaces. The OpenAPI specification can be expressed as a Java-based data description format (Java Script Object Notation, JSON) object and provides a standardized way to specify API endpoints and application layer data contained in request and response messages.
[0073] However, it should be noted that in system design, openness and flexibility often conflict with security, privacy and performance requirements. A balance must be struck between promoting technological innovation and ensuring security and stability. Such a large-scale architectural reform means that the communication mode between network elements will be completely different from before, so new mechanisms are needed to meet the security needs of modern mobile networks.
[0074] The 5G core network adopts a service-oriented architecture design. All integrated network elements are replaced by network functions. Conventional 5G network function access authorization adopts an authorization scheme based on Oauth2.0. When dealing with large-scale cross-operator network function access and authorization scenarios, it will encounter a variety of security and efficiency issues. First, the 5G network introduces a border security agent (Security Edge Protection Proxy, SEPP) at the boundaries of each operator to clearly divide the security domain. However, cross-domain access to network functions requires SEPPs across two network domains, and related security operations and filtering are completed in SEPPs, such as data encryption, signing, or internal and external address mapping. These operations undoubtedly reduce the efficiency of cross-domain network access. Secondly, Internetwork Packet Exchange protocol (IPX) nodes may be introduced between SEPPs for transit transmission. IPX nodes can modify the content of the transmitted messages, thereby posing a security threat to point-to-point secure transmission. Finally, the traditional point-to-point cross-operator access authorization method will face serious efficiency issues in large-scale cross-domain network function access and authorization scenarios. For example, n operators need to maintain n(n-1) / 2 point-to-point access control policies, which is O(n2). 5G supports the deployment of small or even micro operators, which will greatly increase the base number of operators n, thus facing a larger and more complex point-to-point control strategy.
[0075] In view of this, an embodiment of the present application provides a communication method, which adopts blockchain technology and utilizes the distributed, decentralized, and tamper-proof characteristics of blockchain to design a secure and efficient cross-operator network function access authorization scheme. In this method, a network registration function device receives an identity registration request including a network function device from a network function device. Based on the identity of the network function device, the network registration function device obtains the encrypted identity of the network function device. The network registration function device encrypts the registration request of the network function device using a symmetric key with a trusted environment device. Subsequently, the network registration function device sends a transaction request to a distributed management device, and the transaction request includes a certificate of the network registration function device, an encrypted registration request, an encrypted identity of the network function device, and a signature of the network registration function device on the transaction request. The network registration function device also receives a service token request from a second network function device, and the service token request includes the identity of the second network function device, the identity of the network where the second network function device is located, the identity of the first network function device requested by the second network function device, the type of service of the first network function device requested by the second network function device, and the identity of the network where the first network function device is located. The network registration function device encrypts the service token request and then sends a transaction request to the distributed management device. The transaction request includes the encrypted service token request, the certificate of the network registration function device and the signature of the network registration function device on the transaction request.
[0076] In this way, a distributed trust relationship is established between multiple mutually distrustful operators, which reduces the point-to-point trust relationship structure of operators under the traditional core network structure and reduces the complexity of establishing trust between multiple operators. Functions such as network function registration and access authorization of the operator are deployed in the blockchain network, which can be automatically executed and ensure the credibility of the functions. Secure storage and cross-domain sharing of operator network function information are achieved. In order to make the purpose, technical solutions and advantages of this application clearer, the application will be further described in detail below in conjunction with the accompanying drawings. The specific operation methods, function descriptions, etc. in the method embodiments can also be applied to device embodiments or system embodiments.
[0077] Figure 1D A schematic diagram of a system architecture 100D in which an embodiment of the present application can be implemented is shown. The system architecture 100D is a cross-operator network function authorization and authentication framework based on alliance chain, which aims to improve the security, privacy and communication efficiency of cross-operator authorization, authentication and access of network functions with the help of alliance chain technology.
[0078] The network elements involved in the embodiments of the present application mainly include network function provider pNF, network function consumer cNF, access\registration network network function storage function vNRF\hNRF and blockchain management node. Network function provider pNF can provide network logic modules for specific network function services. Network function consumer cNF can access or call network function modules of other network function services. Access\registration network network function storage function vNRF\hNRF supports the functions of registration, discovery, authentication and access authorization of network function services, maintains the information of network function modules, and provides NF instance or NF IP address or corresponding identification. One or more blockchain management nodes are deployed in each shared land mobile network, which are responsible for the construction and maintenance of alliance chains, including the initialization of blockchain platforms, registration and management of blockchain applications, execution of consensus mechanisms and generation of blocks. Among them, the management nodes specifically include certification authority nodes, sorting service nodes Orderer, distributed nodes Peer and trusted computing environment TEE. The certification authority node provides user management services such as registration, identity authentication and certificate issuance of nodes in the alliance chain network. The sorting service node is responsible for sorting all received transactions and packaging them into blocks. Distributed nodes are endorsement nodes. They process transaction proposals according to endorsement policies, call smart contracts to process transaction proposals, and sign and endorse the execution results. Each Peer node saves a blockchain ledger (Ledger), which stores all confirmed transactions in the form of a hash chain. In addition, the Peer node also maintains a blockchain state information (State). The trusted computing environment TEE is a hardware secure computing environment deployed on each Peer node. It can create a secure and trusted execution environment on the Peer node, in which smart contracts can be deployed and executed, as well as secure processing of on-chain data.
[0079] The framework is applicable to cross-operator service scenarios involving two or more shared land mobile networks (PLMNs), such as Figure 1DAs shown, the system architecture 100D may include an access network vPLMN 181 and a home network hPLMN 182. The system architecture 100D may also include an NRF, which supports functions such as registration, authentication, discovery, and access authorization of network services, and may maintain available NF instances and NF profiles. To simplify the description, the embodiments of the present application only describe a case in which two NRF entities are included, namely, vNRF 183 in vPLMN 181 and hNRF 184 in hPLMN 182. The NFs maintained by the NRF include cNF 185 and pNF 186. The blockchain network in the system architecture 100D includes multiple blockchain management nodes, such as peer1 187, peer2 188, and peer2 189. The blockchain network supports registration and management of network function nodes, access control, authorization, automatic generation of access tokens, and identity authentication of NFs across operators, etc. The blockchain network in the system architecture 100D also includes a trusted computing environment (TEE), which is deployed on the blockchain management node to achieve secure storage of on-chain data and secure execution of smart contracts. The blockchain management node also includes an ordering service node 190.
[0080] In this system architecture, cNF 185 is registered in vNRF 183 of vPLMN 181, and pNF 186 is registered in hNRF 184 of hPLMN 182. NRF maintains a list of profiles of NF instances, including but not limited to NF instance identity (ID), NF type (Type), identity of home network (PLMN ID), NF fully qualified domain name (FQDN) or IP address, NF capability information (Capacity), NF priority information (Priority), etc. cNF 185 located in vPLMN 181 network sends a service discovery request to the local NRF, i.e., vNRF 183, to query the network function instances in the local or other networks (e.g., hPLMN 184). In the present invention, in order to simplify the process, we assume that cNF 185 wants to access the network services provided by the network function provider pNF of another operator network hPLMN 182. Since cNF 185 and pNF 186 are registered in different network PLMNs, there is no trust relationship between cNF 185 and pNF 186. Therefore, cNF 185 needs to establish a trust relationship with pNF 186 and call the network services provided by pNF 186 through the authentication and authorization services of vNRF 183 and hNRF 184. vNRF 183 and hNRF 184 authenticate and authorize cNF 185 and issue an access authorization token to it. cNF 185 requests to access the services provided by pNF 186 by presenting the access authorization token to pNF 186. pNF 186 provides the corresponding network services to the network function consumer by verifying the identity of cNF 185 and the access authorization token.
[0081] In this system architecture, two mobile operator networks are connected to a blockchain network, which is responsible for cross-domain discovery, identity authentication, access authorization and other functions of network functions. The smart contract (chain code) deployed in the blockchain system realizes the automatic authentication and authorization of access, and generates the corresponding access token for the network function service requester. At the same time, the blockchain system uses the consensus mechanism to generate blocks, record the system's cross-domain access control information, and realize cross-domain sharing and synchronization of access authorization information. In order to realize the secure storage and confidential calculation of network function information in the operator's network, this system deploys a trusted execution environment (TEE) in the management node (such as Peer node) in the blockchain system, and deploys related smart contract applications in the trusted execution environment. These smart contracts running in the TEE can safely execute user registration, access authorization and other functions, and can encapsulate the operation results in ciphertext form, generate blocks, and finally store them in the blockchain ledger.
[0082] Figure 2The interactive signaling diagram of service authorization according to some embodiments of the present application is illustrated. For the sake of clarity and without any limitation, process 200 will be combined with Figure 1A In this implementation, the network function device 110 is implemented as the second network function device 201, the network registration function device 120 is implemented as the network registration function device 202, the network registration function device 130 is implemented as the network registration function device 205, the distributed management device 140 is implemented as the distributed management device 203, the distributed management device 150 is implemented as the distributed management device 206, the trusted environment device 160 is implemented as the trusted environment device 204, and the trusted environment device 170 is implemented as the trusted environment device 207.
[0083] In process 200, a network registration function device 202 receives (211) a registration request from a first network function device, the registration request including an identity of the first network function device. For example, the network registration function device 202 may be a network function storage device hNRF in a home network hPLMN, and the first network function device may be a network function provider pNF. Based on the identity of the first network function device, the network registration function device 202 obtains (213) an encrypted identity of the first network function device. For example, the network registration function device 202 may perform a hash calculation on the identity (ID) of the first network function device to obtain the encrypted identity of the first network function device. The network registration function device 202 encrypts the registration request of the first network function device using (215) a symmetric key between the network registration function device 202 and the trusted environment device 204. The symmetric key refers to a session key negotiated between the network registration function device 202 and the trusted environment device 204. Subsequently, the network registration function device 202 sends (217) a transaction request 219 to the distributed management device 203, the transaction request 219 including the network registration function device's certificate, the encrypted registration request, the encrypted identity of the first network function device, and the network registration function device 202's signature on the transaction request 219. The transaction request 219 is a transaction proposal for the registration request of the first network function device.
[0084] In some embodiments, the registration request may also include the type of the first network function device, the identity of the network to which the first network function device belongs, the address of the first network function device, the services supported by the first network function device, or a combination of one or more of the above. In some embodiments, the transaction request 219 also includes the identifier of the registration contract requested to be called by the network registration function device 202. The registration contract may be a smart contract deployed in a trusted execution environment, which can securely execute the user's registration, and can encapsulate the operation results in ciphertext form, generate blocks, and finally store them in the blockchain ledger.
[0085] In some embodiments, based on determining that the first network function device is legitimate, the network registration function device 202 can generate an identity credential for the first network function device and send the identity credential to the first network function device. That is, after receiving the registration request, the network registration function device 202 will verify the legitimacy of the first network function device, generate an identity credential or certificate for the legitimate first network function device, and send it back to the first network function device through a secure channel. In some embodiments, the network registration function device 202 can send a second registration request to the authentication device, and the second registration request includes the identity of the network registration function device 202 and the signature of the network registration function device 202. The authentication device can be a certification authority (CA) included in the alliance chain network, which is responsible for generating basic system parameters, managing node identities, and generating corresponding identity certificates (Credential) for nodes. The certificate can be used for functions such as identity authentication and access authorization of nodes in the system. CA verifies the identity of the operator and the network registration function device, generates a public-private key pair for them, and sends the public-private key pair to the network registration function device through a secure channel. After successful authentication, the network registration function device 202 receives the certificate of the network registration function device 202 from the authentication device. In some embodiments, the network registration function device 202 uses the certificate to perform interactive authentication with the trusted environment device 204, and generates a symmetric key between the network registration function device 202 and the trusted environment device 204. For example, the network registration function device 202 can authenticate the trusted environment device 204 on the alliance chain management node through remote authentication.
[0086] Continue to refer Figure 2 The distributed management device 203 receives (221) a transaction request 219 from the network registration function device 202, the transaction request 219 including the certificate of the network registration function device 202, the encrypted registration request of the first network function device, the encrypted identity of the first network function device and the signature of the network registration function device 202 on the transaction request 219.
[0087] The distributed management device 203 determines (223) whether the signature is legitimate based on the certificate. For example, the distributed management device 203 can obtain the public key of the network registration function device 202 based on the certificate of the network registration function device 202, and then use the public key to verify the legitimacy of the transaction request. Based on determining that the signature is legitimate, the distributed management device 203 sends (225) a transaction request 227 to the trusted environment device 204. The transaction request 227 includes the identity of the network registration function device 202, the encrypted registration request of the first network function device, and the encrypted identity of the first network function device. In some embodiments, the transaction request 219 and the transaction request 227 also include the identification of the registration contract that the network registration function device 202 requests to call.
[0088] Accordingly, the trusted environment device 204 receives (229) the transaction request 227 from the distributed management device 203. Based on the identity of the network registration function device 202, the trusted environment device 204 determines the symmetric key between the trusted environment device 204 and the network registration function device 202. The trusted environment device 204 uses (233) the symmetric key to decrypt the encrypted registration request. For example, the trusted environment device 204 can obtain the registration information of the network function device by decrypting the encrypted registration request using the symmetric key. The trusted environment device 204 obtains the identity of the network function device from the registration information of the network function device. After the trusted environment device 204 determines that the transaction request 227 is valid based on the encrypted identity, the first network function device and the services supported by the first network function device are added (251) to the registration list. For example, the trusted environment device 204 can search the local ledger based on the encrypted identity, and if the encrypted identity entry of the network function device is not retrieved, a new key value entry is created, and if the encrypted identity entry is retrieved, the key value is updated. If the creation or update is completed, the chain code running status is returned, and the encrypted key value entry is returned.
[0089] In some embodiments, the encrypted identity of the first network function device included in the transaction request 227 may be a first encrypted identity, and the trusted environment device 204 may also call the registration contract based on the identifier of the registration contract. Based on the identity of the first network function device, the trusted environment device 204 obtains the second encrypted identity of the first network function device. For example, the trusted environment device 204 may perform a hash calculation on the identity of the first network function device to obtain the second encrypted identity of the first network function device. The trusted environment device 204 compares the second encrypted identity with the first encrypted identity included in the transaction request 227. If the first encrypted identity is the same as the second encrypted identity, the trusted environment device 204 determines that the transaction request 227 is valid.
[0090] In some embodiments, the trusted environment device 204 may send a registration success message of the first network function device to the distributed management device 203. Additionally, the distributed management device 203 may receive a registration success message of the first network function device from the trusted environment device 204, and send the registration success message to the network registration function device 202. Alternatively, the network registration function device 202 may receive a registration success message from the distributed management device 203, and then the network registration function device 202 may send the registration success message to the first network function device. In some examples, the distributed management device 203 generates a proposal reply based on the results and output of the execution of the smart contract of the trusted environment device 204, and returns it to the network registration function device 202. The network registration function device 202 submits the collected proposal replies to the sorting service node for global transaction sorting according to the endorsement mechanism, and finally broadcasts them to all distributed management devices for confirmation. If the confirmation is successful, the distributed management device writes the transaction into the local ledger. At this point, the network function device registration and information security storage are completed.
[0091] Continue to refer Figure 2 , the second network function device 201 sends (253) a service token request 255 to the network registration function device 205, the service token request 255 including the identity of the second network function device 201, the identity of the network to which the second network function device 201 belongs, the identity of the first network function device requested by the second network function device 201, the type of service of the first network function device requested by the second network function device 201, and the identity of the network to which the first network function device belongs. The second network function device 201 may be a network function consumer cNF in a visited network vPLMN, and the network registration function device 205 may be a network function storage device vNRF in a visited network vPLMN. For example, the cNF discovers a network function service pNF provided by another network operator (e.g., hPLMN) through a service discovery function. When the cNF requests the service of the pNF in the hPLMN network for the first time, it shall request an access token (Access Token) from the network where the pNF is located. The cNF first sends a token request message to the vNRF in the network vPLMN where it is located.
[0092] Accordingly, the network registration function device 205 receives (257) a service token request 255 from the second network function device 201. The network registration function device 205 encrypts (259) the service token request 255 using the symmetric key of the network registration function device 205 and the trusted environment device 207. Subsequently, the network registration function device 205 sends (263) a transaction request 261 to the distributed management device 206, and the transaction request 261 includes the encrypted service token request, the certificate of the network registration function device 205, and the signature of the network registration function device 205 on the transaction request 261. Additionally, the transaction request 261 may also include the identifier of the authorization contract that the network registration function device 205 requests to invoke. For example, the network registration function device 205 packages the encrypted service token request, the identity of the network registration function device 205, the invoked smart contract, and the signature of the network registration function device 205 on the transaction proposal as a payload into the transaction request 261. After the network registration function device 205 signs the transaction proposal, it sends the transaction proposal to the corresponding distributed management device 206 according to the endorsement mechanism and calls the smart contract.
[0093] The distributed management device 206 receives (265) a transaction request 261 from the network registration function device 205. The distributed management device 206 determines whether the signature is legitimate based on the certificate. If the signature is legitimate, the distributed management device 206 sends (269) a transaction request 271 to the trusted environment device 207, and the transaction request 271 includes the identity of the network registration function device 205 and an encrypted service token request. Additionally, the transaction request 261 and the transaction request 271 also include the identifier of the authorization contract that the network registration function device 205 requests to call. In some examples, after receiving the transaction proposal, the distributed management device 206 obtains the public key of the network registration function device 205 based on the certificate of the network registration function device 205, and then uses the public key to verify the legitimacy of the transaction proposal. If the verification is successful, the distributed management device 206 sends the transaction proposal to the trusted environment device 207 to execute the authorization contract.
[0094] Accordingly, the trusted environment device 207 receives (273) the transaction request 271 from the distributed management device 206. Based on the identity of the network registration function device 205, the trusted environment device 207 determines (275) the symmetric key between the network registration function device 205 and the trusted environment device 207. After obtaining the symmetric key, the trusted environment device 207 decrypts (279) the encrypted service token request based on the symmetric key. Based on the service token request, the trusted environment device 207 determines (281) whether the first network function device provides the service requested by the second network function device 201. If the first network function device provides the service requested by the second network function device 201, the trusted environment device 207 generates (283) a service token for the second network function device 201.
[0095] In some embodiments, the service token may include the identity of the second network function device 201 , the identity of the first network function device, the lifecycle of the service token; or the signature algorithm of the trusted environment device 207 .
[0096] In some embodiments, in order to determine whether the first network function device provides the service requested by the second network function device 201, the trusted environment device 207 may call the authorization contract based on the identifier of the authorization contract. Based on the identity of the first network function device, the trusted environment device 207 may obtain the encrypted identity of the first network function device. Based on the encrypted identity of the first network function device, the trusted environment device 207 may determine the registration information of the first network function device to obtain the services supported by the first network function device. The trusted environment device 207 may determine whether the services supported by the first network function device include the type of the service of the first network function device requested by the second network function device 201.
[0097] In some embodiments, after generating the service token, the trusted environment device 207 may encrypt the service token using a symmetric key and send the encrypted service token to the distributed management device 206. Additionally, the token may be first signed by the trusted environment device 207 using its private key and encrypted using a symmetric key, and then sent to the distributed management device 206. Alternatively, the trusted environment device 207 may encrypt the network function device service access record and the token generation record and return them to the distributed management device 206. Accordingly, the distributed management device 206 may receive the encrypted service token from the trusted environment device 207 and send the encrypted service token to the network registration function device 205. The network registration function device 205 receives the encrypted service token from the distributed management device and decrypts the encrypted service token using a symmetric key. Additionally, after receiving the service token, the network registration function device 205 sends the collected transactions to the sorting service device for sorting according to the endorsement mechanism. The sorting service device broadcasts the block after sorting. After receiving the block, the distributed management device verifies the transaction. If the verification is successful, the block containing the access request and token generation record is written into the local ledger and the global status is updated.
[0098] Subsequently, the network registration function device 205 sends the decrypted service token to the second network function device 201. Correspondingly, the second network function device can receive the decrypted service token from the network registration function device 205. The second network function device 201 uses the public key of the trusted environment device 207 to determine whether the decrypted service token is legal. If the service token is legal, the second network function device 201 sends a service request to the first network function device, and the service request includes the identity of the second network function device 201, the type of the second network function device 201, the identity of the network to which the second network function device 201 belongs, the identity of the first network function device, the type of the first network function device, and the service token. Additionally, the second network function device 201 can receive a service response message from the first network function device. For example, after receiving the service request message from the cNF, the pNF can use the public key of the trusted environment device to verify the service token. If the verification is successful, the pNF verifies the service request parameters of the cNF, and returns a service response message to the cNF and provides the service if the verification is successful. If the verification fails, a failure is returned.
[0099] In this way, the complexity of establishing trust between multiple operators' networks is reduced. Network function registration and access authorization and other functions are deployed on the blockchain network, which can be automatically executed and ensure the credibility of the functions. At the same time, contract technology can realize the rapid deployment and update of system functions. Trusted environment equipment realizes the secure storage and cross-domain sharing of operator network function information, providing confidentiality and integrity protection for the execution of smart contracts.
[0100] Further, for the sake of clarity, reference will be made to Figure 3 and Figure 4 To describe two specific implementation methods of service authorization.
[0101] Figure 3 The example process of service authorization according to some embodiments of the present application is illustrated, which can be considered as Figure 2 For the sake of clarity and without any limitation, process 300 will be combined with Figure 1A In this implementation, the network function device 110 is implemented as NF_k 301, the network registration function device 120 is implemented as NRF_i 304, the network registration function device 130 is implemented as NRF_m 303, the distributed management device 140 and the distributed management device 150 are implemented as Peer_j 305, and the trusted environment device 160 and the trusted environment device 170 are implemented as TEE_j 306. It should be understood that Peer_j 305 can be two distributed management devices. For the convenience of description, Figure 3 Only one distributed management device is shown in FIG. Similarly, TEE_j 306 can be two trusted environment devices. Figure 3 Only one trusted environment device is shown.
[0102] Process 300 is a network function authorization framework based on the alliance chain network and TEE. In process 300, after the blockchain system is started, TEE_j 306 is initialized (310), generates public and private keys and obtains the certificate Cert (PK_tee_j, SK_tee_j) from the certification authority CA, (PK_tee_j, SK_tee_j) is the public and private key pair generated by CA for TEE_j 306. TEE_j 306 deploys the network function management smart contract jointly signed by the operator, and the functions include network function registration, update, deletion, etc. After that, the network element of an operator starts to use the system for network element authorization management.
[0103] NRF_i 304 initiates (312) a registration request to CA308, and the registration request provides the identity NRF_ID of NRF_i 304, the public key and signature of NRF_i 304. CA308 generates (314) a certificate Cert_nrfi for NRF_i 304, and returns (316) the NRF_i certificate Cert_nrfi to NRF_i 304. After receiving the certificate, NRF_i 304 uses the certificate to interact with TEE_j 306 for authentication. After successful authentication, NRF_i 304 and TEE_j 306 generate (320) a symmetric key Kij.
[0104] A network function network element NF_i 302 of the operator initiates (322) a registration request to the network registration network element NRF_i 304 of the operator, and the registration request includes the network ID (PLMN_ID) of the operator, the identity ID_i of NF_i 302, the type NF_Type of NF_i 302, the service list provided by NF_i 302, etc. NRF_i 304 performs (324) a hash operation on the received identity ID_i of NF_i 302 to generate PID_i, i.e. NRF_i 304 uses the symmetric key Kij to encrypt (326) the registration request, that is, CT_nfi = Enc (ID_i, PLMN_ID, NF_type, service list). NRF_i 304 sends (328) the registration request to the blockchain node Peer_j 305 by calling the smart contract. The registration request includes the certificate Cert_nrfi of NRF_i 304, the generated ciphertext CT_nfi, and the signature generated using the private key corresponding to Cert_nrfi.
[0105] After receiving the registration request from NRF_i 304, Peer_j 305 verifies the above signature using Cert_nrfi (330). After the verification is passed, Peer_j 305 runs (332) the smart contract, and the contract parameters include NRF_ID of NRF_i 304 and ciphertext CT_nfi. TEE_j 306 queries and obtains the symmetric key Kij based on the NRF_ID of NRF_i 304, and decrypts (334) CT_nfi. TEE_j 306 adds NF_i 302 and its service list to the registration list (336). TEE_j 306 returns (338) a registration success message to NF_i 302 through entities such as Peer_j 305 and NRF_i304.
[0106] A network function NF_k 301 from another operator sends (340) a service token request to the network registration function NRF_m 303 of the operator, the service token request including the identity information of NF_k 301, specifically including the ID_k of NF_k 301, the type of NF_i 302, the PLMN_ID to which NF_k 301 and NF_i 302 belong respectively, and the requested service type.
[0107] Based on the request, NRF_m 303 generates a service request token, encrypts the token, and then sends (342) a token request to a blockchain node, such as Peer_j 305, which includes a signature provided by NRF_m 303. Blockchain node Peer_j 305 verifies (344) the signature of the request. Peer_j 305 calls (346) the smart contract deployed in TEE_j306 and sends the received encrypted token request and NRF_ID of NRF_m 303 to TEE_j306.
[0108] TEE_j 306 obtains the corresponding decryption key according to the NRF_ID of NRF_m 303 and decrypts the token request (348). TEE_j 306 executes (350) the smart contract and obtains the authorization token of NF_k 301. TEE_j 306 returns (352) the encrypted NF_k 301 access authorization token to NRF_m 303 through Peer_j305. NRF_m 303 decrypts the token and sends (354) the decrypted token to the requesting party NF_k 301.
[0109] Process 300 uses the alliance chain as a blockchain platform to implement distributed registration of network functions, access authorization and other functions, and supports cross-domain secure access to network functions. A trusted execution environment is used to implement secure storage and processing of network function registration information, as well as secure and trusted operation of functions such as user registration and access authorization, protecting data privacy and system credibility. Smart contracts are used to implement automated operation of user registration and access authentication and authorization functions, reducing the communication overhead of cross-domain operations between operator networks. Thus, the service-oriented architecture is combined with the blockchain system, and TEE is used to protect smart contracts with authorization functions, ensuring the openness, transparency, and auditability of the system.
[0110] Figure 4 The diagram shows an example process of service authorization using a public chain structure. Unlike process 3 which uses a consortium chain, process 400 uses a public chain structure. Therefore, an open smart contract needs to be deployed on the public chain, which will call the smart contract in the TEE deployed on the Worker or oracle to generate an authorization token. The open contract is deployed on the public chain (Ethereum). Anyone can call this open contract, which acts as a list, recording all Workers and the addresses of the privacy smart contracts deployed in the Worker, and sending a contract call request. The Worker is a blockchain node and has a privacy contract in its TEE. Workers jointly build a distributed network. The addition of new workers requires mutual authentication and sharing of session keys. Worker_j 407
[0111] In process 400 , after the blockchain system is started, TEE_j 406 is initialized ( 410 ), generates public and private keys, and obtains a certificate Cert (PK_tee_j, SK_tee_j) from a certification authority CA, where (PK_tee_j, SK_tee_j) is a public and private key pair generated by the CA for TEE_j 406 .
[0112] NRF_i 404 initiates (412) a registration request to CA 408, and the registration request provides the identity NRF_ID of NRF_i 404, the public key and signature of NRF_i 404. CA 408 generates (414) a certificate Cert_nrfi for NRF_i 404, and returns (416) the NRF_i certificate Cert_nrfi to NRF_i 404. After receiving the certificate, NRF_i 404 uses the certificate to interact with TEE_j 407 for authentication. After successful authentication, NRF_i 404 and TEE_j 406 generate (420) a symmetric key Kij. The smart contract is deployed (422) on TEE_j 406.
[0113] A network function network element NF_i 402 of the operator initiates (424) a registration request to the network registration network element NRF_i 404 of the operator, and the registration request includes the network ID (PLMN_ID) of the operator, the identity ID_i of NF_i 402, the type NF_Type of NF_i 402, the service list provided by NF_i 402, etc. NRF_i 404 performs (426) a hash operation on the received identity ID_i of NF_i 402 to generate PID_i, i.e. NRF_i 404 encrypts (428) the registration request using the symmetric key Kij, i.e., CT_nfi=Enc(ID_i, PLMN_ID, NF_type, service list). NRF_i 404 sends (430) the registration request to the open contract 405, the registration request including the certificate Cert_nrfi of NRF_i 404, the generated ciphertext CT_nfi, and the signature generated using the private key corresponding to Cert_nrfi.
[0114] After receiving the registration request from NRF_i 404, the open contract 405 verifies the above signature using Cert_nrfi (432). After the verification is passed, the open contract 405 calls (434) the smart contract, and the contract parameters include the NRF_ID of NRF_i 404 and the ciphertext CT_nfi. TEE_j 407 deployed on Worker_j 406 queries and obtains the symmetric key Kij according to the NRF_ID of NRF_i 404, and decrypts (436) CT_nfi. TEE_j 407 adds NF_i 402 and its service list to the registration list (438). TEE_j 407 returns (440) a registration success message to NF_i 402 through the open contract 405, NRF_i 404 and other entities.
[0115] The network function NF_k 401 from another operator sends (442) a service token request to the network registration function NRF_m 403 of the operator, and the service token request includes the identity information of NF_k 401, specifically including the ID_k of NF_k 401, the type of NF_i402, the PLMN_ID to which NF_k 401 and NF_i 402 belong respectively, and the requested service type.
[0116] NRF_m 403 generates a service request token based on the request, encrypts the token, and then sends (444) a token request to the open contract 405, the token request including a signature provided by NRF_m 403. The open contract 405 verifies (446) the signature of the request. The open contract 405 calls (448) the smart contract and sends the received encrypted token request and the NRF_ID of NRF_m 403 to TEE_j 407.
[0117] TEE_j 407 obtains the corresponding decryption key according to the NRF_ID of NRF_m 403 and decrypts (450) the token request. TEE_j 407 executes (452) the smart contract and obtains the authorization token of NF_k 401. TEE_j 407NRF_m403 returns (454) the encrypted NF_k 401 access authorization token. NRF_m 403 decrypts the token and sends (456) the decrypted token to the requesting party NF_k 401.
[0118] In this way, process 400 uses the public chain as a blockchain platform to implement distributed registration, access authorization and other functions of network functions, and supports cross-domain secure access to network functions.
[0119] Specifically, the service authorization process may include system initialization, trusted environment initialization, network function registration, service request authorization, and service access.
[0120] During the system initialization process, the two mobile operator networks, namely the access network vPLMN and the home network hPLMN, jointly initialize a blockchain network. The blockchain network includes a certification authority CA, which is responsible for generating basic system parameters, managing the identities of all system nodes, and generating corresponding identity certificates (Credential) for the nodes. The certificate can be used for functions such as identity authentication and access authorization of nodes within the system. The network function storage function nodes vNRF and hNRF in the core networks of the two operators are registered with the certification authority CA respectively. CA verifies the identities of vNRF and hNRF, and generates a public-private key pair (PK vNRF , S.K. vNRF ) and (PK hNRF , S.K. hNRF), and send the public and private key pairs to vNRF and hNRF through a secure channel. The blockchain network contains two peer nodes, Peer1 and Peer2, a sorting service node and a confidential channel. vNRF and hNRF are associated with two peer nodes respectively. The peer node is responsible for transaction endorsement, signature and execution of smart contracts (chain code); the sorting service node is responsible for packaging blocks and synchronizing ledgers; the two networks involved in the authorization process should belong to the same channel, that is, the peer node corresponding to vNRF and the peer node corresponding to hNRF execute the authorization process in the same channel.
[0121] During the initialization of the trusted computing environment, Peer1 and Peer2 respectively initialize an enclave locally, namely TEE1 and TEE2, to deploy and securely run smart contracts. i ,(i=1,2) According to the preset secure boot procedure, a pair of public and private key pairs (PK TEEi ,SK TEEi ), public key PK TEEi It is made public to other nodes in the system and serves as the unique identifier of this enclave. The operators vPLMN and hPLMN jointly formulate two smart contracts, namely the network function registration contract (NFRegistration Contract) and the network service request authorization contract (Request Authorization Contract), and deploy them in the enclave. These two smart contracts respectively stipulate the corresponding endorsement policies, as well as network function registration and network function access authorization, that is, the generation of access tokens and other functions.
[0122] vNRF and hNRF remotely authenticate the enclave TEE of the Peer node i Authentication is performed. If the authentication is successful, the TEE i Negotiate a symmetric key as the session key sk ij .
[0123] During the network function registration process, a network function NF in the operator's network i , to its network function storage function node NRF i Send a registration request NFRegister_Request, which contains the network function NF i Instance identity Network Function NF i Types Home network ID PLMN ,NF i Address Network Function NF i List of supported network function services The specific process is as follows: Figure 8 shown.
[0124] Network storage function node NRF i After receiving the registration request, verify the NF i The legitimacy of the network and the generation of identity credentials for legitimate network functions, namely public-private key pairs And send it back to NF through a secure channel i NF i Save the identity credentials locally.
[0125] Network storage function node NRF i Network Function NF i Instance identity Perform hash operation to generate hidden identity, that is and use the session key sk ij Encrypt the user registration information, that is, NRF i According to the endorsement mechanism, a transaction proposal is sent to the endorsement node Peer in the alliance chain to execute the user network function registration smart contract (NFRegistration Contract). The transaction proposal contains the network storage function node identity NRF i , Network Function NF i Hidden identity The smart contract ID to be called, the encrypted registration information and NRF i A signature for its transaction proposal.
[0126] According to the endorsement mechanism, the Peer that receives the transaction proposal i First use NRF i The public key verifies the legitimacy of the proposal. If the verification is successful, Peer j The node sends the transaction proposal to the local TEE through the TEE dedicated interface i .TEE i After receiving the transaction proposal, use the NRF i The session key sk ij Ciphertext Decrypt and obtain NF i Registration information of TEE. i Call the network function to register the smart contract and obtain Perform hash operation to obtain hidden identity And compare it with the hidden identity in the transaction proposal to determine the validity of the proposal. Search the local ledger, if not found Then create a new key-value entry (Key-Value), where Key is Value is in Among them, SealK i Trusted Computing Environment TEE i If the wrapping key is retrieved If the creation or update is completed, the chain code running status True is returned, and the encrypted key value entry is returned, that is,
[0127] Peer node based on TEE i The results and outputs of smart contract execution generate proposal responses and return them to NRF i .NRF i According to the endorsement mechanism, the collected proposal replies are submitted to the sorting service node Orderer for global transaction sorting, generating blocks, and broadcasting the blocks to all Peer nodes for confirmation. If the confirmation is successful, the Peer node writes the block into the local ledger. i Registration is complete and your information is saved securely.
[0128] Figure 5 The diagram shows the network function registration process, which can be considered as Figure 2 For the sake of clarity and without any limitation, process 500 will be combined with Figure 1A In this implementation, the network registration function device 120 is implemented as NRF_i 502 , the distributed management device 140 is implemented as Peer 503 , and the trusted environment device 160 is implemented as enclave 504 .
[0129] In process 500, NF_i 501 sends (510) a registration request to NRF_i 502. NRF_i 502 verifies (512) the legitimacy of NF_i 501 and generates a public-private key pair for NF_i 501. Based on the identity of NF_i 501, NRF_i 502 generates a hidden identity PID of NF_i 501. NRF_i 502 encrypts the registration information of NF_i 501 and sends (514) a transaction proposal to Peer 503, where the transaction proposal includes the registration request of NF_i 501. Peer 503 verifies (516) the transaction proposal, and upon successful verification, calls (518) the smart contract in enclave 504. After receiving the transaction proposal, enclave 504 executes (520) the user registration smart contract. Enclave 504 returns (522) the registration result to NRF_i 502. After receiving the registration request, NRF_i 502 sends (524) the sorting request to the sorting service node 505, which then performs global sorting, generates a new block and broadcasts (526) it to Peer 503. Peer 503 sends (528) a registration success message to NRF_i 502, and NRF_i 502 returns (530) a registration success message to NF_i 501.
[0130] In the service request authorization, a network function consumer cNF in the vPLMN discovers a network function service pNF provided by another network operator hPLMN through the service discovery function. When the cNF requests the service of the network function provider pNF in the network of another network operator hPLMN for the first time, it needs to obtain an access token (Access Token). The cNF first sends a token request message (AccessToken_Get_Request) to the vNRF in the network vPLMN where it is located. The message contains the instance identity ID of the cNF cNF , ID of the network where the cNF is located vPLMN , the ID of the expected service provider pNF , expect the service NF type Type pNF , the ID of the network where the pNF is located hPLMN vNRF uses the session key sk corresponding to the TEE execution environment ijThe token request message is encrypted to generate a ciphertext message, and the ciphertext message is packaged as a transaction proposal as a payload to call the calling smart contract (RequestAuthorization Contract) deployed in the TEE environment. After vNRF signs the transaction proposal, it sends the transaction proposal to the corresponding Peer node according to the endorsement mechanism and calls the smart contract (Request Authorization Contract). The transaction proposal contains the network storage function node identity ID vNRF , the smart contract ID to be called, the encrypted token request information, and the vNRF signature on the transaction proposal.
[0131] After receiving the transaction proposal, the Peer node uses the vNRF public key to verify the legitimacy of the transaction proposal. If the verification is successful, the Peer node sends the transaction proposal to the smart contract (Request Authorization Contract) in the enclave TEE for execution. TEE first uses the session key sk ij Decrypt the token request message to obtain the instance identity information ID of the cNF cNF , ID of the network where the cNF is located vPLMN , the ID of the expected service provider pNF , expect the service NF type Type pNF , the ID of the network where the pNF is located hPLMN Then, TEE calculates the hidden identity of the expected service provider, i.e. PID pNF =Hash(ID pNF ), and according to PID pNF Retrieve the local ledger and extract the registration information of pNF TEE decryption Get the service support list of pNF, compare the service request information of cNF with the service support list of pNF, and determine whether the cNF consumer can obtain the service provided by the pNF provider. If satisfied, generate an access token for cNF. The access token defines the signature algorithm, service consumer cNF, service producer pNF, token life cycle and other attributes. Among them, the token is first generated by TEE using its private key SK TEE Sign and use the session key sk ijIt is encrypted and then sent to the peer node. In addition, TEE encrypts the cNF service access record and token generation record and returns them to the Peer node. The Peer node generates a proposal response based on the output of TEE and returns it to vNRF. After receiving the transaction response, vNRF sends the collected transactions to the sorting service for sorting according to the endorsement mechanism. The sorting service broadcasts the block after sorting. After receiving the block, the Peer node verifies the transaction. If the verification is successful, the block containing the access request and token generation record is written to the local ledger and the global state is updated. At the same time, the Peer node sends the received token to vNRF. vNRF uses the session key sk ij Decrypts the plaintext and sends it to the cNF through a secure channel. cNF uses the public key PK of TEE TEE Verify the legitimacy of the token.
[0132] During the service access process, after receiving the access token, the consumer cNF sends a NF Service Request to the pNF according to the address of the pNF. The request contains the identity ID of the cNF. cNF , cNF type Type cNF ,,ID of the network where the cNF is located vPLMN , pNF ID pNF , pNF type pNF , and access token AccessToken. After pNF receives the service request message from cNF, it uses the public key PK of TEE TEE The access token is verified. If the verification is successful, the pNF verifies the service request parameters of the cNF. If the verification is successful, the pNF returns a service response message to the cNF and provides services. If the verification fails, a failure is returned.
[0133] Figure 6 The diagram shows the process of token request authorization and network function service access, which can be considered as Figure 2 For the sake of clarity and without any limitation, process 600 will be combined with Figure 1A In this implementation, the network function device 110 is implemented as cNF 601, the network registration function device 130 is implemented as vNRF 602, the distributed management device 150 is implemented as Peer 603, and the trusted environment device 170 is implemented as enclave 604. Figure 6 (Changed to 603, 604, 605)
[0134] In process 600, cNF 601 sends (610) an access token request to vNRF 602. vNRF 602 encrypts (612) the token request message, generates a transaction proposal and signs the transaction proposal. vNRF 602 then sends (614) a transaction proposal to Peer 603, which includes the token request of cNF 601. Peer 603 verifies (616) the transaction proposal, and upon successful verification, calls (618) the smart contract in enclave 604. After receiving the transaction proposal, enclave 604 executes (620) the request authorization smart contract. Enclave 604 returns (622) the authorization result to vNRF 602. After receiving the authorization result, vNRF 602 sends (624) a sorting request to sorting service node 605, which then performs global sorting, generates a new block and broadcasts (66) it to Peer 603. Peer 603 sends (628) an access token reply to vNRF 602, and vNRF 602 returns (630) an access token reply to cNF 601. After cNF 601 obtains the access token and confirms that the access token is valid, it can send (632) a network function service request carrying the access token to pNF 606. pNF 606 verifies (634) the access token, and after confirming that it is valid, it can provide the corresponding service to cNF 601. pNF 606 also provides (636) a service reply to cNF 601.
[0135] Figure 7 The schematic flow chart of the method 700 implemented at the network registration function device according to an embodiment of the present application is shown. For the sake of clarity of description without any limitation, the process 700 will be combined with Figure 1A In one possible implementation, the method 700 may be implemented by the network registration function device 130 in the communication system 100A. In other possible implementations, the method 700 may also be implemented by other communication devices independent of the communication system 100A. As an example, the method 700 will be described below by taking the implementation by the network registration function device 130 in the communication system 100A as an example.
[0136] At block 710, the network registration function device 130 receives a registration request from a network function device, the registration request including the identity of the network function device. At block 720, the network registration function device 130 obtains an encrypted identity of the network function device based on the identity of the network function device. At block 730, the network registration function device 130 encrypts the registration request of the network function device using a symmetric key between the network registration function device 130 and the trusted environment device. At block 740, the network registration function device 130 sends a transaction request to the distributed management device, the transaction request including the certificate of the network registration function device 130, the encrypted registration request, the encrypted identity of the network function device, and the signature of the network registration function device 130 on the transaction request.
[0137] In some embodiments, the registration request may also include the type of network function device, the identity of the network to which the network function device belongs, the address of the network function device, the services supported by the network function device, or one or more of the above. In some embodiments, the transaction request may also include the identification of the registration contract that the network registration function device 130 requests to invoke.
[0138] In some embodiments, the network registration function device 130 may also generate an identity credential for the network function device based on determining that the network function device is legitimate, and send the identity credential to the network function device.
[0139] In some embodiments, the registration request received from the network function device may be a first registration request, and the network registration function device 130 may also send a second registration request to the authentication device, the second registration request including the identity of the network registration function device 130, and the signature of the network registration function device 130, and the certificate of the network registration function device 130 received from the authentication device.
[0140] In some embodiments, the network registration function device 130 may also use the certificate to perform interactive authentication with the trusted environment device, and generate a symmetric key between the network registration function device and the trusted environment device.
[0141] In some embodiments, the network registration function device 130 may also receive a registration success message from the distributed management device, and send a registration success message to the network function device.
[0142] In this way, registration requests for network function devices can be securely transmitted to the blockchain network, enabling distributed authentication and information sharing of network service functions.
[0143] Figure 8 The schematic flow chart of the method 800 implemented at the distributed management device according to the embodiment of the present application is shown. Figure 1AIn one possible implementation, the method 800 may be implemented by the distributed management device 150 in the communication system 100A. In other possible implementations, the method 800 may also be implemented by other communication devices independent of the communication system 100A. As an example, the method 800 will be described below by taking the distributed management device 150 in the communication system 100A as an example.
[0144] In block 810, the distributed management device 150 receives a first transaction request from a network registration function device, the first transaction request including a certificate of the network registration function device, an encrypted registration request of the network function device, an encrypted identity of the network function device, and a signature of the transaction request by the network registration function device. In block 820, the distributed management device 150 determines whether the signature is legitimate based on the certificate. In block 830, the distributed management device 150 sends a second transaction request to the trusted environment device based on determining that the signature is legitimate, the second transaction request including the identity of the network registration function device, the encrypted registration request of the network function device, and the encrypted identity of the network function device.
[0145] In some embodiments, the distributed management device 150 may also receive a registration success message of the network function device from the trusted environment device, and send a registration success message to the network registration function device.
[0146] In this way, the distributed management device can verify the legitimacy of the transaction request and send the transaction request to a trusted environment for processing, thereby ensuring the security of the transaction.
[0147] Fig. 9 A schematic flow chart of a method 900 implemented at a trusted environment device according to an embodiment of the present application is illustrated. For the sake of clarity of description without any limitation, the process 900 will be combined with Figure 1A In one possible implementation, the method 900 may be implemented by the trusted environment device 170 in the communication system 100A. In other possible implementations, the method 900 may also be implemented by other communication devices independent of the communication system 100A. As an example, the method 900 will be described below by taking the implementation by the trusted environment device 170 in the communication system 100A as an example.
[0148] At block 910, the trusted environment device 170 receives a transaction request from a distributed management device, the transaction request including an identity of a network registration function device, an encrypted registration request of the network function device, and an encrypted identity of the network function device. At block 920, the trusted environment device 170 determines a symmetric key between the trusted environment device and the network registration function device based on the identity of the network registration function device. At block 930, the trusted environment device 170 decrypts the encrypted registration request using the symmetric key. At block 940, in response to determining that the transaction request is valid based on the encrypted identity, the trusted environment device 170 adds the network function device and the services supported by the network function device to a registration list.
[0149] In some embodiments, the transaction request may further include an identifier of the registration contract that the network registration function device requests to call and a signature of the transaction request by the network registration function device.
[0150] In some embodiments, the registration request may include: the identity of the network function device, the type of the network function device, the identity of the network to which the network function device belongs, the address of the network function device, the services supported by the network function device, or one or more of the above.
[0151] In some embodiments, the encrypted identity of the network function device included in the transaction request may be a first encrypted identity, and the trusted environment device 170 may also call the registration contract based on the identifier of the registration contract. Based on the identity of the network function device, the trusted environment device 170 may obtain a second encrypted identity of the network function device. Based on determining that the first encrypted identity is the same as the second encrypted identity, the trusted environment device 170 may determine that the transaction request is valid.
[0152] In some embodiments, the trusted environment device 170 may also send a registration success message of the network function device to the distributed management device.
[0153] In this way, a hardware-secured isolated environment is built on the blockchain, and in this secure environment, the secure operation of the network function registration function and the secure storage and sharing of network function data are achieved.
[0154] Fig.10 The schematic flow chart of the method 1000 implemented at the second network function device according to the embodiment of the present application is shown. For the sake of clarity of description without any limitation, the process 1000 will be combined with Figure 1A In one possible implementation, the method 1000 may be implemented by the network function device 120 in the communication system 100A. In other possible implementations, the method 1000 may also be implemented by other communication devices independent of the communication system 100A. As an example, the method 1000 will be described below by taking the implementation by the network function device 120 in the communication system 100A as an example.
[0155] At block 1010, the second network function device 120 sends a service token request to the network registration function device, the service token request including the identity of the second network function device, the identity of the network to which the second network function device belongs, the identity of the first network function device requested by the second network function device, the type of service of the first network function device requested by the second network function device, and the identity of the network to which the first network function device belongs. At block 1020, the second network function device 120 receives the decrypted service token from the network registration function device.
[0156] In some embodiments, the second network function device 120 may also use the public key of the trusted environment device to determine whether the decrypted service token is legitimate. Based on determining that the service token is legitimate, the second network function device 120 may send a service request to the first network function device, and the service request may include the identity of the second network function device, the type of the second network function device, the identity of the network to which the second network function device belongs, the identity of the first network function device, the type of the first network function device, and the service token. The second network function device 120 may receive a service response message from the first network function device.
[0157] In this way, the second network function device can request services provided by another network function device from the blockchain network, reducing the complexity of the interaction.
[0158] Fig.11 The schematic flow chart of the method 1100 implemented at the network registration function device 120 according to an embodiment of the present application is shown. For the sake of clarity of description without any limitation, the process 1100 will be combined with Figure 1A In one possible implementation, the method 1100 may be implemented by the network registration function device 120 in the communication system 100A. In other possible implementations, the method 1100 may also be implemented by other communication devices independent of the communication system 100A. As an example, the method 1100 will be described below by taking the implementation by the network registration function device 120 in the communication system 100A as an example.
[0159] In block 1110, the network registration function device 120 receives a service token request from the second network function device, the service token request including the identity of the second network function device, the identity of the network where the second network function device is located, the identity of the first network function device requested by the second network function device, the type of service of the first network function device requested by the second network function device, and the identity of the network where the first network function device is located. In block 1120, the network registration function device 120 encrypts the service token request using the symmetric key of the network registration function device 120 and the trusted environment device. In block 1130, the network registration function device 120 sends a transaction request to the distributed management device, the transaction request including the encrypted service token request, the certificate of the network registration function device 120, and the signature of the network registration function device 120 on the transaction request.
[0160] In some embodiments, the transaction request may also include an identifier of the authorization contract that the network registration function device 120 requests to invoke.
[0161] In some embodiments, the network registration function device 120 may also receive an encrypted service token from the distributed management device, and decrypt the encrypted service token using the symmetric key, and then the network registration function device 120 sends the decrypted service token to the network function device.
[0162] In this way, a network function device's service token request can be securely transmitted to the blockchain network.
[0163] Fig.12 The schematic flowchart of the method 1200 implemented at the distributed management device 140 according to an embodiment of the present application is shown. For the sake of clarity of description without any limitation, the process 1200 will be combined with Figure 1A In one possible implementation, the method 1200 may be implemented by the distributed management device 140 in the communication system 100A. In other possible implementations, the method 1200 may also be implemented by other communication devices independent of the communication system 100A. As an example, the method 1200 will be described below by taking the distributed management device 140 in the communication system 100A as an example.
[0164] In block 1210, the distributed management device 140 receives a first transaction request from a network registration function device, the first transaction request including an encrypted service token request of the network function device, a certificate of the network registration function device, and a signature of the network registration function device on the transaction request. In block 1220, the distributed management device 140 determines whether the signature is legitimate based on the certificate. In block 1230, the distributed management device 140 sends a second transaction request to the trusted environment device based on determining that the signature is legitimate, the second transaction request including the identity of the network registration function device and the encrypted service token request.
[0165] In some embodiments, the first transaction request and the second transaction request may further include an identifier of an authorization contract that the network registration function device requests to invoke.
[0166] In some embodiments, the distributed management device 140 may also receive an encrypted service token from the trusted environment device. The distributed management device 140 may then send the encrypted service token to the network registration function device.
[0167] In this way, transaction requests can be securely processed in a trusted environment, enabling secure authorization of network-enabled devices.
[0168] Fig.13 A schematic flow chart of a method 1300 implemented at a trusted environment device 160 according to an embodiment of the present application is shown. For the sake of clarity of description without any limitation, the process 1300 will be combined with Figure 1A In one possible implementation, the method 1300 may be implemented by the trusted environment device 160 in the communication system 100A. In other possible implementations, the method 1300 may also be implemented by other communication devices independent of the communication system 100A. As an example, the method 1300 will be described below by taking the implementation by the trusted environment device 160 in the communication system 100A as an example.
[0169] At block 1310, the trusted environment device 160 receives a transaction request from a distributed management device, the transaction request including the identity of the network registration function device and the encrypted service token request of the second network function device. At block 1320, the trusted environment device 160 determines the symmetric key between the network registration function device and the trusted environment device 160 based on the identity of the network registration function device. At block 1330, the trusted environment device 160 decrypts the encrypted service token request based on the symmetric key. At block 1340, the trusted environment device 160 determines whether the first network function device provides the service requested by the second network function device based on the service token request. At block 1350, the trusted environment device 160 generates a service token for the second network function device based on determining that the first network function device provides the service requested by the second network function device.
[0170] In some embodiments, the transaction request may further include an identifier of the authorization contract that the network registration function device requests to invoke. In some embodiments, the service token request may include: an identity of the second network function device, an identity of the network to which the second network function device belongs, an identity of the first network function device requested by the second network function device, a type of service of the first network function device requested by the second network function device, an identity of the network to which the first network function device belongs, or one or more of the above.
[0171] In some embodiments, the service token may include: the identity of the second network function device, the identity of the first network function device, the life cycle of the service token, the signature algorithm of the trusted environment device, or one or more of the above.
[0172] In some embodiments, in order to determine whether the first network function device provides the service requested by the second network function device, the trusted environment device 160 may call the authorization contract based on the identifier of the authorization contract. Based on the identity of the first network function device, the trusted environment device 160 may obtain the encrypted identity of the first network function device. The trusted environment device 160 may determine the registration information of the first network function device based on the encrypted identity of the first network function device to obtain the services supported by the first network function device, and determine whether the services supported by the first network function device include the type of the service of the first network function device requested by the second network function device.
[0173] In some embodiments, the trusted environment device 160 may further encrypt the service token using a symmetric key and send the encrypted service token to the distributed management device.
[0174] In this way, a hardware-secured isolated environment is built on the blockchain, and in this secure environment, the secure operation of network access authentication and authorization functions, as well as the secure storage and sharing of network function data are achieved.
[0175] Fig.14 The following is a schematic diagram of the structure of possible communication devices provided in the embodiments of the present application. These communication devices can implement the functions of the terminal device or network device in the above method embodiments, and thus can also achieve the beneficial effects of the above method embodiments. In the embodiments of the present application, the communication device can be as follows: Figure 1A The network function device 110, network registration function device 120, network registration function device 130, distributed management device 140, distributed management device 150, trusted environment device 160 and trusted environment device 170 shown may also be modules (such as chips) applied to the network function device 110, network registration function device 120, network registration function device 130, distributed management device 140, distributed management device 150, trusted environment device 160 and trusted environment device 170.
[0176] like Fig.14 As shown, the communication device 1400 includes a processing unit 1410, a receiving unit 1420, and a sending unit 1430. The communication device can be used to implement the above Figures 2 to 13The functions of the network function device, network registration function device, distributed management device or trusted environment device in any of the method embodiments shown in . In some embodiments, the processing unit may be a processor, the sending unit may be a sender, and the receiving unit may be a receiver.
[0177] like Fig.15 As shown, the communication device 1500 includes a processor 1510 and an interface circuit 1520. The processor 1510 and the interface circuit 1520 are coupled to each other. It is understood that the interface circuit 1520 can be a transceiver or an input-output interface. Optionally, the communication device 1500 may also include a memory 1530 for storing instructions executed by the processor 1510 or storing input data required by the processor 1510 to execute instructions or storing data generated after the processor 1510 executes instructions.
[0178] When the communication device 1500 is used to implement the method in the above method embodiment, the processor 1510 is used to execute the function of the above processing unit 1410, and the interface circuit 1520 is used to execute the functions of the above receiving unit 1420 and the sending unit 1430.
[0179] When the above communication device is a chip applied to the network function device 110, the network registration function device 120, the network registration function device 130, the distributed management device 140, the distributed management device 150, the trusted environment device 160 and the trusted environment device 170, the device chip implements the functions of the network function device 110, the network registration function device 120, the network registration function device 130, the distributed management device 140, the distributed management device 150, the trusted environment device 160 and the trusted environment device 170 in the above method embodiment. The device chip receives information from other modules (such as radio frequency modules or antennas) in the network function device 110, the network registration function device 120, the network registration function device 130, the distributed management device 140, the distributed management device 150, the trusted environment device 160 and the trusted environment device 170, and the information may be sent by other network function devices 110, the network registration function device 120, the network registration function device 130, the distributed management device 140, the distributed management device 150, the trusted environment device 160 and the trusted environment device 170; Alternatively, the device chip sends information to other modules (such as radio frequency modules or antennas) of the network function device 110, the network registration function device 120, the network registration function device 130, the distributed management device 140, the distributed management device 150, the trusted environment device 160 and the trusted environment device 170, and the information is sent to other network function devices 110, the network registration function device 120, the network registration function device 130, the distributed management device 140, the distributed management device 150, the trusted environment device 160 and the trusted environment device 170.
[0180] It is understood that the processor in the embodiments of the present application may be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSP), application specific integrated circuits (ASIC), field programmable gate arrays (FPGA) or other programmable logic devices, transistor logic devices, hardware components or any combination thereof. The general-purpose processor may be a microprocessor or any conventional processor.
[0181] The present application embodiment provides a communication system. The communication system may include the above Fig.14 The communication devices involved in the embodiment shown in the figure, such as the network function device 110, the network registration function device 120, the network registration function device 130, the distributed management device 140, the distributed management device 150, the trusted environment device 160 and the trusted environment device 170. Optionally, the terminal device 110, the access and mobility management device 140, the session management device 150, the control management device 160 and the application node discovery device 170 in the communication system can execute Figures 2 to 13 Any of the communication methods shown in .
[0182] The present application also provides a circuit, which can be coupled with a memory and can be used to execute the processes related to the network function device 110, the network registration function device 120, the network registration function device 130, the distributed management device 140, the distributed management device 150, the trusted environment device 160 and the trusted environment device 170 in any of the above method embodiments. The chip system may include the chip and other components such as a memory or a transceiver.
[0183] It should be understood that the processor mentioned in the embodiments of the present application may be a CPU, or other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field programmable gate arrays (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. A general-purpose processor may be a microprocessor or the processor may also be any conventional processor, etc.
[0184] It should also be understood that the memory mentioned in the embodiments of the present application may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memories. Among them, the non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory may be a random access memory (RAM), which is used as an external cache. By way of example and not limitation, many forms of RAM are available, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct rambus RAM (DR RAM).
[0185] It should be noted that when the processor is a general-purpose processor, DSP, ASIC, FPGA or other programmable logic device, discrete gate or transistor logic device, discrete hardware component, the memory (storage module) is integrated in the processor.
[0186] It should be noted that the memory described herein is intended to include, but is not limited to, these and any other suitable types of memory.
[0187] It should be understood that in the various embodiments of the present application, the size of the serial numbers of the above-mentioned processes does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.
[0188] Those of ordinary skill in the art will appreciate that the modules and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.
[0189] Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and modules described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.
[0190] In the several embodiments provided in the present application, it should be understood that the disclosed communication methods and devices can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the module is only a logical function division. There may be other division methods in actual implementation, such as multiple modules or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or described can be an indirect coupling or communication connection through some interfaces, devices or units, which can be electrical, mechanical or other forms.
[0191] The modules described as separate components may or may not be physically separated, and the components shown as modules may or may not be physical modules, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.
[0192] In addition, each functional module in each embodiment of the present application may be integrated into one processing module, or each module may exist physically separately, or two or more modules may be integrated into one module.
[0193] If the function is implemented in the form of a software function module and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application can be essentially or the part that makes the contribution or the part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including several instructions for a computer device (which can be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the method of each embodiment of the present application. The aforementioned computer-readable storage medium can be any available medium that can be accessed by a computer. By way of example but not limitation, computer-readable media may include random access memory (RAM), read-only memory (ROM), electrically erasable programmable read only memory (EEPROM), compact disc read-only memory (CD-ROM), universal serial bus flash disk, mobile hard disk, or other optical disk storage, magnetic disk storage media or other magnetic storage devices, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and can be accessed by a computer.
[0194] As used herein, the term "including" and similar terms should be understood as open inclusion, i.e., "including but not limited to". The term "based on" should be understood as "based at least in part on". The term "one embodiment" or "the embodiment" should be understood as "at least one embodiment". The terms "first", "second", etc. can refer to different or identical objects, and are only used to distinguish the objects referred to, without implying a specific spatial order, temporal order, order of importance, etc. of the objects referred to. In some embodiments, values, processes, selected items, determined items, equipment, devices, means, components, assemblies, etc. are referred to as "best", "lowest", "highest", "minimum", "maximum", etc. It should be understood that such descriptions are intended to indicate that a selection can be made among many available functional options, and such selections do not need to be better, lower, higher, smaller, larger or otherwise preferred than other options in other aspects or all aspects. As used herein, the term "determine" can cover a variety of actions. For example, "determine" can include calculation, calculation, processing, export, investigation, search (e.g., search in a table, database or another data structure), ascertainment, etc. Additionally, "determining" may include receiving (eg, receiving information), accessing (eg, accessing data in a memory), etc. Furthermore, "determining" may include resolving, selecting, choosing, establishing, etc.
[0195] The above is only a specific implementation of the present application, but the protection scope of the embodiments of the present application is not limited thereto. Any technician familiar with the technical field can easily think of changes or replacements within the technical scope disclosed in the embodiments of the present application, which should be included in the protection scope of the embodiments of the present application. Therefore, the protection scope of the embodiments of the present application shall be based on the protection scope of the claims.
Claims
1. A communication method, comprising: receiving, at a network registration function device, a registration request from a network function device, the registration request including an identity of the network function device; Based on the identity of the network function device, obtaining an encrypted identity of the network function device; Encrypting a registration request for the network function device using a symmetric key between the network registration function device and a trusted environment device; as well as A transaction request is sent to a distributed management device, wherein the transaction request includes a certificate of the network registration function device, the encrypted registration request, the encrypted identity of the network function device, and a signature of the network registration function device on the transaction request.
2. The method according to claim 1, wherein the registration request further comprises at least one of the following: The type of the network function device; The identity of the network to which the network function device belongs; The address of the network function device; or The services supported by the network function device.
3. The method according to claim 1, wherein the transaction request further includes an identifier of a registration contract that the network registration function device requests to call.
4. The method according to any one of claims 1 to 3, further comprising: Based on determining that the network function device is legitimate, generating an identity credential for the network function device; as well as Sending the identity credential to the network function device.
5. The method according to any one of claims 1 to 4, wherein the registration request received from the network function device is a first registration request, the method further comprising: Sending a second registration request to the authentication device, the second registration request including the identity of the network registration function device and the signature of the network registration function device; as well as The certificate of the network registration function device is received from the authentication device.
6. The method according to claim 5, further comprising: Using the certificate to perform interactive authentication with the trusted environment device; as well as A symmetric key between the network registration function device and the trusted environment device is generated.
7. The method according to any one of claims 1 to 6, further comprising: Receive a registration success message from a distributed management device; as well as Send the registration success message to the network function device.
8. A communication method, comprising: receiving, at the distributed management device, a first transaction request from a network registration function device, the first transaction request comprising a certificate of the network registration function device, an encrypted registration request of the network function device, an encrypted identity of the network function device, and a signature of the transaction request by the network registration function device; determining whether the signature is legitimate based on the certificate; and Based on determining that the signature is legitimate, a second transaction request is sent to the trusted environment device, the second transaction request including the identity of the network registration function device, the encrypted registration request of the network function device, and the encrypted identity of the network function device. 9 . The method according to claim 8 , wherein the first transaction request and the second transaction request further include an identifier of a registration contract that the network registration function device requests to invoke.
10. The method according to claim 8 or 9, further comprising: Receiving a registration success message of the network function device from the trusted environment device; as well as Sending the registration success message to the network registration function device.
11. A communication method, comprising: receiving, at a trusted environment device, a transaction request from a distributed management device, the transaction request including an identity of the network registration function device, an encrypted registration request of the network function device, and an encrypted identity of the network function device; Determining a symmetric key between the trusted environment device and the network registration function device based on the identity of the network registration function device; decrypting the encrypted registration request using the symmetric key; as well as In response to determining that the transaction request is valid based on the encrypted identity, the network function device and the services supported by the network function device are added to a registration list.
12. The method according to claim 11, wherein the transaction request further comprises an identifier of the registration contract that the network registration function device requests to call and a signature of the transaction request by the network registration function device.
13. The method of claim 11, wherein the registration request comprises at least one of the following: the identity of the network functional device; The type of the network function device; The identity of the network to which the network function device belongs; The address of the network function device; or The services supported by the network function device.
14. The method according to any one of claims 11 to 13, wherein the encrypted identity of the network function device included in the transaction request is a first encrypted identity, further comprising: Invoking a registration contract based on the identifier of the registration contract; Based on the identity of the network function device, obtaining a second encrypted identity of the network function device; as well as Based on determining that the first encrypted identity is the same as the second encrypted identity, the transaction request is determined to be valid.
15. The method according to any one of claims 11 to 14, further comprising: Send a registration success message of the network function device to the distributed management device.
16. A communication method, comprising: At the second network function device, sending a service token request to the network registration function device, the service token request including an identity of the second network function device, an identity of the network to which the second network function device belongs, an identity of the first network function device requested by the second network function device, a type of service of the first network function device requested by the second network function device, and an identity of the network to which the first network function device belongs; as well as A decrypted service token is received from the network registration function device.
17. The method according to claim 16, further comprising: Using the public key of the trusted environment device to determine whether the decrypted service token is legitimate; Based on determining that the service token is legitimate, sending a service request to the first network function device, the service request including the identity of the second network function device, the type of the second network function device, the identity of the network to which the second network function device belongs, the identity of the first network function device, the type of the first network function device, and the service token; as well as A service response message is received from the first network function device.
18. A communication method, comprising: receiving, at the network registration function device, a service token request from a second network function device, the service token request including an identity of the second network function device, an identity of a network in which the second network function device is located, an identity of a first network function device requested by the second network function device, a type of service of the first network function device requested by the second network function device, and an identity of the network in which the first network function device is located; encrypting the service token request using a symmetric key between the network registration function device and the trusted environment device; as well as A transaction request is sent to a distributed management device, wherein the transaction request includes the encrypted service token request, the certificate of the network registration function device, and a signature of the network registration function device on the transaction request.
19. The method according to claim 18, wherein the transaction request further comprises an identification of an authorization contract that the network registration function device requests to invoke.
20. The method according to claim 18 or 19, further comprising: receiving an encrypted service token from a distributed management device; decrypting the encrypted service token using the symmetric key; as well as The decrypted service token is sent to the second network function device.
21. A communication method, comprising: receiving, at the distributed management device, a first transaction request from a network registration function device, the first transaction request comprising an encrypted service token request of the network function device, a certificate of the network registration function device, and a signature of the transaction request by the network registration function device; determining whether the signature is legitimate based on the certificate; as well as Based on determining that the signature is legitimate, a second transaction request is sent to the trusted environment device, where the second transaction request includes the identity of the network registration function device and the encrypted service token request.
22. The method according to claim 21, wherein the first transaction request and the second transaction request further include an identifier of an authorization contract that the network registration function device requests to invoke.
23. The method according to claim 21 or 22, further comprising: receiving an encrypted service token from the trusted environment device; as well as The encrypted service token is sent to the network registration function device.
24. A communication method, comprising: receiving, at the trusted environment device, a transaction request from the distributed management device, the transaction request including an identity of the network registration function device, an encrypted service token request of the second network function device; Based on the identity of the network registration function device, determining a symmetric key between the network registration function device and the trusted environment device; decrypting the encrypted service token request based on the symmetric key; determining, based on the service token request, whether the first network function device provides the service requested by the second network function device; as well as Based on determining that the first network function device provides the service requested by the second network function device, a service token is generated for the second network function device.
25. The method according to claim 24, wherein the transaction request further comprises an identification of an authorization contract that the network registration function device requests to invoke.
26. The method of claim 24, wherein the service token request comprises at least one of: the identity of the second network function device; The identity of the network to which the second network function device belongs; the identity of the first network function device requested by the second network function device; The type of service of the first network function device requested by the second network function device; or The identity of the network to which the first network function device belongs.
27. The method according to any one of claims 24 to 26, wherein the service token comprises at least one of the following: the identity of the second network function device; the identity of the first network function device; the lifecycle of the service token; or The signature algorithm of the trusted environment device.
28. The method according to any one of claims 24 to 27, wherein determining whether the first network function device provides the service requested by the second network function device comprises: Invoking an authorization contract based on the identifier of the authorization contract; Based on the identity of the first network function device, obtaining an encrypted identity of the first network function device; determining, based on the encrypted identity of the first network function device, registration information of the first network function device to obtain services supported by the first network function device; as well as Determining whether services supported by the first network function device include a type of service of the first network function device requested by the second network function device.
29. The method according to any one of claims 24 to 28, further comprising: encrypting the service token using the symmetric key; as well as The encrypted service token is sent to the distributed management device.
30. A communication device comprising: A processor, and a memory storing instructions, which, when executed by the processor, cause the communication device to perform a method according to any one of claims 1 to 7, any one of claims 8 to 10, any one of claims 11 to 15, any one of claims 16 or 17, any one of claims 18 to 20, any one of claims 21 to 23, or any one of claims 24 to 29.
31. A chip comprising a processing circuit configured to perform a method according to any one of claims 1 to 7, any one of claims 8 to 10, any one of claims 11 to 15, any one of claims 16 or 17, any one of claims 18 to 20, any one of claims 21 to 23, or any one of claims 24 to 29.
32. A computer-readable storage medium storing instructions which, when executed by a communication device, cause the communication device to perform a method according to any one of claims 1 to 7, any one of claims 8 to 10, any one of claims 11 to 15, any one of claims 16 or 17, any one of claims 18 to 20, any one of claims 21 to 23, or any one of claims 24 to 29.
Citation Information
Cited By
Communication method, communication device, medium, and program product
EP4697774A1
Communication method, communication device, medium, and program product
WO2024240192A1
Communication method and device
WO2026143504A1
