CN114301912A

CN114301912A - Information interaction method and device based on block chain

Info

Publication number: CN114301912A
Application number: CN202111594892.9A
Authority: CN
Inventors: 昌文婷; 张晓蒙; 邱鸿霖; 彭晋
Original assignee: Alipay Hangzhou Information Technology Co Ltd
Current assignee: Alipay Hangzhou Information Technology Co Ltd
Priority date: 2021-12-23
Filing date: 2021-12-23
Publication date: 2022-04-08

Abstract

The present disclosure discloses an information interaction method and apparatus based on a blockchain, the method being performed by a node of a first blockchain, the method comprising: receiving a cross-link service request; responding to the cross-chain service request, and executing a cross-chain task corresponding to the cross-chain service request; identifying and confirming the cross-chain information related to the cross-chain service request; sending the cross-link information to a node on a second blockchain, so that the node on the second blockchain executes cross-link operation according to the cross-link information; receiving results of the execution of the cross-chain operation from nodes on the second blockchain.

Description

Information interaction method and device based on block chain

Technical Field

The disclosure relates to the technical field of block chains, in particular to an information interaction method and device based on a block chain.

Background

The block chain has the characteristics of multi-party consensus, distributed storage, difficulty in tampering and the like, and has wide application prospects in the aspects of promoting data sharing, improving the cooperation efficiency and establishing a trusted system. Block chains have been applied to a certain extent in the fields of financial science and technology, government affairs and livelihood, judicial evidence storage, supply chain collaboration, tax invoices, copyright protection and the like. With the continuous expansion of the application range and depth of the block chain, the block chain is in flow with various information and values of various industries. The problems of interfacing and interaction between different blockchain systems, between upper layer applications and blockchains, and between links up and down are becoming more and more prominent. No matter the expandability requirement of the technical level or the service scale or horizontal service communication requirement of the service level, the block chain based data interaction is a bottleneck of the requirement of service development, and is a new technical problem to be broken through by the block chain technology.

Disclosure of Invention

In view of the above, the present disclosure provides an information interaction method and apparatus based on a block chain.

In a first aspect, a method for information interaction based on a blockchain is provided, where the method is performed by a node on a first blockchain, and the method includes: receiving a cross-link service request; responding to the cross-chain service request, and executing a cross-chain task corresponding to the cross-chain service request; identifying and confirming the cross-chain information related to the cross-chain service request; sending the cross-link information to a node on a second blockchain, so that the node on the second blockchain executes cross-link operation according to the cross-link information; receiving the execution result of the cross-chain operation from the second blockchain.

In a second aspect, a method for information interaction based on a blockchain is provided, where the method is performed by a node on a second blockchain, and the method includes: after receiving a cross-chain service request, a node on a first blockchain receives cross-chain information related to the cross-chain service request sent by the node on the first blockchain; identifying and confirming the cross-chain information; executing a cross-chain operation according to the cross-chain information; sending the execution result of the cross-chain operation to a node on the first blockchain.

In a third aspect, a method for information interaction based on a blockchain is provided, where the method is performed by a node on a first blockchain, and the method includes: receiving a downlink service request; responding to the downlink service request, and executing an uplink task related to the downlink service request; identifying and confirming the information related to the downlink service request; sending the downlink service request to a downlink system so that the downlink system can execute a downlink task related to the downlink service request; receiving, from the downlinker system, results of execution of the downlinker task.

In a fourth aspect, an information interaction apparatus based on a blockchain is provided, where the apparatus is deployed with a node on a first blockchain, and the apparatus includes: a first receiving unit, configured to receive a cross-link service request; a first execution unit, configured to respond to the cross-chain service request, and execute a cross-chain task corresponding to the cross-chain service request; a first consensus unit, configured to confirm the cross-link information related to the cross-link service request; a first sending unit, configured to send the cross-chain information to a node on a second blockchain, so that the second blockchain performs a cross-chain operation according to the cross-chain information; a second receiving unit, configured to receive an execution result of the cross-chain operation from the second blockchain.

In a fifth aspect, an information interaction apparatus based on a blockchain is provided, where the apparatus is deployed with a node on a second blockchain, and the apparatus includes: a third receiving unit, configured to receive, after a node on a first blockchain accepts a cross-chain service request, cross-chain information related to the cross-chain service request sent by the node on the first blockchain; the second consensus unit is used for confirming the chain-crossing information in a consensus mode; the second execution unit is used for executing the cross-chain operation according to the cross-chain information; a second sending unit, configured to send an execution result of the cross-chain operation to a node on the first blockchain.

In a sixth aspect, an information interaction apparatus based on a blockchain is provided, where the apparatus is deployed with a node on a first blockchain, and the apparatus includes: a fourth receiving unit, configured to receive a downlink service request; a third execution unit, configured to execute an on-chain task related to the off-chain service request in response to the off-chain service request; a third consensus unit, configured to confirm information related to the downlink service request by consensus; a third sending unit, configured to send the downlink service request to a downlink system, so that the downlink system executes a downlink task related to the downlink service request; a fifth receiving unit, configured to receive an execution result of the downlink task from the downlink system. A sixth aspect provides a computer readable storage medium having stored thereon executable code which, when executed, is capable of implementing a method as described in the first or second aspect.

In a seventh aspect, an information interaction apparatus based on a blockchain is provided, which includes a memory and a processor, where the memory stores executable code, and the processor is configured to execute the executable code to implement the method of the first aspect, the second aspect, or the third aspect.

In an eighth aspect, there is provided a computer readable storage medium having stored thereon executable code that, when executed, is capable of implementing a method as described in the first, second or third aspects.

A ninth aspect provides a computer program product comprising executable code which, when executed, is capable of implementing a method as described in the first, second or third aspect.

Based on the method and the device, data interaction among different block chains, between upper-layer application and the block chains and between chains and chains can be realized, so that the block chains are expanded in the technical and business aspects.

Drawings

FIG. 1 is a block chain system.

Fig. 2 is an exemplary diagram of a block chain interoperability framework provided in an embodiment of the disclosure.

Fig. 3 is a schematic flow chart of an information interaction method based on a blockchain according to an embodiment of the present disclosure.

Fig. 4 is a schematic flow chart of a method for implementing message pushing between intelligent contracts between a blockchain according to an embodiment of the present disclosure.

Fig. 5 is a schematic flowchart of a method for implementing ledger pull between block chains according to an embodiment of the present disclosure.

Fig. 6 is a schematic flow chart of another information interaction method based on a blockchain according to an embodiment of the present disclosure.

Fig. 7 is a schematic flow chart of a method for interoperation between a blockchain and an under-chain prediction machine according to an embodiment of the present disclosure.

Fig. 8 is a schematic flow chart of a method for interoperation between a blockchain and an under-chain computing system according to an embodiment of the present disclosure.

Fig. 9 is a schematic structural diagram of an information interaction apparatus based on a block chain according to an embodiment of the present disclosure.

Fig. 10 is a schematic diagram of another information interaction apparatus based on a blockchain according to an embodiment of the present disclosure.

Fig. 11 is a schematic diagram of another information interaction apparatus based on a blockchain according to an embodiment of the present disclosure.

Fig. 12 is a schematic structural diagram of an apparatus provided in an embodiment of the present disclosure.

Detailed Description

