CROSS-REFERENCE TO RELATED APPLICATIONS

The present application claims priority, under 35 U.S.C. Â§120, to U.S. patent application Ser. No. 11/314,199, filed Dec. 20, 2005 and entitled â€œBiometric Personal Data Key (PDK) Authentication,â€ which claims the benefit of U.S. Provisional Application No. 60/637,538, filed on Dec. 20, 2004, and of U.S. Provisional Application No. 60/652,765, filed on Feb. 14, 2005, the entire contents of which are hereby incorporated by reference.

FIELD OF THE INVENTION

The present invention relates generally to computerized authentication, and more specifically, to an authentication responsive to biometric verification of a user being authenticated.

BACKGROUND

Conventional user authentication techniques are designed to prevent access by unauthorized users. One technique is to require a user being authenticated to provide secret credentials, such as a password, before allowing access. Similarly, a PIN number can be required by an ATM machine before allowing a person to perform automated bank transactions. A difficulty with this technique is that it requires the user to memorize or otherwise keep track of the credentials. A uses often has multiple sets of credentials (e.g., passwords and PINs) and it can be quite difficult to keep track of them all.

Another technique that does not require the user to memorize credentials is to provide the user with an access object such as a key (e.g., an electronic key) that the user can present to obtain access. For example, a user can be provided with a small electronic key fob that allows access to a building or other secured location. A difficulty with using access objects is that authentication merely proves that the access object itself is valid; it does not verify that the legitimate user is using the access object. That is, illegitimate user can use a stolen access object to enter a secured location because the user's identity is never checked.

Some hybrid authentication techniques require the user to provide both an access object and credentials. The user is authenticated only upon providing both items. Of course, this solution does not resolve the problem of making the user memorize credentials.

Therefore, there is a need for systems and methods for verifying a user that is being authenticated that does not suffer from the limitations described above. Moreover, the solution should ease authentications by wirelessly providing an identification of the user.

SUMMARY

The present invention addresses the above needs by providing systems and methods for authentication responsive to biometric verification of a user being authenticated. In one embodiment, an integrated device includes a persistent storage to persistently stores a code such as a device identifier (ID) and biometric data for a user in a tamper-resistant format, and a verification module, in communication with the persistent storage, to receive scan data from a biometric scan for comparison against the biometric data, and if the scan data matches the biometric data, wirelessly sending a code for authentication.

In one embodiment, a method for verifying a user during authentication of an integrated device, includes persistently storing biometric data for the user in a tamper-resistant format; responsive to receiving a request for biometric verification of the user, receiving scan data from a biometric scan; comparing the scan data to the biometric data to determine whether the data match; and responsive to a determination that the scan data matches the biometric data, wirelessly sending a code for authentication.

Other embodiments include corresponding systems, apparatus, and computer programming products, configured to perform the actions of the methods, encoded on computer storage devices. These and other embodiments may each optionally include one or more of the following features. For instance the operations further include registering an age verification for the user in association with the code. For instance the operations further include establishing a secure communication channel prior to sending the code for authentication. For instance the operations further include receiving a request for the code without a request for biometric verification, and responsive to receiving the request for the code without a request for biometric verification, sending the code without requesting the scan data. For instance, the features include: the code is registered with a trusted authority, and the code can be authenticated to a third party by the trusted authority; the code uniquely identifies the integrated device; the code indicates that the biometric verification was successful; persistently storing biometric data includes permanently storing biometric data; the biometric data and the scan data are both based on a fingerprint scan by the user, an LED to be activated for requesting the biometric scan.

In one embodiment, a method for authenticating a verified user, includes receiving a code associated with a biometrically verified user; requesting authentication of the code; receiving an authentication result; and in response to the authentication result being positive, providing access to an application.

In one embodiment, a system includes an integrated device (e.g. a biometric key) to store biometric data for a user in a tamper resistant format, and if scan data can be verified as being from the user by comparing the scan data to the biometric data, wirelessly sending a code; and an authentication module to receive the code and send the code to a trusted authority for authentication, and responsive to the code being authenticated, allowing the user to access an application.

