Block chain concurrent transaction processing method and device, equipment and storage medium

Abstract

The invention provides a block chain concurrent transaction processing method and device, equipment and a storage medium, and relates to the technical field of transaction concurrent processing. The method comprises the following steps: performing transaction simulation execution on a plurality of concurrent target transactions, respectively generating read-write sets corresponding to the plurality of target transactions, and sorting the read-write sets according to business partition IDs to which the transactions belong and read-write set key relevance to obtain a first target transaction read-write set; and packaging and chaining the read-write sets in the first target transaction read-write set in sequence, and in the packaging and chaining process, performing version number synchronization processing on the read-write sets with the read-write set key relevance according to the version number of the updated service partition when the last read-write set finishes packaging and chaining in sequence. According to the method, version number synchronization is carried out on the execution results of the concurrent transactions, so that the read set version numbers of the multiple concurrent target transactions are consistent with the version number of the latest service partition, the success rate of the transactions is improved, and the processing efficiency of the nodes on the concurrent transactions can be effectively improved.

Description

Technical Field

[0001] The present invention relates to the technical field of concurrent transaction processing, and in particular to a blockchain concurrent transaction processing method, apparatus, device, and storage medium. Background Art

[0002] Blockchain technology is built on a transmission network (also known as a blockchain network), where distributed node devices (hereinafter referred to as nodes) run blockchain programs. Currently, its applications have expanded to various fields, including the Internet of Things, smart manufacturing, supply chain management, and digital asset trading.

[0003] Currently, when users conduct transactions based on blockchain technology, they first submit the transaction to the blockchain from the user's end. This transaction is then collected and simulated by the endorsing nodes in the business partition. During this simulated execution, a read-write set is generated, containing the read-set version number of the current transaction. After the simulated execution is complete, the endorsing node signs the read-write set and submits the transaction containing the simulated execution results to the master node for verification. During transaction verification, the read-set version number is checked to ensure it matches the world state version number in the blockchain network. If the version numbers match, the transaction is verified successfully, and the world state is updated. If the version numbers differ, the transaction fails.

[0004] However, when the current endorsement node processes transactions, there may be situations where multiple transactions need to be processed concurrently. Since multiple transactions are carried out simultaneously, when the transaction packages are submitted to the master node, the read set version numbers carried by multiple concurrent transactions are the same. This will cause the master node to successfully verify the first transaction, but the read set version numbers of subsequent concurrent transactions will be inconsistent with the version number of the latest world state. This will cause subsequent concurrent transaction verification to fail, and ultimately only some transactions can be successfully executed and uploaded to the chain, which is inefficient for processing concurrent transactions. Summary of the Invention

[0005] The purpose of the embodiments of the present invention is to provide a blockchain concurrent transaction processing method, device, equipment and storage medium to solve the problem that existing blockchain technology has low efficiency in concurrent transaction processing.

[0006] The specific technical solutions of the present invention are as follows: In a first aspect of an embodiment of the present invention, a blockchain concurrent transaction processing method is provided, which is applied to a transaction collection simulation execution node designated by a master node, comprising: Obtain multiple target transactions concurrently submitted to the blockchain, each of which carries a business partition ID and a version number of the business partition in which the target transaction resides; Perform transaction simulation on multiple target transactions, generate read-write sets corresponding to the multiple target transactions, and sort the read-write sets corresponding to the multiple target transactions according to the association between the business partition ID of the transaction and the read-write set key to obtain the first target transaction read-write set; The read-write sets in the first target transaction read-write set are encapsulated and uploaded to the chain in sequence. During the encapsulation and chaining process, the version numbers of the read-write sets associated with the read-write set key are synchronized according to the version number of the business partition updated when the previous read-write set is encapsulated and uploaded to the chain.

[0007] Furthermore, the obtaining of multiple target transactions concurrently submitted to the blockchain includes: Collecting transaction requests for multiple target transactions submitted by the user to the blockchain by the client within the same transaction time period; wherein the blockchain is provided with at least two relatively independent business partitions, each of which has a corresponding partition ledger, and the blockchain as a whole has a global ledger, which maintains the version number of the business partition in which the target transaction is located; Perform signature verification on the transaction signatures of multiple target transactions respectively. After the signature verification is passed, perform data analysis on each transaction request to obtain the business partition ID corresponding to the transaction request and the version number of the business partition where the target transaction is located.

