File storage method, terminal, and storage medium
US-2022407725-A1 · Dec 22, 2022 · US
US12061569B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-12061569-B2 |
| Application number | US-202217703085-A |
| Country | US |
| Kind code | B2 |
| Filing date | Mar 24, 2022 |
| Priority date | Apr 24, 2020 |
| Publication date | Aug 13, 2024 |
| Grant date | Aug 13, 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 provides methods, apparatus, electronic devices, and computer-readable storage medium for archiving blockchain data. One method includes synchronizing, by a first committing node, blockchain data with a consensus node, and determining a synchronization block height of the synchronized blockchain data, the synchronized blockchain data comprising state data; determining target state data required by a current transaction in the state data, and backing up the target state data; generating a state data snapshot of the synchronization block height according to the backed-up target state data, and transmitting the state data snapshot, the synchronization block height, and signature information of the first committing node to a second committing node as archiving point information; receiving endorsement information of the second committing node for the archiving point information; and archiving the synchronized blockchain data according to the endorsement information and the archiving point information.
Opening claim text (preview).
What is claimed is: 1. A method for archiving blockchain data, the method comprising: synchronizing, by a first committing node comprising a memory storing instructions and a processor in communication with the memory, blockchain data with a consensus node, and determining a synchronization block height of the synchronized blockchain data, the synchronized blockchain data comprising state data, wherein the state comprises a plurality of sub-state data; determining, by the first committing node, target state data required by a current transaction in the state data, and backing up the target state data by: obtaining, by the first committing node, a block height corresponding to the sub-state data and a storage label corresponding to the sub-state data in a local database; adding, by the first committing node, the block height corresponding to the sub-state data to the storage label corresponding to the sub-state data for marking, to obtain a marked storage label; selecting, by the first committing node, target sub-state data required by the current transaction from the plurality of sub-state data according to the marked storage label, and backing up, by the first committing node, the target sub-state data; generating, by the first committing node, a state data snapshot of the synchronization block height according to the backed-up target state data, and transmitting the state data snapshot, the synchronization block height, and signature information of the first committing node to a second committing node as archiving point information; receiving, by the first committing node, endorsement information of the second committing node for the archiving point information; and archiving, by the first committing node, the synchronized blockchain data according to the endorsement information and the archiving point information. 2. The method according to claim 1 , wherein the selecting, by the first committing node, the target sub-state data required by the current transaction from the plurality of sub-state data according to the marked storage label comprises: obtaining, by the first committing node, transaction information corresponding to the current transaction; determining, by the first committing node, a current block height of current blockchain data of the first committing node according to the transaction information; determining, by the first committing node, that a new block exists in the current blockchain data, in a case that the current block height exceeds the synchronization block height; selecting, by the first committing node, invocation information required by a transaction in the new block from the current blockchain data, the invocation information being used for indicating the sub-state data to be invoked; and selecting, by the first committing node, the target sub-state data from the plurality of sub-state data according to the invocation information and the marked storage label. 3. The method according to claim 1 , wherein the generating, by the first committing node, the state data snapshot of the synchronization block height according to the backed-up target state data comprises: selecting, by the first committing node, synchronization sub-state data whose block height does not exceed the synchronization block height from the state data, to obtain a synchronization sub-state data set; adding, by the first committing node, the backed-up target sub-state data as new synchronization sub-state data to the synchronization sub-state data set to update the synchronization sub-state data set; performing, by the first committing node, a hash operation on the synchronization sub-state data in the updated synchronization sub-state data set to generate state data of a target structure; and copying, by the first committing node, the state data of the target structure to generate the state data snapshot of the synchronization block height. 4. The method according to claim 1 , wherein the archiving, by the first committing node, the synchronized blockchain data according to the endorsement information and the archiving point information comprises: determining, by the first committing node, an endorsement quantity of second committing nodes that transmit the endorsement information; adding, by the first committing node, the endorsement information to the archiving point information to obtain updated archiving point information, in a case that the endorsement quantity exceeds a quantity threshold; transmitting, by the first committing node, the updated archiving point information to the consensus node; and in response to the first committing node receiving configuration block data transmitted by the consensus node for the updated archiving point information, archiving, by the first committing node, the synchronized blockchain data. 5. The method according to claim 4 , wherein: the synchronized blockchain data comprises first block data; and the archiving, by the first committing node, the synchronized blockchain data comprises: copying, by the first committing node, the updated archiving point information to generate an archiving data snapshot of the first committing node at the synchronization block height, adding, by the first committing node, the configuration block data to the first block data to obtain updated first block data, selecting, by the first committing node, target block data whose block height does not exceed the synchronization block height from the updated first block data, and deleting, by the first committing node, the target block data. 6. The method according to claim 1 , wherein the synchronizing, by the first committing node, the blockchain data with the consensus node comprises: transmitting, by the first committing node, a synchronization request to the consensus node, the synchronization request comprising an identity of the first committing node; receiving, by the first committing node, a block transmitted by the consensus node for the synchronization request, the block being transmitted by the consensus node after successfully verifying the identity of the first committing node in the synchronization request; and updating, by the first committing node, local blockchain data according to the block transmitted by the consensus node, to obtain the synchronized blockchain data. 7. An apparatus for archiving blockchain data, the apparatus comprising: a memory storing instructions; and a processor in communication with the memory, wherein, when the processor executes the instructions, the processor is configured to cause the apparatus to perform: synchronizing blockchain data with a consensus node, and determining a synchronization block height of the synchronized blockchain data, the synchronized blockchain data comprising state data, determining target state data required by a current transaction in the state data, and backing up the target state data by: obtaining, by the first committing node, a block height corresponding to the sub-state data and a storage label corresponding to the sub-state data in a local database; adding, by the first committing node, the block height corresponding to the sub-state data to the storage label corresponding to the sub-state data for marking, to obtain a marked storage label; selecting, by the first committing node, target sub-state data required by the current transaction from the plurality of sub-state data according to the marked storage label, and backing up, by the first committing node, the target sub-state data, generating a state data snapshot of the synchronization block height according to the backed-up target state data, and transmitting the state data snapshot, the synchronization block height, and signature information of the apparatus to a second committ
Using snapshots, i.e. a logical point-in-time copy of the data · CPC title
for networked environments · CPC title
Techniques for file synchronisation in file systems · CPC title
Details of archiving (lifecycle management in storage systems G06F3/0649; point-in-time backing up or restoration of persistent data G06F11/1446) · CPC title
Distributed file systems · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.