Other embodiments include corresponding systems, apparatus, and computer programming products, configured to perform the actions of the methods, encoded on computer storage devices. These and other embodiments may each optionally include one or more of the following features. For instance, the operations further include registering the code with a trusted authority, wherein requesting authentication of the code includes providing the code to the trusted authority and wherein receiving an authentication result comprises receiving the authentication result from the trusted authority. For instance the operations further include registering a date of birth or age with the trusted authority. For instance the operations further include establishing a secure communications channel with an integrated device, wherein the code associated with the biometrically verified user is received from the integrated device. For instance the features include: the integrated device receives an authentication request from the authentication module, and in response, requests a biometric scan from the user to generate the scan data; when the integrated device cannot verify the scan data as being from the user, it does not send the code.

Advantageously, user authentication is bolstered with highly reliable biometric verification of the user in an integrated device. Furthermore, a keyless environment relieves authorized users from having to memorize credentials, and of having to physically enter credentials or keys. In addition, the integrated device can be authenticated for an application that is open to the public (i.e., in an open loop system).

The features and advantages described in the specification are not all inclusive and, in particular, many additional features and advantages will be apparent to one of ordinary skill in the art in view of the drawings, specifications, and claims. Moreover, it should be noted that the language used in the specification has been principally selected for readability and instructional purposes and may not have been selected to delineate or circumscribe the inventive matter.

BRIEF DESCRIPTION OF THE DRAWINGS

The teachings of the present invention can be readily understood by considering the following detailed description in conjunction with the accompanying drawings.

FIG. 1 is a schematic diagram illustrating a biometric key for providing authentication information for a biometrically verified user according to one embodiment of the present invention.

FIG. 2 is a block diagram illustrating functional modules within the biometric key according to one embodiment of the present invention.

FIG. 3 is a block diagram illustrating a system for providing authentication information for a biometrically verified user.

FIG. 4 is a flow chart illustrating a method for providing authentication information for a biometrically verified user.

FIG. 5 is a flow chart illustrating a method for enrolling biometric data of the user with the biometric key.

FIG. 6 is a flow chart illustrating a method for verifying a subject presenting the biometric key according to one embodiment of the present invention.

FIG. 7 is a flow chart illustrating a method for authenticating a verified user of the biometric key according to one embodiment of the present invention.

DETAILED DESCRIPTION

Systems and methods for authentication responsive to biometric verification of a user being authenticated are described. Generally, biometric verification uses biometric data to ensure that the user of, for example, a biometric key, is the person registered as an owner. Biometric data is a digital or analog representation of characteristics unique to the user's body. For example, a fingerprint of a subject can be compared against previously-recorded biometric data for verification that the subject is the registered owner of the biometric key. Then, the biometric key itself can be authenticated.

Although the embodiments below are described using the example of biometric verification using a fingerprint, other embodiments within the spirit of the present invention can perform biometric verification using other types of biometric data. For example, the biometric data can include a palm print, a retinal scan, an iris scan, hand geometry recognition, facial recognition, signature recognition, or voice recognition.

FIG. 1 is a schematic diagram illustrating an example of a biometric key 100 for providing authentication information for a biometrically verified user according to one embodiment of the present invention. In one embodiment, the biometric key 100 comprises a frame 110, a scan pad 120, and an LED 130. In one embodiment, biometric key 100 has a small form factor (e.g., the size of an automobile remote control) such that it can be unobtrusively carried by a user. In one embodiment, the biometric key 100 is integrated into another object or device. A device having an integrated biometric key 100 is occasionally referred to herein as an â€œintegrated device.â€ For example, in one embodiment, the biometric key 100 is integrated into a mobile phone (e.g. a cellular phone or smartphone), tablet, laptop, mp3 player, mobile gaming device, watch, key fob or other mobile device, thereby making the biometric key 100 unobtrusive to carry.

Frame 110 can be formed by plastic, metal or another suitable material. Frame 110 is shaped to secure scan pad 120, and includes a perforation for attachment to, for example a key chain or clip. In one embodiment, frame 110 is formed from a unitary molding to protect biometric data. Accordingly, frame 110 cannot be opened to expose the underlying components unless it is broken.