[0008] Furthermore, the transaction simulation execution is performed on the multiple target transactions to generate read-write sets corresponding to the multiple target transactions respectively, and the read-write sets corresponding to the multiple target transactions are sorted according to the business partition ID to which the transaction belongs and the association between the read-write set key to obtain the first target transaction read-write set, including: Execute multiple target transactions in a simulated manner according to the order in which they were collected, and obtain a read-write set of the multiple target transactions; The read-write sets of multiple target transactions are partitioned and sorted according to the business partition ID, and the read-write sets of the target transactions are associated and sorted according to the read-write set key association in the partitioned read-write sets to obtain the first target transaction read-write set.

[0009] Furthermore, the read-write sets in the first target transaction read-write set are sequentially encapsulated and uploaded to the chain, and during the encapsulation and uploading process, the version numbers of the read-write sets associated with the read-write set key are synchronized in accordance with the version number of the business partition updated when the previous read-write set is encapsulated and uploaded to the chain, including: Sequentially sign and encapsulate the read-write sets of multiple target transactions in the first target transaction read-write set and upload them to the chain. When encapsulating and uploading to the chain, first sign and encapsulate the read-write set of the current target transaction and upload it to the chain; Then, obtain the version number of the business partition updated after the current target transaction is on-chain, and synchronize the read-write set version number of the next read-write set associated with the read-write set key; After the next read-write set associated with the read-write set key completes read-write set version number synchronization, the next read-write set associated with the read-write set key is signed and packaged and uploaded to the chain. Similarly, the read-write set signatures and packaged uploads for all target transactions in the first target transaction set are completed.

[0010] Furthermore, the process of obtaining the version number of the updated business partition after the current target transaction is completed on the chain and synchronizing the read-write set version number of the next read-write set associated with the read-write set key includes: Submit the current target transaction to the Master node for transaction verification. After the Master node updates the version number based on the transaction verification result, obtain the updated version number of the business partition. The version number of the updated business partition is compared with the read-write set version number of the next read-write set associated with the read-write set key. If the two version numbers are consistent, the read-set version number synchronization is completed. If the two version numbers are inconsistent, the version number of the updated business partition is used as the read-set version number of the next read-write set associated with the read-write set key.

[0011] In a second aspect, the present application provides a blockchain concurrent transaction processing device, which is applied to a transaction collection simulation execution node designated by a Master node, including: A transaction collection module is used to obtain multiple target transactions concurrently submitted to the blockchain, each of which carries a business partition ID and a version number of the business partition in which the target transaction resides; A transaction simulation execution module is used to perform transaction simulation execution on multiple target transactions, generate read-write sets corresponding to the multiple target transactions, and sort the read-write sets corresponding to the multiple target transactions according to the association between the business partition ID of the transaction and the read-write set key to obtain the first target transaction read-write set; The transaction encapsulation and chain-up module is used to encapsulate and chain-up the read-write sets in the first target transaction read-write set in sequence, and during the encapsulation and chain-up process, synchronize the version numbers of the read-write sets with the read-write set key association according to the version number of the business partition updated when the previous read-write set is encapsulated and chain-up.

[0012] In a third aspect, an embodiment of the present invention further provides an electronic device, including: one or more processors; A storage device for storing one or more programs, which, when executed by the one or more processors, enables the one or more processors to implement the blockchain concurrent transaction processing method described in the first aspect.

[0013] In a fourth aspect, an embodiment of the present invention further provides a computer-readable medium having a computer program stored thereon, which, when executed by a processor, implements the blockchain concurrent transaction processing method described in the first aspect.

