Multi-chain service management method and device, electronic equipment and storage medium

Abstract

The invention discloses a multi-chain service management method and device, electronic equipment and a storage medium. The method comprises the following steps: acquiring a service request for an external chain; if the service request is a service request for node consensus, acquiring description information of an external chain, and based on the description information of the external chain, establishing a target node corresponding to the description information of the external chain on a multi-chain management platform, and performing P2P connection with the external chain to manage the external chain; if the service request is a service request for driving plug-in access, acquiring first configuration information of an external chain, and based on the first configuration information, performing communication connection with the external chain through a first SDK generated and configured on a multi-chain management platform to manage the external chain; and if the service request is the service request of the node preposition service, generating a preposition service driving plug-in, and performing communication connection with the external chain based on the preposition service driving plug-in deployed in the external chain to manage the external chain.

Description

Technical Field

[0001] The present application belongs to the field of computer information management technology, and specifically relates to a multi-chain business management method, device, electronic device and storage medium. Background Art

[0002] In recent years, blockchain technology, as a distributed ledger technology, has been widely used in finance, supply chain, Internet of Things, copyright protection and other fields due to its decentralization, transparency and immutability. With the deepening of blockchain applications and the expansion of business scale, the coexistence of multiple chains has become the norm. Enterprises use the Blockchain-as-a-Service (BaaS) platform to simplify the deployment, management and operation of blockchain nodes.

[0003] However, although the BaaS platform greatly simplifies the operation and maintenance of internal hosting nodes, the BaaS platform mainly focuses on the operation and maintenance management of internal hosting nodes. Therefore, the management of external blockchains that are not directly started and maintained by the platform is isolated from the management of blockchains within the platform, resulting in the following problems:

[0004] Since the operation and maintenance management of external nodes and nodes within the platform are independent of each other, the operation and maintenance is complex and inefficient. Since the platform lacks real-time monitoring and early warning capabilities for key indicators such as the status, performance, and security of external nodes, it is difficult for enterprises to promptly discover and handle potential failures, affecting business continuity. In application scenarios involving cross-chain interactions, the interoperability between external nodes and nodes within the platform is limited, which increases the difficulty of implementing cross-chain transactions and hinders the interconnection of blockchain networks. External nodes may follow different security standards and compliance requirements, making it difficult for enterprises to conduct comprehensive risk assessments and compliance audits, increasing the difficulty of supervision.

[0005] In order to solve the above problems, it is necessary to uniformly manage the external blockchain (i.e., external chain) and the blockchain within the platform. However, there are limitations in the management of external chains in related technologies. For example, in some scenarios, the required external chain node information may not be obtained, and the external chain cannot be managed. As a result, it is impossible to uniformly manage and operate the external chain and the blockchain within the platform, and the above problems will still exist. Summary of the invention

[0006] The embodiments of the present application provide a multi-chain business management method, device, electronic device and storage medium, which can solve the problem of limitations in the management of external links in related technologies.

[0007] In a first aspect, an embodiment of the present application provides a multi-chain business management method, which is applied to a multi-chain management platform, and the method includes: obtaining a business request for an external chain, the business request including one or more of the following: a business request for node consensus, a business request for driver plug-in access, and a business request for node front-end service; if the business request is the business request for node consensus, obtaining description information of the external chain, and based on the description information of the external chain, establishing a target node corresponding to the description information of the external chain on the multi-chain management platform, and establishing a P2P connection with the external chain to manage the external chain, wherein the management includes participating in the consensus of the external chain; if the business request is the business request for driver plug-in access, obtaining first configuration information of the external chain, and based on the first configuration information, generating and configuring a first software development kit (SDK) on the multi-chain management platform; Kit, SDK), communicates with the external link and manages the external link; if the business request is a business request for the node front-end service, a front-end service driver plug-in is generated, and based on the front-end service driver plug-in deployed on the external link, a communication connection is established with the external link to manage the external link.

[0008] In a second aspect, an embodiment of the present application provides a multi-chain business management device, which is applied to a multi-chain management platform, and the device includes: an acquisition module, which is used to obtain a business request for an external chain, and the request includes one or more of the following: a business request for node consensus, a business request for driver plug-in access, and a business request for node front-end service; a first connection module, which is used to obtain the description information of the external chain if the business request is the business request for node consensus, and based on the description information of the external chain, establish a target node corresponding to the description information of the external chain on the multi-chain management platform, and establish a P2P connection with the external chain to control the external chain. Management includes participating in the consensus of the external chain; a second connection module is used to obtain the first configuration information of the external chain if the business request is a business request accessed by the driver plug-in, and based on the first configuration information, communicate with the external chain through the first software development kit SDK generated and configured on the multi-chain management platform to manage the external chain; a third connection module is used to generate a front-end service driver plug-in if the business request is a business request for the node front-end service, and communicate with the external chain based on the front-end service driver plug-in deployed on the external chain to manage the external chain.

[0009] In a third aspect, an embodiment of the present application provides an electronic device, comprising: a processor; and a memory arranged to store computer executable instructions, wherein the executable instructions are configured to be executed by the processor, and the executable instructions include instructions for executing the multi-chain business management method as described in the first aspect.

[0010] In a fourth aspect, an embodiment of the present application provides a storage medium, which is used to store computer-executable instructions, and the computer-executable instructions enable a computer to execute the multi-chain business management method as described in the first aspect.

[0011] In a fifth aspect, an embodiment of the present application provides a chip, comprising a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement the multi-chain business management method as described in the first aspect.

[0012] In a sixth aspect, an embodiment of the present application provides a computer program product, including a computer program, which, when executed by a processor, implements the multi-chain business management method as described in the first aspect.