Scan pad 120 can be, for example, an optical scanner using a charge coupled device, or a capacitive scanner. Scan pad 120 can be sized to fit a thumb or other finger. Biometric key 100 of the present embodiment includes LED 130 that lights up to request a fingerprint scan from a user. In one embodiment, LED 130 can also confirm that user verification and/or authentication has completed.

Biometric key 100 can authenticate a user for various purposes. For example, biometric key 100 can allow keyless entry into homes and autos. In another example, biometric key 100 can log a user onto a computer system or point of sale register without typing in credentials. In still another example, biometric key 100 can verify that an enrolled user is above a certain age (e.g., before allowing access to a slot machine in a casino). In some embodiments, biometric key 100 operates without biometric verification, and request a fingerprint scan from a user only when biometric verification is needed for the particular use.

FIG. 2 is a block diagram illustrating biometric key 100 according to one embodiment of the present invention. Biometric key 100 comprises control module 210, biometric portion 220, RF communication module 230, persistent storage 240, and battery 250. Biometric key 100 can be formed from a combination of hardware and software components as described above. In one embodiment, biometric key 100 comprises a modified key fob.

Control module 210 coordinates between several functions of biometric key 100. In one embodiment, control module 210 provides a verification code upon successful verification of the user. More specifically, once biometric portion 220 indicates that a fingerprint scan matches biometric data that was collected during enrollment, control module 210 can trigger RF communication module 230 for sending a code indicating that the user was verified. In another embodiment, control module 210 can work in the opposite direction by detecting a request for verification from RF communication module 230, and then requesting verification of the user from biometric portion 210. Note that control module 210 of FIG. 2 is merely a grouping of control functions in a central architecture, and in other embodiments, the control functions can be distributed between several modules around biometric key 100.

Biometric portion 220 comprises enrollment module 222, validation module 224, and biometric data base 226. In one embodiment, enrollment module 222 registers a user with biometric key 100 by persistently storing biometric data associated with the user. Further, enrollment module 222 registers biometric key 100 with a trusted authority by providing the code (e.g., device ID) to the trusted authority. Or conversely, the trusted authority can provide the code to biometric key 100 to be stored therein.

Validation module 224 can comprise scan pad 120 (FIG. 1) to capture scan data from a user's fingerprint (e.g., a digital or analog representation of the fingerprint). Using the scan data, validation module 214 determines whether the user's fingerprint matches the stored biometric data from enrollment. Conventional techniques for comparing fingerprints can be used. For example, the unique pattern of ridges and valleys of the fingerprints can be compared. A statistical model can be used to determine comparison results. Validation module 224 can send comparison results to control module 210.

In other embodiments, validation module 224 can be configured to capture biometric data for other human characteristics. For example, a digital image of a retina, iris, and/or handwriting sample can be captured. In another example, a microphone can capture a voice sample.

Persistent storage 226 persistently stores biometric data from one or more users which can be provided according to specific implementations. In one embodiment, at least some of persistent storage 226 is a memory element that can be written to once but cannot subsequently be altered. Persistent storage 226 can include, for example, a ROM element, a flash memory element, or any other type of non-volatile storage element. Persistent storage 226 is itself, and stores data in, a tamper-proof format to prevent any changes to the stored data. Tamperproofing increases reliability of authentication because it does not allow any changes to biometric data (i.e., allows reads of stored data, but not writes to store new data or modify existing data). Furthermore, data can be stored in an encrypted form.

In one embodiment, persistent storage 226 also stores the code that is provided by the key 100 responsive to successful verification of the user. As described above, in one embodiment the code is a device ID or other value that uniquely identifies biometric key 100. In one embodiment, the code is providing during the manufacturing process and the biometric data are provided during an enrollment of the user. In other embodiments, the code is provided during enrollment and/or the biometric data are provided during manufacturing. Further, in some embodiments persistent storage 226 stores other data utilized during the operation of biometric key 100. For example, persistent storage 226 can store encryption/decryption keys utilized to establish secure communications links.