The technical solutions in the embodiments of the present disclosure are clearly and completely described below, and it is obvious that the described embodiments are only a part of the embodiments of the present disclosure, and not all embodiments.

For the purpose of facilitating understanding of the embodiments of the present disclosure, some terms related to the embodiments of the present disclosure will be described below.

Block chain (blockchain)

Referring to fig. 1, a blockchain 100 is a typical distributed collaboration system. The system includes a plurality of blockchain nodes 110. The plurality of blockchain nodes 110 may collectively maintain an ever-increasing distributed data record. The recorded data can protect the content and the time sequence through a cryptographic technology, so that any party is difficult to tamper, repudiate and counterfeit. Blockchain nodes 110 may be devices with computing capabilities, such as servers, groups of servers, blockchain chips, etc., where the groups of servers may be centralized or distributed. In other implementations, the server may also be a server that provides services for a cloud platform.

In a blockchain, data (e.g., transaction information, transaction execution results, etc.) may be packaged in blocks (blocks). The tiles may be linked to each other by a forward reference to form a "chain," i.e., a chain of tiles. In general, the first block in a block chain may be referred to as an "originating block" or an "initial block", the one block in the block chain that precedes the current block as a "previous block", and the one block in the block chain that follows the current block as a "subsequent block".

In general, a tile may include a tile head and a tile body. The block header may contain basic information of the current block to ensure that the current block can correctly enter the block chain. For example, the chunk header may record a chunk hash value of a chunk immediately preceding the current chunk. As another example, the block header may also record the block height of the current block. The block height is called "block height" for short, and is used to identify the position of the block in the block chain. Typically, the starting block has a block height of 0. The block body can be used for recording transaction information. The transaction information may include, for example, information such as transaction amount and transaction data.

Blockchains are generally divided into three types: public chains (public chains), private chains (private chains) and federation chains (consortium chains). Furthermore, there may be a combination of the above types, such as private chain + federation chain, federation chain + public chain, and so on. Embodiments provided by the present disclosure can be implemented in a suitable type of blockchain.

Consensus mechanism

The consensus mechanism can be understood as how to agree between the nodes responsible for accounting (or accounting nodes) in the blockchain to identify the validity of a record.

The consensus mechanism of the block chain has the characteristics of 'few obedience majority' and 'human-equal', wherein the 'few obedience majority' does not completely refer to the number of nodes, and can also be the computing power, the number of shares or other characteristic quantities which can be compared by a computer. "equal people" means that when the nodes meet the condition, all the nodes have the right to give priority to the consensus result, are directly identified by other nodes, and finally possibly become the final consensus result. Taking bitcoins as an example, workload proofs are used that it is possible to falsify a record that does not exist only if accounting nodes that control more than 51% of the total network are involved. When enough nodes are added to the blockchain, the method is basically impossible, and therefore the possibility of counterfeiting is eliminated.

The trust of the block chain is mainly embodied in that users distributed in the block chain do not need to trust another party of the transaction or trust a centralized mechanism, and the transaction can be realized only by trusting a software system under a block chain protocol. The premise of self-trust is the consensus mechanism of the blockchain, that is, in a mutually untrusted market, a sufficient requirement for each node to agree is that each node, considering the maximization of its own interest, will spontaneously and honestly obey the rules preset in the protocol, judge the authenticity of each record, and finally record the record judged to be true into the blockchain. In other words, if the nodes have independent interests and compete with each other, the nodes are almost impossible to collude to cheat you, which is especially evident when the nodes have a common reputation in the network. The blockchain technology just applies a set of consensus-based mathematical algorithm to establish a 'trust' network between machines, so that brand-new credit creation is performed through technical endorsements rather than centralized credit organizations.

The present disclosure does not limit the consensus mechanism used by the blockchain, for example, the consensus mechanism of the blockchain may be one of the following consensus mechanisms: a proof of work (PoW), a proof of rights mechanism, a proof of share authorization mechanism, a verification pool mechanism, and a Practical Byzantine Fault Tolerance (PBFT).

Intelligent contract

An intelligent contract (which may be referred to simply as a contract) is a set of commitments defined in digital form, including agreements on which contract participants can enforce the commitments. In other words, a smart contract may be understood as a piece of program deployed on a computer system, and the smart contract may be automatically executed when a trigger condition of the smart contract is satisfied.

The presence of blockchains provides technical support for the implementation of intelligent contracts. The smart contract is written into the block chain in a digital form, and the characteristics of the block chain technology ensure that the whole process of storing, reading and executing the smart contract is transparent, traceable and not easy to modify. On the other hand, a set of state machine system can be constructed by the block chain self-contained consensus algorithm, so that the intelligent contract can run efficiently.

In some implementations, the user can invoke the intelligent contract by submitting a transaction to the blockchain system, set the data recorded in the intelligent contract, and store the set intelligent contract in the blockchain. Accordingly, when a specific condition of the intelligent contract is triggered, the block chain nodes can execute the intelligent contract and record the execution result of the intelligent contract and the execution state of the intelligent contract.

Digital signature

The digital signature may also be referred to as a public-key digital signature, electronic signature, or signature. The digital signature is a digital string which can be generated only by a sender of the information and cannot be forged by others, and the digital string is also a valid proof for the authenticity of the transmitted information. The digital signature can be encrypted and decrypted by using a public key and a private key. A set of digital signatures typically defines two complementary operations, one for the signature and one for the verification. One user signs information as a single sign, and a plurality of users simultaneously sign information as a plurality of signs (namely, multiple signs).

In the block chain, the information and data of the sending node can be prevented from being maliciously forged and tampered by using the digital signature.

Word machine (oracle)

The prediction machine can be used for referencing data on data entities outside the block chain, and further data interaction between the intelligent contract and the data entities of the real world is realized. Data entities outside the chain may include, for example, centralized servers or data centers deployed outside the chain, and so on.

In one embodiment, when deploying a president machine for an intelligent contract on a blockchain system, a president machine intelligent contract corresponding to the president machine may be deployed on the blockchain system. The predictive engine intelligent contract can be used to maintain external data that the predictive engine sends to the intelligent contract on the blockchain system. For example, external data sent by the predictive machine to the smart contracts on the blockchain may be stored in the account storage space of the predictive machine smart contracts. When a target intelligent contract on the blockchain is called, external data required by the target intelligent contract can be read from the account storage space of the prediction machine intelligent contract to complete the calling process of the intelligent contract.

Un-link computing system

The calculation system under the chain can perform calculation tasks outside the blockchain, and after the calculation tasks are completed, calculation results can be returned to the chain, so that the calculation capacity of the blockchain system is expanded and improved. The down-link computing system can utilize a hardware Trusted Execution Environment (TEE) technology to execute trusted computing tasks on the premise of fully protecting data privacy, thereby providing a universal and verifiable private data computing service for users.

In one embodiment, the down-link computing system may support multi-party private data computing. The private data calculation may refer to a calculation that enables privacy protection, the private data being invisible to someone other than the sender by default. For example, the user may send data encryption to the down-link computing system. After the computation of the multi-party privacy data is completed in the TEE, the computation result can be recorded in a block chain in an encrypted manner.

In some embodiments, the offline computing system may include a trusted computing cloud service (C3S). The C3S can provide chain uplink and downlink data cross check for chain application, guarantee credible extension of chain uplink and downlink data, provide universal and privacy-protecting data analysis capability, support multi-party service data fusion and management, and is suitable for scenes such as financial wind control and digital logistics.

