Cross-chain interoperability method, device and electronic device in alliance chain

Abstract

The present application discloses a cross-chain interoperability method, device and electronic device in a consortium chain, which obtains a cross-chain interoperability request, parses the cross-chain interoperability request, determines the initiator ID of the cross-chain interoperability request and the target data pointed to by the cross-chain interoperability request; performs a legality judgment to determine the target data pointed to by the request in the consortium chain, and transfers the target data pointed to by the request in the consortium chain to a temporarily created storage address, in response to the cross-chain interoperability request, sends the target data from the storage address to the data demand node corresponding to the initiator ID, and the data demand node is located in the external blockchain of the consortium chain, and the external blockchain is mapped to the consortium chain subnet within the consortium chain, thereby realizing efficient cross-chain interoperability between the consortium chain and the external blockchain.

Description

Technical Field

[0001] The present application relates to the field of alliance chain technology, and in particular to a cross-chain interoperability method, device and electronic device in an alliance chain. Background Art

[0002] Blockchain, due to its unique traceability and immutability, has gained widespread adoption and is a popular platform for data storage and sharing. Consortium chains, among other blockchains, offer high processing speeds and low transaction costs due to their relatively small number of nodes. However, precisely because these chains have fewer nodes, they are prone to congestion. Therefore, cross-chain collaboration is often used to expand capacity and mitigate congestion by connecting consortium chains with external blockchains.

[0003] However, how to achieve efficient cross-chain interoperability between alliance chains and external blockchains has become a technical problem that needs to be solved urgently. Summary of the Invention

[0004] Based on the above problems, the embodiments of the present application provide a cross-chain interoperability method, device and electronic device in a consortium chain.

[0005] The embodiments of this application disclose the following technical solutions:

[0006] A cross-chain interoperability method in a consortium chain, comprising:

[0007] Obtain a cross-chain interoperation request, parse the cross-chain interoperation request, and determine the initiator ID of the cross-chain interoperation request and the target data pointed to by the cross-chain interoperation request;

[0008] Conducting a legality assessment to determine the target data requested in the consortium chain, transferring the target data requested in the consortium chain to a temporarily created storage address, responding to the cross-chain interoperability request, and sending the target data from the storage address to the data request node corresponding to the initiator ID. The data request node is located in the external blockchain of the consortium chain, and the external blockchain is mapped to the consortium chain subnet within the consortium chain.

[0009] Temporarily creating the storage address according to the cross-chain interoperability request legitimacy declarations generated by multiple nodes in the consortium chain for conducting legitimacy assessment on the cross-chain interoperability request;

[0010] The performing of legitimacy verification on the cross-chain interoperability request based on the legitimacy declarations of the cross-chain interoperability request generated by the multiple in-chain nodes includes: each in-chain node among the multiple in-chain nodes verifies the signature of a non-self-owned legitimacy declaration of the cross-chain interoperability request, counting the volume of the legitimacy declarations of the cross-chain interoperability request that pass the verification, and if a predetermined signature verification threshold indicating that the cross-chain interoperability request is legitimate is reached, determining that the cross-chain interoperability request has passed the legitimacy verification.

[0011] Preferably, in some embodiments, the temporarily creating a storage address according to the legitimacy declaration of the cross-chain interoperability request generated by multiple in-chain nodes in the alliance chain for performing legitimacy judgment on the cross-chain interoperability request includes: collecting the legitimacy declaration of the cross-chain interoperability request generated by multiple in-chain nodes in the blockchain for performing legitimacy judgment on the cross-chain interoperability request; performing legitimacy verification on the cross-chain interoperability request according to the legitimacy declaration of the cross-chain interoperability request generated by the multiple in-chain nodes; and temporarily creating the storage address in response to the cross-chain interoperability request passing the legitimacy verification.

[0012] Preferably, in some embodiments, in response to the cross-chain interoperability request passing the legitimacy verification, a storage address is temporarily created, including: in response to the cross-chain interoperability request passing the legitimacy verification, the private feature data owned by the multiple nodes in the chain and the public feature data of the alliance chain are obtained, so as to temporarily create a storage address based on the private feature data owned by the multiple nodes in the chain and the public feature data of the alliance chain.

