KR20210050846A - System for managing data for documents based on blockchain system - Google Patents

Abstract

The present invention relates to a system for managing an electronic document based on a blockchain technology. More specifically, the present invention relates to a system for managing document data based on the block chain technology comprising: a plurality of main nodes participating in the main blockchain; and a storage part for storing document data, wherein the predetermined main node transfers a predetermined document data to the storage part when a transaction for the predetermined document data is made in a predetermined main node among the plurality of main nodes, and the storage part stores the received predetermined document data. Therefore, the present invention is capable of providing a system with improved reliability.

Description

System for managing document data based on blockchain technology {SYSTEM FOR MANAGING DATA FOR DOCUMENTS BASED ON BLOCKCHAIN SYSTEM}

The present invention relates to a system for managing document data based on a block chain technology, and more specifically, to a document management system that improves reliability by lowering the risk of forgery and alteration of a document, and facilitates future destruction of documents.

Blockchain technology refers to a data distribution processing technology that distributes and stores all the data that are subject to management by all users participating in the network. It is also called'distributed ledger technology (DLC)' or'public transaction ledger' in that the ledger containing transaction information is not owned by the transaction entity or a specific institution, but is shared by all network participants. . Blockchain is a name given as a chain of blocks containing transaction details.

These blockchains can be divided into public blockchains and private blockchains. The public blockchain corresponds to the public transaction ledger described above, and generally refers to the public blockchain when it comes to blockchain. Private blockchain is a relative concept, and is also referred to as enterprise blockchain because it is mainly used by companies. Consortium blockchain, in which several companies (or institutions) jointly participate, also belongs to the category of private blockchain in a broad sense.

Unlike public blockchains, which are open to anyone and allow anyone to create transactions, private blockchains can participate only with the approval of a service provider (corporate or institution), and only legally responsible organizations can create transactions. In addition, unlike the public blockchain, in which transaction details are open to all, and all nodes participating in the network verify it and approve the transaction, in the private blockchain, only authorized organizations verify the transaction and approve the transaction.

The public blockchain has a high reliability through mutual verification of all participants, but it has the disadvantage that the processing speed is slow to record and share the transaction records of all participants. In contrast, the private blockchain is much faster because only authorized nodes participate and there is no need to seek verification of other nodes. However, since the users of the private blockchain must completely rely on the service provider, the reliability is limited compared to the public blockchain.

Such a blockchain can be used in various industrial fields, and it will be most suitable especially for fields where reliability against forgery and alteration must be secured. Verification work such as authentication for users or verification of documents is inevitable to be continuously exposed to the risk of forgery or alteration, and securing reliability will be more urgent than work in other industries.

Blockchain technology can have near-integrity reliability because it cannot delete or modify existing data, but there are also disadvantages resulting from this. For example, documents containing personal information should be destroyed after being used for a purpose, but if it is based on blockchain technology, the destruction of issued documents becomes impossible. In other words, once issued, the document is maintained in a state that can be viewed at any time by a third party, unless the system itself is interrupted.

Therefore, there is a need for research on a system that can destroy documents while improving reliability from the risk of forgery and alteration of documents based on a blockchain system.

It is an object of the present invention to solve the above and other problems. Another object is to provide a document issuing system with improved reliability from the risk of forgery and alteration.

Another object is to provide a document issuing system that facilitates destruction of published documents.

The technical problems to be achieved in the present invention are not limited to the technical problems mentioned above, and other technical problems that are not mentioned will be clearly understood by those of ordinary skill in the technical field to which the present invention belongs from the following description. I will be able to.

According to an aspect of the present invention to achieve the above or other objects, there is provided a system for managing document data based on a blockchain technology, comprising: a plurality of main nodes participating in a main blockchain; And a storage unit for storing document data, wherein when a transaction for predetermined document data is made in a predetermined main node among the plurality of main nodes, the predetermined main node transfers the predetermined document data to the storage unit, and the The storage unit provides a system for managing document data, characterized in that the received predetermined document data is stored.

At this time, the storage unit stores a plurality of document data in a manner that matches the document data with a key value indicating the document data, and when receiving a request to view the document data stored in the storage unit, the The stored document data matched to the key value included in the received view request may be returned.

When a request to destroy any one of the document data stored in the storage unit is received, the storage unit may delete a key value matched to the requested document data and stored.

