WO2021135745A1

WO2021135745A1 - Method and apparatus for carrying out transaction data processing at blockchain node

Info

Publication number: WO2021135745A1
Application number: PCT/CN2020/131838
Authority: WO
Inventors: 林鹏
Original assignee: 支付宝(杭州)信息技术有限公司
Priority date: 2020-01-02
Filing date: 2020-11-26
Publication date: 2021-07-08
Also published as: CN111199485A

Abstract

A method and apparatus for carrying out transaction data processing at a blockchain node. The method comprises: after at least one piece of transaction data is received, sending the received at least one piece of transaction data to a blockchain processing unit to carry out corresponding blockchain processing, wherein the transaction data has a state description field; acquiring, from the blockchain processing unit, corresponding blockchain processing state information for each piece of transaction data; and for each piece of transaction data of the at least one piece of transaction data, updating the state description field of the transaction data by using the received blockchain processing state information, so that an associated party of the at least one piece of transaction data carries out state querying.

Description

Method and device for processing transaction data at block chain node

Technical field

The present disclosure relates to the field of blockchain technology, and in particular, to a method and device for processing transaction data at a blockchain node.

Background technique

Blockchain technology, also known as distributed ledger technology, is an emerging technology in which several computing devices participate in "bookkeeping" and jointly maintain a complete distributed database. Because the blockchain technology has the characteristics of decentralization, openness and transparency, each computing device can participate in database records, and the rapid data synchronization between computing devices, the blockchain technology has been widely used in many fields. To apply.

In the blockchain system, the transaction initiated by the client is sent to the blockchain node to request the blockchain node to perform the blockchain processing operation on the transaction. After the client sends the transaction data to the blockchain node, it needs to query the blockchain node for the processing status of the transaction after a period of time. Blockchain nodes not only need to perform blockchain processing on transaction data, but also respond to client status query requests, which leads to excessive load on blockchain nodes.

Summary of the invention

In view of the above, the present disclosure provides a method and device for processing transaction data at a blockchain node. Using the method and device, the processing status of each transaction is stored independently of the blockchain processing unit, so that the transaction related parties can obtain the processing status of the transaction without accessing the blockchain processing unit of the blockchain node. Reduce the load of the block chain link processing unit.

According to one aspect of the present disclosure, there is provided a method for processing transaction data at a blockchain node, the blockchain node including a blockchain processing unit, and the method includes: upon receiving at least one transaction After data, the received at least one transaction data is sent to the blockchain processing unit for corresponding blockchain processing. The transaction data has a state description field; the transaction data is obtained from the blockchain processing unit for each The corresponding blockchain processing status information of the transaction data; and for each transaction data in the at least one transaction data, use the received blockchain processing status information to update the status description field of the transaction data for the at least A related party of transaction data to perform status query.

Optionally, in an example, the method may further include: periodically sending the updated blockchain processing status information of the at least one transaction data to the related party of the at least one transaction data.

Optionally, in an example, the method may further include: in response to a status query request of an associated party of the at least one transaction data, sending blockchain processing status information of the at least one transaction data to the associated party .

Optionally, in an example, the method may further include: when the pending transaction data sent to the blockchain processing unit exceeds the current limit threshold, stopping sending the pending transaction to the blockchain processing unit Transaction data.

Optionally, in an example, the current limit threshold may be determined based on the processing queue size of the blockchain processing unit, the maximum business volume per unit time, and the consensus state.

Optionally, in an example, the method may further include: buffering at least one piece of received transaction data.

Optionally, in an example, the method may further include: when the amount of the cached transaction data exceeds the storage threshold, storing part or all of the cached transaction data in the non-volatile memory.

Optionally, in an example, the method may further include: for each transaction data stored, deleting the transaction when the state description field of the transaction data is updated to a predetermined time period after completing the block chaining data.

Optionally, in an example, the method may further include: for each transaction data cached, the status description field of the transaction data is updated to be not updated to complete consensus after a second predetermined time has passed after the verification is completed At the time, broadcast the transaction data to other blockchain nodes.

According to another aspect of the present disclosure, there is also provided a device for processing transaction data at a blockchain node, the blockchain node includes a blockchain processing unit, and the device includes a transaction data sending unit, It is configured to, after receiving at least one transaction data, send the received at least one transaction data to the blockchain processing unit for corresponding blockchain processing, and the transaction data has a state description field; processing state An information acquisition unit configured to acquire corresponding blockchain processing status information for each transaction data from the blockchain processing unit; and a processing status update unit configured to target each transaction data in the at least one transaction data , Using the received block chain processing state information to update the state description field of the transaction data, so that the related party of the at least one transaction data can perform state query.

Optionally, in an example, the device may further include: a processing status information sending unit configured to periodically send the updated blockchain processing status information of the at least one transaction data to the at least one transaction data Related party.

Optionally, in an example, the apparatus may further include: a processing status information sending unit configured to send the at least one related party to the at least one related party in response to a status query message of the at least one related party of transaction data. The blockchain of transaction data processes status information.

Optionally, in an example, the device may further include: a data current limiting unit configured to determine whether the transaction data to be processed sent to the blockchain processing unit exceeds a current limiting threshold. The transaction data sending unit is configured to stop sending the transaction data to be processed to the blockchain processing unit when it is determined that the transaction data to be processed sent to the blockchain processing unit exceeds the current limit threshold.

Optionally, in an example, the device may further include: a storage unit configured to store the received at least one transaction data in a cache.

Optionally, in an example, the storage unit may be further configured to store part or all of the cached transaction data in the non-volatile memory when the amount of the cached transaction data exceeds the storage threshold.

Optionally, in an example, the device may further include: a transaction data deletion unit configured to deal with each transaction data cached, after the state description field of the transaction data is updated to complete the block chaining. When a predetermined period of time, delete the transaction data.

Optionally, in an example, the device may further include: a broadcasting unit configured to target each transaction data that is cached, after the state description field of the transaction data is updated to complete verification after a second predetermined time has elapsed When it has not been updated to complete the consensus, the transaction data is broadcast to other blockchain nodes.

According to another aspect of the present disclosure, there is also provided a computing device, including: at least one processor; and a memory, the memory stores instructions, and when the instructions are executed by the at least one processor, the at least one The processor executes the method as described above.

According to another aspect of the present disclosure, there is also provided a non-transitory machine-readable storage medium, which stores executable instructions that, when executed, cause the machine to perform the method as described above.

Using the method and device of the present disclosure, by storing the processing state of each transaction independently of the blockchain processing unit, the related parties of the transaction data can obtain the transaction information without accessing the blockchain processing unit of the blockchain node. Blockchain processing status. Therefore, the blockchain processing unit of the blockchain only needs to update the processing status of the transaction data on the blockchain node, and does not need to respond to the status query request of the related party. Therefore, the method and device can reduce the load of the blockchain processing unit, thereby improving the processing efficiency of transaction data.

Using the method and device of the present disclosure, by periodically sending transaction data blockchain processing status information to transaction data related parties, it is possible to avoid excessive access load or instantaneous access peaks caused by related parties' access to blockchain nodes.

Using the method and device of the present disclosure, by using the current limit threshold to limit the current to be processed transaction data sent to the blockchain processing unit, it is possible to avoid the loss of transaction data due to the processing queue of the blockchain processing unit exceeding the threshold.

By using the method and device of the present disclosure, by caching the received transaction data locally, when the block chain node fails and the transaction data is lost in the block chain processing unit, the transaction data can be obtained from the local cache , So there is no need for the client to send transaction data again.

By using the method and device of the present disclosure, by storing part or all of the cached transaction data in the non-volatile memory when the amount of cached transaction data exceeds the storage threshold, it is possible to avoid difficulty when the cache space becomes vacant. The transaction data is read in the lossy memory, so as to avoid the problem that the client has to send the transaction data again due to the loss of the transaction data caused by insufficient buffer space.

Using the method and device of the present disclosure, by broadcasting the transaction data to other blockchain nodes when the state description field of the transaction data is updated to complete the verification and is not updated to complete the consensus after the second predetermined time has passed after the verification is completed. When a block chain node fails, the transaction data is broadcast to other block chain nodes in time.

Description of the drawings

By referring to the following drawings, a further understanding of the nature and advantages of the present disclosure can be achieved. In the drawings, similar components or features may have the same reference signs. The drawings are used to provide a further understanding of the embodiments of the present invention, and constitute a part of the specification. Together with the following specific implementations, they are used to explain the embodiments of the present disclosure, but do not constitute a limitation to the embodiments of the present disclosure. In the attached picture:

Fig. 1 is a schematic diagram for explaining an example of a blockchain system;

Figure 2 is a schematic diagram for explaining the structure of a blockchain node;

FIG. 3 is a schematic diagram for explaining the message sending process when a blockchain node performs transaction data processing;

Fig. 4 is a schematic structural diagram of a blockchain node according to an embodiment of the present disclosure;

FIG. 5 is a structural block diagram of a device for processing transaction data at a blockchain node suitable for the blockchain node shown in FIG. 4;

6 is a schematic diagram for explaining the message sending process when using the blockchain node of the present disclosure to process transaction data;

Fig. 7 is a flowchart of a method for processing transaction data at a blockchain node according to an embodiment of the present disclosure;

Fig. 8 is a flowchart of an application scenario of a method for processing transaction data at a blockchain node according to an embodiment of the present disclosure; and

Fig. 9 is a structural block diagram of a computing device for implementing a method for processing transaction data at a blockchain node according to an embodiment of the present disclosure.

Detailed ways

The subject described herein will be discussed below with reference to example embodiments. It should be understood that the discussion of these embodiments is only to enable those skilled in the art to better understand and realize the subject described herein, and is not to limit the scope of protection, applicability, or examples set forth in the claims. The function and arrangement of the discussed elements can be changed without departing from the scope of protection of the present disclosure. Various examples can omit, substitute, or add various procedures or components as needed. In addition, features described with respect to some examples can also be combined in other examples.

As used herein, the term "including" and its variations mean open terms, meaning "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."

In this document, the term "connected" refers to direct mechanical connection, communication or electrical connection between two components, or indirect mechanical connection, communication or electrical connection through intermediate components. The term "electrically connected" refers to the possibility of electrical communication between two components for data/information exchange. Similarly, the electrical connection may refer to a direct electrical connection between two components, or an indirect electrical connection through an intermediate component. The electrical connection can be implemented in a wired manner or a wireless manner.

The method and device for processing transaction data at a blockchain node of the present disclosure will now be described with reference to the accompanying drawings.

FIG. 1 is a schematic diagram for explaining an example of the blockchain system 100.

As shown in FIG. 1, in the blockchain system 100, there are blockchain

nodes

102, 103, 104, 105, and 106. The client 101 is connected to the blockchain node 102. When the client 101 initiates a transaction, the transaction data is sent to the blockchain node 102 communicating with it. After receiving the transaction data, the blockchain node 102 first verifies the transaction data. When the verification is legal, the blockchain node 102 broadcasts the received transaction data to other blockchain nodes 103-106 in the blockchain system 100 to perform consensus processing on the transaction data. Figure 1 is just an example of a blockchain system. In other examples, the blockchain system may include a transaction pool, which is used to store transactions initiated by the client 101 (or other clients in the blockchain system) data. Each node can read transaction data from the transaction pool, and perform verification, consensus and other processing. In addition, in another example, the client 101 can also be connected to multiple blockchain nodes, so that transaction data can be sent to multiple blockchain nodes connected to it. The blockchain node that receives the transaction data can fight for the processing right (for example, the accounting right) of the transaction data through a predetermined mechanism. The client 101 may be a lightweight node (or called an SPV node) in a blockchain system, and the

blockchain nodes

102, 103, 104, 105, 106 are full nodes (or called an accounting node). In the blockchain system, the lightweight node can further connect to one or more second clients (not shown in the figure), and the second client can perform operations such as initiating transactions or querying transaction status via the lightweight nodes.

FIG. 2 is a schematic diagram for explaining the structure of a blockchain node 200 in the prior art. As shown in FIG. 2, in the prior art, a blockchain node includes a verification module 201, a consensus module 202, an execution module 203, and a block module 204.

When the transaction data is received, the verification module 201 verifies the received transaction data. The verification module 201 may also have a buffer function, and multiple received transaction data may be queued in the verification module 201 for verification. The verification module 201 is used to verify whether the transaction data is legal. The verification operation performed by the verification module may be, for example, verifying whether the data structure of the transaction data meets the requirements of the corresponding blockchain system; whether the corresponding client has the ability to pay for the transaction procedures Fees (such as verifying the client’s account balance); whether the corresponding transaction is a repeated transaction (ie "double spend"); verifying whether the signature in the transaction data is legal; whether the size of the transaction data exceeds the maximum capacity of the block in the blockchain, etc. Wait. The verification module 201 can perform one or more of the verification operations. In different blockchain systems (such as the Bitcoin system, the Ethereum system, etc.), the verification operations performed by the verification module 201 may be different. The verification operation performed by the verification module 201 is not limited to the content listed here.

If the verification result of the verification module 201 on the transaction data is illegal, the transaction data may not be processed further. If the verification result is legal, the corresponding transaction data enters the consensus queue of the consensus module for consensus. The consensus module 202 executes the consensus operation on the blockchain node, and can broadcast transaction data to other blockchain nodes in the blockchain system to complete the consensus processing on the transaction data. Consensus processing can implement consensus based on consensus mechanisms such as Proof of Work (PoW) and Practical Byzantine Algorithm (PBFT). If other blockchain nodes do not recognize the transaction data after performing a consensus operation on the transaction data, they may not make any response. When each blockchain node recognizes that the transaction data is legal, it can return the consensus result of each blockchain node to the consensus module 202 of the blockchain node. The consensus module 202 can determine whether the transaction data reaches a consensus based on the consensus result of each blockchain node.

When the transaction data reaches a consensus among various blockchain nodes, the execution module 203 will execute the transaction data. The execution module may be a virtual machine module, such as the EVM in the Ethereum system. The execution operation can be the execution of a smart contract. The execution operation of the transaction data may be, for example, deducting the cost of executing the corresponding transaction from the balance of the client that initiated the transaction, and increasing the nonce in the sender’s account by 1 for the current transaction; in order to gain access to the corresponding transaction area Block chain nodes issue rewards, etc. As an example, the corresponding transaction may be a transfer transaction. At this time, when the transaction is executed, the corresponding money (for example, a predetermined amount of Bitcoin, Ether, etc.) will be deducted from the account of the initiator, and the transaction will be transferred to the account of the recipient Increase the corresponding amount. In different blockchain systems, the execution content of the execution module 203 for transactions may be different.

When the execution module 203 completes the execution operation, the block module 204 packages the transaction data of the transaction into a block, and sends it to the blockchain to perform the block chaining operation.

Fig. 3 is a schematic diagram for explaining a message sending process when a block chain node in the prior art is used to process transaction data. As shown in FIG. 3, when the client 301 initiates a transaction, at 320, the client sends the transaction data to the blockchain node 302. After the blockchain node verifies the legality of the transaction data, if the verification result is legal, at 320, the transaction data is broadcast to other blockchain nodes 303, 304, 305, and 306. After other blockchain nodes have reached a consensus on the transaction data, at 340, the consensus result is fed back to the blockchain node 302. Then, if the transaction data reaches a consensus among various blockchain nodes, the blockchain node 302 will perform transaction execution and block chaining operations.

After the client 301 sends the transaction data to the blockchain node 302, it may visit the blockchain node 302 at 350 after a predetermined time interval to obtain the blockchain processing status of the transaction initiated by it. If the client 301 frequently queries the blockchain processing status or multiple clients perform status queries at the same time, it may cause the blockchain node 302 to visit too much and become overloaded, which may cause the efficiency of blockchain processing for transaction data. Decline, or the blockchain node may fail due to overload.