[0014] The beneficial effects of the present invention are as follows: the method first sorts and groups multiple target transactions according to the business partition ID and the read-write set key correlation to obtain the first target transaction read-write set, ensuring that when the target transaction is subsequently processed, the visibility of the business partition version number can be guaranteed, and the success rate of chain upload in the case of read-write set key conflicts is improved. Then, the target transaction read-write sets in the first target transaction set are encapsulated and chain uploaded in sequence, and in the process of encapsulation and chain upload, the execution result of the next target transaction is synchronized with the version number of the business partition updated when the previous target transaction is completed and encapsulated and chain uploaded, so that the read set version number of the concurrent multiple target transactions is consistent with the version number of the latest business partition, thereby improving the success rate of the transaction and effectively improving the node's processing efficiency for concurrent transactions. BRIEF DESCRIPTION OF THE DRAWINGS

[0015] To more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the following briefly introduces the drawings required for use in the embodiments or the description of the prior art. Obviously, the drawings described below are only some embodiments of the present invention, and those skilled in the art can derive other drawings based on these drawings without inventive effort.

[0016] Figure 1 This is a flow chart of a blockchain concurrent transaction processing method proposed in one embodiment of the present invention; Figure 2 This is a schematic diagram of the module structure of a blockchain concurrent transaction processing device proposed in one embodiment of the present invention. DETAILED DESCRIPTION

[0017] The following will provide a clear and complete description of the technical solutions in the embodiments of the present invention in conjunction with the accompanying drawings. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of them. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without making any creative efforts are within the scope of protection of the present invention.

[0018] Example 1: Figure 1 This is a flowchart of a blockchain concurrent transaction processing method proposed in one embodiment of the present invention, which is applied to the transaction collection simulation execution node designated by the Master node. Figure 1 As shown, the blockchain concurrent transaction processing method according to the embodiment of the present invention mainly includes the following steps: S1: Obtain multiple target transactions concurrently submitted to the blockchain, each of which carries a business partition ID and a version number of the business partition in which the target transaction resides; S2: Perform transaction simulations on multiple target transactions to generate read-write sets corresponding to the multiple target transactions. These read-write sets are sorted according to the association between the business partition IDs of the transactions and the read-write set keys to obtain the first target transaction read-write set. S3: The read-write sets in the first target transaction read-write set are encapsulated and uploaded to the chain in sequence. During the encapsulation and uploading process, the version numbers of the read-write sets associated with the read-write set key are synchronized according to the version number of the business partition updated when the previous read-write set is encapsulated and uploaded to the chain.

[0019] The blockchain network used in this invention includes accounting nodes (ANs), infrastructure nodes (INs), and master nodes. The master node is the master node of the IN node. The transaction collection and simulation execution node is an AN node designated by the master node. This node has the authority to collect transactions and simulate transaction execution.

[0020] Furthermore, in one embodiment, obtaining multiple target transactions concurrently submitted to the blockchain in step S1 of the present invention includes but is not limited to the following sub-steps: S11. Collect transaction requests for multiple target transactions submitted by users to the blockchain via the client within the same transaction time period. The blockchain is configured with at least two relatively independent business zones, each with its own zoned ledger. The blockchain as a whole maintains a global ledger, which maintains the version number of the target transaction in the zone. When users in each zone submit transactions via the client, each transaction carries the corresponding zone ID and the zone version number of the exchange. Upon submission, the transaction data is cryptographically signed to prevent tampering. Furthermore, transaction data can be collected and submitted in a predefined format, such as XML or JSON, depending on the specific circumstances.

[0021] S12. Perform signature verification on the transaction signatures of multiple target transactions respectively. After the signature verification is passed, perform data analysis on each transaction request to obtain the business partition ID corresponding to the transaction request and the version number of the business partition where the target transaction is located.

[0022] The embodiment of the present invention collects and organizes target transactions on the blockchain within the same time period through a transaction collection simulation execution node, and obtains information such as the business partition ID and business partition version number from these target transactions, so as to facilitate subsequent version number synchronization and ensure the consistency of the business partition version number.

