KR102118962B1 - Method and server for managing user identity using blockchain network, and method and terminal for verifying user using user identity based on blockchain network - Google Patents

Abstract

The present invention relates to a method and a server for managing user identity by using a blockchain network and a method and a terminal for authenticating a user by using user identity based on a blockchain network. The method for managing user identity by using a blockchain network comprises the steps of: checking, by a specific authentication institution server, a specific user self-claim registered in a distributed ledger by using a specific user self-claim ID to obtain a second specific user specific value included in the specific user self-claim; and obtaining, by the specific authentication institution server, a specific user specific identity claim ID corresponding to a specific user specific identity claim registered in the distributed ledger by using a specific user specific identity claim registration transaction ID and transmitting a specific claim signature value made by signing at least the specific user specific identity with a private key of the specific certification institution server and the specific user specific identity claim ID to a specific user terminal.

Description

METHOD AND SERVER FOR MANAGING USER IDENTITY USING BLOCKCHAIN NETWORK, AND METHOD AND TERMINAL FOR VERIFYING USER USING USER IDENTITY BASED ON BLOCKCHAIN NETWORK}

The present invention relates to a method and a server for managing a user's identity using a blockchain network, and a method and a terminal for authenticating a user using a blockchain network-based user identity, and more specifically, from a user terminal. When the user ID generation transaction including the user ID generation data using the user address of the user and the first user signature value signed with the user master private key is obtained, the first user signature value is verified by verifying the first user signature value If it is confirmed that this is valid, the user management smart contract that executes the ID management contract registered in the distributed ledger of the blockchain network to generate claims for user identities is registered in the distributed ledger, and the user smart contract is registered in the distributed ledger. By sending the user smart contract registration transaction ID corresponding to the user smart contract registration transaction to the user terminal, the user terminal uses the user smart contract registration transaction ID as the user ID of the address of the user smart contract registered in the distributed ledger. User self-claim data and user self-claim data including a user ID, a user-specific value processed with user identities, and a second user signature value signing the user ID and user-specific value with a user private key, and the user self-claim data When a user self-claim registration request transaction including a third user signature value signed with a private key is obtained, if the third user signature value is verified to be valid by verifying the third user signature value, the user smart contract corresponding to the user ID is opened. Execute to enable the user self-claim corresponding to the user self-claim data to be registered in the distributed ledger, and the user using the blockchain network to send the user self-claim transaction ID corresponding to the user self-claim registered in the distributed ledger to the user terminal. How to manage the identity and server, and blockchain network It relates to a method and a terminal for authenticating a user using a user identity based.

With the development of production technology, transportation, and the like in a general trading structure, the structure of the transaction has gradually increased and the transaction cost has increased as the target of the transaction increases and the scope of the transaction expands. In addition, as most transactions are made indirectly, instead of direct transactions, it is expensive to trust the parties and targets of the transaction.

For example, it is necessary to use a credit rating agency to trust a trading party, and to guarantee the quality or value of a product, a certificate, a guarantee certificate, and collateral by a third party are required. In addition, a myriad of intermediaries such as notarization and trust institutions for guaranteeing payment and settlement stability and trust for financial institutions and contracts are appearing, and the cost of trust is incurred.

In particular, since the information about the personal certificate for user authentication is held by the certification authority, there may be a risk of being exposed to hacking while checking the certificate information for the user authentication, so various security measures are needed to strengthen security to prevent this. There is the inconvenience of using the program.

In addition, if a certification authority or the like that stores information on a user's personal certificate is hacked, a large amount of personal information is hacked.

On the other hand, authentication information such as a personal certificate for conventional user authentication is stored in each authentication authority that has been authenticated, and the user authenticates in which the corresponding authentication information for accessing each authentication information stored in a plurality of authentication authorities is stored. It is inconvenient to check the authority every time, and the authority for the authentication information to be stored in each certification authority is owned by each certification authority, so it is difficult for the user to easily manage his or her authentication information.

KR 10-2011-0029032 A KR 10-1484744 B1

The present invention aims to solve all of the above-mentioned problems.

In addition, another object of the present invention is to enable the user himself to have the authority for each user identity for user authentication.

In addition, another object of the present invention is to facilitate management of respective user identities for user authentication.

In addition, another object of the present invention is to enable the user himself to directly manage access rights to user identities.

According to an embodiment of the present invention for achieving the above object, in a method for managing the identity of a user using a blockchain network, (a) claims to generate claims for the identities of users and certification authorities The smart contract is registered in the distributed ledger of the blockchain network composed of a plurality of blockchain nodes with user smart contracts and certification authority smart contracts, respectively, in response to users and certification authorities, and the user smart contract And the addresses on the distributed ledger for the certification authority smart contracts are managed with the IDs of the users and the certification authorities, and each includes user specific values processed by user identities corresponding to the users. In the state where user self claims are registered in the distributed ledger, (i) a specific user ID from a specific user terminal, a specific user specific identity for authentication among specific user identities, and at least a first specific processing of the specific user identities A specific user specific identity claim request for a specific user specific identity including a user specific value, or (ii) the specific user specific identity corresponding to a specific user in response to an identity claim registration request from the specific user terminal When a request for confirmation of a specific user self claim ID corresponding to a specific user self claim is obtained from a specific certification authority server in response to the specific user specific identity claim registration request obtained from the specific user terminal by transmitting to the specific user terminal , At least one blockchain node among the plurality of blockchain nodes executes a specific user smart contract and sets the specific user self-claim ID corresponding to the specific user self-claim registered in the distributed ledger to the specific certification authority server By sending to the specific certification authority server using the specific user self-claim ID registered in the distributed ledger Confirming the specific user self claim to obtain a second specific user specific value included in the specific user self claim; And (b) a specific user-specific identity claim from the specific certification authority server-the specific user-specific identity claim is generated by the specific certification authority server, and is included in the specific user-specific identity claim registration request from the specific user terminal. After the first specific user specific value and the second specific user specific value included in the specific user self-claim of the distributed ledger match, the specific certification authority server verifies the specific user specific identity, and then the A first specific certification authority that signs a specific certification authority ID corresponding to a specific certification authority server, a specific claim type corresponding to the specific user specific identity, and the specific user ID and the specific claim type with a private key of the specific certification authority server. Generated by including a signature value-and a specific user-specific identity claim registration request transaction including a second specific certification authority signature value signed with the specific private authority's master private key and the specific user-specific identity claim is obtained. When at least one blockchain node verifies the signature value of the second specific certification authority and the second specific certification authority signature value is valid, the specific user specific identity claim is executed to the distributed ledger by executing the specific user smart contract. The specific certification authority by sending a specific user-specific identity claim registration transaction ID corresponding to a specific user-specific identity claim registration transaction to be registered and to register the specific user-specific identity claim to the distributed ledger, to the specific certification authority server A server obtains a specific user-specific identity claim ID corresponding to the specific user-specific identity claim registered in the distributed ledger by using the specific user-specific identity claim transaction ID, and at least authenticates the specific user-specific identity The specific claims signature value signed with your institution's private key, Transmitting the specific user-specific identity claim ID to the specific user terminal; A method is provided that includes.

According to an embodiment of the present invention, a blockchain node of a blockchain network that manages a user's identity using a blockchain network, comprising: a memory in which instructions for managing the user identity are stored; And a processor performing an operation of managing the user identity according to the instructions stored in the memory. Including, wherein the processor, (i) claims smart contracts to generate claims for the identities of users and certification authorities corresponding to the users and the certification authority user smart contracts and certification authority smart respectively Addresses on the distributed ledger for the user smart contracts and the certification authority smart contracts are registered in the distributed ledger of the blockchain network constituted by a plurality of blockchain nodes as contracts, the users and the certification authority (I-1) from a specific user terminal while each user self-claim including user-specific values managed by user IDs and processed user identities corresponding to the users is registered in the distributed ledger. Responding to a specific user specific identity claim registration request for a specific user specific identity, including a specific user ID, a specific user specific identity for authentication among specific user identities, and a first specific user specific value at least processing the specific user identities. Alternatively, (i-2) the specific user identification obtained from the specific user terminal by transmitting the specific user specific identity corresponding to the specific user to the specific user terminal in response to the identity claim registration request from the specific user terminal When a request for confirmation of a specific user self-claim ID corresponding to a specific user self-claim is obtained from a specific certification authority server in response to an identity claim registration request, the specific user self-claim registered in the distributed ledger is executed by executing a specific user smart contract By sending the specific user self-claim ID corresponding to the specific certification authority server, the specific certification authority server confirms the specific user self-claim registered in the distributed ledger by using the specific user self-claim ID to identify the A process for obtaining a second specific user specific value included in the user self claim, and (ii) the specific authentication A specific user specific identity claim from an authority server-The specific user specific identity claim is generated by the specific certification authority server, and the first specific user specific value included in the specific user specific identity claim registration request from the specific user terminal And the second specific user specific value included in the specific user self-claim of the distributed ledger, the specific certification authority server verifies the specific user specific identity, and then corresponds to the specific certification authority server. Generated by including a specific certification authority ID, at least a specific claim type corresponding to the specific user specific identity, and a first specific certification authority signature value signing the specific user ID and the specific claim type with the private key of the specific certification authority server -The second specific certification authority signature when a specific user specific identity claim registration request transaction is obtained, including the second specific certification authority signature value signed with the master private key of the specific certification authority and the specific user specific identity claim If the second specific certification authority signature value is valid by verifying a value, the specific user-specific identity claim is executed in the distributed ledger by executing the specific user smart contract, and the specific user-specific identity claim is sent to the distributed ledger. By sending a specific user-specific identity claim registration transaction ID corresponding to a specific user-specific identity claim registration transaction to be registered to the specific certification authority server, the specific certification authority server uses the specific user-specific identity claim registration transaction ID Obtain a specific user-specific identity claim ID corresponding to the specific user-specific identity claim registered in the distributed ledger, and at least the specific user signature identity and the specific user signature value that signed the specific user-specific identity with the private key of the specific certification authority Identifies the identity claim ID There is provided a blockchain node that performs a process to transmit to a specific user terminal.

