Block chain management method and system

Abstract

The embodiment of the invention provides a block chain management method and system, and the method is applied to a main all-in-one machine in the block chain management system, and comprises the steps: determining a deployment node corresponding to a block chain deployment instruction in response to the block chain deployment instruction; if the deployment node is the main all-in-one machine, determining a target block chain type and target encryption information in the block chain deployment instruction; based on the target block chain type and the target encryption information, deploying a corresponding block chain; and otherwise, forwarding the block chain deployment instruction to a corresponding slave all-in-one machine, so that the slave all-in-one machine deploys a corresponding block chain based on the block chain deployment instruction. According to the embodiment, the block chain application deployment difficulty is reduced, the deployment efficiency is improved, and the deployment of block chains in multiple all-in-one machines is completed through an all-in-one machine cluster proxy mode.

Description

Technical Field

[0001] The present application relates to the field of blockchain technology, and in particular to a blockchain management method and system. Background Art

[0002] Blockchain is a decentralized protocol. Each "chain" consists of a block structure that records the summary information of the previous block in a block header. It can store data securely, and the information cannot be forged or tampered with. It can automatically execute smart contracts without the review of any centralized organization. Transactions can be digital currencies or digital assets such as debts, equities, and copyrights. Compared with traditional centralized systems, it has the advantages of decentralization and data immutability.

[0003] In the blockchain architecture, there are usually multiple blockchains deployed in multiple nodes. How to manage blockchains in multiple nodes (such as the deployment of new blockchains, etc.) is an urgent problem to be solved. Summary of the invention

[0004] The embodiments of the present application provide a blockchain management method and system for implementing the management of blockchains in multiple nodes.

[0005] In a first aspect, an embodiment of the present application provides a first blockchain management method, which is applied to a main all-in-one machine in a blockchain management system, and the method includes:

[0006] In response to a blockchain deployment instruction, determining a deployment node corresponding to the blockchain deployment instruction;

[0007] If the deployment node is the master integrated machine, determining the target blockchain type and target encryption information in the blockchain deployment instruction; and deploying the corresponding blockchain based on the target blockchain type and the target encryption information;

[0008] Otherwise, the blockchain deployment instruction is forwarded to the corresponding slave integrated machine, so that the slave integrated machine deploys the corresponding blockchain based on the blockchain deployment instruction.

[0009] In some optional implementations, before responding to a blockchain deployment instruction and determining a deployment node corresponding to the blockchain deployment instruction, the method further includes:

[0010] The deployment interface is displayed with options for blockchain type, encryption, and deploying nodes.

[0011] In some optional implementations, deploying a corresponding blockchain based on the target blockchain type and the target encryption information includes:

[0012] Calling a target configuration template corresponding to the target blockchain type in the configuration warehouse of the main integrated machine; and generating a public-private key pair based on the target encryption information; wherein the configuration warehouse is provided with a plurality of configuration templates corresponding to the first preset blockchain type;

[0013] The corresponding blockchain is deployed based on the target configuration template, and the private key in the public-private key pair is placed in the password card of the main integrated machine.

[0014] In some optional implementations, deploying a corresponding blockchain based on the target blockchain type and the target encryption information further includes:

[0015] Determining whether to perform CA authentication based on the blockchain deployment instruction;

[0016] If so, the target authentication information is generated by the CA module of the main integrated machine.

[0017] Some optional implementations also include:

[0018] Based on the first status monitoring data, determining the operating status of each integrated machine; wherein the first status monitoring data includes the performance parameters of the master integrated machine and each slave integrated machine; and / or,

[0019] Based on the second status monitoring data, the operating status of each blockchain is determined; wherein the second status monitoring data includes request parameters of each blockchain.

[0020] Some optional implementations also include:

[0021] The operating status of all integrated machines and the operating status of all blockchains are sent to each slave integrated machine respectively.

[0022] In a second aspect, an embodiment of the present application provides a second blockchain management method, which is applied to a slave integrated machine in a blockchain management system, and the method includes:

[0023] After receiving the blockchain deployment instruction sent by the master integrated machine, determine the target blockchain type and target encryption information in the blockchain deployment instruction; wherein the blockchain deployment instruction is sent by the master integrated machine after determining that the deployment node corresponding to the blockchain deployment instruction is the slave integrated machine;

[0024] Based on the target blockchain type and the target encryption information, deploy the corresponding blockchain.

[0025] In some optional implementations, deploying a corresponding blockchain based on the target blockchain type and the target encryption information includes:

[0026] Calling the target configuration template corresponding to the target blockchain type in the configuration warehouse of the slave machine; and generating a public-private key pair based on the target encryption information; wherein the configuration warehouse is provided with a plurality of configuration templates corresponding to the second preset blockchain type;

[0027] The corresponding blockchain is deployed based on the target configuration template, and the private key in the public-private key pair is placed in the password card of the slave all-in-one machine.

[0028] In some optional implementations, deploying a corresponding blockchain based on the target blockchain type and the target encryption information further includes:

[0029] Determining whether to perform CA authentication based on the blockchain deployment instruction;

[0030] If so, the target authentication information is generated by the CA module of the slave machine.

[0031] Some optional implementations also include:

[0032] Receiving the performance parameters of each integrated machine and the operating status of each blockchain sent by the main integrated machine;

[0033] Among them, the operating status of each integrated machine is determined by the master integrated machine based on the first status monitoring data; the operating status of each blockchain is determined by the master integrated machine based on the second status monitoring data; the first status monitoring data includes the performance parameters of the master integrated machine and each slave integrated machine; the second status monitoring data includes the request parameters of each blockchain.

[0034] In a third aspect, an embodiment of the present application provides a blockchain management system, the system comprising a master integrated machine and at least one slave integrated machine; wherein:

[0035] A master integrated machine, configured to respond to a blockchain deployment instruction and determine a deployment node corresponding to the blockchain deployment instruction; if the deployment node is the master integrated machine, determine a target blockchain type and target encryption information in the blockchain deployment instruction; deploy a corresponding blockchain based on the target blockchain type and the target encryption information; otherwise, forward the blockchain deployment instruction to a corresponding slave integrated machine;

[0036] The slave machine is used to deploy the corresponding blockchain after receiving the blockchain deployment instruction sent by the master machine.

[0037] In a fourth aspect, an embodiment of the present application provides a first blockchain management device, which is applied to a main all-in-one machine, and the device includes:

[0038] A node determination unit, configured to determine, in response to a blockchain deployment instruction, a deployment node corresponding to the blockchain deployment instruction;

[0039] The first deployment unit is used to determine the target blockchain type and target encryption information in the blockchain deployment instruction if the deployment node is the master integrated machine; deploy the corresponding blockchain based on the target blockchain type and the target encryption information; otherwise, forward the blockchain deployment instruction to the corresponding slave integrated machine, so that the slave integrated machine deploys the corresponding blockchain based on the blockchain deployment instruction.

[0040] Some optional embodiments further include a display unit for displaying a deployment interface including a blockchain type option, an encryption option, and a deployment node option before the node determination unit responds to the blockchain deployment instruction and determines the deployment node corresponding to the blockchain deployment instruction.

[0041] In some optional implementation manners, the first deployment unit is specifically configured to:

[0042] Calling a target configuration template corresponding to the target blockchain type in the configuration warehouse of the main integrated machine; and generating a public-private key pair based on the target encryption information; wherein the configuration warehouse is provided with a plurality of configuration templates corresponding to the first preset blockchain type;

[0043] The corresponding blockchain is deployed based on the target configuration template, and the private key in the public-private key pair is placed in the password card of the main integrated machine.

[0044] In some optional implementation manners, the first deployment unit is specifically configured to:

[0045] Determining whether to perform CA authentication based on the blockchain deployment instruction;

[0046] If so, the target authentication information is generated by the CA module of the main integrated machine.

[0047] Some optional implementations further include a first monitoring unit, configured to:

[0048] Based on the first status monitoring data, determining the operating status of each integrated machine; wherein the first status monitoring data includes the performance parameters of the master integrated machine and each slave integrated machine; and / or,

[0049] Based on the second status monitoring data, the operating status of each blockchain is determined; wherein the second status monitoring data includes request parameters of each blockchain.

[0050] In some optional implementation manners, the first monitoring module is further used to:

[0051] The operating status of all integrated machines and the operating status of all blockchains are sent to each slave integrated machine respectively.

[0052] In a fifth aspect, an embodiment of the present application provides a second blockchain management device, which is applied to an all-in-one machine, and the device includes:

[0053] A second deployment unit is configured to determine, after receiving the blockchain deployment instruction sent by the master integrated machine, the target blockchain type and target encryption information in the blockchain deployment instruction; wherein the blockchain deployment instruction is sent by the master integrated machine after determining that the deployment node corresponding to the blockchain deployment instruction is the slave integrated machine;

[0054] The second deployment unit is also used to deploy the corresponding blockchain based on the target blockchain type and the target encryption information.

[0055] In some optional implementation manners, the second deployment unit is specifically configured to:

[0056] Calling the target configuration template corresponding to the target blockchain type in the configuration warehouse of the slave machine; and generating a public-private key pair based on the target encryption information; wherein the configuration warehouse is provided with a plurality of configuration templates corresponding to the second preset blockchain type;

[0057] The corresponding blockchain is deployed based on the target configuration template, and the private key in the public-private key pair is placed in the password card of the slave all-in-one machine.

[0058] In some optional implementation manners, the second deployment unit is specifically configured to:

[0059] Determining whether to perform CA authentication based on the blockchain deployment instruction;

[0060] If so, the target authentication information is generated by the CA module of the slave machine.

[0061] Some optional implementations further include a second monitoring unit, configured to:

[0062] Receiving the performance parameters of each integrated machine and the operating status of each blockchain sent by the main integrated machine;

[0063] Among them, the operating status of each integrated machine is determined by the master integrated machine based on the first status monitoring data; the operating status of each blockchain is determined by the master integrated machine based on the second status monitoring data; the first status monitoring data includes the performance parameters of the master integrated machine and each slave integrated machine; the second status monitoring data includes the request parameters of each blockchain.

[0064] In a sixth aspect, an embodiment of the present application provides a main all-in-one machine, comprising at least one processor and at least one memory, wherein the memory stores a computer program, and when the program is executed by the processor, the processor executes the blockchain management method described in any one of the first aspects above.

[0065] In the seventh aspect, an embodiment of the present application provides an all-in-one machine, comprising at least one processor and at least one memory, wherein the memory stores a computer program, and when the program is executed by the processor, the processor executes the blockchain management method described in any one of the second aspects above.

[0066] In an eighth aspect, an embodiment of the present application provides a computer-readable storage medium storing a computer program executable by a processor. When the program runs on the processor, the processor executes the blockchain management method described in any one of the first or second aspects above.

[0067] In the embodiment of the present application, a blockchain deployment instruction is received by a master integrated machine, and a corresponding deployment node is determined; when the deployment node is itself, the corresponding blockchain is directly deployed; when the deployment node is a slave integrated machine, the blockchain deployment instruction is sent to the slave integrated machine for blockchain deployment; since the types of blockchains are different and the configurations are different, some blockchains also involve special encryption. Therefore, when deploying, the corresponding blockchain is deployed based on the target blockchain type and target encryption information in the blockchain deployment instruction; not only the difficulty of blockchain application deployment is reduced and the deployment efficiency is improved, but also the deployment of blockchains in multiple nodes (multiple integrated machines) is completed through the integrated machine cluster agent mode. BRIEF DESCRIPTION OF THE DRAWINGS

