WO2023177136A1

WO2023177136A1 - Blockchain data storage method and storage management device for providing service

Info

Publication number: WO2023177136A1
Application number: PCT/KR2023/003032
Authority: WO
Inventors: 박세진; 나동준
Original assignee: 계명대학교 산학협력단
Priority date: 2022-03-14
Filing date: 2023-03-06
Publication date: 2023-09-21
Also published as: KR20230134196A

Abstract

The present invention relates to a blockchain data storage method performed by a blockchain data storage management device for storing data by using a blockchain, comprising steps in which: a plurality of nodes included in a blockchain network is clustered by service so as to generate service-specific groups; blockchain nodes included in the service-specific groups are designated as specific nodes on the basis of a predetermined condition; the specific nodes generate a block on the basis of a transaction when the transaction is received from a service user; and blockchain data based on the block is stored in local storage possessed by blockchain nodes included in the service-specific groups. Therefore, latency time and data reliability are ensured by maintaining asynchronously through the local storage maintained in the blockchain node, data stored in the blockchain is stored in the storage divided by service, and a synchronization transaction is generated through a method of agreeing before storing, by node, data in the local storage, and thus reliability can be guaranteed.

Description

Blockchain data storage method and storage management device for service provision

The present invention relates to a blockchain data storage method and storage management device for service provision. More specifically, blockchain data storage for service provision to solve the problem of delay time between nodes and storage and data reliability not being guaranteed. It relates to a method and storage device.

Recently, blockchain technology has been in the spotlight with the emergence of cryptocurrencies such as Bitcoin, Ethereum, and Ripple. Blockchain technology ensures data security and enables transparent management based on P2P distributed computing. Blockchain, a core technology of the 4th industrial era, is being applied to various fields such as finance and medicine. Unlike the server-client network model in which servers manage data and provide services to clients, blockchain networks have a decentralized structure without servers, and each node must store blockchain data to participate in the network.

However, as blockchain data continues to increase due to the continuous occurrence of transactions, in order to prevent an increase in blockchain capacity, the data is stored in off-chain external distributed storage or cloud storage, and only the metadata is stored on-chain in the blockchain. is using .

However, when data is stored in an external distributed storage or cloud storage rather than a blockchain network, the reliability of the data cannot be guaranteed and network latency also exists.

[Prior art literature]

[Patent Document]

(Patent Document 1) Korean Patent Publication No. 10-2040170

The present invention was created to solve the above problems, and the purpose of the present invention is to maintain external storage for storing blockchain data asynchronously through local storage maintained in the blockchain node, thereby reducing latency and data reliability. A block to provide a service that guarantees reliability by storing data stored in the blockchain in storage divided by service and creating synchronization transactions through agreement before storing the data in local storage for each node. It provides a chain data storage method and storage management device.

A blockchain data storage method performed by a blockchain data storage management device that stores data using a blockchain according to an embodiment of the present invention to achieve the above purpose uses a plurality of nodes included in the blockchain network. Clustering by service to create a group by service; Designating blockchain nodes included in the service-specific group as specific nodes based on certain conditions; Upon receiving a transaction from a service user, a specific node generates a block based on the transaction; and storing blockchain data based on the block in local storage held by blockchain nodes included in the service-specific group.

In the step of designating a specific node, each of the blockchain nodes included in the service-specific group can be designated as one of a service leader node, a general blockchain node, and a lightweight blockchain node.

Additionally, in the step of storing the data, all data connected to the blockchain can be stored in general local storage held by the general blockchain node.

At this time, in the step of storing the data, the data stored in the general local storage can be addressed so that only the address value is stored in the lightweight local storage held by the lightweight blockchain node.

Meanwhile, in the step of generating the block, in order to complete the update agreement before the step of storing the blockchain data, the node designated as the service leader node collects the information received from the general blockchain node and then collects the received information. If all are the same, a synchronization transaction can be created.

Meanwhile, a blockchain data storage management device according to an embodiment of the present invention for achieving the above object includes a group generator for creating a group for each service by clustering a plurality of blockchain nodes included in the blockchain network by service; a node designator that designates blockchain nodes included in the service-specific group as specific nodes based on certain conditions; And when a transaction is received from a service user, a specific node is controlled to create a block based on the transaction, and blockchain data based on the block is stored in local storage held by blockchain nodes included in each service group. It includes a block creation unit that does.