The storage unit may include a plurality of sub-nodes participating in the sub-blockchain, and the plurality of sub-nodes may form a plurality of sub-blocks.

When the storage unit stores the received predetermined document data, when the predetermined document data to be stored is divided into a plurality of data and the plurality of sub-blocks are formed, the divided plurality of data is transferred to the plurality of sub-blocks. Can be divided and stored.

The transaction for the predetermined document data is a transaction for transmission and reception of an e-mail, and the predetermined document data may be an attachment file of the transmitted and received e-mail.

The transaction for the predetermined document data is a transaction for at least one of issuance, distribution, and destruction of an electronic certificate file, and the predetermined document data may be the electronic certificate file.

In order to achieve the above or other objects, according to another aspect of the present invention, a system including a storage unit for storing document data and a plurality of main nodes participating in the main blockchain to manage document files based on blockchain technology In the control method of, when a transaction for predetermined document data is made in a predetermined main node among the plurality of main nodes, the predetermined main node transmitting the predetermined document data to the storage unit; And storing the received predetermined document data by the storage unit. A method of controlling a system for managing document data is provided.

The effect of the document management system according to the present invention will be described as follows.

According to at least one of the embodiments of the present invention, there is an advantage in that it is possible to provide a document management system with improved reliability from the risk of forgery and alteration of documents.

In addition, according to at least one of the embodiments of the present invention, even if it is based on blockchain technology, there is an advantage in that it is possible to provide a document management system capable of destroying an issued document after it is used for a purpose.

Further scope of the applicability of the present invention will become apparent from the detailed description below. However, since various changes and modifications within the spirit and scope of the present invention can be clearly understood by those skilled in the art, specific embodiments such as the detailed description and preferred embodiments of the present invention should be understood as being given by way of example only.

1 is a diagram showing the structure of a block chain according to an embodiment of the present invention.
2 is a diagram illustrating an extension relationship between a main block chain and a sub block chain according to an embodiment of the present invention.
3 is a flowchart of a document management system according to an embodiment of the present invention.
4 is a diagram showing a procedure for checking an issued document according to an embodiment of the present invention.
5 is a flowchart illustrating a procedure for destroying an issued document according to an embodiment of the present invention.
6 is a flowchart of a document management system according to a second embodiment of the present invention.
7 is a diagram illustrating a procedure for confirming an issued document according to an embodiment of the present invention.
8 is a flowchart showing a procedure for destroying an issued document according to the second embodiment of the present invention.

Hereinafter, exemplary embodiments disclosed in the present specification will be described in detail with reference to the accompanying drawings, but identical or similar elements are denoted by the same reference numerals regardless of reference numerals, and redundant descriptions thereof will be omitted. The suffixes "module" and "unit" for constituent elements used in the following description are given or used interchangeably in consideration of only the ease of writing the specification, and do not themselves have a distinct meaning or role from each other. In addition, in describing the embodiments disclosed in the present specification, when it is determined that a detailed description of related known technologies may obscure the subject matter of the embodiments disclosed in the present specification, the detailed description thereof will be omitted. In addition, the accompanying drawings are for easy understanding of the embodiments disclosed in the present specification, and the technical idea disclosed in the present specification is not limited by the accompanying drawings, and all changes included in the spirit and scope of the present invention It should be understood to include equivalents or substitutes.

Terms including ordinal numbers such as first and second may be used to describe various elements, but the elements are not limited by the terms. The above terms are used only for the purpose of distinguishing one component from another component.

When a component is referred to as being "connected" or "connected" to another component, it is understood that it may be directly connected or connected to the other component, but other components may exist in the middle. It should be. On the other hand, when a component is referred to as being "directly connected" or "directly connected" to another component, it should be understood that there is no other component in the middle.

Singular expressions include plural expressions unless the context clearly indicates otherwise.

In this application, terms such as "comprises" or "have" are intended to designate the presence of features, numbers, steps, actions, components, parts, or combinations thereof described in the specification, but one or more other features. It is to be understood that the presence or addition of elements or numbers, steps, actions, components, parts, or combinations thereof does not preclude in advance.

Blockchain technology is currently being actively used in financial systems. Hereinafter, a method applied in the financial system will be described.

Blockchain is a core concept of decentralization, which aims for P2P (Peer to Peer) transactions, away from the existing financial system that secures and manages all transactions in financial institutions. P2P refers to a communication network that connects personal computers without a server or client, and each connected computer acts as a server and a client to share information.