FIG. 4 is a structural block diagram of a blockchain node 400 according to an embodiment of the present disclosure. As shown in FIG. 4, the blockchain node 400 includes a blockchain processing unit 410, a transaction data processing device 420, and a non-volatile memory 430. Among them, the non-volatile memory 430 is not an essential component. In another example, the blockchain node may not include the non-volatile memory.

The blockchain processing unit 410 is configured to perform blockchain processing on transaction data. The blockchain processing unit 410 may include various modules of the blockchain node in the prior art as shown in FIG. 2. As shown in FIG. 4, the blockchain node includes a verification module 411, a consensus module 412, an execution module 413, and a block module 414. The operations performed by each module are the same as each functional module of the blockchain node in the prior art.

FIG. 5 is a structural block diagram of a transaction data processing device 420 suitable for the blockchain node 400 shown in FIG. 4. As shown in FIG. 4, the transaction data processing device 420 includes a transaction data sending unit 421, a processing status information acquiring unit 422, a processing status update unit 423, a processing status information sending unit 424, a data current limiting unit 425, a storage unit 426, and transaction data. Delete unit 427 and broadcasting unit 428. It should be noted that, among the units shown in FIG. 5, the processing status information sending unit, the data current limiting unit, the storage unit, the transaction data deletion unit, and the broadcasting unit are not necessary constituent elements. In other examples of the present disclosure, these unnecessary constituent elements may not be included, and one or more of them may also be included.

After the transaction data is sent to the blockchain node 400, the transaction data processing device 420 waits for the blockchain processing unit 410 to perform blockchain processing on it. The transaction data sending unit 421 is configured to send the received at least one transaction data to the blockchain processing unit 410 for corresponding blockchain processing after receiving at least one transaction data, and the transaction data has a state description field. The status description field is used to describe the blockchain processing status of the transaction data. The blockchain processing status can include: pending verification (waiting for verification by the verification module 411), completed verification (verification processing by the verification module 411), pending consensus (Verified lawful and waiting for consensus processing), Consensus completed (Consensus processing has been passed), Pending execution (Consensus reached a consensus and waiting to be executed), Execution completed (Execution of the execution module has been performed), Waiting for the block to be chained and completed Block chain and so on. In another example, the transaction processing status indicated by the status description field may include pending verification, pending consensus, pending execution, pending block uploading, completing block uploading, and so on.

Pending transaction data refers to the transaction data whose status description field has not been updated to complete the blockchain. When the transaction data has been completed on the blockchain, the blockchain processing for the transaction data has ended, so there is no need to process it again. Before the status of the transaction data is updated to complete the block chaining, the transaction data still needs to be processed.

Transaction data can also include transaction content, the node where the transaction arrives, transaction serial number and business ID, etc. Transaction content is used to describe the specific content of the transaction, such as the initiator of the transaction (such as a transfer transaction), the recipient of the transaction, the transaction amount, and the transaction summary. The transaction serial number indicates the corresponding serial number of the exchange initiated by the client that initiated the transaction. The business ID represents the serial number of the transaction in the corresponding blockchain system.

After the transaction data to be processed is sent to the blockchain processing unit, the state description field of the transaction data is stored in the transaction data processing device 420. After each module of the blockchain processing unit performs corresponding processing on the transaction data, it can The processing state information of the transaction data is sent to the transaction data processing device 420 for updating the state description field of the corresponding transaction data.

At this time, the processing state information acquiring unit 422 is configured to acquire corresponding blockchain processing state information for each transaction data from the blockchain processing unit 410. In an example, each module in the blockchain processing unit 410 can be connected to the processing state information acquisition unit 422 of the transaction data processing device 420 through a state machine interface, so that the transaction processing device can be updated based on the state machine mechanism through the state machine interface The state description field of each transaction data in.

For each transaction data in at least one transaction data, when receiving the blockchain processing status information of the corresponding transaction processing data, the processing status update unit 423 uses the received blockchain processing status information to update the status description of the transaction data Field for at least one related party of transaction data to perform status query. The related party of the transaction data can be, for example, the client that initiates the corresponding transaction, or can be various functional modules of the blockchain processing unit.

FIG. 6 is a schematic diagram for explaining the message sending process when using the blockchain node of the present disclosure to process transaction data. As shown in FIG. 6, at 610, the client 601 sends transaction data to the transaction processing device 602a of the blockchain node 602. The transaction processing device may be the transaction processing device described above with reference to FIG. 45 and FIG. 5. Then at 620, the transaction processing device 602a in the blockchain node 602 sends the data to be processed to the blockchain processing unit 602b in the blockchain node 602.

After the received transaction data to be processed is verified to be legal, the blockchain processing unit 602b broadcasts the verified transaction data to other blockchain nodes 603, 604, 605, and 606 at 630 to perform consensus processing on the transaction data . Then at 640, each blockchain node feeds back the consensus result to the blockchain node 602.

In the process of performing blockchain processing on transaction data, at 650, the blockchain processing unit 602b sends the blockchain processing status information of each transaction data to the transaction processing device 602a. Thus, the transaction processing device 602a can send the blockchain state information of the transaction data to the client at 660. Alternatively, at 670, the client can access the transaction processing device 602a to obtain the blockchain processing status information of the transaction data.

