KR20210146075A - System and method for managing data state based on blockchain - Google Patents

Abstract

Provided are a system and method for managing a data state based on blockchain. The system for managing a data state based on blockchain according to embodiments of the present invention includes: a service device for storing a snapshot, a hash value of the snapshot, and a timestamp of the snapshot in off-chain storage; and a blockchain node for receiving the hash value and the timestamp from the service device to return to the service device whether the hash value and the timestamp match a first hash value and a first timestamp recorded in a first ledger, wherein the service device verifies the integrity of the snapshot based on the reply from the blockchain node, and transmits, upon verification of the integrity, a restoration request for restoring the data state of the blockchain network to the data state of the snapshot to the blockchain network, in which the first ledger is a distributed ledger of the blockchain node. Therefore, even without initialization, the blockchain is restored to the data state at a specific point in time.

Description

Blockchain-based data state management system and method {SYSTEM AND METHOD FOR MANAGING DATA STATE BASED ON BLOCKCHAIN}

The present invention relates to a blockchain-based data state management system and method. More specifically, it relates to a data state management system and method for backing up and restoring data based on blockchain.

Blockchain records continuously increasing data in a specific unit of block, and each block chain node constituting a peer-to-peer (P2P) network manages the block as a chain-type data structure. It refers to the description or data structure itself. Blockchain technology can ensure the integrity and security of transactions through a consensus process in which all blockchain nodes in the network record and verify transactions.

Data recorded in the block chain is referred to as on-chain data, and data that is managed based on block chain technology but cannot be recorded in the block chain is referred to as off-chain data. Each block constituting the block chain is also limited in size, and since the block chain itself is an expensive resource, it is impossible to record all data on the block chain. Data, etc. are recorded as off-chain data.

In general, it is difficult to delete or modify data once recorded in the blockchain. This feature is an advantage of increasing the reliability of blockchain data, but it also makes it difficult to correct the recorded data if it contains errors or confidential information that should not be disclosed to the outside.

When an error occurs in the data of the block chain, if you try to restore it through the prior art, you need to initialize the block chain network and re-create the block from the beginning to re-record the data up to the time before the error occurred. However, this method has too much inefficiency from restarting the blockchain network, and even if it does, there is no record of the restoration operation itself, so it is impossible to determine the history of what data was restored at what point in time. There is no problem.

Republic of Korea Patent Publication No. 10-2051896 (Announcement on Dec. 06, 2019)

The technical task to be achieved through some embodiments of the present invention is to provide a block chain-based data state management system and method that can restore the block chain to the data state of a specific time in the past without initializing the block chain network will be.

Another technical task to be achieved through some embodiments of the present invention is a blockchain-based data state management system that leaves a record when the data state of the block chain is restored so that the history of the restoration work can be easily understood. and to provide a method.

Another technical task to be achieved through some embodiments of the present invention is to back up the data of the block chain at a specific point in time and perform subsequent restoration based on it, but back up based on the consensus of the block chain network Alternatively, it is to provide a blockchain-based data state management system and method that verifies the integrity of the data to be restored.

The technical problems of the present invention are not limited to the technical problems mentioned above, and other technical problems not mentioned will be clearly understood by those skilled in the art from the following description.

In order to solve the above technical problem, a blockchain-based data state management system according to embodiments of the present invention is a blockchain node that creates a snapshot of data and stores a hash value of the snapshot , and receiving the snapshot and the hash value from the blockchain node, verifying the integrity of the snapshot by comparing the hash value with a first hash value of another blockchain node, and when the integrity is verified, the snapshot and a service device that stores the shot in off-chain storage and records the hash value in a blockchain network.

In one embodiment, the service device generates a transaction for recording the timestamp and the hash value of the snapshot in the blockchain network, and the blockchain node responds to the transaction with the hash value and The timestamp may be recorded in the ledger of the blockchain node.

As an embodiment, the service device may further store the timestamp and the hash value in the off-chain storage.

As an embodiment, the service device transmits an I/O disable request for freezing the data to the block chain node before generating the snapshot, and transmits the first hash value to the block After recording in the chain network, an I/O Enable request to release the freeze can be sent to the blockchain node.

In order to solve the above technical problem, a blockchain-based data state management system according to other embodiments of the present invention is a snapshot, a hash value of the snapshot, and a timestamp of the snapshot. a service device storing the off-chain storage, and receiving the hash value and the timestamp from the service device, and a first hash value and a first recorded in the hash value and the timestamp and a first ledger and a blockchain node that returns whether the timestamp matches or not to the service device, wherein the service device verifies the integrity of the snapshot based on the reply from the blockchain node, and when the integrity is verified, the blockchain A restoration request for restoring the data state of the network to the data state of the snapshot is sent to the blockchain network, and the first ledger is a distributed ledger of the blockchain node.

