System and method for enrolling in a biometric system

Abstract
A system and method for enrolling in a biometric authorization system. A system user may be authorized to enroll by providing biometric data from both his person and a third party token.
Description
FIELD OF THE INVENTION

This application relates generally to a system and method of enrollment into a biometric authorization system. More particularly, the present invention relates to a system and method for utilizing registered biometric data to enroll in a biometric authorization system.


BACKGROUND OF THE INVENTION

Generally, systems that provide biometric authorization for verifying an individual's identity, verifying an individual's age, or authorizing a financial transaction require that a system user undergo an enrollment. In an enrollment, the individual typically presents identity verifying information, documents to attest to his true identity, and one or more biometric scans. After enrollment, a user is free to conduct transactions in the system. What is needed are systems and methods that increase the level of enrollment of users in a biometric authorization system.


SUMMARY OF THE INVENTION

The present invention addresses the aforementioned needs by providing a method of allowing individuals to enroll in a biometric authorization system by employing previously registered biometric data. The present invention provides a flexible process by which information registered in a third party system is employed to enroll an individual in a biometric authorization system.





BRIEF SUMMARY OF THE DRAWINGS


FIG. 1 illustrates an overview of the general architecture of a system for enrolling a system user in a biometric system according to an embodiment of the present invention.



FIG. 2 illustrates a flowchart of a process for enrollment in a biometric authorization system by utilizing previously registered biometric data.



FIG. 3 illustrates a flowchart of a process for self-contained enrollment in a biometric authorization system.



FIG. 4 illustrates a flowchart of a process for distributed enrollment in a biometric authorization system.





DETAILED DESCRIPTION OF THE INVENTION

Additional objects and advantages of the present invention will be apparent in the following detailed description read in conjunction with the accompanying drawing figures.


As previously noted, the present invention encompasses a system and method for enrolling user information into a system for verifying identity through tokenless or token-based biometric authorization. The disclosed enrollment method allows a user to utilize biometric information associated with a third party token to enroll in a biometric authorization system. The system may be configured to accept a variety of tokens linked with various forms of biometric information. In one scenario, the system acquires user biometric information that is stored on the token itself. For example, a driver's license may store fingerprint information in a magnetic stripe, a credit card may have an image of the user printed on its surface, or a smartcard may have a biometric template stored in an embedded chip. In another scenario, the system utilizes the token to locate biometric information archived at a third party location. For instance, a database for the Department of Motor Vehicles may have a user's fingerprint information on record and by presenting his driver's license, a user may authorize the system to access this information. Alternatively, the system may be configured to accept biometric information from more than one user token, thus further verifying the identity of the user by comparing user biometric information held on a multiple of tokens for user biometric verification.


The system user presents his token in conjunction with a scan of his biometric at an enrollment station. In one scenario, the system receives biometric data from one or more biometric tokens. In addition to the token biometric data, the user presents biometric data by means of a biometric input device. The biometric data can include a fingerprint scan, an iris scan, a facial scan, a voice scan, a retinal scan, hand architecture, a DNA sample, or any other physical measurement pertaining to a user's person.


The biometric data acquired by means of the token is compared to the biometric data received from the user. If the biometric data matches, the system user is enrolled in the system. The system then stores the biometric data in a user record to be employed at subsequent biometric authorizations. In general, the system may store the user biometric data, token biometric data, or the best biometric data provided. Alternatively, the system may be configured to combine received biometric data with token data and store this composite data. A biometric authorization generally refers to an authorization in which the user provides biometric data to be matched against a biometric record in a database. For example, a user may undergo biometric authorization to complete a financial transaction or to gain access to an age-restricted location. As would be appreciated, the location of the database as well as the specific mechanism by which the biometric data is matched to a particular biometric record would be implementation dependent and would not be limiting on the scope of the present invention. Thus, in a biometric authorization, the biometric data taken during the authorization can be matched against registered biometric data at a location where the registered biometric data is stored or where the authorization biometric data is gathered.


Additionally, the principles of the present invention are not limited to using one form of biometric. For example, the biometric data referred to throughout this description can represent a biometric image (or sample) and/or a mathematical representation of the biometric image, often referred to as a biometric “template”. In one example, a biometric template can represent any data format that includes feature, positional, or other representing information of characteristics of biometric data. Alternatively, a template may be a mathematical representation of more than one biometric. For example, a user template may be generated from biometric data acquired from two individual fingers, such as a thumb and index finger, or from a finger and an iris scan.


In addition to biometric data, the user may provide the system with other information, such as name, address, phone number, email address, social security number, age information, identification number, government-issued identification number, financial account information, biometric token information and the like. This information may be hand-keyed into the system or may be acquired by other means, such as from the provided token or other documents, tokens, and vouchers. Additionally, user information may be acquired from a third party database. The information is stored in the user's record and may be employed at subsequent transactions as needed. The user record may be located at a database, on a token, or both.



