IP Library Granted Patent US 11,514,440
Granted Patent B2
US 11,514,440 · App. 15/487,530 · Granted Nov 29, 2022

Method for issuing authentication information and blockchain-based server using the same

Inventors: Joo Han Song (Gyeonggi-do, KR); Jay Wu Hong (Seoul, KR); Joon Sun Uhr (Gyeonggi-do, KR)
Assignee: COINPLUG, INC.
G06Q20/3829G06Q20/065G06Q20/3823G06Q20/3827
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 11,514,440
App. No.
15/487,530
Granted
Nov 29, 2022
Kind
B2
Abstract

A method for issuing authentication information is provided. The method includes steps of: (a) a managing server, if identification information of a specific user is acquired from a user device in response to a request for issuing the authentication information and the identification information is determined to be registered, creating a transaction whose output includes: (i) the specific user's public key and (ii) a hash value of the identification information or its processed value to thereby record or support other device to record it on a blockchain; and (b) the managing server acquiring a transaction ID representing location information of the transaction recorded on the blockchain.

Claims (40)

1. A method for issuing authentication information, comprising steps of:

generating a notifying signal from a requesting server and sending the notifying signal from the requesting server to a user device for the user device to generate a public key and a private key for the user device;

in response to receiving the notifying signal, the user device blocking a network connection on the user device while generating the public key and the private key;

after generating the public key for the user device, and reconnecting the user device to the network, providing the public key to a managing server;

acquiring, by the managing server, identification information of the specific user from the user device in response to a request for issuing the authentication information;

determining, by the managing server, that the identification information is registered;

creating, by the managing server, a transaction with an output including: (i) the specific user's public key, (ii) a hash value of the identification information or its processed value, and (iii) information on a cost deposit against revocation with a certain amount required to revoke the authentication information;

recording the transaction on a blockchain; and

acquiring, by the managing server, a transaction ID representing location information of the transaction recorded on the blockchain.

2. The method of claim 1 , wherein the recording on the blockchain includes recording as part of the transaction a previous transaction ID for bitcoin payment used to identify a location where bitcoins to be used among bitcoins held by the specific user are stored through previous transaction information for the bitcoin payment, information on an authority of the specific user to use bitcoins, a public key to determine a validity of the authority to use bitcoins, user verification hash information, and OP_RETURN information that it is not a bitcoin transaction but a meta transaction for recording information.

3. The method of claim 2 , wherein the recording on the blockchain includes recording as part of the transaction information on a cost of registering the specific user's public key and the user verification hash information necessary to use the authentication information.

4. The method of claim 2 , wherein the recording on the blockchain includes recording as part of the transaction information on a bitcoin address of a cost deposit against revocation for transfer thereof to a designated bitcoin address and information on the transfer of the cost deposit against revocation which includes an amount thereof.

5. The method of claim 1 further comprising: (i) hashing, by the requesting server, personal information of the user device to produce user identification hash information,

(ii) creating, by the requesting server, a REQ signal that requests the managing server to create the transaction by using the user identification hash information, the specific user's public key, and the specific user's identification information, and

(iii) transmitting, by the requesting server, the REQ signal to the managing server.

6. The method of claim 5 , further comprising:

retrieving the personal information for issuing the authentication information from a database including user identification information, and creating at the requesting server the notifying signal for generation of the specific user's public and private keys.

7. The method of claim 1 , further comprising: the user device encrypting the generated private key based on a password entered and an image selected by the specific user and storing the encrypted private key.

8. The method of claim 1 , wherein the acquiring identification information by the managing server includes acquiring at least some of information on the specific user's name, birth date, phone number and email address.

9. A system for supporting issuance of authentication information, comprising:

a registration server configured to generate and send a notifying signal to a user device over a network that requests the user device to generate a public key and a private key;

the user device, the user device being connected via the network to a managing server and the registration server, the user device being configured to

receive the notifying signal, and in response to receipt of the notifying signal block a network connection to the network and generate the public key and the private key while the network connection remains blocked, and

after the public key is generated, reestablish the network connection and send the public key to the managing server; and

the managing server including a processor configured to

acquire identification information of a specific user from the user device in response to a request for issuing the authentication information, and under a condition the processor determines that the identification information is registered, the processor is further configured to create a transaction with an output including: (i) the specific user's public key (ii) a hash value of the identification information or its processed value to thereby record or support other device to record it on a blockchain, and (iii) information on a certain amount of a cost deposit against revocation required to revoke the authentication information,

record the transaction on a blockchain, and

acquire a transaction ID representing location information of the transaction recorded on the blockchain.

10. The system of claim 9 , wherein the transaction includes: information on a previous transaction ID for bitcoin payment used to identify a location where bitcoins to be used among bitcoins held by the specific user are stored through previous transaction information for the bitcoin payment, information on an authority of the specific user to use bitcoins, information on a public key to determine a validity of the authority to use bitcoins, user verification hash information, and OP_RETURN information that it is not a bitcoin transaction but a meta transaction for recording information.

11. The system of claim 10 , wherein the transaction further includes: information on a cost of registering the specific user's public key and the user verification hash information necessary to use the authentication information.

12. The system of claim 10 , wherein the transaction further includes: information on a bitcoin address of a cost deposit against revocation for transfer thereof to a designated bitcoin address and information on the transfer of the cost deposit against revocation which includes an amount thereof.

13. The system of claim 9 , wherein the requesting server is configured to receive the specific user's public key and personal information for the issuance of the authentication information from the user device, and the requesting server is further configured to

(i) hash the personal information to acquire user identification hash information,

(ii) create a REQ signal that requests the managing server to create the transaction by using the user identification hash information, the specific user's public key, and the specific user's identification information, and

(iii) transmit the REQ signal to the managing server; and

the processor of the managing server is further configured to create and record the transaction.

14. The system of claim 13 , wherein, requesting server is further configured to

retrieve from a database the personal information including user identification information, and create the notifying signal for generation of the specific user's public and private keys and transmit the notifying signal to the user device.

15. The system of claim 9 , wherein the user device encrypts the generated private key based on a password entered and an image selected by the specific user and stores the encrypted private key.

16. The system of claim 9 , wherein the identification information includes at least some of information on the specific user's name, birth date, phone number and email address.

Assignments (2)
CHANGE OF NAME Recorded Nov 20, 2023
From: COINPLUG, INC.
To: CPLABS, INC.
Reel/Frame 065628/0785 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Apr 14, 2017
From: SONG, JOO HAN; HONG, JAY WU; UHR, JOON SUN
To: COINPLUG, INC.
Reel/Frame 042006/0995 →
Priority Claims (1)
KR 10-2016-0059850 · May 16, 2016 · national
Continuity (1)
Related Publication 20170330179A1 · Nov 16, 2017