In one embodiment, when the hash value and the timestamp match the first hash value and the first timestamp, the blockchain node provides the service with a key list of the state database of the blockchain node. can be sent to the device.

In one embodiment, the restore request may include the snapshot and the key list.

In one embodiment, the blockchain node compares the snapshot with the key list in response to the restoration request, and for a key that is not in the snapshot among the key list, sets the key and the key value of the key to the state. It can be deleted from the database.

In one embodiment, the blockchain node compares the snapshot and the key list in response to the restoration request, and for a key of the snapshot that is not in the key list, sets the key and the key value of the key to the state. can be written to the database.

In one embodiment, the blockchain node compares the snapshot with the key list in response to the restoration request, and for a key having a different key value from the snapshot in the key list, the key recorded in the state database The key value of can be modified to the key value of the key on the snapshot.

As an embodiment, the blockchain node may hash the snapshot and compare the hashed result with the first hash value to verify the integrity of the snapshot.

As an embodiment, the service device transmits an I/O disable request for freezing the data to the blockchain node before the blockchain node receives the hash value and the timestamp. and, after the data state of the blockchain network is restored to the data state of the snapshot, an I/O Enable request to release the freeze may be transmitted to the blockchain node.

In order to solve the above technical problem, a blockchain-based data state management method performed by a computing device according to embodiments of the present invention is a method for receiving a snapshot of data and a hash value of the snapshot from a blockchain node. step, verifying the integrity of the snapshot by comparing the hash value with a first hash value of another blockchain node, and if the integrity is verified, storing the snapshot in off-chain storage and blocking the hash value and writing to the chain network.

In order to solve the above technical problem, a blockchain-based data state management method performed by a computing device according to other embodiments of the present invention is a hash value of a snapshot stored in off-chain storage, and the Transmitting a timestamp of the snapshot to a blockchain node, from the blockchain node, the hash value and the timestamp and the first hash value and the first timestamp recorded in the first ledger receiving a match, verifying the integrity of the snapshot based on the match, and when the integrity is verified, sending a restoration request to restore the data state of the blockchain network to the data state of the snapshot transmitting to a blockchain network, wherein the first ledger is a distributed ledger of the blockchain nodes.

In order to solve the above technical problem, a computer program combined with a computing device to execute a block chain-based data state management method according to embodiments of the present invention is a hash value of a snapshot stored in off-chain storage , and transmitting a timestamp of the snapshot to a blockchain node, from the blockchain node, the hash value and the timestamp, and a first hash value and a first recorded in a first ledger Receiving whether timestamps match, verifying the integrity of the snapshot based on the match, and when the integrity is verified, restoring the data state of the blockchain network to the data state of the snapshot stored in a computer-readable recording medium to execute the step of sending a restoration request to the blockchain network, wherein the first ledger is a distributed ledger of the blockchain node.

1 is a diagram schematically illustrating a blockchain-based data state management system 1000 according to embodiments of the present invention.
2 and 3 are diagrams illustrating a method of backing up block chain data in the block chain-based data state management system 1000 according to an embodiment of the present invention.
4 is a flowchart illustrating a method for the service device 100 to back up block chain data as an embodiment for explaining a block chain-based data state management method according to the present invention.
5 is a flowchart illustrating an embodiment in which the step ( S130 ) of verifying the integrity of the snapshot of FIG. 4 is further detailed.
6 and 7 are diagrams for explaining a method of recovering block chain data in the block chain-based data state management system 1000 according to an embodiment of the present invention.
8 is a flowchart illustrating a method for the service device 100 to restore block chain data as an embodiment for explaining a block chain-based data state management method according to the present invention.
9 is a flowchart illustrating specific methods performed by each blockchain node to return its state database to the state of the backup point in the restoration of blockchain data according to an embodiment of the present invention.
10 is a block diagram illustrating an exemplary hardware configuration of a computing device 500 in which various embodiments of the present invention may be implemented.

Hereinafter, embodiments of the present invention will be described in detail with reference to the accompanying drawings. Advantages and features of the present invention and methods of achieving them will become apparent with reference to the embodiments described below in detail in conjunction with the accompanying drawings. However, the technical spirit of the present invention is not limited to the following embodiments, but may be implemented in various different forms, and only the following embodiments complete the technical spirit of the present invention, and in the technical field to which the present invention belongs It is provided to fully inform those of ordinary skill in the art of the scope of the present invention, and the technical spirit of the present invention is only defined by the scope of the claims.

In adding reference numerals to the components of each drawing, it should be noted that the same components are given the same reference numerals as much as possible even though they are indicated on different drawings. In addition, in describing the present invention, if it is determined that a detailed description of a related known configuration or function may obscure the gist of the present invention, the detailed description thereof will be omitted.

