Node deployment method and apparatus, computer device, and storage medium

Abstract

The application relates to a node deployment method and device, computer equipment and a storage medium, and relates to the technical field of blockchains. The method comprises the following steps: a main control node of a blockchain subnet in communication connection with a main blockchain network, in response to a node registration request of a to-be-deployed subnet node in the blockchain subnet, acquiring node information of the to-be-deployed subnet node carried by the node registration request; writing the node information into a pre-stored node mapping table, and synchronizing the node mapping table to the main blockchain network; the main blockchain network is used for acquiring the node information of the to-be-deployed subnet node from the node mapping table, obtaining an approval result of the to-be-deployed subnet node according to the node information, and returning; in the case that the approval result represents that the approval is passed, triggering a deployment request to the to-be-deployed subnet node to deploy the to-be-deployed subnet node. The method can reduce the node deployment cost and improve the node deployment flexibility.

Description

Technical Field

[0001] This application relates to the field of blockchain technology, and in particular to a node deployment method, apparatus, computer equipment, and storage medium. Background Technology

[0002] With the development of blockchain technology, a technology has emerged that uses a blockchain subnet as an external network to connect to the main blockchain network, i.e., an internal network. Subnet nodes within the blockchain subnet can access data on the main blockchain network, while the main blockchain network can also monitor and manage these subnet nodes, thus ensuring secure and stable data transmission between the blockchain subnet and the main network.

[0003] In traditional technologies, when adding new subnet nodes to a blockchain subnet, even with network connectivity between the subnet and the mainnet, the deployment personnel still need to configure the mainnet connection separately in the newly added subnet nodes. Therefore, the existing blockchain subnet node deployment methods have high node deployment costs and low node deployment flexibility. Summary of the Invention

[0004] Therefore, it is necessary to provide a node deployment method, apparatus, computer equipment, computer-readable storage medium, and computer program product that can improve the deployment flexibility of subnet nodes in response to the above-mentioned technical problems.

[0005] In a first aspect, this application provides a node deployment method applied to the main control node of a blockchain subnet, wherein the main control node is communicatively connected to the blockchain mainnet, and the method includes:

[0006] In response to a node registration request from a subnet node to be deployed in the blockchain subnet, obtain the node information of the subnet node to be deployed carried in the node registration request;

[0007] The node information is written into a pre-stored node mapping table, and the node mapping table is synchronized to the blockchain mainnet; the blockchain mainnet is used to obtain the node information of the subnet node to be deployed from the node mapping table, and to obtain and return the approval result of the subnet node to be deployed based on the node information.

[0008] If the approval result indicates that the approval has been passed, a deployment request is triggered to the subnet node to be deployed in order to deploy the subnet node.

[0009] In one embodiment, the number of subnet nodes to be deployed is multiple; the step of writing the node information into a pre-stored node mapping table and synchronizing the node mapping table to the blockchain mainnet includes: writing the node information of each subnet node to be deployed into the node mapping table, and adding a temporary data identifier to the node information in the node mapping table; synchronizing the node mapping table to the blockchain mainnet according to a preset period; the blockchain mainnet is used to obtain the node information with the added temporary data identifier from the node mapping table, and obtain the approval result of the corresponding subnet node based on the node information with the added temporary data identifier and return it; the step of triggering a deployment request to the subnet node to be deployed to deploy the subnet node when the approval result indicates that the approval is passed includes: obtaining the first subnet node to be deployed to deploy with the approval result indicating that the approval is passed, and updating the temporary data identifier added to the node information of the first subnet node to be deployed stored in the node mapping table to an effective identifier; triggering a deployment request to the first subnet node to be deployed to deploy the first subnet node to be deployed.

[0010] In one embodiment, the method further includes: obtaining the approval result indicating that the second subnet node to be deployed has failed the approval, and deleting the node information of the second subnet node to be deployed stored in the node mapping table, so as to cancel the deployment of the second subnet node to be deployed.

[0011] In one embodiment, the node information includes first certificate information provided by the subnet node to be deployed; writing the node information into a pre-stored node mapping table includes: performing certificate authentication on the subnet node to be deployed based on the first certificate information, and obtaining the certificate authentication result of the subnet node to be deployed; if the certificate authentication result is successful, performing quantity verification on the number of subnet nodes included in the blockchain subnet, and obtaining the quantity verification result of the blockchain subnet; if the quantity verification result is successful, writing the node information into the pre-stored node mapping table.

[0012] In one embodiment, the step of performing certificate authentication on the subnet node to be deployed based on the first certificate information and obtaining the certificate authentication result of the subnet node to be deployed includes: obtaining pre-stored second certificate information; and determining the certificate authentication result as certificate authentication passed if the first certificate information is certificate information issued based on the second certificate information.

[0013] In one embodiment, the number of subnet nodes contained in the blockchain subnet is verified to obtain the number verification result of the blockchain subnet, including: obtaining a subnet node number threshold pre-set by the blockchain mainnet for the blockchain subnet; if the number of subnet nodes contained in the blockchain subnet does not reach the subnet node number threshold, the number verification result is determined as a number verification passed.

[0014] In one embodiment, the method further includes: if the certificate authentication result is that the certificate authentication fails, or the quantity verification result is that the verification fails, cancel writing the node information into the pre-stored node mapping table, so as to cancel the deployment of the subnet node to be deployed.