[0013] Preferably, in some embodiments, sending the target data from the storage address to the data demand node corresponding to the initiator ID includes: obtaining a target data release request to verify the legitimacy of the target data release request; in response to the target data release request passing the legitimacy verification, sending the target data from the storage address to the data demand node corresponding to the initiator ID.

[0014] Preferably, in some embodiments, the obtaining of the target data release request to perform legitimacy verification on the target data release request includes: in response to obtaining the target data release request, obtaining legitimacy declarations of the target data release request generated by the multiple nodes in the chain; and performing legitimacy verification on the target data release request based on the legitimacy declarations of the target data release request generated by the multiple nodes in the chain.

[0015] Preferably, in some embodiments, the target data release request is subjected to legitimacy verification based on the legitimacy declaration of the target data release request generated by the multiple chain nodes, including: each chain node among the multiple chain nodes verifies the legitimacy declaration of the target data release request that is not its own, and counts the volume of the legitimacy declaration of the target data release request that passes the verification, and if a predetermined verification threshold indicating that the target data release request is legal is reached, it is determined that the target data release request has passed the legitimacy verification.

[0016] Preferably, in some embodiments, sending the target data from the storage address to the data demand node corresponding to the initiator ID includes: sending the target data from the storage address to the data demand node corresponding to the initiator ID within a set time lock range; if the target data is not sent from the storage address to the data demand node corresponding to the initiator ID within the set time lock range, destroying the storage address to destroy the target data therein.

[0017] Preferably, in some embodiments, the cross-chain interoperability method in a consortium chain further includes: in response to the target data being successfully sent from the storage address to the data demand node corresponding to the initiator ID, destroying the target data release request legitimacy declaration and the cross-chain interoperation request legitimacy declaration.

[0018] Accordingly, the embodiment of the present application further discloses a cross-chain interoperability device in a consortium chain, comprising:

[0019] The first program unit is configured to obtain a cross-chain interoperation request, parse the cross-chain interoperation request, and determine the initiator ID of the cross-chain interoperation request and the target data pointed to by the cross-chain interoperation request;

[0020] The second program unit is used to conduct a legality assessment to determine the target data pointed to by the request in the alliance chain, so as to transfer the target data pointed to by the request in the alliance chain to a temporarily created storage address, so as to respond to the cross-chain interoperability request and send the target data from the storage address to the data demand node corresponding to the initiator ID. The data demand node is located in the external blockchain of the alliance chain, and the external blockchain is mapped to the alliance chain subnet inside the alliance chain.

[0021] Preferably, in some embodiments, the device further includes: a judgment creation unit, used to temporarily create the storage address based on the cross-chain interoperability request legitimacy declaration generated by multiple chain nodes in the alliance chain for performing legitimacy judgment on the cross-chain interoperability request.

[0022] Preferably, in some embodiments, the analysis and creation unit is further used to: collect the legitimacy declarations of the cross-chain interoperability request generated by multiple in-chain nodes in the blockchain for conducting legitimacy analysis on the cross-chain interoperability request; perform legitimacy verification on the cross-chain interoperability request based on the legitimacy declarations of the cross-chain interoperability request generated by the multiple in-chain nodes; and temporarily create the storage address in response to the cross-chain interoperability request passing the legitimacy verification.

[0023] Preferably, in some embodiments, the analysis and creation unit is further used to: in response to the cross-chain interoperability request passing the legitimacy verification, obtain the private feature data owned by the multiple nodes in the chain and the public feature data of the alliance chain, so as to temporarily create the storage address based on the private feature data owned by the multiple nodes in the chain and the public feature data of the alliance chain.

[0024] Preferably, in some embodiments, the analysis and creation unit is further used to: each of the multiple chain nodes verifies the legitimacy declaration of the non-self-owned cross-chain interoperability request, counts the volume of the legitimacy declaration of the cross-chain interoperability request that passes the verification, and if a predetermined verification threshold indicating that the cross-chain interoperability request is legal is reached, it is determined that the cross-chain interoperability request has passed the legitimacy verification.

