KR20190110082A - Apparatus for managing data using block chain and method thereof - Google Patents

Abstract

Disclosed are an apparatus for managing data stored on a block chain and a method thereof. According to an aspect of the present invention, a block chain formed by a plurality of node terminals to synchronize and store data and an apparatus for managing storage, inquiry, and deletion of data of the block chain comprise: a main control unit for controlling management of data by transmitting a chain command for managing a block chain and a data command for managing data to a node terminal; and a DB management unit which stores chain information generated by the chain command in a chain table and stores mapping information of data and transactions stored by the data command in a mapping table.

Description

Apparatus for managing data using block chain and method

The present invention relates to a data management technology, and more particularly, to an apparatus and method for managing storage, inquiry and deletion of data using a blockchain.

In a conventional file system, a block size (for example, 8 KB) is designated on a disk and used in a formatted state. For reference, the typical block size is 8KB on Unix file systems. In the NTFS file system, this is referred to as a cluster. A file is a form of electronic document as a unit of data storage.

Here, if a file having a file size less than or equal to the block size is stored by the file system, inefficient use of the disk occurs. For example, if a 2KB file is stored on a disk of the 8KB block size, 6KB, 75% of free space is left, and the disk is inefficiently used. The larger the block size, the faster the read / write speed, so you can't reduce the block size to save space.

The file system provides only basic file management services, so the user must manage the file's access rights on his own. In addition, the user must manage the backup of the file. In addition to the basic file management service, users need to use a separate dedicated hardware / software device to manage file access and backup.

On the other hand, blockchain is a technology for recording data based on cloud technology and P2P technology, and everyone is the subject of data storage and management and records the same information, respectively. Here, the "block" of the block chain means a data storage unit, which is different from the meaning that "block" of the file system is the minimum space in which one file can be allocated on the disk.

The blockchain technology does not store data in file units based on the file system, but stores data in block units in a DB of the blockchain according to a distributed database environment. The block unit is not limited to the block size of the file system depending on the OS. That is, a plurality of data units can be stored in one storage area of the blockchain, and the storage space is used only by 2K of file size without being limited by 8K block size, and the above 6KB of empty space remains. Used as space to store other files.

Blockchain technology provides security by allowing data access only when the access right to the block, which is the storage unit of data, is granted.

Blockchain technology provides backups by synchronizing the writing of blocks in which the same data is stored between nodes that are the storage subjects of the block.

In addition, blockchain technology can be applied to general-purpose computer equipment, providing a cost-effective deployment without expensive hardware and software equipment.

Korea Patent Registration 10-1637868 (2016.07.01)

SUMMARY OF THE INVENTION The present invention was created with the knowledge of the prior art as described above, and an object thereof is to provide an apparatus and method for efficiently using a storage space of data using a blockchain technology without limiting the block size of a file system.

Another object of the present invention is to provide a service in which a device is set to a mode where only a service provider can access the data without allowing the user to access the data in an open book accessible to anyone. .

Another object of the present invention is for the device to manage the data without a fee by eliminating the fee of the service of the open ledger.

Another object of the present invention is to perform data validation by simplifying a proof-of-work process of a mining node based on a private mode and a removed fee.

Another object of the present invention is to adjust the block generation time by giving a delay to delay the speed of block generation that is accelerated by a simplified mining process, and to generate a block only when a transaction to be stored is generated.

According to an aspect, a block chain formed by a plurality of node terminals to synchronize and store data, and an apparatus for managing storage, inquiry, and deletion of data of the block chain may be configured using the chain information provided by an inquiry request. A main control unit controlling a management of the data by transmitting a data command for managing the data to the node terminal using a chain command for managing a block chain and mapping information provided by an inquiry request; And receiving the chain information of the chain generated by the chain command from the main controller, storing the chain information in a chain table, querying and providing the stored chain information according to the request, and storing the data stored by the data command from the main controller. And a DB management unit which receives the mapping information of the transaction, stores it in the chain table, and searches and provides the stored mapping information according to the request.

