WO2023040450A1 - Blockchain service network establishment - Google Patents

Abstract

Provided are a method an apparatus for establishing a blockchain service network. The establishment method comprises: receiving a registration request corresponding to a target blockchain; and in response to the registration request, performing registration processing on the target blockchain, so as to add the target blockchain to a blockchain service network as a member blockchain; registration processing comprises creating a blockchain account corresponding to a centralized management platform on the target blockchain, the blockchain account being used for initiating contract invocation of a target user smart contract deployed on the target blockchain when a service-using party invokes a registered user service on the centralized management platform; wherein the user service comprises contract execution logic of the target user smart contract deployed on the target blockchain.

Description

Formation of blockchain service network technical field

One or more embodiments of this specification relate to the field of blockchain technology, and in particular to a method and device for establishing a blockchain service network.

Background technique

With the development of blockchain technology, more and more businesses can be implemented using smart contracts deployed in the blockchain system. As the infrastructure behind the business, the blockchain system requires investment in operation and maintenance. Therefore, some large service organizations have launched their own blockchain systems to provide blockchain-related basic services for business parties who are unable to build blockchain systems. The business parties that access the blockchain system can realize the corresponding business by calling the smart contract deployed in the blockchain system.

However, in practical applications, different blockchain systems are usually independent of each other. How to use these mutually independent blockchain systems to provide business parties with basic blockchain-related services more effectively is an urgent need. Solved technical problems.

Contents of the invention

In view of this, one or more embodiments of this specification provide a method, device, electronic equipment, and storage medium for establishing a blockchain service network.

In order to achieve the above purpose, one or more embodiments of this specification provide the following technical solutions: According to the first aspect of one or more embodiments of this specification, a method for establishing a blockchain service network is provided, which is used to establish the blockchain service network The centralized management and control platform of the block chain service network. The method includes: receiving a registration request corresponding to the target blockchain; in response to the registration request, performing registration processing on the target blockchain, so as to add the target blockchain as a member blockchain to the Blockchain service network. Wherein, the registration process includes creating a blockchain account corresponding to the centralized management and control platform in the target blockchain; When the registered user serves, initiate a contract call for the target user smart contract deployed on the target blockchain; the user service includes the contract execution logic of the target user smart contract deployed on the target blockchain.

According to the second aspect of one or more embodiments of the present specification, a device for building a blockchain service network is also proposed, which is applied to building a centralized management and control platform of the blockchain service network. The device includes: a receiving module that receives a registration request corresponding to the target blockchain; a registration module that responds to the registration request and performs registration processing on the target blockchain to use the target blockchain as a member The block chain joins the block chain service network. Wherein, the registration process includes creating a blockchain account corresponding to the centralized management and control platform in the target blockchain; When the registered user serves, initiate a contract call for the target user smart contract deployed on the target blockchain; the user service includes the contract execution logic of the target user smart contract.

In the above implementations of this specification, a blockchain service network composed of at least one member blockchain can be built by way of registration, and based on the contract contained in the user smart contract distributed on the member blockchain Execute the logic and further register standardized user services on the centralized management and control platform. Since the user service can include contract execution logic from user smart contracts on different member blockchains, in this way, it is equivalent to integrating the service capabilities of user smart contracts on different member blockchains , the contract execution logic with basic service capabilities included in user smart contracts on different member blockchains is integrated to generate services with more complex service capabilities, so that the user smart contracts deployed on different member blockchains Service capabilities can be fully circulated and shared among member blockchains, thereby fundamentally solving the problem of information islands caused by the isolation of member blockchains and the inability to integrate the service capabilities they provide.

It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the specification.

Description of drawings

The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the specification and together with the description serve to explain the principles of the specification.

Fig. 1 is a network architecture diagram of a blockchain service network shown in an exemplary embodiment of this specification.

Fig. 2 is a flowchart of a method for establishing a blockchain service network according to an exemplary embodiment in this specification.

Fig. 3 is a flow chart of a process of registering a target blockchain shown in this specification.

Fig. 4 is a flow chart of a service registration method for registering user services on a centralized management and control platform according to an exemplary embodiment of this specification.

Fig. 5 is a flowchart of a service registration method for registering a service solution on a centralized management and control platform according to an exemplary embodiment of this specification.

Fig. 6 is a flow chart of a method for using a service for user services registered on a centralized management and control platform according to an exemplary embodiment of this specification.

Fig. 7 is a flow chart of another method for using services for user services registered on a centralized management and control platform according to an exemplary embodiment of the present specification.

Fig. 8 is a schematic structural diagram of an electronic device provided by an exemplary embodiment.

Fig. 9 is a block diagram of an apparatus for building a blockchain service network according to an exemplary embodiment in this specification.

Detailed ways

Reference will now be made in detail to the exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, the same numerals in different drawings refer to the same or similar elements unless otherwise indicated. Implementations described in the following exemplary embodiments do not represent all implementations consistent with one or more embodiments of this specification. Rather, they are merely examples of apparatuses and methods consistent with aspects of one or more embodiments of the present specification as recited in the appended claims.

It should be noted that in other embodiments, the steps of the corresponding methods are not necessarily performed in the order shown and described in this specification. In some other embodiments, the method may include more or less steps than those described in this specification. In addition, a single step described in this specification may be decomposed into multiple steps for description in other embodiments; multiple steps described in this specification may also be combined into a single step in other embodiments describe.

With the continuous development of blockchain technology, more and more blockchains have been established. However, each blockchain is usually independent of each other, and different blockchains are usually not connected to each other. Therefore, this results in the service capabilities of user smart contracts deployed on a single blockchain, which cannot be fully circulated and shared among different blockchains.

However, this manual aims to build a blockchain service network composed of at least one member blockchain, and distribute the information contained in the user smart contracts on each member blockchain in the blockchain service network. The contract execution logic is integrated to build a technical solution for standardized services open to users.

When implementing, the target blockchain that needs to join the blockchain service network can be registered as a member blockchain of the blockchain service network by sending a registration request to the centralized management and control platform of the blockchain service network .

When the centralized management and control platform receives the registration request corresponding to the target blockchain, it can register the target blockchain to add the target blockchain as a member blockchain to the blockchain service network.

Among them, the centralized management and control platform can support the registration of user services generated by the combination of contract execution logic contained in the user smart contracts deployed on each member blockchain.

After the target blockchain joins the blockchain service network as a member blockchain, the subsequent service provider can integrate the contract execution logic contained in the user smart contract deployed on the target blockchain to generate the target user service , or, integrate the contract execution logic contained in the user smart contract deployed on the target blockchain with the contract execution logic contained in the user smart contract deployed on other member blockchains to generate the target user service, and then the The target user service is registered to the centralized management and control platform.

Wherein, when the centralized management and control platform registers the target blockchain, it can also create a blockchain account corresponding to the centralized management and control platform in the target blockchain. Subsequently, when the user needs to call the above-mentioned target user service registered on the centralized control platform, the user can initiate a transaction for the target block based on creating a blockchain account corresponding to the centralized control platform in the target blockchain. The contract call of the above user smart contract deployed on the chain to complete the service call for the user service.

In the above technical solutions, a blockchain service network composed of at least one member blockchain can be built by means of registration, and based on the contract execution logic contained in the user smart contracts distributed on the member blockchains, Further register standardized user services on the centralized management and control platform. Since the user service can include contract execution logic from user smart contracts on different member blockchains, in this way, it is equivalent to integrating the service capabilities of user smart contracts on different member blockchains , the contract execution logic with basic service capabilities included in user smart contracts on different member blockchains is integrated to generate services with more complex service capabilities, so that the user smart contracts deployed on different member blockchains Service capabilities can be fully circulated and shared among member blockchains, thereby fundamentally solving the problem of information islands caused by the isolation of member blockchains and the inability to integrate the service capabilities they provide.

Please refer to FIG. 1, which is a network architecture diagram of a blockchain service network shown in an exemplary embodiment of this specification.

As shown in Figure 1, in the network architecture of the above-mentioned blockchain service network, it may include a blockchain service network composed of several member blockchains, a target blockchain network to be registered, and a network for blockchain services A centralized management and control platform for network management. It should be noted that initially, there are no member blockchains in the blockchain service network, and the target blockchain can only be added to the blockchain service network after registration through the centralized management platform.

Among them, the target blockchain network to be registered shown in Figure 1 refers to a blockchain network that has not yet joined the blockchain service network. The above-mentioned target blockchain network can register and interact with the centralized management and control platform. To apply to join the above target blockchain network as a member blockchain.

The first member blockchain, the second member blockchain and the third member blockchain shown in FIG. 1 refer to the member blockchains that have joined the aforementioned blockchain service network.

Wherein, in one embodiment shown, at least some of the member blockchains in the aforementioned blockchain service network may be heterogeneous blockchains.

It should be noted that heterogeneous blockchains in a narrow sense usually refer to significant differences in the value of circulation on the blockchain; that is, between two blockchains with significant differences in the value of circulation, usually Call it a heterogeneous blockchain. For example, the Bitcoin network and Ethereum are heterogeneous blockchains in a narrow sense.

In a broad sense, heterogeneous blockchain refers to the obvious differences in the type of blockchain and/or the adopted blockchain protocol; that is, there are obvious differences in the type of blockchain and/or the adopted blockchain protocol. Between two blockchains, it can usually be called a heterogeneous blockchain. For example, ANT CHAIN and hyperledger fabric blockchain are heterogeneous blockchains in a broad sense.

Several user smart contracts can be deployed on each member blockchain in the above-mentioned blockchain service network.

Among them, the contract execution logic expressed by the contract code in these user smart contracts can usually include multiple contract execution logics corresponding to different basic service capabilities.

For example, in practical applications, the contract execution logic contained in a smart contract can usually be in the form of a function, and a smart contract can contain multiple functions corresponding to different service functions.

The centralized management and control platform shown in FIG. 1 may specifically be a service platform for centralized management of the aforementioned blockchain service network. Wherein, it should be noted that the hardware device carrying the centralized management and control platform may be a server, or a server cluster based on several servers, which is not particularly limited in this specification.

As a centralized service platform, the above-mentioned centralized management and control platform can manage members of the above-mentioned blockchain service network; for example, it can be responsible for the registration of member blockchains in the blockchain service network, joining and exiting the network, and so on.

In addition, the above-mentioned centralized management and control platform can also be used to realize cross-chain access between member blockchains; for example, in practical applications, a cross-chain service component can be installed on the above-mentioned centralized management and control platform, The cross-chain service component is specifically used to realize cross-chain data interaction between member blockchains. Each member blockchain that joins the blockchain service network can realize cross-chain data access with other member blockchains through the cross-chain service components on the above-mentioned centralized management and control platform.

Alternatively, the above-mentioned centralized management and control platform, in the process of centralized management of each member blockchain, can also issue and deploy a system smart contract for cross-chain data access to each member blockchain, so that each member The blockchain network can implement cross-chain data access with other member blockchains based on the above-mentioned system smart contracts deployed.

Furthermore, the above-mentioned centralized management and control platform can not only be used for member management of the blockchain service network and cross-chain access between member blockchains, but also support registration by deploying on each member blockchain. The user service generated by the combination of contract execution logic contained in the user smart contract.

Among them, the above-mentioned user services specifically refer to services with more complex service capabilities generated by combining contract execution logic with basic service capabilities contained in user smart contracts on different member blockchains.

For example, during implementation, the contract execution logic with basic service capabilities contained in user smart contracts distributed on each member blockchain can be combined as basic service components to generate more complex user services, and then the User service is registered to the centralized management and control platform as a standardized service for users to call. Among them, in one embodiment shown, the user service registered on the above-mentioned centralized management and control platform may specifically include at least one contract execution logic contained in the user smart contract deployed on each member blockchain, according to the The logical sequence of the service logic corresponding to the user service is combined to generate the service.

It should be noted that the service logic corresponding to the user service and the logical sequence of the service logic usually depend on the user's specific service registration requirements, and in practical applications, the user can usually customize it based on actual needs.