Unless otherwise defined, all terms (including technical and scientific terms) used herein may be used with the meaning commonly understood by those of ordinary skill in the art to which the present invention belongs. In addition, terms defined in a commonly used dictionary are not to be interpreted ideally or excessively unless clearly specifically defined. The terminology used herein is for the purpose of describing the embodiments and is not intended to limit the present invention. In this specification, the singular also includes the plural unless specifically stated otherwise in the phrase.

In addition, in describing the components of the present invention, terms such as first, second, A, B, (a), (b), etc. may be used. These terms are only for distinguishing the elements from other elements, and the essence, order, or order of the elements are not limited by the terms. When it is described that a component is “connected”, “coupled” or “connected” to another component, the component may be directly connected or connected to the other component, but another component is formed between each component. It should be understood that elements may also be “connected,” “coupled,” or “connected.”

Hereinafter, some embodiments of the present invention will be described in detail with reference to the accompanying drawings.

1 is a diagram schematically illustrating a blockchain-based data state management system 1000 according to embodiments of the present invention. Referring to FIG. 1 , the data state management system 1000 includes a service device 100 , an off-chain storage 10 , and a blockchain network 30 . The blockchain network 30 includes a plurality of blockchain nodes. The blockchain network 30 records and stores blockchain data through a process of mutual agreement (or distributed agreement) in which a plurality of blockchain nodes participate. Therefore, in this specification, the meaning of recording data in the blockchain network 30 is to record the data as on-chain data, so that each blockchain node can record the data in its own ledger. It may mean generating a related transaction. Similarly, in the present specification, transmitting data to the blockchain network 30 means transmitting the corresponding data to each blockchain node, providing or transmitting the corresponding data to each blockchain node. It may mean to cause

When the service device 100 receives a backup request from the client 20, it backs up the data (or data state) of the blockchain network 30 in the form of a snapshot and stores it as off-chain data. Then, the service device 100 records information related to the backed-up snapshot, for example, a hash value or timestamp of the snapshot, in the blockchain network 30 as on-chain data.

And, when the service device 100 receives a restore request from the client 20, it restores the data (or data state) of the blockchain network 30 to the point of time of the snapshot by using the previously backed up snapshot. In this case, the service device 100 records information related to a restoration request, for example, a snapshot or a key list referenced for restoration, as on-chain data, and stores the restoration history.

Meanwhile, although the service device 100 has been exemplified as receiving a backup request or a restore request from the client 20, the scope of the present invention is not limited thereto. For example, the service device 100 may directly function as the client 20 without receiving a backup request or a restoration request from an external device.

According to the data state management system 1000 of the present invention, the blockchain can be restored to the data state of the past snapshot time without initializing the blockchain network. In addition, when the data state of the block chain is restored to the snapshot point, a record of it is left as on-chain data so that the history of restoration work can be easily understood later.

Hereinafter, various embodiments of the present invention will be described in detail with specific examples.

2 and 3 are diagrams for explaining a specific method of backing up block chain data in the block chain-based data state management system 1000 according to an embodiment of the present invention. In FIG. 2, only three blockchain nodes (hereinafter referred to as 'nodes', 200, 300, and 400) are shown in the blockchain network 30 for simplicity of the drawing, but in general, the blockchain network 30 has more A large number of blockchain nodes can be included.

The service device 100 requests I/O Disable to the blockchain network 30 before requesting data backup. This is a request to freeze the block chain data in order to prevent the data backup from being affected by the new read or write of the block chain data during the data backup process.

As an embodiment, when an I/O disable request is received, the blockchain network 30 receives whether or not to agree to the I/O disable request from each of the nodes 200 , 300 , 400 and collects them. As a result, if there is a consent of more than a quorum, the blockchain network 30 determines that the consensus of all nodes 200, 300, 400 has accepted the I/O inability request, and data backup proceeds Each node (200, 300, 400) is prohibited from reading or writing new data while it is in progress. However, even in this case, it is exceptionally allowed that each node 200 , 300 , 400 reads and writes a snapshot for data backup and related information (eg, a hash value).

On the other hand, at this time, it receives the consent to the I/O impossibility request, collects them, determines the consensus, and accordingly each node 200, 300, 400 prevents reading or writing of new data. The operations may be performed by a smart contract of the blockchain network 30 .

Then, the service device 100 transmits a data backup request for backing up data in the current state to each node 200 , 300 , and 400 . At this time, the data backup request may be directly transmitted from the service device 100 to each node 200 , 300 , 400 , and the service device 100 generates a transaction requesting data backup through the block chain network 30 . In this case, each node 200 , 300 , 300 may detect the transaction and transmit it in such a way that a related request is received.

Each of the nodes 200 , 300 , and 400 responds to a data backup request, generates a snapshot in which data in a current state is recorded, and returns it to the service device 100 together with a hash value.