[0025] Preferably, in some embodiments, the second program unit is further used to: obtain a target data release request to verify the legitimacy of the target data release request; in response to the target data release request passing the legitimacy verification, send the target data from the storage address to the data demand node corresponding to the initiator ID.

[0026] Preferably, in some embodiments, the second program unit is further used to: in response to obtaining the target data release request, obtain the legitimacy declaration of the target data release request generated by the multiple nodes in the chain; and verify the legitimacy of the target data release request based on the legitimacy declaration of the target data release request generated by the multiple nodes in the chain.

[0027] Preferably, in some embodiments, the second program unit is further used for: each of the multiple chain nodes verifies the legitimacy declaration of the target data release request that is not owned by itself, and counts the volume of the legitimacy declaration of the target data release request that has passed the verification; if a predetermined verification threshold indicating that the target data release request is legal is reached, it is determined that the target data release request has passed the legitimacy verification.

[0028] Preferably, in some embodiments, the second program unit is further used to: send the target data from the storage address to the data demand node corresponding to the initiator ID within a set time lock range; if the target data is not sent from the storage address to the data demand node corresponding to the initiator ID within the set time lock range, destroy the storage address to destroy the target data therein.

[0029] Preferably, in some embodiments, the device further includes: a sending destruction unit, configured to destroy the target data release request legitimacy declaration and the cross-chain interoperability request legitimacy declaration in response to the target data being successfully sent from the storage address to the data demand node corresponding to the initiator ID.

[0030] Accordingly, an embodiment of the present application further provides an electronic device, including a memory and a processor, wherein an executable program is stored in the memory, and when the processor runs the executable program, the following steps are performed:

[0031] Obtain a cross-chain interoperation request, parse the cross-chain interoperation request, and determine the initiator ID of the cross-chain interoperation request and the target data pointed to by the cross-chain interoperation request;

[0032] Conduct a legality assessment to determine the target data pointed to by the request in the alliance chain, transfer the target data pointed to by the request in the alliance chain to a temporarily created storage address, respond to the cross-chain interoperability request, and send the target data from the storage address to the data demand node corresponding to the initiator ID. The data demand node is located in the external blockchain of the alliance chain, and the external blockchain is mapped to the alliance chain subnet within the alliance chain.

[0033] In the technical solution of the embodiment of the present application, a cross-chain interoperation request is obtained, and the cross-chain interoperation request is parsed to determine the initiator ID of the cross-chain interoperation request and the target data pointed to by the cross-chain interoperation request; a legality judgment is performed to determine the target data pointed to by the request in the alliance chain, so as to transfer the target data pointed to by the request in the alliance chain to a temporarily created storage address, in response to the cross-chain interoperation request, and send the target data from the storage address to the data demand node corresponding to the initiator ID, the data demand node is located in the external blockchain of the alliance chain, and the external blockchain is mapped to the alliance chain subnet inside the alliance chain, thereby realizing efficient cross-chain interoperation between the alliance chain and the external blockchain. BRIEF DESCRIPTION OF THE DRAWINGS

[0034] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the following briefly introduces the drawings required for use in the embodiments or the description of the prior art. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative labor.

[0035] Figure 1 This is a flowchart of a cross-chain interoperability method in a consortium chain according to an embodiment of the present application;

[0036] Figure 2 This is a structural diagram of a cross-chain interoperability device in a consortium chain according to an embodiment of the present application;

[0037] Figure 3 This is another structural diagram of a cross-chain interoperability device in a consortium chain according to an embodiment of the present application;

[0038] Figure 4 This is a schematic diagram of the structure of an electronic device in an embodiment of the present application;

[0039] Figure 5 Schematic diagram of the hardware structure of the electronic device in the embodiment of the present application. DETAILED DESCRIPTION

[0040] The implementation of any technical solution in the embodiments of the present application does not necessarily require achieving all of the above advantages at the same time.

[0041] In order to enable those skilled in the art to better understand the solutions of the present invention, the technical solutions in the embodiments of the present invention will be clearly and completely described below in conjunction with the accompanying drawings of the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without making creative efforts shall fall within the scope of protection of the present invention.