FIG. 1 illustrates a general architecture overview of an identity verification system 100 that is based on biometric authorization. As will be described in greater detail below, an identity verification system 100 enables a flexible enrollment process by which users may enroll in the system. This registration information is stored in at least one system database 108, 110 where system user records are stored. In one embodiment, the system database is a central database to which all system user records are stored and from which system user records are accessed for identity verification. In another embodiment, the system database is one or more operator databases 110 to which a select set of system operator records are stored and from which a select set of system operator records are accessed for identity verification. In an additional embodiment, identity verification system 100 may also utilize a combination of central databases 108 and one or more operator databases 110. In general, embodiments utilizing a combination of system databases 108, 110 enable increased control of information flow throughout identity verification system 100. As described in greater detail below, various examples of information flow configurations within the system can include “open,” “closed,” and “multiple system operator” system models. In still further embodiments, system database 108, 110 can further comprise one or more sub databases that are contained within a particular system database 108, 110. In such embodiments, system user data, system operator data, and other system data may be distributed across multiple databases within the system database.


A system user record holds system user biometric information and other identity verifying information related to an individual seeking biometric recognition/verification so that the system user may be identified within the system. The information held in such a record may include, by way of illustration and without limitation, a system user's government identification number(s) and corresponding state(s) of issue, home address, and a telephone number and at least one biometric record. A system user may present any number of identity verifying documents or testaments to his identity depending on the embodiment of the biometric system. By way of illustration and not of limitation, examples of such documents or testaments include a financial token, a digital image, a video clip, family information, or a DNA sample. Depending on the particular implementation, a system user record can also hold financial account information and/or a system identification number (SID). An SID is a code used in conjunction with a system user biometric scan for biometric recognition/verification.


Additionally, system user records are marked according to various states of activity in a biometric authorization system. Such states may include but are not limited to pre-active, active, and negative. Pre-active system user records include those where a system user record has been created and the record has not been enabled. Active system user enrollment records include those where a system user record has been created and is enabled for use. Negative system user records include those where a system user record has been created but fraud regarding information presented for storage or stored in that record has been detected. After a system user record includes enabling enrollment information, the system user record is marked active, and a history of the record's activity is stored in the system user record. In an additional embodiment, system user records that are enabled and are marked active are also marked as verified or unverified. Verified records are those that have been reviewed and verified by at least one system operator, third party, and/or third party database. Unverified records are those that contain the necessary enrollment data needed to enable their respective system users to identify their identities in the system but that have not been verified.


The system also comprises system operator records that hold information useful for authenticating an operator, such as a name or ID number, device ID numbers associated with the operator, an address, and a phone number. In an alternate embodiment of the present invention, the operator records also hold employer information if the operator is an employee of an employer who is also an operator. In another embodiment of the present invention, operator records hold an operator SID and/or an operator biometric scan.


The system may be configured so that at least one system database 108, 110 is connected to at least one network 102, such as but not limited to, the Internet. This network comprises connections to at least one enrollment station where a system user may enter enrollment information. Enrollment stations are composed of at least one enrollment device and the necessary means for sending and receiving information to and from a system user and to and from a system database. These stations include but are not limited to a vending machine 152, a kiosk 156, a personal computer 132, a user service desk 160, a point of sale terminal 164, or a wireless device 136, 140, 144, connected via wireless network 104, with respective biometric input devices (BIDs) 154, 158, 134, 162, 166, 138, 142, and 146. BID devices are illustrated in FIG. 1 as peripheral devices for purposes of emphasis only. The system should not be so limited and may certainly incorporate devices with integrated BIDs.


Networks used in additional embodiments include LANs (local area networks), WANs (wide area networks), and telephone networks. In one example, system users communicate with at least one system database 108, 110 via telephone 128, with a connected BID device 130.


Additional embodiments of the system also comprise connections to one or more third party sources, such as a third party database 106 and/or one or more financial institutions 112, in which system user-presented information is verified and/or from which system user information is pulled.


In one embodiment, the system is configured as an “open” system, meaning all information entered into the system is transmitted to and stored in a centralized system database 108. An open system allows enrollment at any enrollment station in the system because an open system shares system user information stored in the centralized system database 108 with all stations.


In an alternate embodiment, the system is configured as a “closed” system, meaning information entered into the system via a specific operator device is transmitted to and stored in a system database specific to that operator 110, and this information is not shared with other enrollment stations or other system databases. This is referred to as a “closed” system because system users who enrolled in one system operator's database 110 must enroll in the database of each additional system operator system wherein they would like to enroll their information. Operator system databases 110 in closed systems may query other databases, such as a third party information database 118. However, all system user information that is enrolled into a particular operator system database 110 is stored in that database. In an alternate embodiment of the closed system, information pertaining to specific system operators is stored in a partitioned, central system database 108. System operator related information is stored in system, operator-specific partitions and is closed to all other system operators. Only the system operator, system operator employees, and authorized entities may access that partition of the central system database 108. In yet an additional embodiment, system operator related information stored in an operator system database is additionally stored on the central system database 108 where their system users' records are stored. Such an embodiment is useful for information protection in the event database information is lost.