Radio frequency (RF) communication module 230 is, for example, a transceiver or other mechanism for wireless communication. RF communication module 230 can send and receive data (e.g., the code) as modulated electromagnetic signals. In one embodiment, RF communication 220 can be optimized for low-power usage by, for example, using short-range transceivers. RF communication module 230 can actively send out connection requests, or passively detect connection requests.

Battery 260 can be a conventional power source suitable for the components of biometric key 100. Battery 260 can be either replaceable or rechargeable. Alternatively, battery 260 can be embedded within key 100 such that the key must be discarded or recycled upon expiration of the battery.

FIG. 3 is a block diagram illustrating a system 300 for providing authentication information for a biometrically verified user. System 300 comprises an authentication module 310 in communication with biometric key 100, a trusted key authority 320, and an application 330.

Authentication module 310 is coupled in communication with biometric key via line 311 (i.e., a wireless medium such as EM signals), and with trusted key authority 320 via line 312 (e.g., a secure data network such as the Internet, or a cell network). Authentication module 310 can include one or more of, for example, a computerized device, software executing on a computerized device, and/or a reader/decoder circuit. In one embodiment, authentication module 310 servers as a gatekeeper to application 330 by requiring the code indicating successful biometric verification of the user prior to allowing access to the application. Further, in one embodiment, authentication module 310 provides the code to trusted key authority 320 in order to verify that it belongs to a legitimate key (e.g., when application 330 is security-critical). Authentication module 310 can send a message to application 330, or otherwise allow access to the application, responsive to a successful authentication by trusted key authority 320.

Application 330 is a resource that can be accessed by a verified and authenticated user. Application 330 can be, for example, a casino machine, a keyless lock, a garage door opener, an ATM machine, a hard drive, computer software, a web site, a file, a financial account (e.g. a savings account, checking account, brokerage account, credit card account, credit line, etc.) and the like. In one embodiment, a file includes medical information such as a medical record, insurance information or other healthcare information. Application 330 can execute on the same system as authentication module 310 or on another system in communication with the system of the authentication module. In one embodiment, application module 330 allows access by a user after receiving a message from authentication module 310. At that point, application 330 can allow direct use by the user, or require that communications continue to pass through authentication module 310 for continued authentication.

Trusted key authority 320 is a third-party authority that is present in some embodiments in order to provide enhanced security. In one embodiment, trusted key authority 320 verifies that a code from a biometric key is legitimate. To do so, the trusted key authority 320 stores a list of codes for legitimate biometric keys. The list can be batched or updated each time a new user/key is enrolled. In one embodiment, trusted key authority 320 can also store a profile associated with a biometric key. The profile describes the user associated with the key, the key itself, the trusted key authority, and/or other relevant information. In one embodiment, the functionality of trusted key authority 320 is provided by a server or other computerized device.

In an open system, where unknown users can attempt authentication (e.g., in a public grocery store), trusted key authority 320 provides verification that a key presenting a certain code is legitimate. By contrast, in a closed system, only known users are legitimate (e.g., owners of a home), the trusted key authority 320 can be maintained locally and serves to verify that the key belongs to one of the limited number of users that can use the system.

FIG. 4 is a flow chart illustrating a method 400 for authenticating a biometrically verified user using a trusted key authority (e.g., authority 320). A biometric key (e.g., biometric key 100) is registered 410 with the trusted key authority. The code (e.g., device ID) of the key is stored by the trusted key authority. Additionally, a user is enrolled 420 with the biometric key as described below with reference to FIG. 5.

In various situations, authentication of the key is needed 430 (e.g., by authentication module 310). In one embodiment, authentication can be required prior to allowing access to an application (e.g., application 330). For example, a user can be standing proximate to a slot machine in a casino which requires that a user be over the age of 21. The slot machine can detect the biometric key in the user's pocket, and, in response, spawn a conspicuous pop-up window on the slot machine requesting age verification. Alternatively, the biometric key can blink an LED. In other embodiments, biometric verification is not necessary and only the key itself is authenticated.