[0013] In an embodiment of the present application, by obtaining a business request for an external chain, the business request includes one or more of the following: a business request for node consensus, a business request for driver plug-in access, and a business request for node front-end service; thereafter, if the business request is a business request for node consensus, the description information of the external chain is obtained, and based on the description information of the external chain, a target node corresponding to the description information of the external chain is established on a multi-chain management platform, a P2P connection is made with the external chain, and the external chain is managed to participate in the consensus of the external chain; if the business request is a business request for driver plug-in access, the first configuration information of the external chain is obtained, and based on the first configuration information, a first software development kit SDK generated and configured on the multi-chain management platform is used to communicate with the external chain and manage the external chain; if the business request is a business request for node front-end service, a front-end service driver plug-in is generated, and based on the front-end service driver plug-in deployed on the external chain, a communication connection is made with the external chain to manage the external chain. This solution designs a multi-chain management platform with comprehensive applicable scenarios. The multi-chain management platform can process business requests corresponding to the management needs of external chains in various scenarios, thereby managing various external chains, solving the problem of limitations in the management of external chains in related technologies; on this basis, this solution enables enterprises to uniformly deploy smart contracts for external chains on the multi-chain management platform, greatly simplifying cross-chain and cross-organizational contract management. Compared with traditional decentralized and complex deployment methods, this unified deployment mechanism greatly reduces the operating steps, saves time and reduces labor costs. At the same time, it ensures the standardization and consistency of contract deployment, which is conducive to enterprises to quickly respond to market demands and flexibly adjust smart contract strategies. BRIEF DESCRIPTION OF THE DRAWINGS

[0014] Figure 1 It is a flowchart of a multi-chain business management method provided in an embodiment of the present application;

[0015] Figure 2 It is a flowchart of another multi-chain service management method provided in an embodiment of the present application;

[0016] Figure 3 It is a structural diagram of a multi-chain service management device provided in an embodiment of the present application;

[0017] Figure 4 It is a structural schematic diagram of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0018] The following will be combined with the drawings in the embodiments of the present application to clearly and completely describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, not 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 this application.

[0019] The terms "first", "second", etc. in the specification and claims of the present application are used to distinguish similar objects, and are not used to describe a specific order or sequence. It should be understood that the data used in this way can be interchangeable under appropriate circumstances, so that the embodiments of the present application can be implemented in an order other than those illustrated or described here, and the objects distinguished by "first", "second", etc. are generally of one type, and the number of objects is not limited. For example, the first object can be one or more. In addition, "and / or" in the specification and claims represents at least one of the connected objects, and the character " / " generally indicates that the objects associated with each other are in an "or" relationship.

[0020] The following, in conjunction with the accompanying drawings, describes in detail the multi-chain service management method, device, electronic device and storage medium provided in the embodiments of the present application through specific embodiments and their application scenarios.

[0021] Figure 1 A multi-chain business management method provided by an embodiment of the present invention is shown. The method can be applied to a multi-chain management platform and executed by an electronic device where the multi-chain management platform is located, or an electronic device where the multi-chain management platform is located and an electronic device related to the electronic device where the multi-chain management platform is located. The electronic device may include: a server and / or a terminal device, wherein the terminal device may be, for example, a mobile phone terminal. In other words, the method may be executed by software or hardware installed in an electronic device, and the method includes the following steps:

[0022] S102: Obtaining a business request for an external chain, where the business request includes one or more of the following: a business request for node consensus, a business request for driver plug-in access, and a business request for node front-end service.

[0023] An external chain can be a blockchain deployed by the enterprise itself or provided by a third party that is not included in the management system of the multi-chain management platform.

[0024] In order to achieve unified management and operation of external chains and blockchains within the platform, this solution has designed a multi-chain management platform with comprehensive applicable scenarios. The multi-chain management platform can support the management needs of enterprises for external chains in various scenarios, such as the head office's need to conduct in-depth management of nodes in the branch's external chain and participate in the consensus of the branch's external chain; the need to manage the external chain when the enterprise cannot obtain the configuration information of the external chain to be managed, etc. In other words, the multi-chain management platform can process business requests corresponding to the management needs of external chains in various scenarios.

[0025] Specifically, the business request for node consensus is used to indicate the management of the external chain so that it can participate in the consensus of the external chain; the business request for driver plug-in access is used to indicate the management of the external chain when the configuration information of the external chain to be managed cannot be obtained; the business request identifier of the node front-end service is used to indicate the management of the external chain when the configuration information of the external chain to be managed is obtained.

[0026] In actual applications, the external chain party can remotely send a business request for the external chain to the multi-chain management platform, or the management party can operate on the multi-chain management platform. Correspondingly, the multi-chain management platform obtains the business request for the external chain.

[0027] S104: If the business request is a business request for node consensus, obtain the description information of the external chain, and based on the description information of the external chain, establish a target node corresponding to the description information of the external chain on the multi-chain management platform, and establish a P2P connection with the external chain to manage the external chain, including participating in the consensus of the external chain.

[0028] Specifically, the description information of the external chain may include genesis block information, certificate information, organization information and node information. According to the characteristics of the external chain corresponding to the business request, the description information of the external chain may also include information such as channel configuration files and group configuration files. Among them, the genesis block information may be the unique ID number of the genesis block. The genesis block is the earliest constructed block among multiple blocks of the blockchain and has a unique ID number; the certificate information may include one or more of the certificate information such as the organization certificate, user certificate, Transport Layer Security (TLS) certificate, node certificate, etc.; the node information may include one or more of the node type and quantity, external chain ID, name information of the organization to which it belongs, communication address and port information.

[0029] Specifically, the target nodes to be established may include consensus nodes and accounting nodes. Consensus nodes are nodes that participate in the consensus process (mechanism), such as Orderers. The consensus mechanism is to complete the verification and confirmation of transactions in a short time through the voting of consensus nodes. Accounting nodes are network nodes used to maintain the ledger, such as Peers.

[0030] P2P connection, peer-to-peer (P2P) connection means that when two hosts communicate, they do not distinguish which one is the service requester or the service provider.