In the existing financial system, financial companies have kept transaction records on a central server, whereas in a blockchain based on the P2P method, transaction information is stored in blocks and connected in sequence, which is shared by all participants.

Blockchain technology processing for the transaction process (transaction, transaction) in the financial system is performed as follows. ① A requests for a transaction, such as a request for remittance, to B. ② A block containing the transaction information is created. ③ When the block is transmitted to all participants on the network, the participants mutually verify the validity of the transaction information. ④ The transaction details that match the data of the majority of participants are checked with the normal ledger, and the verified block is linked to the previous block, and a copy is made and distributed and stored on each user's computer. ⑤ A transfers money to B and the transaction is completed. At this time, all transactions that have occurred within a preset period (for example, about 10 minutes) can be generated as one block.

Through this process, by checking whether the data of the majority of participants match or not, it is possible to secure the reliability even when the block is created, as well as to prevent forgery by storing a copy of the completed blocks individually in each computer (node). Makes it practically impossible.

The proof system in the present invention is intended to be applied to various operations related to document data (hereinafter, all operations recorded in the blockchain are referred to as transactions), instead of proof of transactions used in the financial system as described above.

Hereinafter, terms related to blockchain will be described.

· Block

A block is a unit that stores data and is divided into a body and a header. The body contains the transaction details, and the header contains encryption codes such as merkle hash (merclout) and nonce (an arbitrary number related to encryption). Blocks are created every about 10 minutes, and they are connected to the previous block to form a block chain while collecting transaction records and creating blocks to verify reliability. The block that starts here is called the genesis block. In other words, the genesis block refers to the first block in which no block has been created before it.

· Node

Blockchain does not store and manage transaction records on a centralized server, but individual servers participating in transactions gather to maintain and manage the network. This individual server, or participant, is called a node. Since there is no central manager, the role of the node distributing blocks is important, and a new block is created only when more than half of the participating nodes agree. Nodes store the blockchain in their computers, and even if some nodes are hacked and the existing contents are changed, data remains in multiple nodes, so data can be preserved continuously.

· Hash function

It is a function that produces a result of the same length no matter what data is entered. It is unlikely that the resulting result will be duplicated, and it is difficult to inversely estimate the input value as the result value. For this reason, by comparing the hash values, it is possible to determine whether data has been changed. As for the hash function, SHA-2 (SHA 256) in a more advanced form came out after SHA (Secure Hash Algorithm)-1 was first devised, which is being used in the blockchain. SHA-2 results in 256 bits no matter what length value is entered.

1 is a diagram showing the structure of a block chain according to an embodiment of the present invention. 2 is a diagram illustrating an extension relationship between a main block chain and a sub block chain according to an embodiment of the present invention.

The proof system according to an embodiment of the present invention may include a main blockchain 110 and a storage unit 190 in which at least two main nodes 111-1 to 111-3 participate. In addition, according to an embodiment of the present invention, the storage unit 190 may be configured to include a sub-blockchain 120 in which at least two sub-nodes 121-1 to 121-4 participate.

The main block chain 110 may form a main block at a preset cycle based on the main transaction, and the sub block chain 120 may form a sub block at a preset cycle based on the sub transaction. That is, blocks generated between the main blockchain 110 and the sub-blockchain 120 are not connected to each other or a verification procedure is performed.

In this way, the relationship between the blocks is blocked, but the main blockchain 110 and the sub-blockchain 120 may transmit and receive data by a connection node. At least one of the main nodes 111-1 to 111-3 participating in the main blockchain 110 is the main connection node 111-3, and the sub-nodes 121-1 to participating in the sub-blockchain 120 At least one of 121-4) is a sub-connection node 121-1, and the main and sub-connection nodes 111-3 and 121-1 are provided to connect the main and sub-block chains to each other.

In this case, being connected to each other may mean exchanging data. In one embodiment of the present invention, it is proposed to exchange data between the connection nodes only under a specific condition (only in a specific situation). For example, in an embodiment of the present invention, data may be exchanged to store or destroy document data.

In this way, the main block chain 110 and the sub block chain 120 are separated to improve security for the document management system. According to the blockchain technology, all transactions can be disclosed to the public, because in the case of documents that must be destroyed in the future, the contents of the document itself should not be indiscriminately disclosed to the public.