In a further embodiment of the present invention, system user information is “selectively shared” and stored in select system multiple-operator databases or select, system multiple-operator partitions within the central system database 108. In this embodiment, a group of system operators share data with each other and they choose whether or not to share system information with other system operators within the system. Such a system is referred to as a “selectively shared” system. This system allows a chain of system operators owned by the same entity or linked in some other manner to share system user information amongst them without sharing that information with all other non-designated system operators registered in the system. Information in such a system may be shared between one or more operator system databases 110 and the central system database 108 freely or sharing may be monitored by rules set in the operator system databases 110, the central system database 108, or both. By way of illustration and not as a limitation, one system operator might only want to share system user transaction information with one of five system operators in a multi-verifier system or all system operators might not want to send or store system user transaction information to the central system database 108. Such a system allows system operators greater control over information flow while still allowing various user conveniences, such as being able to enroll at any store in a selectively shared chain.


The configuration of the system as an “open” system, “closed” system, or “selectively shared” system illustrates various ways of implementing the principles of the present invention. System configuration might be determined by the system in which the enrollment information is used. For example, a merchant who is an operator in the system and who conducts biometrically authorized customer loyalty programs might have a system configured with his own operator system database 110 and one or two biometric authorization terminals connected to that database. In this system configuration, the merchant's database files only exist on his database 110 and are retrieved or accessed for biometric matching only by the one or two pre-determined stations connected to the database 110; therefore, the system would be a “closed” system.



FIG. 2 illustrates a flowchart of an enrollment process in a biometric authorization system that utilizes previously registered biometric data. At step 202, a user is authorized for enrollment by the use of one or more third party biometric tokens. This authorization may occur in several ways. In one embodiment, the user presents one or more biometric tokens along with a biometric scan to an enrollment station where the user biometric data is compared to the token biometric data. The system may acquire biometric data stored upon the token in numerous ways, such as, but not limited to, a magnetic stripe, a barcode, an embedded chip, or an image imprinted on the token's surface or embedded within the token. Alternatively, biometric data may be located in a third party database 106 to which the token provides access. The user and/or the token may indicate which third party database 106 to be accessed. In one scenario, the user has preauthorized the third party to permit other biometric systems to access all or part of his user record. For example, a user registered at a Department of Motor Vehicles may have noted on his registration form that other systems may have access to his biometric, address, age information, and other such data.


If the token biometric data matches the user biometric data, the user is authorized for enrollment. For example, a user employing a smartcard with fingerprint data stored in an embedded chip places his token in the card reader and places his finger upon a biometric input device. If the biometric data acquired from the token matches the data retrieved from the fingerprint scan, the user is authorized to enroll.


In another embodiment, the user may be required to authorize his identity by presenting one or more biometric tokens along with a biometric scan to a verification system independent from the enrollment station. This independent verification may be completed at a service device or may be supervised by a system operator. Additionally, the independent verification may be recorded for review at a later time. The user would present a biometric token along with a biometric scan, and if the acquired biometric data matches, the user would be authorized to enroll. For example, a user may present his biometric token and a biometric scan to an attendant at a convenience store. This presentation may be performed in conjunction with other transactions, such as a purchase transaction. The attendant could then employ an independent system device to perform a biometric identification check on the user. If the user is successfully identified, the attendant and/or the device may inform the user that he may enroll in the biometric authorization system. In one embodiment, the independent verification device may transmit a signal to the enrollment station acknowledging that the user is permitted to enroll in the biometric authorization system.


At step 204, the user enrolls in the biometric system. Due to the initial identity verification provided at step 202, this enrollment process can be performed without supervision by an attendant. If the user has already provided biometric information at the enrollment station, that biometric information can be stored in a user record to be employed upon subsequent biometric authorizations. If the user's third party biometric token was authorized at an independent device, the user presents his biometric at the enrollment station. Once acquired, the biometric information is stored in a user record to be used at later biometric authorizations. The system may be configured to register the token biometric data, the received biometric data or all biometric data acquired. In one embodiment, the system may be configured to evaluate the token biometric data and the received biometric data and enroll the superior data. Alternatively, the system may store composite biometric data generated from the token biometric data and the received biometric data.


In addition to biometric data, the user may provide other information, such as name, address, phone number, financial information and the like. This information may be hand-keyed into the system or may be acquired by other means. In one scenario, user information is acquired by means of the token employed for user authorization at step 202. The system may access information stored on the token or the token may indicate and provide access to a third party database housing user data. Additionally, the system may acquire user information from other sources. Other possible sources are additional tokens, such as credit cards or identification documents. Another possible source may be a paper check with magnetic ink readable by a Magnetic Ink Character Recognition (MICR) device attached to the enrollment station. The system may be configured to acquire user information from one or more documents, tokens, and/or vouchers via magnetic stripes, barcodes, digital scan, Optical Character Recognition (OCR), an embedded data chip, radio frequency identification (RFID) and the like.


At step 206, the biometric authorization system analyzes the enrollment biometric data and user information to determine the reliability of the data and the authenticity of the user. This verification may be completed by an automatic process of the system, a third party system, and/or a system operator. Depending on the system configuration, the enrollment biometric data may be verified instantly granting the user access, conditionally verified allowing a user limited access, or the user may be prohibited from employing the enrolled biometric data until it has been verified. For example, a user may enroll in the system by utilizing a biometric check card from an obscure bank. Because the token biometric data utilized at enrollment is from an unfamiliar source, the user may be required to supply a photo ID in conjunction with his biometric when accessing the biometric authorization system for the first time. This may serve as verification and allow the user full access in the system for subsequent transactions.



