KR20200041148A - Certificate issuance system based on blockchain technology and control method thereof - Google Patents

Abstract

The present invention relates to a blockchain technology-based document issuance system and, more particularly, to a system for issuing an electronic document. The electronic document issuance system includes: a main blockchain including a plurality of main nodes; a sub blockchain including a plurality of sub nodes; a certificate request server requesting certificate issuance; and a certificate issuance server generating a certificate in response to the issuance request from the certificate request server. The certificate issuance server transmits a first transaction on the generation of the certificate to a first main node. The main blockchain transmits the first transaction received by the first main node to the sub blockchain. The certificate request server transmits a validation query of the first transaction to a first sub node.

Description

Electronic document issuing system and its control method using blockchain technology {CERTIFICATE ISSUANCE SYSTEM BASED ON BLOCKCHAIN TECHNOLOGY AND CONTROL METHOD THEREOF}

The present invention relates to an authentication system, and more particularly, to an authentication system capable of improving reliability by recording and viewing operations related to user authentication or document authentication as a transaction in a blockchain.

Blockchain technology is a data distribution processing technology in which all users participating in the network are distributed and stored. It is also called 'distributed ledger technology' (DLT) or 'public ledger' in that it is a technology shared by all network participants rather than being held by a trading entity or a specific institution. . Blockchain is a name given as a block that contains the contents of a transaction, which is a chain.

These blockchains can be divided into public blockchains and private blockchains. The public blockchain corresponds to the public ledger described above, and generally refers to the public blockchain. Private blockchain is a relative concept and is mainly used by companies, so it is also called an enterprise blockchain. The consortium blockchain, in which several companies (or institutions) are jointly participating, also falls into the category of private blockchain in a broad sense.

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

Public blockchains can be joined by anyone, and are highly reliable through mutual verification of all participants, but have the disadvantage of slow processing due to sharing and sharing transaction records of all participants. Compared to this, the private blockchain participates only in the approved nodes and does not need to seek verification of other nodes, so the processing speed is much faster. However, since the users of the private blockchain must rely entirely on the service provider, there is a limit to the reliability compared to the public blockchain.

Such a blockchain can be used in various industries, and it will be most suitable for the field where reliability for forgery and alteration must be secured. Proofing tasks, such as authentication for users or proof of documents, is a task that is constantly exposed to the risk of forgery or tampering, and securing reliability will be more urgent than those in other industries. Nevertheless, research on such a verification system has not been properly conducted using blockchain technology.

The present invention aims to solve the above and other problems. Another object is to provide an authentication system that can improve the user's credibility for authentication or verification of documents.

Another purpose is to provide a proof system that can perform proof of the entire process from issuance, distribution, and destruction of documents that are the subject of proof, and that anyone can verify the process.

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 skilled in the art from the following description. Will be able to.

According to an aspect of the present invention to achieve the above or other object, a system for performing proof of an electronic document, comprising: a main blockchain composed of a plurality of main nodes; A sub-blockchain consisting of a plurality of sub-nodes; A certificate request server requesting the issuance of a certificate; And a certificate issuing server that generates a certificate in response to an issuance request from the certificate request server, wherein the certificate issuing server transmits a first transaction regarding the generation of the certificate to a first main node, The main blockchain delivers the first transaction received by the first main node to the sub blockchain, and the certificate request server delivers a verification query of the first transaction to the first sub node. It provides an electronic document proof system, characterized in that.

When explaining the effect of the authentication system according to the present invention as follows.

According to at least one of the embodiments of the present invention, there is an advantage of improving the reliability of user authentication based on the blockchain technology.

In addition, according to at least one of the embodiments of the present invention, in recording an authentication procedure from an authentication requesting authority as a block chain transaction, even if the number of authentication requesting institutions is large, it has an advantage that it can be effectively recorded without a bottleneck and without problems. have.

Further scope of applicability of the present invention will become apparent from the following detailed description. However, various changes and modifications within the spirit and scope of the present invention may be clearly understood by those skilled in the art, and thus, it should be understood that specific embodiments such as detailed description and preferred embodiments of the present invention are given as examples only.

1 is a view showing the structure of a blockchain according to an embodiment of the present invention.
2 is a view for explaining an extended relationship between a main blockchain and a sub-blockchain according to an embodiment of the present invention.
FIG. 3 is a diagram illustrating a procedure for proving documents according to an embodiment of the present invention.
4 is a diagram illustrating a process of requesting a certificate between certification bodies according to an embodiment of the present invention.
5 is a diagram illustrating a user authentication procedure according to an embodiment of the present invention.

Hereinafter, exemplary embodiments disclosed herein will be described in detail with reference to the accompanying drawings, but the same or similar elements are assigned the same reference numbers regardless of the reference numerals, and overlapping descriptions thereof will be omitted. The suffixes "modules" and "parts" for the components used in the following description are given or mixed only considering the ease of writing the specification, and do not have meanings or roles distinguished from each other in themselves. In addition, in describing the embodiments disclosed in the present specification, when it is determined that detailed descriptions of related known technologies may obscure the gist of the embodiments disclosed herein, detailed descriptions thereof will be omitted. In addition, the accompanying drawings are only for easy understanding of the embodiments disclosed in the present specification, and the technical spirit disclosed in the specification is not limited by the accompanying drawings, and all modifications included in the spirit and technical 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 components, but the components are not limited by the terms. The terms are used only for the purpose of distinguishing one component from other components.

When an element is said to be "connected" or "connected" to another component, it is understood that other components may be directly connected to 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 said to be "directly connected" or "directly connected" to another component, it should be understood that no other component exists in the middle.

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

In this application, the terms "comprises" or "have" are intended to indicate the presence of features, numbers, steps, actions, components, parts or combinations thereof described herein, one or more other features. It should be understood that the existence or addition possibilities of fields or numbers, steps, operations, components, parts or combinations thereof are not excluded in advance.

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

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

In the existing financial system, financial companies have kept transaction records on a central server, whereas in a block chain based on P2P, transaction information is stored in blocks and connected in turn, and all participants share it.

In the financial system, the processing of blockchain technology for the transaction process (transaction, transaction) is performed as follows. ① A asks B for a transaction, such as a transfer request. ② 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. ④ By verifying the transaction details that match the majority of participants' data with normal books, the verified block is connected to the previous block, and a copy is made and distributed to each user's computer. ⑤ A sends money to B and the transaction is completed. At this time, all transactions generated within a predetermined period (for example, about 10 minutes) can be generated as one block.

Through this process, it is possible to secure the reliability when creating a block by checking whether it matches the majority data of the participants, as well as to store the copies of the completed blocks individually on each computer (node) to counterfeit forgery. Practically impossible.

The proof system in the present invention, instead of proof of a transaction utilized in the financial system as described above, various actions related to user authentication and / or proof of electronic documents (hereinafter, all actions recorded in the blockchain are referred to as transactions). ).

Hereinafter, the terms related to the blockchain will be described.

· Block

A block is a unit for storing data, and is divided into a body and a header. The body contains the contents of the transaction, and the header contains cryptographic codes such as Merkle hash (Mercult) or nonce (any number related to encryption). Blocks are created every 10 minutes, and by collecting transaction records, they create blocks to verify reliability, and connect to previous blocks to form a blockchain. The block that started here is called the Genesis block. In other words, the Genesis block is 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 and maintain and manage the network. This individual server, or participant, is called a node. Since there is no central administrator, the role of the node that distributes the block is important, and more than half of the participating nodes must have consent to create a new block. Nodes store the blockchain on a computer, and even if some nodes are hacked and the existing contents are wrong, data remains in multiple nodes, so that the data can be continuously preserved.

· Hash function

It is a function that results in the same length no matter what data is entered. It is unlikely that the resulting results will overlap, and it is difficult to reversely 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. The hash function SHA-2 (SHA 256) has been developed since SHA (Secure Hash Algorithm) -1 was first devised, which is used in blockchain. SHA-2 results in 256 bits no matter what length value is entered.

1 is a view showing the structure of a blockchain according to an embodiment of the present invention. 2 is a view for explaining an extended relationship between a main blockchain and a sub-blockchain according to an embodiment of the present invention.

The proof system according to an embodiment of the present invention includes at least two main nodes 111-1 to 111-3, and a main blockchain 110 and at least two sub nodes 121-1 to 121-4. It may include a sub-blockchain 120 participating.

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

However, the main blockchain 110 and the sub-blockchain 120 may be selectively connected, and optionally, a verification procedure may be required when connecting.

For example, as will be described in detail below, when a certificate generation transaction occurs in the main blockchain 110, information about the transaction may be shared in the sub-blockchain. Based on the shared certificate generation transaction, the sub-blockchain 120 may perform a verification query for the transaction.

As such, the relationship between the blocks is not 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 a main connecting node 111-3, and 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 main and sub connection nodes 111-3 and 121-1 are provided to connect the main and sub blockchains to each other.

At this time, 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 specific conditions. This is because the main blockchain is a private blockchain, and information stored in the main blockchain should not be disclosed to the outside.

For example, only a predetermined query (Query) may be received from the sub-blockchain 120, or only data transmission / reception when replying to the preset query may be performed through the connection node. The preset query and reply to it will be described later in detail.

According to an embodiment of the present invention, the main blockchain 110 may be a private blockchain. That is, the main nodes 111-1 to 111-3, which are nodes of the main blockchain 110, are not disclosed to anyone, and only authorized or designated institutions can participate.

On the other hand, the sub-blockchain 120 may be a private blockchain or a public blockchain. It may not be completely blocked, but it may be a private blockchain with a broad meaning that only verified or authenticated subjects (some pre-set subjects) can participate in a limited amount. Accordingly, additional sub-nodes 122-1, 122-2, ... may participate in the sub-nodes 121-1 to 121-4, which are nodes of the sub-blockchain 120.

As such, the reason why the main blockchain 110 and the sub-blockchain 120 are separated is that security for the authentication system is required. According to the blockchain technology, all transactions are disclosed to the public, because user authentication or the proof content of the document itself should not be disclosed to the public. For example, the proof of graduation document should only be disclosed to the requesting institution (for example, a company that wishes to receive a certificate of the applicant) requested by the requester (for example, an applicant for the company), and for companies other than the receiving institution, This is because it should not be disclosed to third parties such as financial institutions or others.

Another reason for the separation of the main blockchain 110 and the sub-blockchain 120 is to secure scalability of the receiving institution. In the case of the main blockchain 110, since the content is a private blockchain that should not be disclosed, it must be limited in terms of its scalability.

If a company that wants to participate as a node of the blockchain additionally occurs, the system according to an embodiment of the present invention is provided to participate in a node of the sub-blockchain.

A plurality of organizations (hereinafter referred to as a receiving organization) requesting user authentication or requesting proof of documents may correspond to the sub-nodes 121-1 to 121-4. That is, the receiving institution may be matched and connected to one sub-node, and one receiving institution may be connected to one sub-node.

On the other hand, the main blockchain 110 may have a certification authority connected to at least one of the plurality of main nodes 111-1 to 111-3. That is, one integrated proofing authority can use multiple nodes.

Furthermore, the sub-blockchain 120 can expand the number of blockchain itself. 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). Each may be connected.

Hereinafter, a specific method for performing document authentication and user authentication based on this structure of the present invention will be described.

FIG. 3 is a diagram illustrating a procedure for proving documents according to an embodiment of the present invention.

The certificate request server 391 may refer to a server managed by a receiving institution (or individual) who wants to check the authenticity of a document related to the requester 390, for example, the certificate request server 391 It is a server operated by a company, and the requestor 390 may be an applicant who supports applying for employment in the company, and a certificate of graduation to verify the academic information of the requester 390 through the certificate request server 391 at the company. We can assume a situation where we want to check the authenticity of

The certification agency 393 means a subject who performs the corresponding certification, and in the above example, the requestor 390 may be a university undergraduate or academic verification system that is graduated. It will be apparent that the term proof agency 393 used in the present invention is only a term used to easily understand the concept, and can be interpreted as a device, system, or server operated by the proof agency 393.

The certificate issuing server 392 is an organization for collectively managing the procedures related to the certification of a plurality of certification bodies 393, and refers to a subject that issues items proved by the certification authority 393 as an encrypted document. . For example, if each of the numerous universities is a certification institution 393, the certificate issuing server 392 may serve to integrate the contents verified / certified by a number of universities and encrypt it and issue it as a certificate.

However, the present invention is not limited to the certificate issuance server 392 directly generating a certificate, and a case in which a certificate is issued by a plurality of certification agencies 393 and the collection and management of the issued certificates are included in the present invention is also included in the present invention. will be.

In addition, the certificate issuing server 392 may be provided separately from the certification authority 393, but may be provided as a single institution without being separated from the certification authority 393.

The term "server" used in the specific content for carrying out the present invention is a term including all devices capable of transmitting and receiving data on and off-line, and the content of the present invention is not limited to the term itself.