From the above, the blockchain has wide application prospects in the aspects of promoting data sharing, improving cooperative efficiency and establishing a trusted system by the characteristics of multi-party consensus, distributed storage, difficulty in tampering and the like. Block chains have been applied to a certain extent in the fields of financial science and technology, government affairs and livelihood, judicial evidence storage, supply chain collaboration, tax invoices, copyright protection and the like. With the continuous expansion of the application range and depth of the block chain, the block chain is in flow with various information and values of various industries. The problems of interfacing and interaction between different blockchain systems, between upper layer applications and blockchains, and between links up and down are becoming more and more prominent. No matter the expandability requirement of the technical level or the service scale or horizontal service communication requirement of the service level, the block chain based data interaction is a bottleneck of the requirement of service development, and is a new technical problem to be broken through by the block chain technology.

The present disclosure proposes a blockchain interoperation framework to solve the problem of interaction between multiple systems including a blockchain system.

Fig. 2 is an exemplary diagram of a block chain interworking framework provided in an embodiment of the present disclosure. Based on the block chain interoperation framework, the information interaction between the block chain system and a first system except the block chain system can be realized. The first system may be other blockchain systems, a down-link system, or an upper-level application system. As shown in fig. 2, for the blockchain system 220a, the first system may be, for example, a blockchain system 220b, a down-link system 230, or an upper layer application 210.

The blockchain system 220 may enable information interaction through various types of instances of the blockchain. Examples may include, for example: a federation chain, a node, a child chain, or an intelligent contract, etc.

The offline system 230 may include, for example, at least one of a predictive engine 231, an offline computing system 232, a third party system, and an internet of things (IoT) system.

The upper layer application system 210 may include at least one application 211, and the present disclosure does not limit the type of the application 211, and may be, for example, a management application or a service application, etc.

The governing application may implement operations on the chain accounts, which may include, for example, at least one of creating, querying, modifying, and freezing.

The service application may obtain blockchain services. The blockchain services may include intra-chain services, inter-chain services, or down-chain services. The in-chain services may include, for example, services related to at least one of data, transactions, contracts, and assets.

Block chain interoperation may be implemented based on the block chain interoperation framework shown in fig. 2. Block chain interoperation may include: inter-chain interoperation, intra-chain inter-chain interoperation, and application and block chain interoperation, etc.

Inter-chain interoperation can realize information intercommunication between different block chain systems. For example, cross-chaining exchange of native assets, cross-chaining ledger access, intelligent contract intermodulation, and the like may be implemented.

The uplink-downlink interoperation can realize message intercommunication between the block chain system and the downlink system. For example, secure trusted interaction of on-chain and off-chain data resources and/or computing resources may be implemented.

Application and chain interoperation may enable application interaction with a blockchain system. Interoperation of applications and the blockchain system may be achieved, for example, through an interface provided by the blockchain system.

The block chain interoperation method provided by the present disclosure is described in detail below with reference to fig. 3 to 8 based on the above framework.

Fig. 3 is a schematic flow chart of a method for information interaction between different blockchains according to an embodiment of the present disclosure. The method may be performed by a first blockchain (e.g., a node on the first blockchain), a second blockchain (e.g., a node on the second blockchain), and a user.

The method shown in fig. 3 may include steps S310 to S390.

In step S310, the first blockchain receives a cross-chain service request.

Cross-chain traffic may include blockchains and traffic between blockchains (inter-chain traffic). The cross-chain business request may include a request to obtain a blockchain service, such as a service related to data, a transaction, a contract, or an asset.

The cross-chain service request may be user submitted. The present disclosure does not limit the manner in which a user submits or communicates a cross-chain service request. For example, a user may make a cross-chain service request through an application.

In step S320, the first blockchain responds to the cross-chain service request, and executes a cross-chain task corresponding to the cross-chain service request.

The first blockchain may determine a cross-chain task from the cross-chain business request, and the cross-chain task may include, for example: the method comprises the steps of account book pulling, message pushing between intelligent contracts and the like.

In step S330, the first blockchain consensus confirms the cross-chain information related to the cross-chain service request.

The cross-chain information is related to the cross-chain service request. The cross-chain information may include operations that the first blockchain wishes the second blockchain to perform, which may include, for example, invocation of smart contracts or ledger pull. Alternatively, the cross-chain information may include data that the first blockchain wishes to send to the second blockchain.

The first blockchain may implement consensus validation using any of the consensus methods described above, and the disclosure is not limited in this respect.

In step S340, the first blockchain sends cross-chain information to the second blockchain.

In some embodiments, the first blockchain may be referred to as a sender and the second blockchain may be referred to as a receiver. In other embodiments, the first blockchain may be referred to as a source chain and the second blockchain may be referred to as a target chain.

The first blockchain may encapsulate the cross-chain information into a data packet and then send the data packet to the second blockchain. The data packet may include inter-chain information as well as other information, which may include, for example, an address of the second blockchain. It will be appreciated that the type of service across the chain is different, and the packets are also different. For example, when the smart contract message is pushed, the data packet may be a cross-chain data packet, and the cross-chain data packet may include the address of the second blockchain and the cross-chain message pushed by the smart contract. Or, when the ledger data is pulled, the data packet may be a ledger pulling data packet, and the ledger pulling data may include ledger data that the first block chain wishes to pull. The data packet can be packaged into a format which can be analyzed by a receiver of the data packet, so that the receiver can check the data packet, and the data packet is prevented from being tampered in the transmission process, and the credibility of the data packet is improved.

Components can be deployed on blockchains to enable the transfer and encapsulation of information (e.g., cross-chain information) in cross-chain business requests. The information in the cross-chain service request may include, for example: at least one of an address of the second blockchain, an intelligent contract sending message pushing request and an account book pulling request. The intelligent contract or account on the blockchain may invoke this component to pass the information described above. Taking the intelligent contract message push as an example, both blockchains may include a cross-chain message component. Or, taking account book pulling as an example, both blockchains may deploy account book access components.

The first blockchain may send a cross-chain message to the second blockchain through the relay component. The relay component can realize the routing function and relay and deliver the cross-chain information to the second block chain. The relay component may verify the received cross-link information and may also generate a verification result or proof. For example, the relay component may perform a validity check on the data packet encapsulated by the cross-chain message component, generate a validity proof, and deliver both the cross-chain information and the validity proof to the second blockchain. The second blockchain may verify the cross-chain information based on the validation certificate. Therefore, the relay component can prevent the cross-link information from being tampered during transmission, thereby improving the credibility during data transmission.

The relay component may be implemented using a block chain. Alternatively, the relay component may be implemented using a separate modular component. The relay component may be implemented outside the first blockchain, i.e. forming an under-chain relay component. For one embodiment, the down-link relay component may be one of C3S.

It is to be understood that the above-mentioned cross-chain message component, ledger access component or relay component may be implemented in the form of a component, and therefore, the cross-chain message component, ledger access component or relay component may be implemented based on an existing system (including a blockchain system or an off-chain system), that is, adding at least one component to the existing system may implement interoperation of a blockchain. Therefore, a system for block chain interoperation does not need to be separately developed, so that the block chain interoperation is simple and convenient, and the efficiency is higher.

Optionally, the method shown in fig. 3 may include step S350. In step S350, the second blockchain verifies the identity of the first blockchain.