In addition to this, a computer readable recording medium for recording a computer program for executing the method of the present invention is further provided.

According to the present invention, there are the following effects.

The present invention can prevent user information from being traded regardless of the user's will, because the user can own the authority for each user identity for user authentication by using a blockchain technology with excellent security. There will be.

In the present invention, since user identities are stored by a user, management of each user identities can be facilitated.

According to the present invention, it is possible to prevent user information from being exposed irrespective of the user's will by allowing the user himself to directly manage access rights to user identities.

1 schematically shows a system for managing the identity of a user using a blockchain network according to an embodiment of the present invention,
2A and 2B schematically illustrate a method of generating a user ID and the like in a method of managing user identities using a blockchain network according to an embodiment of the present invention,
3A and 3B schematically illustrate a method for registering user self-claim in a method of managing user identity using a blockchain network according to an embodiment of the present invention,
4A and 4B schematically illustrate a method of adding and deleting user keys in a method for managing user identity using a blockchain network according to an embodiment of the present invention,
5A and 5B schematically illustrate a method of backing up user data in a method of managing user identity using a blockchain network according to an embodiment of the present invention,
6 schematically shows a method of recovering user data in a method of managing user identity using a blockchain network according to an embodiment of the present invention,
7A and 7B schematically illustrate a method of registering a specific identity claim in a method of managing a user identity using a blockchain network according to an embodiment of the present invention,
8A and 8B schematically illustrate a method of deleting a specific identity claim in a method of managing user identities using a blockchain network according to an embodiment of the present invention,
9A and 9B schematically illustrate another method of deleting a specific identity claim in a method for managing user identity using a blockchain network according to an embodiment of the present invention,
10A and 10B schematically illustrate a method of authenticating a user using a user identity based on a blockchain network according to an embodiment of the present invention.

For a detailed description of the present invention, which will be described later, reference is made to the accompanying drawings that illustrate, by way of example, specific embodiments in which the invention may be practiced. These examples are described in detail enough to enable those skilled in the art to practice the present invention. It should be understood that the various embodiments of the present invention are different, but need not be mutually exclusive. For example, certain shapes, structures, and properties described herein may be implemented in other embodiments without departing from the spirit and scope of the invention in relation to one embodiment. In addition, it should be understood that the location or placement of individual components within each disclosed embodiment can be changed without departing from the spirit and scope of the invention. Therefore, the following detailed description is not intended to be taken in a limiting sense, and the scope of the present invention, if appropriately described, is limited only by the appended claims, along with all ranges equivalent to those claimed. In the drawings, similar reference numerals refer to the same or similar functions throughout several aspects.

Hereinafter, preferred embodiments of the present invention will be described in detail with reference to the accompanying drawings in order to enable those skilled in the art to easily implement the present invention.

1 relates to a system for managing the identity of a user using a blockchain network according to an embodiment of the present invention, the system includes a user terminal 100, a certification authority server 200, and a blockchain node 300 It may include.

First, the user terminal 100 is a subject that manages a user identity, and may include a personal computer (PC), a mobile computer, a PDA/EDA, a mobile phone, a smartphone, a tablet, and an IoT device. In addition, the user terminal 100 is not limited to this, and may include any device such as a portable game machine having a wired/wireless communication function, a digital camera, and personal navigation. In addition, the user terminal 100 includes a memory 110 for storing instructions for the management of the user identity and a processor 120 for performing an operation for managing the user identity in response to the instructions stored in the memory 110. can do. In this case, although only one user terminal 100 is illustrated in FIG. 1, this is for convenience of description, and the user terminal 100 may be composed of a plurality corresponding to each user.

Specifically, the user terminal 100 is typically a computing device (eg, a computer processor, memory, storage, input device and output device, a device that may include components of other existing computing devices; electronics such as routers, switches, etc.) A desired system using a combination of communication devices; electronic information storage systems such as network attached storage (NAS) and storage area networks (SAN)) and computer software (i.e. instructions that cause the computing device to function in a particular way). It may be to achieve performance.

In addition, the processor of the computing device may include hardware configurations such as a micro processing unit (MPU) or a central processing unit (CPU), a cache memory, and a data bus. Further, the computing device may further include a software configuration of an operating system and an application performing a specific purpose.

Next, the certification authority server 200 performs authentication for user identities, and authenticates the user identity in response to the memory 210 storing instructions for user identity authentication and the instructions stored in the memory 210. It may include a processor 220 for performing an operation for. In this case, although only one certification authority server 200 is shown in FIG. 1, this is for convenience of explanation, and the certification authority server 200 is made up of a plurality of numbers corresponding to each certification authority that performs authentication for a user identity. Can be.

Specifically, the certification authority server 200 is typically a computing device (eg, a computer processor, memory, storage, input device and output device, other devices that may include components of existing computing devices; routers, switches, and the like) Electronic communication devices; electronic information storage systems such as network attached storage (NAS) and storage area networks (SAN)) and computer software (i.e. instructions that cause a computing device to function in a particular way). It may be to achieve system performance.

Next, the blockchain nodes 300 store and manage claims corresponding to user identities or information related to claims, and may be a server constituting a blockchain network, and store instructions for user identity management The memory 310 may include a processor 320 that performs an operation for user identity management in response to the memory 310 and instructions of the memory 310. At this time, in FIG. 1, the block chain node 300 is shown as six, but this is for convenience of description, and the number of the block chain nodes 300 is not limited thereto.

Specifically, the blockchain node 300 is specifically, the information management server 200 is typically a computing device (e.g., computer processor, memory, storage, input and output devices, other components of the existing computing device) Devices that can: electronic communication devices such as routers, switches, etc.; electronic information storage systems such as network attached storage (NAS) and storage area networks (SAN)) and computer software (i.e., enable computing devices to function in a particular way) It may be to achieve the desired system performance using a combination of instructions).

In addition, the system for managing the user's identity using a blockchain network according to an embodiment of the present invention may further include a service providing server (not shown), and the service providing server may authenticate a user using a user identity, etc. Through the user terminal 100 may provide a service desired by the user. In this case, the service providing server may be one that achieves desired system performance using a combination of a computing device and computer software.

A method of managing user identity using a system for managing user identity using a blockchain network according to an embodiment of the present invention configured as described above will be described as follows.

A method of generating a user ID and the like in a method of managing user identities using a blockchain network according to an embodiment of the present invention will be described with reference to FIG. 2A.

When the user runs the identity management app installed on the user terminal 100 to generate the user private key and the user public key, and the user address is generated using the user public key, the user terminal to generate the user ID (100), for example, by executing the identity management app installed on the user terminal 100 to transmit the user ID generation transaction to the blockchain network (S1). At this time, the user ID generation transaction may include user ID generation data using the user address and a first user signature value signed with the user master private key. In addition, the user master private key may be a user private key.

Then, at least one blockchain node 300 among the plurality of blockchain nodes constituting the blockchain network verifies the first user signature value included in the user ID generation transaction (S2).

For example, at least one blockchain node 300 executes a digital signature verification module registered in a distributed ledger on the blockchain network, and refers to a user's master private key by referring to the first user signature value and user ID generation data. You can get the master public key. That is, the at least one blockchain node 300 transmits the first user signature value and user ID generation data to the digital signature verification module registered in the distributed ledger on the blockchain network, and the digital signature verification module is input first The user master private key corresponding to the user master private key used to sign the first user signature value is obtained using the user signature value and the user ID generation data. Then, the at least one blockchain node 300 checks whether the first comparison target data identified from the first user signature value and the user ID generation data match by using the acquired user master public key. We will verify that this is valid.

As another example, the user terminal 100 further includes the user master public key corresponding to the user master private key in the user ID generation transaction, so that at least one blockchain node 100 uses the user master public key. It is verified whether the first user signature value is valid by confirming whether the first comparison target data identified from the first user signature value and the user ID generation data match.

Subsequently, when it is determined that the first user signature value is valid, at least one blockchain node 300 executes an identity management contract registered in the distributed ledger of the blockchain network to generate a claim for user identities. Register the contract with the distributed ledger (S3).

Then, the at least one blockchain node 300 transmits the user smart contract registration transaction ID corresponding to the user smart contract registration transaction to register the user smart contract to the distributed ledger to the user terminal 100 (S4).

Then, the user terminal 100 checks whether the user smart contract is registered in the distributed ledger using the user smart contract registration transaction ID (S5), and the user is agreed by the blockchain nodes 300 constituting the blockchain network. When the smart contract is registered in the distributed ledger, the user smart contract address, which is the location information of the user smart contract registered in the distributed ledger, is obtained (S6), and the obtained user smart contract address is used as the user ID in the user terminal 100 You will be registered.

In FIG. 2A, the user terminal 100 must pay the transaction fee on the blockchain network by transmitting the user ID generation transaction directly to the blockchain network. However, in this case, the user terminal 100 may directly pay the transaction blood through another device without paying the transaction blood.

That is, referring to FIG. 2B, the user terminal 100 does not pay the transaction blood for the user ID generation transaction, but allows the proxy server 150 to pay the transaction blood.

At this time, the user terminal 100 transmits a user ID generation transaction to the proxy server 150 (S1-1).

Then, the proxy server 150 transmits the first proxy server signature value signed by the proxy server master private key of the user ID generation transaction and the user ID generation transaction to the blockchain network (S1-2). , Accordingly, at least one blockchain node 300 constituting the blockchain network verifies the first proxy server signature value (S1-3), and if the first proxy server signature value is valid, the first user signature value Will be verified (S2). At this time, at least one blockchain node 300 has verified the first user verification value, but unlike this, the proxy server 150 may verify the first user verification value.

In addition, the at least one blockchain server 300 transmits the user smart contract registration transaction ID to the proxy server 150 (S4-1), so that the proxy server 150 sends the user smart contract registration transaction ID to the user terminal 100. To (S4-2).

In the above, the process of generating a user ID through the user terminal 100 has been described, but a certification authority server, a service providing server, etc. can also generate each ID by the same method.

A method of registering user self-claim in a method of managing user identity using a blockchain network according to an embodiment of the present invention will be described with reference to FIG. 3A.

The user creates a user self-claim to be registered by using the user identity management app of the user terminal 100 (S11).

At this time, the user self-claim may include a user ID, a user specific value processed with user identities, and a second user signature value signed with the user ID and the user specific value. In this case, the user-specific value may be a value obtained by processing each of the specific identities for the user.

As an example, the user self-claim may be generated in a format of 1. topic, 2. scheme, 3. owner, 4, signature value, 5. data. At this time, the topic may be the type of claim related to user identities, the scheme is the encryption algorithm used, the owner is the subject generating the claim, the signature value is the subject's signature value, and the data is the claim content.

Meanwhile, the user identities include feature information for identifying the user, and the feature information may be stored in the user terminal. In addition, user identities may include all user-related feature information, such as user name, date of birth, gender, nickname, phone number, e-mail address, biometric information, behavioral characteristics, hobbies, body features, and life patterns, and each through a topic. Characteristic information of can be classified by claim type, and topics can be added and deleted as needed. In addition, the owner may be a user ID generated by the method of FIG. 2A or 2B. In addition, the data may be identity information for a claim, a user specific value in which all the identities of the user are processed in the user self claim, and a claim type corresponding to at least one specific identity in the identity claim, that is, a kind of topic. . In addition, the data may include a time stamp, but is not limited thereto, and may include various authentication confirmation data. At this time, the authentication verification data is not the user's identities and the processed values, and may include arbitrary data such as nonce for confirming the evidence that each of the user's identities has been authenticated. In addition, security can be improved by adding a user ID to the data.

Further, the user specific value may be a root hash value of the Merkle tree in which hash values for each of the user identities are assigned to at least some of the respective leaf nodes. In this case, the user specific value may be a hash value for one user identity.

Thereafter, the user terminal 100 transmits a user self claim registration request transaction for registering the generated user self claim to the blockchain network (S12). At this time, the user self-claim registration request transaction includes a user self-claim data, that is, a user ID, a user specific value processed with user identities, and a user including a user ID and a second user signature value signed with the user specific value as a user private key It may include a self-claim and a third user signature value that signs the user self-claim data with a user master private key.

Then, at least one blockchain node 300 among the plurality of blockchain nodes constituting the blockchain network verifies the third user signature value (S13). At this time, verification of the third user signature value may be performed in the same manner as described with reference to FIG. 2A, and a detailed method for verifying the signature value will be omitted in the following description.

Thereafter, when it is determined that the third user signature value is valid, the at least one blockchain node 300 verifies the second user signature value included in the user self claim (S14).

And, when it is confirmed that the second user signature value is valid, at least one blockchain node 300 executes a user smart contract corresponding to the user ID registered in the distributed ledger of the blockchain network to correspond to the user self-claim data. The user self-claim is registered in the distributed ledger (S15), and the user self-claim transaction ID corresponding to the transaction for registering the user self-claim in the distributed ledger is transmitted to the user terminal 100 (S18).

Then, the user terminal 100 checks whether the user self-claim is registered in the distributed ledger using the user self-claim transaction ID, and the user self-claim is distributed by agreement of the blockchain nodes 300 constituting the blockchain network. When registered in the ledger, the user self claim address, that is, the user self claim ID, which is the location information where the user self claim is registered in the distributed ledger is obtained.

On the other hand, referring to Figure 3b, the user terminal 100 transmits a user self claim registration request transaction to the proxy server 150 (S12-1), the proxy server 150 is a user self claim registration request transaction, the user The second proxy server signature value, which signed the self-claim registration request transaction with the proxy server master private key, is transmitted to the blockchain network (S12-2). Then, at least one blockchain node 300 among the plurality of blockchain nodes constituting the blockchain network verifies the second proxy server signature value (S13-1), and if the second proxy server signature value is valid, 2 The user signature value is verified (S14). At this time, at least one blockchain node 300 has verified the second user signature value. Alternatively, the proxy server 150 may verify the second user signature value.

In addition, at least one blockchain node 300 transmits the user self-claim transaction ID to the proxy server 150 (S16-1), and the proxy server 150 sends the user self-claim transaction ID to the user terminal 100 By transmitting to (S16-2), the user terminal 100 may obtain a user self-claim ID.

Through this, in FIG. 3A, the user terminal 100 has paid transaction blood, but in FIG. 3B, the proxy server 150 may allow the transaction payment to be made on behalf of the user terminal 100.

A method of adding and deleting user keys in a method for managing user identity using a blockchain network according to an embodiment of the present invention will be described with reference to FIG. 4A.

In a method of managing user identity using a blockchain network according to an embodiment of the present invention, a user private key is generated using a user address, and each user key can be added or deleted according to the purpose of using the key. . In addition, it is possible to perform an operation of a corresponding purpose only for a user key corresponding to each purpose.

A user key addition or deletion request transaction including a user key addition or deletion request data including a user address and a key purpose and a user signature value signed by the user master private key through the user identity management app of the user terminal 100 When transmitting (S21), at least one blockchain node 300 verifies the user signature value (S22).

At this time, if it is confirmed that the user signature value is valid, the at least one blockchain node 300 adds the user key according to the key purpose from the user key list on the distributed ledger or deletes the user key registered in the key list (S23). ).

Then, the at least one blockchain node 300 transmits the transaction ID for registering the transaction for adding or deleting the user key to the distributed ledger to the user terminal 100 (S24).

Then, the user terminal 100 confirms whether the requested user key is added or deleted from the distributed ledger using the transaction ID (S25), and receives the result information from the distributed ledger of the blockchain network (S26). In result, it is possible to check the result of whether the requested user key is added or deleted. At this time, the user address may initially be registered in the key list for all purposes by default, and different user addresses for the corresponding purpose may be registered in the key list for each purpose according to the addition of the user key.

In addition, referring to FIG. 4B, when the user terminal 100 transmits a transaction for adding or deleting a user key to the proxy server 150 (S21-1), the proxy server proxies the transaction for adding or deleting a user key and the same. The proxy server signature value signed with the server master private key is transmitted to the blockchain network (S21-2), and at least one blockchain node 300 among the plurality of blockchain nodes constituting the blockchain network is signed by the proxy server. If it is determined that the value is valid by verifying the value (S21-3), the user key is added or deleted (S23). At this time, the user signature value included in the user key addition or deletion request transaction may be verified by the proxy server 150 or at least one blockchain node 300.

In addition, at least one blockchain node 300 transmits the transaction ID to the proxy server 150 (S24-1), and the proxy server 150 transmits the transaction ID to the user terminal 100 (S24-2) ) To allow the user terminal 100 to confirm the result of the addition or deletion of the user key using the transaction ID.

Through this, in FIG. 4A, the user terminal 100 has paid transaction blood, but in FIG. 4B, the proxy server 150 may allow the transaction payment for the user terminal 100.

A method of backing up user data in a method of managing user identity using a blockchain network according to an embodiment of the present invention will be described with reference to FIG. 5A.

User data backup is performed when the user identity management app installed in the user terminal 100 is deleted or cannot be managed. In order to enable the user to recover the verified data, the user identities and user keys are IPFS (InterPlanetary File System), etc. It may be stored in the same distributed storage system, email, or personal storage space.

The user generates encrypted user data by encrypting user data to be backed up through the user identity app of the user terminal 100, for example, user identities and user keys with a user public key (S31).

Then, the user terminal 100 transmits the generated encrypted user data to the distributed storage system to request an encrypted user data registration (S32), and accordingly, at least one of a plurality of distributed storage servers constituting the distributed storage system. The distributed storage server 400 registers the encrypted user data in the distributed storage system (S33).

Thereafter, the distributed storage server 400 transmits the file ID, which is the location information of the encrypted user data registered in the distributed storage system, to the user terminal 100 (S34).

Alternatively, the user may encrypt user data to be backed up through the user identity app of the user terminal 100 with a user public key to generate encrypted user data, and store the encrypted user data in an email, personal storage space, and the like. At this time, the personal storage space may include a web hard, a cloud hard, a memory card, a storage space of a user terminal, and the like, but is not limited thereto, and may include all storage spaces accessible by a user.

Then, the user terminal 100 generates a user self-claim including a user ID and a file ID (S35).

And, by the same method as in Figure 3a, the user terminal 100 makes a user self claim registration request (S36) to the blockchain network, the at least one blockchain node 300 constituting the blockchain network is the file ID The user's self-claim for is registered in the distributed ledger (S37). Thereafter, the user terminal 100 may check the registration result by checking the user self-claim ID (S38).

In addition, referring to FIG. 5B, the user terminal 100 makes a request for registering encrypted user data with the proxy server 150 (S32-1), and the proxy server 15 requests for registering user data encrypted with the distributed storage system. (S32-2), and accordingly, at least one distributed storage server 400 among the multiple distributed storage servers constituting the distributed storage system registers the encrypted user data in the distributed storage system (S33).

