Blockchain network management method, device, equipment and first blockchain network

Abstract

The present disclosure proposes a management method, device, equipment and first blockchain network of a blockchain network, which relates to the field of satellite communication business support and blockchain technology. The method includes: a first management node in the first blockchain network broadcasts a first message to a second management node in the first blockchain network, wherein the first message carries the attribute information of the second blockchain network managed by the first management node, and is used by the first management node and the second management node to verify the attribute information through a consensus mechanism; upon receiving at least one second message, the attribute information is uploaded to the blockchain of the first blockchain network for storage, wherein the second message is sent by the second management node that receives the first message after verifying and confirming the attribute information. Thus, the reliability of the management of the blockchain network is improved, and the immutability, security and reliability of the attribute information of the blockchain network can be guaranteed.

Description

Technical Field

[0001] The present disclosure relates to the fields of satellite communication business support and blockchain technology, and in particular to a blockchain network management method, device, equipment and a first blockchain network. Background Art

[0002] Satellite communications involve a large amount of data transmission, including user data, satellite status information, etc. The traditional centralized management method is susceptible to single point failures and it is difficult to ensure the security and reliability of data.

[0003] As a decentralized technology, blockchain can ensure that data is not tampered with during the entire transmission process through distributed ledger records and asymmetric encryption technology, thereby improving data security. Therefore, it is very suitable for solving the security and reliability issues of satellite communications. However, although blockchain technology brings many advantages to satellite communications, reliable management of blockchain networks is still required to fully realize its potential. Summary of the invention

[0004] The present disclosure aims to solve one of the technical problems in the related art at least to some extent.

[0005] To this end, the purpose of the present disclosure is to propose a management method, device, equipment and a first blockchain network for a blockchain network, which can achieve reliable management of the blockchain network.

[0006] The first aspect of the present disclosure provides a method for managing a blockchain network, which is applied to a first management node in a first blockchain network. The method includes: broadcasting a first message to a second management node in the first blockchain network, wherein the first message carries attribute information of the second blockchain network managed by the first management node, and is used for the first management node and the second management node to verify the attribute information through a consensus mechanism; upon receiving at least one second message, uplinking the attribute information to the blockchain of the first blockchain network for storage, wherein the second message is sent by the second management node that receives the first message after verifying and confirming the attribute information.

[0007] The second aspect embodiment of the present disclosure proposes a management method for a blockchain network, which is applied to a second management node in a first blockchain network. The method includes: receiving a first message broadcast by a first management node in the first blockchain network, wherein the first message carries attribute information of the second blockchain network managed by the first management node, and is used by the first management node and the second management node to verify the attribute information through a consensus mechanism; after verifying and confirming the attribute information, sending a second message to the first management node; wherein the second message is used by the first management node to upload the attribute information to the blockchain of the first blockchain network for storage when the first management node receives the second message sent by at least one second management node.

[0008] The third aspect embodiment of the present disclosure proposes a management device for a blockchain network, which is applied to a first management node in a first blockchain network, and the device includes: a transceiver module, which is used to broadcast a first message to a second management node in the first blockchain network, wherein the first message carries attribute information of the second blockchain network managed by the first management node, and is used for the first management node and the second management node to verify the attribute information through a consensus mechanism; a processing module, which is used to upload the attribute information to the blockchain of the first blockchain network for storage when at least one second message is received, wherein the second message is sent by the second management node that receives the first message after verifying and confirming the attribute information.

[0009] The fourth aspect embodiment of the present disclosure proposes a management device for a blockchain network, which is applied to a second management node in a first blockchain network, and the device includes: a transceiver module, which is used to receive a first message broadcast by a first management node in the first blockchain network, wherein the first message carries attribute information of a second blockchain network established by the first management node, and is used for the first management node and the second management node to verify the attribute information through a consensus mechanism; the transceiver module is also used to send a second message to the first management node when the attribute information is verified and confirmed; wherein the second message is used for the first management node to upload the attribute information to the blockchain of the first blockchain network for storage when the first management node receives the second message sent by at least one second management node.

[0010] The fifth aspect embodiment of the present disclosure proposes a first blockchain network, including a first management node for executing the management method of the blockchain network described in the first aspect embodiment, and a second management node for executing the management method of the blockchain network described in the second aspect embodiment.

[0011] The sixth aspect embodiment of the present disclosure proposes a blockchain network system, including: a first blockchain network and a second blockchain network, wherein the first blockchain network includes a first management node and a second management node; the second blockchain network is used to upload the data to be stored in the corresponding area to the blockchain of the second blockchain network for storage; the first blockchain network is used to manage the second blockchain network by executing the method described in the first aspect embodiment through the first management node, and the second management node executing the method described in the second aspect embodiment.

[0012] The seventh aspect embodiment of the present disclosure proposes an electronic device, comprising: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor, and the instructions are configured to execute the management method of the blockchain network as described in the first aspect embodiment of the present disclosure, or to execute the management method of the blockchain network as described in the second aspect embodiment of the present disclosure.

[0013] An eighth aspect embodiment of the present disclosure provides a non-transitory computer-readable storage medium storing computer instructions, wherein the computer instructions are used to enable the computer to execute the management method of the blockchain network as described in the first aspect embodiment of the present disclosure, or to execute the management method of the blockchain network as described in the second aspect embodiment of the present disclosure.

[0014] The ninth aspect embodiment of the present disclosure proposes a computer program product, including a computer program. When the computer program is executed by a processor, it implements the management method of the blockchain network as described in the first aspect embodiment of the present disclosure, or implements the management method of the blockchain network as described in the second aspect embodiment of the present disclosure.

[0015] The management method, device, first blockchain network, blockchain network system, electronic device, computer-readable storage medium and computer program product of the blockchain network proposed in the present disclosure broadcast a first message to a second management node in the first blockchain network through a first management node in the first blockchain network, wherein the first message carries the attribute information of the second blockchain network managed by the first management node, and is used for the first management node and the second management node to verify the attribute information through a consensus mechanism, and when the first management node receives at least one second message, the attribute information is chained to the blockchain of the first blockchain network for storage, wherein the second message is sent by the second management node that receives the first message after verifying and confirming the attribute information. Thus, by using multiple management nodes to form the first blockchain network, a single management node only manages the blockchain network within its own rights and interests, and the management authority of the management node to the blockchain network can be dispersed and balanced, reducing the risk of management failure caused by the failure of a single management node, and improving the reliability of the management of the blockchain network. In addition, by chaining the attribute information of the blockchain network managed by the management node to the blockchain of the first blockchain network for storage, the immutability, security and reliability of the attribute information of the blockchain network can be guaranteed.

[0016] Additional aspects and advantages of the present disclosure will be given in part in the following description and in part will be obvious from the following description or learned through practice of the present disclosure. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] The above and / or additional aspects and advantages of the present disclosure will become apparent and easily understood from the following description of the embodiments in conjunction with the accompanying drawings, in which:

[0018] Figure 1 A flowchart of a method for managing a blockchain network provided by an embodiment of the present disclosure;

[0019] Figure 2 An example diagram of a blockchain network management method provided by an embodiment of the present disclosure;

[0020] Figure 3 A flowchart of another blockchain network management method provided by an embodiment of the present disclosure;

[0021] Figure 4 An example diagram of another blockchain network management method provided by an embodiment of the present disclosure;

[0022] Figure 5 A flowchart of another blockchain network management method provided by an embodiment of the present disclosure;

[0023] Figure 6An example diagram of a process for adding a third management node to a first blockchain network provided by an embodiment of the present disclosure;

[0024] Figure 7 A flowchart of another blockchain network management method provided by an embodiment of the present disclosure;

[0025] Figure 8 A flowchart of another blockchain network management method provided by an embodiment of the present disclosure;

[0026] Fig. 9 A flowchart of another blockchain network management method provided by an embodiment of the present disclosure;

[0027] Fig.10 A schematic diagram of the structure of a blockchain network management device provided by an embodiment of the present disclosure;

[0028] Fig.11 A schematic diagram of the structure of another blockchain network management device provided by an embodiment of the present disclosure;

[0029] Fig.12 A schematic diagram of the structure of a first blockchain network provided by an embodiment of the present disclosure;

[0030] Fig.13 A schematic diagram of the structure of a blockchain network system provided by an embodiment of the present disclosure;

[0031] Fig.14 It is a block diagram of an electronic device according to an exemplary embodiment. DETAILED DESCRIPTION

[0032] Embodiments of the present disclosure are described in detail below, examples of which are shown in the accompanying drawings, wherein the same or similar reference numerals throughout represent the same or similar elements or elements having the same or similar functions. The embodiments described below with reference to the accompanying drawings are exemplary and are intended to be used to explain the present disclosure, and should not be construed as limiting the present disclosure.

[0033] The acquisition, storage, use, and processing of data in the technical solution disclosed in this disclosure are in compliance with the relevant provisions of relevant laws and regulations.

[0034] It should be noted that in the embodiments of the present application, certain software, components, models and other existing solutions in the industry may be mentioned, and they should be considered as exemplary. Their purpose is only to illustrate the feasibility of implementing the technical solution of the present application, but it does not mean that the applicant has or will necessarily use the solution.

[0035] It is understandable that the current system security of satellite communications is mainly network security design, which adopts centralized and hierarchical management methods, and the data security design of the entire network is in its infancy. This centralized system security design relies on centralized decision-making responses when attacked. Edge network nodes such as satellite communication terminals, satellites, and gateways are connected wirelessly and are vulnerable to attacks and interference. When the connection between the node and the center is interrupted, the traditional security model cannot respond quickly. It is necessary to upgrade the capabilities based on traditional network security technology for the complex global collaborative network. In the current centralized model, the relationship between each subsystem (software) is set to be completely trusting, and there is a lack of settings for the internal trust model of the system. It is urgent to set and verify a trusted subsystem interaction mechanism to enhance technical trust between systems.

[0036] When blockchain is empowering existing applications, from a feasibility perspective, blockchain empowers a specific application in satellite communications. As long as it is jointly demonstrated with the business system, it will be able to integrate the existing capabilities of blockchain; from a necessity perspective, the current blockchain still uses a distributed collaborative means to form operational trust and improve the production relations and operation processes within the system. In essence, if blockchain is used to empower the construction of a secure environment for multi-domain data in satellite communications, blockchain needs to be designed and constructed as a digital infrastructure and trust infrastructure base to maximize the effectiveness of blockchain. However, for the complex management and operation of global business networks, this function cannot be completed using a simple one or several blockchains. It is necessary to redesign a blockchain that meets global and local requirements and carries the accumulation and transmission functions of valuable data.

[0037] There are two main types of blockchains at present: permissioned chains (alliance chains and private chains) and permissionless chains (public chains). Public chains do not have access mechanisms and are not suitable for global network management applications; alliance chains have access mechanisms, but the efficiency of consensus collaboration varies greatly between laboratory conditions and actual network conditions, making it difficult to meet the business needs of a global wide-area environment. Currently, open alliance chains have become a new exploration path, exploring the development and application model of blockchain technology by integrating permissioned chains and permissionless chains.

[0038] In order to facilitate the deployment and management of alliance chains, special management tools are usually designed in blockchain service systems, such as BaaS (Blockchain as a Service) tools. Such management tools generally adopt a centralized deployment mode, which can manage, supervise and operate multiple blockchain networks, but there is a risk of management tool failure. Once the centralized management tool fails, the management of the entire blockchain network will fail. Therefore, this method is insufficient in terms of the reliability of blockchain network management.