[0015] In one embodiment, the node information includes the address information of the subnet node to be deployed; after triggering a deployment request to the subnet node to be deployed to deploy the subnet node when the approval result indicates that the approval has been passed, the method further includes: responding to the mainnet interaction request triggered by the deployed target subnet node, obtaining the node identifier of the target subnet node, and sending the mainnet interaction request carrying the node identifier to the blockchain mainnet; the blockchain mainnet is used to obtain the response result corresponding to the mainnet interaction request and return the response result carrying the node identifier; receiving the response result returned by the blockchain mainnet, and obtaining the target address information of the target subnet node from the node mapping table according to the node identifier; and returning the response result to the target subnet node according to the target address information.

[0016] Secondly, this application also provides a node deployment device for use as a main control node in a blockchain subnet, wherein the main control node is communicatively connected to the blockchain mainnet, and the device includes:

[0017] The registration request response module is used to respond to the node registration request of the subnet node to be deployed in the blockchain subnet, and to obtain the node information of the subnet node to be deployed carried in the node registration request;

[0018] The node mapping synchronization module is used to write the node information into a pre-stored node mapping table and synchronize the node mapping table to the blockchain mainnet; the blockchain mainnet is used to obtain the node information of the subnet node to be deployed from the node mapping table, and obtain the approval result of the subnet node to be deployed based on the node information and return it.

[0019] The subnet node deployment module is used to trigger a deployment request to the subnet node to be deployed when the approval result indicates that the approval has been passed, so as to deploy the subnet node to be deployed.

[0020] Thirdly, 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 perform the following steps:

[0021] In response to a node registration request from a subnet node to be deployed in the blockchain subnet, obtain the node information of the subnet node to be deployed carried in the node registration request;

[0022] The node information is written into a pre-stored node mapping table, and the node mapping table is synchronized to the blockchain mainnet; the blockchain mainnet is used to obtain the node information of the subnet node to be deployed from the node mapping table, and to obtain and return the approval result of the subnet node to be deployed based on the node information.

[0023] If the approval result indicates that the approval has been passed, a deployment request is triggered to the subnet node to be deployed in order to deploy the subnet node.

[0024] Fourthly, 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, performs the following steps:

[0025] In response to a node registration request from a subnet node to be deployed in the blockchain subnet, obtain the node information of the subnet node to be deployed carried in the node registration request;

[0026] The node information is written into a pre-stored node mapping table, and the node mapping table is synchronized to the blockchain mainnet; the blockchain mainnet is used to obtain the node information of the subnet node to be deployed from the node mapping table, and to obtain and return the approval result of the subnet node to be deployed based on the node information.

[0027] If the approval result indicates that the approval has been passed, a deployment request is triggered to the subnet node to be deployed in order to deploy the subnet node.

[0028] Fifthly, this application also provides a computer program product. The computer program product includes a computer program that, when executed by a processor, performs the following steps:

[0029] In response to a node registration request from a subnet node to be deployed in the blockchain subnet, obtain the node information of the subnet node to be deployed carried in the node registration request;

[0030] The node information is written into a pre-stored node mapping table, and the node mapping table is synchronized to the blockchain mainnet; the blockchain mainnet is used to obtain the node information of the subnet node to be deployed from the node mapping table, and to obtain and return the approval result of the subnet node to be deployed based on the node information.

[0031] If the approval result indicates that the approval has been passed, a deployment request is triggered to the subnet node to be deployed in order to deploy the subnet node.

[0032] The aforementioned node deployment method, apparatus, computer equipment, storage medium, and computer program product, through the main control node of the blockchain subnet connected to the blockchain mainnet, responds to the node registration request of the subnet node to be deployed in the blockchain subnet, obtains the node information of the subnet node to be deployed carried in the node registration request; writes the node information into a pre-stored node mapping table, and synchronizes the node mapping table to the blockchain mainnet; the blockchain mainnet is used to obtain the node information of the subnet node to be deployed from the node mapping table, obtain the approval result of the subnet node to be deployed based on the node information, and return it; if the approval result indicates that the approval is passed, a deployment request is triggered to the subnet node to be deployed to deploy the subnet node. This application establishes a master management node in the blockchain subnet for communication with the main blockchain network. This allows for the deployment of subnet nodes by writing the node information of the subnet node to be deployed into a node mapping table pre-stored in the master management node. The master management node then synchronizes the node mapping table to the main blockchain network, and the main blockchain network receives the approval result for the subnet node to be deployed. Once approved, the deployment of the subnet node can be executed. This method of deploying subnet nodes achieves deployment through interaction between the master management node and the main blockchain network, eliminating the need for separate configuration of the connection between the subnet node and the main blockchain network. This reduces node deployment costs and improves node deployment flexibility. Attached Figure Description

[0033] Figure 1 This is an application environment diagram of a node deployment method in one embodiment;

[0034] Figure 2 This is a flowchart illustrating a node deployment method in one embodiment;

[0035] Figure 3 This is a schematic diagram of the process of deploying subnet nodes to be deployed in one embodiment;

[0036] Figure 4 This is a schematic diagram illustrating the process of writing node information into a node mapping table in one embodiment;

[0037] Figure 5This is a flowchart illustrating the process of obtaining the interaction response result with the blockchain mainnet in one embodiment;

[0038] Figure 6 This is an architecture diagram of a cross-network monitoring and management system for consortium blockchain nodes in an application example.

[0039] Figure 7 This is a flowchart illustrating the node admission process in an application instance.

[0040] Figure 8 This is a structural block diagram of a node deployment device in one embodiment;

[0041] Figure 9 This is an internal structural diagram of a computer device in one embodiment. Detailed Implementation

[0042] 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.

