KR102081782B1 - Method for providing personal history - Google Patents

Abstract

According to one embodiment of the present invention, a personal history information providing method includes the following steps: receiving a history information registration request from a user node through a hub node; creating a first history information block corresponding to the history information registration request through a hub database (DB) corresponding to the hub node; transmitting a history information confirmation request corresponding to the history information registration request to a participation node through the hub node; creating a second history information block connected to the first history information block in response to history confirmation information transmitted from the participation node through a participation DB corresponding to the participation node; receiving the history confirmation information corresponding to the history information confirmation request from the participation node through the hub node; and transmitting a history information registration response in accordance with the history confirmation information to the user node through the hub node. The hub DB and the participation DB correspond to a blockchain DB, and store a blockchain including the first and second history information blocks in a distributed state.

Description

How to provide personal history information {Method for providing personal history}

Embodiments of the present invention relate to a method of providing personal history information.

Currently, the developer must submit a number of supporting documents to prove his or her history. The submission of multiple proof documents can lead to waste of time and money in issuance and submission.

In addition, if a developer falsifies histories or falsification documents, it may take time and money to find or prove them.

In order to prevent such waste of time and money, and forgery or tampering, a block chain characterized by reliability and integrity may be applied to providing personal history information.

Blockchain is a chain of blocks in which information is recorded like a chain, and refers to a data distribution processing technology in which all subjects participating in the network distribute and store the blockchain managed.

(Patent Document 1) KR10-1906144 B1

The present invention is to provide a method for providing economic and reliable personal history information based on the blockchain.

The method for providing personal history information according to an embodiment of the present invention comprises the steps of receiving a history information registration request from a user node by a hub node, and corresponding to the history information registration request by a hub DB (database) corresponding to the hub node. Generating a first history information block, transmitting, by the hub node, a history information confirmation request corresponding to the history information registration request to a participating node, from the participating node by a participating DB corresponding to the participating node; Generating a second history information block connected to the first history information block in response to the transmitted history confirmation information, receiving the history confirmation information corresponding to the history information confirmation request from the participating node by the hub node; And a history according to the history confirmation information to the user node by the hub node. And transmitting the information registration response, wherein the hub DB and the participating DB correspond to a blockchain DB and distribute and store a blockchain including the first and second history information blocks.

In the present embodiment, the history information registration request may include user identification information and history information, and the history confirmation information may indicate a result of checking the authenticity of the history according to the history information of the user according to the user identification information.

In the present embodiment, at least one of the user identification information, the history information, and time information at which the hub DB receives the history information registration request is recorded in the first history information block, and in the second history information block. At least one of the user identification information, the history confirmation information, and time information when the participation DB receives the history confirmation information may be recorded.

In the present embodiment, receiving a history information request including the user identification information from the operator node by the hub node, retrieving the first and second history information blocks corresponding to the history information request by the hub DB And transmitting, by the hub node, a history information response including history information and history confirmation information extracted from the first and second history information blocks to the operator node.

In the present embodiment, the history information registration response may be a history information registration complete response if the authenticity of the history of the user is recognized, and a history information registration incomplete response if the authenticity of the history of the user is not recognized.

In the present embodiment, the history information includes at least one of education information, qualification information, and career information, wherein the participating node includes at least one of an educational institution node, a certificate issuing authority node, a industrial complex node, an enterprise node, The history confirmation information is education result confirmation information that is the result of the authenticity of the education according to the education information of the user by the educational institution node, the authenticity of the qualification according to the qualification information of the user by the certificate issuing agency node Qualification confirmation information that is a confirmed result, subscription history confirmation information that is the result of confirming the subscription history according to the career information of the user by the corporation node, the authenticity of the work experience according to the career information of the user by the enterprise node It may be at least one of the career confirmation information that is the confirmed result.

In this embodiment, the history confirmation information may be history confirmation information indicating a majority of the plurality of history confirmation information transmitted from a plurality of participating nodes.

The method for providing personal history information according to an embodiment of the present invention includes receiving a history information registration request from a hub node by a charging node, and generating first charging information corresponding to the history information registration request by the charging node. Step, generating a first history information block in response to the history information registration request by the block chain DB (database) corresponding to the billing node, corresponding to the history information registration request to the participating node by the billing node Transmitting a history information confirmation request, receiving, by the charging node, the history confirmation information corresponding to the history information confirmation request from the participating node, a second charging corresponding to the history confirmation information by the charging node; Generating information, the first chain corresponding to the history confirmation information by the blockchain DB; Generating a second history information block connected to an information block, and transmitting the history confirmation information to the hub node by the charging node; wherein the blockchain DB includes the hub node and the participating node. A block chain including a DB corresponding to each of the first and second history information blocks is distributed and stored in a DB corresponding to each of the hub node and the participating node.

In the present embodiment, the history information registration request includes user identification information and history information, wherein the history confirmation information indicates a result of checking the authenticity of the history according to the history information of the user according to the user identification information, The first and second charging information may be charging information for the user.

In the present embodiment, the history information includes at least one of education information, qualification information, and career information, wherein the participating node includes at least one of an educational institution node, a certificate issuing authority node, a industrial complex node, an enterprise node, The history confirmation information is education result confirmation information that is the result of the authenticity of the education according to the education information of the user by the educational institution node, the authenticity of the qualification according to the qualification information of the user by the certificate issuing agency node Qualification confirmation information that is a confirmed result, subscription history confirmation information that is the result of confirming the subscription history according to the career information of the user by the corporation node, the authenticity of the work experience according to the career information of the user by the enterprise node It may be at least one of the career confirmation information that is the confirmed result.

According to embodiments of the present invention, the personal history information may be registered in real time by distributing and storing the history information block.

According to embodiments of the present invention, forgery or tampering of personal history information can be prevented by limiting the subject generating the history information block to a hub node and a participating node.

According to embodiments of the present invention, it is possible to provide more reliable personal history information by providing history information and history confirmation information.

1 is a diagram illustrating an environment for providing personal history information based on a blockchain according to an embodiment of the present invention.
2 is a flowchart illustrating a method of registering personal history information according to an embodiment of the present invention.
3 is a flowchart illustrating a method of providing personal history information according to an embodiment of the present invention.
4 is a flowchart illustrating a method of updating a history information block according to an embodiment of the present invention.
5 is a flowchart illustrating a charging method according to history information registration according to an embodiment of the present invention.
6 is a diagram illustrating an environment for providing personal history information based on a blockchain according to an embodiment of the present invention.
7 to 9 are flowcharts for describing a method for providing personal history information according to an embodiment of the present invention, respectively.

As the inventive concept allows for various changes and numerous embodiments, particular embodiments will be illustrated in the drawings and described in detail in the written description. However, this is not intended to limit the present invention to specific embodiments, it should be understood to include all transformations, equivalents, and substitutes included in the spirit and scope of the present invention. In the following description of the present invention, if it is determined that the detailed description of the related known technology may obscure the gist of the present invention, the detailed description thereof will be omitted.

In the following embodiments, terms such as first and second may be used to describe various components, but the components should not be limited by the terms. The terms are only used to distinguish one component from another.

The terminology used herein is for the purpose of describing particular example embodiments only and is not intended to be limiting of the invention. Singular expressions include plural expressions unless the context clearly indicates otherwise. In the following examples, terms such as "comprise" or "have" are intended to indicate that there is a feature, number, step, operation, component, part, or combination thereof described in the specification, and one or more It is to be understood that it does not exclude in advance the possibility of the presence or addition of other features or numbers, steps, operations, components, components or combinations thereof.

Embodiments of the present invention can be represented by functional block configurations and various processing steps. Such functional blocks may be implemented in various numbers of hardware or / and software configurations that perform particular functions. For example, embodiments of the present invention may be implemented directly, such as memory, processing, logic, look-up table, etc., capable of executing various functions by the control of one or more microprocessors or other control devices. Circuit configurations can be employed. Similar to the components of an embodiment of the present invention may be implemented in software programming or software elements, embodiments of the present invention include various algorithms implemented in combinations of data structures, processes, routines or other programming constructs. It may be implemented in a programming or scripting language such as C, C ++, Java, assembler, or the like. Functional aspects may be implemented in algorithms running on one or more processors. In addition, embodiments of the present invention may employ the prior art for electronic configuration, signal processing, and / or data processing. Terms such as mechanism, element, means, configuration can be used broadly and are not limited to mechanical and physical configurations. The term may include the meaning of a series of routines of software in conjunction with a processor or the like.

1 is a diagram illustrating an environment for providing personal history information based on a blockchain according to an embodiment of the present invention.

Referring to FIG. 1, a blockchain-based personal history information providing environment according to an embodiment of the present invention includes a user node 100, a hub node 210, a participating node 220, and a blockchain DB (database, 300). ).

The user node 100 may communicate with the hub node 210. For example, the user node 100 may communicate with the hub node 210 through an application downloaded from the hub node 210.

The hub node 210 may be a subject that provides personal history information based on a blockchain. For example, the hub node 210 transmits a command according to a request received from the user node 100 to the participating node 220 and the blockchain DB 300, thereby participating in the node 200 and the blockchain DB 300. Can control the operation of.

The participating node 220 may be a subject that checks personal history information based on the blockchain. For example, the participating node 220 may check the authenticity of the personal history according to the command received from the hub node 210.

The participating node 220 may be plural. The authenticity of the personal history may be confirmed by each of the plurality of participating nodes 220 or may be confirmed by a majority of the plurality of participating nodes 220, but is not limited thereto.

The blockchain DB 300 may include a hub DB 310 and a participating DB 320. The blockchain DB 300 may update and distribute the blockchain.

For example, if the hub DB 310 generates the first block, the hub DB 310 and the participating DB 320 each store a blockchain including the first block, and the participating DB 320 stores the first block. After generating the second block connected to the hub DB 310 and the participating DB 320 may store the block chain connected to the first block and the second block, respectively. In other words, if the blockchain is updated by at least one of the hub DB 310 and the participating DB 320 corresponding to the blockchain DB 300, the updated blockchain is the hub DB 310 and the participating DB 320. Distributed to

Hereinafter, a method of providing personal history information in an environment of providing personal history information based on the blockchain of FIG. 1 will be described with reference to FIGS. 2 to 4.

2 is a flowchart illustrating a method of registering personal history information according to an embodiment of the present invention.

Referring to FIG. 2, the user node 100 transmits a history information registration request to the hub node 210 (S201). The user node 100 may download an application provided by the hub node 210 and then transmit a history information registration request to the hub node 210 through the application.

The history information registration request may include user identification information and history information.

The user identification information may be information for distinguishing a user from other users, information for distinguishing a user node from other user nodes, and the like.

The history information may be information input by the user through the user node 100. The history information may be educational information, qualification information, career information, and the like, but is not limited thereto. Academic information may include the content of the curriculum recognized by the educational institution. The qualification information may include content obtained by obtaining a certificate issued by a certificate issuer. Career information may include work at the company.

The hub node 210 transmits the history information registration request received from the user node 100 to the blockchain DB 300 (S203). For example, the hub node 210 may transmit a history information registration request to the hub DB 310.

The blockchain DB 300 generates a first history information block in response to the history information registration request (S205). For example, the hub DB 310 may generate a first history information block in response to a history information registration request. In this case, the first history information block may be distributed and stored in the hub DB 310 and the participating DB 320 corresponding to the blockchain DB 300.

At least one of user identification information, history information, and time information when the hub DB 310 receives a history information registration request may be recorded in the first history information block. The user identification information, history information, and time information may be recorded to correspond to each other. A plurality of user identification information, a plurality of history information, and a plurality of time information corresponding to each other may be recorded in the first history information block.

Meanwhile, the hub node 210 transmits a history information confirmation request corresponding to the history information registration request to the participating node 220 (S207).

The history information confirmation request may be a request for confirmation of educational attainment information, a request for confirmation of qualification information, a request for confirmation of career information, and the like, but is not limited thereto.

The history information confirmation request may include user identification information and history information included in the history information registration request.

The participating node 220 confirms the authenticity of the history according to the user's history information according to the user identification information in response to the history information confirmation request (S209), and transmits the history confirmation information to the blockchain DB 300 (S211). . For example, the participating node 220 may transmit history confirmation information to the participating DB 320.

The history check information may refer to a result of checking the authenticity of the history according to the user history information according to the user identification information. For example, the history confirmation information may be a result that the authenticity of the user's history is recognized or the authenticity of the user's history is not recognized.

The history confirmation information may be determined by one participating node 220 or may be determined by a majority of the plurality of participating nodes 220. For example, one participating node 220 may confirm that the authenticity of the user's history is acknowledged or disapproved. For example, some of the plurality of participating nodes 220 may confirm that the authenticity of the user's history is recognized, and others may confirm that the authenticity of the user's history is disapproved.

The blockchain DB 300 generates a second history information block connected to the first history information block in response to the history confirmation information transmitted from the participating node 200 (S213). For example, the participating DB 320 may generate a second history information block after the first history information block in response to the history confirmation information. In this case, the blockchain including the first and second history information blocks may be distributed and stored in the hub DB 310 and the participating DB 320 corresponding to the blockchain DB 300.

For example, the participating DB 320 may generate a second history information block connected to the first history information block in response to the history confirmation information transmitted from one participating node 200. For example, the participating DB 320 receives a plurality of history confirmation information from the plurality of participating nodes 220 and connects to the first history information block in response to the history confirmation information indicated by a majority of the plurality of history confirmation information. The second history information block may be generated.

At least one of user identification information, history confirmation information, and time information at which the participation DB 320 receives the history confirmation information may be recorded in the second history information block. User identification information, history information, and time information may be recorded to correspond to each other, and a plurality of user identification information, a plurality of history information, and a plurality of time information corresponding to each other may be recorded in the second history information block. have.

Meanwhile, the participating node 220 transmits the history confirmation information corresponding to the history information confirmation request to the hub node 210 (S215), and the hub node 210 transmits the history information according to the history confirmation information to the user node 100. The registration response is transmitted (S217).

The history information registration response may be a history information registration complete response if the authenticity of the user's history is recognized, and a history information registration incomplete response if the authenticity of the user's history is not recognized.

The history information registration response corresponds to user identification information, history information, history confirmation information, time information at which the blockchain DB 300 received a history information registration request, and blockchain DB 300 received history confirmation information. It may include at least one of time information.

As such, by distributing and storing the history information block in the blockchain DB 300, the personal history information can be registered in real time, and by limiting the subject generating the history information block to the hub node 210 and the participating node 220, Forgery or tampering of the history information can be prevented.

3 is a flowchart illustrating a method of providing personal history information according to an embodiment of the present invention.

Referring to FIG. 3, the operator node 400 transmits a history information request to the hub node 210 (S301).

The operator node 400 may communicate with the hub node 210. For example, the operator node 400 may download an application provided by the hub node 210 and then transmit a history information request to the hub node 210 through the application.

The history information request may include user identification information. For example, the history information request may be a request for education information, qualification information, career information, etc. of the user according to the user identification information.

The hub node 210 transmits the history information request received from the operator node 400 to the blockchain DB 300 (S303). For example, the hub node 210 may transmit a history information request to the hub DB 310.

The blockchain DB 300 retrieves the first and second history information blocks corresponding to the history information request (S305). For example, the hub DB 310 may find first and second history information blocks, which are history information blocks in which user identification information of a history information request is recorded, among the history information blocks stored in the hub DB 310.

Subsequently, the blockchain DB 300 transmits history information and history confirmation information to the hub node 210 (S307). For example, the hub DB 310 extracts history information corresponding to user identification information from the first history information block, extracts history confirmation information corresponding to user identification information from the second history information block, and extracts the extracted history. Information and history confirmation information may be transmitted to the hub node 210.

The hub node 210 transmits a history information response corresponding to the history information request to the operator node 400 (S309). The history information response may include history information and history confirmation information extracted from the first and second history information blocks.

As such, by providing history information and history confirmation information based on the history information block stored in the blockchain DB 300, more reliable personal history information may be provided.

4 is a flowchart illustrating a method of updating a history information block according to an embodiment of the present invention.

Referring to FIG. 4, when the hub node 210 transmits a history information registration response to the user node 100 in step S217 of FIG. 2, the hub node 210 determines whether the history information is recognized based on the history confirmation information. It is determined whether or not (S401).

If the history information is recognized based on the history confirmation information, the hub node 210 generates a history information registration completion response (S403).

For example, the hub node 210 may generate a history information registration completion response when history information is recognized based on one history confirmation information received from one participating node 220.

For example, the hub node 210 may generate a history information registration completion response when a majority of the plurality of pieces of history information confirmation information received from the plurality of participating nodes 220 recognize the history information.

If the history information is not recognized based on the history confirmation information, the hub node 210 generates a history information registration incomplete response (S403).

For example, the hub node 210 may generate a history information registration incomplete response when history information is not recognized based on one history confirmation information received from one participating node 220.

For example, the hub node 210 may generate a history information registration incomplete response when a majority of the plurality of pieces of history information confirmation information received from the plurality of participating nodes 220 do not recognize the history information.

Hereinafter, a method of applying billing in an environment for providing personal history information based on the blockchain of FIG. 1 will be described with reference to FIG. 5. In the following, the description of the same parts as the above-described parts will be omitted or simplified.

5 is a flowchart illustrating a charging method according to history information registration according to an embodiment of the present invention.

When the user node 100 transmits a history information registration request to the hub node 210 (S501), the hub node 210 transmits a history information registration request to the charging node 500 (S503).

The history information registration request may include user identification information and history information.

The charging node 500 generates first charging information in response to the history information registration request (S505).

The first billing information may be billing information charged to the user according to the user identification information according to the history information registration.

On the other hand, the charging node 500 transmits a history information registration request to the blockchain DB 300 corresponding to the charging node 500 (S507). For example, the charging node 500 may transmit a history information registration request to the hub DB 310.

The blockchain DB 300 generates a first history information block in response to the history information registration request (S509). For example, the hub DB 310 may generate a first history information block in response to a history information registration request. In this case, the first history information block may be distributed and stored in the hub DB 310 and the participating DB 320 corresponding to the blockchain DB 300.

On the other hand, the charging node 500 transmits a history information confirmation request corresponding to the history information registration request to the participating node 220 (S511).

The history information confirmation request may be a request for confirmation of educational attainment information, a request for confirmation of qualification information, a request for confirmation of career information, and the like, but is not limited thereto.

The history information confirmation request may include user identification information and history information included in the history information registration request.

In response to the request for confirming the history information, the participating node 220 confirms the authenticity of the history according to the history information of the user according to the user identification information (S513), and transmits the history confirmation information to the charging node 500 (S515).

The history confirmation information may refer to a result of confirming the authenticity of the history according to the history information of the user according to the user identification information.

The charging node 500 generates second charging information in response to the history confirmation information (S517).

The second billing information may be billing information charged to the user according to the user identification information according to the confirmation of the history information.

Meanwhile, the blockchain DB 300 receives the history confirmation information from the charging node 500 (S519), and generates a second history information block connected to the first history information block in response to the history confirmation information (S521). . For example, the hub DB 310 may generate a second history information block connected to the first history information block in response to the history confirmation information. In this case, the blockchain including the first and second history information blocks may be distributed and stored in the hub DB 310 and the participating DB 320 corresponding to the blockchain DB 300.

The charging node 500 transmits the history confirmation information to the hub node 210 (S523), and the hub node 210 transmits the history information registration response according to the history confirmation information to the user node 100 (S525).

As such, each time a transaction for the blockchain DB 300 is generated, more accurate charging can be performed by generating charging information charged to the user.

6 is a diagram illustrating an environment for providing personal history information based on a blockchain according to an embodiment of the present invention.

Referring to FIG. 6, the personal history information providing environment based on the blockchain according to an embodiment of the present invention includes a user node 100, a service provider node 211, an education institution node 221, and a certificate issuing authority node 223. ), At least one of the corporation node 225, enterprise node 227, service provider DB (311), educational institution DB (321), certificate issuer DB (323), industrial DB (325), corporate DB (327) It may include.

The service provider node 211 may correspond to the hub node 210 of FIG. 1, and the educational institution node 221, the certificate authority authority node 223, the corporation node 225, and the enterprise node 227 are illustrated in FIG. 1. It may correspond to the participating node 220 of 1.

The service provider DB 311, the education institution DB 321, the certificate issuer DB 323, the corporation DB 325, and the enterprise DB 327 may update and distribute the blockchain as the blockchain DB 300. .

The service provider DB 311, the education institution DB 321, the certificate issuer DB 323, the corporation DB 325, and the enterprise DB 327 are the service provider node 211, the education institution node 221, and the certificate issuer. It may correspond to the institution node 223, the satin node 225, and the enterprise node 227.

In this case, for example, the service provider node 211 may access only the service provider DB 311 corresponding to the service provider node 211, but the service provider DB 311 corresponds to the blockchain DB 300. Therefore, the blockchain updated by the service provider DB 311 may be distributed and stored in the education institution DB 321, the certificate issuing authority DB 323, the corporation DB 325, and the enterprise DB 327.

7 to 9 are flowcharts for describing a method for providing personal history information according to an embodiment of the present invention, respectively.

Referring to FIG. 7, when the user node 100 transmits the education information registration request to the service provider node 211 (S701), the service provider node 211 transmits the education information registration request to the blockchain DB 300. (S703). For example, the service provider node 211 may transmit the education information registration request to the service provider DB 311.

The education information registration request may include user identification information and education information.

The blockchain DB 300 generates a first history information block in response to the education information registration request (S705). For example, the service provider DB 311 may generate a first history information block in response to the education information registration request. At this time, the first history information block is a service provider DB 311, education institution DB 321, certificate issuing authority DB 323, industrial DB 325, and company DB 327 corresponding to the block chain DB (300) Can be stored distributed.

At least one of user identification information, education information, and time information when the service provider DB 311 receives the education information registration request may be recorded in the first history information block.

On the other hand, the service provider node 211 transmits the education information confirmation request corresponding to the education information registration request to the educational institution node 221 (S707).

The education information verification request may include user identification information and education information included in the education information registration request.

The education institution node 221 checks the authenticity of the educational attainment according to the educational attainment information of the user according to the user identification information in response to the educational information check request (S709), and transmits the educational attainment confirmation information to the blockchain DB 300 (S711). ). For example, the educational institution node 221 may transmit the educational attainment confirmation information to the educational institution DB 321.