The biometric key establishes communication with the authentication module using various techniques. In one embodiment, the key and authentication module engage in preliminary data exchanges to determine who and/or what they are (e.g., to ascertain that they belong to the same system). These data exchanges can include challenge-response dialogs, hashing algorithms, and the like in order to ensure that the biometric key and authentication module are themselves legitimate. Further, in one embodiment the key and authentication module establish a secure communications channel. The key performs the biometric verification of the user 440 as described below with reference to FIG. 6. If the biometric verification of the user is successful, the key provides its code over the secure communications channel.

The code is utilized to authenticate the biometric key itself 450, 460 as described below with reference to FIG. 7 and profile information is received. Responsive to successful authentication of the key, access is allowed 470 to the application. In the slot machine example, a new pop-up window can be spawned to indicate a successful age verification.

FIG. 5 is a flow chart illustrating a method 500 for enrolling biometric data of the user with the biometric key according to one embodiment of the present invention. An agent checks 510 an identification of the user and establishes a profile. The agent can be, for example, a government official, a notary, and/or an employee of a third party which operates the trusted key authority, or another form of witness. The agent can follow standardized procedures such as requiring identification based on a state issued driver license, or a federally issued passport in order to establish a true identity of the user.

The profile describes the user and can include, for example, the user's name, date of birth, age, passwords, account numbers, preferences etc. In some embodiments, the profile stores no or only limited information about the user. For example, the agent might store the date of birth of the user in the profile, but not store any other information about the user. In addition, the profile describes the biometric key and/or key authority. For the biometric key, the profile can store a value indicating the status of the key, such as whether the key is in-service, out-of-service, abandoned, lost, stolen etc. For the key authority, the profile can store a value identifying the key authority.

The agent also collects and persistently stores 520 biometric data from the user. To do so, a fingerprint or eye retina can be scanned and converted to data which is then persistently stored in the biometric key. In one embodiment, the agent does not retain the biometric data. Since this step occurs under control of the agent, the agent can be certain that the biometric data stored within the key matches the user who presented the identification. The agent also obtains the code (e.g., device ID) from the biometric key in which the biometric data was stored. The agent associates the code and the profile using a table and/or other data structure.

FIG. 6 is a flow chart illustrating a method 600 for verifying a subject presenting the biometric key according to one embodiment of the present invention. In response to an authentication request, a user scan is requested 610 (e.g., by a blinking LED). Once the subject provides a fingerprint, scan data is received 620. Scan data is compared for a match 630 to previously-stored biometric data. If there is no match, then verification fails 650.

If there is a match, the subject is verified 640 as the user. The code indicating a successful verification is wirelessly sent 650 from the biometric key (e.g., by RF communication module 230).