Furthermore, the sub-blockchain 120 can expand the number of blockchains themselves. As shown in FIG. 2, a plurality of sub-blockchains 120-1, 120-2, 120-3, ... may be connected to one main blockchain 110 to operate. At this time, the main connection node 111-3 of the main blockchain 110 is in a '1 to many' relationship with a plurality of sub-connection nodes (121-1, 130-1, 130-2 in FIG. 2). Will be able to connect.

Hereinafter, a specific method of storing and destroying document data based on this structure of the present invention will be described.

Document management system according to an embodiment of the present invention, a plurality of main nodes participating in the main block chain; And a storage unit for storing document data, wherein when a transaction for predetermined document data is generated in a predetermined main node among the plurality of main nodes, the predetermined main node transmits the predetermined document data to the storage unit, and the The storage unit stores the received predetermined document data.

Here, the document data means data for forming an electronic document. Such document data includes text data related to information (displayed text) to be displayed to the viewer, and metadata related to the document (e.g., document creation date and time information or document issuer information) that is not displayed to the viewer. Could be included.

Document data can include all of the various formats stored in the form of a file, for example, a birth certificate, graduation certificate, internship certificate or transcript provided in an electronic format, and a format for storing the data It will also include all of the various formats, such as pdf, docx or hwp.

Transaction on document data means creating various processes or actions related to the above document data as blocks of the blockchain.

A transaction for document data according to an embodiment of the present invention includes generating a block containing information related to the transmitted e-mail when transmitting an e-mail including an attached file (an electronic document). In this case, the document data will mean data on the attached file.

A transaction for document data according to another embodiment of the present invention may include generating a block containing document issuance related information. Document issuance, for example, when requesting a transcript or graduation certificate from a document issuing agency (academic certification system) will mean a series of issuance-related processes performed by the document issuing agency. That is, at this time, the document data will mean data on the electronic document that has been issued.

As described above, in order to secure reliability from the risk of forgery or falsification of document issuance or sending e-mail, it is intended to be recorded (created) in blocks of the block chain, but as described above, in the case of an e-mail attachment or issued certificate, it must be possible to destroy it later. will be. Because these documents contain personal information. However, if a block is created including the document data itself, since anyone can access and read the block, personal information included in the document cannot be protected.

Therefore, in the present invention, when the main blockchain 110 performs a transaction on document data, it is proposed that the document data is not included in the generated block.

For example, when performing a transaction for sending an e-mail including an attachment, the main blockchain 110 includes information on the date of transmission, information on the presence or absence of an attachment, information on the attachment file name, information on the sender, information on the recipient, subject information, or body text. Blocks containing information related to e-mail transmission, such as information, can be created. However, the block does not contain the document data of the attachment itself.

These attached files may be transferred to the storage unit 190 and stored by the storage unit 190.

3 is a flowchart of a document management system according to an embodiment of the present invention. 3 to 5 illustrate a case of issuing a document as an example, it will be apparent that the present invention is applicable to various transactions related to document data, but is not limited thereto. That is, the procedures of FIGS. 3 to 5 may be equally applied to a transaction for e-mail transmission including an attachment file.

In step S301, the requester 390 makes a document issuing request to the document issuing server 392. For example, a university student asks the student registration system to issue his or her transcript.

The document issuing server 392 may return the issued document to the requester 390 after performing the process required for issuing the document (step S302) (step S303). In response to the issued document, the file itself of the issued document can be returned, and after the URL link to download the file is delivered, the requester 390 is delivered so that the file can be downloaded through the URL link. It might be possible. The method of returning the issued document to the requester 390 does not limit the content of the present invention, and the issued document may be delivered in various ways.

After that, the document issuing server 392 delivers the issued document to the main blockchain 110 (or one of a plurality of main nodes) (step S304). At this time, information for performing a transaction in the main blockchain 110 may also be transmitted in step S304.

Based on the received information, the main blockchain 110 performs a transaction related to the document issuance (step S305). That is, a main block containing information related to document issuance (issuance requester information, issuance date and time information, issuer information, etc.) can be created. At this time, the document data of the issued document itself is not included in the generated main block, but is transferred to the storage unit 190 (step S306), and may be stored in the storage unit 190 (step S307).