Therefore, the related party of the transaction data (for example, the client that initiates the corresponding transaction) can query the status of the transaction data without accessing the blockchain processing unit 410, and thus will not send the blockchain processing unit 410 to the blockchain processing unit 410 due to the query operation of the client. Bring extra load. In addition, because the related party only needs to access the transaction data processing device 420 to obtain the status of the transaction data, and does not need to query the various functional modules of the blockchain processing unit 410 one by one, the path of the status query can be shortened and improved. The client obtains the efficiency of the blockchain processing state information.

In addition, when the related party is a non-local related party such as a client that initiates a transaction, the cost of establishing a communication connection between the non-local related party and the blockchain node is higher and consumes more resources, which will further increase the access load and Access cost. The communication between the transaction data processing device 420 and the blockchain processing unit 410 is local communication, so the communication cost and the access load caused by it are low. Therefore, this example can also save communication resources and reduce the overall load of blockchain nodes.

After the blockchain processing status of each transaction data is updated, each transaction related party can access the transaction processing device to query the blockchain processing status as described above, or the processing status information sending unit 424 can periodically update at least the updated at least The blockchain processing status information of one transaction data is sent to the related party of the at least one transaction data. When regularly sending blockchain processing status information to related parties of transaction data, the load of the transaction processing device can be distributed to various time periods. As a result, it is possible to avoid the occurrence of multiple related parties simultaneously querying the processing status of the blockchain, which may cause excessive transient load. It should be noted that the "regular" is not limited to the "fixed period". In an example, the transmission time of the blockchain processing status information can also be selected according to the load status of the transaction data processing device 420. The blockchain processing status information may be sent when the load (for example, resource occupancy rate) of the transaction data processing device 420 does not exceed a predetermined load.

In an example, the related party of the transaction data may also send a status query request to the transaction data processing device 420. In this example, the processing status information sending unit 424 may also be configured to send the blockchain processing status information of the corresponding transaction data to the associated party in response to the status query request of the associated party.

After the transaction data to be processed sent to the blockchain processing unit 420 is verified by the verification module 411, the consensus module 412 will perform a consensus operation on it. If there is more than one transaction data waiting for consensus, the transaction data to be processed will enter the consensus queue and wait for consensus. If the consensus queue is full, the pending transaction data may be lost due to the inability to perform the consensus queue.

In order to prevent data loss due to the full consensus queue, in the example shown in FIG. 5, a data current limiting unit 425 is configured. The data current limiting unit 425 is configured to determine whether the transaction data to be processed sent to the blockchain processing unit 410 exceeds the current limiting threshold. When it is determined that the transaction data to be processed sent to the blockchain processing unit exceeds the current limit threshold, the transaction data sending unit 421 is configured to stop sending the transaction data to be processed to the blockchain processing unit 410.

The current limit threshold can be determined based on the amount of transaction data, or it can be determined based on the data capacity occupied by the transaction data. For example, the current limit threshold may be the upper limit of the amount of transaction data to be processed sent to the blockchain processing unit 410 within a predetermined time period, or it may be the total amount of transaction data to be processed sent to the blockchain processing unit 410 within a predetermined time period. Maximum data capacity.

The current limit threshold may be determined based on the processing queue size of the blockchain processing unit, the maximum business volume per unit time, and the consensus state. The current limit threshold can be set to be adjustable in real time. The processing queue may be, for example, the size of the consensus queue of the consensus module. The consensus state refers to the state between each block chain node in the block chain system.

Different consensus algorithms have different consensus states. For example, for BFT consensus algorithms, the consensus state includes an initial state (init), a normal state (normal case), a view change state (viewchange), and a recovery state (recovery). Non-BFT consensus algorithms include initial state (init), normal state (normal case), and recovery state (recovery). Only when the consensus state is a normal case can the consensus processing be performed normally. Taking the PBFT algorithm as an example, PBFT includes three stages in the normal state: Pre-Prepare, Prepare, and Commit. In the Normal Case state, the amount of transaction data that can currently be processed can be determined according to the size of the consensus queue. However, whether the blockchain processing unit can receive transaction data is determined according to the consensus state. For example, when the consensus state of a blockchain node is the viewchange state, consensus cannot be carried out. If the amount of transaction data in the consensus queue has reached 2/3 of the consensus queue and the current consensus state is the viewchange state, the blockchain processing unit cannot accept the transaction data.

In addition, if the blockchain processing unit 410 fails, the transaction data will also be lost. In the prior art, when the transaction data is lost, the client is required to resend the transaction data, which is very unfriendly to the client. And the re-sent transaction data needs to go through the blockchain processing operation again from the verification process, which further leads to the waste of blockchain node resources.

Thus, the storage unit 426 is configured in the example in the present disclosure. The storage unit 426 is configured to buffer at least one transaction data received. By buffering the received transaction data locally, when the transaction data is lost due to the consensus queue being full, the blockchain processing unit 410 malfunctions, etc., the blockchain processing unit 410 can obtain the transaction data from the transaction data processing device 420 , Without the need for the client to send transaction data again. In addition, since the transaction data stored in the transaction data processing unit has a state description field, when the blockchain processing unit 410 obtains the transaction data from the storage module of the transaction data processing device 420 again, it can also know which transaction data has been processed. , So there is no need to re-experience all the blockchain processing from the verification process. Therefore, the resources of the blockchain processing unit 420 can also be saved.