Specifically, the first node 200 receives the data backup request, inquires the data state of its first state DB 220 in response thereto, and then creates a snapshot in which the data state is recorded. Then, the first node 200 hashes the generated snapshot to generate a hash value of the snapshot, and then transmits the generated snapshot and hash value to the service device 100 . In this case, the first node 200 may temporarily store the generated hash value.

The second node 300 and the third node 400 also generate their respective snapshots and hash values after inquiring their state DBs 320 and 420 in the same way, and the generated snapshots and hashes The value is transmitted to the service device 100 .

The service device 100 receives a snapshot and a hash value transmitted by each node 200 , 300 , and 400 , and verifies the integrity of the received snapshot or hash value by comparing the received hash values with each other. do. If the hash values received from each of the nodes 200, 300, and 400 are all the same, the snapshots of the respective nodes 200, 300, and 400 will also be the same, so that the corresponding snapshot and the hash value are forged or altered. It can be trusted that it is a true value (ie, integrity) that is not On the other hand, if the hash values received from each of the nodes 200, 300, and 400 are all different, it means that the snapshots of each of the nodes 200, 300, and 400 are also different, so that each of the nodes 200, 300, 400) has a high probability that the snapshot (or data) is forged or altered.

As a specific method of verifying integrity, the service device 100 compares received hash values with each other and determines that the integrity of the corresponding snapshot and hash value is verified if the hash values equal to or greater than a quorum are the same, and on the contrary, the same hash values are If it is less than the quorum, it is determined that the integrity of the corresponding snapshot and hash value has not been verified. In this case, the quorum is a value preset in the service device 100 and may be a variable setting value.

When the integrity of the snapshot and the hash value is verified (that is, if the hash values greater than or equal to the quorum are the same), the service device 100 uses the snapshot and its hash value as off-chain data as off-chain storage 10 save to In this case, the service device 100 may store the timestamp of the corresponding snapshot as off-chain data together. The timestamp means the reference time at which the snapshot is secured, and must be identical to the time when the node 200, 300, or 400 creates the snapshot or the time when the service device 100 receives the snapshot. there is no In the process of data backup, each state DB (220, 320, 420) is in a freezing state in which new data is not read or written, so there is no problem even if an arbitrary time during the data backup process is set as the timestamp does not occur

Here, it is exemplified that the server time of the service device 100 is set as the timestamp when the service device 100 completes verification of the snapshot and hash value and stores it as off-chain data.

When the snapshot, the hash value of the snapshot, and the timestamp of the snapshot are stored in the off-chain storage 10 , the service device 100 records the data backup history as on-chain data. This will be described with reference to FIG. 3 .

The service device 100 generates a transaction for recording the hash value and timestamp stored in the off-chain storage 10 as on-chain data. Each of the nodes 200 , 300 , and 400 detects the generated transaction and receives a hash value and a timestamp requested by the service device 100 to be recorded therefrom.

Specifically, the first node 200 receives the hash value and the timestamp, and compares the received hash value with the previously stored hash value. And, when the two hash values match each other, the service device 100 records the requested hash value and timestamp in its first ledger (Ledger, 210).

The second node 300 and the third node 400 also compare the received hash value with the hash value stored temporarily in the same manner, and if the hash values match each other, the received hash value and timestamp It is recorded in its own ledger (310, 410).

The service device 100 receives a reply from each node 200, 300, 400 that the recording of the hash value and timestamp is completed, and enables I/O to release the freeze of the block chain data (I/O Enable) The request is made to the blockchain network 30 .

As an embodiment, when an I/O enable request is received, the blockchain network 30 receives whether to agree to the I/O enable request from each of the nodes 200 , 300 , 400 and collects them. As a result, if there is a quorum or more consent, the blockchain network 30 determines that the consensus of all nodes 200, 300, 400 has accepted the I/O possible request, and previously new data Unblocks reading or writing.

According to the embodiment described above, the service device 100 may store the backup of the block chain data stored by each node 200 , 300 , 400 in the off-chain data in the form of a snapshot, and in the process After verifying the integrity based on the consensus of each node 200 , 300 , 400 whether the corresponding snapshot is reliable data, only the snapshot whose integrity has been verified is stored as backup data.

4 is a flowchart illustrating a method for the service device 100 to back up block chain data as an embodiment for explaining a block chain-based data state management method according to the present invention.

2 and 3 , the data backup method has been described from the perspective of the overall data state management system 1000 , the data backup method will be described from the perspective of the service device 100 in the embodiment of FIG. 4 . In the present embodiment, for the content overlapping with those described above, an additional description will be omitted for the sake of simplification of the description. Hereinafter, it will be described with reference to the drawings.

In step S110 , the service device 100 transmits an I/O impossible request for freezing the block chain data to the block chain network 30 . The blockchain network 30 collects the consensus of each node 200, 300, and 400, and according to the result, it prohibits each node 200, 300, 400 from reading or writing new data.

