Cross-blockchain data migration
US-2022229577-A1 · Jul 21, 2022 · US
US12079130B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-12079130-B2 |
| Application number | US-202217985375-A |
| Country | US |
| Kind code | B2 |
| Filing date | Nov 11, 2022 |
| Priority date | Jan 20, 2021 |
| Publication date | Sep 3, 2024 |
| Grant date | Sep 3, 2024 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
This application discloses a method and apparatus for processing data based on a block chain. The method includes adding transaction data in at least two blocks into an execution queue according to a block height sequence and transaction data sequence numbers; executing contract services and acquiring a read cache and a write cache of a parallel transaction generated by executing each contract service, the at least two pieces of transaction data comprising target transaction data; determining a write cache of a merged transaction in block caches, and acquiring a read cache of an updated transaction; determining a write cache of the transaction to be merged of the target transaction data according to the read cache of the updated transaction; and merging the write cache of the transaction to be merged of the target transaction data into a block cache to which the target transaction data belongs.
Opening claim text (preview).
What is claimed is: 1. A method for processing data based on a block chain, executed by a computer device, comprising: adding transaction data in at least two blocks into an execution queue according to a block height sequence and transaction data sequence numbers, and acquiring at least two pieces of transaction data from the execution queue in sequence, the at least two pieces of transaction data carrying contract information; executing contract services corresponding to the contract information carried by the at least two pieces of transaction data in parallel, and acquiring a read cache and a write cache of a parallel transaction generated by executing each contract service, the at least two pieces of transaction data comprising target transaction data; determining a write cache of a merged transaction in block caches respectively corresponding to the at least two blocks, and acquiring a read cache of an updated transaction corresponding to the target transaction data in the write cache of the merged transaction, a position or addition time of the transaction data corresponding to the write cache of the merged transaction in the execution queue being in front of the target transaction data; determining a write cache of the transaction to be merged of the target transaction data according to the read cache of the updated transaction, the read cache of the parallel transaction corresponding to the target transaction data and the write cache of the parallel transaction corresponding to the target transaction data; and merging the write cache of the transaction to be merged of the target transaction data into a block cache to which the target transaction data belongs, and continuously merging a write cache of the transaction to be merged of the transaction data next to the target transaction data. 2. The method according to claim 1 , wherein the at least two pieces of transaction data are acquired from different blocks. 3. The method according to claim 1 , wherein the determining a write cache of the transaction to be merged of the target transaction data according to the read cache of the updated transaction, the read cache of the parallel transaction corresponding to the target transaction data and the parallel transaction write cache corresponding to the target transaction data comprises: performing read data conflict verification on the read cache of the parallel transaction corresponding to the target transaction data and the read cache of the updated transaction to obtain a verification result; and determining the write cache of the transaction to be merged of the target transaction data according to the verification result and the parallel transaction write cache corresponding to the target transaction data. 4. The method according to claim 1 , wherein the acquiring at least two pieces of transaction data from the execution queue in sequence comprises: determining an idle number corresponding to idle threads in a parallel execution thread pool; and acquiring the at least two pieces of transaction data from the execution queue in sequence through the idle threads when the idle number is equal to or greater than a parallel execution thread threshold, a transaction number of the at least two pieces of transaction data being equal to the idle number. 5. The method according to claim 1 , wherein the contract services corresponding to the contract information carried by the at least two pieces of transaction data comprise at least two smart contracts and at least two transaction execution services; and the executing contract services corresponding to the contract information carried by the at least two pieces of transaction data in parallel, and acquiring a parallel transaction read cache and a parallel transaction write cache generated by executing each contract service comprises: determining the smart contracts used for executing the at least two pieces of transaction data according to contract identifiers comprised in the at least two pieces of contract information respectively; determining transaction execution services called by the at least two smart contracts respectively for executing the at least two pieces of transaction data according to the service identifiers comprised in the at least two pieces of contract information respectively; and executing the at least two transaction execution services in parallel, and acquiring a parallel transaction read cache and a parallel transaction write cache generated by executing each transaction execution service. 6. The method according to claim 5 , wherein the executing the at least two transaction execution services in parallel, and acquiring a read cache of a parallel transaction and a write cache of a parallel transaction generated by executing each transaction execution service comprises: Creating a read cache of an initial transaction and a write cache of an initial transaction for the at least two pieces of transaction data according to the at least two transaction execution services; executing the at least two transaction execution services in parallel, and acquiring parallel transaction read data and parallel transaction write data generated by executing each transaction execution service; storing each piece of parallel transaction read data into the corresponding initial transaction read cache to obtain parallel transaction read caches corresponding to the at least two pieces of transaction data respectively; and storing each piece of parallel transaction write data into the corresponding the write cache of the initial transaction to obtain write caches of parallel transaction corresponding to the at least two pieces of transaction data respectively. 7. The method according to claim 1 , wherein the acquiring a read cache of an updated transaction corresponding to the target transaction data in the write cache of the merged transaction comprises: sequentially traversing the write cache of the merged transactions according to a block height sequence from high to low and a sequence of transaction data sequence numbers from large to small to obtain the write cache of the merged transaction to be read for the target transaction data; and generating the read cache of the updated transaction according to the write cache of the merged transaction to be read for the target transaction data. 8. The method according to claim 3 , wherein the performing read data conflict verification on the read cache of the parallel transaction corresponding to the target transaction data and the read cache of the updated transaction to obtain a verification result comprises: determining parallel transaction read data in the read cache of the parallel transaction corresponding to the target transaction data as target parallel transaction read data; determining a target object of the target parallel transaction read data, and acquiring updated transaction read data associated with the target object in the read cache of the updated transaction; and performing read data conflict verification on the target parallel transaction read data and the updated transaction read data to obtain the verification result. 9. The method according to claim 8 , wherein the verification result comprises a first verification result and a second verification result; and the performing read data conflict verification on the target parallel transaction read data and the updated transaction read data to obtain the verification result comprises: comparing the target parallel transaction read data with the updated transaction read data; determining the verification result as the first verification result when the target parallel transaction read data is the same as the updated transaction read data, the first v
Server or database system · CPC title
Caches characterised by their organisation or structure · CPC title
with main memory updating (G06F12/0806 takes precedence) · CPC title
Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor · CPC title
Database cache management · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.