CN116975070A - Block chain service method, device, computer equipment, storage medium and product - Google Patents
Block chain service method, device, computer equipment, storage medium and product Download PDFInfo
- Publication number
- CN116975070A CN116975070A CN202211533736.6A CN202211533736A CN116975070A CN 116975070 A CN116975070 A CN 116975070A CN 202211533736 A CN202211533736 A CN 202211533736A CN 116975070 A CN116975070 A CN 116975070A
- Authority
- CN
- China
- Prior art keywords
- contract
- blockchain
- target
- task
- module
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 472
- 230000003993 interaction Effects 0.000 claims abstract description 340
- 238000012545 processing Methods 0.000 claims description 115
- 230000002452 interceptive effect Effects 0.000 claims description 31
- 238000004590 computer program Methods 0.000 claims description 23
- 238000004891 communication Methods 0.000 description 17
- 238000005516 engineering process Methods 0.000 description 16
- 238000010586 diagram Methods 0.000 description 15
- 238000012546 transfer Methods 0.000 description 14
- 230000006870 function Effects 0.000 description 13
- 238000007726 management method Methods 0.000 description 12
- 238000013473 artificial intelligence Methods 0.000 description 7
- 230000006835 compression Effects 0.000 description 7
- 238000007906 compression Methods 0.000 description 7
- 230000001960 triggered effect Effects 0.000 description 4
- 230000005540 biological transmission Effects 0.000 description 3
- 238000013500 data storage Methods 0.000 description 3
- 230000006837 decompression Effects 0.000 description 3
- 230000002349 favourable effect Effects 0.000 description 3
- 238000012423 maintenance Methods 0.000 description 3
- 230000004044 response Effects 0.000 description 3
- 230000006978 adaptation Effects 0.000 description 2
- 238000004364 calculation method Methods 0.000 description 2
- 238000013461 design Methods 0.000 description 2
- 238000011161 development Methods 0.000 description 2
- 238000003672 processing method Methods 0.000 description 2
- 230000001105 regulatory effect Effects 0.000 description 2
- 238000012795 verification Methods 0.000 description 2
- 230000002159 abnormal effect Effects 0.000 description 1
- 238000004458 analytical method Methods 0.000 description 1
- 238000012550 audit Methods 0.000 description 1
- 238000013475 authorization Methods 0.000 description 1
- FFBHFFJDDLITSX-UHFFFAOYSA-N benzyl N-[2-hydroxy-4-(3-oxomorpholin-4-yl)phenyl]carbamate Chemical compound OC1=C(NC(=O)OCC2=CC=CC=C2)C=CC(=C1)N1CCOCC1=O FFBHFFJDDLITSX-UHFFFAOYSA-N 0.000 description 1
- 238000004422 calculation algorithm Methods 0.000 description 1
- 238000013135 deep learning Methods 0.000 description 1
- 238000010801 machine learning Methods 0.000 description 1
- 238000003058 natural language processing Methods 0.000 description 1
- 238000010606 normalization Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 238000012954 risk control Methods 0.000 description 1
- 230000001360 synchronised effect Effects 0.000 description 1
- 238000012384 transportation and delivery Methods 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/23—Updating
- G06F16/2379—Updates performed during online database operations; commit processing
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
- H04L9/08—Key distribution or management, e.g. generation, sharing or updating, of cryptographic keys or passwords
- H04L9/0816—Key establishment, i.e. cryptographic processes or cryptographic protocols whereby a shared secret becomes available to two or more parties, for subsequent use
- H04L9/0819—Key transport or distribution, i.e. key establishment techniques where one party creates or otherwise obtains a secret value, and securely transfers it to the other(s)
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L2209/00—Additional information or applications relating to cryptographic mechanisms or cryptographic arrangements for secret or secure communication H04L9/00
- H04L2209/46—Secure multiparty computation, e.g. millionaire problem
Landscapes
- Engineering & Computer Science (AREA)
- Databases & Information Systems (AREA)
- Theoretical Computer Science (AREA)
- Data Mining & Analysis (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Computer Security & Cryptography (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
The application provides a blockchain service method, a blockchain service device, computer equipment, a storage medium and a blockchain service product. The method is applied to contract task execution equipment, the contract task execution equipment is connected with at least one blockchain, the contract task execution equipment comprises a plurality of task execution modules, and any one task execution module comprises: a task scheduling sub-module and at least one process scheduling module; the method comprises the following steps: acquiring a first interaction message sent by a target blockchain in at least one blockchain aiming at a to-be-executed contract task; determining a target task execution module associated with a chain identification of a target blockchain from a plurality of task execution modules; determining a target process scheduling module matched with the contract identification based on a task scheduling sub-module in the target task execution module; and executing the task to be executed by the target process based on the target contract, which is operated in the target process scheduling module. The execution efficiency of contract tasks in the blockchain can be improved.
Description
Technical Field
The present application relates to the field of blockchain technologies, and in particular, to a blockchain service method, a blockchain service apparatus, a computer device, a computer readable storage medium, and a computer program product.
Background
In a blockchain, a cloud computing service of an intelligent contract is generally involved, the cloud computing service refers to a service for providing corresponding computing resources in the form of on-demand service through the internet, and a computing engine of the cloud computing service corresponding to the blockchain is generally deployed in a blockchain node, and the corresponding contract cloud computing service is provided by a node inside the blockchain.
At present, the contract cloud computing service related in each blockchain needs to be directly configured, and the execution of corresponding contract tasks is completed by accessing a certain blockchain to a corresponding intelligent contract, so that the execution is not flexible and the efficiency is low.
Disclosure of Invention
The embodiment of the application provides a block chain service method, a device, computer equipment, a storage medium and a product, wherein contract task execution equipment provides corresponding contract cloud computing service for each block chain, which is more flexible and convenient, so that the execution efficiency of contract tasks in the block chain can be improved.
In one aspect, an embodiment of the present application provides a blockchain service method, which is applied to a contract task execution device, where the contract task execution device is connected with at least one blockchain, the contract task execution device includes a plurality of task execution modules, and any one task execution module includes: a task scheduling sub-module and at least one process scheduling module; the method comprises the following steps:
Obtaining a first interaction message sent by a target blockchain in at least one blockchain aiming at a to-be-executed contract task, wherein the first interaction message comprises: a chain identification of the target blockchain, a contract identification of a contract task to be executed;
determining a target task execution module from a plurality of task execution modules associated with a chain identification of a target blockchain, each blockchain of the at least one blockchain being associated with one task execution module;
determining a target process scheduling module matched with the contract identification based on a task scheduling sub-module in the target task execution module;
and executing the contract task to be executed by a target process based on the target contract, which is operated in the target process scheduling module, and processing the contract task to be executed by the target process based on the processing rule indicated by the target contract.
In one aspect, an embodiment of the present application provides a blockchain service method applied to a target blockchain, where the target blockchain is connected with a contract task execution device, and the target blockchain includes: the system comprises a task sending module, a contract interaction module and a result processing module; the method comprises the following steps:
the method comprises the steps of obtaining a contract task to be executed in a target block chain, and assembling the contract task to be executed based on a contract interaction module to obtain a first interaction message, wherein the first interaction message comprises: the system comprises a chain identifier of a target block chain and a contract identifier of a contract task to be executed, wherein the chain identifier of the target block chain is used for indicating contract task execution equipment to determine a target task execution module from a plurality of task execution modules, and the contract identifier is used for indicating a task scheduling sub-module in the target task execution module to determine a target process scheduling module;
The method comprises the steps that a first interaction message is sent to a target process scheduling module in contract task execution equipment based on a task sending module, and the first interaction message is used for triggering a target process running in the target process scheduling module and based on a target contract to execute a contract task to be executed;
and receiving a task execution result obtained after the contract task execution device executes the contract task to be executed, and carrying out result processing on the task execution result based on the result processing module.
In one aspect, an embodiment of the present application provides a blockchain service device, which is applied to a contract task execution device, where the contract task execution device is connected with at least one blockchain, the contract task execution device includes a plurality of task execution modules, and any one task execution module includes: a task scheduling sub-module and at least one process scheduling module; the device comprises:
the system comprises an acquisition unit, a processing unit and a processing unit, wherein the acquisition unit is used for acquiring a first interaction message sent by a target blockchain in at least one blockchain aiming at a to-be-executed contract task, and the first interaction message comprises: a chain identification of the target blockchain, a contract identification of a contract task to be executed;
a determining unit configured to determine a target task execution module associated with a chain identification of a target blockchain from a plurality of task execution modules, each of the at least one blockchain being associated with one task execution module;
The determining unit is further used for determining a target process scheduling module matched with the contract identification based on a task scheduling sub-module in the target task execution module;
and the processing unit is used for executing the contract task to be executed through a target process based on the target contract, which is operated in the target process scheduling module, and the target process processes the contract task to be executed based on the processing rule indicated by the target contract.
In one possible implementation, the number of contract tasks to be performed is a plurality; the processing unit executes a contract task to be executed through a target process based on a target contract running in the target process scheduling module, and is used for executing the following operations:
reading an execution statement of a target contract task in a target process based on a target contract running in a target process scheduling module, wherein the target contract task is any one of a plurality of contract tasks to be executed;
if the execution statement is used for indicating that the target contract task does not need to be subjected to interactive processing with the target block chain and the task content of the target contract task is not executed, executing the target contract task;
and after the task content execution of the target contract task is determined to be finished, scheduling the next contract task to be executed, and executing the scheduled contract task to be executed through the target process.
In one possible implementation, the processing unit, after reading the execution statement of the target contract task, is further configured to:
if the execution statement is used for indicating that the target contract task needs to be interacted with the target blockchain, generating a second interaction message;
sending a second interaction message to the target block chain, wherein the second interaction message is used for triggering the target block chain to execute an interaction method indicated by the second interaction message and obtaining an interaction result;
and receiving a third interaction message generated by the target block chain according to the interaction result, and executing a target contract task in the target process according to the interaction result in the third interaction message.
In one possible implementation manner, the processing unit performs, in the target process, a target contract task according to the interaction result in the third interaction message, and is configured to perform the following operations:
analyzing the third interaction message to obtain a chain identification of the target block chain, and determining a target task execution module associated with the chain identification of the target block chain from a plurality of task execution modules;
analyzing the third interaction message to obtain a contract identification of the target contract task, and determining a target process scheduling module matched with the contract identification based on a task scheduling sub-module in the target task execution module;
And analyzing the third interaction message to obtain a process identifier, and executing a target contract task according to an interaction result in a target process which is operated by a target process scheduling module and indicated by the process identifier.
In one possible implementation, before obtaining the first interaction message sent by the target blockchain in the at least one blockchain for the task to be contracted, the processing unit is further configured to:
acquiring a blockchain registration request sent by a blockchain to be registered, wherein the blockchain registration request carries blockchain metadata to be registered;
responding to a blockchain registration request, and carrying out blockchain registration processing for the blockchain to be registered according to the blockchain metadata to be registered;
the blockchain registration process is used for indicating initialization process resources for the blockchain to be registered.
In one possible implementation, the blockchain metadata to be registered includes: chain identification and priority identification of the block chain to be registered, wherein different priority identifications correspond to different quantity information; the processing unit 1003 performs a blockchain registration process for the blockchain to be registered according to the blockchain metadata to be registered, for performing the following operations:
Analyzing the blockchain registration request to obtain the chain identification of the blockchain to be registered, and if the fact that the chain identification of the blockchain to be registered does not exist and the blockchain registration rule is met is determined, acquiring the priority identification in the blockchain registration request;
if the quantity information corresponding to the priority identification is larger than the first preset quantity threshold value and smaller than the second preset quantity threshold value, distributing corresponding process resource parameters for the block chain to be registered according to the priority identification;
and allocating the process resources according to the process quantity indicated by the process resource parameters.
In one possible implementation, the processing unit is further configured to perform the following operations:
acquiring a contract registration request sent by a registered blockchain, wherein the contract registration request is generated after the blockchain to be registered receives a notification message of successful blockchain registration, and the contract registration request carries contract metadata to be registered;
responding to a contract registration request, and performing contract registration processing for the registered blockchain according to contract metadata to be registered;
the contract registration process is used for indicating that an association relation is established between the contract to be registered and the target process scheduling module, and the target process scheduling module is used for running a target process based on the contract to be registered.
In one possible implementation, the contract metadata includes: chain identification of registered blockchain, contract file of contract to be registered; the processing unit performs contract registration processing for the registered blockchain according to contract metadata to be registered, and is used for executing the following operations:
parsing a contract file of a contract to be registered from contract metadata based on a task scheduling sub-module in a target task execution module associated with a chain identification of a registered blockchain;
executing contract specification check on the analyzed contract file;
storing the contract file in the first memory and storing a file address of the contract file in the second memory if it is determined that the contract file passes the contract specification check;
the task scheduling submodule for completing storage is used for distributing an associated target process scheduling module for the contract to be registered.
In one possible implementation, the processing unit is further configured to perform the following operations:
if the task content execution of the contract task to be executed is determined to be finished in the target process, generating a task execution result of the contract task to be executed, wherein the task execution result is generated based on a result message rule;
the task execution result of the target contract task is sent to the target blockchain, so that the target blockchain carries out result processing based on the task execution result;
The task execution result comprises: any one or more of a result type, a read set, a write set, a result indication message, and an additional message; the read set records the blockchain content read by the target process from the target blockchain, and the write set records the content to be written by the target process to the target blockchain.
In one aspect, an embodiment of the present application provides a blockchain service apparatus applied to a target blockchain, where the target blockchain is connected with a contract task execution device, and the target blockchain includes: the system comprises a task sending module, a contract interaction module and a result processing module; the device comprises:
the acquisition unit is used for acquiring the contract task to be executed in the target block chain, and assembling the contract task to be executed based on the contract interaction module to obtain a first interaction message, wherein the first interaction message comprises: the system comprises a chain identifier of a target block chain and a contract identifier of a contract task to be executed, wherein the chain identifier of the target block chain is used for indicating contract task execution equipment to determine a target task execution module from a plurality of task execution modules, and the contract identifier is used for indicating a task scheduling sub-module in the target task execution module to determine a target process scheduling module;
The sending unit is used for sending a first interaction message to a target process scheduling module in the contract task execution equipment based on the task sending module, wherein the first interaction message is used for triggering a target process running in the target process scheduling module and based on a target contract to execute a contract task to be executed;
and the processing unit is used for receiving a task execution result obtained after the contract task execution equipment executes the contract task to be executed, and carrying out result processing on the task execution result based on the result processing module.
In one possible implementation, after the task sending module sends the first interaction message to the target process scheduling module in the contract task execution apparatus, the processing unit is further configured to perform the following operations:
receiving a contract interaction request which is sent by a target process and carries a second interaction message, wherein the second interaction message is generated according to a first contract interaction rule, and the second interaction message comprises: the interaction type of the target contract task to be interacted;
executing an interaction method indicated by the interaction type in the second interaction message, and obtaining an interaction result;
and generating a third interaction message comprising the interaction result according to the second contract interaction rule, and sending the third interaction message to a target process operated by the contract task execution equipment.
In one possible implementation, before acquiring the contract task to be performed in the target blockchain, the acquiring unit and the sending unit are further configured to:
the acquisition unit acquires blockchain metadata to be registered, and generates a blockchain registration request according to the blockchain metadata, wherein the blockchain metadata comprises: any one or more of chain identification and priority identification of the blockchain to be registered;
the sending unit sends a blockchain registration request to the contract task execution device, wherein the blockchain registration request is used for triggering the contract task execution device to perform blockchain registration processing for the blockchain to be registered.
In a possible implementation manner, the acquiring unit and the sending unit are further configured to perform the following operations:
the acquisition unit acquires contract metadata to be registered after receiving a notification message of successful blockchain registration sent by the contract task execution device, wherein the contract metadata to be registered comprises: any one or more of chain identification of registered blockchain, contract file of contract to be registered;
the sending unit generates a contract registration request according to the contract metadata to be registered, and sends the contract registration request to the contract task execution equipment, wherein the contract registration request is used for triggering the contract task execution equipment to conduct contract registration processing for the contract to be registered.
In one aspect, an embodiment of the present application provides a computer device, where the computer device includes a memory and a processor, and the memory stores a computer program, and when the computer program is executed by the processor, causes the processor to execute the blockchain service method described above.
In one aspect, embodiments of the present application provide a computer-readable storage medium storing a computer program that, when read and executed by a processor of a computer device, causes the computer device to perform the blockchain service method described above.
In one aspect, embodiments of the present application provide a computer program product or computer program comprising computer instructions stored in a computer readable storage medium. The processor of the computer device reads the computer instructions from the computer readable storage medium and executes the computer instructions to cause the computer device to perform the blockchain service method described above.
In the embodiment of the application, the contract task execution equipment can be connected with a plurality of blockchains, the contract task execution equipment can comprise task execution modules, any one task execution module comprises a task scheduling sub-module and at least one process scheduling module, and one task execution module is associated with one blockchain. Then, when the contract task needs to be executed, the contract task execution device may acquire a first interaction message sent by a target blockchain in the at least one blockchain for the contract task to be executed, where the first interaction message includes: a chain identification of the target blockchain, a contract identification of a contract task to be executed; then, a target task execution module associated with the chain identification of the target blockchain may be determined from the plurality of task execution modules; next, a target process scheduling module that matches the contract identification may be determined based on a task scheduling sub-module in the target task execution module; and finally, executing the contract task to be executed by a target process based on the target contract, which is operated in the target process scheduling module, wherein the target process processes the contract task to be executed based on the processing rule indicated by the target contract. Therefore, compared with the fact that the contract task of each blockchain is submitted to the nodes in the blockchain for execution, the computing service for executing the contract can be provided for each blockchain by the contract task executing equipment, and the computing and storage pressure of the nodes of the blockchain can be relieved; in addition, the contract task in each block chain is submitted to the corresponding task execution module for charge, so that the concurrent execution of the multi-block-chain multi-contract task can be realized, namely, the method is a one-to-many service mode, and is more flexible and convenient, so that the execution efficiency of the contract task in the block chain can be improved.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings required for the description of the embodiments will be briefly described below, and it is obvious that the drawings in the following description are some embodiments of the present application, and other drawings may be obtained according to these drawings without inventive effort for the person skilled in the art.
FIG. 1a is a block chain system according to an embodiment of the present application;
FIG. 1b is a block chain architecture diagram according to an embodiment of the present application;
FIG. 2 is a schematic diagram of a block chain service system according to an embodiment of the present application;
FIG. 3 is a flowchart of a blockchain service method according to an embodiment of the present application;
FIG. 4 is a flowchart illustrating another blockchain service method according to an embodiment of the present application;
FIG. 5 is a schematic illustration of an interface specification for contract interactions, provided by an embodiment of the application;
FIG. 6 is a schematic diagram of an interactive flow of a blockchain service according to an embodiment of the present application;
FIG. 7 is a flowchart of a blockchain registration process provided by an embodiment of the present application;
FIG. 8 is a flow diagram of a contract registration process provided by an embodiment of the present application;
FIG. 9 is a schematic flow chart of a contractual task interaction provided by an embodiment of the present application;
FIG. 10 is a schematic diagram of a block chain service device according to an embodiment of the present application;
FIG. 11 is a schematic diagram of another blockchain service device according to an embodiment of the present application;
fig. 12 is a schematic structural diagram of a computer device according to an embodiment of the present application.
Detailed Description
Reference will now be made in detail to exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, the same numbers in different drawings refer to the same or similar elements, unless otherwise indicated. The implementations described in the following exemplary examples do not represent all implementations consistent with the application. Rather, they are merely examples of apparatus and methods consistent with aspects of the application as detailed in the accompanying claims.
The application relates to a block chain contract cloud computing service, in particular to contract task execution equipment, which can provide cloud computing service for contract tasks under intelligent contracts in different block chains, namely support concurrent execution of multi-block chain and multi-contract tasks, so that the execution efficiency of the contract tasks in the block chains can be improved. The principle of the block chain service scheme provided by the application is as follows: a contract task execution device may be coupled to a plurality of blockchains, the contract task execution device may include task execution modules, any one of the task execution modules including a task scheduling sub-module and at least one process scheduling module, and one of the task execution modules associated with one of the blockchains. Then, when the contract task needs to be executed, the contract task execution device may acquire a first interaction message sent by a target blockchain in the at least one blockchain for the contract task to be executed, where the first interaction message includes: a chain identification of the target blockchain, a contract identification of a contract task to be executed; then, a target task execution module associated with the chain identification of the target blockchain may be determined from the plurality of task execution modules; next, a target process scheduling module that matches the contract identification may be determined based on a task scheduling sub-module in the target task execution module; and finally, executing the contract task to be executed by a target process based on the target contract, which is operated in the target process scheduling module, wherein the target process processes the contract task to be executed based on the processing rule indicated by the target contract.
Therefore, compared with the fact that the contract task of each blockchain is submitted to the nodes in the blockchain for execution, the computing service for executing the contract can be provided for each blockchain by the contract task executing equipment, and the computing and storage pressure of the nodes of the blockchain can be relieved; in addition, the contract task in each block chain is submitted to the corresponding task execution module for charge, so that the concurrent execution of the multi-block-chain multi-contract task can be realized, namely, the method is a one-to-many service mode, and is more flexible and convenient, so that the execution efficiency of the contract task in the block chain can be improved.
The following describes in detail related technical terms related to the blockchain service scheme provided by the present application with reference to the related drawings:
1. blockchain techniques:
the blockchain is essentially a decentralised database, which is a string of data blocks that are generated in association using cryptographic methods, each of which contains associated information for verifying the validity of its information (anti-counterfeiting) and generating the next Block. Next, terms such as a blockchain system, a blockchain structure, and the like will be described in detail.
(1) Blockchain system:
Referring to fig. 1a, fig. 1a is a schematic diagram of a blockchain system according to an embodiment of the application. As shown in fig. 1a, the blockchain system may be a data sharing system, where the data sharing system refers to a system for performing data sharing between nodes, where the data sharing system may include multiple nodes 101, and the multiple nodes 101 may be respective computer devices in the data sharing system, where the computer devices may be, for example, terminal devices or servers. In order to ensure the information intercommunication in the blockchain system, information connection can exist between every two nodes in the blockchain system, and the nodes can transmit information through the information connection. The information connection is not limited to a specific connection method, and may be, for example, a direct or indirect connection through a wired communication method, a direct or indirect connection through a wireless communication method, or another connection method, which is not limited herein.
(1) Structure of the blockchain:
specifically, the blockchain may include: the system comprises three modules, namely a block chain bottom layer platform, a platform product service layer and an application service layer. The following details of the above modules are described in connection with the embodiments of the present application:
A blockchain bottom platform: processing modules such as user management, basic services, intelligent contracts, operational supervision, etc. may be included. The user management module is responsible for identity information management of all blockchain participants (such as each node 101 in the data sharing system shown in fig. 1 a), including maintenance of public and private key generation (account management), key management, maintenance of correspondence between real identities of users and blockchain addresses (authority management), etc., specifically, the blockchain identity information of the target virtual object in the present application may be assigned, managed, etc. by the user management module, for example, the blockchain address, identity identifier of the target virtual object, at least one identity sub-identifier associated with the identity identifier, etc.; in addition, under the condition of authorization, the transaction condition of certain real identities is regulated and audited, the rule configuration (wind control audit) of risk control is provided, and particularly, the user management module can carry out the process of regulating and auditing the resource transfer transaction process between the digital virtual object and the target virtual object, thereby ensuring the reliability and the safety of the resource transfer process. b. The basic service module is deployed in all block link point devices (such as each node 101 in the data sharing system shown in fig. 1 a) and is used for verifying the validity of a service request (such as a contract interaction request sent by a contract task execution device), recording the service request on a storage after completing consensus, for a new service request, the basic service module firstly performs interface adaptation analysis and authentication processing (interface adaptation), then encrypts service information (consensus management) through a consensus algorithm, and completely and consistently transmits the service information to a shared ledger (network communication) after encryption, and records and stores the service request. c. The intelligent contract module is responsible for registering and issuing contracts, triggering contracts and executing contracts, a development object can define contract logic through a certain programming language, issue the contract logic to a blockchain (contract registering), trigger execution according to the logic of contract clauses, call keys or other events (such as triggering events of contract interaction) to complete the contract logic, and meanwhile provide a function of upgrading and logging off the contracts.
Platform product service layer: providing basic capabilities and implementation frameworks for typical applications, the development object can implement blockchain implementation of business logic based on these basic capabilities, overlaying the characteristics of the business. For example, the application can realize the business logic of resource transfer for the blockchain based on the contract cloud computing service provided by the contract task execution equipment; as another example, the present application may also implement business logic for obtaining interaction data from a blockchain (e.g., obtaining a blockheight of the blockchain, obtaining information of a sending object, etc.) based on a contract cloud computing service provided by a contract task execution device, and so on.
Application service layer: application services based on a blockchain scheme are provided for use by business participants. For example, the application service layer may execute the contract cloud computing service related to the blockchain by the contract task execution device based on the blockchain service scheme provided by the embodiment of the present application, so as to provide, for example: and performing resource transfer based on the block chain, and performing invoice circulation based on the block chain.
(2) Function of the node:
a. and the routing function is a basic function of any node in the blockchain system and is used for supporting communication among the nodes. For example, data interaction may be implemented between a certain node 101 and another node 101 based on a routing function, specifically, after a certain node 101 receives a contract interaction request sent by a contract task execution apparatus, the contract interaction request may be sent to another node 101, so that the other node 101 queries service data based on the contract interaction request, and sends the queried service data to the certain node 101.
b. The application function is used for being deployed in the block chain to realize specific service according to actual service requirements, recording data related to the realization function to form record data, carrying a digital signature in the record data to represent the source of task data, sending the record data to other nodes in the block chain system, and adding the record data into the temporary block when the source and the integrity of the record data are verified by the other nodes.
In particular, the above mentioned application functions may implement business functions of smart contracts, so called smart contracts (which may be abbreviated to contracts): a program (computerized agreement) running on a blockchain that can execute certain terms of an intelligent contract (contract tasks) is implemented by code deployed on a shared ledger for execution when certain conditions are met; unlike common procedures, the intelligent contracts ensure that the results of running in each node in the blockchain system are identical, so that any node can verify whether the results of executing the intelligent contracts in the blocks are correct.
Based on this, the present application relates to a contract task of executing an intelligent contract, and execution of the contract task can be specifically performed by a special contract task execution device. And then, the task execution results obtained after the contract task is executed by the contract task execution equipment can be synchronized to each node in the blockchain system, so that each node can verify the task execution results and ensure the reliability and safety of executing the contract task.
(2) The structure of the block:
referring to fig. 1b, fig. 1b is a schematic block chain structure according to an embodiment of the present application. As shown in fig. 1b, the blockchain is composed of a plurality of blocks, the starting block includes a block header and a block body, the block header stores an input information characteristic value, a version number, a timestamp and a difficulty value, and the block body stores input information (such as blockchain metadata, contract metadata, etc.); the next block of the starting block takes the starting block as a father block, the next block also comprises a block head and a block body, the block head stores the input information characteristic value of the current block, the block head characteristic value of the father block, the version number, the timestamp and the difficulty value, and the like, so that the block data stored in each block in the block chain are associated with the block data stored in the father block, and the safety of the input information in the block is ensured.
Based on this, the blocks in the blockchain are commonly known, then the application stores in the region block such as: the data such as the block chain metadata (chain identification and priority parameter of the block chain), the contract metadata (contract file) and the like has the characteristics of non-falsification, traceability, common maintenance and the like.
2. Artificial intelligence technology:
artificial intelligence (Artificial Intelligence, AI) technology is a comprehensive discipline, and relates to a wide range of fields, including both hardware-level technology and software-level technology. Artificial intelligence infrastructure technologies generally include technologies such as sensors, dedicated artificial intelligence chips, cloud computing, distributed storage, big data processing technologies, operation/interaction systems, mechatronics, and the like. The artificial intelligence software technology mainly comprises a computer vision technology, a voice processing technology, a natural language processing technology, machine learning/deep learning and other directions.
In the block chain service scheme, a large number of contract cloud computing services and data storage services are involved in the block chain, and a large number of data computing and data storage services are required to cost a large number of computer operation costs; therefore, the block chain metadata, the contract metadata and other data related to the application can be realized by cloud computing technology in artificial intelligence technology and distributed storage technology. Specifically, cloud computing technology can be deployed for the contract task execution device, so that the contract task execution device can provide corresponding contract cloud computing services for each contract task of the blockchain; and, the data involved in executing the contractual tasks (e.g., interactive results, task execution results, etc.) may also use distributed storage techniques to provide corresponding data storage services for different blockchains. In this way, computation and storage pressure of nodes in the blockchain may be reduced, thereby improving the efficiency of contract computation.
It should be noted that, in the following specific embodiments of the present application, related data such as object information is referred to, and when the above embodiments of the present application are applied to specific products or technologies, permission or consent of the object needs to be obtained, and collection, use and processing of the related data need to comply with related laws and regulations and standards of related countries and regions.
In combination with the above description of the blockchain service scheme provided by the present application, the architecture of the blockchain service system provided by the embodiment of the present application is specifically described below with reference to fig. 2.
Referring to fig. 2, fig. 2 is a schematic diagram of a block chain service system according to an embodiment of the application. The architecture diagram of the blockchain service system at least comprises: a first blockchain 100, a second blockchain 200, a contract task performing device 300, and the like. Wherein the contract task performing device 300 establishes communication connection with the first blockchain 100 and the second blockchain 200 based on a wired or wireless manner, respectively. Additionally, the first blockchain 100 or the second blockchain 200 may each maintain a respective blockchain network, e.g., the first blockchain is in blockchain network 1, the blockchain network 1 including at least one first blockchain node therein; as another example, the second blockchain is in the blockchain network 2, and at least one second blockchain node is also included in the blockchain network 2. It is appreciated that the contract task execution apparatus 300 of the present application may provide contract cloud computing services for each blockchain node in each blockchain (e.g., the first blockchain 100 or the second blockchain 200), i.e., contract tasks in each blockchain are handed over to be executed by the contract task execution apparatus 300. It should be noted that the present application is not limited to the number of blockchains associated with the constraint task execution device 300.
It should be noted that, the preconditions for interaction between each blockchain in the blockchain service system and the contract task execution device may include the following two conditions:
(1) the contract task execution equipment needs to have network capability: the contract task execution device needs to communicate with the blockchain through a network, and then the contract task execution device needs to have network capability.
(2) Establishing a long connection between the blockchain and the contract task execution equipment: because the contract task needs to interact with the blockchain in the execution process, a communication long connection needs to be established between the blockchain and contract task execution equipment, so that continuous message interaction is realized.
The contract task execution device 300 may be an independent physical server, a server cluster or a distributed system formed by a plurality of physical servers, a cloud server providing cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, CDN (Content Delivery Network ), basic cloud computing services such as big data and an artificial intelligence platform, and the like. The contract task execution devices 300 mentioned above may also be devices including, but not limited to: a cell phone, tablet, notebook, palm top, mobile internet device (MID, mobile internet device), intelligent voice interaction device, vehicle-mounted terminal, roadside device, aircraft, wearable device, smart home appliance, or wearable device with contract task execution function such as smart watch, smart bracelet, pedometer, etc.
Next, a detailed description will be given of the module structure included in each of the first blockchain 100, the second blockchain 200, and the contract task execution apparatus 300.
(1) First blockchain 100 (or second blockchain 200): and the module is responsible for tasks such as block generation, consensus, storage and the like. Wherein the first blockchain 100 may include: a task sending module 101, a contract interaction module 102, and a result processing module 103; the second blockchain 200 may include: a task sending module 201, a contract interaction module 202, and a result processing module 203.
a. The task sending module: each time a new block is generated in the block chain, a transaction of the whole block is packed, and the packed transaction is put into a task queue to be sent, and the task queue is waited to be sent to the contract task execution equipment 300 for execution;
b. contract interaction module: the module is responsible for interacting with a contract process running in the contract task execution equipment 300, specifically, responding to an interaction request sent by the contract process, and returning an interaction result after executing an interaction method indicated by the interaction request;
c. and a result processing module: the module is responsible for receiving a task execution result returned after the execution of the contract process is completed, and processing the task execution result, for example: formatting, normalization, etc.
(2) Task execution device 300: the apparatus may be used to provide contract computing services, i.e., services that perform contract tasks, to each blockchain node in each blockchain (e.g., first blockchain 100, second blockchain 200). The task performing device 300 may include: a blockchain interactive service module 301, a task scheduling module 302, and at least one task execution module 303. Any of the task execution modules 303 includes a task scheduling sub-module 3031 and at least one process scheduling module 3032. It should be noted that, a task execution module 303 may be used to associate a blockchain.
a. The blockchain interactive service module 301: the module is used for providing network transmission service, and can be used for realizing logic for interacting with a plurality of blockchains, in particular, the blockchain interaction service module 301 can be used for receiving a to-be-executed contract task sent by the task sending module 101 of the first blockchain 100;
b. task scheduling module 302: the module is responsible for receiving the contract task to be executed acquired from the blockchain interaction service module 301 and scheduling the contract task to be executed to different task execution modules, specifically, the corresponding task execution modules can be distinguished according to the chain identification (such as the chain ID) of the blockchain;
c. Task execution module 303: one blockchain corresponds to one task execution module, and the task execution module 303 is configured to execute all contract tasks of the corresponding blockchain. For example, the left task execution module shown in fig. 2 is used to execute each contract task to be executed of the first blockchain, and the right task execution module shown in fig. 2 is used to execute each contract task to be executed of the second blockchain; wherein, the task execution module may include: a task scheduling sub-module 3031 and at least one process scheduling module 3032;
i. task scheduling submodule 3031: each task execution module comprises a task scheduling sub-module which is responsible for scheduling all contract tasks to be executed of the same blockchain (e.g., can be distinguished based on contract identification of the contract tasks to be executed);
process scheduling module 3032: the process scheduling module is mainly responsible for all contract tasks to be executed under the contract (such as contract 1 or contract 2) and schedules available processes to execute the contract tasks;
(1) contract process manager: since each contract task under the same contract may be executed by a plurality of contract processes, one or more contract process managers are configured in each process scheduling module, and the contract process manager is used for managing the life cycle of the processes;
(2) Contract process (abbreviated process): each contract process manager corresponds to a contract process, wherein the contract process refers to a main body for executing contract tasks, in the process of executing the contract tasks, the combined appointments are packed into binary files to be executed, and the running state of the executed binary files is the contract process.
In one possible implementation, the blockchain service scheme of the present application is described again in connection with a module interaction procedure between the first blockchain 100 and the contract task performing device 300, taking the first blockchain 100 as an example. Specifically, first, the first blockchain 100 may assemble and generate a first interaction message for a contract task to be performed, and then transmit the first interaction message to the blockchain interaction service module 301 in the contract task performing device 300 based on the task transmitting module 101, wherein the first interaction message may include: chain identification of the first blockchain, contract identification of the contract task to be performed. Second, the task scheduling module 302 in the contracted task execution device 300 may determine a target task execution module associated with the chain identification of the first blockchain from among a plurality of task execution modules, each of the at least one blockchain being associated with one task execution module. Then, a target process scheduling module matching the contract identification is determined based on the task scheduling sub-module in the target task execution module. And finally, executing the contract task to be executed by the target process based on the target contract, which is operated in the target process scheduling module, wherein the target process processes the contract task to be executed based on the processing rule indicated by the target contract.
Based on this, the architecture of the blockchain service system provided by the embodiment of the application can realize two characteristics: (1) the functions of the modules are decoupled, different modules are responsible for respective tasks, corresponding functions are realized, the work division of each module is clear, and the problems of logic confusion and abnormal operation are not easy to occur; (2) the contract task in the block chain is separately executed and stored, the contract task execution equipment divides each module into tree shapes according to the block chain- > contract- > process mode, the contract task is scheduled and separated into corresponding processes, the flow is clear, and the operation is convenient; and the method is easy to provide as public service, realizes the separate execution and storage of contract tasks, and is favorable for the subsequent fine-grained contract task management.
It can be understood that, the blockchain service system described in the embodiment of the present application is for more clearly describing the technical solution of the embodiment of the present application, and does not constitute a limitation on the technical solution provided by the embodiment of the present application, and as a general technical object in the art can know, along with the evolution of the system architecture and the appearance of a new service scenario, the technical solution provided by the embodiment of the present application is also applicable to similar technical problems.
Based on the foregoing description of the blockchain service scheme and blockchain service system of the present application, specific embodiments related to the blockchain service scheme will be described in detail below with reference to the accompanying drawings.
Referring to fig. 3, fig. 3 is a flowchart of a blockchain service method according to an embodiment of the present application. The method is applied to a contract task execution device (which may be a terminal device or a server) in the blockchain service system shown in fig. 2, wherein the contract task execution device is connected with at least one blockchain, and the contract task execution device comprises: and the plurality of task execution modules, any one of which comprises a task scheduling sub-module and at least one process scheduling module. The blockchain service method mainly comprises, but is not limited to, the following steps S301 to S304:
s301: obtaining a first interaction message sent by a target blockchain in at least one blockchain aiming at a to-be-executed contract task, wherein the first interaction message comprises: chain identification of the target blockchain, contract identification of the contract task to be performed.
In the embodiment of the present application, the contract task to be executed refers to a task triggered to be executed based on an intelligent contract in a blockchain, for example, the contract task to be executed may include: the task of transferring resources from a resource transfer object to a resource receiving object, the task of obtaining the block height of a target blockchain, the task of obtaining data stored in the target blockchain, and the like are not particularly limited by the type of contract task to be executed. Wherein, the target blockchain refers to any one of at least one blockchain connected with the contract task execution equipment, and the type of the target blockchain can be: the application is not limited in any way by any of private chain, public chain, and federation chain, nor is the type of target blockchain specified.
Specifically, the contract task execution apparatus may further include: a blockchain interactive service module (such as blockchain interactive service module 301 shown in fig. 2), and a task scheduling module (such as task scheduling module 302 shown in fig. 2). Then, the first interaction message sent by the target blockchain in the at least one blockchain for the to-be-executed contract task can be obtained by the blockchain interaction service module in the contract task execution device.
In one possible implementation, the first interaction message is sent by a target blockchain node in the target blockchain, and the node identification of the target blockchain node may also be included in the first interaction message. Subsequently, after the blockchain interaction service module obtains the first interaction message, the identity of the target blockchain node may be verified based on the node identifier, where the identity verification may include: and after the identity verification of the target blockchain node is determined to pass, the first interactive message can be triggered to be sent to a task scheduling module so that the task scheduling module performs scheduling processing on the first interactive message.
It should be understood that before the target blockchain sends the first interaction message for executing the contract task to be executed to the contract task execution device, the blockchain registration process is first required, and after the completion of the blockchain registration process on the target blockchain, the cloud computing service provided by the contract task execution device for executing the contract task can be used. The blockchain registration process is as follows: when the new blockchain wants to use cloud computing service provided by the contract task execution equipment, the new blockchain needs to register the blockchain information of the new blockchain on the contract task execution equipment side, and the contract task execution equipment side can initialize corresponding process resources for the blockchain to be registered after a series of checks are performed on the blockchain to be registered.
In one possible implementation manner, before the contract task execution device obtains the first interaction message sent by the target blockchain in the at least one blockchain for the contract task to be executed, the following steps may be further executed: firstly, obtaining a blockchain registration request sent by a blockchain to be registered, wherein the blockchain registration request carries blockchain metadata to be registered; then, responding to a blockchain registration request, and carrying out blockchain registration processing for the blockchain to be registered according to the blockchain metadata to be registered; the blockchain registration process is used for indicating initialization process resources for the blockchain to be registered.
In particular, the blockchain metadata to be registered includes: chain identification and priority identification of the block chain to be registered, wherein different priority identifications correspond to different quantity information; the contract task execution device performs blockchain registration processing for the blockchain to be registered according to the blockchain metadata to be registered, and may include the following steps: analyzing the blockchain registration request to obtain the chain identification of the blockchain to be registered, and if the fact that the chain identification of the blockchain to be registered does not exist and the blockchain registration rule is met is determined, acquiring the priority identification in the blockchain registration request; if the quantity information corresponding to the priority identification is larger than the first preset quantity threshold value and smaller than the second preset quantity threshold value, distributing corresponding process resource parameters for the block chain to be registered according to the priority identification; and allocating the process resources according to the process quantity indicated by the process resource parameters.
S302: a target task execution module associated with a chain identification of a target blockchain is determined from a plurality of task execution modules, each of the at least one blockchain being associated with one task execution module.
Specifically, the contract task execution device comprises a plurality of task execution modules, wherein one task execution module is associated with one blockchain, namely one task execution module can be used for executing each contract task under one blockchain.
S303: and determining a target process scheduling module matched with the contract identification based on a task scheduling sub-module in the target task execution module.
In particular implementations, a task execution module may include: a task scheduling sub-module, and at least one process scheduling module. The task scheduling sub-module is used for scheduling all contract tasks to be executed of the same blockchain; the process scheduling module is mainly responsible for all contract tasks to be executed under one contract, and schedules available processes to execute the contract tasks. As shown in fig. 2, a target process scheduling module 3032 that matches a contract identification (e.g., contract 1) may be determined based on a task scheduling sub-module 3031 in the target task execution module, and the target process scheduling module 3032 is configured with a plurality of contract process managers, one for running a process under a contract, e.g., process 1 for contract 1, process 2 for contract 2, etc., may be run in the contract process manager 1.
S304: and executing the contract task to be executed by a target process based on the target contract, which is operated in the target process scheduling module, and processing the contract task to be executed by the target process based on the processing rule indicated by the target contract.
Specifically, the target process refers to any one running in a target contract process manager, which refers to any one of a plurality of contract process managers assigned to be placed in the target process scheduling module. It should be appreciated that multiple processes may be run simultaneously in the same contract process manager, such that multiple contract tasks may be concurrently executed based on the multiple processes, which may increase task execution efficiency. Additionally, the processing rules indicated by the target contract may include: the contract types configured by the target contract, for example, may include: the application is not limited to the types of resource transfer, obtaining block data (e.g., block height), bill transfer, etc.
In one possible implementation, the number of contract tasks to be performed is a plurality; the task execution device executes a contract task to be executed through a target process based on a target contract running in a target process scheduling module, and specifically may include: (1) reading an execution statement of a target contract task in a target process based on a target contract running in a target process scheduling module, wherein the target contract task is any one of a plurality of contract tasks to be executed; (2) if the execution statement is used for indicating that the target contract task does not need to be subjected to interactive processing with the target block chain and the task content of the target contract task is not executed, executing the target contract task; (3) and after the task content execution of the target contract task is determined to be finished, scheduling the next contract task to be executed, and executing the scheduled contract task to be executed through the target process. It should be understood that, the specific execution process of the next to-be-executed contract task may refer to the related execution process of the target contract task, and embodiments of the present application are not limited herein, and in this manner, each to-be-executed contract task may be executed in the target process sequentially.
In another possible implementation manner, after the task execution device reads the execution statement of the target contract task, the method may further include: if the execution statement is used for indicating that the target contract task needs to be interacted with the target blockchain, generating a second interaction message; then, a second interaction message is sent to the target block chain, and the second interaction message is used for triggering the target block chain to execute an interaction method indicated by the second interaction message and obtaining an interaction result; and finally, receiving a third interaction message generated by the target block chain according to the interaction result, and executing the target contract task in the target process according to the interaction result in the third interaction message.
In the specific implementation, executing the target contract task according to the interaction result in the third interaction message in the target process may specifically include: firstly, analyzing and obtaining a chain identification of a target block chain from a third interactive message, and determining a target task execution module associated with the chain identification of the target block chain from a plurality of task execution modules; then, analyzing from the third interaction message to obtain a contract identification of the target contract task, and determining a target process scheduling module matched with the contract identification based on a task scheduling sub-module in the target task execution module; and finally, analyzing the third interaction message to obtain a process identifier, and executing a target contract task according to the interaction result in a target process which is operated by the target process scheduling module and indicated by the process identifier. It should be appreciated that, after the interaction with the target blockchain, the specific process of performing the target contract task according to the interaction result based on the target process may refer to the related steps in detail, and embodiments of the present application are not limited in this disclosure.
In one possible implementation manner, if it is determined that the task content execution of the contract task to be executed is finished in the target process, generating a task execution result of the contract task to be executed, where the task execution result is generated based on a result message rule; and then, sending the task execution result of the target contract task to the target blockchain so that the target blockchain carries out result processing based on the task execution result. The task execution result comprises: any one or more of a result type, a read set, a write set, a result indication message, and an additional message; the read set records the blockchain content read by the target process from the target blockchain, and the write set records the content to be written by the target process to the target blockchain. The result types may include: correct results, incorrect results; the result indication message refers to a specific execution result of the contract task to be executed. The additional message may include: start time, end time, etc. of task execution.
In the embodiment of the application, the contract task execution equipment can be connected with a plurality of blockchains, the contract task execution equipment can comprise task execution modules, any one task execution module comprises a task scheduling sub-module and at least one process scheduling module, and one task execution module is associated with one blockchain. Then, when the contract task needs to be executed, the contract task execution device may acquire a first interaction message sent by a target blockchain in the at least one blockchain for the contract task to be executed, where the first interaction message includes: a chain identification of the target blockchain, a contract identification of a contract task to be executed; then, a target task execution module associated with the chain identification of the target blockchain may be determined from the plurality of task execution modules; next, a target process scheduling module that matches the contract identification may be determined based on a task scheduling sub-module in the target task execution module; and finally, executing the contract task to be executed by a target process based on the target contract, which is operated in the target process scheduling module, wherein the target process processes the contract task to be executed based on the processing rule indicated by the target contract. Therefore, compared with the fact that the contract task of each blockchain is submitted to the nodes in the blockchain for execution, the computing service for executing the contract can be provided for each blockchain by the contract task executing equipment, and the computing and storage pressure of the nodes of the blockchain can be relieved; in addition, the contract task in each block chain is submitted to the corresponding task execution module for charge, so that the concurrent execution of the multi-block-chain multi-contract task can be realized, and the execution efficiency of the contract task can be improved.
Referring to fig. 4, fig. 4 is a flowchart illustrating another blockchain service method according to an embodiment of the present application. The method is applied to the target blockchain in the blockchain service system shown in fig. 2, and in particular, can be applied to any blockchain node in the target blockchain, and for convenience of explanation, the target blockchain will be taken as an example for corresponding description. Wherein the target blockchain is connected with the contract task execution equipment, and the target blockchain comprises: the system comprises a task sending module, a contract interaction module and a result processing module. The blockchain service method mainly comprises, but is not limited to, the following steps S401 to S403:
s401: the method comprises the steps of obtaining a contract task to be executed in a target block chain, and assembling the contract task to be executed based on a contract interaction module to obtain a first interaction message, wherein the first interaction message comprises: chain identification of the target blockchain, contract identification of the contract task to be performed.
Specifically, the chain identifier of the target blockchain is used for indicating the contract task execution equipment to determine a target task execution module from a plurality of task execution modules, and the contract identifier is used for indicating the task scheduling submodule in the target task execution module to determine a target process scheduling module. It should be understood that, the detailed process of determining the target task execution module from the plurality of task execution modules based on the chain identification of the target blockchain and determining the target process scheduling module based on the contract identification may refer to the specific steps in the embodiment of fig. 3, which are not described herein.
In one possible implementation, before obtaining the contract task to be performed in the target blockchain, the method further includes: firstly, obtaining the block chain metadata to be registered, and generating a block chain registration request according to the block chain metadata, wherein the block chain metadata comprises: any one or more of chain identification and priority identification of the blockchain to be registered; and then, sending a blockchain registration request to the contract task execution equipment, wherein the blockchain registration request is used for triggering the contract task execution equipment to perform blockchain registration processing for the blockchain to be registered.
In one possible implementation manner, after receiving the notification message that the blockchain registration is successful, which is sent by the contract task execution device, contract metadata to be registered may also be obtained, where the contract metadata to be registered includes: any one or more of chain identification of registered blockchain, contract file of contract to be registered; then, a contract registration request is generated according to the contract metadata to be registered, and the contract registration request is sent to the contract task execution equipment, wherein the contract registration request is used for triggering the contract task execution equipment to conduct contract registration processing for the contract to be registered.
S402: and the first interactive message is used for triggering a target process running in the target process scheduling module to execute the contract task to be executed.
In one possible implementation manner, after the task sending module sends the first interaction message to the target process scheduling module in the contract task execution device, the method further includes: firstly, receiving a contract interaction request which is sent by a target process and carries a second interaction message, wherein the second interaction message is generated according to a first contract interaction rule, and the second interaction message comprises: the interaction type of the target contract task to be interacted; then, executing an interaction method indicated by the interaction type in the second interaction message, and obtaining an interaction result; and finally, generating a third interaction message comprising the interaction result according to the second contract interaction rule, and sending the third interaction message to a target process operated by the contract task execution equipment.
Specifically, the first contract interaction rule defines a message template for interaction between a contract file executed in the target process and the target blockchain; the second contract interaction rules define message templates for the target blockchain to return interaction results.
S403: and receiving a task execution result obtained after the contract task execution device executes the contract task to be executed, and carrying out result processing on the task execution result based on the result processing module.
It should be appreciated that in order for the target blockchain to normally use the blockchain contract cloud computing service, then a generic interface specification for contract interactions needs to be defined, that is, the contract interaction module in the blockchain and the contract process code running in the contract task execution device are written based on the interaction rules defined by the interface specification, so that the corresponding contract tasks can be executed correctly. Next, the interface specification of the contract interaction proposed by the present application will be described in detail by taking fig. 5 as an example.
Referring to fig. 5, fig. 5 is a schematic diagram illustrating an interface specification of contract interaction according to an embodiment of the present application. As shown in fig. 5, the interface specification is used to define specific interaction rules between the target blockchain and the target process running in the contracted task execution device: a first contract interaction rule, a second contract interaction rule, and a result message rule. Next, the three rules are specifically described respectively:
(1) first contract interaction rules: a message template for defining interactions by a contract software development kit (Software Development Kit, SDK) running in the target process to a contract interaction module of the target blockchain. The message template may include at least the following parameters:
a. A chain identification, a unique identification of the target blockchain;
b. contract name;
c. contract version: i.e., version number, and the contract name + contract version is a unique identification that identifies the contract;
d. process number: the process number of the target process where the contract task is located;
e. type of interaction: such as acquiring data, acquiring block height, acquiring sender information, resource transfer, etc.;
f. interaction parameters: parameters corresponding to the request of the interaction from the target blockchain, for example, the interaction type is a resource transfer type, the interaction parameters may include: the identification of the resource transfer object, the identification of the resource receiving object, and the resource amount of the resource to be transferred.
(2) Second contract interaction rules: a message template for defining a return interaction result of the target blockchain, the message template may include at least the following parameters:
a. a chain identification, a unique identification of the target blockchain;
b. contract name;
c. contract version: i.e., version number, and the contract name + contract version is a unique identification that identifies the contract;
d. process number: the process number of the target process where the contract task is located;
e. type of interaction: such as acquiring data, acquiring block height, acquiring sender information, resource transfer, etc.;
f. Interaction results: and executing the interaction method indicated by the interaction type to obtain an interaction result.
(3) Result message rule: a message template for returning the task execution result by the target process is defined, wherein the message template at least can comprise the following parameters:
a. the result type, including correct results, or incorrect results;
the read set records the blockchain content read from the target blockchain by the target process, and the part of the content only needs to be written into a key (key);
c. write set: the method includes the steps that the content to be written into a target block chain by a target process is recorded, and the part of the content needs to be written into a key and a value at the same time;
d. the result indication message is a specific execution result of the contract task to be executed;
e. additional messages such as start time, end time, etc. of task execution.
In an embodiment of the present application, a generic interface specification for contract interactions is provided, the interface specification comprising: the contract file and the block chain interact with each other, the block chain returns the interaction result, and the contract returns the task execution result. Then, any blockchain can assemble and process the interactive message according to the above-mentioned contract specification, and the blockchain contract cloud computing service provided by the contract task execution device can be used. After the interface specification of contract interaction is realized, the blockchain can normally send corresponding contract tasks to the blockchain contract cloud computing service architecture and execute the corresponding contract tasks, and the interface specification design mode is good in generalization, favorable for message interaction in the contract interaction process, and convenient for management of interaction messages.
Based on the above embodiments, the present application will be described in detail below with respect to a complete interaction flow between a target blockchain and a contract task execution device. Referring to fig. 6, fig. 6 is a schematic diagram of an interaction flow of a blockchain service according to an embodiment of the present application. The interactive flow may be jointly executed by the contract task execution apparatus and the target blockchain, and the interactive flow of the blockchain service method mainly includes, but is not limited to, the following steps S601 to S612. The interactive flow of the blockchain service method may specifically include: blockchain registration processes (S601-S602), contract registration processes (S603-S604), contract task interaction processes (S605-S612).
The specific steps involved in the above-described several processes will be described in detail below with reference to the accompanying drawings:
1. the blockchain registration procedure (S601-S602).
S601: the target blockchain sends a blockchain registration request to the contract task execution device.
The blockchain registration request carries blockchain metadata of the blockchain to be registered.
S602: the contract task execution device responds to the blockchain registration request to conduct blockchain registration processing for the blockchain to be registered.
Next, a detailed description will be given of a specific flow involved in how the blockchain registration process is performed with reference to the related drawings. Referring to fig. 7, fig. 7 is a flowchart of a blockchain registration process according to an embodiment of the present application. As shown in fig. 7, the flow of the blockchain registration process may include S701-S710:
S701: the blockchain to be registered assembles blockchain metadata.
Specifically, the blockchain to be registered assembles blockchain metadata of a blockchain contract cloud computing service provided using a contract task execution device, the blockchain metadata may include: chain identification (chain ID) of the blockchain to be registered, priority identification, and the like. Wherein different priority identifications correspond to different amounts of information, and the priority identifications may be used to indicate the number of processes created for the blockchain to be registered.
S702: the blockchain to be registered creates a client and obtains an IP address and a port number of the contract task execution device.
Specifically, the above-described IP address and port number may be used to establish a communication connection between the blockchain to be registered and the contract task execution device.
S703: the blockchain to be registered sends a blockchain registration request to the contract task execution device.
Specifically, the blockchain registration request may carry: IP address, port number, blockchain metadata, etc. that establish a communication connection with the contract task performing device.
S704: the blockchain interactive service module responds to the blockchain registration request to analyze the blockchain metadata.
Specifically, after receiving the block registration request, the blockchain interactive service module in the contract task execution device may establish a communication connection with the blockchain to be registered according to the IP address and the port number. After the communication connection is successfully established, each transmission field of the block chain metadata in the block registration request can be analyzed to obtain the data such as the chain identification (chain ID), the priority identification and the like of the block chain to be registered.
S705: the task scheduling module determines whether the chain identification is absent and legitimate.
Specifically, whether the chain identifier of the blockchain to be registered meets the blockchain registration rule is legal or not, for example, whether the chain identifier (such as the name of the blockchain) meets the requirement of naming standards is judged. If the chain identification does not exist and the blockchain registration rule is satisfied, S706 is executed; if the chain identification exists or does not satisfy the blockchain registration rule, S708 is performed.
S706: the task scheduling module determines whether the quantity information indicated by the priority identification is greater than a first quantity threshold (e.g., 0) and less than a second quantity threshold. If yes, then execution S707; if not, then S708 is performed.
S707: and the task scheduling module allocates process resources according to the priority identification.
Specifically, the task scheduling module allocates corresponding process resource parameters for the block chain to be registered according to the priority mark, and allocates process resources according to the number of processes indicated by the process resource parameters. In the process of allocating process resources for the blockchain to be registered, a process state with a small number of contract tasks provided by the blockchain contract cloud computing service can be set to be a frozen state, and after the execution of the contract tasks is finished, the frozen state of the corresponding process is released, so that the process with the frozen state released is released to the blockchain to be registered, and the process is used for executing the contract tasks in the blockchain to be registered. Based on the mode, process resources can be reasonably distributed, so that the task execution process is more reasonable and convenient, and the efficiency is improved.
S708: the task scheduling module returns a registration result of blockchain registration to the blockchain to be registered.
The registration result of the blockchain registration may include: registration success, or registration failure.
S709: the blockchain to be registered judges whether the registration result is successful.
Specifically, if the registration result is that the registration is successful, S710 is executed; if the registration result is that the registration fails, ending the blockchain registration flow.
S710: the blockchain to be registered prepares to send tasks and execute.
Among other things, the tasks referred to herein may include tasks to register or create contracts.
In one possible implementation, after the blockchain registration is completed, the contract task performing device may further perform the following steps: firstly, acquiring a contract registration request sent by a registered blockchain, wherein the contract registration request is generated after the blockchain to be registered receives a notification message of successful blockchain registration, and the contract registration request carries contract metadata to be registered; then, in response to the contract registration request, contract registration processing is performed for the registered blockchain according to contract metadata to be registered. The contract registration process is used for indicating that an association relation is established between the contract to be registered and the target process scheduling module, and the target process scheduling module is used for running a target process based on the contract to be registered.
In particular implementations, the contract metadata includes: chain identification of registered blockchain, contract file of contract to be registered; the contract task execution device performs contract registration processing for the registered blockchain according to the contract metadata to be registered, and may include the following procedures: first, parsing a contract file of a contract to be registered from contract metadata based on a task scheduling sub-module in a target task execution module associated with a chain identification of a registered blockchain; then, executing contract specification check on the analyzed contract file; storing the contract file in the first memory and storing a file address of the contract file in the second memory if it is determined that the contract file passes the contract specification check; the task scheduling submodule for completing storage is used for distributing an associated target process scheduling module for the contract to be registered.
2. Contract registration flow (S603-S604).
S603: the target blockchain sends a contract registration request to the contract task execution device.
Wherein the contract registration request carries contract metadata of the contract to be registered.
S604: the contract task execution device performs contract registration processing for the registered blockchain in response to the contract registration request.
Further, after the blockchain is registered, if a contract task needs to be performed, a corresponding contract needs to be registered. Next, a detailed description will be given of a specific flow of how the contract registration process is performed with reference to the related drawings. Referring to fig. 8, fig. 8 is a schematic flow chart of a contract registering process according to an embodiment of the present application. As shown in fig. 8, the flow of the contract registration process may include S801 to S814:
s801: the blockchain to be registered assembles contract metadata.
Specifically, the blockchain to be registered assembles contract metadata of a blockchain contract cloud computing service provided by a contract task execution device, wherein the contract metadata can include: chain identification (chain ID) of the registered blockchain, contract file of the contract to be registered; if the contract file is a compressed file, the contract metadata may also include a compression type of the contract file, and the like.
S802: the blockchain to be registered creates a client and obtains an IP address and a port number of the contract task execution device.
Specifically, the above-described IP address and port number may be used to establish a communication connection between the blockchain to be registered and the contract task execution device.
S803: the blockchain to be registered sends a contract registration request to the contract task execution device.
Specifically, the contract registration request may carry: IP address, port number, contract metadata, etc. that establish a communication connection with the contract task execution device.
S804: the blockchain interactive service module parses the contract metadata in response to the contract registration request.
Specifically, the blockchain interactive service module in the contract task execution device may establish a communication connection with the registered blockchain according to the IP address and the port number after receiving the contract registration request. After the communication connection is successfully established, each transmission field of the contract metadata in the contract registration request can be analyzed to obtain the data such as the chain identification (chain ID) of the registered blockchain, the contract file of the contract to be registered, the compression type of the contract file and the like.
S805: the task scheduling module analyzes the contract metadata to obtain a chain identification, and distributes the chain identification to the corresponding task execution module.
Specifically, in the above-mentioned blockchain registration procedure in fig. 7, after the blockchain registration is completed, the registered blockchain may be assigned to the associated task execution module. Then, after the chain ID is obtained by parsing, the task scheduling module may allocate a corresponding task execution module to the blockchain corresponding to the parsed chain ID.
S806: the task execution module determines whether the contract file needs to be decompressed.
The contract file is usually a binary file (also called binary file), and the binary file can be compressed according to a preset compression type. If it is determined that the contract file is a compressed file, S807 is executed; if it is determined that the contract file is an uncompressed file, S808 is performed.
S807: the task execution module executes decompression processing.
Specifically, the task execution module may decompress the compressed contract file according to a preset compression type, that is, compression and decompression are both performed in the same type of compression mode. Thereby, consistency between the contract file after decompression and the contract file before compression can be ensured.
S808: and the task execution module performs contract specification check on the decompressed contract file.
S809: the task execution module determines whether the contract file passes a contract specification check. If yes, executing S810; if not, S812 is performed.
S810: the task execution module stores the contract file to a disk (first memory).
S811: the task execution module stores the file address of the contract file to a disk (second memory).
S812: the task execution module returns the registration result of the contract to the registered blockchain.
Wherein the registration result of the contract may include: registration success, or registration failure.
S813: the registered blockchain determines whether the registration result is successful registration.
If yes, then execution S814; if not, ending the contract registration flow.
S814: the registered blockchain is ready to send contract task executions.
Based on this, for the blockchain to be registered, after the blockchain registration flow and the contract registration flow are completed, the contract task can be sent to perform the corresponding execution operation.
3. Contract task interaction flow (S605-S612).
S605: the target blockchain sends a first interaction message to the contract task execution device.
Wherein the first interactive message may include: chain identification of the target blockchain, contract identification of the contract task to be performed.
S606: the contract task execution device determines a target task execution module associated with a chain identification of a target blockchain from a plurality of task execution modules.
S607: the contract task execution device determines a target process scheduling module matched with the contract identification based on a task scheduling sub-module in the target task execution module.
S608: the contract task execution device executes the contract task to be executed through a target process based on the target contract running in the target process scheduling module.
Specifically, the target process refers to any one running in a target contract process manager, and the target process processes a contract task to be executed based on a processing rule indicated by the target contract.
In one possible implementation, the number of contract tasks to be performed is a plurality; the task execution device executes a contract task to be executed through a target process based on a target contract running in a target process scheduling module, and specifically may include: (1) reading an execution statement of a target contract task in a target process based on a target contract running in a target process scheduling module, wherein the target contract task is any one of a plurality of contract tasks to be executed; (2) if the execution statement is used for indicating that the target contract task does not need to be subjected to interactive processing with the target block chain and the task content of the target contract task is not executed, executing the target contract task; (3) and after the task content execution of the target contract task is determined to be finished, scheduling the next contract task to be executed, and executing the scheduled contract task to be executed through the target process. It should be understood that, the specific execution process of the next to-be-executed contract task may refer to the related execution process of the target contract task, and embodiments of the present application are not limited herein, and in this manner, each to-be-executed contract task may be executed in the target process sequentially.
It should be noted that, in the embodiment of the present application, specific steps executed by the contract task execution apparatus in steps S606 to S608 may refer to relevant steps executed by the contract task execution apparatus in steps S302 to S304 in the embodiment of fig. 3 in detail, and the embodiment of the present application is not described herein again.
S609: the contract task execution device sends a second interaction message to the target blockchain.
S610: and the target block chain executes the interaction method indicated by the second interaction message and obtains an interaction result.
S611: the target blockchain sends a third interaction message to the contract task execution device.
S612: and the contract task execution device executes the target contract task in the target process according to the interaction result in the third interaction message.
Next, a detailed description will be given of a specific flow of how the contract task interaction is performed, with reference to the related drawings. Referring to fig. 9, fig. 9 is a schematic flow chart of a contract task interaction according to an embodiment of the present application. As shown in fig. 9, the flow of the contract task interaction may include S901 to S923:
s901: the target blockchain assembles task metadata for the contract task to be performed.
Wherein the task metadata may include: the chain identification of the target blockchain, the contract identification with executing contract task (contract name + contract version), and the task parameters of the contract task to be executed, e.g., the contract task to be executed is a resource transfer task, then the task parameters may include: the identification of the resource transfer object, the identification of the resource receiving object, and the resource amount of the resource to be transferred.
S902: the target blockchain creates a client and obtains an IP address and port number of the contract task execution device.
Specifically, the above-described IP address and port number may be used to establish a communication connection between the blockchain to be registered and the contract task execution device.
S903: the target blockchain sends a first interaction message to the contract task execution device.
Wherein, the first interaction message is generated according to the task metadata, and at least the first interaction message may include: chain identification of the target blockchain, contract identification with executing contract tasks, task parameters for the contract tasks to be executed, and so forth.
S904: the blockchain interactive service module receives a first interactive message.
S905: the task scheduling module analyzes the chain identification from the first interaction message and distributes the chain identification to the target task execution module.
S906: the task scheduling sub-module analyzes the contract identification from the first interactive message and distributes the contract identification to the target process scheduling module.
S907: the target process scheduling module determines a proper contract process manager and sends a contract task to be executed.
S908: the contract process manager determines available target processes and sends contract tasks to be executed.
Wherein one or more processes may be running in the contract process manager, one process being operable to perform one or more contract tasks under the same contract. By available target processes is meant processes whose process state is non-frozen.
S909: and reading an execution statement of the contract task to be executed in the target process.
S910: it is determined whether blockchain interactions are needed.
If the contract task to be executed needs to interact with the target blockchain, triggering to execute S911; if the contract task to be executed does not need to interact with the target blockchain, execution is triggered S918.
S911: the contract task execution device assembles the second interaction message.
Specifically, the second interaction message is generated according to the first contract interaction rule, and the second interaction message includes: the type of interaction of the target contract task to be interacted with. Wherein, the first contract interaction rule defines a message template for interaction by the contract SDK running in the target process to the contract interaction module of the target blockchain (refer to the specific description corresponding to the embodiment of FIG. 5 for details).
S912: the contract task execution device sends a second interaction message to the target blockchain.
S913: the target blockchain performs the interaction method indicated by the second interaction message.
S914: the target blockchain sends a third interaction message to the contract task execution device.
The third interaction message is generated according to the interaction result, where the interaction result is obtained after the interaction method indicated by the second interaction message is executed in step S913, and specifically, the third interaction message may include: chain identification of target blockchain, contract identification of contract task to be executed, process identification (process number), interaction result.
S915: the blockchain interactive service module receives a third interactive message.
S916: and the task scheduling module analyzes the chain identification from the third interaction message and distributes the chain identification to the target task execution module.
S917: and the task scheduling module analyzes the contract identification from the third interaction message and distributes the contract identification to the target process scheduling module.
S918: the task scheduling module parses the process identifier from the third interaction message, allocates it to the target process, and then triggers execution step S909.
S919: and judging whether an execution statement of the contract task to be executed is a completion statement.
The completion statement is used to indicate whether the task content of the contract task to be executed is executed, for example, the completion statement may be "end". If yes, triggering execution S920; if not, execution is triggered S923.
S920: the next contract task is scheduled.
S921: the contract task execution device sends a task execution result to the target blockchain.
S922: the target blockchain processes the task execution results.
Specifically, the task execution result is normalized, formatted, and the like.
S923: the contract task is performed in the target process.
In the embodiment of the application, based on the complete interaction flow between the blockchain and the contract task execution equipment, each blockchain node connected with the contract task execution equipment can transfer the calculation task to the contract task execution equipment to realize, thereby reducing the calculation pressure of the blockchain node and lowering the cost. Meanwhile, the block chain contract cloud computing service provided by the contract task execution equipment can process contract tasks in batches and rapidly, so that the contract computing efficiency can be improved, and the block chain contract cloud computing service can be widely reused in various business scenes.
The foregoing details of the method according to the embodiment of the present application are set forth in order to better implement the foregoing aspects of the embodiment of the present application, and accordingly, an apparatus according to the embodiment of the present application is provided below, and next, related apparatuses according to the embodiment of the present application are correspondingly described in connection with the foregoing blockchain service scheme provided by the embodiment of the present application.
Referring to fig. 10, fig. 10 is a schematic structural diagram of a blockchain service device according to an embodiment of the present application. As shown in fig. 10, the blockchain service apparatus 1000 is applicable to the contract task execution device mentioned in the foregoing embodiment, the contract task execution device is connected with at least one blockchain, the contract task execution device includes a plurality of task execution modules, and any one of the task execution modules includes: a task scheduling sub-module and at least one process scheduling module. In particular, the blockchain service 1000 may be a computer program (including program code) running in a computer device, for example, the blockchain service 1000 is an application software; the blockchain service apparatus 1000 may be used to perform corresponding steps in the blockchain data processing method provided by the embodiments of the present application. The blockchain service apparatus 1000 may specifically include:
An obtaining unit 1001, configured to obtain a first interaction message sent by a target blockchain in at least one blockchain for a to-be-executed contract task, where the first interaction message includes: a chain identification of the target blockchain, a contract identification of a contract task to be executed;
a determining unit 1002 configured to determine a target task execution module associated with a chain identification of a target blockchain from a plurality of task execution modules, each of the at least one blockchain being associated with one task execution module;
the determining unit 1002 is further configured to determine, based on a task scheduling sub-module in the target task execution module, a target process scheduling module that matches the contract identifier;
the processing unit 1003 is configured to execute a contract task to be executed by a target process based on a target contract running in the target process scheduling module, where the target process processes the contract task to be executed based on a processing rule indicated by the target contract.
In one possible implementation, the number of contract tasks to be performed is a plurality; the processing unit 1003 executes a contract task to be executed by a target process based on a target contract running in the target process scheduling module for executing the following operations:
reading an execution statement of a target contract task in a target process based on a target contract running in a target process scheduling module, wherein the target contract task is any one of a plurality of contract tasks to be executed;
If the execution statement is used for indicating that the target contract task does not need to be subjected to interactive processing with the target block chain and the task content of the target contract task is not executed, executing the target contract task;
and after the task content execution of the target contract task is determined to be finished, scheduling the next contract task to be executed, and executing the scheduled contract task to be executed through the target process.
In one possible implementation, the processing unit 1003, after reading the execution statement of the target contract task, is further configured to perform the following operations:
if the execution statement is used for indicating that the target contract task needs to be interacted with the target blockchain, generating a second interaction message;
sending a second interaction message to the target block chain, wherein the second interaction message is used for triggering the target block chain to execute an interaction method indicated by the second interaction message and obtaining an interaction result;
and receiving a third interaction message generated by the target block chain according to the interaction result, and executing a target contract task in the target process according to the interaction result in the third interaction message.
In a possible implementation manner, the processing unit 1003 performs, in the target process, a target contract task according to the interaction result in the third interaction message, for performing the following operations:
Analyzing the third interaction message to obtain a chain identification of the target block chain, and determining a target task execution module associated with the chain identification of the target block chain from a plurality of task execution modules;
analyzing the third interaction message to obtain a contract identification of the target contract task, and determining a target process scheduling module matched with the contract identification based on a task scheduling sub-module in the target task execution module;
and analyzing the third interaction message to obtain a process identifier, and executing a target contract task according to an interaction result in a target process which is operated by a target process scheduling module and indicated by the process identifier.
In one possible implementation, before obtaining the first interaction message sent by the target blockchain in the at least one blockchain for the task to be contracted, the processing unit 1003 is further configured to:
acquiring a blockchain registration request sent by a blockchain to be registered, wherein the blockchain registration request carries blockchain metadata to be registered;
responding to a blockchain registration request, and carrying out blockchain registration processing for the blockchain to be registered according to the blockchain metadata to be registered;
the blockchain registration process is used for indicating initialization process resources for the blockchain to be registered.
In one possible implementation, the blockchain metadata to be registered includes: chain identification and priority identification of the block chain to be registered, wherein different priority identifications correspond to different quantity information; the processing unit 1003 performs a blockchain registration process for the blockchain to be registered according to the blockchain metadata to be registered, for performing the following operations:
analyzing the blockchain registration request to obtain the chain identification of the blockchain to be registered, and if the fact that the chain identification of the blockchain to be registered does not exist and the blockchain registration rule is met is determined, acquiring the priority identification in the blockchain registration request;
if the quantity information corresponding to the priority identification is larger than the first preset quantity threshold value and smaller than the second preset quantity threshold value, distributing corresponding process resource parameters for the block chain to be registered according to the priority identification;
and allocating the process resources according to the process quantity indicated by the process resource parameters.
In one possible implementation, the processing unit 1003 is further configured to perform the following operations:
acquiring a contract registration request sent by a registered blockchain, wherein the contract registration request is generated after the blockchain to be registered receives a notification message of successful blockchain registration, and the contract registration request carries contract metadata to be registered;
Responding to a contract registration request, and performing contract registration processing for the registered blockchain according to contract metadata to be registered;
the contract registration process is used for indicating that an association relation is established between the contract to be registered and the target process scheduling module, and the target process scheduling module is used for running a target process based on the contract to be registered.
In one possible implementation, the contract metadata includes: chain identification of registered blockchain, contract file of contract to be registered; the processing unit 1003 performs contract registration processing for the registered blockchain according to contract metadata to be registered, for performing the following operations:
parsing a contract file of a contract to be registered from contract metadata based on a task scheduling sub-module in a target task execution module associated with a chain identification of a registered blockchain;
executing contract specification check on the analyzed contract file;
storing the contract file in the first memory and storing a file address of the contract file in the second memory if it is determined that the contract file passes the contract specification check;
the task scheduling submodule for completing storage is used for distributing an associated target process scheduling module for the contract to be registered.
In one possible implementation, the processing unit 1003 is further configured to perform the following operations:
if the task content execution of the contract task to be executed is determined to be finished in the target process, generating a task execution result of the contract task to be executed, wherein the task execution result is generated based on a result message rule;
the task execution result of the target contract task is sent to the target blockchain, so that the target blockchain carries out result processing based on the task execution result;
the task execution result comprises: any one or more of a result type, a read set, a write set, a result indication message, and an additional message; the read set records the blockchain content read by the target process from the target blockchain, and the write set records the content to be written by the target process to the target blockchain.
In the embodiment of the application, the contract task execution equipment can be connected with a plurality of blockchains, the contract task execution equipment can comprise task execution modules, any one task execution module comprises a task scheduling sub-module and at least one process scheduling module, and one task execution module is associated with one blockchain. Then, when the contract task needs to be executed, the contract task execution device may acquire a first interaction message sent by a target blockchain in the at least one blockchain for the contract task to be executed, where the first interaction message includes: a chain identification of the target blockchain, a contract identification of a contract task to be executed; then, a target task execution module associated with the chain identification of the target blockchain may be determined from the plurality of task execution modules; next, a target process scheduling module that matches the contract identification may be determined based on a task scheduling sub-module in the target task execution module; and finally, executing the contract task to be executed by a target process based on the target contract, which is operated in the target process scheduling module, wherein the target process processes the contract task to be executed based on the processing rule indicated by the target contract. Therefore, compared with the fact that the contract task of each blockchain is submitted to the nodes in the blockchain for execution, the computing service for executing the contract can be provided for each blockchain by the contract task executing equipment, and the computing and storage pressure of the nodes of the blockchain can be relieved; in addition, the contract task in each block chain is submitted to the corresponding task execution module for charge, so that the concurrent execution of the multi-block-chain multi-contract task can be realized, namely, the method is a one-to-many service mode, and is more flexible and convenient, so that the execution efficiency of the contract task in the block chain can be improved.
Referring to fig. 11, fig. 11 is a schematic structural diagram of another blockchain service device according to an embodiment of the present application. As shown in fig. 11, the blockchain service apparatus 1100 may be applied to the target blockchain mentioned in the foregoing embodiments, where the target blockchain is connected to the contract task execution device, and the target blockchain includes: the system comprises a task sending module, a contract interaction module and a result processing module. Specifically, the blockchain service 1100 may be a computer program (including program code) running in a computer device, for example, the blockchain service 1100 is an application software; the blockchain service apparatus 1100 may be used to perform corresponding steps in the blockchain data processing method provided by the embodiments of the present application. The blockchain service apparatus 1100 may specifically include:
the obtaining unit 1101 is configured to obtain a contract task to be executed in the target blockchain, and assemble the contract task to be executed based on the contract interaction module to obtain a first interaction message, where the first interaction message includes: the system comprises a chain identifier of a target block chain and a contract identifier of a contract task to be executed, wherein the chain identifier of the target block chain is used for indicating contract task execution equipment to determine a target task execution module from a plurality of task execution modules, and the contract identifier is used for indicating a task scheduling sub-module in the target task execution module to determine a target process scheduling module;
The sending unit 1102 is configured to send, based on the task sending module, a first interaction message to a target process scheduling module in the contract task execution device, where the first interaction message is used to trigger a target process running in the target process scheduling module and based on a target contract to execute a contract task to be executed;
the processing unit 1103 is configured to receive a task execution result obtained after the contract task to be executed is executed by the contract task execution device, and perform result processing on the task execution result based on the result processing module.
In one possible implementation, after the task sending module sends the first interaction message to the target process scheduling module in the contract task execution device, the processing unit 1103 is further configured to perform the following operations:
receiving a contract interaction request which is sent by a target process and carries a second interaction message, wherein the second interaction message is generated according to a first contract interaction rule, and the second interaction message comprises: the interaction type of the target contract task to be interacted;
executing an interaction method indicated by the interaction type in the second interaction message, and obtaining an interaction result;
and generating a third interaction message comprising the interaction result according to the second contract interaction rule, and sending the third interaction message to a target process operated by the contract task execution equipment.
In one possible implementation, before acquiring the contract task to be performed in the target blockchain, the acquiring unit 1101 and the sending unit 1102 are further configured to:
the acquisition unit 1101 acquires blockchain metadata to be registered, and generates a blockchain registration request from the blockchain metadata, the blockchain metadata including: any one or more of chain identification and priority identification of the blockchain to be registered;
the sending unit 1102 sends a blockchain registration request to the contract task execution device, where the blockchain registration request is used to trigger the contract task execution device to perform blockchain registration processing for the blockchain to be registered.
In a possible implementation manner, the obtaining unit 1101 and the sending unit 1102 are further configured to perform the following operations:
the obtaining unit 1101 obtains, after receiving a notification message that blockchain registration is successful sent by the contract task execution device, contract metadata to be registered, the contract metadata to be registered including: any one or more of chain identification of registered blockchain, contract file of contract to be registered;
the transmitting unit 1102 generates a contract registration request according to the contract metadata to be registered, and transmits the contract registration request to the contract task execution apparatus, the contract registration request being for triggering the contract task execution apparatus to perform contract registration processing for the contract to be registered.
In an embodiment of the present application, a generic interface specification for contract interactions is provided, the interface specification comprising: the contract file and the block chain interact with each other, the block chain returns the interaction result, and the contract returns the task execution result. Then, any blockchain can assemble and process the interactive message according to the above-mentioned contract specification, and the blockchain contract cloud computing service provided by the contract task execution device can be used. After the interface specification of contract interaction is realized, the blockchain can normally send corresponding contract tasks to the blockchain contract cloud computing service architecture and execute the corresponding contract tasks, and the interface specification design mode is good in generalization, favorable for message interaction in the contract interaction process, and convenient for management of interaction messages.
Referring to fig. 12, fig. 12 is a schematic structural diagram of a computer device according to an embodiment of the application. The computer device 1200 is configured to perform the steps performed by the contract task execution device, and the target blockchain in the method embodiments described above. The computer device 1200 includes: one or more processors 1201; one or more input devices 1202, one or more output devices 1203, and a memory 1204. In particular, the memory 1204 is used to store a computer program, the computer program comprising program instructions, the processor 1201 calls the program instructions stored in the memory 1204 for performing the following operations:
Obtaining a first interaction message sent by a target blockchain in at least one blockchain aiming at a to-be-executed contract task, wherein the first interaction message comprises: a chain identification of the target blockchain, a contract identification of a contract task to be executed;
determining a target task execution module from a plurality of task execution modules associated with a chain identification of a target blockchain, each blockchain of the at least one blockchain being associated with one task execution module;
determining a target process scheduling module matched with the contract identification based on a task scheduling sub-module in the target task execution module;
and executing the contract task to be executed by a target process based on the target contract, which is operated in the target process scheduling module, and processing the contract task to be executed by the target process based on the processing rule indicated by the target contract.
In one possible implementation, the number of contract tasks to be performed is a plurality; the processor 1201 performs a contract task to be performed by a target process based on a target contract running in the target process scheduling module for performing the following operations:
reading an execution statement of a target contract task in a target process based on a target contract running in a target process scheduling module, wherein the target contract task is any one of a plurality of contract tasks to be executed;
If the execution statement is used for indicating that the target contract task does not need to be subjected to interactive processing with the target block chain and the task content of the target contract task is not executed, executing the target contract task;
and after the task content execution of the target contract task is determined to be finished, scheduling the next contract task to be executed, and executing the scheduled contract task to be executed through the target process.
In one possible implementation, the processor 1201, after reading the execution statement of the target contract task, is further configured to:
if the execution statement is used for indicating that the target contract task needs to be interacted with the target blockchain, generating a second interaction message;
sending a second interaction message to the target block chain, wherein the second interaction message is used for triggering the target block chain to execute an interaction method indicated by the second interaction message and obtaining an interaction result;
and receiving a third interaction message generated by the target block chain according to the interaction result, and executing a target contract task in the target process according to the interaction result in the third interaction message.
In one possible implementation, the processor 1201 performs the target contract task in the target process according to the interaction result in the third interaction message, for performing the following operations:
Analyzing the third interaction message to obtain a chain identification of the target block chain, and determining a target task execution module associated with the chain identification of the target block chain from a plurality of task execution modules;
analyzing the third interaction message to obtain a contract identification of the target contract task, and determining a target process scheduling module matched with the contract identification based on a task scheduling sub-module in the target task execution module;
and analyzing the third interaction message to obtain a process identifier, and executing a target contract task according to an interaction result in a target process which is operated by a target process scheduling module and indicated by the process identifier.
In one possible implementation, before obtaining the first interaction message sent by the target blockchain of the at least one blockchain for the task to be contracted, the processor 1201 is further configured to:
acquiring a blockchain registration request sent by a blockchain to be registered, wherein the blockchain registration request carries blockchain metadata to be registered;
responding to a blockchain registration request, and carrying out blockchain registration processing for the blockchain to be registered according to the blockchain metadata to be registered;
the blockchain registration process is used for indicating initialization process resources for the blockchain to be registered.
In one possible implementation, the blockchain metadata to be registered includes: chain identification and priority identification of the block chain to be registered, wherein different priority identifications correspond to different quantity information; the processor 1201 performs a blockchain registration process for a blockchain to be registered according to the blockchain metadata to be registered, for performing the following operations:
analyzing the blockchain registration request to obtain the chain identification of the blockchain to be registered, and if the fact that the chain identification of the blockchain to be registered does not exist and the blockchain registration rule is met is determined, acquiring the priority identification in the blockchain registration request;
if the quantity information corresponding to the priority identification is larger than the first preset quantity threshold value and smaller than the second preset quantity threshold value, distributing corresponding process resource parameters for the block chain to be registered according to the priority identification;
and allocating the process resources according to the process quantity indicated by the process resource parameters.
In one possible implementation, the processor 1201 is further configured to perform the following operations:
acquiring a contract registration request sent by a registered blockchain, wherein the contract registration request is generated after the blockchain to be registered receives a notification message of successful blockchain registration, and the contract registration request carries contract metadata to be registered;
Responding to a contract registration request, and performing contract registration processing for the registered blockchain according to contract metadata to be registered;
the contract registration process is used for indicating that an association relation is established between the contract to be registered and the target process scheduling module, and the target process scheduling module is used for running a target process based on the contract to be registered.
In one possible implementation, the contract metadata includes: chain identification of registered blockchain, contract file of contract to be registered; the processor 1201 performs contract registration processing for the registered blockchain according to contract metadata to be registered, for performing the following operations:
parsing a contract file of a contract to be registered from contract metadata based on a task scheduling sub-module in a target task execution module associated with a chain identification of a registered blockchain;
executing contract specification check on the analyzed contract file;
storing the contract file in the first memory and storing a file address of the contract file in the second memory if it is determined that the contract file passes the contract specification check;
the task scheduling submodule for completing storage is used for distributing an associated target process scheduling module for the contract to be registered.
In one possible implementation, the processor 1201 is further configured to perform the following operations:
if the task content execution of the contract task to be executed is determined to be finished in the target process, generating a task execution result of the contract task to be executed, wherein the task execution result is generated based on a result message rule;
the task execution result of the target contract task is sent to the target blockchain, so that the target blockchain carries out result processing based on the task execution result;
the task execution result comprises: any one or more of a result type, a read set, a write set, a result indication message, and an additional message; the read set records the blockchain content read by the target process from the target blockchain, and the write set records the content to be written by the target process to the target blockchain.
Optionally, the memory 1204 is configured to store a computer program, where the computer program includes program instructions, and the processor 1201 invokes the program instructions stored in the memory 1204, and is further configured to perform the following operations:
the method comprises the steps of obtaining a contract task to be executed in a target block chain, and assembling the contract task to be executed based on a contract interaction module to obtain a first interaction message, wherein the first interaction message comprises: the system comprises a chain identifier of a target block chain and a contract identifier of a contract task to be executed, wherein the chain identifier of the target block chain is used for indicating contract task execution equipment to determine a target task execution module from a plurality of task execution modules, and the contract identifier is used for indicating a task scheduling sub-module in the target task execution module to determine a target process scheduling module;
The method comprises the steps that a first interaction message is sent to a target process scheduling module in contract task execution equipment based on a task sending module, and the first interaction message is used for triggering a target process running in the target process scheduling module and based on a target contract to execute a contract task to be executed;
and receiving a task execution result obtained after the contract task execution device executes the contract task to be executed, and carrying out result processing on the task execution result based on the result processing module.
In one possible implementation, after the task sending module sends the first interaction message to the target process scheduling module in the contract task execution apparatus, the processor 1201 is further configured to:
receiving a contract interaction request which is sent by a target process and carries a second interaction message, wherein the second interaction message is generated according to a first contract interaction rule, and the second interaction message comprises: the interaction type of the target contract task to be interacted;
executing an interaction method indicated by the interaction type in the second interaction message, and obtaining an interaction result;
and generating a third interaction message comprising the interaction result according to the second contract interaction rule, and sending the third interaction message to a target process operated by the contract task execution equipment.
In one possible implementation, before acquiring the contract task to be performed in the target blockchain, the processor 1201 is further configured to:
obtaining the blockchain metadata to be registered, and generating a blockchain registration request according to the blockchain metadata, wherein the blockchain metadata comprises: any one or more of chain identification and priority identification of the blockchain to be registered;
and sending a blockchain registration request to the contract task execution equipment, wherein the blockchain registration request is used for triggering the contract task execution equipment to perform blockchain registration processing for the blockchain to be registered.
In one possible implementation, the processor 1201 is further configured to perform the following operations:
after receiving a notification message that the blockchain registration is successful, which is sent by the contract task execution device, contract metadata to be registered is obtained, wherein the contract metadata to be registered comprises: any one or more of chain identification of registered blockchain, contract file of contract to be registered;
and generating a contract registration request according to the contract metadata to be registered, and sending the contract registration request to the contract task execution equipment, wherein the contract registration request is used for triggering the contract task execution equipment to perform contract registration processing for the contract to be registered.
Furthermore, it should be noted here that: the embodiment of the present application further provides a computer storage medium, in which a computer program is stored, and the computer program includes program instructions, when executed by a processor, can perform the method in the corresponding embodiment, so that a detailed description will not be given here. For technical details not disclosed in the embodiments of the computer storage medium according to the present application, please refer to the description of the method embodiments of the present application. As an example, the program instructions may be deployed on one computer device or executed on multiple computer devices at one site or distributed across multiple sites and interconnected by a communication network.
According to one aspect of the present application, there is provided a computer program product or computer program comprising computer instructions stored in a computer readable storage medium. The processor of the computer device reads the computer instructions from the computer readable storage medium, and the processor executes the computer instructions, so that the computer device can perform the method in the foregoing corresponding embodiment, and therefore, a detailed description will not be given here.
It will be understood by those skilled in the art that implementing all or part of the above-described methods in the embodiments may be implemented by a computer program for instructing relevant hardware, and the above-described program may be stored in a computer readable storage medium, and the program may include the steps of the embodiments of the above-described methods when executed. The storage medium may be a magnetic disk, an optical disk, a Read-Only Memory (ROM), a random-access Memory (Random Access Memory, RAM), or the like.
The foregoing disclosure is illustrative of the present application and is not to be construed as limiting the scope of the application, which is defined by the appended claims.
Claims (18)
1. A blockchain service method, applied to a contract task execution device, the contract task execution device being connected with at least one blockchain, the contract task execution device comprising a plurality of task execution modules, any one of the task execution modules comprising: a task scheduling sub-module and at least one process scheduling module; the method comprises the following steps:
obtaining a first interaction message sent by a target blockchain in the at least one blockchain aiming at a to-be-executed contract task, wherein the first interaction message comprises: a chain identification of the target blockchain, a contract identification of a contract task to be executed;
Determining a target task execution module from a plurality of task execution modules associated with a chain identification of the target blockchain, each blockchain of the at least one blockchain being associated with one task execution module;
determining a target process scheduling module matched with the contract identification based on a task scheduling sub-module in a target task execution module;
executing the contract task to be executed by a target process based on a target contract, which is operated in the target process scheduling module, and processing the contract task to be executed by the target process based on a processing rule indicated by the target contract.
2. The method of claim 1, wherein the number of contractual tasks to be performed is a plurality; the executing the contract task to be executed by the target process based on the target contract running in the target process scheduling module comprises the following steps:
reading an execution statement of a target contract task in a target process based on a target contract running in the target process scheduling module, wherein the target contract task is any one of a plurality of contract tasks to be executed;
if the execution statement is used for indicating that the target contract task does not need to be subjected to interactive processing with a target block chain and the task content of the target contract task is not executed, executing the target contract task;
And after the task content execution of the target contract task is determined to be finished, scheduling the next contract task to be executed, and executing the scheduled contract task to be executed through the target process.
3. The method of claim 2, wherein after reading the execution statement of the target contract task, further comprising:
if the execution statement is used for indicating that the target contract task needs to be interacted with a target block chain, generating a second interaction message;
the second interaction message is sent to the target block chain, and the second interaction message is used for triggering the target block chain to execute an interaction method indicated by the second interaction message and obtain an interaction result;
and receiving a third interaction message generated by the target blockchain according to the interaction result, and executing the target contract task in the target process according to the interaction result in the third interaction message.
4. The method of claim 3, wherein the performing the target contract task in the target process according to the interaction result in the third interaction message comprises:
analyzing the third interaction message to obtain a chain identification of a target blockchain, and determining a target task execution module associated with the chain identification of the target blockchain from a plurality of task execution modules;
Analyzing the third interaction message to obtain a contract identification of a target contract task, and determining a target process scheduling module matched with the contract identification based on a task scheduling sub-module in a target task execution module;
and analyzing the third interaction message to obtain a process identifier, and executing the target contract task according to the interaction result in a target process which is operated by a target process scheduling module and indicated by the process identifier.
5. The method of claim 1, wherein prior to the obtaining the first interaction message sent by the target blockchain of the at least one blockchain for the contract task to be performed, further comprising:
acquiring a blockchain registration request sent by a blockchain to be registered, wherein the blockchain registration request carries blockchain metadata to be registered;
responding to the blockchain registration request, and carrying out blockchain registration processing for the blockchain to be registered according to the blockchain metadata to be registered;
the blockchain registration process is used for indicating initialization process resources for the blockchain to be registered.
6. The method of claim 5, wherein the blockchain metadata to be registered includes: chain identification and priority identification of the block chain to be registered, wherein different priority identifications correspond to different quantity information; the block chain registration processing for the block chain to be registered according to the block chain metadata to be registered comprises the following steps:
Analyzing the blockchain registration request to obtain a chain identifier of a blockchain to be registered, and if the fact that the chain identifier of the blockchain to be registered does not exist and the blockchain registration rule is met is determined, acquiring a priority identifier in the blockchain registration request;
if the quantity information corresponding to the priority identification is larger than a first preset quantity threshold value and smaller than a second preset quantity threshold value, corresponding process resource parameters are distributed for the blockchain to be registered according to the priority identification;
and allocating the process resources according to the process quantity indicated by the process resource parameters.
7. The method of any one of claims 1-6, wherein the method further comprises:
acquiring a contract registration request sent by a registered blockchain, wherein the contract registration request is generated after the blockchain to be registered receives a notification message that the blockchain registration is successful, and the contract registration request carries contract metadata to be registered;
responding to the contract registration request, and performing contract registration processing for the registered blockchain according to the contract metadata to be registered;
the contract registration process is used for indicating that an association relation is established between the contract to be registered and a target process scheduling module, and the target process scheduling module is used for running a target process based on the contract to be registered.
8. The method of claim 7, wherein the contract metadata includes: chain identification of registered blockchain, contract file of contract to be registered; the contract registration processing for the registered blockchain according to the contract metadata to be registered comprises the following steps:
parsing a contract file of the contract to be registered from the contract metadata based on a task scheduling sub-module in a target task execution module associated with a chain identification of the registered blockchain;
executing contract specification check on the analyzed contract file;
if the contract file is determined to pass the contract specification check, storing the contract file in a first memory and storing a file address of the contract file in a second memory;
and the task scheduling submodule for completing the storage is used for distributing an associated target process scheduling module for the contract to be registered.
9. The method of claim 1, wherein the method further comprises:
if the task content of the contract task to be executed is determined to be executed in the target process, generating a task execution result of the contract task to be executed, wherein the task execution result is generated based on a result message rule;
The task execution result of the target contract task is sent to the target blockchain, so that the target blockchain carries out result processing based on the task execution result;
wherein, the task execution result comprises: any one or more of a result type, a read set, a write set, a result indication message, and an additional message; and the read set records the blockchain content read by the target process from the target blockchain, and the write set records the content to be written by the target process to the target blockchain.
10. A blockchain service method, applied to a target blockchain, the target blockchain being connected to a contract task execution device, the target blockchain comprising: the system comprises a task sending module, a contract interaction module and a result processing module; the method comprises the following steps:
acquiring a contract task to be executed in a target block chain, and assembling the contract task to be executed based on a contract interaction module to obtain a first interaction message, wherein the first interaction message comprises: the system comprises a chain identifier of a target blockchain and a contract identifier of a contract task to be executed, wherein the chain identifier of the target blockchain is used for indicating contract task execution equipment to determine a target task execution module from a plurality of task execution modules, and the contract identifier is used for indicating a task scheduling submodule in the target task execution module to determine a target process scheduling module;
The first interaction message is sent to a target process scheduling module in the contract task execution equipment based on a task sending module, and the first interaction message is used for triggering a target process running in the target process scheduling module and based on a target contract to execute the contract task to be executed;
and receiving a task execution result obtained after the contract task to be executed is executed by the contract task execution equipment, and carrying out result processing on the task execution result based on a result processing module.
11. The method of claim 10, wherein after the task-based sending module sends the first interaction message to a target process scheduling module in the contracted task performing device, further comprising:
receiving a contract interaction request which is sent by the target process and carries a second interaction message, wherein the second interaction message is generated according to a first contract interaction rule, and the second interaction message comprises: the interaction type of the target contract task to be interacted;
executing the interaction method indicated by the interaction type in the second interaction message, and obtaining an interaction result;
and generating a third interaction message comprising the interaction result according to the second contract interaction rule, and sending the third interaction message to a target process operated by the contract task execution equipment.
12. The method of claim 10, wherein prior to obtaining the contract task to be performed in the target blockchain, further comprising:
obtaining block chain metadata to be registered, and generating a block chain registration request according to the block chain metadata, wherein the block chain metadata comprises: any one or more of chain identification and priority identification of the blockchain to be registered;
and sending the blockchain registration request to the contract task execution equipment, wherein the blockchain registration request is used for triggering the contract task execution equipment to perform blockchain registration processing for the blockchain to be registered.
13. The method of claim 12, wherein the method further comprises:
after receiving a notification message that the blockchain registration is successful, which is sent by the contract task execution device, contract metadata to be registered is obtained, wherein the contract metadata to be registered comprises: any one or more of chain identification of registered blockchain, contract file of contract to be registered;
and generating a contract registration request according to the contract metadata to be registered, and sending the contract registration request to the contract task execution equipment, wherein the contract registration request is used for triggering the contract task execution equipment to perform contract registration processing for the contract to be registered.
14. A blockchain service device, characterized by being applied to a contract task execution device, the contract task execution device being connected with at least one blockchain, the contract task execution device including a plurality of task execution modules, any one of the task execution modules including: a task scheduling sub-module and at least one process scheduling module; the device comprises:
an obtaining unit, configured to obtain a first interaction message sent by a target blockchain in the at least one blockchain for a to-be-executed contract task, where the first interaction message includes: a chain identification of the target blockchain, a contract identification of a contract task to be executed;
a determining unit configured to determine, from a plurality of task execution modules, a target task execution module associated with a chain identification of the target blockchain, each of the at least one blockchain being associated with one task execution module;
the determining unit is further used for determining a target process scheduling module matched with the contract identification based on a task scheduling sub-module in the target task execution module;
and the processing unit is used for executing the contract task to be executed through a target process based on a target contract, which is operated in the target process scheduling module, and the target process processes the contract task to be executed based on a processing rule indicated by the target contract.
15. A blockchain serving apparatus for use with a target blockchain, the target blockchain being coupled to a contract task execution device, the target blockchain comprising: the system comprises a task sending module, a contract interaction module and a result processing module; the device comprises:
the system comprises an acquisition unit, a contract interaction module and a control unit, wherein the acquisition unit is used for acquiring a contract task to be executed in a target block chain, and assembling the contract task to be executed based on the contract interaction module to obtain a first interaction message, and the first interaction message comprises: the system comprises a chain identifier of a target blockchain and a contract identifier of a contract task to be executed, wherein the chain identifier of the target blockchain is used for indicating contract task execution equipment to determine a target task execution module from a plurality of task execution modules, and the contract identifier is used for indicating a task scheduling submodule in the target task execution module to determine a target process scheduling module;
the sending unit is used for sending the first interaction message to a target process scheduling module in the contract task execution equipment based on a task sending module, wherein the first interaction message is used for triggering a target process running in the target process scheduling module and based on a target contract to execute the contract task to be executed;
And the processing unit is used for receiving a task execution result obtained after the contract task to be executed is executed by the contract task execution equipment, and carrying out result processing on the task execution result based on a result processing module.
16. A computer device, comprising: a memory device and a processor;
a memory in which one or more computer programs are stored;
a processor for loading the one or more computer programs to implement the blockchain service method of any of claims 1-9 or 10-13.
17. A computer readable storage medium, characterized in that the computer readable storage medium stores a computer program adapted to be loaded by a processor and to perform the blockchain service method of any of claims 1-9 or 10-13.
18. A computer program product, characterized in that the computer program product comprises a computer program adapted to be loaded by a processor and to perform the blockchain service method of any of claims 1-9 or 10-13.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211533736.6A CN116975070A (en) | 2022-11-30 | 2022-11-30 | Block chain service method, device, computer equipment, storage medium and product |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211533736.6A CN116975070A (en) | 2022-11-30 | 2022-11-30 | Block chain service method, device, computer equipment, storage medium and product |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN116975070A true CN116975070A (en) | 2023-10-31 |
Family
ID=88483728
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202211533736.6A Pending CN116975070A (en) | 2022-11-30 | 2022-11-30 | Block chain service method, device, computer equipment, storage medium and product |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN116975070A (en) |
-
2022
- 2022-11-30 CN CN202211533736.6A patent/CN116975070A/en active Pending
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110311790B (en) | Method and device for sending authenticable message in cross-link mode | |
| US11741083B2 (en) | Cross-shard private atomic commit | |
| CN111163182B (en) | Block chain-based device registration method and apparatus, electronic device, and storage medium | |
| CN112632629B (en) | Voting management method, device, medium and electronic equipment based on block chain | |
| JP2023506634A (en) | partially ordered blockchain | |
| CN109067732A (en) | Internet of things equipment and data insertion system, method and computer readable storage medium | |
| CN103561006A (en) | Application authentication method and device and application authentication server based on Android | |
| CN114971827A (en) | Account checking method and device based on block chain, electronic equipment and storage medium | |
| CN110647583B (en) | Block chain construction method, device, terminal and medium | |
| CN110099068B (en) | Method, device and equipment for interaction between open platforms based on block chains | |
| CN114268638A (en) | Block chain platform channel management method and device, computer equipment and storage medium | |
| CN116975070A (en) | Block chain service method, device, computer equipment, storage medium and product | |
| CN115378605A (en) | Data processing method and device based on block chain | |
| US11640392B2 (en) | Blockchain endorsement agreement | |
| CN111782615B (en) | Block chain-based large file storage method and system and computer equipment | |
| CN115329297A (en) | Application mutual trust method, device, equipment and storage medium based on block chain | |
| CN117010889A (en) | Data processing method, device, equipment, medium and product | |
| JP2023551160A (en) | Automated merging of DLT networks | |
| CN115701078A (en) | Cross-chain transaction processing method and device, electronic equipment and storage medium | |
| CN113010377A (en) | Method and device for collecting operation logs of operation | |
| CN111339189A (en) | Data processing method and device and computer readable storage medium | |
| KR20210027011A (en) | Peer node, method for processing information executed on peer node and blockchain platform system | |
| CN114398082B (en) | Compatible operation method and device for frame type block chain application | |
| CN116719627B (en) | Data processing method, device, equipment and storage medium | |
| CN117032727B (en) | File compiling method, device, equipment, medium and product based on block chain |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication |