Methodology for identifying local/mobile client computing devices using a network based database containing records of hashed distinctive hardware, software, and user provided biometric makers for authorization of electronic transactions and right of entry to secure locations
Abstract
The present invention consists of methods whereby local/mobile computing devices are registered by collecting a set of hardware and/or software distinctive identifiers to be saved in a validation database residing on a validation database server/Web server, such that the local/mobile computing device can be used as a digital hardware key for right of access and authorization of electronic transactions. This is done by comparing a regenerated set of hardware and/or software distinctive identifiers with those previously registered in the validation database in order to validate the identity of the local/mobile computing device. The invention consists of a first software program executing on a local/mobile computing device that generates the set of hashed and/or encrypted hardware and/or software distinctive identifiers and a second software program resident residing on a validation database server/Web server that manages the validation database.
Claims
exact text as granted — not AI-modified1 - 20 . (canceled)
21 . A method of validating an identity of a client computer during authorization of electronic transactions comprising:
Running a validation software program on the client computer; said validation software program obtaining a plurality of distinctive identifiers from the client computer from which the electronic transaction is to be validated, said plurality of distinctive identifiers including multiple identifiers including at least multiple of: at least one hardware module on the client computer, an identifier of a software module on the client computer, a user entered password and user biometric marker; said initially collecting a specified plurality of said distinctive identifiers from the client computer; carrying out a hash function on each of said plurality of distinctive identifiers to create hashed distinctive identifiers, where the hashed distinctive identifiers are hashed in a way that renders anonymous each of said hashed distinctive identifiers, and said hashed distinctive identifiers being such that any of said hashed distinctive identifiers contain no information that is traceable back to said specific client computer from which they were derived, formatting said hashed distinctive identifiers into a record of said hashed distinctive identifiers into a record of a specified format; sending said record of said hashed distinctive identifiers to a remote database as a reference set; and after said sending, carrying out a validation of said client computer using said record of hashed registered distinctive identifiers on said remote database for validating the identity of said client computer, by sending a current set of said distinctive identifiers, creating a current set of hashed distinctive identifiers from said current set, sending said current set of said distinctive identifiers to the remote database, receiving a validation of the transaction if the current set matches to the reference set, and receiving a decline indication of the current set of distinctive identifiers if the current set does not match to the reference set.
22 . The method of claim 21 wherein the remote database is a database server, and further comprising receiving a request in said database server operative to download a first software program to the client computer by a first network site, and sending said first software program responsive to said request, to the client computer,
Wherein said first network site downloads said first software program responsive to a received request.
23 . The method of claim 21 further comprising securely erasing memory locations in said client computer that were used to process said group of specified distinctive identifiers.
24 . The method of claim 21 wherein said validation software program carries out said hash using the SHA-3 hashing algorithm.
25 . The method of claim 21 further comprising running a first network website on a first network connected database server;
Operating said database server operative to download the validation software program to a client computer by said first network site, said first network site downloads said first software program responsive to a received request from the client computer.
26 . The method of claim 25 further comprising using said record of hashed registered distinctive identifiers maintained on said first network connected database server for validating the identity of said client computer, by receiving the hashed current set of said plurality of distinctive identifiers from said client computer, unhashing the current set, regenerating said reference set of said hashed distinctive identifiers and comparing the current set with the reference set.
27 . The method of claim 25 , wherein after said network connected database server receiving said record of distinctive identifiers, said network connected database server escrows said record of distinctive identifiers, and sends a communication to said user of said client computer by a communication part identified by said network site and asking said user to confirm that they had authorized the transmittal of the data to said network site to register their said client computer, and if said user communicates to said network database server that they provided said data to said network site, said network database server stores said record of said distinctive identifiers into said database and makes said record of distinctive identifiers available to validate subsequent hashed records of distinctive identifiers of said client computer sent to said network connected database sever by said network site and, if said user communicates to said network database server that they did not provide said data to said network site said network database server operating to erase said record of distinctive identifiers.
28 . A computer system operating for validating an identity of a client computer during authorization of electronic transactions comprising:
A client computer, running a validation software program on the client computer; said validation software program obtaining a plurality of distinctive identifiers from the client computer from which the electronic transaction is to be validated, said plurality of distinctive identifiers including multiple identifiers including at least multiple of: at least one hardware module on the client computer, an identifier of a software module on the client computer, a user entered password and user biometric marker; said validation software program initially collecting a specified plurality of said distinctive identifiers from the client computer; said validation software program carrying out a hash function on each of said plurality of distinctive identifiers to create hashed distinctive identifiers, where the hashed distinctive identifiers are hashed in a way that renders anonymous each of said hashed distinctive identifiers, and said hashed distinctive identifiers being such that any of said hashed distinctive identifiers contain no information that is traceable back to said specific client computer from which they were derived, said validation software program formatting said hashed distinctive identifiers into a record of said hashed distinctive identifiers into a record of a specified format; said validation software program sending said record of said hashed distinctive identifiers to a remote database as a reference set; and after said sending, said validation software program carrying out a validation of said client computer using said record of hashed registered distinctive identifiers on said remote database for validating the identity of said client computer, by sending a current set of said distinctive identifiers, creating a current set of hashed distinctive identifiers from said current set, sending said current set of said distinctive identifiers to the remote database, receiving a validation of the transaction if the current set matches to the reference set, and receiving a decline indication of the current set of distinctive identifiers if the current set does not match to the reference set.
29 . The computer system as in claim 28 , wherein the remote database is a database server,
and further comprising sending a request to said database server operative to download a first software program to the client computer by said first network site, and said client computer operating for downloading said first software program responsive to said request,
30 . The computer system as in claim 28 , wherein
said validation software program carries out said hash using the SHA-3 hashing algorithm.
31 . The computer system as in claim 28 , wherein said record of hashed registered distinctive identifiers is used for validating the identity of said client computer, by receiving the hashed current set of said plurality of distinctive identifiers from said client computer, unhashing the current set, regenerating said reference set of said hashed distinctive identifiers and comparing the current set with a reference set.Cited by (0)
No later patents cite this yet.
References (0)
No backward citations on record.