[0042] In the technical solution of the embodiment of the present application, a cross-chain interoperation request is obtained, and the cross-chain interoperation request is parsed to determine the initiator ID of the cross-chain interoperation request and the target data pointed to by the cross-chain interoperation request; a legality judgment is performed to determine the target data pointed to by the request in the alliance chain, so as to transfer the target data pointed to by the request in the alliance chain to a temporarily created storage address, in response to the cross-chain interoperation request, and send the target data from the storage address to the data demand node corresponding to the initiator ID, the data demand node is located in the external blockchain of the alliance chain, and the external blockchain is mapped to the alliance chain subnet inside the alliance chain, thereby realizing efficient cross-chain interoperation between the alliance chain and the external blockchain.

[0043] Figure 1 This is a flow chart of a cross-chain interoperability method in a consortium chain according to an embodiment of the present application; Figure 1 As shown, it includes:

[0044] S101. Obtain a cross-chain interoperation request, parse the cross-chain interoperation request, and determine the initiator ID of the cross-chain interoperation request and the target data pointed to by the cross-chain interoperation request;

[0045] In this embodiment, the cross-chain interoperation request can be obtained by burying points and parsed.

[0046] S102. Conduct a legality assessment to determine the target data pointed to by the request in the consortium chain, transfer the target data pointed to by the request in the consortium chain to a temporarily created storage address, respond to the cross-chain interoperability request, and send the target data from the storage address to the data demand node corresponding to the initiator ID. The data demand node is located in the external blockchain of the consortium chain, and the external blockchain is mapped to the consortium chain subnet within the consortium chain.

[0047] Optionally, the cross-chain interoperability method in a consortium chain further includes: temporarily creating the storage address according to the cross-chain interoperability request legitimacy declaration generated by multiple chain nodes in the consortium chain for conducting legitimacy analysis on the cross-chain interoperability request.

[0048] In this embodiment, by temporarily creating the storage address, the flexible maintenance of storage resources is ensured, and the waste of resources caused by occupying too much storage resources is avoided.

[0049] Optionally, temporarily creating the storage address according to the cross-chain interoperability request legitimacy declarations generated by multiple in-chain nodes in the consortium chain for conducting legitimacy assessment on the cross-chain interoperability request includes:

[0050] Collecting cross-chain interoperability request legitimacy declarations generated by multiple nodes in the blockchain for conducting legitimacy assessment of the cross-chain interoperability request;

[0051] Verify the legitimacy of the cross-chain interoperability request based on the legitimacy declarations of the cross-chain interoperability request generated by the multiple nodes in the chain;

[0052] In response to the cross-chain interoperability request passing the legitimacy verification, a storage address is temporarily created.

[0053] In this embodiment, the legitimacy of the cross-chain interoperation request is verified based on the cross-chain interoperation request legitimacy declaration, which improves the security of the data and further enables the rapid temporary creation of the storage address.

[0054] Optionally, in response to the cross-chain interoperability request passing the legitimacy verification, a storage address is temporarily created, including: in response to the cross-chain interoperability request passing the legitimacy verification, the private feature data owned by the multiple nodes in the chain and the public feature data of the alliance chain are obtained, so as to temporarily create a storage address based on the private feature data owned by the multiple nodes in the chain and the public feature data of the alliance chain.

[0055] In this embodiment, based on the private feature data owned by the multiple chain nodes and the public feature data of the alliance chain, the created storage address has higher security, further ensuring the security of data storage.

[0056] Optionally, the performing of legitimacy verification on the cross-chain interoperability request based on the legitimacy declaration of the cross-chain interoperability request generated by the multiple in-chain nodes includes: each in-chain node among the multiple in-chain nodes verifies the signature of the non-self-owned legitimacy declaration of the cross-chain interoperability request, and counts the volume of the legitimacy declaration of the cross-chain interoperability request that passes the verification; if a predetermined signature verification threshold indicating that the cross-chain interoperability request is legitimate is reached, it is determined that the cross-chain interoperability request has passed the legitimacy verification.