Then, the distributed storage server 400 transmits the file ID which is the location information of the encrypted user data registered in the distributed storage system to the proxy server 150 (S34-1), and the proxy server 150 uses the file ID. It transmits to the terminal 100 (S34-2).

Alternatively, the user may encrypt user data to be backed up through the user identity app of the user terminal 100 with a user public key to generate encrypted user data, and store the encrypted user data in an email, personal storage space, and the like. At this time, the personal storage space may include a web hard, a cloud hard, a memory card, a storage space of a user terminal, and the like, but is not limited thereto, and may include all storage spaces accessible by a user.

In addition, by the same method as in FIG. 3B, the user terminal 100 requests the user self claim registration to the proxy server 150 (S36-1), and the proxy server 150 requests the user self claim registration to the blockchain network. (S36-2).

Through this, in FIG. 5A, the user terminal 100 has paid transaction blood, but in FIG. 5B, the proxy server 150 may allow the transaction payment to be made on behalf of the user terminal 100.

A method of recovering user data in a method of managing user identity using a blockchain network according to an embodiment of the present invention will be described with reference to FIG. 6.

In order to recover the user data for the user identities, the user makes a user self-claim ID verification request (S41) to the blockchain network through the user identity management app of the user terminal 100. In this case, the user self-claim to be checked may be a user self-claim corresponding to the file ID registered by the method as shown in FIG. 5A.

Then, at least one blockchain server 300 constituting the blockchain network executes a user smart contract to check the registered user self-claim ID in relation to the file ID among the user claims registered in the distributed ledger, and the user terminal The user self-claim ID is transmitted to (100) (S42).

Then, the user terminal 100 makes a request for confirmation of the user self-claim (S43) to the blockchain network using the verified user self-claim ID, and accordingly at least one blockchain node (300) constituting the blockchain network ) Executes the user smart contract and transmits the file ID included in the user self-claim to the user terminal 100 (S44 ).

Then, the user terminal 100 requests the encrypted user data corresponding to the file ID to the distributed storage system using the obtained file ID (S45), and at least one distributed storage server 400 of the distributed storage system is a file The encrypted user data corresponding to the ID is checked, and the checked encrypted user data is transmitted to the user terminal 100 (S46).

Unlike this, when the encrypted user data is stored in an email, a personal storage space, or the like, the user may directly obtain encrypted user data from an email, a personal storage space, etc. through the user terminal 100.

Then, the user terminal 100 decrypts the obtained encrypted user data with a user private key to obtain user data, and thereby recovers the user data (S47).

In the above, the user terminal 100 directly communicates with the distributed storage system and the blockchain network. Alternatively, the user terminal 100 may mediate communication through a proxy server by the same method as above.

A method of registering a specific identity claim in a method of managing a user identity using a blockchain network according to an embodiment of the present invention will be described with reference to FIG. 7A.

Claims smart contracts to generate claims for the identities of users and certification authorities by the same method as in FIGS. 2A and 3A correspond to users and certification authorities, respectively, user smart contracts and certification authority smart Registered in the distributed ledger of the blockchain network composed of multiple blockchain nodes as contracts, and the addresses on the distributed ledger for user smart contracts and certification authorities smart contracts are managed by the IDs of users and certification authorities In the state in which each user self-claim including user-specific values processed by user identities corresponding to the users is registered in the distributed ledger, a list request of authentication authorities (S51) is obtained from the specific user terminal 100 If it does, the at least one blockchain node 300 transmits a list of authentication agencies registered in the distributed ledger to the specific user terminal 100 (S52). Then, the specific user terminal 100 allows the user to select a specific certification authority to perform authentication for a specific user identity in the certification authority list, and when a specific certification authority is selected by the user, the selected specific certification authority server 200 ) To request information about a specific certification authority (S53).

Then, the specific certification authority server 200 transmits (S54) its own information, that is, specific certification authority information to the user terminal 100 in response to a request for information from the user terminal 100 (S54). The authority server 200 transmits the authentication key information stored in the server, or transmits the access key for the specific authentication authority information registered in the blockchain network or distributed storage system, so that the user terminal 100 accesses the access key. Through this, it is possible to obtain specific certification authority information from a blockchain network or a distributed storage system. Further, the specific certification authority information may include information about the certification authority and information about authenticable user identities, but is not limited thereto.

Then, the specific user terminal 100 transmits a specific user specific identity claim registration request to the specific certification authority server 200 for authentication for the specific identity selected by the specific user (S55). At this time, the request for registering a specific user-specific identity claim may include a specific user ID, a specific user-specific identity for authentication among specific user identities, and a first specific user-specific value processed by specific user identities. In addition, the first specific user specific value may be a root hash value of the Merkle tree in which hash values for each of the specific user identities are assigned to at least some of the respective leaf nodes, and the Merkle tree information is requested in the specific user specific identity claim registration request. May be included. At this time, the request for registering a specific user-specific identity claim may include authentication confirmation data, for example, a time stamp, nonce, and the like.

On the other hand, unlike the specific user terminal 100 requests a specific user specific identity claim registration to the specific certification authority server 200 for authentication for a specific identity selected by the specific user, the specific user is a specific certification authority server 200 ) May request authentication for a specific user-specific identity, and at this time, the specific certification authority server 200 transmits a specific user-specific identity stored in the specific user terminal 100 to transmit a specific user-specific identity. ) May request a specific user-specific identity claim registration for a specific user-specific identity. As an example, since the specific certification authority server 200 does not have a first specific user specific value, the specific specific user specific value corresponding to the specific user specific identity is transmitted by transmitting the specific user specific identity to the user terminal 100. can do.

Then, the specific certification authority server 200 responds to a request for registering a specific user-specific identity claim from the specific user terminal 100, and a specific user self-claim ID for a specific user self-claim corresponding to a specific user ID through the blockchain network Request for confirmation (S56).

Then, at least one blockchain node 300 among a plurality of blockchain nodes constituting the blockchain network executes a specific user smart contract to execute a specific user self claim corresponding to a specific user self claim registered in the distributed ledger. Check the ID and send it to the specific certification authority server 200 (S57). At this time, the at least one blockchain node 300 can identify the specific user self-claim ID by checking the claim corresponding to the self-claim from claims corresponding to the specific user.

Then, the specific certification authority server 200 confirms the specific user self-claim registered in the distributed ledger using the specific user self-claim ID (S58) to obtain a second specific user specific value included in the specific user self-claim (S59) )can do.

Then, the specific certification authority server 200 includes the first specific user specific value included in the specific user specific identity claim registration request from the specific user terminal 100 and the second specific user specified in the specific user self claim of the distributed ledger. It is checked whether the values match, and if the first specific user specific value and the second specific user specific value match, the specific user specific identity is verified (S60 ).

As an example, when the first specific user specific value is a root hash value of the Merkle tree using hash values for each of the specific user identities as leaf nodes, the first root hash value and the distributed ledger included in the specific user specific identity claim registration request Checks whether the second root hash value included in the specific user self-claim of is the same, and when the first root hash value and the second root hash value are the same, is compared by using the merkle tree information and the hash value of the specific user specific identity A root hash value is generated, and whether the generated comparison hash value is the same as the first root hash value determines whether a specific user specific identity is information of a specific user. Then, it is verified that the specific identity is not correct. At this time, the verification of the specific identity is performed by the specific certification authority server 200, and may be verified by confirming whether the specific user specific identity matches the characteristic information of the specific user. For example, if a specific identity is a phone number, normal phone number authentication is performed to check whether the corresponding phone number matches a specific user's phone number.

Then, when the specific user-specific identity is verified, the specific certification authority server 200 generates a specific user-specific identity claim (S61).

At this time, the specific user specific identity claim is a specific certification authority ID corresponding to a specific certification authority server 200, a specific claim type corresponding to a specific user specific identity, and a specific user ID and a specific claim type as a private key of the specific certification authority server. It may include a signed first specific certification authority signature value. In this case, the specific user specific identity claim may include authentication verification data, for example, a time stamp, nonce, etc., and the first specific certification authority signature value may be signed by adding authentication verification data.

For example, a specific user-specific identity claim may be generated in a format of 1. topic, 2. scheme, 3. owner, 4, signature value, 5. data. At this time, the topic may be the type of claims related to user identities, the scheme is the encryption algorithm used, the owner is the subject generating the claim, the signature value is the subject's signature value, and the data is authentication verification data.

Thereafter, the specific certification authority server 200 transmits a request for registering a specific user-specific identity claim to register the generated specific user-specific identity claim to the blockchain network (S62). At this time, the specific user specific identity claim registration request transaction may include a specific user specific identity claim and a second specific certification authority signature value signed by the specific user authority identity claim with the master private key of the specific certification authority.

Then, at least one blockchain node 300 of the blockchain network verifies the signature value of the second specific certification authority. In addition, when the second specific certification authority signature value is valid, the at least one blockchain node 300 may verify the second specific certification authority signature value included in the specific user-specific identity claim.

And, the at least one blockchain node 300 executes a specific user smart contract registered in the distributed ledger so that the specific user specific identity claim is registered in the distributed ledger (S63), and the specific user specific identity claim is registered in the distributed ledger. The specific user specific identity claim registration transaction ID corresponding to the specific user specific identity claim registration transaction to be transmitted is transmitted to the specific certification authority server 200 (S64).

Then, the specific certification authority server 200 checks whether the specific user-specific identity claim is registered in the distributed ledger (S65) by using the transaction ID of the specific user-specific identity claim (S65), and the blockchain node constituting the blockchain network ( When a specific user-specific identity claim is registered in the distributed ledger by agreement of 300), a specific user-specific identity claim ID that is location information in which the specific user-specific identity claim is registered in the distributed ledger is obtained (S66), and the specific user-specific identity And transmits the specific claim signature value signed with the private key of the specific certification authority and the obtained specific user specific identity claim ID to the user terminal 100 (S67). In this case, the specific claim signature value may be signed by further including authentication confirmation data such as a time stamp and nonce.

