CN112019599A - Method and device for synchronizing processing messages during block chain consensus processing - Google Patents
Method and device for synchronizing processing messages during block chain consensus processing Download PDFInfo
- Publication number
- CN112019599A CN112019599A CN202010779693.4A CN202010779693A CN112019599A CN 112019599 A CN112019599 A CN 112019599A CN 202010779693 A CN202010779693 A CN 202010779693A CN 112019599 A CN112019599 A CN 112019599A
- Authority
- CN
- China
- Prior art keywords
- message
- retransmission request
- processing
- node
- blockchain
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000012545 processing Methods 0.000 title claims abstract description 235
- 238000000034 method Methods 0.000 title claims abstract description 203
- 230000008569 process Effects 0.000 claims abstract description 151
- 230000004044 response Effects 0.000 claims abstract description 32
- 230000005540 biological transmission Effects 0.000 claims description 17
- 238000011084 recovery Methods 0.000 claims description 16
- 238000012790 confirmation Methods 0.000 claims description 13
- 238000010586 diagram Methods 0.000 description 21
- 239000012634 fragment Substances 0.000 description 12
- 230000008859 change Effects 0.000 description 8
- 230000006870 function Effects 0.000 description 8
- 238000004891 communication Methods 0.000 description 7
- 230000000977 initiatory effect Effects 0.000 description 4
- 238000012795 verification Methods 0.000 description 4
- 238000012986 modification Methods 0.000 description 3
- 230000004048 modification Effects 0.000 description 3
- 238000005516 engineering process Methods 0.000 description 2
- 238000005192 partition Methods 0.000 description 2
- 230000001360 synchronised effect Effects 0.000 description 2
- 206010000117 Abnormal behaviour Diseases 0.000 description 1
- 238000004590 computer program Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000000750 progressive effect Effects 0.000 description 1
- 230000001681 protective effect Effects 0.000 description 1
- 230000001960 triggered effect Effects 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
- H04L67/1095—Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L1/00—Arrangements for detecting or preventing errors in the information received
- H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
- H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
- H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
- H04L1/1829—Arrangements specially adapted for the receiver end
- H04L1/1848—Time-out mechanisms
Abstract
The disclosure relates to a method and apparatus for processing message synchronization in block chain consensus processing. The message processing synchronization method comprises the following steps: if there is a process message missing at the expiration of a given period, sending a process message retransmission request to a target blockchain node in the blockchain network, the process message being a process message received from the other blockchain nodes at the current process for the data block to be consensus, the process message retransmission request including the data block to be consensus identification; and receiving a process message retransmitted in response to the process message retransmission request from a target blockchain node in the blockchain network.
Description
This patent application is application number: 202010181621.X, filing date: the patent application filed on 16.3.2020 of China entitled "method and apparatus for processing message synchronization during block chain consensus processing".
Technical Field
The present disclosure relates to a blockchain technology, and in particular, to a method and an apparatus for processing message synchronization in blockchain consensus processing.
Background
In order to prevent the node from doing malicious actions, the PBFT-based consensus algorithm needs to receive no less than a preset number of normal processing messages in some consensus processing stages to complete the processing in the consensus processing stages. Therefore, for such consensus algorithm, during the consensus process, it needs to be ensured that each node can successfully receive the processed message sent by other nodes, and the sequence of the processed message needs to be ensured.
Disclosure of Invention
In view of the foregoing, the present disclosure provides a method and apparatus for processing message synchronization in a blockchain consensus process. By using the method and the device, when each block chain link does not receive the processing message sent by other block chain nodes, the processing message retransmission request is sent to other block chain nodes, and when other block chain nodes receive the processing message retransmission request, the corresponding processing message sent before the other block chain nodes resend the corresponding processing message, so that the block chain link nodes with the missing processing message can smoothly receive the processing message.
According to one aspect of the present disclosure, a method for processing message synchronization in a blockchain consensus process is provided. The method includes a first node in a blockchain sending a process message retransmission request to a target blockchain node in the blockchain network if it is determined that there is a process message missing at the expiration of a given period and a current stage of processing for a data block to be identified cannot be completed. Wherein the processing message is a processing message received from other blockchain nodes at a current processing stage for the data block to be consensus. The processing message retransmission request comprises the identification of the data block to be identified. And the first node receives a process message retransmitted in response to the process message retransmission request from a target blockchain node in the blockchain network.
According to another aspect of the present disclosure, there is also provided a method for processing message synchronization in block chain consensus processing. The method is performed by a retransmission request receiving node in a blockchain network. The method includes receiving a process message retransmission request from a retransmission request transmitting node in a block chain network, the process message retransmission request including an identification of a data block to be identified. And sending a processing message corresponding to the processing message retransmission request to a target blockchain node in the blockchain network; wherein the processing message retransmission request is transmitted in a case where the retransmission request transmitting node has a processing message missing and cannot complete a current processing stage for a data block to be identified when a given period expires.
According to another aspect of the present disclosure, there is also provided an apparatus for processing message synchronization in block chain consensus processing. The apparatus is applied to a retransmission request transmitting node. The apparatus includes a message retransmission request transmitting unit configured to transmit a process message retransmission request to a target blockchain node in the blockchain network if there is a process message missing and a current processing stage for a data block to be identified cannot be completed at the expiration of a given period. Wherein the processing message is a processing message received from other blockchain nodes at a current processing stage for the data block to be consensus. The processing message retransmission request comprises the identification of the data block to be identified. The apparatus also includes a process message receiving unit configured to receive a process message retransmitted in response to the process message retransmission request from a target blockchain node in the blockchain network.
According to another aspect of the present disclosure, there is also provided an apparatus for processing message synchronization in block chain consensus processing. The apparatus is applied to a retransmission request receiving node. The apparatus includes a message retransmission request receiving unit configured to receive a processed message retransmission request from a retransmission request transmitting node in a block chain network. The processing message retransmission request comprises the identification of the data block to be identified. The apparatus further includes a message transmitting unit configured to transmit a processed message corresponding to the processed message retransmission request to a target blockchain node in the blockchain network. Wherein the processing message retransmission request is transmitted in a case where the retransmission request transmitting node has a processing message missing and cannot complete a current processing stage for a data block to be identified when a given period expires.
According to another aspect of the present disclosure, there is also provided a block link point apparatus comprising a device as described in the third aspect above; and an apparatus as described in the fourth aspect above.
According to another aspect of the present disclosure, there is also provided a computing device comprising at least one processor. The apparatus also includes a memory, wherein the memory stores instructions. The instructions, when executed by the at least one processor, cause the at least one processor to send a process message retransmission request to a target blockchain node in the blockchain network if it is determined that there is a process message missing at the expiration of a given period and the current stage of processing for the data block to be consensus cannot be completed. Wherein the processing message is a processing message received from other blockchain nodes at a current processing stage for the data block to be identified; the processing message retransmission request comprises the identification of the data block to be identified. And receiving a process message retransmitted in response to the process message retransmission request from a target blockchain node in the blockchain network.
According to another aspect of the present disclosure, there is also provided a machine-readable storage medium having stored thereon executable instructions. The instructions, when executed, cause the machine to send a process message retransmission request to a target blockchain node in the blockchain network if it is determined that there is a process message missing at the expiration of a given period and the current stage of processing for the data block to be consensus cannot be completed. Wherein the processing message is a processing message received from other blockchain nodes at a current processing stage for the data block to be consensus. The processing message retransmission request comprises the identification of the data block to be identified. And receiving a process message retransmitted in response to the process message retransmission request from a target blockchain node in the blockchain network.
According to another aspect of the present disclosure, there is also provided a computing device comprising at least one processor. The apparatus also includes a memory, wherein the memory stores instructions. The instructions, when executed by the at least one processor, cause the at least one processor to receive a process message retransmission request from a retransmission request transmitting node in a block chain network. The processing message retransmission request comprises the identification of the data block to be identified. And sending a processing message corresponding to the processing message retransmission request to a target blockchain node in the blockchain network. Wherein the processing message retransmission request is transmitted in a case where the retransmission request transmitting node has a processing message missing and cannot complete a current processing stage for a data block to be identified when a given period expires.
According to another aspect of the present disclosure, there is also provided a machine-readable storage medium having stored thereon executable instructions. The instructions, when executed, cause the machine to receive a process message retransmission request from a retransmission request transmitting node in a blockchain network. The processing message retransmission request comprises the identification of the data block to be identified. And sending a processing message corresponding to the processing message retransmission request to a target blockchain node in the blockchain network. Wherein the processing message retransmission request is transmitted in a case where the retransmission request transmitting node has a processing message missing and cannot complete a current processing stage for a data block to be identified when a given period expires.
By using the method and the device disclosed by the invention, when the processing message is missing, the processing message retransmission request is periodically sent to other block chain nodes, and the corresponding processing message sent before the processing message is retransmitted by other block chain nodes, so that the block chain nodes with the processing message missing can smoothly receive the processing message. Furthermore, the message synchronization method does not need to consume excessive communication resources. With the method and apparatus of the present disclosure, by transmitting a processing message retransmission request to a target blockchain node in the blockchain network when there is a processing message missing at the expiration of a given period and current processing for the to-be-consensus data block cannot be completed, unnecessary message transmission can be reduced, so that the load of each blockchain node can be reduced.
With the method and apparatus of the present disclosure, by including a missing processed message identification in a processed message retransmission request, a target blockchain node can retransmit only a processed message corresponding to the missing processed message identification, thereby reducing the message transmission amount and saving bandwidth.
By using the method and the device disclosed by the invention, the target block chain node can only retransmit the processing message corresponding to the processing stage by including the processing stage identification in the processing message retransmission request, thereby reducing the message transmission amount and saving network resources.
By using the method and the device disclosed by the invention, other block chain nodes can only send the processing message to the block chain link point which sends the processing message retransmission request by including the retransmission request sending node identification in the processing message retransmission request, thereby reducing the network resources occupied by the retransmission processing message.
Drawings
A further understanding of the nature and advantages of the present disclosure may be realized by reference to the following drawings. In the drawings, similar components or features may have the same reference numerals. The accompanying drawings, which are included to provide a further understanding of the embodiments of the disclosure and are incorporated in and constitute a part of this specification, illustrate embodiments of the disclosure and together with the detailed description serve to explain the embodiments of the disclosure without limiting the embodiments of the disclosure. In the drawings:
FIG. 1 is a schematic diagram of one example of an application environment of an embodiment of the present disclosure;
FIG. 2 is a schematic diagram of one example of the blockchain network shown in FIG. 1;
FIG. 3 is a schematic diagram illustrating one example of a blockchain consensus process;
fig. 4 is a schematic diagram for explaining an example of a consensus process in a consensus process;
FIG. 5 is a flow diagram of a method of handling message synchronization according to one embodiment of the present disclosure;
fig. 6 is a flowchart of one example of a process of processing a message retransmission request transmission in a message synchronization method according to one embodiment of the present disclosure;
FIG. 7 is a block diagram of an apparatus for processing message synchronization according to one embodiment of the present disclosure;
fig. 8 is a block diagram showing an example of a message retransmission request transmission unit in the message synchronization processing apparatus shown in fig. 7;
fig. 9 is a block diagram of a processing message synchronization apparatus according to another embodiment of the present disclosure;
FIG. 10 is a block diagram of a blockchain node according to one embodiment of the present disclosure; and
fig. 11 is a block diagram of a computing device for implementing a method of handling message synchronization according to one embodiment of the present disclosure.
Detailed Description
The subject matter described herein will be discussed with reference to example embodiments. It should be understood that these embodiments are discussed only to enable those skilled in the art to better understand and thereby implement the subject matter described herein, and are not intended to limit the scope, applicability, or examples set forth in the claims. Changes may be made in the function and arrangement of elements discussed without departing from the scope of the disclosure. Various examples may omit, substitute, or add various procedures or components as needed. In addition, features described with respect to some examples may also be combined in other examples.
As used herein, the term "include" and its variants mean open-ended terms in the sense of "including, but not limited to. The term "based on" means "based at least in part on". The terms "one embodiment" and "an embodiment" mean "at least one embodiment". The term "another embodiment" means "at least one other embodiment". The terms "first," "second," and the like may refer to different or the same object. Other definitions, whether explicit or implicit, may be included below. The definition of a term is consistent throughout the specification unless the context clearly dictates otherwise.
The method and apparatus for processing message synchronization in blockchain consensus processing according to the present disclosure will now be described with reference to the accompanying drawings.
Fig. 1 is a schematic diagram of one example of an application environment of an embodiment of the present disclosure.
In some examples, application environment 100 enables entities to participate in a federated blockchain network 101. The application environment 100 includes computing devices or systems 102, 104 and a network 103. In some examples, network 103 includes a Local Area Network (LAN), a Wide Area Network (WAN), the internet, or a combination thereof, and connects websites, user devices (e.g., computing devices), and backend systems, and the like. In some examples, network 103 may be accessed through wired and/or wireless communication links. In some examples, network 103 enables communication with federation blockchain network 101. In general, the network 103 represents one or more communication networks. In some cases, the computing devices 102, 104 may be nodes of a cloud computing system (not shown), or each computing device 102, 104 may be a separate cloud computing system. A cloud computing system may include a plurality of computers interconnected by a network and may function as a distributed processing system.
In the depicted example, each computing device 102, 104 can comprise any suitable computing system capable of acting as a blockchain node in the federated blockchain network 101. Example computing devices include, but are not limited to, servers, desktop computers, laptops, tablet devices, and smartphones.
In some examples, computing devices 102, 104 may host one or more computer-implemented services for interacting with federation blockchain network 101. For example, the computing device 104 may host a computer-implemented service of a first entity (e.g., user a). For example, a first entity may manage a transaction management system for transactions with one or more other entities (e.g., other users). Computing device 102 may host a computer-implemented service of a second entity (e.g., user B). For example, a transaction management system in which a second entity may manage its transactions with one or more other entities (e.g., other users). In the example of fig. 1, in fig. 1, the federated blockchain network 101 is represented as a peer-to-peer node network, and the computing devices 102, 104 provide nodes of first and second entities, respectively, that participate in the federated blockchain network 101.
Fig. 2 is a schematic diagram of the blockchain network shown in fig. 1. In the blockchain network 200, there are blockchain nodes 201, 202, 203, 204, and 205.
Individual blockchain nodes in a blockchain network may participate in different processes. For example, some blockchain nodes may participate in the consensus process (e.g., as consensus nodes that add data blocks to blockchain 206), while other blockchain nodes may not participate in the consensus process. As another example, some blockchain link points may store a complete copy of blockchain 206, while other blockchain nodes may store only copies of portions of blockchain 206. For example, data access permissions may restrict blockchain data stored by respective participants within their respective systems.
A blockchain (e.g., blockchain 206 of fig. 2) consists of a chain of blocks, each block storing data. Examples of data include transaction data representing transactions between two or more participants. Any suitable data may be stored in the blockchain, such as documents, images, video, audio, and the like. Examples of transactions may include, but are not limited to, exchanging things of value (e.g., assets, products, services, and currency). The transaction data stored in the blockchain is not modifiable.
Fig. 3 is a schematic diagram for explaining one example of a block chain consensus process. As shown in fig. 2, the consensus process 200 includes a consensus initiation phase 210, a consensus response phase 220, a data block recovery phase 230, and a consensus confirmation phase 240.
In the consensus starting phase 210, the master Node (Leader Node) of the blockchain network sends a consensus starting message (Initial message) for performing consensus processing on the data blocks to be agreed to other blockchain nodes (i.e., backup nodes) in other blockchain networks. The consensus start message indicates that the master node is starting the consensus process. As shown in fig. 3, master node R0 sends an Initial message to the other blockchain nodes R1, R2, and R3. Note that consensus process 200 is shown as including four block chain nodes R0, R1, R2, and R3 for illustrative purposes only, and consensus process 200 may include any suitable number of block chain nodes.
In one example, the master node may divide the data block to be identified into a plurality of data block fragments based on an erasure coding algorithm, where the number of data block fragments is equal to the number of backup nodes in the blockchain network. The master node may then unicast the individual data block fragments to other blockchain nodes in a consensus start message. In FIG. 3, master node R0 sends each data chunk slice to blockchain nodes R1, R2, and R3. In this example, the format of the Initial message may be, for example: the method comprises the steps of Initial < epoch, tx _ root _ hash, ec _ block _ hash [ ], ec _ block, seq, and j >, wherein epoch is a block chain epoch identifier, tx _ root _ hash is a root hash of a Merckel tree, ec _ block _ hash [ ] is a hash value of a Merckel tree branch node, ec _ block is a data block fragment aiming at a target block chain node after being divided by an erasure coding algorithm, seq is a number of a data block to be identified under the block chain epoch, and j is a target block chain link identifier of the Initial message.
The block chain epoch (epoch) refers to a block chain network period when a certain block chain node acts as a master node. For example, in the example shown in fig. 3, the current blockchain network is in the blockchain age to which master node R0 corresponds. If the co-recognition master is triggered and the master exchange is successful, the master node switches to other blockchain nodes, and the blockchain network period correspondingly switches to the next blockchain era. The blockchain epoch may be identified by a blockchain epoch sequence number. For example, if the sequence number is N in the blockchain generation shown in fig. 3, the next time the main blockchain is co-identified, the sequence number is N + 1.
After the other block link points receive the consensus start message, the consensus process enters the consensus response phase 220. In the consensus response phase 220, when the backup node receives the consensus start message, a consensus response message (Echo message) is prepared in response to the consensus start message and broadcast to other blockchain nodes. The consensus response message is a reply of the backup node to the consensus initiation message sent by the primary node. As shown in FIG. 3, backup node R1 receives the Initial message sent by primary node R0 and replies to primary node R0 with an Echo message as a reply. At the same time, backup node R1 also multicasts Echo messages to other backup nodes, such as backup nodes R2 and R3. Similarly, backup nodes R2 and R3 each multicast Echo messages to other blockchain nodes including master node R0. The consensus process may enter a consensus confirmation phase when a blockchain node (e.g., a primary or backup node) receives Echo messages from other blockchain nodes. In the consensus confirmation phase, the block link node may verify the information in the Echo message. In the example shown in fig. 3, when the data chunk fragments are included in the Initial message, each backup node broadcasts the data chunk fragments received by itself to other blockchain nodes in an Echo message. At this time, each blockchain node enters the data block recovery phase 230 upon receiving the Echo message. Each blockchain node (e.g., backup node) may perform data block recovery based on the received data block fragments. The format of the Echo message may be, for example, Echo < epoch, tx _ root _ hash, ec _ block _ hash [ ], ec _ block, seq, sign _ proof, j >, where ec _ block is a data block fragment, j is a sending node identifier of the Echo message, and sign _ proof is a signature of the block link point j for its data block fragment.
In the data block recovery phase 230, each partition node may perform data block recovery on each owned data block shard (received from the primary node and from other backup nodes) based on an erasure code algorithm to recover the data block to be identified. After the data block to be identified is recovered, the block link point performs the identification confirmation phase 240 on the data block to be identified.
In the stage 240 of consensus verification, each block link node performs consensus verification on the data block to be consensus verified, and broadcasts an acknowledgement message (Accept message) to other block link nodes when the consensus verification passes. If the verification fails, the data block may be discarded and no processing may be performed. For example, as shown in FIG. 3, primary node R0 broadcasts an Accept message to backup nodes R1, R2, and R3. Similarly, backup nodes R1, R2, and R2 each broadcast an Accept message to other blockchain nodes. The format of the Accept message may be, for example, Accept < epoch, tx _ root _ hash, seq, sign _ proofs, j >, in the Accept message, j represents a sending node identifier of the Accept message, and sign _ proofs is a signature set of all data block fragments used by the block link point j to recover the data block to be identified. For example, if the blockchain node R1 recovers the data block to be recognized using the data block fragments carried in the Echo messages of the blockchain nodes R2 and R3, the sign _ proafs field includes the signature sets of the blockchain nodes R2 and R3.
In some implementation scenarios of the present disclosure, the consensus process may not include the data block recovery phase 230. For example, the data block recovery stage 230 may not be included when the primary node does not partition the data block to be identified into data block tiles based on erasure codes.
When the block chain node receives a sufficient number of Accept messages from other block chain nodes, the block chain node determines that the data blocks to be identified have been identified. For example, if the primary node R0 or backup node R1, R2, or R3 receives the number of Accept messages arbitrated (e.g., 2f +1, where f represents multiple failed network nodes), then it is determined that consensus is achieved.
Fig. 4 is a schematic diagram for explaining a main process of co-recognition in a blockchain network. The consensus process (e.g., the consensus process 400 shown in fig. 4) refers to a process of changing the master node, which is initiated when the backup node in the blockchain network considers that the master node has an abnormal behavior (e.g., the master node is malicious) during the consensus process. One concept associated with co-identifying a master and a master node is the blockchain era. When a master node is changed, the blockchain era switches accordingly to the next blockchain era.
In one example, in the master-Change initiation phase 410, when a backup node in the blockchain network considers that a co-identified master is needed, the backup node sends a master-Change initiation message (Epoch _ Change message) to other blockchain nodes. The rehosting start message indicates that the backup node wishes to become the new master node in the new blockchain era. For example, as shown in fig. 4, if backup node R0 determines that the current master node has failed and needs to perform a co-identified master, an Epoch _ Change message is sent to the other blockchain nodes R1, R2, and R3 in the blockchain network to indicate that blockchain node R0 wants to become the new master node. Note that the co-recognition master process 400 is shown as being implemented in connection with four network nodes, but this is merely an example and the co-recognition master process 400 may be implemented in connection with any suitable number of block link points.
Then, in the rehoming response phase 420, each network node receives the rehoming start message sent by the backup node R0, prepares a rehoming response message (New _ Epoch message) in response to the rehoming start message, and broadcasts the rehoming response message to other blockchain nodes. For example, as shown in FIG. 4, blockchain node R1 receives the Epoch _ Change message sent by backup node R0 and replies to backup node R0 with a New _ Epoch message indicating an acknowledgement that backup node R0 may become the New master node. At the same time, blockchain node R1 also broadcasts New _ Epoch messages to other blockchain nodes, such as network nodes R2 and R3. Similarly, block link points R2 and R3 also broadcast respective New _ Epoch messages to other block chain nodes, respectively. Each block link point may determine whether the owner change was successful based on the received owner change response message and identify a new master node and a new block chain era.
In the process of consensus process, both the data block recovery stage and the consensus confirmation stage need to receive enough messages to complete the process of this stage. If the message is lost due to the failure of the block chain node and other reasons, the consensus process at the corresponding stage cannot be completed, so that the block chain node will not respond and the consensus process for the corresponding to-be-consensus data block will be interrupted. However, in the block chain network, there may be a plurality of data blocks to be identified for the same time period, and the identification processing of the data blocks to be identified needs to be kept consistent, i.e. synchronized, for each block chain node. In addition, in the process of co-recognizing master, each block link node needs to receive enough master-change response messages to confirm whether master-change is successful and confirm a new master node. The following embodiments provide a method for enabling each blockchain node to receive a processing message in time, so as to implement synchronous consensus on data blocks to be identified.
Fig. 5 is a flowchart of a method of handling message synchronization according to one embodiment of the present disclosure. Fig. 5 illustrates an example of any two blockchain nodes in a blockchain network.
As shown in fig. 5, at block 502, block link point R1 determines whether a given period has expired. The process message is a process message received from other blockchain nodes at the current stage of processing for the data block to be identified. The current processing phase may be, for example, the data block recovery phase or the consensus confirmation phase shown in fig. 3. The current processing phase may also be the remainders response phase shown in fig. 4.
The starting point of a given period may be the time at which the respective processing stage issues its own processing message, or the time at which the respective processing stage receives the processing message of the first other blockchain node. In one example, in the data block recovery phase, the starting point of a given period may be the time when a block link node receives an Echo message of a certain block link node, or the time when a predetermined period of time has elapsed after sending out its Echo message. In another example, in a handover response procedure in a consensus handover procedure, the starting point of a given period may be the time when the own consensus response message is sent out, or the time when the consensus response message of the first other blockchain node is received.
If the given period expires, at block 504, a determination is made as to whether there is a process message missing for the data block to be consensus. For example, in the data chunk recovery phase shown in fig. 3, the blockchain node R1 may determine whether all Echo messages from other backup nodes (e.g., blockchain nodes R2 and R3) for the data to be consensus received, and determine that there is a processing message missing if any Echo message of R2 or R3 is not received. Similarly, in the consensus confirmation phase, it may be determined whether all Accept messages from other backup nodes (e.g., blockchain nodes R0, R2, and R3) have been received.
When the blockchain node R1 determines that there is a message missing, at block 506, the blockchain node R1 sends a process message retransmission request to the target blockchain node in the blockchain network. The processing message retransmission request comprises the identification of the data block to be identified. The identification of the data block to be identified can be a data block sequence number of the data block to be identified in the block chain network. The data block sequence number may be a consecutive number of all data blocks from the created block or a number in the corresponding block chain generation. Thus, a block chain epoch identifier may also be included in processing a message retransmission request. The target blockchain may be all other blockchain nodes in the blockchain network (e.g., blockchain nodes R0, R2, and R3 shown in fig. 3). At this time, a process message retransmission request may be broadcast to other blockchain nodes in the blockchain network. As an example, a format for processing a message retransmission request may be Status < seq >.
In another example, upon determining that there is a message missing, the source blockchain node of the missing processed message may also be determined. The source blockchain node of a processed message refers to the blockchain link node that sent the processed message. When the source blockchain node missing the processing message is judged, a processing message retransmission request can be sent to the determined source blockchain node. For example, in the data block recovery phase, if the block link node R1 judges the response message of the missing block link node R2, a message retransmission request may be sent only to the block link node R2. Therefore, the occupation of network resources can be reduced.
Upon receiving the message retransmission request, at block 508, the blockchain node R2 transmits a processed message corresponding to the processed message retransmission request to the target blockchain node in the blockchain network. Although shown in fig. 5 as receiving a message retransmission request sent by blockchain node R1, a blockchain link point in a blockchain network may receive a message retransmission request from any other blockchain node.
In one example, each blockchain node may broadcast the processing message for the data block to be identified, which is sent by the node itself, to other blockchain nodes when receiving the message retransmission request. For example, if the block link node receives a message retransmission request for the data block K to be identified, the block link node R2 may broadcast all the processed messages for the data block K to be identified, which have been sent by itself, to other block link nodes. In one example, a block link node that receives a process message retransmission request may only send an Echo message and a data block Accept message.
The processing message retransmission request may further include a missing processing message identifier. As an example, the format for handling the message retransmission request may be Status < epoch, seq, L >, L being the missing handling message identifier. Different values of L can be set to correspond to various processing messages of the consensus processing procedure, so that the missing processing messages can be judged by the value of L. In this example, other blockchain nodes (e.g., blockchain node R2) may send process messages corresponding to seq and L upon receiving the message retransmission request. For example, if blockchain node R1 determines that it is an Echo message that has been missing, it may be identified in processing the message retransmission request that it is an Echo message for the data block to be identified that is missing. Thus, R2 can broadcast Echo messages for the data blocks to be identified to other tile chain nodes upon receiving the process message retransmission request.
In addition, the processing of the message retransmission request may further include a processing stage identifier. As an example, the format for processing the message retransmission request may be Status < seq, E, a >, where E denotes a data block recovery phase and a denotes a consensus confirmation phase. When the value of E is 1, it indicates a message (i.e., Echo message) required by the data block recovery stage, and when the value of E is 0, it indicates that there is no absence of Echo message. Similarly, when a takes a value of 1, it indicates that there is no missing message (i.e., Accept message) required in the phase of the consensus confirmation, and when a takes a value of 0, it indicates that there is no missing in the Accept message. Thus, a block link point that receives a process message retransmission request can retransmit only the process message that block link node R1 is missing. For example, if the message retransmission request received by the blockchain node R2 is Status < K,1,0>, the Echo message for the data block K to be identified may be retransmitted to other blockchain nodes.
In another example, processing the message retransmission request further includes a retransmission request transmitting node identification. As an example, the process message retransmission request may be Status < seq, E, a, j >, where j denotes a block link point identifier of the process message retransmission request. When other block chain nodes receive the process message request, the corresponding process message may be retransmitted to block chain node j.
Fig. 6 is a flowchart of one example of a process of processing a message retransmission request transmission in a message synchronization method according to one embodiment of the present disclosure.
As shown in FIG. 6, a determination is made at block 602 as to whether a given period has expired. When the given period expires, at block 604, a determination is made as to whether there is a processing message missing.
If there is a process message missing, at block 606, it is determined whether the current process for the data block to be consensus can be completed. For example, in the data block recovery phase shown in fig. 3, if the blockchain node R1 can recover the data block to be identified based on the erasure code algorithm and according to the currently collected data block fragments, it indicates that the current processing for the data block to be identified can be completed although there is a message missing. Similarly, in the consensus confirmation phase, if a sufficient number of data confirmation messages have been received and a confirmation result that the consensus passes can be derived, it can be determined that the processing of the phase can be completed. In the master change response phase, if a new master node can be determined based on the received master change response message, it may be determined that the process of the master change response phase can be completed.
When the current process cannot be completed, at block 608, a process message retransmission request is sent to the target blockchain node in the blockchain network. If there are block chain nodes with missing messages that can complete the current process, there is no need to request retransmission of the missing processed message. Therefore, network resources occupied by message transmission can be reduced, and the load of each block chain node can be reduced.
With the above embodiments, the process message synchronization can be achieved using a message retransmission request in a common format in the respective processes of the consensus process (including the consensus-exchange main process).
Fig. 7 is a block diagram of a processing message synchronization apparatus according to an embodiment of the present disclosure. As shown in fig. 7, the processed message synchronization apparatus 700 includes a message retransmission request transmission unit 710 and a processed message reception unit 720.
The message retransmission request transmitting unit 710 is configured to transmit a process message retransmission request to a target block chain node in the block chain network if there is a process message missing at the expiration of a given period, the process message being a process message received from other block chain nodes at the time of current processing for a data block to be consensus, the process message retransmission request including the data block to be consensus identification.
In one example, the message retransmission request transmitting unit 710 may be configured to transmit a processing message retransmission request to a target blockchain node in the blockchain network when there is a processing message missing and current processing for a data block to be identified cannot be completed at the expiration of a given period. The message retransmission request transmission unit 710 may broadcast a process message retransmission request to other blockchain nodes in the blockchain network.
The process message receiving unit 720 is configured to receive a process message retransmitted in response to a process message retransmission request from a target blockchain node in the blockchain network.
Fig. 8 is a block diagram showing an example of a message retransmission request transmitting unit in the message synchronization processing apparatus shown in fig. 7. As shown in fig. 8, the message retransmission request transmission unit 710 includes a source node determination module 711 and a message retransmission request transmission module 712.
The source node determination module 711 is configured to determine the source blockchain node of the missing processed message if there is a processing message missing at the expiration of a given period. The message retransmission request transmission module 712 is configured to transmit a process message retransmission request to the determined source blockchain node.
The process message retransmission request may further include a missing process message identification and may further include a process phase identification, such that other blockchain nodes may only send process messages corresponding to the missing process message identification and/or the process phase identification upon receiving the message retransmission request. In addition, processing the message retransmission request can further include a corresponding block chain time identification of the data block to be identified.
Fig. 9 is a block diagram of a processing message synchronization apparatus according to another embodiment of the present disclosure. As shown in fig. 9, the device for processing message synchronization 900 includes a message retransmission request receiving unit 910 and a message transmitting unit 920.
The message retransmission request receiving unit 910 is configured to receive a process message retransmission request. The processing message retransmission request comprises the identification of the data block to be identified. Upon receiving the process message retransmission request, the message transmission unit 920 transmits a process message corresponding to the process message retransmission request to a target blockchain node in the blockchain network.
In one example, the message sending unit 920 may be configured to broadcast a process message corresponding to the process message retransmission request to other block link points in the block chain network.
Further, when the processing message retransmission request further includes the retransmission request transmission node identification, the message transmission unit may transmit the processing message corresponding to the processing message retransmission request to the block chain node indicated by the retransmission request transmission node identification.
Fig. 10 is a block diagram of a blockchain node according to one embodiment of the present disclosure. As shown in fig. 10, block link point 1000 includes a process message synchronizer 1010 and a process message synchronizer 1020.
The process message synchronizer 1010 may have the functions and structures described above in connection with fig. 7 and 8. The process message synchronizer 1020 may have the functions and structures described above in connection with fig. 9. Embodiments of a method and apparatus for processing message synchronization according to the present disclosure are described above with reference to fig. 1 to 10. The details mentioned in the above description of the method embodiments apply equally to the embodiments of the apparatus of the present disclosure.
The device for processing message synchronization of the present disclosure can be implemented by hardware, or can be implemented by software, or a combination of hardware and software. The various embodiments in this specification are described in a progressive manner, with like reference to each other.
The device for processing message synchronization of the present disclosure may be implemented by hardware, or may be implemented by software, or a combination of hardware and software. The software implementation is taken as an example, and is formed by reading corresponding computer program instructions in the storage into the memory for operation through the processor of the device where the software implementation is located as a logical means. In the present disclosure, an apparatus for handling message synchronization may be implemented with a computing device, for example.
Fig. 11 is a block diagram of a computing device for implementing a method of handling message synchronization according to one embodiment of the present disclosure. As shown in fig. 11, computing device 1100 includes a processor 1110, a memory 1120, a memory 1130, a communication interface 1140, and an internal bus 1150, where processor 1110, memory 1120, memory 1130, and communication interface 1140 are coupled together via internal bus 1150. According to one embodiment, the computing device 1100 may include at least one processor 1110, the at least one processor 1110 executing at least one computer-readable instruction (i.e., an element described above as being implemented in software) stored or encoded in a computer-readable storage medium (i.e., memory 1120).
In one embodiment, computer-executable instructions are stored in the memory 1120 that, when executed, cause the at least one processor 1110 to: if there is a process message missing at the expiration of a given period, sending a process message retransmission request to a target blockchain node in the blockchain network, the process message being a process message received from the other blockchain nodes at the current process for the data block to be consensus, the process message retransmission request including the data block to be consensus identification; and receiving a process message retransmitted in response to the process message retransmission request from a target blockchain node in the blockchain network.
In another embodiment, computer-executable instructions are stored in the memory 1120 that, when executed, cause the at least one processor 1110 to: receiving a processing message retransmission request, wherein the processing message retransmission request comprises a data block identifier to be identified; and transmitting a processing message corresponding to the processing message retransmission request to a target blockchain node in the blockchain network.
It should be appreciated that the computer-executable instructions stored in the memory 1120, when executed, cause the at least one processor 1110 to perform the various operations and functions described above in connection with fig. 1-10 in the various embodiments of the present disclosure.
According to one embodiment, a program product, such as a non-transitory machine-readable medium, is provided. A non-transitory machine-readable medium may have instructions (i.e., elements described above as being implemented in software) that, when executed by a machine, cause the machine to perform various operations and functions described above in connection with fig. 1-10 in various embodiments of the present disclosure.
Specifically, a system or apparatus may be provided which is provided with a readable storage medium on which software program code implementing the functions of any of the above embodiments is stored, and causes a computer or processor of the system or apparatus to read out and execute instructions stored in the readable storage medium.
In this case, the program code itself read from the readable medium can realize the functions of any of the above-described embodiments, and thus the machine-readable code and the readable storage medium storing the machine-readable code form part of the present invention.
Examples of the readable storage medium include floppy disks, hard disks, magneto-optical disks, optical disks (e.g., CD-ROMs, CD-R, CD-RWs, DVD-ROMs, DVD-RAMs, DVD-RWs), magnetic tapes, nonvolatile memory cards, and ROMs. Alternatively, the program code may be downloaded from a server computer or from the cloud via a communications network.
The foregoing description has been directed to specific embodiments of this disclosure. Other embodiments are within the scope of the following claims. In some cases, the actions or steps recited in the claims may be performed in a different order than in the embodiments and still achieve desirable results. In addition, the processes depicted in the accompanying figures do not necessarily require the particular order shown, or sequential order, to achieve desirable results. In some embodiments, multitasking and parallel processing may also be possible or may be advantageous. Not all steps and elements in the above flows and system structure diagrams are necessary, and some steps or elements may be omitted according to actual needs. The execution order of the steps is not fixed, and can be determined as required. The apparatus structures described in the above embodiments may be physical structures or logical structures, that is, some units may be implemented by the same physical entity, or some units may be implemented by a plurality of physical entities, or some units may be implemented by some components in a plurality of independent devices.
The term "exemplary" used throughout this specification means "serving as an example, instance, or illustration," and does not mean "preferred" or "advantageous" over other embodiments. The detailed description includes specific details for the purpose of providing an understanding of the described technology. However, the techniques may be practiced without these specific details. In some instances, well-known structures and devices are shown in block diagram form in order to avoid obscuring the concepts of the described embodiments.
Alternative embodiments of the present disclosure are described in detail with reference to the drawings, however, the embodiments of the present disclosure are not limited to the specific details in the embodiments, and various simple modifications may be made to the technical solutions of the embodiments of the present disclosure within the technical concept of the embodiments of the present disclosure, and the simple modifications all belong to the protective scope of the embodiments of the present disclosure.
The previous description of the disclosure is provided to enable any person skilled in the art to make or use the disclosure. Various modifications to the disclosure will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other variations without departing from the scope of the disclosure. Thus, the disclosure is not intended to be limited to the examples and designs described herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.
Claims (28)
1. A method for processing message synchronization in blockchain consensus processing, the method comprising:
a first node in the blockchain sends a processing message retransmission request to a target blockchain node in the blockchain network if determining that there is a processing message missing at the expiration of a given period and a current processing stage for a data block to be identified cannot be completed; wherein the processing message is a processing message received from other blockchain nodes at a current processing stage for the data block to be identified; the processing message retransmission request comprises a data block identifier to be identified; and the number of the first and second groups,
the first node receives a process message retransmitted in response to the process message retransmission request from a target blockchain node in the blockchain network.
2. The method of claim 1, wherein the process message retransmission request further comprises a missing process message identification.
3. The method according to claim 1 or 2, wherein said processing a message retransmission request further comprises a processing stage identification.
4. The method of claim 3, wherein the processing stage identification comprises any of the following stage identifications:
a block chain data block recovery phase identifier;
and identifying in a consensus confirmation phase.
5. The method of claim 1 or 2, wherein sending a handle message retransmission request to a target blockchain node in a blockchain network comprises:
and broadcasting a processing message retransmission request to other blockchain nodes in the blockchain network.
6. The method of claim 5, wherein said processing the message retransmission request further comprises a retransmission request transmitting node identification,
wherein the other blockchain node retransmits the process message to the retransmission request transmitting node in response to the process message retransmission request.
7. The method of claim 1 or 2, wherein, if it is determined that there is a process message missing and the current processing stage for the data block to be consensus cannot be completed at the expiration of a given period, sending a process message retransmission request to a target blockchain node in the blockchain network comprises:
determining a source block chain node of the missing processing message if there is a missing processing message at the expiration of the given period and the current processing phase for the data block to be consensus cannot be completed; and
and sending the processing message retransmission request to the determined source blockchain node.
8. The method of claim 1, the starting point of the given period being the time at which the current processing stage receives a processing message of a first other blockchain node; alternatively, the starting point of the given period is a time when the first node transmits a processing message to other blockchain nodes.
9. A method for handling message synchronization in blockchain consensus processing, the method being performed by a retransmission request receiving node in a blockchain network, the method comprising:
receiving a processing message retransmission request from a retransmission request transmitting node in a block chain network, wherein the processing message retransmission request comprises a data block identifier to be identified; and
sending a processing message corresponding to the processing message retransmission request to a target blockchain node in the blockchain network;
wherein the processing message retransmission request is transmitted in a case where the retransmission request transmitting node has a processing message missing and cannot complete a current processing stage for a data block to be identified when a given period expires.
10. The method of claim 9, wherein the process message retransmission request further includes a missing process message identification.
11. The method according to claim 9 or 10, wherein said processing a message retransmission request further comprises a processing stage identification.
12. The method of claim 9 or 10, wherein transmitting the process message corresponding to the process message retransmission request to a target blockchain node in the blockchain network comprises:
broadcasting the processing message corresponding to the processing message retransmission request to other blockchain nodes in the blockchain network.
13. The method according to claim 9 or 10, wherein said processing of message retransmission requests further comprises a retransmission request transmitting node identification, and
transmitting a processed message corresponding to the processed message retransmission request to a target blockchain node in the blockchain network includes:
and transmitting the processing message corresponding to the processing message retransmission request to the retransmission request transmitting node.
14. The method of claim 9, the starting point of the given period being the time at which the current processing stage receives a processing message of a first other blockchain node; alternatively, the starting point of the given period is a time when the first node transmits a processing message to other blockchain nodes.
15. An apparatus for processing message synchronization in block chain consensus processing, the apparatus being applied to a retransmission request transmitting node, the apparatus comprising:
a message retransmission request transmitting unit configured to transmit a processing message retransmission request to a target blockchain node in the blockchain network if there is a processing message missing and a current processing stage for a data block to be identified cannot be completed at the expiration of a given period; wherein the processing message is a processing message received from other blockchain nodes at a current processing stage for the data block to be identified; the processing message retransmission request comprises a data block identifier to be identified; and
a process message receiving unit configured to receive a process message retransmitted in response to the process message retransmission request from a target blockchain node in the blockchain network.
16. The apparatus of claim 15, wherein the process message retransmission request further comprises a missing process message identification.
17. The apparatus of claim 15 or 16, wherein the processing of the message retransmission request further comprises a processing stage identification.
18. The apparatus according to claim 15 or 16, wherein the message retransmission request transmitting unit is configured to:
and broadcasting a processing message retransmission request to other blockchain nodes in the blockchain network.
19. The apparatus of claim 15 or 16, wherein the message retransmission request transmission unit comprises:
a source node determination module configured to determine a source blockchain node of a missing processed message if there is a missing processed message at the expiration of a given period; and
a message retransmission request sending module configured to send the processing message retransmission request to the determined source block chain node.
20. The apparatus of claim 15, the start of the given period being the time at which the current processing stage receives a processing message of a first other blockchain node; alternatively, the starting point of the given period is a time when the first node transmits a processing message to other blockchain nodes.
21. An apparatus for processing message synchronization in block chain consensus processing, the apparatus being applied to a retransmission request receiving node, the apparatus comprising:
a message retransmission request receiving unit configured to receive a processed message retransmission request from a retransmission request transmitting node in a block chain network, the processed message retransmission request including a to-be-identified data block identifier; and
a message transmitting unit configured to transmit a process message corresponding to the process message retransmission request to a target blockchain node in the blockchain network,
wherein the processing message retransmission request is transmitted in a case where the retransmission request transmitting node has a processing message missing and cannot complete a current processing stage for a data block to be identified when a given period expires.
22. The apparatus of claim 21, wherein the message transmitting unit is configured to:
broadcasting the processing message corresponding to the processing message retransmission request to other blockchain nodes in the blockchain network.
23. The apparatus of claim 21, wherein said processing the message retransmission request further comprises a retransmission request transmitting node identification, and
the message sending unit is configured to:
and transmitting the processing message corresponding to the processing message retransmission request to the retransmission request transmitting node.
24. A block link point, comprising:
the apparatus of any one of claims 15 to 2; and
apparatus as claimed in any one of claims 21 to 23.
25. A computing device, comprising:
at least one processor; and
a memory storing instructions that, when executed by the at least one processor, cause the at least one processor to:
sending a process message retransmission request to a target blockchain node in the blockchain network if it is determined that there is a process message missing at the expiration of a given period and the current processing stage for the data block to be consensus cannot be completed; wherein the processing message is a processing message received from other blockchain nodes at a current processing stage for the data block to be identified; the processing message retransmission request comprises a data block identifier to be identified; and the number of the first and second groups,
receiving a process message retransmitted in response to the process message retransmission request from a target blockchain node in the blockchain network.
26. A machine-readable storage medium storing executable instructions that, when executed, cause the machine to:
sending a process message retransmission request to a target blockchain node in the blockchain network if it is determined that there is a process message missing at the expiration of a given period and the current processing stage for the data block to be consensus cannot be completed; wherein the processing message is a processing message received from other blockchain nodes at a current processing stage for the data block to be identified; the processing message retransmission request comprises a data block identifier to be identified; and the number of the first and second groups,
receiving a process message retransmitted in response to the process message retransmission request from a target blockchain node in the blockchain network.
27. A computing device, comprising:
at least one processor; and
a memory storing instructions that, when executed by the at least one processor, cause the at least one processor to:
receiving a processing message retransmission request from a retransmission request transmitting node in a block chain network, wherein the processing message retransmission request comprises a data block identifier to be identified; and
transmitting a process message corresponding to the process message retransmission request to a target blockchain node in the blockchain network,
wherein the processing message retransmission request is transmitted in a case where the retransmission request transmitting node has a processing message missing and cannot complete a current processing stage for a data block to be identified when a given period expires.
28. A machine-readable storage medium storing executable instructions that, when executed, cause the machine to:
receiving a processing message retransmission request from a retransmission request transmitting node in a block chain network, wherein the processing message retransmission request comprises a data block identifier to be identified; and
transmitting a process message corresponding to the process message retransmission request to a target blockchain node in the blockchain network,
wherein the processing message retransmission request is transmitted in a case where the retransmission request transmitting node has a processing message missing and cannot complete a current processing stage for a data block to be identified when a given period expires.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010779693.4A CN112019599A (en) | 2020-03-16 | 2020-03-16 | Method and device for synchronizing processing messages during block chain consensus processing |
Applications Claiming Priority (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010779693.4A CN112019599A (en) | 2020-03-16 | 2020-03-16 | Method and device for synchronizing processing messages during block chain consensus processing |
| CN202010181621.XA CN111064813B (en) | 2020-03-16 | 2020-03-16 | Method and device for synchronizing processing messages during block chain consensus processing |
Related Parent Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010181621.XA Division CN111064813B (en) | 2020-03-16 | 2020-03-16 | Method and device for synchronizing processing messages during block chain consensus processing |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN112019599A true CN112019599A (en) | 2020-12-01 |
Family
ID=70307904
Family Applications (2)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010181621.XA Active CN111064813B (en) | 2020-03-16 | 2020-03-16 | Method and device for synchronizing processing messages during block chain consensus processing |
| CN202010779693.4A Pending CN112019599A (en) | 2020-03-16 | 2020-03-16 | Method and device for synchronizing processing messages during block chain consensus processing |
Family Applications Before (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010181621.XA Active CN111064813B (en) | 2020-03-16 | 2020-03-16 | Method and device for synchronizing processing messages during block chain consensus processing |
Country Status (2)
| Country | Link |
|---|---|
| CN (2) | CN111064813B (en) |
| WO (1) | WO2021184879A1 (en) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111064813B (en) * | 2020-03-16 | 2020-06-30 | 支付宝(杭州)信息技术有限公司 | Method and device for synchronizing processing messages during block chain consensus processing |
| CN113872961B (en) * | 2021-09-24 | 2023-09-29 | 支付宝(杭州)信息技术有限公司 | Block chain consensus method, consensus node and electronic equipment |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107392611A (en) * | 2017-03-24 | 2017-11-24 | 阿里巴巴集团控股有限公司 | A kind of method and device for sending Transaction Information and common recognition checking |
| US20180157558A1 (en) * | 2016-10-04 | 2018-06-07 | Nec Europe Ltd. | Method and system for byzantine fault-tolerance replicating of data on a plurality of servers |
| CN109347917A (en) * | 2018-09-14 | 2019-02-15 | 北京沃杰知识产权有限公司 | Block chain data common recognition processing method, system, storage medium and electronic equipment |
| CN110115001A (en) * | 2018-11-07 | 2019-08-09 | 阿里巴巴集团控股有限公司 | Promote practical Byzantine failure tolerance block chain common recognition synchronous with node |
| CN110349029A (en) * | 2019-07-17 | 2019-10-18 | 中国银行股份有限公司 | A kind of processing method, equipment and the system of the trade identity based on block chain |
Family Cites Families (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20170236120A1 (en) * | 2016-02-11 | 2017-08-17 | Oracle International Corporation | Accountability and Trust in Distributed Ledger Systems |
| CN107196772B (en) * | 2017-03-24 | 2020-03-13 | 创新先进技术有限公司 | Method and device for broadcasting message |
| CN107368507B (en) * | 2017-03-28 | 2020-03-27 | 创新先进技术有限公司 | Block chain-based consensus method and device |
| CN107046542B (en) * | 2017-04-24 | 2020-04-14 | 杭州云象网络技术有限公司 | Method for realizing consensus verification by adopting hardware at network level |
| CN108111604B (en) * | 2017-12-21 | 2020-08-14 | 广州广电运通金融电子股份有限公司 | Block chain consensus method, device and system, and identification information processing method and device |
| CN108376106A (en) * | 2018-02-01 | 2018-08-07 | 中国工商银行股份有限公司 | A kind of block chain message feedback method and system |
| CN108462724B (en) * | 2018-05-17 | 2020-07-31 | 京东数字科技控股有限公司 | Data sharing method, device, system, member node and readable storage medium |
| CN111064813B (en) * | 2020-03-16 | 2020-06-30 | 支付宝(杭州)信息技术有限公司 | Method and device for synchronizing processing messages during block chain consensus processing |
-
2020
- 2020-03-16 CN CN202010181621.XA patent/CN111064813B/en active Active
- 2020-03-16 CN CN202010779693.4A patent/CN112019599A/en active Pending
- 2020-12-26 WO PCT/CN2020/139718 patent/WO2021184879A1/en active Application Filing
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20180157558A1 (en) * | 2016-10-04 | 2018-06-07 | Nec Europe Ltd. | Method and system for byzantine fault-tolerance replicating of data on a plurality of servers |
| CN107392611A (en) * | 2017-03-24 | 2017-11-24 | 阿里巴巴集团控股有限公司 | A kind of method and device for sending Transaction Information and common recognition checking |
| CN109347917A (en) * | 2018-09-14 | 2019-02-15 | 北京沃杰知识产权有限公司 | Block chain data common recognition processing method, system, storage medium and electronic equipment |
| CN110115001A (en) * | 2018-11-07 | 2019-08-09 | 阿里巴巴集团控股有限公司 | Promote practical Byzantine failure tolerance block chain common recognition synchronous with node |
| CN110349029A (en) * | 2019-07-17 | 2019-10-18 | 中国银行股份有限公司 | A kind of processing method, equipment and the system of the trade identity based on block chain |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111064813A (en) | 2020-04-24 |
| CN111064813B (en) | 2020-06-30 |
| WO2021184879A1 (en) | 2021-09-23 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110351133B (en) | Method and device for main node switching processing in block chain system | |
| KR102157452B1 (en) | Performing a recovery process for network nodes in a distributed system | |
| EP3780553B1 (en) | Blockchain-based transaction consensus processing method and apparatus, and electrical device | |
| US11128522B2 (en) | Changing a master node in a blockchain system | |
| US11411721B2 (en) | Systems and methods for selecting and utilizing a committee of validator nodes in a distributed system | |
| CN109426949B (en) | Cross-chain transaction method and device | |
| US20190342149A1 (en) | Node device operation method, work status switching apparatus, node device, and medium | |
| CN110754070B (en) | Fast propagation of recent transactions over blockchain networks | |
| CN112685796A (en) | Block chain-based block consensus method and related equipment | |
| WO2016127884A1 (en) | Message pushing method and device | |
| CN112714192B (en) | Data synchronization method and device, computer readable medium and electronic equipment | |
| CN107197036A (en) | A kind of consistent processing method of information based on block chain and terminal | |
| CN114048517B (en) | Dual channel consensus system and method for blockchains, computer readable storage medium | |
| CN113055188B (en) | Data processing method, device, equipment and storage medium | |
| CN111064813B (en) | Method and device for synchronizing processing messages during block chain consensus processing | |
| CN108667635B (en) | Disaster recovery processing method, equipment and system | |
| CN114050904B (en) | Consensus system and method based on two-level leader node fragmentation structure | |
| CN111582843A (en) | Block chain privacy transaction method based on aggregated signature | |
| CN106951443B (en) | Method, equipment and system for synchronizing copies based on distributed system | |
| CN111211876B (en) | Method and device for sending response message aiming at data request and block chain system | |
| US20090083379A1 (en) | Enabling connections for use with a network | |
| CN102761520B (en) | Method and system for processing authentication information | |
| CN116055579A (en) | Multi-alliance chain crossing method | |
| CN116846888A (en) | Consensus processing method, device, equipment and storage medium of block chain network | |
| CN116192868B (en) | Parallel Bayesian fault tolerance consensus method and terminal applied to alliance chain |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| REG | Reference to a national code |
Ref country code: HK Ref legal event code: DE Ref document number: 40041495 Country of ref document: HK |
|
| RJ01 | Rejection of invention patent application after publication | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20201201 |