EP3701413B1 - Procédé, appareil, système et dispositif électronique d'interaction de chaîne de blocs croisés - Google Patents

Procédé, appareil, système et dispositif électronique d'interaction de chaîne de blocs croisés Download PDF

Info

Publication number
EP3701413B1
EP3701413B1 EP19717401.4A EP19717401A EP3701413B1 EP 3701413 B1 EP3701413 B1 EP 3701413B1 EP 19717401 A EP19717401 A EP 19717401A EP 3701413 B1 EP3701413 B1 EP 3701413B1
Authority
EP
European Patent Office
Prior art keywords
blockchain
message
cross
interaction end
client
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.)
Active
Application number
EP19717401.4A
Other languages
German (de)
English (en)
Other versions
EP3701413A1 (fr
Inventor
Honglin QIU
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Advanced New Technologies Co Ltd
Original Assignee
Advanced New Technologies Co Ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Advanced New Technologies Co Ltd filed Critical Advanced New Technologies Co Ltd
Publication of EP3701413A1 publication Critical patent/EP3701413A1/fr
Application granted granted Critical
Publication of EP3701413B1 publication Critical patent/EP3701413B1/fr
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/60—Protecting data
    • G06F21/64—Protecting data integrity, e.g. using checksums, certificates or signatures
    • 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/06—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols the encryption apparatus using shift registers or memories for block-wise or stream coding, e.g. DES systems or RC4; Hash functions; Pseudorandom sequence generators
    • H04L9/0618—Block ciphers, i.e. encrypting groups of characters of a plain text message using fixed encryption transformation
    • H04L9/0637—Modes of operation, e.g. cipher block chaining [CBC], electronic codebook [ECB] or Galois/counter mode [GCM]
    • 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/27—Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/90—Details of database functions independent of the retrieved data types
    • G06F16/901—Indexing; Data structures therefor; Storage structures
    • G06F16/9024—Graphs; Linked lists
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/90—Details of database functions independent of the retrieved data types
    • G06F16/903—Querying
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46—Multiprogramming arrangements
    • G06F9/54—Interprogram communication
    • G06F9/546—Message passing systems or structures, e.g. queues
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
    • G06Q40/04—Trading; Exchange, e.g. stocks, commodities, derivatives or currency exchange
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/12—Applying verification of the received information
    • H04L63/126—Applying verification of the received information the source of the received data
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/133—Protocols for remote procedure calls [RPC]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/14—Session management
    • H04L67/141—Setup of application sessions
    • 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/32—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials
    • H04L9/3236—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials using cryptographic hash functions
    • 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/32—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials
    • H04L9/3247—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials involving digital signatures
    • 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/50—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols using hash chains, e.g. blockchains or hash trees
    • 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/56—Financial cryptography, e.g. electronic payment or e-cash
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/10—Protocols in which an application is distributed across nodes in the network
    • H04L67/1097—Protocols in which an application is distributed across nodes in the network for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS]