In addition, in order to allow the user to approve a specific user-specific identity claim registered by the specific certification authority server 200, a specific user-specific identity claim approval transaction is transmitted to the blockchain network through the specific user terminal 100 ( S68).

In this case, the specific user-specific identity claim approval transaction may include the specific user-specific identity approval data and the third specific user signature value that signs the specific user-specific identity approval data with the specific user master private key, and the specific user-specific identity approval data is It may include identification information for a specific user-specific identity claim and a specific user-specific identity claim.

Then, at least one blockchain node 300 of the blockchain network verifies the third specific user signature value, and when the third specific user signature value is valid, executes a specific user smart contract to execute a specific user specific identity claim approval transaction. Register with the distributed ledger (S69).

And, the at least one blockchain node 300 transmits (S70) a specific user specific identity claim approval transaction ID to a specific user terminal 100 to register a specific user specific identity claim approval transaction in the distributed ledger (S70). The user terminal 100 checks whether the specific user-specific identity claim approval transaction is registered in the distributed ledger using the specific user-specific identity claim approval transaction ID (S71) (S72).

Meanwhile, referring to FIG. 7B, the specific certification authority server 200 transmits a specific user specific identity claim registration request transaction for registering the generated specific user specific identity claim to the proxy server 150 (S62-1), The proxy server 150 transmits a specific user-specific identity claim registration transaction and a second proxy server signature value signed with the proxy server master private key to the blockchain network (S62-2). Then, at least one blockchain node 300 of the blockchain network verifies the second proxy server signature value, and if the second proxy server signature value is valid, registers a specific user-specific identity claim with the distributed ledger (S63). . Then, at least one blockchain node 300 of the blockchain network transmits the transaction ID of the specific user-specific identity claim registration to the proxy server 150 (S64-1), and the proxy server 150 identifies the specific user-specific identity. The claim registration transaction ID is transmitted to the specific certification authority server 200 (S64-2).

Further, the specific user-specific identity claim approval transaction is transmitted to the proxy server 150 through the specific user terminal 100 (S68-1), and the proxy server 150 transmits the specific user-specific identity claim approval transaction and the proxy server. The first proxy server signature value signed with the master private key is transmitted (S68-2). Then, at least one blockchain node 300 in the blockchain network verifies the first proxy server signature value, executes a specific user smart contract when the first proxy server signature value is valid, and distributes a specific user-specific identity claim approval transaction. Register with the ledger (S69). Then, at least one blockchain node 300 of the blockchain network transmits the transaction ID of the specific user-specific identity claim approval to the proxy server 150 (S78-1), and the proxy server 150 identifies the specific user-specific identity. The claim approval transaction ID is transmitted to the specific user terminal 100 (S70-2).

Through this, in FIG. 7A, the specific user terminal 100 and the specific certification authority server 200 have paid transaction blood, but in FIG. 7B, the proxy server 150 displays the user terminal 100 and the specific certification authority server 200. Instead, you can make payments for transactions.

In the above, the operation of registering a new specific user-specific identity claim has been described, but it is possible to update a specific user-specific identity claim registered in the same manner. That is, if there is a previous identity claim corresponding to a specific identity to be registered, if there is a request to register for the same specific identity claim, it is registered in the distributed ledger, and the newly registered specific identity claim is assigned to the specific identity of the specific user. Update to the corresponding claim. At this time, it is possible to confirm a claim corresponding to a specific identity, a preset topic can be used, and when a new claim is registered for the same topic, it can be recognized that it is an update to the user identity claim. However, the present invention is not limited to this, and it is also possible to define and perform functions of each claim, such as a registration claim, an update claim, and a deletion claim.

A method of deleting a specific identity claim in a method of managing user identity using a blockchain network according to an embodiment of the present invention will be described with reference to FIG. 8A.

In the state in which a specific user-specific identity claim is registered by the method as in FIG. 7A, the specific user terminal 100 deletes the specific user-specific identity claim to the blockchain network in order to delete the specific user-specific identity claim according to the user's selection The request transaction is transmitted (S81). At this time, the specific user specific identity claim deletion transaction uses the specific user specific identity deletion claim data using the specific user specific identity claim ID and the first specific user signature value that signs the specific user specific identity deletion claim data with the specific user master private key. It can contain.

Then, at least one blockchain node 300 of the blockchain network verifies the first specific user signature value, and if the first specific user signature value is valid, executes a specific user smart contract to correspond to a specific user specific identity claim ID A specific user-specific identity claim deletion transaction for deleting a specific user-specific identity claim is registered in the distributed ledger (S82).

And, at least one blockchain node 300 of the blockchain network transmits (S83) a specific user specific identity claim deletion transaction ID to the specific user terminal 100, and the specific user terminal 100 is a specific user specific identity It is checked whether a specific user-specific identity claim to be deleted is deleted from the distributed ledger using the transaction deletion transaction ID (S84) (S85).

In addition, referring to FIG. 8B, the specific user terminal 100 transmits a request transaction for deleting a specific user specific identity claim to the proxy server 150 (S81-1), and the proxy server 150 deletes the specific user specific identity claim The request transaction and the proxy server signature value signed with the proxy server master private key are transmitted to the blockchain network (S81-2).

Then, at least one blockchain node 300 of the blockchain network verifies the proxy server signature value (S81-3), and if the proxy server signature value is valid, the first specific included in the transaction for deleting a specific user-specific identity claim After verifying the user signature value, a specific user specific identity claim deletion transaction for deleting a specific user specific identity claim is registered in the distributed ledger (S82).

Then, at least one blockchain node 300 of the blockchain network transmits the transaction ID for deleting a specific user-specific identity claim to the proxy server 150 (S83-1), and the proxy server 150 claims the specific user-specific identity The deleted transaction ID is transmitted to the specific user terminal 100 (S83-2).

Through this, in FIG. 8A, the user terminal 100 has paid transaction blood, but in FIG. 8B, the proxy server 150 may allow the transaction payment to be made on behalf of the user terminal 100.

Another method of deleting a specific identity claim in a method of managing a user identity using a blockchain network according to an embodiment of the present invention will be described with reference to FIG. 9A.

In a state in which a specific user-specific identity claim is registered by the method as in FIG. 7A, the specific certification authority server 200 transmits a transaction for deleting a specific user-specific identity claim to the blockchain network in order to delete the specific user-specific identity claim (S91). At this time, the specific user specific identity claim deletion transaction is signed by a third specific certification authority that signs the specific user specific identity deletion claim data and the specific user specific identity deletion claim data using the specific user specific identity claim ID with the specific certification authority master private key. It can contain values.

Then, at least one blockchain node 300 in the blockchain network verifies the third specific certification authority signature value, and when the third specific certification authority signature value is valid, executes a specific user smart contract to execute a specific user specific identity claim ID Delete a specific user-specific identity claim transaction for deleting a specific user-specific identity claim corresponding to is registered in the distributed ledger.

And, at least one blockchain node 300 of the blockchain network transmits the transaction ID of the specific user specific identity claim deletion to the specific certification authority server 200 (S92), and the specific certification authority server 200 is the specific user The ID of the specific user specific identity deletion claim that is the ID of the specific user specific identity deletion claim registered in the distributed ledger is confirmed by using the specific identity claim deletion transaction ID (S93) (S94).

Thereafter, the specific certification authority server 200 transmits the claim ID for deleting the specific user-specific identity to the specific user terminal 100 (S95).

Then, the specific user terminal 100 transmits the transaction for deleting a specific user-specific identity claim to the blockchain network (S96). At this time, the specific user-specific identity claim deletion approval transaction may include the specific user-specific identity claim deletion approval data and the second specific user signature value signed with the specific user master private key, and the specific user-specific identity claim deletion approval data may be specified. The user-specific identity deletion claim ID and approval information for a specific user-specific identity deletion claim may be included.

And, at least one blockchain node 300 of the blockchain network verifies the second specific user signature value, and when the second specific user signature value is valid, executes a specific user smart contract to claim a specific user specific identity to be deleted. Deleted from this distributed ledger (S97).

Thereafter, at least one blockchain node 300 of the blockchain network transmits (S98) a specific user specific identity claim deletion transaction ID to the specific user terminal 100, and the specific user terminal 100 specifies a specific user It is checked whether the specific user-specific identity claim to be deleted is deleted from the distributed ledger using the identity claim deletion approval transaction ID (S99) (S100).

In addition, referring to FIG. 9B, the specific certification authority server 200 transmits a request for deleting a specific user-specific identity claim to the proxy server 150 (S91-1), and the proxy server 150 deletes the specific user-specific identity The request transaction and the proxy server signature value signed with the proxy server master private key are transmitted to the blockchain network (S91-2).

Then, at least one blockchain node 300 of the blockchain network verifies the proxy server signature value, and if the proxy server signature value is valid, executes a specific user smart contract to identify a specific user corresponding to a specific user specific identity claim ID A specific user to delete an identity claim Delete a specific identity claim transaction to be registered in the distributed ledger.

Then, at least one blockchain node 300 of the blockchain network transmits the transaction ID for deleting the specific user-specific identity claim to the proxy server 150 (S92-1), and the proxy server 150 claims the specific user-specific identity The deleted transaction ID is transmitted to the specific certification authority server 200 (S92-2).

In addition, the specific user terminal 100 transmits a transaction for deleting a specific user-specific identity to the proxy server 150 (S96-1), and the proxy server 150 transmits a transaction for approval of deletion of a specific user-specific identity claim to the blockchain network To (S96-2).

