Business transaction based on dynamic networking of blockchain, dynamic networking method and device of blockchain

Abstract

The application can be applied to the technical field of the application of blockchain technology in finance, and provides a business transaction method based on dynamic networking of a blockchain, a dynamic networking method of a blockchain and corresponding devices. The business transaction method based on dynamic networking of the blockchain applied to a transaction initiating node comprises the following steps: in response to a transaction request of a user received, a blockchain is established through a plurality of edge nodes and a plurality of cloud nodes; a first block message is generated according to the transaction request and is sent to a plurality of edge verification nodes for intelligent contract first edge consensus; and a second block message sent by the cloud node is received to complete the business transaction. The application dynamically establishes a blockchain network in distributed cloud edge cooperation, and through the way of buffering in a weak network, the establishment of edge verification nodes and the interaction mode between a plurality of nodes, the ability of supporting continuous operation of the business in the weak network is realized, and the problem of business transaction interruption caused by network jitter is solved.

Description

TECHNICAL FIELD

[0001] The present application belongs to the technical field of blockchain, and can be used in the technical field of blockchain applied to the financial industry. Specifically, it relates to a business transaction of a blockchain based on dynamic networking, a dynamic networking method and device of the blockchain. BACKGROUND

[0002] Blockchain is a distributed database technology that provides decentralized and tamper-proof data storage capabilities. It is composed of a series of data blocks arranged in chronological order, each containing a certain number of transaction records. These data blocks are linked to each other using cryptographic methods, and once data is written to the blockchain, it is difficult to change or delete. Here are some key features of blockchain:

[0003] Decentralization: Traditional database systems usually rely on centralized management agencies to maintain and manage data. Blockchain technology, through the form of distributed ledger, allows data records to be stored simultaneously on multiple nodes in the network, eliminating the need for centralized management.

[0004] Tamper resistance: Once a transaction is confirmed and added to the blockchain, it is almost impossible to change or delete. This is because each block contains the hash value of the previous block, creating a chain that extends indefinitely. Any attempt to tamper with information will be detected by other nodes in the network.

[0005] Transparency: In a public blockchain, anyone can view the complete blockchain data and verify transactions. This provides a high level of transparency, helping to increase trust.

[0006] Security: Blockchain uses various encryption technologies to ensure data security. For example, asymmetric encryption allows users to generate public and private keys, securely conducting transactions.

[0007] Smart contracts: On some blockchain platforms, such as Ethereum, smart contracts can be deployed. They are computer programs that automatically execute, control and record contract terms.

[0008] In a cloud-edge-end collaborative blockchain network, the following abnormal situations may occur, leading to business interruption.

[0009] Case 1: Weak network. For edge nodes, if a weak network condition occurs, that is, the network is unstable, and there is a short time of network disconnection and automatic recovery, the following situations may occur: 1. Unable to initiate a networking request. 2. Unable to receive a block message generated by an out-block node. 3. Unable to complete the sending of a consensus request (that is, sending a transaction block message to the edge for consensus). 4. Unable to receive a signature feedback after consensus, resulting in a failed consensus. 5. Unable to submit a block message to the cloud. 6. Unable to receive a signature message from the cloud. 7. Cloud feedback verification failure.

[0010] Case 2: Edge consensus failure. Consensus failure refers to when a transaction node initiates a consensus request to a verification node, and does not receive enough signatures after verification, resulting in a failed consensus. The reasons for not receiving enough signatures are as follows: 1. Weak network causes consensus failure. This case is weak network 3 exception. 2. Explicitly receive feedback of verification node verification failure, resulting in implementation failure due to transaction verification failure. The specific reasons for this case are as follows: 1. Business logic verification code failure; 2. Inconsistent contract version; 3. Verification code is not executed and is forcibly exited.

[0011] Current blockchain networks all rely on good network communication capabilities, and when the above-mentioned multiple abnormal situations occur, the cloud-edge collaborative construction of the blockchain network cannot support continuous business transactions. SUMMARY

[0012] The present application can be used in the technical field of financial application of blockchain technology, and can also be used in any field other than the financial field.

[0013] An object of the present application is to provide a business transaction method based on dynamic networking of a blockchain and a dynamic networking method of a blockchain, both of which can dynamically construct a blockchain network in a distributed cloud-edge collaboration, and through the way of buffering in a weak network, constructing edge verification nodes, and the interaction between multiple nodes (transaction initiation nodes, transaction response nodes, edge verification nodes, and cloud nodes), the ability to support continuous business operation in a weak network is realized, and the problem of business transaction interruption caused by network jitter is solved.

[0014] Another object of the present application is to provide a business transaction device based on dynamic networking of a blockchain and a dynamic networking device of a blockchain. Another object of the present application is to provide an electronic device comprising a memory and a processor, the memory storing a computer program, and the processor implementing the steps of the business transaction method based on dynamic networking of a blockchain and the dynamic networking method of a blockchain when executing the computer program. Another object of the present application is to provide a readable medium storing a computer program, the computer program implementing the steps of the business transaction method based on dynamic networking of a blockchain and the dynamic networking method of a blockchain when executed by a processor.

[0015] To solve the technical problems in the background art, the present application provides the following technical solutions.

[0016] In a first aspect, the present application provides a business transaction method based on dynamic networking of a blockchain (applied to a transaction initiating node), comprising:

[0017] In response to a received transaction request of a user, a blockchain is established through a plurality of edge nodes and a plurality of cloud nodes; wherein the edge nodes comprise at least one transaction initiating node, at least one transaction responding node, and a plurality of edge verification nodes, and the edge nodes are user terminals having a second network different from a first network where the cloud nodes are located;

[0018] A first block message is generated according to the transaction request, and is sent to the plurality of edge verification nodes for intelligent contract first edge consensus;

[0019] A second block message sent by the cloud nodes is received to complete the business transaction; wherein the second block message is generated by the local node, the plurality of edge nodes, the plurality of cloud nodes, and the transaction responding node according to the first block message.

[0020] In some embodiments of the present application, when the first network is in a weak network state, the local node, the plurality of edge nodes, and the transaction responding node save their respective business transaction data to the local node and / or the second network.

[0021] In some embodiments of the present application, generating a first block message according to the transaction request comprises:

[0022] Changing the execution role in the block message template of the blockchain to a transaction initiator;

[0023] Executing a business logic function of an intelligent contract in the block message template;

[0024] Filling in the transaction initiator and transaction responder information in the block message template;

[0025] filling in the contract output in the block message template;

[0026] signing the block message template to generate the first block message.

[0027] In some embodiments of the present application, the second block message sent by the cloud node is received to complete the business transaction; wherein the second block message is generated by the local node, the plurality of edge nodes, the plurality of cloud nodes and the transaction response node according to the first block message, and includes:

[0028] The first block message is verified by the plurality of edge nodes to generate a third block message;

[0029] The third block message sent by the edge node is received and signed to generate a fourth block message;

[0030] The fourth block message is sent to the plurality of cloud nodes for intelligent contract cloud consensus;

[0031] The second block message is received; wherein the second block message is generated by the plurality of cloud nodes according to the fifth block message sent by the transaction response node, and the fifth block message is generated by the transaction response node and a plurality of edge verification nodes according to the sixth block message sent by the cloud node for intelligent contract second edge consensus, and the sixth block message corresponds to the intelligent contract cloud consensus of the plurality of cloud nodes.

[0032] In a second aspect, the present application provides a business transaction method based on dynamic networking of a block chain (applied to at least one edge verification node) including:

[0033] The first block message sent by the transaction initiating node is received through the block chain established by the transaction initiating node; wherein the first block message is generated by the transaction initiating node according to the transaction request of the user;

[0034] The first block message is subjected to intelligent contract first edge consensus to generate a third block message;

[0035] The third block message is sent to the transaction initiating node;

[0036] The seventh block message sent by the transaction response node is received, and the seventh block message is subjected to intelligent contract second edge consensus to generate an eighth block message;

[0037] The eighth block message is sent to the transaction response node, and the transaction response node and a plurality of cloud nodes complete the business transaction according to the eighth block message.

[0038] The blockchain is composed of the local node, the transaction initiation node, the transaction response node, and the plurality of cloud nodes; the edge verification node, the transaction initiation node, and the transaction response node are user terminals having a second network different from a first network in which the cloud nodes are located.

[0039] In some embodiments of the present application, when the first network is in a weak network state, the local node, the transaction initiation node, and the transaction response node save respective business transaction data to the local and / or the second network.

[0040] In some embodiments of the present application, the first block message is subjected to smart contract first edge consensus to generate a third block message, including:

[0041] The execution role of the first block message is changed to an edge consensus party;

[0042] A verification function in the first block message is executed;

[0043] The first block message is signed to generate the third block message.

[0044] In some embodiments of the present application, the seventh block message sent by the transaction response node is received, and the seventh block message is subjected to smart contract second edge consensus to generate an eighth block message, including:

[0045] The execution role of the seventh block message is changed to an edge consensus party;

[0046] A verification function in the seventh block message is executed;

[0047] The seventh block message is signed to generate the eighth block message.

[0048] In a third aspect, the present application provides a business transaction method based on a dynamic networking blockchain (applied to at least one cloud node), including:

[0049] A fourth block message sent by a transaction initiation node is received;

[0050] The fourth block message is verified to generate a sixth block message;

[0051] The sixth block message is distributed in the blockchain;

[0052] A fifth block message sent by a transaction response node is received;

[0053] The fifth block message is verified to generate a ninth block message;

[0054] The sixth block message and the ninth block message are subjected to block processing; wherein the fourth block message contains the results of the first edge-end consensus of the smart contract by the plurality of edge-end verification nodes; and the fifth block message contains the results of the second edge-end consensus of the smart contract by the plurality of edge-end verification nodes.

[0055] The blockchain is composed of local nodes and a plurality of edge-end nodes; wherein the edge-end nodes at least include at least one transaction initiating node, at least one transaction responding node and a plurality of edge-end verification nodes, and the edge-end nodes are user terminals of a second network different from the first network of the cloud nodes.

[0056] In some embodiments of the present application, when the first network is in a weak network state, the edge-end nodes save the business transaction data to the local and / or the second network.

[0057] In some embodiments of the present application, the fourth block message is verified to generate the sixth block message, including:

[0058] The fourth block message is verified according to the signature in the fourth block message;

[0059] When the verification is passed, the message outputs corresponding to the other cloud nodes and the edge-end nodes in the fourth block message are set according to the message content submitted by the transaction initiating node in the fourth block message;

[0060] The fourth block message with the set message output is signed to generate the sixth block message.

[0061] In some embodiments of the present application, the fifth block message is verified to generate the ninth block message, including:

[0062] The fifth block message is verified according to the signature in the fifth block message;

[0063] When the verification is passed, the message outputs corresponding to the other cloud nodes and the edge-end nodes in the fifth block message are set according to the message content submitted by the transaction responding node in the fifth block message;

[0064] The fifth block message with the set message output is signed to generate the ninth block message.

[0065] In a fourth aspect, the present application provides a business transaction method based on a dynamic networking blockchain (applied to a transaction responding node), including:

[0066] The sixth block message sent by the cloud node is received;

[0067] generate a seventh block message according to the sixth block message; and send the seventh block message to the plurality of edge verification nodes for a second edge consensus of the smart contract;

[0068] receive an eighth block message sent by the plurality of edge verification nodes; wherein the eighth block message is generated by the plurality of edge verification nodes according to the second edge consensus of the smart contract based on the seventh block message;

[0069] generate a fifth block message according to the eighth block message, and send the fifth block message to the cloud nodes, and complete a business transaction by the plurality of cloud nodes according to the fifth block message;

[0070] The blockchain is composed of the local node, the plurality of cloud nodes, and the plurality of edge nodes; wherein the edge nodes at least include at least one transaction initiation node and a plurality of edge verification nodes, and the edge nodes are user terminals of a second network different from a first network where the cloud nodes are located.

[0071] In some embodiments of the present application, when the first network is in a weak network state, the local node, the transaction initiation node, and the plurality of edge nodes save respective business transaction data to the local and / or the second network.

[0072] In some embodiments of the present application, generating a seventh block message according to the sixth block message includes:

[0073] changing an execution role of the sixth block message to a transaction response party;