[0023] Furthermore, in one embodiment, in step S2 of the present invention, transaction simulation execution is performed on multiple target transactions, read-write sets corresponding to the multiple target transactions are generated respectively, and the read-write sets corresponding to the multiple target transactions are sorted according to the business partition ID to which the transaction belongs and the association between the read-write set key to obtain a first target transaction read-write set, including but not limited to the following sub-steps: S21: Execute transaction simulations on multiple target transactions in the order in which they were collected, and obtain read-write sets of the multiple target transactions; S22: partition and sort the read-write sets of multiple target transactions according to the business partition ID, and associate and sort the read-write sets of the target transactions according to the read-write set key association in the partition-sorted read-write sets to obtain the first target transaction read-write set.

[0024] Among them, the business partition ID can indicate the business partition where the transaction occurs. Therefore, during the simulation execution process, the embodiment of the present invention can partition and sort multiple target transactions according to the correlation between the business partition ID and the read-write set key, thereby ensuring that the business partition version number of the target transaction occurring earlier can be seen by the subsequent target transaction, thereby improving the success rate of transactions on the chain in the case of read-write set key conflicts.

[0025] Furthermore, in one embodiment, in step S3 of the embodiment of the present invention, the read-write sets in the first target transaction read-write set are sequentially encapsulated and uploaded to the chain. During the encapsulation and uploading process, the version numbers of the read-write sets associated with the read-write set key are synchronized in accordance with the version number of the business partition updated when the previous read-write set is encapsulated and uploaded to the chain, including but not limited to the following sub-steps: S31. Sequentially sign and encapsulate the read-write sets of multiple target transactions in the first target transaction read-write set and upload them to the blockchain. When encapsulating and uploading them to the blockchain, first sign and encapsulate the read-write set of the current target transaction and upload it to the blockchain. S32. Then, obtain the version number of the business partition updated after the current target transaction is on-chain, and synchronize the read-write set version number of the next read-write set associated with the read-write set key; S33. After the next read-write set associated with the read-write set key completes read-write set version number synchronization, the next read-write set associated with the read-write set key is signed and packaged and uploaded to the chain. Similarly, the read-write set signatures and packaging and upload to the chain for all target transactions in the first target transaction set are completed.

[0026] Specifically, after the target transaction's read-write set is signed, the signed target transaction data is segmented to obtain multiple corresponding data segments. These data segments are then converted into data packets and transmitted to the Master node in the form of bitstreams for processing. This completes the signing, packaging, and uploading of the target transaction to the blockchain. The signed target transaction data includes data such as the business partition ID, read-write set, and user information.

[0027] Furthermore, sub-step S32 specifically includes the following steps: S321: Submit the current target transaction to the Master node for transaction verification. After the Master node updates the version number based on the transaction verification result, it obtains the updated version number of the business partition. S322: Compare the version number of the updated business partition with the read-write set version number of the next read-write set associated with the read-write set key. If the two version numbers are consistent, the read-set version number synchronization is completed. If the two version numbers are inconsistent, the version number of the updated business partition is used as the read-set version number of the next read-write set associated with the read-write set key.

[0028] Specifically, after multiple target transactions are encapsulated and uploaded to the chain, the Master node verifies the transactions on the chain. The verification process includes processes such as read-write set signature authentication, execution policy verification, and version number verification. During version number verification, it is verified whether the version number of the read set is the same as the version number of the business partition in the blockchain network. If the version numbers are the same, the transaction verification is successful, and the version number of the business partition is updated, and the data of the target transaction is written to the block. If the two version numbers are different, the verification of the target transaction fails, and the version number of the business partition is not changed. In the embodiment of the present invention, by querying the version number of the business partition in turn during the simulation execution process to update each target transaction in the set, it can ensure that the version number remains consistent during transaction verification, and can effectively improve the success rate of concurrent transactions.

[0029] The embodiment of the present invention first sorts and groups multiple target transactions according to the business partition ID and the read-write set key correlation to obtain the first target transaction read-write set, ensuring that when the target transaction is subsequently processed, the visibility of the business partition version number can be guaranteed, and the success rate of chain upload in the case of read-write set key conflicts is improved. Then, the target transaction read-write sets in the first target transaction set are encapsulated and uploaded to the chain in turn, and in the process of encapsulation and chain upload, the execution result of the next target transaction is synchronized with the version number of the business partition updated when the previous target transaction is completed and uploaded to the chain, so that the read set version number of the concurrent multiple target transactions is consistent with the version number of the latest business partition, thereby improving the success rate of the transaction and effectively improving the node's processing efficiency for concurrent transactions.