[0043] The node deployment method provided in this application embodiment can be applied to, for example, Figure 1In the application environment shown, the blockchain subnet 101 includes a master control node 101a and a subnet node 101b to be configured. The subnet node 101b communicates with the main blockchain network 102 through the master control node 101a. Specifically, when the subnet node 101b needs to be configured, it can trigger a node registration request to the master control node 101a in the blockchain subnet 101. The master control node 101a can then respond to the registration request, obtain the node information of the subnet node 101b from the request, and write the node information into a pre-stored node mapping table in the master control node 101a. This node mapping table can be synchronized to the main blockchain network 102 by the master control node 101a. After receiving the node mapping table synchronized by the main control node 101a, the blockchain mainnet 102 can extract the node information of the subnet node 101b to be configured from the node mapping table, thereby approving the node configuration of the subnet node 101b to be configured. After obtaining the approval result of the subnet node 101b to be configured, the approval result can be returned to the main control node 101a. If the approval result indicates that the approval is successful, the main control node 101a can also trigger a deployment request to the subnet node 101b to be deployed, thereby realizing the deployment of the subnet node 101b to be deployed. The blockchain subchain 101 and the blockchain main chain 102 can be blockchains composed of multiple server nodes, and the main control node 101a and the subnet node 101b to be deployed can be implemented through independent servers or server clusters composed of multiple servers.

[0044] In one embodiment, such as Figure 2 As shown, a node deployment method is provided, which can be applied to Figure 1 Taking the main control node 101a as an example, the following steps are included:

[0045] Step S201: In response to the node registration request of the subnet node 101b to be deployed in the blockchain subnet 101, obtain the node information of the subnet node 101b to be deployed carried in the node registration request.

[0046] The node registration request is triggered by the subnet node 101b to register itself for deployment. The node information includes details about the subnet node 101b, such as its IP address and port number. Specifically, when deployment is needed, the subnet node 101b can trigger a node registration request to the main management node 101a, including its node information. Upon receiving the request, the main management node 101a can respond and extract the node information from the request.

[0047] Step S202: Write the node information into the pre-stored node mapping table and synchronize the node mapping table to the blockchain mainnet 102; the blockchain mainnet 102 is used to obtain the node information of the subnet nodes to be deployed from the node mapping table, and obtain the approval result of the subnet nodes to be deployed based on the node information and return it.

[0048] The node mapping table stores the node information of each subnet node in blockchain subnet 101. This node mapping table can be pre-stored in the main control node 101a. Specifically, after receiving the node information of the subnet node 101b to be deployed, the main control node 101a can write the node information into the node mapping table pre-stored in the main control node 101a. Then, the main control node 101a can send the node mapping table containing the node information of the subnet node 101b to the blockchain mainnet 102 for synchronization. After receiving the node mapping table sent by the main control node 101a, the blockchain mainnet 102 can obtain the node information of the subnet node 101b to be deployed from the node mapping table, thereby approving the subnet node 101b to be deployed, and after obtaining the approval result of the subnet node 101b to be deployed, return the approval result to the main control node 101a.

[0049] Step S203: If the approval result indicates that the approval has been passed, a deployment request is triggered to the subnet node to be deployed in order to deploy the subnet node.

[0050] If the blockchain mainnet 102 approves the deployment of the subnet node 101b, meaning the blockchain mainnet 102 agrees to the deployment of the subnet node 101b, then the main control node 101a can trigger a deployment request to the subnet node 101b to execute the deployment operation. The subnet node 101b can then respond to the deployment request, thereby completing the deployment process of the subnet node 101b.

[0051] In the above node deployment method, the main control node 101a of the blockchain subnet 101, which is connected to the blockchain mainnet 102, responds to the node registration request of the subnet node 101b to be deployed in the blockchain subnet 101, and obtains the node information of the subnet node 101b to be deployed carried in the node registration request; writes the node information into a pre-stored node mapping table, and synchronizes the node mapping table to the blockchain mainnet 102; the blockchain mainnet 102 is used to obtain the node information of the subnet node to be deployed from the node mapping table, and obtains the approval result of the subnet node to be deployed based on the node information and returns it; if the approval result indicates that the approval is passed, a deployment request is triggered to the subnet node 101b to be deployed, so as to deploy the subnet node 101b. This application establishes a master management node 101a in the blockchain subnet 101 for communication with the blockchain mainnet 102. This allows for the deployment of subnet nodes by writing the node information of the subnet node 101b to be deployed into a node mapping table pre-stored in the master management node. The master management node then synchronizes the node mapping table to the blockchain mainnet, and the blockchain mainnet receives the approval result for the subnet node 101b. Once approved, the deployment of the subnet node can be executed. This method of deployment allows for subnet node deployment through interaction between the master management node 101a and the blockchain mainnet 102, eliminating the need for separate configuration of the connection between the subnet node and the blockchain mainnet. This reduces node deployment costs and improves node deployment flexibility.

[0052] In one embodiment, the number of subnet nodes to be deployed is multiple; such as Figure 3 As shown, step S202 may further include:

[0053] Step S301: Write the node information of each subnet node 101b to be deployed into the node mapping table, and add temporary data identifiers to the node information in the node mapping table.

[0054] Step S302: Synchronize the node mapping table to the blockchain mainnet 102 according to a preset cycle; the blockchain mainnet 102 is used to obtain node information with added temporary data identifiers from the node mapping table, and obtain and return the approval results of the corresponding subnet nodes based on the node information with added temporary data identifiers.