[0039] The present disclosure proposes a management method, device, first blockchain network, blockchain network system, electronic device, computer-readable storage medium and computer program product for a blockchain network. Based on the alliance chain, a first blockchain network composed of multiple distributed management nodes is established. By adopting the "chain-based governance" approach, a single management node can only manage the blockchain network within its own rights and interests, thereby distributing and balancing the management authority of the management node over the blockchain network, reducing the risk of management failure caused by the failure of a single management node, and improving the reliability of the management of the blockchain network. In addition, by uploading the attribute information of the blockchain network managed by the management node to the blockchain of the first blockchain network for storage, the immutability, security and reliability of the attribute information of the blockchain network can be guaranteed.

[0040] The management node may be an electronic device configured with a management tool such as a BaaS management tool, or a management tool configured in an electronic device such as a BaaS management tool, and the present disclosure does not limit this. The management node has collaborative consensus capabilities and can manage, supervise and operate one or more blockchain networks.

[0041] The following is a detailed introduction to the blockchain network management method, device, first blockchain network, blockchain network system, electronic device, computer-readable storage medium and computer program product provided by the present invention in conjunction with the accompanying drawings.

[0042] Figure 1 A flowchart of a method for managing a blockchain network provided in an embodiment of the present disclosure.

[0043] It should be noted that the method is applied to the first management node in the first blockchain network and is executed by the management device of the blockchain network. The management device of the blockchain network may be the first management node or may be configured in the first management node, and the present disclosure does not limit this.

[0044] like Figure 1 As shown, the method may include but is not limited to the following steps 101-102.

[0045] Step 101, broadcast a first message to a second management node in a first blockchain network, wherein the first message carries attribute information of a second blockchain network managed by the first management node, and is used by the first management node and the second management node to verify the attribute information through a consensus mechanism.

[0046] In some embodiments, the first blockchain network includes multiple management nodes, and a single management node can only manage the blockchain network within its own jurisdiction, and the attribute information of the blockchain network managed by the single management node can be stored on the blockchain of the first blockchain network. In order to distinguish it from the first blockchain network, the blockchain network managed by the first management node in the embodiment of the present disclosure is referred to as the second blockchain network.

[0047] The management nodes in the first blockchain network may belong to different parties (such as different organizations or operators), and a single party may have one or at least two management nodes.

[0048] The first management node is a management node in the first blockchain network that submits a transaction application when the attribute information of the blockchain network it manages is stored as a transaction or operation on the blockchain of the first blockchain network. The second management node is any other management node in the first blockchain network except the first management node.

[0049] In some embodiments, the second blockchain network can be managed by the first management node alone, or can be managed by at least two management nodes including the first management node in collaboration, and the present disclosure does not limit this. Among them, the number of second blockchain networks managed by the first management node can be one or more, and the present disclosure does not limit this.

[0050] In some embodiments, the second blockchain network may include at least one of a first type blockchain network and a second type blockchain network;

[0051] The first type of blockchain network includes multiple blockchain nodes deployed in different areas, the communication delay between different areas is higher than the first delay threshold, and / or the distance between different areas is greater than the first distance threshold;

[0052] The second type of blockchain network includes multiple blockchain nodes deployed in the same area, the communication delay in the same area is lower than the second delay threshold, and / or the distance between different locations in the same area is not greater than the second distance threshold.

[0053] The first delay threshold and the second delay threshold may be equal or different, and the first distance threshold and the second distance threshold may be equal or different, which is not limited in the present disclosure.

[0054] The region may be a functional domain, a physical domain, or a logical domain, etc., and the present disclosure does not impose any limitation on this.

[0055] It should be noted that the first type of blockchain network can also be called a remotely deployed blockchain network, or a remotely deployed blockchain node network, or other names, and the multiple blockchain nodes included in the first type of blockchain network can be called remotely deployed blockchain nodes or other names, and the present disclosure does not limit this. The second type of blockchain network can also be called a locally deployed blockchain network, or a locally deployed blockchain node network, or other names, and the multiple blockchain nodes included in the second type of blockchain network can be called locally deployed blockchain nodes or other names, and the present disclosure does not limit this.

[0056] In actual applications, the first type of blockchain network and the second type of blockchain network can be flexibly deployed according to business needs.

[0057] For example, the second type of blockchain network can quickly upload and store data in the deployed area, and achieve reliable traceability of transactions or operations in the deployed area. In regional networks or local area networks with a large number of operation or transaction requirements, multiple blockchain nodes with consensus capabilities can be centrally deployed, thereby efficiently completing the chain operation of local data and ensuring the traceability and non-tamperability of the data.

[0058] The first type of blockchain network can be used for secondary on-chain storage of blockchain network data in a local area and interactive storage of cross-regional data. In order to reliably interact with data between multiple regions with high communication latency, blockchain nodes can be deployed in multiple regions to form a first type of blockchain network. The first type of blockchain network can improve the disaster tolerance and anti-destruction characteristics of local data and further enhance the immutability of data.

[0059] Among them, different blockchain networks deployed in different regions may belong to the same or different parties. The blockchain network deployed in each region may be managed solely by the management node owned by the party to which it belongs, or jointly managed by multiple management nodes owned by the party to which it belongs, or jointly managed by the management node owned by the party to which it belongs and the management nodes owned by other parties. Then, the second type of blockchain network can be managed solely by one management node, or jointly managed by multiple management nodes. Similarly, the first type of blockchain network deployed in multiple regions can also be managed solely by one management node, or jointly managed by multiple management nodes.

[0060] Among them, since in the first type of blockchain network, the communication delay between the areas where the blockchain nodes are deployed is higher than the first delay threshold, and / or the distance is greater than the first distance threshold, the first type of blockchain network can adopt an efficient asynchronous consensus algorithm to ensure reliable storage and trusted interaction of wide-area data. In the second type of blockchain network, the communication delay within the area where the blockchain nodes are deployed is lower than the second delay threshold, and / or the distance between different locations within the area is not greater than the second distance threshold, then the consensus algorithm adopted by the second type of blockchain network can be selected as needed, such as selecting a consensus algorithm such as BFT (Byzantine Fault Tolerance) or CFT (Crash Fault Tolerance).

[0061] In some embodiments, the attribute information of the second blockchain network may include at least one of the following:

[0062] The identifier of the second blockchain network;

[0063] The number of blockchain nodes included in the second blockchain network;

[0064] The identifier of the alliance to which the second blockchain network belongs;

[0065] The network protocol of the second blockchain network;

[0066] The consensus algorithm used by the second blockchain network;

[0067] The incentive mechanism adopted by the second blockchain network;

[0068] Second, information about smart contracts deployed on the blockchain network;

[0069] The deployment method of the second blockchain network.

[0070] The identifier of the second blockchain network is used to uniquely identify the second blockchain network, for example, it can be the network number of the second blockchain network. The identifier of the alliance to which the second blockchain network belongs is used to uniquely identify the alliance to which the second blockchain network belongs, for example, it can be the number of the alliance to which the second blockchain network belongs. The network protocol may include a data transmission layer protocol, an application layer protocol, a peer-to-peer network protocol, a security protocol, a data exchange protocol, etc. The consensus algorithm may include BFT, CFT or PBFT (Practical Byzantine Fault Tolerance), etc. The incentive mechanism may include PoW (Proof of Work), PoS (Proof of Stake), DPoS (Delegated Proof of Stake), etc. The relevant information of the smart contract may include the definition, function, algorithm and other information of the smart contract.

[0071] In some embodiments, when the attribute information of the second blockchain network managed by the first management node is uploaded to the chain, the first management node may broadcast a first message to the second management node in the first blockchain network, wherein the first message carries the attribute information of the second blockchain network managed by the first management node, and is used by the first management node and the second management node to verify the attribute information through a consensus mechanism. The number of the second management node may be one or more, and the present disclosure does not limit this.

[0072] Step 102, upon receiving at least one second message, uplinking the attribute information to the blockchain of the first blockchain network for storage, wherein the second message is sent by the second management node that receives the first message after verifying and confirming the attribute information.

[0073] In some embodiments, after the first management node broadcasts the first message, it can verify the attribute information with the second management node through a consensus mechanism. The second management node that receives the first message can send a second message to the first management node after verifying and confirming the attribute information, so that the first management node can upload the attribute information to the blockchain of the first blockchain network for storage when receiving at least one second message. In this way, the attribute information of the second blockchain network can be processed on the blockchain of the first blockchain network in a distributed manner.

[0074] In some embodiments, the attribute information of the second blockchain network can be uploaded to the blockchain of the first blockchain network in the form of plain text or ciphertext for storage as needed, and the present disclosure does not limit this.

[0075] Among them, the consensus mechanism adopted by the first blockchain network can be set to any available consensus mechanism in the relevant technology as needed, and this disclosure does not impose any restrictions on this.

[0076] In the following, the first blockchain network includes management nodes 1, 2, 3, and 4, where management node 1 is the first management node, the second management node includes management nodes 2, 3, and 4, and management node 4 is in a faulty or offline state. Figure 2 , the process of using the consensus mechanism for each management node to verify and confirm the attribute information of the second blockchain network managed by management node 1 is illustrated by way of example. Figure 2 The “×” in indicates that the management node 4 is in a faulty or offline state.

[0077] refer to Figure 2 The process of uploading the attribute information of the second blockchain network managed by the management node 1 can include four stages, namely, the application stage, the preparation stage, the confirmation stage, and the feedback stage. Among them, since the management node 4 is in a faulty or offline state, it does not participate in the message broadcasting and log writing processes in each stage.

[0078] In the application stage, management node 1 can package the attribute information of the second blockchain network managed by it, and submit a transaction application to management nodes 2, 3, and 4, and write the transaction application into the message log of management node 1. The transaction application, i.e., the first message in the embodiment of the present disclosure, can carry the attribute information of the second blockchain network managed by management node 1, and is used for management nodes 1, 2, 3, and 4 to verify the attribute information through a consensus mechanism.

[0079] After receiving the transaction application, management nodes 2 and 3 enter the preparation phase. In the preparation phase, management nodes 2 and 3 can broadcast preparation messages to other management nodes in the first blockchain network and write the preparation messages into their own message logs. For example, Figure 2 Management node 2 can broadcast the preparation message to management nodes 1, 3, and 4, and management node 3 can broadcast the preparation message to management nodes 1, 2, and 4. The management node that receives the preparation message can verify the validity of the preparation message and write the verified preparation message into its own message log.

[0080] After the preparation phase is completed, the management node enters the confirmation phase. In the confirmation phase, each management node can broadcast its own confirmation message to other management nodes in the first blockchain network, verify other confirmation messages received, and write the verified messages into the message log. For example, Figure 2In this example, management node 1 can broadcast confirmation messages to management nodes 2, 3, and 4, management node 2 can broadcast confirmation messages to management nodes 1, 3, and 4, management node 3 can broadcast confirmation messages to management nodes 1, 2, and 4, management node 1 can verify the confirmation messages broadcast by management nodes 2 and 3, and write the verified messages to the message log, management node 2 can verify the confirmation messages broadcast by management nodes 1 and 3, and write the verified messages to the message log, and management node 3 can verify the confirmation messages broadcast by management nodes 1 and 2, and write the verified messages to the message log. When a management node receives no less than 2f (2f is 2 in this example) confirmation messages in addition to the confirmation messages broadcast by itself, it is considered that the confirmation phase has been completed. Among them, f represents the number of faulty nodes that can be tolerated, and f is 1 in this example.

[0081] After the confirmation phase is completed, the management node enters the feedback phase and can send a feedback message to the management node 1, thereby confirming the new requirement proposed by the management node 1. The feedback message is the second message in the embodiment of the present disclosure.

[0082] It should be noted that the process of verifying and confirming the attribute information based on the consensus mechanism by the above-mentioned management nodes can refer to the relevant technology, and the implementation details of the embodiment of the present disclosure will not be repeated. In addition, the process of verifying and confirming the attribute information based on the consensus mechanism by the above-mentioned management nodes is only an exemplary description and cannot be understood as a limitation on the embodiment of the present disclosure. In actual applications, any other consensus mechanism can be used as needed to verify and confirm the attribute information of the second blockchain network, and the present disclosure does not limit this in real time.