[0031] If the business request is for node consensus, the management of the external chain includes: participating in the consensus of the external chain, adding or deleting nodes or organizations; contract management, including contract deployment, upgrade and freezing; access to external chain data. Specifically, the deployment of the contract can include the organization administrator creating a contract on the multi-chain management platform and uploading the source code file of the contract. After that, the contract can be deployed on its internal and external chains through the multi-chain management platform at the same time.

[0032] S106: If the business request is a business request for driver plug-in access, first configuration information of the external chain is obtained, and based on the first configuration information, a communication connection is established with the external chain through a first SDK generated and configured on the multi-chain management platform to manage the external chain.

[0033] Specifically, the first configuration information may include the above-mentioned certificate information and node information.

[0034] If the business request is a business request for driver plug-in access, the management of the external chain includes: contract management, including contract deployment, upgrade and freezing; access to external chain data.

[0035] S108: If the service request is a service request for a node front-end service, a front-end service driver plug-in is generated, and based on the front-end service driver plug-in deployed in the external chain, a communication connection is established with the external chain to manage the external chain.

[0036] If the business request is a business request for node front-end services, the management of the external chain includes: contract management, including contract deployment, upgrade and freezing; access to external chain data.

[0037] In addition, an integrated operation and maintenance view and a centralized control platform can be designed for use with the above solution, allowing enterprises to perform resource allocation, troubleshooting, performance optimization and other tasks in an efficient and intuitive manner, thereby reducing operation and maintenance complexity and response time and improving overall operation and maintenance efficiency; it is also possible to uniformly monitor the nodes of the external chain, so that enterprises can grasp the node status, performance and security in real time, so as to promptly discover potential problems and respond quickly to abnormal situations, effectively reducing the probability of business interruptions due to node failures, and significantly enhancing the stability and reliability of the blockchain network. At the same time, through centralized analysis of node data, it can provide more accurate risk warnings, helping enterprises to prevent risks in advance and improve business continuity.

[0038] The multi-chain business management method provided by the embodiment of the present invention obtains a business request for an external chain, and the business request includes one or more of the following: a business request for node consensus, a business request for driver plug-in access, and a business request for node front-end service; then, if the business request is a business request for node consensus, the description information of the external chain is obtained, and based on the description information of the external chain, a target node corresponding to the description information of the external chain is established on a multi-chain management platform, a P2P connection is made with the external chain, and the external chain is managed to participate in the consensus of the external chain; if the business request is a business request for driver plug-in access, the first configuration information of the external chain is obtained, and based on the first configuration information, a first software development kit SDK generated and configured on the multi-chain management platform is used to communicate and connect with the external chain to manage the external chain; if the business request is a business request for node front-end service, a front-end service driver plug-in is generated, and based on the front-end service driver plug-in deployed on the external chain, a communication connection is made with the external chain to manage the external chain. This solution designs a multi-chain management platform with comprehensive applicable scenarios. The multi-chain management platform can process business requests corresponding to the management needs of external chains in various scenarios, thereby managing various external chains, solving the problem of limitations in the management of external chains in related technologies; on this basis, this solution enables enterprises to uniformly deploy smart contracts for external chains on the multi-chain management platform, greatly simplifying cross-chain and cross-organizational contract management. Compared with traditional decentralized and complex deployment methods, this unified deployment mechanism greatly reduces the operating steps, saves time and reduces labor costs. At the same time, it ensures the standardization and consistency of contract deployment, which is conducive to enterprises to quickly respond to market demands and flexibly adjust smart contract strategies.

[0039] In one implementation, if the service request is a service request for node consensus, the description information of the external chain is obtained, and based on the description information of the external chain, a target node corresponding to the description information of the external chain is established on the multi-chain management platform, and a P2P connection is made with the external chain (i.e., S104), which can be specifically performed as follows: Steps A1 to A4:

[0040] Step A1, in response to a business request for node consensus, obtain description information of the external chain.

[0041] Among them, the description information of the external chain includes genesis block information, organization information, node information and certificate information.

[0042] Step A2: based on the description information of the external chain, establishing an organization and a target node corresponding to the description information of the external chain on the multi-chain management platform, and generating a first configuration file of the organization and the target node.

[0043] Specifically, the first configuration file is a configuration file of both the organization and the target node. The generated first configuration files of the organization and the target node may include certificate information.

[0044] Step A3: determining third configuration information based on the acquired second configuration information of the external link and the first configuration file, and sending the third configuration information to the external link.

[0045] Specifically, the third configuration information includes the second configuration information of the external link and data corresponding to the first configuration file.

[0046] Step A4: based on the first configuration file, start the target node, and establish a P2P connection between the target node and the external link configured with the third configuration information.

[0047] Specifically, according to the first configuration file, the environment variables can be configured, such as configuring the correct TLS certificate path environment variables, and then the target node can be started: the consensus node and the accounting node can be started respectively; after that, the network of the external chain can be joined after the target node is started. Specifically, the way to join the external chain network can be selected according to different blockchain types. For example, if the external chain is a blockchain Fabric, which is an open source distributed ledger platform based on the hyperledger technology, the accounting node needs to be added to the external chain channel. If it is an enterprise-level public chain Fisco Bcos based on the hyperledger technology, the accounting node needs to be added to the group to which the external chain belongs.

[0048] After step A4, the communication status between the blockchain of the multi-chain management platform and the external chain can be observed on the visualization interface set by the multi-chain management platform. For example, the communication status can be identified by setting a communication status display component or a communication status message reminder. Specifically, the communication status between the blockchain of the multi-chain management platform and the external chain can be determined by monitoring whether the data of the blockchain of the multi-chain management platform and the external chain are synchronized and whether the blockchain of the multi-chain management platform participates in the consensus of the external chain.

[0049] In this embodiment, through the above solution, the multi-chain management platform can process business requests corresponding to management needs such as the head office wanting to perform in-depth management of nodes in the branch's external chain, participate in the consensus of the branch's external chain, etc.

[0050] In one implementation, if the service request is a service request for a node front-end service, a front-end service driver plug-in is generated, and based on the front-end service driver plug-in deployed in the external chain, a communication connection is established with the external chain to manage the external chain (i.e., S108), which can be specifically performed as follows: Steps B1 to B3:

[0051] Step B1: In response to a service request of a node front-end service, generate a front-end service driver plug-in and a second configuration file of the front-end service driver plug-in.

[0052] Among them, the front-end service driver plug-in encapsulates the configuration information of the second SDK and the multi-chain management platform.

[0053] Specifically, the configuration information of the multi-chain management platform may include the address and port of the multi-chain management platform. The second SDK is used to manage the nodes of the external chain on an agent basis.

[0054] Step B2: when the third configuration information of the external link is configured in the second configuration file and the front-end service driver plug-in is deployed in the external link, the fourth configuration information of the front-end service driver plug-in is obtained.

[0055] Specifically, the second configuration file can be configured by the node administrator of the external link according to the third configuration information of the external link. The third configuration information can be the configuration information of the node, and the configuration information of the node includes data such as the node certificate, the organization to which the node belongs, the node Internet Protocol (IP) address and port. Afterwards, the corresponding second configuration file can be deployed to the internal network of the external link with the front-end service driver plug-in configured with the third configuration information.

[0056] Specifically, after the front-end service driver plug-in is successfully deployed, the fourth configuration information of the front-end service driver plug-in can be sent to the multi-chain management platform, and the multi-chain management platform receives the fourth configuration information. The fourth configuration information may include the organization to which the front-end service driver plug-in is deployed and the third configuration information.

[0057] Step B3: Based on the fourth configuration information, the external chain is managed through the first external chain management component created on the multi-chain management platform and the front-end service driver plug-in that communicates with the external chain.

[0058] The first external link management component is used to control the front-end service driver plug-in based on the fourth configuration information to manage the external link. Optionally, the first external link management component can be created before obtaining the fourth configuration information of the front-end service driver plug-in, or can be created in response to the fourth configuration information of the front-end service driver plug-in obtained.

[0059] Since the network policy of the external chain, such as the network configuration policy and the network access control policy, may not allow the public network to access the internal network of the external chain, it is also possible to first enable the network policy of the external chain and register all external organizations and node information on the multi-chain management platform to ensure that the internal network of the external chain can be accessed by the multi-chain management platform, and then manage the external chain through the first external chain management component and the front-end service driver plug-in that communicates with the external chain.

[0060] In this embodiment, through the above solution, the multi-chain management platform can process business requests corresponding to management needs when the enterprise cannot obtain configuration information of the external chain to be managed.

[0061] In one implementation, if the service request is a service request for access by a driver plug-in, the first configuration information of the external chain is obtained, and based on the first configuration information, a communication connection is established with the external chain through a first software development kit SDK generated and configured on the multi-chain management platform to manage the external chain (i.e., S106), which can be specifically performed as follows: Steps C1 to C3:

[0062] Step C1, in response to a service request for access by a driver plug-in, obtaining first configuration information of an external link, and generating a first SDK based on the first configuration information.

[0063] Step C2, based on the first configuration information, configure the first SDK, and establish a communication connection between the configured first SDK on the multi-chain management platform and the external chain.

[0064] Step C3: manage the external chain based on the communication connection between the configured first SDK on the multi-chain management platform and the external chain.

[0065] Specifically, based on the communication connection, the first SDK can be used to call the data query interface of the node of the external chain to query data, access the blockchain browser of the multi-chain management platform, and manage the data of the external chain.

[0066] In this embodiment, through the above solution, the multi-chain management platform can process business requests corresponding to management needs when the enterprise can obtain configuration information of the external chain to be managed.

[0067] In one implementation, in response to a service request for access by a driver plug-in, first configuration information of an external link is obtained, and based on the first configuration information, a first SDK is generated (i.e., step C1), which can be specifically performed as follows: step c1 to step c2:

[0068] Step c1: creating a second external link management component in response to a service request for access by the driver plug-in.

[0069] Step c2: acquiring first configuration information of the external link through the second external link management component, and generating a first SDK based on the first configuration information through a driver plug-in generation tool in the second external link management component.

[0070] In this embodiment, the first configuration information of the external link is acquired through the second external link management component, and the driver plug-in generation tool in the second external link management component quickly generates the first SDK.

[0071] In one implementation, based on the acquired second configuration information of the external link and the first configuration file, the third configuration information is determined, and the third configuration information is sent to the external link (i.e., step A3), which can be specifically performed as follows: steps a1 to a3:

[0072] Step a1, obtaining the second configuration information of the external link, and decoding the second configuration information to obtain the fourth configuration information.

[0073] Step a2: merge and encode the first configuration file and the fourth configuration information to obtain the third configuration information.

[0074] Step a3: submit the third configuration information as a configuration update transaction to the node of the external chain.

[0075] Specifically, the third configuration information is formatted into a format corresponding to the second configuration information of the external chain to obtain a corresponding file, and then the corresponding file is signed. Thereafter, the signed corresponding file is submitted to the node of the external chain as a transaction.

[0076] In one implementation, based on the description information of the external chain, after establishing a target node corresponding to the description information of the external chain on the multi-chain management platform and establishing a P2P connection with the external chain (i.e., S104), the following steps D1 to D3 may be performed to manage the external chain:

[0077] Step D1, obtaining a request for adding a new node for an external chain.

[0078] In actual applications, the organization administrator of the external chain first fills in the type and quantity of nodes to be added. After that, the organization administrator of the external chain conducts a consensus vote with other organization administrators of the external chain. If the consensus vote is in favor, the multi-chain management platform obtains the request to add a new node for the external chain.

[0079] Step D2: Based on the request to add a new node, the administrator of the multi-chain management platform conducts a consensus vote through the multi-chain management platform.

[0080] Administrators of the multi-chain management platform participate in the consensus of external chains and conduct consensus voting based on requests to add new nodes.

[0081] Step D3: When the voting result of the administrators of the multi-chain management platform is in favor, the alliance administrator processes the request to add a new node.