[0030] Example 2: Reference Figure 2 As shown, based on the above-mentioned embodiment 1, the embodiment of the present invention further provides a blockchain concurrent transaction processing device, which is applied to the transaction collection simulation execution node designated by the Master node, including: A transaction collection module is used to obtain multiple target transactions concurrently submitted to the blockchain, each of which carries a business partition ID and a version number of the business partition in which the target transaction resides; A transaction simulation execution module is used to perform transaction simulation execution on multiple target transactions, generate read-write sets corresponding to the multiple target transactions, and sort the read-write sets corresponding to the multiple target transactions according to the association between the business partition ID of the transaction and the read-write set key to obtain the first target transaction read-write set; The transaction encapsulation and chain-up module is used to encapsulate and chain-up the read-write sets in the first target transaction read-write set in sequence, and during the encapsulation and chain-up process, synchronize the version numbers of the read-write sets with the read-write set key association according to the version number of the business partition updated when the previous read-write set is encapsulated and chain-up.

[0031] Specifically, the transaction collection module's workflow involves collecting transaction requests for multiple target transactions submitted by users to the blockchain via the client within the same transaction time period. The blockchain is configured with at least two relatively independent business zones, each with its own zoned ledger. The blockchain as a whole maintains a global ledger, which maintains the version number of the target transaction's zone. When users in each zone submit transactions via the client, each transaction carries the corresponding zone ID and the zone's version number. Upon submission, the transaction data is cryptographically signed to prevent tampering. Furthermore, transaction data can be collected and submitted in a predefined format, such as XML or JSON, depending on the specific circumstances.

[0032] Perform signature verification on the transaction signatures of multiple target transactions respectively. After the signature verification is passed, perform data analysis on each transaction request to obtain the business partition ID corresponding to the transaction request and the version number of the business partition where the target transaction is located.

[0033] The embodiment of the present invention collects and organizes target transactions on the blockchain within the same time period through a transaction collection module, and obtains information such as the business partition ID and business partition version number from these target transactions, so as to facilitate subsequent version number synchronization and ensure the consistency of the business partition version number.

[0034] Furthermore, in one embodiment, the working process of the transaction collection module of the present invention specifically includes the following: Multiple target transactions within the same transaction time period are sorted in ascending order according to the business partition IDs of the target transactions to obtain a corresponding first target transaction set.

[0035] The size of the business partition ID is usually related to the order and time of transaction occurrence. Therefore, the embodiment of the present invention arranges multiple target transactions in ascending order of the business partition ID, which can ensure that the business partition version number of the target transaction that occurred earlier can be seen by the subsequent target transaction.

[0036] Furthermore, in one embodiment, the transaction simulation execution module of the embodiment of the present invention processes transactions in the first target transaction set including: First, multiple target transactions are simulated and executed in the order in which they were collected to obtain the read-write sets of the multiple target transactions; Then, the read-write sets of multiple target transactions are partitioned and sorted according to the business partition ID, and the read-write sets of the target transactions are associated and sorted according to the read-write set key association in the partitioned read-write sets to obtain the first target transaction read-write set.

[0037] Among them, the business partition ID can indicate the business partition where the transaction occurs. Therefore, during the simulation execution process, the embodiment of the present invention can partition and sort multiple target transactions according to the correlation between the business partition ID and the read-write set key, thereby ensuring that the business partition version number of the target transaction occurring earlier can be seen by the subsequent target transaction, thereby improving the success rate of transactions on the chain in the case of read-write set key conflicts.