[0083] In summary, the management method of the blockchain network provided by the embodiment of the present disclosure broadcasts the first message to the second management node in the first blockchain network through the first management node in the first blockchain network, wherein the first message carries the attribute information of the second blockchain network managed by the first management node, and is used for the first management node and the second management node to verify the attribute information through the consensus mechanism. When the first management node receives at least one second message, the attribute information is chained to the blockchain of the first blockchain network for storage, wherein the second message is sent by the second management node that receives the first message after verifying and confirming the attribute information. Thus, by using multiple management nodes to form the first blockchain network, a single management node only manages the blockchain network within its own rights and interests, and the management authority of the management node on the blockchain network can be dispersed and balanced, reducing the risk of management failure caused by the failure of a single management node, and improving the reliability of the management of the blockchain network. In addition, by chaining the attribute information of the blockchain network managed by the first management node to the blockchain of the first blockchain network for storage, the immutability, security and reliability of the attribute information of the blockchain network can be guaranteed.

[0084] In a possible implementation form, at least two management nodes in the first blockchain network can collaboratively manage the same blockchain network. Figure 3 , the management method of the blockchain network provided by the embodiment of the present disclosure is further explained.

[0085] Figure 3 A flowchart of another blockchain network management method provided by an embodiment of the present disclosure.

[0086] like Figure 3 As shown, the management method of the blockchain network may include the following steps 301-303.

[0087] Step 301: The first management node in the first blockchain network negotiates with the target management node to determine the attribute information of the second blockchain network, and the second blockchain network is jointly managed by the first management node and the target management node.

[0088] Among them, the second blockchain network can be jointly managed by at least two management nodes in the first blockchain network, and the first management node can be any one of the at least two management nodes.

[0089] The target management node may be any other management node in the first blockchain network except the first management node, that is, any second management node in the first blockchain network. The number of target management nodes may be one or more, and the present disclosure does not limit this.

[0090] In some embodiments, the first management node and the target management node may negotiate and determine the attribute information of the second blockchain network by means of multiple interactions, wherein the attribute information may include, for example, the network protocol of the second blockchain network, the consensus algorithm adopted, the incentive mechanism adopted, the relevant information of the smart contract deployed thereon, the deployment method, etc.

[0091] In some embodiments, step 301 may be implemented in the following manner:

[0092] The first management node sends a third message to the target management node, wherein the third message carries initial attribute information of the second blockchain network;

[0093] When the first management node receives the fourth message sent by the target management node, it determines the initial attribute information as the attribute information of the second blockchain network; wherein, the fourth message is sent when the target management node confirms the initial attribute information.

[0094] Among them, the initial attribute information can be understood as the attribute information of the second blockchain network preliminarily determined by the first management node.

[0095] It is understandable that after the first management node sends the third message to the target management node, if the target management node confirms that the initial attribute information carried therein is feasible, the fourth message can be sent to the first management node. When the first management node receives the fourth message sent by the target management node, it can determine that the target management node agrees with the initial attribute information, so that the initial attribute information can be determined as the attribute information of the second blockchain network finally determined by negotiation.

[0096] In some embodiments, step 301 may be implemented in the following manner:

[0097] The first management node sends a fifth message to the target management node, wherein the fifth message carries initial attribute information of the second blockchain network;

[0098] The first management node receives a sixth message sent by the target management node, wherein the sixth message carries revised attribute information of the second blockchain network and is sent by the target management node without confirming the initial attribute information;

[0099] When confirming the revised attribute information, the first management node determines the revised attribute information as the attribute information of the second blockchain network.

[0100] The modified attribute information may be understood as the attribute information obtained by modifying or updating the initial attribute information by the target management node.

[0101] It is understandable that after the first management node sends the fifth message to the target management node, if the target management node confirms that the initial attribute information carried therein is not feasible, that is, if the initial attribute information carried therein is not confirmed, the sixth message may be sent to the first management node, which carries the revised attribute information of the second blockchain network. Upon receiving the sixth message sent by the target management node and confirming that the revised attribute information carried therein is feasible, the first management node may determine the revised attribute information as the attribute information of the second blockchain network finally negotiated and determined. Upon receiving the sixth message sent by the target management node and confirming that the revised attribute information carried therein is not feasible, that is, if the revised attribute information is not confirmed, the first management node may send a message to the target management node again, which carries the revised attribute information again, and then through multiple rounds of interaction with the target management node, finally negotiate and determine the attribute information of the second blockchain network.

[0102] It is understandable that the above-mentioned interaction process between the first management node and the target management node is initiated for the first time by the first management node, and in some embodiments, it may also be initiated for the first time by the target management node. Accordingly, in some embodiments, step 301 may be implemented in the following manner:

[0103] Receiving an eighth message sent by the target management node, wherein the eighth message carries initial attribute information of the second blockchain network;

[0104] When the initial attribute information is confirmed, the initial attribute information is determined as the attribute information of the second blockchain network.

[0105] Alternatively, in some embodiments, step 301 may be implemented in the following manner:

[0106] Receiving a ninth message sent by the target management node, wherein the ninth message carries initial attribute information of the second blockchain network;

[0107] In the case where the initial attribute information is not confirmed, sending a tenth message to the target management node, wherein the tenth message carries the revised attribute information of the second blockchain network;

[0108] When the eleventh message sent by the target management node is received, the revised attribute information is determined as the attribute information of the second blockchain network, wherein the eleventh message is sent by the target management node after confirming the revised attribute information.

[0109] As a result, the first management node and the target management node can negotiate and determine the attribute information of the second blockchain network through multiple interactions.

[0110] It should be noted that the process in which the first management node and the target management node use multiple interactions to negotiate and determine the attribute information of the second blockchain network is merely an exemplary description and should not be construed as a limitation on the embodiments of the present disclosure. In actual applications, the first management node and the target management node may use more or fewer interactions or other types of interactions to negotiate and determine the attribute information of the second blockchain network, and the present disclosure does not impose any limitations on this.

[0111] Furthermore, after the attribute information of the second blockchain network is determined through negotiation, the second blockchain network and its smart contracts and application services can be deployed based on the attribute information of the second blockchain network determined through negotiation.

[0112] In some embodiments, the second blockchain network and the smart contracts and application services deployed thereon may be deployed by the first management node. Accordingly, the management method of the blockchain network applied to the first management node may further include:

[0113] Deploying a second blockchain network including a plurality of blockchain nodes;

[0114] Deploy smart contracts and application services on the second blockchain network;

[0115] According to the demand information of application services, the smart contract is configured, and the start and stop and functions of the second blockchain network are adjusted.

[0116] Among them, the demand information of the application service may include the demand information of the application service on the functions of the smart contract, such as which core functions the smart contract needs to implement and when to execute, etc., and may also include the demand information on the technical aspects of the smart contract, such as the version management strategy and programming language of the smart contract, etc., and may also include the demand information on the performance of the smart contract, such as the execution efficiency of the smart contract and how to handle transactions under high concurrency, etc., and may also include the demand information on the blockchain network where the application service is deployed, such as when the blockchain network starts and stops, and what functions the blockchain network includes, etc.

[0117] In some embodiments, the first management node may first deploy multiple blockchain nodes, thereby completing the construction of a second blockchain network composed of multiple blockchain nodes. For each blockchain node, the first management node may complete authentication and protocol interaction with a network function unit (such as a gateway or protocol gateway, or service) at the deployment site of the blockchain node, and deploy the blockchain node through a container or virtual machine. When the second blockchain network is successfully deployed, each blockchain node may display normal network information through a display device.

[0118] Furthermore, the first management node may deploy a smart contract on the second blockchain network. When the smart contract is successfully deployed, each blockchain node may send a message to the first management node that the smart contract is successfully deployed, so that the first management node may further deploy application services on the second blockchain network. When the application service is successfully deployed, each blockchain node may display normal operation information through a display device. Furthermore, the first management node may configure the smart contract according to the demand information of the application service. When the smart contract is successfully configured, each blockchain node may send a message to the first management node that the smart contract is successfully configured. Furthermore, the first management node may adjust the start and stop and functions of the second blockchain network according to the demand information of the application service.

[0119] As a result, the deployment of the second blockchain network managed by the first management node and the smart contracts and application services deployed thereon is achieved.

[0120] Furthermore, the following steps 302-303 may be adopted to distribute and store the attribute information of the second blockchain network on the blockchain of the first blockchain network.

[0121] In step 302, the first management node broadcasts a first message to the second management node in the first blockchain network, wherein the first message carries attribute information of the second blockchain network, and is used by the first management node and the second management node to verify the attribute information through a consensus mechanism.

[0122] Step 303: Upon receiving at least one second message, the first management node uploads the attribute information to the blockchain of the first blockchain network for storage, wherein the second message is sent by the second management node that receives the first message after verifying and confirming the attribute information.

[0123] The second management node that sends the second message may include the target management node, or the second management node that sends the second message may not include the target management node, which is not limited in the present disclosure.

[0124] The following example takes the first blockchain network including management nodes 1, 2, 3 and 4, where management node 1 is the first management node, the second management node includes management nodes 2, 3 and 4, where management node 2 is the target management node, and management node 4 is in a faulty or offline state. Figure 4 , an example is given of the process in which management nodes 1 and 2 negotiate to determine the attribute information of the second blockchain network they jointly manage, and each management node uses a consensus mechanism to verify and confirm the attribute information of the second blockchain network. Figure 4The “×” in indicates that the management node 4 is in a faulty or offline state.

[0125] refer to Figure 4 , management nodes 1 and 2 can negotiate and determine the attribute information of the second blockchain network jointly managed by management nodes 1 and 2 during the interactive negotiation stage. Among them, management node 1 can send a third message to management node 2, which carries the initial attribute information of the second blockchain network. When management node 2 confirms that the initial attribute information is feasible, it can send a fourth message to management node 1. When management node 1 receives the fourth message sent by management node 2, it can determine that management node 2 agrees with the initial attribute information, so that the initial attribute information can be determined as the attribute information of the second blockchain network finally negotiated and determined.

[0126] The process of uploading the attribute information of the second blockchain network managed by management nodes 1 and 2 may include four stages, namely, application stage, preparation stage, confirmation stage, and feedback stage. In particular, since management node 4 is in a faulty or offline state, it does not participate in message broadcasting and log writing in each stage. For the explanation of each stage, please refer to Figure 2 The explanation will not be repeated here.

[0127] It should be noted that steps 302-303 can be performed at any time before, during or after the second blockchain network is deployed, and the present disclosure does not impose any restrictions on this.

[0128] It should be noted that the specific implementation process and principle of steps 302-303 can be referred to the description of other embodiments and will not be repeated here.

[0129] The management method of the blockchain network provided by the embodiment of the present disclosure is that the first management node in the first blockchain network negotiates with the target management node to determine the attribute information of the second blockchain network, and the second blockchain network is managed by the first management node and the target management node in collaboration; the first management node broadcasts the first message to the second management node in the first blockchain network, wherein the first message carries the attribute information of the second blockchain network, and is used by the first management node and the second management node to verify the attribute information through a consensus mechanism; the first management node, when receiving at least one second message, links the attribute information to the blockchain of the first blockchain network for storage, wherein the second message is sent by the second management node that receives the first message after verifying and confirming the attribute information. Thus, by using multiple management nodes to form the first blockchain network, a single management node only manages the blockchain network within its own rights and interests, which can disperse and balance the management authority of the management node over the blockchain network, reduce the risk of management failure caused by the failure of a single management node, and improve the reliability of the management of the blockchain network. In addition, the same blockchain network can belong to at least two management nodes and be managed by the at least two management nodes in a coordinated manner, thereby avoiding the failure of a single management node to cause the failure of the management of the blockchain network, and meeting the needs of a global multi-party application scenario where multiple parties need to collaborate to establish a blockchain network to meet the needs of a certain special business. In addition, by uploading the attribute information of the blockchain network managed by the first management node and the target management node to the blockchain of the first blockchain network for storage, the immutability, security and reliability of the attribute information of the blockchain network can be guaranteed.