For one embodiment, the first blockchain and/or the second blockchain may be assigned a verifiable global identity. The global identity may support non-interactive authentication. The second blockchain may verify the identity of the first blockchain according to the global identity of the first blockchain.

Optionally, the method shown in fig. 3 comprises step S360. In step S360, the second blockchain verifies the cross-chain information.

The verification of the cross-chain information by the second blockchain may include: at least one of authenticity, integrity, accuracy, trustworthiness, validity of the cross-chain information. The authenticity can verify the identity of the sender of the cross-link information, and for example, the validity of the received data can be actively verified through a cryptology mechanism. Integrity can verify whether the cross-chain information is complete to ensure that the cross-chain information is accurate and has not been tampered. The credibility can verify whether the data format is correct or not, and can also verify that the sender of the cross-link information really exists.

The second blockchain may enable verification of the first blockchain identity and/or cross-chain information by a component deployed on the second blockchain. The component may be, for example, a cross-chain message component and/or an ledger access component deployed on the second blockchain.

In step S370, the second blockchain performs consensus confirmation on the cross-chain information. Through consensus confirmation, the effectiveness of the cross-chain information can be identified, thereby avoiding counterfeiting.

In step S380, the second blockchain performs a cross-chain operation corresponding to the cross-chain service request.

The cross-chain operations may include sending a cross-chain message to the target account or target intelligent contract and/or collecting the accounts that the first blockchain wishes to pull. In some embodiments, a cross-chain operation may also be referred to as cross-chain logic.

In step S390, the second blockchain sends the execution result of the cross-chain operation to the first blockchain.

The execution result may include whether the cross-chain operation was successfully executed. Based on receiving the execution result, consistency of the first blockchain and the second blockchain can be achieved. Taking a system in which the first blockchain and the second blockchain both support asset or information cross-chaining as an example, a cross-chaining request initiated by the first blockchain and aiming at changing the states of the first blockchain and the second blockchain can meet atomicity between the first blockchain and the second blockchain according to a feedback result. Atomicity is either a successful execution in both the first blockchain and the second blockchain, or a failure in execution in both chains.

Based on the method provided by the embodiment of the disclosure, data interaction between different block chains, between an upper layer application and the block chain, and between the chain and the chain can be realized, so that the block chain is expanded in the technical and service level.

It should be noted that the present disclosure does not limit the structure of the blockchain, and the first blockchain and the second blockchain may be homogeneous chains or heterogeneous chains.

It should be noted that the first blockchain and/or the second blockchain may have transactional functions, such as: an extensible Remote Procedure Call (RPC), atomic asset exchange, etc.

For ease of understanding, the method of inter-chain interoperation will be described in detail below with reference to the first embodiment and the second embodiment.

The first embodiment is as follows: message push between intelligent contracts between block chains

Fig. 4 is a schematic flowchart of a method for implementing message pushing between intelligent contracts between blockchains according to an embodiment of the present disclosure. The method may be implemented by a first blockchain (e.g., a node on the first blockchain), a second blockchain (e.g., a node on the second blockchain), and a down-link relay component. The first blockchain may have a first intelligent contract and a first cross-chain message component deployed thereon, and the second blockchain has a second intelligent contract and a second cross-chain message component deployed thereon.

The method illustrated in fig. 4 includes steps S410 to S440.

In step S410, the first blockchain delivers a cross-chain service request.

For one embodiment, an account or a first intelligent contract on a first blockchain may invoke a first cross-chain component to pass information in a cross-chain business request. The information in the cross-chain service request may include a message push request (e.g., a cross-chain message) sent by the first intelligent contract to the second intelligent contract, and the information in the cross-chain service request may also include an address of the second blockchain, i.e., a target address.

In step S420, the first blockchain encapsulates the message push request into a cross-chain data packet. The first cross-chain message component may also encapsulate other data, such as the address of the second blockchain, in a cross-chain data packet. The first cross-link message component can also output the cross-link data packet to the down-link relay component in a mode that the down-link can be analyzed, and the cross-link data packet is sent to the second intelligent contract of the second block chain through the down-link relay component.

In step S430, the downlink relay component checks the data packet. For example, the validity of the data packet may be checked and a proof of validity generated. And the down-link relay component delivers the data packet and the validity certificate to a second cross-link message component of the second block chain. Wherein the down-link relay component may belong to a down-link cross-link message processing application.

In step S440, the second blockchain checks the data packet.

As an implementation, the second cross-chain message component of the second blockchain may check the validity of the data packet according to the validity certificate. After the check is completed, the second blockchain may pass the data packet to a second intelligent contract on the chain.

As can be seen from the above steps, by deploying the cross-chain message components (i.e., the first cross-chain message component and the second cross-chain message component) on both blockchains, it is possible to receive a cross-chain request of a user, and also to implement communication between the first blockchain and the second blockchain, and check cross-chain data interacted between the first blockchain and the second blockchain. That is, based on the cross-chain message component of the blockchain, the push of messages between trusted intelligent contracts can be implemented between different blockchains.

Example two: realize that account book draws between block chain and get

Fig. 5 is a schematic flowchart of a method for implementing account book pulling between block chains according to an embodiment of the present disclosure. The method may be implemented by a first blockchain (e.g., a node on the first blockchain), a second blockchain (e.g., a node on the second blockchain), and a down-link relay component. A first ledger access component may be deployed on the first blockchain, and a second ledger access component may be deployed on the second blockchain. The method illustrated in fig. 5 includes steps S510 to S540.

Step S510, the first blockchain initiates a cross-chain service request.

As one embodiment, an account or smart contract on a first blockchain may invoke a first ledger access component to initiate or pass information in a cross-chain business request. The information in the cross-chain business request may include an account of the first blockchain or an ledger pull request of an intelligent contract to obtain target ledger data. The information in the cross-chain service request may include an address of the second blockchain.

In step S520, the first blockchain encapsulates the cross-chain service request into an account book pull data packet. The ledger pull packet may also include other data, such as the address of the second blockchain. As an implementation manner, the first ledger access component may encapsulate the cross-link request into a cross-link data packet, output the data packet to the down-link relay component in a manner that the data packet can be resolved under the link, and pull the ledger data of the second block link through the down-link relay component.

In step S530, the downlink relay component checks the account book pull packet. For example, the validity of the data packet may be checked and a proof of validity generated. The downlink relay component may deliver the data packet and the validity certificate to a second ledger access component of a second blockchain. The second ledger access component may transmit the cross-chain data packet to a ledger or an intelligent contract of the second blockchain. Wherein the down-link relay component may belong to a down-link account pull processing application.

In step S540, the second blockchain checks the ledger pull packet.

As an implementation, the second ledger access component of the second blockchain may verify the validity of the data packet according to the validity proof. After the verification is completed, the down-chain relay component can collect the target account book data and the validity proof of the target account book data, and delivers the data to the first account book access component of the first block chain. The first account book access component of the first block chain can verify the validity of the account book data according to the validity proof, and after the verification is completed, the target account book data is transmitted to the target contract or the target account on the chain.

As can be seen from the above steps, by deploying the account book access component on each block chain, that is, deploying the first account book access component and the second account book access component on the first block chain and the second block chain, respectively, the cross-chain service request can be obtained, communication between the first block chain and the second block chain can also be realized, and verification of cross-chain data interacted between the first block chain and the second block chain is realized. That is, based on the blockchain ledger component, a trusted ledger pull can be implemented between different blockchains.