[0055] The temporary data identifier is used to indicate that the node information is temporary, meaning that the corresponding subnet node 101b to be deployed belongs to a subnet node that has not been approved by the blockchain mainnet 102. In this embodiment, there can be multiple subnet nodes 101b to be deployed in the blockchain subnet 101. If the node mapping table is synchronized to the blockchain mainnet 102 immediately after the node information of each subnet node to be deployed is written, then it is necessary to establish the connection between the main control node 101a and the blockchain mainnet 102 multiple times to execute the approval process of the blockchain mainnet 102 for each subnet node 101b to be deployed. This method may cause a waste of transmission resources. Therefore, in this embodiment, in order to reduce the waste of network resources, the blockchain mainnet 102 can process the approval of multiple subnet nodes 101b to be deployed in batches. In this way, the main control node 101a only needs to make a network connection with the blockchain mainnet 102 once, and can synchronize the node mapping table that records the node information of multiple subnet nodes 101b to be deployed to the blockchain mainnet 102, and then the blockchain mainnet 102 can process the batch approval of each subnet node 101b to be deployed.

[0056] Specifically, each time the main control node 101a writes the node information of the subnet node 101b to be deployed into the node mapping table, the main control node 101a can also add a temporary data identifier to the written node information. This identifier indicates that the node information is temporary and that the corresponding subnet node 101b to be deployed belongs to a subnet node that has not been approved by the blockchain mainnet 102. Afterwards, the main control node 101a can synchronize the node mapping table to the blockchain mainnet 102 according to a pre-set cycle, such as daily or weekly. Upon receiving the node mapping table, the blockchain mainnet 102 can first extract the node information with the added temporary data identifier, i.e., identify the unapproved subnet nodes, and then process the approval for each unapproved subnet node separately. After obtaining the approval result for each subnet node, the result is returned to the main control node 101a.

[0057] Step S203 may further include:

[0058] Step S303: Obtain the approval result indicating the first subnet node to be deployed that has passed the approval, and update the temporary data identifier added to the node information of the first subnet node to be deployed stored in the node mapping table to the effective identifier;

[0059] Step S304: Trigger a deployment request to the first subnet node to be deployed in order to deploy the first subnet node to be deployed.

[0060] The first subnet node to be deployed refers to the subnet node 101b among multiple subnet nodes 101b that has passed the approval process. The effectiveness identifier indicates that the corresponding node information is effective data, meaning that the corresponding subnet node 101b has been approved by the blockchain mainnet 102. Specifically, after receiving the approval results for each subnet node 101b from the blockchain mainnet 102, the main control node 101a can identify the subnet node 101b whose approval result indicates it has passed, and designate it as the first subnet node to be deployed. Furthermore, it can update the temporary data identifier added to the node information of the first subnet node to be deployed stored in the node mapping table to the effectiveness identifier. Simultaneously, it can trigger deployment requests to each first subnet node to be deployed, thereby implementing deployment processing for each first subnet node to be deployed.

[0061] In this embodiment, when the main control node 101a writes the node information of the subnet node 101b to be deployed into the node mapping table, it can also add a temporary data identifier to the node information and synchronize the node mapping table to the blockchain mainnet 102 according to a set period. The blockchain mainnet 102 can then use the temporary data identifier to perform batch approval processing of the subnet nodes 101b to be deployed. Afterwards, if the approval is successful, the main control node 101a can update the temporary data identifier to an effective identifier to achieve batch deployment of subnet nodes, thereby reducing the waste of transmission resources and improving the utilization rate of transmission resources.

[0062] In addition, the node deployment method also includes: obtaining the approval result indicating the second subnet node to be deployed that has failed the approval, and deleting the node information of the second subnet node to be deployed stored in the node mapping table to cancel the deployment of the second subnet node to be deployed.

[0063] The second subnet node to be deployed refers to the subnet node 101b whose approval result is approved. If a subnet node 101b is the second subnet node to be deployed, that is, the main blockchain 102 does not agree to the deployment of the second subnet node to be deployed, then the main control node 101a can delete the node information of the above-mentioned second subnet node to be deployed stored in the node mapping table, thereby canceling the deployment process of the second subnet node to be deployed.

[0064] For example, multiple subnet nodes 101b to be deployed can be designated as node 1, node 2, and node 3. Each time the main control node 101a writes the node information of node 1, node 2, and node 3 into the node mapping table, it can add a temporary data identifier to each node's information. Then, the main control node 101a synchronizes the node mapping table to the blockchain mainnet 102 according to a preset period. The blockchain mainnet 102 can then filter out the node information with added temporary data identifiers from the node mapping table, i.e., the node information of node 1, node 2, and node 3, and process them separately. The approval result can be that node 1 and node 2 are approved, while node 3 is not approved. After the blockchain mainnet 102 returns the approval result, node 1 and node 2 can be designated as the first subnet nodes to be deployed. Therefore, the main control node 101a can update the temporary data identifiers of node 1 and node 2 to an effective identifier and trigger the deployment of node 1 and node 2, thus realizing the deployment of node 1 and node 2. Node 3 is then designated as the second subnet node to be deployed. At this point, the main control node 101a can delete the node information of Node 3 from the node mapping table and cancel the deployment process for Node 3.

[0065] In this embodiment, if the approval result indicates that the approval is not approved, the main control node 101a can delete the node information of the subnet node 101b to be deployed from the storage of the node mapping table, thereby canceling the deployment of the subnet node and releasing the storage of the node mapping table, further improving the storage utilization of the node mapping table.

[0066] In one embodiment, the node information includes the first certificate information provided by the subnet node 101b to be deployed; such as Figure 4 As shown, step S202 may further include:

[0067] Step S401: Based on the first certificate information, perform certificate authentication on the subnet node 101b to be deployed, and obtain the certificate authentication result of the subnet node 101b to be deployed.

[0068] The first certificate information refers to the certificate information provided by the subnet node 101b to the main control node 101a. In this embodiment, when the subnet node 101b initiates a node registration request to the main control node 101a, it can also send the certificate information it carries, i.e., the first certificate information, as part of the node information to the main control node 101a. After receiving the node information sent by the subnet node 101b, the main control node 101a can obtain the first certificate information from it, and then perform certificate authentication on the first certificate information to obtain the certificate authentication result of the subnet node 101b.