In the present disclosure, "caching" refers to storing data in volatile memory, for example, in the memory of a computing device.

In addition, in an example, the storage unit 426 may also store part or all of the cached transaction data in the non-volatile memory 430 (as shown in FIG. 4) when the amount of the cached transaction data exceeds the storage threshold. . When the number of buffered transaction data exceeds the storage threshold, the storage unit may also store the newly received transaction data in the non-volatile memory 430. As a result, when the storage space of the transaction data processing device 420 is free, transaction data can be read from the non-volatile memory for processing, thereby avoiding data loss due to the storage space exceeding the storage threshold and causing the client to repeatedly send transactions. data.

In order to clear the transaction data stored in the transaction data processing device 420 in time, the transaction data deletion unit 427 may be used to perform deletion processing. The transaction data deletion unit 427 is configured to delete the transaction data when the state description field of the transaction data is updated to complete the block chaining after a predetermined period of time has passed for each stored transaction data. When the transaction data is completed on the blockchain, it means that the transaction data has been processed on the blockchain. At this time, it is no longer necessary for the blockchain node to continue to retain the transaction data. However, it is necessary to reserve a predetermined period of time for the related party (for example, the client) of the transaction data to obtain the blockchain processing status of the corresponding transaction data. Within the reserved predetermined time period, the related party can actively query the blockchain processing status or the transaction data processing device 420 can send the blockchain processing status to the related party. After the predetermined time period has elapsed, it can be assumed that the related party has obtained the blockchain processing status, so the corresponding transaction data can be deleted to avoid the transaction data that has completed the blockchain processing from continuously occupying storage space.

As mentioned above, the transaction data is broadcast by the consensus module to other blockchain nodes for consensus processing after being verified by the verification module. If the blockchain node fails, the consensus module may not be able to broadcast transaction data to other nodes smoothly. Therefore, the broadcasting unit 428 can be used for each transaction data stored, when the state description field of the transaction data is updated to complete the verification and is not updated to complete the consensus after the second predetermined time, the transaction data Broadcast to other blockchain nodes. If the state description field of the transaction data is updated to complete the verification and has not been updated to complete the consensus for a long time, it can be inferred that the blockchain processing unit has failed or the transaction data in the blockchain processing unit has been lost. The transaction data processing device 420 has a broadcasting unit 428 to broadcast the corresponding transaction data.

Fig. 7 is a flowchart of a method for processing transaction data at a blockchain node according to an embodiment of the present disclosure.

As shown in FIG. 7, in block 720, after receiving at least one transaction data, the received at least one transaction data is sent to the blockchain processing unit for corresponding blockchain processing, and the transaction data has a status Description field.

The blockchain processing unit can send the blockchain processing status information of the transaction data in the process of blockchain processing the transaction data. Therefore, the method may obtain corresponding blockchain processing state information for each transaction data from the blockchain processing unit at block 740.

After obtaining the corresponding blockchain processing status information, in block 760, for each transaction data in at least one transaction data, use the received blockchain processing status information to update the status description field of the transaction data for at least A related party of transaction data to perform status query.

Fig. 8 is a flowchart for explaining an application scenario of a method for processing transaction data at a blockchain node according to an embodiment of the present disclosure. As shown in FIG. 8, the method for processing transaction data at a blockchain node in this example can be executed by a transaction data processing device.

As shown in Figure 8, at 802, the client that initiated the transaction sends the transaction data to the transaction data processing device of the blockchain node. When the transaction data processing device receives the transaction data, in 804, the received transaction data is buffered. And at 806, it is determined whether the buffered transaction data exceeds the storage threshold. When the buffered transaction data exceeds the storage threshold, at 808, the transaction data processing device stores the buffered transaction data in the non-volatile memory.

In addition, although not shown in FIG. 8, when the buffered transaction data exceeds the storage threshold, the method of the present disclosure may store part or all of the buffered transaction data in a non-volatile memory. In another example, for each transaction data stored, the transaction data may be deleted when the state description field of the transaction data is updated to complete the block chaining after a predetermined period of time has passed.

In the process of sending the transaction data to be processed to the blockchain processing unit, it may be determined at 810 whether the transaction data to be processed sent to the blockchain processing unit exceeds the current limit threshold. The amount of transaction data to be processed to be sent to the blockchain processing unit may be determined based on the first predetermined time period, and it may be determined whether the amount exceeds the current limit threshold. When the transaction data to be processed sent to the blockchain processing unit exceeds the current limit threshold, stop sending the transaction data to be processed to the blockchain processing unit. Then, after the second predetermined period of time has passed, it can be determined again whether the sent transaction data to be processed exceeds the current limit threshold, and if it still exceeds the current limit threshold, continue to wait. When it is determined that the transaction data to be processed sent to the blockchain processing unit does not exceed the current limit threshold, at 812, the transaction data to be processed is sent to the blockchain processing unit. The current limit threshold may be determined based on the processing queue size of the blockchain processing unit, the maximum business volume per unit time, and the consensus state. For example, the maximum or minimum of the processing queue size, the maximum business volume per unit time, and the number of transactions in the pending consensus state can be selected as the current limit threshold.