[0074] executing a business logic function of the smart contract in the sixth block message;

[0075] filling in a contract output in the sixth block message;

[0076] signing the sixth block message to generate the seventh block message.

[0077] In some embodiments of the present application, generating a fifth block message according to the eighth block message includes:

[0078] changing an execution role of the eighth block message to a transaction response party;

[0079] executing a verification function in the eighth block message;

[0080] signing the eighth block message to generate the fifth block message.

[0081] In some embodiments of the present application, the blockchain is established by the transaction initiation node in response to a received transaction request of a user; and / or:

[0082] The blockchain is constructed by the transaction response node in response to the received sixth block message.

[0083] In a fifth aspect, the present application provides a dynamic networking method of a blockchain (applied to a transaction initiating node and / or a transaction response node), comprising:

[0084] When applied to the transaction initiating node, the blockchain is constructed by a plurality of edge nodes and a plurality of cloud nodes in response to a received transaction request of a user;

[0085] When applied to the transaction response node, the blockchain is constructed by a plurality of edge nodes and a plurality of cloud nodes in response to a received sixth block message sent by a cloud node; wherein the sixth block message is generated by intelligent contract cloud consensus of the plurality of cloud nodes;

[0086] The edge nodes at least include at least one transaction initiating node, at least one transaction response node, and a plurality of edge verification nodes, and the edge nodes are user terminals having a second network different from a first network where the cloud nodes are located.

[0087] In a sixth aspect, the present application provides a business transaction device of a blockchain based on dynamic networking (applied to a transaction initiating node), comprising:

[0088] A blockchain construction module is configured to construct a blockchain by a plurality of edge nodes and a plurality of cloud nodes in response to a received transaction request of a user; wherein the edge nodes at least include at least one transaction initiating node, at least one transaction response node, and a plurality of edge verification nodes, and the edge nodes are user terminals having a second network different from a first network where the cloud nodes are located;

[0089] A first message generation module is configured to generate a first block message according to the transaction request and send it to the plurality of edge verification nodes for intelligent contract first edge consensus;

[0090] A second message receiving module is configured to receive a second block message sent by a cloud node to complete a business transaction; wherein the second block message is generated by a local node, the plurality of edge nodes, the plurality of cloud nodes, and the transaction response node according to the first block message.

[0091] In some embodiments of the present application, when the first network is in a weak network state, the local node, the plurality of edge nodes, and the transaction response node save respective business transaction data to the local and / or the second network.

[0092] In some embodiments of the present application, the first message generation module comprises:

[0093] The role changing first unit is configured to change an execution role in the block message template of the blockchain to a transaction initiator.

[0094] The logic function execution first unit is configured to execute a business logic function of the smart contract in the block message template.

[0095] The information filling first unit is configured to fill in the transaction initiator and transaction responder information in the block message template.

[0096] The contract output filling first unit is configured to fill in a contract output in the block message template.

[0097] The template signature unit is configured to sign the block message template to generate the first block message.

[0098] In some embodiments of the present application, the second message receiving module comprises:

[0099] The third message generation first unit is configured to verify the first block message by the plurality of edge nodes to generate a third block message.

[0100] The fourth message generation unit is configured to receive the third block message sent by the edge node and sign it to generate a fourth block message.

[0101] The fourth block message is sent to the plurality of cloud nodes for smart contract cloud consensus.

[0102] The second block message receiving unit is configured to receive the second block message, wherein the second block message is generated by the plurality of cloud nodes according to the fifth block message sent by the transaction responder node, and the fifth block message is generated by the transaction responder node and the plurality of edge verification nodes according to the sixth block message sent by the cloud node for smart contract second edge consensus, and the sixth block message corresponds to the smart contract cloud consensus of the plurality of cloud nodes.

[0103] In a seventh aspect, the present application provides a business transaction device based on a dynamic networking blockchain (applied to at least one edge verification node), which comprises:

[0104] The first message receiving module is configured to receive the first block message sent by the transaction initiator node through the blockchain established by the transaction initiator node, wherein the first block message is generated by the transaction initiator node according to the transaction request of the user.

[0105] a third message generation module, configured to perform smart contract first edge consensus on the first block message to generate a third block message;

[0106] a third message sending module, configured to send the third block message to the transaction initiation node;

[0107] a seventh message receiving module, configured to receive a seventh block message sent by a transaction response node, and perform smart contract second edge consensus on the seventh block message to generate an eighth block message;

[0108] an eighth message sending module, configured to send the eighth block message to the transaction response node, and complete a business transaction according to the eighth block message by the transaction response node and the plurality of cloud nodes;

[0109] The blockchain is composed of the local node, the transaction initiation node, the transaction response node and the plurality of cloud nodes; the edge verification node, the transaction initiation node and the transaction response node are user terminals having a second network different from a first network where the cloud nodes are located.

[0110] In some embodiments of the present application, when the first network is in a weak network state, the local node, the transaction initiation node and the transaction response node save respective business transaction data to the local and / or the second network.

[0111] In some embodiments of the present application, the third message generation module comprises:

[0112] a role changing second unit, configured to change an execution role of the first block message to an edge consensus party;

[0113] a verification function execution first unit, configured to execute a verification function in the first block message;

[0114] a third message generation second unit, configured to sign in the first block message to generate the third block message.

[0115] In some embodiments of the present application, the seventh message receiving module comprises:

[0116] a role changing third unit, configured to change an execution role of the seventh block message to an edge consensus party;

[0117] a verification function execution second unit, configured to execute a verification function in the seventh block message;

[0118] an eighth message generation unit, configured to sign in the seventh block message to generate the eighth block message.

[0119] In an eighth aspect, the present application provides a business transaction device based on a dynamic networking blockchain (applied to at least one cloud node), which comprises:

[0120] a fourth message receiving module configured to receive a fourth block message sent by a transaction initiating node;

[0121] a sixth message generating module configured to verify the fourth block message to generate a sixth block message;

[0122] a sixth message distributing module configured to distribute the sixth block message in the blockchain;

[0123] a fifth message receiving module configured to receive a fifth block message sent by a transaction responding node;

[0124] a ninth message generating module configured to verify the fifth block message to generate a ninth block message;

[0125] a message block processing module configured to perform block processing on the sixth block message and the ninth block message; wherein the fourth block message contains the results of the first edge consensus of the smart contract by the plurality of edge verification nodes; and the fifth block message contains the results of the second edge consensus of the smart contract by the plurality of edge verification nodes.

[0126] The blockchain is composed of local nodes and a plurality of edge nodes; wherein the edge nodes at least include at least one transaction initiating node, at least one transaction responding node, and a plurality of edge verification nodes, and the edge nodes are user terminals of a second network different from a first network where the cloud nodes are located.

[0127] In some embodiments of the present application, when the first network is in a weak network state, the edge nodes save the business transaction data to the local and / or the second network.

[0128] In some embodiments of the present application, the sixth message generating module comprises:

[0129] a fourth message verifying unit configured to verify the fourth block message according to the signature in the fourth block message;

[0130] a message output setting first unit configured to, when the verification is passed, set the message outputs of the other cloud nodes and the edge nodes corresponding to the fourth block message according to the message content submitted by the transaction initiating node in the fourth block message;

[0131] a sixth message generating unit configured to sign the fourth block message with the set message output to generate the sixth block message.

[0132] In some embodiments of the present application, the ninth message generation module comprises:

[0133] The fifth message verification unit is configured to verify the fifth block message according to the signature in the fifth block message.

[0134] The message output setting second unit is configured to, when the verification is passed, set the message output of other cloud nodes and edge nodes corresponding to the fifth block message according to the message content submitted by the transaction response node in the transaction in the fifth block message.

[0135] The ninth message generation unit is configured to sign the fifth block message with the set message output to generate the ninth block message.

[0136] In the ninth aspect, the present application provides a business transaction device based on a dynamic networking blockchain (applied to a transaction response node), which comprises:

[0137] The sixth message receiving module is configured to receive the sixth block message sent by a cloud node.

[0138] The seventh message generation module is configured to generate a seventh block message according to the sixth block message and send the seventh block message to a plurality of edge verification nodes to perform a smart contract second edge consensus.

[0139] The eighth message receiving module is configured to receive the eighth block message sent by the plurality of edge verification nodes, wherein the eighth block message is generated by the plurality of edge verification nodes according to the smart contract second edge consensus of the seventh block message.

[0140] The fifth message generation module is configured to generate a fifth block message according to the eighth block message and send the fifth block message to the cloud node, and complete a business transaction by a plurality of cloud nodes according to the fifth block message.

[0141] The blockchain is composed of a local node, a plurality of cloud nodes and a plurality of edge nodes, wherein the edge nodes at least include at least one transaction initiation node and a plurality of edge verification nodes, and the edge nodes are user terminals with a second network different from a first network where the cloud nodes are located.

[0142] In some embodiments of the present application, when the first network is in a weak network state, the local node, the transaction initiation node and the plurality of edge nodes save respective business transaction data to the local and / or the second network.

[0143] In some embodiments of the present application, the seventh message generation module comprises:

[0144] The role changing third unit is configured to change the execution role of the sixth block message to a transaction responder;

[0145] The logic function execution second unit is configured to execute a business logic function of the smart contract in the sixth block message.

[0146] The contract output filling second unit is configured to fill a contract output in the sixth block message.

[0147] The seventh message generation first unit is configured to sign the sixth block message to generate the seventh block message.

[0148] In some embodiments of the present application, the fifth message generation module comprises:

[0149] The role changing fourth unit is configured to change the execution role of the eighth block message to a transaction responder.

[0150] The verification function execution third unit is configured to execute a verification function in the eighth block message.

[0151] The fifth block message generation unit is configured to sign the eighth block message to generate the fifth block message.

[0152] In some embodiments of the present application, the blockchain is established by the transaction initiating node in response to the received transaction request of the user; and / or:

[0153] The blockchain is established by the transaction responding node in response to the received sixth block message.

[0154] In a tenth aspect, the present application provides a dynamic networking device of a blockchain (applied to a transaction initiating node and / or a transaction responding node), which comprises:

[0155] The blockchain establishment first module is configured to, when applied to the transaction initiating node, establish a blockchain through a plurality of edge nodes and a plurality of cloud nodes in response to a received transaction request of a user.

[0156] The blockchain establishment second module is configured to, when applied to the transaction responding node, establish a blockchain through a plurality of edge nodes and a plurality of cloud nodes in response to a received sixth block message sent by the cloud node; wherein the sixth block message is generated by the plurality of cloud nodes through a smart contract cloud consensus.

[0157] The edge nodes at least include at least one transaction initiating node, at least one transaction responding node, and a plurality of edge verification nodes, and the edge nodes are user terminals of a second network different from a first network where the cloud nodes are located.

[0158] In a first aspect, the present application provides a computer program product comprising computer programs / instructions which, when executed by a processor, implement the steps of a business transaction method based on dynamic networking of blockchains and a dynamic networking method of blockchains.

[0159] In a second aspect, the present application provides an electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the steps of a business transaction method based on dynamic networking of blockchains and a dynamic networking method of blockchains when executing the program.

[0160] In a third aspect, the present application provides a computer-readable storage medium having stored thereon a computer program which, when executed by a processor, implements the steps of a business transaction method based on dynamic networking of blockchains and a dynamic networking method of blockchains.

[0161] As can be seen from the above description, the embodiments of the present application provide a business transaction method based on dynamic networking of blockchains, a dynamic networking method of blockchains, and corresponding devices. The business transaction method based on dynamic networking of blockchains (applied to a transaction initiating node) comprises: in response to a received transaction request of a user, establishing a blockchain through a plurality of edge nodes and a plurality of cloud nodes; wherein the edge nodes at least include at least one transaction initiating node, at least one transaction responding node, and a plurality of edge verification nodes, and the edge nodes are user terminals having a second network different from a first network in which the cloud nodes are located; generating a first block message according to the transaction request and sending the first block message to the plurality of edge verification nodes for intelligent contract first edge consensus; and receiving a second block message sent by the cloud nodes to complete the business transaction; wherein the second block message is generated by the local node, the plurality of edge nodes, the plurality of cloud nodes, and the transaction responding node according to the first block message.