Since the transaction related to the issuance of the document has been performed in step S305, it will not be possible to forgery whether or not the document is issued. In other words, when checking the authenticity of an issued document, it is possible to check the information stored in the main block to confirm that the document was actually issued properly. On the other hand, the document data itself is not stored in the main block.

Instead of storing the document data itself, an embodiment of the present invention proposes to include a key value for identifying (indicating) the document data in the main block. In addition, when the document data is stored in the storage unit 190, it may be stored in a form matching the corresponding key value. This is to view the document data later. To this end, in step S306, the key value may be transmitted together with the document data.

That is, as long as the key value stored in the main block and the key value are not deleted in the storage unit 190, the issued document is stored using the key value when checking the issued document (or checking forgery of the issued document). It will be able to be checked and viewed in section 190. A detailed process of checking/reading the issued document will be described with reference to the flowchart of FIG. 4.

4 is a diagram showing a procedure for checking an issued document according to an embodiment of the present invention.

The document confirmation requester 490 makes a document issuance confirmation request (step S401) to the document confirmation server 492 whether the document issuance is correct. For example, the request for confirmation of issuance of a document may be a verification of the authenticity of the document itself (forgery verification), or may include a verification of the authenticity of the issuance of the document (regarding the issuer or date of issuance). The document confirmation server 492 may have the same configuration as the document issuing server 392 of FIG. 3 or may be configured separately.

Subsequently, the document confirmation server 492 transmits the document issuance confirmation request to the main blockchain 110 (or one of a plurality of main nodes) (step S402). The main block chain 110 inquires the main block corresponding to the request (step S403). That is, it will be possible to search the main block containing the transaction and check the information (document issuance information) stored in the main block. In particular, it is possible to inquire the key value for confirming the document itself along with the document issuance information.

The main blockchain 110 requests to view the document stored in the storage unit 190 based on the inquired key value 450 (step S404). That is, since document data is not stored in the main block itself, a read is requested to check the document data stored in the storage unit 190. In this case, the view request may include a key value 450 corresponding to the document to be viewed.

The storage unit 190 searches for stored document data based on the key value 450 included in the view request (step S405). That is, the document data 451 stored in correspondence with the key value 450 is checked (452). In addition, the storage unit 190 may return the retrieved document data 451 to the main blockchain 110 (step S406).

The main blockchain 110 may return the document data 451 together with the document issuance information checked in step S403 (step S407). That is, the document confirmation requester 490 can check/read not only the information on the issuance of the document, but also the document data of the issued document, and the confirmed information is information stored in the blockchain and can doubt its reliability. There won't be. In this way, when checking the document issuance information and the issued document data, it will be possible to clearly check whether the issued document itself has been forged or altered, as well as whether or not the document has been issued.

As described above, personal information may be stored in the document data. Therefore, if the request of the requester 390 or a specific condition is satisfied, a procedure for destroying the issued document will be required. In other words, the issued document will have to be destroyed after it is used for its purpose. To this end, the present invention proposes a method of deleting the key value 450 stored in the storage unit 190 during the above process.

During the above process, the document data 451 stored in the storage unit 190 can be searched through the key value 450. If the same process as in FIG. 4 is performed while the key value 450 is deleted, the document data 451 may not be searched or viewed. In one embodiment of the present invention, although the document data 451 itself is not destroyed through such a method, it is proposed that the document data 451 is not substantially inquired or viewed, thereby producing a substantial destruction effect.

A procedure for destroying the issued document will be described below with reference to FIG. 5.

5 is a flowchart illustrating a procedure for destroying an issued document according to an embodiment of the present invention.

In step S501, the destruction requester 590 makes a request for destruction to the document destruction server 592. In addition, the document destruction server 592 transmits the request to the main blockchain 110. At this time, the document destruction server 592 may have the same configuration as the document verification server 492 or the document issuing server 392 or may be a separate configuration.

The main blockchain 110 inquires the key value for the document corresponding to the destruction request in the main block (step S503). The inquired key value 550 is transmitted to the storage unit 190 together with the document destruction request (step S504). When the request to destroy the document is received, the storage unit searches 552 for the stored key value 550 and deletes at least one of the key value 550 and the document data 551 of the corresponding data (step S505).

When at least one of the key value 550 and the document data 551 is deleted, the storage unit 190 tells the requester 590 that the document destruction is completed through the main blockchain 110 and the document destruction server 592. You can reply (step S506).