[0057] In this embodiment, by verifying the signatures of non-self-owned cross-chain interoperability request legitimacy declarations and further counting the volume of cross-chain interoperability request legitimacy declarations that have passed the signature verification, the accuracy of legitimacy verification is improved and misjudgment is avoided.

[0058] Optionally, sending the target data from the storage address to the data demand node corresponding to the initiator ID includes: obtaining a target data release request to verify the legitimacy of the target data release request; in response to the target data release request passing the legitimacy verification, sending the target data from the storage address to the data demand node corresponding to the initiator ID.

[0059] In this embodiment, since the storage address is temporarily created, the target data is sent from the storage address to the data demand node corresponding to the initiator ID, thereby ensuring the security of data transmission.

[0060] Optionally, obtaining the target data release request to verify the legitimacy of the target data release request includes: in response to obtaining the target data release request, obtaining the legitimacy declaration of the target data release request generated by the multiple nodes in the chain; and verifying the legitimacy of the target data release request based on the legitimacy declaration of the target data release request generated by the multiple nodes in the chain.

[0061] In this embodiment, the legitimacy of the target data release request is verified by using the legitimacy declarations of the target data release request generated by the multiple nodes in the chain, which can ensure the reliability of the legitimacy verification.

[0062] Optionally, the target data release request is subjected to a validity verification based on the target data release request validity declaration generated by the multiple chain nodes, including: each chain node among the multiple chain nodes verifies the validity declaration of the target data release request that is not its own, and counts the volume of the target data release request validity declaration that has passed the verification; if a predetermined verification threshold indicating that the target data release request is legitimate is reached, it is determined that the target data release request has passed the validity verification.

[0063] Optionally, sending the target data from the storage address to the data demand node corresponding to the initiator ID includes: sending the target data from the storage address to the data demand node corresponding to the initiator ID within a set time lock range; if the target data is not sent from the storage address to the data demand node corresponding to the initiator ID within the set time lock range, destroying the storage address to destroy the target data therein.

[0064] In this embodiment, the time lock can ensure the security of data transmission. Once the target data is not sent from the storage address to the data requesting node corresponding to the initiator ID, the storage address is destroyed to destroy the target data therein, thereby directly destroying the storage address to destroy the target data therein, thereby ensuring the security of the target data.

[0065] Optionally, the cross-chain interoperability method in a consortium chain further includes: in response to the target data being successfully sent from the storage address to the data demand node corresponding to the initiator ID, destroying the target data release request legitimacy declaration and the cross-chain interoperation request legitimacy declaration.

[0066] By destroying the target data release request legitimacy declaration and the cross-chain interoperability request legitimacy declaration, the release of resources is achieved, ensuring the flexibility of algorithm execution.

[0067] Figure 2This is a structural diagram of a cross-chain interoperability device in a consortium chain according to an embodiment of the present application; Figure 2 As shown, it includes:

[0068] The first program unit 201 is used to obtain a cross-chain interoperation request, parse the cross-chain interoperation request, and determine the initiator ID of the cross-chain interoperation request and the target data pointed to by the cross-chain interoperation request;

[0069] The second program unit 202 is used to perform a legitimacy analysis to determine the target data pointed to by the request in the alliance chain, so as to transfer the target data pointed to by the request in the alliance chain to a temporarily created storage address, so as to respond to the cross-chain interoperability request and send the target data from the storage address to the data demand node corresponding to the initiator ID. The data demand node is located in the external blockchain of the alliance chain, and the external blockchain is mapped to the alliance chain subnet inside the alliance chain.

[0070] Optionally, the device also includes: a judgment creation unit 203, which is used to temporarily create a storage address based on the cross-chain interoperation request legitimacy declaration generated by multiple chain nodes in the alliance chain for performing legitimacy judgment on the cross-chain interoperation request.

[0071] Optionally, the analysis and creation unit 203 is further used to: collect the cross-chain interoperability request legitimacy declarations generated by multiple chain nodes in the blockchain for conducting legitimacy analysis on the cross-chain interoperability request; verify the legitimacy of the cross-chain interoperability request based on the cross-chain interoperability request legitimacy declarations generated by the multiple chain nodes; and temporarily create the storage address in response to the cross-chain interoperability request passing the legitimacy verification.