The blockchain may include a first function of providing a private mode in which data access is permitted only to a user whose authority is defined; A second function that is free of fees for data processing of the blockchain; A third function of removing a verification process of a node and performing a data validation process in a process of proving a mining node's work for a node terminal required for a block chain; A fourth function of delaying a block generation time by giving a delay to delay a generation time of a block shortened by the proof-of-work process; And at least one or more functions of the fifth function of generating a block only when a transaction to be stored is generated and executed in each node terminal.

The apparatus further includes a web management unit which provides a user interface through a web page to receive management information of the chain and data, and provide a processing result of the input management information.

The apparatus may further include a scheduler configured to register the scheduling information for management and request the main controller to execute a process corresponding to the registered scheduling information, wherein the main controller transmits a command corresponding to the request. do.

According to another aspect, the node terminal comprises: a mining API node terminal for generating a block through a mining process and data information of the block chain through an application program interface (API); And a data synchronization node terminal in which data management of the block chain is synchronized by the mining API node terminal.

The mining API node terminal may include: a chain generation unit configured to receive the chain command, process generation, deletion, and execution of a block chain according to the received chain command, and respond to a processing result; A command processor for receiving the data command, processing the received data command, and responding to the processing result; And a block chain processing unit that executes a data command according to the processing on the block chain.

The data synchronization node terminal may include: a chain generation unit configured to receive the chain command, process generation, deletion, and execution of a block chain according to the received chain command, and respond to a processing result; And a block chain processing unit connected to the block chain processing unit of the mining API node terminal in synchronization with the data command transmitted through the connected port.

According to another aspect, the main controller generates a chain ID from the file information of each data file managed by the block chain, generates a port ID by applying a formula to the generated chain ID, and generates the chain ID. Create a folder path for the files stored in the blockchain.

The main control unit receives file information of a data file to be stored, inquires chain information corresponding to the input file information from the chain table, and transmits the data command according to the inquired chain information to the node terminal. Requests data storage, receives the storage result of the data command, and the DB manager maps the mapping information including the file ID of the transmitted storage result, the transaction ID generated during the storage by the blockchain, and the storage time. Save to a table.

The main control unit transmits the chain command requesting generation and execution of a block chain having the generated chain ID when the chain information generated from the chain information fails to inquire the chain information from the chain table. Receiving the execution result of the chain command, the DB manager generates the chain information including a chain ID, a root directory, and an execution state for each chain by using the transmitted execution result, and generates the generated chain information. Store in the chain table.

The main controller receives file information of a data file to be queried, inquires mapping information corresponding to the input file information from the mapping table, and transmits the data command according to the inquired mapping information to the node terminal. Requesting data inquiry, receiving the inquiry file and the inquiry result of the data command, and providing the transmitted file.

According to yet another aspect, a blockchain formed by a plurality of node terminals for synchronizing and storing data, and a method for storing a data file by an apparatus managing data of the blockchain may include: from file information of a data file to be stored; Generating a chain ID; Querying the chain information from the chain table using the generated chain ID as a key; Generating a data command requesting storage of the file according to the inquired chain information, and transmitting the generated data command and file to the node terminal and storing the data command in the block chain; And storing mapping information of data and transactions in a mapping table by using a result of storing the file received from the node terminal.

According to another aspect, a blockchain formed by a plurality of node terminals for synchronizing and storing data and a method for inquiring a data file by an apparatus managing data of the blockchain may include an ID of a file to be queried from a user terminal. Receiving an input; Retrieving mapping information from the mapping table using the input file ID as a key; Generating a data command for requesting the inquiry of the file according to the inquired mapping information and transmitting the generated data command to the node terminal; Receiving a data file queried from the node terminal; And transmitting the received file to the user terminal.

According to an aspect of the present invention, the data is stored in the storage area of the blockchain from which empty space is removed according to the block size limitation of the file system, thereby enabling efficient data storage in preparation for the storage area.