Further, in another embodiment shown, at least part of the contract execution logic in the contract execution logic that is combined to generate the above-mentioned user services may respectively correspond to user smart contracts deployed on different member blockchains. In other words, users can combine the contract execution logic contained in user smart contracts distributed on different member blockchains to generate a user service.

Of course, in practical applications, at least part of the contract execution logic in the contract execution logic for generating the above-mentioned user services can also be derived from the contract execution logic contained in multiple user smart contracts in the same member blockchain; or, It can also be derived from multiple contract execution logic contained in the same user smart contract in the same member blockchain, which is not specifically limited in this specification.

In order to facilitate users of the service provider, the contract execution logic contained in each user smart contract deployed on each member blockchain can be freely combined to generate user services with more complex service capabilities. The centralized platform can combine the above blocks The access authority of the contract execution logic contained in the user smart contract deployed on each member blockchain in the chain service network is open to the users of the service provider.

Among them, when the centralized platform opens the access rights of the contract execution logic contained in the user smart contracts deployed on the member blockchains of the above-mentioned blockchain service network to the users of the service provider, in order to maximize the protection of all The data privacy and security of each user smart contract deployed on the member blockchain can be selectively opened to the service provider's access rights to only part of the contract execution logic contained in the user smart contract deployed on the member blockchain. user. However, for contract execution logic that does not have open access rights, it cannot be used to combine and generate user services.

In one embodiment shown, the centralized management and control platform can also support the registration of the contract execution logic contained in the user smart contracts deployed on each member blockchain on the centralized management and control platform. Correspondingly, the user services registered on the centralized management and control platform can be services generated by combining at least one contract execution logic registered on the centralized management and control platform.

For example, in one example, the centralized management and control platform can support the registration of the contract execution logic contained in the user smart contracts deployed on each member blockchain as a basic service component on the centralized management and control platform; where the basic service component will As a basic unit for composing user services. The user service registered on the centralized management and control platform can be a service generated by combining at least one basic service component registered on the centralized management and control platform. The deployer or manager of the user smart contract deployed on each member blockchain can send a basic component registration request to the centralized management and control platform, and the basic component registration request can include the execution of the target contract to be registered contained in the user smart contract Logical identification information (such as function name). When the centralized management and control platform receives the basic component registration request, it can assign a basic service component identifier to the deployment party or management party, and then the identification information of the target contract execution logic to be registered, including the target contract execution logic The address of the user's smart contract and the identification information of the member blockchain where the user's smart contract is deployed are bound to the basic service component identification to complete the registration of the basic service component.

In this case, the centralized management and control platform can only open the access rights of the contract execution logic registered on the centralized management and control platform to the users of the service provider, so that the users of the service provider can control the At least one contract execution logic registered on the platform can be freely combined to define new user services. However, access to contract execution logic that is not registered on the centralized management and control platform may not be opened to service users. In this way, the data privacy of user smart contracts on each member blockchain can be protected to the greatest extent, so that service providers can only freely combine the execution logic of contracts registered on the centralized management and control platform to customize new ones. user services without access to the smart logic of contracts that have not been opened.

For example, in one example, the centralized management and control platform can output the registered contract execution logic to the user of the service provider through a visual interface, so as to obtain the access rights of the contract execution logic registered on the centralized management and control platform, Open to users of the service provider, and then obtain at least one contract execution logic selected by the user of the service provider in the visual interface, and then execute the logic of at least one contract selected by the user of the service provider in the visual interface, According to the logical sequence of the service logic corresponding to the user service that the user of the service provider needs to register, the user service is combined to generate the user service.

Since the contract execution logic contained in the user's smart contract deployed on each member blockchain may involve user privacy or other contract execution logic that is not easy to open; therefore, in this way, the deployment in each member block The deployer or manager of the user's smart contract on the chain can selectively register only part of the contract execution logic contained in the user's smart contract on the centralized management and control platform, and only register these on the centralized management and control platform The access authority of the contract execution logic is open to the users of the service provider, so that the data privacy and security of the user smart contracts deployed on each member blockchain can be guaranteed to the greatest extent.

Of course, in practical applications, the centralized management and control platform can also choose to open the access rights of the contract execution logic contained in all user smart contracts deployed on the member blockchains to the users of the service provider.

In this case, the centralized management and control platform can no longer support the registration of the contract execution logic contained in the user smart contracts deployed on each member blockchain on the centralized management and control platform. After each member blockchain joins the blockchain service network, the centralized management and control platform can actively scan and analyze the blockchain data of each member blockchain to obtain user smart contracts on each member blockchain Deployment status; for example, through block scanning and analysis, to obtain user smart contracts deployed on each member blockchain, as well as the contract execution logic included in each user smart contract. Then, the access rights of the contract execution logic contained in all user smart contracts deployed on the member blockchains scanned and parsed are opened to the users of the service provider.

Please refer to FIG. 2. FIG. 2 is a flowchart of a method for forming a blockchain service network shown in this specification according to an exemplary embodiment. The method is applied to the centralized management and control platform shown in FIG. 1; the method includes : Step 201: receiving a registration request corresponding to the target blockchain; the above-mentioned target blockchain refers to a blockchain that needs to join the blockchain service network but has not yet completed registration. The above-mentioned target blockchain can be registered as a member blockchain of the blockchain service network by registering and interacting with the centralized management and control platform of the blockchain service network, and sending a registration request to the above-mentioned centralized management and control platform.

Wherein, the above-mentioned registration request may specifically be initiated by a user with the registration authority of the above-mentioned target block chain through a user account registered on the above-mentioned centralized management and control platform; The users with the registration permission of the chain, the user account registered on the above-mentioned centralized management and control platform, can specifically include the system administrator account in the above-mentioned centralized management and control platform, the manager of the above-mentioned target blockchain registered on the above-mentioned centralized management and control platform The administrator account of the target blockchain, the user account registered by the deployment party user of the user smart contract in the target blockchain on the above-mentioned centralized management and control platform, and so on. It should be pointed out that the user account that sends the registration request specifically refers to the centralized account registered in the centralized management and control platform, not the blockchain account registered in each member blockchain.

Wherein, in the above registration request, some basic registration information related to the above target blockchain to be registered may be included. The above-mentioned basic registration information may specifically include, access address information of the above-mentioned target blockchain, and blockchain configuration information related to the above-mentioned target blockchain, and so on.

Of course, in practical applications, in addition to some basic registration information related to the target blockchain to be registered, other forms of registration information may also be included in the above registration request, which is not specifically limited in this specification . Among them, the above-mentioned access address information of the target blockchain is specifically used to establish a network connection with the centralized management and control platform; in practical applications, the above-mentioned access address information may specifically include one or more nodes in the above-mentioned target blockchain The domain name information or IP address information corresponding to the device enables the centralized management and control platform to establish a communication connection with one or more node devices in the target blockchain based on the above domain name information or IP address information.

The above block chain configuration information may specifically include any form of information that can be used to represent the basic configuration of the above target block chain; for example, the above block chain configuration information may specifically include the block corresponding to the above target block chain Chain type information, protocol type information of the blockchain protocol adopted by the target blockchain, and algorithm type information of the consensus algorithm adopted by the target blockchain, etc.

For example, in an example, the above registration request can be expressed in the following data format:

{chain001.io; Common chain; Polkadot;….}

In the data format shown above, the domain name information of the above-mentioned target blockchain is "chain001.io", its blockchain type is "Common chain (public chain)", and the blockchain protocol it has adopted is " Polkadot (Poca)". Of course, in practical applications, the data format shown above may also contain other forms of data content, which will not be listed in this specification.

Step 202: In response to the registration request, perform registration processing for the target blockchain, so as to add the target blockchain as a member blockchain to the blockchain service network; the registration processing includes Create a blockchain account corresponding to the centralized management and control platform in the target blockchain, and the blockchain account is used to initiate a target user service registered on the centralized management and control platform when the service user calls The contract call of the target user smart contract deployed on the target blockchain; wherein, the user service includes the contract execution logic of the target user smart contract deployed on the target blockchain.

When the centralized management and control platform receives a registration request corresponding to the target blockchain, it can respond to the registration request and conduct a legality check on the registration request; for example, the legality check on the registration request may specifically include checking the Whether the initiator of the registration request has the corresponding registration authority; and whether the data format in the registration request meets the preset rules or format requirements, and so on.

After the centralized management and control platform completes the legality check for the registration request, if the registration request passes the legality check, the centralized management and control platform can further register the target blockchain based on the data content carried in the registration request Process to add the target blockchain as a member blockchain to the blockchain service network.

Wherein, the registration processing of the target blockchain by the centralized management and control platform may specifically include creating a blockchain account corresponding to the centralized management and control platform in the target blockchain.

For example, when implementing, you can first apply for a public-private key pair for the centralized management and control platform in the target blockchain, the private key is held by the management user of the centralized management and control platform, and then calculate and generate a corresponding account address (for example, the account address can usually be a hash value calculated by the public key), and then create a blockchain account corresponding to the account address in the target blockchain.

It should be noted that in a blockchain that adopts an account model, the types of accounts supported by the blockchain usually include external accounts and contract accounts. An external account is an account directly controlled by a user, also called a user account. The contract account is created by the user through an external account and contains an account of the contract code (that is, a smart contract). The creation of a blockchain account corresponding to the centralized management and control platform in the target blockchain described above may specifically be an external account. After the corresponding blockchain account is created for the centralized management and control platform in the target blockchain, the centralized management and control platform has obtained the legal user identity in the target blockchain, so that the centralized management and control platform Based on the external account, a contract call for the user's smart contract deployed in the target blockchain can be initiated.

The registration processing of the target blockchain by the centralized management and control platform may include, in addition to creating a blockchain account corresponding to the centralized management and control platform in the target blockchain, it may also include Other forms of registration processing related to the registration process.

For example, in one embodiment shown, the registration process performed by the centralized management and control platform on the target blockchain may specifically include deploying at least one system smart contract in the target blockchain; wherein, the above-mentioned at least one system smart contract The contract can specifically include a target system smart contract for cross-chain communication with other member blockchains.

Of course, in addition to the target system smart contract for cross-chain communication with other member blockchains, it may also include system smart contracts for implementing other basic management functions; for example, at least one of the above system smart contracts may also include Smart contracts for service management of the target blockchain, and smart contracts for service incentives for users registered on the centralized management and control platform for user services or service solutions, etc., are no longer included in this manual. List them all.

The process of registering the target blockchain is described in detail below through a specific embodiment.

Please refer to Fig. 3, Fig. 3 is a flow chart of the registration process for the target blockchain shown in this specification, including the following execution steps: Step 301, the registration direction centralized platform initiates the registration corresponding to the target blockchain request; after receiving the above registration request, the centralized management and control platform can respond to the registration request and start the registration process for the above target blockchain. Wherein, in this embodiment, the registration process for the above-mentioned target blockchain may include the registration process flow shown in the following steps 302-306.

Step 302, save the blockchain configuration information of the target blockchain; Step 303, establish communication connections with at least some node devices in the target blockchain based on the access address information of the target blockchain; The request may include some blockchain configuration information related to the above-mentioned target blockchain; for example, the above-mentioned blockchain configuration information may include the access address information of the above-mentioned target blockchain, and the configuration related to the above-mentioned target blockchain information, etc. After receiving the above-mentioned registration request, the centralized management and control platform can obtain the above-mentioned blockchain configuration information carried in the registration request, and then perform subsequent registration processing procedures for the above-mentioned target blockchain based on the obtained blockchain configuration information.

After receiving the above registration request, the centralized management and control platform can use the block chain configuration information related to the target block chain read from the registration request as the configuration information of the member block chains in the local database. storage.

For example, during implementation, the centralized management and control platform can maintain an information base for storing the blockchain configuration information related to each member blockchain in the above-mentioned blockchain service network, and the centralized management and control platform can send the registration request from the above Read the block chain configuration information related to the target block chain, and store it in the information base as the block chain configuration information of the member block chains.