In addition, at least one blockchain node 300 of the blockchain network transmits the transaction ID for the approval of deleting a specific user-specific identity to the proxy server 150 (S98-1), and the proxy server 150 identifies the specific user The identity claim deletion approval transaction ID is transmitted to the specific user terminal 100 (S98-2).

Through this, in FIG. 9A, the specific user terminal 100 and the specific certification authority server 200 paid transaction blood, but in FIG. 9B, the proxy server 150 displays the user terminal 100 and the specific certification authority server 200. Instead, you can make payments for transactions.

In the case of generating self-claims and identity claims by the method as described above, achievements corresponding to each claim can be provided, such as the subject who generates the claim, the owner of the claim, and the subject who uses the claim, and rewards corresponding to the achievement Can provide At this time, the achievement status and the compensation payment status, etc. can be managed through the blockchain network by a method similar to that described above. That is, each achievement acquired by the subject can be registered in the blockchain network in a manner similar to self-claim, and specific rewards desired for compensation among achievements can be registered and managed in the blockchain network in a manner similar to the identity claim.

A method of authenticating a user using another blockchain network-based user identity according to an embodiment of the present invention will be described with reference to FIGS. 10A and 10B.

First, referring to FIG. 10A, a method of performing sign up using a user identity based on a blockchain network will be described.

Claim smart contracts that allow users to generate claims for their identities are registered in the distributed ledger of the blockchain network, which is composed of multiple blockchain nodes with user smart contracts corresponding to each user, and user smart At least one for each of the user self claims, each of the user identities, including user specific values whose addresses on the distributed ledger for the contracts are managed by the user's identities and which process user identities corresponding to the users respectively. The user identity claims registered by the certification authority and the user addresses corresponding to the user key are registered and managed on the distributed ledger, and the user signs up to the service providing server 500 through the service using terminal 110. When requesting (S111), the service providing server 500 requests user specific information required for signing up to the service using terminal 110 (S112). At this time, the service using terminal 110 may access the service providing server 500 through an application or the web, and the service providing server 500 may callback URL or URL for requesting user specific information. A scheme can be added to provide access information to the service providing server 500.

Then, the service using terminal 110 transmits the user specific information request from the service providing server 500 to the user terminal 100 (S113). At this time, the service use terminal 110 may be the same terminal as the user terminal 100 or a different terminal.

Then, the user terminal 100 checks the user specific information requested from the service providing server 500 through the user identity management app (S114). At this time, the user terminal 100 checks whether the user specific identity claims of the user specific identities corresponding to the requested user specific information are registered on the distributed ledger of the blockchain network.

Then, the user terminal 100 provides the requested user-specific information to the service providing terminal 500 (S115).

In this case, the user terminal 100, when the user-specific identity claims corresponding to the requested user-specific information is registered in the distributed ledger, a specific user ID, a specific user-specific identity corresponding to the specific user-specific information, a specific user-specific Identity claim ID, user self-claim ID, specific user-specific value, specific user-specific identity creation information, specific user-signed value of specific user-signed value with specific user private key, and specific user-specific identity Specific user claim information including a specific claim signature value signed with the private key of the specific certification authority server may be provided to the service providing server 500. At this time, if the requested information is multiple, the specific user claim information includes specific user specific identities, specific user specific identity claim IDs, specific user specific value generation information, and specific claim signature values corresponding to each information. It can contain.

Then, the service provision server 500 checks whether the specific user specific value generation information is valid by referring to the specific user specific value and specific user specific value generation information using the specific user specific value, and the specific user specific value generation information If is valid, it is checked whether a specific user signature value is valid (S116).

In this case, the specific user specific value is a root hash value of the Merkle tree in which hash values for each of the specific user identities are assigned to at least some of the respective leaf nodes, and the generation information of the specific user specific value using the specific user specific identity is It may be merkle tree information for a specific user-specific identity, and in this case, the service providing server 500 generates a comparison target hash value using the merkle tree information and a specific user-specific identity, and compares the comparison hash value and the route. By checking whether the hash values match, it is possible to check whether generation information of a specific user-specific value is valid.

In addition, the service providing server 500 executes a digital signature verification module registered in the distributed ledger to obtain a specific user public key corresponding to a specific user private key by referring to a specific user signature value and a specific user specific value, or a user terminal By transmitting the specific user public key corresponding to the specific user private key to the specific user claim information, the specific user public key may be obtained from the specific user claim information, and the specific user signature may be signed using the specific user public key It is possible to confirm whether a specific user signature value is valid by confirming whether the comparison target data identified from the value matches a specific user specific value.

In addition, when the specific user signature value is valid, the service provision server 500 checks the specific user self-claim and the specific user-specific identity claim registered in the distributed ledger with reference to the specific user self-claim ID and the specific user specific identity claim ID ( S117) (S118), and the specific user claim information is authenticated with reference to the identified specific user self claim and the specific user specific identity claim (S119).

In this case, the service provision server 500 may verify a specific user specific value using a specific user self claim, and verify a specific user specific identity using a specific user specific identity claim.

In addition, the service providing server 500 verifies a specific user-specific value and a specific user-specific identity, and then verifies a certification authority that generates a specific user-specific identity claim, and if the certification authority is determined to be reliable, a specific user-specific identity Can be verified as valid.

Subsequently, when the specific user claim information is authenticated, the service providing server 500 allows sign-up of the specific user (S120 ). For example, the service providing server 500 may register a specific user ID as the user ID of the service providing server 500.

In addition, in order to prevent a replay attack, the user terminal 100 includes a timestamp in the specific user claim information, generates a specific user signature value by signing the specific user specific value and timestamp with a specific user private key, and transmits the generated specific user signature value. , The service providing server 500 may check whether a specific user signature value is valid, and then check the validity of the time stamp.

On the other hand, the user terminal 100 when the user-specific identity claims corresponding to the requested user-specific information is not registered in the distributed ledger, a specific user ID, a specific user-specific identity, a specific user self-claim ID, a specific user By providing the service provision server 500 with specific user claim information including a specific user signature value, a specific user signature value using a specific user specific identity, and a specific user signature value signing a specific user specific value with a specific user private key Can give.

Then, the service providing server 500 checks the user signature value (S116), then checks the specific user self-claim registered in the distributed ledger with reference to the specific user self-claim ID (S117) (S118), and confirms the specific The specific user claim information may be authenticated by referring to the user self-claim, and then, by verifying whether the specific user-specific identity matches the characteristic information of the specific user (S119), sign-up of the specific user may be allowed (S120). . At this time, checking and authenticating whether the specific user-specific identity matches the characteristic information of the specific user may be authenticating the specific user-specific identity in the service providing server 500 itself. For example, if a specific identity is a phone number, normal phone number authentication can be performed to check whether the corresponding phone number matches a specific user's phone number.

In addition, the service providing server 500 may register a specific user-specific identity claim for a specific identity authenticated by the method as in FIG. 7A to the distributed ledger of the blockchain network (S121).

That is, the service provision server 500 refers to the specific user-specific identity that has been authenticated, a service provision server ID corresponding to the service provision server, a specific claim type corresponding to a specific user-specific identity, and a specific user ID and specific claim type A second service provision server that generates a specific user-specific identity claim including the first service provision server signature value signed with the private key of the service provision server 500, and signs the specific user-specific identity claim with the private key of the service provision server A transaction for requesting registration of a specific user-specific identity claim including the signature value is transmitted to the blockchain network. In this case, the specific user-specific identity claim may include authentication verification data such as a time stamp, and the first service provision server signature value may be signed by adding authentication verification data such as a time stamp. Then, when at least one blockchain node 300 of the blockchain network verifies the second service provision server signature value and the second service provision server signature value is valid, a specific user specific contract is executed by executing a specific user smart contract You will be registered in the distributed ledger. In addition, the specific claim signature value signed by the specific user specific identity with the private key of the service providing server may be transmitted to and stored in the user terminal 100.

Next, a method of using a service using a user identity based on a blockchain network will be described with reference to FIG. 10B.

Claim smart contracts that allow users to generate claims for their identities are registered in the distributed ledger of the blockchain network, which is composed of multiple blockchain nodes with user smart contracts corresponding to each user, and user smart At least one for each of the user self claims, each of the user identities, including user specific values whose addresses on the distributed ledger for the contracts are managed by the user's identities and which process user identities corresponding to the users respectively. In the state in which the user identity claims registered by the certification authority and the user addresses corresponding to the user key are registered and managed on the distributed ledger, the user requests a service from the service using terminal 110 to the service providing server 500 If (S131), the service providing server 500 requests a specific user signature value for service provision to the service using terminal 110 (S132). At this time, the service using terminal 110 may access the service providing server 500 through an application or the web, and the service providing server 500 may request a specific user signature value callback URL or By adding a URL scheme, access information to the service providing server 500 may be provided.

Then, the service using terminal 110 transmits a request for a user signature value from the service providing server 500 to the user terminal 100 (S133). At this time, the service use terminal 110 may be the same terminal as the user terminal 100 or a different terminal.

Then, the user terminal 100 generates a specific user signature value through the user identity management app (S134).

At this time, the user terminal 100 checks data corresponding to a specific user signature value request, and may generate a specific user signature value that signs the data with a specific user private key.

In addition, the data may be generated in the service providing server 500, and may be included in specific user signature value request information, data for transaction information, data for information to be verified by the user for service provision, and signature value It may include data on nonce for verification, but is not limited thereto, and may include all data generated by the service providing server 500 in connection with service provision.

In addition to this, the data may be generated by the user terminal 100 in response to information requested from the service providing server 500, data on transaction information required for service use, a specific user identity for logging in, a password, etc. Data, nonce data for use in verifying the signature value, and the like, but is not limited thereto, and may include all data generated by the user terminal 100 in connection with the use of the service.