In addition, according to another aspect of the present invention, since only the user whose authority is set by the private mode set in the blockchain can access and manage the data through the management server, data security can be maintained.

Further, according to another aspect of the present invention, by configuring a node terminal as a command node for receiving a command from the management server to provide a mining function and an API function and a synchronization node in which data is synchronized to the command node, data security and data backup Can be provided.

In addition, according to another aspect of the present invention, it is possible to build a blockchain-based DB at a low cost because by eliminating the fees of the service of the open book according to the transaction of the blockchain to manage data without a fee.

The following drawings attached to this specification are illustrative of preferred embodiments of the present invention, and together with the detailed description of the invention to serve to further understand the technical spirit of the present invention, the present invention is a matter described in such drawings It should not be construed as limited to.
1 to 5 are exemplary diagrams of a blockchain to which the present invention is applied.
FIG. 2 is a schematic internal configuration diagram of the network management system of FIG. 1.
6 is a schematic structural diagram of unique functions set in the blockchain of the present invention.
7 is a schematic internal configuration diagram of a data management system according to an embodiment of the present invention.
8 is a schematic flowchart of a method for storing data in a blockchain according to an embodiment of the present invention.
9 is a schematic flowchart of a data inquiry method according to an embodiment of the present invention.

Hereinafter, exemplary embodiments of the present invention will be described in detail with reference to the accompanying drawings. Prior to this, terms or words used in the present specification and claims should not be construed as being limited to the common or dictionary meanings, and the inventors should properly explain the concept of terms in order to explain their invention in the best way. Based on the principle that can be defined, it should be interpreted as meaning and concept corresponding to the technical idea of the present invention. Therefore, the embodiments described in the specification and the drawings shown in the drawings are only the most preferred embodiment of the present invention and do not represent all of the technical spirit of the present invention, various modifications that can be substituted at the time of the present application It should be understood that there may be equivalents and variations.

1 is an exemplary view of a block chain 100 to which the present invention is applied.

The blockchain 100 is a distributed database built on cloud storage and P2P functions. Typically, Bitcoin, Ethereum, etc. are provided on the blockchain. The block chain 100 is composed of blocks 101 of a unit in which data is stored and a chain 102 corresponding to a data link between the blocks.

The blockchain 100 is a distributed / relational data DB and stores data using a storage area allocated to the DB independently from the file system as one area. Therefore, it is not limited by the block size dependent on the file system. Therefore, no empty area generated by the limitation of the block size is generated.

2 is an exemplary diagram of a node terminal 200 in which the blockchain 100 of FIG. 1 is constructed.

The node terminal 200 is a computer device that provides a storage space for data. The node terminal 200 is not limited to the specification as long as it has a network function, a storage function, and a processing function as a smart terminal, a notebook computer, a PC, a server, and the like. In a blockchain, the computer device is called a node.

3 illustrates that four unique chains 300 are installed in the node terminal 200 of FIG. 2.

Due to the nature of open book technology, it is a common method that one chain is performed on one node terminal 200. This is because the book record of the monetary transaction has one open book to ensure the reliability of the data, and each node maintains and manages the same open book in one chain based on synchronization and openness.

However, since the present invention aims to manage and classify data such as documents, images, and the like, which are not kept in the open book, the distribution of data based on a plurality of chains classified according to the purpose is desirable.

4 is an exemplary diagram in which three node terminals 200 are synchronized through pairing for four chains.

Each node terminal 200 has four unique block chains # 1 to # 4. Each chain establishes pairings 401-404 and data is synchronized. Each chain can be described as consisting of three nodes. That is, each chain # 1 stored in the three node terminals 200 is synchronized by the first pairing 401 to store the same data. When synchronization, processing such as storing or deleting data occurs in the chain # 1 of the first node, the same data processing is performed for the chain # 1 of the second and third nodes remaining in the first pairing 401. Is generated.

