US2021217007A1PendingUtilityA1

Distributed ledger for encrypted digital identity

Assignee: DISH NETWORK LLCPriority: Oct 12, 2018Filed: Mar 30, 2021Published: Jul 15, 2021
Est. expiryOct 12, 2038(~12.2 yrs left)· nominal 20-yr term from priority
Inventors:Anand Menon
H04L 9/50G06Q 20/4014G06Q 20/3829G06Q 20/3827H04L 9/3239H04L 63/08H04W 12/40H04W 12/06H04L 9/0643G06Q 20/409G06Q 20/02H04L 9/0825H04L 9/3236H04L 9/3297
56
PatentIndex Score
0
Cited by
0
References
0
Claims

Abstract

The disclosed technique includes identity verification implanted via a blockchain. An identity system utilizes a key library to store private keys and a smart contract functionality to facilitate verification with third-party users. The identity system generates a public key based on the private key where the public key is stored on a blockchain. The public key stored on the blockchain can be retrieved by a third-party user via the smart contract functionality to authenticate a user on the blockchain.

Claims

exact text as granted — not AI-modified
What is claimed is: 
     
         1 . A method comprising:
 associating private keys with users of an identity system, the private keys being stored in a key library of the identity system;   receiving, by a third-party user, a request to register a mobile device;   in response to the registration request, initiating a blockchain transaction including a public key for an identity system user associated with the mobile device; and   implementing a smart contract on the blockchain to enable the third-party user to authenticate the identity system user.   
     
     
         2 . The method of  claim 1 , further comprising:
 identifying the identity system user from among the users of the identity system associated with the mobile device based on mobile device data received along with the registration request.   
     
     
         3 . The method of  claim 1 , further comprising:
 generating the public key for the mobile device based on a private key in the key library, the private key being associated with the identity system user.   
     
     
         4 . The method of  claim 1 , further comprising:
 receiving a cryptographic one-way hash of a mobile identity key from the mobile device;   in response to receiving the cryptographic one-way hash of the mobile identity key, retrieving the private key associated with the identity system user from the key library;   performing a cryptographic one-way hash on the private key; and   determining if a threshold correspondence exists between the cryptographic hash of the private key and the cryptographic hash of the mobile identity key.   
     
     
         5 . The method of  claim 4 , wherein upon determining that the threshold correspondence exists, verifying a user of the mobile device as the identity system user. 
     
     
         6 . The method of  claim 4 , wherein upon determining that the cryptographic hash of the private key and the cryptographic hash of the mobile identity key lack the threshold correspondence, declining to verify a user of the mobile device as the identity system user. 
     
     
         7 . The method of  claim 4 , further comprising:
 transmitting the verification results to the third-party user upon implementing the smart contract.   
     
     
         8 . The method of  claim 1 , wherein the third-party user is a cellular network provider. 
     
     
         9 . An identity system, comprising:
 a distributed computing platform;   a key library comprising associations between private keys and users of the identity system; and   a processor configured to:
 receive a request to register a mobile device by a third-party user; 
 in response to the registration request, initiate a blockchain transaction including a public key for an identity system user associated with the mobile device; and 
 implement a smart contract on the blockchain to enable the third-party user to authenticate the identity system user. 
   
     
     
         10 . The identity system of  claim 9 , wherein the processor is further configured to:
 identify the identity system user from among the users of the identity system associated with the mobile device based on mobile device data received along with the registration request.   
     
     
         11 . The identity system of  claim 9 , wherein the processor is further configured to:
 generate the public key for the mobile device based on a private key in the key library, the private key being associated with the identity system user.   
     
     
         12 . The identity system of  claim 9 , wherein the processor is further configured to:
 receive a cryptographic one-way hash of a mobile identity key from the mobile device;   in response to receiving the cryptographic one-way hash of the mobile identity key, retrieve the private key associated with the identity system user from the key library;   perform a cryptographic one-way hash on the private key; and   determine if a threshold correspondence exists between the cryptographic hash of the private key and the cryptographic hash of the mobile identity key.   
     
     
         13 . The identify system of  claim 12 , wherein upon determining that the threshold correspondence exists, verifying a user of the mobile device as the identity system user, and wherein upon determining that the cryptographic hash of the private key and the cryptographic hash of the mobile identity key lack the threshold correspondence, declining to verify a user of the mobile device as the identity system user. 
     
     
         14 . The identify system of  claim 12 , wherein the processor is further configured to:
 transmit the verification results to the third-party user upon implementing the smart contract.   
     
     
         15 . An method for authenticating a user, comprising:
 providing an identity system comprising a distributed computing platform and a key library, wherein the key library comprises associations between private keys and users of the identity system;   receiving, by a third-party user, a request to register a mobile device;   in response to the registration request, performing the following:
 identifying the user from among the identity system users associated with the mobile device; 
 generating a public key for the mobile device based on a private key in the key library, the private key being associated with the identified identity system user; and 
 initiating a blockchain transaction including the public key for the identified identity system user; and 
   implementing a smart contract on the blockchain to enable the third-party user to authenticate the identified identity system user.   
     
     
         16 . The method of  claim 15 , wherein the identified identity system user is identified based on mobile device data received along with the registration request. 
     
     
         17 . The method of  claim 15 , further comprising:
 receiving a cryptographic one-way hash of a mobile identity key from the mobile device;   in response to receiving the cryptographic one-way hash of the mobile identity key, retrieving the private key associated with the identity system user from the key library;   performing a cryptographic one-way hash on the private key; and   determining if a threshold correspondence exists between the cryptographic hash of the private key and the cryptographic hash of the mobile identity key.   
     
     
         18 . The method of  claim 17 , wherein upon determining that the threshold correspondence exists, verifying a user of the mobile device as the identity system user. 
     
     
         19 . The method of  claim 17 , wherein upon determining that the cryptographic hash of the private key and the cryptographic hash of the mobile identity key lack the threshold correspondence, declining to verify a user of the mobile device as the identity system user. 
     
     
         20 . The method of  claim 17 , further comprising:
 transmitting the verification results to the third-party user upon implementing the smart contract.

Join the waitlist — get patent alerts

Track US2021217007A1 — get alerts on status changes and closely related new filings.

We store only your email — no account needed. See our privacy policy.