When at least one of the key value 550 and the document data 551 is deleted as described above, the document is virtually destroyed even if the other node participating in the main blockchain 110 does not allow inquiries/reviews. You will be able to achieve the same effect as you did.

Meanwhile, in an embodiment of the present invention, it is proposed that the storage unit 190 is configured based on the sub-blockchain 120. That is, when storing a document, it may be stored in sub-nodes 121-1, 121-2, ... in the form of sub-blocks, rather than simply storing them in storage. This is because the reliability is higher when stored in a block form.

That is, the storage unit 190 includes a plurality of sub-nodes 121-1, 121-2, ... participating in the sub-blockchain 120, and a plurality of sub-nodes 121-1, 121- 2, ...) can store document data in the generated sub-block.

When creating a block in a blockchain system, it must always go through a verification procedure from all nodes. Therefore, if the procedure in a specific node is delayed, the procedure of the entire blockchain system is delayed. In other words, if a specific node tries to store too much data in a block, there is a risk of causing a delay in the entire blockchain system.

Accordingly, in the present invention, it is proposed to divide the document data to be stored into a plurality of piece data, and to divide and store the plurality of piece data into a plurality of sub-blocks.

For example, the document data to be stored is divided into first to third piece data, and the piece data is divided into first to third sub-blocks in the first to third sub-nodes 121-1 to 121-3, respectively. To save.

If it is divided and stored in this way, the case that the entire sub-blockchain 120 is delayed due to a delay by any one sub-node will be reduced.

On the other hand, due to the technical idea (concept) of the blockchain, it is forbidden to transfer (export) any kind of data received through a node back to another device. In other words, on a commonly used blockchain system, an act of transmitting data other than a response to a pre-set query on the system is not allowed.

Therefore, in the following embodiment, an embodiment that can conform to the above block chain idea will be described.

6 is a flowchart of a document management system according to a second embodiment of the present invention. In FIGS. 6 to 8, a case of issuing a document is also described as an example, but it will be apparent that the second embodiment is applicable to various transactions related to document data, but is not limited thereto.

In step S601, the requester 390 makes a document issuing request to the document issuing server 392. For example, a university student asks the student registration system to issue his or her transcript.

The document issuing server 392 may return the issued document to the requester 390 after performing the process required for issuing the document (step S602) (step S603). In response to the issued document, the file itself of the issued document can be returned, and after the URL link to download the file is delivered, the requester 390 is delivered so that the file can be downloaded through the URL link. It might be possible. The method of returning the issued document to the requester 390 does not limit the content of the present invention, and the issued document may be delivered in various ways.

After that, the document issuing server 392 delivers the issued document to the storage unit 190 (step S604). At this time, information for performing a transaction in the main blockchain 110 may also be delivered in step S604.

The storage unit 190 stores the received document (S605) and transfers the received transaction information to the main blockchain 110 (or one of a plurality of main nodes) (step S606). At this time, it will be the same as described above that it may be stored in the storage unit 190 in a form matching the key value.

In step S607, the main blockchain 110 performs a transaction related to issuing a document based on the received information (step S607). That is, a main block containing information related to document issuance (issuance requester information, issuance date and time information, issuer information, etc.) can be created.

Since the transaction related to the issuance of the document was performed in step S607, it will not be possible to forge or alter the issuance of the document. In other words, when checking the authenticity of an issued document, it is possible to check the information stored in the main block to confirm that the document was actually issued properly. On the other hand, the document data itself is not stored in the corresponding main block (instead of stored in the storage unit 190).

Instead of storing the document data itself, the second embodiment of the present invention also proposes to include a key value for identifying (indicating) the document data in the main block. When the document data is stored in the storage unit 190, it is stored in a form matching the key value, and this is for viewing the document data later. To this end, in step S606 described above, the storage unit 190 may transmit the corresponding key value together with the transaction information. That is, the key value corresponding to the transaction information may be transmitted in a state that is included.

7 is a diagram illustrating a procedure for confirming an issued document according to an embodiment of the present invention.

The document confirmation requester 490 makes a document issuance confirmation request (step S701) to the document confirmation server 492 whether the document issuance is correct. For example, the request for confirmation of issuance of a document may be a verification of the authenticity of the document itself (forgery verification), or may include a verification of the authenticity of the issuance of the document (regarding the issuer or date of issuance). The document confirmation server 492 may have the same configuration as the document issuing server 392 of FIG. 3 or may be configured separately.