[0130] In a possible implementation form, on the basis of the existing management nodes of the first blockchain network, a new management node can be added to the first blockchain network. Figure 5 , the management method of the blockchain network provided by the embodiment of the present disclosure is further explained.

[0131] Figure 5 A flowchart of another blockchain network management method provided by an embodiment of the present disclosure.

[0132] like Figure 5 As shown, based on any of the foregoing embodiments, the management method of the blockchain network may further include the following steps 501-503.

[0133] Step 501, receiving a seventh message sent by a third management node, where the seventh message is used to apply to join the first blockchain network.

[0134] Among them, the third management node is a management node that is not currently included in the first blockchain network.

[0135] The seventh message may carry the identity information, public key certificate, etc. of the third management node.

[0136] Step 502: Determine with the second management node through a consensus mechanism whether to allow the third management node to join the first blockchain network.

[0137] Among them, the consensus mechanism can be set to any available consensus mechanism in the relevant technology as needed, and the present disclosure does not limit this.

[0138] The second management node is any other management node in the first blockchain network except the first management node. The number of the second management node can be one or more, and the present disclosure does not limit this.

[0139] Step 503: When the third management node is allowed to join the first blockchain network and the synchronization of the target data is completed, the third management node is added to the first blockchain network, wherein the target data includes the data stored in the blockchain of the first blockchain network.

[0140] It should be noted that when the third management node needs to join the first blockchain network, it can send the seventh message to any management node in the first blockchain network to apply to join the first blockchain network. Correspondingly, steps 501-503 can be performed by the management node that receives the seventh message. In the case where the third management node sends the seventh message to the first management node, the first management node can perform the process of steps 501-503. Among them, the seventh message in the embodiment of the present disclosure is used to apply to join the first blockchain network, and can also be named as other messages. The present disclosure does not limit the naming of the seventh message.

[0141] In some embodiments, the target data may be synchronized from any management node in the first blockchain network to a third management node. Wherein, in the case where the target data is synchronized from the first management node to the third management node, the method may further include: synchronizing the target data to the third management node.

[0142] The step of synchronizing the target data to the third management node by the first management node may be executed by the first management node in response to receiving a twelfth message sent by the third management node, wherein the twelfth message is used to apply for synchronization of the target data.

[0143] It should be noted that the process in which the third management node sends the twelfth message to the first management node and the first management node synchronizes the target data to the third management node can be performed before step 501 or after step 501. The present disclosure does not limit the execution timing of this process.

[0144] In view of the problem of preventing malicious behavior between management nodes, the following Figure 6 , taking the PBFT consensus mechanism as an example, the synchronization process of the target data and the process in which the first management node determines with the second management node whether to allow the third management node to join the first blockchain network through the consensus mechanism are illustrated. In which, the first blockchain network includes management nodes 1, 2, 3, and 4, among which there are no malicious or faulty nodes, management node 1 is the first management node, the second management node includes management nodes 2, 3, and 4, and management node 5 is the third management node (i.e., the new node to be added to the first blockchain network), and the first management node synchronizes the target data to the third management node as an example.

[0145] refer to Figure 6 After the management node 5 is started, it can send a synchronization data request (i.e., the twelfth message in the embodiment of the present disclosure) to the existing management node 1 in the first blockchain network (corresponding to Figure 6 Synchronous data application in ).

[0146] The management node 1 that receives the data synchronization application may synchronize the target data to the management node 5 after verifying the identity of the management node 5 .