After the centralized management and control platform stores the block chain configuration information related to the target block chain as the configuration information of the member block chains in the local database, it can further base on the above-mentioned information read from the registration request. The access address information of the target blockchain establishes communication connections with at least some of the node devices in the target blockchain.

For example, as mentioned above, the above-mentioned access address information may specifically include domain name information or IP address information corresponding to one or more node devices in the above-mentioned target blockchain, and the centralized management and control platform may be based on the above-mentioned domain name information or IP address information, Establish a communication connection with one or more node devices in the above target blockchain. Among them, during implementation, the centralized management and control platform can establish communication connections with all node devices in the above-mentioned target blockchain, or only with some key node devices in the above-mentioned target blockchain (such as storing complete block The full node of the chain ledger) establishes a communication connection.

Step 304, acquire block chain data related to the target block chain from node devices in the target block chain based on the communication connection.

After the centralized management and control platform has established a communication connection with at least some node devices in the target blockchain, it can continue to obtain the blockchain related to the target blockchain from the node devices in the target blockchain based on the communication connection. data.

Among them, the block chain data related to the target block chain obtained from the node device in the target block chain may specifically include any form of data related to the target block chain, and no special description will be made in this specification. Limitation; for example, in one example, the block chain data related to the target block chain obtained from the node device in the target block chain may specifically include the complete block chain ledger of the target block chain, and The authentication root data corresponding to the blockchain ledger of the target blockchain, the public key data of each node device in the target blockchain, and so on.

Among them, it should be noted that in the field of blockchain, the authentication root data corresponding to the blockchain ledger can usually include the genesis block data in the blockchain ledger, the block header data of each block, etc., which can be used for Data that authenticates the data stored in the blockchain ledger.

After acquiring the blockchain data related to the target blockchain from the node devices in the target blockchain, the centralized management and control platform can store the acquired blockchain data in the database.

For example, as mentioned above, the centralized management and control platform can maintain an information base for storing the blockchain configuration information related to each member blockchain in the above-mentioned blockchain service network, and the centralized management and control platform can transfer the information from the above-mentioned registered The block chain configuration information related to the target block chain is read in the request, and stored in the information base as the block chain configuration information of the member block chains. After the centralized management and control platform obtains the block chain data related to the target block chain from the node device in the target block chain, it can also use the obtained block chain data in the above information base and the above target The blockchain configuration information related to the blockchain is stored associatively.

Step 305, creating a blockchain account corresponding to the centralized management and control platform on the target blockchain.

After the centralized management and control platform obtains the blockchain data related to the target blockchain from the node device in the target blockchain based on the above-mentioned communication connection, it can also continue to create a centralized management and control platform on the above-mentioned target blockchain A corresponding blockchain account. Among them, the specific process of creating the above-mentioned blockchain account will not be described in detail.

After the corresponding blockchain account is created for the centralized management and control platform on the above target blockchain, the centralized management and control platform has obtained the legal user identity in the target blockchain and has the ability to call the above target area The ability of user smart contracts deployed on the block chain, the subsequent centralized management and control platform can initiate a contract call for the user smart contract deployed on the target block chain based on the block chain account.

Among them, on the above-mentioned centralized management and control platform, a blockchain account list can be maintained specifically. The block chain account list may specifically include the block chain accounts corresponding to the above-mentioned centralized management and control platforms created on each member block chain. After the corresponding blockchain account is created for the centralized management and control platform on the above-mentioned target blockchain, the blockchain account can be added to the above-mentioned blockchain account list for maintenance.

It should be noted that the blockchain accounts corresponding to the above-mentioned centralized management and control platforms created on each member blockchain may be the same or different. For example, in one example, in order to facilitate account management, the blockchain accounts corresponding to the above-mentioned centralized management and control platforms created on each member blockchain can use the same preset blockchain account by default. For example, during implementation, each member blockchain can reserve a fixed blockchain account in advance as the blockchain account corresponding to the centralized management and control platform.

Step 306, deploying at least one system smart contract in the target blockchain; wherein, the at least one system smart contract includes a target system smart contract for cross-chain communication with other member blockchains.

After creating a corresponding blockchain account for the centralized management and control platform on the above target blockchain, the centralized management and control platform can continue to deploy at least one system smart contract in the target blockchain. The above at least one system smart contract may specifically include a target system smart contract for cross-chain communication with other member blockchains.

Wherein, the above at least one system smart contract may include not only the target system smart contract for cross-chain communication with other member blockchains, but also the system smart contract for network governance of the target blockchain network, The system smart contracts used to provide service incentives for users related to user services registered on the centralized management and control platform, etc., are not specifically limited in this specification.

It should be noted that the above-mentioned system smart contract and the user smart contract deployed on the above-mentioned target blockchain are two completely different types of smart contracts.

The contract execution logic contained in the above-mentioned system smart contract is usually related to some management functions on the centralized management and control platform. For example, the contract execution logic contained in the system smart contract for network governance as mentioned above can be the execution logic related to the function of the centralized management and control platform for the network governance of the above-mentioned blockchain service network; The contract execution logic contained in the system smart contract used to provide service incentives for users related to user services registered on the centralized management and control platform may be related to the centralized management and control platform for users related to registered user services. Execution logic associated with the function of the incentive. The contract execution logic contained in the above user smart contract is usually related to the user service logic defined by the user on the member blockchain.

By deploying at least one system smart contract on the above-mentioned target blockchain, on the basis that the centralized management and control platform already has the ability to invoke the user smart contracts deployed on the above-mentioned target blockchain, users on the above-mentioned target blockchain can , it is also possible to complete some operations related to the management functions on the above-mentioned centralized management and control platform on the above-mentioned target blockchain by calling the system smart contract deployed on the above-mentioned target blockchain.

Step 307, returning a successful registration message corresponding to the target blockchain to the registrar.

After the centralized management and control platform executes the various registration processes shown in steps 302 to 306 for the above-mentioned target blockchain, the above-mentioned target blockchain will be successfully added to the above-mentioned block as a member blockchain Chain service network.

In this case, the above-mentioned centralized management and control platform returns a successful registration message corresponding to the above-mentioned target blockchain to the above-mentioned registrant to notify the above-mentioned registrant that the target blockchain has successfully joined the above-mentioned blockchain as a member blockchain. Blockchain service network.

Wherein, it should be noted that the order of the various registration processing flows shown in steps 302 to 306 in the above embodiment is only illustrative, and is not specifically limited in this specification. It can be understood that, in practical applications, the order of the various registration processing procedures shown in steps 302 to 306 in the above embodiment can be flexibly adjusted and exchanged based on actual registration requirements.

In this manual, after the target blockchain joins the blockchain service network as a member blockchain, users of subsequent service providers can, according to their own needs, deploy the target smart contract on the target blockchain The contract execution logic included is combined with the contract execution logic contained in the user smart contracts deployed on other member blockchains to generate target user services, and then register the target user services to the centralized management and control platform.

Among them, it can be understood that the contract execution logic for generating the above-mentioned target user service through combination will include the contract execution logic contained in the above-mentioned target user smart contract deployed on the above-mentioned target blockchain.

When the service user needs to call the above-mentioned target user service registered on the centralized control platform, it can create a blockchain account corresponding to the centralized management and control platform in the target blockchain, and use the blockchain account The blockchain identity of the representative to initiate a contract call for the above-mentioned target user contract deployed on the target blockchain.

Wherein, when the above-mentioned target user service is registered on the above-mentioned centralized management and control platform, the above-mentioned centralized management and control platform can specifically deploy the target user service as a standardized service, so as to be open to service users to call.

It should be noted that when the above-mentioned centralized management and control platform deploys the above-mentioned target user services that have been registered, it can specifically adopt a distributed deployment method or a centralized deployment method.

In one embodiment shown, when the above-mentioned centralized management and control platform deploys the above-mentioned target user services, specifically, the above-mentioned user services can be distributed and deployed on each member blockchain in the form of system smart contracts for service Called by the consumer.

Since the contract call logic that constitutes the above target user service may include contract execution logic contained in multiple user smart contracts deployed on multiple member blockchains, users may also need to call across chains when calling the above target user service Multiple user smart contracts distributed on multiple member blockchains; therefore, when the above-mentioned centralized management and control platform deploys user services registered on the centralized management and control platform, it can specifically develop corresponding cross-chain call logic for the user services , and then deploy the cross-chain call logic on each member blockchain as the contract execution logic of the system smart contract.

For example, as mentioned earlier, the contract execution logic contained in the above-mentioned system smart contract is usually related to some management functions on the centralized management and control platform. Therefore, in this way, it is equivalent to developing the corresponding cross-chain call logic for the user service, and as part of the execution logic related to some management functions on the centralized management and control platform, it is deployed in the form of system smart contracts in each member on the blockchain.

In one embodiment shown, the above-mentioned target system smart contract for cross-chain communication may include cross-chain call logic corresponding to the above-mentioned target user service.

The cross-chain call logic can be specifically used to: determine the user smart contracts corresponding to the execution logic of each contract that generates the target user service, and deploy the member blockchains of the above-mentioned user smart contracts, and based on the above-mentioned member areas The blockchain account created in the blockchain corresponding to the centralized management and control platform initiates cross-chain calls for the above-mentioned user smart contracts in accordance with the logical sequence of the service logic corresponding to the above-mentioned target user services.

In this way, service users can call the above-mentioned target user services that have been registered on the centralized management and control platform by calling the above-mentioned cross-chain call logic contained in the target system smart contract. In one embodiment shown, in the above-mentioned target system smart contract, the service configuration information corresponding to the above-mentioned target user service can also be maintained, as well as the block chain created for the above-mentioned centralized platform on each member block chain account list.

For example, during implementation, the service configuration information corresponding to the above-mentioned target user services, and the blockchain account list created for the above-mentioned centralized platform on each member blockchain can be specifically stored in the account storage of the above-mentioned target system smart contract. space; for example, the above-mentioned service configuration information and the above-mentioned blockchain account list can be organized in the form of key-value key-value pairs, built into a Merkle tree and stored in the storage medium carried by the node devices in each member blockchain ; Then store the root hash of the Merkle tree in the account structure of the contract account corresponding to the target system smart contract.

Wherein, the above-mentioned service configuration information may specifically include: the identification information (such as the function name) of each contract execution logic combined to generate the above-mentioned target user service, the contract address of each user smart contract containing the above-mentioned contract execution logic, and the deployment of each of the above-mentioned user The correspondence between the blockchain identifiers of each member blockchain of the smart contract.

In this case, the above-mentioned cross-chain calling logic may be specifically composed of the following execution logic: query logic, which is used to query the above-mentioned corresponding relationship in the service configuration information corresponding to the above-mentioned target user service maintained in the above-mentioned target system smart contract, Each contract execution logic of the above-mentioned target user service, each user smart contract including the above-mentioned contract execution logic, and each member blockchain deploying the above-mentioned user smart contracts are generated in a determined combination. And, it can also be used to further query the above-mentioned blockchain account list maintained in the above-mentioned target system smart contract after determining the member blockchains that deploy the above-mentioned user smart contracts, so as to determine the The created blockchain account corresponding to the centralized platform.

Cross-chain logic, which is used to determine based on the query logic, each user smart contract containing the above-mentioned contract execution logic, each member blockchain that deploys the above-mentioned user smart contracts, and the created and According to the logical sequence of the service logic corresponding to the above-mentioned target user services, the information such as the blockchain account corresponding to the centralized platform initiates cross-chain calls for the smart contracts of the above-mentioned users respectively. Among them, the specific implementation details of cross-chain calling user smart contracts deployed on other member blockchains will not be described in detail in this specification, and those skilled in the art can refer to the records in related technologies.

In one embodiment shown, the above service configuration information may also include: based on the logic sequence of the service logic corresponding to the above target user service, the invocation sequence determined for each contract execution logic that is combined to generate the above target user service .

