US20220337419A1 - Systems, apparatus and methods for secure electrical communication of biometric personal identification information to validate the identity of an individual - Google Patents
Systems, apparatus and methods for secure electrical communication of biometric personal identification information to validate the identity of an individual Download PDFInfo
- Publication number
- US20220337419A1 US20220337419A1 US17/691,597 US202217691597A US2022337419A1 US 20220337419 A1 US20220337419 A1 US 20220337419A1 US 202217691597 A US202217691597 A US 202217691597A US 2022337419 A1 US2022337419 A1 US 2022337419A1
- Authority
- US
- United States
- Prior art keywords
- biometric
- data
- signed
- hash value
- compute device
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Abandoned
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/38—Payment protocols; Details thereof
- G06Q20/40—Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
- G06Q20/401—Transaction verification
- G06Q20/4014—Identity check for transactions
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/30—Authentication, i.e. establishing the identity or authorisation of security principals
- G06F21/31—User authentication
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/30—Authentication, i.e. establishing the identity or authorisation of security principals
- G06F21/31—User authentication
- G06F21/32—User authentication using biometric data, e.g. fingerprints, iris scans or voiceprints
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/30—Authentication, i.e. establishing the identity or authorisation of security principals
- G06F21/31—User authentication
- G06F21/33—User authentication using certificates
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/30—Authentication, i.e. establishing the identity or authorisation of security principals
- G06F21/31—User authentication
- G06F21/34—User authentication involving the use of external additional devices, e.g. dongles or smart cards
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/60—Protecting data
- G06F21/64—Protecting data integrity, e.g. using checksums, certificates or signatures
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/60—Protecting data
- G06F21/64—Protecting data integrity, e.g. using checksums, certificates or signatures
- G06F21/645—Protecting data integrity, e.g. using checksums, certificates or signatures using a third party
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06K—GRAPHICAL DATA READING; PRESENTATION OF DATA; RECORD CARRIERS; HANDLING RECORD CARRIERS
- G06K19/00—Record carriers for use with machines and with at least a part designed to carry digital markings
- G06K19/06—Record carriers for use with machines and with at least a part designed to carry digital markings characterised by the kind of the digital marking, e.g. shape, nature, code
- G06K19/06009—Record carriers for use with machines and with at least a part designed to carry digital markings characterised by the kind of the digital marking, e.g. shape, nature, code with optically detectable marking
- G06K19/06018—Record carriers for use with machines and with at least a part designed to carry digital markings characterised by the kind of the digital marking, e.g. shape, nature, code with optically detectable marking one-dimensional coding
- G06K19/06028—Record carriers for use with machines and with at least a part designed to carry digital markings characterised by the kind of the digital marking, e.g. shape, nature, code with optically detectable marking one-dimensional coding using bar codes
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06K—GRAPHICAL DATA READING; PRESENTATION OF DATA; RECORD CARRIERS; HANDLING RECORD CARRIERS
- G06K19/00—Record carriers for use with machines and with at least a part designed to carry digital markings
- G06K19/06—Record carriers for use with machines and with at least a part designed to carry digital markings characterised by the kind of the digital marking, e.g. shape, nature, code
- G06K19/06009—Record carriers for use with machines and with at least a part designed to carry digital markings characterised by the kind of the digital marking, e.g. shape, nature, code with optically detectable marking
- G06K19/06037—Record carriers for use with machines and with at least a part designed to carry digital markings characterised by the kind of the digital marking, e.g. shape, nature, code with optically detectable marking multi-dimensional coding
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/02—Payment architectures, schemes or protocols involving a neutral party, e.g. certification authority, notary or trusted third party [TTP]
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/04—Payment circuits
- G06Q20/06—Private payment circuits, e.g. involving electronic currency used among participants of a common payment scheme
- G06Q20/065—Private payment circuits, e.g. involving electronic currency used among participants of a common payment scheme using e-cash
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/30—Payment architectures, schemes or protocols characterised by the use of specific devices or networks
- G06Q20/32—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using wireless devices
- G06Q20/327—Short range or proximity payments by means of M-devices
- G06Q20/3276—Short range or proximity payments by means of M-devices using a pictured code, e.g. barcode or QR-code, being read by the M-device
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/38—Payment protocols; Details thereof
- G06Q20/382—Payment protocols; Details thereof insuring higher security of transaction
- G06Q20/3825—Use of electronic signatures
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/38—Payment protocols; Details thereof
- G06Q20/382—Payment protocols; Details thereof insuring higher security of transaction
- G06Q20/3827—Use of message hashing
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
- H04L63/0861—Network architectures or network communication protocols for network security for authentication of entities using biometrical features, e.g. fingerprint, retina-scan
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
- H04L9/06—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols the encryption apparatus using shift registers or memories for block-wise or stream coding, e.g. DES systems or RC4; Hash functions; Pseudorandom sequence generators
- H04L9/0618—Block ciphers, i.e. encrypting groups of characters of a plain text message using fixed encryption transformation
- H04L9/0637—Modes of operation, e.g. cipher block chaining [CBC], electronic codebook [ECB] or Galois/counter mode [GCM]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
- H04L9/06—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols the encryption apparatus using shift registers or memories for block-wise or stream coding, e.g. DES systems or RC4; Hash functions; Pseudorandom sequence generators
- H04L9/0643—Hash functions, e.g. MD5, SHA, HMAC or f9 MAC
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
- H04L9/14—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols using a plurality of keys or algorithms
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
- H04L9/30—Public key, i.e. encryption algorithm being computationally infeasible to invert or user's encryption keys not requiring secrecy
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
- H04L9/30—Public key, i.e. encryption algorithm being computationally infeasible to invert or user's encryption keys not requiring secrecy
- H04L9/3006—Public key, i.e. encryption algorithm being computationally infeasible to invert or user's encryption keys not requiring secrecy underlying computational problems or public-key parameters
- H04L9/302—Public key, i.e. encryption algorithm being computationally infeasible to invert or user's encryption keys not requiring secrecy underlying computational problems or public-key parameters involving the integer factorization problem, e.g. RSA or quadratic sieve [QS] schemes
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
- H04L9/30—Public key, i.e. encryption algorithm being computationally infeasible to invert or user's encryption keys not requiring secrecy
- H04L9/3066—Public key, i.e. encryption algorithm being computationally infeasible to invert or user's encryption keys not requiring secrecy involving algebraic varieties, e.g. elliptic or hyper-elliptic curves
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
- H04L9/32—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials
- H04L9/3226—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials using a predetermined code, e.g. password, passphrase or PIN
- H04L9/3231—Biological data, e.g. fingerprint, voice or retina
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
- H04L9/32—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials
- H04L9/3236—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials using cryptographic hash functions
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
- H04L9/32—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials
- H04L9/3236—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials using cryptographic hash functions
- H04L9/3239—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials using cryptographic hash functions involving non-keyed hash functions, e.g. modification detection codes [MDCs], MD5, SHA or RIPEMD
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
- H04L9/32—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials
- H04L9/3247—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials involving digital signatures
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
- H04L9/32—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials
- H04L9/3247—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials involving digital signatures
- H04L9/3249—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials involving digital signatures using RSA or related signature schemes, e.g. Rabin scheme
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
- H04L9/32—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials
- H04L9/3247—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials involving digital signatures
- H04L9/3252—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials involving digital signatures using DSA or related signature schemes, e.g. elliptic based signatures, ElGamal or Schnorr schemes
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
- H04L9/32—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials
- H04L9/3263—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials involving certificates, e.g. public key certificate [PKC] or attribute certificate [AC]; Public key infrastructure [PKI] arrangements
- H04L9/3268—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials involving certificates, e.g. public key certificate [PKC] or attribute certificate [AC]; Public key infrastructure [PKI] arrangements using certificate validation, registration, distribution or revocation, e.g. certificate revocation list [CRL]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
- H04W12/04—Key management, e.g. using generic bootstrapping architecture [GBA]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
- H04W12/06—Authentication
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q2220/00—Business processing using cryptography
-
- H04L2209/38—
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
- H04L9/50—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols using hash chains, e.g. blockchains or hash trees
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
- H04W12/60—Context-dependent security
- H04W12/69—Identity-dependent
- H04W12/77—Graphical identity
Definitions
- the present application generally relates to systems, apparatus and methods for secure electrical communication of biometric personal identification information to validate the identity of an individual. Specifically, the present application relates to use of a distributed database for identity validation using body characteristics and/or biometric personal identification information.
- biometrics can be stored and used for identity validation.
- Such systems are often insecure and inefficient. Specifically, such known systems are subject to data breaches leaving biometric data of users exposed. Moreover, such known systems are often difficult for multiple entities to use to validate an identity of an individual using biometrics.
- An apparatus for validating an identity of an individual based on biometrics includes a memory and a processor operatively coupled to a distributed database and the memory.
- the processor is configured to receive encrypted biometric data associated with a compute device and decrypt the biometric data using a private key associated with the processor to obtain biometric data.
- the processor is configured to provide the biometric data as an input to a predefined hash function to obtain a first biometric hash value.
- the processor is configured to receive a first pointer to a record in the distributed database including a signed second biometric hash value and obtain, using the first pointer, the second biometric hash value from the distributed database.
- the processor is configured to validate an identity of a user of the compute device in response to verifying that a signature of the signed second biometric hash value is associated with the compute device using a public key of the compute device and verifying that the first biometric hash value corresponds with the second biometric hash value.
- the processor is configured to define a certification based on the validating; digitally sign the certification using a private key associated with the processor to produce a signed biometric certification; store the signed biometric certification in the distributed database; and provide, to the compute device, a second pointer to the signed biometric certification in the distributed database such that the compute device can provide the second pointer to a relying entity.
- FIG. 1A shows a simplified block diagram of a system and method for sealing an identity of a person in a public storage facility.
- FIG. 1B also shows a simplified block diagram of a system and method for sealing an identity of a person in a public storage facility.
- FIG. 1C shows a simplified block diagram of a system and method for sealing any input data in a public storage facility.
- FIG. 2A shows a simplified block diagram of a system and method for certifying an identity of a person.
- FIGS. 2B-1 and 2B-2 show a process for verifying hashed input data and a digital signature.
- FIG. 2C shows a simplified block diagram for recording an acknowledgment.
- FIG. 3A shows a simplified block diagram of a system and method for verifying an acknowledgment record.
- FIG. 3B shows a flowchart diagram for a method for verifying an acknowledgment record and its underlying certification record.
- FIGS. 4A-4C are data flow diagrams illustrating the certification of user generated biometric data, in accordance with one embodiment of the present disclosure.
- FIG. 5 is a data flow diagram illustrating secure data sharing via a server, in accordance with one embodiment of the present disclosure.
- An apparatus for validating an identity of an individual based on biometrics includes a memory and a processor operatively coupled to a distributed database and the memory.
- the processor is configured to receive encrypted biometric data associated with a compute device and decrypt the biometric data using a private key associated with the processor to obtain biometric data.
- the processor is configured to provide the biometric data as an input to a predefined hash function to obtain a first biometric hash value.
- the processor is configured to receive a first pointer to a record in the distributed database including a signed second biometric hash value and obtain, using the first pointer, the second biometric hash value from the distributed database.
- the processor is configured to validate an identity of a user of the compute device in response to verifying that a signature of the signed second biometric hash value is associated with the compute device using a public key of the compute device and verifying that the first biometric hash value corresponds with the second biometric hash value.
- the processor is configured to define a certification based on the validating; digitally sign the certification using a private key associated with the processor to produce a signed biometric certification; store the signed biometric certification in the distributed database; and provide, to the compute device, a second pointer to the signed biometric certification in the distributed database such that the compute device can provide the second pointer to a relying entity.
- the identification card 102 may also take a physical or a digital form and the information can be retrieved either through scanning a code as described, performing Optical Character Recognition (OCR) on text strings, digitally transferring a digital identification card from one system to another, manually inputting the information using a keyboard, manually inputting the information using voice recognition, etc., in example embodiments.
- OCR Optical Character Recognition
- the identification card 102 can be a government issued form of identification such as a driver license, passport, employee badge, military identification, political documentation, or the like.
- the identification card 102 can also be a privately issued form of identification such as a student ID, library card, social club card, or any other form of identification issued by a third party.
- an input device 112 may be used to input such personal data from the identification card 102 to provide input data.
- Input device 112 can take many forms.
- input device 112 can be a digital scanner, digital camera, or smartphone (e.g., with the camera commonly found in smartphones) for reading data from the identification card 102 , including any codes appearing on the card 102 .
- the input device 112 can also be a device for manually inputting personal data such as a keyboard, touchscreen, voice recognition device, handwriting recognition device, or other manual input device.
- the input data can be optionally encrypted by encryption logic 118 and securely stored in operation 119 b .
- the input data is transferred directly to hashing logic 120 , without passing through encryption logic 118 .
- the operations of the optional encryption logic 118 will be discussed first, and then the operations processed by the hashing logic 120 . As such, the process may proceed directly from receiving the user information via 112 to the hashing logic 120 .
- encryption logic 118 On input device 112 .
- encryption logic 118 might include software, firmware, hardware, or any combination thereof, and consist of one or more encryption algorithms, e.g., an RSA encryption algorithm.
- Encryption logic 118 encrypts the input data with a public key to provide encrypted data.
- the public key is paired with an associated private key as is conventional when generating such keys using an RSA encryption algorithm, an Elliptic Curve Digital Signature Algorithm (ECDSA), or other encryption algorithm known to those skilled in the art.
- EDSA Elliptic Curve Digital Signature Algorithm
- this encrypted data can then be stored locally on the input device 112 for added security.
- input device 112 It can then only be accessed with the private key of the user on the input device 112 , which might be stored in a more secure part of input device 112 , e.g., “the Keychain”, in operation 119 a , if input device 112 is an iOS (e.g., operating system used by devices made by Apple, Inc.) smartphone. If the device is of a different type, e.g., one using an Android OS (e.g., operating system by Google, Inc.), similar secure device storage methods may be used. In this manner, for added security, the private key is not compromised and is kept safely on the input device 112 . It should be understood that the private key may be stored on another device, but similar or additional security should be processed to ensure that the private key is not compromised.
- iOS e.g., operating system used by devices made by Apple, Inc.
- Android OS e.g., operating system by Google, Inc.
- similar secure device storage methods may be used. In this manner, for added security, the private key is
- the operations to be performed by the hashing logic 120 can proceed directly after receiving the input data from the input device 112 .
- the hashing logic 120 is used for hashing the input data (e.g., personal information collected) to provide or generate a hash value.
- the hash value is sometimes referred to as “hash data,” that is generated by an algorithm.
- hashing logic 120 might be software, firmware, hardware, or any combination thereof, and consist of one or more hashing algorithms, e.g., a Secure Hash Algorithm (SHA) algorithm.
- Hashing logic 120 passes the hash value to digital-signature logic 121 , which performs a digital signature on the hash value, using the private key on the input device 112 .
- digital-signature logic 121 might be a component (or module) of encryption logic 118 . In other embodiments, the digital-signature logic 121 may be defined by separate code, firmware, and/or hardware.
- the digital-signature logic 121 then passes the signed hash value and the public key to a user accessible interface 126 (e.g., a graphical user interface or GUI), which might be other software running on the input device 112 .
- a user accessible interface 126 e.g., a graphical user interface or GUI
- the user accessible interface 126 might be part of an application or app that includes encryption logic 118 , hashing logic 120 , and digital-signature logic 121 , and/or other modules or code.
- the user accessible interface 126 might be used by the user to transmit the digitally signed hash value and the public key to a public storage facility 128 via a line 130 , and receive back from the public storage facility 128 a transaction number 132 corresponding to the transmitted hash value and public key.
- a “line” might be part of a wired and/or wireless connection or network, including a bus, an intranet, an internet, an extranet, a public computer network, a private computer network, etc., in an example embodiment.
- only the signed hash value might be transmitted to public storage facility 128 by the user and persons retrieving the signed hash value might obtain the public key from elsewhere (e.g., the user, a public database, an Internet repository, a website, etc.).
- the algorithms using public/private key pairs are design to enable full sharing of public keys.
- the private key on the other hand, must be kept secure, as noted above.
- the public storage facility 128 can take the form of a block chain (e.g., in a bitcoin online payment system) or any other public or private distributed database.
- the public storage facility 128 is connected to a communication link via a line and can be adapted to communicate over a public computer network, the internet, an intranet, an extranet, or any private communication network.
- the public storage facility 128 is accessible by any device that has an Internet connection over a network.
- a block chain as is known in the art, is a system that enables users' access to securely store data in a public place. The data is deemed secure, as each time data is written, the written data is dependent on previously written data, which includes performing cryptographic hash operations.
- a benefit of using a block chain is that once data is written to the block chain and a block chain transaction is created, that transaction remains intact, and can be verified in the future.
- the reason for this, is that data is continually written to the block chain, e.g., after a particular transaction is made, and that later data is dependent on an earlier particular transaction. Consequently, by writing data to a public storage facility that implements a public block chain, later verification of that data is practically ensured to be correct.
- a distributed public database is a block chain, which receives data for storage from a plurality of entities. The entities need not be related, and the type of data need not be the same.
- entities storing the block chain are unrelated, and the type of data can vary to almost any type of digital data, e.g., not limited to identity data, commercial data, bitcoin data, etc.
- the data received for storage is configured to be processed to generate a transaction record that is dependent on previous data stored to the block chain.
- the transaction record being dependent on previous data stored to the block chain ensures that data stored to the block chain is not modifiable, as each later data stored to the block chain continues to be dependent on previous data stored to the block chain.
- the input data might be hashed and the resulting hash value might be signed with a digital signature, created using a private key paired with a public key, before transmission, optionally along with the public key, from the input device (e.g., a user's smartphone) 112 to the public storage facility 128 for storage.
- the user accessible interface 126 is thus adapted to “seal” the signed hash value and the public key in the public storage facility 128 .
- a later verification may be made if another party is able to hash the same input data.
- user accessible interface 126 can be controllable by the user of the input device 112 to encrypt and provide the transaction number 132 , the input data, and, optionally, the public key of the user, to an input device 142 (e.g., a smartphone) of a third party (e.g., a financial institution or other entity engaging in a commercial, private transaction, or other transaction with the user) to, for example, establish the identity of the user.
- an input device 142 e.g., a smartphone
- a third party e.g., a financial institution or other entity engaging in a commercial, private transaction, or other transaction with the user
- the third party will access the block chain using the transaction number 132 to retrieve the digitally signed hash value, and optionally, the public key if the public key has not been previously obtained by the third party from another source/location, and enable comparison with a hash value that is generated by the third party using the input data and the same hashing algorithm.
- the encryption of the transaction number 132 , the input data, and, optionally, the public key of the user might be performed by the encryption logic 118 using a public key of a third party paired with a private key of the third party.
- coding logic 150 on the input device 112 might code the encrypted items into a barcode or QR code and the third party might use input device 142 to scan the barcode or QR code and decode it to gain access to the encrypted items.
- the third party might decrypt the encrypted items using the private key of the third party to perform a verification operation.
- the verification may use an RSA algorithm as explained in further detail below. Other verification algorithms may also be used, depending on the configured implementation.
- FIG. 1C shows a simplified block diagram of a system and method for sealing any input data in a public storage facility.
- the operations to be performed by the hashing logic 120 can proceed directly after receiving the user information from the input device 112 .
- the hashing logic 120 is used for hashing the input data (e.g., personal information collected) to provide or generate a hash value.
- the hash value is sometimes referred to as “hash data,” that is generated by an algorithm.
- hashing logic 120 might be software, firmware, hardware, or any combination thereof, and consist of one or more hashing algorithms, e.g., a Secure Hash Algorithm (SHA) algorithm.
- SHA Secure Hash Algorithm
- Hashing logic 120 passes the hash value to digital-signature logic 121 , which performs a digital signature on the hash value, using the private key on the input device 112 .
- digital-signature logic 121 might be a component (or module) of encryption logic 118 .
- the digital-signature logic 121 may be defined by separate code, firmware, and/or hardware.
- the digital-signature logic 121 then passes the signed hash value and the public key to a user accessible interface 126 (e.g., a graphical user interface or GUI), which might be other software running on the input device 112 .
- a user accessible interface 126 e.g., a graphical user interface or GUI
- the user accessible interface 126 might be part of an application or app that includes encryption logic 118 , hashing logic 120 , and digital-signature logic 121 , and/or other modules or code.
- the user accessible interface 126 might be used by the user to transmit the digitally signed hash value and the public key to a public storage facility 128 via a line 130 , and receives back from the public storage facility 128 a transaction number 132 corresponding to the transmitted hash value and public key.
- only the signed hash value might be transmitted to public storage facility 128 by the user and persons retrieving the signed hash value might obtain the public key from elsewhere (e.g., the user, a public database, an Internet repository, a website, etc.).
- persons retrieving the signed hash value might obtain the public key from elsewhere (e.g., the user, a public database, an Internet repository, a website, etc.).
- the algorithms using public/private key pairs are design to enable full sharing of public keys.
- the private key on the other hand, must be kept secure, as noted above.
- the public storage facility 128 can take the form of a block chain (e.g., in a bitcoin online payment system) or any other public or private distributed database.
- the public storage facility 128 is connected to a communication link via a line and can be adapted to communicate over a public computer network, the internet, an intranet, an extranet, or any private communication network.
- the public storage facility 128 is accessible by any device that has an Internet connection over a network.
- the input data might be hashed and the resulting hash value might be signed with a digital signature, created using a private key paired with a public key, before transmission, optionally along with the public key, from the input device (e.g., a user's smartphone) 112 to the public storage facility 128 for storage.
- the user accessible interface 126 is thus adapted to “seal” the signed hash value and the public key in the public storage facility 128 .
- a later verification may be made if another party is able to hash the same input data.
- FIG. 2A shows a simplified block diagram for a certification method for managing the identity of a user in a public storage facility 228 .
- an identification card 202 may be used. In other embodiments, other forms of identification, which may be digital or non-digital may be used.
- personal data 204 is contained thereon, which identifies the user.
- the input data can include a photo 206 of the user; the user's name, address and driver license number 208 , and/or a bar code 210 or similar computer code for storing, scanning and/or retrieving additional data.
- Such coding can include PDF417 codes, QR codes, and other such codes.
- the identification card 202 may also take a physical or a digital form and the information can be retrieved either through scanning a code as described, performing Optical Character Recognition (OCR) on text strings, digitally transferring a digital identification card from one system to another, manually inputting the information using a keyboard, manually inputting the information using voice recognition, etc., in example embodiments.
- OCR Optical Character Recognition
- the identification card 202 can be a government issued form of identification such as a driver license, passport, employee badge, military identification, political documentation, or the like.
- the identification card 202 can also be a privately issued form of identification such as a student ID, library card, social club card, or any other form of identification issued by a third party.
- an input device 212 may be used to input such personal data from the identification card 202 to provide input data.
- Input device 212 can take many forms.
- input device 212 can be a digital scanner, digital camera, or smartphone (e.g., with the camera commonly found in smartphones) for reading data from the identification card 202 , including any codes appearing on the card 202 .
- the input device 212 can also be a device for manually inputting personal data such as a keyboard, touchscreen, voice recognition device, handwriting recognition device, or other manual input device.
- the input data can be optionally encrypted by encryption logic 218 and securely stored.
- the input data is transferred directly to hashing logic 220 , without passing through encryption logic 218 .
- the operations of the optional encryption logic 218 will be discussed first, and then the operations processed by the hashing logic 220 . As such, the process may proceed directly from receiving the user information via 212 to the hashing logic 220 .
- encryption logic 218 On input device 212 .
- encryption logic 218 might include software, firmware, hardware, or any combination thereof, and consist of one or more encryption algorithms, e.g., an RSA encryption algorithm.
- Encryption logic 218 encrypts the input data with a public key to provide encrypted data.
- the public key is paired with an associated private key as is conventional when generating such keys using an RSA encryption algorithm, an Elliptic Curve Digital Signature Algorithm (ECDSA), or other encryption algorithm known to those skilled in the art.
- EDSA Elliptic Curve Digital Signature Algorithm
- the private key of the user on the input device 212 can then only be accessed with the private key of the user on the input device 212 , which might be stored in a more secure part of input device 212 , e.g., “the Keychain”, if input device 212 is an iOS (e.g., operating system used by devices made by Apple, Inc.) smartphone. If the device is of a different type, e.g., one using an Android OS (e.g., operating system by Google, Inc.), similar secure device storage methods may be used. In this manner, for added security, the private key is not compromised and is kept safely on the input device 212 . It should be understood that the private key may be stored on another device, but similar or additional security should be processed to ensure that the private key is not compromised.
- iOS e.g., operating system used by devices made by Apple, Inc.
- Android OS e.g., operating system by Google, Inc.
- similar secure device storage methods may be used. In this manner, for added security, the private key is not
- the operations to be performed by the hashing logic 220 can proceed directly after receiving the input data from the input device 212 .
- the hashing logic 220 is used for hashing the input data (or selected fields of the input data or personal data) to provide or generate a hash value.
- the hash value is sometimes referred to as “hash data,” that is generated by an algorithm.
- hashing logic 220 might be software, firmware, hardware, or any combination thereof, and consist of one or more hashing algorithms, e.g., a Secure Hash Algorithm (SHA) algorithm.
- SHA Secure Hash Algorithm
- Hashing logic 220 passes the hash value to digital-signature logic 221 , which performs a digital signature on the hash value, using the private key on the input device 212 .
- digital-signature logic 221 might be a component (or module) of encryption logic 218 .
- the digital-signature logic 221 may be defined by separate code, firmware, and/or hardware.
- the digital-signature logic 221 then passes the signed hash value and the public key to a user accessible interface 226 (e.g., a graphical user interface or GUI), which might be other software running on the input device 212 .
- a user accessible interface 226 e.g., a graphical user interface or GUI
- the user accessible interface 226 might be part of an application or app that includes encryption logic 218 , hashing logic 220 , and digital-signature logic 221 , and/or other modules or code.
- the user accessible interface 226 might be used by the user to transmit the digitally signed hash value and, optionally, the public key to a public storage facility 228 via a line 230 , and receive back from the public storage facility 228 a transaction number 232 corresponding to the transmitted hash value and public key.
- the public storage facility 228 can take the form of a block chain (e.g., in a bitcoin online payment system) or any other public or private distributed database.
- the public storage facility 228 is connected to a communication link via a line and can be adapted to communicate over a public computer network, the internet, an intranet, an extranet, or any private communication network.
- the public storage facility 228 is accessible by any device that has an Internet connection over a network.
- the input data (or selected fields of the input data) might be hashed and the resulting hash value might be signed with a digital signature, created using a private key paired with a public key, before transmission, along with, optionally, the public key, from the input device (e.g., a user's smartphone) 212 to the public storage facility 228 for storage.
- the user accessible interface 226 is thus adapted to “seal” the signed hash value and the public key in the public storage facility 228 .
- a later verification may be made if another party is able to hash the same input data.
- the user accessible interface 226 (e.g., a GUI) can be controllable by the user of the input device 212 to encrypt and provide the transaction number 232 , the input data (or selected fields of the input data), and, optionally, the public key to an input device 242 (e.g., a smartphone) of a certifier.
- the encryption might be performed by the encryption logic 218 using a public key of a certifier paired with a private key of the certifier.
- coding logic on the input device 212 might code the encrypted transaction number 232 , the input data (or selected fields of the input data), and, optionally, the public key into a barcode or QR code and the certifier might use input device 242 to scan the barcode or QR code and decode it to gain access to the encrypted items. Thereafter, the certifier might decrypt the encrypted items using the private key of the certifier and verify them, e.g., using a “verify” function call to an RSA algorithm as explained in further detail below.
- decoding logic on the certifier's input device 212 might decode the barcode or QR code and decryption logic 270 on the certifier's input device 242 might use the certifier's private key to decrypt the encrypted items.
- decryption logic 270 might be a component (or module) of more general encryption logic.
- the decrypted input data (or selected fields of the input data) might be hashed into a hash value by hashing logic 272 on the certifier's input device 242 , using the same hashing algorithm that was used to create the hash value that was digitally signed by the user.
- the decrypted transaction number 232 might be used by a user accessible interface 280 (e.g., a GUI) to access the public storage facility 228 (e.g., the block chain) and retrieve the signed hash value and public key of the user.
- the retrieved signed hash value, the generated hash value, and the retrieved or obtained public key might then be input to verifying logic 273 for verification (e.g., through a “verify” function call to an RSA algorithm), which outputs a “true” value if the two hash values are the same and the public key is associated with the signature or a “false” value if the two hash values are not the same or the public key is not associated with the signature.
- verifying logic 273 might be a component (or module) of decryption logic 270 . In another embodiment, the verifying logic 273 may be a separate module, software, firmware and/or hardware. As indicated above, in an example embodiment, the public key of the user might be obtained from some other source than the public storage facility 228 (e.g., from the user), in an example embodiment.
- FIG. 2B-1 shows how a digitally signed hash value is created from input data.
- the input data (or selected fields of the input data) is hashed into a hash value “ABC” by hashing logic 220 on the user's input device 112 , in operation 1.
- the hash value “ABC” is digitally signed with the user's private key using digital-signature logic 121 to create digitally signed hash value “XYZ”, in operation 2.
- FIG. 2B-2 shows how a digitally signed hash value is verified after being retrieved along with the public key of the user from the public storage facility 228 .
- the input data (or selected fields of the input data) is received from the user's input device 212 at the certifier's input device 242 and is hashed into a generated hash value “ABC” using hashing logic 272 , in operation 3.
- the signed hash value “XYZ”, the generated hash value “ABC”, and the user's public key are input to verification logic 273 in operation 4.
- the verification logic 273 might include a RSA verification algorithm, in an example embodiment.
- the verification logic 273 If the hash value in the digitally signed hash value “XYZ” is the same as the generated hash value “ABC” and the digital signature was signed with a private key that is associated with the user's public key, the verification logic 273 returns a value of “true”. Otherwise the verification logic 273 returns a value of “false”. It should be understood that the verification logic 273 may be executed on any device (e.g., a user's device, a certifier's device, a verifier's device, a third party's device, a commercial entity's device, a private entity's device, etc.), that needs to perform a verification operation.
- a user's device e.g., a user's device, a certifier's device, a verifier's device, a third party's device, a commercial entity's device, a private entity's device, etc.
- the certifier Upon receipt of a “true” value from encryption logic 270 , the certifier might create a certification record that refers to the verification.
- the certification record might include the transaction number 232 , the input data (or selected fields of the input data), received from the user, and, optionally, a timestamp, and the certification record might be hashed and digitally signed by the certifier using a private key of the certifier associated with a public key.
- the certifier might use user accessible interface 280 (e.g., a GUI) to transmit the signed certification record to the public storage facility 228 for storage and receive in return transaction number 282 from the public storage facility 228 .
- the certifier might encrypt the certification record with the certifier's public key before transmission to the public storage facility 228 , in order to keep the certification record private.
- the verification process shown in FIGS. 2B-1 and 2B-2 might be used to verify the digital signature on items of data other than the input data (or selected fields of the input data) received by input device 212 .
- the item of data that is digitally signed might not be hashed before being digitally signed.
- the verification process shown in FIGS. 2B-1 and 2B-2 might be used to verify a digitally-signed hash of a document other than an identification card, e.g., a digitally-signed certification as described above or a digitally-signed acknowledgment as described below.
- the same verification process might be used to verify a digitally-signed token (e.g., random number) that is sent by a sender using a secure-envelope process.
- a secure-envelope process as described below, might be used instead of, or in addition to, public-key encryption when transmitting data from a user to a certifier, verifier, third party, etc., and vice versa.
- a sender when using a secure envelope process, might hash a real-time token (e.g., a random number generated by the user's remote device) and digitally sign the hashed token using the sender's private key.
- a timestamp might be optionally included with the token. Then the sender might transmit the signed hashed token and, optionally, the public key associated with the sender's private key to a distributed public database for storage, receiving a transaction number in return from the distributed public database.
- the sender might transmit the transaction number and the token to a receiver, e.g., a certifier, a verifier, a third party, etc., optionally, after encrypting the transaction number and the token with the receiver's public key.
- a receiver e.g., a certifier, a verifier, a third party, etc.
- the receiver might receive the transaction number and token (optionally including the timestamp), decrypt them using the receiver's private key, if necessary, and then use the transaction number to retrieve the digitally signed hashed and, optionally, the sender's public key from the distributed public database.
- the receiver might generate a hash of the token using the same hashing algorithm the sender used.
- the receiver might verify, e.g., using an RSA verify call as described above, that the token in the generated hash is the same as the token in the digitally signed hash token and verify that the digital signature was created with the sender's private key.
- An RSA verify call may be, for example, processed by verifying logic 273 , e.g., to execute a verify operation.
- the token (optionally including the timestamp) might not be hashed before being signed.
- the certifier might encrypt the certification record and transaction number 282 (e.g., the transaction number the certifier received from the public storage facility 228 ) with the user's public key and transmit in 281 the encrypted certification record to the user, using user accessible interface 280 (e.g., a GUI).
- user accessible interface 280 e.g., a GUI
- the user Upon receiving the encrypted certification record, the user might decrypt it using the user's private key and then create an acknowledgment record that refers to or includes the certification record, and optionally includes a timestamp, in order to link the two records in the public storage facility 228 to facilitate convenient lookup by a third party, if the certification record is verified.
- the user might hash the certification record using the same hashing algorithm that the certifier used prior to digital signature by the certifier.
- the user might use transaction number 282 to retrieve the signed certification record and the certifier's public key from the public storage facility 228 .
- the user might verify that the certification record in the generated hash is the same as the certification record in the digitally signed certification record and verify that the digital signature was created with the certifier's private key, e.g., using an RSA verify call as described above.
- the acknowledgment record might include the certification record, the transaction number 282 , and optionally, a timestamp, and the user might digitally sign the acknowledgment record with the user's private key. Then the user might use user accessible interface 228 (e.g., a GUI) to transmit the signed acknowledgment record and the user's public key to the public storage facility 228 for storage and receive a transaction number 229 in response from the public storage facility 228 . In an example embodiment, the user might encrypt the signed acknowledgment record with the user's public key before transmission to the public storage facility 228 in order to keep the acknowledgment record private.
- user accessible interface 228 e.g., a GUI
- FIG. 3A shows a simplified block diagram for a system and method for certifying a pending transaction.
- an identification card 302 may be used. In other embodiments, other forms of identification, which may be digital or non-digital may be used.
- personal data 304 is contained thereon, which identifies the user.
- the personal data can include a photo 306 of the user; the user's name, address and driver license number 308 , and/or a bar code 310 or similar computer code for storing, scanning and/or retrieving additional data.
- Such coding can include PDF417 codes, QR codes, and other such codes. However, it is not necessary to have such code and the identification card may only have human-readable text strings.
- the identification card 302 may also take a physical or a digital form and the information can be retrieved either through scanning a code as described, performing Optical Character Recognition (OCR) on text strings, digitally transferring a digital identification card from one system to another, manually inputting the information using a keyboard, manually inputting the information using voice recognition, etc., in example embodiments.
- OCR Optical Character Recognition
- the identification card 302 can be a government issued form of identification such as a driver license, passport, employee badge, military identification, political documentation, or the like.
- the identification card 302 can also be a privately issued form of identification such as a student ID, library card, social club card, or any other form of identification issued by a third party.
- an input device 312 may be used to input such personal data from the identification card 302 to provide input data.
- Input device 312 can take many forms.
- input device 312 can be a digital scanner, digital camera, or smartphone (e.g., with the camera commonly found in smartphones) for reading data from the identification card 302 , including any codes appearing on the card 302 .
- the input device 312 can also be a device for manually inputting personal data such as a keyboard, touchscreen, voice recognition device, handwriting recognition device, or other manual input device.
- the input data can be optionally encrypted by encryption logic 318 and securely stored.
- the input data is transferred directly to hashing logic 320 , without passing through encryption logic 318 .
- the operations of the optional encryption logic 318 will be discussed first, and then the operations processed by the hashing logic 320 . As such, the process may proceed directly from receiving the user information via 312 to the hashing logic 320 .
- encryption logic 318 On input device 312 .
- encryption logic 318 might include software, firmware, hardware, or any combination thereof, and consist of one or more encryption algorithms, e.g., an RSA encryption algorithm.
- Encryption logic 318 encrypts the input data with a public key to provide encrypted data.
- the public key is paired with an associated private key as is conventional when generating such keys using an RSA encryption algorithm, an Elliptic Curve Digital Signature Algorithm (ECDSA), or other encryption algorithm known to those skilled in the art.
- EDSA Elliptic Curve Digital Signature Algorithm
- input device 312 It can then only be accessed with the private key of the user on the input device 312 , which might be stored in a more secure part of input device 312 , e.g., “the Keychain”, if input device 312 is an iOS (e.g., operating system used by devices made by Apple, Inc.) smartphone. If the device is of a different type, e.g., one using an Android OS (e.g., operating system by Google, Inc.), similar secure device storage methods may be used. In this manner, for added security, the private key is not compromised and is kept safely on the input device 312 . It should be understood that the private key may be stored on another device, but similar or additional security should be processed to ensure that the private key is not compromised.
- iOS e.g., operating system used by devices made by Apple, Inc.
- Android OS e.g., operating system by Google, Inc.
- similar secure device storage methods may be used. In this manner, for added security, the private key is not compromised and is kept safely on the
- the operations to be performed by the hashing logic 320 can proceed directly after receiving the user information from the input device 312 .
- the hashing logic 320 is used for hashing the input data (or selected fields of the input data or personal data) to provide or generate a hash value.
- the hash value is sometimes referred to as “hash data,” that is generated by an algorithm.
- hashing logic 320 might be software, firmware, hardware, or any combination thereof, and consist of one or more hashing algorithms, e.g., a Secure Hash Algorithm (SHA) algorithm.
- SHA Secure Hash Algorithm
- Hashing logic 320 passes the hash value to digital-signature logic 321 , which performs a digital signature on the hash value, using the private key on the input device 312 .
- digital-signature logic 321 might be a component (or module) of encryption logic 318 .
- the digital-signature logic 321 may be defined by separate code, firmware, and/or hardware.
- the digital-signature logic 321 then passes the signed hash value and, optionally, the public key to a user accessible interface 326 (e.g., a graphical user interface or GUI), which might be other software running on the input device 312 .
- a user accessible interface 326 e.g., a graphical user interface or GUI
- the user accessible interface 326 might be part of an application or app that includes encryption logic 318 , hashing logic 320 , and digital-signature logic 321 , and/or other modules or code.
- the user accessible interface 326 might be used by the user to transmit the digitally signed hash value and, optionally, the public key to a public storage facility 328 via a line 330 , and receive back from the public storage facility 328 a transaction number 332 corresponding to the transmitted hash value and public key.
- the public storage facility 328 can take the form of a block chain (e.g., in a bitcoin online payment system) or any other public or private distributed database.
- the public storage facility 328 is connected to a communication link via a line and can be adapted to communicate over a public computer network, the internet, an intranet, an extranet, or any private communication network.
- the public storage facility 328 is accessible by any device that has an Internet connection over a network.
- the input data might be hashed and the resulting hash value might be signed with a digital signature, created using a private key paired with a public key, before transmission, optionally along with the public key, from the input device (e.g., a user's smartphone) 312 to the public storage facility 328 for storage.
- the user accessible interface 326 is thus adapted to “seal” the signed hash value and the public key in the public storage facility 328 .
- a later verification may be made if another party is able to hash the same input data.
- the user accessible interface 326 can be controllable by the user of the input device 312 to transmit, in 350 , an acknowledgment record, a transaction number for a signed acknowledgment record, and optionally the user's public key to a verifier 342 .
- transaction number 332 for the signed input data and the input data might also be transmitted to verifier 342 , for verification using the verification process used by the certifier, as described above.
- an example use case of a bank being the verifier is provided. It should be understood that the verifier can be any entity that needs to verify identity, data, or transaction(s).
- the certifier may be any entity that has certified identity, data, or transaction(s).
- the bank is not necessarily the same entity as the certifier, but in other circumstances, the bank may also be the certifier.
- the bank may verify a certification made by another entity, e.g., a credit card company, a car company, a government agency, a private entity, etc. Acknowledgment records and transaction numbers for signed acknowledgment records were discussed in detail above with respect to FIG. 2C .
- the user might use encryption with the verifier's public key and/or a secure-envelope process for transmission 350 .
- the verifier might use the process shown in FIG. 3B to verify the acknowledgment record and its underlying certification record.
- the verifier uses the transaction number to retrieve the signed acknowledgment record and, optionally, the user's public key from public storage facility 328 .
- the verifier hashes the acknowledgment record with the same hashing algorithm that was used by the user and verifies the acknowledgment record and the user's signature, using a verification algorithm as discussed in detail above. If the verification is successful, the verifier uses the transaction number for the signed certification record to retrieve the signed certification record and the certifier's public key from public storage facility 328 , in operation 3.
- the verifier hashes the certification record with the same hashing algorithm that was used by the certifier and verifies the certification record and the certifier's signature, using a verification algorithm as discussed in detail above. If this verification is also successful, the verifier might create another certification record as discussed above and transmit it to public storage facility 328 , receiving, in response, another transaction number, which might be transmitted along with the verifier's certification record to the user for another acknowledgment record.
- the user transmits an unencrypted acknowledgment record to the verifier and the verifier performs its verifications using the data in the unencrypted acknowledgment record.
- these verifications include checking that an acknowledgment record in fact exists in the block chain with the transaction number for the signed acknowledgment record.
- the unencrypted acknowledgment record includes the transaction number of the signed certification record along with other unencrypted data from the certification record.
- the verifier can confirm that the certification record in fact exists on the block chain and can process the unencrypted data in the certification record to verify the certifier's signature, even if the certification record was also encrypted before transmission to the block chain.
- a User may generate any type of data (UGD) and have that data Certified by a third party (Certifier).
- the data can be any of the following types, but not limited only to these types of data: 1) a simple text string; 2) a date; 3) an enumerated data type; 4) a number; 5) an arbitrary series of data bytes (e.g., a data block).
- This data would be saved locally on the Users' mobile App.
- the User would then Seal her record by writing this data to the blockchain. This can be done by either inserting a new Seal record with the added user generated data that overwrites any previous Seal (if any), or a new Seal that complements any prior Seals.
- the value field written to the block chain is for validation of the original data only.
- the user is expected to hold onto that data and only share it when the user chooses to.
- the data is first hashed so the UGD becomes ⁇ hash.UGD>.
- Any number of hashing algorithms can be used such as SHA256.
- the User may then present the UGD (maintained by the User or another device storage of his/her choosing), along with her public-key and a pointer to the Seal record on the blockchain to another party.
- the other party can then get the hash value of the UGD by hashing the data with the same algorithm. This produces ⁇ hash.UGD>.
- the Certifier can then use ⁇ hash.UGD>, the users' public-key and the ⁇ signed.hash.UGD> pointed to on the blockchain to confirm that the data given to it is what was Sealed on the blockchain.
- the Certifier can then inspect the UGD in its clear form for authenticity, approval, or agreement.
- the Certifier may then certify that data.
- it uses methods previously described to uniquely certify the ⁇ signed.hash.UGD>.
- the user may present the UGD along with a pointer to its Sealed record and the Certified record along with its public-key to the Certifier or any other third party.
- the third party or the Certifier can validate the certification and matching of the UGD to the signature on the blockchain and feel comfortable to use the UGD without separately authenticating, approving, or agreeing to the data.
- the UGD was previously authenticated, approved or agreed to by the Certifier, a trusted party.
- the contents of the UGD may now be used for additional activities. If the UGD is a contract, its content can be trusted to the degree that the Certification attests to it.
- the UGD may be biometric data such as a fingerprint, facial image, iris-scan, voice, DNA-data or other biometric data. If the Certification represented a relationship of that data to the user, the third party presented with the data and the Certification can trust that association to the degree that it trusts the Certifier.
- the Verifier can now capture a new biometric from the same person (e.g., capture a new finger print, a new facial image, a new DNA-sample, a new iris-scan, a new voice-sample, or other biometric data) and compare it with the UGD that the User presented. If the two match, the Verifier can be assured that this is the same individual as the person who was previous Certified by the government agency. This not only validates the Users' digital id presented, but also the physical person who just presented that.
- FIGS. 4A-4C combined illustrate in more detail the process for certifying user generated biometric data as described above, in accordance with embodiments of the present disclosure.
- FIG. 4A-4C are data flow diagrams illustrating the certification of user generated biometric data.
- Participants e.g., devices, systems, etc.
- Participants include user 405 , certifier 420 , verifier 430 , and blockchain 450 .
- FIG. 4A illustrates operations performed at the user 405 .
- user generated data UGD
- UGD user generated data
- the UGD is hashed to generate: ⁇ hash.UGD>.
- a signature of the hashed UGD is performed using the private key of the user to generate: ⁇ signed.hash.UGD>.
- a seal name is delivered to the blockchain, wherein the seal name is the signature of the hashed UGD.
- a seal transaction identifier (“Seal txn-ID”) is returned to the user 405 from the blockchain 450 .
- FIG. 4B illustrates operations performed at the certifier 420 .
- the user presents to the certifier 420 the user generated data (UGD), the public key of the user (PBK.user), and the seal transaction identifier (e.g., “Seal txn-ID”).
- the certifier 420 gets the seal record from the blockchain 450 using the seal transaction identifier (e.g., “Seal txn-ID”).
- the seal record is returned to the certifier 420 from the blockchain 450 .
- the signature of the hashed UGD ( ⁇ signed.hash.UGD>) is extracted.
- a generated hash value ( ⁇ hash.UGD>) is created by the certifier 420 by performing a hash operation on the user generated data received from the user.
- the certifier verifies that the generated hash value ( ⁇ hash.UGD>) matches the hash value in the signature of the hashed UGD ( ⁇ signed.hash.UGD>) using in part the public key of the user.
- the generated hash value is verified at 466 , then the raw data of the user generated data (UGD) is checked for validation purposes.
- a certification signature of the seal transaction identifier (e.g., “Seal txn-ID”), and possibly other data, is generated using the private key of the certifier is generated (“CertSig”).
- CertSig a certification record
- a certification record transaction identifier (“CertRecord txn-ID”) is returned to the certifier 420 .
- the certification record transaction identifier (“CertRecord txn-ID”) is delivered to the user 405 .
- FIG. 4C illustrates operations performed at the verifier 430 .
- the user 405 presents to the verifier 430 the user generated data (UGD), the public key of the user, the seal transaction identifier (Seal txn-ID), and the certification record transaction identifier (“CertRecord txn-ID”).
- the verifier 430 presents the seal transaction identifier (Seal txn-ID) and the certification record transaction identifier (“CertRecord txn-ID”) to the blockchain 450 to retrieve the sealed records.
- the blockchain 450 delivers to the verifier 430 the seal record (“SealRecord”) and the certification record (“CertRecord”) stored to the blockchain.
- the verifier extracts the signed hash of the user generated data.
- the verifier also hashes the user generated data by performing a hash algorithm on the UGD to create a generated hash value ( ⁇ hash.UGD>).
- the verifier 430 verifies that the generated hash value ( ⁇ hash.UGD>) matches the hash value in the signature of the hashed UGD ( ⁇ signed.hash.UGD>) from the seal record (“SealRecord”) using in part the public key of the user.
- the verifier 430 may retrieve the sealed certification record using the certifier seal transaction identifier (“certifier Seal txn-ID”).
- the sealed certification record (Certifier Seal Record) is returned to the verifier 430 from the blockchain 450 .
- the verifier 430 verifies that the information in the sealed certification record matches presented data. For example, the certification signature (CertSig) in the sealed certification record is verified against newly presented CertSig data.
- the verifier 430 verifies that the user generated data (UGD) is sealed and certified by the certifier 420 .
- This description outlines a method where the server stores and directs the messages for the two parties, but is unable to ever read any of its content, in one embodiment.
- the server in the middle is depicted by the name “Store” 520 in this description, but it can be any server.
- User A intends to send a block of data to user B.
- User A places that data in a data block and may add additional identification fields to that block of data such as timestamp, its own
- the ⁇ secureEnvelope> is sent to Store.
- Store creates a unique ⁇ messageId> that is associated with the ⁇ secureEnvelope> and it returns that id to User A.
- User A then relays the ⁇ messageId> and possibly the address of the Store server (if not a well known server service between the two Users) to User B.
- This data is rather short and can easily fit in nearly digital codes such as a bar code, a QR code, pdf-417-code and the like.
- User B receives the data in some form, such as scanning the code from the mobile screen of User A and then sends a message to Store to get the ⁇ secureEnvelope> associated with the ⁇ messageId>.
- Store returns the associated ⁇ secureEnvelope>. If the protocol requires that the transmission be a onetime process, the ⁇ secureEnvelope> can be deleted after a successful transmission. It is also possible to delete the envelope if an expiration time is associated with it.
- This secure envelope can now be transmitted to user B from the store.
- User B can view the ⁇ envelopeContent> by decrypting the ⁇ secureEnvelope> using his private key that no one else is aware of. It may then verify the ⁇ dataBlock> in the envelope content by verifying the ⁇ dataBlock> and the ⁇ envelopeSignature> with the user A's public key that was passed. It may also verify that this is the same public key that was used in user A's SealId.
- User A passes the secure envelope to User B. It can be done via email, a text message, NFC, or any other form of digital communication where the data can be passed. Because it is encrypted using User B's public key, only User B can view the message and no other use can modify it either. In fact, after the secure envelope is created, even User A can no longer view its content, in one embodiment.
- FIG. 5 in more detail shows the exchange of data securely via a Secure Envelope between two users via a server as described above, in accordance with one embodiment of the present disclosure.
- the secure envelope exchange disclosed in FIG. 5 includes participants: User A, User B, and Store 520 .
- the assumption in this exchange is that the two Users A and B already know one another and are aware of each others' SealId (e.g., “SealID.userA” and “SealID.userB”), and may be obtained from seal records on a corresponding blockchain.
- SealId e.g., “SealID.userA” and “SealID.userB”
- user A creates a data block ⁇ dataBlock> to include: the data to be exchanged, a timestamp, the seal identifier of user A (SealID.userA), the seal identifier of user B (SealID.userB), a session identifier (sessionID) if available, and the public key of user A.
- user A signs the data block using the private key of user A to generate an envelope signature ⁇ envelopeSignature>.
- an envelope ⁇ EnvelopeContent> is generated having contents including the data block and the envelope signature ⁇ envelopeSignature>.
- a secure envelope ⁇ secureEnvelope> may be generated by encrypting the contents of the envelope ⁇ EnvelopeContent> using the public key of user B.
- user A sends the secure envelope ⁇ secureEnvelope> to store 520 .
- store 520 may create a unique message identifier ⁇ messageID> to be used as an index for accessing the secure envelope ⁇ secureEnvelope>.
- the message identifier ⁇ messageID> is delivered from store 520 to user A.
- the message identifier ⁇ messageID> is delivered from user A to user B.
- user B accesses the secure envelope ⁇ secureEnvelope> by sending message identifier ⁇ messageID> to store 520 .
- the secure envelope ⁇ secureEnvelope> is delivered from store 520 to user B.
- the secure envelope ⁇ secureEnvelope> may be removed from store 520 if it generated for purposes of a one-time use.
- user B extracts the contents of the secure envelope ⁇ secureEnvelope> by decrypting the secure envelope ⁇ secureEnvelope> using the private key of user B.
- the data block that is extracted is verified using the envelope signature ⁇ envelopeSignature> and the public key of user A.
- identity verification can be integrated into various commercial applications, as well as private applications.
- Commercial applications may include those that require commercial entities to verify a user's identity. Verifying a user's identity can be required for achieving any number of functions, such as traveling, making transactions, banking, communication, loan verification, credit verification, purchase verification, and other uses.
- Private identity verification can also be facilitated using the methods, apparatus, computer readable media, and systems described herein. Private identity verification may be useful when a user wishes to prove to another user their identity, in a fast and efficient manner.
- the systems described herein, as described above, utilize methods that write data to the block chain database, which is non-rewritable and permanently maintains the record without compromise. This enables writing of information to the block chain in a manner that can be verified by one or more transactions executed by methods of the present inventions.
- the method operations described herein may be executed with any number of computer systems.
- the computer systems may include user devices, such as mobile phones, tablets, desktop computers, watch computers, head attached computers, eyeglasses computers, or combinations thereof.
- Server operations may also be performed and communicated between client devices, to facilitate transactions with the block chain database, server storage, and the like.
- these computer devices can communicate over networks, such as the Internet.
- the networks enable individual devices to transact with each other, such as by way of sending, receiving, and processing exchanged information.
- the exchanged information can include different types of encrypted data, hashed data, envelopes, codes, QR codes, messages, notifications, and other types of data.
- the messaging and communication functions are provided to enable users to exchange data in order to verify identity, or enable or provide access to users to services, goods, or commercial transactions.
- the verification process can be utilized by banks, as well as users of the bank or third parties that require certified information from the banks regarding users.
- different travel entities can require identification of users, and that the identification be verified by themselves or by other third parties that are trusted.
- These operations can be facilitated using the systems, methods, computer readable media, and code that execute the verification processes.
- verification of a user identity can be useful in any type of industry, or private setting. The use of verification is simply facilitated by using the verifying infrastructure, programs code, applications, and combinations thereof, to ensure that verification is secure.
- the verification systems can be embodied in an application, such as those that can be installed on mobile devices (e.g., Apps).
- Apps e.g., users wishing to have their identity verified can use an App to seal information regarding their identity. Once the data has been sealed, and encrypted data has been stored to the block chain, this data can be used for later certification by another party. The other party may also be utilizing a corresponding App, which enables efficient reading of the data, code, QR code, message, or notification, to validate the identity of the user.
- code plug-ins can be integrated into commercial websites, which may use identity verification for different reasons or functions.
- banks can install plug-in applications, code, or programs that can execute part or all of the verification processing to seal information and/or to certify information regarding identity.
- a method is described.
- logic on a remote device causes the capture of personal data identifying a user from an identification card.
- the remote device supports a user-accessible interface.
- the logic generates a hash value from the personal data using a hashing algorithm and signs the hash value with a digital signature created using a private key paired with a public key.
- the logic transmits, over a network, the signed hash value and the public key from the remote device to a distributed public database for storage.
- the logic receives, over the network, a transaction number from the distributed public database and, transmits using the user-accessible interface, the transaction number and the personal data to a remote device of a third party for certification and/or verification.
- logic on a first remote device causes the capture of personal data identifying a user from an identification card.
- the first remote device supports a user-accessible interface.
- the logic generates a hash value from the personal data using a hashing algorithm and signs the hash value with a digital signature created using a first private key paired with a first public key.
- the logic transmits, over a network, the signed hash value and the first public key from the remote device to a distributed public database for storage.
- the logic receives, over the network, a first transaction number from the distributed public database.
- the logic then transmits the first transaction number and the personal data to a second remote device, wherein logic on the second remote device (a) uses the first transaction number to retrieve the signed hash value and the first public key from the distributed public database, (b) hashes the personal data using the hashing algorithm to create a generated hash value, (c) verifies that the hash value in the signed hash value is the same as the generated hash value, (d) verifies that the signed hash value was signed with the first private key, and (c) creates a certification.
- logic on a first smartphone causes the capture of personal data identifying a user from an identification card.
- the logic generates a hash value from the personal data using a hashing algorithm and signs the hash value with a digital signature created using a first private key paired with a first public key.
- the logic transmits, over a network, the signed hash value and the first public key from the remote device to a block chain database for storage.
- the logic receives, over the network, a first transaction number from the block chain database.
- the logic then transmits the first transaction number and the personal data to a second smartphone, wherein logic on the second smartphone (a) uses the first transaction number to retrieve the signed hash value and the first public key from the block chain database, (b) hashes the personal data using the hashing algorithm to create a generated hash value, (c) verifies that the hash value in the signed hash value is the same as the generated hash value, (d) verifies that the signed hash value was signed with the first private key, and (c) creates a certification.
- embodiments defined herein may define individual implementations or can define implementations that rely on combinations of one or more of the defined embodiments. Further, embodiments of the present invention may be practiced with various computer system configurations including hand-held devices, microprocessor systems, microprocessor-based or programmable consumer electronics, minicomputers, mainframe computers and the like. The invention can also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a wire-based or wireless network.
- the invention also relates to a device or an apparatus for performing these operations.
- the apparatus can be specially constructed for the required purpose, or the apparatus can be a general-purpose computer selectively activated or configured by a computer program stored in the computer.
- various general-purpose machines can be used with computer programs written in accordance with the teachings herein, or it may be more convenient to construct a more specialized apparatus to perform the required operations.
- the invention can also be embodied as computer readable code on a computer readable medium.
- the computer readable medium is any data storage device that can store data, which can thereafter be read by a computer system.
- the computer readable medium can also be distributed over a network-coupled computer system so that the computer readable code is stored and executed in a distributed fashion.
- the inventions might employ various computer-implemented operations involving data stored in computer systems. Any of the operations described herein that form part of the inventions are useful machine operations.
- the inventions also relate to a device or an apparatus for performing these operations.
- the apparatus may be specially constructed for the required purposes, such as the carrier network discussed above, or it may be a general purpose computer selectively activated or configured by a computer program stored in the computer.
- various general purpose machines may be used with computer programs written in accordance with the teachings herein, or it may be more convenient to construct a more specialized apparatus to perform the required operations.
- the inventions can also be embodied as computer readable code on a computer readable medium.
- the computer readable medium is any data storage device that can store data, which can thereafter be read by a computer system. Examples of the computer readable medium include hard drives, network attached storage (NAS), read-only memory, random-access memory, CD-ROMs, CD-Rs, CD-RWs, DVDs, Flash, magnetic tapes, and other optical and non-optical data storage devices.
- the computer readable medium can also be distributed over a network coupled computer systems so that the computer readable code is stored and executed in a distributed fashion.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Security & Cryptography (AREA)
- Theoretical Computer Science (AREA)
- Business, Economics & Management (AREA)
- General Physics & Mathematics (AREA)
- Physics & Mathematics (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Accounting & Taxation (AREA)
- Strategic Management (AREA)
- General Business, Economics & Management (AREA)
- General Engineering & Computer Science (AREA)
- Computer Hardware Design (AREA)
- Software Systems (AREA)
- Finance (AREA)
- Computing Systems (AREA)
- Health & Medical Sciences (AREA)
- General Health & Medical Sciences (AREA)
- Bioethics (AREA)
- Biomedical Technology (AREA)
- Mathematical Analysis (AREA)
- Algebra (AREA)
- Mathematical Optimization (AREA)
- Mathematical Physics (AREA)
- Pure & Applied Mathematics (AREA)
- Power Engineering (AREA)
- Biodiversity & Conservation Biology (AREA)
- Life Sciences & Earth Sciences (AREA)
- Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)
- Storage Device Security (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
Description
- The present application generally relates to systems, apparatus and methods for secure electrical communication of biometric personal identification information to validate the identity of an individual. Specifically, the present application relates to use of a distributed database for identity validation using body characteristics and/or biometric personal identification information.
- In some known systems, biometrics can be stored and used for identity validation. Such systems, however, are often insecure and inefficient. Specifically, such known systems are subject to data breaches leaving biometric data of users exposed. Moreover, such known systems are often difficult for multiple entities to use to validate an identity of an individual using biometrics.
- Accordingly, a need exists for secure and efficient systems, apparatus and methods for secure electrical communication of biometric personal identification information to validate the identity of an individual.
- An apparatus for validating an identity of an individual based on biometrics includes a memory and a processor operatively coupled to a distributed database and the memory. The processor is configured to receive encrypted biometric data associated with a compute device and decrypt the biometric data using a private key associated with the processor to obtain biometric data. The processor is configured to provide the biometric data as an input to a predefined hash function to obtain a first biometric hash value. The processor is configured to receive a first pointer to a record in the distributed database including a signed second biometric hash value and obtain, using the first pointer, the second biometric hash value from the distributed database. The processor is configured to validate an identity of a user of the compute device in response to verifying that a signature of the signed second biometric hash value is associated with the compute device using a public key of the compute device and verifying that the first biometric hash value corresponds with the second biometric hash value. The processor is configured to define a certification based on the validating; digitally sign the certification using a private key associated with the processor to produce a signed biometric certification; store the signed biometric certification in the distributed database; and provide, to the compute device, a second pointer to the signed biometric certification in the distributed database such that the compute device can provide the second pointer to a relying entity.
-
FIG. 1A shows a simplified block diagram of a system and method for sealing an identity of a person in a public storage facility. -
FIG. 1B also shows a simplified block diagram of a system and method for sealing an identity of a person in a public storage facility. -
FIG. 1C shows a simplified block diagram of a system and method for sealing any input data in a public storage facility. -
FIG. 2A shows a simplified block diagram of a system and method for certifying an identity of a person. -
FIGS. 2B-1 and 2B-2 show a process for verifying hashed input data and a digital signature. -
FIG. 2C shows a simplified block diagram for recording an acknowledgment. -
FIG. 3A shows a simplified block diagram of a system and method for verifying an acknowledgment record. -
FIG. 3B shows a flowchart diagram for a method for verifying an acknowledgment record and its underlying certification record. -
FIGS. 4A-4C are data flow diagrams illustrating the certification of user generated biometric data, in accordance with one embodiment of the present disclosure. -
FIG. 5 is a data flow diagram illustrating secure data sharing via a server, in accordance with one embodiment of the present disclosure. - Corresponding reference characters indicate corresponding parts throughout the drawings.
- In the following description, numerous specific details are set forth in order to provide a thorough understanding of the exemplary embodiments. However, it will be apparent to one skilled in the art that the example embodiments may be practiced without some of these specific details. In other instances, process operations and implementation details have not been described in detail, if already well known.
- An apparatus for validating an identity of an individual based on biometrics includes a memory and a processor operatively coupled to a distributed database and the memory. The processor is configured to receive encrypted biometric data associated with a compute device and decrypt the biometric data using a private key associated with the processor to obtain biometric data. The processor is configured to provide the biometric data as an input to a predefined hash function to obtain a first biometric hash value. The processor is configured to receive a first pointer to a record in the distributed database including a signed second biometric hash value and obtain, using the first pointer, the second biometric hash value from the distributed database. The processor is configured to validate an identity of a user of the compute device in response to verifying that a signature of the signed second biometric hash value is associated with the compute device using a public key of the compute device and verifying that the first biometric hash value corresponds with the second biometric hash value. The processor is configured to define a certification based on the validating; digitally sign the certification using a private key associated with the processor to produce a signed biometric certification; store the signed biometric certification in the distributed database; and provide, to the compute device, a second pointer to the signed biometric certification in the distributed database such that the compute device can provide the second pointer to a relying entity.
-
FIG. 1A shows a simplified block diagram for asystem 100 and method for managing the identity of a user by way of making verifiable transactions with apublic storage facility 128. By way of example, anidentification card 102 may be used. In other embodiments, other forms of identification, which may be digital or non-digital may be used. In the example of theidentification card 102,personal data 104 is contained thereon, which identifies the user. The personal data can include aphoto 106 of the user; the user's name, address anddriver license number 108, and/or abar code 110 or similar computer code for storing, scanning and/or retrieving additional data. Such coding can include PDF417 codes, QR codes, and other such codes. However, it is not necessary to have such code and the identification card may only have human-readable text strings. As noted above, theidentification card 102 may also take a physical or a digital form and the information can be retrieved either through scanning a code as described, performing Optical Character Recognition (OCR) on text strings, digitally transferring a digital identification card from one system to another, manually inputting the information using a keyboard, manually inputting the information using voice recognition, etc., in example embodiments. - The
identification card 102 can be a government issued form of identification such as a driver license, passport, employee badge, military identification, political documentation, or the like. Theidentification card 102 can also be a privately issued form of identification such as a student ID, library card, social club card, or any other form of identification issued by a third party. - In one embodiment, as indicated by
triangle 114, aninput device 112 may be used to input such personal data from theidentification card 102 to provide input data.Input device 112 can take many forms. For example,input device 112 can be a digital scanner, digital camera, or smartphone (e.g., with the camera commonly found in smartphones) for reading data from theidentification card 102, including any codes appearing on thecard 102. Theinput device 112 can also be a device for manually inputting personal data such as a keyboard, touchscreen, voice recognition device, handwriting recognition device, or other manual input device. - As shown in
FIG. 1A , the input data can be optionally encrypted byencryption logic 118 and securely stored inoperation 119 b. In one implementation, the input data is transferred directly tohashing logic 120, without passing throughencryption logic 118. For ease of understanding, the operations of theoptional encryption logic 118 will be discussed first, and then the operations processed by thehashing logic 120. As such, the process may proceed directly from receiving the user information via 112 to the hashinglogic 120. - The input data collected from the input device 112 (e.g., a user's smartphone) is passed to
encryption logic 118 oninput device 112. In an example embodiment,encryption logic 118 might include software, firmware, hardware, or any combination thereof, and consist of one or more encryption algorithms, e.g., an RSA encryption algorithm.Encryption logic 118 encrypts the input data with a public key to provide encrypted data. The public key is paired with an associated private key as is conventional when generating such keys using an RSA encryption algorithm, an Elliptic Curve Digital Signature Algorithm (ECDSA), or other encryption algorithm known to those skilled in the art. As shown inoperation 119 b, this encrypted data can then be stored locally on theinput device 112 for added security. It can then only be accessed with the private key of the user on theinput device 112, which might be stored in a more secure part ofinput device 112, e.g., “the Keychain”, inoperation 119 a, ifinput device 112 is an iOS (e.g., operating system used by devices made by Apple, Inc.) smartphone. If the device is of a different type, e.g., one using an Android OS (e.g., operating system by Google, Inc.), similar secure device storage methods may be used. In this manner, for added security, the private key is not compromised and is kept safely on theinput device 112. It should be understood that the private key may be stored on another device, but similar or additional security should be processed to ensure that the private key is not compromised. - As noted above, the operations to be performed by the hashing
logic 120 can proceed directly after receiving the input data from theinput device 112. In this embodiment, the hashinglogic 120 is used for hashing the input data (e.g., personal information collected) to provide or generate a hash value. The hash value is sometimes referred to as “hash data,” that is generated by an algorithm. In an example embodiment, hashinglogic 120 might be software, firmware, hardware, or any combination thereof, and consist of one or more hashing algorithms, e.g., a Secure Hash Algorithm (SHA) algorithm. Hashinglogic 120 passes the hash value to digital-signature logic 121, which performs a digital signature on the hash value, using the private key on theinput device 112. In an example embodiment, digital-signature logic 121 might be a component (or module) ofencryption logic 118. In other embodiments, the digital-signature logic 121 may be defined by separate code, firmware, and/or hardware. - In one embodiment, the digital-
signature logic 121 then passes the signed hash value and the public key to a user accessible interface 126 (e.g., a graphical user interface or GUI), which might be other software running on theinput device 112. In an example embodiment, the useraccessible interface 126 might be part of an application or app that includesencryption logic 118, hashinglogic 120, and digital-signature logic 121, and/or other modules or code. The useraccessible interface 126 might be used by the user to transmit the digitally signed hash value and the public key to apublic storage facility 128 via aline 130, and receive back from the public storage facility 128 atransaction number 132 corresponding to the transmitted hash value and public key. As used in this disclosure, a “line” might be part of a wired and/or wireless connection or network, including a bus, an intranet, an internet, an extranet, a public computer network, a private computer network, etc., in an example embodiment. In an alternative example embodiment, only the signed hash value might be transmitted topublic storage facility 128 by the user and persons retrieving the signed hash value might obtain the public key from elsewhere (e.g., the user, a public database, an Internet repository, a website, etc.). As is well known, there is no need to keep public keys secure, and in fact, the algorithms using public/private key pairs are design to enable full sharing of public keys. The private key, on the other hand, must be kept secure, as noted above. - In one embodiment, the
public storage facility 128 can take the form of a block chain (e.g., in a bitcoin online payment system) or any other public or private distributed database. Thepublic storage facility 128 is connected to a communication link via a line and can be adapted to communicate over a public computer network, the internet, an intranet, an extranet, or any private communication network. Broadly speaking, thepublic storage facility 128 is accessible by any device that has an Internet connection over a network. A block chain, as is known in the art, is a system that enables users' access to securely store data in a public place. The data is deemed secure, as each time data is written, the written data is dependent on previously written data, which includes performing cryptographic hash operations. A benefit of using a block chain is that once data is written to the block chain and a block chain transaction is created, that transaction remains intact, and can be verified in the future. The reason for this, is that data is continually written to the block chain, e.g., after a particular transaction is made, and that later data is dependent on an earlier particular transaction. Consequently, by writing data to a public storage facility that implements a public block chain, later verification of that data is practically ensured to be correct. In one embodiment, a distributed public database is a block chain, which receives data for storage from a plurality of entities. The entities need not be related, and the type of data need not be the same. In general, entities storing the block chain are unrelated, and the type of data can vary to almost any type of digital data, e.g., not limited to identity data, commercial data, bitcoin data, etc. Thus, the data received for storage is configured to be processed to generate a transaction record that is dependent on previous data stored to the block chain. The transaction record being dependent on previous data stored to the block chain ensures that data stored to the block chain is not modifiable, as each later data stored to the block chain continues to be dependent on previous data stored to the block chain. - As indicated above, in an example embodiment, the input data might be hashed and the resulting hash value might be signed with a digital signature, created using a private key paired with a public key, before transmission, optionally along with the public key, from the input device (e.g., a user's smartphone) 112 to the
public storage facility 128 for storage. The useraccessible interface 126 is thus adapted to “seal” the signed hash value and the public key in thepublic storage facility 128. In one embodiment, once the hash value, and optionally the public key of the user is written to the block chain in a transaction, a later verification may be made if another party is able to hash the same input data. - As depicted in
FIG. 1B , user accessible interface 126 (e.g., a GUI) can be controllable by the user of theinput device 112 to encrypt and provide thetransaction number 132, the input data, and, optionally, the public key of the user, to an input device 142 (e.g., a smartphone) of a third party (e.g., a financial institution or other entity engaging in a commercial, private transaction, or other transaction with the user) to, for example, establish the identity of the user. In one embodiment, the third party will access the block chain using thetransaction number 132 to retrieve the digitally signed hash value, and optionally, the public key if the public key has not been previously obtained by the third party from another source/location, and enable comparison with a hash value that is generated by the third party using the input data and the same hashing algorithm. - In an example embodiment, the encryption of the
transaction number 132, the input data, and, optionally, the public key of the user might be performed by theencryption logic 118 using a public key of a third party paired with a private key of the third party. Then, codinglogic 150 on theinput device 112 might code the encrypted items into a barcode or QR code and the third party might useinput device 142 to scan the barcode or QR code and decode it to gain access to the encrypted items. Thereafter, the third party might decrypt the encrypted items using the private key of the third party to perform a verification operation. In one embodiment, the verification may use an RSA algorithm as explained in further detail below. Other verification algorithms may also be used, depending on the configured implementation. -
FIG. 1C shows a simplified block diagram of a system and method for sealing any input data in a public storage facility. As noted above, the operations to be performed by the hashinglogic 120 can proceed directly after receiving the user information from theinput device 112. In this embodiment, the hashinglogic 120 is used for hashing the input data (e.g., personal information collected) to provide or generate a hash value. The hash value is sometimes referred to as “hash data,” that is generated by an algorithm. In an example embodiment, hashinglogic 120 might be software, firmware, hardware, or any combination thereof, and consist of one or more hashing algorithms, e.g., a Secure Hash Algorithm (SHA) algorithm. Hashinglogic 120 passes the hash value to digital-signature logic 121, which performs a digital signature on the hash value, using the private key on theinput device 112. In an example embodiment, digital-signature logic 121 might be a component (or module) ofencryption logic 118. In other embodiments, the digital-signature logic 121 may be defined by separate code, firmware, and/or hardware. - In one embodiment, the digital-
signature logic 121 then passes the signed hash value and the public key to a user accessible interface 126 (e.g., a graphical user interface or GUI), which might be other software running on theinput device 112. In an example embodiment, the useraccessible interface 126 might be part of an application or app that includesencryption logic 118, hashinglogic 120, and digital-signature logic 121, and/or other modules or code. The useraccessible interface 126 might be used by the user to transmit the digitally signed hash value and the public key to apublic storage facility 128 via aline 130, and receives back from the public storage facility 128 atransaction number 132 corresponding to the transmitted hash value and public key. In an alternative example embodiment, only the signed hash value might be transmitted topublic storage facility 128 by the user and persons retrieving the signed hash value might obtain the public key from elsewhere (e.g., the user, a public database, an Internet repository, a website, etc.). As is well known, there is no need to keep public keys secure, and in fact, the algorithms using public/private key pairs are design to enable full sharing of public keys. The private key, on the other hand, must be kept secure, as noted above. - In one embodiment, the
public storage facility 128 can take the form of a block chain (e.g., in a bitcoin online payment system) or any other public or private distributed database. Thepublic storage facility 128 is connected to a communication link via a line and can be adapted to communicate over a public computer network, the internet, an intranet, an extranet, or any private communication network. Broadly speaking, thepublic storage facility 128 is accessible by any device that has an Internet connection over a network. - As indicated above, in an example embodiment, the input data might be hashed and the resulting hash value might be signed with a digital signature, created using a private key paired with a public key, before transmission, optionally along with the public key, from the input device (e.g., a user's smartphone) 112 to the
public storage facility 128 for storage. The useraccessible interface 126 is thus adapted to “seal” the signed hash value and the public key in thepublic storage facility 128. In one embodiment, once the hash value, and, optionally, the public key of the user is written to the block chain in a transaction, a later verification may be made if another party is able to hash the same input data. -
FIG. 2A shows a simplified block diagram for a certification method for managing the identity of a user in apublic storage facility 228. By way of example, anidentification card 202 may be used. In other embodiments, other forms of identification, which may be digital or non-digital may be used. In the example of theidentification card 202,personal data 204 is contained thereon, which identifies the user. The input data can include aphoto 206 of the user; the user's name, address anddriver license number 208, and/or abar code 210 or similar computer code for storing, scanning and/or retrieving additional data. Such coding can include PDF417 codes, QR codes, and other such codes. However, it is not necessary to have such code and the identification card may only have human-readable text strings. As noted above, theidentification card 202 may also take a physical or a digital form and the information can be retrieved either through scanning a code as described, performing Optical Character Recognition (OCR) on text strings, digitally transferring a digital identification card from one system to another, manually inputting the information using a keyboard, manually inputting the information using voice recognition, etc., in example embodiments. - The
identification card 202 can be a government issued form of identification such as a driver license, passport, employee badge, military identification, political documentation, or the like. Theidentification card 202 can also be a privately issued form of identification such as a student ID, library card, social club card, or any other form of identification issued by a third party. - In one embodiment, as indicated by
triangle 214, aninput device 212 may be used to input such personal data from theidentification card 202 to provide input data.Input device 212 can take many forms. For example,input device 212 can be a digital scanner, digital camera, or smartphone (e.g., with the camera commonly found in smartphones) for reading data from theidentification card 202, including any codes appearing on thecard 202. Theinput device 212 can also be a device for manually inputting personal data such as a keyboard, touchscreen, voice recognition device, handwriting recognition device, or other manual input device. - As shown in
FIG. 2A , the input data can be optionally encrypted byencryption logic 218 and securely stored. In one implementation, the input data is transferred directly to hashinglogic 220, without passing throughencryption logic 218. For ease of understanding, the operations of theoptional encryption logic 218 will be discussed first, and then the operations processed by the hashinglogic 220. As such, the process may proceed directly from receiving the user information via 212 to the hashinglogic 220. - The input data collected from the input device 212 (e.g., a user's smartphone) is passed to
encryption logic 218 oninput device 212. In an example embodiment,encryption logic 218 might include software, firmware, hardware, or any combination thereof, and consist of one or more encryption algorithms, e.g., an RSA encryption algorithm.Encryption logic 218 encrypts the input data with a public key to provide encrypted data. The public key is paired with an associated private key as is conventional when generating such keys using an RSA encryption algorithm, an Elliptic Curve Digital Signature Algorithm (ECDSA), or other encryption algorithm known to those skilled in the art. This encrypted data can then be stored locally on theinput device 212 for added security. It can then only be accessed with the private key of the user on theinput device 212, which might be stored in a more secure part ofinput device 212, e.g., “the Keychain”, ifinput device 212 is an iOS (e.g., operating system used by devices made by Apple, Inc.) smartphone. If the device is of a different type, e.g., one using an Android OS (e.g., operating system by Google, Inc.), similar secure device storage methods may be used. In this manner, for added security, the private key is not compromised and is kept safely on theinput device 212. It should be understood that the private key may be stored on another device, but similar or additional security should be processed to ensure that the private key is not compromised. - As noted above, the operations to be performed by the hashing
logic 220 can proceed directly after receiving the input data from theinput device 212. In this embodiment, the hashinglogic 220 is used for hashing the input data (or selected fields of the input data or personal data) to provide or generate a hash value. The hash value is sometimes referred to as “hash data,” that is generated by an algorithm. In an example embodiment, hashinglogic 220 might be software, firmware, hardware, or any combination thereof, and consist of one or more hashing algorithms, e.g., a Secure Hash Algorithm (SHA) algorithm. Hashinglogic 220 passes the hash value to digital-signature logic 221, which performs a digital signature on the hash value, using the private key on theinput device 212. In an example embodiment, digital-signature logic 221 might be a component (or module) ofencryption logic 218. In other embodiments, the digital-signature logic 221 may be defined by separate code, firmware, and/or hardware. - In one embodiment, the digital-
signature logic 221 then passes the signed hash value and the public key to a user accessible interface 226 (e.g., a graphical user interface or GUI), which might be other software running on theinput device 212. In an example embodiment, the useraccessible interface 226 might be part of an application or app that includesencryption logic 218, hashinglogic 220, and digital-signature logic 221, and/or other modules or code. The useraccessible interface 226 might be used by the user to transmit the digitally signed hash value and, optionally, the public key to apublic storage facility 228 via aline 230, and receive back from the public storage facility 228 atransaction number 232 corresponding to the transmitted hash value and public key. - In one embodiment, the
public storage facility 228 can take the form of a block chain (e.g., in a bitcoin online payment system) or any other public or private distributed database. Thepublic storage facility 228 is connected to a communication link via a line and can be adapted to communicate over a public computer network, the internet, an intranet, an extranet, or any private communication network. Broadly speaking, thepublic storage facility 228 is accessible by any device that has an Internet connection over a network. - As indicated above, in an example embodiment, the input data (or selected fields of the input data) might be hashed and the resulting hash value might be signed with a digital signature, created using a private key paired with a public key, before transmission, along with, optionally, the public key, from the input device (e.g., a user's smartphone) 212 to the
public storage facility 228 for storage. The useraccessible interface 226 is thus adapted to “seal” the signed hash value and the public key in thepublic storage facility 228. In one embodiment, once the hash value, and, optionally, the public key of the user is written to the block chain in a transaction, a later verification may be made if another party is able to hash the same input data. - The user accessible interface 226 (e.g., a GUI) can be controllable by the user of the
input device 212 to encrypt and provide thetransaction number 232, the input data (or selected fields of the input data), and, optionally, the public key to an input device 242 (e.g., a smartphone) of a certifier. In an example embodiment, the encryption might be performed by theencryption logic 218 using a public key of a certifier paired with a private key of the certifier. Then, coding logic on theinput device 212 might code theencrypted transaction number 232, the input data (or selected fields of the input data), and, optionally, the public key into a barcode or QR code and the certifier might useinput device 242 to scan the barcode or QR code and decode it to gain access to the encrypted items. Thereafter, the certifier might decrypt the encrypted items using the private key of the certifier and verify them, e.g., using a “verify” function call to an RSA algorithm as explained in further detail below. - Once the certifier's
input device 242 receives the barcode or QR code, decoding logic on the certifier'sinput device 212 might decode the barcode or QR code anddecryption logic 270 on the certifier'sinput device 242 might use the certifier's private key to decrypt the encrypted items. In an example embodiment,decryption logic 270 might be a component (or module) of more general encryption logic. In one embodiment, the decrypted input data (or selected fields of the input data) might be hashed into a hash value by hashinglogic 272 on the certifier'sinput device 242, using the same hashing algorithm that was used to create the hash value that was digitally signed by the user. And the decryptedtransaction number 232 might be used by a user accessible interface 280 (e.g., a GUI) to access the public storage facility 228 (e.g., the block chain) and retrieve the signed hash value and public key of the user. The retrieved signed hash value, the generated hash value, and the retrieved or obtained public key might then be input to verifyinglogic 273 for verification (e.g., through a “verify” function call to an RSA algorithm), which outputs a “true” value if the two hash values are the same and the public key is associated with the signature or a “false” value if the two hash values are not the same or the public key is not associated with the signature. In an example embodiment, verifyinglogic 273 might be a component (or module) ofdecryption logic 270. In another embodiment, the verifyinglogic 273 may be a separate module, software, firmware and/or hardware. As indicated above, in an example embodiment, the public key of the user might be obtained from some other source than the public storage facility 228 (e.g., from the user), in an example embodiment. - This verification process is depicted in
FIGS. 2B-1 and 2B-2 .FIG. 2B-1 shows how a digitally signed hash value is created from input data. The input data (or selected fields of the input data) is hashed into a hash value “ABC” by hashinglogic 220 on the user'sinput device 112, inoperation 1. Then the hash value “ABC” is digitally signed with the user's private key using digital-signature logic 121 to create digitally signed hash value “XYZ”, inoperation 2. -
FIG. 2B-2 shows how a digitally signed hash value is verified after being retrieved along with the public key of the user from thepublic storage facility 228. The input data (or selected fields of the input data) is received from the user'sinput device 212 at the certifier'sinput device 242 and is hashed into a generated hash value “ABC” usinghashing logic 272, inoperation 3. Then the signed hash value “XYZ”, the generated hash value “ABC”, and the user's public key are input toverification logic 273 inoperation 4. Theverification logic 273 might include a RSA verification algorithm, in an example embodiment. If the hash value in the digitally signed hash value “XYZ” is the same as the generated hash value “ABC” and the digital signature was signed with a private key that is associated with the user's public key, theverification logic 273 returns a value of “true”. Otherwise theverification logic 273 returns a value of “false”. It should be understood that theverification logic 273 may be executed on any device (e.g., a user's device, a certifier's device, a verifier's device, a third party's device, a commercial entity's device, a private entity's device, etc.), that needs to perform a verification operation. - Upon receipt of a “true” value from
encryption logic 270, the certifier might create a certification record that refers to the verification. In an example embodiment, the certification record might include thetransaction number 232, the input data (or selected fields of the input data), received from the user, and, optionally, a timestamp, and the certification record might be hashed and digitally signed by the certifier using a private key of the certifier associated with a public key. Then the certifier might use user accessible interface 280 (e.g., a GUI) to transmit the signed certification record to thepublic storage facility 228 for storage and receive inreturn transaction number 282 from thepublic storage facility 228. In an example embodiment, the certifier might encrypt the certification record with the certifier's public key before transmission to thepublic storage facility 228, in order to keep the certification record private. - It will be appreciated that the verification process shown in
FIGS. 2B-1 and 2B-2 might be used to verify the digital signature on items of data other than the input data (or selected fields of the input data) received byinput device 212. In an example embodiment, the item of data that is digitally signed might not be hashed before being digitally signed. In an example embodiment, the verification process shown inFIGS. 2B-1 and 2B-2 might be used to verify a digitally-signed hash of a document other than an identification card, e.g., a digitally-signed certification as described above or a digitally-signed acknowledgment as described below. Or, the same verification process might be used to verify a digitally-signed token (e.g., random number) that is sent by a sender using a secure-envelope process. A secure-envelope process, as described below, might be used instead of, or in addition to, public-key encryption when transmitting data from a user to a certifier, verifier, third party, etc., and vice versa. - In an example embodiment, when using a secure envelope process, a sender might hash a real-time token (e.g., a random number generated by the user's remote device) and digitally sign the hashed token using the sender's private key. In an example embodiment, a timestamp might be optionally included with the token. Then the sender might transmit the signed hashed token and, optionally, the public key associated with the sender's private key to a distributed public database for storage, receiving a transaction number in return from the distributed public database. Thereafter, the sender might transmit the transaction number and the token to a receiver, e.g., a certifier, a verifier, a third party, etc., optionally, after encrypting the transaction number and the token with the receiver's public key. In an example embodiment, the receiver might receive the transaction number and token (optionally including the timestamp), decrypt them using the receiver's private key, if necessary, and then use the transaction number to retrieve the digitally signed hashed and, optionally, the sender's public key from the distributed public database. The receiver might generate a hash of the token using the same hashing algorithm the sender used. Then the receiver might verify, e.g., using an RSA verify call as described above, that the token in the generated hash is the same as the token in the digitally signed hash token and verify that the digital signature was created with the sender's private key. An RSA verify call may be, for example, processed by verifying
logic 273, e.g., to execute a verify operation. In an example embodiment, the token (optionally including the timestamp) might not be hashed before being signed. - In one configuration, as depicted in
FIG. 2C , the certifier might encrypt the certification record and transaction number 282 (e.g., the transaction number the certifier received from the public storage facility 228) with the user's public key and transmit in 281 the encrypted certification record to the user, using user accessible interface 280 (e.g., a GUI). Upon receiving the encrypted certification record, the user might decrypt it using the user's private key and then create an acknowledgment record that refers to or includes the certification record, and optionally includes a timestamp, in order to link the two records in thepublic storage facility 228 to facilitate convenient lookup by a third party, if the certification record is verified. Here again, to verify the certification record, the user might hash the certification record using the same hashing algorithm that the certifier used prior to digital signature by the certifier. The user might usetransaction number 282 to retrieve the signed certification record and the certifier's public key from thepublic storage facility 228. Then the user might verify that the certification record in the generated hash is the same as the certification record in the digitally signed certification record and verify that the digital signature was created with the certifier's private key, e.g., using an RSA verify call as described above. - In an example embodiment, the acknowledgment record might include the certification record, the
transaction number 282, and optionally, a timestamp, and the user might digitally sign the acknowledgment record with the user's private key. Then the user might use user accessible interface 228 (e.g., a GUI) to transmit the signed acknowledgment record and the user's public key to thepublic storage facility 228 for storage and receive atransaction number 229 in response from thepublic storage facility 228. In an example embodiment, the user might encrypt the signed acknowledgment record with the user's public key before transmission to thepublic storage facility 228 in order to keep the acknowledgment record private. -
FIG. 3A shows a simplified block diagram for a system and method for certifying a pending transaction. By way of example, anidentification card 302 may be used. In other embodiments, other forms of identification, which may be digital or non-digital may be used. In the example of theidentification card 302,personal data 304 is contained thereon, which identifies the user. The personal data can include aphoto 306 of the user; the user's name, address anddriver license number 308, and/or abar code 310 or similar computer code for storing, scanning and/or retrieving additional data. Such coding can include PDF417 codes, QR codes, and other such codes. However, it is not necessary to have such code and the identification card may only have human-readable text strings. As noted above, theidentification card 302 may also take a physical or a digital form and the information can be retrieved either through scanning a code as described, performing Optical Character Recognition (OCR) on text strings, digitally transferring a digital identification card from one system to another, manually inputting the information using a keyboard, manually inputting the information using voice recognition, etc., in example embodiments. - The
identification card 302 can be a government issued form of identification such as a driver license, passport, employee badge, military identification, political documentation, or the like. Theidentification card 302 can also be a privately issued form of identification such as a student ID, library card, social club card, or any other form of identification issued by a third party. - In one embodiment, as indicated by
triangle 314, aninput device 312 may be used to input such personal data from theidentification card 302 to provide input data.Input device 312 can take many forms. For example,input device 312 can be a digital scanner, digital camera, or smartphone (e.g., with the camera commonly found in smartphones) for reading data from theidentification card 302, including any codes appearing on thecard 302. Theinput device 312 can also be a device for manually inputting personal data such as a keyboard, touchscreen, voice recognition device, handwriting recognition device, or other manual input device. - As shown in
FIG. 3A , the input data can be optionally encrypted byencryption logic 318 and securely stored. In one implementation, the input data is transferred directly to hashinglogic 320, without passing throughencryption logic 318. For ease of understanding, the operations of theoptional encryption logic 318 will be discussed first, and then the operations processed by the hashinglogic 320. As such, the process may proceed directly from receiving the user information via 312 to the hashinglogic 320. - The input data collected from the input device 312 (e.g., a user's smartphone) is passed to
encryption logic 318 oninput device 312. In an example embodiment,encryption logic 318 might include software, firmware, hardware, or any combination thereof, and consist of one or more encryption algorithms, e.g., an RSA encryption algorithm.Encryption logic 318 encrypts the input data with a public key to provide encrypted data. The public key is paired with an associated private key as is conventional when generating such keys using an RSA encryption algorithm, an Elliptic Curve Digital Signature Algorithm (ECDSA), or other encryption algorithm known to those skilled in the art. This encrypted data can then be stored locally on theinput device 312 for added security. It can then only be accessed with the private key of the user on theinput device 312, which might be stored in a more secure part ofinput device 312, e.g., “the Keychain”, ifinput device 312 is an iOS (e.g., operating system used by devices made by Apple, Inc.) smartphone. If the device is of a different type, e.g., one using an Android OS (e.g., operating system by Google, Inc.), similar secure device storage methods may be used. In this manner, for added security, the private key is not compromised and is kept safely on theinput device 312. It should be understood that the private key may be stored on another device, but similar or additional security should be processed to ensure that the private key is not compromised. - As noted above, the operations to be performed by the hashing
logic 320 can proceed directly after receiving the user information from theinput device 312. In this embodiment, the hashinglogic 320 is used for hashing the input data (or selected fields of the input data or personal data) to provide or generate a hash value. The hash value is sometimes referred to as “hash data,” that is generated by an algorithm. In an example embodiment, hashinglogic 320 might be software, firmware, hardware, or any combination thereof, and consist of one or more hashing algorithms, e.g., a Secure Hash Algorithm (SHA) algorithm. Hashinglogic 320 passes the hash value to digital-signature logic 321, which performs a digital signature on the hash value, using the private key on theinput device 312. In an example embodiment, digital-signature logic 321 might be a component (or module) ofencryption logic 318. In other embodiments, the digital-signature logic 321 may be defined by separate code, firmware, and/or hardware. - In one embodiment, the digital-
signature logic 321 then passes the signed hash value and, optionally, the public key to a user accessible interface 326 (e.g., a graphical user interface or GUI), which might be other software running on theinput device 312. In an example embodiment, the useraccessible interface 326 might be part of an application or app that includesencryption logic 318, hashinglogic 320, and digital-signature logic 321, and/or other modules or code. The useraccessible interface 326 might be used by the user to transmit the digitally signed hash value and, optionally, the public key to apublic storage facility 328 via aline 330, and receive back from the public storage facility 328 atransaction number 332 corresponding to the transmitted hash value and public key. - In one embodiment, the
public storage facility 328 can take the form of a block chain (e.g., in a bitcoin online payment system) or any other public or private distributed database. Thepublic storage facility 328 is connected to a communication link via a line and can be adapted to communicate over a public computer network, the internet, an intranet, an extranet, or any private communication network. Broadly speaking, thepublic storage facility 328 is accessible by any device that has an Internet connection over a network. - As indicated above, in an example embodiment, the input data might be hashed and the resulting hash value might be signed with a digital signature, created using a private key paired with a public key, before transmission, optionally along with the public key, from the input device (e.g., a user's smartphone) 312 to the
public storage facility 328 for storage. The useraccessible interface 326 is thus adapted to “seal” the signed hash value and the public key in thepublic storage facility 328. In one embodiment, once the hash value, and, optionally, the public key of the user is written to the block chain in a transaction, a later verification may be made if another party is able to hash the same input data. - The user accessible interface 326 (e.g., a GUI) can be controllable by the user of the
input device 312 to transmit, in 350, an acknowledgment record, a transaction number for a signed acknowledgment record, and optionally the user's public key to averifier 342. In an example embodiment,transaction number 332 for the signed input data and the input data might also be transmitted toverifier 342, for verification using the verification process used by the certifier, as described above. As used herein, to provide broad understanding of the functions or operation ofverifier 342, an example use case of a bank, being the verifier is provided. It should be understood that the verifier can be any entity that needs to verify identity, data, or transaction(s). Additionally, the certifier may be any entity that has certified identity, data, or transaction(s). Thus, in this use case example, the bank is not necessarily the same entity as the certifier, but in other circumstances, the bank may also be the certifier. By way of example, the bank may verify a certification made by another entity, e.g., a credit card company, a car company, a government agency, a private entity, etc. Acknowledgment records and transaction numbers for signed acknowledgment records were discussed in detail above with respect toFIG. 2C . As noted indicated above, the user might use encryption with the verifier's public key and/or a secure-envelope process fortransmission 350. - Once the verifier receives the acknowledgment record and the transaction number for the signed acknowledgment record, the verifier might use the process shown in
FIG. 3B to verify the acknowledgment record and its underlying certification record. Inoperation 1, the verifier uses the transaction number to retrieve the signed acknowledgment record and, optionally, the user's public key frompublic storage facility 328. Then, inoperation 2, the verifier hashes the acknowledgment record with the same hashing algorithm that was used by the user and verifies the acknowledgment record and the user's signature, using a verification algorithm as discussed in detail above. If the verification is successful, the verifier uses the transaction number for the signed certification record to retrieve the signed certification record and the certifier's public key frompublic storage facility 328, inoperation 3. Then, inoperation 4, the verifier hashes the certification record with the same hashing algorithm that was used by the certifier and verifies the certification record and the certifier's signature, using a verification algorithm as discussed in detail above. If this verification is also successful, the verifier might create another certification record as discussed above and transmit it topublic storage facility 328, receiving, in response, another transaction number, which might be transmitted along with the verifier's certification record to the user for another acknowledgment record. - In the event the certification record and/or the acknowledgment record are optionally encrypted before transmission to the block chain, the user transmits an unencrypted acknowledgment record to the verifier and the verifier performs its verifications using the data in the unencrypted acknowledgment record. In an example embodiment, these verifications include checking that an acknowledgment record in fact exists in the block chain with the transaction number for the signed acknowledgment record. Also, in an example embodiment, the unencrypted acknowledgment record includes the transaction number of the signed certification record along with other unencrypted data from the certification record. Using the transaction number for the signed certification and the unencrypted data from the certification record, the verifier can confirm that the certification record in fact exists on the block chain and can process the unencrypted data in the certification record to verify the certifier's signature, even if the certification record was also encrypted before transmission to the block chain.
- A User may generate any type of data (UGD) and have that data Certified by a third party (Certifier). There are no limitations as to the type of data generated. The data can be any of the following types, but not limited only to these types of data: 1) a simple text string; 2) a date; 3) an enumerated data type; 4) a number; 5) an arbitrary series of data bytes (e.g., a data block).
- For distinction, the data types would have a name associated with them, so they appear in the form: Name=Value.
- This data would be saved locally on the Users' mobile App. The User would then Seal her record by writing this data to the blockchain. This can be done by either inserting a new Seal record with the added user generated data that overwrites any previous Seal (if any), or a new Seal that complements any prior Seals.
- The value field written to the block chain is for validation of the original data only. The user is expected to hold onto that data and only share it when the user chooses to. Hence, the data is first hashed so the UGD becomes <hash.UGD>. Any number of hashing algorithms can be used such as SHA256. The user then signs the <hash.UGD> with its private key producing <signed.hash.UGD>. This becomes the value that is then written to the blockchain in the form: Name=<signed.hash.UGD>.
- Once the record is sealed, the User may then present the UGD (maintained by the User or another device storage of his/her choosing), along with her public-key and a pointer to the Seal record on the blockchain to another party.
- The other party (the Certifier) can then get the hash value of the UGD by hashing the data with the same algorithm. This produces <hash.UGD>. The Certifier can then use <hash.UGD>, the users' public-key and the <signed.hash.UGD> pointed to on the blockchain to confirm that the data given to it is what was Sealed on the blockchain.
- The Certifier can then inspect the UGD in its clear form for authenticity, approval, or agreement.
- If the Certifier chooses to, it may then certify that data. To Certify that record, it uses methods previously described to uniquely certify the <signed.hash.UGD>. By doing so, at any point in the future, the user may present the UGD along with a pointer to its Sealed record and the Certified record along with its public-key to the Certifier or any other third party. To the degree that these parties trust the original Certifier who certified the record, the third party or the Certifier can validate the certification and matching of the UGD to the signature on the blockchain and feel comfortable to use the UGD without separately authenticating, approving, or agreeing to the data. The UGD was previously authenticated, approved or agreed to by the Certifier, a trusted party.
- The contents of the UGD may now be used for additional activities. If the UGD is a contract, its content can be trusted to the degree that the Certification attests to it. The UGD may be biometric data such as a fingerprint, facial image, iris-scan, voice, DNA-data or other biometric data. If the Certification represented a relationship of that data to the user, the third party presented with the data and the Certification can trust that association to the degree that it trusts the Certifier.
- For example, if a government agency Certifies a users' UGD (that is a biometric data) as association of that biometric data with the given User, the User can later present that same UGD to the same government agency or anyone else who accepts that government agency's certification process (the Verifier). The Verifier can now capture a new biometric from the same person (e.g., capture a new finger print, a new facial image, a new DNA-sample, a new iris-scan, a new voice-sample, or other biometric data) and compare it with the UGD that the User presented. If the two match, the Verifier can be assured that this is the same individual as the person who was previous Certified by the government agency. This not only validates the Users' digital id presented, but also the physical person who just presented that.
- Similar evaluations can be done with the UGD, if it is any other data such as a date, a simple text-string, an enumerated data-type, a number, or any arbitrary set of data bytes.
-
FIGS. 4A-4C combined illustrate in more detail the process for certifying user generated biometric data as described above, in accordance with embodiments of the present disclosure. In particular,FIG. 4A-4C are data flow diagrams illustrating the certification of user generated biometric data. Participants (e.g., devices, systems, etc.) includeuser 405,certifier 420,verifier 430, andblockchain 450. -
FIG. 4A illustrates operations performed at theuser 405. At 451, user generated data (UGD) is captured. At 452, the UGD is hashed to generate: <hash.UGD>. Also, a signature of the hashed UGD is performed using the private key of the user to generate: <signed.hash.UGD>. At 453, to seal the signature of the hashed UGD, a seal name is delivered to the blockchain, wherein the seal name is the signature of the hashed UGD. At 454, a seal transaction identifier (“Seal txn-ID”) is returned to theuser 405 from theblockchain 450. -
FIG. 4B illustrates operations performed at thecertifier 420. At 461, the user presents to thecertifier 420 the user generated data (UGD), the public key of the user (PBK.user), and the seal transaction identifier (e.g., “Seal txn-ID”). At 462, thecertifier 420 gets the seal record from theblockchain 450 using the seal transaction identifier (e.g., “Seal txn-ID”). At 463, the seal record is returned to thecertifier 420 from theblockchain 450. At 464, from the seal record the signature of the hashed UGD (<signed.hash.UGD>) is extracted. A generated hash value (<hash.UGD>) is created by thecertifier 420 by performing a hash operation on the user generated data received from the user. In addition, the certifier verifies that the generated hash value (<hash.UGD>) matches the hash value in the signature of the hashed UGD (<signed.hash.UGD>) using in part the public key of the user. At 465, if the generated hash value is verified at 466, then the raw data of the user generated data (UGD) is checked for validation purposes. If the raw UGD is validated, then a certification signature of the seal transaction identifier (e.g., “Seal txn-ID”), and possibly other data, is generated using the private key of the certifier is generated (“CertSig”). Also, a certification record (“CertRecord”) is generated by signing the certifier seal transaction identifier, the seal transaction identifier, and possibly other information such as the field=name, and CertSig. Thereafter, a certification is performed. In particular, the certification record is written and/or sealed to the blockchain at 466. At 467, a certification record transaction identifier (“CertRecord txn-ID”) is returned to thecertifier 420. At 468, the certification record transaction identifier (“CertRecord txn-ID”) is delivered to theuser 405. -
FIG. 4C illustrates operations performed at theverifier 430. At 471, theuser 405 presents to theverifier 430 the user generated data (UGD), the public key of the user, the seal transaction identifier (Seal txn-ID), and the certification record transaction identifier (“CertRecord txn-ID”). At 472, theverifier 430 then presents the seal transaction identifier (Seal txn-ID) and the certification record transaction identifier (“CertRecord txn-ID”) to theblockchain 450 to retrieve the sealed records. At 473, theblockchain 450 delivers to theverifier 430 the seal record (“SealRecord”) and the certification record (“CertRecord”) stored to the blockchain. At 474 the verifier extracts the signed hash of the user generated data. The verifier also hashes the user generated data by performing a hash algorithm on the UGD to create a generated hash value (<hash.UGD>). Also, theverifier 430 verifies that the generated hash value (<hash.UGD>) matches the hash value in the signature of the hashed UGD (<signed.hash.UGD>) from the seal record (“SealRecord”) using in part the public key of the user. At 475, if the generated hash value is verified, then theverifier 430 may retrieve the sealed certification record using the certifier seal transaction identifier (“certifier Seal txn-ID”). At 476, the sealed certification record (Certifier Seal Record) is returned to theverifier 430 from theblockchain 450. At 477, theverifier 430 verifies that the information in the sealed certification record matches presented data. For example, the certification signature (CertSig) in the sealed certification record is verified against newly presented CertSig data. At 478, if the data is verified, then theverifier 430 verifies that the user generated data (UGD) is sealed and certified by thecertifier 420. - It is possible to provide the secure exchange of data described in the prior section by using a server. This can be handy if it is not feasible to exchange large data sets between two users. For example, User A may be on a mobile device and user B may be also on a mobile device or even interact via a web page. The two users in this case cannot exchange data directly without having a communication path. One way, they can share data is through digital codes such as a bar-code, a QR code, pdf-417-code or any other similar type of displayable codes. This section describes how variable sizes of data blocks (potentially very large data blocks) can be securely exchanged between such two parties by utilizing a server in the middle. This description outlines a method where the server stores and directs the messages for the two parties, but is unable to ever read any of its content, in one embodiment. The server in the middle is depicted by the name “Store” 520 in this description, but it can be any server.
- The assumption in this exchange is that the two users already know one another and are aware of each others' SealId, and ultimately each other public keys that are associated with corresponding private keys they have used to Seal their identification.
- User A intends to send a block of data to user B. User A places that data in a data block and may add additional identification fields to that block of data such as timestamp, its own
- SealId, User B's SealId, its public key and if there is a session between the two, a sessionId. The value of the timestamp and the sessionId is to ensure vitality of the data block versus one that may have been created and somehow reused again. This data block will be referred to as <dataBlock>.
- Next, User A uses its own private key to digitally sign the <dataBlock> that was created. The result is <envelopeSignature>. Next, an <envelopeContent> is created by putting together the <dataBlock> and the <envelopeSignature>. Last, a <secureEnvelope> is created by encrypting the <envelopeContent> with User B's public key.
- Once a <secureEnvelope> is created by User A, the <secureEnvelope> is sent to Store. Store creates a unique <messageId> that is associated with the <secureEnvelope> and it returns that id to User A.
- User A then relays the <messageId> and possibly the address of the Store server (if not a well known server service between the two Users) to User B. This data is rather short and can easily fit in nearly digital codes such as a bar code, a QR code, pdf-417-code and the like. User B receives the data in some form, such as scanning the code from the mobile screen of User A and then sends a message to Store to get the <secureEnvelope> associated with the <messageId>. Store returns the associated <secureEnvelope>. If the protocol requires that the transmission be a onetime process, the <secureEnvelope> can be deleted after a successful transmission. It is also possible to delete the envelope if an expiration time is associated with it.
- This secure envelope can now be transmitted to user B from the store. User B can view the <envelopeContent> by decrypting the <secureEnvelope> using his private key that no one else is aware of. It may then verify the <dataBlock> in the envelope content by verifying the <dataBlock> and the <envelopeSignature> with the user A's public key that was passed. It may also verify that this is the same public key that was used in user A's SealId.
- There is no restriction as to how User A passes the secure envelope to User B. It can be done via email, a text message, NFC, or any other form of digital communication where the data can be passed. Because it is encrypted using User B's public key, only User B can view the message and no other use can modify it either. In fact, after the secure envelope is created, even User A can no longer view its content, in one embodiment.
-
FIG. 5 in more detail shows the exchange of data securely via a Secure Envelope between two users via a server as described above, in accordance with one embodiment of the present disclosure. The secure envelope exchange disclosed inFIG. 5 includes participants: User A, User B, andStore 520. The assumption in this exchange is that the two Users A and B already know one another and are aware of each others' SealId (e.g., “SealID.userA” and “SealID.userB”), and may be obtained from seal records on a corresponding blockchain. - At 531, user A creates a data block <dataBlock> to include: the data to be exchanged, a timestamp, the seal identifier of user A (SealID.userA), the seal identifier of user B (SealID.userB), a session identifier (sessionID) if available, and the public key of user A.
- At 532, user A signs the data block using the private key of user A to generate an envelope signature <envelopeSignature>. Also, an envelope <EnvelopeContent> is generated having contents including the data block and the envelope signature <envelopeSignature>. A secure envelope <secureEnvelope> may be generated by encrypting the contents of the envelope <EnvelopeContent> using the public key of user B.
- At 533, user A sends the secure envelope <secureEnvelope> to store 520. At 534,
store 520 may create a unique message identifier <messageID> to be used as an index for accessing the secure envelope <secureEnvelope>. At 535, the message identifier <messageID> is delivered fromstore 520 to user A. - At 536, the message identifier <messageID> is delivered from user A to user B. at 537, user B accesses the secure envelope <secureEnvelope> by sending message identifier <messageID> to store 520. At 538 the secure envelope <secureEnvelope> is delivered from
store 520 to user B. At 539, the secure envelope <secureEnvelope> may be removed fromstore 520 if it generated for purposes of a one-time use. - At 540, user B extracts the contents of the secure envelope <secureEnvelope> by decrypting the secure envelope <secureEnvelope> using the private key of user B. The data block that is extracted is verified using the envelope signature <envelopeSignature> and the public key of user A.
- It should be understood that the embodiments and described use cases herein are only by way of example. Many new use cases can be encompassed and facilitated by the functionality described herein. For instance, identity verification can be integrated into various commercial applications, as well as private applications. Commercial applications may include those that require commercial entities to verify a user's identity. Verifying a user's identity can be required for achieving any number of functions, such as traveling, making transactions, banking, communication, loan verification, credit verification, purchase verification, and other uses. Private identity verification can also be facilitated using the methods, apparatus, computer readable media, and systems described herein. Private identity verification may be useful when a user wishes to prove to another user their identity, in a fast and efficient manner. The systems described herein, as described above, utilize methods that write data to the block chain database, which is non-rewritable and permanently maintains the record without compromise. This enables writing of information to the block chain in a manner that can be verified by one or more transactions executed by methods of the present inventions.
- Additionally, the method operations described herein may be executed with any number of computer systems. By way of example, the computer systems may include user devices, such as mobile phones, tablets, desktop computers, watch computers, head attached computers, eyeglasses computers, or combinations thereof. Server operations may also be performed and communicated between client devices, to facilitate transactions with the block chain database, server storage, and the like. By way of example, these computer devices can communicate over networks, such as the Internet. The networks enable individual devices to transact with each other, such as by way of sending, receiving, and processing exchanged information. The exchanged information can include different types of encrypted data, hashed data, envelopes, codes, QR codes, messages, notifications, and other types of data.
- The messaging and communication functions are provided to enable users to exchange data in order to verify identity, or enable or provide access to users to services, goods, or commercial transactions. In the case of banking operations, the verification process can be utilized by banks, as well as users of the bank or third parties that require certified information from the banks regarding users. In the case of travel type verifications, different travel entities can require identification of users, and that the identification be verified by themselves or by other third parties that are trusted. These operations can be facilitated using the systems, methods, computer readable media, and code that execute the verification processes. Broadly speaking, verification of a user identity can be useful in any type of industry, or private setting. The use of verification is simply facilitated by using the verifying infrastructure, programs code, applications, and combinations thereof, to ensure that verification is secure.
- In some embodiments, the verification systems can be embodied in an application, such as those that can be installed on mobile devices (e.g., Apps). By way of example, users wishing to have their identity verified can use an App to seal information regarding their identity. Once the data has been sealed, and encrypted data has been stored to the block chain, this data can be used for later certification by another party. The other party may also be utilizing a corresponding App, which enables efficient reading of the data, code, QR code, message, or notification, to validate the identity of the user.
- In still other embodiments, code plug-ins can be integrated into commercial websites, which may use identity verification for different reasons or functions. For example, banks can install plug-in applications, code, or programs that can execute part or all of the verification processing to seal information and/or to certify information regarding identity. In view of the foregoing, it should be understood that the verifying processes described herein and the various use cases are only by way of example, and additional use cases will be evident to those skilled in the art.
- In an example embodiment, a method is described. According to the method, logic on a remote device causes the capture of personal data identifying a user from an identification card. The remote device supports a user-accessible interface. The logic generates a hash value from the personal data using a hashing algorithm and signs the hash value with a digital signature created using a private key paired with a public key. Then the logic transmits, over a network, the signed hash value and the public key from the remote device to a distributed public database for storage. The logic then receives, over the network, a transaction number from the distributed public database and, transmits using the user-accessible interface, the transaction number and the personal data to a remote device of a third party for certification and/or verification.
- In another example embodiment, another method is described. According to the method, logic on a first remote device causes the capture of personal data identifying a user from an identification card. The first remote device supports a user-accessible interface. The logic generates a hash value from the personal data using a hashing algorithm and signs the hash value with a digital signature created using a first private key paired with a first public key. Then the logic transmits, over a network, the signed hash value and the first public key from the remote device to a distributed public database for storage. The logic then receives, over the network, a first transaction number from the distributed public database.
- The logic then transmits the first transaction number and the personal data to a second remote device, wherein logic on the second remote device (a) uses the first transaction number to retrieve the signed hash value and the first public key from the distributed public database, (b) hashes the personal data using the hashing algorithm to create a generated hash value, (c) verifies that the hash value in the signed hash value is the same as the generated hash value, (d) verifies that the signed hash value was signed with the first private key, and (c) creates a certification.
- In another example embodiment, another method is described. According to the method, logic on a first smartphone causes the capture of personal data identifying a user from an identification card. The logic generates a hash value from the personal data using a hashing algorithm and signs the hash value with a digital signature created using a first private key paired with a first public key. Then the logic transmits, over a network, the signed hash value and the first public key from the remote device to a block chain database for storage. The logic then receives, over the network, a first transaction number from the block chain database.
- The logic then transmits the first transaction number and the personal data to a second smartphone, wherein logic on the second smartphone (a) uses the first transaction number to retrieve the signed hash value and the first public key from the block chain database, (b) hashes the personal data using the hashing algorithm to create a generated hash value, (c) verifies that the hash value in the signed hash value is the same as the generated hash value, (d) verifies that the signed hash value was signed with the first private key, and (c) creates a certification.
- Other aspects and advantages of the inventions will become apparent from the detailed description, taken in conjunction with the accompanying drawings, which illustrate by way of example the principles of the inventions.
- The various embodiments defined herein may define individual implementations or can define implementations that rely on combinations of one or more of the defined embodiments. Further, embodiments of the present invention may be practiced with various computer system configurations including hand-held devices, microprocessor systems, microprocessor-based or programmable consumer electronics, minicomputers, mainframe computers and the like. The invention can also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a wire-based or wireless network.
- Any of the operations described herein that form part of the invention are useful machine operations. The invention also relates to a device or an apparatus for performing these operations. The apparatus can be specially constructed for the required purpose, or the apparatus can be a general-purpose computer selectively activated or configured by a computer program stored in the computer. In particular, various general-purpose machines can be used with computer programs written in accordance with the teachings herein, or it may be more convenient to construct a more specialized apparatus to perform the required operations.
- The invention can also be embodied as computer readable code on a computer readable medium. The computer readable medium is any data storage device that can store data, which can thereafter be read by a computer system. The computer readable medium can also be distributed over a network-coupled computer system so that the computer readable code is stored and executed in a distributed fashion.
- Having provided this detailed description, it will be apparent that modifications and variations are possible without departing from the scope of the invention defined in the appended claims. When introducing elements of the present invention or the preferred embodiments(s) thereof, the articles “a”, “an”, “the” and “said” are intended to mean that there are one or more of the elements. The terms “comprising”, “including” and “having” are intended to be inclusive and mean that there may be additional elements other than the listed elements. In view of the above, it will be seen that the several objects of the invention are achieved and other advantageous results attained. As various changes could be made in the above systems without departing from the scope of the invention, it is intended that all matter contained in the above description and shown in the accompanying drawings shall be interpreted as illustrative and not in a limiting sense.
- With the above embodiments in mind, it should be understood that the inventions might employ various computer-implemented operations involving data stored in computer systems. Any of the operations described herein that form part of the inventions are useful machine operations. The inventions also relate to a device or an apparatus for performing these operations. The apparatus may be specially constructed for the required purposes, such as the carrier network discussed above, or it may be a general purpose computer selectively activated or configured by a computer program stored in the computer. In particular, various general purpose machines may be used with computer programs written in accordance with the teachings herein, or it may be more convenient to construct a more specialized apparatus to perform the required operations.
- The inventions can also be embodied as computer readable code on a computer readable medium. The computer readable medium is any data storage device that can store data, which can thereafter be read by a computer system. Examples of the computer readable medium include hard drives, network attached storage (NAS), read-only memory, random-access memory, CD-ROMs, CD-Rs, CD-RWs, DVDs, Flash, magnetic tapes, and other optical and non-optical data storage devices. The computer readable medium can also be distributed over a network coupled computer systems so that the computer readable code is stored and executed in a distributed fashion.
- Although example embodiments of the inventions have been described in some detail for purposes of clarity of understanding, it will be apparent that certain changes and modifications can be practiced within the scope of the following claims. For example, the web site might host an online retailer or an online publication, instead of a connected-television service. Moreover, the operations described above can be ordered, modularized, and/or distributed in any suitable way. Accordingly, the present embodiments are to be considered as illustrative and not restrictive, and the inventions are not to be limited to the details given herein, but may be modified within the scope and equivalents of the following claims. In the following claims, elements and/or steps do not imply any particular order of operation, unless explicitly stated in the claims or implicitly required by the disclosure.
Claims (23)
Priority Applications (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US17/691,597 US20220337419A1 (en) | 2015-05-05 | 2022-03-10 | Systems, apparatus and methods for secure electrical communication of biometric personal identification information to validate the identity of an individual |
US17/738,106 US11544367B2 (en) | 2015-05-05 | 2022-05-06 | Systems, apparatus and methods for secure electrical communication of biometric personal identification information to validate the identity of an individual |
US18/068,083 US20230196362A1 (en) | 2015-05-05 | 2022-12-19 | Systems, apparatus and methods for secure electrical communication of biometric personal identification information to validate the identity of an individual |
Applications Claiming Priority (6)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US201562157256P | 2015-05-05 | 2015-05-05 | |
US201662304934P | 2016-03-07 | 2016-03-07 | |
US15/146,872 US10007913B2 (en) | 2015-05-05 | 2016-05-04 | Identity management service using a blockchain providing identity transactions between devices |
US16/018,773 US20180308098A1 (en) | 2015-05-05 | 2018-06-26 | Identity Management Service Using A Block Chain Providing Identity Transactions Between Devices |
US202117514667A | 2021-10-29 | 2021-10-29 | |
US17/691,597 US20220337419A1 (en) | 2015-05-05 | 2022-03-10 | Systems, apparatus and methods for secure electrical communication of biometric personal identification information to validate the identity of an individual |
Related Parent Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US202117514667A Continuation | 2015-05-05 | 2021-10-29 |
Related Child Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US17/738,106 Continuation US11544367B2 (en) | 2015-05-05 | 2022-05-06 | Systems, apparatus and methods for secure electrical communication of biometric personal identification information to validate the identity of an individual |
Publications (1)
Publication Number | Publication Date |
---|---|
US20220337419A1 true US20220337419A1 (en) | 2022-10-20 |
Family
ID=57218599
Family Applications (8)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US15/146,881 Active US9722790B2 (en) | 2015-05-05 | 2016-05-04 | Identity management service using a blockchain providing certifying transactions between devices |
US15/146,872 Active US10007913B2 (en) | 2015-05-05 | 2016-05-04 | Identity management service using a blockchain providing identity transactions between devices |
US15/640,795 Active 2036-11-24 US10657532B2 (en) | 2015-05-05 | 2017-07-03 | Identity management service using a blockchain providing certifying transactions between devices |
US16/018,773 Abandoned US20180308098A1 (en) | 2015-05-05 | 2018-06-26 | Identity Management Service Using A Block Chain Providing Identity Transactions Between Devices |
US17/121,971 Abandoned US20210334808A1 (en) | 2015-05-05 | 2020-12-15 | Identity management service using a blockchain providing certifying transactions between devices |
US17/691,597 Abandoned US20220337419A1 (en) | 2015-05-05 | 2022-03-10 | Systems, apparatus and methods for secure electrical communication of biometric personal identification information to validate the identity of an individual |
US17/738,106 Active US11544367B2 (en) | 2015-05-05 | 2022-05-06 | Systems, apparatus and methods for secure electrical communication of biometric personal identification information to validate the identity of an individual |
US18/068,083 Pending US20230196362A1 (en) | 2015-05-05 | 2022-12-19 | Systems, apparatus and methods for secure electrical communication of biometric personal identification information to validate the identity of an individual |
Family Applications Before (5)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US15/146,881 Active US9722790B2 (en) | 2015-05-05 | 2016-05-04 | Identity management service using a blockchain providing certifying transactions between devices |
US15/146,872 Active US10007913B2 (en) | 2015-05-05 | 2016-05-04 | Identity management service using a blockchain providing identity transactions between devices |
US15/640,795 Active 2036-11-24 US10657532B2 (en) | 2015-05-05 | 2017-07-03 | Identity management service using a blockchain providing certifying transactions between devices |
US16/018,773 Abandoned US20180308098A1 (en) | 2015-05-05 | 2018-06-26 | Identity Management Service Using A Block Chain Providing Identity Transactions Between Devices |
US17/121,971 Abandoned US20210334808A1 (en) | 2015-05-05 | 2020-12-15 | Identity management service using a blockchain providing certifying transactions between devices |
Family Applications After (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US17/738,106 Active US11544367B2 (en) | 2015-05-05 | 2022-05-06 | Systems, apparatus and methods for secure electrical communication of biometric personal identification information to validate the identity of an individual |
US18/068,083 Pending US20230196362A1 (en) | 2015-05-05 | 2022-12-19 | Systems, apparatus and methods for secure electrical communication of biometric personal identification information to validate the identity of an individual |
Country Status (6)
Country | Link |
---|---|
US (8) | US9722790B2 (en) |
EP (2) | EP3292484B1 (en) |
JP (1) | JP2018516030A (en) |
CN (1) | CN107851111A (en) |
CA (1) | CA2984888A1 (en) |
WO (1) | WO2016179334A1 (en) |
Cited By (7)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US11652644B1 (en) * | 2018-03-09 | 2023-05-16 | Wells Fargo Bank, N.A. | Quantum-resistant double signature system |
US11658961B2 (en) | 2016-03-04 | 2023-05-23 | Ping Identity Corporation | Method and system for authenticated login using static or dynamic codes |
US11722301B2 (en) | 2018-10-17 | 2023-08-08 | Ping Identity Corporation | Blockchain ID connect |
US11777726B2 (en) | 2017-12-08 | 2023-10-03 | Ping Identity Corporation | Methods and systems for recovering data using dynamic passwords |
US11799668B2 (en) | 2017-02-06 | 2023-10-24 | Ping Identity Corporation | Electronic identification verification methods and systems with storage of certification records to a side chain |
US11818265B2 (en) | 2018-10-17 | 2023-11-14 | Ping Identity Corporation | Methods and systems for creating and recovering accounts using dynamic passwords |
USRE49968E1 (en) | 2017-02-06 | 2024-05-14 | Ping Identity Corporation | Electronic identification verification methods and systems with storage of certification records to a side chain |
Families Citing this family (529)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US9185095B1 (en) | 2012-03-20 | 2015-11-10 | United Services Automobile Association (Usaa) | Behavioral profiling method and system to authenticate a user |
US9553982B2 (en) * | 2013-07-06 | 2017-01-24 | Newvoicemedia, Ltd. | System and methods for tamper proof interaction recording and timestamping |
US10320781B2 (en) * | 2016-12-08 | 2019-06-11 | Sensoriant, Inc. | System and methods for sharing and trading user data and preferences between computer programs and other entities while preserving user privacy |
US9973341B2 (en) * | 2015-01-23 | 2018-05-15 | Daniel Robert Ferrin | Method and apparatus for the limitation of the mining of blocks on a block chain |
US9965628B2 (en) | 2015-03-02 | 2018-05-08 | Dell Products Lp | Device reporting and protection systems and methods using a secure distributed transactional ledger |
US10484168B2 (en) | 2015-03-02 | 2019-11-19 | Dell Products L.P. | Methods and systems for obfuscating data and computations defined in a secure distributed transaction ledger |
US9967333B2 (en) * | 2015-03-02 | 2018-05-08 | Dell Products Lp | Deferred configuration or instruction execution using a secure distributed transaction ledger |
US9967334B2 (en) * | 2015-03-02 | 2018-05-08 | Dell Products Lp | Computing device configuration and management using a secure decentralized transaction ledger |
US10592985B2 (en) | 2015-03-02 | 2020-03-17 | Dell Products L.P. | Systems and methods for a commodity contracts market using a secure distributed transaction ledger |
US10979410B1 (en) | 2015-05-04 | 2021-04-13 | United Services Automobile Association (Usaa) | Systems and methods for utilizing cryptology with virtual ledgers in support of transactions and agreements |
CN107851111A (en) | 2015-05-05 | 2018-03-27 | 识卡公司 | Use the identity management services of block chain |
US11232415B2 (en) * | 2015-05-28 | 2022-01-25 | OX Labs Inc. | Method for cryptographically managing title transactions |
US9904544B2 (en) * | 2015-06-08 | 2018-02-27 | Ripple Luxembourg S.A. | System and method for determining that results produced from executions of software have not been altered or falsified |
KR101680540B1 (en) * | 2015-06-18 | 2016-11-30 | 주식회사 코인플러그 | Financial institution document verification system that is based on the block chain |
US10997570B1 (en) | 2015-07-10 | 2021-05-04 | Wells Fargo Bank, N.A. | Context-aware, vehicle-based mobile banking |
US11188907B1 (en) | 2015-08-21 | 2021-11-30 | United Services Automobile Association (Usaa) | ACH authorization validation using public blockchains |
US11195177B1 (en) | 2015-08-21 | 2021-12-07 | United Services Automobile Association (Usaa) | Distributed ledger systems for tracking recurring transaction authorizations |
JP6951329B2 (en) | 2015-10-14 | 2021-10-20 | ケンブリッジ ブロックチェーン,エルエルシー | Systems and methods for managing digital identities |
US10298396B1 (en) * | 2015-11-10 | 2019-05-21 | Wells Fargo Bank, N.A. | Identity management service via virtual passport |
US20170132615A1 (en) * | 2015-11-11 | 2017-05-11 | Bank Of America Corporation | Block chain alias for person-to-person payments |
US10949856B1 (en) | 2015-11-17 | 2021-03-16 | United Services Automobile Association (Usaa) | Systems and methods for adaptive learning to replicate peak performance of human decision making |
US11361286B1 (en) | 2015-11-20 | 2022-06-14 | United Services Automobile Association (Usaa) | Identifying negotiable instrument fraud using distributed ledger systems |
US10423938B1 (en) | 2015-11-20 | 2019-09-24 | United Services Automobile Association | Identifying negotiable instrument fraud using distributed ledger systems |
US10164973B1 (en) | 2015-12-02 | 2018-12-25 | United Services Automobile Association (Usaa) | Public authentication systems and methods |
US10833843B1 (en) | 2015-12-03 | 2020-11-10 | United Services Automobile Association (USAA0 | Managing blockchain access |
US10521780B1 (en) * | 2015-12-16 | 2019-12-31 | United Services Automobile Association (Usaa) | Blockchain based transaction management |
US10824983B1 (en) | 2015-12-18 | 2020-11-03 | Wells Fargo Bank, N.A. | Systems and methods for tracking-based transactions |
EP3394779B1 (en) | 2015-12-22 | 2021-11-03 | Financial & Risk Organisation Limited | Methods and systems for identity creation, verification and management |
US11374935B2 (en) | 2016-02-11 | 2022-06-28 | Bank Of America Corporation | Block chain alias person-to-person resource allocation |
US11416849B1 (en) | 2016-02-19 | 2022-08-16 | Wells Fargo Bank, N.A. | Systems and methods for sending and receiving math-based currency via a fiat currency account |
US10454677B1 (en) | 2016-02-24 | 2019-10-22 | United Services Automobile Associate (USAA) | Cryptographic key generation from biometric data |
US10007826B2 (en) | 2016-03-07 | 2018-06-26 | ShoCard, Inc. | Transferring data files using a series of visual codes |
US10509932B2 (en) | 2016-03-07 | 2019-12-17 | ShoCard, Inc. | Large data transfer using visual codes with feedback confirmation |
US10091003B2 (en) * | 2016-03-18 | 2018-10-02 | Adobe Systems Incorporated | Mobile signature embedded in desktop workflow |
US11120507B2 (en) | 2016-04-14 | 2021-09-14 | Sensoriant, Inc. | Confirmation and rating of user generated activities |
KR101766303B1 (en) * | 2016-04-19 | 2017-08-08 | 주식회사 코인플러그 | Method for creating, registering, revoking certificate information and server using the same |
US10853804B1 (en) | 2016-04-22 | 2020-12-01 | Wells Fargo Bank, N.A. | Dynamic transaction token/dynamic pricing based on conditions of order |
KR101780635B1 (en) * | 2016-04-28 | 2017-09-21 | 주식회사 코인플러그 | Method for creating, registering, revoking certificate information and server using the same |
US10333705B2 (en) | 2016-04-30 | 2019-06-25 | Civic Technologies, Inc. | Methods and apparatus for providing attestation of information using a centralized or distributed ledger |
US10489278B2 (en) * | 2016-05-16 | 2019-11-26 | Jpmorgan Chase Bank, N.A. | Method and system for implementing an automation software testing and packaging framework with entitlements |
US10838846B1 (en) | 2016-05-16 | 2020-11-17 | Jpmorgan Chase Bank, N.A. | Method and system for implementing an automation software testing and packaging framework |
US9635000B1 (en) * | 2016-05-25 | 2017-04-25 | Sead Muftic | Blockchain identity management system based on public identities ledger |
US10104055B2 (en) * | 2016-05-27 | 2018-10-16 | David Joseph Ponder | System and process of protecting client side information in electronic transactions |
US10469487B1 (en) | 2016-05-31 | 2019-11-05 | Wells Fargo Bank, N.A. | Biometric electronic signature authenticated key exchange token |
US10154029B1 (en) | 2016-05-31 | 2018-12-11 | Wells Fargo Bank, N.A. | Biometric knowledge extraction for mutual and multi-factor authentication and key exchange |
US11405387B1 (en) | 2016-05-31 | 2022-08-02 | Wells Fargo Bank, N.A. | Biometric electronic signature authenticated key exchange token |
CN108780390B (en) | 2016-06-06 | 2022-09-27 | 金融与风险组织有限公司 | System and method for providing identity scores |
US20170357522A1 (en) * | 2016-06-10 | 2017-12-14 | Lenovo Enterprise Solutions (Singapore) Pte. Ltd. | System, method, and computer program for controlling configuration implementation |
US10341309B1 (en) * | 2016-06-13 | 2019-07-02 | Allstate Insurance Company | Cryptographically protecting data transferred between spatially distributed computing devices using an intermediary database |
US10142333B1 (en) | 2016-06-21 | 2018-11-27 | Wells Fargo Bank, N.A. | Biometric reference template record |
US10572641B1 (en) | 2016-06-21 | 2020-02-25 | Wells Fargo Bank, N.A. | Dynamic enrollment using biometric tokenization |
US10193884B1 (en) | 2016-06-21 | 2019-01-29 | Wells Fargo Bank, N.A. | Compliance and audit using biometric tokenization |
US10411905B2 (en) * | 2016-07-01 | 2019-09-10 | Intel Corporation | Public key infrastructure using blockchains |
JP2019525303A (en) * | 2016-07-01 | 2019-09-05 | ウェルズ・ファーゴ・バンク・ナショナル・アソシエーション | International Trade Finance Blockchain System |
US11854011B1 (en) | 2016-07-11 | 2023-12-26 | United Services Automobile Association (Usaa) | Identity management framework |
US10402796B2 (en) | 2016-08-29 | 2019-09-03 | Bank Of America Corporation | Application life-cycle transition record recreation system |
US11568388B1 (en) | 2016-09-21 | 2023-01-31 | Wells Fargo Bank, N.A. | Systems and methods for transferring fiat currency via mapped math-based currency accounts |
US10587628B2 (en) * | 2016-09-29 | 2020-03-10 | Microsoft Technology Licensing, Llc | Verifiable outsourced ledgers |
US10749684B2 (en) | 2016-09-30 | 2020-08-18 | Entrust, Inc. | Methods and apparatus for providing blockchain participant identity binding |
US11769146B1 (en) * | 2016-09-30 | 2023-09-26 | Hrb Innovations, Inc. | Blockchain transactional identity verification |
EP3523744B1 (en) * | 2016-10-06 | 2021-04-07 | Mastercard International Incorporated | Method and system for identity and credential protection and verification via blockchain |
US11258587B2 (en) * | 2016-10-20 | 2022-02-22 | Sony Corporation | Blockchain-based digital rights management |
US10277400B1 (en) | 2016-10-20 | 2019-04-30 | Wells Fargo Bank, N.A. | Biometric electronic signature tokens |
US10547457B1 (en) | 2016-10-21 | 2020-01-28 | Wells Fargo Bank N.A. | Systems and methods for notary agent for public key infrastructure names |
JP6149324B1 (en) * | 2016-10-24 | 2017-06-21 | ミミワークス株式会社 | Profile information exchange system |
US20180343120A1 (en) * | 2016-10-26 | 2018-11-29 | Black Gold Coin, Inc. | Systems and methods for providing a universal decentralized solution for verification of users with cross-verification features |
US10749681B2 (en) * | 2016-10-26 | 2020-08-18 | Black Gold Coin, Inc. | Systems and methods for providing a universal decentralized solution for verification of users with cross-verification features |
US10484178B2 (en) | 2016-10-26 | 2019-11-19 | Black Gold Coin, Inc. | Systems and methods for providing a universal decentralized solution for verification of users with cross-verification features |
US10516538B2 (en) * | 2016-11-01 | 2019-12-24 | Netcomm Inc. | System and method for digitally signing documents using biometric data in a blockchain or PKI |
DE102016221699A1 (en) * | 2016-11-04 | 2018-05-09 | Bundesdruckerei Gmbh | Procedure for issuing a virtual version of a document |
US20180130034A1 (en) * | 2016-11-07 | 2018-05-10 | LedgerDomain, LLC | Extended blockchains for event tracking and management |
US11070378B1 (en) | 2016-11-07 | 2021-07-20 | Wells Fargo Bank, N.A. | Signcrypted biometric electronic signature tokens |
CN108075895B (en) * | 2016-11-15 | 2020-03-24 | 深圳银链科技有限公司 | Node permission method and system based on block chain |
US11651360B2 (en) * | 2016-11-21 | 2023-05-16 | Kyndryl, Inc. | Triggering actions responsive to blockchain transactions |
CN106991334B (en) | 2016-11-24 | 2021-03-02 | 创新先进技术有限公司 | Data access method, system and device |
CN106789920A (en) * | 2016-11-25 | 2017-05-31 | 深圳前海微众银行股份有限公司 | The joint connecting method and device of block chain |
DE102016123019A1 (en) * | 2016-11-29 | 2018-07-05 | Infineon Technologies Ag | A method for electronically initiating an action and an electronic system for electronically initiating an action |
CN106534160B (en) * | 2016-12-02 | 2020-02-21 | 江苏通付盾科技有限公司 | Identity authentication method and system based on block chain |
CN107016542A (en) * | 2016-12-06 | 2017-08-04 | 阿里巴巴集团控股有限公司 | A kind of business data processing method, verification method, apparatus and system |
JP6775086B2 (en) * | 2016-12-16 | 2020-10-28 | 株式会社日立製作所 | Blockchain monitoring and management |
DK3340212T3 (en) * | 2016-12-21 | 2020-02-17 | Merck Patent Gmbh | READER UNIT FOR READING A COMPOSITION MARKING INCLUDING A PHYSICAL NON-CLONABLE FUNCTION FOR THE FIGHT AGAINST FALSE |
EP3560136B1 (en) | 2016-12-22 | 2020-12-02 | Itext Group NV | Distributed blockchain-based method for saving the location of a file |
BE1024386B1 (en) * | 2016-12-22 | 2018-02-05 | Itext Group Nv | Distributed blockchain-based method for jointly signing a PDF-based document by multiple parties |
BE1024384B9 (en) * | 2016-12-22 | 2018-03-23 | Itext Group Nv | Distributed blockchain-based method for digitally signing a PDF-based document |
BE1024381B1 (en) * | 2016-12-22 | 2018-02-05 | Itext Group Nv | Distributed blockchain-based method for maintaining the validity of a file |
WO2018114585A1 (en) | 2016-12-22 | 2018-06-28 | Itext Group Nv | Improved blockchain-based method for registration and verification of a file |
GB2573666A (en) * | 2016-12-23 | 2019-11-13 | Walmart Apollo Llc | Verifying authenticity of computer readable information using the blockchain |
US11115418B2 (en) * | 2016-12-23 | 2021-09-07 | Cloudminds (Shanghai) Robotics Co., Ltd. | Registration and authorization method device and system |
US11190360B2 (en) * | 2016-12-23 | 2021-11-30 | Cloudminds (Shanghai) Robotics Co., Ltd. | Method, apparatus, node, signature device and system for generating block of blockchain |
US10715331B2 (en) * | 2016-12-28 | 2020-07-14 | MasterCard International Incorported | Method and system for providing validated, auditable, and immutable inputs to a smart contract |
CN106649838B (en) * | 2016-12-29 | 2020-10-30 | 成都质数斯达克科技有限公司 | Data transmission method, block chain node and distributed database |
KR102470727B1 (en) * | 2016-12-30 | 2022-11-25 | 비씨 디벨롭먼트 랩스 게엠베하 | Blockchain-enabled service provider system |
EP3566390B1 (en) | 2017-01-03 | 2020-12-02 | University Of Stavanger | User controlled, decentralized, distributed, and secure content distribution |
WO2018130994A1 (en) * | 2017-01-13 | 2018-07-19 | Hashkloud Pty Ltd | Data verification and authentication system and method |
CN106790234B (en) * | 2017-01-18 | 2018-09-04 | 维沃移动通信有限公司 | A kind of e-mail sending method, method of reseptance, first terminal and second terminal |
US10824747B1 (en) | 2017-01-25 | 2020-11-03 | State Farm Mutual Automobile Insurance Company | Systems and methods for controlled access to policy data on blockchain |
CN106850200B (en) * | 2017-01-25 | 2019-10-22 | 中钞***产业发展有限公司杭州区块链技术研究院 | A kind of safety method, system and the terminal of digital cash of the use based on block chain |
US10419225B2 (en) | 2017-01-30 | 2019-09-17 | Factom, Inc. | Validating documents via blockchain |
US11257070B2 (en) * | 2017-01-31 | 2022-02-22 | Nchain Licensing Ag | Computer-implemented system and method for generating and extracting user related data stored on a blockchain |
ZA201800647B (en) * | 2017-01-31 | 2019-01-30 | Cognition Holdings Ltd | A method of controlling personal information and allowing interaction with authenticated user |
EP3577850B1 (en) | 2017-02-01 | 2021-07-14 | Equifax, Inc. | Verifying an identity based on multiple distributed data sources using a blockchain to safeguard the identity |
WO2018145127A1 (en) * | 2017-02-06 | 2018-08-09 | ShoCard, Inc. | Electronic identification verification methods and systems with storage of certification records to a side chain |
US9992022B1 (en) * | 2017-02-06 | 2018-06-05 | Northern Trust Corporation | Systems and methods for digital identity management and permission controls within distributed network nodes |
CN106850622B (en) * | 2017-02-07 | 2020-03-03 | 杭州秘猿科技有限公司 | User identity management method based on permission chain |
US11574372B2 (en) | 2017-02-08 | 2023-02-07 | Upstream Data Inc. | Blockchain mine at oil or gas facility |
US20180232739A1 (en) * | 2017-02-10 | 2018-08-16 | Selfiepay, Inc. | Systems and methods for biometric transaction management |
US11356427B1 (en) | 2017-02-15 | 2022-06-07 | Wells Fargo Bank, N.A. | Signcrypted envelope message |
US10411897B2 (en) | 2017-02-17 | 2019-09-10 | Factom, Inc. | Secret sharing via blockchains |
US9998286B1 (en) | 2017-02-17 | 2018-06-12 | Accenture Global Solutions Limited | Hardware blockchain consensus operating procedure enforcement |
US10291413B2 (en) * | 2017-02-17 | 2019-05-14 | Accenture Global Solutions Limited | Hardware blockchain corrective consensus operating procedure enforcement |
CN106941487B (en) | 2017-02-24 | 2021-01-05 | 创新先进技术有限公司 | Data sending method and device |
FR3063406B1 (en) * | 2017-02-28 | 2021-08-06 | Airbus Helicopters | METHOD AND DEVICE FOR EXCHANGING INTEGRATED DATA |
US11005653B2 (en) * | 2017-02-28 | 2021-05-11 | Airbus Helicopters | Integrated method and device for storing and sharing data |
FR3073111B1 (en) * | 2017-10-30 | 2020-06-26 | Airbus Helicopters | METHOD AND DEVICE FOR STORING AND SHARING INTEGRATED DATA |
US10671712B1 (en) * | 2017-03-01 | 2020-06-02 | United Services Automobile Association (Usaa) | Virtual notarization using cryptographic techniques and biometric information |
CN107070660B (en) * | 2017-03-03 | 2020-03-17 | 上海唯链信息科技有限公司 | Storage design method of block chain encryption radio frequency chip |
US11763303B1 (en) | 2017-03-10 | 2023-09-19 | Wells Fargo Bank, N.A. | Identity management service via a user-level token |
US10721226B1 (en) | 2017-03-10 | 2020-07-21 | Wells Fargo Bank, N.A. | User-level token for user authentication via a user device |
JP6961960B2 (en) * | 2017-03-13 | 2021-11-05 | ソニーグループ株式会社 | Information processing device and information processing method |
US10817873B2 (en) | 2017-03-22 | 2020-10-27 | Factom, Inc. | Auditing of electronic documents |
CN107248074A (en) * | 2017-03-29 | 2017-10-13 | 阿里巴巴集团控股有限公司 | A kind of method for processing business and equipment based on block chain |
US10871948B1 (en) | 2017-03-30 | 2020-12-22 | Wells Fargo Bank, N.A. | Smart contract blockchain abstraction API |
US10476862B2 (en) * | 2017-03-31 | 2019-11-12 | Mastercard International Incorporated | Systems and methods for providing digital identity records to verify identities of users |
US10685399B2 (en) | 2017-03-31 | 2020-06-16 | Factom, Inc. | Due diligence in electronic documents |
US11538031B2 (en) | 2017-03-31 | 2022-12-27 | Vijay Madisetti | Method and system for identity and access management for blockchain interoperability |
WO2018186874A1 (en) * | 2017-04-07 | 2018-10-11 | Chang Hwa Shang | Blockchain network and method of operation thereof |
US10541818B2 (en) * | 2017-04-19 | 2020-01-21 | International Business Machines Corporation | Decentralized biometric signing of digital contracts |
EP3396608A1 (en) * | 2017-04-24 | 2018-10-31 | BlockSettle AB | Method and system for settling a blockchain transaction |
EP3396612A1 (en) * | 2017-04-24 | 2018-10-31 | BlockSettle AB | Method and system for creating a user identity |
US10505723B1 (en) | 2017-04-26 | 2019-12-10 | Wells Fargo Bank, N.A. | Secret sharing information management and security system |
US10419209B1 (en) | 2017-04-26 | 2019-09-17 | Wells Fargo Bank, N.A. | Parallel assurance of blockchain signatures |
US10270599B2 (en) | 2017-04-27 | 2019-04-23 | Factom, Inc. | Data reproducibility using blockchains |
US11354660B1 (en) | 2017-04-27 | 2022-06-07 | Wells Fargo Bank, N.A. | Encapsulation of payment information |
CN107169371B (en) * | 2017-04-27 | 2019-11-22 | 北京众享比特科技有限公司 | A kind of database operation method and system based on block chain |
US10778450B1 (en) | 2017-04-28 | 2020-09-15 | Wells Fargo Bank, N.A. | Gesture-extracted passwords for authenticated key exchange |
US11074558B1 (en) | 2017-04-28 | 2021-07-27 | Wells Fargo Bank, N.A. | Systems and methods for real-time trickle payments |
US10700875B1 (en) | 2017-05-01 | 2020-06-30 | Wells Fargo Bank, N.A. | Systems and methods for value transfers using signcryption |
US11436597B1 (en) | 2017-05-01 | 2022-09-06 | Wells Fargo Bank, N.A. | Biometrics-based e-signatures for pre-authorization and acceptance transfer |
US11074648B1 (en) | 2017-05-01 | 2021-07-27 | Wells Fargo Bank, N.A. | Blockchain based loan securitization |
SE541713C2 (en) * | 2017-05-03 | 2019-12-03 | Enigio Time Ab | Method and system for registering digital documents |
US10411895B2 (en) * | 2017-05-04 | 2019-09-10 | International Business Machines Corporation | Creating match cohorts and exchanging protected data using blockchain |
US10320574B2 (en) * | 2017-05-05 | 2019-06-11 | International Business Machines Corporation | Blockchain for open scientific research |
US11238543B2 (en) * | 2017-05-06 | 2022-02-01 | Adp, Llc | Payroll based blockchain identity |
US20180330342A1 (en) * | 2017-05-11 | 2018-11-15 | Gyan Prakash | Digital asset account management |
US10762506B1 (en) | 2017-05-11 | 2020-09-01 | United Services Automobile Association | Token device for distributed ledger based interchange |
CN108881120B (en) * | 2017-05-12 | 2020-12-04 | 创新先进技术有限公司 | Data processing method and device based on block chain |
DE102017208503A1 (en) * | 2017-05-19 | 2018-11-22 | Bayerische Motoren Werke Aktiengesellschaft | A method, computer readable medium, system and vehicle comprising the system for providing a record of a vehicle to a third party |
US10438198B1 (en) | 2017-05-19 | 2019-10-08 | Wells Fargo Bank, N.A. | Derived unique token per transaction |
US10554649B1 (en) | 2017-05-22 | 2020-02-04 | State Farm Mutual Automobile Insurance Company | Systems and methods for blockchain validation of user identity and authority |
WO2018214133A1 (en) * | 2017-05-25 | 2018-11-29 | 深圳前海达闼云端智能科技有限公司 | Method, device and system for fido authentication based on blockchain |
EP3632034B1 (en) | 2017-06-02 | 2021-10-13 | Visa International Service Association | Methods and systems for ownership verification using blockchain |
US20200274714A1 (en) * | 2017-06-02 | 2020-08-27 | Roberto Jesus Arriola Suson | System for, method of, and server computer system for implementing transformation of an original entity into a verifiably authenticable entity in a heterogeneous communications network environment |
CN107239954B (en) * | 2017-06-07 | 2021-01-22 | 北京汇通金财信息科技有限公司 | Method and device for increasing block generation speed |
US10924283B2 (en) | 2017-06-12 | 2021-02-16 | Cisco Technology, Inc. | Dynamically-changing identity for IoT devices with blockchain validation |
EP3416334B1 (en) * | 2017-06-15 | 2020-01-15 | Accenture Global Solutions Limited | Portable biometric identity on a distributed data storage layer |
CN107257340B (en) | 2017-06-19 | 2019-10-01 | 阿里巴巴集团控股有限公司 | A kind of authentication method, authentication data processing method and equipment based on block chain |
US10608910B2 (en) | 2017-06-26 | 2020-03-31 | Myomega Systems Gmbh | Using blockchain to track information for devices on a network |
CN107370730B (en) | 2017-07-14 | 2020-06-02 | 创新先进技术有限公司 | Login information processing method and equipment |
US11170370B1 (en) | 2017-07-14 | 2021-11-09 | Wells Fargo Bank, N.A. | Systems and methods for distributed management of negative certificates for blockchain-based value exchange transactions |
US10616324B1 (en) * | 2017-07-20 | 2020-04-07 | Architecture Technology Corporation | Decentralized ledger system and method for enterprises |
US11651358B2 (en) | 2017-07-25 | 2023-05-16 | Mastercard International Incorporated | Method and system for transaction processing with complete cryptographic auditability |
US10601665B2 (en) * | 2017-07-26 | 2020-03-24 | International Business Machines Corporation | Using blockchain smart contracts to manage dynamic data usage requirements |
EP3435270B1 (en) * | 2017-07-27 | 2020-09-23 | Siemens Aktiengesellschaft | Device and method for cryptographically protected operation of a virtual machine |
CN109309650B (en) * | 2017-07-27 | 2020-12-08 | 华为技术有限公司 | Data processing method, terminal equipment and network equipment |
WO2019032089A1 (en) * | 2017-08-07 | 2019-02-14 | Visa International Service Association | Blockchain architecture with record security |
CN111201752A (en) * | 2017-08-11 | 2020-05-26 | 塞库尔开放***公司 | Data verification system based on Hash |
TWI648679B (en) * | 2017-08-16 | 2019-01-21 | 永豐商業銀行股份有限公司 | License management system and method using blockchain |
US10805085B1 (en) | 2017-08-24 | 2020-10-13 | United Services Automobile Association (Usaa) | PKI-based user authentication for web services using blockchain |
CN109428722A (en) * | 2017-08-30 | 2019-03-05 | 上海策赢网络科技有限公司 | A kind of content delivery method and device |
US10728036B2 (en) * | 2017-09-05 | 2020-07-28 | PeerNova, Inc. | Cryptographically linking related events processed across multiple processing systems |
WO2019050527A1 (en) | 2017-09-07 | 2019-03-14 | Visa International Service Association | System and method for generating trust tokens |
KR20200054226A (en) * | 2017-09-13 | 2020-05-19 | 요르단 스토자노브스키 | Cash equivalent device for digital currency |
GB2568453A (en) * | 2017-09-14 | 2019-05-22 | Blockpass Idn Ltd | Systems and methods for user identity |
AU2018333068B2 (en) | 2017-09-18 | 2023-02-23 | Mastercard International Incorporated | Systems and methods for managing digital identities associated with mobile devices |
KR102024991B1 (en) * | 2017-09-26 | 2019-11-04 | 한양대학교 산학협력단 | Flying apparatus and data transmission method thereof |
US11251975B1 (en) | 2017-09-27 | 2022-02-15 | Seagate Technology Llc | Block chain based trusted security infrastructure |
US11505924B2 (en) * | 2017-09-28 | 2022-11-22 | Yokogawa Electric Corporation | Systems and methods for securing fluid distribution systems |
DE102017217342B4 (en) * | 2017-09-28 | 2019-08-14 | Rudolf Bayer | Method for managing an electronic transaction document |
CN107862215B (en) | 2017-09-29 | 2020-10-16 | 创新先进技术有限公司 | Data storage method, data query method and device |
JP6901373B2 (en) * | 2017-10-03 | 2021-07-14 | 株式会社日立製作所 | User management device, user management system |
CN111356995B (en) | 2017-10-04 | 2021-05-28 | 邓白氏公司 | System and method for identity resolution across disparate immutable distributed ledger networks |
EP3729721A4 (en) * | 2017-10-11 | 2021-10-13 | Cambridge Blockchain, Inc. | Systems and methods for managing relationships among digital identities |
US11463241B2 (en) | 2017-10-20 | 2022-10-04 | Hewlett Packard Enterprise Development Lp | Transmitting or receiving blockchain information |
US11604890B2 (en) | 2017-10-20 | 2023-03-14 | Hewlett Packard Enterprise Development Lp | Accessing information based on privileges |
CN111434084B (en) | 2017-10-20 | 2022-07-05 | 慧与发展有限责任合伙企业 | Permission to access information from an entity |
WO2019078880A1 (en) * | 2017-10-20 | 2019-04-25 | Hewlett Packard Enterprise Development Lp | Authenticating and paying for services using blockchain |
CN111543031B (en) * | 2017-10-23 | 2022-09-20 | 西门子股份公司 | Method and control system for controlling and/or monitoring a device |
US10549202B2 (en) * | 2017-10-25 | 2020-02-04 | Sony Interactive Entertainment LLC | Blockchain gaming system |
US20210182849A1 (en) * | 2017-11-06 | 2021-06-17 | Velo Holdings Limited | Limited scope blockchain system |
WO2019090342A1 (en) * | 2017-11-06 | 2019-05-09 | Velo Holdings Limited | Blockchain system |
US11025419B2 (en) | 2017-11-15 | 2021-06-01 | Alexander J. M. Van Der Velden | System for digital identity authentication and methods of use |
US10887098B2 (en) | 2017-11-15 | 2021-01-05 | Alexander J. M. Van Der Velden | System for digital identity authentication and methods of use |
US11037227B1 (en) * | 2017-11-22 | 2021-06-15 | Storcentric, Inc. | Blockchain-based decentralized storage system |
US11836717B2 (en) | 2017-12-04 | 2023-12-05 | Vijay Madisetti | System and method for processing payments in fiat currency using blockchain and tethered tokens |
US10853772B2 (en) * | 2018-04-04 | 2020-12-01 | Vijay K. Madisetti | Method and system for exchange of value or tokens between blockchain networks |
US10476847B1 (en) | 2017-12-08 | 2019-11-12 | Symbiont.Io, Inc. | Systems, methods, and devices for implementing a smart contract on a distributed ledger technology platform |
US10320843B1 (en) | 2017-12-08 | 2019-06-11 | Symbiont.Io, Inc. | Methods, systems, and devices for encrypted electronic storage and confidential network transfer of private data through a trustless distributed ledger technology system |
US11138590B2 (en) * | 2017-12-11 | 2021-10-05 | Titan Seal, Inc. | Apparatus and method for embedding digital certifications within documents |
US10715317B2 (en) * | 2017-12-12 | 2020-07-14 | International Business Machines Corporation | Protection of confidentiality, privacy and financial fairness in a blockchain based decentralized identity management system |
US10855473B1 (en) | 2017-12-15 | 2020-12-01 | Wells Fargo Bank, N.A. | Systems and methods for biometric electronic signature agreement and intention |
US9990504B1 (en) | 2017-12-18 | 2018-06-05 | Northern Trust Corporation | Systems and methods for generating and maintaining immutable digital meeting records within distributed network nodes |
US11544708B2 (en) | 2017-12-29 | 2023-01-03 | Ebay Inc. | User controlled storage and sharing of personal user information on a blockchain |
US10715323B2 (en) | 2017-12-29 | 2020-07-14 | Ebay Inc. | Traceable key block-chain ledger |
US10659217B2 (en) | 2018-01-05 | 2020-05-19 | Bank Of America Corporation | Blockchain-based automated user matching |
US10756883B2 (en) | 2018-01-19 | 2020-08-25 | Trist Technologies, Inc. | Systems and methods for data collection with blockchain recording |
US11251937B2 (en) * | 2018-01-21 | 2022-02-15 | CipherTrace, Inc. | Distributed security mechanism for blockchains and distributed ledgers |
DE102018000471A1 (en) * | 2018-01-22 | 2019-07-25 | Giesecke+Devrient Mobile Security Gmbh | Blockchain-based identity system |
US11088842B1 (en) | 2018-01-30 | 2021-08-10 | State Farm Mutual Automobile Insurance Company | Vehicle configuration verification using cryptographic hash chains |
US11942195B2 (en) | 2018-01-30 | 2024-03-26 | Humana Inc. | System for providing a data market for health data and for providing rewards to data market participants |
US11100503B2 (en) * | 2018-02-07 | 2021-08-24 | Mastercard International Incorporated | Systems and methods for use in managing digital identities |
US20190251573A1 (en) * | 2018-02-09 | 2019-08-15 | Airbus (S.A.S.) | Systems and methods of verifying credentials of aircraft personnel using a blockchain computer system |
US10558471B2 (en) * | 2018-02-09 | 2020-02-11 | Merck Sharp & Dohme Corp. | Proof of configuration |
CN111713088B (en) * | 2018-02-14 | 2022-03-01 | 华为技术有限公司 | Method and device for processing data and equipment for processing data |
US10614253B2 (en) | 2018-02-14 | 2020-04-07 | Fortune Vieyra | Systems and methods for state of data management |
DE112018007016T5 (en) * | 2018-03-07 | 2020-11-05 | Ford Global Technologies, Llc | BLOCKCHAIN AUTHENTICATION OF A VEHICLE RIDER |
US11048228B2 (en) | 2018-03-16 | 2021-06-29 | General Electric Company | System and method to protect items associated with additive manufacturing |
JP2019161580A (en) * | 2018-03-16 | 2019-09-19 | 日本電気株式会社 | Data transmission device, data transmission/reception system, data reception device, data transmission method, and program |
US11487851B2 (en) | 2018-03-19 | 2022-11-01 | International Business Machines Corporation | Using blockchain for flexible application licensing |
US10664811B2 (en) | 2018-03-22 | 2020-05-26 | Bank Of America Corporation | Automated check encoding error resolution |
US11716320B2 (en) | 2018-03-27 | 2023-08-01 | Workday, Inc. | Digital credentials for primary factor authentication |
US11019053B2 (en) | 2018-03-27 | 2021-05-25 | Workday, Inc. | Requesting credentials |
US11641278B2 (en) * | 2018-03-27 | 2023-05-02 | Workday, Inc. | Digital credential authentication |
US11792181B2 (en) | 2018-03-27 | 2023-10-17 | Workday, Inc. | Digital credentials as guest check-in for physical building access |
US11770261B2 (en) | 2018-03-27 | 2023-09-26 | Workday, Inc. | Digital credentials for user device authentication |
US11627000B2 (en) | 2018-03-27 | 2023-04-11 | Workday, Inc. | Digital credentials for employee badging |
US11683177B2 (en) | 2018-03-27 | 2023-06-20 | Workday, Inc. | Digital credentials for location aware check in |
US11698979B2 (en) | 2018-03-27 | 2023-07-11 | Workday, Inc. | Digital credentials for access to sensitive data |
US11700117B2 (en) | 2018-03-27 | 2023-07-11 | Workday, Inc. | System for credential storage and verification |
US11531783B2 (en) | 2018-03-27 | 2022-12-20 | Workday, Inc. | Digital credentials for step-up authentication |
US11792180B2 (en) | 2018-03-27 | 2023-10-17 | Workday, Inc. | Digital credentials for visitor network access |
US11522713B2 (en) | 2018-03-27 | 2022-12-06 | Workday, Inc. | Digital credentials for secondary factor authentication |
CN110311883B (en) | 2018-03-27 | 2020-11-10 | 华为技术有限公司 | Identity management method, device, communication network and storage medium |
US10878429B2 (en) | 2018-03-28 | 2020-12-29 | Konstantinos Bakalis | Systems and methods for using codes and images within a blockchain |
CN108512661A (en) * | 2018-04-02 | 2018-09-07 | 成都零光量子科技有限公司 | A kind of safety protecting method of block chain private key for user |
WO2019195205A1 (en) * | 2018-04-02 | 2019-10-10 | Jpmorgan Chase Bank, N.A. | Method and system for implementing an automation software testing and packaging framework with entitlements |
JP6742558B2 (en) * | 2018-04-09 | 2020-08-19 | 三菱電機株式会社 | Certification system and certification program |
SG11202008211YA (en) * | 2018-04-09 | 2020-09-29 | Mitsubishi Electric Corp | Authentication system and authentication program |
US10848395B2 (en) * | 2018-04-10 | 2020-11-24 | Zscaler, Inc. | State management across distributed services using cryptographically bound journals |
CN108810901A (en) * | 2018-04-17 | 2018-11-13 | 中国地质大学(武汉) | A kind of malice number mark recognition methods based on block chain |
WO2019209291A1 (en) * | 2018-04-24 | 2019-10-31 | Black Gold Coin, Inc. | Systems and methods for providing a universal decentralized solution for verification of users with cross-verification features |
EP3562090B1 (en) * | 2018-04-25 | 2020-07-01 | Siemens Aktiengesellschaft | Data processing device for processing a radio signal |
CN112534452A (en) | 2018-05-06 | 2021-03-19 | 强力交易投资组合2018有限公司 | Method and system for improving machines and systems for automatically performing distributed ledger and other transactions in spot and forward markets for energy, computing, storage, and other resources |
US11550299B2 (en) | 2020-02-03 | 2023-01-10 | Strong Force TX Portfolio 2018, LLC | Automated robotic process selection and configuration |
US11669914B2 (en) | 2018-05-06 | 2023-06-06 | Strong Force TX Portfolio 2018, LLC | Adaptive intelligence and shared infrastructure lending transaction enablement platform responsive to crowd sourced information |
US11544782B2 (en) | 2018-05-06 | 2023-01-03 | Strong Force TX Portfolio 2018, LLC | System and method of a smart contract and distributed ledger platform with blockchain custody service |
US10783164B2 (en) | 2018-05-18 | 2020-09-22 | Factom, Inc. | Import and export in blockchain environments |
US11170366B2 (en) | 2018-05-18 | 2021-11-09 | Inveniam Capital Partners, Inc. | Private blockchain services |
US11134120B2 (en) | 2018-05-18 | 2021-09-28 | Inveniam Capital Partners, Inc. | Load balancing in blockchain environments |
US10560261B1 (en) | 2018-05-24 | 2020-02-11 | DeepTruth, LLC | Systems and techniques for capture of trusted media data |
US11683180B1 (en) | 2018-05-24 | 2023-06-20 | Swear Inc. | Protecting digital media with nested hashing techniques |
US11038676B2 (en) | 2018-05-25 | 2021-06-15 | Incertrust Technologies Corporation | Cryptographic systems and methods using distributed ledgers |
US11836718B2 (en) | 2018-05-31 | 2023-12-05 | CipherTrace, Inc. | Systems and methods for crypto currency automated transaction flow detection |
DE102018004423A1 (en) * | 2018-06-04 | 2019-12-05 | Sap Se | Secure data exchange |
TR201808119A2 (en) * | 2018-06-07 | 2018-07-23 | Elektronik Bilgi Guevenligi Anonim Sirketi | METHOD OF IDENTIFICATION OF E-SIGNATURE AND BLOCKCHAIN LAYERS |
CN109034796B (en) * | 2018-06-15 | 2023-09-22 | 安达数据技术(深圳)有限公司 | Alliance chain-based transaction supervision method, electronic device and readable storage medium |
JP6494004B1 (en) * | 2018-06-18 | 2019-04-03 | Necソリューションイノベータ株式会社 | Personal information management system, service providing system, method and program |
WO2019245924A1 (en) * | 2018-06-19 | 2019-12-26 | Docusign, Inc. | File validation using a blockchain |
US10546444B2 (en) | 2018-06-21 | 2020-01-28 | Capital One Services, Llc | Systems and methods for secure read-only authentication |
US20190394046A1 (en) * | 2018-06-22 | 2019-12-26 | Sf Motors, Inc. | Secure firmware updates for remote vehicles |
US11837344B2 (en) | 2018-06-29 | 2023-12-05 | OutcomeMD, Inc. | Systems and methods for securely storing patient information and providing access thereto |
CN112491551B (en) * | 2018-06-29 | 2023-01-20 | 创新先进技术有限公司 | Data verification method and device based on block chain and electronic equipment |
WO2020008367A1 (en) * | 2018-07-02 | 2020-01-09 | Bitchange Oü | A method of creating a digital id or digital data storage of a person or an organization, and a method of using the digital id or digital data storage for remote identification |
EP3591553B1 (en) * | 2018-07-02 | 2022-11-02 | Nxp B.V. | Authentication token and method of operating the same |
CN110677376B (en) * | 2018-07-03 | 2022-03-22 | 中国电信股份有限公司 | Authentication method, related device and system and computer readable storage medium |
GB201811263D0 (en) * | 2018-07-10 | 2018-08-29 | Netmaster Solutions Ltd | A method and system for managing digital using a blockchain |
CN110708269B (en) * | 2018-07-10 | 2022-04-12 | 北京京东尚科信息技术有限公司 | Block chain data transmission method, block chain node and computer readable storage medium |
US11019585B1 (en) * | 2018-07-24 | 2021-05-25 | Sprint Communications Company L.P. | Network generated precision time |
US11270403B2 (en) | 2018-07-30 | 2022-03-08 | Hewlett Packard Enterprise Development Lp | Systems and methods of obtaining verifiable image of entity by embedding secured representation of entity's distributed ledger address in image |
US11356443B2 (en) | 2018-07-30 | 2022-06-07 | Hewlett Packard Enterprise Development Lp | Systems and methods for associating a user claim proven using a distributed ledger identity with a centralized identity of the user |
US11250466B2 (en) | 2018-07-30 | 2022-02-15 | Hewlett Packard Enterprise Development Lp | Systems and methods for using secured representations of user, asset, and location distributed ledger addresses to prove user custody of assets at a location and time |
US11184175B2 (en) | 2018-07-30 | 2021-11-23 | Hewlett Packard Enterprise Development Lp | Systems and methods for using secured representations of location and user distributed ledger addresses to prove user presence at a location and time |
US11403674B2 (en) | 2018-07-30 | 2022-08-02 | Hewlett Packard Enterprise Development Lp | Systems and methods for capturing time series dataset over time that includes secured representations of distributed ledger addresses |
US11488160B2 (en) | 2018-07-30 | 2022-11-01 | Hewlett Packard Enterprise Development Lp | Systems and methods for using captured time series of secured representations of distributed ledger addresses and smart contract deployed on distributed ledger network to prove compliance |
US11233641B2 (en) | 2018-07-31 | 2022-01-25 | Hewlett Packard Enterprise Development Lp | Systems and methods for using distributed attestation to verify claim of attestation holder |
US11488161B2 (en) * | 2018-07-31 | 2022-11-01 | Hewlett Packard Enterprise Development Lp | Systems and methods for providing transaction provenance of off-chain transactions using distributed ledger transactions with secured representations of distributed ledger addresses of transacting parties |
US11271908B2 (en) * | 2018-07-31 | 2022-03-08 | Hewlett Packard Enterprise Development Lp | Systems and methods for hiding identity of transacting party in distributed ledger transaction by hashing distributed ledger transaction ID using secured representation of distributed ledger address of transacting party as a key |
CN109088865B (en) * | 2018-08-02 | 2021-10-12 | 京东方科技集团股份有限公司 | User identity authentication method and device, readable storage medium and computer equipment |
US11348097B2 (en) | 2018-08-06 | 2022-05-31 | Inveniam Capital Partners, Inc. | Digital contracts in blockchain environments |
US11328290B2 (en) | 2018-08-06 | 2022-05-10 | Inveniam Capital Partners, Inc. | Stable cryptocurrency coinage |
US11044095B2 (en) | 2018-08-06 | 2021-06-22 | Factom, Inc. | Debt recordation to blockchains |
US11164250B2 (en) | 2018-08-06 | 2021-11-02 | Inveniam Capital Partners, Inc. | Stable cryptocurrency coinage |
US11989208B2 (en) | 2018-08-06 | 2024-05-21 | Inveniam Capital Partners, Inc. | Transactional sharding of blockchain transactions |
JP6566278B1 (en) * | 2018-08-08 | 2019-08-28 | 株式会社DataSign | Personal data management system |
CN110830256A (en) * | 2018-08-14 | 2020-02-21 | 珠海金山办公软件有限公司 | File signature method and device, electronic equipment and readable storage medium |
CN108985100B (en) * | 2018-08-15 | 2022-02-25 | 百度在线网络技术(北京)有限公司 | Block chain-based element security certification method, device, equipment and medium |
KR102097995B1 (en) * | 2018-08-17 | 2020-04-07 | 주식회사 트러스트디비 | Electronic payment system for protection of double spending and payment method therefor |
US10673847B2 (en) | 2018-08-28 | 2020-06-02 | Ofer A. LIDSKY | Systems and methods for user authentication based on a genetic sequence |
US11140177B2 (en) * | 2018-08-31 | 2021-10-05 | Cisco Technology, Inc. | Distributed data authentication and validation using blockchain |
US11301590B2 (en) * | 2018-09-05 | 2022-04-12 | International Business Machines Corporation | Unfalsifiable audit logs for a blockchain |
EP3847657A1 (en) | 2018-09-05 | 2021-07-14 | Translational Imaging Innovations LLC | Methods, systems and computer program products for retrospective data mining |
KR20200034020A (en) | 2018-09-12 | 2020-03-31 | 삼성전자주식회사 | Electronic apparatus and control method thereof |
WO2020055413A1 (en) * | 2018-09-13 | 2020-03-19 | Hitachi, Ltd. | Blockchain for audit |
CN109214163B (en) * | 2018-09-14 | 2021-08-20 | 北卡科技有限公司 | Identity authentication method and device |
CN109389498A (en) * | 2018-09-18 | 2019-02-26 | 上海诚频信息科技合伙企业(有限合伙) | Block chain user identity management method, system, equipment and storage medium |
CN110932859B (en) * | 2018-09-20 | 2021-06-15 | 北大方正集团有限公司 | User information processing method, device and equipment and readable storage medium |
CN109036430A (en) * | 2018-09-29 | 2018-12-18 | 芜湖星途机器人科技有限公司 | Voice control terminal |
CN109492424B (en) * | 2018-09-29 | 2023-05-26 | 平安科技(深圳)有限公司 | Data asset management method, data asset management device, and computer-readable medium |
CA3108917A1 (en) | 2018-10-02 | 2020-04-09 | Capital One Services, Llc | Systems and methods for cryptographic authentication of contactless cards |
CA3115252A1 (en) | 2018-10-02 | 2020-04-09 | Capital One Services, Llc | Systems and methods for cryptographic authentication of contactless cards |
US10860814B2 (en) | 2018-10-02 | 2020-12-08 | Capital One Services, Llc | Systems and methods for cryptographic authentication of contactless cards |
US10579998B1 (en) | 2018-10-02 | 2020-03-03 | Capital One Services, Llc | Systems and methods for cryptographic authentication of contactless cards |
US11368446B2 (en) * | 2018-10-02 | 2022-06-21 | International Business Machines Corporation | Trusted account revocation in federated identity management |
US10554411B1 (en) | 2018-10-02 | 2020-02-04 | Capital One Services, Llc | Systems and methods for cryptographic authentication of contactless cards |
MX2021003138A (en) | 2018-10-02 | 2021-05-14 | Capital One Services Llc | Systems and methods for cryptographic authentication of contactless cards. |
US10592710B1 (en) | 2018-10-02 | 2020-03-17 | Capital One Services, Llc | Systems and methods for cryptographic authentication of contactless cards |
US10771254B2 (en) | 2018-10-02 | 2020-09-08 | Capital One Services, Llc | Systems and methods for email-based card activation |
CA3115107A1 (en) | 2018-10-02 | 2020-04-09 | Capital One Services, Llc | Systems and methods for cryptographic authentication of contactless cards |
US10511443B1 (en) | 2018-10-02 | 2019-12-17 | Capital One Services, Llc | Systems and methods for cryptographic authentication of contactless cards |
US10771253B2 (en) | 2018-10-02 | 2020-09-08 | Capital One Services, Llc | Systems and methods for cryptographic authentication of contactless cards |
US10797882B2 (en) | 2018-10-02 | 2020-10-06 | Capital One Services, Llc | Systems and methods for cryptographic authentication of contactless cards |
US10748138B2 (en) | 2018-10-02 | 2020-08-18 | Capital One Services, Llc | Systems and methods for cryptographic authentication of contactless cards |
US10581611B1 (en) | 2018-10-02 | 2020-03-03 | Capital One Services, Llc | Systems and methods for cryptographic authentication of contactless cards |
AU2019355878A1 (en) | 2018-10-02 | 2021-02-25 | Capital One Services, Llc | Systems and methods for cryptographic authentication of contactless cards |
US10542036B1 (en) | 2018-10-02 | 2020-01-21 | Capital One Services, Llc | Systems and methods for signaling an attack on contactless cards |
CA3115142A1 (en) | 2018-10-02 | 2020-04-09 | Capital One Services, Llc | Systems and methods for cryptographic authentication of contactless cards |
US10489781B1 (en) | 2018-10-02 | 2019-11-26 | Capital One Services, Llc | Systems and methods for cryptographic authentication of contactless cards |
US10949520B2 (en) | 2018-10-02 | 2021-03-16 | Capital One Services, Llc | Systems and methods for cross coupling risk analytics and one-time-passcodes |
US10783519B2 (en) | 2018-10-02 | 2020-09-22 | Capital One Services, Llc | Systems and methods for cryptographic authentication of contactless cards |
US10565587B1 (en) | 2018-10-02 | 2020-02-18 | Capital One Services, Llc | Systems and methods for cryptographic authentication of contactless cards |
KR20210066798A (en) | 2018-10-02 | 2021-06-07 | 캐피탈 원 서비시즈, 엘엘씨 | System and method for cryptographic authentication of contactless card |
US10505738B1 (en) | 2018-10-02 | 2019-12-10 | Capital One Services, Llc | Systems and methods for cryptographic authentication of contactless cards |
US10909527B2 (en) | 2018-10-02 | 2021-02-02 | Capital One Services, Llc | Systems and methods for performing a reissue of a contactless card |
US10582386B1 (en) | 2018-10-02 | 2020-03-03 | Capital One Services, Llc | Systems and methods for cryptographic authentication of contactless cards |
US10607214B1 (en) | 2018-10-02 | 2020-03-31 | Capital One Services, Llc | Systems and methods for cryptographic authentication of contactless cards |
US10992477B2 (en) | 2018-10-02 | 2021-04-27 | Capital One Services, Llc | Systems and methods for cryptographic authentication of contactless cards |
US11210664B2 (en) | 2018-10-02 | 2021-12-28 | Capital One Services, Llc | Systems and methods for amplifying the strength of cryptographic algorithms |
WO2020072583A1 (en) | 2018-10-02 | 2020-04-09 | Capital One Services, Llc | Systems and methods for establishing identity for order pick up |
AU2019355110A1 (en) | 2018-10-02 | 2021-04-08 | Capital One Services, Llc | Systems and methods for cryptographic authentication of contactless cards |
US11374762B2 (en) * | 2018-10-09 | 2022-06-28 | International Business Machines Corporation | Certifying authenticity of data modifications |
US11301452B2 (en) | 2018-10-09 | 2022-04-12 | Ebay, Inc. | Storing and verification of derivative work data on blockchain with original work data |
US11849047B2 (en) | 2018-10-09 | 2023-12-19 | International Business Machines Corporation | Certifying authenticity of data modifications |
KR101981699B1 (en) * | 2018-10-22 | 2019-05-23 | 김보언 | System for copyright management of non-digital work based on block-chain |
CN109347632B (en) * | 2018-10-23 | 2022-02-25 | 北京金山安全软件有限公司 | Block chain ID generation and use method, device, electronic equipment and storage medium |
US10916253B2 (en) | 2018-10-29 | 2021-02-09 | International Business Machines Corporation | Spoken microagreements with blockchain |
US10929816B2 (en) * | 2018-10-29 | 2021-02-23 | Advanced Messaging Technologies, Inc. | Systems and methods for message transmission and retrieval using blockchain |
CN109460975A (en) * | 2018-10-30 | 2019-03-12 | 国家电网有限公司 | Construction project data anti-counterfeiting management system and method |
CN109583230A (en) | 2018-10-31 | 2019-04-05 | 阿里巴巴集团控股有限公司 | Data based on block chain deposit card method and device, electronic equipment |
KR102580881B1 (en) * | 2018-11-08 | 2023-09-20 | 삼성전자주식회사 | Electronic device and method of providing personal information, and computer-readable recording medium recording the same |
CN109508521B (en) * | 2018-11-12 | 2022-05-03 | 四川长虹电器股份有限公司 | Block chain-based household appliance maintenance personnel verification method |
US11546373B2 (en) | 2018-11-20 | 2023-01-03 | CipherTrace, Inc. | Cryptocurrency based malware and ransomware detection systems and methods |
CN109684797B (en) * | 2018-11-21 | 2020-10-20 | 众安信息技术服务有限公司 | Virtual IP protection method and system for confrontation network generated picture based on block chain |
TR201817812A2 (en) * | 2018-11-23 | 2019-02-21 | Turkcell Teknoloji Arastirma Ve Gelistirme Anonim Sirketi | A SYSTEM THAT ENABLES USER-SPECIFIC DIGITAL IDENTIFICATION AND STORAGE |
CN113793151A (en) * | 2018-11-28 | 2021-12-14 | 创新先进技术有限公司 | Block chain-based data evidence storing method and device and electronic equipment |
CN109583896A (en) * | 2018-11-30 | 2019-04-05 | 元灵通智能科技(深圳)有限公司 | Transaction verification method, block chain node and storage medium |
US11070449B2 (en) | 2018-12-04 | 2021-07-20 | Bank Of America Corporation | Intelligent application deployment to distributed ledger technology nodes |
US10841153B2 (en) | 2018-12-04 | 2020-11-17 | Bank Of America Corporation | Distributed ledger technology network provisioner |
US11882214B2 (en) * | 2018-12-06 | 2024-01-23 | Telefonaktiebolaget Lm Ericsson (Publ) | Technique for cryptographic document protection and verification |
US11468176B2 (en) | 2018-12-06 | 2022-10-11 | Pasig And Hudson, Pvt Limited | Computer method and graphical user interface for identity management using blockchain |
CN109547461A (en) * | 2018-12-13 | 2019-03-29 | 如般量子科技有限公司 | Anti- quantum calculation block chain secure transactions system and method based on P2P pool of symmetric keys |
US20200193426A1 (en) * | 2018-12-18 | 2020-06-18 | Secude Ag | Method and system for creating and updating an authentic log file for a computer system and transactions |
CN111782668B (en) * | 2018-12-20 | 2024-06-28 | 创新先进技术有限公司 | Data structure reading and updating method and device and electronic equipment |
CN109710692B (en) * | 2018-12-21 | 2021-03-05 | 咪咕文化科技有限公司 | User information processing method and device in block chain network and storage medium |
CN110046482A (en) * | 2018-12-25 | 2019-07-23 | 阿里巴巴集团控股有限公司 | Identity verification method and its system |
CN111371941A (en) * | 2018-12-26 | 2020-07-03 | 中兴通讯股份有限公司 | Method and device for preventing harassing call, terminal and storage medium |
US20200210996A1 (en) * | 2018-12-27 | 2020-07-02 | Capital One Services, Llc | Systems, methods, and platforms for providing tracking through blockchain networks |
CN110032882A (en) | 2018-12-29 | 2019-07-19 | 阿里巴巴集团控股有限公司 | Card method and apparatus are deposited based on block chain |
KR20200085095A (en) | 2019-01-04 | 2020-07-14 | 삼성전자주식회사 | Electronic apparatus and method for managing data based on block chain |
KR20200086962A (en) | 2019-01-10 | 2020-07-20 | 휴렛-팩커드 디벨롭먼트 컴퍼니, 엘.피. | Manage and perform job based on blockchain in image forming device |
KR20200087377A (en) | 2019-01-10 | 2020-07-21 | 휴렛-팩커드 디벨롭먼트 컴퍼니, 엘.피. | User account management based on blockchain in image forming device |
US20200226581A1 (en) | 2019-01-11 | 2020-07-16 | Capital One Services, Llc | Systems and methods for touch screen interface interaction using a card overlay |
EP3683756A1 (en) * | 2019-01-15 | 2020-07-22 | ABB Schweiz AG | Verifiable analytics platform with smart contracts |
US10839387B2 (en) | 2019-01-15 | 2020-11-17 | Adp, Llc | Blockchain based action and billing |
CN110245522B (en) * | 2019-01-16 | 2022-07-12 | 腾讯科技(深圳)有限公司 | Data processing method, terminal and medium in block chain fund settlement system |
KR20200088995A (en) | 2019-01-16 | 2020-07-24 | 휴렛-팩커드 디벨롭먼트 컴퍼니, 엘.피. | Document security and integrity verification based on blockchain in image forming device |
US11037136B2 (en) | 2019-01-24 | 2021-06-15 | Capital One Services, Llc | Tap to autofill card data |
CN110032892A (en) * | 2019-01-29 | 2019-07-19 | 香港贝尔科技有限公司 | A kind of innovatory algorithm based on block chain DPOS common recognition mechanism |
CN109658236A (en) * | 2019-01-31 | 2019-04-19 | 北京京东尚科信息技术有限公司 | Information interacting method, block chain node and credit investigation system based on block chain |
US10510074B1 (en) | 2019-02-01 | 2019-12-17 | Capital One Services, Llc | One-tap payment using a contactless card |
US11120453B2 (en) | 2019-02-01 | 2021-09-14 | Capital One Services, Llc | Tap card to securely generate card data to copy to clipboard |
US10467622B1 (en) | 2019-02-01 | 2019-11-05 | Capital One Services, Llc | Using on-demand applications to generate virtual numbers for a contactless card to securely autofill forms |
KR102236620B1 (en) * | 2019-02-15 | 2021-04-05 | 김세진 | Method and System for management of blood donation |
CN109934672A (en) * | 2019-02-19 | 2019-06-25 | 薛伟忠 | A kind of E-shop system economic based on the logical card of block chain |
US10425129B1 (en) | 2019-02-27 | 2019-09-24 | Capital One Services, Llc | Techniques to reduce power consumption in near field communication systems |
US11212090B1 (en) | 2019-02-27 | 2021-12-28 | Wells Fargo Bank, N.A. | Derived unique random key per transaction |
US11888992B2 (en) | 2019-02-28 | 2024-01-30 | Advanced New Technologies Co., Ltd. | System and method for generating digital marks |
CN110753944B (en) * | 2019-02-28 | 2023-07-04 | 创新先进技术有限公司 | System and method for blockchain-based data management |
EP3913890B1 (en) * | 2019-02-28 | 2023-04-12 | Advanced New Technologies Co., Ltd. | System and method for blockchain-based authentication |
US11363003B2 (en) * | 2019-03-11 | 2022-06-14 | Mitsubishi Electric Corporation | Data management device, data management system, data management method, and program |
US11093482B2 (en) | 2019-03-12 | 2021-08-17 | International Business Machines Corporation | Managing access by third parties to data in a network |
US10523708B1 (en) | 2019-03-18 | 2019-12-31 | Capital One Services, Llc | System and method for second factor authentication of customer support calls |
US10984416B2 (en) | 2019-03-20 | 2021-04-20 | Capital One Services, Llc | NFC mobile currency transfer |
US10643420B1 (en) | 2019-03-20 | 2020-05-05 | Capital One Services, Llc | Contextual tapping engine |
US10438437B1 (en) | 2019-03-20 | 2019-10-08 | Capital One Services, Llc | Tap to copy data to clipboard via NFC |
US10535062B1 (en) * | 2019-03-20 | 2020-01-14 | Capital One Services, Llc | Using a contactless card to securely share personal data stored in a blockchain |
US10970712B2 (en) | 2019-03-21 | 2021-04-06 | Capital One Services, Llc | Delegated administration of permissions using a contactless card |
US11777712B2 (en) * | 2019-03-22 | 2023-10-03 | International Business Machines Corporation | Information management in a database |
US11228443B2 (en) * | 2019-03-25 | 2022-01-18 | Micron Technology, Inc. | Using memory as a block in a block chain |
US10467445B1 (en) | 2019-03-28 | 2019-11-05 | Capital One Services, Llc | Devices and methods for contactless card alignment with a foldable mobile device |
WO2020192948A1 (en) * | 2019-03-28 | 2020-10-01 | NEC Laboratories Europe GmbH | Method and distributed ledger system for supporting identity management of travelers in an airport |
TWI695293B (en) * | 2019-03-29 | 2020-06-01 | 天逸財金科技服務股份有限公司 | Method, system and server for protection mechanism of digital signature certificate |
CN109981655B (en) * | 2019-03-29 | 2022-03-01 | 富士胶片实业发展(上海)有限公司 | Method and device for transmitting and receiving information |
US11605076B2 (en) | 2019-04-01 | 2023-03-14 | The Toronto-Dominion Bank | Reconciliation of indirectly executed exchanges of data using permissioned distributed ledgers |
US20200320622A1 (en) * | 2019-04-05 | 2020-10-08 | Secude Ag | Method and system for processing and documenting digital transactions |
EP3723017A1 (en) | 2019-04-08 | 2020-10-14 | Mastercard International Incorporated | Improvements relating to identity authentication and validation |
DE102019002663A1 (en) * | 2019-04-11 | 2020-10-15 | Daimler Ag | Procedure for the documentation of data of a physical unit |
US10825024B1 (en) | 2019-04-12 | 2020-11-03 | Symbiont.Io, Inc. | Systems, devices, and methods for DLT-based data management platforms and data products |
CN110032890B (en) * | 2019-04-15 | 2021-03-05 | 京东方科技集团股份有限公司 | Safety network device and safety access method |
US11671432B1 (en) * | 2019-04-18 | 2023-06-06 | Riccardo Vieri | Portable trust rating method and system |
CN111835520B (en) * | 2019-04-19 | 2023-04-07 | 株式会社理光 | Method for device authentication, method for service access control, device and storage medium |
CN110059092A (en) * | 2019-04-22 | 2019-07-26 | 广州市品高软件股份有限公司 | The method for writing data and system of relevant database based on block chain |
KR102085999B1 (en) * | 2019-05-15 | 2020-03-06 | 김보언 | System for determining whether non-digital work is digitalization data and type of non-digital work |
US11907029B2 (en) | 2019-05-15 | 2024-02-20 | Upstream Data Inc. | Portable blockchain mining system and methods of use |
KR102086000B1 (en) * | 2019-05-15 | 2020-03-06 | 김보언 | System for determining identity of non-digital work |
KR102086001B1 (en) * | 2019-05-15 | 2020-03-06 | 김보언 | System for managing information of distribution history based on block-chain |
AU2020279093A1 (en) * | 2019-05-23 | 2021-11-18 | Mastercard International Incorporated | Method and system for generalized provenance solution for blockchain supply chain applications |
US11516001B2 (en) * | 2019-05-23 | 2022-11-29 | Mastercard International Incorporated | Method and system for generalized provenance solution for blockchain supply chain applications |
GB201907392D0 (en) * | 2019-05-24 | 2019-07-10 | Nchain Holdings Ltd | Proof-of-work |
CN110223064B (en) * | 2019-05-27 | 2020-07-28 | 四川大学 | Non-repudiation safety data transmission method based on block chain |
US11521262B2 (en) | 2019-05-28 | 2022-12-06 | Capital One Services, Llc | NFC enhanced augmented reality information overlays |
US11503026B2 (en) | 2019-05-28 | 2022-11-15 | Alexander J. M. Van Der Velden | Email address with identity string and methods of use |
US10474834B1 (en) | 2019-06-04 | 2019-11-12 | Capital One Services, Llc | Data sharing via distributed ledgers |
US10554406B1 (en) | 2019-06-04 | 2020-02-04 | Capital One Services, Llc | Authorized data sharing using smart contracts |
CN110287725B (en) * | 2019-06-04 | 2021-05-14 | 大唐微电子技术有限公司 | Equipment, authority control method thereof and computer readable storage medium |
US11374768B2 (en) * | 2019-06-11 | 2022-06-28 | Mastercard International Incorporated | Method and system for real-time driving alerts |
US10516447B1 (en) | 2019-06-17 | 2019-12-24 | Capital One Services, Llc | Dynamic power levels in NFC card communications |
CN111213147B (en) | 2019-07-02 | 2023-10-13 | 创新先进技术有限公司 | Systems and methods for blockchain-based cross-entity authentication |
WO2019179533A2 (en) | 2019-07-02 | 2019-09-26 | Alibaba Group Holding Limited | System and method for issuing verifiable claims |
EP3721603B1 (en) | 2019-07-02 | 2021-12-08 | Advanced New Technologies Co., Ltd. | System and method for creating decentralized identifiers |
CN116910726A (en) | 2019-07-02 | 2023-10-20 | 创新先进技术有限公司 | System and method for mapping a de-centralized identity to a real entity |
EP3688633A4 (en) | 2019-07-02 | 2020-10-07 | Alibaba Group Holding Limited | System and method for verifying verifiable claims |
CN111316303B (en) | 2019-07-02 | 2023-11-10 | 创新先进技术有限公司 | Systems and methods for blockchain-based cross-entity authentication |
US10871958B1 (en) | 2019-07-03 | 2020-12-22 | Capital One Services, Llc | Techniques to perform applet programming |
US11694187B2 (en) | 2019-07-03 | 2023-07-04 | Capital One Services, Llc | Constraining transactional capabilities for contactless cards |
US11392933B2 (en) | 2019-07-03 | 2022-07-19 | Capital One Services, Llc | Systems and methods for providing online and hybridcard interactions |
US10713649B1 (en) | 2019-07-09 | 2020-07-14 | Capital One Services, Llc | System and method enabling mobile near-field communication to update display on a payment card |
US10498401B1 (en) | 2019-07-15 | 2019-12-03 | Capital One Services, Llc | System and method for guiding card positioning using phone sensors |
US10885514B1 (en) | 2019-07-15 | 2021-01-05 | Capital One Services, Llc | System and method for using image data to trigger contactless card transactions |
US10733601B1 (en) | 2019-07-17 | 2020-08-04 | Capital One Services, Llc | Body area network facilitated authentication or payment authorization |
US10832271B1 (en) | 2019-07-17 | 2020-11-10 | Capital One Services, Llc | Verified reviews using a contactless card |
US11182771B2 (en) | 2019-07-17 | 2021-11-23 | Capital One Services, Llc | System for value loading onto in-vehicle device |
US11521213B2 (en) | 2019-07-18 | 2022-12-06 | Capital One Services, Llc | Continuous authentication for digital services based on contactless card positioning |
US10506426B1 (en) | 2019-07-19 | 2019-12-10 | Capital One Services, Llc | Techniques for call authentication |
CN112241513B (en) * | 2019-07-19 | 2024-04-19 | 傲为有限公司 | Digital asset processing system to be authenticated |
US10541995B1 (en) | 2019-07-23 | 2020-01-21 | Capital One Services, Llc | First factor contactless card authentication system and method |
CN110489985B (en) * | 2019-08-21 | 2021-08-03 | 泰康保险集团股份有限公司 | Data processing method and device, computer readable storage medium and electronic equipment |
CN110535659B (en) * | 2019-09-03 | 2020-11-03 | 北京海益同展信息科技有限公司 | Method, apparatus, electronic device and computer readable medium for processing data request |
EP4038587A4 (en) | 2019-10-02 | 2023-06-07 | Capital One Services, LLC | Client device authentication using contactless legacy magnetic stripe data |
CN110928534B (en) * | 2019-10-14 | 2021-11-09 | 上海唯链信息科技有限公司 | Workflow node authentication method and device based on block chain |
CN111182020B (en) * | 2019-10-17 | 2021-12-07 | 腾讯科技(深圳)有限公司 | Signature service processing method, device, medium and electronic equipment |
US11328080B2 (en) | 2019-11-18 | 2022-05-10 | Frostbyte, Llc | Cryptographic key management |
KR20210072321A (en) * | 2019-12-09 | 2021-06-17 | 삼성전자주식회사 | Cryptographic communication system and cryptographic communication method based on blockchain |
CN110716923B (en) * | 2019-12-12 | 2020-03-17 | 腾讯科技(深圳)有限公司 | Data processing method, data processing device, node equipment and storage medium |
US10657754B1 (en) | 2019-12-23 | 2020-05-19 | Capital One Services, Llc | Contactless card and personal identification system |
US11615395B2 (en) | 2019-12-23 | 2023-03-28 | Capital One Services, Llc | Authentication for third party digital wallet provisioning |
US10862540B1 (en) | 2019-12-23 | 2020-12-08 | Capital One Services, Llc | Method for mapping NFC field strength and location on mobile devices |
US10885410B1 (en) | 2019-12-23 | 2021-01-05 | Capital One Services, Llc | Generating barcodes utilizing cryptographic techniques |
US11651361B2 (en) | 2019-12-23 | 2023-05-16 | Capital One Services, Llc | Secure authentication based on passport data stored in a contactless card |
US11113685B2 (en) | 2019-12-23 | 2021-09-07 | Capital One Services, Llc | Card issuing with restricted virtual numbers |
CN111131444B (en) * | 2019-12-23 | 2020-09-29 | 广州公评科技有限公司 | Network course processing system based on block chain technology |
US10733283B1 (en) | 2019-12-23 | 2020-08-04 | Capital One Services, Llc | Secure password generation and management using NFC and contactless smart cards |
US11200563B2 (en) | 2019-12-24 | 2021-12-14 | Capital One Services, Llc | Account registration using a contactless card |
US10664941B1 (en) | 2019-12-24 | 2020-05-26 | Capital One Services, Llc | Steganographic image encoding of biometric template information on a card |
US10853795B1 (en) | 2019-12-24 | 2020-12-01 | Capital One Services, Llc | Secure authentication based on identity data stored in a contactless card |
CN111182525B (en) * | 2019-12-25 | 2022-09-02 | 中国联合网络通信集团有限公司 | Method and device for storing data |
US10909544B1 (en) | 2019-12-26 | 2021-02-02 | Capital One Services, Llc | Accessing and utilizing multiple loyalty point accounts |
US10757574B1 (en) | 2019-12-26 | 2020-08-25 | Capital One Services, Llc | Multi-factor authentication providing a credential via a contactless card for secure messaging |
US11038688B1 (en) | 2019-12-30 | 2021-06-15 | Capital One Services, Llc | Techniques to control applets for contactless cards |
US11455620B2 (en) | 2019-12-31 | 2022-09-27 | Capital One Services, Llc | Tapping a contactless card to a computing device to provision a virtual number |
US10860914B1 (en) | 2019-12-31 | 2020-12-08 | Capital One Services, Llc | Contactless card and method of assembly |
US11343075B2 (en) | 2020-01-17 | 2022-05-24 | Inveniam Capital Partners, Inc. | RAM hashing in blockchain environments |
US11982993B2 (en) | 2020-02-03 | 2024-05-14 | Strong Force TX Portfolio 2018, LLC | AI solution selection for an automated robotic process |
CA3076653A1 (en) | 2020-03-21 | 2021-09-21 | Upstream Data Inc. | Portable blockchain mining systems and methods of use |
CN111431696B (en) * | 2020-03-26 | 2023-10-17 | 深圳市欧欣泰科技有限公司 | Block chain seal mechanism based on identity |
US11210656B2 (en) | 2020-04-13 | 2021-12-28 | Capital One Services, Llc | Determining specific terms for contactless card activation |
US11222342B2 (en) | 2020-04-30 | 2022-01-11 | Capital One Services, Llc | Accurate images in graphical user interfaces to enable data transfer |
US11030339B1 (en) | 2020-04-30 | 2021-06-08 | Capital One Services, Llc | Systems and methods for data access control of personal user data using a short-range transceiver |
US10915888B1 (en) | 2020-04-30 | 2021-02-09 | Capital One Services, Llc | Contactless card with multiple rotating security keys |
US10861006B1 (en) | 2020-04-30 | 2020-12-08 | Capital One Services, Llc | Systems and methods for data access control using a short-range transceiver |
US11823175B2 (en) | 2020-04-30 | 2023-11-21 | Capital One Services, Llc | Intelligent card unlock |
CN111581627A (en) * | 2020-05-11 | 2020-08-25 | 北京精准沟通传媒科技股份有限公司 | Data processing method and device and electronic equipment |
US10963865B1 (en) | 2020-05-12 | 2021-03-30 | Capital One Services, Llc | Augmented reality card activation experience |
US11949784B2 (en) | 2020-05-13 | 2024-04-02 | Ridgeline, Inc. | Auditing for events |
US11818259B2 (en) | 2020-05-13 | 2023-11-14 | Ridgeline, Inc. | Query and projection processing for events |
US11233640B2 (en) * | 2020-05-13 | 2022-01-25 | Ridgeline, Inc. | Mutation processing for events |
US11063979B1 (en) | 2020-05-18 | 2021-07-13 | Capital One Services, Llc | Enabling communications between applications in a mobile operating system |
US11100511B1 (en) | 2020-05-18 | 2021-08-24 | Capital One Services, Llc | Application-based point of sale system in mobile operating systems |
CN113849851A (en) | 2020-06-28 | 2021-12-28 | 中兴通讯股份有限公司 | Proxy method, device and computer readable storage medium |
US11368310B2 (en) | 2020-07-11 | 2022-06-21 | Bank Of America Corporation | Data transfer between computing nodes of a distributed computing system |
CN111563130A (en) * | 2020-07-15 | 2020-08-21 | 成都无右区块链科技有限公司 | Data credible data management method and system based on block chain technology |
US11769209B2 (en) * | 2020-07-31 | 2023-09-26 | MediConCen Limited | Method and system for conducting and recording insurance claim transactions using blockchain |
US11062098B1 (en) | 2020-08-11 | 2021-07-13 | Capital One Services, Llc | Augmented reality information display and interaction via NFC based authentication |
CN112100142A (en) * | 2020-08-13 | 2020-12-18 | 广州汇才创智科技有限公司 | Block chain-based digital asset processing method and system |
CN111754349B (en) | 2020-08-28 | 2020-12-04 | 支付宝(杭州)信息技术有限公司 | Method and device for grouping transactions in blockchain |
CN111754350B (en) * | 2020-08-28 | 2020-11-24 | 支付宝(杭州)信息技术有限公司 | Method and device for parallelly acquiring serial numbers of transaction access variables in block chain |
CN112015460B (en) * | 2020-09-09 | 2023-11-03 | 南京工程学院 | Code responsibility-following method and system based on block chain technology |
US11917088B2 (en) | 2020-09-21 | 2024-02-27 | International Business Machines Corporation | Integrating device identity into a permissioning framework of a blockchain |
US11658832B2 (en) | 2020-09-22 | 2023-05-23 | Bank Of America Corporation | Information security using data control ledgers |
US11573953B2 (en) | 2020-09-22 | 2023-02-07 | Bank Of America Corporation | Error correction for integrated data control ledgers |
US11593351B2 (en) | 2020-09-22 | 2023-02-28 | Bank Of America Corporation | Error correction for data control ledgers |
US11763296B2 (en) | 2020-09-22 | 2023-09-19 | Bank Of America Corporation | Information security using integrated data control ledgers |
CN112162984B (en) * | 2020-09-28 | 2024-07-19 | 彩讯科技股份有限公司 | Real-name authentication method, system, equipment and storage medium based on blockchain |
CN112367165A (en) * | 2020-10-19 | 2021-02-12 | 珠海格力电器股份有限公司 | Serial port communication method and device, electronic equipment and computer readable medium |
DE102020127853A1 (en) * | 2020-10-22 | 2022-04-28 | Bundesdruckerei Gmbh | Method for personalizing an ID document, personalized ID document and method for authenticating a personalized ID document |
US11165586B1 (en) | 2020-10-30 | 2021-11-02 | Capital One Services, Llc | Call center web-based authentication using a contactless card |
US11482312B2 (en) | 2020-10-30 | 2022-10-25 | Capital One Services, Llc | Secure verification of medical status using a contactless card |
US11373169B2 (en) | 2020-11-03 | 2022-06-28 | Capital One Services, Llc | Web-based activation of contactless cards |
US11652636B2 (en) | 2020-11-03 | 2023-05-16 | Cognizant Technology Solutions India Pvt. Ltd. | System and method for securing and authenticating serialized data associated with a product |
GB2601824A (en) * | 2020-12-14 | 2022-06-15 | Mbj Tech Limited | Identity verification method and devices |
CN112702323B (en) * | 2020-12-14 | 2022-06-03 | 杭州溪塔科技有限公司 | License issuing verification method and device for block chain software and electronic equipment |
WO2022154957A1 (en) | 2020-12-29 | 2022-07-21 | CipherTrace, Inc. | Systems and methods for correlating cryptographic addresses between blockchain networks |
CN112651835B (en) * | 2020-12-30 | 2023-05-23 | 成都佳华物链云科技有限公司 | Alliance chain transaction method, device, electronic equipment and storage medium |
US11216799B1 (en) | 2021-01-04 | 2022-01-04 | Capital One Services, Llc | Secure generation of one-time passcodes using a contactless card |
CN112733089B (en) * | 2021-01-15 | 2021-09-17 | 深圳市龙影天下信息***有限公司 | Movie key distribution management method, movie key distribution management device, computer equipment and storage medium |
US11682012B2 (en) | 2021-01-27 | 2023-06-20 | Capital One Services, Llc | Contactless delivery systems and methods |
US11687930B2 (en) | 2021-01-28 | 2023-06-27 | Capital One Services, Llc | Systems and methods for authentication of access tokens |
US11562358B2 (en) | 2021-01-28 | 2023-01-24 | Capital One Services, Llc | Systems and methods for near field contactless card communication and cryptographic authentication |
US11792001B2 (en) | 2021-01-28 | 2023-10-17 | Capital One Services, Llc | Systems and methods for secure reprovisioning |
US11438329B2 (en) | 2021-01-29 | 2022-09-06 | Capital One Services, Llc | Systems and methods for authenticated peer-to-peer data transfer using resource locators |
US11777933B2 (en) | 2021-02-03 | 2023-10-03 | Capital One Services, Llc | URL-based authentication for payment cards |
TWI763294B (en) * | 2021-02-03 | 2022-05-01 | 宜鼎國際股份有限公司 | Data storage device, system, and method for digital signature |
US12026789B2 (en) | 2021-02-08 | 2024-07-02 | CipherTrace, Inc. | Systems and methods of forensic analysis of cryptocurrency transactions |
US11637826B2 (en) | 2021-02-24 | 2023-04-25 | Capital One Services, Llc | Establishing authentication persistence |
SG10202102327UA (en) * | 2021-03-08 | 2021-09-29 | Alipay Labs Singapore Pte Ltd | Methods and devices for verifying data integrity |
US11245438B1 (en) | 2021-03-26 | 2022-02-08 | Capital One Services, Llc | Network-enabled smart apparatus and systems and methods for activating and provisioning same |
US12008526B2 (en) | 2021-03-26 | 2024-06-11 | Inveniam Capital Partners, Inc. | Computer system and method for programmatic collateralization services |
US11170130B1 (en) | 2021-04-08 | 2021-11-09 | Aster Key, LLC | Apparatus, systems and methods for storing user profile data on a distributed database for anonymous verification |
US11961089B2 (en) | 2021-04-20 | 2024-04-16 | Capital One Services, Llc | On-demand applications to extend web services |
US11935035B2 (en) | 2021-04-20 | 2024-03-19 | Capital One Services, Llc | Techniques to utilize resource locators by a contactless card to perform a sequence of operations |
US11902442B2 (en) | 2021-04-22 | 2024-02-13 | Capital One Services, Llc | Secure management of accounts on display devices using a contactless card |
US11354555B1 (en) | 2021-05-04 | 2022-06-07 | Capital One Services, Llc | Methods, mediums, and systems for applying a display to a transaction card |
US12007972B2 (en) | 2021-06-19 | 2024-06-11 | Inveniam Capital Partners, Inc. | Systems and methods for processing blockchain transactions |
US12041172B2 (en) | 2021-06-25 | 2024-07-16 | Capital One Services, Llc | Cryptographic authentication to control access to storage devices |
US11451402B1 (en) * | 2021-07-29 | 2022-09-20 | IPAssets Technology Holdings Inc. | Cold storage cryptographic authentication apparatus and system |
US20230274246A1 (en) * | 2022-01-24 | 2023-08-31 | Deborah Zell | Item and ownership authentication, management and return |
DE202022101294U1 (en) | 2022-03-09 | 2022-03-23 | Neha Jain | A blockchain-based API system to improve user privacy in private blockchain-based applications |
WO2023212141A1 (en) * | 2022-04-27 | 2023-11-02 | Arey Scott Shiao | System and method to help enable creation of, distribution of, and/or access to content |
US11978038B2 (en) * | 2022-05-06 | 2024-05-07 | Paypal, Inc. | Hot wallet protection using a layer-2 blockchain network |
US11770788B1 (en) | 2022-06-03 | 2023-09-26 | Bloxtel Inc. | Systems and methods for deployment of a decentralized electronic subscriber identity module |
US20230418979A1 (en) * | 2022-06-24 | 2023-12-28 | Unstoppable Domains, Inc. | Data resolution using user domain names |
Family Cites Families (233)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5005200A (en) | 1988-02-12 | 1991-04-02 | Fischer Addison M | Public key/signature cryptosystem with enhanced digital signature certification |
US20020170966A1 (en) | 1995-07-27 | 2002-11-21 | Hannigan Brett T. | Identification document including embedded data |
US5901229A (en) * | 1995-11-06 | 1999-05-04 | Nippon Telegraph And Telephone Corp. | Electronic cash implementing method using a trustee |
US5862325A (en) | 1996-02-29 | 1999-01-19 | Intermind Corporation | Computer-based communication system and method using metadata defining a control structure |
US5923763A (en) * | 1996-03-21 | 1999-07-13 | Walker Asset Management Limited Partnership | Method and apparatus for secure document timestamping |
US6327656B2 (en) | 1996-07-03 | 2001-12-04 | Timestamp.Com, Inc. | Apparatus and method for electronic document certification and verification |
US5996076A (en) * | 1997-02-19 | 1999-11-30 | Verifone, Inc. | System, method and article of manufacture for secure digital certification of electronic commerce |
KR100486062B1 (en) | 1997-05-09 | 2005-04-29 | 지티이 서비스 코포레이션 | Biometric certificates |
US6985583B1 (en) | 1999-05-04 | 2006-01-10 | Rsa Security Inc. | System and method for authentication seed distribution |
US6785815B1 (en) | 1999-06-08 | 2004-08-31 | Intertrust Technologies Corp. | Methods and systems for encoding and protecting data using digital signature and watermarking techniques |
AU1432901A (en) * | 1999-10-18 | 2001-04-30 | Stamps.Com | Cryptographic module for secure processing of value-bearing items |
US6792536B1 (en) | 1999-10-20 | 2004-09-14 | Timecertain Llc | Smart card system and methods for proving dates in digital files |
US7949606B1 (en) * | 1999-12-03 | 2011-05-24 | William Sweet | Intellectual property brokerage system and method |
US7716484B1 (en) | 2000-03-10 | 2010-05-11 | Rsa Security Inc. | System and method for increasing the security of encrypted secrets and authentication |
WO2001067705A2 (en) * | 2000-03-10 | 2001-09-13 | Herbert Street Technologies Ltd. | A data transfer and management system |
US8447967B1 (en) * | 2000-06-29 | 2013-05-21 | Datamotion, Inc. | Controlled message distribution |
US8380630B2 (en) | 2000-07-06 | 2013-02-19 | David Paul Felsher | Information record infrastructure, system and method |
US7552333B2 (en) | 2000-08-04 | 2009-06-23 | First Data Corporation | Trusted authentication digital signature (tads) system |
AU2001287164B2 (en) | 2000-08-04 | 2008-06-26 | First Data Corporation | Method and system for using electronic communications for an electronic contact |
US7043635B1 (en) | 2000-09-15 | 2006-05-09 | Swivel Secure Limited | Embedded synchronous random disposable code identification method and system |
US20020071565A1 (en) | 2000-12-11 | 2002-06-13 | Kurn David Michael | Software process pre-authorization scheme for applications on a computer system |
US20020141593A1 (en) | 2000-12-11 | 2002-10-03 | Kurn David Michael | Multiple cryptographic key linking scheme on a computer system |
JP4185363B2 (en) * | 2001-02-22 | 2008-11-26 | ビーイーエイ システムズ, インコーポレイテッド | System and method for message encryption and signing in a transaction processing system |
US7216083B2 (en) * | 2001-03-07 | 2007-05-08 | Diebold, Incorporated | Automated transaction machine digital signature system and method |
US20030037261A1 (en) * | 2001-03-26 | 2003-02-20 | Ilumin Corporation | Secured content delivery system and method |
US7353204B2 (en) * | 2001-04-03 | 2008-04-01 | Zix Corporation | Certified transmission system |
US7257546B2 (en) * | 2001-09-04 | 2007-08-14 | Yahoo! Inc. | System and method for correlating user data from a content provider and user data from an advertising provider that is stored on autonomous systems |
US9189788B1 (en) | 2001-09-21 | 2015-11-17 | Open Invention Network, Llc | System and method for verifying identity |
US20030070075A1 (en) | 2001-10-04 | 2003-04-10 | Frederic Deguillaume | Secure hybrid robust watermarking resistant against tampering and copy-attack |
US7225161B2 (en) | 2001-12-21 | 2007-05-29 | Schlumberger Omnes, Inc. | Method and system for initializing a key management system |
WO2003103217A1 (en) | 2002-01-20 | 2003-12-11 | Scientific Generics Limited | Biometric authentication system |
US20030172273A1 (en) * | 2002-03-05 | 2003-09-11 | Sjoblom Hans | Method for controlling the distribution of data |
US7206934B2 (en) * | 2002-09-26 | 2007-04-17 | Sun Microsystems, Inc. | Distributed indexing of identity information in a peer-to-peer network |
US7644290B2 (en) * | 2003-03-31 | 2010-01-05 | Power Measurement Ltd. | System and method for seal tamper detection for intelligent electronic devices |
US20090266882A1 (en) | 2003-06-17 | 2009-10-29 | Sajkowsky James M | Smart passport system for monitoring and recording activity and data relating to persons |
DE10336805A1 (en) | 2003-08-11 | 2005-06-23 | Siemens Ag | Method for transmitting protected information to multiple recipients |
WO2005029746A2 (en) | 2003-09-12 | 2005-03-31 | Rsa Security Inc. | System and method providing disconnected authentication |
US7822988B2 (en) * | 2003-10-23 | 2010-10-26 | Microsoft Corporation | Method and system for identity recognition |
US20050114447A1 (en) * | 2003-10-24 | 2005-05-26 | Kim Cameron | Method and system for identity exchange and recognition for groups and group members |
JP2005260490A (en) | 2004-03-10 | 2005-09-22 | Murata Mach Ltd | Transmission apparatus |
US7373516B2 (en) | 2004-08-19 | 2008-05-13 | International Business Machines Corporation | Systems and methods of securing resources through passwords |
US7575168B2 (en) | 2004-10-01 | 2009-08-18 | Nokia Corporation | Methods, devices and computer program products for generating, displaying and capturing a series of images of visually encoded data |
DE102004052117A1 (en) | 2004-10-26 | 2006-04-27 | Zilch, André, Dr. | Identification documents production method involves obtaining electronic graphic data and electronic text data of customer, and obtaining signature of customer electronically to complete identification document for customer |
US7578436B1 (en) | 2004-11-08 | 2009-08-25 | Pisafe, Inc. | Method and apparatus for providing secure document distribution |
US8359611B2 (en) | 2005-03-08 | 2013-01-22 | International Business Machines Corporation | Searchable television commercials |
US20070016785A1 (en) * | 2005-07-14 | 2007-01-18 | Yannick Guay | System and method for digital signature and authentication |
CN100379190C (en) | 2005-07-19 | 2008-04-02 | 北京中星微电子有限公司 | Rate control method based on two-dimension code video transmission |
US20070033150A1 (en) | 2005-08-08 | 2007-02-08 | Enenia Biometrics, Inc. | Biometric web payment system |
US8903744B2 (en) * | 2005-11-18 | 2014-12-02 | Xerox Corporation | System and method for controlling access to personal identification information contained in documents |
FR2895125B1 (en) | 2005-12-21 | 2008-12-12 | Novatec Sa | METHOD OF AUTHENTICATING DOCUMENTS AND DEVICE FOR READING SAID DOCUMENTS FOR RECORDING FOR EVIDENCE |
JP4427513B2 (en) | 2006-01-16 | 2010-03-10 | 株式会社リコー | Card authentication system |
US8249965B2 (en) * | 2006-03-30 | 2012-08-21 | Obopay, Inc. | Member-supported mobile payment system |
US7873573B2 (en) * | 2006-03-30 | 2011-01-18 | Obopay, Inc. | Virtual pooled account for mobile banking |
KR100798651B1 (en) | 2006-06-16 | 2008-01-28 | 삼성전자주식회사 | Apparatus and method for dynamically changing password |
US8078880B2 (en) | 2006-07-28 | 2011-12-13 | Microsoft Corporation | Portable personal identity information |
US7766241B2 (en) | 2006-09-29 | 2010-08-03 | Konica Minolta Systems Laboratory, Inc. | Barcode for two-way verification of a document |
US7523865B2 (en) | 2006-09-29 | 2009-04-28 | Konica Minolta Systems Laboratory, Inc. | High resolution barcode and document including verification features |
JP4996904B2 (en) | 2006-10-04 | 2012-08-08 | 株式会社日立製作所 | Biometric authentication system, registration terminal, authentication terminal, and authentication server |
US20100020970A1 (en) | 2006-11-13 | 2010-01-28 | Xu Liu | System And Method For Camera Imaging Data Channel |
US7953670B2 (en) | 2006-12-27 | 2011-05-31 | Colella Brian A | Biometrically secured identification authentication and card reader device |
US8769637B2 (en) | 2007-03-23 | 2014-07-01 | Sap Ag | Iterated password hash systems and methods for preserving password entropy |
US8744076B2 (en) | 2007-04-04 | 2014-06-03 | Oracle International Corporation | Method and apparatus for encrypting data to facilitate resource savings and tamper detection |
US8058972B2 (en) | 2007-05-09 | 2011-11-15 | University Of North Texas | Methods and devices for enrollment and verification of biometric information in identification documents |
WO2009070430A2 (en) * | 2007-11-08 | 2009-06-04 | Suridx, Inc. | Apparatus and methods for providing scalable, dynamic, individualized credential services using mobile telephones |
US7904450B2 (en) * | 2008-04-25 | 2011-03-08 | Wilson Kelce S | Public electronic document dating list |
KR101007521B1 (en) | 2008-07-23 | 2011-01-18 | (주)에스알파트너즈 | Document authentication system using electronic signature of licensee and document authentication method thereof |
ATE524897T1 (en) | 2008-09-17 | 2011-09-15 | Gmv Soluciones Globales Internet S A | METHOD AND SYSTEM FOR AUTHENTICATING A USER USING A MOBILE TELEPHONE DEVICE |
US8788830B2 (en) | 2008-10-02 | 2014-07-22 | Ricoh Co., Ltd. | Method and apparatus for logging based identification |
US20110302412A1 (en) * | 2008-10-08 | 2011-12-08 | Leiwen Deng | Pseudonymous public keys based authentication |
EP2234028A1 (en) | 2009-02-26 | 2010-09-29 | Research In Motion Limited | System and method of handling encrypted backup data |
US9270420B2 (en) | 2009-04-24 | 2016-02-23 | Samsung Electronics Co., Ltd. | Data communication using 2D bar codes |
US9768965B2 (en) * | 2009-05-28 | 2017-09-19 | Adobe Systems Incorporated | Methods and apparatus for validating a digital signature |
US10255419B1 (en) | 2009-06-03 | 2019-04-09 | James F. Kragh | Identity validation and verification system and associated methods |
US8560353B2 (en) | 2009-06-25 | 2013-10-15 | Victor Smith | Receipt insurance systems and methods |
US8668137B2 (en) | 2009-07-02 | 2014-03-11 | Barcode Graphics Inc. | Barcode systems having multiple viewing angles |
US20120185398A1 (en) | 2009-09-17 | 2012-07-19 | Meir Weis | Mobile payment system with two-point authentication |
NZ624935A (en) * | 2009-10-19 | 2016-01-29 | Theranos Inc | Integrated health data capture and analysis system |
US8430301B2 (en) | 2009-11-23 | 2013-04-30 | Konica Minolta Laboratory U.S.A., Inc. | Document authentication using hierarchical barcode stamps to detect alterations of barcode |
DE102009055947A1 (en) | 2009-11-30 | 2011-06-01 | Christoph Busch | Authenticated transmission of data |
US8924302B2 (en) | 2009-12-11 | 2014-12-30 | Eoriginal, Inc. | System and method for electronic transmission, storage, retrieval and remote signing of authenticated electronic original documents |
US8522024B2 (en) | 2009-12-31 | 2013-08-27 | Feitian Technologies Co., Ltd. | Authentication method, system, and device |
US20110231913A1 (en) * | 2010-03-17 | 2011-09-22 | State of Oregon acting by and through the State Board of Education on Behalf of Portland State | System and methods of determining computational puzzle difficulty for challenge-response authentication |
EP2553863A1 (en) | 2010-03-29 | 2013-02-06 | Intel Corporation | Methods and apparatuses for administrator-driven profile update |
US8788842B2 (en) | 2010-04-07 | 2014-07-22 | Apple Inc. | System and method for content protection based on a combination of a user PIN and a device specific identifier |
US8601263B1 (en) | 2010-05-18 | 2013-12-03 | Google Inc. | Storing encrypted objects |
US10193689B2 (en) | 2010-05-19 | 2019-01-29 | International Business Machines Corporation | Storing access information in a dispersed storage network |
DE102010030590A1 (en) | 2010-06-28 | 2011-12-29 | Bundesdruckerei Gmbh | Procedure for generating a certificate |
US8832807B1 (en) | 2010-08-05 | 2014-09-09 | Christine E. Kuo | Method and apparatus for asynchronous dynamic password |
US20130173484A1 (en) | 2010-09-18 | 2013-07-04 | Philip Wesby | System and Method for Encoding and Controlled Authentication |
US8342406B2 (en) | 2010-09-20 | 2013-01-01 | Research In Motion Limited | System and method for data transfer through animated barcodes |
US8756706B2 (en) * | 2010-10-12 | 2014-06-17 | Blackberry Limited | Method for securing credentials in a remote repository |
US8381973B2 (en) | 2010-11-22 | 2013-02-26 | International Business Machines Corporation | System and method for providing and verifying a passport |
WO2012125655A1 (en) | 2011-03-14 | 2012-09-20 | Conner Investments, Llc | Bluetooth enabled credit card with a large date storage volume |
US20120308003A1 (en) | 2011-05-31 | 2012-12-06 | Verisign, Inc. | Authentic barcodes using digital signatures |
US9141779B2 (en) | 2011-05-19 | 2015-09-22 | Microsoft Technology Licensing, Llc | Usable security of online password management with sensor-based authentication |
US9721078B2 (en) | 2011-06-29 | 2017-08-01 | Alclear Llc | System and method for user enrollment in a secure biometric verification system |
US9355393B2 (en) | 2011-08-18 | 2016-05-31 | Visa International Service Association | Multi-directional wallet connector apparatuses, methods and systems |
US9240058B1 (en) | 2011-07-12 | 2016-01-19 | A9.Com, Inc. | Dynamic barcode generation for content location |
US8646686B2 (en) | 2011-08-11 | 2014-02-11 | Benton William Bullwinkel | Secure system for creating and validating personal identification cards with operator discretion |
US8874915B1 (en) * | 2011-09-28 | 2014-10-28 | Amazon Technologies, Inc. | Optimized encryption key exchange |
US8943320B2 (en) | 2011-10-31 | 2015-01-27 | Novell, Inc. | Techniques for authentication via a mobile device |
KR20130055794A (en) | 2011-11-21 | 2013-05-29 | 주식회사 케이티 | User device for sharing qr code information, and method of sharing qr code information using user device |
CN102497265B (en) | 2011-11-24 | 2014-03-12 | 飞天诚信科技股份有限公司 | Pulse light signal identification method and apparatus thereof |
EP2786369A4 (en) * | 2011-11-30 | 2016-12-07 | Overtone Labs Inc | Drum and drum-set tuner |
US8635448B2 (en) * | 2011-12-06 | 2014-01-21 | Cisco Technology, Inc. | Secure prefix authorization with untrusted mapping services |
GB2497580A (en) | 2011-12-16 | 2013-06-19 | Intercede Ltd | Data transmission using a plurality of barcodes displayed in a loop |
US8751794B2 (en) * | 2011-12-28 | 2014-06-10 | Pitney Bowes Inc. | System and method for secure nework login |
US8776194B2 (en) | 2012-02-01 | 2014-07-08 | Amazon Technologies, Inc. | Authentication management services |
US20130228624A1 (en) | 2012-03-02 | 2013-09-05 | Mastercard International Incorporated | Method and apparatus for transferring and receiving data using multi-frame bar codes |
US10503888B2 (en) | 2012-03-16 | 2019-12-10 | Traitware, Inc. | Authentication system |
US20160337351A1 (en) | 2012-03-16 | 2016-11-17 | Acuity Systems, Inc. | Authentication system |
DE13771788T1 (en) | 2012-04-01 | 2015-12-17 | Authentify, Inc. | Secure authentication in a multiparty system |
US20130262309A1 (en) | 2012-04-02 | 2013-10-03 | Mpayme Ltd. | Method and System for Secure Mobile Payment |
US9087204B2 (en) | 2012-04-10 | 2015-07-21 | Sita Information Networking Computing Ireland Limited | Airport security check system and method therefor |
US20130290733A1 (en) | 2012-04-26 | 2013-10-31 | Appsense Limited | Systems and methods for caching security information |
US9642005B2 (en) * | 2012-05-21 | 2017-05-02 | Nexiden, Inc. | Secure authentication of a user using a mobile device |
US8925059B2 (en) * | 2012-06-08 | 2014-12-30 | Lockheed Martin Corporation | Dynamic trust connection |
US20140006806A1 (en) | 2012-06-23 | 2014-01-02 | Pomian & Corella, Llc | Effective data protection for mobile devices |
US9947005B2 (en) | 2012-06-24 | 2018-04-17 | Amx Llc | Method and apparatus of processing symbology interactions between mobile stations and a control system |
CN103516687B (en) * | 2012-06-27 | 2016-08-17 | ***股份有限公司 | Security information interaction system, Apparatus and method for |
US8762712B1 (en) * | 2012-07-27 | 2014-06-24 | Trend Micro Incorporated | Methods and system for person-to-person secure file transfer |
US8770484B2 (en) | 2012-09-21 | 2014-07-08 | Alcatel Lucent | Data exchange using streamed barcodes |
US20150278805A1 (en) | 2012-10-01 | 2015-10-01 | Acuity Systems, Inc. | Authentication system |
US20140093144A1 (en) | 2012-10-01 | 2014-04-03 | Dannie Gerrit Feekes | More-Secure Hardware Token |
US9876775B2 (en) | 2012-11-09 | 2018-01-23 | Ent Technologies, Inc. | Generalized entity network translation (GENT) |
US10102510B2 (en) | 2012-11-28 | 2018-10-16 | Hoverkey Ltd. | Method and system of conducting a cryptocurrency payment via a mobile device using a contactless token to store and protect a user's secret key |
US20160005032A1 (en) * | 2012-11-28 | 2016-01-07 | Hoverkey Ltd. | Method and system of providing authentication of user access to a computer resource via a mobile device using multiple separate security factors |
US9172699B1 (en) | 2012-11-30 | 2015-10-27 | Microstrategy Incorporated | Associating a device with a user account |
US9069879B2 (en) * | 2012-12-27 | 2015-06-30 | Dropbox, Inc. | Globally unique identifiers in an online content management system |
US9741265B2 (en) | 2012-12-31 | 2017-08-22 | Piyush Bhatnagar | System, design and process for secure documents credentials management using out-of-band authentication |
US9412283B2 (en) | 2012-12-31 | 2016-08-09 | Piyush Bhatnagar | System, design and process for easy to use credentials management for online accounts using out-of-band authentication |
US8869303B2 (en) | 2013-02-16 | 2014-10-21 | Mikhail Fleysher | Method and system for generation of dynamic password |
US20140254796A1 (en) | 2013-03-08 | 2014-09-11 | The Chinese University Of Hong Kong | Method and apparatus for generating and/or processing 2d barcode |
US9059858B1 (en) * | 2013-03-11 | 2015-06-16 | Ca, Inc. | User characteristic based digital signature of documents |
US9269224B2 (en) | 2013-03-11 | 2016-02-23 | Cfph, Llc | Devices for gaming |
US9130929B2 (en) | 2013-03-15 | 2015-09-08 | Aol Inc. | Systems and methods for using imaging to authenticate online users |
WO2014182957A1 (en) | 2013-05-08 | 2014-11-13 | Acuity Systems, Inc. | Authentication system |
US20140344015A1 (en) * | 2013-05-20 | 2014-11-20 | José Antonio Puértolas-Montañés | Systems and methods enabling consumers to control and monetize their personal data |
JP6096893B2 (en) | 2013-05-28 | 2017-03-15 | 株式会社日立製作所 | Biometric signature system, registration terminal and signature generation terminal |
EP3036672A4 (en) * | 2013-08-21 | 2017-04-26 | Ascribe GmbH | Method to securely establish, affirm, and transfer ownership of artworks |
US20180082050A1 (en) | 2013-09-08 | 2018-03-22 | Yona Flink | Method and a system for secure login to a computer, computer network, and computer website using biometrics and a mobile computing wireless electronic communication device |
US9710808B2 (en) | 2013-09-16 | 2017-07-18 | Igor V. SLEPININ | Direct digital cash system and method |
US9646150B2 (en) | 2013-10-01 | 2017-05-09 | Kalman Csaba Toth | Electronic identity and credentialing system |
US9465800B2 (en) | 2013-10-01 | 2016-10-11 | Trunomi Ltd. | Systems and methods for sharing verified identity documents |
US20150104005A1 (en) | 2013-10-10 | 2015-04-16 | Elwha Llc | Methods, systems, and devices for handling captured image data that is received by devices |
US9087205B2 (en) | 2013-10-11 | 2015-07-21 | Sap Se | Shared encrypted storage |
KR101450013B1 (en) | 2013-12-20 | 2014-10-13 | 주식회사 시큐브 | Authentication system and method using Quick Response(QR) code |
US9639710B2 (en) | 2013-12-23 | 2017-05-02 | Symantec Corporation | Device-based PIN authentication process to protect encrypted data |
US9838388B2 (en) | 2014-08-26 | 2017-12-05 | Veridium Ip Limited | System and method for biometric protocol standards |
US10163105B1 (en) | 2014-01-24 | 2018-12-25 | Microstrategy Incorporated | Variable biometrics for multi-factor authentication |
US20160012465A1 (en) * | 2014-02-08 | 2016-01-14 | Jeffrey A. Sharp | System and method for distributing, receiving, and using funds or credits and apparatus thereof |
US9331856B1 (en) | 2014-02-10 | 2016-05-03 | Symantec Corporation | Systems and methods for validating digital signatures |
WO2015142765A1 (en) * | 2014-03-17 | 2015-09-24 | Coinbase, Inc | Bitcoin host computer system |
US20150269614A1 (en) * | 2014-03-18 | 2015-09-24 | Onename Global, Inc. | Combination Social Media Dashboard, Social Media Website Network and Monetized Advertisement Marketplace |
US9608822B2 (en) | 2014-03-18 | 2017-03-28 | Ecole Polytechnique Federale De Lausanne (Epfl) | Method for generating an HTML document that contains encrypted files and the code necessary for decrypting them when a valid passphrase is provided |
US9594919B2 (en) | 2014-03-21 | 2017-03-14 | Samunsung Electronics Co., Ltd. | System and method for executing file by using biometric information |
CA2980707A1 (en) * | 2014-03-25 | 2015-10-01 | Botanic Technologies, Inc. | Systems and methods for executing cryptographically secure transactions using voice and natural language processing |
US9135787B1 (en) | 2014-04-04 | 2015-09-15 | Mark Russell | Bitcoin kiosk/ATM device and system integrating enrollment protocol and method of using the same |
US20150302401A1 (en) * | 2014-04-18 | 2015-10-22 | Ebay Inc. | Distributed crypto currency unauthorized transfer monitoring system |
US10340038B2 (en) * | 2014-05-13 | 2019-07-02 | Nant Holdings Ip, Llc | Healthcare transaction validation via blockchain, systems and methods |
US9818092B2 (en) * | 2014-06-04 | 2017-11-14 | Antti Pennanen | System and method for executing financial transactions |
US20150356523A1 (en) | 2014-06-07 | 2015-12-10 | ChainID LLC | Decentralized identity verification systems and methods |
US9509720B2 (en) * | 2014-06-12 | 2016-11-29 | Cisco Technology, Inc. | Techniques for improved run time trustworthiness |
WO2016014969A1 (en) | 2014-07-24 | 2016-01-28 | Marvell Semiconductor, Inc. | Group acknowledgement for multiple user communication in a wireless local area network |
US9608829B2 (en) | 2014-07-25 | 2017-03-28 | Blockchain Technologies Corporation | System and method for creating a multi-branched blockchain with configurable protocol rules |
AU2015311866B2 (en) | 2014-09-03 | 2018-06-07 | Nant Holdings Ip, Llc | Synthetic genomic variant-based secure transaction devices, systems and methods |
US20160098730A1 (en) * | 2014-10-01 | 2016-04-07 | The Filing Cabinet, LLC | System and Method for Block-Chain Verification of Goods |
US20160098723A1 (en) * | 2014-10-01 | 2016-04-07 | The Filing Cabinet, LLC | System and method for block-chain verification of goods |
US9749297B2 (en) * | 2014-11-12 | 2017-08-29 | Yaron Gvili | Manicoding for communication verification |
US20160162897A1 (en) | 2014-12-03 | 2016-06-09 | The Filing Cabinet, LLC | System and method for user authentication using crypto-currency transactions as access tokens |
GB2533340A (en) * | 2014-12-17 | 2016-06-22 | Ibm | Network system and method for transferring cryptocurrencies between a user account and a receiving account |
US10110385B1 (en) * | 2014-12-22 | 2018-10-23 | Amazon Technologies, Inc. | Duress signatures |
EP3040898A1 (en) * | 2014-12-31 | 2016-07-06 | Gemalto Sa | System and method for obfuscating an identifier to protect the identifier from impermissible appropriation |
US20160217436A1 (en) * | 2015-01-25 | 2016-07-28 | Dror Samuel Brama | Method, System and Program Product for Tracking and Securing Transactions of Authenticated Items over Block Chain Systems. |
US10257179B1 (en) | 2015-01-26 | 2019-04-09 | Microstrategy Incorporated | Credential management system and peer detection |
US10594484B2 (en) | 2015-02-13 | 2020-03-17 | Yoti Holding Limited | Digital identity system |
US10853592B2 (en) | 2015-02-13 | 2020-12-01 | Yoti Holding Limited | Digital identity system |
WO2016145454A1 (en) | 2015-03-12 | 2016-09-15 | Wiacts, Inc. | Multi-factor user authentication |
US10146923B2 (en) | 2015-03-20 | 2018-12-04 | Aplcomp Oy | Audiovisual associative authentication method, related system and device |
US20160283939A1 (en) * | 2015-03-25 | 2016-09-29 | Qualcomm Incorporated | System and method to prevent loss of bitcoins due to address errors |
SI3073670T1 (en) | 2015-03-27 | 2021-07-30 | Black Gold Coin, Inc. | A system and a method for personal identification and verification |
US20180240107A1 (en) * | 2015-03-27 | 2018-08-23 | Black Gold Coin, Inc. | Systems and methods for personal identification and verification |
US20160283920A1 (en) | 2015-03-28 | 2016-09-29 | Justin Fisher | Authentication and verification of digital data utilizing blockchain technology |
US20160300234A1 (en) | 2015-04-06 | 2016-10-13 | Bitmark, Inc. | System and method for decentralized title recordation and authentication |
US9397985B1 (en) * | 2015-04-14 | 2016-07-19 | Manifold Technology, Inc. | System and method for providing a cryptographic platform for exchanging information |
US9876646B2 (en) * | 2015-05-05 | 2018-01-23 | ShoCard, Inc. | User identification management system and method |
CN107851111A (en) | 2015-05-05 | 2018-03-27 | 识卡公司 | Use the identity management services of block chain |
US20170228731A1 (en) | 2016-02-09 | 2017-08-10 | Fmr Llc | Computationally Efficient Transfer Processing and Auditing Apparatuses, Methods and Systems |
US20170109735A1 (en) | 2015-07-14 | 2017-04-20 | Fmr Llc | Computationally Efficient Transfer Processing and Auditing Apparatuses, Methods and Systems |
US10033702B2 (en) * | 2015-08-05 | 2018-07-24 | Intralinks, Inc. | Systems and methods of secure data exchange |
US10419514B2 (en) | 2015-08-14 | 2019-09-17 | Oracle International Corporation | Discovery of federated logins |
US10148437B2 (en) | 2015-09-21 | 2018-12-04 | Oracle International Corporation | Encryption system with key recovery |
US20170103389A1 (en) | 2015-10-07 | 2017-04-13 | Aerius, Inc. | Electronic Payment Validation and Authorization System |
KR101637854B1 (en) | 2015-10-16 | 2016-07-08 | 주식회사 코인플러그 | Certificate issuance system and method based on block chain, certificate authentication system and method based on block chain |
US9948467B2 (en) | 2015-12-21 | 2018-04-17 | Mastercard International Incorporated | Method and system for blockchain variant using digital signatures |
US10079682B2 (en) * | 2015-12-22 | 2018-09-18 | Gemalto Sa | Method for managing a trusted identity |
US10475036B2 (en) * | 2016-01-08 | 2019-11-12 | Ca, Inc. | Restricting account use by controlled replenishment |
US10341091B2 (en) | 2016-01-15 | 2019-07-02 | Bittium Wireless Oy | Secure memory storage |
US9679276B1 (en) | 2016-01-26 | 2017-06-13 | Stampery, Inc. | Systems and methods for using a block chain to certify the existence, integrity, and/or ownership of a file or communication |
US20190342096A1 (en) | 2016-02-11 | 2019-11-07 | Evident ID, Inc. | Online identity and credential verification systems and methods protecting user data |
US11354658B2 (en) | 2016-02-11 | 2022-06-07 | Mastercard International Incorporated | Method and system for offline blockchain exchanges |
US10587609B2 (en) | 2016-03-04 | 2020-03-10 | ShoCard, Inc. | Method and system for authenticated login using static or dynamic codes |
US10509932B2 (en) | 2016-03-07 | 2019-12-17 | ShoCard, Inc. | Large data transfer using visual codes with feedback confirmation |
US10007826B2 (en) | 2016-03-07 | 2018-06-26 | ShoCard, Inc. | Transferring data files using a series of visual codes |
US20170279788A1 (en) | 2016-03-28 | 2017-09-28 | Internet Brands, Inc. | Secure remote password retrieval |
US20170324711A1 (en) * | 2016-05-03 | 2017-11-09 | The Real Mccoy, Llc Inc. | Method for establishing, securing and transferring computer readable information using peer-to-peer public and private key cryptography |
US20170344988A1 (en) | 2016-05-24 | 2017-11-30 | Ubs Ag | System and method for facilitating blockchain-based validation |
US10204341B2 (en) | 2016-05-24 | 2019-02-12 | Mastercard International Incorporated | Method and system for an efficient consensus mechanism for permissioned blockchains using bloom filters and audit guarantees |
US10574692B2 (en) | 2016-05-30 | 2020-02-25 | Christopher Nathan Tyrwhitt Drake | Mutual authentication security system with detection and mitigation of active man-in-the-middle browser attacks, phishing, and malware and other security improvements |
US11025618B2 (en) | 2016-06-09 | 2021-06-01 | Logmein, Inc. | Mobile device access to a protected account associated with a website |
US10108954B2 (en) | 2016-06-24 | 2018-10-23 | PokitDok, Inc. | System and method for cryptographically verified data driven contracts |
WO2018027059A1 (en) | 2016-08-03 | 2018-02-08 | KryptCo, Inc. | Systems and methods for delegated cryptography |
US10511589B2 (en) | 2016-09-14 | 2019-12-17 | Oracle International Corporation | Single logout functionality for a multi-tenant identity and data security management cloud service |
US11170346B2 (en) | 2016-09-19 | 2021-11-09 | Sap Se | Decentralized credentials verification network |
US20180343120A1 (en) | 2016-10-26 | 2018-11-29 | Black Gold Coin, Inc. | Systems and methods for providing a universal decentralized solution for verification of users with cross-verification features |
US10484178B2 (en) | 2016-10-26 | 2019-11-19 | Black Gold Coin, Inc. | Systems and methods for providing a universal decentralized solution for verification of users with cross-verification features |
EP3536002B1 (en) | 2016-11-08 | 2020-11-18 | Aware, Inc. | Decentralized biometric identity authentication |
US10460126B2 (en) | 2016-11-21 | 2019-10-29 | Adobe Inc. | Providing user control of shared personal information |
FR3061974B1 (en) | 2017-01-18 | 2020-04-24 | Safran Identity and Security | METHOD AND DEVICE FOR VERIFYING THE VALIDITY OF AN ELECTRONIC DOCUMENT |
WO2018145127A1 (en) | 2017-02-06 | 2018-08-09 | ShoCard, Inc. | Electronic identification verification methods and systems with storage of certification records to a side chain |
US10498541B2 (en) | 2017-02-06 | 2019-12-03 | ShocCard, Inc. | Electronic identification verification methods and systems |
DE102017113529A1 (en) | 2017-06-12 | 2018-12-13 | Rubean AG | Method and system for checking the authenticity of a trusted user interface |
US10805085B1 (en) | 2017-08-24 | 2020-10-13 | United Services Automobile Association (Usaa) | PKI-based user authentication for web services using blockchain |
US10642967B2 (en) | 2017-11-28 | 2020-05-05 | American Express Travel Related Services Company, Inc. | Single sign-on solution using blockchain |
EP3721578B1 (en) * | 2017-12-08 | 2022-09-07 | Ping Identity Corporation | Methods and systems for recovering data using dynamic passwords |
US10885220B2 (en) | 2018-01-24 | 2021-01-05 | Zortag Inc. | Secure access to physical and digital assets using authentication key |
KR101893729B1 (en) | 2018-03-28 | 2018-10-04 | 주식회사 마크로젠 | Data sharing method based on multiple block-chains |
EP3791341A1 (en) | 2018-05-11 | 2021-03-17 | Civic Technologies, Inc. | Rewards and penalties of the reward function for the attestation game |
US11082221B2 (en) | 2018-10-17 | 2021-08-03 | Ping Identity Corporation | Methods and systems for creating and recovering accounts using dynamic passwords |
US10979227B2 (en) | 2018-10-17 | 2021-04-13 | Ping Identity Corporation | Blockchain ID connect |
US11134065B2 (en) | 2018-12-06 | 2021-09-28 | Visa International Service Association | Secured extended range application data exchange |
US11128471B2 (en) | 2019-04-25 | 2021-09-21 | Microsoft Technology Licensing, Llc | Accessibility controls in distributed data systems |
US20220029799A1 (en) * | 2020-12-18 | 2022-01-27 | Signzy Technologies Private Limited | System and method for creating one or more hashes for biometric authentication in real-time |
-
2016
- 2016-05-04 CN CN201680039853.3A patent/CN107851111A/en active Pending
- 2016-05-04 US US15/146,881 patent/US9722790B2/en active Active
- 2016-05-04 EP EP16790050.5A patent/EP3292484B1/en active Active
- 2016-05-04 JP JP2018510317A patent/JP2018516030A/en active Pending
- 2016-05-04 CA CA2984888A patent/CA2984888A1/en not_active Abandoned
- 2016-05-04 WO PCT/US2016/030863 patent/WO2016179334A1/en active Application Filing
- 2016-05-04 EP EP21181229.2A patent/EP3955146A1/en active Pending
- 2016-05-04 US US15/146,872 patent/US10007913B2/en active Active
-
2017
- 2017-07-03 US US15/640,795 patent/US10657532B2/en active Active
-
2018
- 2018-06-26 US US16/018,773 patent/US20180308098A1/en not_active Abandoned
-
2020
- 2020-12-15 US US17/121,971 patent/US20210334808A1/en not_active Abandoned
-
2022
- 2022-03-10 US US17/691,597 patent/US20220337419A1/en not_active Abandoned
- 2022-05-06 US US17/738,106 patent/US11544367B2/en active Active
- 2022-12-19 US US18/068,083 patent/US20230196362A1/en active Pending
Cited By (7)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US11658961B2 (en) | 2016-03-04 | 2023-05-23 | Ping Identity Corporation | Method and system for authenticated login using static or dynamic codes |
US11799668B2 (en) | 2017-02-06 | 2023-10-24 | Ping Identity Corporation | Electronic identification verification methods and systems with storage of certification records to a side chain |
USRE49968E1 (en) | 2017-02-06 | 2024-05-14 | Ping Identity Corporation | Electronic identification verification methods and systems with storage of certification records to a side chain |
US11777726B2 (en) | 2017-12-08 | 2023-10-03 | Ping Identity Corporation | Methods and systems for recovering data using dynamic passwords |
US11652644B1 (en) * | 2018-03-09 | 2023-05-16 | Wells Fargo Bank, N.A. | Quantum-resistant double signature system |
US11722301B2 (en) | 2018-10-17 | 2023-08-08 | Ping Identity Corporation | Blockchain ID connect |
US11818265B2 (en) | 2018-10-17 | 2023-11-14 | Ping Identity Corporation | Methods and systems for creating and recovering accounts using dynamic passwords |
Also Published As
Publication number | Publication date |
---|---|
EP3292484A4 (en) | 2018-05-30 |
US20210334808A1 (en) | 2021-10-28 |
CN107851111A (en) | 2018-03-27 |
US9722790B2 (en) | 2017-08-01 |
EP3292484B1 (en) | 2021-07-07 |
JP2018516030A (en) | 2018-06-14 |
US20230196362A1 (en) | 2023-06-22 |
EP3292484A1 (en) | 2018-03-14 |
US11544367B2 (en) | 2023-01-03 |
US20180308098A1 (en) | 2018-10-25 |
US10007913B2 (en) | 2018-06-26 |
EP3955146A1 (en) | 2022-02-16 |
US20160330027A1 (en) | 2016-11-10 |
CA2984888A1 (en) | 2016-11-10 |
WO2016179334A1 (en) | 2016-11-10 |
US20220342973A1 (en) | 2022-10-27 |
US20170302450A1 (en) | 2017-10-19 |
US20160328713A1 (en) | 2016-11-10 |
US10657532B2 (en) | 2020-05-19 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US11544367B2 (en) | Systems, apparatus and methods for secure electrical communication of biometric personal identification information to validate the identity of an individual | |
US11799668B2 (en) | Electronic identification verification methods and systems with storage of certification records to a side chain | |
US11777726B2 (en) | Methods and systems for recovering data using dynamic passwords | |
US11082221B2 (en) | Methods and systems for creating and recovering accounts using dynamic passwords | |
CN110692214B (en) | Method and system for ownership verification using blockchain | |
US10432402B1 (en) | Biometric electronic signature tokens | |
US9876646B2 (en) | User identification management system and method | |
WO2018145127A1 (en) | Electronic identification verification methods and systems with storage of certification records to a side chain | |
CN110598433B (en) | Block chain-based anti-fake information processing method and device | |
CN110999254A (en) | Securely performing cryptographic operations | |
US11070378B1 (en) | Signcrypted biometric electronic signature tokens | |
USRE49968E1 (en) | Electronic identification verification methods and systems with storage of certification records to a side chain | |
CN116647413B (en) | Application login method, device, computer equipment and storage medium | |
Oliveira | Dynamic QR codes for Ticketing Systems |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
STPP | Information on status: patent application and granting procedure in general |
Free format text: DOCKETED NEW CASE - READY FOR EXAMINATION |
|
AS | Assignment |
Owner name: PING IDENTITY CORPORATION, COLORADO Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:EBRAHIMI, ARMIN;REEL/FRAME:060686/0307 Effective date: 20211123 Owner name: SHOCARD, LLC, COLORADO Free format text: CHANGE OF NAME;ASSIGNOR:SHOCARD, INC.;REEL/FRAME:061032/0770 Effective date: 20200302 Owner name: PING IDENTITY CORPORATION, COLORADO Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:SHOCARD, LLC;REEL/FRAME:060686/0450 Effective date: 20200505 Owner name: SHOCARD, INC., CALIFORNIA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:EBRAHIMI, ARMIN;REEL/FRAME:060686/0433 Effective date: 20161213 |
|
AS | Assignment |
Owner name: OWL ROCK CAPITAL CORPORATION, AS COLLATERAL AGENT, NEW YORK Free format text: GRANT OF SECURITY INTEREST IN PATENT RIGHTS;ASSIGNOR:PING IDENTITY CORPORATION;REEL/FRAME:061703/0988 Effective date: 20221018 |
|
STCB | Information on status: application discontinuation |
Free format text: EXPRESSLY ABANDONED -- DURING EXAMINATION |