Network function registration method, device, system, computer device and storage medium
By directly exchanging target-level information between NF service management functions and distributed service nodes, and utilizing the blockchain network for validity verification and consensus, the complexity of the NRF service registration process in existing technologies is solved, and the interaction efficiency of network functions is improved.
Patent Information
- Application Number
- CN202310926972.2
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2023-07-26
- Publication Date
- 2026-01-06
- Estimated Expiration
- 2043-07-26
AI Technical Summary
Existing NRF service registration methods are complex and result in low efficiency in network function interaction, especially in cross-network NF service registration or discovery processes that require the participation of multiple levels of NRFs.
By receiving the NF level information of the target network function, determining the target level information, and sending a level information registration request to the distributed service node, the blockchain network is used for validity verification and consensus, and data interaction is carried out directly between the NF service management function and the distributed service node, reducing the transmission of multi-level NRF.
The registration process for network functions has been simplified, the interaction efficiency of network functions has been improved, and the transmission process of target-level information has been reduced.
Smart Images

Figure CN117062213B_ABST
Abstract
Description
Technical Field
[0001] This application relates to the field of wireless communication technology, and in particular to a network function registration method, apparatus, system, computer equipment, storage medium, and computer program product. Background Technology
[0002] With the development of 5G, in the current 5G service-oriented framework, a two-tier network of Network Repository Functions (NRFs) is typically used to handle service registration or discovery across the entire network. In the current network, each provincial-level NRF only handles service registration or discovery for its own Network Functions (NFs). When the core network process involves cross-network NF service registration or discovery, it is necessary to further query the national-level NRF, which in turn queries other provincial-level NRFs. Therefore, this process is implemented based on a two-tier NRF architecture consisting of the national-level and provincial-level NRFs.
[0003] In existing NRF service registration, service registration typically involves the NF acting as the service provider initiating a service registration request to the NRF, which includes information about the NF. However, this service registration method involves multiple levels of NRFs, making the process complex and reducing the efficiency of network function interactions. Summary of the Invention
[0004] Therefore, it is necessary to provide a network function registration method, apparatus, system, computer equipment, computer-readable storage medium, and computer program product to address the aforementioned technical problems.
[0005] Firstly, this application provides a network function registration method, applied to NF service management functions. The method includes:
[0006] Receive NF level information of a target network function (NF), and determine target level information based on the NF level information, wherein the target level information includes at least one of network level information, NF level information, and service level information;
[0007] A level information registration request is sent to a distributed service node, the level information registration request carrying the target level information, so that the distributed service node can perform registration processing based on the target level information;
[0008] Receive the registration response message containing the target level information returned by the distributed service node.
[0009] In one embodiment, determining the target level information based on the NF level information includes:
[0010] Based on the NF level information, network level information corresponding to the NF level information is generated, and the network level information is used as the target level information.
[0011] In one embodiment, determining the target level information based on the NF level information includes:
[0012] Based on the NF level information, determine the service level information within the NF level information, and use the service level information as the target level information; or...
[0013] Based on the NF level information, the updated NF level information is determined, and the updated NF level information is used as the target level information.
[0014] In one embodiment, the method further includes:
[0015] A discovery request is sent to the distributed service node; the discovery request is used to instruct the distributed service node to determine the level information of the target level that matches the discovery request;
[0016] Receive the discovery response message returned by the distributed service node; the discovery response message carries the level information of the target level.
[0017] In one embodiment, the method further includes:
[0018] An update request corresponding to the target level information is sent to the distributed service node; the update request carries the update content corresponding to the target level information, so that the distributed service node performs update processing based on the update content.
[0019] Receive the update response message containing the updated content returned by the distributed service node.
[0020] Secondly, this application provides a network function registration method applied to a distributed service node, wherein the distributed service node is a node in a target blockchain network, and the target blockchain network includes multiple distributed service nodes, the method comprising:
[0021] Receive a level information registration request sent by the NF service management function; the level information registration request carries target level information, the target level information including at least one of network level information, NF level information and service level information;
[0022] Based on the target level information, a validity check is performed to obtain the check result;
[0023] A registration response message is generated based on the verification result and sent to the NF service management function.
[0024] In one embodiment, the validity verification based on the target level information to obtain the verification result includes:
[0025] A transaction is generated based on the target-level information, and the transaction is sent to other distributed service nodes included in the target blockchain network so that the target blockchain network can obtain the validity result of the transaction;
[0026] The verification result of the target level information is determined based on the validity result of the transaction.
[0027] In one embodiment, the validity result is the result of reaching a consensus; sending the transaction to other distributed service nodes included in the target blockchain network, so that the target blockchain network obtains the validity result of the transaction, includes:
[0028] The transaction is sent to other distributed service nodes included in the target blockchain network, so that the blockchain network can reach a consensus on the transaction and obtain a consensus result.
[0029] The method further includes:
[0030] The target-level information contained in the transaction corresponding to the consensus result is stored in the blockchain corresponding to the target-level information.
[0031] In one embodiment, after performing validity verification based on the target level information and obtaining the verification result, the method further includes:
[0032] When updating the blockchain corresponding to the target level information based on the target level information, the target level information is sent to other blockchains corresponding to the distributed service node, so that the other blockchains corresponding to the distributed service node are updated based on the target level information.
[0033] In one embodiment, the method further includes:
[0034] Receive the discovery request sent by the NF service management function;
[0035] Based on the discovery request, query whether there is target-level information in the target blockchain network that matches the discovery request;
[0036] If the target blockchain network contains level information matching the discovery request at the target level, a discovery response message is sent to the NF service management function; the discovery response message carries the level information of the target level.
[0037] In one embodiment, the method further includes:
[0038] Receive the update request corresponding to the target level information sent by the NF service management function;
[0039] A transaction is generated based on the update content in the update request, and the transaction is sent to other distributed service nodes in the target blockchain network so that the target blockchain network can reach a consensus on whether the transaction is valid and obtain the verification result message of the transaction from the target blockchain network.
[0040] An update response message is generated based on the verification result message, and the update response message is sent to the NF service management function.
[0041] Thirdly, this application also provides a network function registration device. Applied to NF service management functions, the device includes:
[0042] The level information receiving module is used to receive NF level information of a target network function (NF), and determine target level information based on the NF level information. The target level information includes at least one of network level information, NF level information, and service level information.
[0043] The registration request sending module is used to send a level information registration request to a distributed service node. The level information registration request carries the target level information so that the distributed service node can perform registration processing based on the target level information.
[0044] The response message receiving module is used to receive the registration response message of the target level information returned by the distributed service node.
[0045] In one embodiment, the level information receiving module is specifically used to: generate network level information corresponding to the NF level information based on the NF level information, and use the network level information as the target level information.
[0046] In one embodiment, the level information receiving module is further configured to: determine service level information in the NF level information based on the NF level information, and use the service level information as the target level information; or, determine updated NF level information based on the NF level information, and use the updated NF level information as the target level information.
[0047] In one embodiment, the apparatus further includes: a level information discovery module, configured to send a discovery request to the distributed service node; the discovery request instructs the distributed service node to determine level information of a target level that matches the discovery request; and to receive a discovery response message returned by the distributed service node; the discovery response message carrying the level information of the target level.
[0048] In one embodiment, the apparatus further includes: a level information update module, configured to send an update request corresponding to the target level information to the distributed service node; the update request carries update content corresponding to the target level information, so that the distributed service node performs update processing based on the update content; and receive an update response message of the update content returned by the distributed service node.
[0049] Fourthly, this application also provides a network function registration device. Applied to distributed service nodes, the distributed service nodes being nodes in a target blockchain network, the target blockchain network including multiple distributed service nodes, the device includes:
[0050] The registration request receiving module is used to receive a level information registration request sent by the NF service management function; the level information registration request carries target level information; the target level information includes at least one of network level information, NF level information, and service level information.
[0051] The validity verification module is used to perform validity verification based on the target level information and obtain the verification result.
[0052] The response message sending module is used to generate a registration response message based on the verification result and send the registration response message to the NF service management function.
[0053] In one embodiment, the validity verification module is specifically used to generate a transaction based on the target level information and send the transaction to other distributed service nodes included in the target blockchain network, so that the target blockchain network obtains the validity result of the transaction; and determine the verification result of the target level information based on the validity result of the transaction.
[0054] In one embodiment, the validity result is the result of reaching a consensus; the validity verification module is further configured to send the transaction to other distributed service nodes included in the target blockchain network, so that the blockchain network can obtain a consensus result when it reaches a consensus on the transaction; the method further includes: storing the target level information contained in the transaction corresponding to the consensus result to the blockchain corresponding to the target level information.
[0055] In one embodiment, the device further includes:
[0056] The blockchain network update module is specifically used to send the target level information to other blockchains corresponding to the distributed service node when updating the blockchain corresponding to the target level information based on the target level information, so that the other blockchains corresponding to the distributed service node can be updated based on the target level information.
[0057] In one embodiment, the device further includes:
[0058] The level information discovery module is specifically used to receive the discovery request sent by the NF service management function; based on the discovery request, query whether there is level information of the target level matching the discovery request in the target blockchain network; if there is level information of the target level matching the discovery request in the target blockchain network, then send a discovery response message to the NF service management function; the discovery response message carries the level information of the target level.
[0059] In one embodiment, the device further includes:
[0060] The level information update module is specifically used to receive the update request corresponding to the target level information sent by the NF service management function; generate a transaction based on the update content in the update request, and send the transaction to other distributed service nodes in the target blockchain network so that the target blockchain network can reach a consensus on whether the transaction is valid and obtain the verification result message of the transaction from the target blockchain network; generate an update response message based on the verification result message, and send the update response message to the NF service management function.
[0061] Fifthly, this application also provides a network function registration system. The network function registration system includes NF service management functions and distributed service nodes, wherein the distributed service nodes are nodes in the target blockchain network, and the target blockchain network includes multiple distributed service nodes, wherein:
[0062] The NF service management function is used to receive NF level information corresponding to the target network function NF, and determine target level information based on the NF level information. The target level information includes at least one of network level information, NF level information and service level information.
[0063] The NF service management function is also used to send a level information registration request to the distributed service node, the level information registration request carrying the target level information;
[0064] The distributed service node is used to receive a level information registration request sent by the NF service management function; the level information registration request carries target level information, and a validity verification is performed based on the target level information to obtain a verification result; a registration response message is generated based on the verification result, and the registration response message is sent to the NF service management function.
[0065] The NF service management function is also used to receive the registration response message of the target level information returned by the distributed service node.
[0066] Sixthly, this application also provides a computer device. The computer device includes a memory and a processor, the memory storing a computer program, and the processor executing the computer program to implement the steps of the method as described in the first or second aspect.
[0067] In a seventh aspect, this application also provides a computer-readable storage medium. The computer-readable storage medium stores a computer program thereon, which, when executed by a processor, implements the steps of the method as described in the first or second aspect.
[0068] Eighthly, this application also provides a computer program product. The computer program product includes a computer program that, when executed by a processor, implements the steps of the method as described in the first or second aspect.
[0069] The aforementioned network function registration method, apparatus, system, computer equipment, storage medium, and computer program product, by receiving target level information corresponding to a target network function (NF), wherein the target level information includes at least one of network level information, NF level information, and service level information; sending a level information registration request to a distributed service node, wherein the level information registration request carries the target level information, so that the distributed service node performs registration processing based on the target level information; and receiving a registration response message of the target level information returned by the distributed service node.
[0070] By employing this method, the NF service management function can receive the NF level information of a network function (NF), determine the target level information based on the NF level information, and send a registration request for the target level information to the distributed service nodes. This enables the distributed service nodes to register the target level information and return a registration response message to the NF service management function, thus completing the NF registration process. The entire registration process only requires data interaction between the NF service management function and the distributed service nodes, eliminating the need for the target level information to be transmitted through multiple levels of NRFs, thereby reducing the transmission process of the target level information and improving the interaction efficiency of network functions. Attached Figure Description
[0071] Figure 1 This is an application environment diagram of the network function registration method in one embodiment;
[0072] Figure 2 This is a flowchart illustrating a network function registration method in one embodiment;
[0073] Figure 3 This is a flowchart illustrating the steps for determining target-level information in one embodiment;
[0074] Figure 4 This is a flowchart illustrating the steps for determining target level information in another embodiment;
[0075] Figure 5 This is a flowchart illustrating the steps for discovering target-level information in one embodiment;
[0076] Figure 6 This is a flowchart illustrating the steps for updating target-level information in one embodiment;
[0077] Figure 7 This is a flowchart illustrating the network function registration method in another embodiment;
[0078] Figure 8 This is a flowchart illustrating the validity verification steps in one embodiment;
[0079] Figure 9 This is a flowchart illustrating the validity verification steps in another embodiment;
[0080] Figure 10 This is a flowchart illustrating the steps for discovering target-level information in one embodiment;
[0081] Figure 11 This is a flowchart illustrating the steps for updating target-level information in one embodiment;
[0082] Figure 12 This is a flowchart illustrating the network function registration method in another embodiment;
[0083] Figure 13 This is a flowchart illustrating the network function registration method in yet another embodiment;
[0084] Figure 14 This is a schematic diagram illustrating the structure of the steps for updating a blockchain network in one embodiment;
[0085] Figure 15 This is an application environment diagram of the network function registration method in another embodiment;
[0086] Figure 16 This is a structural block diagram of a network function registration device in one embodiment;
[0087] Figure 17 This is a structural block diagram of a network function registration device in another embodiment;
[0088] Figure 18 This is an internal structural diagram of a computer device in one embodiment. Detailed Implementation
[0089] To make the objectives, technical solutions, and advantages of this application clearer, the following detailed description is provided in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative and not intended to limit the scope of this application.
[0090] The network function registration method provided in this application embodiment can be applied to, for example, Figure 1 In the application environment shown, the distributed network A100 communicates with the blockchain 300. Specifically, the NF service management 110 of the distributed network A100 can communicate with the distributed service node 310 of the blockchain 300. The NF service management 110 is used to manage multiple network functions (NFs) in the distributed network A100 and to initiate registration requests, update requests, and discovery requests for target-level information to the distributed service node 310, etc.
[0091] The NF service management 210 of the distributed network B200 can initiate registration requests, update requests, and discovery requests for target-level information to the distributed service node 320. For example, the NF service management 210 initiates a discovery request to the distributed service node 320, and the distributed service node 320 returns a response message corresponding to the discovery request to the NF service management 210 based on the discovery request. The NF service management 210 can call the network function NF in the distributed network A100 corresponding to the response message through the network connection. The distributed network can be the core network.
[0092] Optionally, a distributed service node is a node in the target blockchain network, which includes multiple distributed service nodes. The target blockchain network may contain multiple distributed service nodes and multiple blockchains, where data interaction is possible between the multiple blockchains and the multiple distributed service nodes. A distributed service node can be any one or more nodes in the target blockchain network, and multiple distributed service nodes can receive level information registration requests sent by the NF service management function.
[0093] In one embodiment, such as Figure 2 As shown, a network function registration method is provided, which is applied to... Figure 1 Taking NF service management 110 (i.e., NF service management function) as an example, the explanation includes the following steps:
[0094] Step S202: Receive the NF level information of the target network function (NF), and determine the target level information based on the NF level information.
[0095] The target level information includes at least one of network level information, NF level information, and service level information; the NF service management function is a management node that manages all nodes in the distributed network. The NF service management function is used to manage the registration, update, discovery, and other operations of all network functions (NFs) in the distributed network, and can also be used to manage service calls, service forwarding, and service negotiation between multiple distributed networks.
[0096] The NF service management function can receive the NF level information corresponding to the target network function NF to be registered in the network to which the NF service management function belongs, and determine the target level information based on the NF level information. The target network function NF is a node in the distributed network that can provide network functions, and the target network function NF to be registered belongs to the same network as the NF service management function. Through the NF level information corresponding to the target network function NF, various types of target level information can be obtained, enabling the NF service management function to initiate registration, update, and discovery operation requests to the distributed service nodes based on these various types of target level information. These various types of target level information can be one or more of network level information, NF level information, and service level information. Therefore, the target level information carries specific information about the target network function NF, and is necessary information for the target network function NF to perform registration, update, and discovery operation requests.
[0097] Specifically, the NF service management function receives the NF level information corresponding to the target network function NF, and the NF service management function determines the required target level information based on the NF level information; wherein, according to the requirements of the NF service management function, the target level information includes at least one of network level information, NF level information and service level information.
[0098] Optionally, as an example, network level information, NF level information, and service level information can each correspond to different levels of information.
[0099] Among them, service level information is the first level of information. Service level information can correspond to a service instance in the target network function (NF). Service level information can store information such as the ID of a service instance, the target network function (NF) to which the service instance belongs, and the service name of the service instance.
[0100] NF level information is the second level of information. NF level information can be generated by merging one or more service level information and contains detailed information about the target network function (NF). For example, NF level information includes the unique NF instance ID corresponding to the target network function, the capabilities supported by the target network function, the distributed network to which the target network function belongs, and a list of multiple service instances in the target network function.
[0101] Network-level information is third-level information, and it can be generated by combining one or more service-level information. For example, network-level information includes the network ID of the distributed network to which the target network function (NF) belongs, the location information of the distributed network to which the target network function (NF) belongs, and the supporting capabilities corresponding to the distributed network to which the target network function (NF) belongs. The NF service management function can generate second-level information based on first-level information, or generate third-level information based on second-level information. The NF service management function can also generate third-level information based on both first-level and second-level information.
[0102] Optionally, as an embodiment, after receiving the target level information, the NF service management function can verify whether the target level information and the request corresponding to the target level information are valid. If the NF service management function determines that the target level information is invalid, or the request corresponding to the target level information is invalid, the NF service management function can generate an invalid response message and send the invalid response message to the target network function NF. The invalid response message carries the reason for the invalidity of the target level and / or the reason for the invalidity of the request corresponding to the target level information.
[0103] Accordingly, if the NF service management function determines that the target level information is valid and the request corresponding to the target level information is valid, the NF service management function can temporarily store the target level information.
[0104] In one possible implementation, when the target-level information is network-level information, the target-level information may specifically include: NfInstanceID: a unique NF instance ID; NfType: the NF type of the instance (such as AMF, SMF, etc.); AllowedCapacity: supported capabilities, corresponding to the elements in NetworkCapacityInfo in NW-Chain; HNId: the ID of the home network, corresponding to NetworkIdentifier in NW-Chain; Ipv4Addr: the IPv4 address of the instance; Ipv6Addr: the IPv6 address of the instance; ServiceList: the service list of the instance.
[0105] In one possible implementation, when the target-level information is NF-level information, the target-level information may specifically include: NfInstanceID: a unique NF instance ID; NfType: the NF type of the instance (such as AMF, SMF, etc.); AllowedCapacity: supported capabilities, corresponding to the elements in NetworkCapacityInfo in NW-Chain; HNId: the ID of the home network, corresponding to NetworkIdentifier in NW-Chain; Ipv4Addr: the IPv4 address of the instance; Ipv6Addr: the IPv6 address of the instance; ServiceList: the service list of the instance.
[0106] In one possible implementation, when the target level information is service level information, the target level information may specifically include: ServiceInstanceId: a unique service instance ID; ServiceName: service name; HNfId: the ID of the NF to which it belongs (i.e., NfInstanceId in the NF-Chain); Port: port; AllowedNfTypes: the NF types that are allowed to access the service.
[0107] Step S204: Send a level information registration request to the distributed service node.
[0108] The registration request for level information carries target level information, enabling distributed service nodes to process registration based on this information. Distributed service nodes are service nodes within the target blockchain network, which comprises multiple distributed service nodes. These nodes assess the registration and updating of the target level information, reaching a consensus to determine whether the target network function (NF) corresponding to the target level information can be registered or updated. Distributed networks can communicate and interact with each other through distributed service nodes within the blockchain network; each distributed service node in the blockchain network corresponds to at least one distributed network.
[0109] In addition, distributed service nodes can store and manage target-level information; distributed service nodes can respond to discovery requests for target network functions (NFs) issued by the NF service management function. A discovery request is a request sent by a distributed network to a distributed service node in the target blockchain network through the NF service management function in the distributed network. The discovery request is used to enable the target blockchain network to determine whether there is a target network function (NF) or a target service on the target network function (NF) required by a certain distributed network in the target blockchain network, and to return a corresponding discovery response message to the NF service management function that sent the discovery request.
[0110] Therefore, if a target network function (NF) wants to register on a target blockchain network, the NF service management function will send a level information registration request to the distributed service nodes of the target blockchain network. This registration request will carry the target level information corresponding to the target network function (NF). Once the distributed service nodes receive the target level information, they can process the registration.
[0111] Specifically, after receiving the target level information corresponding to the target network function (NF), the NF service management function sends a level information registration request to the distributed service node. The level information registration request carries the target level information so that the distributed service node can perform registration processing based on the target level information.
[0112] Step S206: Receive the registration response message containing target-level information returned by the distributed service node.
[0113] After the distributed service node completes the registration process for the target-level information, it generates a registration response message and sends the registration response message to the NF service management function. Based on this, the NF service management function can determine the registration result of the target-level information based on the registration response message. The registration response message can be a response message indicating that the target network function NF registration is successful or that the target network function NF registration has failed.
[0114] Specifically, after the distributed service node completes the registration process for the target-level information, the NF service management function receives the registration response message for the target-level information returned by the distributed service node.
[0115] In the network function registration method described above, the NF service management function receives the target level information of the network function (NF) and sends a registration request for the corresponding level information to the distributed service node. This causes the distributed service node to register the target level information and return a registration response message to the NF service management function, thus completing the NF registration process. The entire registration process only requires data interaction between the NF service management function and the distributed service node, eliminating the need for the target level information to be transmitted through multiple levels of NRFs. This reduces the transmission process of the target level information and improves the interaction efficiency of the network function.
[0116] In one embodiment, such as Figure 3 As shown, the specific implementation process of step "determine the target level information based on the NF level information" includes:
[0117] Step S302: Based on the NF level information, generate the network level information corresponding to the NF level information.
[0118] Step S304: Use network-level information as the target-level information.
[0119] When the target level information is network level information, the network level information of the target network function (NF) can be generated from the NF level information of the target network function (NF). It should be understood that network level information includes NF level information, and NF service level information includes service level information. Therefore, network level information can be generated from NF level information, or service level information can be determined based on NF level information.
[0120] Specifically, the NF service management function receives the NF level information corresponding to the target network function NF in this distributed network. Based on the NF level information corresponding to the target network function NF, and the data structure relationship between network level information, NF level information, and service level information, it generates the network level information corresponding to the target network function NF, and uses the network level information as the target level information.
[0121] In one embodiment, the NF service management function can receive NF level information corresponding to the target network function NF, and generate network level information corresponding to the target network function NF based on the NF level information.
[0122] In this embodiment, by understanding the relationship between network-level information and NF-level information, it is possible to generate network-level information based on NF-level information.
[0123] In one embodiment, such as Figure 4 As shown, the specific implementation process of step "determine the target level information based on the NF level information" includes:
[0124] Step S402: Based on the NF level information, determine the service level information in the NF level information, and use the service level information as the target level information.
[0125] Step S404: Based on the NF level information, determine the updated NF level information, and use the updated NF level information as the target level information.
[0126] Specifically, if the target level information is NF level information, it can be updated based on the NF level information of the target network function NF to obtain the updated NF level information. When the target level information is service level information, the service level information of the target network function NF can be extracted from the NF level information of the target network function NF.
[0127] It should be understood that, since there is a relationship in the data structure between network level information, NF level information, and service level information, network level information contains NF level information, and NF service level information contains service level information. Therefore, service level information and NF level information can be determined through NF level information.
[0128] Specifically, the NF service management function receives the NF level information corresponding to the target network function NF, and based on the NF level information corresponding to the target network function NF, as well as the relationship between the NF level information and the service level information in the data structure, determines the service level information corresponding to the target network function NF, and uses the service level information as the target level information.
[0129] In one embodiment, the NF service management function receives the NF level information corresponding to the target network function NF, updates the NF level information based on the received NF level information, and obtains the updated NF level information.
[0130] In this embodiment, by understanding the relationship between NF level information and service level information, it is possible to obtain service level information based on NF level information, and to obtain updated NF level information based on NF level information.
[0131] In one embodiment, such as Figure 5 As shown, the specific implementation process of the network function registration method also includes:
[0132] Step S502: Send a discovery request to the distributed service node.
[0133] The discovery request is used to instruct distributed service nodes to determine the level information of the target level that matches the discovery request. The level information of the target level is the level information of the specified level.
[0134] Specifically, the NF service management function can send discovery requests to distributed service nodes. Based on the received discovery request, the distributed service node can determine the specified level of the discovery request. Based on this, the distributed service node can determine the level information that matches the discovery request from multiple level information corresponding to the specified level.
[0135] In one example, the specified level in the discovery request can be a service level. Based on this, as an embodiment, the service required in the discovery request can be the video-on-demand service corresponding to the service level information. Then, the target level that matches the discovery request in the target blockchain network is the level of the service level information, where the service level information corresponds to the video-on-demand service.
[0136] Specifically, if a node in a distributed network needs to determine whether a target network function (NF) exists in the entire network, it will submit a discovery request for that service or function to the NF service management function. Upon receiving the discovery request, the NF service management function can generate a corresponding discovery request. The NF service management function then sends the discovery request to the distributed service nodes. Upon receiving the discovery request, the distributed service nodes can determine whether the corresponding service or function is recorded in the target blockchain network, and return a discovery response message carrying the target level information for the required service or function to the NF service management function. The NF service management function can then obtain the discovery result based on this discovery response message.
[0137] Specifically, the NF service management function generates a discovery request and sends it to the distributed service nodes, enabling the distributed service nodes to determine whether target-level information matching the discovery request exists in the target blockchain network. If target-level information matching the discovery request exists, the discovery response message can be a discovery success response message, which is returned to the NF service management function; conversely, if target-level information matching the discovery request does not exist, the discovery response message can be a discovery failure response message, which is returned to the NF service management function.
[0138] Step S504: Receive the discovery response message returned by the distributed service node.
[0139] The discovery response message carries level information about the target level.
[0140] Specifically, after the distributed service node determines the discovery response message, it sends the discovery response message to the NF service management function, which then receives the discovery response message.
[0141] In one embodiment, after the distributed service node obtains the discovery result of the target level information matching the discovery request, it generates a discovery response message regardless of whether the discovery is successful or unsuccessful, and returns the discovery response message to the NF service management function so that the NF service management function can obtain the final discovery result.
[0142] In this embodiment, by sending a discovery request to the distributed service node, it is possible to determine whether there are services or capabilities in the target blockchain network that meet the discovery request, thereby improving the discovery efficiency of network functions.
[0143] In one embodiment, such as Figure 6 As shown, the specific implementation process of the network function registration method also includes:
[0144] Step S602: Send an update request corresponding to the target level information to the distributed service node.
[0145] The update request carries the updated content corresponding to the target level information, enabling the distributed service nodes to perform update processing based on the updated content. Since the target level information corresponding to the target network function NF changes, the target level information registered in the target blockchain network should also be changed accordingly. Therefore, it is necessary to synchronize the updated content to the target blockchain network.
[0146] Based on this, the NF service management function generates an update request corresponding to the target level information before the update, and the update request carries the update content corresponding to the target level information; the update content is the level information after the target level information is updated. When the distributed service node receives the update request, the distributed service node can update the corresponding level information in the target blockchain network based on the update content.
[0147] Specifically, the NF service management function sends an update request corresponding to the target level information to the distributed service nodes, so that the distributed service nodes can update the target level information before the update based on the update content.
[0148] Step S604: Receive the update response message containing the updated content returned by the distributed service node.
[0149] Specifically, after the distributed service node updates the target-level information before the update based on the updated content, it obtains the result of the update processing; and generates an update-related message based on the result of the update processing, thereby notifying the NF service management function of the update processing result. The result of the update processing can be either a successful update or a failed update.
[0150] Specifically, the NF service management function receives update response messages of updated content returned by the distributed service nodes and synchronizes the update response messages to the distributed network corresponding to the NF service management function.
[0151] In this embodiment, by sending an update request to the distributed service node, the target-level information that has not been updated in the target blockchain network can be directly updated, thereby improving the update efficiency of network functions.
[0152] In one embodiment, such as Figure 7 As shown, a network function registration method is provided, which is applied to... Figure 1 Taking distributed service node 310 as an example, a distributed service node is a node in the target blockchain network. The target blockchain network includes multiple distributed service nodes, and the process includes the following steps:
[0153] Step S702: Receive the level information registration request sent by the NF service management function.
[0154] The registration request for level information carries target level information, which includes at least one of network level information, NF level information, and service level information.
[0155] Step S704: Perform validity verification based on target-level information to obtain the verification result.
[0156] Before the distributed service node returns a registration response message to the NF service management function, the target-level information needs to be validated in the target blockchain network corresponding to the distributed service node to obtain the validation result or the validation failure result.
[0157] Validation is used to determine whether target-level information meets the registration conditions. If the target-level information meets the registration conditions, the validity check is successful and the result of the check is obtained; conversely, if the target-level information does not meet the registration conditions, the validity check fails.
[0158] Specifically, when a distributed service node receives a level information registration request sent by the NF service management function, it obtains the target level information from the level information registration request, performs validity verification based on the target level information, and obtains the verification result.
[0159] Step S706: Generate a registration response message based on the verification result and send the registration response message to the NF service management function.
[0160] After the distributed service node completes the registration process for the target-level information, it sends the processed registration response message to the NF service management function to obtain the final registration result. Based on the registration result, it generates a registration response message, which can be either a response message indicating successful registration of the target network function NF or a response message indicating failed registration of the target network function NF.
[0161] Specifically, after the distributed service node completes the registration process for the target-level information, it generates a registration response message based on the verification result and sends the registration response message to the NF service management function.
[0162] because Figure 7 The network function registration method shown is implemented on the distributed service node side. Other corresponding specific examples and explanations have been explained in detail on the NF service management function side, so they will not be elaborated on here.
[0163] As described in the network function registration method above, the NF service management function sends a registration request for the target level information to the distributed service node, enabling the distributed service node to register the target level information. The distributed service node then returns a registration response message corresponding to the target level information to the NF service management function, thus completing the NF registration process. The entire registration process only requires data interaction between the NF service management function and the distributed service node, eliminating the need for the target level information to be transmitted through multiple levels of NRF, thereby reducing the transmission process of the target level information and improving the interaction efficiency of network functions.
[0164] In one embodiment, such as Figure 8 As shown, the specific implementation process for validating the results based on target-level information includes:
[0165] Step S802: Generate a transaction based on the target-level information and send the transaction to other distributed service nodes included in the target blockchain network so that the target blockchain network can obtain the validity result of the transaction.
[0166] Distributed service nodes create transactions upon receiving target-level information. Transactions serve as the information carriers for data interaction within the blockchain ecosystem. Therefore, validating the target-level information can be transformed into validating the transaction. Consequently, other distributed service nodes in the target blockchain network also need to validate the transaction. Thus, each distributed service node sends the transaction to other distributed service nodes and receives their respective validation results. These validation results are then exchanged among all distributed service nodes to ensure the target blockchain network obtains the final validity result of the transaction.
[0167] Specifically, distributed nodes generate transactions based on the received target-level information, which includes that information. These transactions are then sent to other distributed service nodes in the target blockchain network, allowing them to determine the validity of the transactions. The validity results from these other distributed service nodes, and consequently, the validity results from the target blockchain network, are obtained.
[0168] Step S804: Determine the verification result of the target level information based on the validity result of the transaction.
[0169] The validity result can be either a result where the target-level information is valid or a result where the target-level information is invalid. Therefore, the validity result of the transaction based on the target blockchain network can yield the final verification result of the target-level information.
[0170] Specifically, the distributed service node obtains the verification result of the target-level information based on the validity result of the transaction, which can be that the target-level information is valid or invalid. For example, it can include a verification pass result or a verification fail result.
[0171] In this embodiment, by sending transactions to other distributed service nodes of the target blockchain network and enabling the target blockchain network to obtain the validity result of the transactions, the validity of the transactions can be determined within the target blockchain network, thereby obtaining a more accurate verification result.
[0172] In one embodiment, the validity result is the result of reaching a consensus; accordingly, such as Figure 9 As shown, the specific implementation process of the step "sending the transaction to other distributed service nodes included in the target blockchain network so that the target blockchain network obtains the validity result of the transaction" includes:
[0173] Step S902: The transaction is sent to other distributed service nodes included in the target blockchain network, so that the blockchain network can reach a consensus on the transaction and obtain a consensus result.
[0174] Step S904: Store the target-level information contained in the transaction corresponding to the consensus result into the blockchain corresponding to the target-level information.
[0175] Specifically, after a distributed service node sends a transaction to other distributed service nodes within the target blockchain network, the target blockchain network reaches a consensus on the transaction based on the consensus reached by the distributed service nodes and other distributed service nodes. Reaching a consensus on a transaction requires the consensus reached by each node within the target blockchain network.
[0176] In one example, the validity result can be either a consensus result or a non-consensus result. Therefore, the distributed service node can obtain the consensus result or the non-consensus result for the transaction. If the validity result is a consensus result, that is, the target blockchain network reaches a consensus on the transaction, then the distributed service node can write the transaction into the corresponding blockchain. If the target level information is network level information, then the transaction and its corresponding network level information are written into the blockchain corresponding to the network level information. If the target level information is NF level information, then the transaction and its corresponding NF level information are written into the blockchain corresponding to the NF level information. If the target level information is service level information, then the transaction and its corresponding service level information are written into the blockchain corresponding to the service level information.
[0177] It is understood that after a transaction is written to the blockchain, the target blockchain network stores target-level information. Other distributed networks can perform subsequent updates, discovery, and other operations by querying the target-level information in the target blockchain network. The target blockchain network can contain blockchains corresponding to network-level information, NF (Network Functions)-Chain, and service-level information, respectively. These blockchains can be three blockchains: NW (Network)-Chain, NF (Network Functions)-Chain, and NS (Network Service)-Chain.
[0178] In this embodiment, by sending transactions to other distributed service nodes of the target blockchain network and enabling the target blockchain network to obtain the validity result of the transactions, the validity of the transactions can be determined in the target blockchain network. The target blockchain network writes the valid transactions into the blockchain network corresponding to the transactions, thereby storing the transaction information in the target blockchain network, achieving the effect of facilitating the query and discovery of the target-level information corresponding to the transactions.
[0179] In one embodiment, the specific implementation process of the steps following the validity verification based on target-level information and obtaining the verification result further includes:
[0180] When updating the blockchain corresponding to the target-level information based on the target-level information, the target-level information is sent to other blockchains corresponding to the distributed service nodes so that the other blockchains corresponding to the distributed service nodes can be updated based on the target-level information.
[0181] In a target blockchain network composed of distributed service nodes, when there are multiple blockchains, the target-level information stored on different blockchains at different levels is related to each other.
[0182] If target-level information updates the blockchain corresponding to that target-level information, then other blockchains associated with that blockchain network should also update their own blockchains based on the target-level information. Since distributed service nodes can communicate with other blockchains, they can send target-level information to other blockchains.
[0183] For example, when a service of the target network function NF becomes unavailable, the distributed service node will delete the data representing that service on the NS-Chain and should update the associated NF data on the NF-Chain. If the unavailability of the service will cause the failure of a specific network capability, the associated network data on the NW-Chain should also be updated.
[0184] Specifically, after updating the target-level information to the first blockchain, the distributed service node sends the target-level information to other blockchain networks so that the distributed service node can write the target-level information into other blockchain networks, where other blockchains can be the second blockchain or the third blockchain.
[0185] Optionally, as an implementation example Figure 14 As shown, if Chain 3NS-Chain is a blockchain network that updates target-level information, then the distributed service nodes update the corresponding content in Chain 1NF-Chain and Chain 2NW-Chain based on the target-level information (service-level information).
[0186] In this embodiment, by updating multiple blockchain networks corresponding to the target level information through distributed service nodes, the effect of direct cross-chain data synchronization by distributed service nodes can be achieved.
[0187] In one embodiment, such as Figure 10 As shown, the specific implementation process of the network function registration method also includes:
[0188] S1002, Receive discovery request sent by NF service management function.
[0189] S1004, Based on the discovery request, query whether there is target-level information in the target blockchain network that matches the discovery request.
[0190] S1006 If the target blockchain network contains level information matching the discovery request at the target level, a discovery response message is sent to the NF service management function.
[0191] The discovery request is used to instruct distributed service nodes to determine the level information of the target level that matches the discovery request.
[0192] Specifically, if a node in a distributed network needs to determine whether a certain target network function (NF) exists in the entire network, it will submit a discovery request for a certain service or function to the NF service management function. After receiving the discovery request, the NF service management function will generate a discovery request corresponding to the discovery request.
[0193] The NF service management function sends a discovery request to the distributed service nodes. Upon receiving the discovery request, the distributed service nodes can determine whether the service or function corresponding to the discovery request is recorded in the target blockchain network. They then send a discovery response message carrying the target level information corresponding to the required service or function to the NF service management function. The NF service management function can obtain the discovery result based on the discovery response message.
[0194] Specifically, the NF service management function generates a discovery request and sends it to the distributed service nodes. The distributed service nodes determine whether there is target-level information in the target blockchain network that matches the discovery request. If target-level information that matches the discovery request exists, the discovery response message can be a discovery success response message, which is returned to the NF service management function. Conversely, if no target-level information that matches the discovery request exists, the discovery response message can be a discovery failure response message, which is returned to the NF service management function.
[0195] The discovery response message carries level information about the target level.
[0196] Specifically, after the distributed service node determines the discovery response message, it sends the discovery response message to the NF service management function, which then receives the discovery response message.
[0197] In one embodiment, after the distributed service node obtains the discovery result of the target level information matching the discovery request, it generates a discovery response message regardless of whether the discovery is successful or unsuccessful, and returns the discovery response message to the NF service management function so that the NF service management function can obtain the final discovery result.
[0198] In this embodiment, by receiving a discovery request sent by the NF service management function, and querying whether there is target level information in the target blockchain network that matches the discovery request, it is possible to determine whether there is a service or capability in the target blockchain network that meets the discovery request, thereby improving the discovery efficiency of network functions.
[0199] In one embodiment, such as Figure 11 As shown, the steps of the network function registration method, in their specific implementation process, also include:
[0200] Step S1102: Receive the update request corresponding to the target level information sent by the NF service management function.
[0201] Step S1104: Generate a transaction based on the update content in the update request, and send the transaction to other distributed service nodes in the target blockchain network so that the target blockchain network can reach a consensus on whether the transaction is valid and obtain the verification result message of the transaction from the target blockchain network.
[0202] Step S1106: Generate an update response message based on the verification result message and send the update response message to the NF service management function.
[0203] The update request carries the updated content corresponding to the target level information, enabling the distributed service nodes to perform update processing based on the updated content. Since the target level information corresponding to the target network function NF changes, the target level information registered in the target blockchain network should also be changed accordingly. Therefore, it is necessary to synchronize the updated content to the target blockchain network.
[0204] Based on this, the NF service management function generates an update request corresponding to the target level information before the update, and the update request carries the update content corresponding to the target level information; the update content is the level information after the target level information is updated. When the distributed service node receives the update request, the distributed service node can update the corresponding level information in the target blockchain network based on the update content.
[0205] Specifically, the NF service management function sends an update request corresponding to the target level information to the distributed service nodes, so that the distributed service nodes can update the target level information before the update based on the update content.
[0206] Specifically, after the distributed service node updates the target-level information before the update based on the updated content, it obtains the result of the update processing; and generates an update-related message based on the result of the update processing, thereby notifying the NF service management function of the update processing result. The result of the update processing can be either a successful update or a failed update.
[0207] Specifically, the NF service management function receives update response messages of updated content returned by the distributed service nodes and synchronizes the update response messages to the distributed network corresponding to the NF service management function.
[0208] In this embodiment, by sending an update request to the distributed service node, the target-level information that has not been updated in the target blockchain network can be directly updated, thereby improving the update efficiency of network functions.
[0209] In this embodiment, by receiving update requests sent by the NF service management function, verifying the update content based on the update requests, and returning update response messages based on the verification results, the target-level information that has not been updated in the target blockchain network can be directly updated, thereby improving the update efficiency of network functions.
[0210] like Figure 12 As shown, the specific execution process of the above-mentioned network function registration method will be described in detail below with reference to a specific embodiment.
[0211] Specifically, operators can deploy distributed service nodes, which together form a blockchain network to build an NW-Chain. This NW-Chain is a blockchain that stores network-level information. The networks corresponding to each distributed service node can register or update based on the network-level information on the blockchain.
[0212] Network function NF in distributed network A sends a service registration / update request to the NF service management function. This request includes the target level information (NF level information) corresponding to the NF. The NF service management function verifies the validity of the received request. If invalid, it returns a response explaining the reason; if valid, it temporarily stores the relevant information.
[0213] 1. Generate network-level information; specifically, the NF service management function can generate network-level information based on NF-level information.
[0214] 2. Network-level information registration / update request; Specifically, the NF service management function sends a network-level information registration / update request to the distributed service nodes.
[0215] 3. Create transactions: Distributed service nodes use network-level information to create transactions.
[0216] 4. Sending the transaction: The distributed service node sends the transaction to other distributed service nodes in the blockchain network.
[0217] 5. The blockchain network reaches a consensus on the transaction, that is, whether the transaction is valid.
[0218] 6. Distributed service nodes write transactions to the blockchain, and each distributed service node writes valid transactions to NW-Chain.
[0219] 7. Network-level information registration / update response: The distributed service node returns a successful network-level information registration / update response to the NF service management function.
[0220] Specifically, after receiving the response, the NF service management function saves the NF level information and returns a registration / update response to the NF. Now, the network level information of distributed network A is available, and other distributed networks can obtain the capabilities of distributed network A through NW-Chain. The network registration method provided in this embodiment also includes a blockchain-based network level information discovery step, which can specifically be:
[0221] 8. Network Level Information Discovery Request: The NF service management function of distributed network B initiates a network level information query request to the distributed service node, specifying which capabilities the requested network should support.
[0222] 9. Query the blockchain: the distributed service node queries NW-Chain and filters out all networks that have registered and provide the requested capabilities.
[0223] 10. Network-level information discovery response, distributed service nodes return a response.
[0224] Based on this, distributed network B can initiate capability calls to distributed network A. Detailed information about NFs is only registered within the NF service management function of this network; the blockchain network composed of distributed service nodes only stores network-level information generated from NF-level information.
[0225] As an example, the distributed service nodes establish a second blockchain (hereinafter referred to as NF-Chain) outside of NW-Chain to store detailed information (i.e., NF-level information) of the core network NF.
[0226] Specifically, operators can deploy distributed service nodes, each forming a blockchain network, establishing an NW-Chain and an NF-Chain respectively. The NF-Chain can be a blockchain network storing NF-level information. The networks corresponding to each distributed service node can register / update based on the two-level information of the blockchain.
[0227] Network function NF in distributed network A sends a service registration / update request to the NF service management function. This request contains NF level information. The NF service management function verifies the validity of the received request. If invalid, it returns a response explaining the reason; if valid, it temporarily stores the relevant information, such as... Figure 13 As shown:
[0228] 1. NF Level Information Registration / Update Request; Specifically, the NF service management function sends NF level information registration / update requests to the distributed service nodes.
[0229] 2. Create a transaction: Distributed service nodes create transactions using NF-level information.
[0230] 3. Sending the transaction: The distributed service node sends the transaction to other distributed service nodes in the blockchain network.
[0231] 4. The blockchain network reaches a consensus on the transaction, that is, whether the transaction is valid.
[0232] 5. Distributed service nodes write transactions into the NF-Chain, and each distributed service node writes valid transactions into the NF-Chain.
[0233] 6. NF Level Information Registration / Update Response: The distributed service node returns a successful NF level information registration / update response to the NF service management function.
[0234] Now, the NF level information of core network A is available, and other core networks can obtain the NF information of core network A through NF-Chain.
[0235] 7. Generate network-level information: The NF service management function generates network-level information based on the NF-level information.
[0236] 8. Network Level Information Registration / Update Request: The NF service management function sends a network level information registration / update request to the distributed service nodes.
[0237] 9. Create a transaction: Distributed service nodes create transactions using network-level information.
[0238] 10. Sending the transaction: The distributed service node sends the transaction to other distributed service nodes in the blockchain network.
[0239] 11. The blockchain network reaches a consensus on the validity of a transaction.
[0240] 12. Distributed service nodes write transactions to NW-Chain, and each distributed service node writes valid transactions to NW-Chain.
[0241] 13. Network-level information registration / update response: The distributed service node returns a successful network-level information registration / update response to the NF service management function.
[0242] After receiving the response, the NF service management function returns a registration / update response to the NF. Now, the network-level and NF-level information of distributed network A are available, and other distributed networks can obtain the capabilities and services of distributed network A through the NW-Chain and NF-Chain.
[0243] C) Two-level information discovery based on blockchain:
[0244] 1. Distributed network B initiates a network capability query request to the distributed service node (specifying which capabilities the requested network should support).
[0245] 2. Distributed service nodes query NW-Chain and filter out all networks that have registered with NW-Chain and provide the requested capabilities.
[0246] 3. The distributed service nodes return a network capability query response.
[0247] 4. Distributed network B initiates an NF service query request (specifying which services the requested NF should support).
[0248] 5. Distributed service nodes NF-Chain filter out all NFs that have registered with NF-Chain and provide the requested service.
[0249] 6. The distributed service node returns the NF service response.
[0250] In the aforementioned method, the ServiceList field in the NF level information stores complete information about all services of a specific NF instance in the form of a list.
[0251] As an example, distributed service nodes could establish a third blockchain (hereinafter referred to as NS-Chain) outside of NW-Chain and NF-Chain to store detailed information (i.e., service level information) of NF examples. The NS-Chain could be a blockchain network that stores service level information.
[0252] Based on the aforementioned extended method of this application, the corresponding information registration and discovery method is as follows:
[0253] A) The operator deploys distributed service nodes, and each node forms a blockchain network, building NW-Chain, NF-Chain and NS-Chain respectively.
[0254] B) Blockchain-based three-level information registration / update.
[0255] C) Blockchain-based three-level information discovery.
[0256] The complete blockchain network topology is as follows Figure 14 As shown. Depending on the number of blockchains deployed, there are three blockchain construction schemes. The blockchain between distributed service node 1 and distributed service node 2 can include chain 1, chain 2, and chain 3. The blockchain construction scheme can include:
[0257] Chain construction scheme A: Chain 1;
[0258] Chain construction scheme B: Chain 1 + Chain 2;
[0259] Chain building scheme C: Chain 1 + Chain 2 + Chain 3.
[0260] When a blockchain network composed of distributed service nodes has multiple chains, information stored at different levels on different chains is related to each other. For example, when a service in NF becomes unavailable, the distributed service node will delete the data representing that service on NS-Chain and should update the associated NF data on NF-Chain. If the unavailability of that service will cause the failure of a specific network capability, the associated network data on NW-Chain should also be updated.
[0261] In the aforementioned process, each blockchain is unaware of whether the information related to each chain is synchronized. Alternatively, cross-chain technology can be used to achieve collaborative updates of information at different levels throughout the blockchain network. If cross-chain technology is supported, in Solution B, chain 1 and chain 2 should support cross-chain interoperability; similarly, in Solution C, chain 1 and chain 2, as well as chain 2 and chain 3, should support cross-chain interoperability.
[0262] The data structures corresponding to the various blockchains storing information at different levels are shown below:
[0263] On a blockchain network, the data structure of a blockchain (hereinafter referred to as NW-Chain) that stores network-level information can contain the following:
[0264] NetworkIdentifier: A unique network ID (MCC+MNC+number, network slice identifier, or a completely new numbering system); AccessType: Supported access methods (6G / 5G / 4G, WiFi, satellite access, near-field communication, etc.); Location: Location information; Coverage: Coverage area; Operator: Operating entity; NetworkCapacityInfo: Network supported capabilities.
[0265] On a blockchain network, the data structure of NF-Chain can contain the following:
[0266] NfInstanceID: A unique NF instance ID; NfType: The NF type of the instance (e.g., AMF, SMF, etc.); AllowedCapacity: Supported capabilities, corresponding to the element in NetworkCapacityInfo in NW-Chain; HNId: The ID of the home network, corresponding to NetworkIdentifier in NW-Chain; Ipv4Addr: The IPv4 address of the instance; Ipv6Addr: The IPv6 address of the instance; ServiceList: The service list of the instance.
[0267] On a blockchain network, the data structure of NS-Chain can contain the following:
[0268] ServiceInstanceId: A unique service instance ID; ServiceName: The service name; HNfId: The ID of the NF to which it belongs (i.e., the NfInstanceId in the NF-Chain); Port: The port number; AllowedNfTypes: The NF types that are allowed to access this service.
[0269] like Figure 15As shown, the network function registration method described above will be described in detail below with reference to a specific embodiment. The network access method provided in this embodiment can be used in existing 5G networks and future evolved versions of 5G networks. This embodiment includes a functional network, a distributed network A, and a distributed network B.
[0270] Functional Networks: Meeting users' value-added service needs, functional networks are deployed on demand, with multiple distributed networks sharing a single functional network. Functional networks include various functions: an IMS-enhanced holographic communication network; a dedicated sensing service network; and an intelligent service network (for scheduling data, computing power, and algorithms to complete intelligent tasks, etc.).
[0271] Distributed network A and distributed network B include two types: 2C edge network and 2B dedicated network.
[0272] Distributed network A and distributed network B can meet the low-latency access requirements of 2C and basic private network services of 2B (such as access services that do not require users to leave the campus).
[0273] The network includes Network Repository Function (NRF), Access and Mobility Management Function (AMF), Session Management Function (SMF), User Plane Function (UPF), Service Communication Proxy (SCP), and Data Network (DN). In addition, there are User Equipment (UE) and Radio Access Network (RAN), which communicate with the aforementioned distributed network A and distributed network B.
[0274] In various networks, NRF serves as the NF service manager, introducing a new NF: DSN (Distributed Service Node) to form a blockchain.
[0275] The network access method provided in this embodiment enhances the flexibility of network deployment, meets the needs of dynamic and frequent service calls involving multiple parties, can selectively modify or provide some information according to the request requirements, helps improve performance under high concurrency, and can also avoid excessive exposure of information; simplifies the process of NF service registration and discovery, effectively solving the pain points and difficulties of traditional solutions; can avoid the loss and destruction of service data; and the service registration and discovery method of this invention is relatively easy to implement on the existing network.
[0276] It should be understood that although the steps in the flowcharts of the above embodiments are shown sequentially according to the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless explicitly stated herein, there is no strict order restriction on the execution of these steps, and they can be executed in other orders. Moreover, at least some steps in the flowcharts of the above embodiments may include multiple steps or multiple stages. These steps or stages are not necessarily completed at the same time, but can be executed at different times. The execution order of these steps or stages is not necessarily sequential, but can be performed alternately or in turn with other steps or at least some of the steps or stages of other steps.
[0277] Based on the same inventive concept, this application also provides a network function registration apparatus for implementing the network function registration method described above. The solution provided by this apparatus is similar to the implementation described in the above method; therefore, the specific limitations in one or more network function registration apparatus embodiments provided below can be found in the limitations of the network function registration method described above, and will not be repeated here.
[0278] In one embodiment, such as Figure 16 As shown, a network function registration device 1600 is provided for NF service management functions. The device includes: a level information receiving module, a registration request sending module, and a response message receiving module, wherein:
[0279] The level information receiving module 1601 is used to receive NF level information of a target network function NF, and determine target level information based on the NF level information. The target level information includes at least one of network level information, NF level information and service level information.
[0280] The registration request sending module 1602 is used to send a level information registration request to the distributed service node. The level information registration request carries target level information so that the distributed service node can perform registration processing based on the target level information.
[0281] The response message receiving module 1603 is used to receive the registration response message containing target-level information returned by the distributed service node.
[0282] Furthermore, the level information receiving module is specifically used to: generate network level information corresponding to the NF level information based on the NF level information, and use the network level information as the target level information.
[0283] Furthermore, the level information receiving module is specifically used to: determine the service level information in the NF level information based on the NF level information, and use the service level information as the target level information; or, determine the updated NF level information based on the NF level information, and use the updated NF level information as the target level information.
[0284] Furthermore, the device also includes: a level information discovery module, configured to send a discovery request to the distributed service node; the discovery request is used to instruct the distributed service node to determine the level information of a target level that matches the discovery request; and to receive a discovery response message returned by the distributed service node; the discovery response message carries the level information of the target level.
[0285] Furthermore, the device also includes: a level information update module, used to send an update request corresponding to the target level information to the distributed service node; the update request carries the update content corresponding to the target level information, so that the distributed service node performs update processing based on the update content; and receives an update response message of the update content returned by the distributed service node.
[0286] Each module in the aforementioned network function registration device can be implemented entirely or partially through software, hardware, or a combination thereof. These modules can be embedded in or independent of the processor in a computer device, or stored in the memory of a computer device as software, so that the processor can call and execute the operations corresponding to each module.
[0287] In one embodiment, such as Figure 17 As shown, a network function registration device 1700 is provided, applied to a distributed service node, which is a node in a target blockchain network. The target blockchain network includes multiple distributed service nodes. The device includes:
[0288] The registration request receiving module 1701 is used to receive a level information registration request sent by the NF service management function; the level information registration request carries target level information; the target level information includes at least one of network level information, NF level information and service level information;
[0289] The validity verification module 1702 is used to perform validity verification based on target-level information and obtain the verification result.
[0290] The response message sending module 1703 is used to generate a registration response message based on the verification result and send the registration response message to the NF service management function.
[0291] Furthermore, the validity verification module is specifically used to generate transactions based on target-level information and send the transactions to other distributed service nodes included in the target blockchain network, so that the target blockchain network obtains the validity result of the transactions; and to determine the verification result of the target-level information based on the validity result of the transactions.
[0292] Furthermore, the validity result is the result of reaching a consensus; the validity verification module is specifically used to send the transaction to other distributed service nodes included in the target blockchain network, so that the blockchain network can obtain a consensus result when it reaches a consensus on the transaction; the method further includes: storing the target level information contained in the transaction corresponding to the consensus result to the blockchain corresponding to the target level information.
[0293] Furthermore, the device also includes:
[0294] The blockchain network update module is specifically used to send the target-level information to other blockchain networks corresponding to the distributed service nodes when updating the blockchain network corresponding to the target-level information based on the target-level information, so that the other blockchain networks corresponding to the distributed service nodes can be updated based on the target-level information.
[0295] Furthermore, the device also includes:
[0296] The level information discovery module is specifically used to receive the discovery request sent by the NF service management function; based on the discovery request, query whether there is level information of the target level matching the discovery request in the target blockchain network; if there is level information of the target level matching the discovery request in the target blockchain network, then send a discovery response message to the NF service management function; the discovery response message carries the level information of the target level.
[0297] Furthermore, the device also includes:
[0298] The level information update module is specifically used to receive update requests corresponding to the target level information sent by the NF service management function; generate a transaction based on the update content in the update request, and send the transaction to other distributed service nodes in the target blockchain network so that the target blockchain network can reach a consensus on whether the transaction is valid and obtain the verification result message of the transaction from the target blockchain network; generate an update response message based on the verification result message, and send the update response message to the NF service management function.
[0299] Each module in the aforementioned network function registration device can be implemented entirely or partially through software, hardware, or a combination thereof. These modules can be embedded in or independent of the processor in a computer device, or stored in the memory of a computer device as software, so that the processor can call and execute the operations corresponding to each module.
[0300] In one embodiment, a computer device is provided, which may be a server, and its internal structure diagram may be as follows: Figure 18 As shown, this computer device includes a processor, memory, input / output (I / O) interfaces, and a communication interface. The processor, memory, and I / O interfaces are connected via a system bus, and the communication interface is also connected to the system bus via the I / O interfaces. The processor provides computational and control capabilities. The memory includes non-volatile storage media and internal memory. The non-volatile storage media stores the operating system, computer programs, and a database. The internal memory provides the environment for the operation of the operating system and computer programs stored in the non-volatile storage media. The database stores target-level information to be sent. The I / O interfaces are used for exchanging information between the processor and external devices. The communication interface is used for communicating with external terminals via a network connection. When executed by the processor, the computer program implements a network function registration method.
[0301] Those skilled in the art will understand that Figure 18 The structure shown is merely a block diagram of a portion of the structure related to the present application and does not constitute a limitation on the computer device to which the present application is applied. Specific computer devices may include more or fewer components than those shown in the figure, or combine certain components, or have different component arrangements.
[0302] In one embodiment, a network function registration system is also provided. The system includes NF service management functions and distributed service nodes. The distributed service nodes are nodes in a target blockchain network, which includes multiple distributed service nodes.
[0303] The NF service management function is used to receive NF level information corresponding to a target network function NF, and determine target level information based on the NF level information. The target level information includes at least one of network level information, NF level information and service level information.
[0304] The NF service management function is also used to send level information registration requests to distributed service nodes. The level information registration request carries the target level information.
[0305] The distributed service node is used to receive the level information registration request sent by the NF service management function; the level information registration request carries the target level information, performs validity verification based on the target level information, obtains the verification result; generates a registration response message based on the verification result, and sends the registration response message to the NF service management function;
[0306] The NF service management function is also used to receive registration response messages containing target-level information returned by distributed service nodes.
[0307] In one embodiment, a computer device is also provided, including a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to implement the steps in the above method embodiments.
[0308] In one embodiment, a computer-readable storage medium is provided having a computer program stored thereon that, when executed by a processor, implements the steps in the above method embodiments.
[0309] In one embodiment, a computer program product is provided, including a computer program that, when executed by a processor, implements the steps in the above method embodiments.
[0310] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, data stored, data displayed, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties, and the collection, use and processing of the relevant data shall comply with the relevant laws, regulations and standards of the relevant countries and regions.
[0311] Those skilled in the art will understand that all or part of the processes in the methods of the above embodiments can be implemented by a computer program instructing related hardware. The computer program can be stored in a non-volatile computer-readable storage medium, and when executed, it can include the processes of the embodiments of the above methods. Any references to memory, databases, or other media used in the embodiments provided in this application can include at least one of non-volatile and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetic random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. By way of illustration and not limitation, RAM can take many forms, such as Static Random Access Memory (SRAM) or Dynamic Random Access Memory (DRAM). The databases involved in the embodiments provided in this application may include at least one type of relational database and non-relational database. Non-relational databases may include, but are not limited to, blockchain-based distributed databases. The processors involved in the embodiments provided in this application may be general-purpose processors, central processing units, graphics processing units, digital signal processors, programmable logic devices, quantum computing-based data processing logic devices, etc., and are not limited to these.
[0312] The technical features of the above embodiments can be combined in any way. For the sake of brevity, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.
[0313] The embodiments described above are merely illustrative of several implementation methods of this application, and while the descriptions are specific and detailed, they should not be construed as limiting the scope of this patent application. It should be noted that those skilled in the art can make various modifications and improvements without departing from the concept of this application, and these all fall within the protection scope of this application. Therefore, the protection scope of this application should be determined by the appended claims.
Claims
1. A network function registration method, characterized by, The method applied to an NF service management function comprises: receiving NF level information of a target network function (NF), determining target level information based on the NF level information, the target level information comprising at least one of network level information, NF level information and service level information; wherein the NF service management function is a management node managing all nodes in a distributed network; the target network function (NF) is a node capable of providing network functions in the distributed network, and the target network function (NF) to be registered belongs to the same network as the NF service management function; sending a level information registration request to a distributed service node, the level information registration request carrying the target level information, so that the distributed service node performs registration processing based on the target level information; receiving a registration response message of the target level information returned by the distributed service node.
2. The method of claim 1, wherein, The method further comprises: generating network level information corresponding to the NF level information based on the NF level information, and taking the network level information as the target level information.
3. The method of claim 1, wherein, The method further comprises: determining service level information in the NF level information based on the NF level information, and taking the service level information as the target level information; or determining updated NF level information based on the NF level information, and taking the updated NF level information as the target level information.
4. The method of claim 1, wherein, The method further comprises: sending a discovery request to the distributed service node; the discovery request is used to instruct the distributed service node to determine level information of a target level matching the discovery request; receiving a discovery response message returned by the distributed service node; the discovery response message carries the level information of the target level.
5. The method of claim 1, wherein, The method further comprises: sending an update request corresponding to the target level information to the distributed service node; the update request carries update content corresponding to the target level information, so that the distributed service node performs update processing based on the update content; receiving an update response message of the update content returned by the distributed service node.
6. A network function registration method characterized by, The method applied to a distributed service node, the distributed service node being a node in a target blockchain network, the target blockchain network comprising a plurality of distributed service nodes, the method comprising: receive a level information registration request sent by an NF service management function; the level information registration request carries target level information, and the target level information includes at least one of network level information, NF level information and service level information; wherein the NF service management function is a management node for managing all nodes in a distributed network; the NF service management function is configured to receive NF level information corresponding to a target network function NF to be registered in a network to which the NF service management function belongs, and determine target level information based on the NF level information; the target network function NF is a node capable of providing a network function in the distributed network, and the target network function NF to be registered and the NF service management function belong to the same network; perform validity checking based on the target level information to obtain a checking result; generate a registration response message based on the checking result and send the registration response message to the NF service management function.
7. The method of claim 6, wherein, The validity checking based on the target level information to obtain a checking result includes: generating a transaction based on the target level information and sending the transaction to other distributed service nodes included in the target blockchain network, so that the target blockchain network obtains an effectiveness result of the transaction; determining a checking result of the target level information based on the effectiveness result of the transaction.
8. The method of claim 7, wherein, The effectiveness result is a consensus result; and the sending of the transaction to the other distributed service nodes included in the target blockchain network so that the target blockchain network obtains the effectiveness result of the transaction includes: sending the transaction to the other distributed service nodes included in the target blockchain network, so that the target blockchain network obtains a consensus result in the case of reaching a consensus on the transaction. The method further includes: storing the target level information included in the transaction corresponding to the consensus result to a blockchain corresponding to the target level information.
9. The method of claim 6, wherein, After the validity checking based on the target level information to obtain a checking result, the method further includes: in the case of updating the blockchain corresponding to the target level information based on the target level information, sending the target level information to other blockchains corresponding to the distributed service nodes, so that the other blockchains corresponding to the distributed service nodes are updated based on the target level information.
10. The method of claim 6, wherein, The method further includes: receiving a discovery request sent by the NF service management function; querying whether there is level information of a target level matching the discovery request in the target blockchain network based on the discovery request; if there is level information of a target level matching the discovery request in the target blockchain network, sending a discovery response message carrying the level information of the target level to the NF service management function.
11. The method of claim 6, wherein, The method further includes: receiving an update request corresponding to the target level information sent by the NF service management function; generate a transaction based on the update content in the update request, and send the transaction to other distributed service nodes in the target blockchain network, so that the target blockchain network reaches a consensus on whether the transaction is valid, and obtains a verification result message of the target blockchain network on the transaction; generate an update response message based on the verification result message, and send the update response message to the NF service management function.
12. A network function registration apparatus characterized by comprising: The application is applied to an NF service management function, and the device comprises: a level information receiving module, configured to receive NF level information of a target network function (NF), determine target level information based on the NF level information, and the target level information comprises at least one of network level information, NF level information and service level information; wherein the NF service management function is a management node for managing all nodes in a distributed network; the target network function (NF) is a node capable of providing network functions in the distributed network, and the target network function (NF) to be registered belongs to the same network as the NF service management function; a registration request sending module, configured to send a level information registration request to a distributed service node, and the level information registration request carries the target level information, so that the distributed service node performs registration processing based on the target level information; a response message receiving module, configured to receive a registration response message of the target level information returned by the distributed service node.
13. A network function registration apparatus characterized by comprising: The application is applied to a distributed service node, and the distributed service node is a node in a target blockchain network, the target blockchain network comprises a plurality of distributed service nodes, and the device comprises: a registration request receiving module, configured to receive a level information registration request sent by an NF service management function; the level information registration request carries target level information; the target level information comprises at least one of network level information, NF level information and service level information; wherein the NF service management function is a management node for managing all nodes in a distributed network; the NF service management function is configured to receive NF level information corresponding to a target network function (NF) to be registered in a network to which the NF service management function belongs, and determine target level information based on the NF level information; the target network function (NF) is a node capable of providing network functions in the distributed network, and the target network function (NF) to be registered belongs to the same network as the NF service management function; an effectiveness verification module, configured to perform effectiveness verification based on the target level information, and obtain a verification result; a response message sending module, configured to generate a registration response message based on the verification result, and send the registration response message to the NF service management function.
14. A network function registration system, characterized by, The system comprises an NF service management function and a distributed service node, the distributed service node is a node in a target blockchain network, the target blockchain network comprises a plurality of distributed service nodes, and the system comprises: The NF service management function is configured to receive NF level information of a target network function (NF), determine target level information based on the NF level information, and the target level information comprises at least one of network level information, NF level information, and service level information; the NF service management function is a management node for managing all nodes in a distributed network; the target network function (NF) is a node in the distributed network that can provide network functions, and the target network function (NF) to be registered belongs to the same network as the NF service management function. The NF service management function is further configured to send a level information registration request to a distributed service node, and the level information registration request carries the target level information. The distributed service node is configured to receive the level information registration request sent by the NF service management function, the level information registration request carries the target level information, perform validity verification based on the target level information to obtain a verification result, generate a registration response message based on the verification result, and send the registration response message to the NF service management function. The NF service management function is further configured to receive the registration response message of the target level information returned by the distributed service node.
15. A computer device comprising a memory and a processor, the memory storing a computer program, characterized in that, The processor executes the computer program to implement the steps of the method in any one of claims 1 to 11.
16. A computer readable storage medium having stored thereon a computer program, characterized in that, The computer program is executed by the processor to implement the steps of the method in any one of claims 1 to 11.
17. A computer program product comprising a computer program, characterized in that, The computer program is executed by the processor to implement the steps of the method in any one of claims 1 to 11.
Citation Information
Patent Citations
Virtual network function management method, NFVO, blockchain node and MANO network element
CN110727498A
Network node and method for supporting a service based architecture
CN113039752A