[0162] The corresponding dynamic networking method of blockchains (applied to the transaction initiating node and / or the transaction responding node) comprises: when applied to the transaction initiating node, in response to a received transaction request of a user, establishing a blockchain through a plurality of edge nodes and a plurality of cloud nodes; when applied to the transaction responding node, in response to a received sixth block message sent by the cloud nodes, establishing a blockchain through a plurality of edge nodes and a plurality of cloud nodes; wherein the sixth block message is generated by the plurality of cloud nodes through intelligent contract cloud consensus; the edge nodes at least include at least one transaction initiating node, at least one transaction responding node, and a plurality of edge verification nodes, and the edge nodes are user terminals having a second network different from a first network in which the cloud nodes are located.

[0163] The application dynamically constructs a block chain network in a distributed cloud edge cooperation manner, and realizes the ability of supporting continuous operation of a business in a weak network through a cache mode in a weak network, construction of an edge-end verification node, and an interaction mode among multiple nodes (a transaction initiation node, a transaction response node, an edge-end verification node, and a cloud node), thereby solving the problem of business transaction interruption caused by network jitter. BRIEF DESCRIPTION OF DRAWINGS

[0164] In order to more clearly illustrate the technical solutions in the embodiments of the present application or the prior art, the following will briefly introduce the drawings needed to be used in the embodiments or the prior art description. Obviously, the drawings in the following description are some embodiments of the present application, and other drawings can also be obtained by those skilled in the art without any creative effort on the basis of these drawings.

[0165] Figure 1 A flowchart of a business transaction method of a block chain based on dynamic networking (applied to a transaction initiation node) in an embodiment of the present application;

[0166] Figure 2 A flowchart of a business transaction method of a block chain based on dynamic networking (applied to at least one edge-end verification node) in an embodiment of the present application;

[0167] Figure 3 A flowchart of a business transaction method of a block chain based on dynamic networking (applied to at least one cloud node) in an embodiment of the present application;

[0168] Figure 4 A flowchart of a business transaction method of a block chain based on dynamic networking (applied to a transaction response node) in an embodiment of the present application;

[0169] Figure 5 A flowchart of a dynamic networking method of a block chain (applied to a transaction initiation node and / or a transaction response node) in an embodiment of the present application;

[0170] Figure 6 An interaction diagram among nodes of a business transaction method of a block chain based on dynamic networking in an embodiment of the present application;

[0171] Figure 7 A flowchart of step A2 of a business transaction method of a block chain based on dynamic networking (applied to a transaction initiation node) in an embodiment of the present application;

[0172] Figure 8 A flowchart of step A3 of a business transaction method of a block chain based on dynamic networking (applied to a transaction initiation node) in an embodiment of the present application;

[0173] Figure 9 Flowchart of step B2 of a business transaction method based on a dynamic networking blockchain (applied to at least one edge verification node) according to an embodiment of the present application;

[0174] Figure 10 Flowchart of step B4 of a business transaction method based on a dynamic networking blockchain (applied to at least one edge verification node) according to an embodiment of the present application;

[0175] Figure 11 Flowchart of step C2 of a business transaction method based on a dynamic networking blockchain (applied to at least one cloud node) according to an embodiment of the present application;

[0176] Figure 12 Flowchart of step C5 of a business transaction method based on a dynamic networking blockchain (applied to at least one cloud node) according to an embodiment of the present application;

[0177] Figure 13 Flowchart of step D2 of a business transaction method based on a dynamic networking blockchain (applied to a transaction response node) according to an embodiment of the present application;

[0178] Figure 14 Flowchart of step D4 of a business transaction method based on a dynamic networking blockchain (applied to a transaction response node) according to an embodiment of the present application;

[0179] Figure 15 Flowchart of a business transaction method based on a dynamic networking blockchain according to a specific embodiment of the present application;

[0180] Figure 16 Schematic diagram of the composition of each node according to a specific embodiment of the present application;

[0181] Figure 17 Mind map of step S1 according to a specific embodiment of the present application;

[0182] Figure 18 Block diagram of a business transaction device based on a dynamic networking blockchain (applied to a transaction initiation node) according to an embodiment of the present application;

[0183] Figure 19 Block diagram of the first message generation module 20 of a business transaction device based on a dynamic networking blockchain (applied to a transaction initiation node) according to an embodiment of the present application;

[0184] Figure 20Block diagram of the second message receiving module 30 in the business transaction device based on the dynamic networking blockchain (applied to the transaction initiating node) in the embodiment of the present application;

[0185] Figure 21 Block diagram of the business transaction device based on the dynamic networking blockchain (applied to at least one edge verification node) in the embodiment of the present application;

[0186] Figure 22 Block diagram of the third message generating module 50 in the business transaction device based on the dynamic networking blockchain (applied to at least one edge verification node) in the embodiment of the present application;

[0187] Figure 23 Block diagram of the seventh message receiving module 70 in the business transaction device based on the dynamic networking blockchain (applied to at least one edge verification node) in the embodiment of the present application;

[0188] Figure 24 Block diagram of the business transaction device based on the dynamic networking blockchain (applied to at least one cloud node) in the embodiment of the present application;

[0189] Figure 25 Block diagram of the sixth message generating module 11 in the business transaction device based on the dynamic networking blockchain (applied to at least one cloud node) in the embodiment of the present application;

[0190] Figure 26 Block diagram of the ninth message generating module 14 in the business transaction device based on the dynamic networking blockchain (applied to at least one cloud node) in the embodiment of the present application;

[0191] Figure 27 Block diagram of the business transaction device based on the dynamic networking blockchain (applied to the transaction responding node) in the embodiment of the present application;

[0192] Figure 28 Block diagram of the seventh message generating module 17 in the business transaction device based on the dynamic networking blockchain (applied to the transaction responding node) in the embodiment of the present application;

[0193] Figure 29 Block diagram of the fifth message generating module 19 in the business transaction device based on the dynamic networking blockchain (applied to the transaction responding node) in the embodiment of the present application;

[0194] Figure 30 Block diagram of the fifth message generating module 19 in the dynamic networking device of the blockchain (applied to the transaction initiating node and / or the transaction responding node) in the embodiment of the present application;

[0195] Figure 31Structure diagram of an electronic device in an embodiment of the present application. DETAILED DESCRIPTION

[0196] In order to make the objects, technical solutions and advantages of the embodiments of the present application clearer, the technical solutions in the embodiments of the present application will be described clearly and completely below with reference to the drawings in the embodiments of the present application. Obviously, the described embodiments are some but not all of the embodiments of the present application. Based on the embodiments in the present application, all other embodiments obtained by a person of ordinary skill in the art without creative work fall within the protection scope of the present application.

[0197] Those skilled in the art should understand that the embodiments of the present application can be provided as a method, a system or a computer program product. Therefore, the present application can take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Moreover, the present application can take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0198] It should be noted that the terms “include” and “have” and any variations thereof in the specification and claims of the present application and the above drawings are intended to cover non-exclusive inclusion, for example, a process, method, system, product or device containing a series of steps or units does not have to be limited to those steps or units clearly listed, but can include other steps or units not clearly listed or inherent to these processes, methods, products or devices. The embodiments in the present application and the features in the embodiments can be combined with each other without conflict. The present application will be described in detail below with reference to the drawings and in combination with the embodiments.

[0199] The acquisition, storage, use, processing and the like of data in the technical solutions of the present application comply with the relevant provisions of laws and regulations.

[0200] Firstly, the embodiments of the present application provide a specific implementation of a business transaction method (applied to a transaction initiating node) based on a dynamic networking blockchain, as shown in Figure 1 The method specifically includes the following contents:

[0201] Step A1: In response to the received transaction request of the user, a blockchain is established through a plurality of edge nodes and a plurality of cloud nodes; wherein the edge nodes at least include at least one transaction initiating node, at least one transaction responding node and a plurality of edge verification nodes, and the edge nodes are user terminals having a second network different from a first network where the cloud nodes are located;

[0202] Step A2: generating a first block message according to the transaction request, and sending to the plurality of edge verification nodes for smart contract first edge consensus;

[0203] Step A3: receiving the second block message sent by the cloud node to complete the business transaction; wherein the second block message is generated by the local node, the plurality of edge nodes, the plurality of cloud nodes and the transaction response node according to the first block message.

[0204] Next, the embodiment of the application also provides a specific implementation of a business transaction method based on a dynamic networking blockchain (applied to at least one edge verification node), which is shown in Figure 2 , which specifically includes the following contents:

[0205] Step B1: receiving the first block message sent by the transaction initiating node through the blockchain composed of the transaction initiating node; wherein the first block message is generated by the transaction initiating node according to the transaction request of the user;

[0206] Step B2: performing smart contract first edge consensus on the first block message to generate a third block message;

[0207] Step B3: sending the third block message to the transaction initiating node;

[0208] Step B4: receiving the seventh block message sent by the transaction response node, and performing smart contract second edge consensus on the seventh block message to generate an eighth block message;

[0209] Step B5: sending the eighth block message to the transaction response node, and completing the business transaction by the transaction response node and the plurality of cloud nodes according to the eighth block message;

[0210] The blockchain is composed of the local node, the transaction initiating node, the transaction response node and the plurality of cloud nodes; the edge verification node, the transaction initiating node and the transaction response node are user terminals with a second network different from the first network where the cloud node is located.

[0211] Next, the embodiment of the application also provides a specific implementation of a business transaction method based on a dynamic networking blockchain (applied to at least one cloud node), which is shown in Figure 3 , which specifically includes the following contents:

[0212] Step C1: receiving the fourth block message sent by the transaction initiating node;

[0213] Step C2: verifying the fourth block message to generate a sixth block message;

[0214] Step C3: distributing the sixth block message in the blockchain;

[0215] Step C4: receiving the fifth block message sent by the transaction response node;

[0216] Step C5: verifying the fifth block message to generate a ninth block message;

[0217] Step C6: performing block processing on the sixth block message and the ninth block message; wherein the fourth block message contains the results of the first edge consensus of the smart contract by the plurality of edge verification nodes; and the fifth block message contains the results of the second edge consensus of the smart contract by the plurality of edge verification nodes;

[0218] The blockchain is composed of local nodes and a plurality of edge nodes; wherein the edge nodes at least include at least one transaction initiation node, at least one transaction response node, and a plurality of edge verification nodes, and the edge nodes are user terminals having a second network different from the first network where the cloud nodes are located.

[0219] Next, the embodiment of the application also provides a specific implementation of a business transaction method (applied to a transaction response node) based on a dynamic networking blockchain, as shown in Figure 4 The method specifically includes the following contents:

[0220] Step D1: receiving the sixth block message sent by the cloud node;

[0221] Step D2: generating a seventh block message according to the sixth block message; and sending the seventh block message to a plurality of edge verification nodes to perform a second edge consensus of a smart contract;

[0222] Step D3: receiving an eighth block message sent by the plurality of edge verification nodes; wherein the eighth block message is generated by the plurality of edge verification nodes according to the seventh block message to perform the second edge consensus of the smart contract;

[0223] Step D4: generating a fifth block message according to the eighth block message, and sending the fifth block message to the cloud node, and completing a business transaction by a plurality of cloud nodes according to the fifth block message;

[0224] The blockchain is composed of local nodes, a plurality of cloud nodes, and a plurality of edge nodes; wherein the edge nodes at least include at least one transaction initiation node and a plurality of edge verification nodes, and the edge nodes are user terminals having a second network different from the first network where the cloud nodes are located.

[0225] Finally, the embodiment of the present application also provides a specific implementation of a dynamic networking method of a blockchain (applied to a transaction initiating node and / or a transaction responding node), see Figure 5 The method specifically includes the following contents:

[0226] Step E1: when applied to the transaction initiating node, in response to the received transaction request of the user, the blockchain is established through a plurality of edge nodes and a plurality of cloud nodes;

[0227] Step E2: when applied to the transaction responding node, in response to the received sixth block message sent by the cloud node, the blockchain is established through a plurality of edge nodes and a plurality of cloud nodes; wherein the sixth block message is generated by the intelligent contract cloud consensus of the plurality of cloud nodes;

[0228] The edge node at least includes at least one transaction initiating node, at least one transaction responding node and a plurality of edge verification nodes, and the edge node is a user terminal having a second network different from the first network where the cloud node is located.