In this case, when invoking the above-mentioned cross-chain logic contained in the above-mentioned target system smart contract, according to the logical order of the service logic corresponding to the above-mentioned target user service, when initiating cross-chain calls for the above-mentioned user smart contracts, the details can be read Take the above call sequence included in the above service configuration information, and then initiate cross-chain calls for the above user smart contracts according to the read above call sequence.

Of course, in practical applications, the logical sequence of the service logic corresponding to the above-mentioned target user service may not be maintained in the above-mentioned target system smart contract as part of the service configuration information, but on the above-mentioned centralized management and control platform.

In this case, when invoking the above-mentioned cross-chain logic contained in the above-mentioned target system smart contract, according to the logical sequence of the service logic corresponding to the above-mentioned target user service, when initiating cross-chain calls for the above-mentioned user smart contracts, it can be specifically related to The above-mentioned centralized management and control platform performs off-chain interaction, reads the logical sequence of the service logic corresponding to the above-mentioned target user service from the above-mentioned centralized management and control platform, and then initiates a cross-connection of the smart contracts for each of the above-mentioned users according to the above-mentioned call sequence read. chain calls.

For example, during implementation, the above-mentioned target system smart contract can specifically interact with the above-mentioned centralized management and control platform through an oracle oracle program, and read the logic of the service logic corresponding to the above-mentioned target user service from the above-mentioned centralized management and control platform order. Among them, the specific implementation details of the above-mentioned target system smart contract interacting with the above-mentioned centralized management and control platform through the oracle oracle program will not be described in detail in this specification, and those skilled in the art can refer to the records in related technologies.

In one embodiment shown, after the centralized management and control platform deploys the target system smart contracts for cross-chain communication on each member blockchain, users of subsequent service providers register on the above-mentioned centralized management and control platform When a new user service is created, the centralized management and control platform can also store the service configuration information corresponding to the newly registered user service in the target system smart contract, so as to update the service configuration information maintained in the target system smart contract.

In one embodiment shown, after the centralized management and control platform deploys the target system smart contract for cross-chain communication on each member blockchain, if the above-mentioned blockchain service network joins a new member area Blockchain, the centralized management and control platform can also store the blockchain account corresponding to the centralized management and control platform created on the new member blockchain into the above target system smart contract, so that the target system smart contract Update the list of blockchain accounts maintained in .

Among them, it should be noted that in practical applications, the centralized management and control platform described above updates the service configuration information maintained in the smart contract of the target system and the list of blockchain accounts. Specifically, real-time updates can be adopted. It can also be updated offline.

On the one hand, if a real-time update method is adopted, whenever a new user service is registered on the above-mentioned centralized management and control platform, the centralized management and control platform can immediately store the service configuration information corresponding to the newly registered user service in the above-mentioned The target system smart contract to update the service configuration information maintained in the target system smart contract.

Correspondingly, whenever the above-mentioned blockchain service network joins a new member blockchain, the centralized management and control platform can immediately transfer the block corresponding to the centralized management and control platform created on the new member blockchain Chain accounts are stored in the target system smart contract to update the list of blockchain accounts maintained in the target system smart contract.

On the other hand, if the offline update method is adopted, each time the target system smart contract is invoked, it can trigger an update of the service configuration information and blockchain account list maintained in the target system smart contract.

In this case, whenever a new user service is registered on the above-mentioned centralized management and control platform, the centralized management and control platform may first cache the service configuration information corresponding to the newly registered user service. When the target system smart contract is invoked, the cached service configuration information is stored in the target system smart contract, so as to update the service configuration information maintained in the target system smart contract. Correspondingly, whenever a new member blockchain is added to the above-mentioned blockchain service network, the centralized management and control platform can also first transfer the block corresponding to the centralized management and control platform created on the new member blockchain to The chain account is cached. When the target system smart contract is invoked, the cached blockchain account is stored in the target system smart contract to update the list of blockchain accounts maintained in the target system smart contract.

For example, when implementing, the execution logic of data synchronization can be introduced into the above-mentioned target system smart contract, so that each time the above-mentioned target system smart contract is called, the execution logic of data synchronization can be run first to serve with the centralized management and control platform Data synchronization of configuration information and blockchain account list, based on the service configuration information and blockchain accounts cached by the centralized management and control platform, update the service configuration information and blockchain account list maintained in the smart contract of the target system, and then Continue to execute the contract execution logic that is called this time.

In one embodiment shown, when the above-mentioned centralized management and control platform deploys the above-mentioned target user service, the above-mentioned user service can also be centrally deployed on the above-mentioned centralized management and control platform in the form of a service interface for service use party calls.

Wherein, the calling method related to the above-mentioned target user service may be included in the service interface (for example, the calling method may specifically be in the form of an interface function), and the calling logic corresponding to these calling methods may specifically include: determining a combination to generate the target user service Each user smart contract corresponding to the execution logic of each contract, and each member blockchain that deploys the above-mentioned user smart contracts, and based on the blockchain accounts corresponding to the centralized management and control platform created in the above-mentioned member blockchains, In accordance with the logical order of the service logic corresponding to the above-mentioned target user services, respectively initiate cross-chain calls for the smart contracts of each of the above-mentioned users.

In this case, when the service user needs to call the above-mentioned target user service that has been registered on the above-mentioned centralized management and control platform, it can initiate a call request for the above-mentioned service interface to call the above-mentioned target user service.

After receiving the call request for the above service interface, the centralized management and control platform can respond to the call request and execute the above call method contained in the service interface to determine the execution logic of each contract corresponding to the combined generation of the target user service. User smart contracts, and each member blockchain that deploys the above-mentioned user smart contracts, and based on the blockchain accounts corresponding to the centralized management and control platform created in the above-mentioned member blockchains, according to the corresponding target user services The logical order of the service logic is to initiate cross-chain calls for the above-mentioned user smart contracts, and then summarize the call results of the cross-chain calls for the above-mentioned user smart contracts, and return the above-mentioned call results to the above-mentioned service users.

For example, in one example, the service configuration information corresponding to the above-mentioned target user service described in the above embodiment, and the block chain account list created for the above-mentioned centralized platform on each member block chain can be specifically maintained in the above-mentioned center For example, in practical applications, the above-mentioned service configuration information and the above-mentioned blockchain account list can be written into the above-mentioned service interface in the form of call parameters related to the service interface.

Correspondingly, the invocation logic corresponding to the invocation method related to the above-mentioned target user service contained in the above-mentioned service interface may specifically include: query logic for querying the above-mentioned corresponding relationship in the above-mentioned service configuration information, so as to determine the combined generation of the above-mentioned target user. Each contract execution logic of the service, each user smart contract containing the above-mentioned contract execution logic, and each member blockchain deploying the above-mentioned user smart contracts. And, after determining the member blockchains that deploy the above-mentioned user smart contracts, further query the above-mentioned blockchain account list to determine the blockchain corresponding to the centralized platform created on the above-mentioned member blockchains account.

Cross-chain logic, which is used to query the blockchain accounts corresponding to the centralized platform created on the above-mentioned member blockchains according to the above-mentioned query logic, and initiate respectively according to the logical order of the service logic corresponding to the above-mentioned target user services Cross-chain calls for the above-mentioned user smart contracts.

In another example, the above-mentioned service configuration information maintained by the centralized management and control platform may also include: based on the logic sequence of the service logic corresponding to the above-mentioned target user service, the contract execution logic determined for the combination of the above-mentioned target user service call sequence.

In this case, when the above-mentioned cross-chain logic initiates cross-chain calls for the above-mentioned user smart contracts according to the logical sequence of the service logic corresponding to the above-mentioned target user service, the above-mentioned call can be read from the above-mentioned service configuration information. order, and then initiate cross-chain calls for the smart contracts of each user above in accordance with the read order of the above calls.

Please refer to Fig. 4, Fig. 4 is a flowchart of a service registration method for registering user services on a centralized management and control platform according to an exemplary embodiment of this specification, and the method is applied to the centralized management and control platform shown in Fig. 1 The method includes: step 401, receiving a user service registration request initiated by a service provider; the above-mentioned service provider may specifically be a user who has a service requirement for registering user services on the centralized management and control platform. Users of the service provider can combine the contract execution logic contained in the user smart contracts deployed on each member blockchain according to their own service requirements to generate user services, and then register the user services to the centralized Control platform.

Wherein, it should be noted that the user of the above-mentioned service provider may specifically be a user who has registered a blockchain account on any member blockchain on the above-mentioned blockchain service network. That is to say, the user of the service provider may specifically be a user member belonging to a certain member blockchain in the above-mentioned blockchain service network.

In this case, the user of the service provider can combine the contract execution logic contained in the smart contract deployed on the member blockchain with the contract execution logic contained in the user smart contract deployed on other member blockchains according to their own service needs. The included contract execution logic is combined to generate user services, and then register the user services to the centralized management and control platform.

Of course, in practical applications, the user of the above-mentioned service provider may also be a user who has not registered a blockchain account on each member blockchain on the above-mentioned blockchain service network, but a user in the above-mentioned center A user who has registered a user account on the management and control platform; that is, the user of the above-mentioned service provider is a user member who does not belong to any member blockchain in the above-mentioned blockchain service network, but belongs to the above-mentioned centralized A user member of the management platform. For example, the user of the above-mentioned service provider may specifically be a platform administrator who has registered an administrator account on the centralized management and control platform.

In this case, the users of the above-mentioned service providers can, based on their own overall understanding of the deployment of user smart contracts on each member blockchain, and then according to their own service needs, deploy the smart contracts deployed on each member blockchain The contract execution logic contained in the user smart contract is freely combined to generate user services, and then register the user services to the centralized management and control platform.

When users of the above-mentioned service provider register user services on the centralized management and control platform, it can specifically be completed through a user client docked with the above-mentioned centralized management and control platform. Users of the above-mentioned service provider can initiate a service registration request to the above-mentioned centralized management and control platform by performing a service registration operation on the above-mentioned user client, so that the above-mentioned centralized management and control platform can respond to the service registration request, and on the above-mentioned centralized management and control platform Sign up for user services.

Step 402, in response to the user service registration request, determine a contract execution logic set for realizing the service function corresponding to the user service; the contract execution logic set includes user smart contracts deployed on each member blockchain Included contract execution logic; when the above-mentioned centralized management and control platform receives the user service registration request initiated by the user of the above-mentioned service provider, it can respond to the user service registration request to determine the user’s need to register for the implementation of the service provider. The contract execution logic set of the service function corresponding to the user service; wherein, the contract execution logic set includes the contract execution logic contained in the user smart contract deployed on each member blockchain.

For example, as mentioned above, at least part of the contract execution logic in the contract execution logic that is combined to generate the above user services may correspond to user smart contracts deployed on different member blockchains. In this case, at least part of the contract execution logic in the contract execution logic set may be the contract execution logic contained in user smart contracts on different member blockchains. Of course, in practical applications, at least part of the contract execution logic in the contract execution logic that generates the above-mentioned user services can also be derived from the contract execution logic contained in multiple user smart contracts in the same member blockchain; or , can also be derived from multiple contract execution logic contained in the same user smart contract in the same member blockchain. In this case, at least part of the contract execution logic in the contract execution logic set can also be derived from the contract execution logic contained in multiple user smart contracts in the same member blockchain; or, it can also be derived from The multiple contract execution logic contained in the same user smart contract in the same member blockchain is not specifically limited in this specification.

In one embodiment shown, the centralized management and control platform can support the registration of the contract execution logic included in the user smart contracts deployed on each member blockchain on the centralized management and control platform. Correspondingly, the user services registered on the centralized management and control platform can be services generated by combining at least one contract execution logic registered on the centralized management and control platform.

In this case, when the above-mentioned centralized management and control platform responds to the above-mentioned user service registration request to determine the contract execution logic set for realizing the service function corresponding to the user service that the user of the above-mentioned service provider needs to register, then specifically, it can be obtained from the above-mentioned In the contract execution logic registered on the centralized management and control platform, the contract execution logic set used to realize the service function corresponding to the user service is determined.