[0069] Step S402: If the certificate authentication result is that the certificate authentication is successful, the number of subnet nodes contained in the blockchain subnet 101 is verified, and the number verification result of the blockchain subnet 101 is obtained.

[0070] The quantity verification refers to verifying the number of nodes contained in the blockchain subnet 101. If the master control node 101a completes the certificate authentication of the subnet node 101b to be deployed in step S401, and the certificate authentication is successful, the master control node 101a can further verify the number of subnet nodes contained in the blockchain subnet 101 to obtain the quantity verification result of the blockchain subnet 101.

[0071] Step S403: If the quantity verification result is successful, write the node information into the pre-stored node mapping table.

[0072] Subsequently, if the quantity verification result of the blockchain subnet 101 obtained in step S402 is that the verification is passed, that is, when the blockchain subnet 101 meets the quantity verification conditions, the main control node 101a can write the node information of the subnet node 101b to be deployed into the node mapping table, so that the blockchain mainnet 102 can approve the node information of the subnet node 101b to be deployed through the node mapping table.

[0073] In this embodiment, after obtaining the node information of the subnet node 101b to be deployed, the master control node 101a can first perform certificate authentication on the subnet node 101b to be deployed, and perform quantity verification on the number of subnet nodes contained in the blockchain subnet 101. Only when the certificate authentication and quantity verification are both passed will the node information of the subnet node 101b to be deployed be written into the node mapping table, thereby improving the security of subnet node deployment.

[0074] Furthermore, step S401 may further include: obtaining pre-stored second certificate information; and, if the first certificate information is certificate information issued based on the second certificate information, determining the certificate authentication result as certificate authentication passed.

[0075] The second certificate information refers to the certificate information carried in the master control node 101a. In this embodiment, the process of the master control node 101a performing certificate authentication on the subnet node 101b to be deployed is as follows: first, it obtains the certificate information pre-stored in the master control node 101a as the second certificate information; then, it determines whether the first certificate information provided by the subnet node 101b to be deployed is the certificate information issued based on the second certificate information. If the first certificate information is the certificate information issued based on the second certificate information, it means that the sub-certificate provided by the subnet node 101b to be deployed is issued by the root certificate stored in the master control node 101a. At this time, the master control node 101a can determine the certificate authentication result as certificate authentication passed.

[0076] In this embodiment, the certificate authentication of the subnet node 101b to be deployed is performed by determining whether the first certificate information provided by the subnet node 101b to be deployed is issued by the second certificate information stored in the master control node 101a. By determining whether the subcertificate is issued by the root certificate, the certificate authentication of the subnet node 101b to be deployed is realized, thereby improving the security of certificate authentication.

[0077] In addition, step S402 may further include: obtaining the subnet node number threshold set in advance by the blockchain mainnet 102 for the blockchain subnet 101; if the number of subnet nodes contained in the blockchain subnet 101 does not reach the subnet node number threshold, the number verification result is determined as the number verification passed.

[0078] The subnet node number threshold represents the maximum number of subnet nodes that can be included in the blockchain subnet 101. This threshold can be pre-set by the blockchain mainnet 102 for the blockchain subnet 101 to ensure that the number of subnet nodes in the blockchain subnet 101 does not exceed the aforementioned subnet node number threshold.

[0079] Specifically, the mainnet 102 can pre-set the maximum number of subnet nodes for the subnet 101, i.e., the subnet node number threshold, and can upload this subnet node number threshold to the blockchain. Then, if the certificate authentication result is successful, the main control node 101a can retrieve the pre-set subnet node number threshold from the blockchain mainnet 102 and determine whether the current number of subnet nodes in the subnet 101 has reached the threshold. If it hasn't, it indicates that the subnet 101 can add more subnet nodes, and at this point, the main control node 101a can confirm that the quantity verification result of the subnet 101 has passed.

[0080] In this embodiment, the main blockchain 102 can also set a maximum number of subnet nodes for the blockchain subnet 101. Only when the number of subnet nodes in the blockchain subnet 101 has not reached the maximum number of subnet nodes will the main control node 101a determine the number verification result of the blockchain subnet 101 as passed, thereby controlling the number of nodes in the blockchain subnet 101 and further improving the intelligence of node deployment.

[0081] In one embodiment, the node deployment method may further include: canceling the writing of node information into a pre-stored node mapping table, so as to cancel the deployment of the subnet node to be deployed, if the certificate authentication result is that the certificate authentication fails or the quantity verification result is that the verification fails.

[0082] If the certificate authentication result is "authentication failed" or the quantity verification result is "verification failed", it indicates that the sub-certificate information held by the subnet node 101b to be deployed, i.e., the first certificate information, was not issued by the root certificate information held by the main control node 101a, i.e., the second certificate information. Alternatively, it indicates that the number of subnet nodes contained in the current blockchain subnet 101 has reached the maximum number set by the blockchain mainnet 102. In this case, the main control node 101a will not allow the node information of the aforementioned subnet node 101b to be deployed to be written into the node mapping table and will prohibit the deployment of the aforementioned subnet node 101b to be deployed.

[0083] In this embodiment, if the certificate authentication of the subnet node 101b to be deployed fails, or the quantity verification of the blockchain subnet 101 fails, then the main control node 101a can stop writing the node information of the subnet node 101b to be deployed into the node mapping table and prohibit the deployment of the aforementioned subnet node 101b, thereby ensuring the security of the subnet node deployment.

[0084] In one embodiment, the node information includes the address information of the subnet node 101b to be deployed; such as Figure 5 As shown, after step S203, the following may also be included:

[0085] Step S501: In response to the mainnet interaction request triggered by the deployed target subnet node, obtain the node identifier of the target subnet node, and send the mainnet interaction request carrying the node identifier to the blockchain mainnet; the blockchain mainnet is used to obtain the response result corresponding to the mainnet interaction request, and return the response result carrying the node identifier.

[0086] When deploying subnet node 101b, the node information of subnet node 101b may include its address information, such as its IP address. The target subnet node can be any subnet node in blockchain subchain 101 that has already been deployed. The mainnet interaction request is triggered by the target subnet node and is used to execute a request to interact with the blockchain mainchain 102. For example, it could be an interaction request to update or query the data of the blockchain mainchain 102. The response result refers to the response result of the mainnet interaction request, and the node identifier is used to identify the target subnet node that triggered the mainnet interaction request.

[0087] In this embodiment, after the deployment of subnet nodes in blockchain subnet 101 is completed, if a subnet node, i.e., the target subnet node, needs to interact with the blockchain mainnet 102, it must first trigger an interaction request with the main control node 101a to interact with the blockchain mainnet 102, instead of directly initiating the interaction request to the blockchain mainnet 102. After receiving the mainnet interaction request, blockchain subnet 101 can first determine the node identifier of the target subnet node that triggered the interaction request, and can send the mainnet interaction request carrying the node identifier to blockchain mainnet 102. Upon receiving the mainnet interaction request carrying the node identifier, blockchain mainnet 102 can respond to the mainnet interaction request, and after obtaining the response result, can return the response result carrying the node identifier to the main control node 101a.

[0088] Step S502: Receive the response result returned by the blockchain mainnet 102, and obtain the target address information of the target subnet node from the node mapping table according to the node identifier;

[0089] Step S503: Return the response result to the target subnet node according to the target address information.

[0090] The target address information refers to the address information corresponding to the target subnet node. This address information can be stored in the node information of the target subnet node contained in the node mapping table. Specifically, after the main control node 101a receives the response result returned by the blockchain mainnet 102, it can query the node mapping table based on the node identifier carried in the response result, and obtain the address information of the target subnet node corresponding to the node identifier from the node mapping table as the target address information. Then, according to the target address information, the response result is returned to the subnet node corresponding to the target address information, thus returning the response result to the target subnet node.

[0091] In this embodiment, after the deployment of subnet nodes is completed, if a deployed subnet node needs to interact with the main blockchain 102, it can trigger a main network interaction request to the main control node 101a. The main control node 101a then sends the main network interaction request carrying the node identifier of the subnet node to the main blockchain 102. After receiving the corresponding response, the main blockchain 102 can also return the response carrying the node identifier to the main control node 101a. The main control node 101a then queries the target address information corresponding to the node identifier to return the response to the target subnet node. This method enables interaction between deployed subnet nodes and the main blockchain 102 through the main control node 101a, eliminating the need for deployed subnet nodes to directly interact with the main blockchain 102, thereby improving the convenience of node interaction management.

[0092] In one application example, a method for cross-network monitoring and management of consortium blockchain nodes is also provided. This method can be applied to, for example... Figure 6 In the blockchain system shown, the control program mainly performs the following functions:

[0093] 1. Docker: This module integrates go-dockerclient, which encapsulates access to the Docker API, enabling calls to Docker and managing node startup, shutdown, node monitoring, and node image management through Docker and blockchain node images.

[0094] 2. Network: A standard communication module is built using GRPC to enable multi-party network communication between the management program, nodes, and the BaaS mainnet;

[0095] 3. Mapping Table: Manages and maintains a mapping table between nodes within the subnet and information such as the IP address and port of the control program. This table is used for request location and forwarding. New nodes need to be registered in the mapping table.

[0096] 4. Certificate Authentication: The main control program holds the subnet root certificate A. Only nodes in the subnet that hold a subcertificate issued by root certificate A can pass certificate verification, register to the mapping table, and communicate.

[0097] 5. Node Admission: After a new node is added within a subnet and registers with the main management program, the main management program synchronizes it with the mainnet BaaS and consensus nodes. The node admission process within the subnet has been optimized. Node admission within a subnet is controlled by the subnet management service. Simultaneously, BaaS can process the on-chain limit on the number of child nodes in each subnet's main management program. During node registration, the main management program queries on-chain information; if the number of nodes reaches the limit, the addition of a new subnet node is rejected. The specific process is as follows: Figure 7 As shown.

[0098] The above application example proposes a method for cross-network node management of consortium blockchains with a management program as the core. The management program is easy to access, does not intrude on blockchain nodes, runs in Docker container mode, and has the characteristics of cross-platform, lightweight, and easy deployment. In a multi-party cross-network environment, the management program image only needs to be handed over to the staff of each network environment, and it can be deployed through a simple script, reducing the deployment cost of the blockchain external network. In terms of subnet node access, the master-slave mode, mapping table and certificate authentication of the management program support the internal authentication and access management of subnet nodes, eliminating the need for repeated interaction between individual nodes and the main network BaaS. Therefore, it has the following advantages: (1) The solution has the advantages of being lightweight, cross-platform and easy to deploy. The solution is mainly implemented by the management program, which runs in Docker mode and is easy to deploy. Compared with the existing method of directly deploying heavyweight BaaS on the external network, this solution is low-cost and easy to operate. (2) The solution achieves efficient external node management. The management program implements the standard API of Docker to start, shut down, monitor and manage nodes through blockchain node images. (3) The solution uses master-slave management program, mapping table and certificate system to isolate subnet nodes from BaaS mainnet to a certain extent. The addition of subnet nodes no longer requires repeated interaction with BaaS mainnet, but is managed uniformly by master management program, which improves the flexibility of subnet management. This has a great advantage in large consortium blockchain scenarios with multiple departments and large organizations.