[0229] From the above description, the embodiment of the present application provides a business transaction method of a blockchain based on dynamic networking and a dynamic networking method of a blockchain. The business transaction method of the blockchain based on dynamic networking (applied to a transaction initiating node) includes: in response to the received transaction request of the user, the blockchain is established through a plurality of edge nodes and a plurality of cloud nodes; wherein the edge node at least includes at least one transaction initiating node, at least one transaction responding node and a plurality of edge verification nodes, and the edge node is a user terminal having a second network different from the first network where the cloud node is located; a first block message is generated according to the transaction request, and is sent to a plurality of edge verification nodes for intelligent contract first edge consensus; a second block message sent by the cloud node is received to complete the business transaction; wherein the second block message is generated by the local node, the plurality of edge nodes, the plurality of cloud nodes and the transaction responding node according to the first block message.

[0230] A dynamic networking method of a blockchain (applied to a transaction initiating node and / or a transaction responding node) includes: when applied to the transaction initiating node, in response to the received transaction request of the user, the blockchain is established through a plurality of edge nodes and a plurality of cloud nodes; when applied to the transaction responding node, in response to the received sixth block message sent by the cloud node, the blockchain is established through a plurality of edge nodes and a plurality of cloud nodes; wherein the sixth block message is generated by the intelligent contract cloud consensus of the plurality of cloud nodes; the edge node at least includes at least one transaction initiating node, at least one transaction responding node and a plurality of edge verification nodes, and the edge node is a user terminal having a second network different from the first network where the cloud node is located.

[0231] The application can dynamically build a blockchain network in a distributed cloud edge collaboration, and through the way of caching in a weak network, building edge-end verification nodes, and the interaction between multiple nodes (transaction initiation nodes, transaction response nodes, edge-end verification nodes, and cloud nodes), it realizes the ability to support continuous operation of business in a weak network, and solves the problem of business transaction interruption caused by network jitter.

[0232] For step A1, the edge-end node is composed of different types of terminals relative to the cloud node. The terminal can be: an android device, an iOS device, a PC device, a web page, a linux virtual machine, an intelligent terminal on a car, etc. Similarly, the cloud node (or cloud agent node) can also be composed of different types of terminals.

[0233] For steps A2 and A3, then, referring to Figure 6 , the business transaction is transmitted in different blockchain network nodes in units of block data. When the blockchain network is normal, the process of the transaction is as shown in Figure 6 , the business transaction has a transaction initiation node, an edge-end verification node, a cloud node, and a transaction response node to cooperatively interact and process the block in the blockchain.

[0234] In addition, the block message is the information transmission or data communication related to the block in the blockchain. In the blockchain network, the block contains a series of transaction records and is propagated to all participating nodes through the network. Preferably, the block message contains the following contents:

[0235] Block header information: including version number, hash value of the previous block, Merkle tree root hash value, timestamp, difficulty target and nonce.

[0236] Transaction list: data of all transactions contained in the block.

[0237] For steps B1 to B5, which are applied to at least one edge-end verification node, specifically, before conducting a business transaction, at least one (preferably 20) can be selected from multiple terminals as an edge-end verification node. And the edge-end verification node performs steps B1 to B5.

[0238] For steps B2 and B4, it can be understood that the first edge consensus and the second edge consensus perform the same content, but the execution subject and the execution order are different. The first edge consensus is performed when the first edge verification consensus is performed (in response to an action of the transaction initiating node), and before the second edge consensus. Correspondingly, the second edge consensus is performed when the second edge verification consensus is performed (in response to an action of the transaction responding node), and after the first edge consensus. When a new block is mined by a miner, it is broadcast as a message to the entire network. After receiving the new block message, the edge verification node performs verification, and the edge consensus (the first edge consensus and the second edge consensus) includes but is not limited to: confirming that the size of the block does not exceed the specified maximum value. Checking whether the hash value in the block header information meets the current difficulty target. Confirming that all transactions are valid and there is no double spending. Executing the verification function. Replacing the execution role, and signing the block message.

[0239] For steps C1 to C6, see Figure 6 which is applied to the traditional cloud node, responsible for tasks such as storing data, verifying transactions, participating in consensus mechanisms, etc. Specifically, it is responsible for cloud transaction verification signature, distribution of transaction block messages, remote transaction verification signature, and block processing, block storage, and block distribution of business transactions.

[0240] For steps D1 to D4, they are executed by the transaction responding node. Specifically, the transaction responding node collects the block message distributed by the cloud node for the transaction responding node to process during the heartbeat synchronization process with the cloud node. The transaction responding node executes the exec function in the smart contract with the identity specified in the block message. Fill in the contract_out information of the corresponding node in trans_parts of the transaction responding node. The transaction responding node changes the role in the App_Data role in the message to the role defined by the transaction responding node. The transaction responding node initiates a networking consensus request. And send the message supplemented by the transaction responding node to the edge verification node.

[0241] For steps E1 and E2, it can be understood that in a weak network, the transaction initiating node and the transaction responding node directly establish a connection. The means of establishing a connection include Bluetooth connection, scanning code communication, or other communication methods for data communication connection. Each participant in the transaction signs the block data formed by the transaction data. The transaction signature of each party is retained in the block, and the block is cached. When the block is recovered, the block data is submitted to each edge verification node and cloud node in the cloud edge network for verification. After verification, the block data is stored in the cloud node and each transaction participating node, thereby finally realizing the cached transaction block data in the weak network, and obtaining the recognition and consensus of the transaction data by the numerous edge verification nodes and cloud nodes in the block chain network.

[0242] In some embodiments of the present application, for steps A1 to A3, when the first network is in a weak network state, the local node, the plurality of edge nodes and the transaction response node save their respective business transaction data to the local and / or the second network.

[0243] In some embodiments of the present application, referring to Figure 7 , step A2 comprises:

[0244] Step A21: change the execution role in the block message template of the blockchain to the transaction initiator;

[0245] The execution role is the execution role of the smart contract, and each node executes the contract logic in a specific role. Each edge script has at least three execution roles: a business role, which varies according to the business. For example: for remittance transactions, there are remittance and receiving roles. A verification role is responsible for executing the verification logic of the verification contract. A cloud role is responsible for verifying the contract and performing block landing processing according to the logic of the contract.

[0246] Step A22: execute the business logic function of the smart contract in the block message template;

[0247] A smart contract is an automatically executed script running on a blockchain network, which is a code composed of a series of defined rules and business logic. When the conditions are met, these scripts will automatically execute the corresponding business logic.

[0248] In a smart contract, a business logic function is a function defined within the contract that can perform a specific task. For example, a smart contract may contain functions such as transfer, balanceOf, etc. These functions can be called by sending a transaction, and the transaction data contains the function name and parameters. A business logic function is a specific function defined in a smart contract that encapsulates some business logic, which is executed when the contract is called

[0249] Step A23: fill in the transaction initiator and transaction response information in the block message template;

[0250] Step A24: fill in the contract output in the block message template;

[0251] Step A25: sign the block message template to generate the first block message.

[0252] In steps A21 to A25, the transaction initiating node executes the business logic function in the smart contract in the role defined in the business parameters of the smart contract delivered to the smart contract execution in the application layer. The transaction initiating node initiates a networking request and sends a block message to each edge verification node. In the block message constructed by the transaction initiating node, the information of each participant of the transaction is specified in the transaction part of the message, and the contract output of the transaction initiating node itself is written, and the contract output of the winning of other transaction participants is left blank. Finally, the transaction initiating node signs the constructed block message data and sends it to each edge verification node.

[0253] In some embodiments of the present application, referring to Figure 8 , step A3 comprises:

[0254] Step A31: verifying the first block message by the plurality of edge nodes to generate a third block message;

[0255] Step A32: receiving the third block message sent by the edge node and signing to generate a fourth block message;

[0256] Step A33: sending the fourth block message to the plurality of cloud nodes for smart contract cloud consensus;

[0257] Step A34: receiving the second block message; wherein the second block message is generated by the plurality of cloud nodes according to the fifth block message sent by the transaction responding node, and the fifth block message is generated by the transaction responding node and a plurality of edge verification nodes according to the sixth block message sent by the cloud node for smart contract second edge consensus, and the sixth block message corresponds to the smart contract cloud consensus of the plurality of cloud nodes.

[0258] It should be explained that the sixth block message is generated by the plurality of cloud nodes for smart contract cloud consensus.

[0259] In some embodiments of the present application, for steps B1 to B5, when the first network is in a weak network state, the local node, the transaction initiating node and the transaction responding node save the respective business transaction data to the local and / or the second network.

[0260] It can be understood that the above-mentioned construction method and data storage method of the blockchain network realize the ability of the weak network supporting the continuous operation of the business of the blockchain network, and solve the technical problem of transaction business interruption caused by network jitter.

[0261] In some embodiments of the present application, referring to Figure 9 , step B2 comprises:

[0262] Step B21: changing the execution role of the first block message to an edge consensus party;

[0263] It should be noted that each node needs to change the execution role to the corresponding party before executing the respective steps, which can prevent the smart contract from being tampered with and ensure the security of business transactions.

[0264] Step B22: executing the verification function in the first block message;

[0265] Step B23: signing in the first block message to generate a third block message.

[0266] In steps B21 to B23, first, the edge verification node receives the block message sent by the transaction initiating node and performs verification. The edge verification node executes the verification function in the smart contract in the verification role. (Modify the role value of App_Data)

[0267] Then, the edge verification node returns the verification signature to the transaction initiating node. The transaction initiating node supplements the signature data of each edge verification node to the structure item corresponding to the edge verification node in the block message. After the transaction initiating node signs the constructed block message data, it is sent to the cloud node.

[0268] In some embodiments of the present application, referring to Figure 10 , step B4 includes:

[0269] Step B41: changing the execution role of the seventh block message to an edge consensus party;

[0270] Step B42: executing the verification function in the seventh block message;

[0271] Step B43: signing in the seventh block message to generate an eighth block message.

[0272] It can be understood that steps B41 to B43 correspond to steps B21 to B23, except that B21 to step B23 are the first edge consensus of the smart contract corresponding to the block message sent by the transaction initiating node, and steps B41 to B43 are the second edge consensus of the smart contract corresponding to the block message sent by the transaction responding node.

[0273] In some embodiments of the present application, for steps C1 to C6, when the first network is in a weak network state, the edge node saves the business transaction data to the local and / or the second network.

[0274] In some embodiments of the present application, referring to Figure 11 , step C2 includes:

[0275] Step C21: verifying the fourth block message according to the signature in the fourth block message;

[0276] Step C22: when the verification is passed, setting the message outputs corresponding to other cloud nodes and edge nodes in the fourth block message according to the message content submitted by the transaction initiating node in the fourth block message;

[0277] Step C23: signing the fourth block message with the set message outputs to generate the sixth block message.

[0278] In steps C21 to C23, the cloud node verifies the signatures in the block message submitted by the transaction initiating node, and then makes a cloud signature. The cloud node returns the signed block message to the transaction initiating node. The cloud node makes a block processing on the block message sent by the transaction initiating node. After receiving the block message with the signature sent by the cloud node, the transaction initiating node updates the local data according to the indication of the message output in the block message. The cloud node distributes the message to the nodes other than the transaction initiating node in the block message. The distribution message of the cloud node sets the message outputs of the nodes other than the transaction initiating node and the distribution target node to NULL based on the message content submitted by the transaction initiating node, and then re-signs and distributes to the nodes other than the transaction initiating node in the business transaction.

[0279] In some embodiments of the present application, referring to Figure 12 , step C5 comprises:

[0280] Step C51: verifying the fifth block message according to the signature in the fifth block message;

[0281] Step C52: when the verification is passed, setting the message outputs corresponding to other cloud nodes and edge nodes in the fifth block message according to the message content submitted by the transaction response node in the fifth block message;

[0282] Step C53: signing the fifth block message with the set message outputs to generate the ninth block message.

[0283] In steps C51 to C53, it can be understood that they correspond to steps C21 to C51, specifically, the cloud node verifies the signatures in the block message submitted by the transaction response node, and then makes a cloud signature. The cloud node returns the signed block message to the transaction response node. The cloud node makes a block processing on the block message of the transaction response node. After receiving the block message with the signature sent by the cloud node, the transaction response node updates the local data according to the contract output indication in the node.