In one embodiment shown, the centralized management and control platform can output the registered contract execution logic to the user of the service provider through the visual interface on the above-mentioned business user client, so that the centralized management and control platform will The access rights of the registered contract execution logic are open to the users of the service provider.

The users of the service provider can select at least one registered contract execution logic from the above-mentioned visual interface based on their own service requirements, and carry the identification information (such as the function name) corresponding to the selected contract execution logic in the above-mentioned user service registration request, and then send the service registration request to the above-mentioned centralized management and control platform.

In this case, the above-mentioned centralized management and control platform, in response to the above-mentioned user service registration request, determines the contract execution for realizing the service function corresponding to the user service from the contract execution logic registered on the above-mentioned centralized management and control platform. In logic collection, specifically, the above-mentioned identification information carried in the user service registration request can be obtained, and then at least one contract execution logic corresponding to the above-mentioned identification information in the registered contract execution logic can be determined as the corresponding one for realizing the above-mentioned user service A collection of contract execution logic for service functions.

In another illustrated implementation manner, the user of the above-mentioned service provider may define service logic for the above-mentioned user services that need to be registered based on their own service requirements. In the above-mentioned user service registration request, it is also possible not to carry the identification information corresponding to at least one registered contract execution logic selected from the above-mentioned visual interface, but to carry the service logic related to the service logic defined by the user of the service provider for the above-mentioned user service Description. For example, the description information may specifically be a function description related to the user service that the user needs to register.

In this case, the above-mentioned centralized management and control platform, in response to the above-mentioned user service registration request, determines the contract execution for realizing the service function corresponding to the user service from the contract execution logic registered on the above-mentioned centralized management and control platform. In logic collection, the registered contract execution logic can be matched with the service logic indicated by the description information; and then according to the matching result, the registered contract execution logic can be matched with the service logic indicated by the description information. At least one contract execution logic that matches the logic is determined as a set of contract execution logic for realizing the service function corresponding to the above user service.

In this way, users of the service provider can only submit description information related to the service logic corresponding to the user service that needs to be registered to the centralized management and control platform without knowing the service logic corresponding to each registered contract execution logic , the centralized management and control platform can find the set of contract execution logic that can be combined to generate the above user services from the registered contract execution logic through logical matching, so that some service logics that execute logic for each registered contract Users who don't know much can also independently register new user services on the centralized management and control platform based on their own service needs, which can improve the convenience of registering user services on the centralized management and control platform.

Step 403, combine the contract execution logic in the contract execution logic set to generate the user service, so as to complete the service registration of the user service.

After the above-mentioned centralized management and control platform determines the contract execution logic set used to realize the service functions corresponding to the above-mentioned user services from the contract execution logic registered on the above-mentioned centralized management and control platform, the above-mentioned contract execution logic set can be The contract execution logic is combined to generate the above user services to complete the service registration of the above user services.

In one embodiment shown, the above-mentioned centralized management and control platform can assign a service identifier to the user of the service provider, and then combine the contract execution logic in the above-mentioned contract execution logic set to generate a contract execution logic combination, and then Bind the contract execution logic combination with the above service identifier to complete the service registration for the above user service.

For example, during implementation, the contract execution logic in the above contract execution logic set can be combined in accordance with the logical sequence of the service logic defined by the user of the service provider for the above user service to obtain the contract execution logic combination, and then the The contract execution logic combination is bound to the above-mentioned service identifier to complete the service registration for the above-mentioned user service.

In one embodiment shown, after the service registration of the above-mentioned user service is completed, the centralized management and control platform can generate corresponding service configuration information for the registered user service, and store the service generated for the user service locally configuration information.

For example, during implementation, on the centralized management and control platform, an information base for storing the service configuration information corresponding to the registered user service can be maintained. When a new user service is registered, the new user service can be The service configuration information generated by the service is associated with the service identifier assigned to the new user service and stored in the information base.

Wherein, the specific content of the above-mentioned service configuration information is not particularly limited in this specification; for example, it may include: the identification information of each contract execution logic that combines and generates the above-mentioned user services, and each user smart contract containing the above-mentioned contract execution logic The corresponding relationship between the contract address of , and the blockchain identification of each member blockchain that deploys the above-mentioned user smart contracts, and so on.

In this specification, in addition to supporting the registration of user services generated by the contract execution logic combination contained in the user smart contracts deployed on each member blockchain, the above-mentioned centralized management and control platform can also support user services generated by At least one user service composition that has registered generates a service solution.

Please refer to Fig. 5. Fig. 5 is a flowchart of a service registration method for registering a service solution on a centralized management and control platform according to an exemplary embodiment of this specification. This method can also be applied to the center shown in Fig. 1 a centralized management and control platform; the method includes: step 501, receiving a solution registration request initiated by a service provider; wherein, the above-mentioned service solution specifically refers to performing at least one user service that has been registered on the above-mentioned centralized management and control platform A solution with more complex service capabilities generated after combination.

When users of the above-mentioned service provider register user services on the centralized management and control platform, it can also be done through a user client docked with the above-mentioned centralized management and control platform. Users of the above-mentioned service provider can initiate a solution registration request to the above-mentioned centralized management and control platform by performing a service registration operation on the above-mentioned user client, so that the above-mentioned centralized management and control platform can respond to the solution registration request, and in the above-mentioned centralized management and control Register service solutions on the platform.

Step 502, in response to the solution registration request, determine from the registered user services the set of user services used to realize the service functions corresponding to the service solution; When a user initiates a solution registration request, the user service set for implementing the service function corresponding to the service solution that the user of the service provider needs to register may be determined in response to the solution registration request.

In one embodiment shown, the above-mentioned centralized management and control platform can output the registered user services to the user of the service provider through the visual interface, so that the user of the service provider can select in the visual interface for combination Generate at least one user service of the above service solution. Correspondingly, the above-mentioned solution registration request may carry the identification information corresponding to the above-mentioned at least one user service selected by the user of the service provider, and the above-mentioned centralized management and control platform responds to the above-mentioned solution registration request. When determining the set of user services used to implement the service functions corresponding to the service solution among the registered user services, you can specifically obtain the above identification information carried in the solution registration request, and then combine the registered user services with the The at least one user service corresponding to the above identification information is determined as a user service set for realizing the service function corresponding to the above service solution.

In another embodiment shown, the user of the above-mentioned service provider may also define a service logic for the above-mentioned service solution that needs to be registered based on his own service requirements. In the above-mentioned solution registration request, it is also possible not to carry the identification information corresponding to at least one registered user service selected from the above-mentioned visual interface, but to carry the service logic-related information defined by the user of the service provider for the above-mentioned service solution. Description. For example, the description information may specifically be a function description related to the service solution that the user needs to register.

In this case, the above-mentioned centralized management and control platform, in response to the above-mentioned solution registration request, determines the user service for realizing the service function corresponding to the service solution from the user services registered on the above-mentioned centralized management and control platform. When gathering, specifically, the service logic corresponding to the registered user service can be matched with the service logic indicated by the description information; and then according to the matching result, the registered user service and the service logic indicated by the description information can be matched. At least one user service matching the service logic is determined as a user service set for realizing the service function corresponding to the above service solution.

Step 503: Combine the user services in the user service set to generate the service solution, so as to complete the service registration of the service solution.

After the above-mentioned centralized management and control platform determines the user service set used to realize the service function corresponding to the above-mentioned service solution from the user services registered on the above-mentioned centralized management and control platform, the user service set in the above-mentioned user service set can be Combine to generate the above service solutions, so as to complete the registration of the above service solutions.

In one embodiment shown, the above-mentioned centralized management and control platform can assign a scheme identifier to the user of the service provider, and then combine the user services in the above-mentioned user service set to generate a user service combination, and then the user The service combination is bound with the above-mentioned solution ID to complete the service registration for the above-mentioned service solution.

For example, during implementation, the user services in the above user service set can be combined according to the logical order of the service logic defined by the user of the service provider for the above service solution to obtain a user service combination, and then the user service The combination is bound with the above-mentioned solution ID to complete the registration for the above-mentioned service solution.

In one embodiment shown, after the service registration of the above-mentioned service solution is completed, the centralized management and control platform can generate corresponding service configuration information for the registered service solution, and store it locally as the service solution Generated service configuration information.

For example, during implementation, on the centralized management and control platform, an information base for storing the service configuration information corresponding to the registered service solution can be maintained. When a new service solution is registered, the new service solution can be The service configuration information generated by the new service solution is associated with the service identification allocated for the new service solution and stored in the information base.

Wherein, the specific content of the above-mentioned service configuration information is not particularly limited in this specification; for example, it may include: combining and generating the service identification of each user service of the above-mentioned service solution, and combining and generating each contract execution logic of the above-mentioned user service Identification information, the contract address of each user smart contract containing the execution logic of each contract, and the corresponding relationship between the block chain identifiers of each member block chain that deploys the above-mentioned user smart contracts, and so on.

In this manual, when the user of the service provider registers the user service on the above-mentioned centralized management and control platform, the centralized management and control platform can specifically deploy the registered user service as a standardized service to open it to the service user to make the call.

Among them, when the centralized management and control platform deploys registered user services, it can be deployed centrally on the centralized management and control platform in the form of a service interface, or in the form of a system smart contract, distributed in each member area on the block chain.

Please refer to FIG. 6. FIG. 6 is a flow chart of a method for using services for user services registered on a centralized management and control platform according to an exemplary embodiment of this specification. This method can also be applied to the method shown in FIG. 1 A centralized management and control platform; wherein, a service interface corresponding to the registered user service is deployed on the centralized management and control platform; the method includes: step 601, obtaining a call request for the service interface initiated by a service user; The user service registered on the above-mentioned centralized management and control platform can be deployed on the above-mentioned centralized management and control platform in the form of a service interface. The service user who has the invocation requirements of the above-mentioned user services can call the user services centrally deployed on the above-mentioned centralized management and control platform by initiating a call request for the above-mentioned service interface.

Wherein, the above-mentioned service user may specifically be a user having a calling requirement of the above-mentioned user service, or a business system having a calling requirement of the above-mentioned user service, which is not specifically limited in this description.

Step 602, in response to the call request, determine the user smart contracts corresponding to the contract execution logics that are combined to generate the user services, and the member blockchains that deploy the user smart contracts.

Step 603: Based on the blockchain accounts corresponding to the centralized management and control platform created in the member blockchains, respectively initiate cross-chain calls for the smart contracts of the users to complete the service for the users service call.

Wherein, the above-mentioned service interface may specifically include a calling method related to the above-mentioned user service; for example, in practical applications, the calling method included in the above-mentioned service interface may specifically be in the form of an interface function. The invocation logic corresponding to these invocation methods may specifically include: determining each user smart contract corresponding to the execution logic of each contract that is combined to generate user services, and deploying each member block chain of each user smart contract above, and based on the above-mentioned member blocks The blockchain account corresponding to the centralized management and control platform created in the chain respectively initiates cross-chain calls for the above-mentioned user smart contracts.

After the centralized management and control platform receives the call request from the user of the above-mentioned service user for the above-mentioned service interface, it can respond to the call request and execute the above-mentioned call method contained in the service interface to determine the combined generation of each contract of the user service. Each user smart contract corresponding to the execution logic, and each member blockchain that deploys the above-mentioned user smart contracts, and based on the blockchain account corresponding to the centralized management and control platform created in each of the above member blockchains, respectively initiates a target The cross-chain calls of the above-mentioned user smart contracts.

In one embodiment shown, the service configuration information corresponding to the registered user service can be maintained on the above-mentioned centralized management and control platform, as well as the blockchain account created for the above-mentioned centralized platform on each member blockchain. list; for example, in practical applications, the above-mentioned service configuration information and the above-mentioned blockchain account list can be written into the above-mentioned service interface in the form of invocation parameters related to the service interface.