Thereafter, the user terminal 100 transmits a specific user ID, a specific user address, data, and a specific user signature value to the service providing server 500 (S135).

Then, the service providing server 500 checks whether the specific user signature value is valid (S136), and when the specific user signature value is valid, checks the comparison target user address registered in the distributed ledger of the blockchain network by referring to the specific user ID. (S137) (S138), and check whether a specific user address is valid by referring to the comparison target user address (S139), and then provide the requested service to the service requesting terminal 100 (S140).

At this time, when the data transmitted from the user terminal 100 includes a specific user-specific identity and a specific user-specific identity claim ID, the service provision server 500 refers to the specific user-specific identity claim ID to distribute the ledger of the blockchain network. In order to obtain a specific user-specific identity claim, a specific user-specific identity may be verified by referring to the specific user-specific identity claim.

In addition, the service providing server 500 executes a digital signature verification module registered in the distributed ledger to obtain a specific user public key corresponding to a specific user private key by referring to a specific user signature value and data, or the user terminal 100 A specific user public key can be obtained by adding and transmitting a specific user public key corresponding to the specific user private key, and using the specific user public key, check whether the data to be compared with the comparison data verified from the specific user signature value matches By doing so, it is possible to check whether a specific user signature value is valid.

In addition, the embodiments according to the present invention described above may be implemented in the form of program instructions that can be executed through various computer components to be recorded in a computer-readable recording medium. The computer-readable recording medium may include program instructions, data files, data structures, or the like alone or in combination. The program instructions recorded on the computer-readable recording medium may be specially designed and configured for the present invention or may be known and usable by those skilled in the computer software field. Examples of computer-readable recording media include magnetic media such as hard disks, floppy disks, and magnetic tapes, optical recording media such as CD-ROMs, DVDs, and magneto-optical media such as floptical disks. media), and hardware devices specifically configured to store and execute program instructions such as ROM, RAM, flash memory, and the like. Examples of program instructions include not only machine language codes produced by a compiler, but also high-level language codes executable by a computer using an interpreter or the like. The hardware device may be configured to operate as one or more software modules to perform processing according to the present invention, and vice versa.

In the above, the present invention has been described by specific matters such as specific components and limited embodiments and drawings, but this is provided only to help a more comprehensive understanding of the present invention, and the present invention is not limited to the above embodiments , Those skilled in the art to which the present invention pertains can make various modifications and variations from these descriptions.

Therefore, the spirit of the present invention is not limited to the above-described embodiment, and should not be determined, and all claims that are equally or equivalently modified with the claims as described below belong to the scope of the spirit of the present invention. Would say

100: user terminal,
150: proxy server
200: certification authority server,
300: blockchain node,
500: service providing server

Claims (24)