[0284] In some embodiments of the present application, the block processing in step C6 is the process of creating a block and adding it to the block chain. Once a new block is accepted and added to the block chain, it becomes the successor of the previous block and is linked together, forming a growing block chain. Other nodes continue to build blocks on top of the new block, further extending the chain and confirming the validity of the transaction.

[0285] In some embodiments of the present application, for steps D1 to D4, when the first network is in a weak network state, the local node, the transaction initiating node and the plurality of edge nodes save their respective business transaction data to the local and / or the second network.

[0286] In some embodiments of the present application, referring to Figure 13 , step D2 includes:

[0287] Step D21: change the execution role of the sixth block message to a transaction responder;

[0288] Step D22: execute the business logic function of the smart contract in the sixth block message;

[0289] Step D23: fill in the contract output in the sixth block message;

[0290] Step D24: sign the sixth block message to generate the seventh block message.

[0291] In steps D21 to D24, the transaction responder node receives the block message to be processed by the transaction responder node distributed by the cloud node in the process of synchronizing with the cloud heartbeat. The transaction responder node executes the business logic function in the smart contract with the identity specified in the block message. The transaction responder node fills in the contract output information of the corresponding node in the transaction part. The transaction responder node changes the execution role of the smart contract in the message to the role defined by the transaction responder node. The transaction responder node initiates a networking consensus request. The transaction responder node sends the supplemented message to the verification node.

[0292] In some embodiments of the present application, referring to Figure 14 , step D4 includes:

[0293] Step D41: change the execution role of the eighth block message to a transaction responder;

[0294] Step D42: execute the verification function in the eighth block message;

[0295] Step D43: sign the eighth block message to generate the fifth block message.

[0296] In some embodiments of the present application, the blockchain is assembled by the transaction initiating node in response to the received transaction request of the user; and / or:

[0297] The blockchain is assembled by the transaction responding node in response to the received sixth block message.

[0298] It can be understood that the blockchain can be assembled by the transaction initiating node, and when the processing step is to the transaction responding node, the blockchain assembled by the transaction responding node can be continued to be used, or the blockchain can be assembled again by the transaction responding node, or the two blockchains can be used together to execute the subsequent steps.

[0299] In a specific embodiment, the present application also provides a specific embodiment of a business transaction method based on a dynamically networked blockchain, as shown in Figure 15 , which specifically includes the following contents.

[0300] Term explanation:

[0301] Transaction initiating node (such as A node in Figure 16 ): the node initiating the transaction, responsible for initiating the networking and transaction consensus process. Perform the logical business handled by the business role (according to different business definitions) in the business role.

[0302] Edge verification node: verifies the block message generated in the transaction, and is responsible for executing the verification logic part of the smart contract in the verification role.

[0303] Cloud node: responsible for cloud verification and data block processing.

[0304] Transaction responding node (such as B node in Figure 16 ): as a transaction participant, it accepts the block message initiated by the transaction node. And execute the role specified by the transaction initiator, execute the logic business in the smart contract.

[0305] App_Data: business parameters in the smart contract passed to the smart contract execution by the application layer.

[0306] Role: smart contract execution role. Each node executes the contract logic in a specific role. Each edge script has at least three roles: business role, which varies according to different businesses. For example: in the remittance transaction, there are remittance and receiving roles. Verification role, responsible for executing the verification logic of the verification contract. Cloud role: responsible for verifying the contract and executing the block processing according to the contract logic.

[0307] contract_out: is part of the block message, and is the block data change instruction part generated after the business role executes the smart contract.

[0308] Edge-end verification node: a verification node, which executes the verification logic of the smart contract on the transaction message generated by the transaction initiation node in the dynamic networking process.

[0309] S1: dynamically establishing a blockchain.

[0310] Specifically, when applied to the transaction initiation node, the blockchain is established by the plurality of edge-end nodes and the plurality of cloud-end nodes in response to the received transaction request of the user; when applied to the transaction response node, the blockchain is established by the plurality of edge-end nodes and the plurality of cloud-end nodes in response to the received sixth block message sent by the cloud-end node; wherein the sixth block message is generated by the plurality of cloud-end nodes through the smart contract cloud-end consensus; the edge-end nodes include at least one transaction initiation node, at least one transaction response node, and a plurality of edge-end verification nodes, and the edge-end nodes are user terminals having a second network different from the first network in which the cloud-end nodes are located.

[0311] Referring to Figure 17 , based on a distributed network, the computing power and storage capacity of various device nodes are utilized, so that terminal devices with different computing power can serve as consensus nodes and participate in the consensus calculation process of the blockchain network, the computing power and storage capacity of low-power edge-end devices are fully utilized, the blockchain network is dynamically constructed, the contract is executed by the edge-end devices in collaboration, and the consensus process of block data is completed.

[0312] In the cloud-edge collaborative blockchain network environment, edge-end nodes and cloud-end nodes (cloud service nodes) are included. In the process of executing the smart contract of the transaction, the edge-end nodes are responsible for submitting transactions or verifying edge-end transactions initiated by other nodes, and the cloud-end nodes are responsible for cloud-end transaction verification. The edge-end nodes store the data of their own participation in the transaction, and the cloud-end nodes need to store the data of all nodes' transactions. In short, a transaction data must be stored in each node of the participants of the transaction, and also exists in the cloud-end nodes. Preferably, the cloud-end nodes use a consortium chain to store transaction data.

[0313] Next, as shown in Figure 16 , the composition types of the transaction nodes can be composed of different terminal types to form the edge-end nodes or the proxy nodes of the cloud-end. The terminal types can be: android devices, iOS devices, PC devices, web pages, linux virtual machines, etc.

[0314] As shown in Figure 6 , the business transaction is propagated in different network nodes in units of block data. When the blockchain network is normal, the process of the transaction is as shown in Figure 6 , the business transaction is processed by the transaction initiation node, the edge-end verification node, the cloud-end node, and the transaction response node in collaboration to complete the transaction block.

[0315] The basic logic of the bilateral (transaction initiator and transaction responder) consensus is that the transaction initiator completes the edge consensus, sends the consensus message to the cloud, the cloud verifies the signature, distributes the block message to the transaction initiator and the transaction participant, the transaction initiator updates the local user data after receiving the cloud signature block, the transaction participant receives the block distributed by the cloud, processes the data, supplements the block message content, initiates the edge consensus process again, and finally sends the message to the cloud, the cloud signs, and the transaction participant updates the local user data after receiving the cloud signature message. Based on the above content, the following takes A as the transaction initiator and B as the transaction participant, and the specific bilateral consensus steps are as follows:

[0316] S2: A edge consensus.

[0317] The A node executes the exec function (business logic function) in the smart contract in the role defined in App_Data. The A node initiates a networking request and sends a block message to each edge verification node. The A node constructs the block message, specifies the part_item information of each participant in the trans_parts (transaction part) of the transaction, and writes the contract_out output (contract output) of the A node itself. The contract_out of other part_item is left blank. The A node signs the constructed block message data and sends it to each verification node.

[0318] S3: A edge verification consensus.

[0319] The verification node receives the block message sent by the A node and performs verification. The verification node executes the verify function in the smart contract in the verification role. (Modify the role value in App_Data)

[0320] The verification node returns the verification signature to the A node. The A node supplements the signature data of each edge verification node under the verification_nodes structure item of the block message. The A node signs the constructed block message data and sends it to the cloud node.

[0321] S4: Cloud verification and distribution.

[0322] The cloud node verifies each signature in the message submitted by the A node, and then makes a cloud signature. The cloud node returns the signed message to the A node. The cloud node performs block processing on the message of the A node. After receiving the signature node of the cloud, the A node updates the local data according to the contract_out indication in the node.

[0323] S5: B node supplements message information.

[0324] The B node receives the block message to be processed by the B node distributed by the cloud in the process of heartbeat synchronization with the cloud. The B node executes the exec function in the smart contract in the identity specified in the message. The contract_out information of the corresponding node in trans_parts of the B node is filled. The B node changes the role in the App_Data role in the message to the role defined by the B node. The B node initiates a networking consensus request. The B node sends the message supplemented by the B node to the verification node.

[0325] S6: B edge consensus and B edge verification consensus.

[0326] The edge verification node receives the block message issued by the B node, and performs verification. The edge verification node executes the verify function in the smart contract in the verify role. (Modify the role value in App_Data), and the edge verification node returns the verification signature to the B node. The B node supplements the signature data of each edge verification node to the block message under the verification_nodes structure item. After signing the constructed block message data, the B node sends it to the cloud node.

[0327] S7: Cloud verification distribution and edge cloud data synchronization.

[0328] The cloud node verifies each signature in the message submitted by the B node, and then makes a cloud signature. The cloud node returns the signed message to the B node. The cloud node performs block processing on the message of the B node. After receiving the signature node of the cloud, the B node updates the local data according to the contract_out indication in the node.

[0329] The user can use the wide-area block chain function provided by the edge SDK through various terminals. However, at any moment, only one of all the ways allows the user to operate. If a user logs in a terminal, when this client moves from this terminal to other terminals, data synchronization is needed, so that the data between the nodes of each terminal and the cloud nodes is synchronized. When the node synchronizes the block data, if the block has been processed by the user, only the local data file is updated according to the data update instruction in the message in the block. If it has not been processed, according to the role specified, the corresponding business logic is processed, and then the corresponding smart contract processing message is generated, and then the networking verification process is initiated, after the message is verified, the cloud verification signature is submitted, and then the data is updated again.

[0330] In steps S1 to S7, the block data constraint relationship is as follows: the blocks have a constraint relationship, and a new transaction block is based on the data of the historical block. The user's data is organized and stored in a tree structure in the user.dat file. Each data item is correspondingly related to a transaction block, and this corresponding relationship is saved in the link.dat file. Each transaction block information is saved in the block.dat file. When the verification node or the cloud node verifies the transaction, the transaction initiating node must send the historical block information and the link relationship between the data items and the block to the verification node or the cloud for verification. When the cloud signs a block and the initiating transaction terminal receives and stores it, it means that the transaction step of the terminal is completed. The link relationship between the blocks is also saved in the block, that is, each block has a data item indicating that the block is based on the data of a historical block transaction. When the terminal receives the block signed by the cloud, it will update the local data files according to the data update instruction in the block.

[0331] S8: When the weak network condition occurs, the transaction nodes directly establish a connection between them.

[0332] In the weak network condition, the transaction nodes directly establish a connection between them, and the means of establishing the connection include Bluetooth connection, code scanning communication or other communication methods for data communication connection. The transaction participants sign the block data constituted by the transaction data of each other, and the signatures of each party are retained in the block and cached. When the block is recovered, the block data is submitted to the verification nodes in the cloud edge network and the cloud nodes for verification. After verification, the block data is stored in the cloud nodes and each transaction participant node, so as to finally realize the cached transaction block data in the weak network, and obtain the recognition and consensus of the transaction data by the numerous verification nodes and cloud nodes in the block chain network.

[0333] From the above description, the embodiment of the present application provides a business transaction method based on dynamic networking of a blockchain, which constructs a blockchain network in a distributed cloud edge collaboration manner, provides a weak network caching method, realizes the ability of supporting continuous operation of a business in a weak network, and solves the technical problem of business interruption caused by network jitter.

[0334] Based on the same inventive concept, the embodiment of the present application further provides a business transaction device based on dynamic networking of a blockchain, which can be used to implement the method described in the above embodiments, as follows. Since the business transaction device based on dynamic networking of a blockchain solves problems in a similar principle to the business transaction method based on dynamic networking of a blockchain, and the dynamic networking device of a blockchain solves problems in a similar principle to the dynamic networking method of a blockchain, the implementation of the business transaction device based on dynamic networking of a blockchain can be referred to the implementation of the business transaction method based on dynamic networking of a blockchain, and the implementation of the dynamic networking device of a blockchain can be referred to the implementation of the dynamic networking method of a blockchain, and the repeated parts will not be described herein. The term "unit" or "module" used below can be a combination of software and / or hardware that implements a predetermined function. Although the system described in the following embodiments is preferably implemented in software, hardware, or a combination of software and hardware is also possible and contemplated.