Technically, paired chains communicate using the same port. Each chain of # 1 to # 4 can operate as an independent chain by using unique ports.

5 is an exemplary diagram of a plurality of node groups operating in the blockchain environment of FIG. 4.

The node terminal 200 is composed of node group # 1 500 and node group # 2 501 composed of three nodes. Node group # 1 500 holds chains # 1 to # 4 for each node, with each chain paired. Node group # 2 501 holds chains # 5-# 8 for each node, with each chain paired. Pairing connections between each chain are omitted for simplicity.

Compared with one node having eight chains of # 1 to # 8, the load may be distributed by separate node groups. In order for one chain to operate, resources such as CPU, memory, and storage space are required. In order to execute several chains simultaneously, loads are concentrated on one node, so that loads can be divided into node groups. In addition, through load balancing, even if one node of a group node physically fails, the influence on service operation can be reduced. If a node storing eight chains fails, data access to the eight chains is disabled.

6 is a schematic structural diagram of modification functions set for the blockchain of the present invention.

The present invention is subject to the unique functions of the blockchain. First, the use of blockchain DBs eliminates waste of storage space. Second, because data is contained in blocks in the blockchain, access to this data requires special privileges (administrator accounts) to increase security. Third, synchronization is supported between the nodes held by the blockchain, enabling real-time backup to avoid the risk of original loss. Finally, cost savings can be achieved by using x86 servers and open source to build a system using blockchain technology without expensive equipment or software.

At this time, conventional techniques representing blockchain technologies such as Bitcoin or Ethereum cannot be directly applied. Implementation of the present invention requires an optimized separate chain. Of course, it is also possible to implement the blockchain of the present invention by modifying and applying the prior art. Preferably, the present invention can be applied from the blockchain of Ethereum. In the case of bitcoin, the technology is optimized only for the purpose of circulation and use of money, and it is not suitable for general data storage proposed in the present invention because the technology such as smart contract has not been implemented. Of course, Ethereum's blockchain method is not available as it is, and a correction function of the first to fifth functions described below is required.

By the first function, the network configuration between the nodes in the blockchain is set to the private mode. The service does not need to be disclosed to other users because only authorized users can use it.

By the second function, the data processing of the blockchain is set to have no fee. Blockchain technology is originally a public database of decentralized powers. Thus, there is a fee for using a public database called blockchain. However, since the present invention is operated as a user-only database rather than a public database, the concept of fees is unnecessary. Therefore, the code should be set up so as not to incur a fee.

By the third function, the POW (Proof of Work) process of the mining node is set to be simplified. Any public blockchain provides financial benefits to nodes that have performed a process called mining to induce voluntary participation as nodes in the chain. This mining process is to maximize the use of HW resources, which is also unnecessary to the type of service to which the present invention applies. Therefore, only the validation part of the data is left during the mining process, and processes such as finding nonce values by random hash calculation are removed so that blocks are generated quickly and resources such as CPU / memory are minimized.

By the fourth function, the delay is set so that the block can be generated at an appropriate speed because the speed of generating the block is unnecessarily faster in the simplified mining process of the third function. The delay setting delays the generation rate of the block.

By the fifth function, the conventional blockchain is set to proceed with block generation only when there is a transaction to process because empty blocks are constantly generated even in the absence of a transaction but are unnecessary overhead in the present invention.

The blockchain in which the above-described correction functions of the first to fifth functions are set is applied to the present invention. Hereinafter, for convenience of description, the credit card company stores the data file of the signature image generated when the customer pays the card in the blockchain of the present invention. Of course, the present invention does not limit the content and format of the data file.

The credit card company stores the signature image of the customer transmitted from the POS terminal to the VAN company in a separate file. For each approval, the serial number assigned by the VAN company is assigned, and this serial number is used as the file name. Save it as a bitmap file (eg serial number.bmp). It is assumed that the serial number is unique information including the time of occurrence of the card settlement. When a file of a signature image is stored by a file system of about 2KB, it is inefficient because a 6KB empty area remains due to a block size limitation.