In step S120 , the service device 100 receives a snapshot of current data and a hash value of the snapshot from each node 200 , 300 , and 400 .

In step S130, the service device 100 verifies the integrity of the snapshot by comparing the received hash values.

In step S140 , when the integrity of the snapshot is verified, the service device 100 stores the snapshot, a hash value of the snapshot, and a timestamp of the snapshot in the off-chain storage 10 . In this case, the timestamp is the reference time of the snapshot, for example, the service device 100 may be a server time at the time of storing the snapshot off-chain storage 10 .

In step S150 , the service device 100 generates a transaction for recording the hash value and timestamp of the snapshot stored in the off-chain storage 10 as on-chain data. Each node 200 , 300 , 400 detects a transaction that has occurred, compares it with a hash value that it temporarily stores, and records it in its own ledger 210 , 310 , 410 if the two hash values match.

In step S160 , the service device 100 receives a reply from each node 200 , 300 , and 400 indicating that the recording of the hash value and timestamp has been completed, and then releases the freeze of the block chain data in the block chain network 30 . Sends an I/O enable request.

5 is a flowchart illustrating an embodiment in which the step ( S130 ) of verifying the integrity of the snapshot of FIG. 4 is further detailed.

In step S131 , the service device 100 compares the received hash values with each other and determines whether the respective hash values are identical to each other.

In step S132 , the service device 100 determines whether the hash values match more than a quorum. If the number of hash values with matching values is equal to or greater than the quorum, the present embodiment proceeds to step S133.

In step S133, the service device 100 sees that the consensus of the blockchain network 30 has approved the corresponding snapshot and hash value, and determines the received snapshot as a valid snapshot.

On the other hand, returning to step S132, if the number of hash values with matching values is not equal to or greater than a quorum (ie, less than a quorum), the received snapshot is not trusted, and thus the snapshot is not stored and is ended as it is.

6 and 7 are diagrams for explaining a specific method of recovering block chain data in the block chain-based data state management system 1000 according to an embodiment of the present invention. 6 and 7, the service device 100, the off-chain storage 10, the blockchain network 30, each node 200, 300, 400 and its ledger 210, 310, 410 and state DBs 220 , 320 , and 420 are the same components as those described above with reference to FIGS. 1 to 3 .

The service device 100 requests I/O Disable to the blockchain network 30 before requesting data restoration. This is a request to freeze blockchain data to prevent data backup from being affected by new reading or writing of blockchain data during data restoration. Other contents of the I/O disable request are the same as described above.

Then, the service device 100 reads off-chain data stored in the off-chain storage 10, for example, a previously backed up snapshot, a hash value of the snapshot, or a timestamp of the snapshot, and , transmits the read hash value and timestamp to each node 200 , 300 , and 400 .

Each node 200 , 300 , 400 receives a hash value and a timestamp, compares it with the hash value and timestamp it stores, and returns whether the hash value and timestamp match.

Specifically, the first node 200 receives the hash value and timestamp, and checks whether the hash value and timestamp of the snapshot recorded in its first ledger 210 match, respectively. Then, a reply on whether the match (ie, match or mismatch) is transmitted to the service device 100 . At this time, when the received hash value and timestamp match the hash value and timestamp recorded in the first ledger 210 , the first node 200 has a key list of data stored in its first state DB 220 . is further transmitted to the service device 100 .

The second node 300 and the third node 400 also check whether the hash values and timestamps are matched with the received hash values and timestamps after inquiring the hash values and timestamps recorded in their ledgers 310 and 410 in the same way. It is transmitted to the service device 100 . If they match, the second node 300 and the third node 400 also transmit the key list of data stored in their own state DBs 320 and 420 to the service device 100 .

The service device 100 verifies the integrity of the snapshot by aggregating the correspondences received from each of the nodes 200 , 300 , and 400 . Specifically, the service device 100 determines that the integrity of the snapshot is verified if the number of matching ones among the replies is greater than or equal to a preset quorum; If the number of replies is less than a preset quorum), it is determined that the integrity of the snapshot is not verified.

When the integrity of the snapshot is verified, the service device 100 transmits a data restoration request to the blockchain network 30 to restore the data state of the blockchain network to the data state at the time of the snapshot. In this case, the service device 100 may transmit the snapshot and the key list received from each node 200 , 300 , 400 to the blockchain network 30 together with a restoration request.

When a data restoration request is received from the service device 100 , each node 200 , 300 , and 400 restores the data state of its state DB 220 , 320 , 420 to the data state at the time of the snapshot. This will be described with reference to FIG. 7 .

After receiving the snapshot and the key list provided by the service device 100 , the first node 200 generates a hash value by hashing the received snapshot. Then, the generated hash value is compared with the hash value of the snapshot recorded in its first ledger 210 . If both match, the first node 200 determines that the received snapshot is a reliable (or authentic) snapshot, and the data of the first state DB 220 to match the data state of the received snapshot. change the state