[0038] Furthermore, in one embodiment, the process of the transaction encapsulation and chaining module of the embodiment of the present invention encapsulating and chaining the read-write set in the first target transaction read-write set specifically includes: First, sign and encapsulate the read-write sets of multiple target transactions in the first target transaction read-write set in order and upload them to the chain. When encapsulating and uploading to the chain, first sign and encapsulate the read-write set of the current target transaction and upload it to the chain; Then, obtain the version number of the business partition updated after the current target transaction is on-chain, and synchronize the read-write set version number of the next read-write set associated with the read-write set key; Finally, after the next read-write set associated with the read-write set key completes the read-write set version number synchronization, the next read-write set associated with the read-write set key is signed and packaged and uploaded to the chain. Similarly, the read-write set signatures and packaging of all target transactions in the first target transaction set are completed and uploaded to the chain.

[0039] Specifically, after the target transaction's read-write set is signed, the signed target transaction data is segmented to obtain multiple corresponding data segments. These data segments are then converted into data packets and transmitted to the Master node in the form of bitstreams for processing. This completes the signing, packaging, and uploading of the target transaction to the blockchain. The signed target transaction data includes data such as the business partition ID, read-write set, and user information.

[0040] Furthermore, the process of synchronizing the read set version number by the transaction encapsulation and chaining module in the embodiment of the present invention specifically includes: Submit the current target transaction to the Master node for transaction verification. After the Master node updates the version number based on the transaction verification result, obtain the updated version number of the business partition. The version number of the updated business partition is compared with the read-write set version number of the next read-write set associated with the read-write set key. If the two version numbers are consistent, the read-set version number synchronization is completed. If the two version numbers are inconsistent, the version number of the updated business partition is used as the read-set version number of the next read-write set associated with the read-write set key.

[0041] Furthermore, an embodiment of the present invention further provides an electronic device, including: one or more processors; A storage device for storing one or more programs, which, when executed by the one or more processors, enables the one or more processors to implement the blockchain concurrent transaction processing method in Example 1.

[0042] Furthermore, an embodiment of the present invention also provides a computer-readable medium having a computer program stored thereon, which, when executed by a processor, implements the blockchain concurrent transaction processing method in Example 1.

[0043] In the above embodiments, all or part of the embodiments can be implemented using software, hardware, firmware, or any combination thereof. When implemented using software, all or part of the embodiments can be implemented in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the processes or functions described in accordance with the embodiments of the present invention are generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium that can be accessed by a computer, or a data storage device such as a server or data center that integrates one or more available media. The available medium can be magnetic media (e.g., floppy disk, hard disk, tape), optical media (e.g., DVD), or semiconductor media (e.g., solid-state disk (SSD)).

[0044] It should be noted that, in this document, relational terms such as first and second, etc., are used only to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply the existence of any such actual relationship or order between these entities or operations. Moreover, the terms "comprises," "comprising," or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article, or device comprising a series of elements includes not only those elements, but also other elements not explicitly listed, or elements inherent to such process, method, article, or device. In the absence of further limitations, an element defined by the phrase "comprising a ..." does not exclude the presence of other identical elements in the process, method, article, or device comprising the element.

[0045] Each embodiment in this specification is described in a related manner. Similar parts between the various embodiments can be referred to in conjunction with each other. Each embodiment focuses on the differences between the other embodiments. In particular, the system embodiment is generally similar to the method embodiment, so the description is relatively simple. For related parts, refer to the description of the method embodiment.

[0046] The above description is only a preferred embodiment of the present invention and is not intended to limit the scope of protection of the present invention. Any modifications, equivalent replacements, improvements, etc. made within the spirit and principles of the present invention are included in the scope of protection of the present invention.

Claims

1. A blockchain concurrent transaction processing method, applied to a transaction collection simulation execution node designated by a Master node, characterized in that: include: Obtain multiple target transactions concurrently submitted to the blockchain, each of which carries a business partition ID and a version number of the business partition in which the target transaction resides; Perform transaction simulation on multiple target transactions, generate read-write sets corresponding to the multiple target transactions, and sort the read-write sets corresponding to the multiple target transactions according to the association between the business partition ID of the transaction and the read-write set key to obtain the first target transaction read-write set; The read-write sets in the first target transaction read-write set are encapsulated and uploaded to the chain in sequence. During the encapsulation and chaining process, the version numbers of the read-write sets associated with the read-write set key are synchronized according to the version number of the business partition updated when the previous read-write set is encapsulated and uploaded to the chain.