[0082] In actual applications, the organization administrator of the external link can organize and approve the changes of the external link, the administrator of the multi-chain management platform can approve, confirm and implement the changes of the external link, and the alliance administrator can make directional decisions on the changes of the external link.

[0083] Specifically, the alliance administrator processes the request to add a new node, which may include, if the alliance administrator agrees to the request to add a new node, communicating offline with the organization administrator of the external chain, and then processing the request to add a new node through the multi-chain management platform.

[0084] The multi-chain management platform processes the request to add a new node, which can be specifically executed as follows: based on the description information of the node corresponding to the request to add a new node, a target node corresponding to the description information of the external chain is established on the multi-chain management platform, and a first configuration file of the target node is generated; based on the obtained second configuration information of the external chain and the first configuration file, the third configuration information is determined, and the third configuration information is sent to the external chain; based on the first configuration file, the target node is started so that the target node establishes a P2P connection with the external chain configured with the third configuration information.

[0085] In this embodiment, compared with the architecture in which external links are managed only by administrators of each organization through external links, the architecture of this solution is more hierarchical, and the security of external link management is enhanced by multi-level managers participating in the management of external links.

[0086] Figure 2 FIG. 1 is a flow chart of another multi-chain service management method provided in an embodiment of the present application. Figure 2 As shown, the method includes:

[0087] Step 202, obtaining a business request for an external chain, where the business request includes one or more of the following: a business request for node consensus, a business request for driver plug-in access, and a business request for node front-end service.

[0088] Step 204: If the service request is a service request for node consensus, then in response to the service request for node consensus, obtain description information of the external chain.

[0089] Step 206: Based on the description information of the external link, an organization and a target node corresponding to the description information of the external link are established on the multi-chain management platform, and a first configuration file of the organization and the target node is generated.

[0090] Step 208: Determine third configuration information based on the acquired second configuration information of the external link and the first configuration file, and send the third configuration information to the external link.

[0091] Step 210, based on the first configuration file, start the target node, and establish a P2P connection between the target node and the external chain configured with the third configuration information, so as to manage the external chain, and the management includes participating in the consensus of the external chain.

[0092] Among them, the description information of the external chain includes genesis block information, organization information, node information and certificate information.

[0093] Step 212: If the service request is a service request for a node front-end service, a front-end service driver plug-in and a second configuration file of the front-end service driver plug-in are generated in response to the service request for the node front-end service.

[0094] Step 214, when the second configuration file is configured with the third configuration information of the external link and the front-end service driver plug-in is deployed in the external link, obtain the fourth configuration information of the front-end service driver plug-in.

[0095] Step 216: Based on the fourth configuration information, the external chain is managed through the first external chain management component created on the multi-chain management platform and the front-end service driver plug-in that communicates with the external chain.

[0096] Among them, the front-end service driver plug-in encapsulates the configuration information of the second SDK and the multi-chain management platform.

[0097] Step 218: If the service request is a service request for access by a driver plug-in, a second external link management component is created in response to the service request for access by the driver plug-in.

[0098] Step 220: Acquire first configuration information of the external link through the second external link management component, and generate a first SDK based on the first configuration information through a driver plug-in generation tool in the second external link management component.

[0099] Step 222: Based on the first configuration information, configure the first SDK, and establish a communication connection between the configured first SDK on the multi-chain management platform and the external chain.

[0100] Step 224: manage the external chain based on the communication connection between the configured first SDK on the multi-chain management platform and the external chain.

[0101] In this embodiment, by obtaining a business request for an external chain, the business request includes one or more of the following: a business request for node consensus, a business request for driver plug-in access, and a business request for node front-end service; then, if the business request is a business request for node consensus, the description information of the external chain is obtained, and based on the description information of the external chain, a target node corresponding to the description information of the external chain is established on a multi-chain management platform, a P2P connection is made with the external chain, and the external chain is managed to participate in the consensus of the external chain; if the business request is a business request for driver plug-in access, the first configuration information of the external chain is obtained, and based on the first configuration information, a first software development kit SDK generated and configured on the multi-chain management platform is used to communicate with the external chain and manage the external chain; if the business request is a business request for node front-end service, a front-end service driver plug-in is generated, and based on the front-end service driver plug-in deployed on the external chain, a communication connection is made with the external chain to manage the external chain. This solution designs a multi-chain management platform with comprehensive applicable scenarios. The multi-chain management platform can process business requests corresponding to the management needs of external chains in various scenarios, thereby managing various external chains, solving the problem of limitations in the management of external chains in related technologies; on this basis, this solution enables enterprises to uniformly deploy smart contracts for external chains on the multi-chain management platform, greatly simplifying cross-chain and cross-organizational contract management. Compared with traditional decentralized and complex deployment methods, this unified deployment mechanism greatly reduces the operating steps, saves time and reduces labor costs. At the same time, it ensures the standardization and consistency of contract deployment, which is conducive to enterprises to quickly respond to market demands and flexibly adjust smart contract strategies.

[0102] Corresponding to the multi-chain service management method provided in the above embodiment, based on the same technical concept, the embodiment of the present invention also provides a multi-chain service management device. Figure 3 is a schematic diagram of the structure of a multi-chain service management device according to an embodiment of the present invention, the multi-chain service management device is used to execute Figure 1 to Figure 2 The multi-chain business management method described in Figure 3 As shown, the multi-chain service management device includes: an acquisition module 310, a first connection module 320, a second connection module 330 and a third connection module 340.

[0103] The acquisition module 310 is used to acquire a business request for an external chain, where the request includes one or more of the following: a business request for node consensus, a business request for driver plug-in access, and a business request for node front-end service;

[0104] The first connection module 320 is used to obtain the description information of the external chain if the business request is a business request for node consensus, and based on the description information of the external chain, establish a target node corresponding to the description information of the external chain on the multi-chain management platform, and establish a P2P connection with the external chain to manage the external chain, including participating in the consensus of the external chain;