Specifically, the first node 200 compares the received key list with the snapshot, and sees a key in the key list but not in the snapshot as a newly added key after the snapshot time, and in the first state DB 220 . Delete the corresponding key and key value. Alternatively, a key in the first node (200) that is not in the key list and exists only in the snapshot is regarded as a key deleted after the time of the snapshot, and corresponds to the first state DB 220 by referring to the key and key value recorded in the snapshot. Record a new key and key value. Alternatively, the first node 200 considers a key having a different key value in the key list and the snapshot, but having a different key value, as a key whose key value has been changed since the snapshot point, and in the first state as the key value recorded in the snapshot. The corresponding key value of the DB 220 is modified.

The second node 300 and the third node 400 also use the snapshot and key list received in the same way so that the data state of their state DBs 320 and 420 matches the data state of the snapshot. Changes the data state of the state DB (320, 420).

When the data state change (or restoration) of the state DB 220 , 320 , and 420 is completed, each node 200 , 300 , and 400 returns the result to the service device 100 . The service device 100 receives a reply from each node 200, 300, and 400 that the restoration is complete, and sends an I/O Enable request to the blockchain network ( 30) is requested.

According to the embodiment described above, the service device 100 may restore the data state of the blockchain network 30 to the data state at the time of the snapshot by using the snapshot stored in the off-chain storage 10, Records the related restoration record as on-chain data in the blockchain network 30. In addition, in the process, the service device 100 determines whether the snapshot is reliable data or not After verifying the integrity based on

8 is a flowchart illustrating a method for the service device 100 to restore block chain data as an embodiment for explaining a block chain-based data state management method according to the present invention.

6 and 7 , the data restoration method has been described from the perspective of the overall data state management system 1000 , the data restoration method will be described from the viewpoint of the service device 100 in the embodiment of FIG. 8 . In the present embodiment, for the content overlapping with those described above, an additional description will be omitted for the sake of simplification of the description. Hereinafter, it will be described with reference to the drawings.

In step S210 , the service device 100 transmits an I/O impossible request for freezing the block chain data to the block chain network 30 . The blockchain network 30 collects the consensus of each node 200, 300, and 400, and according to the result, it prohibits each node 200, 300, 400 from reading or writing new data.

In step S220, the service device 100 reads the snapshot, the hash value of the snapshot, or the timestamp of the snapshot from the off-chain storage 10, and stores the read hash value and timestamp in the blockchain network to transmit to (30)

In step S230, each node 200, 300, 400 of the blockchain network 30 checks whether the transmitted hash value and timestamp match the hash value and timestamp recorded in their ledgers 210, 310, 410 The comparison is performed, and whether the match is returned to the service device 100 . The service device 100 receives the match or not from each node 200 , 300 , 400 .

In step S240, the service device 100 verifies the integrity of the snapshot based on the received match. For example, the service device 100 determines that the integrity of the snapshot is verified if the number of correspondence among the replies is equal to or greater than a preset quorum, otherwise (ie, replies as matching among the replies) If the number of the ones made is less than a preset quorum), it is determined that the integrity of the snapshot is not verified.

In step S250 , when the integrity of the snapshot is verified, the service device 100 transmits a data restoration request together with the snapshot and the key list to the blockchain network 30 . Each node 200 , 300 , 400 of the blockchain network 30 restores the data state of its state DB 220 , 320 , 420 to the data state at the time of the snapshot in response to the data restoration request. . Then, the restoration result is returned to the service device 100 .

In step S120 , the service device 100 receives a reply from each node 200 , 300 , 400 indicating that data restoration is complete, and then enables I/O to release the freeze of the block chain data to the block chain network 30 . send the request

9 is a flowchart illustrating specific methods performed by each blockchain node to return its state database to the state of the backup point in the restoration of blockchain data according to an embodiment of the present invention. Accordingly, the performing subject of each step of FIG. 9 becomes each node 200 , 300 , and 400 .

In step S310 , the nodes 200 , 300 , and 400 compare the key list with the snapshot received from the service device 100 .

In step S320, the nodes 200, 300, and 400 determine whether the corresponding key is in the key list but not in the snapshot. If the key is not in the snapshot, the present embodiment proceeds to step S330.

In step S330, the nodes 200, 300, and 400 view the corresponding key as a newly added key after the snapshot time, and delete the corresponding key and key value from the state DBs 220, 320, and 420. When the deletion is completed, the present embodiment proceeds to step S380.

Meanwhile, if the corresponding key is not in the snapshot in step S320, the present embodiment proceeds to step S340 to determine whether the corresponding key is only in the snapshot (ie, not in the key list). If the key exists only in the snapshot, the present embodiment proceeds to step S350.