[0335] The embodiment of the present application provides a specific implementation of a business transaction device based on dynamic networking of a blockchain, which can implement a business transaction method based on dynamic networking of a blockchain, as follows. Figure 18 The business transaction device based on dynamic networking of a blockchain (applied to a transaction initiation node) specifically includes the following contents.

[0336] The blockchain building module 10 is configured to build a blockchain through a plurality of edge nodes and a plurality of cloud nodes in response to a transaction request of a user received; wherein the edge nodes include at least one transaction initiation node, at least one transaction response node, and a plurality of edge verification nodes, and the edge nodes are user terminals having a second network different from a first network where the cloud nodes are located.

[0337] The first message generation module 20 is configured to generate a first block message according to the transaction request, and send the first block message to the plurality of edge verification nodes for intelligent contract first edge consensus.

[0338] The second message receiving module 30 is configured to receive a second block message sent by the cloud nodes to complete the business transaction; wherein the second block message is generated by the local node, the plurality of edge nodes, the plurality of cloud nodes, and the transaction response node according to the first block message.

[0339] In some embodiments of the present application, when the first network is in a weak network state, the local node, the plurality of edge nodes and the transaction response node save respective business transaction data to the local and / or the second network.

[0340] In some embodiments of the present application, referring to Figure 19 The first message generation module 20 comprises:

[0341] The role changing first unit 201 is configured to change an execution role in the block message template of the blockchain to a transaction initiator.

[0342] The logic function execution first unit 202 is configured to execute a business logic function of a smart contract in the block message template.

[0343] The information filling first unit 203 is configured to fill in the transaction initiator and transaction response party information in the block message template.

[0344] The contract output filling first unit 204 is configured to fill in a contract output in the block message template.

[0345] The template signature unit 205 is configured to sign the block message template to generate the first block message.

[0346] In some embodiments of the present application, referring to Figure 20 The second message receiving module 30 comprises:

[0347] The third message generation first unit 301 is configured to verify the first block message by the plurality of edge nodes to generate a third block message.

[0348] The fourth message generation unit 302 is configured to receive the third block message sent by the edge nodes and sign to generate a fourth block message.

[0349] The fourth message generation sending unit 303 is configured to send the fourth block message to the plurality of cloud nodes for smart contract cloud consensus.

[0350] The second block message receiving unit 304 is configured to receive the second block message, wherein the second block message is generated by the plurality of cloud nodes according to the fifth block message sent by the transaction response node, and the fifth block message is generated by the transaction response node and a plurality of edge verification nodes according to the sixth block message sent by the cloud nodes for smart contract second edge consensus, and the sixth block message corresponds to the smart contract cloud consensus of the plurality of cloud nodes.

[0351] Referring to Figure 21The application provides a business transaction device based on a dynamic networking blockchain (applied to at least one edge verification node), which comprises:

[0352] The first message receiving module 40 is used for receiving the first block message sent by the transaction initiating node through the blockchain formed by the transaction initiating node; wherein the first block message is generated by the transaction initiating node according to the transaction request of a user;

[0353] The third message generating module 50 is used for performing intelligent contract first edge consensus on the first block message to generate a third block message;

[0354] The third message sending module 60 is used for sending the third block message to the transaction initiating node;

[0355] The seventh message receiving module 70 is used for receiving the seventh block message sent by the transaction responding node and performing intelligent contract second edge consensus on the seventh block message to generate an eighth block message;

[0356] The eighth message sending module 80 is used for sending the eighth block message to the transaction responding node, and completing the business transaction according to the eighth block message by the transaction responding node and a plurality of cloud nodes;

[0357] The blockchain is composed of a local node, the transaction initiating node, the transaction responding node and the plurality of cloud nodes; the edge verification node, the transaction initiating node and the transaction responding node are user terminals with a second network different from a first network where the cloud nodes are located.

[0358] In some embodiments of the application, when the first network is in a weak network state, the local node, the transaction initiating node and the transaction responding node save respective business transaction data to the local and / or the second network.

[0359] In some embodiments of the application, referring to Figure 22 The third message generating module 50 comprises:

[0360] The role changing second unit 501 is used for changing the execution role of the first block message to an edge consensus party;

[0361] The verification function executing first unit 502 is used for executing the verification function in the first block message;

[0362] The third message generating second unit 503 is used for signing in the first block message to generate a third block message.

[0363] In some embodiments of the application, referring to Figure 23The seventh message receiving module 70 comprises:

[0364] The third role changing unit 701 is configured to change the execution role of the seventh block message to an edge consensus party.

[0365] The second verification function executing unit 702 is configured to execute a verification function in the seventh block message.

[0366] The eighth message generating unit 703 is configured to sign the seventh block message to generate an eighth block message.

[0367] Referring to Figure 24 The application provides a business transaction device based on a dynamic networking blockchain (applied to at least one cloud node), which comprises:

[0368] The fourth message receiving module 90 is configured to receive a fourth block message sent by a transaction initiating node.

[0369] The sixth message generating module 11 is configured to verify the fourth block message to generate a sixth block message.

[0370] The sixth message distributing module 12 is configured to distribute the sixth block message in the blockchain.

[0371] The fifth message receiving module 13 is configured to receive a fifth block message sent by a transaction responding node.

[0372] The ninth message generating module 14 is configured to verify the fifth block message to generate a ninth block message.

[0373] The message block processing module 15 is configured to perform block processing on the sixth block message and the ninth block message; wherein the fourth block message contains the results of intelligent contract first edge consensus of a plurality of edge verification nodes; the fifth block message contains the results of intelligent contract second edge consensus of the plurality of edge verification nodes.

[0374] The blockchain is composed of local nodes and a plurality of edge nodes; wherein the edge nodes at least include at least one transaction initiating node, at least one transaction responding node and a plurality of edge verification nodes, and the edge nodes are user terminals of a second network different from a first network where the cloud nodes are located.

[0375] In some embodiments of the application, when the first network is in a weak network state, the edge nodes save business transaction data to the local and / or the second network.

[0376] In some embodiments of the application, referring to Figure 25The sixth message generation module 11 comprises:

[0377] The fourth message verification unit 111 is configured to verify the fourth block message according to the signature in the fourth block message.

[0378] The message output setting first unit 112 is configured to, when the verification is passed, set the message outputs corresponding to other cloud nodes and edge nodes in the fourth block message according to the message content submitted by the transaction initiating node in the fourth block message.

[0379] The sixth message generation unit 113 is configured to sign the fourth block message with the set message output to generate the sixth block message.

[0380] In some embodiments of the present application, referring to Figure 26 The ninth message generation module 14 comprises:

[0381] The fifth message verification unit 141 is configured to verify the fifth block message according to the signature in the fifth block message.

[0382] The message output setting second unit 142 is configured to, when the verification is passed, set the message outputs corresponding to other cloud nodes and edge nodes in the fifth block message according to the message content submitted by the transaction response node in the fifth block message.

[0383] The ninth message generation unit 143 is configured to sign the fifth block message with the set message output to generate the ninth block message.

[0384] Referring to Figure 27 The present application provides a business transaction device based on dynamic networking block chain (applied to a transaction response node), which comprises:

[0385] The sixth message receiving module 16 is configured to receive the sixth block message sent by the cloud node.

[0386] The seventh message generation module 17 is configured to generate a seventh block message according to the sixth block message, and send the seventh block message to a plurality of edge verification nodes to perform intelligent contract second edge consensus.

[0387] The eighth message receiving module 18 is configured to receive the eighth block message sent by the plurality of edge verification nodes; wherein the eighth block message is generated by the plurality of edge verification nodes according to the intelligent contract second edge consensus of the seventh block message.

[0388] The fifth message generation module 19 is configured to generate a fifth block message according to the eighth block message, and send the fifth block message to the cloud nodes, and the cloud nodes complete the business transaction according to the fifth block message;

[0389] The blockchain is composed of the local node, the cloud nodes and the edge nodes; wherein the edge nodes at least include the transaction initiation node and the edge verification nodes, and the edge nodes are user terminals of a second network different from the first network of the cloud nodes.

[0390] In some embodiments of the present application, when the first network is in a weak network state, the local node, the transaction initiation node and the edge nodes save the respective business transaction data to the local and / or the second network.

[0391] In some embodiments of the present application, referring to Figure 28 , the seventh message generation module 17 includes:

[0392] The role changing third unit 171 is configured to change the execution role of the sixth block message to a transaction response party;

[0393] The logic function execution second unit 172 is configured to execute the business logic function of the smart contract in the sixth block message;

[0394] The contract output filling second unit 173 is configured to fill the contract output in the sixth block message;

[0395] The seventh message generation first unit 174 is configured to sign the sixth block message to generate the seventh block message.

[0396] In some embodiments of the present application, referring to Figure 29 , the fifth message generation module 19 includes:

[0397] The role changing fourth unit 191 is configured to change the execution role of the eighth block message to a transaction response party;

[0398] The verification function execution third unit 192 is configured to execute the verification function in the eighth block message;

[0399] The fifth block message generation unit 193 is configured to sign the eighth block message to generate the fifth block message.

[0400] In some embodiments of the present application, the blockchain is established by the transaction initiation node in response to the received transaction request of the user; and / or:

[0401] The blockchain is constructed by the transaction response node in response to the received sixth block message.

[0402] Embodiments of the application also provide a specific implementation of a dynamic networking device of a blockchain capable of implementing a dynamic networking method of a blockchain, as described in Figure 30 The dynamic networking device of a blockchain applied to a transaction initiation node and / or a transaction response node specifically includes the following contents:

[0403] The blockchain construction first module 21 is configured to, when applied to the transaction initiation node, construct a blockchain through a plurality of edge nodes and a plurality of cloud nodes in response to a received transaction request of a user.

[0404] The blockchain construction second module 22 is configured to, when applied to the transaction response node, construct a blockchain through a plurality of edge nodes and a plurality of cloud nodes in response to a received sixth block message sent by a cloud node, wherein the sixth block message is generated by intelligent contract cloud consensus of the plurality of cloud nodes.

[0405] The edge nodes at least include at least one transaction initiation node, at least one transaction response node, and a plurality of edge verification nodes, and the edge nodes are user terminals having a second network different from a first network where the cloud nodes are located.

[0406] As can be seen from the above description, the embodiments of the application provide a business transaction device of a blockchain based on dynamic networking and a dynamic networking device of a blockchain. The business transaction device of a blockchain based on dynamic networking (applied to a transaction initiation node) includes a blockchain construction module configured to construct a blockchain through a plurality of edge nodes and a plurality of cloud nodes in response to a received transaction request of a user. The edge nodes at least include at least one transaction initiation node, at least one transaction response node, and a plurality of edge verification nodes, and the edge nodes are user terminals having a second network different from a first network where the cloud nodes are located. A first block message generation module is configured to generate a first block message according to the transaction request and send it to a plurality of edge verification nodes for intelligent contract first edge consensus. A second block message receiving module is configured to receive a second block message sent by a cloud node to complete a business transaction, wherein the second block message is generated by a local node, a plurality of edge nodes, a plurality of cloud nodes, and a transaction response node according to the first block message.

[0407] The application discloses a dynamic networking device of a blockchain (applied to a transaction initiating node and / or a transaction responding node), comprising a blockchain establishing first module, which is used for establishing a blockchain through a plurality of edge nodes and a plurality of cloud nodes in response to a transaction request of a user received when applied to the transaction initiating node; a blockchain establishing second module, which is used for establishing a blockchain through a plurality of edge nodes and a plurality of cloud nodes in response to a sixth block message sent by the cloud node received when applied to the transaction responding node; wherein the sixth block message is generated by intelligent contract cloud consensus of the plurality of cloud nodes; the edge node at least comprises at least one transaction initiating node, at least one transaction responding node and a plurality of edge verification nodes, and the edge node is a user terminal of a second network different from a first network of the cloud node.

[0408] The application dynamically establishes a blockchain network in a distributed cloud edge cooperation mode, and realizes the ability of supporting continuous operation of a business in a weak network through a buffering mode in the weak network, establishment of an edge verification node and interaction among a plurality of nodes (a transaction initiating node, a transaction responding node, an edge verification node and a cloud node), and solves the problem of business transaction interruption caused by network jitter.