The method for inter-chain interoperation proposed by the embodiment of the present disclosure is described above with reference to fig. 3 to 5. The method for chain uplink and downlink interoperation provided by the embodiment of the present disclosure will be described in detail below with reference to fig. 6 to 8.

Fig. 6 is a schematic flowchart of a data interaction method between a blockchain and a system under the chain according to an embodiment of the present disclosure. The method shown in fig. 6 may be performed by the first blockchain, the system under the chain, and the user. The method shown in fig. 6 may include steps S610 to S680.

In step S610, the first block link receives a downlink service request sent by the user.

A user (task originator) may cross-link a service request down the first blockchain. The downlink traffic request may include a downlink calculation and/or a downlink data read.

Step S620, the first blockchain responds to the downlink service request, and executes an uplink task related to the downlink service request.

The first blockchain determines the on-chain tasks to be executed on the chain according to the off-chain service request. An on-chain task may be any operation that can be performed on a block chain, which is not limited by this disclosure. For example, an on-chain task may include collecting data to be computed for computation by an off-chain system. Alternatively, the on-chain task may include invoking an intelligent contract related to the off-chain business request.

In step S630, the first blockchain consensus confirms information related to the downlink service request.

In step S640, the first block chain sends a downlink service request to the downlink system, so that the downlink system executes a downlink task related to the downlink service request.

The first blockchain may encapsulate the downlink service request into a data packet and send the data packet to the downlink system. The data packet may include a down-link service request as well as other information, which may include, for example, an address of the second blockchain. It will be appreciated that the type of service across the chain is different, and the packets are also different. The data packet can be encapsulated into a format that can be analyzed by a receiver of the data packet, so that the receiver can check the data packet, and the data packet can be prevented from being tampered in the transmission process.

The first blockchain can realize the packaging of cross-chain information and the transmission of information of a service request under a chain through the components arranged on the first blockchain. Taking the interaction between the blockchain and the predictive engine as an example, the predictive engine component can be deployed on the first blockchain to implement encapsulation of cross-chain information and transfer of information in the service request under the chain. Alternatively, taking the interaction between the blockchain and the offline computing system as an example, an external computing component may be deployed on the first blockchain to implement encapsulation of the cross-chain information and transfer of information of the offline service request. It is to be understood that the components may also be deployed on an existing first blockchain, which may simplify the development of blockchain interoperation, i.e., the interoperation of the blockchain may be implemented by adding at least one component to an existing system. Therefore, a system for block chain interoperation does not need to be separately developed, so that chain uplink and downlink interoperation is simple and convenient, and efficiency is higher.

For one embodiment, the first blockchain may be assigned a verifiable global identity. The global identification may support non-interactive authentication. The system under the chain can verify the identity of the first blockchain according to the global identity of the first blockchain. It is to be appreciated that the identity of the first blockchain is verified by the system under chain, which can determine that the first blockchain is truly present.

Step S660, the downlink system verifies the downlink service request.

The downlink system may verify at least one of authenticity, integrity, accuracy, trustworthiness, and validity of the downlink service request. Therefore, whether the downlink service request is complete, accurate and not tampered can be determined.

In step S670, the linked system executes the linked task.

For example, when the system is a predictive machine, the predictive machine may perform the task of collecting the data that the first blockchain wishes to acquire. Alternatively, when the down-link system is a down-link computing system, the down-link tasks performed by the down-link computing system may be computing tasks.

In step S680, the linked system sends the execution result of the linked task to the first block chain.

The execution results of the linked tasks may include, for example, collected target data, calculation results, and the like.

Optionally, the method shown in fig. 6 may further include step S691 or step S692.

In step S691, the first blockchain verifies the execution result of the system under the link and generates a verification result.

The off-chain system may deliver the execution results to the component on the first blockchain for the component to verify the execution results. It is to be appreciated that the execution results can be posted to a predictive engine component or an external computing component, which can verify the execution results. In this case, the predictive engine component or the external computing component may have the functionality to collect, send, or process cross-chain information at the same time. Taking the downlink system as the downlink computing system as an example, the external computing component may implement encapsulation and transmission of the downlink service request, and may also implement reception and verification of the downlink task execution result. Taking the downlink system as the predictive machine as an example, the predictive machine component can implement the encapsulation and sending of the contact service request, and can also implement the receiving and verification of the downlink data.

In step S692, the first blockchain returns the verification result to the task initiator for confirmation or synchronization by the task initiator.

For ease of understanding, the method of on-chain and off-chain interoperation will be described in detail below with reference to example three and example four.

Example three: interoperation between blockchain and under-chain predictive

Fig. 7 is a schematic flowchart of an interoperation method between a blockchain and an under-chain prediction machine according to an embodiment of the present disclosure. The method may be implemented by a first blockchain (e.g., a node in the first blockchain) and a prediction machine. The first blockchain may be deployed with a predictive engine component for communicating with the down-link predictive engine for obtaining the down-link data.

The method illustrated in fig. 7 may include steps S710 to S760.

Step S710, the first blockchain initiates a downlink service request.

As one embodiment, an account or smart contract on a first blockchain may invoke a predictive engine component to initiate or pass information in an off-chain business request. The downlink service request may include, for example: request to acquire the downlink data (i.e., target data) desired to be acquired.

In step S720, the first blockchain encapsulates the downlink service request into a data packet. As one embodiment, step S720 may be implemented using a predictive engine component.

In step S730, the prolog engine component of the first blockchain outputs the data packet to the downlink prolog engine in a manner that the downlink prolog engine can parse the data packet. As one embodiment, step S730 may be implemented using a predictive engine component.

Step S740, the prediction machine checks the data packet. For example, the validity of the data packet may be checked.

In step S750, the prediction engine collects the target data and signs the target data. The target data and signature are delivered to a prolog component of the first blockchain.

In step S760, the first blockchain checks the received target data. The target data may be verified for validity, accuracy or trustworthiness based on the speaker signature, for example. After the verification is complete, the first blockchain may pass the target data to a target contract or a target account on the chain.

As can be seen from the above steps, by deploying the predictive engine component on the first blockchain, communication between the first blockchain and the predictive engine can be achieved, and verification of data interacted between the first blockchain and the predictive engine can also be achieved. That is, based on the prolog machine component of the blockchain, trusted interaction between the blockchain and the prolog machine can be achieved.

It should be noted that the prolog engine can provide an effective method to confirm the called record of the prolog engine, so as to improve the traceability of the interoperation.

Alternatively, the predictive machine may be a predictive machine that supports a trusted execution environment. As one embodiment, a predictive machine that supports a trusted execution environment may enable trusted storage of data such that data stored by the predictive machine cannot be deleted or tampered with. As another example, a predictive engine that supports a trusted execution environment may have the ability to provide proof that application output is coming from trusted hardware to increase the trustworthiness of data stored within the predictive engine.

Example four: interoperation between blockchains and down-chain computing systems

Fig. 8 is a schematic flow chart of an interoperation method between a blockchain and a computing system under the chain according to an embodiment of the present disclosure. The method may be implemented by a first blockchain (e.g., a node on the first blockchain) and a down-chain computing system. The first blockchain may include an external computing component for communicating with the down-link computing system to complete a computing task corresponding to the computing request. For example, an account or smart contract for a first blockchain may invoke an external computing component to pass information in the down-chain business request.