[0105] The second connection module 330 is used to obtain the first configuration information of the external chain if the business request is a business request for driver plug-in access, and based on the first configuration information, communicate with the external chain through the first software development kit SDK generated and configured on the multi-chain management platform to manage the external chain;

[0106] The third connection module 340 is used to generate a front-end service driver plug-in if the business request is a business request for a node front-end service, and communicate with the external link based on the front-end service driver plug-in deployed in the external link to manage the external link.

[0107] In one implementation, the first connection module 320 includes:

[0108] The acquisition unit 3201 is used to obtain description information of the external chain in response to the business request for node consensus;

[0109] The first generating unit 3202 is used to establish an organization and a target node corresponding to the description information of the external chain on the multi-chain management platform based on the description information of the external chain, and to generate a first configuration file of the organization and the target node;

[0110] The sending unit 3203 is used to determine the third configuration information based on the acquired second configuration information of the external link and the first configuration file, and send the third configuration information to the external link;

[0111] The starting unit 3203 is used to start the target node based on the first configuration file, and establish a P2P connection between the target node and the external link configured with the third configuration information;

[0112] Among them, the description information of the external chain includes genesis block information, organization information, node information and certificate information.

[0113] In one implementation, the third connection module 340 is specifically configured to:

[0114] In response to a service request of a node front-end service, generating a front-end service driver plug-in and a second configuration file of the front-end service driver plug-in;

[0115] When the second configuration file is configured with the third configuration information of the external link and the front-end service driver plug-in is deployed in the external link, obtaining the fourth configuration information of the front-end service driver plug-in;

[0116] Based on the fourth configuration information, the external chain is managed through the first external chain management component created on the multi-chain management platform and the front-end service driver plug-in that communicates with the external chain;

[0117] Among them, the front-end service driver plug-in encapsulates the configuration information of the second SDK and the multi-chain management platform.

[0118] In one implementation, the second connection module 330 includes:

[0119] The second generating unit 3301 is used to obtain first configuration information of the external link in response to the service request of the driver plug-in access, and generate a first SDK based on the first configuration information;

[0120] The first connection unit 3302 is used to configure the first SDK based on the first configuration information, and to establish a communication connection between the configured first SDK on the multi-chain management platform and the external chain;

[0121] The second connection unit 3303 is used to manage the external chain based on the communication connection between the configured first SDK on the multi-chain management platform and the external chain.

[0122] In one implementation, the second generating unit 3301 is specifically configured to:

[0123] In response to the service request for access by the driver plug-in, create a second external chain management component;

[0124] The first configuration information of the external link is obtained through the second external link management component, and the first SDK is generated based on the first configuration information through the driver plug-in generation tool in the second external link management component.

[0125] In one implementation, the sending unit 3203 is specifically configured to:

[0126] Obtaining the second configuration information of the external link, and decoding the second configuration information to obtain fourth configuration information;

[0127] Merging and encoding the first configuration file and the fourth configuration information to obtain third configuration information;

[0128] The third configuration information is submitted to the node of the external chain as a configuration update transaction.

[0129] In one implementation, the multi-chain service management device further includes a processing module 350 .

[0130] The processing module 350 is used to obtain a request for adding a new node for an external link;

[0131] Based on the request to add a new node, the administrator of the multi-chain management platform conducts a consensus vote through the multi-chain management platform;

[0132] When the administrators of the multi-chain management platform vote in favor, the alliance administrator will process the request to add a new node.

[0133] In this embodiment, by obtaining a business request for an external chain, the business request includes one or more of the following: a business request for node consensus, a business request for driver plug-in access, and a business request for node front-end service; then, if the business request is a business request for node consensus, the description information of the external chain is obtained, and based on the description information of the external chain, a target node corresponding to the description information of the external chain is established on a multi-chain management platform, a P2P connection is made with the external chain, and the external chain is managed to participate in the consensus of the external chain; if the business request is a business request for driver plug-in access, the first configuration information of the external chain is obtained, and based on the first configuration information, a first software development kit SDK generated and configured on the multi-chain management platform is used to communicate with the external chain and manage the external chain; if the business request is a business request for node front-end service, a front-end service driver plug-in is generated, and based on the front-end service driver plug-in deployed on the external chain, a communication connection is made with the external chain to manage the external chain. This solution designs a multi-chain management platform with comprehensive applicable scenarios. The multi-chain management platform can process business requests corresponding to the management needs of external chains in various scenarios, thereby managing various external chains, solving the problem of limitations in the management of external chains in related technologies; on this basis, this solution enables enterprises to uniformly deploy smart contracts for external chains on the multi-chain management platform, greatly simplifying cross-chain and cross-organizational contract management. Compared with traditional decentralized and complex deployment methods, this unified deployment mechanism greatly reduces the operating steps, saves time and reduces labor costs. At the same time, it ensures the standardization and consistency of contract deployment, which is conducive to enterprises to quickly respond to market demands and flexibly adjust smart contract strategies.

[0134] Those skilled in the art should understand that the above-mentioned multi-chain business management device can be used to implement the multi-chain business management method mentioned above, and the detailed description thereof should be similar to the description of the method part mentioned above, and will not be repeated here to avoid repetition.

[0135] Based on the same technical concept, an embodiment of the present application further provides an electronic device, which is used to execute the above-mentioned multi-chain service management method. Figure 4 A schematic diagram of the structure of an electronic device for implementing various embodiments of the present application. The electronic device may have relatively large differences due to different configurations or performances, and may include a processor (processor) 410, a communication interface (Communications Interface) 420, a memory (memory) 430 and a communication bus 440, wherein the processor 410, the communication interface 420, and the memory 430 communicate with each other through the communication bus 440. The processor 410 may call a computer program stored in the memory 430 and executable on the processor 410 to perform the following steps:

[0136] Obtain business requests for external chains, which include one or more of the following: business requests for node consensus, business requests for driver plug-in access, and business requests for node front-end services;