Definitions

  • One or more implementations of the present application relate to the field of blockchain technologies, and in particular, to a cross-blockchain interaction method, apparatus, and system, and an electronic device.
  • Blockchain technology (also referred to as a distributed ledger technology) is a decentralized distributed database technology, and is characterized by decentralization, openness and transparency, temper-resistance, trustworthiness, etc. Therefore, the blockchain technology is applicable to many application scenarios requiring high data reliability.
  • WO 2018/006072 A1 relates to a system and method for forming, storing, managing, and executing contracts.
  • one or more implementations of the present application provide a cross-blockchain interaction method, apparatus, and system, and an electronic device.
  • a cross-blockchain interaction system including the following: a first blockchain and a second blockchain; a subscribing client, where the subscribing client corresponds to a blockchain node in the first blockchain, and is configured to maintain a message queue corresponding to the blockchain node, and the message queue includes a message that the blockchain node subscribes; a publishing client, where the publishing client corresponds to the second blockchain, and is configured to obtain a message generated by a second smart contract in the second blockchain; and a cross-blockchain interaction end, where the cross-blockchain interaction end obtains a subscription condition of the blockchain node, and requests a message that satisfies the subscription condition from the publishing client and sends the message to the subscribing client to update the message to the message queue when the message queue does not include a message that satisfies the subscription condition, where the blockchain node calls a first smart contract in the first blockchain to trigger a corresponding contract operation when
  • a cross-blockchain interaction method including the following: determining, by a blockchain node in a first blockchain, a message generated by a second smart contract in a second blockchain by using a cross-blockchain interaction end between the first blockchain and the second blockchain; and calling, by the blockchain node, a first smart contract in the first blockchain to trigger a corresponding contract operation when the message generated by the second smart contract satisfies a subscription condition of the blockchain node.
  • a cross-blockchain interaction method including the following: obtaining, by a subscribing client, a message generated by a second smart contract in a second blockchain, where the message is obtained by a cross-blockchain interaction end between a first blockchain and the second blockchain from the second blockchain, and the message satisfies a subscription condition provided by a blockchain node in the first blockchain to the cross-blockchain interaction end; and providing, by the subscribing client, the message to the blockchain node, to trigger the blockchain node to call a first smart contract in the first blockchain.
  • a cross-blockchain interaction method including the following: obtaining, by a cross-blockchain interaction end, a subscription request initiated by a blockchain node in a first blockchain, where the subscription request includes a subscription condition; obtaining, by the cross-blockchain interaction end, a message that satisfies the subscription condition and is generated by a second smart contract in a second blockchain; and providing, by the cross-blockchain interaction end, the message to the blockchain node, so that the blockchain node calls a first smart contract in the first blockchain based on the message.
  • a cross-blockchain interaction method including the following: obtaining, by a publishing client, a message generated by a second smart contract in a second blockchain; and providing, by the publishing client, the message to a blockchain node in a first blockchain by using a cross-blockchain interaction end between the first blockchain and the second blockchain, so as to trigger the blockchain node to call a first smart contract in the first blockchain.
  • a cross-blockchain interaction apparatus including the following: a determining unit, configured to determine a message generated by a second smart contract in a second blockchain by using a cross-blockchain interaction end between a first blockchain and the second blockchain; and a calling unit, configured to call a first smart contract in the first blockchain to trigger a corresponding contract operation when the message generated by the second smart contract satisfies a subscription condition of the blockchain node.
  • a cross-blockchain interaction apparatus including the following: an acquisition unit, configured to obtain a message generated by a second smart contract in a second blockchain, where the message is obtained by a cross-blockchain interaction end between a first blockchain and the second blockchain from the second blockchain, and the message satisfies a subscription condition provided by a blockchain node in the first blockchain to the cross-blockchain interaction end; and a providing unit, configured to provide the message to the blockchain node, to trigger the blockchain node to call a first smart contract in the first blockchain.
  • a cross-blockchain interaction apparatus including the following: a request acquisition unit, configured to obtain a subscription request initiated by a blockchain node in a first blockchain, where the subscription request includes a subscription condition; a message acquisition unit, configured to obtain a message that satisfies the subscription condition and is generated by a second smart contract in a second blockchain; and a providing unit, configured to provide the message to the blockchain node, so that the blockchain node calls a first smart contract in the first blockchain based on the message.
  • a cross-blockchain interaction apparatus including the following: an acquisition unit, configured to obtain a message generated by a second smart contract in a second blockchain; and a providing unit, configured to provide the message to a blockchain node in a first blockchain by using a cross-blockchain interaction end between the first blockchain and the second blockchain, so as to trigger the blockchain node to call a first smart contract in the first blockchain.
  • an electronic device including the following: a processor; and a memory, configured to store an instruction that can be executed by the processor, where the processor is configured to implement the method according to any one of the previous implementations.
  • a cross-blockchain interaction system including the following: a first blockchain and a second blockchain; a subscribing client, where the subscribing client corresponds to a blockchain node in the first blockchain, and is configured to maintain a message queue corresponding to the blockchain node, and the message queue includes a message that the blockchain node subscribes; a publishing client, where the publishing client corresponds to the second blockchain, and is configured to obtain a message generated by a second smart contract in the second blockchain; and a cross-blockchain interaction end, where the cross-blockchain interaction end obtains a subscription condition of the blockchain node, and requests a message that satisfies the subscription condition from the publishing client and sends the message to the subscribing client to update the message to the message queue when the message queue does not include a message that satisfies the subscription condition, where the blockchain node calls a first smart contract in the first blockchain to trigger a corresponding contract operation,
  • steps in the corresponding method are not necessarily performed according to the sequence shown and described in the present application.
  • the method can include steps more or fewer than those described in the present application.
  • a single step described in the present application can be decomposed into a plurality of steps in other implementations, and a plurality of steps described in the present application can be combined into a single step in other implementations.
  • FIG. 1 is a flowchart illustrating a cross-blockchain interaction method, according to an example implementation. As shown in FIG. 1 , the method is applied to a blockchain node in a first blockchain, and can include the following steps.
  • Step 102 The blockchain node in the first blockchain determines a message generated by a second smart contract in a second blockchain by using a cross-blockchain interaction end between the first blockchain and the second blockchain.
  • the cross-blockchain interaction end is disposed between the first blockchain and the second blockchain, so that the first blockchain and the second blockchain can exchange messages based on the cross-blockchain interaction end, thereby implementing cross-blockchain interaction between a plurality of blockchains.
  • the first blockchain represents a party that receives an interaction message in cross-blockchain interaction
  • the second blockchain represents a party that provides the interaction message in cross-blockchain interaction.
  • first blockchain and second blockchain depend on roles that corresponding blockchains play in cross-blockchain interaction, instead of limiting a certain blockchain to the first blockchain or the second blockchain.
  • first blockchain when a blockchain receives an interaction message from another blockchain in cross-blockchain interaction, the blockchain is a "first blockchain” in this process; and when a blockchain provides an interaction message to another blockchain in cross-blockchain interaction, the blockchain is a "second blockchain” in this process.
  • the message obtained by the blockchain node includes a message that satisfies a subscription condition of the blockchain node and is generated by the second smart contract in the second blockchain.
  • user A needs to transfer asset 1 to user B in the second blockchain and user B needs to transfer asset 2 to user A in the first blockchain.
  • user A first transfers asset 1 to user B by calling the second smart contract in the second blockchain, and after the first blockchain receives an operation completion message corresponding to this operation, user B transfers asset 2 to user A by calling a first smart contract in the first blockchain.
  • the subscription condition of the blockchain node in the first blockchain can be "received a message indicating that user A has transferred asset 1 to user B". Therefore, the blockchain node needs to obtain a message of "user A has transferred asset 1 to user B" that is generated by the second smart contract in the second blockchain, to trigger the blockchain node to call the first smart contract.
  • user B can transfer asset 2 to user A.
  • the blockchain node can initiate a subscription request to the cross-blockchain interaction end, where the subscription request is used to indicate the subscription condition to the cross-blockchain interaction end, so that the cross-blockchain interaction end obtains a message that satisfies the subscription condition and is generated by the second smart contract, and adds the message to a message queue maintained by a subscribing client corresponding to the blockchain node. Then the blockchain node determines that the second smart contract has generated a message that satisfies the subscription condition when the message queue includes a message that satisfies the subscription condition.
  • Step 104 The blockchain node calls a first smart contract in the first blockchain to trigger a corresponding contract operation when the message generated by the second smart contract satisfies a subscription condition of the blockchain node.
  • the cross-blockchain interaction end obtains the message generated by the second smart contract in the second blockchain, and triggers the blockchain node in the first blockchain to call the first smart contract based on the message, so that the first blockchain and the second blockchain can implement reliable cross-blockchain interaction of the message.
  • the message generated by the second smart contract is asynchronously sent to the first smart contract, to automatically trigger calling the first smart contract, ensuring that the corresponding contract operation can be performed efficiently in time.
  • FIG. 2 is a flowchart illustrating another cross-blockchain interaction method, according to an example implementation. As shown in FIG. 2 , the method is applied to a subscribing client, and can include the following steps.
  • Step 202 The subscribing client obtains a message generated by a second smart contract in a second blockchain, where the message is obtained by a cross-blockchain interaction end between a first blockchain and the second blockchain from the second blockchain, and the message satisfies a subscription condition provided by a blockchain node in the first blockchain to the cross-blockchain interaction end.
  • the subscribing client can be configured on the blockchain node, in other words, the subscribing client can be understood as a message subscription function that is implemented or extended on the blockchain node. In other implementations, the subscribing client can be configured on a node outside the first blockchain. Implementations are not limited in the present application.
  • Step 204 The subscribing client provides the message to the blockchain node, to trigger the blockchain node to call a first smart contract in the first blockchain.
  • the subscribing client can maintain a message queue corresponding to the blockchain node, and the message queue includes a message that the blockchain node subscribes, in other words, the subscribing client adds a message that satisfies the subscription condition provided by the blockchain node to the message queue, so that the blockchain node can consume the message included in the message queue.
  • subscribing clients are in a one-to-one correspondence with blockchain nodes so that the cross-blockchain interaction end can perform mapping to a corresponding blockchain node based on a subscribing client, ensuring accurate message transfer.
  • one subscribing client can correspond to a plurality of blockchain nodes.
  • the subscribing client can maintain a plurality of message queues that are in a one-to-one correspondence with a plurality of blockchain nodes, so as to perform mapping to a corresponding blockchain node by using a message queue.
  • the subscribing client can provide a queue status of the message queue to the cross-blockchain interaction end, and the queue status indicates a message included in the message queue.
  • the queue status indicates that the message queue includes a message that satisfies the subscription condition
  • the cross-blockchain interaction end does not need to obtain the message again.
  • the cross-blockchain interaction end can obtain a message that satisfies the subscription condition and is generated by the second smart contract in the second blockchain, so as to update the message to the message queue.
  • the subscribing client can receive a status query request initiated by the cross-blockchain interaction end, so as to return the queue status to the cross-blockchain interaction end in response to the status query request.
  • both the message queue and the queue status of the message queue are maintained by the subscribing client corresponding to the blockchain node instead of the cross-blockchain interaction end, reducing malicious behaviors performed by the related personnel on the cross-blockchain interaction end, and improving message transfer reliability.
  • the subscribing client can add the message to the message queue, and the subscribing client can trigger an arrival event of the message in the first blockchain, so as to trigger the blockchain node to consume the message queue.
  • the blockchain node can be triggered to call the first smart contract when determining that the message queue includes a message that satisfies the subscription condition and is generated by the second smart contract.
  • the subscribing client can perform verification on the message provided by the cross-blockchain interaction end by using a pre-anchored verification root, so as to provide the message to the blockchain node after the message is verified.
  • the subscribing client can actively verify whether the message actually exists in the second blockchain.
  • a simplified payment verification (SPV) client can be configured on the subscribing client, the SPV client maintains a simplified blockchain (including a header of each block only) corresponding to the second blockchain, and the verification root can include the simplified blockchain. Therefore, whether the message actually exists in the second blockchain can be determined based on the message.
  • SPV payment verification
  • a predetermined oracle client different from the subscribing client can verify whether the message actually exists in the second blockchain, and the subscribing client has an absolute trust in the oracle client.
  • the oracle client can add a signature of the oracle client to the message when determining that the message actually exists in the second blockchain.
  • the verification root can include verification information for the signature
  • the subscribing client can determine that the oracle client has verified that the message actually exists in the second blockchain when verifying that the signature is actually from the oracle client. If the signature of the message is not verified, the subscribing client considers that the message does not actually exist in the second blockchain, and therefore can discard the message.
  • the subscribing client can perform verification on the message in another way. Implementations are not limited in the present application.
  • a corresponding contract operation can be triggered when the first smart contract is called.
  • An execution process of the contract operation can be independent of the previous message, in other words, the message is merely used to trigger calling the first smart contract.
  • the previous message can be applied to an execution process of the contract operation, for example, the message is used as input information of the contract operation, and therefore is involved in the execution process of the contract operation.
  • FIG. 3 is a flowchart illustrating still another cross-blockchain interaction method, according to an example implementation. As shown in FIG. 3 , the method is applied to a cross-blockchain interaction end, and can include the following steps.
  • Step 302 The cross-blockchain interaction end obtains a subscription request initiated by a blockchain node in a first blockchain, where the subscription request includes a subscription condition.
  • the cross-blockchain interaction end can initiate a status query request to a subscribing client corresponding to the blockchain node, the subscribing client maintains a message queue corresponding to the blockchain node, and the message queue includes a message that the blockchain node subscribes. Then the cross-blockchain interaction end receives a queue status of the message queue that is returned by the subscribing client, so as to obtain a message that satisfies the subscription condition and is generated by a second smart contract in a second blockchain when determining that the message queue does not include a message that satisfies the subscription condition based on the queue status.
  • both the message queue and the queue status of the message queue are maintained by the subscribing client corresponding to the blockchain node instead of the cross-blockchain interaction end, so as to reduce malicious behaviors performed by the related personnel on the cross-blockchain interaction end, and improving message transfer reliability.
  • Step 304 The cross-blockchain interaction end obtains a message that satisfies the subscription condition and is generated by a second smart contract in a second blockchain.
  • the cross-blockchain interaction end can be connected to predetermined storage space in the second blockchain through bridging by using a publishing client (the publishing client is used to connect the cross-blockchain interaction end and the predetermined storage space through bridging).
  • the predetermined storage space is used to store messages generated by the second smart contract.
  • the cross-blockchain interaction end queries whether the predetermined storage space includes a message that satisfies the subscription condition by using a query interface provided by the publishing client.
  • the cross-blockchain interaction end can initiate a message acquisition request to the publishing client, so that the publishing client obtains a message that satisfies the subscription condition from the predetermined storage space and returns the message to the cross-blockchain interaction end.
  • the publishing client functions as a bridge, so that the cross-blockchain interaction end only needs to implement connection to the publishing client without learning how the publishing client is connected to the predetermined storage space through bridging, how the publishing client obtains a related message, etc., thereby simplifying configuration of the cross-blockchain interaction end and reducing system complexity.
  • the predetermined storage space can include at least one of the following: a third smart contract in the second blockchain and a predetermined blockchain data structure in the second blockchain.
  • the third smart contract can be exclusively used to store a message generated by the second smart contract.
  • the predetermined storage space includes the predetermined blockchain data structure, provided that the publishing client knows the predetermined blockchain data structure, the publishing client can be accurately connected to the predetermined storage space through bridging by obtaining the predetermined blockchain data structure included in a blockchain ledger in the second blockchain.
  • the predetermined storage space can further include other forms, and the forms are not limited in the present application.
  • Step 306 The cross-blockchain interaction end provides the message to the blockchain node, so that the blockchain node calls a first smart contract in the first blockchain based on the message.
  • FIG. 4 is a flowchart illustrating yet another cross-blockchain interaction method, according to an example implementation. As shown in FIG. 4 , the method is applied to a publishing client, and can include the following steps.
  • Step 402 The publishing client obtains a message generated by a second smart contract in a second blockchain.
  • the publishing client is connected to predetermined storage space in the second blockchain through bridging, the predetermined storage space is used to store a message generated by the second smart contract, and the publishing client can obtain the message generated by the second smart contract from the predetermined storage space.
  • the predetermined storage space can include at least one of the following: a third smart contract in the second blockchain and a predetermined blockchain data structure in the second blockchain.
  • the third smart contract can be exclusively used to store a message generated by the second smart contract.
  • the publishing client knows the predetermined blockchain data structure, the publishing client can be accurately connected to the predetermined storage space through bridging by obtaining the predetermined blockchain data structure included in a blockchain ledger in the second blockchain.
  • the predetermined storage space can further include other forms, and the forms are not limited in the present application.
  • a query interface for the predetermined storage space is configured for the publishing client.
  • the publishing client can open the query interface to a cross-blockchain interaction end, so that the cross-blockchain interaction end performs a query in the predetermined storage space by using the query interface.
  • the publishing client can obtain a message identified by the cross-blockchain interaction end based on a message acquisition request initiated by the cross-blockchain interaction end, and return the message to the cross-blockchain interaction end.
  • the message identified by the cross-blockchain interaction end matches a subscription condition provided by a blockchain node to the cross-blockchain interaction end.
  • Step 404 The publishing client provides the message to a blockchain node in a first blockchain by using a cross-blockchain interaction end between the first blockchain and the second blockchain, so as to trigger the blockchain node to call a first smart contract in the first blockchain.
  • the publishing client can receive the message acquisition request initiated by the cross-blockchain interaction end, and the message acquisition request matches the subscription condition provided by the blockchain node to the cross-blockchain interaction end. Then the publishing client can send a message that matches the message acquisition request and is generated by the second smart contract to the cross-blockchain interaction end, so that the cross-blockchain interaction end provides the message to the blockchain node.
  • the publishing client can add a signature to the verified message based on a result of verification performed on the obtained message.
  • the publishing client can send the message to a subscribing client corresponding to the blockchain node by using the cross-blockchain interaction end, so that the subscribing client adds the message to a message queue corresponding to the blockchain node after the signature is verified by the subscribing client.
  • the blockchain node calls the first smart contract when determining that the message queue includes a message that satisfies the subscription condition.
  • An oracle function can be configured on the publishing client (which means the publishing client can be implemented as an oracle client), so that the publishing client can perform verification on the obtained message, to determine whether the message actually exists in the second blockchain.
  • the publishing client can add a signature to the message when determining that the message actually exists in the second blockchain, so that after the signature is verified by the subscribing client, the subscribing client can directly determine that the publishing client has verified that the message actually exists in the second blockchain, without actively performing verification.
  • FIG. 5 is an architectural diagram illustrating a cross-blockchain interaction system, according to an example implementation.
  • the cross-blockchain interaction system can include a first blockchain and a second blockchain; a subscribing client; a publishing client; and a cross-blockchain interaction end.
  • the first blockchain is a blockchain as a message subscriber
  • the second blockchain is a blockchain as a message publisher.
  • first blockchain and second blockchain are merely used to distinguish between roles that different blockchains play, instead of limiting a certain blockchain to the first blockchain or the second blockchain.
  • the subscribing client corresponds to a blockchain node in the first blockchain, and is configured to maintain a message queue corresponding to the blockchain node, and the message queue includes a message that the blockchain node subscribes.
  • the subscribing client can be configured on a device, a node, a platform, etc. outside the first blockchain.
  • the subscribing client can be configured on a blockchain node in the first blockchain, and is equivalent to a subscription function that the blockchain node extends from a related technology.
  • the publishing client corresponds to the second blockchain, and is configured to obtain a message generated by a second smart contract in the second blockchain. Based on a distributed accounting feature of a blockchain, all blockchain nodes in the second blockchain can maintain all accounting data of the same content through consensus, namely, a blockchain ledger.
  • the publishing client can obtain, from the blockchain ledger, a message that can be published, so that the cross-blockchain interaction end obtains the message.
  • the publishing client can be configured on a device, a node, a platform, etc. outside the second blockchain.
  • the publishing client can be configured on a blockchain node in the second blockchain, and is equivalent to a publishing function that the blockchain node extends from a related technology.
  • the cross-blockchain interaction end can receive a subscription request initiated by the blockchain node in the first blockchain, and the subscription request includes a subscription condition indicating a subscription requirement of the blockchain node.
  • the cross-blockchain interaction end can initiate a status query message to the subscribing client, and determine whether the message queue includes a message that satisfies the subscription condition based on a queue status of the message queue that is returned by the subscribing client. If yes, the cross-blockchain interaction end does not need to obtain the message again. If no, the cross-blockchain interaction end needs to obtain a message that satisfies the subscription condition from the publishing client.
  • the cross-blockchain interaction end can request a message that satisfies the subscription condition from the publishing client, and send the message returned by the publishing client to the subscribing client, so that the subscribing client updates the message to the message queue for the blockchain node in the first blockchain to consume.
  • the cross-blockchain interaction end only transfers messages between the publishing client and the subscribing client, and does not need to make the message persistent.
  • the cross-blockchain interaction end can be configured on a device, a node, a platform, etc. outside the first blockchain and the second blockchain.
  • the cross-blockchain interaction end can be configured on a blockchain node in the first blockchain, and is equivalent to a cross-blockchain interaction function that the blockchain node extends from a related technology.
  • the cross-blockchain interaction end can be configured on a blockchain node in the second blockchain, and is equivalent to a cross-blockchain interaction function that the blockchain node extends from a related technology.
  • the message generated by the second smart contract can be an asynchronous message.
  • the blockchain node in the first blockchain can provide the subscription condition to the cross-blockchain interaction end, so that the cross-blockchain interaction end obtains the asynchronous message.
  • the cross-blockchain interaction end can send the asynchronous message to the subscribing client, so that the subscribing client adds the asynchronous message to the message queue.
  • the subscribing client can trigger an arrival event of the message in the first blockchain, so that the blockchain node in the first blockchain can be triggered to call a first smart contract when determining that the message queue includes the asynchronous message.
  • the message generated by the second smart contract can be a synchronous message.
  • the blockchain node in the first blockchain can call the first smart contract to trigger a corresponding contract operation.
  • the synchronous message needs to be used as input information. Therefore, the blockchain node can provide the subscription condition to the cross-blockchain interaction end, so that the cross-blockchain interaction end obtains the synchronous message.
  • the cross-blockchain interaction end can send the synchronous message to the subscribing client, so that the subscribing client adds the synchronous message to the message queue.
  • the subscribing client can trigger an arrival event of the message in the first blockchain, so as to trigger the contract operation to be further performed.
  • the contract operation cannot be performed until the arrival event of the message is detected.
  • the message queue corresponding to the blockchain node in the first blockchain is maintained by the subscribing client corresponding to the blockchain node, and a status of consuming a message in the message queue by the blockchain node is maintained on the blockchain node, but none of the cross-blockchain interaction end, the publishing client, etc. needs to maintain the consumption status.
  • the cross-blockchain interaction end, the publishing client, etc. are prevented from providing incorrect or invalid messages to the subscribing client.
  • a message provided by the cross-blockchain interaction end to the subscribing client is from the publishing client, and a message provided by the publishing client is from the second blockchain.
  • the publishing client does not maintain the queue status of the message queue, and therefore cannot tamper with message content.
  • it is meaningless for the cross-blockchain interaction end to tamper with the message content because the subscribing client can perform verification on the content based on a blockchain ledger maintained in the second blockchain.
  • the message content is reliable.
  • the subscribing client actively performs verification on a received message, for example, by using an SPV blockchain that corresponds to the second blockchain and is maintained by the subscribing client, to determine whether the message actually exists in the second blockchain.
  • the subscribing client can verify whether a signature of the message is from a predetermined oracle client, and determine that the message actually exists in the second blockchain after the signature is verified by the subscribing client.
  • the cross-blockchain interaction end can initiate a denial of service attack, and therefore the subscribing client cannot obtain a message published by the publishing client.
  • a plurality of independent cross-blockchain interaction ends such as cross-blockchain interaction end 1, cross-blockchain interaction end 2, etc. can be configured between the subscribing client and the publishing client, so that the subscribing client can still obtain a message published by the publishing client by using cross-blockchain interaction end 2 even if cross-blockchain interaction end 1 initiates a denial of service attack.
  • FIG. 7 is a structural diagram illustrating a cross-blockchain transfer-related system, according to an example implementation.
  • user A has account A1 in blockchain 1 and account A2 in blockchain 2
  • user B has account B1 in blockchain 1 and account B2 in blockchain 2.
  • Account A1 and account B1 in blockchain 1 are used to maintain a type of asset objects (e.g., RMB)
  • account A2 and account B2 in blockchain 2 are used to maintain another type of asset objects (e.g., Securities).
  • the following transfer-related logic can be used: A specified number of securities are transferred from account A2 to account B2, and then a specified amount of RMB is transferred from account B1 to account A1.
  • corresponding smart contracts can be separately set in blockchain 1 and blockchain 2, so that the previous two transfer processes are automatically completed, thereby reducing intentional or unintentional transfer amount errors, delays, etc. caused in a user's manual transfer process, and ensuring a quick and accurate transfer process.
  • cross-blockchain message exchange can be implemented between blockchain 1 and blockchain 2, so that the transfer operation can be performed from account B1 to account A1 in blockchain 1 after blockchain 1 determines that the transfer operation from account A2 to account B2 is completed.
  • blockchain 1 includes blockchain node 1, blockchain node 2, blockchain node 3, etc.
  • subscribing client 1 is configured on blockchain node 1
  • subscribing client 2 is configured on blockchain node 2
  • subscribing client 3 is configured on blockchain node 3, and so on.
  • Subscribing clients 1 to 3 are not necessarily configured on blockchain nodes 1 to 3, and can be configured on nodes outside blockchain 1. Implementations are not limited in the present application.
  • Subscribing client 1 maintains message queue 1 corresponding to blockchain node 1
  • subscribing client 2 maintains message queue 2 corresponding to blockchain node 2
  • subscribing client 3 maintains message queue 3 corresponding to blockchain node 3.
  • a corresponding publishing client is configured for blockchain 2.
  • the publishing client can be configured on a blockchain node in blockchain 2, or can be configured on a node outside blockchain 2. Implementations are not limited in the present application.
  • a cross-blockchain interaction end is configured between subscribing clients 1 to 3 and the publishing client.
  • the cross-blockchain interaction end can be configured on a blockchain node in blockchain 1, or can be configured on a blockchain node in blockchain 2, or can be configured on a node outside blockchain 1 and blockchain 2. Implementations are not limited in the present application.
  • Message queues 1 to 3 respectively maintained by subscribing clients 1 to 3 include messages that blockchain nodes 1 to 3 separately subscribe. Subscribing clients 1 to 3 can maintain queue statuses of message queues 1 to 3 based on respective message consumption statuses in message queues 1-3 by blockchain nodes 1-3. However, neither the cross-blockchain interaction end nor the publishing client needs to maintain the queue statuses.
  • the publishing client can obtain to-be-published messages in blockchain 2, and the cross-blockchain interaction end can query the queue statuses from subscribing clients 1 to 3, and request a corresponding message from the publishing client, so as to update the message to a corresponding message queue.
  • the following uses blockchain node 1 as an example to describe a cross-blockchain message exchange process.
  • FIG. 8 is a schematic diagram illustrating a cross-blockchain message exchange process, according to an example implementation. As shown in FIG. 8 , the message exchange process can include the following steps.
  • Step 801 A cross-blockchain interaction end requests a queue status from subscribing client 1.
  • Step 802 The cross-blockchain interaction end receives the queue status returned by subscribing client 1.
  • subscribing client 1 maintains a message queue (namely, message queue 1) corresponding to blockchain node 1, where the message queue includes a message that blockchain node 1 subscribes, and the queue status includes a status of consuming each message by blockchain node 1, so that the cross-blockchain interaction end can know a next message that the cross-blockchain interaction end needs to request to obtain from a publishing client based on the consumption status.
  • message queue 1 namely, message queue 1
  • blockchain node 1 initiates a subscription request to the cross-blockchain interaction end, and the subscription request includes a subscription condition.
  • the subscription condition is that transaction of transferring a specified number of securities from account A2 to account B2 is successfully completed.
  • the cross-blockchain interaction end can determine, by querying the queue status, whether the message queue maintained by subscribing client 1 includes a message that satisfies the subscription condition, namely, a message indicating that transaction of transferring a specified number of securities from account A2 to account B2 is successful.
  • the cross-blockchain interaction end does not need to obtain the message again, and determines that a response is successfully made to the subscription request. If no message that satisfies the subscription condition exists, the cross-blockchain interaction end can determine that the next message to be obtained is the message indicating that transaction of transferring a specified number of securities from account A2 to account B2 is successful, and needs to perform subsequent steps to obtain the next message.
  • Step 803 The cross-blockchain interaction end initiates a message acquisition request to a publishing client.
  • Step 804 The cross-blockchain interaction end obtains a message returned by the publishing client.
  • the publishing client can determine the message needed by the cross-blockchain interaction end by parsing the message acquisition request. If the publishing client has obtained the transaction success message, the publishing client can directly return the transaction success message to the cross-blockchain interaction end. If the publishing client has not obtained the transaction success message, the publishing client can notify the cross-blockchain interaction end of the acquisition failure, so that the cross-blockchain interaction end can initiate a query repeatedly based on a predetermined period, until the publishing client has obtained the transaction success message. In some situations, if the publishing client has not obtained the transaction success message, the publishing client can monitor the transaction success message, and actively send the transaction success message to the cross-blockchain interaction end after determining that the transaction success message is obtained.
  • the transfer operation performed from account A2 to account B2 in blockchain 2 can be completed by a blockchain node in blockchain 2 by calling a smart contract, or can be automatically triggered by a smart contract based on a predetermined trigger condition. Implementations are not limited in the present application.
  • Step 805 The cross-blockchain interaction end sends the obtained message to subscribing client 1.
  • the cross-blockchain interaction end is only responsible for a data transfer function between subscribing client 1 and the publishing client, but does not maintain the message queue or the queue status, or focus on data content, or need to perform persistent processing on data.
  • the cross-blockchain interaction end only functions as a "pipeline" for data transfer.
  • Step 806 Subscribing client 1 adds the message sent by the cross-blockchain interaction end to a message queue, to maintain the message queue.
  • subscribing client 1 or blockchain node 1 can perform verification on the received message to ensure that the message is actually from blockchain 2 and content is reliable and untampered.
  • Subscribing client 1 or blockchain node 1 can use various verification methods. The methods are not limited in the present application. For example, subscribing client 1 or blockchain node 1 can check whether a block where the message is located in blockchain 2 is in the longest chain and determine the number of blocks following the block. The message is verified if the block where the message is located is in the longest chain and the number of blocks following the block is not less than 6.
  • subscribing client 1 or blockchain node 1 can perform verification on the message based on a PBFT algorithm or by using an oracle.
  • subscribing client 1 or blockchain node 1 can perform verification on the message by using a configured SPV blockchain corresponding to blockchain 2.
  • a corresponding smart contract is created in advance in blockchain 1, the smart contract is triggered once the transaction success message is obtained, and content of a contract operation is transferring a specified amount of RMB from account B1 to account A1.
  • the smart contract can be automatically called and the corresponding contract operation is initiated to automatically transfer a specified amount of RMB from account B1 to account A1.
  • the transfer operation between user A and user B can be completed reliably without a delay (which is a delay caused by a manual operation and does not include a time for transferring and processing data).
  • FIG. 9 is a structural diagram illustrating a device, according to an example implementation.
  • the device includes a processor 902, an internal bus 904, a network interface 906, a memory 908, and a non-volatile memory 910, and certainly can further include other hardware needed by a service.
  • the processor 902 reads a corresponding computer program from the non-volatile memory 910 into the memory 908, and then the corresponding computer program runs to form a logical cross-blockchain interaction apparatus.
  • one or more implementations of the present application include other implementations, for example, a logic device or a combination of hardware and software.
  • an execution body of the following processing procedure is not limited to each logical unit, and can be hardware or a logic device.
  • the cross-blockchain interaction apparatus can include the following: a determining unit 1001, configured to determine, by the blockchain nodes of the first blockchain, a message generated by a second smart contract in a second blockchain by using a cross-blockchain interaction end between a first blockchain and the second blockchain; and a calling unit 1002, configured to call, by the blockchain node, a first smart contract in the first blockchain to trigger a corresponding contract operation when the message generated by the second smart contract satisfies a subscription condition of the blockchain node.
  • a determining unit 1001 configured to determine, by the blockchain nodes of the first blockchain, a message generated by a second smart contract in a second blockchain by using a cross-blockchain interaction end between a first blockchain and the second blockchain
  • a calling unit 1002 configured to call, by the blockchain node, a first smart contract in the first blockchain to trigger a corresponding contract operation when the message generated by the second smart contract satisfies a subscription condition of the blockchain node.
  • the determining unit 1001 is configured to initiate, by the blockchain node, a subscription request to the cross-blockchain interaction end, where the subscription request is used to indicate the subscription condition to the cross-blockchain interaction end, so that the cross-blockchain interaction end obtains a message that satisfies the subscription condition and is generated by the second smart contract, and adds the message to a message queue maintained by a subscribing client corresponding to the blockchain node; and determine that the second smart contract has generated a message that satisfies the subscription condition when the message queue includes a message that satisfies the subscription condition.
  • the cross-blockchain interaction apparatus can include the following: an acquisition unit 1101, configured to obtain, by the subscribing client, a message generated by a second smart contract in a second blockchain, where the message is obtained by a cross-blockchain interaction end between a first blockchain and the second blockchain from the second blockchain, and the message satisfies a subscription condition provided by a blockchain node in the first blockchain to the cross-blockchain interaction end; and a providing unit 1102, configured to provide, by the subscribing client, the message to the blockchain node, to trigger the blockchain node to call a first smart contract in the first blockchain.
  • the apparatus further includes a maintenance unit 1103, configured to maintain, by the subscribing client, a message queue corresponding to the blockchain node, where the message queue includes a message that the blockchain node subscribes.
  • a maintenance unit 1103 configured to maintain, by the subscribing client, a message queue corresponding to the blockchain node, where the message queue includes a message that the blockchain node subscribes.
  • the acquisition unit 1101 is configured to provide, by the subscribing client, a queue status of the message queue to the cross-blockchain interaction end, so that the cross-blockchain interaction end obtains a message that satisfies the subscription condition and is generated by the second smart contract in the second blockchain when determining that the message queue does not include a message that satisfies the subscription condition based on the queue status.
  • the apparatus further includes the following: a receiving unit 1104, configured to receive, by the subscribing client, a status query request initiated by the cross-blockchain interaction end, so as to return the queue status to the cross-blockchain interaction end in response to the status query request.
  • a receiving unit 1104 configured to receive, by the subscribing client, a status query request initiated by the cross-blockchain interaction end, so as to return the queue status to the cross-blockchain interaction end in response to the status query request.
  • the providing unit 1102 is configured to add, by the subscribing client, the message to the message queue; and trigger, by the subscribing client, an arrival event of the message in the first blockchain, so as to trigger the blockchain node to consume the message queue.
  • the apparatus further includes the following: a verification unit 1105, configured to perform, by the subscribing client, verification on the message provided by the cross-blockchain interaction end by using a pre-anchored verification root, so as to provide the message to the blockchain node when it is determined that the message provided by the cross-blockchain interaction end is from the second blockchain.
  • a verification unit 1105 configured to perform, by the subscribing client, verification on the message provided by the cross-blockchain interaction end by using a pre-anchored verification root, so as to provide the message to the blockchain node when it is determined that the message provided by the cross-blockchain interaction end is from the second blockchain.
  • the verification unit 1105 is configured to determine, by the subscribing client, whether the message includes a signature of an oracle client; and determine, by the subscribing client, that the oracle client has verified that the message actually exists in the second blockchain after the signature is verified by the subscribing client; or actively verify whether the message actually exists in the second blockchain.
  • the cross-blockchain interaction apparatus can include the following: a request acquisition unit 1201, configured to obtain, by the cross-blockchain interaction end, a subscription request initiated by a blockchain node in a first blockchain, where the subscription request includes a subscription condition; a message acquisition unit 1202, configured to obtain, by the cross-blockchain interaction end, a message that satisfies the subscription condition and is generated by a second smart contract in a second blockchain; and a providing unit 1203, configured to provide, by the cross-blockchain interaction end, the message to the blockchain node, so that the blockchain node calls a first smart contract in the first blockchain based on the message.
  • the apparatus further includes the following: a request initiation unit 1204, configured to initiate, by the cross-blockchain interaction end, a status query request to a subscribing client corresponding to the blockchain node, where the subscribing client maintains a message queue corresponding to the blockchain node, and the message queue includes a message that the blockchain node subscribes; and a status receiving unit 1205, configured to receive, by the cross-blockchain interaction end, a queue status of the message queue that is returned by the subscribing client, so as to obtain a message that satisfies the subscription condition and is generated by the second smart contract in the second blockchain when it is determined that the message queue does not include a message that satisfies the subscription condition based on the queue status.
  • a request initiation unit 1204 configured to initiate, by the cross-blockchain interaction end, a status query request to a subscribing client corresponding to the blockchain node, where the subscribing client maintains a message queue corresponding to the blockchain node,
  • the message acquisition unit 1202 is configured to connect, by the cross-blockchain interaction end, to predetermined storage space in the second blockchain through bridging by using a publishing client, where the predetermined storage space is used to store a message generated by the second smart contract; query, by the cross-blockchain interaction end, whether the predetermined storage space includes a message that satisfies the subscription condition by using a query interface provided by the publishing client; and initiate, by the cross-blockchain interaction end, a message acquisition request to the publishing client, so that the publishing client obtains a message that satisfies the subscription condition from the predetermined storage space and returns the message to the cross-blockchain interaction end.
  • the cross-blockchain interaction apparatus can include the following: an acquisition unit 1301, configured to obtain, by the publishing client, a message generated by a second smart contract in a second blockchain; and a providing unit 1302, configured to provide, by the publishing client, the message to a blockchain node in a first blockchain by using a cross-blockchain interaction end between the first blockchain and the second blockchain, so as to trigger the blockchain node to call a first smart contract in the first blockchain.
  • the providing unit 1302 is configured to receive, by the publishing client, a message acquisition request initiated by the cross-blockchain interaction end, where the message acquisition request matches a subscription condition provided by the blockchain node to the cross-blockchain interaction end; and send, by the publishing client, a message that matches the message acquisition request and is generated by the second smart contract to the cross-blockchain interaction end, so that the cross-blockchain interaction end provides the message to the blockchain node.
  • the publishing client is connected to predetermined storage space in the second blockchain through bridging, the predetermined storage space is used to store a message generated by the second smart contract, and the acquisition unit 1301 is configured to obtain, by the publishing client, the message generated by the second smart contract from the predetermined storage space.
  • a query interface for the predetermined storage space is configured for the publishing client, and the apparatus further includes the following: an interface management unit 1303, configured to open, by the publishing client, the query interface to the cross-blockchain interaction end, so that the cross-blockchain interaction end performs a query in the predetermined storage space by using the query interface; and a message returning unit 1304, configured to obtain, by the publishing client, a message identified by the cross-blockchain interaction end based on a message acquisition request initiated by the cross-blockchain interaction end, and return the message to the cross-blockchain interaction end, where the message identified by the cross-blockchain interaction end matches a subscription condition provided by the blockchain node to the cross-blockchain interaction end.
  • the predetermined storage space includes at least one of the following: a third smart contract in the second blockchain and a predetermined blockchain data structure in the second blockchain.
  • the apparatus further includes a signature adding unit 1305, configured to add, by the publishing client, a signature to the verified message based on a result of verification performed on the obtained message.
  • a signature adding unit 1305 configured to add, by the publishing client, a signature to the verified message based on a result of verification performed on the obtained message.
  • the providing unit 1302 is configured to send, by the publishing client, the message to a subscribing client corresponding to the blockchain node by using the cross-blockchain interaction end, so that the subscribing client adds the message to a message queue corresponding to the blockchain node after the signature is verified by the subscribing client, where the blockchain node calls the first smart contract when determining that the message queue includes a message that satisfies the subscription condition.
  • the system, apparatus, module, or unit illustrated in the previous implementations can be implemented by using a computer chip or an entity, or can be implemented by using a product having a certain function.
  • a typical implementation device is a computer, and the computer can be a personal computer, a laptop computer, a cellular phone, a camera phone, a smartphone, a personal digital assistant, a media player, a navigation device, an email receiving and sending device, a game console, a tablet, a wearable device, or any combination of these devices.
  • the computer includes one or more processors (CPU), one or more input/output interfaces, one or more network interfaces, and one or more memories.
  • the memory can include a non-persistent memory, a random access memory (RAM), a non-volatile memory, and/or another form that are in a computer readable medium, for example, a read-only memory (ROM) or a flash memory (flash RAM).
  • ROM read-only memory
  • flash RAM flash memory
  • the computer readable medium includes persistent, non-persistent, movable, and unmovable media that can store information by using any method or technology.
  • the information can be a computer readable instruction, a data structure, a program module, or other data.
  • the computer storage medium includes but is not limited to a phase change random access memory (PRAM), a static random access memory (SRAM), a dynamic random access memory (DRAM), a random access memory (RAM) of another type, a read-only memory (ROM), an electrically erasable programmable read-only memory (EEPROM), a flash memory or another memory technology, a compact disc read-only memory (CD-ROM), a digital versatile disc (DVD) or another optical storage, a magnetic tape, a magnetic disk storage, a quantum memory, a graphene-based storage medium, another magnetic storage device, or any other non-transmission medium.
  • the computer storage medium can be used to store information that can be accessed by a computing device. Based on the definition in the present application, the computer
  • first, second, third, etc. can be used in the one or more implementations of the present application to describe various types of information, the information is not limited to the terms. These terms are only used to differentiate between information of a same type. For example, without departing from the scope of the one or more implementations of the present application, first information can also be referred to as second information, and similarly, second information can also be referred to as first information. Depending on the context, for example, the word “if” used here can be explained as “while”, “when”, or "in response to determining”.
  • FIG. 14 is a flowchart illustrating an example of a computer-implemented method 1400 for improving data transmission in cross-blockchain interactions, according to an implementation of the present disclosure.
  • method 1400 can be performed, for example, by any system, environment, software, and hardware, or a combination of systems, environments, software, and hardware, as appropriate.
  • steps of method 1400 can be run in parallel, in combination, in loops, or in any order.
  • a subscription request initiated by a blockchain node associated with a first blockchain is receievd by a cross-blockchain interaction end, where the subscription request includes a subscription condition.
  • the message is generated by a second smart contract associated with the second blockchain. From 1402, method 1400 proceeds to 1404.
  • a message that satisfies the subscription condition is obtained by the cross-blockchain interaction end and from a publishing client that corresponds to a second blockchain.
  • obtaining the message can include sending, from the cross-blockchain interaction end, a message acquisition request to the publishing client, where the message acquisition request matches the subscription condition.
  • method 1400 can also include receiving, at the cross-blockchain interaction end and from the publishing client, the message, where the message matches the message acquisition request and is generated by a second smart contract associated with the second blockchain.
  • method 1400 can further include, prior to sending a message acquisition request to the publishing client: querying, by the cross-blockchain interaction end and using a query interface provided by the publishing client, as to whether a predetermined storage space in the second blockchain includes a particular message that satisfies the subscription condition, where the predetermined storage space stores a plurality of messages generated by a second smart contract that corresponds to the second blockchain. If the determination is YES, a message acquisition request is initiated by the cross-blockchain interaction end to the publishing client to obtain the particular message that satisfies the subscription condition from the predetermined storage space. From 1404, method 1400 proceeds to 1406.
  • the message is sent to a subscribing client that corresponds to the blockchain node a from the cross-blockchain interaction end, where the blockchain node calls a first smart contract associated with the first blockchain to trigger a corresponding contract operation based on the message.
  • method 1400 further includes, prior to obtaining the message: 1) initiating, by the cross-blockchain interaction end, a status query request to the subscribing client, where the subscribing client maintains a message queue that corresponds to the blockchain node; 2) receiving, at the cross-blockchain interaction end, a queue status associated with the message queue from the subscribing client; 3) determining, by the cross-blockchain interaction end, whether the message queue comprises a message that satisfies the subscription condition based on the received queue status; and 4) if it is determined that the message queue does not comprise a message that satisfies the subscription condition, obtaining, by the cross-blockchain interaction end, another message that satisfies the subscription condition from the publishing client that corresponds to the second blockchain.
  • the message can include a signature added by the publishing client, where the subscribing client updates a message queue that corresnpnds to the blockchain node by adding the message to that particular message queue after the subscribing client verifies the signature.
  • the blockchain node can call the first smart contract if it is determined that the message queue is updated. After 1406, method 1400 can stop.
  • Implementations of the present application can solve technical problems in blockchain network data transmission and data storage.
  • the database when receiving written data, the database saves a data log, and then writes the data to the database. If data loss in the database occurs, the lost data can be recovered by re-executing the written data log.
  • Blockchain data is written into blockchain in a similar way. Each block records a data log passed by block verification, and stores a data state change after the data log is executed.
  • data cannot be transferred across different blockchains. As such, transactions that include multiple steps cannot be implemented through cross-blockchain interactions using existing technologies. What is needed is a technique to bypass these problems in the conventional implementations, and to provide a more efficient and unified method for cross-blockchain interactions.
  • Implementation of the present application provide methods and apparatuses for improving data transmission in cross-blockchain interactions.
  • the solution of these implementations includes an asynchronous cross-chain smart contract call.
  • the smart contract on the blockchain can send an asynchronous message to the smart contract on another chain, ensuring that the message can arrive through the certifiable publish-subscribe framework.
  • the blockchain node in the first blockchain can provide the subscription condition to the cross-blockchain interaction end, where the cross-blockchain interaction end obtains the asynchronous message.
  • the cross-blockchain interaction end can send the asynchronous message to the subscribing client, where the subscribing client adds the asynchronous message to the message queue.
  • the subscribing client can trigger an arrival event of the message in the first blockchain, where the blockchain node in the first blockchain can be triggered to call a first smart contract when determining that the message queue includes the asynchronous message.
  • Embodiments and the operations described in this specification can be implemented in digital electronic circuitry, or in computer software, firmware, or hardware, including the structures disclosed in this specification or in combinations of one or more of them.
  • the operations can be implemented as operations performed by a data processing apparatus on data stored on one or more computer-readable storage devices or received from other sources.
  • a data processing apparatus, computer, or computing device may encompass apparatus, devices, and machines for processing data, including by way of example a programmable processor, a computer, a system on a chip, or multiple ones, or combinations, of the foregoing.
  • the apparatus can include special purpose logic circuitry, for example, a central processing unit (CPU), a field programmable gate array (FPGA) or an application-specific integrated circuit (ASIC).
  • CPU central processing unit
  • FPGA field programmable gate array
  • ASIC application-specific integrated circuit
  • the apparatus can also include code that creates an execution environment for the computer program in question, for example, code that constitutes processor firmware, a protocol stack, a database management system, an operating system (for example an operating system or a combination of operating systems), a cross-platform runtime environment, a virtual machine, or a combination of one or more of them.
  • the apparatus and execution environment can realize various different computing model infrastructures, such as web services, distributed computing and grid computing infrastructures.
  • a computer program (also known, for example, as a program, software, software application, software module, software unit, script, or code) can be written in any form of programming language, including compiled or interpreted languages, declarative or procedural languages, and it can be deployed in any form, including as a stand-alone program or as a module, component, subroutine, object, or other unit suitable for use in a computing environment.
  • a program can be stored in a portion of a file that holds other programs or data (for example, one or more scripts stored in a markup language document), in a single file dedicated to the program in question, or in multiple coordinated files (for example, files that store one or more modules, sub-programs, or portions of code).
  • a computer program can be executed on one computer or on multiple computers that are located at one site or distributed across multiple sites and interconnected by a communication network.
  • processors for execution of a computer program include, by way of example, both general- and special-purpose microprocessors, and any one or more processors of any kind of digital computer.
  • a processor will receive instructions and data from a read-only memory or a random-access memory or both.
  • the essential elements of a computer are a processor for performing actions in accordance with instructions and one or more memory devices for storing instructions and data.
  • a computer will also include, or be operatively coupled to receive data from or transfer data to, or both, one or more mass storage devices for storing data.
  • a computer can be embedded in another device, for example, a mobile device, a personal digital assistant (PDA), a game console, a Global Positioning System (GPS) receiver, or a portable storage device.
  • PDA personal digital assistant
  • GPS Global Positioning System
  • Devices suitable for storing computer program instructions and data include non-volatile memory, media and memory devices, including, by way of example, semiconductor memory devices, magnetic disks, and magneto-optical disks.
  • the processor and the memory can be supplemented by, or incorporated in, special-purpose logic circuitry.
  • Mobile devices can include handsets, user equipment (UE), mobile telephones (for example, smartphones), tablets, wearable devices (for example, smart watches and smart eyeglasses), implanted devices within the human body (for example, biosensors, cochlear implants), or other types of mobile devices.
  • the mobile devices can communicate wirelessly (for example, using radio frequency (RF) signals) to various communication networks (described below).
  • RF radio frequency
  • the mobile devices can include sensors for determining characteristics of the mobile device's current environment.
  • the sensors can include cameras, microphones, proximity sensors, GPS sensors, motion sensors, accelerometers, ambient light sensors, moisture sensors, gyroscopes, compasses, barometers, fingerprint sensors, facial recognition systems, RF sensors (for example, Wi-Fi and cellular radios), thermal sensors, or other types of sensors.
  • the cameras can include a forward- or rear-facing camera with movable or fixed lenses, a flash, an image sensor, and an image processor.
  • the camera can be a megapixel camera capable of capturing details for facial and/or iris recognition.
  • the camera along with a data processor and authentication information stored in memory or accessed remotely can form a facial recognition system.
  • the facial recognition system or one-or-more sensors for example, microphones, motion sensors, accelerometers, GPS sensors, or RF sensors, can be used for user authentication.
  • embodiments can be implemented on a computer having a display device and an input device, for example, a liquid crystal display (LCD) or organic light-emitting diode (OLED)/virtual-reality (VR)/augmented-reality (AR) display for displaying information to the user and a touchscreen, keyboard, and a pointing device by which the user can provide input to the computer.
  • LCD liquid crystal display
  • OLED organic light-emitting diode
  • VR virtual-reality
  • AR pointing device
  • Other kinds of devices can be used to provide for interaction with a user as well; for example, feedback provided to the user can be any form of sensory feedback, for example, visual feedback, auditory feedback, or tactile feedback; and input from the user can be received in any form, including acoustic, speech, or tactile input.
  • a computer can interact with a user by sending documents to and receiving documents from a device that is used by the user; for example, by sending web pages to a web browser on a user's client device in response
  • Embodiments can be implemented using computing devices interconnected by any form or medium of wireline or wireless digital data communication (or combination thereof), for example, a communication network.
  • interconnected devices are a client and a server generally remote from each other that typically interact through a communication network.
  • a client for example, a mobile device, can carry out transactions itself, with a server, or through a server, for example, performing buy, sell, pay, give, send, or loan transactions, or authorizing the same.
  • Such transactions may be in real time such that an action and a response are temporally proximate; for example an individual perceives the action and the response occurring substantially simultaneously, the time difference for a response following the individual's action is less than 1 millisecond (ms) or less than 1 second (s), or the response is without intentional delay taking into account processing limitations of the system.
  • ms millisecond
  • s 1 second
  • Examples of communication networks include a local area network (LAN), a radio access network (RAN), a metropolitan area network (MAN), and a wide area network (WAN).
  • the communication network can include all or a portion of the Internet, another communication network, or a combination of communication networks.
  • Information can be transmitted on the communication network according to various protocols and standards, including Long Term Evolution (LTE), 5G, IEEE 802, Internet Protocol (IP), or other protocols or combinations of protocols.
  • LTE Long Term Evolution
  • 5G Fifth Generation
  • IEEE 802 Internet Protocol
  • IP Internet Protocol
  • the communication network can transmit voice, video, biometric, or authentication data, or other information between the connected computing devices.

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Computer Security & Cryptography (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • General Engineering & Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Software Systems (AREA)
  • Databases & Information Systems (AREA)
  • Computer Hardware Design (AREA)
  • Data Mining & Analysis (AREA)
  • General Health & Medical Sciences (AREA)
  • Bioethics (AREA)
  • Health & Medical Sciences (AREA)
  • Computing Systems (AREA)
  • Business, Economics & Management (AREA)
  • Computational Linguistics (AREA)
  • Accounting & Taxation (AREA)
  • Finance (AREA)
  • Strategic Management (AREA)
  • Technology Law (AREA)
  • General Business, Economics & Management (AREA)
  • Marketing (AREA)
  • Economics (AREA)
  • Development Economics (AREA)
  • Information Transfer Between Computers (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)
  • Telephonic Communication Services (AREA)

Claims (9)

  1. Procédé d'interaction entre chaînes de blocs, le procédé comprenant :
    la détermination (102), par un nœud de chaîne de blocs dans une première chaîne de blocs, d'un message généré par un deuxième contrat dans une deuxième chaîne de blocs au moyen d'une extrémité d'interaction entre chaînes de blocs entre la première chaîne de blocs et la deuxième chaîne de blocs et au moyen d'un client souscripteur correspondant au nœud de chaîne de blocs, le client souscripteur étant configuré pour tenir une pluralité de files d'attente de messages qui sont en correspondance biunivoque avec une pluralité de nœuds de chaîne de blocs, pour réaliser un mappage vers un nœud de chaîne de blocs correspondant au moyen d'une file d'attente de messages, comprenant :
    l'initiation, par le nœud de chaîne de blocs, d'une requête de souscription auprès de l'extrémité d'interaction entre chaînes de blocs, la requête de souscription étant utilisée pour indiquer une condition de souscription à l'extrémité d'interaction entre chaînes de blocs, de sorte que l'extrémité d'interaction entre chaînes de blocs obtienne le message qui remplit la condition de souscription et qui est généré par le deuxième contrat, et ajoute le message à la file d'attente de messages tenue par le client souscripteur correspondant au nœud de chaîne de blocs ; et
    la détermination, par le nœud de chaîne de blocs, que le deuxième contrat a généré le message qui remplit la condition de souscription lorsque la file d'attente de messages comprend le message qui remplit la condition de souscription ;
    la réalisation, par le client souscripteur, d'une vérification sur le message fourni par l'extrémité d'interaction entre chaînes de blocs au moyen d'une racine de vérification préalablement ancrée, de manière à fournir le message au nœud de chaîne de blocs lorsque le client souscripteur détermine que le message fourni par l'extrémité d'interaction entre chaînes de blocs provient de la deuxième chaîne de blocs ; et
    l'appel (104), par le nœud de chaîne de blocs, d'un premier contrat dans la première chaîne de blocs pour déclencher une opération de contrat correspondante lorsque le message généré par le deuxième contrat remplit la condition de souscription du nœud de chaîne de blocs.
  2. Procédé selon la revendication 1, comprenant en outre :
    la réception (204), depuis le client souscripteur, du message qui déclenche l'appel, par le nœud de chaîne de blocs, du premier contrat dans la première chaîne de blocs.
  3. Procédé selon la revendication 2, comprenant en outre :
    la réception, depuis le client souscripteur, d'un état de file d'attente de la file d'attente de messages auprès de l'extrémité d'interaction entre chaînes de blocs, de sorte que l'extrémité d'interaction entre chaînes de blocs obtienne le message qui remplit la condition de souscription et qui est généré par le deuxième contrat dans la deuxième chaîne de blocs en cas de détermination que la file d'attente de messages ne comprend pas le message qui remplit la condition de souscription sur la base de l'état de file d'attente.
  4. Procédé selon la revendication 3, dans lequel le client souscripteur reçoit une requête d'interrogation d'état initiée par l'extrémité d'interaction entre chaînes de blocs, de manière à renvoyer l'état de file d'attente à l'extrémité d'interaction entre chaînes de blocs en réponse à la requête d'interrogation d'état.
  5. Procédé selon la revendication 3, dans lequel la réception du message comprend :
    l'ajout, par le client souscripteur, du message à la file d'attente de messages ; et
    le déclenchement, par le client souscripteur, d'un événement d'arrivée du message dans la première chaîne de blocs, de manière à déclencher la consommation de la file d'attente de messages par le nœud de chaîne de blocs.
  6. Procédé selon la revendication 1, dans lequel la réalisation de la vérification comprend :
    la détermination, par le client souscripteur, si le message comprend une signature d'un client oracle ; et la détermination, par le client souscripteur, que le client oracle a vérifié que le message existe bien dans la deuxième chaîne de blocs après que la signature a été vérifiée par le client souscripteur ; ou
    la vérification active, par le client souscripteur, si le message existe bien dans la deuxième chaîne de blocs.
  7. Procédé selon l'une quelconque des revendications 3 à 6, dans lequel l'obtention du message qui remplit la condition de souscription comprend :
    la connexion, par l'extrémité d'interaction entre chaînes de blocs, à un espace de stockage prédéterminé dans la deuxième chaîne de blocs par pontage au moyen d'un client publieur, l'espace de stockage prédéterminé étant utilisé pour stocker le message généré par le deuxième contrat ;
    l'interrogation, par l'extrémité d'interaction entre chaînes de blocs, si l'espace de stockage prédéterminé comprend le message qui remplit la condition de souscription au moyen d'une interface d'interrogation fournie par la client publieur ; et
    l'initiation, par l'extrémité d'interaction entre chaînes de blocs, d'une requête d'acquisition de message auprès du client publieur, de sorte que le client publieur obtienne le message qui remplit la condition de souscription à partir de l'espace de stockage prédéterminé et renvoie le message à l'extrémité d'interaction entre chaînes de blocs.
  8. Procédé selon la revendication 7, dans lequel l'espace de stockage prédéterminé comprend :
    un troisième contrat dans la deuxième chaîne de blocs et/ou une structure de données de chaîne de blocs prédéterminée dans la deuxième chaîne de blocs.
  9. Appareil d'interaction entre chaînes de blocs, l'appareil comprenant une pluralité de modules configurés pour réaliser le procédé selon l'une quelconque des revendications 1 à 8.
EP19717401.4A 2018-04-03 2019-03-28 Procédé, appareil, système et dispositif électronique d'interaction de chaîne de blocs croisés Active EP3701413B1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201810290446.0A CN108848119B (zh) 2018-04-03 2018-04-03 跨区块链的交互方法及装置、系统、电子设备
PCT/US2019/024520 WO2019195071A1 (fr) 2018-04-03 2019-03-28 Procédé, appareil, système et dispositif électronique d'interaction de chaîne de blocs croisés

Publications (2)

Publication Number Publication Date
EP3701413A1 EP3701413A1 (fr) 2020-09-02
EP3701413B1 true EP3701413B1 (fr) 2022-02-23

Family

ID=64211796

Family Applications (1)

Application Number Title Priority Date Filing Date
EP19717401.4A Active EP3701413B1 (fr) 2018-04-03 2019-03-28 Procédé, appareil, système et dispositif électronique d'interaction de chaîne de blocs croisés

Country Status (11)

Country Link
US (2) US10615964B2 (fr)
EP (1) EP3701413B1 (fr)
JP (1) JP6929497B2 (fr)
KR (1) KR102215248B1 (fr)
CN (2) CN108848119B (fr)
AU (1) AU2019248524C1 (fr)
CA (1) CA3084080C (fr)
PH (1) PH12020550739A1 (fr)
SG (1) SG11202004836UA (fr)
TW (1) TWI710979B (fr)
WO (1) WO2019195071A1 (fr)

Families Citing this family (58)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2020522796A (ja) 2017-06-01 2020-07-30 シュヴェイ， インク． ディー／ビー／エー アクソーニＳＣＨＶＥＹ， ＩＮＣ． ｄ／ｂ／ａ ＡＸＯＮＩ 安全なアクセス制限を管理する分散型のプライベートにサブスペース化されたブロックチェーン・データ構造
US10476847B1 (en) 2017-12-08 2019-11-12 Symbiont.Io, Inc. Systems, methods, and devices for implementing a smart contract on a distributed ledger technology platform
CN108848119B (zh) 2018-04-03 2020-04-28 阿里巴巴集团控股有限公司 跨区块链的交互方法及装置、系统、电子设备
CN109614823B (zh) 2018-10-26 2022-05-13 蚂蚁双链科技(上海)有限公司 一种数据的处理方法、装置及设备
CN112765595B (zh) * 2018-11-16 2024-05-10 创新先进技术有限公司 跨区块链的数据处理方法、装置、客户端、区块链系统
CN111224793B (zh) * 2018-11-27 2021-06-01 华为技术有限公司 数据存储方法、装置、计算机设备及可读存储介质
CN109446273B (zh) * 2018-12-04 2022-07-22 深圳前海环融联易信息科技服务有限公司 区块链的数据同步方法、装置、计算机设备及存储介质
CN109600367A (zh) * 2018-12-07 2019-04-09 众安信息技术服务有限公司 用于实现跨链消息处理的方法以及设备
CN110009369A (zh) * 2018-12-20 2019-07-12 阿里巴巴集团控股有限公司 容器检验方法及装置、电子设备
CN111782668B (zh) 2018-12-20 2024-06-28 创新先进技术有限公司 数据结构的读取及更新方法、装置、电子设备
BR112019016064A2 (pt) 2018-12-28 2020-03-31 Alibaba Group Holding Limited Método implementado por computador, meio de armazenamento legível e sistema
MX2019009344A (es) 2018-12-28 2019-10-02 Alibaba Group Holding Ltd Ejecucion paralela de transacciones en una red de cadena de bloques con base en listas blancas de contratos inteligentes.
CN109873861B (zh) * 2019-01-11 2022-04-12 平安科技（深圳）有限公司 跨区块链节点的交互方法及装置、存储介质及电子设备
US20220123947A1 (en) * 2019-01-18 2022-04-21 Zeu Technologies, Inc. A Method for Generating Random Numbers in Blockchain Smart Contracts
US10901983B2 (en) * 2019-03-01 2021-01-26 Wanchain Ltd. System and method for universal blockchain interoperability
CN109857580B (zh) * 2019-03-12 2022-06-07 深圳市迅雷网络技术有限公司 区块链跨链合约调用方法、装置及存储介质
CN109981679B (zh) * 2019-04-08 2021-08-10 上海点融信息科技有限责任公司 在区块链网络中执行事务的方法和装置
US10825024B1 (en) * 2019-04-12 2020-11-03 Symbiont.Io, Inc. Systems, devices, and methods for DLT-based data management platforms and data products
CN110098979B (zh) * 2019-04-16 2023-04-14 深圳前海微众银行股份有限公司 一种基于区块链的短链接消息监听方法及装置
EP3632082B1 (fr) * 2019-04-19 2023-09-06 Advanced New Technologies Co., Ltd. Procédés et dispositifs pour établir une communication entre des réseaux de chaînes de blocs
US11995647B2 (en) * 2019-04-30 2024-05-28 Salesforce, Inc. System and method of providing interoperable distributed and decentralized ledgers using consensus on consensus and delegated consensus
CN110247842A (zh) * 2019-06-28 2019-09-17 江苏物联网研究发展中心 一种基于消息订阅机制的通讯方法
US11336451B2 (en) 2019-06-28 2022-05-17 Advanced New Technologies Co., Ltd. Cross-blockchain resource transmission
CN112862612B (zh) * 2019-06-28 2024-04-30 创新先进技术有限公司 一种跨链发送资源的方法和装置
EP3996028A4 (fr) 2019-07-26 2022-08-31 Huawei Technologies Co., Ltd. Appareil et procédé de transaction à chaîne croisée
CN114902204A (zh) * 2019-08-06 2022-08-12 泽乌科技公司 分布式区块链交易系统
CN110597925B (zh) * 2019-08-15 2021-09-14 腾讯科技（深圳）有限公司 一种基于区块链的跨链数据处理方法及装置
CN110532038B (zh) * 2019-08-19 2021-07-30 杭州趣链科技有限公司 一种基于Java智能合约的并行执行方法
CN111418183B (zh) 2019-11-27 2022-09-16 支付宝(杭州)信息技术有限公司 区块链区块的异步处理
EP4070221A1 (fr) 2019-12-02 2022-10-12 Schvey, Inc. D/B/A/ Axoni Appels inter-partition dans des mémoires de données partitionnées et inviolables
CN113111389A (zh) * 2020-01-13 2021-07-13 梅特勒-托利多(常州)精密仪器有限公司 测量设备的信息管理方法及装置
US12099997B1 (en) 2020-01-31 2024-09-24 Steven Mark Hoffberg Tokenized fungible liabilities
CN111724170B (zh) * 2020-03-05 2022-10-11 支付宝(杭州)信息技术有限公司 一种业务处理系统、业务处理的方法、装置及设备
CN111159307B (zh) * 2020-04-02 2020-07-24 支付宝(杭州)信息技术有限公司 跨链数据订阅方法及装置
CN111769948B (zh) * 2020-06-15 2023-06-02 布比（北京）网络技术有限公司 基于区块链的链间交互方法、系统、装置和计算机设备
CN111782707B (zh) * 2020-06-19 2024-04-16 京东科技信息技术有限公司 一种数据查询方法及系统
CN112104606B (zh) * 2020-08-12 2022-06-17 北京智融云河科技有限公司 一种基于随机多节点的可信执行方法和系统
CN114116883A (zh) * 2020-08-28 2022-03-01 京东方科技集团股份有限公司 数据管理方法、数据管理装置、区块链网络和系统
CN112153124B (zh) * 2020-09-11 2021-05-25 北京天德科技有限公司 一种区块链及智能合约系统协作层设计
CN112380266A (zh) * 2020-10-16 2021-02-19 广州市百果园网络科技有限公司 消息数据处理方法、装置、设备和存储介质
US11368288B2 (en) 2020-11-20 2022-06-21 Hong Kong Applied Science and Technology Research Institute Company Limited Apparatus and method of lightweight communication protocols between multiple blockchains
CN112235110B (zh) * 2020-12-14 2021-03-23 支付宝(杭州)信息技术有限公司 区块链的跨链业务处理方法、装置及电子设备
CN112511355B (zh) * 2020-12-18 2022-02-08 四川大学 一种跨链智能合约合作可能性评估方法
CN112737862B (zh) * 2021-01-08 2023-12-22 江苏众享金联科技有限公司 一种基于智能合约的跨链数据共享方法
CN112396427B (zh) * 2021-01-19 2021-04-23 北京连琪科技有限公司 一种面向通用场景的跨链互换操作方法
CN113032482B (zh) * 2021-03-10 2022-05-13 杭州链网科技有限公司 一种跨链转接桥的构建方法及系统
CN112737782B (zh) * 2021-03-30 2021-06-25 支付宝(杭州)信息技术有限公司 提供跨链消息的方法和装置
CN112732800B (zh) * 2021-03-30 2021-07-13 支付宝(杭州)信息技术有限公司 提供跨链消息的方法和装置
CN112948499A (zh) * 2021-03-31 2021-06-11 北京金山云网络技术有限公司 信息获取方法和装置、电子设备和存储介质
CN113077342B (zh) * 2021-04-06 2023-01-20 立旃（上海）科技有限公司 基于区块链进行跨境使用数据的方法及装置
CN113222766B (zh) * 2021-05-13 2023-02-07 杭州趣链科技有限公司 金融产品的信息监管方法、装置、计算机设备及介质
CN113328935B (zh) * 2021-05-20 2022-11-11 福建思特电子有限公司 基于工业互联网的分布式安全追溯区块链系统
CN113259131B (zh) * 2021-06-23 2021-10-08 北京笔新互联网科技有限公司 区块链节点、系统和区块链构建方法
CN113688317B (zh) * 2021-08-24 2022-06-17 江苏中润普达信息技术有限公司 一种基于区块链的信息推荐方法及系统
CN114157671B (zh) * 2021-11-26 2024-06-18 支付宝(杭州)信息技术有限公司 将区块链网络承载的信息向多个客户端节点分发的方法
CN114257487B (zh) * 2021-11-26 2024-03-29 蚂蚁区块链科技(上海)有限公司 管理网络节点集的系统和方法
CN114390097A (zh) * 2022-01-10 2022-04-22 北京新华夏信息技术有限公司 基于消息队列的区块链运行方法、系统及其应用
CN114827071B (zh) * 2022-03-29 2023-05-09 中国人民解放军军事科学院战争研究院 一种基于信息目录的跨业务区域消息交互方法、装置、电子设备及存储介质

Family Cites Families (25)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104092767B (zh) * 2014-07-21 2017-06-13 北京邮电大学 一种增加消息队列模型的发布/订阅系统及其工作方法
US10812274B2 (en) * 2015-05-07 2020-10-20 Blockstream Corporation Transferring ledger assets between blockchains via pegged sidechains
US20170132626A1 (en) 2015-11-05 2017-05-11 Mastercard International Incorporated Method and system for processing of a blockchain transaction in a transaction processing network
US20170140408A1 (en) * 2015-11-16 2017-05-18 Bank Of America Corporation Transparent self-managing rewards program using blockchain and smart contracts
US10135870B2 (en) 2016-02-22 2018-11-20 Bank Of America Corporation System for external validation of secure process transactions
US10142312B2 (en) 2016-02-22 2018-11-27 Bank Of America Corporation System for establishing secure access for users in a process data network
WO2018006072A1 (fr) * 2016-06-30 2018-01-04 Clause, Inc. Systèmes et procédé de formation, de stockage, de gestion et d'exécution de contrats
US10097344B2 (en) 2016-07-15 2018-10-09 Mastercard International Incorporated Method and system for partitioned blockchains and enhanced privacy for permissioned blockchains
CN106485495A (zh) * 2016-09-18 2017-03-08 江苏通付盾科技有限公司 交易信息订阅方法、装置、服务器以及系统
US11182851B2 (en) 2016-10-20 2021-11-23 International Business Machines Corporation Inter-ledger messaging in a blockchain
TWI614713B (zh) * 2017-01-23 2018-02-11 現代財富控股有限公司 基於區塊鏈的智能合約版本控管系統及其方法
CN106874087A (zh) * 2017-01-25 2017-06-20 上海钜真金融信息服务有限公司 一种区块链智能合约定时任务调度方法
CN106960388A (zh) * 2017-03-01 2017-07-18 中钞信用卡产业发展有限公司北京智能卡技术研究院 跨区块链的数字资产流转的方法和装置
KR102414732B1 (ko) * 2017-04-05 2022-06-28 삼성에스디에스 주식회사 블록체인 기반 디지털 아이덴티티 관리 방법
CN107103473A (zh) * 2017-04-27 2017-08-29 电子科技大学 一种基于区块链的智能合约实现方法
CN107231299A (zh) * 2017-06-07 2017-10-03 众安信息技术服务有限公司 一种链路由及实现区块链跨链通信的系统
CN107301536B (zh) * 2017-06-12 2019-07-12 腾讯科技（深圳）有限公司 资源转移方法及装置
CN107248076A (zh) * 2017-06-24 2017-10-13 北京天德科技有限公司 一种双链式跨链交易的区块链互联网模型的核心算法
US10944546B2 (en) * 2017-07-07 2021-03-09 Microsoft Technology Licensing, Llc Blockchain object interface
TWM554608U (zh) * 2017-09-01 2018-01-21 國泰人壽保險股份有限公司 基於區塊鏈的保險服務系統
CN107742210A (zh) * 2017-10-13 2018-02-27 布比（北京）网络技术有限公司 一种不同区块链间的跨链转账系统和方法
US10567320B2 (en) * 2017-10-17 2020-02-18 American Express Travel Related Services Company, Inc. Messaging balancing and control on blockchain
US20190156938A1 (en) * 2017-11-20 2019-05-23 Michael Brunner System, method and data model for secure prescription management
CN108848119B (zh) 2018-04-03 2020-04-28 阿里巴巴集团控股有限公司 跨区块链的交互方法及装置、系统、电子设备
US20190050854A1 (en) * 2018-09-28 2019-02-14 Intel Corporation Blockchain-based digital data exchange

Also Published As

Publication number Publication date
CA3084080C (fr) 2023-03-14
AU2019248524A1 (en) 2020-06-18
CN111787072A (zh) 2020-10-16
AU2019248524C1 (en) 2021-04-08
JP2021504847A (ja) 2021-02-15
JP6929497B2 (ja) 2021-09-01
CN108848119B (zh) 2020-04-28
SG11202004836UA (en) 2020-06-29
KR102215248B1 (ko) 2021-02-16
US10693630B1 (en) 2020-06-23
US20200213088A1 (en) 2020-07-02
CN108848119A (zh) 2018-11-20
US10615964B2 (en) 2020-04-07
TWI710979B (zh) 2020-11-21
TW201942816A (zh) 2019-11-01
EP3701413A1 (fr) 2020-09-02
AU2019248524B2 (en) 2021-01-07
US20190305935A1 (en) 2019-10-03
PH12020550739A1 (en) 2021-04-19
CA3084080A1 (fr) 2019-10-10
WO2019195071A1 (fr) 2019-10-10
KR20200069370A (ko) 2020-06-16
CN111787072B (zh) 2023-02-28

Similar Documents

Publication Publication Date Title
EP3701413B1 (fr) Procédé, appareil, système et dispositif électronique d'interaction de chaîne de blocs croisés
US10785232B2 (en) Method, apparatus, system, and electronic device for cross-blockchain interaction
CA3083819C (fr) Procede, appareil et dispositif electronique d'authentification entre chaines de blocs
US11016961B2 (en) Blockchain-based smart contract invocation method and apparatus, and electronic device
AU2019227618B2 (en) Method, apparatus, and electronic device for executing transactions based on blockchain

Legal Events

Date Code Title Description
STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: UNKNOWN

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE INTERNATIONAL PUBLICATION HAS BEEN MADE

PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: REQUEST FOR EXAMINATION WAS MADE

17P Request for examination filed

Effective date: 20200527

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

AX Request for extension of the european patent

Extension state: BA ME

RAP1 Party data changed (applicant data changed or rights of an application transferred)

Owner name: ADVANCED NEW TECHNOLOGIES CO., LTD.

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: EXAMINATION IS IN PROGRESS

17Q First examination report despatched

Effective date: 20210329

DAV Request for validation of the european patent (deleted)
DAX Request for extension of the european patent (deleted)
REG Reference to a national code

Ref country code: DE

Ref legal event code: R079

Ref document number: 602019011896

Country of ref document: DE

Free format text: PREVIOUS MAIN CLASS: G06F0021640000

Ipc: H04L0009320000

GRAP Despatch of communication of intention to grant a patent

Free format text: ORIGINAL CODE: EPIDOSNIGR1

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: GRANT OF PATENT IS INTENDED

RIC1 Information provided on ipc code assigned before grant

Ipc: G06F 21/64 20130101ALI20210812BHEP

Ipc: H04L 9/32 20060101AFI20210812BHEP

INTG Intention to grant announced

Effective date: 20210902

GRAJ Information related to disapproval of communication of intention to grant by the applicant or resumption of examination proceedings by the epo deleted

Free format text: ORIGINAL CODE: EPIDOSDIGR1

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: EXAMINATION IS IN PROGRESS

GRAP Despatch of communication of intention to grant a patent

Free format text: ORIGINAL CODE: EPIDOSNIGR1

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: GRANT OF PATENT IS INTENDED

INTC Intention to grant announced (deleted)
INTG Intention to grant announced

Effective date: 20211019

GRAS Grant fee paid

Free format text: ORIGINAL CODE: EPIDOSNIGR3

GRAA (expected) grant

Free format text: ORIGINAL CODE: 0009210

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE PATENT HAS BEEN GRANTED

AK Designated contracting states

Kind code of ref document: B1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

REG Reference to a national code

Ref country code: GB

Ref legal event code: FG4D

REG Reference to a national code

Ref country code: CH

Ref legal event code: EP

REG Reference to a national code

Ref country code: AT

Ref legal event code: REF

Ref document number: 1471308

Country of ref document: AT

Kind code of ref document: T

Effective date: 20220315

REG Reference to a national code

Ref country code: IE

Ref legal event code: FG4D

REG Reference to a national code

Ref country code: DE

Ref legal event code: R096

Ref document number: 602019011896

Country of ref document: DE

REG Reference to a national code

Ref country code: LT

Ref legal event code: MG9D

REG Reference to a national code

Ref country code: NL

Ref legal event code: MP

Effective date: 20220223

REG Reference to a national code

Ref country code: AT

Ref legal event code: MK05

Ref document number: 1471308

Country of ref document: AT

Kind code of ref document: T

Effective date: 20220223

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: SE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20220223

Ref country code: RS

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20220223

Ref country code: PT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20220623

Ref country code: NO

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20220523

Ref country code: NL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20220223

Ref country code: LT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20220223

Ref country code: HR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20220223

Ref country code: ES

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20220223

Ref country code: BG

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20220523

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: PL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20220223

Ref country code: LV

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20220223

Ref country code: GR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20220524

Ref country code: FI

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20220223

Ref country code: AT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20220223

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: IS

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20220623

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: SM

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20220223

Ref country code: SK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20220223

Ref country code: RO

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20220223

Ref country code: EE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20220223

Ref country code: DK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20220223

Ref country code: CZ

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20220223

REG Reference to a national code

Ref country code: CH

Ref legal event code: PL

REG Reference to a national code

Ref country code: DE

Ref legal event code: R097

Ref document number: 602019011896

Country of ref document: DE

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: MC

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20220223

Ref country code: AL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20220223

REG Reference to a national code

Ref country code: BE

Ref legal event code: MM

Effective date: 20220331

PLBE No opposition filed within time limit

Free format text: ORIGINAL CODE: 0009261

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: NO OPPOSITION FILED WITHIN TIME LIMIT

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: LU

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20220328

Ref country code: LI

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20220331

Ref country code: IE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20220328

Ref country code: CH

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20220331

26N No opposition filed

Effective date: 20221124

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: SI

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20220223

Ref country code: BE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20220331

P01 Opt-out of the competence of the unified patent court (upc) registered

Effective date: 20230524

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: IT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20220223

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: MK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20220223

Ref country code: CY

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20220223

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: DE

Payment date: 20240130

Year of fee payment: 6

Ref country code: GB

Payment date: 20240108

Year of fee payment: 6

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: HU

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT; INVALID AB INITIO

Effective date: 20190328

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: FR

Payment date: 20240213

Year of fee payment: 6

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: MT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20220223