Here, the node designator may designate each of the blockchain nodes included in the service-specific group as one of a service leader node, a general blockchain node, and a lightweight blockchain node.

And the block generator can ensure that all data stored in the blockchain is stored in general local storage held by the general blockchain node.

Additionally, the block generator may address data stored in the general local storage to the lightweight local storage held by the lightweight blockchain node so that only the address value is stored.

And the block generator collects the information received from the general blockchain node by the node designated as the service leader node in order to complete the update agreement before storing the blockchain data, and when all of the received information is the same. You can create a synchronization transaction.

According to one aspect of the present invention described above, by providing a blockchain data storage method and storage management device for service provision, external storage for blockchain data storage is maintained asynchronously through local storage maintained in the blockchain node. This ensures latency and data reliability, stores data stored in the blockchain in storage divided by service, and ensures reliability by creating a synchronization transaction through agreement before storing the data in local storage for each node. You can.

1 is a diagram illustrating the configuration of a blockchain data storage management device 100 according to an embodiment of the present invention;

FIGS. 2 to 5 are diagrams for explaining the process of storing blockchain data in a blockchain network through the blockchain data storage management device 100 of FIG. 1, and

Figure 6 is a flowchart illustrating a blockchain data storage management method according to an embodiment of the present invention.

The detailed description of the present invention described below refers to the accompanying drawings, which show by way of example specific embodiments in which the present invention may be practiced. These embodiments are described in sufficient detail to enable those skilled in the art to practice the invention. It should be understood that the various embodiments of the present invention are different from one another but are not necessarily mutually exclusive. For example, specific shapes, structures and characteristics described herein may be implemented in one embodiment without departing from the spirit and scope of the invention. Additionally, it should be understood that the location or arrangement of individual components within each disclosed embodiment may be changed without departing from the spirit and scope of the invention. Accordingly, the detailed description that follows is not intended to be taken in a limiting sense, and the scope of the invention is limited only by the appended claims, together with all equivalents to what those claims assert, if properly described. Similar reference numbers in the drawings refer to identical or similar functions across various aspects.

The components according to the present invention are components defined by functional division rather than physical division, and can be defined by the functions each performs. Each component may be implemented as hardware or program code and processing units that perform each function, and the functions of two or more components may be included and implemented in one component. Therefore, the names given to the components in the following embodiments are not intended to physically distinguish each component, but are given to suggest the representative function performed by each component, and the names of the components refer to the present invention. It should be noted that the technical idea is not limited.

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

Figure 1 is a diagram for explaining the configuration of the blockchain data storage management device 100 according to an embodiment of the present invention, and Figures 2 to 5 are block diagrams through the blockchain data storage management device 100 of Figure 1. This is a diagram to explain the process by which blockchain data is stored in a chain network.

The blockchain data storage management device 100 (hereinafter referred to as the device) of the present invention is provided to ensure the reliability of data stored in the blockchain as well as reduce network delay time. In the figure, the nodes (N) are computers, It may refer to a terminal device such as a smartphone or server, and in this case, the node (N) can communicate with another device 100 connected to the blockchain network. Additionally, the device 100 may include a group creation unit 110, a node designation unit 120, and a block creation unit 130.

At this time, the device 100, although not shown in the drawing, provides storage space necessary for the operation of the group creation unit 110, node designation unit 120, and block creation unit 130, and a storage unit where various information is stored. It may further include a communication unit for transmitting and receiving various types of information with the outside world through a network. In addition, the device 100 may install and execute software (application) for performing a blockchain data storage management method by controlling a plurality of nodes (N) included in the blockchain network.

And nodes (N) can create transactions according to the commands of the user (U). Here, the user's (U) command may refer to various requests that can occur in the blockchain consensus system, such as user registration, modification of registered user information, transaction request, deposit request, and withdrawal request.

Accordingly, a transaction may include various information required according to a user command, such as information required for user registration, user information entered to be modified, information on traders requesting a transaction, transaction details, and amount.

Therefore, the node (N) can perform authentication by comparing the user information input from the user (U) with the user information registered in the blockchain network. Through this, the nodes (N) are connected to the blockchain network and respond to the user's commands. You can create transactions accordingly.