Here, it is assumed that 5 million 2KB signature image files are generated and stored for 5 years under the law. The number of files stored over five years is 5 million * 365 * 5 = 9,125,000,000. The file size is 16TB, with 9,125,000,000 * 2 * 1024.

Storing 16TB in one chain on one node is inefficient and load-intensive. Therefore, it is efficient to form a plurality of chains to reduce the data size. In the present invention, it is preferable to define the management unit of the chain in consideration of the characteristics that the data to be stored is generated. In the present invention, the chain is generated on a monthly basis of the signature image, and 60 chains stored for 5 years are operated, and the chain after 5 years is operated to be deleted every 1 month.

For reference, the way data is stored in the blockchain is stored in 'key / value' format. In the case of the file of the signature image, the file name is unique and thus can be utilized as a "key", and the image file corresponds to "value".

7 is a schematic internal configuration diagram of a data management system 700 according to an embodiment of the present invention.

The data management system 700 according to an embodiment of the present invention includes a management server 710, a mining API node terminal 730, and a data synchronization node terminal 750.

The management server 710 includes a web manager 711, a scheduler 713, a main controller 715, and a DB manager 717.

The web manager 711 provides a data management service using a user UI to a user terminal accessing a web site. The web manager 711 provides a management service to provide the current state of the chain, the current state of the records contained in the chain, and the data inquired from the chain to the user terminal.

Here, the "data management service" includes creation, inquiry, modification and deletion of each of the chain and the data. The web manager 711 provides a user UI to a user accessing a web site, receives a data management request through the user UI, and transmits the received user's request to the main controller 715. When the user's request is processed by the main controller 715, the web manager 711 receives the processing result from the main controller 715, and provides the user with the processing result received through the user UI. Of course, the result of processing is the result of the creation, inquiry, modification and deletion of the chain and the data.

The scheduler 713 registers scheduling information of data management, and requests the main controller 715 to execute a process of registered scheduling information. When the request of the scheduler 713 is processed by the main controller 715, the scheduler 713 receives a processing result of the scheduled process from the main controller 715.

When the web manager 711 is reserved data management from the user, the user's reservation information is registered in the scheduler 713 as the scheduling information. The web manager 711 may receive a management request from a user according to a real time or scheduling method. The registered scheduling information includes a time reserved by the user and reserved management information. For example, after a chain created monthly stores data for five years, a process deleted every one month may be registered as scheduling information.

The main controller 715 transmits a chain command for managing the block chain and a data command for managing the data to a node. By this transfer, the management of the blockchain and data is controlled. The main controller 715 generates a chain ID and a file ID according to a rule set from a file name of a file to be managed.

In the case of storage, the main control unit 715 generates a chain ID from the file name of the storage target, and inquires the chain information of the generated chain ID. The path information of the file is identified from the inquired chain information, and a data command and a file requesting that data be stored in the identified path information are transmitted to the node. The node then stores the file in the corresponding chain and path according to the path information.

In the case of inquiry, the main controller 715 inquires mapping information corresponding to the file name to be inquired. The data command of the data inquiry including the transaction ID of the inquired mapping information is transmitted to the node. Then, the node inquires a file corresponding to the transaction ID and transmits the inquired file to the main controller 715. The main controller 715 provides the received file to the user terminal through the web manager 711.

In the case of deletion, following the data command processing of the inquiry, the node deletes the corresponding file according to the transaction ID.

The DB manager 717 manages that the chain information of the generated chain is stored, inquired and deleted in the chain table. The DB manager 717 generates chain information including "chain ID, root directory, and execution status" for each chain using the execution result of the chain generation received through the main controller 715, and generates the generated chain information. Store in the chain table. A chain ID is information that uniquely identifies a chain. The root directory is the root directory where the chain is stored. The chain ID and root directory form path information that identifies the chain corresponding to the file. The execution state is referenced for the execution of the chain if the chain in which the file is stored for execution of the administrative command is not in the execution state.