[0072] Optionally, the analysis and creation unit 203 is further used to: in response to the cross-chain interoperability request passing the legitimacy verification, obtain the private feature data owned by the multiple nodes in the chain and the public feature data of the alliance chain, so as to temporarily create the storage address based on the private feature data owned by the multiple nodes in the chain and the public feature data of the alliance chain.

[0073] Optionally, the analysis and creation unit 203 is further used to: each of the multiple chain nodes verifies the legitimacy declaration of the non-self-owned cross-chain interoperation request, counts the volume of the legitimacy declaration of the cross-chain interoperation request that passes the verification, and if a predetermined verification threshold indicating that the cross-chain interoperation request is legal is reached, it is determined that the cross-chain interoperation request has passed the legitimacy verification.

[0074] Optionally, the second program unit 202 is further used to: obtain a target data release request to verify the legitimacy of the target data release request; in response to the target data release request passing the legitimacy verification, send the target data from the storage address to the data demand node corresponding to the initiator ID.

[0075] Optionally, the second program unit 202 is further used to: in response to obtaining the target data release request, obtain the target data release request legitimacy declaration generated by the multiple nodes in the chain; and verify the legitimacy of the target data release request based on the target data release request legitimacy declaration generated by the multiple nodes in the chain.

[0076] Optionally, the second program unit 202 is further used for: each of the multiple chain nodes verifies the legitimacy declaration of the target data release request that is not owned by itself, and counts the volume of the legitimacy declaration of the target data release request that has passed the verification; if a predetermined verification threshold indicating that the target data release request is legal is reached, it is determined that the target data release request has passed the legitimacy verification.

[0077] Optionally, the second program unit 202 is further used to: send the target data from the storage address to the data demand node corresponding to the initiator ID within the set time lock range; if the target data is not sent from the storage address to the data demand node corresponding to the initiator ID within the set time lock range, destroy the storage address to destroy the target data therein.

[0078] Figure 3 This is a structural diagram of a cross-chain interoperability device in a consortium chain according to an embodiment of the present application; Figure 3 As shown in the above Figure 2 Based on the embodiment, the cross-chain interoperability device in the alliance chain of the embodiment of the present application has the following features:

[0079] Optionally, the device also includes: a sending destruction unit 204, which is used to destroy the target data release request legitimacy declaration and the cross-chain interoperability request legitimacy declaration in response to the target data being successfully sent from the storage address to the data demand node corresponding to the initiator ID.

[0080] Figure 4 This is a schematic diagram of the structure of an electronic device according to an embodiment of the present application; Figure 4As shown, it includes a memory 301 and a processor 302. The memory stores an executable program. When the processor runs the executable program, it performs the following steps: obtaining a cross-chain interoperation request, parsing the cross-chain interoperation request, and determining the initiator ID of the cross-chain interoperation request and the target data pointed to by the cross-chain interoperation request;

[0081] Conduct a legality assessment to determine the target data pointed to by the request in the alliance chain, transfer the target data pointed to by the request in the alliance chain to a temporarily created storage address, respond to the cross-chain interoperability request, and send the target data from the storage address to the data demand node corresponding to the initiator ID. The data demand node is located in the external blockchain of the alliance chain, and the external blockchain is mapped to the alliance chain subnet within the alliance chain. Figure 5 Schematic diagram of the hardware structure of the electronic device in the embodiment of the present application; Figure 5 As shown, the hardware structure of the electronic device may include: the electronic device 400 includes a computing unit 401, which can perform various appropriate actions and processes according to a computer program stored in a read-only memory (ROM) 402 or a computer program loaded from a storage unit 408 into a random access memory (RAM) 403. Various programs and data required for the operation of the device 400 can also be stored in the RAM 403. The computing unit 401, ROM 402, and RAM 403 are connected to each other via a bus 404. An input / output (I / O) interface 405 is also connected to the bus 404.