The method illustrated in fig. 8 includes steps S810 to S860.

In step S810, the first blockchain initiates a request.

As one embodiment, an account or smart contract on a first blockchain may invoke a predictive engine component to initiate or pass a request. The request may include, for example: the account of the first blockchain or the calculation request of the intelligent contract, i.e. the calculation that is desired to be performed by the computing system down the chain.

In step S820, the first blockchain encapsulates the request into a data packet. As one embodiment, step S820 may be implemented using an external computing component.

In step S830, the first blockchain outputs the data packet to the downlink in a manner interpretable by the downlink computing system. As one embodiment, step S830 may be implemented using an external computing component.

In step S840, the calculating system checks the data packet. For example, the validity of the data packet may be checked.

Alternatively, the down-link computing system may be a down-link computing system that supports a trusted execution environment. As one embodiment, a chain down computing system supporting a trusted execution environment may not have the logic, inputs of the chain down computing system deleted or tampered with. As another example, an off-chain computing system that supports a trusted execution environment may have the ability to provide proof that application output is from trusted hardware to improve the trustworthiness of the off-chain computing system computing.

Alternatively, the down-link computing system may be provided with extensibility, e.g., to support programmability.

Alternatively, the down-link computing system may be provided with a library of computing classes, such as an artificial intelligence algorithm library.

Optionally, the down-link computing system may have capacity expansion capability to handle large data operation requirements.

Alternatively, the down-link computing system may support privacy-preserving computing capabilities, such as may be implemented by mechanisms such as TEE, Zero Knowledge Proof (ZKP), multiparty security computing (MPC), and so on.

Alternatively, the down-link computing system may provide an efficient method to validate records that the down-link computing system is invoked to improve interoperability traceability.

And step S850, the calculation system under the chain finishes the calculation task corresponding to the request, obtains the calculation result and signs the calculation result. The down-chain computing system may deliver the computed result and the signature to an external computing component of the first blockchain.

It should be noted that the down-link computing system may ensure the integrity of the computing process and/or the verifiability of the results. The present disclosure is not limited to a specific implementation, and may be implemented by mechanisms such as TEE, ZKP, verifiable computing, and the like.

In step S860, the first blockchain check receives the calculation result. For example, the external computing component may verify the validity, accuracy, or trustworthiness of the computed result based on the signature. After verification is complete, the first blockchain may pass the calculation to a target contract or a target account on the chain.

As can be seen from the above steps, by deploying an external computing component on the first blockchain, communication between the first blockchain and the down-link computing system can be achieved, and data exchanged between the first blockchain and the down-link computing system can also be checked. That is, based on the external computing components of the blockchain, trusted interactions between the blockchain and the computing system under the chain may be achieved.

It should be noted that any cross-chain data can be verified in the steps shown in fig. 3 to 8. The inter-chain data may be data that flows between different blockchains, between blockchains and an off-chain system, and between blockchains and applications. The cross-chain data may include, for example, one or more of cross-chain information, an execution result of the cross-chain information, a verification result of the execution result, a packet, first data requested to be obtained by the first blockchain, and the like. Through verification, authenticity, integrity, accuracy or credibility of cross-chain data can be guaranteed. It is to be appreciated that the first blockchain, the second blockchain, or the system under the chain can all implement authentication. Alternatively, a third party verifier may effect the verification. The third party verifier may be trusted, and trusted verification by the third party verifier may be achieved through a single-sign, multi-sign, or TEE trusted computing execution environment, among other mechanisms.

It should be noted that the interoperation of the application and the block chain proposed by the present disclosure may include at least one of the following operations: applying an operation (e.g., including at least one of creating, querying, modifying, freezing) to an account on the chain; the application obtains the block chain service through the interface, wherein the block chain service comprises at least one of intra-chain service, inter-chain service and under-chain service; the pushing of the events on the chain to the application is realized in a mode of subscribing the events; the application deploys and configures the blockchain system, and performs full-life-cycle management operation on each type of instance (alliance chain/node/sub chain/contract) of the blockchain; the operation, monitoring, maintenance and upgrading of the block chain system are applied; and carrying out safety treatment and audit on the block chain.

Method embodiments of the present disclosure are described above in conjunction with fig. 3-8, and apparatus embodiments of the present disclosure are described below in conjunction with fig. 9-12.

Fig. 9 is a schematic structural diagram of an information interaction apparatus 900 based on a block chain according to an embodiment of the present disclosure. Apparatus 900 is deployed with nodes on a first blockchain that can be communicatively connected with a second blockchain, apparatus 900 comprising: a first receiving unit 910, a first executing unit 920, a first identifying unit 930, a first sending unit 940 and a second receiving unit 950.

The first receiving unit 910 may be configured to receive a cross-chain service request.

The first execution unit 920 may be configured to execute, in response to the cross-chain service request, a cross-chain task corresponding to the cross-chain service request.

The first consensus unit 930 may be configured to agree on cross-chain information related to the cross-chain service request.

The first sending unit 940 may be configured to send the cross-link information to a node on the second blockchain, so that the node on the second blockchain performs a cross-link operation according to the cross-link information.

The second receiving unit 950 may be configured to receive a result of performing the cross-chain operation from a node on the second blockchain.

Optionally, a node on the first blockchain is deployed with a first intelligent contract and a first cross-chain message component, a node on the second blockchain is deployed with a second intelligent contract and a second cross-chain message component, information in the cross-chain service request is transferred by the first intelligent contract invoking the first cross-chain message component, and the cross-chain service request includes a message push request sent by the first intelligent contract to the second intelligent contract, and the first cross-chain message component is configured to encapsulate the message push request into a cross-chain data packet, so as to transmit the cross-chain data packet to the second intelligent contract through the second cross-chain message component.

Optionally, a first account book access component is deployed at a node on the first blockchain, a second account book access component is deployed at a node on the second blockchain, information in the cross-chain business request is transferred by an account or an intelligent contract of the first blockchain to the first account book access component, the cross-chain business request includes an account or an account book pulling request of the intelligent contract of the first blockchain, and the first account book access component is configured to encapsulate the account book pulling request to a cross-chain data packet, so that the cross-chain data packet is transmitted to the account or the intelligent contract of the second blockchain through the second account book access component.

Optionally, an under-link relay component is disposed between the first blockchain and the second blockchain, and the under-link relay component is configured to relay the cross-link packet.

Optionally, the downlink relay component is further configured to check validity of the data in the cross-chain data packet, and send a validity proof of the data in the cross-chain data packet to the second blockchain.

Fig. 10 is a schematic diagram of an information interaction apparatus 1000 based on a block chain according to an embodiment of the present disclosure. Apparatus 1000 is deployed with nodes on a second blockchain that can be communicatively connected with a first blockchain, apparatus 1000 comprising: a third receiving unit 1010, a second recognizing unit 1020, a second executing unit 1030 and a second sending unit 1040.

The third receiving unit 1010 may be configured to receive, after a node on the first blockchain receives a cross-chain service request, cross-chain information related to the cross-chain service request sent by the node on the first blockchain.

The second consensus unit 1020 is used for consensus confirmation of the cross-chain information.

The second execution unit 1030 may be configured to execute the cross-chain operation according to the cross-chain information.