And the nodes (N) of this blockchain network can perform tasks such as generating data included in transactions, creating and disseminating transactions, storing blockchains, and creating and disseminating blocks. The device 100 of the present invention allows multiple service providers to participate in a blockchain network so that data generated in each environment is stored in the same blockchain, and each service provider has a blockchain node (N) and a local storage (N). DB) can be provided.

To this end, the group creation unit 110 first clusters a plurality of blockchain nodes (N) included in the blockchain network into services (A, B, C) to create groups (G1, G2, G3) for each service. You can.

The node designation unit 120 selects the blockchain nodes (N) included in the service-specific groups (G1, G2, G3) created in the group creation unit 110 into specific nodes (N110, N120, N130) based on certain conditions. ) can be prepared to designate.

At this time, the plurality of blockchain nodes (N110, N120, N130) have a plurality of local storages (DBs) where data is stored as shown in FIG. 2, and each local storage (DB) is stored for each service provided. It can be held. Such local storage (DB) may include regular local storage (DB110) and lightweight local storage (DB120).

And the node designator 120 divides each of the blockchain nodes (N) included in the service-specific groups (G1, G2, G3) into a service leader node (N110), a general blockchain node (N120), and a lightweight blockchain node ( N130) can be specified as one of the following.

Here, the general blockchain node (N120) is a node participating in the blockchain network and stores the same blockchain, and can have different local storage for each service used, as shown in Figures 3 to 5. And the local storage (DB) provided in the general blockchain node (N120) is designated as general local storage (DB110), and all data to be stored in the service can be stored in this general local storage (DB110).

Meanwhile, the service leader node (N110) is responsible for processing requests for data storage in the service, and can play a role in distributing and synchronizing data to be stored after receiving transactions, and does not have a separate local storage (DB). It may not be possible.

And, as shown in the figure, the service leader node (N110) can maintain different local storage networks for each service by disseminating and collecting transactions as a gateway.

This service leader node (N110) may be a node created for the service to be provided through a blockchain smart contract, or the contract may allow a specific node and designate that node as the service leader node (N110). . Alternatively, a group (G1, G2, G3) may be created for each service, and one of the nodes included in the group may be randomly generated, but is not limited to this.

And the lightweight blockchain nodes (N130-1, N130-2, N130-3) may be nodes that reduce capacity by storing only addressed data rather than storing data in local storage (DB). And the local storage (DB) provided in this lightweight blockchain node (N130) is designated as lightweight local storage (DB120), and data stored in general local storage (DB110) is addressed to lightweight local storage (DB120), and only the address value is stored in lightweight local storage (DB120). You can save it.

Therefore, even if lightweight blockchain nodes (N130-1, N130-2, N130-3) do not have all the data, they can access other nodes through lightweight local storage (DB120), which only has address values.

At this time, the node designator 120 determines in advance if the storage capacity of the local storage (DB) corresponding to the service is less than the preset capacity based on the capacity of the local storage (DB) provided in the blockchain node (N). After the point where the capacity falls below the set capacity, it can be designated as a lightweight blockchain node (N130-1, N130-2, N130-3).

Of course, the method by which the node designator 120 designates lightweight blockchain nodes (N130-1, N130-2, N130-3) is not necessarily limited to the method described above, and may be used according to other embodiments or by the node designator ( 120), unlike the above method, randomly selects a certain percentage or a certain number of nodes from the beginning within each service group (G1, G2, G3) among the blockchain nodes (N) participating in the blockchain network as lightweight blockchain nodes. It can also be specified as (N130).

Referring to Figure 3, the second general blockchain node (N120-2) and the third general blockchain node (N120-3) included in the first group (G1) are the fourth general blockchain node included in the second group (G2). As connected to the blockchain node (N120-4), the connection between nodes included in different service groups may mean that the nodes are connected through a P2P network.

When the block generator 130 receives a transaction (e.g., a data modification request) from a service user (U), it can control a specific node to generate a block based on the transaction, and can control the service-specific groups (G1, G2, It is possible to control block-based blockchain data to be stored in local storage (DB) held by blockchain nodes (N) included in G3).

This block generator 130 can ensure that all blockchain data stored in the blockchain is stored in the general local storage (DB110) held by the general blockchain node (N120). And the block generator 130 can address the data stored in the general local storage (DB110) to the lightweight local storage (DB120) held by the lightweight blockchain node (N130) so that only the address value is stored.