In addition, in the specific content for carrying out the present invention, the term certificate is a term encompassing all electronic documents that can be issued, distributed, and stored electronically.

According to the existing proof system, the requestor 390 directly requests the proof of graduation document from the certification authority 393 or the certificate issuing server 392 to output the proof of graduation document to the printer and print the proof of graduation document output to the receiving institution. It was confirmed by submission method.

According to the existing verification system, there was always a risk of forgery and alteration in the process of requesting documents and submitting them to the receiving institution.

However, in one embodiment of the present invention, based on the request of the requester 390, an institution that wants to verify a certificate using a blockchain technology (for example, a company that wants to check the requester's academic information, etc.) We propose a method for carrying out and forwarding a request for issuing a direct certificate.

In step S301, the requestor 390 requests the certificate request server 391 to generate a document (certificate) to be proved by itself. In step S302, the certificate request server 391 transmits the request to the certificate issuing server 392. In step S303, the certificate issuing server 392 designates the name of the certificate file to be generated, and returns the specified file name to the certificate request server 391.

In step S304, the certificate issuing server 392 transmits a request for generating a certificate to the certification authority 393. The certification body 393 may generate a certificate based on the received request. Subsequently, the certificate issuing server 392 transfers the transaction for generating the certificate to the node of the main blockchain 110 (S305). The transaction delivered in this way may be stored in the main block as described above, and may also be selectively delivered to the sub-blockchain 120 and stored in the sub-block.

Furthermore, it is proposed that the transaction according to an embodiment of the present invention is transmitted to a sub-chain and stored as a sub-block. This is because verification is performed in step S307 described later. At this time, the transaction may be transmitted through the connection between the main connection node 111-3 and the sub connection node 121-1. That is, the transaction for generating the certificate may be recorded in a sub-block of the sub-blockchain sequentially through the main connection node 111-3 and the sub-connection node 121-1.

In step S306, the certificate request server 391 continuously checks the generated contract to the certificate issuing server 392. That is, based on the file name returned in step S303, it is continuously checked whether a certificate having the file name is generated. If the certificate generation is confirmed, a verification query is transmitted to the sub-blockchain 120 to determine whether the certificate is generated (S307). That is, it is to check whether the certificate is generated correctly.

At this time, the checking process (S307) may be performed based on the content stored in the sub-block. That is, a transaction for generating a certificate is stored in a sub-block, and verification is performed by checking the transaction recorded in the sub-block.

The confirmation result, which is a response to the query, may be returned to the certificate request server 391 again.

Then, the generated certificate is transmitted to the certification authority 393, the certificate issuing server 392, and the certificate request server 391 through steps S308 and S309, and the certificate request server 391 can receive (download) the certificate. When the receipt of the certificate is completed, the certificate request server 391 transmits a transaction for receipt completion to the sub-node 121-4 in step S310. The transmitted transaction will be stored in a sub-block of the sub-blockchain 120.

Subsequently, in step S311, the requester 390 receives (downloads) the certificate from the certificate request server 391. The certificate request server 391 can transfer the transaction for the issuance of the certificate (that is, delivery to the requester) to the sub-node 121-4 of the sub-blockchain 120 (step S312) and store it in the sub-block. There will be. In addition, not only the completion of the delivery of the certificate, but also all operations such as copying, destruction or transfer of the certificate may be performed as a transaction and delivered to the sub-node 121-4.

According to the procedure in FIG. 3, the certificate request server 391 that receives the certificate can verify with high reliability whether the received certificate is correctly generated, and the requestor 390 receives the generated certificate by the receiving institution It has the advantage of being able to check with high confidence whether it has been delivered, whether it has been delivered to a third party, or whether it has been destroyed.

4 is a diagram illustrating a process of requesting a certificate between certification bodies according to an embodiment of the present invention.

In some cases, it may be necessary to issue certificates between certification bodies. For example, if a student attending University A is applying for credit transfer to University B, or going to graduate school at University B, a certificate may be required from University B to see whether he or she is attending University A. Since the certification agencies collectively manage the contents of the certificate issuance through the above-described certificate issuing server 392, the procedure may be slightly different from the procedure of FIG.

FIG. 4 shows a process in which the first certification authority 393-1 requests a certificate from the second certification authority 393-2 based on the requester's request. That is, in the above example, if a student who wishes to apply for credit exchange makes a request to University B as the requestor, University B may become the first certification institution (393-1), and University A where the requester is currently enrolled Can be the second certification body (393-2).

In step S401, the first certification authority 393-1 transmits a request to generate a certificate to the certificate issuing server 392. Subsequently, the certificate issuing server 392 designates the name of the certificate file to be generated, and returns the designated file name to the first certification authority 393-1. In step S403, the certificate issuing server 392 transmits a certificate generation request to the second certificate authority 393-2, and the second certificate authority 393-2 generates the requested certificate.

When a certificate is generated, the certificate issuing server 392 can deliver the transaction for generating the certificate to the main node of the main blockchain 110.

In step S405, the first certification authority 393-1 continuously checks the generated contract to the certificate issuing server 392. On the basis of the file name returned in step S402, it is continuously checked whether a certificate having the file name has been generated.

In step S406, the second certification authority 393-2 transmits the generated certificate to the certificate issuing server 392. Upon receiving the certificate, the certificate issuing server 392 generates a transaction for receiving the certificate, and transmits it to the main node of the main blockchain 110 (step S407).

Subsequently, the certificate issuing server 392 delivers the received certificate to the first certification authority (step S408). Then, when the certificate delivery is completed, a transaction for certificate delivery is generated and delivered to the main node of the main blockchain 110 (step S409).

Hereinafter, a process of performing user authentication using a blockchain technology will be described.

5 is a diagram illustrating a user authentication procedure according to an embodiment of the present invention.

The authentication request server 591 may refer to a server that wants to perform authentication for the requestor 390, and for example, may mean a server of a homepage to which the requestor 390 wants to subscribe.

The certification authority 393 'means a subject that performs authentication on the requestor 390, and for example, the certification request server 591 is enrolled in the requestor 390 (college attendance, graduation, etc.) ) It may be possible to request a certification authority 393 '. In this case, the certification authority 393 ′ may be a university undergraduate or academic verification system from which the requestor 390 graduated. The certification authority 393 'may be an organization belonging to the certification authority 393 described above with reference to FIGS. 3 and 4, or may be a separate organization from the certification authority 393.

The integrated authentication server 592 means a subject for collectively managing a user authentication related procedure of a plurality of certification authorities 393 '. For example, if each of the numerous universities is a certification authority 393 ', the integrated authentication server 592 may serve to consolidate the authentications performed by the numerous universities and to encrypt and issue them as user identification information.

In step S501, the requester 390 may request the authentication request server 591 to generate user identification information, and in step S502, the authentication request server 591 may forward the request to the integrated authentication server 592. have.

The integrated authentication server 592 may transfer the transaction for the above request to the main blockchain 110 (step S503).

The integrated authentication server 592 receiving the request for generating user identification information passes the request back to the certification authority 393 ', and the certification authority 393' performs user authentication (step S504) based on the received request content. can do. In the user authentication step of S504, the certification authority 393 'may search the database for the requestor 390 and perform an authentication operation. For example, the requestor 390 is a university student, and the certification authority 393 'is a corresponding university academic system, performs academic authentication on the requester 390 through a query of the academic database and integrates the results of the execution with the integrated authentication server (592).

The integrated authentication server 592 may generate user identification information for the user whose authentication has been completed, and transfer a transaction for the generation of the user identification information to the main node of the main blockchain (step S505). Here, the user identification information may mean a unique code assigned to the requestor 390, and may indicate a user ID (Identication information) or a token value. At this time, the subject generating the user identification information may be the integrated authentication server 592, but the authentication authority 393 'may generate the user identification information and deliver it to the integrated authentication server 592.

On the other hand, the system according to an embodiment of the present invention, the transaction for the request as in step S503, the first main node (111-1), and the transaction for generating identification information is the second main node (111- It is suggested to block by passing it to 2). The transaction for generating identification information may be an authentication response to the S503 request.

In a blockchain system, at least three nodes are basically required. This is because verification of the newly created block is performed at all nodes together, and a new block can be generated only after a majority of verification results, and it is impossible to form a majority result with two nodes. Therefore, the main blockchain 110 shown in FIG. 5 also requires at least three nodes.

Since the integrated authentication server 592 performs a role of integrating authentication procedures for a large number of certification authorities 393 ', there is a concern that a bottleneck may occur. Accordingly, in the present invention, the types of transactions that may occur in the integrated authentication server 592 are classified, so that one type of transaction is in the first main node 111-1 and the other type of transaction is in the second main node ( 111-2). In other words, due to the nature of the blockchain where at least three nodes must be formed, it is intended to share the role among nodes in order to alleviate the bottleneck.

The integrated authentication server 592 may transmit the user identification information generated in step S506 to the authentication request server 591. The authentication request server 591 may transmit a transaction for receiving user identification information to a sub-node of the sub-blockchain (step S507).

Then, in step S508, the user identification number may be delivered to the requestor 390, or a notification (instruction) may be made about the fact that the user identification number has been issued.

As described above, although an embodiment of the authentication system and its control method according to the present invention has been described, it is described as at least one embodiment, whereby the technical spirit of the present invention and its configuration and operation are not limited. The scope of the technical spirit of the present invention is not limited / restricted 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 a person having ordinary knowledge in the technical field to which the present invention pertains as a basis for modifying or designing with other structures in order to perform the same purpose of the present invention. , The equivalent structure modified or changed by a person having ordinary knowledge in the technical field to which the present invention pertains is bound by the technical scope of the present invention described in the claims, and the scope or scope of the invention described in the claims Various changes, substitutions, and changes are possible without departing.

Claims (14)

In the system for issuing the electronic document,
A main blockchain consisting of a plurality of main nodes;
A sub-blockchain consisting of a plurality of sub-nodes;
A certificate request server requesting the issuance of a certificate; And
It includes a certificate issuing server for generating a certificate in response to the issuance request from the certificate request server,
The certificate issuing server transmits a first transaction related to the generation of the certificate to a first main node,
The main blockchain delivers the first transaction received by the first main node to the sub blockchain,
The certificate request server, characterized in that for passing the verification query (Query) of the first transaction to the first sub-node,
Electronic document issuance system. According to claim 1,
When the main blockchain delivers the first transaction,
Characterized in that the transmission through the connection of the second main node and the second sub-node,
Electronic document issuance system. According to claim 1,
The sub-blockchain is characterized by forming a sub-block based on the received first transaction,
Electronic document issuance system. The method of claim 3,
The main blockchain is characterized by forming a main block based on the received first transaction,
Electronic document issuance system. The method of claim 3,
The first sub-node performs verification for the first transaction based on the first transaction stored in the sub-block,
Responding to the certificate request server to perform the verification result (reponse),
Electronic document issuance system. According to claim 1,
Upon receiving the generated certificate, the certificate request server sends a second transaction for receiving the certificate to the first sub-node,
The sub-blockchain forms a sub-block based on the second transaction received by the first sub-node,
Electronic document issuance system. The method of claim 6,
The certificate request server, characterized in that for delivering the operation of the received certificate, such as destruction, the third transaction to the first sub-node,
Electronic document issuance system.
A main blockchain composed of a plurality of main nodes, a sub blockchain composed of a plurality of sub nodes, a certificate request server requesting the issuance of a certificate, and a certificate issuing server generating a certificate in response to an issue request from the certificate request server In the control method of the system for performing the issuance of an electronic document comprising:
Sending, by the certificate issuing server, a first transaction related to the generation of the certificate to a first main node;
Transmitting, by the main blockchain, the first transaction received by the first main node to the sub-blockchain; And
The certificate request server, characterized in that it comprises the step of passing a verification query (Query) of the first transaction to a first sub-node,
Control method of electronic document issuance system. The method of claim 8,
When the main blockchain delivers the first transaction,
Characterized in that the transmission through the connection of the second main node and the second sub-node,
Control method of electronic document issuance system. The method of claim 8,
The sub-blockchain, characterized in that it further comprises the step of forming a sub-block based on the received first transaction,
Control method of electronic document issuance system. The method of claim 8,
The main block chain, characterized in that it further comprises the step of forming a main block based on the received first transaction,
Control method of electronic document issuance system. The method of claim 10,
Performing, by the first sub-node, verification for the first transaction based on the first transaction stored in the sub-block; And
The first sub-node, characterized in that it further comprises the step of responding (response) to the certificate request server to perform the verification result,
Control method of electronic document issuance system. The method of claim 8,
When the certificate request server receives the generated certificate, transmitting a second transaction for receiving the certificate to the first sub-node; And
The sub-blockchain further comprising forming a sub-block based on the second transaction received by the first sub-node,
Control method of electronic document issuance system. The method of claim 13,
The certificate request server, characterized in that it further comprises the step of transmitting an operation related to the issuance, destruction, etc. of the received certificate to the first sub-node in a third transaction,
Control method of electronic document issuance system.

Images