EP3400541B1 - Systems and methods for providing block chain-based multifactor personal identity verification - Google Patents
Systems and methods for providing block chain-based multifactor personal identity verification Download PDFInfo
- Publication number
- EP3400541B1 EP3400541B1 EP16897290.9A EP16897290A EP3400541B1 EP 3400541 B1 EP3400541 B1 EP 3400541B1 EP 16897290 A EP16897290 A EP 16897290A EP 3400541 B1 EP3400541 B1 EP 3400541B1
- Authority
- EP
- European Patent Office
- Prior art keywords
- individual
- biometric data
- verification
- private key
- identity
- 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.)
- Active
Links
- 238000012795 verification Methods 0.000 title claims description 96
- 238000000034 method Methods 0.000 title claims description 30
- 210000001525 retina Anatomy 0.000 claims description 6
- 230000005021 gait Effects 0.000 claims description 2
- 230000033764 rhythmic process Effects 0.000 claims description 2
- 210000003462 vein Anatomy 0.000 claims description 2
- 238000012545 processing Methods 0.000 description 15
- 230000003542 behavioural effect Effects 0.000 description 9
- 230000004044 response Effects 0.000 description 7
- 230000008569 process Effects 0.000 description 6
- 238000000605 extraction Methods 0.000 description 5
- 230000007246 mechanism Effects 0.000 description 5
- 238000004891 communication Methods 0.000 description 4
- 238000005516 engineering process Methods 0.000 description 4
- 230000003993 interaction Effects 0.000 description 2
- 230000000007 visual effect Effects 0.000 description 2
- 238000013459 approach Methods 0.000 description 1
- 230000015572 biosynthetic process Effects 0.000 description 1
- 230000001419 dependent effect Effects 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 238000003384 imaging method Methods 0.000 description 1
- 230000010365 information processing Effects 0.000 description 1
- 238000004519 manufacturing process Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 238000003786 synthesis reaction Methods 0.000 description 1
Images
Classifications
-
- 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/08—Key distribution or management, e.g. generation, sharing or updating, of cryptographic keys or passwords
- H04L9/0861—Generation of secret information including derivation or calculation of cryptographic keys or passwords
- H04L9/0866—Generation of secret information including derivation or calculation of cryptographic keys or passwords involving user or device identifiers, e.g. serial number, physical or biometrical information, DNA, hand-signature or measurable physical characteristics
-
- 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/36—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using electronic wallets or electronic money safes
-
- 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
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
-
- 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
-
- 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/34—User authentication involving the use of external additional devices, e.g. dongles or smart cards
- G06F21/35—User authentication involving the use of external additional devices, e.g. dongles or smart cards communicating wirelessly
-
- 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/40—User authentication by quorum, i.e. whereby two or more security principals are required
-
- 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/41—User authentication where a single sign-on provides access to a plurality of computers
-
- 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
-
- 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
-
- 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/3829—Payment protocols; Details thereof insuring higher security of transaction involving key management
-
- 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
- G06Q20/40145—Biometric identity checks
-
- 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
-
- 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/006—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols involving public key infrastructure [PKI] trust models
-
- 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
-
- 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
- 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
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L2463/00—Additional details relating to network architectures or network communication protocols for network security covered by H04L63/00
- H04L2463/082—Additional details relating to network architectures or network communication protocols for network security covered by H04L63/00 applying multi-factor authentication
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L2463/00—Additional details relating to network architectures or network communication protocols for network security covered by H04L63/00
- H04L2463/102—Additional details relating to network architectures or network communication protocols for network security covered by H04L63/00 applying security measure for e-commerce
-
- 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
-
- 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/40—Network security protocols
Definitions
- This disclosure relates to systems and methods for providing block chain-based multifactor personal identity verification.
- US application US 2015/0324789 A1 discloses virtual wallets used to store and execute transactions using cryptocurrency.
- the security of the cryptocurrency transaction is enhanced by utilizing three encryption keys stored in three different locations to secure the wallet.
- FIG. 1 illustrates a system 100 for providing block chain-based multifactor personal identity verification, in accordance with one or more implementations.
- system 100 may include one or more servers 102.
- the server(s) 102 may be configured to communicate with one or more computing platforms 104 according to a client/server architecture, a peer-to-peer architecture, and/or other architectures.
- the users may access system 100 via computing platform(s) 104.
- the server(s) 102 may be configured to execute machine-readable instructions 106.
- the machine-readable instructions 106 may include one or more of an individual identifier component 108, a verification address assignment component 110, an address recordation component 112, a user interface component 114, a verification request component 116, an information extraction component 118, an identity verification component 120, and/or other machine-readable instruction components.
- the machine-readable instructions 106 may be executable to establish verification addresses on a block chain.
- a block chain is a transaction database shared by some or all nodes participating in system 100. Such participation may be based on the Bitcoin protocol, Ethereum protocol, and/or other protocols related to digital currencies and/or block chains. A full copy of the block chain contains every transaction ever executed in an associated digital currency. In addition to transactions, other information may be contained by the block chain, such as described further herein.
- the block chain may be based on several blocks.
- a block may include a record that contains and confirms one or more waiting transactions. Periodically (e.g., roughly every one minute), a new block including transactions and/or other information may be appended to the block chain.
- a given block in the block chain contains a hash of the previous block. This may have the effect of creating a chain of blocks from a genesis block (i.e., the first block in the block chain) to a current block.
- the given block may be guaranteed to come chronologically after a previous block because the previous block's hash would otherwise not be known.
- the given block may be computationally impractical to modify once it is included in the block chain because every block after it would also have to be regenerated.
- a given verification address may include a specific location on the block chain where certain information is stored.
- an individual verification address may be referred to as an "AtenVerify Address.” Verification addresses are further described below in connection with verification address assignment component 110.
- the individual identifier component 108 may be configured to associated identifiers with individuals having previously verified personal identities. For example, a first identifier may be associated a first individual. The first individual may have a previously verified personal identity. Generally speaking, an identifier may include one or more of a number, an alphanumeric code, a username, and/or other information that can be linked to an individual. In some implementations, an individual identifier may be referred to as an "Aten ID.”
- an individual having a previously verified personal identity may have obtained the previously verified personal identity through a variety of approaches.
- the individual may be required to provide evidence of the individual's identity.
- Such evidence may include one or more of providing a copy of a government issued identification (e.g., passport and/or driver's license), providing a copy of mail received by the individual (e.g., a utility bill), evidence provided by a third party, and/or other evidence on an individual's identity.
- the evidence may be provided to an entity associated with server(s) 102.
- the verification address assignment component 110 may be configured to assign verification addresses on a block chain to the individuals.
- a given verification address may include a public key and a private key.
- a first verification address may be assigned to the first individual.
- the first verification address may include a first public key and a first private key.
- a public and private key-pair may be used for encryption and decryption according to one or more public key algorithms.
- a key pair may be used for digital signatures.
- Such a key pair may include a private key for signing and a public key for verification.
- the public key may be widely distributed, while the private key is kept secret (e.g., known only to its proprietor).
- the keys may be related mathematically, but calculating the private key from the public key is unfeasible.
- verification address assignment component 110 may be configured such that private keys may be stored within computing platform(s) 104.
- the first private key may be stored within a computing platform 104 and/or other locations associated with the first individual.
- a private key may be stored in one or more of a "verify.dat" file, a SIM card, and/or other locations.
- verification address assignment component 110 may be configured such that multiple verification addresses may be assigned to separate individuals. For example, in addition to the first verification address, a second verification address may be assigned to the first individual. One or more additional verification addresses may be assigned to the first individual, in accordance with one or more implementations.
- the address recordation component 112 may be configured to record identifiers and biometric data associated with the individuals at corresponding verification addresses.
- the first identifier and first biometric data associated with the first individual may be recorded at the first verification address.
- Recording information at a given verification address may include recording a hash or other encrypted representation of the information.
- different biometric data may be recorded at multiple verification addresses assigned to a single given individual.
- the first identifier and second biometric data associated with the first individual may be recorded at a second verification address.
- biometric data may include metrics related to human characteristics.
- Biometric identifiers are distinctive, measurable characteristics that can be used to label and describe individuals. Biometric identifiers are typically include physiological characteristics, but may also include behavioral characteristics and/or other characteristics.
- Physiological characteristics may be related to the shape of an individual's body. Examples of physiological characteristics used as biometric data may include one or more of fingerprint, palm veins, face recognition, DNA, palm print, hand geometry, iris recognition, retina, odor or scent, and/or other physiological characteristics.
- Behavioral characteristics may be related to a pattern of behavior of an individual. Examples of behavioral characteristics used as biometric data may include one or more of typing rhythm, gait, voice, and/or other behavioral characteristics.
- the biometric data may include one or more of an image or other visual representation of a physiological characteristic, a recording of a behavioral characteristic, a template of a physiological characteristic and/or behavioral characteristic, and/or other biometric data.
- a template may include a synthesis of relevant features extracted from the source.
- a template may include one or more of a vector describing features of a physiological characteristic and/or behavioral characteristic, a numerical representation of a physiological characteristic and/or behavioral characteristic, an image with particular properties, and/or other information.
- Biometric data may be received via computing platforms 104 associated with the individuals.
- biometric data associated with a first individual may be received via a first computing platform 104 associated with the first individual.
- the first computing platform 104 may include an input device (not depicted) configured to capture and/or record a physiological characteristic and/or behavioral characteristic of the first individual. Examples of such an input device may include one or more of a camera and/or other imaging device, a fingerprint scanner, a microphone, an accelerometer, and/or other input devices.
- the user interface component 114 may be configured to provide an interface for presentation to individuals via associated computing platforms 104.
- the interface may include a graphical user interface presented via individual computing platforms 104.
- the interface may be configured to allow a given individual to add or delete verification addresses assigned to the given individual so long as at least one verification address is assigned to the given individual.
- user interface component 114 may be configured to access and/or manage one or more user profiles and/or user information associated with users of system 100.
- the one or more user profiles and/or user information may include information stored by server(s) 102, one or more of the computing platform(s) 104, and/or other storage locations.
- the user profiles may include, for example, information identifying users (e.g., a username or handle, a number, an identifier, and/or other identifying information), security login information (e.g., a login code or password), system account information, subscription information, digital currency account information (e.g., related to currency held in credit for a user), relationship information (e.g., information related to relationships between users in system 100), system usage information, demographic information associated with users, interaction history among users in the system 100, information stated by users, purchase information of users, browsing history of users, a computing platform identification associated with a user, a phone number associated with a user, and/or other information related to users.
- information identifying users e.g., a username or handle, a number, an identifier, and/or other identifying information
- security login information e.g., a login code or password
- system account information e.g., subscription information, digital currency account information (e.g., related to currency held in credit for a user),
- the machine-readable instructions 106 may be executable to perform block chain-based multifactor personal identity verification using the verification addresses.
- the verification request component 116 may be configured to receive one or more identifiers in connection with one or more requests to verify an identity of one or more individuals.
- the first identifier may be received in connection with a request to verify an identity of the first individual.
- Requests for identity verification may be provided in connection with and/or related to financial transactions, information exchanges, and/or other interactions. Requests may be received from other individuals and/or other third parties.
- the information extraction component 118 may be configured to extract the biometric data associated with the one or more individuals from the corresponding verification addresses.
- the first biometric data associated with the first individual may be extracted from the first verification address.
- Extracting information e.g., biometric data
- decrypting information may include decrypting information.
- information extraction component 118 may be configured such that, responsive to receiving the request to verify the identity of the first individual, a prompt may be provided to the first individual for biometric data matching the first biometric data and a private key matching the first private key.
- the prompt may be conveyed via a computing platform 104 associated with the first individual.
- the prompt may be conveyed via a graphical user interface and/or other user interface provided by the computing platform 104 associated with the first individual.
- the prompt may include an indication that is one or more of visual, audible, haptic, and/or other indications.
- information extraction component 118 may be configured such that, responsive to receiving the request to verify the identity of the first individual, a prompt may be provided to a computing platform 104 associated with the first individual.
- the prompt may cause the computing platform 104 to automatically provide, to server(s) 102, biometric data matching the first biometric data and/or a private key matching the first private key.
- the identity verification component 120 may be configured to verify the identity of the one or more individuals upon, or in response to, receiving matching biometric data and private keys. For example, the personal identity of the first individual may be verified upon receipt of (1) biometric data matching the first biometric data and (2) a private key matching the first private key. Verifying the personal identity of the first individual may include comparing stored information with newly received information.
- identity verification component 120 may be configured such that the personal identity of the first individual may be verified upon receipt of (1) biometric data matching the first biometric data or the second biometric data and (2) a private key matching the first private key.
- biometric data matching the first biometric data or the second biometric data
- private key matching the first private key.
- Such implementations may provide so-called "M-of-N" signatures for identity verification where some subset of a larger set of identifying information is required.
- identity verification component 120 may be configured such that the biometric data matching the first biometric data and the private key matching the first private key may be used to sign the verification of the personal identity of the first individual.
- a cryptographic signature is a mathematical mechanism that allows someone to prove ownership.
- a Bitcoin wallet and its private key(s) are linked by some mathematical magic.
- your Bitcoin software signs a transaction with the appropriate private key, the whole network can see that the signature matches the Bitcoins being spent. However, there is no way for the world to guess your private key to steal your hard-earned bitcoins.
- At least one dedicated node performs the signing of the verification of the personal identity of the first individual.
- a given dedicated node may include one or more of the server(s) 102.
- the given dedicated node may be a public node or a private node configured for creating new blocks and/or for signing verification.
- server(s) 102, computing platform(s) 104, and/or external resources 122 may be operatively linked via one or more electronic communication links.
- electronic communication links may be established, at least in part, via a network such as the Internet and/or other networks. It will be appreciated that this is not intended to be limiting, and that the scope of this disclosure includes implementations in which server(s) 102, computing platform(s) 104, and/or external resources 122 may be operatively linked via some other communication media.
- a given computing platform 104 may include one or more processors configured to execute machine-readable instructions.
- the machine-readable instructions may be configured to enable an expert or user associated with the given computing platform 104 to interface with system 100 and/or external resources 122, and/or provide other functionality attributed herein to computing platform(s) 104.
- the given computing platform 104 may include one or more of a desktop computer, a laptop computer, a handheld computer, a tablet computing platform, a NetBook, a Smartphone, a gaming console, and/or other computing platforms.
- External resources 122 may include sources of information, hosts and/or providers of virtual environments outside of system 100, external entities participating with system 100, and/or other resources. In some implementations, some or all of the functionality attributed herein to external resources 100 may be provided by resources included in system 100.
- Server(s) 102 may include electronic storage 124, one or more processors 126, and/or other components. Server(s) 102 may include communication lines, or ports to enable the exchange of information with a network and/or other computing platforms. Illustration of server(s) 102 in FIG. 1 is not intended to be limiting. Server(s) 102 may include a plurality of hardware, software, and/or firmware components operating together to provide the functionality attributed herein to server(s) 102. For example, server(s) 102 may be implemented by a cloud of computing platforms operating together as server(s) 102.
- Electronic storage 124 may comprise non-transitory storage media that electronically stores information.
- the electronic storage media of electronic storage 124 may include one or both of system storage that is provided integrally (i.e., substantially non-removable) with server(s) 102 and/or removable storage that is removably connectable to server(s) 102 via, for example, a port (e.g., a USB port, a firewire port, etc.) or a drive (e.g., a disk drive, etc.).
- a port e.g., a USB port, a firewire port, etc.
- a drive e.g., a disk drive, etc.
- Electronic storage 124 may include one or more of optically readable storage media (e.g., optical disks, etc.), magnetically readable storage media (e.g., magnetic tape, magnetic hard drive, floppy drive, etc.), electrical charge-based storage media (e.g., EEPROM, RAM, etc.), solid-state storage media (e.g., flash drive, etc.), and/or other electronically readable storage media.
- Electronic storage 124 may include one or more virtual storage resources (e.g., cloud storage, a virtual private network, and/or other virtual storage resources).
- Electronic storage 124 may store software algorithms, information determined by processor(s) 126, information received from server(s) 102, information received from computing platform(s) 104, and/or other information that enables server(s) 102 to function as described herein.
- Processor(s) 126 may be configured to provide information processing capabilities in server(s) 102.
- processor(s) 126 may include one or more of a digital processor, an analog processor, a digital circuit designed to process information, an analog circuit designed to process information, a state machine, and/or other mechanisms for electronically processing information.
- processor(s) 126 is shown in FIG. 1 as a single entity, this is for illustrative purposes only.
- processor(s) 126 may include a plurality of processing units. These processing units may be physically located within the same device, or processor(s) 126 may represent processing functionality of a plurality of devices operating in coordination.
- the processor(s) 126 may be configured to execute machine-readable instruction components 108, 110, 112, 114, 116, 118, 120, and/or other machine-readable instruction components.
- Processor(s) 126 may be configured to execute machine-readable instruction components 108, 110, 112, 114, 116, 118, 120, and/or other machine-readable instruction components by software; hardware; firmware; some combination of software, hardware, and/or firmware; and/or other mechanisms for configuring processing capabilities on processor(s) 126.
- the term "machine-readable instruction component” may refer to any component or set of components that perform the functionality attributed to the machine-readable instruction component. This may include one or more physical processors during execution of processor readable instructions, the processor readable instructions, circuitry, hardware, storage media, or any other components.
- machine-readable instruction components 108, 110, 112, 114, 116, 118, and 120 are illustrated in FIG. 1 as being implemented within a single processing unit, in implementations in which processor(s) 126 includes multiple processing units, one or more of machine-readable instruction components 108, 110, 112, 114, 116, 118, and/or 120 may be implemented remotely from the other machine-readable instruction components.
- machine-readable instruction components 108, 110, 112, 114, 116, 118, and/or 120 described below is for illustrative purposes, and is not intended to be limiting, as any of machine-readable instruction components 108, 110, 112, 114, 116, 118, and/or 120 may provide more or less functionality than is described.
- one or more of machine-readable instruction components 108, 110, 112, 114, 116, 118, and/or 120 may be eliminated, and some or all of its functionality may be provided by other ones of machine-readable instruction components 108, 110, 112, 114, 116, 118, and/or 120.
- processor(s) 126 may be configured to execute one or more additional machine-readable instruction components that may perform some or all of the functionality attributed below to one of machine-readable instruction components 108, 110, 112, 114, 116, 118, and/or 120.
- FIG. 2 illustrates a method 200 for establishing verification addresses on a block chain in order to provide block chain-based multifactor personal identity verification, in accordance with one or more implementations.
- the operations of method 200 presented below are intended to be illustrative. In some implementations, method 200 may be accomplished with one or more additional operations not described, and/or without one or more of the operations discussed. Additionally, the order in which the operations of method 200 are illustrated in FIG. 2 and described below is not intended to be limiting.
- one or more operations of method 200 may be implemented in one or more processing devices (e.g., a digital processor, an analog processor, a digital circuit designed to process information, an analog circuit designed to process information, a state machine, and/or other mechanisms for electronically processing information).
- the one or more processing devices may include one or more devices executing some or all of the operations of method 200 in response to instructions stored electronically on an electronic storage medium.
- the one or more processing devices may include one or more devices configured through hardware, firmware, and/or software to be specifically designed for execution of one or more of the operations of method 200.
- identifiers may be associated with individuals having previously verified personal identities.
- a first identifier may be associated a first individual.
- the first individual may have a previously verified personal identity.
- Operation 202 may be performed by one or more hardware processors configured to execute a machine-readable instruction component that is the same as or similar to individual identifier component 108 (as described in connection with FIG. 1 ), in accordance with one or more implementations.
- verification addresses on a block chain may be assigned to the individuals.
- a given verification address may include a public key and a private key.
- a first verification address may be assigned to the first individual.
- the first verification address may include a first public key and a first private key.
- Operation 204 may be performed by one or more hardware processors configured to execute a machine-readable instruction component that is the same as or similar to verification address assignment component 110 (as described in connection with FIG. 1 ), in accordance with one or more implementations.
- identifiers and biometric data associated with the individuals may be recorded at corresponding verification addresses.
- the first identifier and first biometric data associated with the first individual may be recorded at the first verification address.
- the identity of the one or more individuals may be verifiable upon, or in response to, receiving matching biometric data and private keys.
- the personal identity of the first individual may be verifiable upon, or in response to, receipt of (1) biometric data matching the first biometric data and (2) a private key matching the first private key.
- Operation 206 may be performed by one or more hardware processors configured to execute a machine-readable instruction component that is the same as or similar to address recordation component 112 (as described in connection with FIG. 1 ), in accordance with one or more implementations.
- FIG. 3 illustrates a method 300 for performing block chain-based multifactor personal identity verification using verification addresses, in accordance with one or more implementations.
- the operations of method 300 presented below are intended to be illustrative. In some implementations, method 300 may be accomplished with one or more additional operations not described, and/or without one or more of the operations discussed. Additionally, the order in which the operations of method 300 are illustrated in FIG. 3 and described below is not intended to be limiting.
- method 300 may be implemented in one or more processing devices (e.g., a digital processor, an analog processor, a digital circuit designed to process information, an analog circuit designed to process information, a state machine, and/or other mechanisms for electronically processing information).
- the one or more processing devices may include one or more devices executing some or all of the operations of method 300 in response to instructions stored electronically on an electronic storage medium.
- the one or more processing devices may include one or more devices configured through hardware, firmware, and/or software to be specifically designed for execution of one or more of the operations of method 300.
- one or more identifiers may be received in connection with one or more requests to verify an identity of one or more individuals.
- a first identifier may be received in connection with a request to verify an identity of a first individual.
- Operation 302 may be performed by one or more hardware processors configured to execute a machine-readable instruction component that is the same as or similar to verification request component 116 (as described in connection with FIG. 1 ), in accordance with one or more implementations.
- biometric data associated with the one or more individuals may be extracted from corresponding verification addresses on a block chain.
- a given verification address may include a public key and a private key.
- First biometric data associated with the first individual may extracted from a first verification address assigned to the first individual.
- the first verification address may include a first public key and a first private key.
- Operation 304 may be performed by one or more hardware processors configured to execute a machine-readable instruction component that is the same as or similar to information extraction component 118 (as described in connection with FIG. 1 ), in accordance with one or more implementations.
- the identity of the one or more individuals may be verified upon, or in response to, receiving matching biometric data and private keys.
- the personal identity of the first individual may be verified upon, or in response to, receipt of (1) biometric data matching the first biometric data and (2) a private key matching the first private key.
- Operation 306 may be performed by one or more hardware processors configured to execute a machine-readable instruction component that is the same as or similar to identity verification component 120 (as described in connection with FIG. 1 ), in accordance with one or more implementations.
- Exemplary implementations may facilitate storing personal data on the block chain.
- the personal data may be stored on the block chain in an encrypted way.
- a person may be identified at the block chain level with one or more of a private key, a finger print, a finger print hash, an eye retina, an eye retina hash, and/or other unique information.
- the data stored may include or relate to one or more of a passport, an identification card, extracted passport information, a driver's license, extracted driver's license information, finger print, eye retina, and/or other information.
- a new record may be created for that person in the block chain. That is, all changes are added as new records. The old record will always be stored on the block chain. Generally speaking, all records on the block chain are stored forever and cannot be removed. More than one copy of the block chain will exist to ensure the records are not manipulated.
- Exemplary implementations may facilitate access to personal data.
- Access controls may be grated on public/private key pairs levels. Examples of access levels may include one or more of Super Admin (full access to block chain), authorities-country level (full read-only access), authorities-state/local level (limited read-only access), police and other services including Emergency (access to certain personal data by Finger Print/Eye retina of that person only), Participating Merchants (limited access), and/or other access levels.
- Exemplary implementations may facilitate verification check. There may be multiple levels for how it is possible to check verification. For example, some implementations may ensure a person has a record at "Company" but no personal data is provided. Some implementations may ensure a person has a record at Company and get very basic personal information such as Full Name, DOB, Gender, and/or other basic information. Some implementations may ensure a person has a record at Company and get all personal data.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Security & Cryptography (AREA)
- Business, Economics & Management (AREA)
- Theoretical Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Accounting & Taxation (AREA)
- General Engineering & Computer Science (AREA)
- Signal Processing (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Computer Hardware Design (AREA)
- General Health & Medical Sciences (AREA)
- Biomedical Technology (AREA)
- Health & Medical Sciences (AREA)
- Computing Systems (AREA)
- Strategic Management (AREA)
- Finance (AREA)
- General Business, Economics & Management (AREA)
- Software Systems (AREA)
- Biodiversity & Conservation Biology (AREA)
- Data Mining & Analysis (AREA)
- Databases & Information Systems (AREA)
- Life Sciences & Earth Sciences (AREA)
- Collating Specific Patterns (AREA)
- Storage Device Security (AREA)
- Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Priority Applications (5)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
EP18206482.4A EP3486854A1 (en) | 2016-03-28 | 2016-03-29 | Systems and methods for providing block chain-based multifactor personal identity verification |
EP18206522.7A EP3483816A1 (en) | 2016-03-28 | 2016-03-29 | Systems and methods for providing block chain-based multifactor personal identity verification |
EP18206524.3A EP3483817A1 (en) | 2016-03-28 | 2016-03-29 | Systems and methods for providing block chain-based multifactor personal identity verification |
EP18206468.3A EP3483814A1 (en) | 2016-03-28 | 2016-03-29 | Systems and methods for providing block chain-based multifactor personal identity verification |
EP18206477.4A EP3483815A1 (en) | 2016-03-28 | 2016-03-29 | Systems and methods for providing block chain-based multifactor personal identity verification |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US15/083,241 US9985964B2 (en) | 2016-03-28 | 2016-03-28 | Systems and methods for providing block chain-based multifactor personal identity verification |
PCT/US2016/024776 WO2017171733A1 (en) | 2016-03-28 | 2016-03-29 | Systems and methods for providing block chain-based multifactor personal identity verification |
Related Child Applications (10)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
EP18206477.4A Division EP3483815A1 (en) | 2016-03-28 | 2016-03-29 | Systems and methods for providing block chain-based multifactor personal identity verification |
EP18206477.4A Division-Into EP3483815A1 (en) | 2016-03-28 | 2016-03-29 | Systems and methods for providing block chain-based multifactor personal identity verification |
EP18206522.7A Division EP3483816A1 (en) | 2016-03-28 | 2016-03-29 | Systems and methods for providing block chain-based multifactor personal identity verification |
EP18206522.7A Division-Into EP3483816A1 (en) | 2016-03-28 | 2016-03-29 | Systems and methods for providing block chain-based multifactor personal identity verification |
EP18206524.3A Division EP3483817A1 (en) | 2016-03-28 | 2016-03-29 | Systems and methods for providing block chain-based multifactor personal identity verification |
EP18206524.3A Division-Into EP3483817A1 (en) | 2016-03-28 | 2016-03-29 | Systems and methods for providing block chain-based multifactor personal identity verification |
EP18206482.4A Division EP3486854A1 (en) | 2016-03-28 | 2016-03-29 | Systems and methods for providing block chain-based multifactor personal identity verification |
EP18206482.4A Division-Into EP3486854A1 (en) | 2016-03-28 | 2016-03-29 | Systems and methods for providing block chain-based multifactor personal identity verification |
EP18206468.3A Division EP3483814A1 (en) | 2016-03-28 | 2016-03-29 | Systems and methods for providing block chain-based multifactor personal identity verification |
EP18206468.3A Division-Into EP3483814A1 (en) | 2016-03-28 | 2016-03-29 | Systems and methods for providing block chain-based multifactor personal identity verification |
Publications (3)
Publication Number | Publication Date |
---|---|
EP3400541A1 EP3400541A1 (en) | 2018-11-14 |
EP3400541A4 EP3400541A4 (en) | 2018-11-21 |
EP3400541B1 true EP3400541B1 (en) | 2020-10-21 |
Family
ID=59896616
Family Applications (6)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
EP18206468.3A Withdrawn EP3483814A1 (en) | 2016-03-28 | 2016-03-29 | Systems and methods for providing block chain-based multifactor personal identity verification |
EP18206522.7A Withdrawn EP3483816A1 (en) | 2016-03-28 | 2016-03-29 | Systems and methods for providing block chain-based multifactor personal identity verification |
EP18206477.4A Withdrawn EP3483815A1 (en) | 2016-03-28 | 2016-03-29 | Systems and methods for providing block chain-based multifactor personal identity verification |
EP18206482.4A Withdrawn EP3486854A1 (en) | 2016-03-28 | 2016-03-29 | Systems and methods for providing block chain-based multifactor personal identity verification |
EP16897290.9A Active EP3400541B1 (en) | 2016-03-28 | 2016-03-29 | Systems and methods for providing block chain-based multifactor personal identity verification |
EP18206524.3A Withdrawn EP3483817A1 (en) | 2016-03-28 | 2016-03-29 | Systems and methods for providing block chain-based multifactor personal identity verification |
Family Applications Before (4)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
EP18206468.3A Withdrawn EP3483814A1 (en) | 2016-03-28 | 2016-03-29 | Systems and methods for providing block chain-based multifactor personal identity verification |
EP18206522.7A Withdrawn EP3483816A1 (en) | 2016-03-28 | 2016-03-29 | Systems and methods for providing block chain-based multifactor personal identity verification |
EP18206477.4A Withdrawn EP3483815A1 (en) | 2016-03-28 | 2016-03-29 | Systems and methods for providing block chain-based multifactor personal identity verification |
EP18206482.4A Withdrawn EP3486854A1 (en) | 2016-03-28 | 2016-03-29 | Systems and methods for providing block chain-based multifactor personal identity verification |
Family Applications After (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
EP18206524.3A Withdrawn EP3483817A1 (en) | 2016-03-28 | 2016-03-29 | Systems and methods for providing block chain-based multifactor personal identity verification |
Country Status (38)
Country | Link |
---|---|
US (10) | US9985964B2 (es) |
EP (6) | EP3483814A1 (es) |
JP (6) | JP3220620U (es) |
KR (5) | KR20180133944A (es) |
CN (5) | CN109657445A (es) |
AU (5) | AU2016400090B2 (es) |
BR (5) | BR112018070096A2 (es) |
CA (1) | CA3006587A1 (es) |
CL (1) | CL2018002724A1 (es) |
CO (1) | CO2018011415A2 (es) |
CR (1) | CR20180514A (es) |
CU (1) | CU20180116A7 (es) |
DE (6) | DE202016008686U1 (es) |
DK (1) | DK201870697A1 (es) |
EA (1) | EA035080B1 (es) |
EC (1) | ECSP18079192A (es) |
EE (1) | EE201800028A (es) |
ES (1) | ES2692871B2 (es) |
FI (1) | FI20185901A1 (es) |
GB (7) | GB2564787B (es) |
HR (1) | HRP20181711A2 (es) |
HU (1) | HUP1800363A1 (es) |
IL (5) | IL261839B (es) |
MA (1) | MA43326B1 (es) |
MX (3) | MX2018010163A (es) |
NO (1) | NO343876B1 (es) |
NZ (1) | NZ744540A (es) |
PH (1) | PH12018502087A1 (es) |
PL (1) | PL427232A1 (es) |
PT (1) | PT2017171733B (es) |
RS (1) | RS20181135A1 (es) |
RU (1) | RU2667801C1 (es) |
SA (1) | SA518392296B1 (es) |
SE (1) | SE1851298A1 (es) |
SG (1) | SG11201804658SA (es) |
SV (1) | SV2018005745A (es) |
WO (2) | WO2017171733A1 (es) |
ZA (1) | ZA201805308B (es) |
Families Citing this family (216)
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 |
US11277412B2 (en) | 2018-05-28 | 2022-03-15 | Royal Bank Of Canada | System and method for storing and distributing consumer information |
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 |
WO2016164496A1 (en) * | 2015-04-06 | 2016-10-13 | Bitmark, Inc. | System and method for decentralized title recordation and authentication |
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 |
US11032286B1 (en) | 2015-12-02 | 2021-06-08 | United Services Automobile Association (Usaa) | Block chain authentication systems and methods |
US10454677B1 (en) | 2016-02-24 | 2019-10-22 | United Services Automobile Associate (USAA) | Cryptographic key generation from biometric data |
US9985964B2 (en) * | 2016-03-28 | 2018-05-29 | Black Gold Coin, Inc. | Systems and methods for providing block chain-based multifactor personal identity verification |
US10546296B2 (en) * | 2016-04-13 | 2020-01-28 | Paypal, Inc. | Public ledger authentication system |
US10366388B2 (en) * | 2016-04-13 | 2019-07-30 | Tyco Fire & Security Gmbh | Method and apparatus for information management |
US11120507B2 (en) | 2016-04-14 | 2021-09-14 | Sensoriant, Inc. | Confirmation and rating of user generated activities |
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 |
US10341309B1 (en) * | 2016-06-13 | 2019-07-02 | Allstate Insurance Company | Cryptographically protecting data transferred between spatially distributed computing devices using an intermediary database |
US11854011B1 (en) | 2016-07-11 | 2023-12-26 | United Services Automobile Association (Usaa) | Identity management framework |
JP7047760B2 (ja) * | 2016-07-29 | 2022-04-05 | 日本電気株式会社 | システム、データ管理方法及びプログラム |
GB201613233D0 (en) * | 2016-08-01 | 2016-09-14 | 10Am Ltd | Data protection system and method |
US11769146B1 (en) * | 2016-09-30 | 2023-09-26 | Hrb Innovations, Inc. | Blockchain transactional identity verification |
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 |
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 |
US10373159B2 (en) * | 2016-12-07 | 2019-08-06 | International Business Machines Corporation | Concomitance of an asset and identity block of a blockchain |
US11423351B2 (en) * | 2016-12-15 | 2022-08-23 | International Business Machines Corporation | Blockchain-based food product shelf-life management |
US10637646B2 (en) * | 2017-02-01 | 2020-04-28 | Equifax Inc. | Verifying an identity based on multiple distributed data sources using a blockchain to safeguard the identity |
CN107040582B (zh) | 2017-02-17 | 2020-08-14 | 创新先进技术有限公司 | 一种数据处理方法及装置 |
US11538031B2 (en) * | 2017-03-31 | 2022-12-27 | Vijay Madisetti | Method and system for identity and access management for blockchain interoperability |
US10362517B2 (en) | 2017-04-07 | 2019-07-23 | Vapor IO Inc. | Distributed handoff-related processing for wireless networks |
US11238543B2 (en) * | 2017-05-06 | 2022-02-01 | Adp, Llc | Payroll based blockchain identity |
US10762506B1 (en) | 2017-05-11 | 2020-09-01 | United Services Automobile Association | Token device for distributed ledger based interchange |
US10129269B1 (en) | 2017-05-15 | 2018-11-13 | Forcepoint, LLC | Managing blockchain access to user profile information |
US10917423B2 (en) | 2017-05-15 | 2021-02-09 | Forcepoint, LLC | Intelligently differentiating between different types of states and attributes when using an adaptive trust profile |
US10862927B2 (en) | 2017-05-15 | 2020-12-08 | Forcepoint, LLC | Dividing events into sessions during adaptive trust profile operations |
US9882918B1 (en) | 2017-05-15 | 2018-01-30 | Forcepoint, LLC | User behavior profile in a blockchain |
US10999296B2 (en) | 2017-05-15 | 2021-05-04 | Forcepoint, LLC | Generating adaptive trust profiles using information derived from similarly situated organizations |
US10999297B2 (en) | 2017-05-15 | 2021-05-04 | Forcepoint, LLC | Using expected behavior of an entity when prepopulating an adaptive trust profile |
US10447718B2 (en) | 2017-05-15 | 2019-10-15 | Forcepoint Llc | User profile definition and management |
US10623431B2 (en) | 2017-05-15 | 2020-04-14 | Forcepoint Llc | Discerning psychological state from correlated user behavior and contextual information |
US10943019B2 (en) | 2017-05-15 | 2021-03-09 | Forcepoint, LLC | Adaptive trust profile endpoint |
US10146792B1 (en) * | 2017-05-31 | 2018-12-04 | Symbiont.Io, Inc. | Systems and methods for implementing a programming model for smart contracts within a decentralized computer network |
US20180365691A1 (en) * | 2017-06-15 | 2018-12-20 | KoopaCoin LLC | Identity ledger in crypto currency transactions |
US10318729B2 (en) | 2017-07-26 | 2019-06-11 | Forcepoint, LLC | Privacy protection during insider threat monitoring |
US10805085B1 (en) | 2017-08-24 | 2020-10-13 | United Services Automobile Association (Usaa) | PKI-based user authentication for web services using blockchain |
US10637662B2 (en) * | 2017-08-28 | 2020-04-28 | International Business Machines Corporation | Identity verification using biometric data and non-invertible functions via a blockchain |
US11528147B2 (en) | 2017-09-13 | 2022-12-13 | Vijay Madisetti | Verifying integrity and secure operations of cloud-based software services |
US20190228409A1 (en) * | 2017-09-13 | 2019-07-25 | Vijay Madisetti | Transaction Pools Using Smart Contracts and Blockchains |
US11316933B2 (en) | 2017-09-13 | 2022-04-26 | Vijay Madisetti | Service meshes and smart contracts for zero-trust systems |
US11283865B2 (en) | 2017-09-13 | 2022-03-22 | Vijay Madisetti | Service meshes and smart contracts for zero-trust systems |
CN113204532A (zh) | 2017-10-04 | 2021-08-03 | 邓白氏公司 | 跨全异的不可变分布式账本网络进行身份解析的系统和方法 |
US10682981B2 (en) * | 2017-10-11 | 2020-06-16 | Uniquid, Inc. | Systems and methods for networked device security |
CN108171494A (zh) | 2017-11-23 | 2018-06-15 | 阿里巴巴集团控股有限公司 | 一种数据处理方法和装置 |
US10771449B2 (en) * | 2017-12-04 | 2020-09-08 | Mastercard International Incorporated | Method and system for trustworthiness using digital certificates |
US11836717B2 (en) | 2017-12-04 | 2023-12-05 | Vijay Madisetti | System and method for processing payments in fiat currency using blockchain and tethered tokens |
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 |
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 |
WO2019126471A1 (en) * | 2017-12-21 | 2019-06-27 | Taliware, Inc. | Blockchain network management implementing biometric based authentication of an individual |
US11438139B2 (en) * | 2018-02-07 | 2022-09-06 | Raouf Boutaba | Blockchain based secure naming and update verification |
CN108446314B (zh) * | 2018-02-07 | 2021-08-13 | 平安科技(深圳)有限公司 | 一种学生信息存储方法、计算机可读存储介质及终端设备 |
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 |
CN110166413A (zh) * | 2018-02-14 | 2019-08-23 | 上海硅孚信息科技有限公司 | 基于区块链进行身份关系认证管理及服务的方法及系统 |
CN110166412A (zh) * | 2018-02-14 | 2019-08-23 | 上海硅孚信息科技有限公司 | 基于区块链的智能身份生物认证凭证管理方法及系统 |
US11700265B2 (en) | 2018-03-06 | 2023-07-11 | Americorp Investments Llc | Customized view of restricted information recorded into a blockchain |
US10951626B2 (en) | 2018-03-06 | 2021-03-16 | Americorp Investments Llc | Blockchain-based commercial inventory systems and methods |
EP3763102A4 (en) * | 2018-03-06 | 2021-11-24 | Americorp Investments Llc | PERSONALIZED VIEW OF RESTRICTED INFORMATION SAVED IN A CHAIN OF BLOCKS |
CN108564688A (zh) * | 2018-03-21 | 2018-09-21 | 阿里巴巴集团控股有限公司 | 身份验证的方法及装置和电子设备 |
JP6438615B1 (ja) * | 2018-03-29 | 2018-12-19 | 株式会社三井住友銀行 | ブロックチェーン上での正誤判断・結果共有システム |
CN108650231B (zh) * | 2018-04-04 | 2021-02-26 | 广州广电运通金融电子股份有限公司 | 基于区块链的生物特征采集方法及系统 |
JP7091791B2 (ja) * | 2018-04-06 | 2022-06-28 | 富士通株式会社 | データ管理装置,データ管理プログラム及びデータ管理方法 |
CN110799966A (zh) | 2018-04-22 | 2020-02-14 | 因特比有限公司 | 用于使用现有区块链节点来托管新区块链的方法和系统 |
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 |
CN108809952A (zh) * | 2018-05-22 | 2018-11-13 | 隆正信息科技有限公司 | 基于多标识分区段通用唯一信物链的物体认证方法及系统 |
KR102497579B1 (ko) * | 2018-05-30 | 2023-02-08 | 주식회사 씨브이티 | 생체 인식 기반의 출입문 제어 시스템 및 방법 |
KR102519761B1 (ko) * | 2018-05-30 | 2023-04-11 | 주식회사 씨브이티 | 생체 인식 기반의 출입문 제어 시스템 및 방법 |
WO2019236638A1 (en) * | 2018-06-06 | 2019-12-12 | Argosoperem Llc | Method and system for data storage and retrieval |
US11244316B2 (en) | 2018-06-07 | 2022-02-08 | International Business Machines Corporation | Biometric token for blockchain |
US10771240B2 (en) | 2018-06-13 | 2020-09-08 | Dynamic Blockchains Inc | Dynamic blockchain system and method for providing efficient and secure distributed data access, data storage and data transport |
KR102210665B1 (ko) * | 2018-06-20 | 2021-02-03 | 희 김 | 동물 관리 방법 및 시스템 |
US11797519B2 (en) * | 2018-06-22 | 2023-10-24 | Attestiv Inc. | Atomic capture of a set of related files, using a distributed ledger, for proof of authenticity |
US11321983B2 (en) | 2018-06-26 | 2022-05-03 | Veriscan, Llc | System and method for identifying and verifying one or more individuals using facial recognition |
US10721060B1 (en) * | 2018-06-29 | 2020-07-21 | Verisign, Inc. | Domain name blockchain user addresses |
CN108765615B (zh) * | 2018-06-29 | 2021-03-19 | 北京阿尔山区块链联盟科技有限公司 | 基于区块链的打卡信息存储方法及系统 |
US11632236B1 (en) * | 2018-06-29 | 2023-04-18 | Verisign, Inc. | Establishment, management, and usage of domain name to blockchain address associations |
US11527107B1 (en) * | 2018-06-29 | 2022-12-13 | Apple Inc. | On the fly enrollment for facial recognition |
KR102121930B1 (ko) * | 2018-07-03 | 2020-06-11 | 네이버 주식회사 | 블록체인 기반의 개인 데이터 처리 방법 및 시스템 |
US11356262B2 (en) * | 2018-07-03 | 2022-06-07 | Royal Bank Of Canada | System and method for anonymous location verification |
CA3048425A1 (en) | 2018-07-03 | 2020-01-03 | Royal Bank Of Canada | System and method for an electronic identity brokerage |
CN108965418A (zh) * | 2018-07-04 | 2018-12-07 | 临沂大学 | 一种智能合约的植入设备 |
CN109213914A (zh) * | 2018-08-28 | 2019-01-15 | 蔡捷 | 利用活体生物身份登陆基于区块链技术的网络搜索引擎 |
US10673847B2 (en) * | 2018-08-28 | 2020-06-02 | Ofer A. LIDSKY | Systems and methods for user authentication based on a genetic sequence |
US10826704B2 (en) | 2018-08-31 | 2020-11-03 | Hewlett Packard Enterprise Development Lp | Blockchain key storage on SIM devices |
CN110874464A (zh) | 2018-09-03 | 2020-03-10 | 巍乾全球技术有限责任公司 | 用户身份认证数据的管理方法和设备 |
US10810166B2 (en) * | 2018-09-20 | 2020-10-20 | Paypal, Inc. | Reconciliation of data in a distributed system |
JP2022002351A (ja) * | 2018-09-20 | 2022-01-06 | ソニーグループ株式会社 | 情報処理装置、情報処理方法、およびプログラム |
US11488271B2 (en) * | 2018-10-16 | 2022-11-01 | International Business Machines Corporation | System and method for supplier information management |
CN109359601A (zh) * | 2018-10-19 | 2019-02-19 | 平安科技(深圳)有限公司 | 身份验证识别方法、电子装置及计算机可读存储介质 |
KR20200046456A (ko) * | 2018-10-24 | 2020-05-07 | 비에이지노믹스(주) | 개인의 유전자 표현형이 적용된 컬러드 코인 |
RU2695976C1 (ru) * | 2018-10-24 | 2019-07-29 | Максим Михайлович Михайленко | Способ масштабирования обработки данных в распределенной системе |
CN109558422A (zh) * | 2018-10-29 | 2019-04-02 | 平安科技(深圳)有限公司 | 基于区块链的驾驶证档案管理方法、装置、计算机设备 |
US10929816B2 (en) * | 2018-10-29 | 2021-02-23 | Advanced Messaging Technologies, Inc. | Systems and methods for message transmission and retrieval using blockchain |
US11488727B2 (en) * | 2018-10-30 | 2022-11-01 | LogicMatter, Inc. | Immutable system of records for IoT/control systems for compliance |
GB2581315A (en) | 2018-10-30 | 2020-08-19 | Barclays Execution Services Ltd | Secure data communication |
CN109583230A (zh) | 2018-10-31 | 2019-04-05 | 阿里巴巴集团控股有限公司 | 基于区块链的数据存证方法及装置、电子设备 |
KR20200051404A (ko) * | 2018-11-05 | 2020-05-13 | 휴렛-팩커드 디벨롭먼트 컴퍼니, 엘.피. | 화상 형성 소모품 사용량 정보의 블록체인 기반 관리 |
EP3651112A1 (en) * | 2018-11-06 | 2020-05-13 | Electricité de France | Method for processing data and apparatuses for implementing the same |
US10992612B2 (en) * | 2018-11-12 | 2021-04-27 | Salesforce.Com, Inc. | Contact information extraction and identification |
IT201800010379A1 (it) * | 2018-11-16 | 2020-05-16 | Abcd Tech Sarl | Blockchain neurale |
DE102018010027A1 (de) * | 2018-12-19 | 2020-06-25 | Daimler Ag | Abwicklungssystem |
CN110046482A (zh) * | 2018-12-25 | 2019-07-23 | 阿里巴巴集团控股有限公司 | 身份核实方法及其系统 |
CN109660330B (zh) * | 2018-12-28 | 2022-04-01 | 飞天诚信科技股份有限公司 | 一种在区块链上进行身份认证的方法及系统 |
JP6858264B2 (ja) | 2018-12-28 | 2021-04-14 | アドバンスド ニュー テクノロジーズ カンパニー リミテッド | スマートコントラクトのホワイトリスト |
ES2774397A1 (es) * | 2019-01-18 | 2020-07-20 | Telefonica Digital Espana Slu | Metodo y sistema para recuperacion de claves criptograficas de una red de cadena de bloques |
CN109660359B (zh) * | 2019-01-22 | 2022-01-18 | 上海易酷信息技术服务有限公司 | 生成hd钱包名片的方法、设备及生成hd钱包可信地址的方法 |
CN109886681B (zh) * | 2019-01-31 | 2021-06-18 | 北京瑞卓喜投科技发展有限公司 | 区块链共识方法及共识系统 |
US11290448B1 (en) | 2019-02-05 | 2022-03-29 | Wells Fargo Bank, N.A. | Multifactor identity authentication via cumulative dynamic contextual identity |
WO2020162780A1 (ru) * | 2019-02-08 | 2020-08-13 | Алексей Сергеевич СМИРНОВ | Система и способ для безопасного хранения цифровых валют и осуществления транзакций в блокчейн сети |
US11038857B1 (en) | 2019-02-14 | 2021-06-15 | Sprint Communications Company L.P. | Data messaging service with distributed ledger control |
US11271724B2 (en) | 2019-02-21 | 2022-03-08 | Quantum Lock, Inc. | One-time-pad encryption system and methods |
CN111612922A (zh) * | 2019-02-22 | 2020-09-01 | 上海银晨智能识别科技有限公司 | 验票方法及系统、计算机可读存储介质 |
KR102250081B1 (ko) | 2019-02-22 | 2021-05-10 | 데이터얼라이언스 주식회사 | 공개 원장 기반 크리덴셜 자율적 운영 시스템 및 방법 |
EP3935782A1 (en) * | 2019-03-05 | 2022-01-12 | HRL Laboratories, LLC | A system and method for selective transparency for public ledgers |
CN110011985A (zh) | 2019-03-19 | 2019-07-12 | 阿里巴巴集团控股有限公司 | 用于操作物联网设备的方法和系统 |
CN110070359B (zh) * | 2019-03-19 | 2020-12-01 | 创新先进技术有限公司 | 基于区块链的数据核对系统、方法、计算设备及存储介质 |
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 |
CN110035002B (zh) * | 2019-04-01 | 2021-09-10 | 达闼机器人有限公司 | 即时通信的实现方法,终端设备及存储介质 |
US11303452B2 (en) | 2019-04-03 | 2022-04-12 | Keychainx Ag | Biometric digital signature generation for identity verification |
US10825024B1 (en) | 2019-04-12 | 2020-11-03 | Symbiont.Io, Inc. | Systems, devices, and methods for DLT-based data management platforms and data products |
US20200177390A1 (en) * | 2019-04-18 | 2020-06-04 | Alibaba Group Holding Limited | Providing data verification in a blockchain ledger |
US10691640B1 (en) * | 2019-04-18 | 2020-06-23 | Alibaba Group Holding Limited | Storing an asset update record |
CN110147686A (zh) * | 2019-04-18 | 2019-08-20 | 阿里巴巴集团控股有限公司 | 一种个人资产变更记录的存储方法、系统、装置及设备 |
US10997295B2 (en) | 2019-04-26 | 2021-05-04 | Forcepoint, LLC | Adaptive trust profile reference architecture |
US11394554B2 (en) * | 2019-04-30 | 2022-07-19 | Paypal, Inc. | Decentralized trust using blockchain for tracking and validation of voice communications |
CN110239483B (zh) * | 2019-05-07 | 2021-10-08 | 山东工商学院 | 车辆控制方法、系统及计算机可读存储介质 |
KR102044008B1 (ko) * | 2019-05-07 | 2019-11-12 | 옥철식 | 가상 현실 세계의 신원 인증 관리 시스템 |
US11315150B2 (en) | 2019-05-08 | 2022-04-26 | Data Vault Holdings, Inc. | Portfolio driven targeted advertising network, system, and method |
JP6650157B1 (ja) * | 2019-05-08 | 2020-02-19 | 株式会社モールサービス | 情報管理システム、情報管理方法及び情報管理プログラム |
US20220318853A1 (en) * | 2019-05-08 | 2022-10-06 | Data Vault Holdings, Inc. | System and method for tokenized licensing of content |
US11106812B2 (en) | 2019-05-09 | 2021-08-31 | At&T Intellectual Property I, L.P. | Controlling access to datasets described in a cryptographically signed record |
CN110120953B (zh) * | 2019-05-20 | 2021-09-07 | 大连交通大学 | 一种面向智能手机客户端的铁路旅客身份认证系统 |
CN110225095B (zh) * | 2019-05-20 | 2022-02-11 | 中国银行股份有限公司 | 一种数据处理方法、装置及系统 |
CN110245187A (zh) * | 2019-05-20 | 2019-09-17 | 深圳壹账通智能科技有限公司 | 一种基于区块链的名单类型查询方法及节点 |
CN110169774B (zh) * | 2019-05-28 | 2022-06-14 | 深圳正指向科技有限公司 | 一种基于区块链的运动状态识别系统及方法 |
CN110188526B (zh) * | 2019-05-31 | 2023-06-30 | 创新先进技术有限公司 | 基于区块链的约定信息处理方法、装置、系统及电子设备 |
CN110188697A (zh) * | 2019-05-31 | 2019-08-30 | 山东省计算中心(国家超级计算济南中心) | 一种基于区块链的指纹识别管理系统及方法 |
US10942920B2 (en) | 2019-06-03 | 2021-03-09 | Advanced New Technologies Co., Ltd. | Service processing system and method based on blockchain |
WO2020256680A1 (en) * | 2019-06-18 | 2020-12-24 | Tovarystvo Z Obmezhenoiu Vidpovidalnistiu "Simcord" | Method for executing a digital asset transfer transaction |
WO2020256681A1 (en) * | 2019-06-18 | 2020-12-24 | Tovarystvo Z Obmezhenoiu Vidpovidalnistiu "Simcord" | Digital asset transfer system |
CN111095327B (zh) | 2019-07-02 | 2023-11-17 | 创新先进技术有限公司 | 用于验证可验证声明的系统和方法 |
EP3721603B1 (en) | 2019-07-02 | 2021-12-08 | Advanced New Technologies Co., Ltd. | System and method for creating decentralized identifiers |
CN116910726A (zh) | 2019-07-02 | 2023-10-20 | 创新先进技术有限公司 | 用于将去中心化标识映射到真实实体的系统和方法 |
CN111213147B (zh) | 2019-07-02 | 2023-10-13 | 创新先进技术有限公司 | 用于基于区块链的交叉实体认证的系统和方法 |
CN111316303B (zh) | 2019-07-02 | 2023-11-10 | 创新先进技术有限公司 | 用于基于区块链的交叉实体认证的系统和方法 |
WO2019179533A2 (en) | 2019-07-02 | 2019-09-26 | Alibaba Group Holding Limited | System and method for issuing verifiable claims |
CN110334681B (zh) * | 2019-07-12 | 2020-12-01 | 蚌埠科睿达机械设计有限公司 | 基于区块链的指静脉身份识别方法及系统 |
KR20210009791A (ko) | 2019-07-18 | 2021-01-27 | 삼성전자주식회사 | 블록 체인을 이용한 전자 인증 장치 및 그 방법 |
US11797655B1 (en) | 2019-07-18 | 2023-10-24 | Verisign, Inc. | Transferring a domain name on a secondary blockchain market and in the DNS |
BR112022000940A2 (pt) * | 2019-07-23 | 2022-03-08 | Veridium Ip Ltd | Sistema e método para padrões de protocolo biométrico |
CN110362633B (zh) * | 2019-07-23 | 2023-12-05 | 腾讯科技(深圳)有限公司 | 区块数据存储方法、装置、计算机设备及存储介质 |
CN116578962A (zh) * | 2019-07-24 | 2023-08-11 | 创新先进技术有限公司 | 一种身份验证方法、装置及设备 |
CN110471986B (zh) * | 2019-07-31 | 2020-08-04 | 阿里巴巴集团控股有限公司 | 基于区块链的票据实名领取方法、装置及电子设备 |
CN111859347B (zh) * | 2019-08-01 | 2024-07-05 | 创新先进技术有限公司 | 基于区块链的身份验证方法、装置及设备 |
US10756901B2 (en) | 2019-08-01 | 2020-08-25 | Alibaba Group Holding Limited | Blockchain-based identity authentication method, apparatus, and device |
KR102088206B1 (ko) * | 2019-08-05 | 2020-03-13 | 주식회사 블록펫 | 이미지 기반의 객체 인식 방법 및 이러한 방법을 수행하는 장치 |
CN110443076B (zh) * | 2019-08-07 | 2021-06-01 | 瑞资(北京)科技有限公司 | 基于实名区块链的存证方法和系统 |
JP2022544411A (ja) * | 2019-08-13 | 2022-10-18 | エーディーアイ・アソシエーション | 分散型アイデンティティプラットフォームのための統合認証システム |
KR102117931B1 (ko) * | 2019-08-22 | 2020-06-02 | 정성원 | 서버에서 복수의 노드에 저장된 블록체인을 이용하여 2차 사용자 인증을 수행하는 방법 |
KR20210023601A (ko) * | 2019-08-23 | 2021-03-04 | 삼성전자주식회사 | 블록체인 계좌 정보를 제공하는 전자 장치와 이의 동작 방법 |
CN110753029B (zh) * | 2019-09-16 | 2021-09-14 | 中国联合网络通信集团有限公司 | 一种身份验证方法及生物识别平台 |
CN110519297B (zh) * | 2019-09-17 | 2021-06-15 | 腾讯科技(深圳)有限公司 | 一种基于区块链私钥的数据处理方法以及设备 |
US11023423B2 (en) | 2019-10-10 | 2021-06-01 | Avery Glasser | System and method for information storage using blockchain databases combined with pointer databases |
US11706017B2 (en) * | 2019-10-24 | 2023-07-18 | Hewlett Packard Enterprise Development Lp | Integration of blockchain-enabled readers with blockchain network using machine-to-machine communication protocol |
KR102355708B1 (ko) * | 2019-10-25 | 2022-01-26 | 주식회사 락키 | 블록체인 키를 이용한 사용자 인증 기반의 요청 처리 방법, 그 방법이 적용된 시스템 |
CN110809035B (zh) * | 2019-10-25 | 2021-12-03 | 广州查正源电子科技有限公司 | 一种去中心化防伪数据生成和管理方法及系统 |
CN110991253B (zh) * | 2019-11-08 | 2023-04-28 | 中国联合网络通信集团有限公司 | 一种基于区块链的人脸数字身份识别方法和装置 |
RU2748964C2 (ru) * | 2019-11-27 | 2021-06-02 | Акционерное общество "Лаборатория Касперского" | Способ безопасной передачи запрашиваемых данных и реализующая его система |
CN111079128B (zh) * | 2019-12-11 | 2021-09-28 | 腾讯科技(深圳)有限公司 | 一种数据处理方法、装置、电子设备以及存储介质 |
CN111294384A (zh) * | 2019-12-30 | 2020-06-16 | 深圳市服讯信息技术有限公司 | 基于模块链的物联网数据共享方法 |
CN111241196B (zh) * | 2020-01-03 | 2021-07-13 | 腾讯科技(深圳)有限公司 | 广告频次控制方法及系统 |
CN111371543B (zh) * | 2020-01-08 | 2023-03-24 | 中国科学院重庆绿色智能技术研究院 | 基于双区块链结构的物联网设备访问控制方法 |
KR102094705B1 (ko) * | 2020-01-17 | 2020-03-30 | 주식회사 에프엔에스벨류 | 블록 체인을 기반으로 한 다중 노드 인증 방법 및 이를 위한 장치 |
US11146386B2 (en) * | 2020-01-17 | 2021-10-12 | Agile Blockchain Corp. | Method and system for authentication seal deployment in networked immutable transactions |
US10972475B1 (en) * | 2020-01-29 | 2021-04-06 | Capital One Services, Llc | Account access security using a distributed ledger and/or a distributed file system |
US12099997B1 (en) | 2020-01-31 | 2024-09-24 | Steven Mark Hoffberg | Tokenized fungible liabilities |
US11424911B2 (en) | 2020-03-03 | 2022-08-23 | International Business Machines Corporation | Storage and communication environment for cryptographic tags |
EP3799683B1 (en) * | 2020-03-06 | 2022-10-05 | Alipay (Hangzhou) Information Technology Co., Ltd. | Methods and devices for generating and verifying passwords |
US10979230B1 (en) | 2020-03-11 | 2021-04-13 | Drfirst.Com, Inc. | Block chain proof for identification |
CN111309812A (zh) * | 2020-03-11 | 2020-06-19 | 深圳市网心科技有限公司 | 基于区块链的函件传输方法及相关设备 |
US11531724B2 (en) | 2020-03-28 | 2022-12-20 | Dataparency, LLC | Entity centric database |
KR20210125655A (ko) | 2020-04-08 | 2021-10-19 | 삼성전자주식회사 | 전자 장치 및 그 제어 방법 |
CN111552215B (zh) * | 2020-05-22 | 2022-02-11 | 中国联合网络通信集团有限公司 | 物联网设备安全防护方法和系统 |
US12101399B2 (en) | 2020-07-20 | 2024-09-24 | Pruve Systems, Inc. | Secure storage techniques utilizing consortium distributed ledgers |
WO2022019693A1 (ko) * | 2020-07-24 | 2022-01-27 | 주식회사 코인플러그 | 사용자 비대면 인증 vc(verifiable credential)를 이용한 did(decentralized identifier) 기반의 사용자 비대면 인증 방법 및 이를 이용한 인증 지원 서버 |
US20240089087A1 (en) * | 2020-08-19 | 2024-03-14 | Quantum Lock, Inc. | One-time pad encryption system and method |
US11853438B2 (en) * | 2020-10-02 | 2023-12-26 | Blockframe, Inc. | Providing cryptographically secure post-secrets-provisioning services |
KR102424275B1 (ko) * | 2020-11-06 | 2022-07-25 | 서울시립대학교 산학협력단 | 블록체인 기반의 분산 신원 인증을 통해 할인 정보를 제공하는 챗봇 서버, 방법 및 사용자 단말 |
CN112131316B (zh) * | 2020-11-20 | 2021-02-12 | 腾讯科技(深圳)有限公司 | 应用于区块链系统的数据处理方法及装置 |
JP2023554555A (ja) * | 2020-12-09 | 2023-12-27 | デヴィオ,インコーポレイテッド | ネットワーク上のアイデンティティ |
US20220188836A1 (en) * | 2020-12-15 | 2022-06-16 | Nicholas Scherling | Anti-Money Laundering Blockchain Technology |
CN112714111B (zh) * | 2020-12-22 | 2023-03-28 | 北京八分量信息科技有限公司 | 大数据系统中对用户身份进行多模式认证的方法、装置及相关产品 |
CN112613020B (zh) * | 2020-12-31 | 2024-05-28 | 中国农业银行股份有限公司 | 一种身份验证方法及装置 |
US11799639B2 (en) | 2021-01-05 | 2023-10-24 | Bank Of America Corporation | Systems and methods using distributed ledgers to correct for missing one time passwords in event processing |
KR102488866B1 (ko) * | 2021-01-25 | 2023-01-17 | 주식회사 블로코엑스와이지 | 블록체인 기반 개인 신상 증명을 위한 서비스 제공 장치 및 방법 |
CN112966049B (zh) * | 2021-03-09 | 2023-06-13 | 安徽超清科技股份有限公司 | 一种基于区块链的资产管理系统 |
CN113079146B (zh) * | 2021-03-25 | 2023-04-18 | 中国联合网络通信集团有限公司 | 一种验证方法及装置 |
CN113127908B (zh) * | 2021-04-29 | 2024-04-26 | 郑杰骞 | 链式结构地址生成、交易数据处理方法、装置及存储介质 |
US12003615B2 (en) | 2021-05-20 | 2024-06-04 | Verisign, Inc. | Lifecycle administration of domain name blockchain addresses |
US12052373B1 (en) | 2021-05-20 | 2024-07-30 | Verisign, Inc. | Delegated agent proof of network identifier control |
US11750401B2 (en) | 2021-05-20 | 2023-09-05 | Verisign, Inc. | Proving top level domain name control on a blockchain |
US11924161B1 (en) | 2021-05-20 | 2024-03-05 | Verisign, Inc. | Authorization and refusal of modification, and partial modification ability, of a network identifier |
CN113079027B (zh) * | 2021-06-04 | 2024-08-16 | 江苏数字产权交易有限公司 | 一种基于哈希值的区块数据生成与验证方法 |
CN113327165A (zh) | 2021-06-07 | 2021-08-31 | 支付宝(杭州)信息技术有限公司 | 一种基于区块链的交易方法 |
US11979484B2 (en) | 2021-07-21 | 2024-05-07 | Bank Of America Corporation | System for electronic data encryption and decryption using a consensus draft process |
WO2023141643A2 (en) * | 2022-01-24 | 2023-07-27 | Osom Products, Inc. | Digital non-fungible assets in persistent virtual environments linked to real assets |
US11652639B1 (en) | 2022-03-28 | 2023-05-16 | Veiovia Ltd. | Cryptographically generated data tethered to biological dataset through synchronization over peer-to-peer nodes |
US20230308301A1 (en) * | 2022-03-28 | 2023-09-28 | Veiovia Ltd. | Cryptographically generated data tethered to biological dataset provided by a user through synchronization over peer-to-peer nodes |
US11683186B1 (en) * | 2022-03-28 | 2023-06-20 | Veiovia Ltd. | Cryptographically generated data tethered to biological dataset through synchronization over peer-to-peer nodes for certification |
US11546322B1 (en) * | 2022-06-24 | 2023-01-03 | Numéraire Financial, Inc. | Decentralized avatar authentication in online platforms |
US11997086B1 (en) * | 2022-07-19 | 2024-05-28 | One Footprint Inc. | Systems and methods for identity verification and authentication |
EP4418152A1 (en) * | 2023-02-15 | 2024-08-21 | Telefonica Innovacion Digital SL | On-chain push-mode multi-factor authentication method and system for blockchain services |
US20240291659A1 (en) * | 2023-02-24 | 2024-08-29 | Authenticating. Com, LLC | Tokenized Credential Verification System |
Family Cites Families (54)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6988199B2 (en) * | 2000-07-07 | 2006-01-17 | Message Secure | Secure and reliable document delivery |
JP4519963B2 (ja) * | 1999-06-21 | 2010-08-04 | 富士通株式会社 | 生体情報の暗号化・復号化方法および装置並びに、生体情報を利用した本人認証システム |
CA2901250A1 (en) * | 2002-07-12 | 2004-01-22 | Apple Inc. | Personal authentication software and systems for travel privilege assignation and verification |
JP3961439B2 (ja) * | 2003-03-31 | 2007-08-22 | 富士通サポートアンドサービス株式会社 | 指紋による個人認証システム |
US8090945B2 (en) * | 2005-09-16 | 2012-01-03 | Tara Chand Singhal | Systems and methods for multi-factor remote user authentication |
US8989390B2 (en) * | 2005-12-12 | 2015-03-24 | Qualcomm Incorporated | Certify and split system and method for replacing cryptographic keys |
US20080120698A1 (en) * | 2006-11-22 | 2008-05-22 | Alexander Ramia | Systems and methods for authenticating a device |
US10255591B2 (en) * | 2009-12-18 | 2019-04-09 | Visa International Service Association | Payment channel returning limited use proxy dynamic value |
WO2011121530A1 (en) * | 2010-03-31 | 2011-10-06 | International Business Machines Corporation | Method, secure device, system and computer program product for digitally signing a document |
JP5564649B2 (ja) * | 2010-06-23 | 2014-07-30 | 日本碍子株式会社 | リチウム二次電池の正極及びリチウム二次電池 |
US20110137750A1 (en) | 2010-08-26 | 2011-06-09 | Aslam Gani | Internet currency and a system and method for online internet currency transactions |
US9043747B2 (en) * | 2011-09-07 | 2015-05-26 | Imagine Communications Corp. | Systems and methods for dynamic development and deployment of computing applications using blueprints |
FR2986350A1 (fr) | 2012-01-26 | 2013-08-02 | Paul Lahmi | Procede de transmission de documents et/ou d'informations avec authentification perenne |
US8921216B2 (en) * | 2012-07-19 | 2014-12-30 | SK Hynix Inc. | Semiconductor device and method of fabricating the same |
US8806524B1 (en) * | 2013-01-29 | 2014-08-12 | Telefonaktiebolaget L M Ericsson (Publ) | Restricting use of a direct-to-home digital broadcast satellite signal |
US10269009B1 (en) | 2013-06-28 | 2019-04-23 | Winklevoss Ip, Llc | Systems, methods, and program products for a digital math-based asset exchange |
CN104418951B (zh) * | 2013-08-29 | 2017-07-18 | 北京伟德杰生物科技有限公司 | 人Nectin‑2蛋白的应用 |
US10157294B2 (en) * | 2013-11-26 | 2018-12-18 | CaffeiNATION Signings (Series 3 of Caffeinaton Series, LLC) | Systems, methods and computer program products for managing remote execution of transaction documents |
US10127528B2 (en) | 2013-12-20 | 2018-11-13 | Movocash, Inc. | Financial services ecosystem |
US20150220928A1 (en) | 2014-01-31 | 2015-08-06 | Robert Allen | Platform for the purchase and sale of digital currency |
US10162954B2 (en) * | 2014-02-04 | 2018-12-25 | Lenovo (Singapore) Pte. Ltd. | Biometric account card |
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 |
FR3018378A1 (fr) * | 2014-03-12 | 2015-09-11 | Enrico Maim | Systeme et procede transactionnels a architecture repartie fondees sur des transactions de transferts d'unites de compte entre adresses |
WO2015142765A1 (en) * | 2014-03-17 | 2015-09-24 | Coinbase, Inc | Bitcoin host computer system |
US20150269538A1 (en) | 2014-03-18 | 2015-09-24 | Darin Stanchfield | Security devices and systems for digital currency transfer |
US9858569B2 (en) * | 2014-03-21 | 2018-01-02 | Ramanan Navaratnam | Systems and methods in support of authentication of an item |
US9672499B2 (en) * | 2014-04-02 | 2017-06-06 | Modernity Financial Holdings, Ltd. | Data analytic and security mechanism for implementing a hot wallet service |
CA2985040A1 (en) * | 2014-05-06 | 2015-12-03 | Case Wallet, Inc. | Cryptocurrency virtual wallet system and method |
US10340038B2 (en) * | 2014-05-13 | 2019-07-02 | Nant Holdings Ip, Llc | Healthcare transaction validation via blockchain, systems and methods |
US20150348169A1 (en) * | 2014-05-28 | 2015-12-03 | Michael Richards Harris | System and method for marketplace software platform |
US20150348017A1 (en) * | 2014-06-03 | 2015-12-03 | Jonathan Allmen | Method for integrating cryptocurrency transfer on a social network interface |
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 |
US20150363777A1 (en) * | 2014-06-16 | 2015-12-17 | Bank Of America Corporation | Cryptocurrency suspicious user alert system |
WO2016036969A1 (en) * | 2014-09-03 | 2016-03-10 | Nantomics, 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 |
CN104463001A (zh) * | 2014-12-19 | 2015-03-25 | 比特卡国际有限公司 | 一种独立生成和保存加密数字货币私钥的方法及承载加密数字货币私钥的装置 |
US9785764B2 (en) | 2015-02-13 | 2017-10-10 | Yoti Ltd | Digital identity |
US9641338B2 (en) * | 2015-03-12 | 2017-05-02 | Skuchain, Inc. | Method and apparatus for providing a universal deterministically reproducible cryptographic key-pair representation for all SKUs, shipping cartons, and items |
EP3767878A1 (en) | 2015-03-27 | 2021-01-20 | 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 |
WO2016164496A1 (en) * | 2015-04-06 | 2016-10-13 | Bitmark, Inc. | System and method for decentralized title recordation and authentication |
WO2017044554A1 (en) * | 2015-09-11 | 2017-03-16 | Aware, Inc. | Biometric verification of a blockchain database transaction contributor |
US20170228727A1 (en) * | 2016-02-10 | 2017-08-10 | Align Commerce Corporation | Conditional payment processing using multi-signature addresses |
US9818116B2 (en) * | 2015-11-11 | 2017-11-14 | Idm Global, Inc. | Systems and methods for detecting relations between unknown merchants and merchants with a known connection to fraud |
KR101590076B1 (ko) * | 2015-11-18 | 2016-02-01 | 주식회사 웨이브스트링 | 개인정보 관리 방법 |
CA3002235C (en) * | 2015-12-22 | 2021-01-26 | Thomson Reuters Global Resources Unlimited Company | Methods and systems for identity creation, verification and management |
EP3405862B1 (en) * | 2016-01-19 | 2020-11-18 | Priv8Pay, Inc. | Network node authentication |
WO2017152150A1 (en) * | 2016-03-04 | 2017-09-08 | ShoCard, Inc. | Method and system for authenticated login using static or dynamic codes |
US9985964B2 (en) * | 2016-03-28 | 2018-05-29 | Black Gold Coin, Inc. | Systems and methods for providing block chain-based multifactor personal identity verification |
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 |
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 |
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 |
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 |
-
2016
- 2016-03-28 US US15/083,241 patent/US9985964B2/en active Active
- 2016-03-29 BR BR112018070096A patent/BR112018070096A2/pt not_active IP Right Cessation
- 2016-03-29 DE DE202016008686.4U patent/DE202016008686U1/de active Active
- 2016-03-29 CN CN201811131854.8A patent/CN109657445A/zh active Pending
- 2016-03-29 AU AU2016400090A patent/AU2016400090B2/en not_active Ceased
- 2016-03-29 BR BR112018070093A patent/BR112018070093A2/pt not_active IP Right Cessation
- 2016-03-29 GB GB1815740.4A patent/GB2564787B/en active Active
- 2016-03-29 DE DE202016008687.2U patent/DE202016008687U1/de active Active
- 2016-03-29 KR KR1020187035609A patent/KR20180133944A/ko not_active Application Discontinuation
- 2016-03-29 CA CA3006587A patent/CA3006587A1/en not_active Abandoned
- 2016-03-29 KR KR1020187033161A patent/KR101990763B1/ko active IP Right Grant
- 2016-03-29 CN CN201811131873.0A patent/CN109660501B/zh not_active Expired - Fee Related
- 2016-03-29 PL PL427232A patent/PL427232A1/pl unknown
- 2016-03-29 ES ES201890049A patent/ES2692871B2/es active Active
- 2016-03-29 GB GB1815756.0A patent/GB2579764B/en active Active
- 2016-03-29 BR BR112018070091A patent/BR112018070091B1/pt not_active IP Right Cessation
- 2016-03-29 MA MA43326A patent/MA43326B1/fr unknown
- 2016-03-29 CN CN201811133009.4A patent/CN109657446B/zh not_active Expired - Fee Related
- 2016-03-29 EP EP18206468.3A patent/EP3483814A1/en not_active Withdrawn
- 2016-03-29 RU RU2018120742A patent/RU2667801C1/ru not_active IP Right Cessation
- 2016-03-29 DE DE112016006077.7T patent/DE112016006077B4/de active Active
- 2016-03-29 GB GB1913409.7A patent/GB2583984B/en active Active
- 2016-03-29 MX MX2018010163A patent/MX2018010163A/es unknown
- 2016-03-29 CN CN201680081706.2A patent/CN108701136B/zh not_active Expired - Fee Related
- 2016-03-29 CU CU2018000116A patent/CU20180116A7/es unknown
- 2016-03-29 MX MX2018011927A patent/MX2018011927A/es unknown
- 2016-03-29 SE SE1851298A patent/SE1851298A1/sv not_active Application Discontinuation
- 2016-03-29 EA EA201891901A patent/EA035080B1/ru not_active IP Right Cessation
- 2016-03-29 EP EP18206522.7A patent/EP3483816A1/en not_active Withdrawn
- 2016-03-29 PT PT2016024776A patent/PT2017171733B/pt active IP Right Grant
- 2016-03-29 DE DE202016008688.0U patent/DE202016008688U1/de active Active
- 2016-03-29 WO PCT/US2016/024776 patent/WO2017171733A1/en active Application Filing
- 2016-03-29 HU HUP1800363 patent/HUP1800363A1/hu unknown
- 2016-03-29 KR KR1020187033150A patent/KR101990762B1/ko active IP Right Grant
- 2016-03-29 MX MX2018011933A patent/MX2018011933A/es unknown
- 2016-03-29 BR BR112018070088-6A patent/BR112018070088A2/pt not_active Application Discontinuation
- 2016-03-29 GB GB1815742.0A patent/GB2584981B/en active Active
- 2016-03-29 JP JP2018600050U patent/JP3220620U/ja not_active Expired - Fee Related
- 2016-03-29 GB GB1815754.5A patent/GB2567960B/en active Active
- 2016-03-29 DK DKPA201870697A patent/DK201870697A1/en not_active Application Discontinuation
- 2016-03-29 KR KR1020187030963A patent/KR101990761B1/ko active IP Right Grant
- 2016-03-29 DE DE202016008584.1U patent/DE202016008584U1/de active Active
- 2016-03-29 RS RSP20181135 patent/RS20181135A1/sr unknown
- 2016-03-29 EE EEP201800028A patent/EE201800028A/et unknown
- 2016-03-29 KR KR1020187033177A patent/KR20180125630A/ko not_active Application Discontinuation
- 2016-03-29 NZ NZ744540A patent/NZ744540A/en not_active IP Right Cessation
- 2016-03-29 EP EP18206477.4A patent/EP3483815A1/en not_active Withdrawn
- 2016-03-29 EP EP18206482.4A patent/EP3486854A1/en not_active Withdrawn
- 2016-03-29 FI FI20185901A patent/FI20185901A1/en not_active Application Discontinuation
- 2016-03-29 GB GB1808833.6A patent/GB2561107B/en active Active
- 2016-03-29 EP EP16897290.9A patent/EP3400541B1/en active Active
- 2016-03-29 SG SG11201804658SA patent/SG11201804658SA/en unknown
- 2016-03-29 BR BR112018070095A patent/BR112018070095A2/pt not_active IP Right Cessation
- 2016-03-29 CN CN201811131215.1A patent/CN109660500A/zh active Pending
- 2016-03-29 DE DE202016008689.9U patent/DE202016008689U1/de active Active
- 2016-03-29 EP EP18206524.3A patent/EP3483817A1/en not_active Withdrawn
- 2016-03-29 GB GBGB2013529.9A patent/GB202013529D0/en not_active Ceased
-
2017
- 2017-03-29 CR CR20180514A patent/CR20180514A/es unknown
-
2018
- 2018-04-30 US US15/966,320 patent/US10116657B2/en active Active - Reinstated
- 2018-05-11 US US15/978,004 patent/US10749865B2/en active Active
- 2018-05-16 WO PCT/US2018/033027 patent/WO2019216923A1/en active Application Filing
- 2018-07-31 JP JP2018143775A patent/JP2019057271A/ja active Pending
- 2018-08-07 NO NO20181053A patent/NO343876B1/no not_active IP Right Cessation
- 2018-08-10 ZA ZA201805308A patent/ZA201805308B/en unknown
- 2018-08-14 US US16/103,666 patent/US10182051B1/en active Active
- 2018-08-21 US US16/107,126 patent/US10298571B2/en active Active - Reinstated
- 2018-08-28 SA SA518392296A patent/SA518392296B1/ar unknown
- 2018-09-17 IL IL261839A patent/IL261839B/en active IP Right Grant
- 2018-09-21 US US16/138,359 patent/US10389713B2/en active Active
- 2018-09-21 US US16/138,781 patent/US20190036919A1/en not_active Abandoned
- 2018-09-21 US US16/138,454 patent/US10298572B2/en active Active - Reinstated
- 2018-09-25 AU AU2018236723A patent/AU2018236723B2/en not_active Ceased
- 2018-09-25 AU AU2018236722A patent/AU2018236722B2/en not_active Ceased
- 2018-09-25 AU AU2018236721A patent/AU2018236721B2/en not_active Ceased
- 2018-09-26 CL CL2018002724A patent/CL2018002724A1/es unknown
- 2018-09-26 AU AU2018236747A patent/AU2018236747B2/en not_active Ceased
- 2018-09-27 PH PH12018502087A patent/PH12018502087A1/en unknown
- 2018-09-28 SV SV2018005745A patent/SV2018005745A/es unknown
- 2018-10-19 HR HRP20181711AA patent/HRP20181711A2/hr not_active Application Discontinuation
- 2018-10-22 EC ECSENADI201879192A patent/ECSP18079192A/es unknown
- 2018-10-23 JP JP2018199423A patent/JP2019135825A/ja active Pending
- 2018-10-23 JP JP2018199420A patent/JP2019126020A/ja active Pending
- 2018-10-23 JP JP2018199422A patent/JP2019126022A/ja active Pending
- 2018-10-23 JP JP2018199421A patent/JP2019126021A/ja active Pending
- 2018-10-25 CO CONC2018/0011415A patent/CO2018011415A2/es unknown
- 2018-11-19 IL IL263109A patent/IL263109B/en active IP Right Grant
-
2019
- 2019-01-03 IL IL264079A patent/IL264079B/en active IP Right Grant
- 2019-01-03 IL IL264078A patent/IL264078B/en active IP Right Grant
- 2019-03-11 IL IL265284A patent/IL265284A/en unknown
- 2019-08-01 US US16/529,356 patent/US11290449B2/en active Active
-
2022
- 2022-03-08 US US17/653,965 patent/US20220191197A1/en active Pending
Non-Patent Citations (1)
Title |
---|
None * |
Also Published As
Similar Documents
Publication | Publication Date | Title |
---|---|---|
AU2018236747B2 (en) | Systems and methods for providing block chain-based multifactor personal identity verification | |
AU2018100477A4 (en) | Systems and methods for providing block chain-based multifactor personal identity verification | |
OA18670A (en) | Systems and methods for providing block chain-based multifactor personal identity verification | |
OA19648A (en) | Systems and methods for providing block chain-based multifactor personal identity verification. |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: THE INTERNATIONAL PUBLICATION HAS BEEN MADE |
|
PUAI | Public reference made under article 153(3) epc to a published international application that has entered the european phase |
Free format text: ORIGINAL CODE: 0009012 |
|
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: REQUEST FOR EXAMINATION WAS MADE |
|
17P | Request for examination filed |
Effective date: 20180724 |
|
AK | Designated contracting states |
Kind code of ref document: A1 Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR |
|
AX | Request for extension of the european patent |
Extension state: BA ME |
|
A4 | Supplementary search report drawn up and despatched |
Effective date: 20181023 |
|
RIC1 | Information provided on ipc code assigned before grant |
Ipc: G06Q 20/38 20120101ALI20181017BHEP Ipc: H04L 29/06 20060101ALI20181017BHEP Ipc: G06Q 20/36 20120101ALI20181017BHEP Ipc: G06F 17/30 20060101AFI20181017BHEP |
|
DAV | Request for validation of the european patent (deleted) | ||
DAX | Request for extension of the european patent (deleted) | ||
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: EXAMINATION IS IN PROGRESS |
|
17Q | First examination report despatched |
Effective date: 20191018 |
|
REG | Reference to a national code |
Ref country code: HK Ref legal event code: DE Ref document number: 40000319 Country of ref document: HK |
|
REG | Reference to a national code |
Ref country code: DE Ref legal event code: R079 Ref document number: 602016046511 Country of ref document: DE Free format text: PREVIOUS MAIN CLASS: G06F0017300000 Ipc: G06Q0020360000 |
|
RIC1 | Information provided on ipc code assigned before grant |
Ipc: G06Q 20/38 20120101ALI20200312BHEP Ipc: G06Q 20/36 20120101AFI20200312BHEP Ipc: H04L 29/06 20060101ALI20200312BHEP |
|
GRAP | Despatch of communication of intention to grant a patent |
Free format text: ORIGINAL CODE: EPIDOSNIGR1 |
|
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: GRANT OF PATENT IS INTENDED |
|
INTG | Intention to grant announced |
Effective date: 20200529 |
|
GRAS | Grant fee paid |
Free format text: ORIGINAL CODE: EPIDOSNIGR3 |
|
GRAA | (expected) grant |
Free format text: ORIGINAL CODE: 0009210 |
|
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: THE PATENT HAS BEEN GRANTED |
|
AK | Designated contracting states |
Kind code of ref document: B1 Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR |
|
REG | Reference to a national code |
Ref country code: GB Ref legal event code: FG4D |
|
REG | Reference to a national code |
Ref country code: CH Ref legal event code: EP |
|
REG | Reference to a national code |
Ref country code: IE Ref legal event code: FG4D |
|
REG | Reference to a national code |
Ref country code: DE Ref legal event code: R096 Ref document number: 602016046511 Country of ref document: DE |
|
REG | Reference to a national code |
Ref country code: AT Ref legal event code: REF Ref document number: 1326597 Country of ref document: AT Kind code of ref document: T Effective date: 20201115 |
|
REG | Reference to a national code |
Ref country code: AT Ref legal event code: MK05 Ref document number: 1326597 Country of ref document: AT Kind code of ref document: T Effective date: 20201021 |
|
REG | Reference to a national code |
Ref country code: NL Ref legal event code: MP Effective date: 20201021 |
|
REG | Reference to a national code |
Ref country code: CH Ref legal event code: NV Representative=s name: E. BLUM AND CO. AG PATENT- UND MARKENANWAELTE V, CH |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: RS Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20201021 Ref country code: PT Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20210222 Ref country code: NO Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20210121 Ref country code: GR Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20210122 Ref country code: FI Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20201021 |
|
REG | Reference to a national code |
Ref country code: LT Ref legal event code: MG4D |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: AT Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20201021 Ref country code: BG Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20210121 Ref country code: IS Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20210221 Ref country code: LV Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20201021 Ref country code: PL Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20201021 Ref country code: SE Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20201021 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: NL Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20201021 Ref country code: HR Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20201021 |
|
REG | Reference to a national code |
Ref country code: DE Ref legal event code: R097 Ref document number: 602016046511 Country of ref document: DE |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: SM Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20201021 Ref country code: LT Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20201021 Ref country code: EE Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20201021 Ref country code: CZ Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20201021 Ref country code: SK Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20201021 Ref country code: RO Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20201021 |
|
PLBE | No opposition filed within time limit |
Free format text: ORIGINAL CODE: 0009261 |
|
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: NO OPPOSITION FILED WITHIN TIME LIMIT |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: DK Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20201021 Ref country code: ES Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20201021 |
|
26N | No opposition filed |
Effective date: 20210722 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: IT Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20201021 Ref country code: MC Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20201021 Ref country code: AL Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20201021 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: SI Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20201021 |
|
REG | Reference to a national code |
Ref country code: BE Ref legal event code: MM Effective date: 20210331 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: LU Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20210329 Ref country code: IE Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20210329 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: IS Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20210221 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: BE Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20210331 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: CY Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20201021 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: HU Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT; INVALID AB INITIO Effective date: 20160329 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: MK Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20201021 |
|
PGFP | Annual fee paid to national office [announced via postgrant information from national office to epo] |
Ref country code: DE Payment date: 20240304 Year of fee payment: 9 Ref country code: GB Payment date: 20240322 Year of fee payment: 9 |
|
PGFP | Annual fee paid to national office [announced via postgrant information from national office to epo] |
Ref country code: FR Payment date: 20240320 Year of fee payment: 9 |
|
PGFP | Annual fee paid to national office [announced via postgrant information from national office to epo] |
Ref country code: CH Payment date: 20240401 Year of fee payment: 9 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: MT Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20201021 |