Subsequently, the document confirmation server 492 transmits the document issuance confirmation request to the main blockchain 110 (or one of a plurality of main nodes) (step S702). The main block chain 110 inquires the main block corresponding to the request (step S703). That is, it will be possible to search the main block containing the transaction and check the information (document issuance information) stored in the main block. In particular, it is possible to inquire the key value for confirming the document itself along with the document issuance information.

The main blockchain 110 may return the inquired document issuance information and the key value 450 to the document verification server 492 (step S704). Further, a document access request (step S705) may be made based on the key value 450 returned to the storage unit 190. That is, the key value 450 returned from the main blockchain 110 may be included in the document view request.

The storage unit 190 searches for stored document data based on the key value 450 included in the view request (step S706). That is, the document data 451 stored in correspondence with the key value 450 is checked (452). In addition, the storage unit 190 may return the retrieved document data 451 to the document verification server 492 (step S707).

The document verification server 492 may transmit the document data 451 returned in step S707 together with the document issuance information returned in step S704 to the document verification requester 490. Accordingly, the document verification requester 490 can check/read not only the information on the issuance of the document, but also the document data of the issued document, and the verified information is information stored in the blockchain and can doubt its reliability. There won't be. In this way, when checking the document issuance information and the issued document data, it will be possible to clearly check whether the issued document itself has been forged or altered, as well as whether or not the document has been issued.

Likewise in the second embodiment of the present invention, for the protection of personal information, a method of deleting the key value 450 when the issued document is destroyed is proposed. Likewise in the second embodiment of the present invention, the document data 451 itself is not destroyed through such a method, but the document data 451 cannot be viewed or viewed substantially, thereby providing a substantial destruction effect.

A procedure for destroying the issued document will be described below with reference to FIG. 8.

8 is a flowchart showing a procedure for destroying an issued document according to the second embodiment of the present invention.

In step S801, the destruction requester 590 makes a request for destruction to the document destruction server 592. In addition, the document destruction server 592 transmits the request to the main blockchain 110. At this time, the document destruction server 592 may have the same configuration as the document verification server 492 or the document issuing server 392 or may be a separate configuration.

The main blockchain 110 inquires the key value for the document corresponding to the destruction request in the main block (step S803). The inquired key value 550 is returned to the destruction server 592 (step S804).

The document destruction server 592 transmits the key value 550 received while requesting destruction to the storage unit 190 (step S805). That is, in the request for destruction, the key value 550 corresponding to the document to be destroyed will be included.

When the request to destroy the document is received, the storage unit searches 552 for the stored key value 550 and deletes at least one of the key value 550 and the document data 551 (step S806).

When at least one of the key value 550 and the document data 551 is deleted, the storage unit 190 returns to the requester 590 that the document destruction is completed through the storage unit 190 and the document destruction server 592 (Step S807) You can do it.

When at least one of the key value 550 and the document data 551 is deleted as described above, the document is virtually destroyed even if the other node participating in the main blockchain 110 does not allow inquiries/views. You will be able to achieve the same effect as you did.

The embodiments of the document management system according to the present invention have been described above, but this is described as at least one embodiment, and the technical idea of the present invention and its configuration and operation are not limited thereto. The scope of the idea is not limited/limited by the drawings or the description referring to the drawings. In addition, the concepts and embodiments of the invention presented in the present invention may be used by those of ordinary skill in the art as a basis for modifying or designing a different structure in order to perform the same object of the present invention. , Modified or changed equivalent structure by a person of ordinary skill in the technical field to which the present invention belongs is bound by the technical scope of the present invention described in the claims, and does not depart from the spirit or scope of the invention described in the claims. Various changes, substitutions and changes are possible within the limit.

Claims (19)