The second sending unit 1040 may be configured to send the execution result of the cross-chain operation to the first blockchain.

Optionally, a first account book access component is deployed on the first blockchain, a second account book access component is deployed on a node on the second blockchain, information in the cross-chain business request is transferred by an account or an intelligent contract of the first blockchain to the first account book access component, the cross-chain business request includes an account book pull request of the account of the first blockchain, and the first account book access component is configured to encapsulate the account book pull request to the cross-chain data packet, so that the cross-chain data packet is transmitted to the account or the intelligent contract of the second blockchain through the second account book access component.

Optionally, the apparatus 1000 may further include: the authentication unit is used for authenticating the identity of the first block chain; and/or a second verification unit for verifying the cross-chain information.

Fig. 11 is a schematic diagram of an information interaction apparatus 1100 based on a block chain according to an embodiment of the present disclosure. The apparatus 1100 is deployed with nodes on a first blockchain that can be communicatively connected to an off-chain system, the apparatus 1100 comprising: a fourth receiving unit 1110, a third executing unit 1120, a third recognizing unit 1130, a third sending unit 1140 and a fifth receiving unit 1150.

The fourth receiving unit 1110 may be configured to receive a downlink service request; the third execution unit 1120 may be configured to execute an on-chain task related to the off-chain service request in response to the off-chain service request; the third consensus unit 1130 may be configured to agree to confirm information related to the downlink service request; the third sending unit 1140 may be configured to send the downlink service request to the downlink system, so that the downlink system performs a downlink task related to the downlink service request; the fifth receiving unit 1150 may be used to receive the execution result of the downlink task from the downlink system.

Optionally, a preplan machine component is deployed at a node on the first blockchain, the offline system is an offline preplan machine, information of the offline service request is transferred by the account of the first blockchain or the intelligent contract calling the preplan machine component, the offline service request includes offline data that the account of the first blockchain or the intelligent contract desires to acquire, and the preplan machine component is used for communicating with the offline preplan machine to acquire the offline data.

Optionally, an external computing component is deployed at a node on the first blockchain, the system below the chain is a system below the chain, information of the service request below the chain is transferred by the account of the first blockchain or the intelligent contract calling the external computing component, the service request below the chain includes the computing request of the account of the first blockchain or the intelligent contract, and the external computing component is used for communicating with the system below the chain to complete a computing task corresponding to the computing request.

Fig. 12 is a schematic structural diagram of an apparatus according to yet another embodiment of the present disclosure. The apparatus 1200 may be, for example, a computing device having computing functionality. For example, the apparatus 1200 may be a server. The apparatus 1200 may include a memory 1210 and a processor 1220. Memory 1210 may be used to store executable code. The memory 1210 may also be used to store map data. The processor 1220 may be configured to execute the executable code stored in the memory 1210 to implement the steps of the various methods described above. In some embodiments, the apparatus 1200 may further include a network interface 1230, and data exchange between the processor 1220 and external devices may be implemented through the network interface 1230.

It will be appreciated that in the above embodiments, the methods and steps performed by the blockchain may be performed by nodes of the blockchain. The method provided by the embodiment can be applied to a cross-chain product or a block chain as a service (BaaS). In addition, in the above embodiment, the blockchain deployed in the apparatus may be deployed as a node of the blockchain.

In the above embodiments, all or part of the implementation may be realized by software, hardware, firmware or any other combination. When implemented in software, may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. The procedures or functions described in accordance with the embodiments of the disclosure are, in whole or in part, generated when the computer program instructions are loaded and executed on a computer. The computer may be a general purpose computer, a special purpose computer, a network of computers, or other programmable device. The computer instructions may be stored on a computer readable storage medium or transmitted from one computer readable storage medium to another, for example, from one website, computer, server, or data center to another website, computer, server, or data center via wire (e.g., coaxial cable, fiber optic, Digital Subscriber Line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.). The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device, such as a server, a data center, etc., that incorporates one or more of the available media. The usable medium may be a magnetic medium (e.g., a floppy disk, a hard disk, a magnetic tape), an optical medium (e.g., a Digital Video Disk (DVD)), or a semiconductor medium (e.g., a Solid State Disk (SSD)), among others.

Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present disclosure.

In the several embodiments provided in the present disclosure, it should be understood that the disclosed system, apparatus, and method may be implemented in other ways. For example, the above-described apparatus embodiments are merely illustrative, and for example, the division of the units is only one logical division, and other divisions may be realized in practice, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.

The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.

In addition, functional units in the embodiments of the present disclosure may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit.

The above description is only for the specific embodiments of the present disclosure, but the scope of the present disclosure is not limited thereto, and any person skilled in the art can easily conceive of the changes or substitutions within the technical scope of the present disclosure, and all the changes or substitutions should be covered within the scope of the present disclosure. Therefore, the protection scope of the present disclosure shall be subject to the protection scope of the claims.

Claims

1. A method of information interaction based on blockchains, the method being performed by a node on a first blockchain,

the method comprises the following steps:

receiving a cross-link service request;

responding to the cross-chain service request, and executing a cross-chain task corresponding to the cross-chain service request;

identifying and confirming the cross-chain information related to the cross-chain service request;

sending the cross-link information to a node on a second blockchain, so that the node on the second blockchain executes cross-link operation according to the cross-link information;

receiving results of the execution of the cross-chain operation from nodes on the second blockchain.

2. The method of claim 1, wherein a node on the first blockchain is deployed with a first intelligent contract and a first cross-chain message component, wherein a node on the second blockchain is deployed with a second intelligent contract and a second cross-chain message component, wherein information in the cross-chain service request is passed by the first intelligent contract invoking the first cross-chain message component, and wherein the cross-chain service request comprises a message push request sent by the first intelligent contract to the second intelligent contract, and wherein the first cross-chain message component is configured to encapsulate the message push request into a cross-chain data packet for transmission to the second intelligent contract by the second cross-chain message component.

3. The method of claim 1, a node on the first blockchain having a first ledger access component deployed thereon, a node on the second blockchain having a second ledger access component deployed thereon, information in the cross-chain business request being passed by an account or smart contract call of the first blockchain to the first ledger access component, and the cross-chain business request comprising a ledger pull request of the account or smart contract of the first blockchain, the first ledger access component for encapsulating the ledger pull request into a cross-chain data packet for transmission of the cross-chain data packet to the account or smart contract of the second blockchain through the second ledger access component.

4. The method of claim 2 or 3, wherein a down-link relay component is disposed between the first blockchain and the second blockchain, and the down-link relay component is configured to relay the cross-link packet.

5. The method of claim 4, the downlinker relay component further for checking the validity of the data in the cross-chain data packet and sending a proof of validity of the data in the cross-chain data packet to the second blockchain.

6. A method of information interaction based on a blockchain, the method being performed by a node on a second blockchain,

the method comprises the following steps:

after a node on a first blockchain receives a cross-chain service request, receiving cross-chain information related to the cross-chain service request sent by the node on the first blockchain;

identifying and confirming the cross-chain information;

executing a cross-chain operation according to the cross-chain information;

sending the execution result of the cross-chain operation to a node on the first blockchain.