[0068] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings required for use in the description of the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.

[0069] Figure 1 A schematic diagram of a blockchain management system architecture provided for an embodiment of the present application;

[0070] Figure 2 An all-in-one software architecture diagram provided for an embodiment of the present application;

[0071] Figure 3 An interactive flow chart of the first blockchain management method provided in an embodiment of the present application;

[0072] Figure 4A flowchart of the first blockchain management method provided in the embodiment of the present application;

[0073] Figure 5 A flowchart of a second blockchain management method provided in an embodiment of the present application;

[0074] Figure 6 A schematic diagram of the structure of the first blockchain management device provided in an embodiment of the present application;

[0075] Figure 7 A schematic diagram of the structure of a second blockchain management device provided in an embodiment of the present application;

[0076] Figure 8 A schematic diagram of the structure of the main integrated machine provided in an embodiment of the present application. DETAILED DESCRIPTION

[0077] In order to make the purpose, technical solutions and advantages of the present application clearer, the present application will be further described in detail below in conjunction with the accompanying drawings. Obviously, the described embodiments are only part of the embodiments of the present application, rather than all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present application.

[0078] The terms "first" and "second" are used for descriptive purposes only and should not be understood as indicating or implying relative importance or implicitly indicating the number of the indicated technical features. Thus, a feature defined as "first" or "second" may explicitly or implicitly include one or more of the features. In the description of this application, unless otherwise specified, "plurality" means two or more.

[0079] In the description of this application, it should be noted that, unless otherwise clearly specified and limited, the term "connection" should be understood in a broad sense, for example, it can be directly connected, or indirectly connected through an intermediate medium, or it can be the internal connection of two devices. For ordinary technicians in this field, the specific meanings of the above terms in this application can be understood according to specific circumstances.

[0080] Blockchain is a decentralized protocol. Each "chain" consists of a block structure that records the summary information of the previous block in a block header. It can store data securely, and the information cannot be forged or tampered with. It can automatically execute smart contracts without the review of any centralized organization. Transactions can be digital currencies or digital assets such as debt, equity, and copyright. Compared with traditional centralized systems, it has the advantages of decentralization and data cannot be tampered with. It has good applications in finance, quality traceability, energy and other fields, solving important problems such as trust mechanism and privacy protection.

[0081] Blockchain can be divided into public chain, consortium chain and private chain according to its participation form. Among them, consortium chain is limited to the participation of consortium members. Whether it is the read and write permissions on the blockchain or the permission to participate in bookkeeping, it is determined by the consortium rules. For example, Hyperledger, supported by the Linux (an operating system) Foundation, belongs to the consortium chain architecture. Because the consortium chain is a blockchain that requires registration permission, it can also be called a permissioned blockchain.

[0082] The consensus process of the consortium chain is controlled by pre-selected nodes. It is suitable for business-to-business (B2B) marketing relationships such as transactions, settlements or clearing between institutions. Consortium chains generally use consensus algorithms such as proof of stake, practical Byzantine fault tolerance (PBFT), and distributed consensus algorithm (RAFT). The confirmation time and number of transactions per second of the consortium chain are significantly different from those of the public chain, and the requirements for transaction security and performance are much higher than those of the public chain.

[0083] In the blockchain architecture, there are usually multiple blockchains deployed in multiple nodes. How to manage blockchains in multiple nodes (such as the deployment of new blockchains) is an urgent problem that needs to be solved.

[0084] In view of this, an embodiment of the present application proposes a blockchain management method and system to achieve the management of blockchains in multiple nodes.

[0085] See also Figure 1 As shown, a blockchain management system provided by this embodiment includes a master integrated machine, a slave integrated machine 1 and a slave integrated machine 2 ( Figure 1 Taking two slave integrated machines as an example, more or fewer slave integrated machines may be provided in implementation).

[0086] This embodiment does not specifically limit the setting method of the master integrated machine and the slave integrated machine. For example, during the initialization process of the blockchain management system, the user accesses the management architecture of one of the integrated machines to define the integrated machine as the master integrated machine and the other integrated machines as slave integrated machines.

[0087] A master integrated machine, configured to respond to a blockchain deployment instruction and determine a deployment node corresponding to the blockchain deployment instruction; if the deployment node is the master integrated machine, determine a target blockchain type and target encryption information in the blockchain deployment instruction; deploy a corresponding blockchain based on the target blockchain type and the target encryption information; otherwise, forward the blockchain deployment instruction to a corresponding slave integrated machine;

[0088] The slave machine is used to deploy the corresponding blockchain after receiving the blockchain deployment instruction sent by the master machine.

[0089] See also Figure 2 As shown, a management architecture of an all-in-one machine provided in this embodiment includes a user interface, a cluster agent, a service module ( Figure 2 Taking the service modules including monitoring module, configuration warehouse, CA module and deployment module as an example, during implementation, some of the modules can be set up, or other modules can be added, etc.) and blockchain network.

[0090] Among them, the user interface is used to display various interfaces in the management process;

[0091] The cluster agent is mainly responsible for all-in-one network configuration, node data access, cluster information synchronization, etc.

[0092] The service module is mainly responsible for blockchain deployment, monitoring, etc.;

[0093] The blockchain network includes a blockchain deployed on an all-in-one machine.

[0094] The specific functions of these modules will be described in subsequent embodiments.

[0095] The following will be combined with the accompanying drawings and specific embodiments to describe in detail the technical solution of the present application and how the technical solution of the present application solves the above technical problems. The following specific embodiments can be combined with each other, and the same or similar concepts or processes may not be repeated in some embodiments.

[0096] Figure 3 The interactive flow chart of the first blockchain management method provided in the embodiment of the present application is as follows: Figure 3 As shown, the following steps are included:

[0097] Step S301: The main integrated machine responds to the blockchain deployment instruction and determines the deployment node corresponding to the blockchain deployment instruction.