[0409] Embodiments of the application also provide a specific implementation of an electronic device capable of realizing the business transaction method of the blockchain based on dynamic networking in the above-mentioned embodiments and all steps of the business transaction method of the blockchain based on dynamic networking, as shown in Figure 31 , the electronic device specifically comprises the following contents:

[0410] a processor 1201, a memory 1202, a communications interface 1203 and a bus 1204;

[0411] The processor 1201, the memory 1202 and the communications interface 1203 are connected to each other through the bus 1204; the communications interface 1203 is used for realizing information transmission between a server-side device, a user-side device and other related devices;

[0412] The processor 1201 is used for calling a computer program in the memory 1202, and the processor realizes the business transaction method of the blockchain based on dynamic networking in the above-mentioned embodiments and all steps of the business transaction method of the blockchain based on dynamic networking when executing the computer program, for example, the processor realizes the following steps when executing the computer program:

[0413] steps A1 to A3; steps B1 to B5; steps C1 to C6; steps D1 to D4 and steps E1 to E2.

[0414] Embodiments of the present application also provide a computer readable storage medium storing computer program, wherein the computer program is executed by a processor to implement the steps of the business transaction method based on the dynamic networking blockchain and the business transaction method based on the dynamic networking blockchain, for example, the steps of:

[0415] Steps A1 to A3; Steps B1 to B5; Steps C1 to C6; Steps D1 to D4; and Steps E1 to E2.

[0416] Each of the embodiments in the specification is described in a progressive manner, and the same or similar parts of each of the embodiments can be referred to each other. Each of the embodiments focuses on the difference from other embodiments. In particular, for the hardware + program type embodiments, since they are basically similar to the method embodiments, the description is relatively simple, and the relevant parts can be referred to the part of the method embodiments.

[0417] The above describes specific embodiments of the specification. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recited in the claims can be executed in an order different than the order in the embodiments and still achieve the desired result. In addition, the processes depicted in the figures do not necessarily require the particular order shown or sequential order to achieve the desired results. In certain implementations, multitasking and parallel processing can be advantageous or possible.

[0418] Although the present application provides method operation steps such as embodiments or flowcharts, more or fewer operation steps can be included based on routine or non-creative labor. The order of steps listed in the embodiments is only one of the many execution orders of the steps, and does not represent the only execution order. When the device or user terminal product is executed in practice, it can be executed in the order shown in the embodiments or in parallel (for example, in the environment of parallel processor or multi-thread processing).

[0419] For ease of description, the above apparatus is described in various modules with functions respectively. Of course, in the implementation of the embodiments of the present specification, the functions of each module can be implemented in the same or more software and / or hardware, or the modules implementing the same function can be implemented by a combination of sub-modules or sub-units, etc. The apparatus embodiment described above is only schematic. For example, the division of the units is only a logical function division, and there can be another division manner in actual implementation. For example, a plurality of units or components can be combined or integrated into another system, or some features can be ignored or not executed. In addition, the coupling or direct coupling or communication connection between the displayed or discussed each other can be indirect coupling or communication connection through some interface, device or unit, which can be electrical, mechanical or other forms.

[0420] Those skilled in the art also know that, in addition to implementing the controller in the form of pure computer readable program code, the controller can also be implemented in the form of logic gates, switches, application specific integrated circuits, programmable logic controllers and embedded microcontrollers, etc. by logically programming the method steps to achieve the same functions. Therefore, such a controller can be considered as a hardware component, and the devices included therein for implementing various functions can also be considered as structures within the hardware component. Alternatively, even the devices for implementing various functions can be considered as both software modules implementing the method and structures within the hardware component.

[0421] In a typical configuration, a computing device includes one or more processors (CPUs), input / output interfaces, network interfaces, and memory.

[0422] The memory can include non-persistent memory in computer readable media, random access memory (RAM), and / or non-volatile memory, such as read-only memory (ROM) or flash memory (flash RAM). The memory is an example of computer readable media.

[0423] Each of the embodiments in the specification is described in a progressive manner, and the same or similar parts between the embodiments can be referred to each other. Each of the embodiments focuses on the difference from other embodiments. In particular, the system embodiments are described simply because they are basically similar to the method embodiments, and the relevant parts can be referred to the description of the method embodiments. In the description of the specification, the description of the terms "one embodiment", "some embodiments", "an example", "a specific example", or "some examples" means that the specific features, structures, materials or characteristics described in connection with the embodiment or example are included in at least one embodiment or example of the embodiments of the specification. The illustrative description of the above terms in the specification does not necessarily refer to the same embodiment or example. Moreover, the specific features, structures, materials or characteristics described can be combined in any suitable manner in any one or more embodiments or examples. In addition, the person skilled in the art can combine and combine the different embodiments or examples described in the specification and the features of the different embodiments or examples without contradiction.

[0424] The above only describes the embodiments of the embodiments of the specification and does not limit the embodiments of the specification. The embodiments of the specification can have various changes and variations for those skilled in the art. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the embodiments of the specification shall be included in the scope of claims of the embodiments of the specification.

Claims

1. A business transaction method based on a dynamically networked blockchain, characterized in that, Applied to transaction initiation nodes, including: In response to a received transaction request from a user, a blockchain is constructed using multiple edge nodes and multiple cloud nodes; wherein, the edge node includes at least one transaction initiating node, at least one transaction responding node, and multiple edge verification nodes, and the edge node is a user terminal having a second network that is different from the first network where the cloud node is located. The first block message is generated based on the transaction request and sent to the multiple edge verification nodes to achieve the first edge consensus of the smart contract. The system receives a second block message sent by the cloud node to complete a business transaction; wherein the second block message is generated by the local node, the plurality of edge nodes, the plurality of cloud nodes, and the transaction response node based on the first block message; The step of receiving the second block message sent by the cloud node to complete the business transaction includes: the multiple edge nodes verifying the first block message to generate a third block message; receiving the third block message sent by the edge node and signing it to generate a fourth block message; sending the fourth block message to the multiple cloud nodes for smart contract cloud consensus; and receiving the second block message; wherein the second block message is generated by the multiple cloud nodes based on the fifth block message sent by the transaction response node, and the fifth block message is generated by the transaction response node and multiple edge verification nodes for smart contract second edge consensus based on the sixth block message sent by the cloud node, and the sixth block message corresponds to the smart contract cloud consensus performed by the multiple cloud nodes.

2. The business transaction method according to claim 1, characterized in that, When the first network is in a weak network state, the local node, multiple edge nodes and transaction response nodes save their respective business transaction data to the local network and / or the second network.

3. The business transaction method according to claim 1, characterized in that, Generate a first block message based on the transaction request, including: Change the execution role in the block message template of the blockchain to the transaction initiator; Execute the business logic function of the smart contract in the block message template; Fill in the transaction initiator and transaction responder information in the block message template; Fill in the contract output in the block message template; The block message template is signed to generate the first block message.

4. A business transaction method based on a dynamically networked blockchain, characterized in that, Applied to at least one edge verification node, including: The system receives the first block message sent by the transaction initiating node through a blockchain formed by the transaction initiating node; wherein the first block message is generated by the transaction initiating node based on the user's transaction request; The first block message is used to achieve consensus on the first edge of the smart contract to generate the third block message; The third block message is sent to the transaction initiating node; the transaction initiating node is used to: receive the third block message sent by the edge node, sign it to generate a fourth block message; and send the fourth block message to multiple cloud nodes for smart contract cloud consensus. The system receives the seventh block message sent by the transaction response node and performs smart contract second-side consensus on the seventh block message to generate the eighth block message. The seventh block message is generated by the transaction response node based on the sixth block message sent by the cloud node. The sixth block message corresponds to the smart contract cloud consensus performed by the multiple cloud nodes. The eighth block message is sent to the transaction response node, and the transaction response node and multiple cloud nodes complete the business transaction based on the eighth block message. The transaction response node is configured to: generate a fifth block message based on the eighth block message, and send the fifth block message to the cloud node; the cloud node is configured to: generate a second block message based on the fifth block message, and send it to the transaction initiating node; the transaction initiating node is configured to: receive the second block message sent by the cloud node to complete the business transaction. The blockchain consists of local nodes, transaction initiating nodes, transaction responding nodes, and multiple cloud nodes; the edge verification nodes, transaction initiating nodes, and transaction responding nodes are user terminals of a second network that is different from the first network in which the cloud nodes are located.

5. The business transaction method according to claim 4, characterized in that, When the first network is in a weak network state, the local node, the transaction initiating node and the transaction responding node save their respective business transaction data to the local network and / or the second network.

6. The business transaction method according to claim 4, characterized in that, The first block message is used to achieve consensus on the first edge of the smart contract to generate the third block message, including: Change the execution role of the first block message to the edge consensus party; Execute the verification function in the first block message; Sign the first block message to generate the third block message.

7. The business transaction method according to any one of claims 4 to 6, characterized in that, The process of receiving the seventh block message sent by the transaction response node and performing smart contract second-side consensus on the seventh block message to generate the eighth block message includes: Change the execution role of the seventh block message to the edge consensus party; Execute the verification function in the seventh block message; Sign the seventh block message to generate the eighth block message.

8. A business transaction method based on a dynamically networked blockchain, characterized in that, Applied to at least one cloud node, including: The system receives a fourth block message sent by a transaction initiating node. The transaction initiating node is configured to: respond to a received user transaction request by constructing a blockchain using multiple edge nodes and multiple cloud nodes; generate a first block message based on the transaction request and send it to multiple edge verification nodes for first edge consensus on the smart contract; have the multiple edge nodes verify the first block message to generate a third block message; receive the third block message sent by the edge nodes and sign it to generate a fourth block message; and send the fourth block message to the multiple cloud nodes for cloud consensus on the smart contract. The fourth block message is verified to generate the sixth block message; Distribute the sixth block message in the blockchain; Receive the fifth block message sent by the transaction response node; The fifth block message is verified to generate the ninth block message; The sixth block message and the ninth block message are processed for block creation; wherein, the fourth block message contains the result of the first edge consensus of the smart contract by multiple edge verification nodes; the fifth block message contains the result of the second edge consensus of the smart contract by the multiple edge verification nodes. Based on the fifth block message, a second block message is generated and sent to the transaction initiating node; the transaction initiating node is used to: receive the second block message sent by the cloud node to complete the business transaction; The fifth block message is generated by the transaction response node and multiple edge verification nodes through the second edge consensus of the smart contract based on the sixth block message sent by the cloud node. The sixth block message corresponds to the cloud consensus of the smart contract performed by the multiple cloud nodes. The blockchain consists of local nodes and multiple edge nodes; wherein, each edge node includes at least one transaction initiating node, at least one transaction responding node, and multiple edge verification nodes, and the edge node is a user terminal having a second network that is different from the first network where the cloud node is located.

9. The business transaction method according to claim 8, characterized in that, When the first network is in a weak network state, the edge node saves the business transaction data to the local network and / or the second network.

10. The business transaction method according to claim 8, characterized in that, Verifying the fourth block message to generate the sixth block message includes: The fourth block message is verified based on the signature in the fourth block message; When the verification is successful, the message output corresponding to other cloud nodes and edge nodes in the fourth block message is set according to the message content submitted by the transaction initiating node in the fourth block message. The fourth block message output by the setting message is signed to generate the sixth block message.

11. The business transaction method according to any one of claims 8 to 10, characterized in that, Verifying the fifth block message to generate the ninth block message includes: The fifth block message is verified based on the signature in the fifth block message; When the verification is successful, the message output corresponding to other cloud nodes and edge nodes in the fifth block message is set according to the message content submitted by the transaction response node in the fifth block message. The fifth block message output by the setting message is signed to generate the ninth block message.