2. The blockchain concurrent transaction processing method according to claim 1, characterized in that: The obtaining of multiple target transactions concurrently submitted to the blockchain includes: Collecting transaction requests for multiple target transactions submitted by the user to the blockchain by the client within the same transaction time period; wherein the blockchain is provided with at least two relatively independent business partitions, each of which has a corresponding partition ledger, and the blockchain as a whole has a global ledger, which maintains the version number of the business partition in which the target transaction is located; Perform signature verification on the transaction signatures of multiple target transactions respectively. After the signature verification is passed, perform data analysis on each transaction request to obtain the business partition ID corresponding to the transaction request and the version number of the business partition where the target transaction is located.

3. The blockchain concurrent transaction processing method according to claim 1, characterized in that: The step of performing transaction simulation on multiple target transactions, generating read-write sets corresponding to the multiple target transactions respectively, and sorting the read-write sets corresponding to the multiple target transactions according to the business partition ID to which the transactions belong and the association between the read-write set key, to obtain a first target transaction read-write set, includes: Execute multiple target transactions in a simulated manner according to the order in which they were collected, and obtain a read-write set of the multiple target transactions; The read-write sets of multiple target transactions are partitioned and sorted according to the business partition ID, and the read-write sets of the target transactions are associated and sorted according to the read-write set key association in the partitioned read-write sets to obtain the first target transaction read-write set.

4. The blockchain concurrent transaction processing method according to claim 1, characterized in that: The process of sequentially encapsulating and uploading the read-write sets in the first target transaction read-write set to the chain, and performing version number synchronization processing on the read-write sets associated with the read-write set key according to the version number of the business partition updated when the previous read-write set is encapsulated and uploaded to the chain, includes: Sequentially sign and package the read-write sets of multiple target transactions in the first target transaction read-write set and upload them to the chain. When encapsulating and uploading to the chain, first sign and package the read-write set of the current target transaction and upload it to the chain; Then, obtain the version number of the business partition updated after the current target transaction is on-chain, and synchronize the read-write set version number of the next read-write set associated with the read-write set key; After the next read-write set associated with the read-write set key completes read-write set version number synchronization, the next read-write set associated with the read-write set key is signed and packaged and uploaded to the chain. Similarly, the read-write set signatures and packaged uploads for all target transactions in the first target transaction set are completed.

5. The blockchain concurrent transaction processing method according to claim 4, characterized in that: The process of obtaining the updated version number of the business partition after the current target transaction is on-chain and synchronizing the read-write set version number of the next read-write set associated with the read-write set key includes: Submit the current target transaction to the Master node for transaction verification. After the Master node updates the version number based on the transaction verification result, obtain the updated version number of the business partition. The version number of the updated business partition is compared with the read-write set version number of the next read-write set associated with the read-write set key. If the two version numbers are consistent, the read-set version number synchronization is completed. If the two version numbers are inconsistent, the version number of the updated business partition is used as the read-set version number of the next read-write set associated with the read-write set key.

6. A blockchain concurrent transaction processing device, applied to the transaction collection simulation execution node designated by the Master node, characterized in that: include: A transaction simulation execution module is used to perform transaction simulation execution on multiple target transactions, generate read-write sets corresponding to the multiple target transactions, and sort the read-write sets corresponding to the multiple target transactions according to the association between the business partition ID of the transaction and the read-write set key to obtain the first target transaction read-write set; The transaction encapsulation and chain-up module is used to encapsulate and chain-up the read-write sets in the first target transaction read-write set in sequence, and during the encapsulation and chain-up process, synchronize the version numbers of the read-write sets with the read-write set key association according to the version number of the business partition updated when the previous read-write set is encapsulated and chain-up.

7. An electronic device, characterized in that: include: one or more processors; A storage device for storing one or more programs, which, when executed by the one or more processors, enables the one or more processors to implement the blockchain concurrent transaction processing method according to any one of claims 1 to 5.

8. A computer-readable medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the blockchain concurrent transaction processing method according to any one of claims 1 to 5 is implemented.

Images