In step S350, the nodes 200, 300, and 400 see the corresponding key as a key deleted after the time of the snapshot, and refer to the key and key value recorded in the snapshot, and the corresponding key in the state DBs 220, 320, 420. and a new key value. When the recording is completed, the present embodiment proceeds to step S380.

On the other hand, if the corresponding key is not a key only in the snapshot in step S340, the present embodiment proceeds to step S360 and the key value recorded in the state DB (220, 320, 420) of the corresponding key is the key value recorded in the snapshot. to determine whether it is different from If the two key values are different from each other, the present embodiment proceeds to step S370. Otherwise, the present embodiment proceeds directly to step S380.

In step S370, the nodes 200, 300, and 400 view the corresponding key as a key whose key value has changed since the time of the snapshot, and use the corresponding key value in the state DB 220, 320, 420 as the key value recorded in the snapshot. make corrections When the modification is completed, the present embodiment proceeds to step S380.

In step S380 , the nodes 200 , 300 , and 400 compare and verify all keys in the snapshot and the key list. If there is a key that has not yet been compared or confirmed, the present embodiment returns to step S310 and repeats steps S320 to S370. On the other hand, when all keys are compared and confirmed, this embodiment ends.

Hereinafter, an exemplary computing device 500 in which the methods described in various embodiments of the present invention are implemented will be described with reference to FIG. 10 .

10 is an exemplary hardware configuration diagram illustrating the computing device 500 . The computing device 500 shown in FIG. 10 may be, for example, the service device 100 shown in FIG. 2 or a device that implements the respective block chain nodes 200, 300, and 400 in hardware.

As shown in FIG. 10 , the computing device 500 loads one or more processors 510 , a bus 550 , a communication interface 570 , and a computer program 591 executed by the processor 510 . It may include a memory 530 and a storage 590 for storing the computer program (591). However, only the components related to the embodiment of the present invention are illustrated in FIG. 10 . Accordingly, a person skilled in the art to which the present invention pertains can know that other general-purpose components other than the components shown in FIG. 10 may be further included.

The processor 510 controls the overall operation of each component of the computing device 500 . The processor 510 includes at least one of a central processing unit (CPU), a micro processor unit (MPU), a micro controller unit (MCU), a graphic processing unit (GPU), or any type of processor well known in the art. may be included. In addition, the processor 510 may perform an operation on at least one application or program for executing the method/operation according to various embodiments of the present disclosure. Computing device 500 may include one or more processors.

The memory 530 stores various data, commands, and/or information. The memory 530 may load one or more programs 591 from the storage 590 to execute methods/operations according to various embodiments of the present disclosure. An example of the memory 530 may be a RAM, but is not limited thereto.

The bus 550 provides a communication function between components of the computing device 500 . The bus 550 may be implemented as various types of buses, such as an address bus, a data bus, and a control bus.

The communication interface 570 supports wired/wireless Internet communication of the computing device 500 . The communication interface 570 may support various communication methods other than Internet communication. To this end, the communication interface 570 may be configured to include a communication module well-known in the art.

The storage 590 may non-temporarily store one or more computer programs 591 . The storage 590 is a non-volatile memory such as a read only memory (ROM), an erasable programmable ROM (EPROM), an electrically erasable programmable ROM (EEPROM), a flash memory, a hard disk, a removable disk, or well in the art to which the present invention pertains. It may be configured to include any known computer-readable recording medium.

The computer program 591 may include one or more instructions in which methods/operations according to various embodiments of the present invention are implemented. For example, the computer program 591 transmits a hash value of a snapshot stored in off-chain storage, and a timestamp of the snapshot to a blockchain node, from the blockchain node Receiving whether the hash value and the timestamp match the first hash value and the first timestamp recorded in a first ledger, verifying the integrity of the snapshot based on the match, and When the integrity is verified, it may include instructions for performing an operation of transmitting a restoration request for restoring the data state of the block chain network to the data state of the snapshot to the block chain network. In this case, the first ledger may be a distributed ledger of the blockchain node. When the computer program 591 is loaded into the memory 530 , the processor 510 may execute the one or more instructions to perform methods/operations according to various embodiments of the present disclosure.

The technical idea of the present invention described so far may be embodied as computer-readable codes on a computer-readable medium. The computer-readable recording medium may be, for example, a removable recording medium (CD, DVD, Blu-ray disk, USB storage device, removable hard disk) or a fixed recording medium (ROM, RAM, computer-equipped hard disk). can The computer program recorded on the computer-readable recording medium may be transmitted to another computing device through a network such as the Internet and installed in the other computing device, thereby being used in the other computing device.

