BLOCKCHAIN SYSTEM AND OPERATION METHOD THEREOF

• US 20200133943A1
• Filed: 10/29/2019
• Published: 04/30/2020
• Est. Priority Date: 10/29/2018
• Status: Active Grant

• Current Assignee: Electronics and Telecommunications Research Institute
• Original Assignee: Electronics and Telecommunications Research Institute
• Inventors: YIM, Jong Choul, KIM, Sun Me
• Granted Patent: US 11,409,734 B2
• Time in Patent Office: Days
• CPC Class Codes: G06F 16/2365 Ensuring data consistency and integrity
• CPC Class Codes: G06F 16/2379 Updates performed during online database operations; commit processing
• CPC Class Codes: G06Q 20/065 using e-cash
• CPC Class Codes: G06Q 20/389 Keeping log of transactions for guaranteeing non-repudiation of a transaction
• CPC Class Codes: G06Q 20/401 Transaction verification
• CPC Class Codes: G06Q 20/405 Establishing or using transaction specific rules
• CPC Class Codes: G06Q 2220/00 Business processing using cryptography
• CPC Class Codes: H04L 9/3239 involving non-keyed hash functions, e.g. modification detection codes [MDCs], MD5, SHA or RIPEMD
• CPC Class Codes: H04L 9/50 using hash chains, e.g. blockchains or hash trees

Abstract

Disclosed is a blockchain system. A blockchain system according to an embodiment of the present disclosure includes: at least one confirmation node; at least one management node configuring a confirmation group by including the at least one confirmation node, and configuring a confirmation block by combining transactions generated in the confirmation group; and an operator node controlling the at least one management node, wherein the at least one management node configures blockchain by combining respective confirmation blocks, wherein the management node configures the blockchain by resetting a parent block on the basis of an generation order of the confirmation blocks and distributes the blockchain.

Claims

1. A blockchain system, the system comprising:

at least one confirmation node;

at least one management node configuring a confirmation group by including the at least one confirmation node, and configuring a confirmation block by combining transactions generated in the confirmation group; and

an operator node controlling the at least one management node,

wherein the at least one management node configures a blockchain by combining respective confirmation blocks, wherein the management node configures the blockchain by resetting a parent block on the basis of an generation order of the confirmation blocks and distributes the blockchain.

2. The system of claim 1, wherein the at least one management node checks whether or not a conflict between transactions respectively included in confirmation blocks different with each other is present, and configures the confirmation block by reflecting whether or not the conflict between transactions is present.

3. The system of claim 1, wherein the confirmation block includes:

a block body including a list of the transactions;

a block header including at least one of a hash value of the parent block, a root value of a Merkle tree for the transaction included in the confirmation block, a time at which the confirmation block is generated, and an identifier of the confirmation group in association with the confirmation block.

4. The system of claim 3, wherein the at least one management node resets the parent block according to the parent block set in the confirmation block, and the time at which the confirmation block is generated.

5. The system of claim 4, wherein the at least one management node configures a scalable header including a hash value of the reset parent block, and a hash value of the block header included in the confirmation block, and configures a final block by adding the configured scalable header to the confirmation block.

6. The system of claim 5, wherein the at least one management node determines to discard the transaction according to whether or not the conflict between transactions respectively included in confirmation blocks different with each other is present.

7. The system of claim 6, wherein the at least one management node inserts a discarded transaction list indicating the discarded transaction into the scalable header.

8. The system of claim 1, wherein a first management node included in a first confirmation group receives a participation request message in the confirmation group from a first node, determines whether or not to approve the participation of the first node in the first confirmation group, and notifies the first node of the determined result.

9. The system of claim 8, wherein the first management node determines whether or not to approve the participation of the first node in the first confirmation group according to at least one of a number of nodes constituting the first confirmation group, and a consensus time of the confirmation block.

10. The system of claim 8, wherein the first management node transmits a new node notice message representing the participation of the first node in the first confirmation group to the at least one confirmation node included in the first confirmation group.

11. The system of claim 8, wherein the first management node determines at least one another second confirmation group different from the first confirmation group, and provides information indicating at least one second management node included in the at least one second confirmation group to the first node.

12. The system of claim 8, wherein the participation request message includes a hash value of a last block among confirmation blocks included in the first node.

13. The system of claim 12, wherein the first management node determines whether or not to approve the participation of the first node in the first confirmation group on the basis of a distance between the last block included in the first node and a last confirmation block included in a unit of the management group.

14. The system of claim 8, wherein the first management node transmits a proof required message including at least one of a nonce value issued by the first management node, information representing a level of difficulty of a hash function, and information on a count value representing a number of times of performing the hash function to the first node, receives a proof required response message including a result value of the hash function from the first node, and determines whether or not to approve the participation of the first node in the first confirmation group according to the result value of the hash function.

15. The system of claim 8, wherein the first management node transmits a NACK message indicating a refusal of the participation in the first confirmation group to the first node, wherein the NACK message includes a reason for refusal.

16. The system of claim 15, wherein the reason for refusal includes at least one of information indicating that a node in association with an address and a public key of the first node has been already joined, information representing that the information of the level of difficulty does not match, information indicating that the nonce value provided form the first management node is not used, and information indicating that an error exists in a result value of the hash function.

17. The system of claim 1, wherein a first management node included in a first confirmation group monitors a state of the blockchain system, and transmits a request message for performing transfer from the first confirmation group to a second confirmation group to a first confirmation node of the first confirmation group, wherein the transfer request message includes an address and a public key of the first confirmation node, and an address and a public key of a second management node included in the second confirmation group, and a signature value of the first management node.

18. The system of claim 17, wherein the first confirmation node determines whether or not to be transferred to the second confirmation group, and transmits the transfer request message to the second management node.

19. The system of claim 17, wherein the first confirmation node generates the second management node according to a state of the blockchain system.

20. A method of operating a blockchain system, the method comprising:

respectively configuring, by at least one management node controlled by an operator node, at least one confirmation group including the management node and at least one confirmation node;

respectively configuring, by the least one management node, a confirmation block by combining transactions generated in the confirmation group; and

configuring, by the least one management node, a blockchain by combining the confirmation blocks configured in another management node,

wherein the blockchain is configured by resetting a parent block according to a generation order of the confirmation blocks so as to be distributed.