FIG. 3 illustrates an embodiment of a self-contained method for enrollment in a biometric authorization system. At step 302, the system receives token biometric data and biometric data received from the user at an enrollment station. The system user presents one or more biometric tokens in conjunction with a live scan of his biometric at the enrollment station. For example, the user may swipe his driver's license through a magnetic stripe reader and then place his finger upon a fingerprint sensor. In another example, the user performs an iris scan and then supplies an identification card with bar-coded biometric data. If the user token does not house biometric information, the system accesses the biometric data from a third party database indicated by the token.


In addition to biometric data, the user may provide other information, such as name, address, phone number, financial information and the like. This information may be hand-keyed into the system or may be acquired by other means. The system may acquire further user information from the biometric token previously employed. The information may be stored on the token or the token may indicate and provide access to a third party database housing user data. Additionally, the system may acquire user information from other sources, such as other tokens, documents and/or vouchers via magnetic stripes, barcodes, digital scan, MICR, OCR, an embedded data chip, a RFID and the like.


At step 304, the system compares the biometric data received from the user with the biometric data acquired via the token. If the biometric data matches sufficiently to meet system requirements, the user is enrolled in the biometric authorization system. The comparison of the data may transpire at a variety of locations. In one embodiment, the biometric data is compared at the enrollment device. In this localized matching system, the system acquires the user's biometric scan and retrieves the token biometric data, either from the token itself or an associated third party database 106, and compares the biometric data at the local device. If the biometric data matches, the user's information, including biometric data, is transmitted to a database 108, 110 for storage. Alternatively, the system may be configured for centralized matching. In a centralized matching system, after the system receives the user's biometric scan data and the token biometric data, the data is transmitted to a database 108, 110 for comparison. If the biometric data matches, biometric data is stored in a user record at the database 108, 110. Alternatively, if a third party database 106 houses the token biometric data, the token biometric data is retrieved from the third party database 106 and then transmitted to a system database 108, 110 along with the scanned biometric data for comparison. In another scenario, the scanned biometric data is sent to the third party database 106 in conjunction with a token indicator, and the biometrics are matched at the third party database 106. This may be necessary if the third party does not permit retrieval of biometric data stored within its records.


At step 308, the system stores the biometric data and user information in a user record to be employed at subsequent biometric authorizations. The system may store the user biometric data, token biometric data, all the biometric data provided, or the biometric data deemed the most beneficial. Alternatively, the system may be configured to combine scanned biometric data with token data and store this composite data.


As noted, the principles of the present invention can be used for verifying identity through tokenless or token-based biometric authorization. In one embodiment, the user record that is stored at step 308 is also stored on a new token that can be issued to the user. This newly-issued token, which represents a form of token conversion based on the third-party token, can form the basis for future transactions. More generally, it is a feature of the present invention that a first token of a given level of reliability and security can be used to generate a second token or other biometric enrollment.



FIG. 4 illustrates a distributed method for enrollment in a biometric authorization system. This distributed method can apply to those instances where independent devices would exist at the enrollment location. At step 402, the system user presents one or more biometric tokens in conjunction with a scan of his biometric at an independent device. If the user token does not house biometric information, the device accesses the biometric data from a third party database 106 indicated by the token.


At step 404, the system compares the biometric data received from the user with the token biometric data. The comparison of the biometric data may transpire at a variety of locations. In one embodiment, the biometric data is locally compared at the independent device. Here, the system acquires the user's biometric scan and retrieves the token biometric data, either from the token itself or a third party database 106 and compares the data at the device. Alternatively, in a centralized matching system, after the system receives the scanned biometric data and the token biometric data, the data is transmitted to a database 108, 110 for comparison. In a further embodiment, if a third party database 106 houses the token biometric data, the token biometric data is retrieved from the third party database 106 and then transmitted to an independent authorization system along with the scanned biometric data for comparison. In yet another embodiment, the scanned biometric data is sent to the third party database 106 in conjunction with the token indicator, and the biometrics are matched at the third party database 106. This may be necessary if the third party does not permit retrieval of biometric data stored within its records.


At step 406, if the biometric data matches sufficiently to meet a system requirement, the user is authorized to enroll in the biometric authorization system. In one embodiment, the independent device transmits a signal to the enrollment station acknowledging that the user has been authorized. Alternatively, the device may be utilized by a system operator who permits the user to enroll upon a successful authorization.


Once the user has been authorized, he may enroll at step 408. At an enrollment station, the user presents his biometric data by means of a biometric input device. The system may also receive biometric data from one or more biometric tokens. In addition to biometric data, the user may provide other information, such as name, address, phone number, financial information and the like. This information may be hand-keyed into the system or may be acquired by other means, such as from the provided token or other documents, tokens and vouchers. The system may be configured to acquire user information from a document, token, or voucher via magnetic stripes, barcodes, digital scan, MICR, OCR, an embedded data chip, a RFID and the like.


At step 410, the system stores the biometric data and user information in a user record to be employed at subsequent biometric authorizations. The system may store the user biometric data, token biometric data, all the biometric data provided, or the biometric data deemed the most beneficial. Alternatively, the system may be configured to combine received biometric data with token data. Again, in one embodiment, the biometric data and user information can also be stored in a token and issued to the user.


As aforementioned, after the user has enrolled in a biometric authorization system, the system may analyze enrolled biometric data and user information in order to determine the reliability of the data and the authenticity of the user. In order to ensure that a biometric token utilized for enrollment authorization is from a reputable source, the system may be configured to evaluate the supplied token. The evaluation may be based upon one or more a biometric token source, a biometric token type, a biometric token certification, a biometric token generation process, a biometric token generation date, a biometric token generation time, a biometric token generation location, and a biometric token generation supervising attendant. Tokens may be assigned a rating corresponding with the integrity of this information. For example, tokens of a trustworthy origin, such as government-issued documents, may be rated highly and accepted without further scrutiny. However, if the biometric token is from an ambiguous source, such as an employee identification card, enrollment may be declined or the user may be required to provide further information to complete enrollment. This information may be entered immediately at the enrollment station or during a subsequent transaction in the biometric authorization system. For example, a user may employ a biometric employee ID card to enroll in the system. The system may not recognize the source of this biometric token and require the user supply driver's license information to continue enrollment. This information may be acquired by swiping the license through a card reader at the enrollment station. If the enrollment station is not equipped with such a reader or if the user does not have his license, he may have limited access to the system until the verification is complete. The user may be required to present his driver's license to a system operator when first employing the biometric authorization system. Once the required information has been registered in the user record, full access may be granted. Alternatively, enrollment verification may be completed by a third party system linked to the biometric authorization system.


In an additional embodiment, a system operator may verify the user to complete enrollment. If a biometric token utilized for enrollment is deemed ambiguous, a system operator may be notified and requested to provide verification. For example, at an enrollment station, a user may present a biometric token with a low integrity rating. The system may then transmit a signal to a system operator device notifying him of the situation. If the system operator is located at the same location as the enrollment station or overseeing the enrollment process from a remote location, the operator may acquire more identity verification information from the user. If the system operator deems the enrolling user is acceptable, he may notify the system, either at the enrollment station or at a separate system device. Alternatively, if the system operator is not accessible from the enrollment site, the user may be granted limited system access until a system operator has reviewed his enrollment information. If the system operator deems that more information is needed to verify the user, the user may be prompted to provide more verification information upon subsequent system use. For example, the user may be required to answer a security question upon his initial transaction in the system. The correct answer would remove the restriction and grant the user system access at future transactions.


In an additional embodiment, the enrollment process may be recorded to ensure security. An enrollment station may be equipped with a recording device, such as, but not limited to, a video or digital camera. The recorded enrollment process may then be employed to verify the user and/or the system operator and aid in the prevention of fraudulent use. Additionally, the recorded enrollment may be compared to an image stored at a database to authenticate the user. Alternatively, the camera may provide a live video feed to a security service.


A system and method for enrolling in a biometric authorization system has been illustrated. It will be appreciated by those skilled in the art that the system and method of the present invention can be used to perform enrollments in a biometric system. It will thus be appreciated by those skilled in the art that other variations of the present invention will be possible without departing from the scope of the invention disclosed.


These and other aspects of the present invention will become apparent to those skilled in the art by a review of the preceding detailed description. Although a number of salient features of the present invention have been described above, the invention is capable of other embodiments and of being practiced and carried out in various ways that would be apparent to one of ordinary skill in the art after reading the disclosed invention. Therefore, the above description should not be considered to be exclusive of these other embodiments. Also, it is to be understood that the phraseology and terminology employed herein are for the purposes of description and should not be regarded as limiting.

Claims
  • 1. A method for enrolling a user in a biometric authorization system, the method comprising: receiving, from a first biometric input device enabled to acquire biometric data stored on a token, a token biometric sample;receiving, from a second biometric input device enabled to acquire biometric data via a live biometric scan of an individual, a live biometric sample;comparing said received token biometric sample with said received live biometric sample;in response to said received live biometric sample matching said received token biometric sample, storing a new biometric sample, the new biometric sample being a composite of said received live biometric sample and said received token biometric sample in a user record for subsequent authorization determinations in said biometric authorization system, wherein the new biometric sample comprises at least a portion of the received live biometric data and at least a portion of the received token biometric data;associating with the user record an integrity rating, said integrity rating indicating an evaluated integrity of the token, wherein the evaluated integrity of the token is based on a token source, a token generation process, and a token generation location; andgranting the user a level of access to the biometric authorization system based upon the associating of the user record with the integrity rating.
  • 2. The method of claim 1, further comprising receiving a user identification code.
  • 3. The method of claim 1, wherein said biometric data is one or more of a fingerprint, an iris scan, a facial scan, a voice scan, a retinal scan, a hand architecture, and a DNA sample.
  • 4. The method of claim 1, further comprising authorizing a request for a financial transaction.
  • 5. The method of claim 1, further comprising authorizing a request for an age-verification transaction.
  • 6. The method of claim 1, further comprising authorizing a request for an identity verification transaction.
  • 7. The method of claim 1, wherein said user record is located at one or more of a database and a token.
  • 8. The method of claim 1, further comprising receiving additional information from one or more of a biometric token, magnetic ink character recognition data reader, a barcode reader, a digital scanner, a manual input device, a radio frequency identification device, an embedded data chip reader, a magnetic stripe reader, optical character recognition device and a database.
  • 9. The method of claim 1, further comprising receiving additional information including one or more of a user name, a user address, a user phone number, a user email address, a user social security number, user age information, a user identification number, a government-issued identification number, user financial account information, and biometric token information.
  • 10. The method of claim 9, further comprising storing at least part of said additional information in said user record.
  • 11. The method of claim 1, further comprising storing a recording of one or more of said user, a system operator, and an enrollment event.
  • 12. The method of claim 11, wherein said recording includes one or more of an image and a video recording.
  • 13. The method of claim 12, further comprising comparing said image to a registered image.
  • 14. The method of claim 13, wherein said registered image is retrieved from a database.
  • 15. The method of claim 1, further comprising receiving a live video transmission of said enrolling.
  • 16. The method of claim 1, further comprising limiting user access to said biometric authorization system until said received token biometric sample is evaluated by one or more of an automated system process, a third party, and a system operator.
  • 17. The method of claim 16, wherein said system operator is at a remote location.
  • 18. The method of claim 1, wherein said comparing is performed at one or more of a local biometric device and a database.