In the method of managing the identity of the user using the blockchain network,
(a) Claims smart contracts to generate claims for the identities of users and certifying authorities, multiple blockchain nodes with user smart contracts and certifying authority smart contracts respectively corresponding to users and certifying authorities Registered in the distributed ledger of the blockchain network constituted by, the addresses on the distributed ledger for the user smart contracts and the certification authority smart contracts are managed with the IDs of the users and the certification authorities, and the In the state where each user self-claim including user-specific values processed by user identities corresponding to users is registered in the distributed ledger, (i) authentication from a specific user ID and specific user identities from a specific user terminal. Respond to a specific user-specific identity claim registration request for a specific user-specific identity, including a specific user-specific identity for, and at least a first specific user-specific value processing the specific user identities, or (ii) from the specific user terminal In response to the specific user specific identity claim registration request obtained from the specific user terminal by transmitting the specific user specific identity corresponding to a specific user to the specific user terminal in response to the identity claim registration request of When a confirmation request for a specific user self-claim ID corresponding to a specific user self-claim is obtained, at least one blockchain node among the plurality of blockchain nodes executes a specific user smart contract and is registered in the distributed ledger By sending the specific user self claim ID corresponding to a specific user self claim to the specific certification authority server, the specific certification authority server uses the specific user self claim ID to register the specific user self claim registered in the distributed ledger. Confirming to obtain a second specific user specific value included in the specific user self claim; And
(b) a specific user-specific identity claim from the specific certification authority server-the specific user-specific identity claim is generated by the specific certification authority server, and included in the specific user-specific identity claim registration request from the specific user terminal In a state where the first specific user specific value and the second specific user specific value included in the specific user self-claim of the distributed ledger match, the specific certification authority server verifies the specific user specific identity, and then the specific The first specific signature of the specific certification authority ID corresponding to the certification authority server, the specific claim type corresponding to the specific user specific identity, and the specific user ID and the specific claim type with the specific certification authority private key of the specific certification authority server. Generated by including a certification authority signature value-and a specific user-specific identity claim registration request transaction including the second specific certification authority signature value signed by the specific certification authority private key and the specific user-specific identity claim is obtained. When at least one blockchain node verifies the signature value of the second specific certification authority and the second specific certification authority signature value is valid, the specific user specific identity claim is executed to the distributed ledger by executing the specific user smart contract. The specific certification authority by sending a specific user-specific identity claim registration transaction ID corresponding to a specific user-specific identity claim registration transaction to be registered and to register the specific user-specific identity claim to the distributed ledger, to the specific certification authority server A server obtains a specific user-specific identity claim ID corresponding to the specific user-specific identity claim registered in the distributed ledger by using the specific user-specific identity claim transaction ID, and at least authenticates the specific user-specific identity The specific claims signature value signed with the institution private key, Transmitting the specific user-specific identity claim ID to the specific user terminal;
How to include. According to claim 1,
(c) a first specific user signature that signs the specific user specific identity deletion claim data and the specific user specific identity deletion claim data with the specific user private key of the specific user using the specific user specific identity claim ID from the specific user terminal When a request for deleting a specific user-specific identity claim including a value is obtained, the at least one blockchain node verifies the first specific user signature value, and if the first specific user signature value is valid, the specific user smart Executing a contract so that a transaction for deleting a specific user-specific identity claim for deleting the specific user-specific identity claim corresponding to the specific user-specific identity claim is registered in the distributed ledger;
Method further comprising a. According to claim 1,
(d) a third specific certification authority signing the specific user specific identity deletion claim data and the specific user specific identity deletion claim data with the specific certification authority private key using the specific user specific identity claim ID from the specific certification authority server When a request for deleting a specific user-specific identity claim including a value is obtained, the at least one blockchain node verifies the third specific certification authority signature value, and if the third specific certification authority signature value is valid, the specific Executing a user smart contract so that a transaction for deleting a specific user-specific identity claim for deleting the specific user-specific identity claim corresponding to the specific user-specific identity claim is registered in the distributed ledger;
Method further comprising a. According to claim 3,
The at least one blockchain node transmits a specific user specific identity deletion claim ID which is an ID of the specific user specific identity deletion claim registered in the distributed ledger to the specific certification authority server in response to a user specific identity claim deletion transaction. , To allow the specific certification authority server to transmit the ID of the specific user-specific identity deletion claim to the specific user terminal, and approve the specific user-specific identity deletion claim ID and the specific user-specific identity deletion claim from the specific user terminal A specific user-specific identity claim deletion approval transaction that includes a specific user-specific identity deletion approval data including information and a second specific user signature value that signs the specific user-specific identity claim deletion approval data with the specific user private key of the specific user When it is obtained, if the second specific user signature value is valid by verifying the second specific user signature value, the specific user specific identity claim is deleted from the distributed ledger by executing the specific user smart contract. How to. According to claim 1,
(e) The specific user-specific identity claim ID and the specific user from the specific user terminal by referring to the specific user-specific identity claim ID corresponding to the specific user-specific identity claim registered in the distributed ledger from the specific certification authority server. A specific user-specific identity claim including a specific user-specific identity approval data including approval information for a specific identity claim, and a third specific user signature value signing the specific user-specific identity approval data with the specific user private key of the specific user. When an approval transaction is obtained, the at least one blockchain node verifies the third specific user signature value, and if the third specific user signature value is valid, executes the specific user smart contract to claim the specific user specific identity Allowing an approval transaction to be registered in the distributed ledger;
Method further comprising a. The method of claim 5,
In step (e),
The at least one blockchain node obtains the specific user-specific identity claim approval transaction from a proxy server, and the specific user-specific identity claim approval transaction and the specific user-specific identity claim approval transaction are obtained from the proxy server. A method of obtaining a first proxy server signature value signed with a proxy server private key, and verifying the first proxy server signature value to execute the specific user smart contract when the first proxy server signature value is valid. According to claim 1,
In step (a),
The at least one blockchain node transmits a list of the certification authorities registered in the distributed ledger to the specific user terminal in response to a request for a list of the certification authorities from the specific user terminal, so that the specific user terminal authenticates the A method characterized in that it is possible to select a specific certification authority to perform authentication for the specific user-specific identity among institutions. According to claim 1,
The specific user specific value registered in the specific user self-claim is a root hash value of the Merkle tree in which hash values for each of the specific user identities are assigned to at least some of the respective leaf nodes,
In step (a),
The request for registering the specific user-specific identity claim includes the information of the Merkle tree,
In step (b),
The specific certification authority server generates a root hash value using the information of the Merkle tree and a hash value of the specific user-specific identity, and the generated root hash value and the comparison target root hash value included in the specific user self-claim A method characterized in that it matches. According to claim 1,
In step (b),
The at least one blockchain node executes a digital signature verification module registered in the distributed ledger, and refers to the second specific certification authority signature value and the specific user-specific identity claim to correspond to the specific certification authority private key. The second specific certification authority is obtained by confirming whether the comparison target data identified from the second specific certification authority signature value and the specific user-specific identity claim match by using the specific certification authority public key. And verifying that the signature value is valid. According to claim 1,
In step (b),
The specific user specific identity claim registration request transaction includes a specific certification authority public key corresponding to the specific certification authority private key,
The at least one blockchain node uses the specific certification authority public key to confirm whether the comparison target data identified from the second specific certification authority signature value and the specific user-specific identity claim match. And verifying that the signature value is valid. According to claim 1,
In step (b),
The at least one blockchain node may obtain (i) the specific user-specific identity claim registration request transaction from a proxy server, but the specific user-specific identity claim registration transaction and the specific user-specific identity claim registration request from the proxy server Acquire a second proxy server signature value that signs a transaction with the proxy server private key of the proxy server, and verify the second proxy server signature value to execute the specific user smart contract when the second proxy server signature value is valid, , (ii) sending the specific user-specific identity claim registration transaction ID to the proxy server, so that the proxy server transmits the specific user-specific identity claim registration transaction ID to the specific certification authority server. According to claim 1,
In step (a),
The request to register the specific user-specific identity claim further includes a time stamp,
In step (b),
The specific user-specific identity claim further includes the time stamp,
And wherein the first specific certification authority signature value and the specific claim signature value further include the time stamp. In the blockchain node of the blockchain network that manages the user's identity using the blockchain network,
A memory in which instructions for managing user identities are stored; And
A processor performing an operation of managing the user identity according to the instructions stored in the memory;
Including,
The processor,
(i) Claims smart contracts to generate claims for the identities of users and certifying authorities, multiple blockchain nodes with user smart contracts and certifying authority smart contracts, respectively, corresponding to users and certifying agents Registered in the distributed ledger of the blockchain network constituted by, the addresses on the distributed ledger for the user smart contracts and the certification authority smart contracts are managed with the IDs of the users and the certification authorities, and the In the state where each user self-claim including user-specific values processed by user identities corresponding to users is registered in the distributed ledger, (i-1) a specific user ID from a specific user terminal, specific user identities Respond to a specific user specific identity claim registration request for a specific user specific identity including a specific user specific identity for authentication, and at least a first specific user specific value processing the specific user identities, or (i-2) In response to a request for registering an identity claim from a specific user terminal, the specific user-specific identity corresponding to a specific user is transmitted to the specific user terminal to be specified in response to the specific user-specific identity claim registration request obtained from the specific user terminal When a request for confirmation of a specific user self-claim ID corresponding to a specific user self-claim is obtained from a certification authority server, the specific user self-claim corresponding to the specific user self-claim registered in the distributed ledger is executed by executing a specific user smart contract By sending the ID to the specific certification authority server, the specific certification authority server confirms the specific user self-claim registered in the distributed ledger using the specific user self-claim ID, and the second included in the specific user self-claim A process for obtaining a specific user specific value, and (ii) specific user identification from the specific certification authority server Identity claim-The specific user specific identity claim is generated by the specific certification authority server, and includes the first specific user specific value and the distributed ledger included in the specific user specific identity claim registration request from the specific user terminal. In the state in which the second specific user specific value included in the specific user self-claim matches, the specific certification authority server verifies the specific user specific identity, and then the specific certification authority ID corresponding to the specific certification authority server, at least It is generated by including a specific claim type corresponding to the specific user specific identity, and a first specific certification authority signature value signing the specific user ID and the specific claim type with a specific certification authority private key of the specific certification authority server − And a specific user-specific identity claim registration request transaction including the second specific certification authority signature value signed with the specific certification authority private key, and verifying the second specific certification authority signature value. If the second specific certification authority signature value is valid, the specific user executes the specific user smart contract so that the specific user specific identity claim is registered in the distributed ledger, and the specific user specific identity claim is registered in the distributed ledger By sending a specific user specific identity claim registration transaction ID corresponding to a specific identity claim registration transaction to the specific certification authority server, the specific certification authority server registers with the distributed ledger using the specific user specific identity claim registration transaction ID Obtain a specific user-specific identity claim ID corresponding to the specific user-specific identity claim, and at least the specific user-signed identity signed by the specific certification authority private key and the specific user-signed identity value and the specific user-specific identity claim ID Even when transmitted to the user terminal Blockchain node characterized by performing a locking process. The method of claim 13,
The process is
(iii) a first specific user signature that has signed the specific user specific identity deletion claim data and the specific user specific identity deletion claim data with the specific user private key of the specific user using the specific user specific identity claim ID from the specific user terminal When a request for deleting a specific user specific identity claim including a value is obtained, if the first specific user signature value is valid by validating the first specific user signature value, executing the specific user smart contract to execute the specific user specific identity Blockchain node further comprising the process of deleting a specific user-specific identity claim transaction for deleting the specific user-specific identity claim corresponding to the claim ID in the distributed ledger. The method of claim 13,
The processor,
(iv) a third specific certification authority signing the specific user specific identity deletion claim data and the specific user specific identity deletion claim data with the specific certification authority private key using the specific user specific identity claim ID from the specific certification authority server When a request for deleting a specific user specific identity claim including a value is obtained, if the third specific certification authority signature value is valid by verifying the third specific certification authority signature value, the specific user is executed by executing the specific user smart contract A blockchain node, further comprising a process of deleting a specific user-specific identity claim for deleting the specific user-specific identity claim corresponding to a specific identity claim ID in the distributed ledger. The method of claim 15,
In response to the user specific identity claim deletion transaction, the process transmits the specific user specific identity deletion claim ID, which is the ID of the specific user specific identity deletion claim registered in the distributed ledger, to the specific certification authority server, so that the specific certification authority The server is configured to transmit the specific user specific identity deletion claim ID to the specific user terminal, and includes the specific user specific identity deletion claim ID and approval information for the specific user specific identity deletion claim from the specific user terminal. When a specific user specific identity claim deletion approval transaction is obtained, which includes a user specific identity deletion approval data and a second specific user signature value that signs the specific user specific identity claim deletion approval data with the specific user private key of the specific user, the transaction A blockchain node characterized by verifying a second specific user signature value to execute the specific user smart contract so that the specific user specific identity claim is deleted from the distributed ledger when the second specific user signature value is valid. The method of claim 13,
The processor,
(v) the specific user-specific identity claim ID and the specific user from the specific user terminal by referring to the specific user-specific identity claim ID corresponding to the specific user-specific identity claim registered in the distributed ledger from the specific certification authority server A specific user-specific identity claim including a specific user-specific identity approval data including approval information for a specific identity claim, and a third specific user signature value signing the specific user-specific identity approval data with the specific user private key of the specific user. When an approval transaction is obtained, if the third specific user signature value is valid by validating the third specific user signature value, execute the specific user smart contract so that the specific user specific identity claim approval transaction is registered in the distributed ledger. Blockchain node characterized by further performing the process. The method of claim 17,
The processor,
In the (v) process, the specific user-specific identity claim approval transaction is obtained from a proxy server, but the specific user-specific identity claim approval transaction and the specific user-specific identity claim approval transaction are obtained from the proxy server. A blockchain node characterized by acquiring a first proxy server signature value signed with a private key, and executing the specific user smart contract when the first proxy server signature value is valid by verifying the first proxy server signature value. The method of claim 13,
The processor,
In the process (i), the specific user terminal transmits the list of the certification authorities registered in the distributed ledger to the specific user terminal in response to a request for the list of the certification authorities from the specific user terminal, so that the specific user terminal is the authentication authorities. Among them, a blockchain node characterized by allowing a specific certification authority to perform authentication for the specific user-specific identity. The method of claim 13,
The specific user specific value registered in the specific user self-claim is a root hash value of the Merkle tree in which hash values for each of the specific user identities are assigned to at least some of the respective leaf nodes,
In the (i) process,
The request for registering the specific user-specific identity claim includes the information of the Merkle tree,
In the above (ii) process,
The specific certification authority server generates a root hash value using the information of the Merkle tree and a hash value of the specific user-specific identity, and the generated root hash value and the comparison target root hash value included in the specific user self-claim Blockchain node, characterized in that it matches. The method of claim 13,
The processor,
In the process (ii), the digital signature verification module registered in the distributed ledger is executed to refer to the second specific certification authority signature value and the specific user-specific identity claim, and the specific certification authority corresponding to the specific certification authority private key. The second specific certification authority signature value is obtained by confirming whether the comparison target data identified from the second specific certification authority signature value and the specific user-specific identity claim match by using the specific certification authority public key. Blockchain node characterized by verifying that this is valid. The method of claim 13,
The processor,
In the above (ii) process,
The specific user specific identity claim registration request transaction includes a specific certification authority public key corresponding to the specific certification authority private key,
Verifying that the second specific certification authority signature value is valid by confirming whether the comparison target data identified from the second specific certification authority signature value and the specific user-specific identity claim match using the specific certification authority public key Blockchain node. The method of claim 13,
The processor,
In the process (ii), (ii-1) obtaining the specific user specific identity claim registration transaction from a proxy server, wherein the specific user specific identity claim registration transaction and the specific user specific identity claim registration request from the proxy server Acquire a second proxy server signature value that signs a transaction with the proxy server private key of the proxy server, and verify the second proxy server signature value to execute the specific user smart contract when the second proxy server signature value is valid, , (ii-2) A block characterized in that the proxy server transmits the specific user specific identity claim registration transaction ID to the specific certification authority server by sending the specific user specific identity claim registration transaction ID to the proxy server. Chain node. The method of claim 13,
In the (i) process,
The request to register the specific user-specific identity claim further includes a time stamp,
In step (ii),
The specific user-specific identity claim further includes the time stamp,
The first specific certification authority signature value and the particular claim signature value are further signed by including the time stamp, a blockchain node.

Images