[0098] In this embodiment, in order to facilitate the deployment of blockchains in multiple integrated machines, an integrated machine cluster proxy mode is adopted, and a master integrated machine is selected; after the master integrated machine receives the blockchain deployment instruction, the blockchain deployment instruction may be for its own blockchain deployment or for the blockchain deployment of the slave integrated machine;

[0099] Based on this, the master machine needs to determine whether the deployment node corresponding to the blockchain deployment instruction is itself or the slave machine.

[0100] During implementation, if the deployment node is a master integrated machine, the master integrated machine executes steps S302A to S303A; if the deployment node is a slave integrated machine, the master integrated machine executes steps S302B to S303B.

[0101] Step S302A: The main integrated machine determines the target blockchain type and target encryption information in the blockchain deployment instruction.

[0102] During implementation, if the deployed node is a main integrated machine, the main integrated machine needs to directly deploy the blockchain.

[0103] Since blockchains vary in type and configuration, and some blockchains involve special encryption, it is necessary to determine the target blockchain type and target encryption information in the blockchain deployment instructions.

[0104] Step S303A: The main integrated machine deploys the corresponding blockchain based on the target blockchain type and the target encryption information.

[0105] During implementation, when deploying, the corresponding blockchain is deployed based on the target blockchain type and target encryption information in the blockchain deployment instruction.

[0106] Step S302B: The master integrated machine forwards the blockchain deployment instruction to the corresponding slave integrated machine.

[0107] During implementation, if the deployment node is a slave integrated machine, the master integrated machine needs to send the blockchain deployment instruction to the slave integrated machine to deploy the blockchain.

[0108] This embodiment does not specifically limit the manner in which the main integrated machine forwards the blockchain deployment instruction. For example, the main integrated machine forwards the blockchain deployment instruction through a cluster proxy.

[0109] Step S303B: After receiving the blockchain deployment instruction sent by the master integrated machine, the slave integrated machine deploys the corresponding blockchain.

[0110] In this embodiment, the method of deploying blockchain from the integrated machine is similar to that of deploying blockchain from the main machine, which will not be repeated here.

[0111] In the above scheme, the master integrated machine receives the blockchain deployment instruction and determines the corresponding deployment node; when the deployment node is itself, the corresponding blockchain is directly deployed; when the deployment node is a slave integrated machine, the blockchain deployment instruction is sent to the slave integrated machine for blockchain deployment; due to the different types of blockchains and different configurations, some blockchains also involve special encryption. Therefore, when deploying, the corresponding blockchain is deployed based on the target blockchain type and target encryption information in the blockchain deployment instruction; it not only reduces the difficulty of blockchain application deployment and improves deployment efficiency, but also completes the deployment of blockchains in multiple nodes (multiple integrated machines) through the integrated machine cluster agent mode.

[0112] In some optional implementations, before the above step S301, the main integrated machine further performs the following steps:

[0113] The deployment interface is displayed with options for blockchain type, encryption, and deploying nodes.

[0114] See above Figure 2 As shown, the all-in-one machine provides a user interface. When the user has a blockchain deployment requirement, the corresponding deployment interface can be displayed through the display screen.

[0115] Since the main integrated machine needs to make deployment node judgment, the deployment node needs to deploy the corresponding blockchain based on the target blockchain type and target encryption information;

[0116] Therefore, the blockchain deployment instructions need to provide information related to the deployment node, blockchain type, and encryption.

[0117] Based on this, in this embodiment, the main integrated machine displays a deployment interface including blockchain type options, encryption options, and deployment node options.

[0118] The above blockchain deployment instructions are triggered by selecting the blockchain type option, encryption option, and deployment node option.

[0119] The above solution facilitates guiding users to make blockchain deployment selections by displaying a deployment interface.

[0120] In some optional implementation manners, the above step S303A may be implemented by but not limited to the following methods:

[0121] Calling a target configuration template corresponding to the target blockchain type in the configuration warehouse of the main integrated machine; and generating a public-private key pair based on the target encryption information; wherein the configuration warehouse is provided with a plurality of configuration templates corresponding to the first preset blockchain type;

[0122] The corresponding blockchain is deployed based on the target configuration template, and the private key in the public-private key pair is placed in the password card of the main integrated machine.

[0123] In this embodiment, the integrated machine is provided with a configuration warehouse, and the configuration warehouse of the main integrated machine is provided with a plurality of configuration templates corresponding to the first preset blockchain type;

[0124] After determining the target blockchain type, the target configuration template corresponding to the target blockchain type can be directly called by accessing the configuration repository to meet the configuration requirements of different blockchain types.

[0125] In addition, after generating a public-private key pair based on the target encryption information, the private key in the public-private key pair needs to be saved. By setting a password card in the all-in-one machine and saving the private key separately in the password card, the security of the private key is improved.

[0126] In some optional implementations, the main integrated machine further performs the following steps:

[0127] Determining whether to perform CA authentication based on the blockchain deployment instruction;

[0128] If so, the target authentication information is generated by the CA module of the main integrated machine.

[0129] In implementation, some blockchains have CA certification requirements; based on this, this embodiment determines whether to perform CA certification according to the blockchain deployment instructions. For example, the blockchain deployment instructions carry information on whether to perform CA certification, or perform CA certification for some types of blockchains. When performing CA certification, the target authentication information is generated by the CA module.

[0130] In some optional implementation manners, the above step S303B may be implemented by but not limited to the following methods:

[0131] Calling the target configuration template corresponding to the target blockchain type in the configuration warehouse of the slave machine; and generating a public-private key pair based on the target encryption information; wherein the configuration warehouse is provided with a plurality of configuration templates corresponding to the second preset blockchain type;

[0132] The corresponding blockchain is deployed based on the target configuration template, and the private key in the public-private key pair is placed in the password card of the slave all-in-one machine.