[0082] Multiple components within electronic device 400 are connected to I / O interface 405, including an input unit 406, an output unit 407, a storage unit 408, and a communication unit 409. Input unit 406 can be any type of device capable of inputting information into electronic device 400. Input unit 406 can receive input numeric or character information and generate key input signals related to user settings and / or function control of the electronic device. Output unit 407 can be any type of device capable of presenting information and may include, but is not limited to, a display, a speaker, a video / audio output terminal, a vibrator, and / or a printer. Storage unit 408 may include, but is not limited to, a magnetic disk or an optical disk. Communication unit 409 allows electronic device 400 to exchange information / data with other devices via computer networks such as the Internet and / or various telecommunication networks and may include, but is not limited to, a modem, a network card, an infrared communication device, a wireless communication transceiver and / or a chipset, such as a Bluetooth™ device, a WiFi device, a WiMax device, a cellular communication device, and / or the like.

[0083] The computing unit 401 may be a variety of general and / or special processing components with processing and computing capabilities. Some examples of the computing unit 401 include, but are not limited to, a central processing unit (CPU), a graphics processing unit (GPU), various dedicated artificial intelligence (AI) computing chips, various computing units that run machine learning model algorithms, digital signal processors (DSPs), and any appropriate processors, controllers, microcontrollers, etc. The computing unit 401 performs the various methods and processes described above. For example, in some embodiments, the above steps may be implemented as a computer software program that is tangibly included in a machine-readable medium, such as a storage unit 408. In some embodiments, part or all of the computer program may be loaded and / or installed on the electronic device 400 via the ROM 402 and / or the communication unit 409. In some embodiments, the computing unit 401 may be configured to perform the above steps in any other appropriate manner (e.g., by means of firmware).

[0084] The electronic devices of the embodiments of the present application exist in various forms, including but not limited to:

[0085] (1) Mobile communication devices: These devices are characterized by their mobile communication capabilities and are primarily designed to provide voice and data communications. These terminals include smartphones (e.g., iPhones), multimedia phones, feature phones, and low-end phones.

[0086] (2) Ultra-mobile personal computer devices: These devices fall under the category of personal computers, have computing and processing capabilities, and generally also have mobile Internet access. These terminals include PDAs, MIDs, and UMPCs, such as the iPad.

[0087] (3) Portable entertainment devices: These devices can display and play multimedia content. These devices include audio and video players (such as iPods), handheld game consoles, e-books, smart toys, and portable car navigation devices.

[0088] (4) Server: A device that provides computing services. The server consists of a processor 410, a hard disk, memory, a system bus, etc. The server is similar to a general computer architecture, but because it needs to provide highly reliable services, it has higher requirements in terms of processing power, stability, reliability, security, scalability, and manageability.

[0089] (5) Other electronic devices with data interaction functions.

[0090] It should be noted that the various embodiments in this specification are described in a progressive manner, and the same or similar parts between the various embodiments can be referred to each other, and each embodiment focuses on the differences from other embodiments. In particular, for the device and system embodiments, since they are basically similar to the method embodiments, the description is relatively simple, and the relevant parts can be referred to the partial description of the method embodiments. The device and system embodiments described above are merely schematic, wherein the modules described as separate components may or may not be physically separated, and the components indicated as modules may or may not be physical modules, that is, they may be located in one place, or they may be distributed on multiple network modules. Some or all of the modules can be selected according to actual needs to achieve the purpose of the scheme of this embodiment. A person of ordinary skill in the art can understand and implement it without paying any creative work.

[0091] The above is merely one specific embodiment of the present application, but the scope of protection of the present application is not limited thereto. Any changes or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in this application should be included in the scope of protection of the present application. Therefore, the scope of protection of the present application should be based on the scope of protection of the claims.

Claims