[0099] It should be understood that although the steps in the flowcharts of the embodiments described above 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 embodiments described above 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.

[0100] Based on the same inventive concept, this application also provides a node deployment apparatus for implementing the node deployment method described above. The solution provided by this apparatus is similar to the implementation scheme described in the above method; therefore, the specific limitations in one or more node deployment apparatus embodiments provided below can be found in the limitations of the node deployment method described above, and will not be repeated here.

[0101] In one embodiment, such as Figure 8As shown, a node deployment device is provided for the main control node of a blockchain subnet, which communicates with the blockchain mainnet. The device includes: a registration request response module 801, a node mapping synchronization module 802, and a node mapping synchronization module 803, wherein:

[0102] The registration request response module 801 is used to respond to the node registration request of the subnet node to be deployed in the blockchain subnet and obtain the node information of the subnet node to be deployed carried in the node registration request.

[0103] The node mapping synchronization module 802 is used to write node information into a pre-stored node mapping table and synchronize the node mapping table to the blockchain mainnet; the blockchain mainnet is used to obtain the node information of the subnet nodes to be deployed from the node mapping table, and obtain and return the approval result of the subnet nodes to be deployed based on the node information.

[0104] The subnet node deployment module 803 is used to trigger a deployment request to the subnet node to be deployed when the approval result indicates that the approval has been passed, so as to deploy the subnet node to be deployed.

[0105] In one embodiment, the number of subnet nodes to be deployed is multiple; the node mapping synchronization module 802 is further used to write the node information of each subnet node to be deployed into the node mapping table, and add temporary data identifiers to the node information in the node mapping table; synchronize the node mapping table to the blockchain mainnet according to a preset period; the blockchain mainnet is used to obtain the node information with added temporary data identifiers from the node mapping table, and obtain the approval result of the corresponding subnet node based on the node information with added temporary data identifiers and return it; the subnet node deployment module 803 is further used to obtain the approval result indicating the first subnet node to be deployed that has passed the approval, and update the temporary data identifier added to the node information of the first subnet node to be deployed stored in the node mapping table to an effective identifier; trigger a deployment request to the first subnet node to be deployed to deploy the first subnet node to be deployed.

[0106] In one embodiment, the node deployment apparatus further includes: a node deployment cancellation module, configured to obtain an approval result indicating that the second subnet node to be deployed has failed the approval, and delete the node information of the second subnet node to be deployed stored in the node mapping table, so as to cancel the deployment of the second subnet node to be deployed.

[0107] In one embodiment, the node information includes first certificate information provided by the subnet node to be deployed; the node mapping synchronization module 802 is further used to perform certificate authentication on the subnet node to be deployed based on the first certificate information, and obtain the certificate authentication result of the subnet node to be deployed; if the certificate authentication result is that the certificate authentication is successful, the number of subnet nodes contained in the blockchain subnet is verified, and the number verification result of the blockchain subnet is obtained; if the number verification result is that the verification is successful, the node information is written into the pre-stored node mapping table.

[0108] In one embodiment, the node mapping synchronization module 802 is further configured to obtain pre-stored second certificate information; and if the first certificate information is certificate information issued based on the second certificate information, the certificate authentication result is determined to be certificate authentication passed.

[0109] In one embodiment, the node mapping synchronization module 802 is further used to obtain the subnet node quantity threshold pre-set by the blockchain mainnet for the blockchain subnet; if the number of subnet nodes contained in the blockchain subnet does not reach the subnet node quantity threshold, the quantity verification result is determined as the quantity verification passed.

[0110] In one embodiment, the node deployment apparatus further includes a node deployment cancellation module, used to cancel writing node information into a pre-stored node mapping table when the certificate authentication result is a certificate authentication failure or the quantity verification result is a verification failure, so as to cancel the deployment of the subnet node to be deployed.

[0111] In one embodiment, the node information includes the address information of the subnet node to be deployed; the node deployment device further includes: a mainnet interaction response module, used to respond to a mainnet interaction request triggered by the deployed target subnet node, obtain the node identifier of the target subnet node, and send the mainnet interaction request carrying the node identifier to the blockchain mainnet; the blockchain mainnet is used to obtain the response result corresponding to the mainnet interaction request and return the response result carrying the node identifier; receive the response result returned by the blockchain mainnet, and obtain the target address information of the target subnet node from the node mapping table according to the node identifier; and return the response result to the target subnet node according to the target address information.

[0112] Each module in the aforementioned node deployment 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.

[0113] In one embodiment, a computer device is provided, which may be a server, and its internal structure diagram may be as follows: Figure 9 As shown, the computer device includes a processor, memory, and a network interface connected via a system bus. The processor provides computing 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 an environment for the operation of the operating system and computer programs in the non-volatile storage media. The database stores node information data. The network interface communicates with external terminals via a network connection. When the computer program is executed by the processor, it implements a node deployment method.

[0114] Those skilled in the art will understand that Figure 9 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.

[0115] 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.

[0116] 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.

[0117] 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.

[0118] 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.

[0119] 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.

[0120] 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.