7. The method of claim 6, wherein a node on the first blockchain is deployed with a first intelligent contract and a first cross-chain message component, wherein a node on the second blockchain is deployed with a second intelligent contract and a second cross-chain message component, wherein information in the cross-chain service request is passed by the first intelligent contract invoking the first cross-chain message component, and wherein the cross-chain service request comprises a message push request sent by the first intelligent contract to the second intelligent contract, and wherein the first cross-chain message component is configured to encapsulate the message push request into a cross-chain data packet for transmission to the second intelligent contract by the second cross-chain message component.

8. The method of claim 6, a node on the first blockchain deployed with a first ledger access component, a node on the second blockchain deployed with a second ledger access component, information in the cross-chain business request passed by the first ledger access component invoked by an account or smart contract of the first blockchain, and the cross-chain business request comprising a ledger pull request of the account or smart contract of the first blockchain, the first ledger access component to encapsulate the ledger pull request into a cross-chain data packet for transmission of the cross-chain data packet to the account or smart contract of the second blockchain through the second ledger access component.

9. The method of claim 6, prior to the performing a cross-chain operation according to the cross-chain information, the method further comprising:

authenticating the identity of the first blockchain; and/or

And verifying the cross-chain information.

10. A method of blockchain-based information interaction, the method being performed by a node on a first blockchain, the method comprising:

receiving a downlink service request;

responding to the downlink service request, and executing an uplink task related to the downlink service request;

identifying and confirming the information related to the downlink service request;

sending the downlink service request to a downlink system so that the downlink system can execute a downlink task related to the downlink service request;

receiving, from the downlinker system, results of execution of the downlinker task.

11. The method of claim 10, wherein a node on the first blockchain is deployed with a preplanning machine component, the offline system is an offline preplanning machine, information in the offline service request is transferred by an account or an intelligent contract of the first blockchain calling the preplanning machine component, and the offline service request contains offline data that the account or the intelligent contract of the first blockchain wishes to obtain, and the preplanning machine component is used for communicating with the offline preplanning machine to obtain the offline data.

12. The method of claim 10, wherein an external computing component is deployed at a node on the first blockchain, the off-chain system is an off-chain computing system, information in the off-chain service request is passed by an account or an intelligent contract of the first blockchain invoking the external computing component, and the off-chain service request includes a computing request of the account or the intelligent contract of the first blockchain, and the external computing component is configured to communicate with the off-chain computing system to complete a computing task corresponding to the computing request.

13. An information interaction device based on a blockchain, the device being deployed with nodes on a first blockchain, the device comprising:

a first receiving unit, configured to receive a cross-link service request;

a first execution unit, configured to respond to the cross-chain service request, and execute a cross-chain task corresponding to the cross-chain service request;

a first consensus unit, configured to confirm the cross-link information related to the cross-link service request;

a first sending unit, configured to send the cross-link information to a node on a second blockchain, so that the node on the second blockchain performs a cross-link operation according to the cross-link information;

a second receiving unit, configured to receive an execution result of the cross-chain operation from a node on the second blockchain.

14. The apparatus of claim 13, a node on the first blockchain deployed with a first intelligent contract and a first cross-chain message component, a node on the second blockchain deployed with a second intelligent contract and a second cross-chain message component, information in the cross-chain service request passed by the first intelligent contract invoking the first cross-chain message component, and the cross-chain service request comprising a message push request sent by the first intelligent contract to the second intelligent contract, the first cross-chain message component to encapsulate the message push request into a cross-chain data packet for transmission of the cross-chain data packet to the second intelligent contract by the second cross-chain message component.

15. The apparatus of claim 13, a node on the first blockchain deployed with a first ledger access component, a node on the second blockchain deployed with a second ledger access component, information in the cross-chain business request passed by an account or smart contract call of the first blockchain to the first ledger access component, and the cross-chain business request comprising a ledger pull request of the account or smart contract of the first blockchain, the first ledger access component to encapsulate the ledger pull request into a cross-chain data packet for transmission of the cross-chain data packet to the account or smart contract of the second blockchain through the second ledger access component.

16. The apparatus according to claim 14 or 15, wherein a down-link relay component is disposed between the first blockchain and the second blockchain, and the down-link relay component is configured to relay the cross-link packet.

17. The apparatus of claim 16, the down-link relay component further configured to verify validity of data in the cross-link data packet and send a proof of validity of data in the cross-link data packet to the second blockchain.

18. An information interaction device based on a block chain, the device is deployed with nodes on a second block chain,

the device comprises:

a third receiving unit, configured to receive, after a node on a first blockchain receives a cross-chain service request, cross-chain information related to the cross-chain service request sent by the node on the first blockchain;

the second consensus unit is used for confirming the chain-crossing information in a consensus mode;

the second execution unit is used for executing the cross-chain operation according to the cross-chain information;

a second sending unit, configured to send an execution result of the cross-chain operation to a node on the first blockchain.

19. The apparatus of claim 18, a node on the first blockchain is deployed with a first intelligent contract and a first cross-chain message component, a node on the second blockchain is deployed with a second intelligent contract and a second cross-chain message component, information in the cross-chain service request is passed by the first intelligent contract invoking the first cross-chain message component, and the cross-chain service request comprises a message push request sent by the first intelligent contract to the second intelligent contract, the first cross-chain message component is configured to encapsulate the message push request into a cross-chain data packet for transmission to the second intelligent contract by the second cross-chain message component.

20. The apparatus of claim 18, a node on the first blockchain deployed with a first ledger access component, a node on the second blockchain deployed with a second ledger access component, information in the cross-chain business request passed by the first ledger access component invoked by an account or smart contract of the first blockchain, and the cross-chain business request comprising an ledger pull request of the account of the first blockchain, the first ledger access component to encapsulate the ledger pull request into a cross-chain data packet for transmission of the cross-chain data packet to the account or smart contract of the second blockchain by the second ledger access component.

21. The apparatus of claim 18, the apparatus further comprising:

the authentication unit is used for authenticating the identity of the first block chain; and/or

And the verification unit is used for verifying the cross-chain information.

22. An information interaction device based on a blockchain, the device being deployed with nodes on a first blockchain, the device comprising:

a fourth receiving unit, configured to receive a downlink service request;

a third execution unit, configured to execute an on-chain task related to the off-chain service request in response to the off-chain service request;

a third consensus unit, configured to confirm information related to the downlink service request by consensus;

a third sending unit, configured to send the downlink service request to a downlink system, so that the downlink system executes a downlink task related to the downlink service request;

a fifth receiving unit, configured to receive an execution result of the downlink task from the downlink system.

23. The apparatus of claim 22, a node on the first blockchain is deployed with a preplanning machine component, the offline system is an offline preplanning machine, information in the offline service request is transferred by an account or an intelligent contract of the first blockchain calling the preplanning machine component, and the offline service request contains offline data that the account or the intelligent contract of the first blockchain wishes to obtain, and the preplanning machine component is configured to communicate with the offline preplanning machine to obtain the offline data.

24. The apparatus of claim 22, wherein a node on the first blockchain is deployed with an external computing component, the off-chain system is an off-chain computing system, information in the off-chain service request is passed by an account or an intelligent contract of the first blockchain invoking the external computing component, and the off-chain service request comprises a computing request of the account or the intelligent contract of the first blockchain, and the external computing component is configured to communicate with the off-chain computing system to complete a computing task corresponding to the computing request.

25. A blockchain-based information interaction device comprising a memory having stored therein executable code and a processor configured to execute the executable code to implement the method of any of claims 1-12.