1. A cross-chain interoperability method in a consortium chain, characterized in that: include: Obtain a cross-chain interoperation request, parse the cross-chain interoperation request, and determine the initiator ID of the cross-chain interoperation request and the target data pointed to by the cross-chain interoperation request; Performing legitimacy verification to determine the target data pointed to by the request in the consortium chain, transferring the target data pointed to by the request in the consortium chain to a temporarily created storage address, responding to the cross-chain interoperability request, and sending the target data from the storage address to the data demand node corresponding to the initiator ID, wherein the data demand node is located in the external blockchain of the consortium chain, and the external blockchain is mapped to the consortium chain subnet within the consortium chain; Temporarily creating the storage address according to the cross-chain interoperability request legitimacy declarations generated by multiple nodes in the consortium chain for verifying the legitimacy of the cross-chain interoperability request; The cross-chain interoperability request is subjected to a validity verification according to the legitimacy declarations of the cross-chain interoperability request generated by the multiple in-chain nodes, including: each of the multiple in-chain nodes verifies the signature of a non-self-owned legitimacy declaration of the cross-chain interoperability request, and counts the volume of the legitimacy declarations of the cross-chain interoperability request that pass the verification; if a predetermined signature verification threshold indicating that the cross-chain interoperability request is legitimate is reached, it is determined that the cross-chain interoperability request has passed the legitimacy verification.

2. The cross-chain interoperability method in the alliance chain according to claim 1 is characterized in that: The temporarily creating a storage address according to the legitimacy declaration of the cross-chain interoperation request generated by multiple in-chain nodes in the alliance chain for performing legitimacy verification on the cross-chain interoperation request includes: collecting the legitimacy declaration of the cross-chain interoperation request generated by multiple in-chain nodes in the blockchain for performing legitimacy verification on the cross-chain interoperation request; performing legitimacy verification on the cross-chain interoperation request according to the legitimacy declaration of the cross-chain interoperation request generated by the multiple in-chain nodes; and temporarily creating the storage address in response to the cross-chain interoperation request passing the legitimacy verification.

3. The cross-chain interoperability method in the alliance chain according to claim 1 is characterized in that: In response to the cross-chain interoperability request passing the legitimacy verification, temporarily creating the storage address, including: in response to the cross-chain interoperability request passing the legitimacy verification, obtaining the private feature data owned by the multiple nodes in the chain and the public feature data of the alliance chain, so as to temporarily create the storage address based on the private feature data owned by the multiple nodes in the chain and the public feature data of the alliance chain.

4. The cross-chain interoperability method in a consortium chain according to any one of claims 1 to 3, characterized in that: The sending of the target data from the storage address to the data demand node corresponding to the initiator ID includes: obtaining a target data release request to verify the legitimacy of the target data release request; in response to the target data release request passing the legitimacy verification, sending the target data from the storage address to the data demand node corresponding to the initiator ID.

5. The cross-chain interoperability method in the alliance chain according to claim 4 is characterized in that: The obtaining of the target data release request to verify the legitimacy of the target data release request includes: in response to obtaining the target data release request, obtaining the legitimacy declaration of the target data release request generated by the multiple nodes in the chain; and verifying the legitimacy of the target data release request based on the legitimacy declaration of the target data release request generated by the multiple nodes in the chain.

6. The cross-chain interoperability method in the alliance chain according to claim 5 is characterized in that: The target data release request is subjected to the validity verification based on the target data release request legitimacy declaration generated by the multiple chain nodes, including: each of the multiple chain nodes verifies the signature of the target data release request legitimacy declaration that is not its own, and counts the volume of the target data release request legitimacy declaration that has passed the signature verification; if a predetermined signature verification threshold indicating that the target data release request is legitimate is reached, it is determined that the target data release request has passed the validity verification.

7. The cross-chain interoperability method in the alliance chain according to claim 6, characterized in that: The sending of the target data from the storage address to the data demand node corresponding to the initiator ID includes: sending the target data from the storage address to the data demand node corresponding to the initiator ID within a set time lock range; if the target data is not sent from the storage address to the data demand node corresponding to the initiator ID within the set time lock range, destroying the storage address to destroy the target data therein.

8. The cross-chain interoperability method in the alliance chain according to claim 6 is characterized in that: The cross-chain interoperability method in a consortium chain also includes: in response to the target data being successfully sent from the storage address to the data demand node corresponding to the initiator ID, destroying the target data release request legitimacy declaration and the cross-chain interoperation request legitimacy declaration.

Images