Subsequently, when a file storage request is generated, the DB manager 717 inquires the chain information corresponding to the file to be managed from the chain table according to the inquiry request from the main controller 715. The information on the chain and the access path corresponding to the file is identified from the inquired chain information, and the main controller 715 may issue a data command for storing the file using the identified information.

In addition, the DB manager 717 manages that the data that has been stored and the mapping information of the stored transaction are stored, inquired, and deleted from the mapping table. The DB management unit 717 uses the storage result of the data storage received through the main control unit 715 to map the mapping information including the file ID and the "file ID, transaction ID and storage time" generated when the data is stored by the blockchain. Save to mapping table. The file ID is a unique key that is generated from the file name and identifies the file. The transaction ID is unique information that the blockchain uniquely generates and accesses to the file by the storage of the file. The storage time is the processing time of the transaction.

Then, when a request for management (eg, inquiry, deletion, etc.) of the stored file is generated, the DB manager 717 inquires the mapping information corresponding to the file to be managed from the mapping table according to the inquiry request from the main controller 715. . Transaction information corresponding to the file is identified from the inquired mapping information, and the main controller 715 may issue a data command for managing the stored file using the identified transaction information.

The management server 710 controls the management of the blockchain and data for the mining API node terminal 730 and the data synchronization node terminal 750 connected by WAS port communication. The node terminal 200 corresponds to the mining API node terminal 730 and the data synchronization node terminal 750.

The mining API node terminal 730 receives various commands from the main control unit 715 through WAS port communication, generates a block according to the received commands, connects them to the chain, and manages commands (for example, storage / An inquiry, etc.), processes the received command, and responds to the main controller 715 with the processing result. The mining API node terminal 730 includes a chain generation unit 731, a block chain module 733, an instruction processor unit 735, and a block chain processing unit 737.

The chain generation unit 731 receives a chain command for managing a chain from the main control unit 715, and performs a generation, execution (drive), and deletion process of a chain corresponding to the received chain command. The "Chain Maker" of the block chain is the chain generation unit 731.

Here, in order for a chain to be created on a node, the chain's executables and ancillary configuration files must be distributed in advance to the promised directory of each node. The chain generation unit 731 processes the chain command by using the block chain module 733 including distributed executable files and configuration files. If the chain instruction is a delete, the running processor is stopped and the files created due to the chain operation are deleted.

The command processor 735 receives a data command for managing data from the main controller 715, and stores, inquires, and deletes data corresponding to the received data command. The command processor 735 transfers the data command received from the main controller 715 to the blockchain process 737. The command processor 735 is connected to an external service to receive the data command. Although possible, a secure connection is required.

The block chain processor 737 receives a data command from the command processor 735 to perform data management. By performing data management, data is stored, inquired and deleted in the chain. In addition, the block chain processing unit 737 is synchronized with the block chain processing unit 757 of another node through a synchronization port communication by a pairing function.

The data synchronization node terminal 750 includes a chain generation unit 751, a block chain module 753, and a block chain processing unit 757. The chain generation unit 751 and the block chain module 753 have the same configuration as the mining API node terminal 730. In addition, the block chain processing unit 757 is synchronized with the block chain processing unit 737 of the mining API node terminal 730.

The difference between the mining operation and the API operation is performed only in the mining API node terminal 730. Of course, the command processor unit 735 may be provided in every node to correspond to the system fail-over. However, in the embodiment of the present invention, the mining operation and the window of the API operation for the management server 710 are unified to the mining API node terminal 730 to maintain data security, and to pair with the mining API node terminal 730. By doing so, the data synchronization node terminal 750 is synchronized to provide data backup. That is, in terms of data security, only an authorized user can access the management server 710, and only an authorized management server 710 can access the mining API node terminal 730. Is blocked.