12. A business transaction method based on a dynamically networked blockchain, characterized in that, Applied to transaction response nodes, including: The system receives a sixth block message sent by a cloud node; the cloud node is configured to: receive a fourth block message sent by a transaction initiating node; verify the fourth block message to generate a sixth block message; and distribute the sixth block message in the blockchain; the transaction initiating node is configured to: respond to a received user transaction request, construct a blockchain through multiple edge nodes and multiple cloud nodes; generate a first block message according to the transaction request, and send it to multiple edge verification nodes for smart contract first edge consensus; have the multiple edge nodes verify the first block message to generate a third block message; receive the third block message sent by the edge node, sign it to generate a fourth block message; and send the fourth block message to the multiple cloud nodes for smart contract cloud consensus. A seventh block message is generated based on the sixth block message; and the seventh block message is sent to multiple edge verification nodes to conduct second-side consensus of the smart contract. Receive the eighth block message sent by the plurality of edge verification nodes; wherein the eighth block message is generated by the plurality of edge verification nodes through the second edge consensus of the smart contract based on the seventh block message; A fifth block message is generated based on the eighth block message, and the fifth block message is sent to the cloud node. Multiple cloud nodes complete business transactions based on the fifth block message. The cloud node is used to: generate a second block message based on the fifth block message and send it to the transaction initiating node. The transaction initiating node is used to: receive the second block message sent by the cloud node to complete the business transaction. The blockchain consists of local nodes, multiple cloud nodes, and multiple edge nodes; wherein, the edge nodes include at least one transaction initiating node and multiple edge verification nodes, and the edge nodes are user terminals of a second network that is different from the first network in which the cloud nodes are located.

13. The business transaction method according to claim 12, characterized in that, When the first network is in a weak network state, the local node, the transaction initiating node, and the multiple edge nodes save their respective business transaction data to the local network and / or the second network.

14. The business transaction method according to claim 12, characterized in that, Generate a seventh block message based on the sixth block message, including: Change the execution role of the sixth block message to the transaction responder; Execute the business logic function of the smart contract in the sixth block message; Fill in the contract output in the sixth block message; The sixth block message is signed to generate the seventh block message.

15. The business transaction method according to claim 12, characterized in that, The fifth block message is generated based on the eighth block message, including: Change the execution role of the eighth block message to the transaction responder; Execute the verification function in the eighth block message; Sign the eighth block message to generate the fifth block message.

16. The business transaction method according to any one of claims 12 to 15, characterized in that, The blockchain is constructed by the transaction initiating node in response to received user transaction requests; and / or: The blockchain is constructed by the transaction response node in response to the received sixth block message.

17. A dynamic networking method for blockchain, characterized in that, Applied to transaction initiation nodes and / or transaction response nodes, including: When applied to the transaction initiation node, in response to the received user transaction request, a blockchain is constructed through multiple edge nodes and multiple cloud nodes; When applied to the transaction response node, in response to the received sixth block message sent by the cloud node, a blockchain is constructed through multiple edge nodes and multiple cloud nodes; wherein, the sixth block message is generated by the multiple cloud nodes through smart contract cloud consensus; The edge node includes at least one transaction initiating node, at least one transaction responding node, and multiple edge verification nodes, and the edge node is a user terminal with a second network that is different from the first network where the cloud node is located. The transaction initiating node is configured to: generate a first block message according to the transaction request and send it to the plurality of edge verification nodes for smart contract first edge consensus; receive a second block message sent by the cloud node to complete the business transaction; wherein, the second block message is generated by the local node, the plurality of edge nodes, the plurality of cloud nodes, and the transaction response node based on the first block message; the step of receiving the second block message sent by the cloud node to complete the business transaction includes: the plurality of edge nodes verifying the first block message to generate a third block message; receiving the second block message sent by the cloud node to complete the business transaction. The edge node sends a third block message and signs it to generate a fourth block message; the fourth block message is sent to the multiple cloud nodes for smart contract cloud consensus; the second block message is received; wherein the second block message is generated by the multiple cloud nodes based on the fifth block message sent by the transaction response node, and the fifth block message is generated by the transaction response node and multiple edge verification nodes based on the sixth block message sent by the cloud nodes for smart contract second edge consensus, and the sixth block message corresponds to the smart contract cloud consensus performed by the multiple cloud nodes.

18. A business transaction device based on a dynamically networked blockchain, characterized in that, Applied to transaction initiation nodes, including: A blockchain construction module is used to construct a blockchain through multiple edge nodes and multiple cloud nodes in response to a received user transaction request; wherein, the edge node includes at least one transaction initiating node, at least one transaction responding node, and multiple edge verification nodes, and the edge node is a user terminal having a second network different from the first network where the cloud node is located. The first message generation module is used to generate a first block message according to the transaction request and send it to the multiple edge verification nodes to achieve the first edge consensus of the smart contract. The second message receiving module is used to receive the second block message sent by the cloud node to complete the business transaction; wherein, the second block message is generated by the local node, the plurality of edge nodes, the plurality of cloud nodes and the transaction response node based on the first block message; The second message receiving module is configured to: verify the first block message by the plurality of edge nodes to generate a third block message; receive the third block message sent by the edge nodes and sign it to generate a fourth block message; send the fourth block message to the plurality of cloud nodes for smart contract cloud consensus; and receive the second block message; wherein the second block message is generated by the plurality of cloud nodes based on the fifth block message sent by the transaction response node, and the fifth block message is generated by the transaction response node and the plurality of edge verification nodes based on the sixth block message sent by the cloud nodes for smart contract second edge consensus, and the sixth block message corresponds to the smart contract cloud consensus performed by the plurality of cloud nodes.

19. A business transaction device based on a dynamically networked blockchain, characterized in that, Applied to at least one edge verification node, including: The first message receiving module is used to receive the first block message sent by the transaction initiating node through the blockchain formed by the transaction initiating node; wherein the first block message is generated by the transaction initiating node according to the user's transaction request; The third message generation module is used to perform smart contract first-side consensus on the first block message to generate the third block message; The third message sending module is used to send the third block message to the transaction initiating node; the transaction initiating node is used to: receive the third block message sent by the edge node, sign it to generate the fourth block message; and send the fourth block message to multiple cloud nodes for smart contract cloud consensus. The seventh message receiving module is used to receive the seventh block message sent by the transaction response node, and to perform smart contract second-side consensus on the seventh block message to generate the eighth block message; the seventh block message is generated by the transaction response node based on the sixth block message sent by the cloud node; the sixth block message corresponds to the smart contract cloud consensus performed by the multiple cloud nodes; The eighth message sending module is used to send the eighth block message to the transaction response node, and the transaction response node and multiple cloud nodes complete the business transaction based on the eighth block message; the transaction response node is used to: generate a fifth block message based on the eighth block message, and send the fifth block message to the cloud node; the cloud node is used to: generate a second block message based on the fifth block message, and send it to the transaction initiating node; the transaction initiating node is used to: receive the second block message sent by the cloud node to complete the business transaction; The blockchain consists of local nodes, transaction initiating nodes, transaction responding nodes, and multiple cloud nodes; the edge verification nodes, transaction initiating nodes, and transaction responding nodes are user terminals of a second network that is different from the first network in which the cloud nodes are located.

20. A business transaction device based on a blockchain with dynamic networking, characterized in that, Applied to at least one cloud node, including: The fourth message receiving module is used to receive the fourth block message sent by the transaction initiating node. The transaction initiating node is used to: respond to the received user transaction request, construct a blockchain through multiple edge nodes and multiple cloud nodes; generate a first block message according to the transaction request, and send it to multiple edge verification nodes for first edge consensus of the smart contract; have the multiple edge nodes verify the first block message to generate a third block message; receive the third block message sent by the edge nodes, sign it to generate a fourth block message; and send the fourth block message to the multiple cloud nodes for cloud consensus of the smart contract. The sixth message generation module is used to verify the fourth block message in order to generate the sixth block message; The sixth message distribution module is used to distribute the sixth block message in the blockchain; The fifth message receiving module is used to receive the fifth block message sent by the transaction response node; The ninth message generation module is used to verify the fifth block message to generate a ninth block message; based on the fifth block message, it generates a second block message and sends it to the transaction initiating node; the transaction initiating node is used to: receive the second block message sent by the cloud node to complete the business transaction; the fifth block message is generated by the transaction response node and multiple edge verification nodes through smart contract second edge consensus based on the sixth block message sent by the cloud node, and the sixth block message corresponds to the smart contract cloud consensus performed by the multiple cloud nodes; The message block processing module is used to process the sixth block message and the ninth block message; wherein, the fourth block message contains the result of the first edge consensus of the smart contract by multiple edge verification nodes; the fifth block message contains the result of the second edge consensus of the smart contract by the multiple edge verification nodes. The blockchain consists of local nodes and multiple edge nodes; wherein, each edge node includes at least one transaction initiating node, at least one transaction responding node, and multiple edge verification nodes, and the edge node is a user terminal having a second network that is different from the first network where the cloud node is located.

21. A business transaction device based on a dynamically networked blockchain, characterized in that, Applied to transaction response nodes, including: The sixth message receiving module is used to receive the sixth block message sent by the cloud node; the cloud node is used to: receive the fourth block message sent by the transaction initiating node; verify the fourth block message to generate the sixth block message; and distribute the sixth block message in the blockchain; the transaction initiating node is used to: respond to a received user transaction request, construct a blockchain through multiple edge nodes and multiple cloud nodes; generate a first block message according to the transaction request, and send it to multiple edge verification nodes for smart contract first edge consensus; have the multiple edge nodes verify the first block message to generate a third block message; receive the third block message sent by the edge node, sign it to generate a fourth block message; and send the fourth block message to the multiple cloud nodes for smart contract cloud consensus; The seventh message generation module is used to generate a seventh block message based on the sixth block message; and send the seventh block message to multiple edge verification nodes to conduct second edge consensus of the smart contract; The eighth message receiving module is used to receive the eighth block message sent by the plurality of edge verification nodes; wherein the eighth block message is generated by the plurality of edge verification nodes through the second edge consensus of the smart contract based on the seventh block message; The fifth message generation module is used to generate a fifth block message based on the eighth block message, and send the fifth block message to the cloud node, whereby multiple cloud nodes complete business transactions based on the fifth block message; the cloud node is used to: generate a second block message based on the fifth block message and send it to the transaction initiating node; the transaction initiating node is used to: receive the second block message sent by the cloud node to complete the business transaction; The blockchain consists of local nodes, multiple cloud nodes, and multiple edge nodes; wherein, the edge nodes include at least one transaction initiating node and multiple edge verification nodes, and the edge nodes are user terminals of a second network that is different from the first network in which the cloud nodes are located.

22. A dynamic networking device for blockchain, characterized in that, Applied to transaction initiation nodes and / or transaction response nodes, including: The first blockchain module is used to construct a blockchain through multiple edge nodes and multiple cloud nodes in response to a received user transaction request when applied to the transaction initiation node. The second blockchain module is used to construct a blockchain through multiple edge nodes and multiple cloud nodes in response to the sixth block message received by the cloud node when applied to the transaction response node; wherein the sixth block message is generated by the multiple cloud nodes through smart contract cloud consensus. The edge node includes at least one transaction initiating node, at least one transaction responding node, and multiple edge verification nodes, and the edge node is a user terminal with a second network that is different from the first network where the cloud node is located. The transaction initiating node is configured to: generate a first block message according to the transaction request and send it to the plurality of edge verification nodes for smart contract first edge consensus; receive a second block message sent by the cloud node to complete the business transaction; wherein, the second block message is generated by the local node, the plurality of edge nodes, the plurality of cloud nodes, and the transaction response node based on the first block message; the step of receiving the second block message sent by the cloud node to complete the business transaction includes: the plurality of edge nodes verifying the first block message to generate a third block message; receiving the second block message sent by the cloud node to complete the business transaction. The edge node sends a third block message and signs it to generate a fourth block message; the fourth block message is sent to the multiple cloud nodes for smart contract cloud consensus; the second block message is received; wherein the second block message is generated by the multiple cloud nodes based on the fifth block message sent by the transaction response node, and the fifth block message is generated by the transaction response node and multiple edge verification nodes based on the sixth block message sent by the cloud nodes for smart contract second edge consensus, and the sixth block message corresponds to the smart contract cloud consensus performed by the multiple cloud nodes.

23. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, When the processor executes the program, it implements the steps of any one of claims 1 to 17: the business transaction method based on dynamic networking of blockchain and the dynamic networking method of blockchain.

24. A computer-readable storage medium having a computer program stored thereon, characterized in that, When executed by a processor, the computer program implements the steps of the business transaction method based on dynamic networking blockchain and the dynamic networking method of blockchain according to any one of claims 1 to 17.

Images