[0133] The specific implementation method of this embodiment is similar to the above-mentioned main integrated machine deployment method, and will not be repeated here.

[0134] Configuration templates in different configuration repositories can be the same or different.

[0135] During implementation, after the blockchain is deployed, on-chain transactions can be performed.

[0136] For example, the user registers his / her on-chain identity on the blockchain network; deploys a smart contract; calls the contract and initiates a transaction. The blockchain node calls the private key in the password card to complete the process during the transaction verification phase, and then completes consensus and block generation.

[0137] In some optional implementation manners, based on any of the above embodiments, the main integrated machine further performs the following steps:

[0138] Based on the first status monitoring data, determining the operating status of each integrated machine; wherein the first status monitoring data includes the performance parameters of the master integrated machine and each slave integrated machine; and / or,

[0139] Based on the second status monitoring data, the operating status of each blockchain is determined; wherein the second status monitoring data includes request parameters of each blockchain.

[0140] In the implementation, the main integrated machine obtains the first status monitoring data of each integrated machine (the performance parameters of each integrated machine) and the second status monitoring data of the deployed blockchain (the request parameters of each blockchain). Figure 2 The monitoring module in collects the first state monitoring data and the second state monitoring data.

[0141] The main integrated machine determines the operating status of each integrated machine based on the first status monitoring data of all integrated machines. For example, based on the performance parameters and operating status of the sample integrated machine, the first monitoring model is trained, and the operating status of each integrated machine is output through the first monitoring model; or, a performance parameter range is set, and the operating status of the integrated machine within the performance parameter range is normal, and the operating status of the integrated machine outside the performance parameter range is abnormal, etc.

[0142] The main integrated machine determines the operating status of each blockchain based on the second status monitoring data of all blockchains. For example, based on the request parameters, types and operating status of the sample blockchain, the second monitoring model is trained, and the operating status of each blockchain is output through the second monitoring model; or, the request parameter range of each type of blockchain is set, and the operating status of the blockchain within the request parameter range is normal, and the operating status of the blockchain outside the request parameter range is abnormal, etc.

[0143] In addition, the main integrated machine can also obtain the specific transaction amounts of some blockchains (such as public chains) and monitor the transaction amounts.

[0144] In some optional implementations, the main integrated machine further performs the following steps:

[0145] Notify the machine and blockchain whose operation status is abnormal; and / or,

[0146] In response to the status viewing instruction, an operation status interface of the all-in-one machine and / or blockchain corresponding to the status viewing instruction is displayed.

[0147] By notifying the all-in-one machine and blockchain with abnormal operation status, users can find abnormalities in time;

[0148] By displaying the operation status interface and providing it to users for browsing, users can easily obtain operation information.

[0149] In some optional implementations, the main integrated machine further performs the following steps:

[0150] The operating status of all integrated machines and the operating status of all blockchains are sent to each slave integrated machine respectively.

[0151] Since multiple all-in-one machines are set up in this embodiment, each all-in-one machine can provide a user interface; based on this, in this embodiment, the master all-in-one machine sends the performance parameters of all all-in-one machines and the operating status of all blockchains to each slave all-in-one machine respectively, so that each slave all-in-one machine can also know the operating status of all all-in-one machines and all blockchains.

[0152] In some optional implementation manners, the slave machine further performs the following steps:

[0153] Notify the machine and blockchain whose operation status is abnormal; and / or,

[0154] In response to the status viewing instruction, an operation status interface of the all-in-one machine and / or blockchain corresponding to the status viewing instruction is displayed.

[0155] In the embodiment of the present application, the blockchain management method executed by the main integrated machine is as follows: Figure 4 As shown, the following steps are included:

[0156] Step S401: In response to a blockchain deployment instruction, determining a deployment node corresponding to the blockchain deployment instruction;

[0157] Step S402: If the deployment node is the master integrated machine, determine the target blockchain type and target encryption information in the blockchain deployment instruction; deploy the corresponding blockchain based on the target blockchain type and the target encryption information; otherwise, forward the blockchain deployment instruction to the corresponding slave integrated machine, so that the slave integrated machine deploys the corresponding blockchain based on the blockchain deployment instruction.

[0158] In some optional implementations, before responding to a blockchain deployment instruction and determining a deployment node corresponding to the blockchain deployment instruction, the method further includes:

[0159] The deployment interface is displayed with options for blockchain type, encryption, and deploying nodes.

[0160] In some optional implementations, deploying a corresponding blockchain based on the target blockchain type and the target encryption information includes:

[0161] Calling a target configuration template corresponding to the target blockchain type in the configuration warehouse of the main integrated machine; and generating a public-private key pair based on the target encryption information; wherein the configuration warehouse is provided with a plurality of configuration templates corresponding to the first preset blockchain type;

[0162] The corresponding blockchain is deployed based on the target configuration template, and the private key in the public-private key pair is placed in the password card of the main integrated machine.

[0163] In some optional implementations, deploying a corresponding blockchain based on the target blockchain type and the target encryption information further includes:

[0164] Determining whether to perform CA authentication based on the blockchain deployment instruction;

[0165] If so, the target authentication information is generated by the CA module of the main integrated machine.

[0166] Some optional implementations also include:

[0167] Based on the first status monitoring data, determining the operating status of each integrated machine; wherein the first status monitoring data includes the performance parameters of the master integrated machine and each slave integrated machine; and / or,

[0168] Based on the second status monitoring data, the operating status of each blockchain is determined; wherein the second status monitoring data includes request parameters of each blockchain.

[0169] Some optional implementations also include:

[0170] The operating status of all integrated machines and the operating status of all blockchains are sent to each slave integrated machine respectively.

[0171] In the embodiment of the present application, the blockchain management method executed by the all-in-one machine is as follows: Figure 5 As shown, the following steps are included:

[0172] Step S501: after receiving the blockchain deployment instruction sent by the master integrated machine, determining the target blockchain type and target encryption information in the blockchain deployment instruction; wherein the blockchain deployment instruction is sent by the master integrated machine after determining that the deployment node corresponding to the blockchain deployment instruction is the slave integrated machine;

[0173] Step S502: Based on the target blockchain type and the target encryption information, deploy the corresponding blockchain.

[0174] In some optional implementations, deploying a corresponding blockchain based on the target blockchain type and the target encryption information includes:

[0175] Calling the target configuration template corresponding to the target blockchain type in the configuration warehouse of the slave machine; and generating a public-private key pair based on the target encryption information; wherein the configuration warehouse is provided with a plurality of configuration templates corresponding to the second preset blockchain type;

[0176] The corresponding blockchain is deployed based on the target configuration template, and the private key in the public-private key pair is placed in the password card of the slave all-in-one machine.

[0177] Some optional implementations also include:

[0178] Receiving the performance parameters of each integrated machine and the operating status of each blockchain sent by the main integrated machine;

[0179] Among them, the operating status of each integrated machine is determined by the master integrated machine based on the first status monitoring data; the operating status of each blockchain is determined by the master integrated machine based on the second status monitoring data; the first status monitoring data includes the performance parameters of the master integrated machine and each slave integrated machine; the second status monitoring data includes the request parameters of each blockchain.

[0180] Figure 4-5 The specific implementation of the embodiment can refer to the implementation of the above-mentioned interaction method, and the repeated parts will not be repeated.

[0181] like Figure 6 As shown, based on Figure 4 The blockchain management method shown in the figure has the same inventive concept, and the embodiment of the present application provides a first blockchain management device 600, which is applied to a main all-in-one machine, and the device includes:

[0182] A node determination unit 601 is used to determine, in response to a blockchain deployment instruction, a deployment node corresponding to the blockchain deployment instruction;

[0183] The first deployment unit 602 is used to determine the target blockchain type and target encryption information in the blockchain deployment instruction if the deployment node is the master integrated machine; deploy the corresponding blockchain based on the target blockchain type and the target encryption information; otherwise, forward the blockchain deployment instruction to the corresponding slave integrated machine, so that the slave integrated machine deploys the corresponding blockchain based on the blockchain deployment instruction.

[0184] Some optional implementations further include a display unit 603, which is used to display a deployment interface including a blockchain type option, an encryption option, and a deployment node option before the node determination unit 601 responds to the blockchain deployment instruction and determines the deployment node corresponding to the blockchain deployment instruction.

[0185] In some optional implementation manners, the first deployment unit 602 is specifically configured to:

[0186] Calling a target configuration template corresponding to the target blockchain type in the configuration warehouse of the main integrated machine; and generating a public-private key pair based on the target encryption information; wherein the configuration warehouse is provided with a plurality of configuration templates corresponding to the first preset blockchain type;

[0187] The corresponding blockchain is deployed based on the target configuration template, and the private key in the public-private key pair is placed in the password card of the main integrated machine.

[0188] In some optional implementation manners, the first deployment unit 602 is specifically configured to:

[0189] Determining whether to perform CA authentication based on the blockchain deployment instruction;

[0190] If so, the target authentication information is generated by the CA module of the main integrated machine.

[0191] Some optional implementations further include a first monitoring unit 604, configured to:

[0192] Based on the first status monitoring data, determining the operating status of each integrated machine; wherein the first status monitoring data includes the performance parameters of the master integrated machine and each slave integrated machine; and / or,

[0193] Based on the second status monitoring data, the operating status of each blockchain is determined; wherein the second status monitoring data includes request parameters of each blockchain.

[0194] In some optional implementation manners, the first monitoring module 604 is further configured to:

[0195] The operating status of all integrated machines and the operating status of all blockchains are sent to each slave integrated machine respectively.

[0196] like Figure 7 As shown, based on Figure 5 The blockchain management method shown in the figure has the same inventive concept, and the embodiment of the present application provides a second blockchain management device 700, which is applied to an all-in-one machine, and the device includes:

[0197] The second deployment unit 701 is used to determine the target blockchain type and target encryption information in the blockchain deployment instruction after receiving the blockchain deployment instruction sent by the master integrated machine; wherein the blockchain deployment instruction is sent by the master integrated machine after determining that the deployment node corresponding to the blockchain deployment instruction is the slave integrated machine;

[0198] The second deployment unit 701 is also used to deploy the corresponding blockchain based on the target blockchain type and the target encryption information.

[0199] In some optional implementation manners, the second deployment unit 701 is specifically configured to:

[0200] Calling the target configuration template corresponding to the target blockchain type in the configuration warehouse of the slave machine; and generating a public-private key pair based on the target encryption information; wherein the configuration warehouse is provided with a plurality of configuration templates corresponding to the second preset blockchain type;

[0201] The corresponding blockchain is deployed based on the target configuration template, and the private key in the public-private key pair is placed in the password card of the slave all-in-one machine.

[0202] In some optional implementation manners, the second deployment unit 701 is specifically configured to:

[0203] Determining whether to perform CA authentication based on the blockchain deployment instruction;

[0204] If so, the target authentication information is generated by the CA module of the slave machine.

[0205] Some optional implementations further include a second monitoring unit 702, configured to:

[0206] Receiving the performance parameters of each integrated machine and the operating status of each blockchain sent by the main integrated machine;

[0207] Among them, the operating status of each integrated machine is determined by the master integrated machine based on the first status monitoring data; the operating status of each blockchain is determined by the master integrated machine based on the second status monitoring data; the first status monitoring data includes the performance parameters of the master integrated machine and each slave integrated machine; the second status monitoring data includes the request parameters of each blockchain.

[0208] Figure 6-7 The specific implementation of the embodiment can refer to the implementation of the above-mentioned interaction method, and the repeated parts will not be repeated.