Correspondingly, the invocation logic corresponding to the invocation method related to the above-mentioned target user service contained in the above-mentioned service interface may specifically include: query logic, querying the above-mentioned corresponding relationship in the above-mentioned service configuration information, so as to determine the combined generation of the above-mentioned target user service. Each contract execution logic, each user smart contract containing the above-mentioned contract execution logic, and each member blockchain deploying the above-mentioned user smart contracts. And, after determining the member blockchains that deploy the above-mentioned user smart contracts, further query the above-mentioned blockchain account list to determine the blockchain corresponding to the centralized platform created on the above-mentioned member blockchains account.

Cross-chain logic, according to the above-mentioned query logic, the blockchain accounts corresponding to the centralized platform created on the above-mentioned member blockchains are queried, and the cross-chain calls for the smart contracts of the above-mentioned users are respectively initiated.

In one embodiment shown, the above-mentioned user service may also be at least one contract execution logic included in the user smart contract deployed on each member blockchain, according to the service logic corresponding to the user service Services that are combined in a logical order.

In this case, when the above-mentioned cross-chain logic initiates cross-chain calls for the above-mentioned user smart contracts based on the blockchain accounts corresponding to the centralized platform created on the above-mentioned member blockchains, it can specifically According to the blockchain accounts corresponding to the centralized platform created on the above-mentioned member blockchains, and in accordance with the above-mentioned logical order, respectively initiate cross-chain calls for the above-mentioned user smart contracts.

In one embodiment shown, the above-mentioned service configuration information maintained by the centralized management and control platform may also include: based on the logical order of the service logic corresponding to the above-mentioned user services, the execution logic of each contract for the combination of the above-mentioned user services is determined. The call sequence information that comes out. Correspondingly, when the above-mentioned cross-chain logic initiates cross-chain calls for the above-mentioned user smart contracts in accordance with the logical sequence of the service logic corresponding to the above-mentioned user services, the above-mentioned call sequence can be read from the above-mentioned service configuration information, and then according to The read-out of the above-mentioned call sequence initiates cross-chain calls for the smart contracts of each of the above-mentioned users respectively.

After the centralized management and control platform completes the cross-chain calls for the above-mentioned user smart contracts by calling the above-mentioned service interface, it can further summarize the call results of the cross-chain calls for the above-mentioned user smart contracts, and use the above-mentioned call results as the The call result of the user service is returned to the above service user.

Please refer to FIG. 7. FIG. 7 is a flowchart of another method for using services for user services registered on a centralized management and control platform according to an exemplary embodiment of this specification. This method can be applied to the method shown in FIG. 1 A node device in any target member blockchain in the blockchain service network. Among them, at least one system smart contract issued by the centralized management and control platform is deployed on each member blockchain in the above-mentioned blockchain service network; The target system smart contract of chain communication; the target system smart contract includes the cross-chain call logic corresponding to the user service registered on the centralized management and control platform; the method includes: step 701, obtaining the target The call data of the user service; the user service registered on the above-mentioned centralized management and control platform can be deployed on the above-mentioned centralized management and control platform in the form of the above-mentioned system smart contract. The service user who has the call requirements of the above-mentioned user services can call the above-mentioned user services decentralized and deployed on each member blockchain by initiating a contract call for the above-mentioned target system smart contract.

Among them, the user of the above-mentioned service can be a user who has the call requirement of the above-mentioned user service, or a user smart contract deployed on any member blockchain with the call requirement of the above-mentioned user service. In this specification Not particularly limited.

For example, in one case, if the above-mentioned service user is a user who needs to call the above-mentioned user service, the user may specifically be a user who has registered a blockchain account on the above-mentioned target member blockchain. The user can initiate a contract call for the above-mentioned target system smart contract deployed on the target member blockchain based on the blockchain account registered on the target member blockchain, so as to complete the service call for the above-mentioned user service.

In another case, if the user of the above service is a target user smart contract deployed on the target member blockchain, the contract execution logic contained in the target user smart contract can be embedded with the above user service. set of calling relationships; for example, the contract execution logic contained in the target user smart contract refers to the user service registered on the centralized management and control platform. In this case, in the process of executing the included contract execution logic, the target user smart contract can further initiate a contract call for the above-mentioned target system smart contract through nested calls between smart contracts.

Correspondingly, the specific content of the above invocation data usually depends on the specific type of the above service user; for example, if the above service user is a user who needs to call the above user service, the above invocation data can specifically be The user initiates a contract call transaction for calling the above target system contract initiated by the blockchain account registered in the above target member blockchain.

If the above-mentioned service user is a target user smart contract deployed on the above-mentioned target member blockchain, at this time, the above-mentioned call data can specifically be that when the above-mentioned target user smart contract calls the above-mentioned target system smart contract, the target user smart contract The call message for the above-mentioned user service sent by the contract to the above-mentioned target system smart contract.

For example, in practical applications, mutual calls between smart contracts usually adopt the method of "message call". When a smart contract needs to call other smart contracts, it will send a call message to the other smart contracts. Therefore, in this specification, when the above-mentioned target user smart contract calls the above-mentioned target system smart contract, this method of "message call" can also be used specifically, by sending a call message to the above-mentioned target system smart contract to initiate a call for the above-mentioned The contract call of the target system smart contract.

It should be noted that when a certain smart contract uses the method of "message call" to call other smart contracts, after the call is completed, the other smart contract will return the call result to the smart contract that sent the call message to trigger the smart contract. The contract continues to execute the next contract execution logic based on the call result.

Step 702, in response to the call data, call the cross-chain call logic contained in the target system smart contract, determine the user smart contracts corresponding to the contract execution logics that combine to generate the user service, and deploy the various user smart contracts. Member blockchains of user smart contracts.

Step 703: Based on the blockchain accounts corresponding to the centralized management and control platform created in the member blockchains, respectively initiate cross-chain calls for the smart contracts of the users to complete the service for the users service call.

At least one system smart contract issued by the centralized management and control platform can be deployed on the above-mentioned target member blockchain; the above-mentioned at least one system smart contract can specifically include the target system smart contract for cross-chain communication with other member blockchains . Among them, the target system smart contract may specifically include cross-chain call logic corresponding to the above-mentioned user services.

For example, because the contract call logic that makes up the above user services may include contract execution logic contained in multiple user smart contracts deployed on multiple member blockchains, users may also need to call across chains when calling the above user services Multiple user smart contracts distributed on multiple member blockchains; therefore, when the above-mentioned centralized management and control platform deploys the above-mentioned user services, it can specifically develop corresponding cross-chain call logic for the user service, and then call the cross-chain As the contract execution logic of the above-mentioned system smart contract, the logic is deployed on the above-mentioned target member blockchain.

The cross-chain call logic can be specifically used to: determine the user smart contracts corresponding to the execution logic of the contracts generated by the user service, and deploy the member blockchains of the above user smart contracts, and based on the above-mentioned member blocks The blockchain account created in the chain corresponding to the centralized management and control platform initiates cross-chain calls for the above-mentioned user smart contracts in accordance with the logical order of the service logic corresponding to the above-mentioned target user services.

In this way, in this way, the service user can independently call the above-mentioned cross-chain call logic contained in the target system smart contract, and the above-mentioned target users who have registered on the centralized management and control platform The service initiates the call.

When the node device on the above-mentioned target member blockchain receives the calling data initiated by the service user, it can respond to the calling data, call the above-mentioned cross-chain calling logic contained in the smart contract of the above-mentioned target system, and determine the combination to generate the user service. Each user smart contract corresponding to the contract execution logic, and each member blockchain that deploys the above-mentioned user smart contracts, and based on the blockchain account corresponding to the centralized management and control platform created in each of the above member blockchains, according to the The logical sequence of the service logic corresponding to the above-mentioned target user services initiates cross-chain calls for the smart contracts of each of the above-mentioned users respectively.

For example, in one case, if the above-mentioned service user is a user who needs to call the above-mentioned user service, the user may specifically be a user who has registered a blockchain account on the above-mentioned target member blockchain. The above invocation data may specifically be a contract invocation transaction for the above target system smart contract packaged by the user through the blockchain account registered on the target member blockchain. After the above-mentioned node device receives the contract call transaction, it can respond to the contract call transaction and further call the above-mentioned cross-chain call logic contained in the above-mentioned target system smart contract.

In another case, if the user of the above service is a target user smart contract deployed on the target member blockchain, the contract execution logic contained in the target user smart contract can be embedded with the above user service. Set of calling relations. In this case, the above invocation data may specifically be an invocation message sent by the target user smart contract to the above target system smart contract. After receiving the call message, the above-mentioned node device can respond to the call message and further call the above-mentioned cross-chain call logic contained in the above-mentioned target system smart contract.

In one embodiment shown, in the above-mentioned target system smart contract, the service configuration information corresponding to the above-mentioned user service and the blockchain account created for the above-mentioned centralized platform on each member blockchain can also be maintained list.

For example, during implementation, the service configuration information corresponding to the above-mentioned user services, and the list of blockchain accounts created for the above-mentioned centralized platform on each member blockchain can be specifically stored in the account storage space of the above-mentioned target system smart contract For example, the above-mentioned service configuration information and the above-mentioned blockchain account list can be organized in the form of key-value key-value pairs, constructed as a Merkle tree and stored in the storage medium carried by the node devices in each member blockchain; Then store the root hash of the Merkle tree in the account structure of the contract account corresponding to the target system smart contract.

Wherein, the above-mentioned service configuration information may specifically include: the identification information (such as the function name) of each contract execution logic combined to generate the above-mentioned user service, the contract address of each user smart contract containing the above-mentioned contract execution logic, and the deployment of each of the above-mentioned user smart contracts. The correspondence between the blockchain identifiers of each member blockchain of the contract.

In this case, the above-mentioned cross-chain call logic may specifically consist of the following execution logic: query logic, used to query the above-mentioned corresponding relationship in the service configuration information corresponding to the above-mentioned user service maintained in the above-mentioned target system smart contract, and Determine the combination of each contract execution logic for generating the above user services, each user smart contract containing the above each contract execution logic, and each member block chain that deploys the above each user smart contract. And, it can also be used to further query the above-mentioned blockchain account list maintained in the above-mentioned target system smart contract after determining the member blockchains that deploy the above-mentioned user smart contracts, so as to determine the The created blockchain account corresponding to the centralized platform.

Cross-chain logic, which is used to determine based on the query logic, each user smart contract containing the above-mentioned contract execution logic, each member blockchain that deploys the above-mentioned user smart contracts, and the created and Information such as the blockchain account corresponding to the centralized platform initiates cross-chain calls for the above-mentioned user smart contracts. Among them, the specific implementation details of cross-chain calling user smart contracts deployed on other member blockchains will not be described in detail in this specification, and those skilled in the art can refer to the records in related technologies.

In this case, when the node device on the target member blockchain receives the call data initiated by the service user, it can respond to the call data, call the above query logic contained in the target system smart contract, and query the above correspondence , to determine the combination to generate each contract execution logic of the above-mentioned user services, each user smart contract containing the above-mentioned contract execution logic, and each member blockchain deploying the above-mentioned user smart contracts. And, further query the above-mentioned block chain account list to determine the block chain accounts corresponding to the centralized platform created on the above-mentioned member block chains. Then, the above-mentioned cross-chain logic contained in the above-mentioned target system smart contract can be further invoked, and based on the above-mentioned determined blockchain account, respectively initiate cross-chain calls for the smart contracts of each user.

In one embodiment shown, the above-mentioned user service may also be at least one contract execution logic included in the user smart contract deployed on each member blockchain, according to the service logic corresponding to the user service Services that are combined in a logical order.

In this case, the above-mentioned cross-chain logic is specifically used for: the user smart contracts that contain the execution logic of the above-mentioned contracts determined based on the query logic, the member blockchains that deploy the above-mentioned user smart contracts, and the Information such as the blockchain accounts corresponding to the centralized platform created on the member blockchains, respectively initiate cross-chain calls for the above-mentioned user smart contracts in accordance with the above logical order.

Correspondingly, when the above-mentioned node device calls the above-mentioned cross-chain logic included in the above-mentioned target system smart contract, and based on the above-mentioned determined blockchain accounts, when respectively initiating cross-chain calls for the user smart contracts, it can specifically be based on the determined According to the above logical sequence, the above-mentioned blockchain accounts of , respectively initiate cross-chain calls for the smart contracts of each of the above-mentioned users.