[0147] After the management node 5 completes the synchronization of the target data, it can send a node addition request (i.e., the seventh message in the embodiment of the present disclosure) to the existing management node 1 (corresponding to Figure 6 to apply to add a new management node.

[0148] The existing management node 1 that receives the application for adding a node can send a proposal message for adding a node to other existing management nodes (i.e., management nodes 2, 3, and 4) in the first blockchain network (corresponding to Figure 6 The proposal message may include information such as the conditions under which the management node 5 participates in the management consensus voting after being triggered.

[0149] The management nodes (i.e., management nodes 2, 3, and 4) that receive the proposal message for adding a node can send a node preparation message (corresponding to the request message) to other existing management nodes in the first blockchain network after determining whether to allow management node 5 to join the first blockchain network according to the proposed contract. Figure 6 Preparation for adding nodes in the Figure 6 The middle management node 2 may send a node adding preparation message to the existing management nodes 1, 3, 4, the management node 3 may send a node adding preparation message to the existing management nodes 1, 2, 4, and the management node 4 may send a node adding preparation message to the existing management nodes 1, 2, 3.

[0150] Furthermore, all existing management nodes can send a node addition confirmation message to other management nodes in the first blockchain network (corresponding to Figure 6Add node confirmation in ), for example Figure 6 The management node 1 can send a node add confirmation message to the existing management nodes 2, 3, and 4, the management node 2 can send a node add confirmation message to the existing management nodes 1, 3, and 4, the management node 3 can send a node add confirmation message to the existing management nodes 1, 2, and 4, and the management node 4 can send a node add confirmation message to the existing management nodes 1, 2, and 3.

[0151] Furthermore, the management nodes that receive the add node proposal message (i.e., management nodes 2, 3, and 4) can send an add node reply message (corresponding to Figure 6 Add node reply in ).

[0152] Furthermore, the management node (i.e., management node 1) that receives the application for adding a node may send a node adding feedback message to management node 5 (corresponding to Figure 6 Add node feedback in ).

[0153] It should be noted that the implementation details in the above examples can refer to the relevant technologies, and the embodiments of the present disclosure will not go into details about the implementation details.

[0154] As a result, the existing management nodes in the first blockchain network can determine whether to allow the third management node to join the first blockchain network through a consensus mechanism, and when the third management node is allowed to join the first blockchain network and the synchronization of target data is completed, the third management node is added to the first blockchain network.

[0155] In some embodiments, for an established blockchain network with specific functions, if data interaction is required, cross-chain data intercommunication can be achieved through cross-chain technology (including mechanisms such as notaries, side chains / relays, hash locking, distributed private key control, and cross-chain gateways that can include two or more parties). For wide-area cross-domain data interaction, especially in scenarios involving multiple parties, a wide-area blockchain functional network across functional domains can be established through negotiation by managing multiple management nodes of multiple functional domains, and cryptographic and privacy computing technologies can be combined to achieve secure interaction of wide-area cross-domain data. For data verification and data interaction between locally deployed blockchain networks and remotely deployed blockchain networks, a secure and efficient cross-chain mechanism needs to be adopted for communication. For example, a two-party or multi-party cross-chain gateway mechanism can be used for cross-chain data interaction to ensure the efficiency of interaction and the flexibility and scalability of the interaction protocol.

[0156] In some embodiments, based on any of the foregoing embodiments, the management method of the blockchain network may further include:

[0157] Obtain the hash value of each block in the second blockchain network;

[0158] The hash value is sent to the third blockchain network, and the hash value is used to store the blockchain that is uploaded to the third blockchain network, wherein the third blockchain network is a blockchain network managed by any management node in the first blockchain network.

[0159] Among them, the third blockchain network can be a blockchain network managed by the first management node, or it can be a blockchain network managed by the second management node, and the present disclosure does not impose any restrictions on this.

[0160] Thus, the data interaction between the second blockchain network managed by the first management node and the third blockchain network managed by any management node can be realized. And because each block in the second blockchain network has saved the hash value of the previous block, the hash value of each block in the second blockchain network is linked to the blockchain of the third blockchain network for storage, which is equivalent to multi-layer hash locking. Through multi-layer hash locking, the hash value of each block in the second blockchain network can be stored only on the blockchain of the third blockchain network, which reduces the consumption of storage resources and improves the efficiency of data on-chain, and further improves the tamper-proof characteristics of data in the blockchain nodes of the alliance chain network with a limited number of nodes.

[0161] In addition, there may be a situation in the first blockchain network where a management node is unwilling to use blockchain to record its management behavior. For example, it is unwilling to store the attribute information of the second blockchain network it manages in the blockchain of the first blockchain network. In this case, a model of multiple third-party endorsements can be adopted to record its management behavior. Its management behavior can adopt a privacy protection solution to prove that it has no malicious impact on the entire blockchain network system.

[0162] Figure 7 A flowchart of another blockchain network management method provided by an embodiment of the present disclosure.

[0163] It should be noted that the method is applied to any second management node in the first blockchain network and is executed by the management device of the blockchain network. The management device of the blockchain network may be the second management node or may be configured in the second management node, and the present disclosure does not limit this.

[0164] like Figure 7 As shown, the management method of the blockchain network may include the following steps 701-702.

[0165] Step 701: Receive a first message broadcast by a first management node in a first blockchain network, wherein the first message carries attribute information of a second blockchain network managed by the first management node, and is used by the first management node and the second management node to verify the attribute information through a consensus mechanism.

[0166] In some embodiments, the first blockchain network includes multiple management nodes, and a single management node can only manage the blockchain network within its own scope of authority, and the attribute information of the blockchain network managed by the single management node can be stored on the blockchain of the first blockchain network.

[0167] In some embodiments, when uploading the attribute information of the second blockchain network managed by the first management node, the first management node may broadcast a first message to the second management node in the first blockchain network, wherein the first message carries the attribute information of the second blockchain network managed by the first management node, and is used by the first management node and the second management node to verify the attribute information through a consensus mechanism. The number of the second management node may be one or more, and the present disclosure does not limit this. Accordingly, execution Figure 7 The second management node of the blockchain network management method shown can receive the first message.

[0168] In some embodiments, the second blockchain network includes at least one of a first type of blockchain network and a second type of blockchain network;

[0169] The first type of blockchain network includes multiple blockchain nodes deployed in different areas, the communication delay between different areas is higher than the first delay threshold, and / or the distance between different areas is greater than the first distance threshold;

[0170] The second type of blockchain network includes multiple blockchain nodes deployed in the same area, the communication delay in the same area is lower than the second delay threshold, and / or the distance between different locations in the same area is not greater than the second distance threshold.

[0171] In some embodiments, the attribute information of the second blockchain network includes at least one of the following:

[0172] The identifier of the second blockchain network;

[0173] The number of blockchain nodes included in the second blockchain network;

[0174] The identifier of the alliance to which the second blockchain network belongs;

[0175] The network protocol of the second blockchain network;

[0176] The consensus algorithm used by the second blockchain network;

[0177] The incentive mechanism adopted by the second blockchain network;

[0178] Second, information about smart contracts deployed on the blockchain network;

[0179] The deployment method of the second blockchain network.

[0180] Step 702, after verifying and confirming the attribute information, send a second message to the first management node; wherein, the second message is used for the first management node to upload the attribute information to the blockchain of the first blockchain network for storage when receiving the second message sent by at least one second management node.

[0181] In some embodiments, after any second management node receives the first message, it can send a second message to the first management node after verifying and confirming the attribute information through a consensus mechanism, so that the first management node can upload the attribute information to the blockchain of the first blockchain network for storage after receiving the second message sent by at least one second management node. In this way, the attribute information of the second blockchain network can be stored in a distributed manner on the blockchain of the first blockchain network.

[0182] It should be noted that, for the specific implementation process and principles of the steps in the embodiments of the present disclosure that are similar or corresponding to those in other embodiments, reference can be made to the descriptions of other embodiments and will not be repeated here.

[0183] The management method of the blockchain network provided by the embodiment of the present disclosure receives the first message broadcast by the first management node through the second management node in the first blockchain network, wherein the first message carries the attribute information of the second blockchain network managed by the first management node, and is used for the first management node and the second management node to verify the attribute information through the consensus mechanism; in the case of verifying and confirming the attribute information, the second message is sent to the first management node; wherein the second message is used for the first management node to link the attribute information to the blockchain of the first blockchain network for storage when receiving the second message sent by at least one second management node. Thus, by using multiple management nodes to form the first blockchain network, a single management node only manages the blockchain network within its own rights and interests, which can disperse and balance the management authority of the management node on the blockchain network, reduce the risk of management failure caused by the failure of a single management node, and improve the reliability of the management of the blockchain network. In addition, by linking the attribute information of the blockchain network managed by the first management node to the blockchain of the first blockchain network for storage, the immutability, security and reliability of the attribute information of the blockchain network can be guaranteed.

[0184] In a possible implementation form, at least two management nodes in the first blockchain network can collaboratively manage the same blockchain network. Figure 8 , the management method of the blockchain network provided by the embodiment of the present disclosure is further explained.

[0185] Combine the following Figure 8 , the management method of the blockchain network provided by the embodiment of the present disclosure is further explained.

[0186] Figure 8 A flowchart of another blockchain network management method provided by an embodiment of the present disclosure.

[0187] like Figure 8 As shown, the management method of the blockchain network may include the following steps 801-803.

[0188] Step 801: The second management node in the first blockchain network negotiates with the first management node to determine the attribute information of the second blockchain network. The second blockchain network is jointly managed by the first management node and the target management node, and the target management node includes the second management node.

[0189] The second blockchain network can be managed by at least two management nodes in the first blockchain network, and the first management node can be any one of the at least two management nodes. The target management node can be any other management node in the first blockchain network except the first management node, that is, any second management node in the first blockchain network. The number of target management nodes can be one or more, and the present disclosure does not limit this.

[0190] In some embodiments, the target management node includes executing Figure 8 In the case of the second management node of the blockchain network management method shown, the second management node and the first management node can use multiple interactions to negotiate and determine the attribute information of the second blockchain network.

[0191] In some embodiments, step 801 may be implemented in the following manner:

[0192] Receiving a third message sent by the first management node, wherein the third message carries initial attribute information of the second blockchain network;

[0193] When the initial attribute information is confirmed, a fourth message is sent to the first management node, and the fourth message is used by the first management node to determine the initial attribute information as the attribute information of the second blockchain network.

[0194] In some embodiments, step 801 may be implemented in the following manner:

[0195] Receiving a fifth message sent by the target management node, wherein the fifth message carries initial attribute information of the second blockchain network;

[0196] When the initial attribute information is not confirmed, a sixth message is sent to the first management node, wherein the sixth message carries the revised attribute information of the second blockchain network, so that the first management node can determine the revised attribute information as the attribute information of the second blockchain network when the revised attribute information is confirmed.

[0197] In some embodiments, step 801 may be implemented in the following manner:

[0198] An eighth message is sent to the first management node, wherein the eighth message carries initial attribute information of the second blockchain network, and is used by the first management node to determine the initial attribute information as the attribute information of the second blockchain network when the initial attribute information is confirmed.

[0199] In some embodiments, step 801 may be implemented in the following manner:

[0200] Sending a ninth message to the first management node, wherein the ninth message carries initial attribute information of the second blockchain network;

[0201] receiving a tenth message sent by the first management node, wherein the tenth message carries revised attribute information of the second blockchain network and is sent by the first management node without confirming the initial attribute information;

[0202] When the revised attribute information is confirmed, an eleventh message is sent to the first management node, wherein the eleventh message is used by the first management node to determine the revised attribute information as the attribute information of the second blockchain network.

[0203] As a result, the second management node and the first management node can negotiate and determine the attribute information of the second blockchain network through multiple interactions.

[0204] It should be noted that the process in which the second management node and the first management node use multiple interactions to negotiate and determine the attribute information of the second blockchain network is merely an exemplary description and should not be construed as a limitation on the embodiments of the present disclosure. In actual applications, the second management node and the first management node may use more or fewer interactions or other types of interactions to negotiate and determine the attribute information of the second blockchain network, and the present disclosure does not impose any limitations on this.

[0205] Furthermore, after the attribute information of the second blockchain network is determined through negotiation, the second blockchain network and its smart contracts and application services can be deployed based on the attribute information of the second blockchain network determined through negotiation.

[0206] In some embodiments, when the second blockchain network is managed by the first management node and the second management node in a coordinated manner, the second blockchain network and the smart contracts and application services deployed thereon may be deployed by the second management node. Accordingly, the management method of the blockchain network may further include:

[0207] Deploying a second blockchain network including a plurality of blockchain nodes;

[0208] Deploy smart contracts and application services on the second blockchain network;

[0209] According to the demand information of application services, the smart contract is configured, and the start and stop and functions of the second blockchain network are adjusted.

[0210] Furthermore, the following steps 802-803 may be adopted to distribute and store the attribute information of the second blockchain network on the blockchain of the first blockchain network.

[0211] Step 802: The second management node receives the first message broadcast by the first management node, wherein the first message carries attribute information of the second blockchain network, and is used by the first management node and the second management node to verify the attribute information through a consensus mechanism.

[0212] Step 803, when the attribute information is verified and confirmed, the second management node sends a second message to the first management node; wherein, the second message is used for the first management node to upload the attribute information to the blockchain of the first blockchain network for storage when receiving the second message sent by at least one second management node.

[0213] Therefore, by using multiple management nodes to form the first blockchain network, a single management node only manages the blockchain network within its own jurisdiction, which can disperse and balance the management node's management authority over the blockchain network, reduce the risk of management failure caused by the failure of a single management node, and improve the reliability of the management of the blockchain network. In addition, the same blockchain network can belong to at least two management nodes and be managed by the at least two management nodes in a coordinated manner, thereby avoiding the failure of a single management node to cause the management failure of the blockchain network, and meeting the needs of a global multi-party application scenario where multiple parties need to collaborate to establish a blockchain network to meet the needs of a certain special business. In addition, by uploading the attribute information of the blockchain network jointly managed by the first management node and the target management node to the blockchain of the first blockchain network for storage, the immutability, security and reliability of the attribute information of the blockchain network can be guaranteed.

[0214] In some embodiments, the blockchain network management method may further include:

[0215] Obtain the hash value of each block in the second blockchain network;

[0216] The hash value is sent to the fourth blockchain network, and the hash value is used to be stored in the blockchain uploaded to the fourth blockchain network, wherein the fourth blockchain network is a blockchain network managed by any management node in the first blockchain network.

[0217] Among them, the fourth blockchain network can be a blockchain network managed by the first management node, or it can be a blockchain network managed by the second management node, and the present disclosure does not impose any restrictions on this.

[0218] Thus, the second management node can realize data interaction between the second blockchain network managed in collaboration with the first management node and the fourth blockchain network managed by any management node. And because each block in the second blockchain network has saved the hash value of the previous block, the hash value of each block in the second blockchain network is linked to the blockchain of the fourth blockchain network for storage, which is equivalent to multi-layer hash locking. Through multi-layer hash locking, the hash value of each block in the second blockchain network can be stored only on the blockchain of the fourth blockchain network, which reduces the consumption of storage resources, improves the efficiency of data on-chain, and further improves the tamper-proof characteristics of data in the blockchain nodes of the alliance chain network with a limited number of nodes.

[0219] It should be noted that, for the specific implementation process and principles of the steps in the embodiments of the present disclosure that are similar or corresponding to those in other embodiments, reference can be made to the descriptions of other embodiments and will not be repeated here.

[0220] In a possible implementation form, on the basis of the existing management nodes of the first blockchain network, a new management node can be added to the first blockchain network. Fig. 9 , the management method of the blockchain network provided by the embodiment of the present disclosure is further explained.

[0221] Fig. 9 A flowchart of another blockchain network management method provided by an embodiment of the present disclosure.

[0222] like Fig. 9 As shown in the aforementioned Figure 7 or Figure 8 Based on the illustrated embodiment, the management method of the blockchain network may further include the following steps 901-903.

[0223] Step 901, receiving the seventh message sent by the third management node, where the seventh message is used to apply to join the first blockchain network.

[0224] Among them, the third management node is a management node that is not currently included in the first blockchain network.

[0225] The seventh message may carry the identity information, public key certificate, etc. of the third management node.

[0226] Step 902: Determine, through a consensus mechanism, with at least one management node in the first blockchain network whether to allow the third management node to join the first blockchain network.

[0227] Among them, the consensus mechanism can be set to any available consensus mechanism in the relevant technology as needed, and the present disclosure does not limit this.

[0228] In some embodiments, the at least one management node may include a first management node.

[0229] In some embodiments, the at least one management node may include at least one other second management node in the first blockchain network except the second management node executing step 902.

[0230] In some embodiments, the at least one management node may include the first management node and at least one other second management node in the first blockchain network except the second management node executing step 902. For example, the at least one management node may include all management nodes in the first blockchain network except the second management node executing step 902.

[0231] Step 903: When the third management node is allowed to join the first blockchain network and the synchronization of the target data is completed, the third management node is added to the first blockchain network, wherein the target data includes the data stored in the blockchain of the first blockchain network.

[0232] It should be noted that when the third management node needs to join the first blockchain network, it can send the seventh message to any management node in the first blockchain network to apply to join the first blockchain network. Correspondingly, steps 901-903 can be performed by the management node that receives the seventh message. In the case where the third management node sends the seventh message to the second management node, the second management node can perform the process of steps 901-903. Among them, the seventh message in the embodiment of the present disclosure is used to apply to join the first blockchain network, and can also be named as other messages. The present disclosure does not limit the naming of the seventh message.

[0233] In some embodiments, the target data may be synchronized from any management node in the first blockchain network to a third management node. Wherein, when the target data is synchronized from the second management node to the third management node, the method may further include: synchronizing the target data to the third management node.

[0234] The step of synchronizing the target data from the second management node to the third management node may be performed by the second management node in response to receiving a twelfth message sent by the third management node, wherein the twelfth message is used to apply for synchronization of the target data. The twelfth message may also be named as other messages, and the present disclosure does not limit the naming of the twelfth message.

[0235] It should be noted that the process in which the third management node sends the twelfth message to the second management node and the second management node synchronizes the target data to the third management node can be performed before step 901 or after step 901. The present disclosure does not limit the execution timing of this process.

[0236] As a result, the existing management nodes in the first blockchain network can determine whether to allow the third management node to join the first blockchain network through a consensus mechanism, and when the third management node is allowed to join the first blockchain network and the synchronization of target data is completed, the third management node is added to the first blockchain network.

[0237] It should be noted that, for the specific implementation process and principles of the steps in the embodiments of the present disclosure that are similar or corresponding to those in other embodiments, reference can be made to the descriptions of other embodiments and will not be repeated here.

[0238] In order to implement the above embodiments, the present disclosure also proposes a management device for a blockchain network.

[0239] Fig.10 A schematic diagram of the structure of a management device for a blockchain network provided in an embodiment of the present disclosure. The management device for the blockchain network is applied to a first management node in a first blockchain network, and can execute the management method of the blockchain network applied to the first management node in the aforementioned embodiment, wherein the management device for the blockchain network can be the first management node, or can be configured in the first management node, and the present disclosure does not limit this.

[0240] like Fig.10 As shown, the management device 1000 of the blockchain network includes: a transceiver module 1010 and a processing module 1020.

[0241] The transceiver module 1010 is used to broadcast a first message to the second management node in the first blockchain network, wherein the first message carries attribute information of the second blockchain network managed by the first management node, and is used for the first management node and the second management node to verify the attribute information through a consensus mechanism;

[0242] The processing module 1020 is used to upload the attribute information to the blockchain of the first blockchain network for storage when at least one second message is received, wherein the second message is sent by the second management node that receives the first message after verifying and confirming the attribute information.

[0243] As a possible implementation of the embodiment of the present disclosure, the second blockchain network is managed by the first management node and the target management node in the first blockchain network in a collaborative manner, wherein the second management node that sends the second message includes the target management node, or the second management node that sends the second message does not include the target management node; the management device 1000 of the blockchain network also includes:

[0244] The negotiation module is used to negotiate with the target management node to determine the attribute information of the second blockchain network.

[0245] As a possible implementation of the embodiment of the present disclosure, the negotiation module is used to:

[0246] Sending a third message to the target management node, wherein the third message carries initial attribute information of the second blockchain network;

[0247] When the fourth message sent by the target management node is received, the initial attribute information is determined as the attribute information of the second blockchain network; wherein, the fourth message is sent when the target management node confirms the initial attribute information.

[0248] As a possible implementation of the embodiment of the present disclosure, the negotiation module is used to:

[0249] Sending a fifth message to the target management node, wherein the fifth message carries initial attribute information of the second blockchain network;

[0250] receiving a sixth message sent by the target management node, wherein the sixth message carries revised attribute information of the second blockchain network and is sent by the target management node without confirming the initial attribute information;

[0251] When the revised attribute information is confirmed, the revised attribute information is determined as the attribute information of the second blockchain network.

[0252] As a possible implementation of the embodiment of the present disclosure, the attribute information of the second blockchain network includes at least one of the following:

[0253] The identifier of the second blockchain network;

[0254] The number of blockchain nodes included in the second blockchain network;

[0255] The identifier of the alliance to which the second blockchain network belongs;

[0256] The network protocol of the second blockchain network;

[0257] The consensus algorithm used by the second blockchain network;

[0258] The incentive mechanism adopted by the second blockchain network;

[0259] Second, information about smart contracts deployed on the blockchain network;

[0260] The deployment method of the second blockchain network.

[0261] As a possible implementation of the embodiment of the present disclosure, the second blockchain network includes at least one of a first type blockchain network and a second type blockchain network;

[0262] The first type of blockchain network includes multiple blockchain nodes deployed in different areas, the communication delay between different areas is higher than the first delay threshold, and / or the distance between different areas is greater than the first distance threshold;

[0263] The second type of blockchain network includes multiple blockchain nodes deployed in the same area, the communication delay in the same area is lower than the second delay threshold, and / or the distance between different locations in the same area is not greater than the second distance threshold.

[0264] As a possible implementation of the embodiment of the present disclosure, the management device 1000 of the blockchain network further includes:

[0265] An acquisition module, used to obtain the hash value of each block in the second blockchain network;

[0266] The transceiver module 1010 is also used to send the hash value to the third blockchain network, and the hash value is used to be uploaded to the blockchain of the third blockchain network for storage, wherein the third blockchain network is a blockchain network managed by any management node in the first blockchain network.

[0267] As a possible implementation of the embodiment of the present disclosure, the transceiver module 1010 is further used to receive a seventh message sent by the third management node, where the seventh message is used to apply to join the first blockchain network;

[0268] The processing module 1020 is also used to determine with the second management node through a consensus mechanism whether to allow the third management node to join the first blockchain network, and to add the third management node to the first blockchain network when the third management node is allowed to join the first blockchain network and the synchronization of target data is completed, wherein the target data includes data stored in the blockchain of the first blockchain network.

[0269] As a possible implementation manner of the embodiment of the present disclosure, the transceiver module 1010 is further configured to synchronize the target data to the third management node.

[0270] As a possible implementation of the embodiment of the present disclosure, the management device 1000 of the blockchain network further includes a deployment module for:

[0271] Deploying a second blockchain network including a plurality of blockchain nodes;

[0272] Deploy smart contracts and application services on the second blockchain network;

[0273] According to the demand information of application services, the smart contract is configured, and the start and stop and functions of the second blockchain network are adjusted.

[0274] It should be noted that the aforementioned explanation of the embodiment of the management method of the blockchain network applied to the first management node is also applicable to the management device of the blockchain network of this embodiment, and will not be repeated here.

[0275] In order to implement the above embodiments, the present disclosure also proposes a management device for a blockchain network.

[0276] Fig.11 A schematic diagram of the structure of a management device for a blockchain network provided in an embodiment of the present disclosure. The management device for the blockchain network is applied to a second management node in a first blockchain network, and can execute the management method of the blockchain network applied to the second management node in the aforementioned embodiment, wherein the management device for the blockchain network can be the second management node, or can be configured in the second management node, and the present disclosure does not limit this.

[0277] like Fig.11 As shown, the management device 1100 of the blockchain network includes: a transceiver module 1110.

[0278] The transceiver module 1110 is used to receive a first message broadcast by a first management node in the first blockchain network, wherein the first message carries attribute information of a second blockchain network established by the first management node, and is used by the first management node and the second management node to verify the attribute information through a consensus mechanism;

[0279] The transceiver module 1110 is also used to send a second message to the first management node when the attribute information is verified and confirmed; wherein, the second message is used for the first management node to upload the attribute information to the blockchain of the first blockchain network for storage when the first management node receives the second message sent by at least one second management node.

[0280] As a possible implementation of the embodiment of the present disclosure, the second blockchain network is managed by the first management node in collaboration with the target management node in the first blockchain network. When the target management node includes the second management node, the management device 1100 of the blockchain network further includes:

[0281] The negotiation module is used to negotiate with the first management node to determine the attribute information of the second blockchain network.

[0282] As a possible implementation of the embodiment of the present disclosure, the negotiation module is used to:

[0283] Receiving a third message sent by the first management node, wherein the third message carries initial attribute information of the second blockchain network;

[0284] When the initial attribute information is confirmed, a fourth message is sent to the first management node, and the fourth message is used by the first management node to determine the initial attribute information as the attribute information of the second blockchain network.

[0285] As a possible implementation of the embodiment of the present disclosure, the negotiation module is used to:

[0286] Receiving a fifth message sent by the target management node, wherein the fifth message carries initial attribute information of the second blockchain network;

[0287] When the initial attribute information is not confirmed, a sixth message is sent to the first management node, wherein the sixth message carries the revised attribute information of the second blockchain network, so that the first management node can determine the revised attribute information as the attribute information of the second blockchain network when the revised attribute information is confirmed.

[0288] As a possible implementation of the embodiment of the present disclosure, the management device 1100 of the blockchain network further includes a deployment module for:

[0289] Deploying a second blockchain network including a plurality of blockchain nodes;

[0290] Deploy smart contracts and application services on the second blockchain network;

[0291] According to the demand information of application services, the smart contract is configured, and the start and stop and functions of the second blockchain network are adjusted.

[0292] As a possible implementation of the embodiment of the present disclosure, the management device 1100 of the blockchain network further includes:

[0293] An acquisition module, used to obtain the hash value of each block in the second blockchain network;

[0294] The transceiver module 1110 is also used to send the hash value to the fourth blockchain network, and the hash value is used to be uploaded to the blockchain of the fourth blockchain network for storage, wherein the fourth blockchain network is a blockchain network managed by any management node in the first blockchain network.

[0295] As a possible implementation of the embodiment of the present disclosure, the attribute information of the second blockchain network includes at least one of the following:

[0296] The identifier of the second blockchain network;

[0297] The number of blockchain nodes included in the second blockchain network;

[0298] The identifier of the alliance to which the second blockchain network belongs;

[0299] The network protocol of the second blockchain network;

[0300] The consensus algorithm used by the second blockchain network;

[0301] The incentive mechanism adopted by the second blockchain network;

[0302] Second, information about smart contracts deployed on the blockchain network;

[0303] The deployment method of the second blockchain network.

[0304] As a possible implementation of the embodiment of the present disclosure, the second blockchain network includes at least one of a first type blockchain network and a second type blockchain network;

[0305] The first type of blockchain network includes multiple blockchain nodes deployed in different areas, the communication delay between different areas is higher than the first delay threshold, and / or the distance between different areas is greater than the first distance threshold;

[0306] The second type of blockchain network includes multiple blockchain nodes deployed in the same area, the communication delay in the same area is lower than the second delay threshold, and / or the distance between different locations in the same area is not greater than the second distance threshold.

[0307] As a possible implementation of the embodiment of the present disclosure, the transceiver module 1110 is further used to receive a seventh message sent by the third management node, where the seventh message is used to apply to join the first blockchain network;

[0308] The management device 1100 of the blockchain network also includes a processing module, which is used to determine whether to allow a third management node to join the first blockchain network through a consensus mechanism with at least one management node in the first blockchain network, and to add the third management node to the first blockchain network when the third management node is allowed to join the first blockchain network and the synchronization of target data is completed, wherein the target data includes data stored in the blockchain of the first blockchain network.

[0309] As a possible implementation manner of the embodiment of the present disclosure, the transceiver module 1110 is further configured to synchronize the target data to the third management node.

[0310] It should be noted that the aforementioned explanation of the embodiment of the management method of the blockchain network applied to the second management node is also applicable to the management device of the blockchain network of this embodiment, and will not be repeated here.

[0311] In order to implement the above embodiments, the present disclosure also proposes a first blockchain network.

[0312] Fig.12 A schematic diagram of the structure of a first blockchain network provided in an embodiment of the present disclosure.

[0313] like Fig.12 As shown, the first blockchain network 1200 includes a first management node 1210 and a second management node 1220. The first management node is used to execute the management method of the blockchain network applied to the first management node in the aforementioned embodiment. The second management node is used to execute the management method of the blockchain network applied to the second management node in the aforementioned embodiment. The number of the second management node can be one or more, Fig.12 An example is given in which the number of the second management nodes 1220 is three.

[0314] In some embodiments, the second blockchain network managed by the first management node 1210 includes at least one of a first type blockchain network and a second type blockchain network;

[0315] The first type of blockchain network includes multiple blockchain nodes deployed in different areas, the communication delay between different areas is higher than the first delay threshold, and / or the distance between different areas is greater than the first distance threshold;

[0316] The second type of blockchain network includes multiple blockchain nodes deployed in the same area, the communication delay in the same area is lower than the second delay threshold, and / or the distance between different locations in the same area is not greater than the second distance threshold.

[0317] It should be noted that the aforementioned explanation of the embodiment of the management method of the blockchain network applied to the first management node or the second management node is also applicable to the first blockchain network of this embodiment and will not be repeated here.

[0318] In order to implement the above embodiment, the present disclosure also proposes a blockchain network system. The blockchain network system includes a first blockchain network and a second blockchain network. The first blockchain network includes a first management node and a second management node.

[0319] Among them, the second blockchain network is used to upload the data to be stored in the corresponding area to the blockchain of the second blockchain network for storage.

[0320] A first blockchain network, for executing through a first management node Figure 1 , 3 or the method described in any one of the embodiments 5, and the second management node executes Figure 7 , 8 Or the method described in any one of embodiments 9 to manage the second blockchain network.

[0321] Among them, the second blockchain network includes at least one of the first type blockchain network and the second type blockchain network.

[0322] The first type of blockchain network includes multiple blockchain nodes deployed in different areas, the communication delay between different areas is higher than the first delay threshold, and / or the distance between different areas is greater than the first distance threshold;

[0323] The second type of blockchain network includes multiple blockchain nodes deployed in the same area, the communication delay in the same area is lower than the second delay threshold, and / or the distance between different locations in the same area is not greater than the second distance threshold.

[0324] Combine the following Fig.13 , the blockchain network system provided by the embodiment of the present disclosure is illustrated by way of example.

[0325] like Fig.13 As shown, the blockchain network system may include a first blockchain network, and the first blockchain network includes management node 1301, management node 1302, management node 1303, management node 1304 and management node 1305.

[0326] Among them, taking management node 1303 as an example, management node 1303 can independently manage blockchain network 1306, and other blockchain networks that have data interaction with blockchain network 1306, such as blockchain networks 1309, 1310, and 1311. In addition, management node 1303 can also independently manage blockchain network 1312.

[0327] Taking management node 1305 as an example, management node 1305 can independently manage blockchain network 1308, as well as other blockchain networks that have data interaction with blockchain network 1308, such as blockchain networks 1315 and 1316. In addition, management node 1305 can also independently manage blockchain network 1317.

[0328] In addition, management node 1303 and management node 1305 can jointly manage blockchain network 1307, as well as other blockchain networks that have data interactions with blockchain network 1307, such as blockchain networks 1313 and 1314.

[0329] Among them, the blockchain network managed by each management node can be flexibly deployed as a first type blockchain network or a second type blockchain network according to business needs. For example, blockchain networks 1306, 1307, and 1308 can be first type blockchain networks, and other blockchain networks can be deployed as second type blockchain networks, or blockchain networks 1306, 1307, and 1308 can be second type blockchain networks, and other blockchain networks can be deployed as first type blockchain networks.

[0330] Taking the management node 1303 as the first management node as an example, the management nodes 1301, 1302, 1304, and 1305 are second management nodes.

[0331] For a blockchain network managed solely by the management node 1303, the management node 1303 may broadcast a first message to other second management nodes 1301, 1302, 1304, and 1305, wherein the first message carries the attribute information of the blockchain network managed by the management node 1303, and is used for the management node 1303 and the second management nodes 1301, 1302, 1304, and 1305 to verify the attribute information through a consensus mechanism. The second management node that receives the first message may send a second message to the management node 1303 after verifying and confirming the attribute information. When the management node 1303 receives at least one second message, the attribute information may be uploaded to the blockchain of the first blockchain network for storage.

[0332] For the blockchain network managed by the management node 1303 and the management node 1305, the management node 1303 and the management node 1305 can negotiate to determine the attribute information of the blockchain network. The management node 1303 can broadcast a first message to other second management nodes 1301, 1302, 1304, and 1305, wherein the first message carries the attribute information of the blockchain network managed by the management node 1303 and the management node 1305, and is used by the first management node and the second management node to verify the attribute information through a consensus mechanism. The second management node that receives the first message can send a second message to the management node 1303 after verifying and confirming the attribute information. When the management node 1303 receives at least one second message, the attribute information can be uploaded to the blockchain of the first blockchain network for storage.

[0333] Taking the management node 1305 as the first management node as an example, the management nodes 1301, 1302, 1303, and 1304 are second management nodes.

[0334] For a blockchain network managed solely by the management node 1305, the management node 1305 may broadcast a first message to other second management nodes 1301, 1302, 1303, and 1304, wherein the first message carries the attribute information of the blockchain network managed by the management node 1305, and is used by the first management node and the second management node to verify the attribute information through a consensus mechanism. The second management node that receives the first message may send a second message to the management node 1305 after verifying and confirming the attribute information. When the management node 1305 receives at least one second message, the attribute information may be uploaded to the blockchain of the first blockchain network for storage.

[0335] For the blockchain network managed by the management node 1303 and the management node 1305, the management node 1303 and the management node 1305 can negotiate to determine the attribute information of the blockchain network. The management node 1305 can broadcast a first message to other second management nodes 1301, 1302, 1303, and 1304, wherein the first message carries the attribute information of the blockchain network managed by the management node 1303 and the management node 1305, and is used by the first management node and the second management node to verify the attribute information through a consensus mechanism. The second management node that receives the first message can send a second message to the management node 1305 after verifying and confirming the attribute information. When the management node 1305 receives at least one second message, the attribute information can be uploaded to the blockchain of the first blockchain network for storage.

[0336] Therefore, by using multiple management nodes to form the first blockchain network, a single management node only manages the blockchain network within its own jurisdiction, which can disperse and balance the management rights of the management nodes over the blockchain network, reduce the risk of management failure caused by the failure of a single management node, and improve the reliability of the management of the blockchain network. In addition, by uploading the attribute information of the blockchain network managed by each management node to the blockchain of the first blockchain network for storage, the immutability, security and reliability of the attribute information of the blockchain network can be guaranteed.

[0337] In order to implement the above embodiments, the present disclosure also proposes an electronic device, comprising: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor so that the at least one processor can execute the management method of the blockchain network proposed in any of the aforementioned embodiments of the present disclosure.

[0338] In order to implement the above embodiments, the present disclosure also proposes a non-transitory computer-readable storage medium storing computer instructions, wherein the computer instructions are used to enable the computer to execute the blockchain network management method proposed in any of the aforementioned embodiments of the present disclosure.

[0339] In order to implement the above embodiments, the present disclosure also proposes a computer program product, including a computer program. When the computer program is executed by a processor, it implements the management method of the blockchain network proposed in any of the aforementioned embodiments of the present disclosure.

[0340] Fig.14 A schematic block diagram of an example electronic device 1400 that can be used to implement an embodiment of the present disclosure is shown. The electronic device is intended to represent various forms of digital computers, such as laptop computers, desktop computers, workstations, personal digital assistants, servers, blade servers, mainframe computers, and other suitable computers. The electronic device can also represent various forms of mobile devices, such as personal digital processing, cellular phones, smart phones, wearable devices, and other similar computing devices. The components shown herein, their connections and relationships, and their functions are merely examples and are not intended to limit the implementation of the present disclosure described and / or required herein.

[0341] like Fig.14As shown, the device 1400 includes a computing unit 1401, which can perform various appropriate actions and processes according to a computer program stored in a ROM (Read-Only Memory) 1402 or a computer program loaded from a storage unit 1405 to a RAM (Random Access Memory) 1403. Various programs and data required for the operation of the device 1400 can also be stored in the RAM 1403. The computing unit 1401, the ROM 1402, and the RAM 1403 are connected to each other via a bus 1404. An I / O (Input / Output) interface 1405 is also connected to the bus 1404.

[0342] A number of components in the device 1400 are connected to the I / O interface 1405, including: an input unit 1406, such as a keyboard, a mouse, etc.; an output unit 1407, such as various types of displays, speakers, etc.; a storage unit 1405, such as a disk, an optical disk, etc.; and a communication unit 1409, such as a network card, a modem, a wireless communication transceiver, etc. The communication unit 1409 allows the device 1400 to exchange information / data with other devices through a computer network such as the Internet and / or various telecommunication networks.

[0343] The computing unit 1401 may be a variety of general and / or special processing components with processing and computing capabilities. Some examples of the computing unit 1401 include, but are not limited to, a CPU (Central Processing Unit), a GPU (Graphic Processing Units), various dedicated AI (Artificial Intelligence) computing chips, various computing units running machine learning model algorithms, a DSP (Digital Signal Processor), and any appropriate processor, controller, microcontroller, etc. The computing unit 1401 performs the various methods and processes described above, such as a management method for a blockchain network. For example, in some embodiments, the management method for a blockchain network may be implemented as a computer software program, which is tangibly contained in a machine-readable medium, such as a storage unit 1405. In some embodiments, part or all of the computer program may be loaded and / or installed on the device 1400 via the ROM 1402 and / or the communication unit 1409. When the computer program is loaded into the RAM 1403 and executed by the computing unit 1401, one or more steps of the management method for the blockchain network described above may be performed. Alternatively, in other embodiments, the computing unit 1401 may be configured to execute the management method of the blockchain network in any other appropriate manner (for example, by means of firmware).

[0344] Various embodiments of the systems and techniques described above herein may be implemented in digital electronic circuit systems, integrated circuit systems, FPGAs (Field Programmable Gate Arrays), ASICs (Application-Specific Integrated Circuits), ASSPs (Application Specific Standard Products), SOCs (System On Chips), CPLDs (Complex Programmable Logic Devices), computer hardware, firmware, software, and / or combinations thereof. These various embodiments may include: being implemented in one or more computer programs that may be executed and / or interpreted on a programmable system including at least one programmable processor that may be a dedicated or general-purpose programmable processor that may receive data and instructions from a storage system, at least one input device, and at least one output device, and transmit data and instructions to the storage system, the at least one input device, and the at least one output device.

[0345] The program code for implementing the method of the present disclosure may be written in any combination of one or more programming languages. These program codes may be provided to a processor or controller of a general-purpose computer, a special-purpose computer, or other programmable data processing device, so that the program code, when executed by the processor or controller, enables the functions / operations specified in the flow chart and / or block diagram to be implemented. The program code may be executed entirely on the machine, partially on the machine, partially on the machine and partially on a remote machine as a stand-alone software package, or entirely on a remote machine or server.

[0346] In the context of the present disclosure, a machine-readable medium may be a tangible medium that may contain or store a program for use by or in conjunction with an instruction execution system, device, or apparatus. A machine-readable medium may be a machine-readable signal medium or a machine-readable storage medium. A machine-readable medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, device, or device, or any suitable combination of the foregoing. More specific examples of machine-readable storage media may include an electrical connection based on one or more lines, a portable computer disk, a hard disk, RAM, ROM, EPROM (Electrically Programmable Read-Only-Memory) or flash memory, optical fiber, CD-ROM (Compact Disc Read-Only Memory), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

[0347] To provide interaction with a user, the systems and techniques described herein can be implemented on a computer having: a display device (e.g., a CRT (Cathode-Ray Tube) or LCD (Liquid Crystal Display) monitor) for displaying information to the user; and a keyboard and pointing device (e.g., a mouse or trackball) through which the user can provide input to the computer. Other types of devices can also be used to provide interaction with the user; for example, the feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user can be received in any form (including acoustic input, voice input, or tactile input).

[0348] The systems and techniques described herein may be implemented in a computing system that includes a backend component (e.g., as a data server), or a computing system that includes a middleware component (e.g., an application server), or a computing system that includes a frontend component (e.g., a user computer with a graphical user interface or a web browser through which a user can interact with an implementation of the systems and techniques described herein), or a computing system that includes any combination of such backend components, middleware components, or frontend components. The components of the system may be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include: LAN (Local Area Network), WAN (Wide Area Network), the Internet, and blockchain networks.

[0349] A computer system may include a client and a server. The client and the server are generally remote from each other and usually interact through a communication network. The relationship between the client and the server is generated by computer programs running on the corresponding computers and having a client-server relationship with each other. The server may be a cloud server, also known as a cloud computing server or cloud host, which is a host product in the cloud computing service system to solve the defects of difficult management and weak business scalability in traditional physical hosts and VPS services ("Virtual Private Server", or "VPS" for short). The server may also be a server of a distributed system, or a server combined with a blockchain.

[0350] In the description of this specification, the terms "first" and "second" are used for descriptive purposes only and cannot be understood as indicating or implying relative importance or implicitly indicating the number of the indicated technical features. Therefore, the features defined as "first" and "second" may explicitly or implicitly include at least one of the features. In the description of this disclosure, the meaning of "plurality" is at least two, such as two, three, etc., unless otherwise clearly and specifically defined.

[0351] In the description of this specification, the description with reference to the terms "one embodiment", "some embodiments", "example", "specific example", or "some examples" etc. means that the specific features, structures, materials or characteristics described in conjunction with the embodiment or example are included in at least one embodiment or example of the present disclosure. In this specification, the schematic representations of the above terms do not necessarily refer to the same embodiment or example. Moreover, the specific features, structures, materials or characteristics described may be combined in any one or more embodiments or examples in a suitable manner. In addition, those skilled in the art may combine and combine the different embodiments or examples described in this specification and the features of the different embodiments or examples, without contradiction.

[0352] Although the embodiments of the present disclosure have been shown and described above, it is to be understood that the above embodiments are exemplary and are not to be construed as limitations of the present disclosure. A person skilled in the art may change, modify, replace and vary the above embodiments within the scope of the present disclosure.

Claims

1. A method for managing a blockchain network, characterized in that: Applied to a first management node in a first blockchain network, the method includes: Broadcasting a first message to a second management node in the first blockchain network, wherein the first message carries attribute information of the second blockchain network managed by the first management node, so that the first management node and the second management node verify the attribute information through a consensus mechanism; Upon receiving at least one second message, uplinking the attribute information to the blockchain of the first blockchain network for storage, wherein the second message is sent by the second management node that receives the first message after verifying and confirming the attribute information; The second blockchain network is managed by the first management node and a target management node in the first blockchain network in collaboration, wherein the second management node that sends the second message includes the target management node, or the second management node that sends the second message does not include the target management node; The method further comprises: Negotiate with the target management node to determine the attribute information of the second blockchain network; The step of negotiating with the target management node to determine the attribute information of the second blockchain network includes: Sending a third message to the target management node, wherein the third message carries initial attribute information of the second blockchain network; Upon receiving the fourth message sent by the target management node, determining the initial attribute information as the attribute information of the second blockchain network; wherein the fourth message is sent by the target management node when confirming the initial attribute information; Alternatively, the negotiating with the target management node to determine the attribute information of the second blockchain network includes: Sending a fifth message to the target management node, wherein the fifth message carries initial attribute information of the second blockchain network; receiving a sixth message sent by the target management node, wherein the sixth message carries revised attribute information of the second blockchain network and is sent by the target management node without confirming the initial attribute information; When the revised attribute information is confirmed, the revised attribute information is determined as the attribute information of the second blockchain network.

2. The method according to claim 1, characterized in that The attribute information of the second blockchain network includes at least one of the following: an identifier of the second blockchain network; the number of blockchain nodes included in the second blockchain network; An identifier of the alliance to which the second blockchain network belongs; The network protocol of the second blockchain network; The consensus algorithm adopted by the second blockchain network; the incentive mechanism adopted by the second blockchain network; Relevant information about the smart contract deployed on the second blockchain network; The deployment method of the second blockchain network.

3. The method according to claim 1, characterized in that The second blockchain network includes at least one of a first type of blockchain network and a second type of blockchain network; The first type of blockchain network includes multiple blockchain nodes deployed in different areas, the communication delay between the different areas is higher than the first delay threshold, and / or the distance between the different areas is greater than the first distance threshold; The second type of blockchain network includes multiple blockchain nodes deployed in the same area, the communication delay in the same area is lower than the second delay threshold, and / or the distance between different locations in the same area is not greater than the second distance threshold.

4. The method according to claim 1, characterized in that: The method further comprises: Obtaining hash values ​​of each block in the second blockchain network; The hash value is sent to a third blockchain network, and the hash value is used to be uploaded to the blockchain of the third blockchain network for storage, wherein the third blockchain network is a blockchain network managed by any management node in the first blockchain network.

5. The method according to any one of claims 1 to 4, characterized in that The method further comprises: receiving a seventh message sent by the third management node, where the seventh message is used to apply to join the first blockchain network; Determine, through the consensus mechanism, with the second management node whether to allow the third management node to join the first blockchain network; When the third management node is allowed to join the first blockchain network and the synchronization of target data is completed, the third management node is added to the first blockchain network, wherein the target data includes the data stored in the blockchain of the first blockchain network.

6. The method according to claim 5, characterized in that The method further comprises: The target data is synchronized to the third management node.

7. The method according to any one of claims 1 to 4, characterized in that The method further comprises: Deploy the second blockchain network including a plurality of blockchain nodes; Deploy smart contracts and application services on the second blockchain network; The smart contract is configured according to the demand information of the application service, and the start and stop and functions of the second blockchain network are adjusted.

8. A method for managing a blockchain network, characterized in that: Applied to a second management node in a first blockchain network, the method includes: Receiving a first message broadcasted by a first management node in the first blockchain network, wherein the first message carries attribute information of a second blockchain network managed by the first management node, and is used by the first management node and the second management node to verify the attribute information through a consensus mechanism; When the attribute information is verified and confirmed, a second message is sent to the first management node; wherein the second message is used for the first management node to upload the attribute information to the blockchain of the first blockchain network for storage when receiving the second message sent by at least one of the second management nodes; The second blockchain network is managed by the first management node in collaboration with a target management node in the first blockchain network. When the target management node includes the second management node, the method further includes: Negotiate with the first management node to determine attribute information of the second blockchain network; The step of negotiating with the first management node to determine the attribute information of the second blockchain network includes: Receiving a third message sent by the first management node, wherein the third message carries initial attribute information of the second blockchain network; When the initial attribute information is confirmed, a fourth message is sent to the first management node, where the fourth message is used by the first management node to determine the initial attribute information as the attribute information of the second blockchain network; Alternatively, the negotiating with the first management node to determine the attribute information of the second blockchain network includes: Receiving a fifth message sent by the first management node, wherein the fifth message carries initial attribute information of the second blockchain network; Without confirming the initial attribute information, a sixth message is sent to the first management node, wherein the sixth message carries the revised attribute information of the second blockchain network, so that the first management node can determine the revised attribute information as the attribute information of the second blockchain network when the revised attribute information is confirmed.

9. The method according to claim 8, characterized in that The method further comprises: Deploy the second blockchain network including a plurality of blockchain nodes; Deploy smart contracts and application services on the second blockchain network; The smart contract is configured according to the demand information of the application service, and the start and stop and functions of the second blockchain network are adjusted.

10. The method according to claim 8, characterized in that The method further comprises: Obtaining hash values ​​of each block in the second blockchain network; The hash value is sent to a fourth blockchain network, and the hash value is used to be uploaded to the blockchain of the fourth blockchain network for storage, wherein the fourth blockchain network is a blockchain network managed by any management node in the first blockchain network.

11. The method according to claim 8, characterized in that The attribute information of the second blockchain network includes at least one of the following: an identifier of the second blockchain network; the number of blockchain nodes included in the second blockchain network; An identifier of the alliance to which the second blockchain network belongs; The network protocol of the second blockchain network; The consensus algorithm adopted by the second blockchain network; the incentive mechanism adopted by the second blockchain network; Relevant information about the smart contract deployed on the second blockchain network; The deployment method of the second blockchain network.

12. The method according to claim 8, characterized in that The second blockchain network includes at least one of a first type of blockchain network and a second type of blockchain network; The first type of blockchain network includes multiple blockchain nodes deployed in different areas, the communication delay between the different areas is higher than the first delay threshold, and / or the distance between the different areas is greater than the first distance threshold; The second type of blockchain network includes multiple blockchain nodes deployed in the same area, the communication delay in the same area is lower than the second delay threshold, and / or the distance between different locations in the same area is not greater than the second distance threshold.

13. The method according to any one of claims 8 to 12, characterized in that: The method further comprises: receiving a seventh message sent by the third management node, where the seventh message is used to apply to join the first blockchain network; Determine, through the consensus mechanism, with at least one management node in the first blockchain network whether to allow the third management node to join the first blockchain network; When the third management node is allowed to join the first blockchain network and the synchronization of target data is completed, the third management node is added to the first blockchain network, wherein the target data includes the data stored in the blockchain of the first blockchain network.

14. The method according to claim 13, characterized in that The method further comprises: The target data is synchronized to the third management node.

15. A management device for a blockchain network, characterized in that: Applied to a first management node in a first blockchain network, the device comprises: A transceiver module, configured to broadcast a first message to a second management node in the first blockchain network, wherein the first message carries attribute information of the second blockchain network managed by the first management node, and is used for the first management node and the second management node to verify the attribute information through a consensus mechanism; A processing module, configured to upload the attribute information to the blockchain of the first blockchain network for storage upon receiving at least one second message, wherein the second message is sent by the second management node that receives the first message after verifying and confirming the attribute information; The second blockchain network is managed by the first management node and a target management node in the first blockchain network in collaboration, wherein the second management node that sends the second message includes the target management node, or the second management node that sends the second message does not include the target management node; The device also includes: A negotiation module, used to negotiate with the target management node to determine the attribute information of the second blockchain network; Wherein, the negotiation module is used to: Sending a third message to the target management node, wherein the third message carries initial attribute information of the second blockchain network; Upon receiving the fourth message sent by the target management node, determining the initial attribute information as the attribute information of the second blockchain network; wherein the fourth message is sent by the target management node when confirming the initial attribute information; Alternatively, the negotiation module is used to: Sending a fifth message to the target management node, wherein the fifth message carries initial attribute information of the second blockchain network; receiving a sixth message sent by the target management node, wherein the sixth message carries revised attribute information of the second blockchain network and is sent by the target management node without confirming the initial attribute information; When the revised attribute information is confirmed, the revised attribute information is determined as the attribute information of the second blockchain network.

16. A management device for a blockchain network, characterized in that: Applied to a second management node in a first blockchain network, the device comprises: A transceiver module, configured to receive a first message broadcast by a first management node in the first blockchain network, wherein the first message carries attribute information of a second blockchain network established by the first management node, and is used for the first management node and the second management node to verify the attribute information through a consensus mechanism; The transceiver module is further configured to send a second message to the first management node when the attribute information is verified and confirmed; wherein the second message is configured for the first management node to upload the attribute information to the blockchain of the first blockchain network for storage when the first management node receives the second message sent by at least one of the second management nodes; The second blockchain network is managed by the first management node in collaboration with a target management node in the first blockchain network. When the target management node includes the second management node, the device further includes: A negotiation module, configured to negotiate with the first management node to determine attribute information of the second blockchain network; Wherein, the negotiation module is used to: Receiving a third message sent by the first management node, wherein the third message carries initial attribute information of the second blockchain network; When the initial attribute information is confirmed, a fourth message is sent to the first management node, where the fourth message is used by the first management node to determine the initial attribute information as the attribute information of the second blockchain network; Alternatively, the negotiation module is used to: Receiving a fifth message sent by the first management node, wherein the fifth message carries initial attribute information of the second blockchain network; Without confirming the initial attribute information, a sixth message is sent to the first management node, wherein the sixth message carries the revised attribute information of the second blockchain network, so that the first management node can determine the revised attribute information as the attribute information of the second blockchain network when the revised attribute information is confirmed.

17. A first blockchain network, characterized in that: include: A first management node, configured to execute the method according to any one of claims 1 to 7; The second management node is used to execute the method according to any one of claims 8 to 14.

18. The network according to claim 17, characterized in that The second blockchain network managed by the first management node includes at least one of a first type of blockchain network and a second type of blockchain network; The first type of blockchain network includes multiple blockchain nodes deployed in different areas, the communication delay between the different areas is higher than the first delay threshold, and / or the distance between the different areas is greater than the first distance threshold; The second type of blockchain network includes multiple blockchain nodes deployed in the same area, the communication delay in the same area is lower than the second delay threshold, and / or the distance between different locations in the same area is not greater than the second distance threshold.

19. A blockchain network system, characterized in that: include: A first blockchain network and a second blockchain network, wherein the first blockchain network includes a first management node and a second management node; The second blockchain network is used to upload the data to be stored in the corresponding area to the blockchain of the second blockchain network for storage; The first blockchain network is used to manage the second blockchain network by executing the method described in any one of claims 1 to 7 through the first management node, and the second management node executing the method described in any one of claims 8 to 14.

20. An electronic device comprising: at least one processor; as well as A memory communicatively connected to the at least one processor; characterized in that The memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor to enable the at least one processor to execute the method of any one of claims 1-7, or execute the method of any one of claims 8-14.

21. A non-transitory computer-readable storage medium storing computer instructions, wherein: The computer instructions are used to enable the computer to execute the method according to any one of claims 1 to 7, or to execute the method according to any one of claims 8 to 14.

22. A computer program product, characterized in that The invention comprises a computer program, which, when executed by a processor, implements the method according to any one of claims 1 to 7, or implements the method according to any one of claims 8 to 14.

Images