[0209] Based on the same technical concept, the embodiment of the present application also provides a main integrated machine 800, such as Figure 8 As shown, it includes at least one processor 801 and a memory 802 connected to the at least one processor. The specific connection medium between the processor 801 and the memory 802 is not limited in the embodiment of the present application. Figure 8 For example, the processor 801 and the memory 802 are connected via a bus 803. The bus can be divided into a path bus, a data bus, a control bus, etc. For convenience of representation, Figure 8 Only one thick line is used in the diagram, but this does not mean that there is only one bus or only one type of bus.

[0210] See also Figure 8 As shown, in some optional implementations, the main integrated machine 800 is also provided with a password card 804.

[0211] Among them, the processor 801 is the control center of the main integrated machine, and can use various interfaces and lines to connect various parts of the main integrated machine, and realize data processing by running or executing instructions stored in the memory 802 and calling data stored in the memory 802. Optionally, the processor 801 may include one or more processing units, and the processor 801 may integrate an application processor and a modem processor, wherein the application processor mainly processes the operating system, user interface, and application program, etc., and the modem processor mainly processes the issuance of instructions. It is understandable that the above-mentioned modem processor may not be integrated into the processor 801. In some embodiments, the processor 801 and the memory 802 may be implemented on the same chip, and in some embodiments, they may also be implemented separately on independent chips.

[0212] Processor 801 can be a general-purpose processor, such as a central processing unit (CPU), a digital signal processor, an application-specific integrated circuit (ASIC), a field programmable gate array or other programmable logic device, a discrete gate or transistor logic device, a discrete hardware component, and can implement or execute the methods, steps and logic block diagrams disclosed in the embodiments of this application. A general-purpose processor can be a microprocessor or any conventional processor. The steps of the method disclosed in the embodiment of the blockchain management method can be directly embodied as a hardware processor, or can be executed by a combination of hardware and software modules in the processor.

[0213] The memory 802 is a non-volatile computer-readable storage medium that can be used to store non-volatile software programs, non-volatile computer executable programs and modules. The memory 802 may include at least one type of storage medium, such as a flash memory, a hard disk, a multimedia card, a card-type memory, a random access memory (Random Access Memory, RAM), a static random access memory (Static Random Access Memory, SRAM), a programmable read-only memory (Programmable Read Only Memory, PROM), a read-only memory (Read Only Memory, ROM), an electrically erasable programmable read-only memory (Electrically Erasable Programmable Read-Only Memory, EEPROM), a magnetic memory, a disk, an optical disk, etc. The memory 802 is any other medium that can be used to carry or store a desired program code in the form of an instruction or data structure and can be accessed by a computer, but is not limited thereto. The memory 802 in the embodiment of the present application can also be a circuit or any other device that can realize a storage function, for storing program instructions and / or data.

[0214] In the embodiment of the present application, the memory 802 stores a computer program. When the program is executed by the processor 801, the processor 801 executes:

[0215] In response to a blockchain deployment instruction, determining a deployment node corresponding to the blockchain deployment instruction;

[0216] If the deployment node is the master integrated machine, determining the target blockchain type and target encryption information in the blockchain deployment instruction; and deploying the corresponding blockchain based on the target blockchain type and the target encryption information;

[0217] Otherwise, the blockchain deployment instruction is forwarded to the corresponding slave integrated machine, so that the slave integrated machine deploys the corresponding blockchain based on the blockchain deployment instruction.

[0218] In some optional implementations, before responding to the blockchain deployment instruction and determining the deployment node corresponding to the blockchain deployment instruction, the processor 801 further executes:

[0219] The deployment interface is displayed with options for blockchain type, encryption, and deploying nodes.

[0220] In some optional implementation manners, the processor 801 specifically performs:

[0221] Calling a target configuration template corresponding to the target blockchain type in the configuration warehouse of the main integrated machine; and generating a public-private key pair based on the target encryption information; wherein the configuration warehouse is provided with a plurality of configuration templates corresponding to the first preset blockchain type;

[0222] The corresponding blockchain is deployed based on the target configuration template, and the private key in the public-private key pair is placed in the password card 804 of the main integrated machine.

[0223] In some optional implementations, the processor 801 further executes:

[0224] Determining whether to perform CA authentication based on the blockchain deployment instruction;

[0225] If so, the target authentication information is generated by the CA module of the main integrated machine.

[0226] In some optional implementations, the processor 801 further executes:

[0227] Based on the first status monitoring data, determining the operating status of each integrated machine; wherein the first status monitoring data includes the performance parameters of the master integrated machine and each slave integrated machine; and / or,

[0228] Based on the second status monitoring data, the operating status of each blockchain is determined; wherein the second status monitoring data includes request parameters of each blockchain.

[0229] In some optional implementations, the processor 801 further executes:

[0230] The operating status of all integrated machines and the operating status of all blockchains are sent to each slave integrated machine respectively.

[0231] Based on the same technical concept, an embodiment of the present application further provides a slave all-in-one machine, comprising at least one processor and at least one memory, wherein the memory stores a computer program, and when the program is executed by the processor, the processor executes:

[0232] After receiving the blockchain deployment instruction sent by the master integrated machine, determine the target blockchain type and target encryption information in the blockchain deployment instruction; wherein the blockchain deployment instruction is sent by the master integrated machine after determining that the deployment node corresponding to the blockchain deployment instruction is the slave integrated machine;

[0233] Based on the target blockchain type and the target encryption information, deploy the corresponding blockchain.

[0234] In some optional implementations, the processor specifically performs:

[0235] Calling the target configuration template corresponding to the target blockchain type in the configuration warehouse of the slave machine; and generating a public-private key pair based on the target encryption information; wherein the configuration warehouse is provided with a plurality of configuration templates corresponding to the second preset blockchain type;

[0236] The corresponding blockchain is deployed based on the target configuration template, and the private key in the public-private key pair is placed in the password card of the slave all-in-one machine.