In an illustrated embodiment, the above service configuration information may also include: based on the logical sequence of the service logic corresponding to the above target user service, the call determined for each contract execution logic that is combined to generate the above target user service order.

The above-mentioned cross-chain logic is specifically used to: read the above-mentioned call sequence included in the above-mentioned service configuration information, determine based on the query logic, each user smart contract containing the above-mentioned contract execution logic, and each member area where the above-mentioned user smart contracts are deployed Block chains, and information such as the blockchain accounts corresponding to the centralized platform created on the above-mentioned member blockchains, respectively initiate cross-chain calls for the above-mentioned user smart contracts according to the above-mentioned logical sequence read.

Correspondingly, when the above-mentioned node device invokes the above-mentioned cross-chain logic included in the above-mentioned target system smart contract, based on the above-mentioned determined blockchain account, and according to the above-mentioned logic sequence, when respectively initiating cross-chain calls for the smart contracts of each user, Specifically, the above-mentioned call sequence included in the above-mentioned service configuration information can be read, and then based on the above-mentioned determined blockchain account, according to the read above-mentioned logic sequence, respectively initiate cross-chain calls for the above-mentioned user smart contracts.

Of course, in practical applications, the logical sequence of the service logic corresponding to the above-mentioned target user service may not be maintained in the above-mentioned target system smart contract as part of the service configuration information, but on the above-mentioned centralized management and control platform.

In this case, when invoking the above-mentioned cross-chain logic contained in the above-mentioned target system smart contract, according to the logical sequence of the service logic corresponding to the above-mentioned target user service, when initiating cross-chain calls for the above-mentioned user smart contracts, it can be specifically related to The above-mentioned centralized management and control platform performs off-chain interaction, reads the logical sequence of the service logic corresponding to the above-mentioned target user service from the above-mentioned centralized management and control platform, and then initiates a cross-connection of the smart contracts for each of the above-mentioned users according to the above-mentioned call sequence read. chain calls.

For example, during implementation, the above-mentioned target system smart contract can interact with the above-mentioned centralized management and control platform outside the chain through another oracle oracle program, and read the service logic corresponding to the above-mentioned target user service from the above-mentioned centralized management and control platform. logical order. Among them, the specific implementation details of the above-mentioned target system smart contract interacting with the above-mentioned centralized management and control platform through the oracle oracle program will not be described in detail in this specification, and those skilled in the art can refer to the records in related technologies.

In one embodiment shown, after the centralized management and control platform deploys the target system smart contracts for cross-chain communication on each member blockchain, users of subsequent service providers register on the above-mentioned centralized management and control platform When a new user service is created, the centralized management and control platform can also store the service configuration information corresponding to the newly registered user service in the target system smart contract, so as to update the service configuration information maintained in the target system smart contract.

In one embodiment shown, after the centralized management and control platform deploys the target system smart contract for cross-chain communication on each member blockchain, if the above-mentioned blockchain service network joins a new member area Blockchain, the centralized management and control platform can also store the blockchain account corresponding to the centralized management and control platform created on the new member blockchain into the above target system smart contract, so that the target system smart contract Update the list of blockchain accounts maintained in .

Among them, it should be noted that in practical applications, the centralized management and control platform described above updates the service configuration information maintained in the smart contract of the target system and the list of blockchain accounts. Specifically, real-time updates can be adopted. It can also be updated offline.

On the one hand, if a real-time update method is adopted, whenever a new user service is registered on the above-mentioned centralized management and control platform, the centralized management and control platform can immediately store the service configuration information corresponding to the newly registered user service in the above-mentioned The target system smart contract to update the service configuration information maintained in the target system smart contract.

Correspondingly, whenever the above-mentioned blockchain service network joins a new member blockchain, the centralized management and control platform can immediately transfer the block corresponding to the centralized management and control platform created on the new member blockchain Chain accounts are stored in the target system smart contract to update the list of blockchain accounts maintained in the target system smart contract.

On the other hand, if the offline update method is adopted, each time the target system smart contract is invoked, it can trigger an update of the service configuration information and blockchain account list maintained in the target system smart contract.

In this case, whenever a new user service is registered on the above-mentioned centralized management and control platform, the centralized management and control platform may first cache the service configuration information corresponding to the newly registered user service. When the target system smart contract is invoked, the cached service configuration information is stored in the target system smart contract, so as to update the service configuration information maintained in the target system smart contract. Correspondingly, whenever a new member blockchain is added to the above-mentioned blockchain service network, the centralized management and control platform can also first transfer the block corresponding to the centralized management and control platform created on the new member blockchain to The chain account is cached. When the target system smart contract is invoked, the cached blockchain account is stored in the target system smart contract to update the list of blockchain accounts maintained in the target system smart contract.

For example, when implementing, the execution logic of data synchronization can be introduced into the above-mentioned target system smart contract, so that each time the above-mentioned target system smart contract is called, the execution logic of data synchronization can be run first to serve with the centralized management and control platform Data synchronization of configuration information and blockchain account list, based on the service configuration information and blockchain accounts cached by the centralized management and control platform, update the service configuration information and blockchain account list maintained in the smart contract of the target system, and then Continue to execute the contract execution logic that is called this time.

In one embodiment shown, in addition to supporting the registration of the above-mentioned user services, the above-mentioned centralized management and control platform can also support, on the above-mentioned centralized management and control platform, as the user of the above-mentioned services deployed on each member block chain The user smart contract registers the associated user service.

When the above-mentioned service user is a target user smart contract deployed on the target member blockchain, at this time, the deployer or manager of the target user smart contract can send the user smart contract registration request to the centralized management and control platform. way, register the associated user service for the target user smart contract. Wherein, in the user smart contract registration request, specifically, the contract address of the above-mentioned target user smart contract and the service identifier of the target user service that needs to be associated with the target user smart contract can be carried.

When the centralized management and control platform receives the user smart contract registration request sent by the deployment party or management party of the target user smart contract, it can respond to the user smart contract registration request and read the target user service information carried in the user smart contract registration request. The service ID of the target user and the contract address of the target user’s smart contract, and then create an association between the service ID of the target user’s service and the contract address of the target user’s smart contract, and store the association on the centralized management and control platform .

In this case, the invocation data for the above user service may specifically be an invocation message for the above user service submitted by the above target user smart contract to the above target system smart contract. In response to the above-mentioned call message, the above-mentioned node device can first determine whether the user service has been registered as a user service associated with the above-mentioned target user smart contract before invoking the above-mentioned cross-chain call logic contained in the above-mentioned target system smart contract; for example, in an example , the above-mentioned association relationship may be specifically maintained in the above-mentioned target system smart contract as part of the above-mentioned service configuration information. In this case, before calling the above-mentioned cross-chain call logic contained in the above-mentioned target system smart contract in response to the above-mentioned call message, the above-mentioned node device can first query the above-mentioned association relationship to determine whether the user service has been registered as a link with the above-mentioned target user User services associated with smart contracts.

Of course, the above-mentioned association relationship may not be part of the above-mentioned service configuration information and maintained in the above-mentioned target system smart contract, but on the above-mentioned centralized management and control platform. In this case, before the above-mentioned node device responds to the above-mentioned calling message and calls the above-mentioned cross-chain calling logic contained in the above-mentioned target system smart contract, it can interact with the above-mentioned centralized management and control platform through an oracle oracle program outside the chain, from The above-mentioned association relationship is read on the above-mentioned centralized management and control platform, and then based on the read association relationship, it is determined whether the user service has been registered as a user service associated with the above-mentioned target user smart contract. Alternatively, before the above-mentioned node device responds to the above-mentioned call message and calls the above-mentioned cross-chain call logic contained in the above-mentioned target system smart contract, it can use an oracle oracle program to interact with the above-mentioned centralized management and control platform outside the chain, and provide the above-mentioned centralized management and control The platform sends a query request, and the centralized management and control platform queries the above-mentioned relationship to determine whether the user service has been registered as a user service associated with the above-mentioned target user smart contract, and then returns the query result to the above-mentioned target system smart contract.

When it is determined that the above-mentioned user service has been registered as a user service associated with the above-mentioned target user smart contract, the above-mentioned cross-chain calling logic included in the above-mentioned target system smart contract can be further invoked. If it is determined that the above-mentioned user service is not registered as a user service associated with the above-mentioned target user smart contract, the above-mentioned target user smart contract can be rejected to call the above-mentioned cross-chain call logic contained in the above-mentioned target system smart contract.

In this way, it is possible to flexibly register user services for each user smart contract deployed on each member blockchain as a service user, and strictly control each user smart contract as a service user according to the registration result. Service calling authority; for example, through this registration mechanism, the calling authority of user services registered on the centralized management and control platform can be limited to the user smart contracts associated with these user services, thereby ensuring that each user smart contract can only As a service consumer to invoke its associated user service.

In this manual, when a user of the service provider registers a service solution on the above-mentioned centralized management and control platform, the centralized management and control platform can specifically deploy the registered service solution as a standardized service to open it to the service The consumer makes the call. Among them, when the centralized management and control platform deploys the registered service solution, it can also be deployed centrally on the centralized management and control platform in the form of a service interface, or distributed in the form of a system smart contract. On each member blockchain, for service users to call.

It should be noted that the detailed process of the above-mentioned centralized management and control platform deploying and registering the service solution and the detailed process of the service user invoking the deployed service solution will not be described in detail in this manual, and those skilled in the art can Refer to the detailed process of deploying the registered user service and the detailed process of calling the deployed user service by the service consumer shown in FIG. 6 and FIG. 7 above.

In each of the above embodiments, user services registered on the centralized management and control platform, specifically referring to the contract execution logic contained in the user smart contracts on the member blockchains on the blockchain service network, are combined to generate service as an example. What needs to be added is that in practical applications, the user services registered on the centralized management and control platform can be services generated by combining the contract execution logic contained in the user smart contracts on the member blockchains. , specifically, it can also refer to the data service generated after combining the blockchain data on each member blockchain.

In this case, the blockchain account corresponding to the centralized management and control platform created on each member blockchain is specifically used for initiating a transaction on each member blockchain when the service user invokes the above-mentioned user services. Compose the data access that generates the blockchain data for that user service.

Correspondingly, when the above-mentioned user service is a data service generated by combining the blockchain data on each member blockchain, the specific implementation details of the registration, deployment and invocation of this type of user service are the same as those in Figure 2 above. - The registration, deployment and invocation processes for user services described in the various embodiments shown in FIG. 7 are similar.

For example, in this case, when the service provider registers this type of user service with the centralized management and control platform, it can send a user service registration request to the centralized management and control platform, and the centralized management and control platform, after receiving the user service registration request, , in response to the user service registration request, determine the block chain data set used to realize the service function corresponding to the user service; the above block chain data set includes the member block chains deployed in the block chain service network block chain data; then, combine the block chain data in the above block chain data set to generate the above user service, so as to complete the service registration for the user service, the details of the specific registration service will not be described in detail, this field Those skilled in the art may refer to the descriptions of the various embodiments shown in FIG. 4 , which will not be repeated in this specification.

When the above-mentioned user services are deployed, they can also be deployed centrally on the above-mentioned centralized management and control platform in the form of service interfaces, or can be distributed and deployed on each member blockchain in the form of system smart contracts. For example, take the distributed deployment of system smart contracts on each member blockchain as an example. At this time, the above-mentioned system smart contract for cross-chain communication contains the cross-chain call logic corresponding to the above-mentioned user services. Specifically, you can use In: determine the member blockchains corresponding to the blockchain data that are combined to generate the user service, and based on the blockchain accounts corresponding to the centralized management and control platform created in the member blockchains, respectively Initiate data access to the data of each blockchain on each of the above member blockchains. When the service user needs to call this type of user service, it can initiate a call to this type of user service that has been registered on the centralized management and control platform by calling the above-mentioned cross-chain call logic contained in the system smart contract. The specific service call The details will not be repeated here, and those skilled in the art can refer to the descriptions of the embodiments shown in FIG. 6 and FIG. 7 , which will not be repeated in this specification.