[0121] 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 node deployment method, characterized in that, A main control node applied to a blockchain subnet, wherein the main control node is communicatively connected to the blockchain mainnet, the method comprising: In response to a node registration request from a subnet node to be deployed in the blockchain subnet, obtain the node information of the subnet node to be deployed carried in the node registration request; The node information is written into a pre-stored node mapping table, and the node mapping table is synchronized to the blockchain mainnet; the blockchain mainnet is used to obtain the node information of the subnet node to be deployed from the node mapping table, and to obtain and return the approval result of the subnet node to be deployed based on the node information. If the approval result indicates that the approval has been passed, a deployment request is triggered to the subnet node to be deployed in order to deploy the subnet node; The number of subnet nodes to be deployed is multiple; The step of writing the node information into a pre-stored node mapping table and synchronizing the node mapping table to the blockchain mainnet includes: The node information of each of the subnet nodes to be deployed is written into the node mapping table through the main control node of the blockchain subnet, and a temporary data identifier is added to the node information in the node mapping table; The node mapping table is synchronized to the blockchain mainnet according to a preset period; the blockchain mainnet is used to obtain node information with the added temporary data identifier from the node mapping table, and to obtain and return the approval result of the corresponding subnet node based on the node information with the added temporary data identifier. The step of triggering a deployment request to the subnet node to be deployed, in order to deploy the subnet node, when the approval result indicates that the approval has been passed, includes: The approval result indicates that the first subnet node to be deployed has passed the approval, and the temporary data identifier added to the node information of the first subnet node to be deployed stored in the node mapping table is updated to the effective identifier; Trigger a deployment request to the first subnet node to be deployed, so as to deploy the first subnet node to be deployed; The approval process for multiple subnet nodes to be deployed is carried out in batches on the blockchain mainnet; the node information of each subnet node to be deployed is written into the node mapping table by the main control node of the blockchain subnet.

2. The method according to claim 1, characterized in that, The method further includes: The approval result indicates that the second subnet node to be deployed has failed the approval, and the node information of the second subnet node to be deployed stored in the node mapping table is deleted to cancel the deployment of the second subnet node to be deployed.

3. The method according to claim 1, characterized in that, The node information includes the first certificate information provided by the subnet node to be deployed; The step of writing the node information into a pre-stored node mapping table includes: Based on the first certificate information, perform certificate authentication on the subnet node to be deployed, and obtain the certificate authentication result of the subnet node to be deployed; If the certificate authentication result is that the certificate authentication is successful, the number of subnet nodes contained in the blockchain subnet is verified, and the number verification result of the blockchain subnet is obtained. If the quantity verification result is successful, the node information is written into a pre-stored node mapping table.

4. The method according to claim 3, characterized in that, The step of performing certificate authentication on the subnet node to be deployed based on the first certificate information and obtaining the certificate authentication result of the subnet node to be deployed includes: Retrieve pre-stored second certificate information; If the first certificate information is a certificate information issued based on the second certificate information, the certificate authentication result is determined to be certificate authentication passed.

5. The method according to claim 3, characterized in that, The number of subnet nodes contained in the blockchain subnet is verified, and the verification result of the number of blockchain subnet nodes is obtained, including: Obtain the threshold number of subnet nodes that the blockchain mainnet has pre-set for the blockchain subnet; If the number of subnet nodes contained in the blockchain subnet does not reach the subnet node number threshold, the quantity verification result is determined as a quantity verification passed.

6. The method according to claim 3, characterized in that, The method further includes: If the certificate authentication result is "certificate authentication failed" or the quantity verification result is "verification failed", the node information will not be written to the pre-stored node mapping table, thereby canceling the deployment of the subnet node to be deployed.

7. The method according to claim 1, characterized in that, The node information includes the address information of the subnet nodes to be deployed; The method further includes: In response to a mainnet interaction request triggered by a deployed target subnet node, the node identifier of the target subnet node is obtained, and a mainnet interaction request carrying the node identifier is sent to the blockchain mainnet; the blockchain mainnet is used to obtain the response result corresponding to the mainnet interaction request and return the response result carrying the node identifier. Receive the response result returned by the blockchain mainnet, and obtain the target address information of the target subnet node from the node mapping table according to the node identifier; According to the target address information, the response result is returned to the target subnet node.

8. A node deployment device, characterized in that, A master control node for use in a blockchain subnet, wherein the master control node is communicatively connected to the blockchain mainnet, the device comprising: The registration request response module is used to respond to the node registration request of the subnet node to be deployed in the blockchain subnet, and to obtain the node information of the subnet node to be deployed carried in the node registration request; The node mapping synchronization module is used to write the node information into a pre-stored node mapping table and synchronize the node mapping table to the blockchain mainnet; the blockchain mainnet is used to obtain the node information of the subnet node to be deployed from the node mapping table, and obtain the approval result of the subnet node to be deployed based on the node information and return it. The subnet node deployment module is used to trigger a deployment request to the subnet node to be deployed when the approval result indicates that the approval has been passed, so as to deploy the subnet node to be deployed; The number of subnet nodes to be deployed is multiple; Specifically, the node mapping synchronization module is used to write the node information of each subnet node to be deployed into the node mapping table through the main control node of the blockchain subnet, and add temporary data identifiers to the node information in the node mapping table; synchronize the node mapping table to the blockchain mainnet according to a preset period; the blockchain mainnet is used to obtain the node information with added temporary data identifiers from the node mapping table, and obtain and return the approval result of the corresponding subnet node based on the node information with added temporary data identifiers. The subnet node deployment module is specifically used to obtain the approval result indicating the first subnet node to be deployed that has passed the approval, and to update the temporary data identifier added to the node information of the first subnet node to be deployed stored in the node mapping table to the effective identifier; and to trigger a deployment request to the first subnet node to be deployed in order to deploy the first subnet node to be deployed. The approval process for multiple subnet nodes to be deployed is carried out in batches on the blockchain mainnet.

9. A computer device comprising a memory and a processor, wherein the memory stores a computer program, characterized in that, When the processor executes the computer program, it implements the steps of the method according to any one of claims 1 to 7.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1 to 7.

11. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1 to 7.

Images