Here, the WAS port communication between the main controller 715 and the node terminals 730 and 750 is assumed to be implemented in the form of a Java Servlet, and is performed through a port used by a Web Application Server such as Tomcat and JBOSS. .

An RPC (Remote Procedure Call) port is used between the command processor unit 735 and the block chain processing unit 737. The sync port is used for synchronization between the blockchain processing units 737 and 750. The IDs of the Sync and RPC ports can be calculated from the chain ID.

8 is a schematic flowchart of a method for storing data in a blockchain according to an embodiment of the present invention.

An event of file storage occurs in the management server 710. File storage may request the user to save the file through the web site of the web manager 711. In addition, an event of file storage may occur by the batch processing or the scheduler 713 or the like. When the file to be stored is stored in the designated directory of the web site, the main control unit 715 receives a notification of event occurrence (S801).

The main controller 715 generates a chain ID using file information (eg, file name, file time, etc.) of the file according to the service policy (S811). Here, a chain ID, a unique key, a port number, etc. may be generated from the file information. The creation rule involves processing such as extracting, converting, and calculating a unique value from a file name, with no special limitation.

In the case of the signature image, a chain ID of year (2) + month (2) is extracted from the file name of the date time and generated. For example, a signature image file generated in January 17, '1701' is included in a file name, and a chain ID of '1701' extracted from the file name is generated. If the unique key has a unique file name, the file name can be used as it is, and the generation rule can be applied. The port number is generated using the following formula.

<Formula>

Sync Port = Chain ID + 10000

RPC  Port = Sync Port + 3000

Then, in the case of the '1701' chain ID, the synchronization port of the block chain processing units 737 and 757 is '11701', and the RPC port of the command processor unit 735 is '14701'.

When the chain ID is generated, the main controller 715 inquires the chain information by inputting the chain ID to the DB manager 717 (S821). The DB manager 717 inquires the chain table using the chain ID as a key, inquires the chain information including the chain ID, the root directory, and the execution status of the chain, and provides the inquired chain information to the main controller 715.

If the inquiry of the chain information fails (S823), the main controller 715 generates a chain command including a chain name and a path name including a root directory and generating a chain, and generates the chain command of each node. Transmission to the chain generation units 731 and 751 (S825). The chain generation units 731 and 751 generate and execute a chain according to the received path name. When generation of the chain is completed, the chain generation units 731 and 751 respond to the main control unit 715 with the generation result. The main controller 715 stores the chain information in the chain table through the DB manager 717 using the generated result.

For the signature image, if the root directory is '/ CHAIN_DATA' and the chain ID is '1701', the path name of the data directory may be '/ CHAIN_DATA / datadir_1701' according to the defined service policy. When the signature image generated on a monthly basis is stored in the corresponding chain, when the storage of the first data of each month occurs, a chain command for generating a chain is executed. If the chain storage space of '/ CHAIN_DATA' is insufficient, the user can solve the extension issue by changing this location to another storage area such as '/ CHAIN_DATA2'.

In addition, if the execution state of the inquired chain information is not running (S827), the main controller 715 generates a chain command including a chain ID and a path name including the root directory and executes the chain, and generates the generated chain command. Transmission is performed to chain generation units 731 and 751 of each node (S829). The chain generation units 731 and 751 execute the chain according to the received path name. The execution status of the chain table is updated to be executed by the execution of the chain. For processing efficiency, the chain can end execution once processing is complete.

After the chain information of the running chain is inquired, the main controller 715 generates a unique file ID from file information (eg, file name, file time, etc.) of the file. The generated file ID corresponds to a key for identifying the file. In order to generate the file ID, various conversions, hash processing, and the like may be applied to the file information. Of course, if the file name is unique, the main controller 715 may use the file name as the file ID. The main controller 715 generates a data command including the inquired chain information and the generated file ID, and transmits the generated data command and file to the command processor 735 to store the file (S831).