Corresponding to the foregoing method embodiments, this specification also provides embodiments of apparatuses, electronic equipment, and storage media.

Fig. 8 is a schematic structural diagram of an electronic device provided by an exemplary embodiment. Please refer to FIG. 8 , at the hardware level, the device includes a processor 802 , an internal bus 804 , a network interface 806 , a memory 808 and a non-volatile memory 810 , and of course may also include hardware required by other services. One or more embodiments of this specification may be implemented based on software, for example, the processor 802 reads a corresponding computer program from the non-volatile memory 810 into the memory 808 and executes it. Of course, in addition to software implementations, one or more embodiments of this specification do not exclude other implementations, such as logic devices or a combination of software and hardware, etc., that is to say, the execution subject of the following processing flow is not limited to each A logic unit, which can also be a hardware or logic device.

As shown in FIG. 9, FIG. 9 is a block diagram of a device for building a blockchain service network shown in this specification according to an exemplary embodiment. The device can be applied to the electronic device shown in FIG. 8 to realize this Specifications for technical solutions. The device is applied to a centralized management and control platform corresponding to the blockchain service network; the blockchain service network includes at least one member blockchain; the centralized management and control platform supports registered user services; the user services include The user service generated by the contract execution logic combination contained in the user smart contract deployed on each member blockchain; the device 900 includes: a receiving module 901, which receives a registration request corresponding to the target blockchain; a registration module 902, In response to the registration request, perform a registration process for the target blockchain, so as to add the target blockchain as a member blockchain to the blockchain service network; the registration process includes A block chain account corresponding to the centralized management and control platform is created in the block chain, and the block chain account is used to initiate a target block for the target block when the user calls the target user service registered on the centralized control platform. The contract call of the target user smart contract deployed on the chain; wherein, the combination generates the contract execution logic of the target user service, including the contract execution logic contained in the target user smart contract.

The specific details of each module of the above-mentioned apparatus 900 have been described in detail in the method flow described above, so details are not repeated here.

Correspondingly, this specification also provides an electronic device, the electronic device includes a processor; a memory for storing processor-executable instructions; wherein, the processor is configured to implement all the methods described above A step of.

Correspondingly, this specification also provides a computer-readable storage medium, on which executable instructions are stored; wherein, when the instructions are executed by a processor, the steps in all the method processes described above are implemented.

As for the device embodiment, since it basically corresponds to the method embodiment, for related parts, please refer to the part description of the method embodiment. The device embodiments described above are only illustrative, and the modules described as separate components may or may not be physically separated, and the components shown as modules may or may not be physical modules, that is, they may be located in One place, or it can be distributed to multiple network modules. Part or all of the modules can be selected according to actual needs to achieve the purpose of the solution in this specification. It can be understood and implemented by those skilled in the art without creative effort.

The systems, devices, modules, or units described in the above embodiments can be specifically implemented by computer chips or entities, or by products with certain functions. A typical implementing device is a computer, which may take the form of a personal computer, laptop computer, cellular phone, camera phone, smart phone, personal digital assistant, media player, navigation device, e-mail device, game control device, etc. desktops, tablets, wearables, or any combination of these.

In a typical configuration, a computer includes one or more processors (CPUs), input/output interfaces, network interfaces and memory.

Memory may include non-permanent storage in computer-readable media, in the form of random access memory (RAM) and/or nonvolatile memory such as read-only memory (ROM) or flash RAM. Memory is an example of computer readable media.

Computer-readable media, including both permanent and non-permanent, removable and non-removable media, can be implemented by any method or technology for storage of information. Information may be computer readable instructions, data structures, modules of a program, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read only memory (ROM), Electrically Erasable Programmable Read-Only Memory (EEPROM), Flash memory or other memory technology, Compact Disc Read-Only Memory (CD-ROM), Digital Versatile Disc (DVD) or other optical storage, Magnetic cassettes, disk storage, quantum memory, graphene-based storage media or other magnetic storage devices or any other non-transmission media that can be used to store information that can be accessed by computing devices. As defined herein, computer-readable media excludes transitory computer-readable media, such as modulated data signals and carrier waves.

It should also be noted that the term "comprises", "comprises" or any other variation thereof is intended to cover a non-exclusive inclusion such that a process, method, article, or apparatus comprising a set of elements includes not only those elements, but also includes Other elements not expressly listed, or elements inherent in the process, method, commodity, or apparatus are also included. Without further limitations, an element defined by the phrase "comprising a ..." does not exclude the presence of additional identical elements in the process, method, article or apparatus comprising said element.

The foregoing describes specific embodiments of this specification. Other implementations are within the scope of the following claims. In some cases, the actions or steps recited in the claims can be performed in an order different from that in the embodiments and still achieve desirable results. In addition, the processes depicted in the accompanying figures do not necessarily require the particular order shown, or sequential order, to achieve desirable results. Multitasking and parallel processing are also possible or may be advantageous in certain embodiments.

Terms used in one or more embodiments of the present specification are for the purpose of describing specific embodiments only, and are not intended to limit the one or more embodiments of the present specification. As used in one or more embodiments of this specification and the appended claims, the singular forms "a", "the", and "the" are also intended to include the plural forms unless the context clearly dictates otherwise. It should also be understood that the term "and/or" as used herein refers to and includes any and all possible combinations of one or more of the associated listed items.

It should be understood that although the terms first, second, third, etc. may be used in one or more embodiments of the present specification to describe various information, the information should not be limited to these terms. These terms are only used to distinguish information of the same type from one another. For example, without departing from the scope of one or more embodiments of this specification, first information may also be called second information, and similarly, second information may also be called first information. Depending on the context, the word "if" as used herein may be interpreted as "at" or "when" or "in response to a determination."

The above descriptions are only preferred embodiments of one or more embodiments of this specification, and are not intended to limit one or more embodiments of this specification. Within the spirit and principles of one or more embodiments of this specification, Any modification, equivalent replacement, improvement, etc. should be included in the scope of protection of one or more embodiments of this specification.

Claims (16)

1. A method for forming a block chain service network, applied to the centralized management and control platform of the block chain service network; the method includes:

   Receive a registration request corresponding to the target blockchain;

   In response to the registration request, perform registration processing for the target blockchain, so as to add the target blockchain as a member blockchain to the blockchain service network;

   The registration process includes creating a block chain account corresponding to the centralized management and control platform in the target block chain, and the block chain account is used when the service user calls the account registered on the centralized control platform. When serving the user, initiate a contract call for the target user smart contract deployed on the target blockchain; wherein, the user service includes the contract execution logic of the target user smart contract deployed on the target blockchain.
2. According to the method according to claim 1, the user service includes a service generated by the contract execution logic combination of user smart contracts deployed on each member blockchain in the blockchain service network.
3. According to the method according to claim 2, the user service includes combining at least one contract execution logic of the user smart contract deployed on each member blockchain according to the logical sequence of the service logic corresponding to the user service to generate services.
4. According to the method of claim 2, at least part of the contract execution logic in the contract execution logic of the user service is combined to correspond to user smart contracts deployed on different member blockchains.
5. The method according to claim 2, said registration process further comprising:

   Deploy at least one system smart contract in the target blockchain; wherein, the at least one system smart contract includes a target system smart contract for cross-chain communication with other member blockchains.
6. The method according to claim 5,

   The target system smart contract includes cross-chain call logic corresponding to the target user service;

   Among them, the cross-chain calling logic is used for:

   Determine the user smart contracts corresponding to the execution logic of each contract that generates the target user service, and the member blockchains that deploy the user smart contracts, and based on the information created in the member blockchains and the The blockchain account corresponding to the centralized management and control platform respectively initiates cross-chain calls for the smart contracts of each user according to the logical sequence of the service logic corresponding to the target user service.
7. According to the method according to claim 6, the service configuration information corresponding to the target user service is maintained in the target system smart contract, and the blockchain account created for the centralized platform on each member blockchain list; wherein, the service configuration information includes: the identification information of each contract execution logic combined to generate the target user service, the contract address of each user smart contract containing the each contract execution logic, and the deployment of each user smart contract Correspondence between the blockchain identifiers of each member blockchain of the contract;

   The determined combination generates each user smart contract corresponding to each contract execution logic of the target user service, and each member block chain that deploys each user smart contract, and based on the created in each member block chain The blockchain account corresponding to the centralized management and control platform, according to the logical sequence of the service logic corresponding to the target user service, respectively initiates cross-chain calls for the smart contracts of each user, including:

   Querying the corresponding relationship to determine the combination of each contract execution logic for generating the target user service, each user smart contract containing the each contract execution logic, and each member blockchain deploying each user smart contract; and , and further query the list of blockchain accounts to determine the blockchain accounts corresponding to the centralized platform created on the member blockchains, and based on the determined blockchain accounts, according to The logic sequence of the service logic corresponding to the target user service respectively initiates cross-chain calls for the smart contracts of each user.
8. According to the method according to claim 7, the service configuration information further includes: based on the logic sequence of the service logic corresponding to the target user service, the call sequence determined for the execution logic of each contract combined to generate the target user service;

   Based on the determined blockchain account, according to the logical sequence of the service logic corresponding to the target user service, respectively initiating cross-chain calls for the smart contracts of each user includes:

   reading the invocation sequence included in the service configuration information;

   Based on the determined blockchain account, according to the read invocation order, respectively initiate cross-chain invocations for the user smart contracts.
9. The method according to claim 7, said method further comprising:

   In response to the registration of a new user service on the centralized management and control platform, the service configuration information corresponding to the new user service is stored in the target system smart contract, so that the Service configuration information is updated; and,

   In response to the addition of a new member blockchain in the blockchain service network, the blockchain account corresponding to the centralized management and control platform created on the new member blockchain is stored in the The target system smart contract is used to update the blockchain account list maintained in the system smart contract.
10. The method according to claim 5, said method further comprising:

    In response to the invocation request initiated by the service user for the service interface corresponding to the target user service deployed on the centralized management and control platform, determine the user smart contracts corresponding to the execution logic of each contract that is combined to generate the target user service , and deploy each member blockchain of each user smart contract, and based on the blockchain account corresponding to the centralized management and control platform created in each member blockchain, according to the target user service The logical sequence of the corresponding service logic initiates cross-chain calls for the smart contracts of each user.
11. According to the method described in claim 2, the centralized management and control platform supports the contract execution logic contained in the user smart contracts deployed on each member block chain to be registered on the centralized management and control platform; the centralized management and control The user services registered on the platform include services generated by combining at least one contract execution logic registered on the centralized management and control platform.
12. The method of claim 11, further comprising:

    Output the contract execution logic registered on the centralized management and control platform to the service provider through a visual interface;

    Obtain at least one contract execution logic selected by the service provider on the visual interface;

    The user service is generated by combining the at least one contract execution logic according to the logic sequence of the service logic corresponding to the user service.
13. According to the method according to claim 1, at least some member blockchains in the blockchain service network are heterogeneous blockchains.
14. A device for establishing a blockchain service network, which is applied to the centralized management and control platform for establishing the blockchain service network; the device includes:

    The receiving module receives the registration request corresponding to the target blockchain;

    The registration module, in response to the registration request, performs registration processing for the target blockchain, so as to add the target blockchain as a member blockchain to the blockchain service network; the registration processing includes Create a block chain account corresponding to the centralized management and control platform in the target block chain, and the block chain account is used for initiating a target The contract call of the target user smart contract deployed on the target blockchain; wherein, the user service includes the contract execution logic of the target user smart contract.
15. An electronic device comprising:

    processor;

    memory for storing processor-executable instructions;

    Wherein, the processor implements the method according to any one of claims 1-13 by running the executable instructions.
16. A computer-readable storage medium, on which computer instructions are stored, and the steps of the method according to any one of claims 1-13 are implemented when the instructions are executed by a processor.

Images