The blockchain DB 300 generates a second history information block connected to the first history information block in response to the education confirmation information transmitted from the educational institution node 221 (S713). For example, the educational institution DB 321 may generate a second history information block after the first history information block in response to the education confirmation information. At this time, the blockchain including the first and second history information block is a service provider DB 311 corresponding to the blockchain DB 300, educational institution DB 321, certificate issuing authority DB 323, industrial DB ( 325, and distributed in the enterprise DB 327.

In the second history information block, at least one of user identification information, education confirmation information, and time information when the education institution DB 321 receives the education confirmation information may correspond to each other.

Meanwhile, the educational institution node 221 transmits educational attainment confirmation information corresponding to the educational attainment information confirmation request to the service provider node 211 (S715), and the service provider node 211 transmits the educational attainment confirmation information to the user node 100. In response to the education information registration response is transmitted (S717).

According to this embodiment, personal education information can be registered in real time, can be confirmed by the educational institution node 221, and forgery or tampering can be prevented.

Referring to FIG. 8, when the user node 100 transmits a credential information registration request to the service provider node 211 (S801), the service provider node 211 transmits a credential information registration request to the blockchain DB 300. (S803). For example, the service provider node 211 may transmit a credential information registration request to the service provider DB 311.

The credential information registration request may include user identification information and credential information.

The blockchain DB 300 generates a first history information block in response to the entitlement information registration request (S805). For example, the service provider DB 311 may generate a first history information block in response to the entitlement information registration request. At this time, the first history information block is a service provider DB 311, education institution DB 321, certificate issuing authority DB 323, industrial DB 325, and company DB 327 corresponding to the block chain DB (300) Can be stored distributed.

At least one of user identification information, entitlement information, and time information at which the service provider DB 311 receives the entitlement information registration request may be recorded in the first history information block.

Meanwhile, the service provider node 211 transmits a credential information confirmation request corresponding to the credential information registration request to the credential issuing authority node 223 (S807).

The credential information confirmation request may include user identification information and credential information included in the credential information registration request.

The credential issuing authority node 223 confirms the authenticity of the credential according to the credential of the user according to the user identification information in response to the credential information confirmation request (S809), and transmits the credential confirmation information to the blockchain DB 300 ( S811). For example, the certificate issuing authority node 223 may transmit the qualification confirmation information to the certificate issuing authority DB 323.

The blockchain DB 300 generates a second history information block connected to the first history information block in response to the qualification confirmation information transmitted from the certificate issuing authority node 223 (S813). For example, the certificate issuing authority DB 323 may generate a second history information block after the first history information block in response to the qualification confirmation information. At this time, the blockchain including the first and second history information block is a service provider DB 311 corresponding to the blockchain DB 300, educational institution DB 321, certificate issuing authority DB 323, industrial DB ( 325, and distributed in the enterprise DB 327.

In the second history information block, at least one of user identification information, qualification confirmation information, and time information at which the certificate issuing authority DB 323 receives the qualification confirmation information may correspond to each other.

On the other hand, the certificate issuing authority node 223 transmits the credential confirmation information corresponding to the credential information confirmation request to the service provider node 211 (S815), the service provider node 211 the credential confirmation information to the user node (100) In step S817, the entitlement information registration response is transmitted.

According to the present embodiment, personal qualification information may be registered in real time, may be verified by the certificate issuing authority node 223, and forgery or tampering may be prevented.

Referring to FIG. 9, when the user node 100 transmits a career information registration request to the service provider node 211 (S901), the service provider node 211 transmits a career information registration request to the blockchain DB 300. (S903). For example, the service provider node 211 may transmit a career information registration request to the service provider DB 311.

The career information registration request may include user identification information and career information.

The blockchain DB 300 generates a first history information block in response to the career information registration request (S905). For example, the service provider DB 311 may generate a first history information block in response to the career information registration request. In this case, the first history information block is a service provider DB 311, education institution DB 321, certificate issuing authority DB 323, industrial DB 325, and company DB 327 corresponding to the block chain DB (300) Can be stored distributed.

At least one of user identification information, career information, and time information when the service provider DB 311 receives a career information registration request may be recorded in the first history information block.

On the other hand, the service provider node 211 transmits a career information confirmation request corresponding to the career information registration request to the industrial complex node 225 (S907).

The career information confirmation request may include user identification information and career information included in the career information registration request.

In response to the career information confirmation request, the corporation node 225 confirms the subscription details of the user according to the user identification information (S909), and transmits subscription details confirmation information to the blockchain DB 300 (S911). For example, the satin node 225 may transmit subscription history check information to the satin DB 325.

The blockchain DB 300 generates a second history information block connected to the first history information block in response to the subscription history confirmation information transmitted from the complex node 225 (S913). For example, the corporation DB 325 may generate a second history information block after the first history information block in response to the subscription history confirmation information. In this case, the blockchain including the first and second history information block is a service provider DB 311 corresponding to the blockchain DB 300, education institution DB 321, certificate issuing authority DB 323, industrial DB ( 325, and distributed in the enterprise DB 327.

In the second history information block, at least one of user identification information, subscription history confirmation information, and time information at which the DB DB 325 receives subscription history confirmation information may correspond to each other.

Meanwhile, the corporation node 225 transmits subscription history confirmation information corresponding to the career information confirmation request to the service provider node 211 (S915), and the service provider node 211 subscribes to the user node 100 for subscription history confirmation information. The career information registration response according to the transmission (S917).

The career information registration response may include information about whether the career information included in the career information registration request and the subscription history check information from the corporation node 225 match.

According to the present embodiment, personal career information can be registered in real time, can be confirmed by the satin node 225, and forgery or tampering can be prevented.

Although not shown, the enterprise node 227 and the enterprise DB 327 of FIG. 6 may perform operations of the satin node 225 and the satin DB 325 of FIG. 9. At this time, the enterprise node 227 confirms the user's work experience according to the identification information of the user in response to the career information confirmation request in step S909, and transmits the career confirmation information to the company DB 327 in step S911, step S915 May transmit career confirmation information corresponding to the career information confirmation request to the service provider node 211.

According to the present embodiment, personal career information can be registered in real time, verified by the enterprise node 227, and counterfeiting or tampering can be prevented.

So far I looked at the center of the preferred embodiment for the present invention. Those skilled in the art will understand that the present invention can be implemented in a modified form without departing from the essential characteristics of the present invention.

Therefore, the disclosed embodiments should be considered in descriptive sense only and not for purposes of limitation. The scope of the present invention is shown not in the above description but in the claims, and the invention claimed by the claims and the inventions equivalent to the claims should be construed as being included in the present invention.

100: user node
210: hub node
220: participating node
300: blockchain DB
310: hub DB
320: participating DB

Claims (10)

Receiving, by the hub node, a history information registration request from the user node;
Generating, by a hub DB corresponding to the hub node, a first history information block in response to the history information registration request;
Transmitting, by the hub node, a history information confirmation request corresponding to the history information registration request to a participating node;
Generating, by the participating DB corresponding to the participating node, a second history information block connected to the first history information block in response to the history confirmation information transmitted from the participating node;
Receiving, by the hub node, the history confirmation information corresponding to the history information confirmation request from the participating node; And
Transmitting, by the hub node, a history information registration response according to the history confirmation information to the user node;
The hub DB and the participating DB correspond to a blockchain DB, and store and store a blockchain including the first and second history information blocks,
The history information registration request includes user identification information and history information,
The history confirmation information indicates a result of confirming the authenticity of the history according to the history information of the user according to the user identification information,
The history information registration response is a history information registration complete response if the authenticity of the history of the user is recognized, a history information registration incomplete response if the authenticity of the history of the user is not recognized,
At least one of the user identification information, the history information, and time information when the hub DB receives the history information registration request is recorded in the first history information block.
At least one of the user identification information, the history confirmation information, and time information when the participation DB receives the history confirmation information is recorded in the second history information block.
The history information registration completion response is generated when a majority of the plurality of history confirmation information received from the plurality of participating nodes acknowledge the history information,
The history information registration incomplete response is generated when a majority of the plurality of history confirmation information received from the plurality of participating nodes do not recognize the history information. delete delete The method according to claim 1,
Receiving, by the hub node, a history information request including the user identification information from a provider node;
Retrieving, by the hub DB, first and second history information blocks corresponding to the history information request; And
And transmitting, by the hub node, a history information response including history information and history confirmation information extracted from the first and second history information blocks to the operator node. delete The method according to claim 1,
The history information includes at least one of education information, qualification information, and career information.
The participating node includes at least one of an educational institution node, a certificate issuer node, a corporation node, and an enterprise node.
The history confirmation information is education result confirmation information that is the result of the authenticity of the education according to the education information of the user by the educational institution node, the authenticity of the qualification according to the qualification information of the user by the certificate issuing agency node Qualification confirmation information that is a confirmed result, subscription history confirmation information that is the result of the subscription history according to the career information of the user by the Corporation node, the authenticity of the work experience according to the career information of the user by the enterprise node Is at least one of the career confirmation information that is the result of the verification, personal history information providing method. The method according to claim 1,
And the history confirmation information is history confirmation information indicated by a majority of the plurality of history confirmation information transmitted from a plurality of participating nodes. Receiving, by the charging node, a history information registration request of the user node from the hub node;
Generating, by the charging node, first charging information corresponding to the history information registration request;
Generating a first history information block in response to the history information registration request by a block chain database corresponding to the charging node;
Sending, by the charging node, a history information confirmation request corresponding to the history information registration request to a participating node;
Receiving, by the charging node, history confirmation information corresponding to the history information confirmation request from the participating node;
Generating, by the charging node, second charging information corresponding to the history confirmation information;
Generating, by the blockchain DB, a second history information block connected to the first history information block in response to the history confirmation information;
Delivering, by the charging node, the history confirmation information to the hub node; And
Transmitting, by the hub node, a history information registration response according to the history confirmation information to the user node;
The blockchain DB includes a DB corresponding to each of the hub node and the participating node, and a blockchain including the first and second history information blocks to a DB corresponding to each of the hub node and the participating node. Distributed storage,
The history information registration request includes user identification information and history information,
The history confirmation information indicates a result of checking the authenticity of the history according to the history information of the user according to the user identification information,
The history information registration response is a history information registration completion response if the authenticity of the history of the user is recognized, a history information registration incomplete response if the authenticity of the history of the user is not recognized, and the history information registration completion response is a plurality of participations. A majority of the plurality of history confirmation information received from the nodes is generated when the history information is acknowledged, and the history information registration incomplete response is generated by the majority of the plurality of history confirmation information received from the plurality of participating nodes. If the history information is not accepted,
The first billing information is billing information charged to the user according to the user identification information according to the history information registration,
And the second charging information is billing information charged to the user according to the user identification information according to the confirmation of the history information. delete The method according to claim 8,
The history information includes at least one of education information, qualification information, and career information.
The participating node includes at least one of an educational institution node, a certificate issuer node, a corporation node, and an enterprise node.
The history confirmation information is education result confirmation information that is the result of the authenticity of the education according to the education information of the user by the educational institution node, the authenticity of the qualification according to the qualification information of the user by the certificate issuing agency node Qualification confirmation information that is a confirmed result, subscription history confirmation information that is the result of the subscription history according to the career information of the user by the Corporation node, the authenticity of the work experience according to the career information of the user by the enterprise node Is at least one of the career confirmation information that is the result of the verification, personal history information providing method.

Images