After receiving the transaction data to be processed, the blockchain processing unit performs blockchain processing operations such as verification and consensus on the transaction data to be processed, and during the processing, at 814, the blockchain processing status information of the transaction data is sent to the transaction Data processing device. At 816, the transaction data processing device may receive blockchain processing status information. Then, at 818, when the blockchain processing status information for the transaction data is received, the received blockchain processing status information is used to update the status description field of the corresponding transaction data.

The updated blockchain processing status information can be queried by the related parties of the transaction data (for example, the client that initiates the corresponding transaction), or it can be periodically sent by the transaction processing device to the related parties of the transaction data. As shown in FIG. 8, at 820, it is determined whether the status transmission period has expired. When the status sending period expires, at 822, the blockchain processing status information of the transaction data is sent to the client that initiated the corresponding transaction. It should be noted that the “periodical” or “status transmission period” is not necessarily a fixed period, and it may also be a variable time period. The client can also send a status query request to the transaction processing device at 824. Therefore, in 826, the transaction processing device may send the blockchain state information of the corresponding transaction data to the client in response to the client's state query request.

In addition, in block 828, for each of the cached transaction data, it is also possible to determine whether the predetermined time has passed after the block chain status information of the transaction data is updated to complete the verification. If the predetermined time has passed, then at 830, it is determined whether the blockchain status information updated to complete the consensus is received. If the state description field of the transaction data is updated to complete the verification and is not updated to complete the consensus after the second predetermined time has elapsed, then at 832, the transaction data is broadcast to other blockchain nodes.

It should be noted that in the flow of the method for processing transaction data at a blockchain node shown in FIG. 8, some operations are not mandatory operations. For example, in other examples, operations 804 to 808 may not be performed, and in some examples, operations 810 may not be performed. In practice, certain operations can be omitted according to practical needs.

Above, referring to FIGS. 1 to 8, the embodiments of the method and device for processing transaction data at a blockchain node according to the present disclosure have been described. The details mentioned in the above description of the method embodiment are also applicable to the embodiment of the device of the present disclosure.

The device for processing transaction data at a blockchain node of the present disclosure can be implemented by hardware, or by software or a combination of hardware and software. The details mentioned in the above description of the method embodiment are also applicable to the embodiment of the device of the present disclosure. The various embodiments in this specification are described in a progressive manner, and the same or similar parts among the various embodiments are referred to each other.

The device for processing transaction data at a blockchain node of the present disclosure can be implemented by hardware, or by software or a combination of hardware and software. Taking software implementation as an example, as a logical device, it is formed by reading the corresponding computer program instructions in the memory into the memory through the processor of the device where it is located. In the present disclosure, the device for processing transaction data at a blockchain node can be implemented by using a computing device, for example.

Fig. 9 is a structural block diagram of a computing device for implementing a method for processing transaction data at a blockchain node according to an embodiment of the present disclosure. As shown in FIG. 9, the computing device 900 includes a processor 910, a memory 920, a memory 930, a communication interface 940, and an internal bus 950. According to an embodiment, the computing device 900 may include at least one processor 910 that executes at least one computer-readable instruction (ie, the aforementioned Elements implemented in software).

In one embodiment, computer-executable instructions are stored in the memory 920, which when executed, cause at least one processor 910 to: after receiving at least one transaction data, send the received at least one transaction data to the area The block chain processing unit performs the corresponding block chain processing, and the transaction data has a state description field; obtains the corresponding block chain processing state information for each transaction data from the block chain processing unit; and for each transaction in at least one transaction data Data, using the received blockchain processing status information to update the status description field of the transaction data, so that at least one related party of the transaction data can perform status query.

It should be understood that the computer-executable instructions stored in the memory 920, when executed, cause at least one processor 610 to perform various operations and functions described above in conjunction with FIGS. 1-8 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. The non-transitory machine-readable medium may have instructions (ie, the above-mentioned elements implemented in the form of software), which when executed by a machine, cause the machine to execute the various embodiments described above in conjunction with FIGS. 1-8 in the various embodiments of the present disclosure. Operation and function.

Specifically, a system or device equipped with a readable storage medium may be provided, and the software program code for realizing the function of any one of the above-mentioned embodiments is stored on the readable storage medium, and the computer or device of the system or device The processor reads and executes the instructions stored in the readable storage medium.

In this case, the program code itself read from the readable medium can realize the function of any one of the above embodiments, so the machine readable code and the readable storage medium storing the machine readable code constitute the present invention a part of.

Examples of readable storage media include floppy disks, hard disks, magneto-optical disks, optical disks (such as CD-ROM, CD-R, CD-RW, DVD-ROM, DVD-RAM, DVD-RW, DVD-RW), magnetic tape, Volatile memory card and ROM. Alternatively, the program code can be downloaded from a server computer or cloud via a communication network.

The foregoing describes specific embodiments of this specification. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps described in the claims may be performed in a different order than in the embodiments and still achieve desired results. In addition, the processes depicted in the drawings do not necessarily require the specific order or sequential order shown in order to achieve the desired results. In some embodiments, multitasking and parallel processing are also possible or may be advantageous.