Here, the command processor 735 transmits the received data command to the block chain processing unit 737 so that data is stored in the block chain. The file information stored in the blockchain follows the RDB format of the key / value, and other meta information related to the file (such as a unique key) may be further stored. When data is stored in the blockchain by the blockchain processing unit 737, the synchronized blockchain processing unit 757 also receives data commands and files through the synchronization port, and stores and synchronizes the files.

When file storage is completed, the command processor 735 responds to the main controller 715 with a result of storing the transaction ID of the stored file by the API operation. The transaction ID is uniquely generated when data transactions are stored on the blockchain. The main controller 715 stores the mapping information in the mapping table through the DB manager 717 using the response of the stored result. The meta information of the file may be further stored in the mapping table.

Steps S801 to S843 are repeated until storage of files stored in the directory of the web site is completed. After the storing of the files is completed, the main controller 715 deletes the stored files from the directory (S845).

Thereafter, the main controller 715 transmits the chain command to the node and deletes the chain satisfying the condition according to the service policy (S851). In the case of signature images, chains that are five years and one month old are automatically deleted from the node.

9 is a schematic flowchart of a data inquiry method according to an embodiment of the present invention.

An event of file inquiry occurs in the management server 710. In the file inquiry, a corresponding event may be generated by a request of a user connected to a web site, a batch process, or a scheduler 713. The main controller 715 receives the file ID by notifying that the event of file inquiry has occurred (S901).

Here, the main controller 715 may search the mapping information of the mapping table and provide the searched mapping information to the web manager 11 to provide a search service for the user to select a file to be queried.

The main controller 715 inquires the mapping information from the mapping table using the received file ID as a key (S903). If mapping lookup fails, provide an appropriate error message that no record to delete exists. In addition, depending on the type of service, a function of refusing to provide the data when a specific date has passed may be added at this stage.

When the mapping information is inquired, the main controller 715 generates a data command including a transaction ID of the mapping information and requests for inquiry of data (S911), and transmits the generated data command to the command processor unit 735 to send a file. Request an inquiry (S913).

Here, the command processor 735 transmits the received data command to the block chain processing unit 737 to request an inquiry of a file stored in the block chain. The file of the transaction ID is inquired by the blockchain processing unit 737, and the command processor 735 transmits the inquired file and the processing result to the main control unit 715 according to the API operation. The main control unit 715 downloads and receives a file from the command processor unit 735 (S921). The downloaded file is downloaded to the user through the web management unit (S931).

Steps S901 through S931 may be repeated until the inquiry of the requested files is completed. After the download service of files is completed, the main controller 715 deletes the downloaded files from the download directory.

On the other hand, the main controller 715 may be accompanied by encryption and decryption processing for data security in the process of storing and retrieving the file. It is also possible to provide a service that shows the contents of a document file or an image file according to the service policy of a web site.

Although the present invention has been described by way of limited embodiments and drawings, the present invention is not limited thereto, and the technical spirit of the present invention and the claims to be described below by those skilled in the art to which the present invention pertains. Of course, various modifications and variations are possible within the scope of equivalents.

700: data management system: 710: management server
711: Web management unit 713: Scheduler unit
715: main control unit 717: DB management unit
730: mining API node terminal 750: data synchronization node terminal

Claims (1)

An apparatus for managing storage, inquiry, and deletion of a block chain formed by a plurality of node terminals to synchronize and store data, and data of the block chain,
A chain command for managing the block chain using the chain information provided by the inquiry request and a data command for managing the data using the mapping information provided by the inquiry request to the node terminal to control the management of the data. Main controller; And
Receiving the chain information of the chain generated by the chain command from the main control unit and storing the chain information in the chain table, querying and providing the stored chain information according to the request, and storing the data stored by the data command from the main control unit; DB management unit that receives the mapping information of the transaction and stores it in the chain table, and provides the stored mapping information in response to the request
Device comprising a.

Images