Parent Case Info

This application is a continuation-in-part of application Ser. No. 10/743,189, filed Dec. 23, 2003, now U.S. Pat. No. 7,367,049 which is a continuation-in-part of application Ser. No. 10/678,646, filed Oct. 6, 2003, which is a continuation-in-part of application Ser. No. 10/251,305, filed Sep. 20, 2002, now U.S. Pat. No. 7,269,737 which claims domestic priority from provisional application No. 60/324,229, filed Sep. 21, 2001. Each above-identified application is incorporated by reference herein, in its entirety, for all purposes.

US Referenced Citations (258)
Number Name Date Kind
4230214 Cortez Oct 1980 A
4359631 Lockwood et al. Nov 1982 A
4553222 Kurland et al. Nov 1985 A
4716593 Hirai et al. Dec 1987 A
4879747 Leighton et al. Nov 1989 A
4915205 Reid et al. Apr 1990 A
4995081 Leighton et al. Feb 1991 A
5042073 Collot et al. Aug 1991 A
5086389 Hassett et al. Feb 1992 A
5144553 Hassett et al. Sep 1992 A
5274695 Green Dec 1993 A
5280527 Gullman et al. Jan 1994 A
5289183 Hassett et al. Feb 1994 A
5335288 Faulkner Aug 1994 A
5351187 Hassett Sep 1994 A
5352876 Watanabe et al. Oct 1994 A
5386104 Sime Jan 1995 A
5412738 Brunelli et al. May 1995 A
5450980 Laidlaw Sep 1995 A
5453601 Rosen Sep 1995 A
5455407 Rosen Oct 1995 A
5483601 Faulkner Jan 1996 A
5485510 Colbert Jan 1996 A
5523551 Scott Jun 1996 A
5546523 Gatto Aug 1996 A
5581630 Bonneau, Jr. Dec 1996 A
5594806 Colbert Jan 1997 A
5598474 Johnson Jan 1997 A
5602933 Blackwell et al. Feb 1997 A
5613012 Hoffman et al. Mar 1997 A
5615217 Horne et al. Mar 1997 A
5615277 Hoffman Mar 1997 A
5657389 Houvener Aug 1997 A
5679938 Templeton et al. Oct 1997 A
5688974 Devine et al. Nov 1997 A
5696739 Chang Dec 1997 A
5719950 Osten et al. Feb 1998 A
5722526 Sharrard Mar 1998 A
5737439 Lapsley et al. Apr 1998 A
5745598 Shaw et al. Apr 1998 A
5751973 Hassett May 1998 A
5764789 Pare, Jr. et al. Jun 1998 A
5790674 Houvener et al. Aug 1998 A
5790785 Klug et al. Aug 1998 A
5799092 Kristol et al. Aug 1998 A
5802199 Pare, Jr. et al. Sep 1998 A
5805082 Hassett Sep 1998 A
5805719 Pare, Jr. et al. Sep 1998 A
5832464 Houvener et al. Nov 1998 A
5838812 Pare, Jr. et al. Nov 1998 A
5845256 Pescitelli et al. Dec 1998 A
5850442 Muftic Dec 1998 A
5857079 Claus et al. Jan 1999 A
5864623 Messina et al. Jan 1999 A
5870723 Pare, Jr. et al. Feb 1999 A
5872834 Teitelbaum Feb 1999 A
5893075 Plainfield et al. Apr 1999 A
5897616 Kanevsky et al. Apr 1999 A
5914472 Foladare et al. Jun 1999 A
5927544 Kanoh et al. Jul 1999 A
5930804 Yu et al. Jul 1999 A
5933816 Zeanah et al. Aug 1999 A
5943423 Muftic Aug 1999 A
5982914 Lee et al. Nov 1999 A
5984366 Priddy Nov 1999 A
6009411 Kepecs Dec 1999 A
6012039 Hoffman et al. Jan 2000 A
6018739 McCoy et al. Jan 2000 A
6028950 Merjanian Feb 2000 A
6040783 Houvener et al. Mar 2000 A
D425800 Shin May 2000 S
6061660 Eggleston et al. May 2000 A
6070141 Houvener et al. May 2000 A
6070147 Harms et al. May 2000 A
6092192 Kanevsky et al. Jul 2000 A
6094632 Hattori Jul 2000 A
6105010 Musgrave Aug 2000 A
6119932 Maloney et al. Sep 2000 A
6125192 Bjorn et al. Sep 2000 A
6148091 DiMaria Nov 2000 A
6149055 Gatto Nov 2000 A
6154879 Pare, Jr. et al. Nov 2000 A
6157314 Loftus Dec 2000 A
6160903 Hamid et al. Dec 2000 A
6161059 Tedesco et al. Dec 2000 A
6161090 Kanevsky et al. Dec 2000 A
6175922 Wang Jan 2001 B1
6181807 Setlak et al. Jan 2001 B1
6192142 Pare, Jr. et al. Feb 2001 B1
6196460 Shin Mar 2001 B1
6222914 McMullin Apr 2001 B1
6230148 Pare, Jr. et al. May 2001 B1
6233564 Schulze, Jr. May 2001 B1
6246751 Bergl et al. Jun 2001 B1
6256737 Bianco et al. Jul 2001 B1
6269348 Pare, Jr. et al. Jul 2001 B1
6282658 French et al. Aug 2001 B2
6307955 Zank et al. Oct 2001 B1
6307956 Black Oct 2001 B1
6310966 Dulude et al. Oct 2001 B1
6314169 Schelberg, Jr. et al. Nov 2001 B1
6317723 Walker et al. Nov 2001 B1
6317834 Gennaro et al. Nov 2001 B1
6321339 French et al. Nov 2001 B1
6327573 Walker et al. Dec 2001 B1
6330543 Kepecs Dec 2001 B1
6332134 Foster Dec 2001 B1
6334109 Kanevsky et al. Dec 2001 B1
6334112 Walker et al. Dec 2001 B1
6334113 Walker et al. Dec 2001 B1
6341169 Cadorette, Jr. et al. Jan 2002 B1
6345263 Matsumoto et al. Feb 2002 B1
6363485 Adams et al. Mar 2002 B1
6366682 Hoffman et al. Apr 2002 B1
6370649 Angelo et al. Apr 2002 B1
6381344 Smithies et al. Apr 2002 B1
6389401 Kepecs May 2002 B1
6397126 Nelson May 2002 B1
6397198 Hoffman et al. May 2002 B1
6405125 Ayed Jun 2002 B1
6415262 Walker et al. Jul 2002 B1
6422464 Terranova Jul 2002 B1
6424249 Houvener Jul 2002 B1
6433818 Steinberg et al. Aug 2002 B1
6446044 Luth et al. Sep 2002 B1
6463127 Maier et al. Oct 2002 B1
6466917 Goyal et al. Oct 2002 B1
6470233 Johnson, Jr. Oct 2002 B1
6470322 Walker et al. Oct 2002 B1
6477509 Hammons et al. Nov 2002 B1
6496595 Pucheck et al. Dec 2002 B1
6497360 Schulze Dec 2002 B1
6498970 Colmenarez et al. Dec 2002 B2
6507912 Matyas et al. Jan 2003 B1
6522772 Morrison et al. Feb 2003 B1
6523741 DiMaria et al. Feb 2003 B1
6529871 Kanevsky et al. Mar 2003 B1
6529878 De Rafael et al. Mar 2003 B2
6532459 Berson Mar 2003 B1
6539282 Metcalf et al. Mar 2003 B2
6542874 Walker Apr 2003 B1
6554705 Cumbers Apr 2003 B1
6559776 Katz May 2003 B2
6567787 Walker et al. May 2003 B1
6581042 Pare et al. Jun 2003 B2
6591224 Sullivan et al. Jul 2003 B1
6594376 Hoffman et al. Jul 2003 B2
6636973 Novoa et al. Oct 2003 B1
6646568 MacPhail et al. Nov 2003 B2
6647372 Brady et al. Nov 2003 B1
6650999 Brust et al. Nov 2003 B1
6651063 Vorobiev Nov 2003 B1
6653946 Hassett Nov 2003 B1
6655585 Shinn Dec 2003 B2
6662166 Pare et al. Dec 2003 B2
6685088 Royer et al. Feb 2004 B1
6694300 Walker et al. Feb 2004 B1
6695206 Ross Feb 2004 B2
6715673 Fulcher et al. Apr 2004 B2
6715674 Schneider et al. Apr 2004 B2
6748365 Quinlan et al. Jun 2004 B1
6755344 Mollett et al. Jun 2004 B1
6758394 Maskatiya et al. Jul 2004 B2
6792334 Metcalf et al. Sep 2004 B2
6792422 Stride et al. Sep 2004 B1
6796492 Gatto Sep 2004 B1
6796499 Wang Sep 2004 B1
6827260 Stoutenburg et al. Dec 2004 B2
6854642 Metcalf et al. Feb 2005 B2
6865544 Austin Mar 2005 B1
6873969 Stone et al. Mar 2005 B2
6886742 Stoutenburg et al. May 2005 B2
6935559 Mollett et al. Aug 2005 B2
7630986 Herz et al. Dec 2009 B1
20010000535 Lapsley et al. Apr 2001 A1
20010011680 Soltesz et al. Aug 2001 A1
20010025245 Flickinger et al. Sep 2001 A1
20010034609 Dovolis Oct 2001 A1
20010042022 Kirkpatrick et al. Nov 2001 A1
20010047223 Metcalf et al. Nov 2001 A1
20010047343 Dahan et al. Nov 2001 A1
20020019811 Lapsley et al. Feb 2002 A1
20020029196 Metcalf et al. Mar 2002 A1
20020030584 Perler et al. Mar 2002 A1
20020038165 McHale, IV et al. Mar 2002 A1
20020046121 Walker et al. Apr 2002 A1
20020062249 Iannacci May 2002 A1
20020077889 Kolls Jun 2002 A1
20020077890 LaPointe et al. Jun 2002 A1
20020077902 Marcus Jun 2002 A1
20020087413 Mahaffy et al. Jul 2002 A1
20020091537 Algazi Jul 2002 A1
20020094111 Pucheck et al. Jul 2002 A1
20020107965 Piccionelli Aug 2002 A1
20020111917 Hoffman et al. Aug 2002 A1
20020112177 Voltmer et al. Aug 2002 A1
20020116266 Marshall Aug 2002 A1
20020128851 Chefalas et al. Sep 2002 A1
20020147588 Davis et al. Oct 2002 A1
20020148892 Bardwell Oct 2002 A1
20020149467 Calvesio et al. Oct 2002 A1
20020153414 Stoutenburg et al. Oct 2002 A1
20020154793 Hillhouse et al. Oct 2002 A1
20020161629 Jentoft Oct 2002 A1
20020162031 Levin et al. Oct 2002 A1
20020173986 Lehew et al. Nov 2002 A1
20020178063 Gravelle et al. Nov 2002 A1
20020194128 Maritzen et al. Dec 2002 A1
20020196963 Bardwell Dec 2002 A1
20030006277 Maskatiya et al. Jan 2003 A1
20030009382 D'Arbeloff et al. Jan 2003 A1
20030009393 Norris Jan 2003 A1
20030018522 Denimarck et al. Jan 2003 A1
20030018567 Flitcroft et al. Jan 2003 A1
20030034876 Pucheck et al. Feb 2003 A1
20030046228 Berney Mar 2003 A1
20030046542 Chen et al. Mar 2003 A1
20030055727 Walker et al. Mar 2003 A1
20030067396 Hassett Apr 2003 A1
20030075287 Weik Apr 2003 A1
20030076417 Thomas et al. Apr 2003 A1
20030090473 Joshi May 2003 A1
20030105725 Hoffman Jun 2003 A1
20030126448 Russo Jul 2003 A1
20030130954 Carr et al. Jul 2003 A1
20030144956 Yu et al. Jul 2003 A1
20030150907 Metcalf et al. Aug 2003 A1
20030183689 Swift et al. Oct 2003 A1
20030187790 Swift et al. Oct 2003 A1
20030187796 Swift et al. Oct 2003 A1
20030191709 Elston et al. Oct 2003 A1
20030209599 Gatto Nov 2003 A1
20030216967 Williams Nov 2003 A1
20030216987 Mollett et al. Nov 2003 A1
20030222135 Stoutenburg et al. Dec 2003 A1
20030229539 Algiene Dec 2003 A1
20030229540 Algiene Dec 2003 A1
20030229790 Russell Dec 2003 A1
20030236704 Antonucci Dec 2003 A1
20040012481 Brusseaux Jan 2004 A1
20040020982 Hoffman et al. Feb 2004 A1
20040024672 Brake et al. Feb 2004 A1
20040039632 Han et al. Feb 2004 A1
20040054587 Dev et al. Mar 2004 A1
20040083172 Wiederin Apr 2004 A1
20040088232 Minnis, Jr. May 2004 A1
20040088295 Glazer et al. May 2004 A1
20040143505 Kovach Jul 2004 A1
20040155101 Royer et al. Aug 2004 A1
20040158524 Anderson et al. Aug 2004 A1
20040192434 Walker et al. Sep 2004 A1
20040201520 Flick Oct 2004 A1
20040215565 Huffman Oct 2004 A1
20040254840 Slemmer et al. Dec 2004 A1
20050010478 Gravelle Jan 2005 A1
20050055582 Bazakos et al. Mar 2005 A1
20050144133 Hoffman et al. Jun 2005 A1
20050152598 Birchbauer et al. Jul 2005 A1
Provisional Applications (1)
Number Date Country
60324229 Sep 2001 US
Continuation in Parts (3)
Number Date Country
Parent 10743189 Dec 2003 US
Child 10861864 US
Parent 10678646 Oct 2003 US
Child 10743189 US
Parent 10251305 Sep 2002 US
Child 10678646 US