Not all steps and units in the above processes and system structure diagrams are necessary, and some steps or units can be omitted according to actual needs. The order of execution of each step is not fixed and can be determined as needed. The device structure described in the foregoing embodiments may be a physical structure or a logical structure, that is, some units may be implemented by the same physical entity, or some units may be implemented by multiple physical entities, or may be implemented by multiple physical entities. Some components in independent devices are implemented together.

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. For the purpose of providing an understanding of the described technology, the detailed description includes specific details. However, these techniques can be implemented without these specific details. In some instances, in order to avoid incomprehensibility to the concepts of the described embodiments, well-known structures and devices are shown in the form of block diagrams.

The optional implementations of the embodiments of the present disclosure are described in detail above with reference to the accompanying drawings. However, the embodiments of the present disclosure are not limited to the specific details in the above-mentioned implementation manners. Within the scope of the technical concept of the embodiments of the present disclosure, the present disclosure can be modified. The technical solutions of the disclosed embodiments are subjected to a variety of simple modifications, and these simple modifications all fall within the protection scope of the embodiments of the present disclosure.

The foregoing description of the present disclosure is provided to enable any person of ordinary skill in the art to implement or use the present disclosure. For those of ordinary skill in the art, various modifications to the present disclosure are obvious, and the general principles defined herein can also be applied to other modifications without departing from the scope of protection of the present disclosure. . Therefore, the present disclosure is not limited to the examples and designs described herein, but is consistent with the widest scope that conforms to the principles and novel features disclosed herein.

Claims

A method for processing transaction data at a block chain node, the block chain node includes a block chain processing unit, and the method includes:

After receiving at least one transaction data, sending the received at least one transaction data to the blockchain processing unit for corresponding blockchain processing, where the transaction data has a state description field;

Obtain corresponding blockchain processing state information for each transaction data from the blockchain processing unit; and

For each transaction data in the at least one transaction data, the received block chain processing status information is used to update the status description field of the transaction data, so that the associated parties of the at least one transaction data can perform status query.
The method of claim 1, further comprising:

The updated blockchain processing status information of the at least one transaction data is sent to the related party of the at least one transaction data on a regular basis.
The method of claim 1, further comprising:

In response to the status query request of the at least one related party of transaction data, the blockchain processing status information of the at least one transaction data is sent to the related party.
The method of claim 1, further comprising:

When the transaction data to be processed sent to the blockchain processing unit exceeds the current limit threshold, stop sending the transaction data to be processed to the blockchain processing unit.
The method of claim 4, wherein the current limit threshold is determined based on the processing queue size of the blockchain processing unit, the maximum business volume per unit time, and the consensus state.
The method of claim 1, further comprising:

At least one transaction data received is cached.
The method of claim 6, further comprising:

When the number of cached transaction data exceeds the storage threshold, some or all of the cached transaction data is stored in the non-volatile memory.
The method of claim 6 or 7, further comprising:

For each transaction data that is cached, the transaction data is deleted when the state description field of the transaction data is updated to complete the block chaining after a predetermined period of time has passed.
The method of claim 6 or 7, further comprising:

For each transaction data cached, when the state description field of the transaction data is updated to be not updated to complete the consensus after the second predetermined time has passed after the verification is completed, the transaction data is broadcast to other blockchain nodes.
A device for processing transaction data at a block chain node, the block chain node includes a block chain processing unit, and the device includes:

The transaction data sending unit is configured to, after receiving at least one transaction data, send the received at least one transaction data to the blockchain processing unit for corresponding blockchain processing, and the transaction data has a status Description field

A processing state information acquiring unit configured to acquire corresponding blockchain processing state information for each transaction data from the blockchain processing unit; and

The processing status update unit is configured to use the received block chain processing status information to update the status description field of the transaction data for each transaction data in the at least one transaction data, so as to provide for the at least one transaction data Related parties to perform status inquiries.
The device of claim 10, further comprising:

The processing status information sending unit is configured to periodically send the updated blockchain processing status information of the at least one transaction data to the associated party of the at least one transaction data.
The device of claim 10, further comprising:

The processing status information sending unit is configured to respond to the status query message of the at least one transaction data related party to send the blockchain processing status information of the at least one transaction data to the related party.
The device of claim 10, further comprising:

The data current limiting unit is configured to determine whether the transaction data to be processed sent to the blockchain processing unit exceeds the current limiting threshold,

The transaction data sending unit is configured to stop sending the transaction data to be processed to the blockchain processing unit when it is determined that the transaction data to be processed sent to the blockchain processing unit exceeds the current limit threshold.
The device of claim 10, further comprising:

The storage unit is configured to store the received at least one transaction data in a cache.
The apparatus of claim 14, wherein the storage unit is further configured to store part or all of the cached transaction data in the non-volatile memory when the amount of the cached transaction data exceeds a storage threshold.
The device according to claim 14 or 15, further comprising:

The transaction data deletion unit is configured to delete the transaction data when the state description field of the transaction data is updated to complete the block chaining after a predetermined period of time has elapsed for each cached transaction data.
The device according to claim 14 or 15, further comprising:

The broadcasting unit is configured to broadcast the transaction data to other areas when the state description field of the transaction data is updated to complete the verification after the second predetermined time has passed after the verification is completed. Block chain node.
A computing device including:

At least one processor; and

A memory, where the memory stores instructions, and when the instructions are executed by the at least one processor, the at least one processor executes the method according to any one of claims 1 to 9.
A non-transitory machine-readable storage medium that stores executable instructions that, when executed, cause the machine to execute the method according to any one of claims 1 to 9.