In addition, in order to complete the update agreement before storing the blockchain data, the block generator 130 receives data from the general blockchain nodes (N120) included in the same service-specific group by the node designated as the service leader node (N110). After collecting the information, if the information received from multiple general blockchain nodes (N120) in the group is all the same, a synchronization transaction can be created as shown in the figure.

Hereinafter, with reference to FIGS. 3 to 5, the process in which each node agrees on data and adds blocks on a blockchain network through the device 100 and stores them in local storage (DB) will be described in more detail.

When group creation and node designation are completed through the group creation unit 110 and the node designation unit 120, the block creation unit 130 allows the user (U) using service A to use the key value as shown in FIG. 3. When receiving a data modification request to change the value to b, along with the ID of the user (U) that can identify the user (U), that is, a transaction, the leader node (N110-1) stores the data to be stored in the first group (G1). It can be distributed to general blockchain nodes (N120-1, N120-2, N120-3) and have the leader node (N110-1) create a synchronization transaction for local storage update.

Specifically, as shown in Figure 3, the service leader node (N110-1) included in the first group (G1) transmits the transaction received from the user (U) to the first to third blockchain nodes located in the first group (G1) ( It can spread to N120-1~N120-3).

Then, after the first to third blockchain nodes (N120-1 to N120-3) execute the commands in the transaction received from the service leader node (N110), the results are sent to the first group ( After the first service leader node (N110-1) of G1) collects, if the results are all the same, a synchronization transaction is created as in ②, and the synchronization transaction thus created is sent to all general blockchain nodes (G1) of the first group (G1). It can be spread to N120-1~N120-3).

As shown in the figure, the synchronization transaction created in this way may include metadata about the local storage update, information about nodes participating in the update agreement, and the signature of the service leader node (N110) of the service group.

And the block generator 130 randomly selects a block generation node among other nodes (N110, N120, and N130) existing in the blockchain network, and controls the selected node to generate a block containing synchronization transactions, The created block can be propagated and recorded. In the drawing, the third service leader node (N110-3) of the third group (G3) is shown receiving a synchronization transaction and generating a block based on this, but this is not explained in detail. This is only an example for convenience and is not limited thereto. And the block created in this way can include a hash, previous block hash, and synchronization transaction as shown in the drawing.

Additionally, the block generator 130 may maintain the results of commands executed by nodes included in services within the block in the local storage (DB110) as shown in ③ of FIG. 5. Meanwhile, the block generator 130 can store the address values of nodes participating in the update agreement in the lightweight local storage (DB120) included in the first group (G1), and store only metadata in the blockchain. there is.

Through this, the device 100 of the present invention can store data (text, files, etc.) in storage divided by service in order to store data stored in the blockchain in local storage for each node, and reach an agreement before storing it in local storage. Through this process, reliability can be guaranteed by creating a synchronization transaction.

FIG. 6 is a flowchart for explaining a blockchain data storage management method according to an embodiment of the present invention. The blockchain data storage management method according to an embodiment of the present invention includes the blockchain data shown in FIGS. 1 to 5. Since it is carried out on substantially the same configuration as the storage management device 100, the same reference numerals are assigned to the same components as the blockchain data storage management device 100 (hereinafter referred to as the device), and repeated descriptions are omitted.

The device 100 can cluster a plurality of blockchain nodes by service (A, B, C) provided by the service provider to create groups (G1, G2, G3) by service (S110).

Additionally, blockchain nodes included in each service group can be designated as specific nodes based on certain conditions (S130).

In the step of designating the specific node (S130), each of the blockchain nodes (N) included in the service-specific group is selected from among the service leader node (N110), general blockchain node (N120), and lightweight blockchain node (N130). You can specify one.

Afterwards, when a transaction (for example, a data modification request) is received from a service user, a specific node can be controlled to create a block based on the transaction (S150), and a step of controlling to create a block based on this transaction (S150) ), in order to complete the update agreement before the step of storing blockchain data (S170), the node designated as the service leader node (N110) collects the information received from the general blockchain node (N120), and then all the received information is collected. If they are identical, a synchronization transaction can be created. This is to solve the problem that data reliability cannot be guaranteed when data is stored in an external distributed file storage or cloud storage rather than a blockchain network. In the present invention, reliability can be guaranteed by creating a synchronization transaction through a method of agreeing before storing data stored in the blockchain in local storage for each node.

And block-based blockchain data can be stored in local storage (DB110) held by blockchain nodes (N120) included in each service group (S170).