[0137] If the business request is a business request for node consensus, the description information of the external chain is obtained, and based on the description information of the external chain, a target node corresponding to the description information of the external chain is established on the multi-chain management platform, and a P2P connection is made with the external chain to manage the external chain, including participating in the consensus of the external chain;

[0138] If the service request is a service request for access by a driver plug-in, first configuration information of the external chain is obtained, and based on the first configuration information, a first software development kit SDK generated and configured on the multi-chain management platform is used to communicate with the external chain to manage the external chain;

[0139] If the business request is a business request for a node front-end service, a front-end service driver plug-in is generated, and based on the front-end service driver plug-in deployed on the external chain, a communication connection is established with the external chain to manage the external chain.

[0140] In this embodiment, by obtaining a business request for an external chain, the business request includes one or more of the following: a business request for node consensus, a business request for driver plug-in access, and a business request for node front-end service; then, if the business request is a business request for node consensus, the description information of the external chain is obtained, and based on the description information of the external chain, a target node corresponding to the description information of the external chain is established on a multi-chain management platform, a P2P connection is made with the external chain, and the external chain is managed to participate in the consensus of the external chain; if the business request is a business request for driver plug-in access, the first configuration information of the external chain is obtained, and based on the first configuration information, a first software development kit SDK generated and configured on the multi-chain management platform is used to communicate with the external chain and manage the external chain; if the business request is a business request for node front-end service, a front-end service driver plug-in is generated, and based on the front-end service driver plug-in deployed on the external chain, a communication connection is made with the external chain to manage the external chain. This solution designs a multi-chain management platform with comprehensive applicable scenarios. The multi-chain management platform can process business requests corresponding to the management needs of external chains in various scenarios, thereby managing various external chains, solving the problem of limitations in the management of external chains in related technologies; on this basis, this solution enables enterprises to uniformly deploy smart contracts for external chains on the multi-chain management platform, greatly simplifying cross-chain and cross-organizational contract management. Compared with traditional decentralized and complex deployment methods, this unified deployment mechanism greatly reduces the operating steps, saves time and reduces labor costs. At the same time, it ensures the standardization and consistency of contract deployment, which is conducive to enterprises to quickly respond to market demands and flexibly adjust smart contract strategies.

[0141] The specific execution steps can refer to the various steps of the above-mentioned multi-chain business management method embodiment, and can achieve the same technical effect. To avoid repetition, they will not be repeated here.

[0142] It should be noted that the electronic devices in the embodiments of the present application include: servers, terminals, or other devices except terminals.

[0143] The above electronic device structure does not constitute a limitation on the electronic device. The electronic device may include more or fewer components than shown in the figure, or combine certain components, or arrange the components differently. For example, the input unit may include a graphics processing unit (GPU) and a microphone, and the display unit may be configured with a display panel in the form of a liquid crystal display, an organic light-emitting diode, etc. The user input unit includes a touch panel and at least one of other input devices. The touch panel is also called a touch screen. Other input devices may include, but are not limited to, a physical keyboard, function keys (such as volume control buttons, switch buttons, etc.), a trackball, a mouse, and a joystick, which will not be repeated here.

[0144] The memory can be used to store software programs and various data. The memory may mainly include a first storage area for storing programs or instructions and a second storage area for storing data, wherein the first storage area may store an operating system, an application program or instructions required for at least one function (such as a sound playback function, an image playback function, etc.), etc. In addition, the memory may include a volatile memory or a non-volatile memory, or the memory may include both volatile and non-volatile memories. Among them, the non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. Volatile memory can be random access memory (RAM), static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDRSDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM) and direct memory bus random access memory (DRRAM).

[0145] The processor may include one or more processing units; optionally, the processor integrates an application processor and a modem processor, wherein the application processor mainly processes operations related to the operating system, user interface, and application programs, and the modem processor mainly processes wireless communication signals, such as a baseband processor. It is understandable that the modem processor may not be integrated into the processor.

[0146] The embodiment of the present application also provides a storage medium, on which computer executable instructions are stored. When the computer executable instructions are executed by the processor, the various processes of the above-mentioned multi-chain business management method embodiment are implemented, and the same technical effect can be achieved. To avoid repetition, they are not repeated here.

[0147] The processor is the processor in the electronic device described in the above embodiment. The storage medium includes a computer-readable storage medium, such as a computer read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.

[0148] An embodiment of the present application further provides a chip, which includes a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement the various processes of the above-mentioned multi-chain business management method embodiment, and can achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0149] It should be understood that the chip mentioned in the embodiments of the present application can also be called a system-level chip, a system chip, a chip system or a system-on-chip chip, etc.

[0150] The embodiment of the present application also provides a computer program product, including a computer program. When the computer program is executed by a processor, the various processes of the above-mentioned multi-chain business management method embodiment are implemented, and the same technical effect can be achieved. To avoid repetition, it will not be repeated here.

[0151] It should be noted that, in this article, the terms "comprise", "include" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also includes other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, an element defined by the sentence "comprises one..." does not exclude the presence of other identical elements in the process, method, article or device including the element. In addition, it should be noted that the scope of the methods and devices in the embodiments of the present application is not limited to performing functions in the order shown or discussed, and may also include multitasking and parallel processing according to the functions involved, and various steps may also be added, omitted, or combined. In addition, the features described with reference to certain examples may be combined in other examples.

[0152] Through the description of the above implementation methods, those skilled in the art can clearly understand that the above-mentioned embodiment methods can be implemented by means of software plus a necessary general hardware platform, and of course by hardware, but in many cases the former is a better implementation method. Based on such an understanding, the technical solution of the present application, or the part that contributes to the prior art, can be embodied in the form of a software product, which is stored in a storage medium (such as ROM / RAM, a magnetic disk, or an optical disk), and includes a number of instructions for a terminal (which can be a mobile phone, a computer, a server, an air conditioner, or a network device, etc.) to execute the methods described in each embodiment of the present application.