FIG. 7 is a flow chart illustrating a method 700 for authenticating a biometric key according to one embodiment of the present invention. The code is wirelessly received 710. A request for authentication of the code is sent to the trusted key authority 720. The trusted key authority determines whether the code is authentic 730 (i.e., it was created through an established enrollment process) and has a valid status (e.g., has not expired). If authentication is successful, the trusted key authority sends an access message to the application to allow user access and/or provide additional information from the profile 740 (such as the user's age). If authentication is not successful, authentication fails 750 and the message to the application indicates that the user should be denied access.

In some embodiments, the biometric key provides multiple codes and/or other data values. For example, the key can provide a device ID code that the authentication module can provide to the trusted key authority in order to authenticate the key, and the key can provide a secret decryption value that can be used to communicate with the biometric key. As used herein, the term â€œcodeâ€ is intended to include one or more of these values, depending upon the specific embodiment.

The order in which the steps of the methods of the present invention are performed is purely illustrative in nature. The steps can be performed in any order or in parallel, unless otherwise indicated by the present disclosure. The methods of the present invention may be performed in hardware, firmware, software, or any combination thereof operating on a single computer or multiple computers of any type. Software embodying the present invention may comprise computer instructions in any form (e.g., source code, object code, interpreted code, etc.) stored in any computer-readable storage medium (e.g., a ROM, a RAM, a magnetic media, a compact disc, a DVD, etc.). Such software may also be in the form of an electrical data signal embodied in a carrier wave propagating on a conductive medium or in the form of light pulses that propagate through an optical fiber.

While particular embodiments of the present invention have been shown and described, it will be apparent to those skilled in the art that changes and modifications may be made without departing from this invention in its broader aspect and, therefore, the appended claims are to encompass within their scope all such changes and modifications, as fall within the true spirit of this invention.

In the above description, for purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of the invention. It will be apparent, however, to one skilled in the art that the invention can be practiced without these specific details. In other instances, structures and devices are shown in block diagram form in order to avoid obscuring the invention.

Reference in the specification to â€œone embodimentâ€ or â€œan embodimentâ€ means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment of the invention. The appearances of the phrase â€œin one embodimentâ€ in various places in the specification are not necessarily all referring to the same embodiment.

Some portions of the detailed description are presented in terms of algorithms and symbolic representations of operations on data bits within a computer memory. These algorithmic descriptions and representations are the means used by those skilled in the data processing arts to most effectively convey the substance of their work to others skilled in the art. An algorithm is here, and generally, conceived to be a self-consistent sequence of steps leading to a desired result. The steps are those requiring physical manipulations of physical quantities. Usually, though not necessarily, these quantities take the form of electrical or magnetic signals capable of being stored, transferred, combined, compared, and otherwise manipulated. It has proven convenient at times, principally for reasons of common usage, to refer to these signals as bits, values, elements, symbols, characters, terms, numbers, or the like.

It should be borne in mind, however, that all of these and similar terms are to be associated with the appropriate physical quantities and are merely convenient labels applied to these quantities. Unless specifically stated otherwise as apparent from the discussion, it is appreciated that throughout the description, discussions utilizing terms such as â€œprocessingâ€ or â€œcomputingâ€ or â€œcalculatingâ€ or â€œdeterminingâ€ or â€œdisplayingâ€ or the like, refer to the action and processes of a computer system, or similar electronic computing device, that manipulates and transforms data represented as physical (electronic) quantities within the computer system's registers and memories into other data similarly represented as physical quantities within the computer system memories or registers or other such information storage, transmission or display devices.

The present invention also relates to an apparatus for performing the operations herein. This apparatus can be specially constructed for the required purposes, or it can comprise a general-purpose computer selectively activated or reconfigured by a computer program stored in the computer. Such a computer program can be stored in a computer readable storage medium, such as, but is not limited to, any type of disk including floppy disks, optical disks, CD-ROMs, and magnetic-optical disks, read-only memories (ROMs), random access memories (RAMs), EPROMs, EEPROMs, magnetic or optical cards, or any type of media suitable for storing electronic instructions, and each coupled to a computer system bus.

The algorithms and modules presented herein are not inherently related to any particular computer or other apparatus. Various general-purpose systems can be used with programs in accordance with the teachings herein, or it may prove convenient to construct more specialized apparatuses to perform the method steps. The required structure for a variety of these systems will appear from the description below. In addition, the present invention is not described with reference to any particular programming language. It will be appreciated that a variety of programming languages can be used to implement the teachings of the invention as described herein. Furthermore, as will be apparent to one of ordinary skill in the relevant art, the modules, features, attributes, methodologies, and other aspects of the invention can be implemented as software, hardware, firmware or any combination of the three. Of course, wherever a component of the present invention is implemented as software, the component can be implemented as a standalone program, as part of a larger program, as a plurality of separate programs, as a statically or dynamically linked library, as a kernel loadable module, as a device driver, and/or in every and any other way known now or in the future to those of skill in the art of computer programming. Additionally, the present invention is in no way limited to implementation in any specific operating system or environment.

It will be understood by those skilled in the relevant art that the above-described implementations are merely exemplary, and many changes can be made without departing from the true spirit and scope of the present invention. Therefore, it is intended by the appended claims to cover all such changes and modifications that come within the true spirit and scope of this invention.