In the step of storing such blockchain data (S170), all data connected to the blockchain can be stored in the general local storage (DB110) held by the general blockchain node (N120).

In addition, in the step of storing blockchain data (S170), the data stored in general local storage (DB110) can be addressed to the lightweight local storage (DB120) held by the lightweight blockchain node (N130) so that only the address value is stored.

Through this, the blockchain data storage method according to the present invention can solve the problem of delay time between nodes and storage.

The blockchain data storage method of the present invention can be implemented in the form of program instructions that can be executed through various computer components and recorded on a computer-readable recording medium. The computer-readable recording medium may include program instructions, data files, data structures, etc., singly or in combination.

The program instructions recorded on the computer-readable recording medium may be those specifically designed and configured for the present invention, or may be known and usable by those skilled in the computer software field.

Examples of computer-readable recording media include magnetic media such as hard disks, floppy disks and magnetic tapes, optical recording media such as CD-ROMs and DVDs, and magneto-optical media such as floptical disks. media), and hardware devices specifically configured to store and perform program instructions, such as ROM, RAM, flash memory, etc.

Examples of program instructions include not only machine language code such as that created by a compiler, but also high-level language code that can be executed by a computer using an interpreter or the like. The hardware device may be configured to operate as one or more software modules to perform processing according to the invention and vice versa.

Although various embodiments of the present invention have been shown and described above, the present invention is not limited to the specific embodiments described above, and may be used in the technical field to which the invention pertains without departing from the gist of the invention as claimed in the claims. Of course, various modifications can be made by those skilled in the art, and these modifications should not be understood individually from the technical idea or perspective of the present invention.

[Explanation of symbols]

100: Blockchain data storage management device 110: Group creation unit

120: node designation unit 130: block generation unit

N110: Leader node N120: General blockchain node

N130: Lightweight blockchain node DB110: Local storage

DB120: Lightweight local storage U: Service user

Claims

In the blockchain data storage method performed by a blockchain data storage management device that stores data using blockchain,

Clustering a plurality of nodes included in the blockchain network by service to create a group by service;

Designating blockchain nodes included in the service-specific group as specific nodes based on certain conditions;

Upon receiving a transaction from a service user, a specific node generates a block based on the transaction; and

A blockchain data storage method comprising storing blockchain data based on the block in local storage held by blockchain nodes included in the service-specific group.
According to paragraph 1,

In the step of designating the specific node,

A blockchain data storage method characterized by designating each of the blockchain nodes included in the service-specific group as one of a service leader node, a general blockchain node, and a lightweight blockchain node.
According to paragraph 2,

In the step of storing the data,

A blockchain data storage method, characterized in that all data connected to the blockchain is stored in general local storage held by the general blockchain node.
According to paragraph 3,

In the step of storing the data,

A blockchain data storage method characterized by addressing the data stored in the general local storage so that only the address value is stored in the lightweight local storage held by the lightweight blockchain node.
According to paragraph 2,

In the step of creating the block,

In order to complete the update agreement before the step of storing the blockchain data, the node designated as the service leader node collects the information received from the general blockchain node and then creates a synchronization transaction if all of the received information is the same. A blockchain data storage method characterized by:
A group creation unit that clusters a plurality of blockchain nodes included in the blockchain network by service to create a group by service;

a node designator that designates blockchain nodes included in the service-specific group as specific nodes based on certain conditions; and

When a transaction is received from a service user, a specific node is controlled to create a block based on the transaction, and blockchain data based on the block is stored in local storage held by blockchain nodes included in each service group. A blockchain data storage management device that includes a block generation unit.
According to clause 6,

The node designator,

A blockchain data storage management device characterized in that each of the blockchain nodes included in the service-specific group is designated as one of a service leader node, a general blockchain node, and a lightweight blockchain node.
In clause 7,

The block generator,

A blockchain data storage management device characterized in that all data stored in the blockchain is stored in general local storage held by the general blockchain node.
According to clause 8,

The block generator,

A blockchain data storage management device characterized in that only the address value is stored in the lightweight local storage held by the lightweight blockchain node by addressing the data stored in the general local storage.
In clause 7,

The block generator,

In order to complete update agreement before storing the blockchain data, the node designated as the service leader node collects the information received from the general blockchain node and then creates a synchronization transaction if all the received information is the same. Characteristics of a blockchain data storage management device.