In a system for managing document data based on blockchain technology,
A plurality of main nodes participating in the main blockchain; And
Including a storage unit for storing document data,
When a transaction for predetermined document data is made in a predetermined main node among the plurality of main nodes, the predetermined main node transfers the predetermined document data to the storage unit,
The storage unit, characterized in that to store the received predetermined document data,
A system for managing document data.
The method of claim 1,
The storage unit,
Stores a plurality of document data in a manner that matches the document data with a key value indicating the document data,
Receiving a request to view the document data stored in the storage unit, characterized in that to return the stored document data matched with the key value included in the received view request,
A system for managing document data.
The method of claim 2,
The storage unit, when a request for destruction of any one of the document data stored in the storage unit is received, deletes at least one of a key value and document data stored in matching with the requested document data,
A system for managing document data.
The method of claim 1, wherein the storage unit,
Including a plurality of sub-nodes participating in the sub-blockchain,
The plurality of sub-nodes, characterized in that to form a plurality of sub-blocks,
A system for managing document data.
The method of claim 4,
In the storage unit to store the received predetermined document data,
Splitting the predetermined document data to be stored into a plurality of data,
When forming the plurality of sub-blocks, characterized in that the divided plurality of data is divided and stored in the plurality of sub-blocks,
A system for managing document data.
The method of claim 1,
The transaction for the predetermined document data,
It is a transaction for sending and receiving emails,
The predetermined document data is characterized in that the attachment of the transmitted and received e-mail,
A system for managing document data.
The method of claim 1,
The transaction for the predetermined document data,
It is a transaction for at least one of issuance, distribution, and destruction of an electronic certificate file,
Wherein the predetermined document data is the electronic certificate file,
A system for managing document data.
In the control method of a system including a storage unit for storing document data and a plurality of main nodes participating in the main blockchain to manage document files based on blockchain technology,
Transmitting, by the predetermined main node, the predetermined document data to the storage unit when a transaction for predetermined document data is made in a predetermined main node among the plurality of main nodes; And
And storing the received predetermined document data by the storage unit,
A control method of a system for managing document data.
The method of claim 8,
The storing step,
Stores a plurality of document data in a manner that matches the document data with a key value indicating the document data,
Receiving a view request for the document data stored in the storage unit, further comprising the step of returning the stored document data matched with the key value included in the received view request,
A control method of a system for managing document data.
The method of claim 9,
When a request for destruction of any one of the document data stored in the storage unit is received, the storage unit deletes at least one of the key value and document data stored by matching the document data requested for destruction. Made by,
A control method of a system for managing document data.
The method of claim 8,
The storage unit includes a plurality of sub-nodes participating in the sub-blockchain,
The storing step is characterized in that the plurality of sub-nodes form a plurality of sub-blocks,
A control method of a system for managing document data.
The method of claim 11,
In the step of storing the received predetermined document data by the storage unit,
Dividing the predetermined document data to be stored into a plurality of data; And
When forming the plurality of sub-blocks, it characterized in that it comprises the step of storing the divided plurality of data divided into the plurality of sub-blocks,
A control method of a system for managing document data.
The method of claim 8,
The transaction for the predetermined document data,
It is a transaction for sending and receiving emails,
The predetermined document data is characterized in that the attachment of the transmitted and received e-mail,
A control method of a system for managing document data.
The method of claim 8,
The transaction for the predetermined document data,
It is a transaction for at least one of issuance, distribution, and destruction of an electronic certificate file,
Wherein the predetermined document data is the electronic certificate file,
A control method of a system for managing document data.
In a system for managing document data based on blockchain technology,
A plurality of main nodes participating in the main blockchain; And
Including a storage unit for storing document data,
When the storage unit receives information on a transaction for predetermined document data to be performed on the main blockchain, it stores the predetermined document data and transmits the information on the transaction to the main blockchain,
A predetermined main node among the plurality of main nodes is characterized in that to perform a transaction based on the information on the received transaction,
A system for managing document data.
The method of claim 15,
The storage unit,
Stores a plurality of document data in a manner that matches the document data with a key value indicating the document data,
Receiving a request to view the document data stored in the storage unit, characterized in that to return the stored document data matched with the key value included in the received view request,
A system for managing document data.
The method of claim 16,
The storage unit, when a request for destruction of any one of the document data stored in the storage unit is received, deletes a key value matched with the requested document data and stored,
A system for managing document data.
The method of claim 15, wherein the storage unit,
Including a plurality of sub-nodes participating in the sub-blockchain,
The plurality of sub-nodes, characterized in that to form a plurality of sub-blocks,
A system for managing document data.
The method of claim 18,
In the storage unit to store the received predetermined document data,
Splitting the predetermined document data to be stored into a plurality of data,
When forming the plurality of sub-blocks, characterized in that the divided plurality of data is divided and stored in the plurality of sub-blocks,
A system for managing document data.

Images