[0153] The embodiments of the present application are described above in conjunction with the accompanying drawings, but the present application is not limited to the above-mentioned specific implementation methods. The above-mentioned specific implementation methods are merely illustrative and not restrictive. Under the guidance of the present application, ordinary technicians in this field can also make many forms without departing from the purpose of the present application and the scope of protection of the claims, all of which are within the protection of the present application.

Claims

1. A multi-chain business management method, characterized in that: Applied to a multi-chain management platform, the method includes: Obtaining a business request for an external chain, wherein the business request includes one or more of the following: a business request for node consensus, a business request for driver plug-in access, and a business request for node front-end service; If the service request is the service request for node consensus, the description information of the external chain is obtained, and based on the description information of the external chain, a target node corresponding to the description information of the external chain is established on the multi-chain management platform, and a P2P connection is established with the external chain to manage the external chain, wherein the management includes participating in the consensus of the external chain; If the service request is a service request for access by the driver plug-in, first configuration information of the external chain is obtained, and based on the first configuration information, a communication connection is established with the external chain through a first software development kit SDK generated and configured on the multi-chain management platform to manage the external chain; If the service request is a service request for the node front-end service, a front-end service driver plug-in is generated, and based on the front-end service driver plug-in deployed on the external link, a communication connection is established with the external link to manage the external link.

2. The method according to claim 1, characterized in that: If the service request is the service request for node consensus, the description information of the external chain is obtained, and based on the description information of the external chain, a target node corresponding to the description information of the external chain is established on the multi-chain management platform to establish a P2P connection with the external chain, including: In response to the service request for node consensus, obtaining description information of the external chain; Based on the description information of the external chain, establishing an organization and the target node corresponding to the description information of the external chain on the multi-chain management platform, and generating a first configuration file of the organization and the target node; Determine third configuration information based on the acquired second configuration information of the external link and the first configuration file, and send the third configuration information to the external link; Based on the first configuration file, start the target node, and establish a P2P connection between the target node and the external link configured with the third configuration information; The description information of the external chain includes genesis block information, organization information, node information and certificate information.

3. The method according to claim 1, characterized in that If the service request is a service request for the node front-end service, a front-end service driver plug-in is generated, and based on the front-end service driver plug-in deployed on the external link, a communication connection is established with the external link to manage the external link, including: In response to a service request of the node front-end service, generating the front-end service driver plug-in and a second configuration file of the front-end service driver plug-in; When the second configuration file is configured with the third configuration information of the external link and the front-end service driver plug-in is deployed in the external link, acquiring the fourth configuration information of the front-end service driver plug-in; Based on the fourth configuration information, the external chain is managed through the first external chain management component created on the multi-chain management platform and the front-end service driver plug-in that is in communication connection with the external chain; Among them, the front-end service driver plug-in encapsulates the configuration information of the second SDK and the multi-chain management platform.

4. The method according to claim 1, characterized in that If the service request is a service request for access by the driver plug-in, first configuration information of the external chain is obtained, and based on the first configuration information, a first software development kit SDK generated and configured on the multi-chain management platform is used to communicate with the external chain to manage the external chain, including: In response to a service request for access by the driver plug-in, obtaining first configuration information of the external link, and generating the first SDK based on the first configuration information; Based on the first configuration information, configure the first SDK, and establish a communication connection between the configured first SDK on the multi-chain management platform and the external chain; Based on the communication connection between the first SDK configured on the multi-chain management platform and the external chain, the external chain is managed.

5. The method according to claim 4, characterized in that The step of obtaining, in response to the service request for access by the driver plug-in, first configuration information of the external link and generating the first SDK based on the first configuration information includes: In response to the service request for access by the driver plug-in, creating a second external link management component; The first configuration information of the external link is acquired through the second external link management component, and the first SDK is generated based on the first configuration information through the driver plug-in generation tool in the second external link management component.

6. The method according to claim 2, characterized in that The determining, based on the acquired second configuration information of the external link and the first configuration file, third configuration information, and sending the third configuration information to the external link includes: Acquire second configuration information of the external link, and decode the second configuration information to obtain fourth configuration information; Merging and encoding the first configuration file and the fourth configuration information to obtain the third configuration information; Submit the third configuration information as a configuration update transaction to the node of the external chain.

7. The method according to claim 1 or 2, characterized in that: After establishing a target node corresponding to the description information of the external chain on the multi-chain management platform based on the description information of the external chain and performing a P2P connection with the external chain, the method further includes: Obtaining a request for adding a new node for the external chain; Based on the request to add a new node, the administrator of the multi-chain management platform performs a consensus vote through the multi-chain management platform; When the voting result of the administrator of the multi-chain management platform is in favor, the alliance administrator processes the request to add a new node.

8. A multi-chain service management device, characterized in that: Applied to a multi-chain management platform, the device comprises: An acquisition module, used to acquire business requests for external chains, wherein the requests include one or more of the following: business requests for node consensus, business requests for driver plug-in access, and business requests for node front-end services; A first connection module, configured to obtain the description information of the external chain if the service request is the service request for node consensus, and establish a target node corresponding to the description information of the external chain on a multi-chain management platform based on the description information of the external chain, and establish a P2P connection with the external chain to manage the external chain, wherein the management includes participating in the consensus of the external chain; A second connection module is used for obtaining first configuration information of the external chain if the service request is a service request for access by the driver plug-in, and based on the first configuration information, communicating with the external chain through a first software development kit SDK generated and configured on the multi-chain management platform to manage the external chain; The third connection module is used to generate a front-end service driver plug-in if the business request is a business request for the front-end service of the node, and to communicate with the external link based on the front-end service driver plug-in deployed on the external link to manage the external link.

9. An electronic device, characterized in that: include: processor; as well as A memory arranged to store computer executable instructions, wherein the executable instructions are configured to be executed by the processor, and the executable instructions include instructions for executing the multi-chain business management method according to any one of claims 1 to 7.

10. A storage medium, characterized in that: The storage medium is used to store computer-executable instructions, and the computer-executable instructions enable a computer to execute the multi-chain business management method according to any one of claims 1 to 7.

Images