[0237] In some optional implementations, the processor further executes:

[0238] Receiving the performance parameters of each integrated machine and the operating status of each blockchain sent by the main integrated machine;

[0239] Among them, the operating status of each integrated machine is determined by the master integrated machine based on the first status monitoring data; the operating status of each blockchain is determined by the master integrated machine based on the second status monitoring data; the first status monitoring data includes the performance parameters of the master integrated machine and each slave integrated machine; the second status monitoring data includes the request parameters of each blockchain.

[0240] Based on the same technical concept, an embodiment of the present application also provides a computer-readable storage medium, which stores a computer program executable by a processor. When the program runs on the processor, the processor executes the steps of the above-mentioned blockchain management method.

[0241] Those skilled in the art will appreciate that the embodiments of the present application may be provided as methods, systems, or computer program products. Therefore, the present application may adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment in combination with software and hardware. Moreover, the present application may adopt the form of a computer program product implemented in one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) that include computer-usable program code.

[0242] The present application is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the present application. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of the processes and / or boxes in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0243] These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture comprising an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.

[0244] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for implementing the process in the computer or other programmable device. Figure 1 A process or multiple processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes.

[0245] Although the preferred embodiments of the present application have been described, those skilled in the art may make other changes and modifications to these embodiments once they have learned the basic creative concept. Therefore, the appended claims are intended to be interpreted as including the preferred embodiments and all changes and modifications falling within the scope of the present application.

[0246] Obviously, those skilled in the art can make various changes and modifications to the present application without departing from the spirit and scope of the present application. Thus, if these modifications and variations of the present application fall within the scope of the claims of the present application and their equivalents, the present application is also intended to include these modifications and variations.

Claims

1. A blockchain management method, characterized in that: The method is applied to a main integrated machine in a blockchain management system, and includes: In response to a blockchain deployment instruction, determining a deployment node corresponding to the blockchain deployment instruction; If the deployment node is the main integrated machine, determining the target blockchain type and target encryption information in the blockchain deployment instruction; and deploying the corresponding blockchain based on the target blockchain type and the target encryption information; Otherwise, the blockchain deployment instruction is forwarded to the corresponding slave integrated machine, so that the slave integrated machine deploys the corresponding blockchain based on the blockchain deployment instruction.

2. The method according to claim 1, characterized in that Before responding to the blockchain deployment instruction and determining the deployment node corresponding to the blockchain deployment instruction, the method further includes: The deployment interface is displayed with options for blockchain type, encryption, and deploying nodes.

3. The method according to claim 1, characterized in that Based on the target blockchain type and the target encryption information, deploying a corresponding blockchain includes: Calling a target configuration template corresponding to the target blockchain type in the configuration warehouse of the main integrated machine; and generating a public-private key pair based on the target encryption information; wherein the configuration warehouse is provided with a plurality of configuration templates corresponding to the first preset blockchain type; The corresponding blockchain is deployed based on the target configuration template, and the private key in the public-private key pair is placed in the password card of the main integrated machine.

4. The method according to claim 3, characterized in that Based on the target blockchain type and the target encryption information, deploying a corresponding blockchain also includes: Determining whether to perform CA authentication based on the blockchain deployment instruction; If so, the target authentication information is generated by the CA module of the main integrated machine.

5. The method according to claim 1, characterized in that Also includes: Based on the first status monitoring data, determining the operating status of each integrated machine; wherein the first status monitoring data includes the performance parameters of the master integrated machine and each slave integrated machine; and / or, Based on the second status monitoring data, the operating status of each blockchain is determined; wherein the second status monitoring data includes request parameters of each blockchain.

6. The method according to claim 5, characterized in that Also includes: The operating status of all integrated machines and the operating status of all blockchains are sent to each slave integrated machine respectively.

7. A blockchain management method, characterized in that: The method is applied to a slave integrated machine in a blockchain management system, and includes: After receiving the blockchain deployment instruction sent by the master integrated machine, determine the target blockchain type and target encryption information in the blockchain deployment instruction; wherein the blockchain deployment instruction is sent by the master integrated machine after determining that the deployment node corresponding to the blockchain deployment instruction is the slave integrated machine; Based on the target blockchain type and the target encryption information, deploy the corresponding blockchain.

8. The method according to claim 7, characterized in that Based on the target blockchain type and the target encryption information, deploying a corresponding blockchain includes: Calling the target configuration template corresponding to the target blockchain type in the configuration warehouse of the slave machine; and generating a public-private key pair based on the target encryption information; wherein the configuration warehouse is provided with a plurality of configuration templates corresponding to the second preset blockchain type; The corresponding blockchain is deployed based on the target configuration template, and the private key in the public-private key pair is placed in the password card of the slave all-in-one machine.

9. The method according to claim 7, characterized in that Also includes: Receiving the performance parameters of each integrated machine and the operating status of each blockchain sent by the main integrated machine; Among them, the operating status of each integrated machine is determined by the master integrated machine based on the first status monitoring data; the operating status of each blockchain is determined by the master integrated machine based on the second status monitoring data; the first status monitoring data includes the performance parameters of the master integrated machine and each slave integrated machine; the second status monitoring data includes the request parameters of each blockchain.

10. A blockchain management system, characterized in that: The system includes a master integrated machine and at least one slave integrated machine; wherein: A master integrated machine, configured to respond to a blockchain deployment instruction and determine a deployment node corresponding to the blockchain deployment instruction; if the deployment node is the master integrated machine, determine a target blockchain type and target encryption information in the blockchain deployment instruction; deploy a corresponding blockchain based on the target blockchain type and the target encryption information; otherwise, forward the blockchain deployment instruction to a corresponding slave integrated machine; The slave machine is used to deploy the corresponding blockchain after receiving the blockchain deployment instruction sent by the master machine.

Images