Although embodiments of the present invention have been described above with reference to the accompanying drawings, those of ordinary skill in the art to which the present invention pertains can practice the present invention in other specific forms without changing the technical spirit or essential features. can understand that there is Therefore, it should be understood that the embodiments described above are illustrative in all respects and not restrictive. The protection scope of the present invention should be interpreted by the following claims, and all technical ideas within the equivalent range should be interpreted as being included in the scope of the technical ideas defined by the present invention.

Claims (15)

a blockchain node that creates a snapshot of data and stores a hash value of the snapshot; and
Receives the snapshot and the hash value from the blockchain node, compares the hash value with a first hash value of another blockchain node to verify the integrity of the snapshot, and when the integrity is verified, the snapshot A service device that stores in off-chain storage and writes the hash value to a blockchain network.
Blockchain-based data state management system. According to claim 1,
The service device is
generating a transaction to record the timestamp of the snapshot and the hash value in the blockchain network;
The blockchain node is
recording the hash value and the timestamp in the ledger of the blockchain node in response to the transaction,
Blockchain-based data state management system. 3. The method of claim 2,
The service device is
further storing the timestamp and the hash value in the off-chain storage;
Blockchain-based data state management system. According to claim 1,
The service device is
Before the creation of the snapshot, an I/O disable request for freezing the data is transmitted to the block chain node,
After recording the first hash value in the blockchain network, sending an I/O Enable request to release the freeze to the blockchain node,
Blockchain-based data state management system. a service device for storing a snapshot, a hash value of the snapshot, and a timestamp of the snapshot in off-chain storage; and
Receives the hash value and the timestamp from the service device, and returns to the service device whether the hash value and the timestamp match the first hash value and the first timestamp recorded in a first ledger including a blockchain node that
The service device is
Verifies the integrity of the snapshot based on the reply from the blockchain node, and when the integrity is verified, a restoration request to restore the data state of the blockchain network to the data state of the snapshot is sent to the blockchain network send,
The first ledger is a distributed ledger of the blockchain node,
Blockchain-based data state management system. 6. The method of claim 5,
The blockchain node is
When the hash value and the timestamp match the first hash value and the first timestamp, transmitting a key list of the state database of the blockchain node to the service device,
Blockchain-based data state management system. 7. The method of claim 6,
The restoration request is
comprising the snapshot and the key list;
Blockchain-based data state management system. 8. The method of claim 7,
The blockchain node is
comparing the snapshot with the key list in response to the restoration request, and deleting the key and a key value of the key from the state database for a key in the key list that is not in the snapshot,
Blockchain-based data state management system. 8. The method of claim 7,
The blockchain node is
comparing the snapshot with the key list in response to the restore request, and for a key of the snapshot that is not in the key list, recording the key and a key value of the key in the state database;
Blockchain-based data state management system. 8. The method of claim 7,
The blockchain node is
In response to the restoration request, the snapshot and the key list are compared, and for a key having a different key value from the snapshot in the key list, the key value of the key recorded in the state database is stored in the snapshot. to be modified with the key value of the key,
Blockchain-based data state management system. 8. The method of claim 7,
The blockchain node is
Hashing the snapshot and verifying the integrity of the snapshot by comparing the hashing result with the first hash value,
Blockchain-based data state management system. 6. The method of claim 5,
The service device is
Before the blockchain node receives the hash value and the timestamp, sending an I/O disable request for freezing the data to the blockchain node,
After the data state of the blockchain network is restored to the data state of the snapshot, sending an I/O Enable request to release the freeze to the blockchain node,
Blockchain-based data state management system. A method performed by a computing device, comprising:
receiving a snapshot of data and a hash value of the snapshot from a blockchain node;
verifying the integrity of the snapshot by comparing the hash value with a first hash value of another blockchain node; and
When the integrity is verified, storing the snapshot in off-chain storage and writing the hash value to a blockchain network.
A blockchain-based data state management method. A method performed by a computing device, comprising:
transmitting a hash value of the snapshot stored in off-chain storage, and a timestamp of the snapshot to a blockchain node;
receiving, from the block chain node, whether the hash value and the timestamp match a first hash value recorded in a first ledger and a first timestamp;
verifying the integrity of the snapshot based on the match; and
When the integrity is verified, transmitting a restoration request to the blockchain network to restore the data state of the blockchain network to the data state of the snapshot;
The first ledger is a distributed ledger of the blockchain node,
Blockchain-based data state management system. Combined with a computing device to execute a blockchain-based data state management method,
transmitting a hash value of the snapshot stored in off-chain storage, and a timestamp of the snapshot to a blockchain node;
receiving, from the block chain node, whether the hash value and the timestamp match a first hash value recorded in a first ledger and a first timestamp;
verifying the integrity of the snapshot based on the match; and
When the integrity is verified, it is stored in a computer-readable recording medium to execute the step of sending a restoration request to the blockchain network to restore the data state of the blockchain network to the data state of the snapshot,
The first ledger is a distributed ledger of the blockchain node,
computer program.

Images