Single step transaction authentication using proximity and biometric input

Description

BACKGROUND

1. Field of Art

The invention generally relates to electronic authentication, and more specifically, to secure authentication using biometric verification.

2. Description of the Related Art

Optimizing sales transactions and providing secure access to physical and/or digital assets are challenges faced by many businesses and organizations. Ensuring these processes are safe, efficient and simple is important to merchants, providers, users and consumers alike. Conventionally, technologies such as magnetic cards (e.g., credit cards, debit cards, ATM cards, and employee badges) have been used in attempt to address these needs. More recently, various contactless cards or tokens requiring placement near compatible readers have been used.

Each of these technologies, however, has inherent problems in providing secure transaction processing and access control. In particular, the conventional technologies fail to sufficiently ensure that individuals attempting to perform a transaction are associated with the access device and are authorized to do so. Conventional attempts to address this issue include requiring users to provide Personal Identification Numbers (PINs) or passwords in conjunction with account numbers. While in some instances, these options have helped to combat fraudulent activity, these solutions add unwanted complexity and delay to transactions. With the growing need to memorize various PINs and passwords, individuals tend to repeatedly use the same, simple phrase to protect many items, or worse, keep the written phrases in their purse/wallet or next to their computer. Thus, the use of PINs and passwords are often defeated.

A technology better suited to address the issue of authenticating users is biometrics. In biometric authentication, physical and/or behavioral characteristics of an individual are analyzed to uniquely identify the individual. For example, biometric characteristics can include fingerprint, retinal, iris, face, palm, DNA, voice or signature characteristics that can each be uniquely associated with the individual. However, traditional biometric authentication solutions also suffer from significant problems. First, traditional biometric authentication techniques typically expose the participating parties to serious liabilities, risks and inefficiencies. Conventional biometric authentication techniques nearly always require users to release personal, private and unchangeable data to a controlling-entity (e.g., a merchant or business authority) or to a third-party relied upon by the controlling-entity. This exposes an individual's personal biometric information to the possibility of theft and fraudulent use. Further, controlling entities must either assume the risks and liabilities of storing this data, or trust the data to a third-party's care.

Second, conventional biometric authentication techniques generally require an individual to submit biometric information (e.g., a fingerprint, retinal scan, facial scan, or signature) for storage in a database that can then be later used for comparison with biometric data acquired at the point of transaction. This “enrollment” process is time-consuming, risky, error-prone and considered intrusive by many individuals. Further, the enrollment process must be repeated for each individual for every intended use. For example, a user may need to enroll for biometric authentication with his/her company (e.g., for secure access to facilities or digital files), and separately enroll with various merchants using biometric authentication for transactions. Thus, the individual has to spend significant time completing each separate enrollment, and additionally must trust each entity with his/her personal biometric information. For these reasons alone many individuals do not even consider these options.

The above-defined issues represent serious roadblocks to the widespread deployment and acceptance of conventional biometric authentication options. Unless the identified deficiencies are addressed, the full potential of biometric solutions will never be realized. Therefore, a new technology is needed that provides highly reliable, safe and efficient secure authentication for transaction-processing and/or access control. Moreover, the new technology should allow for a simple and efficient enrollment process that does not put an individual's highly personal information at risk of identity theft or other fraudulent use.

SUMMARY

A system and method provide efficient, secure and highly reliable authentication for transaction processing and/or access control applications. A portable physical device, referred to herein as a Personal Digital Key or “PDK”, stores one or more profiles (e.g., a biometric profile) in a tamper-proof memory. The biometric profile is acquired in a secure trusted process and is uniquely associated with an individual that is authorized to use and is associated with the PDK. The PDK can wirelessly transmit the identification information including a unique PDK identification number and the biometric profile over a secure wireless channel for use in an authentication process. Additionally, the PDK can store other information such as credit/debit card information, bank information, or personal information in a memory for use in authorizing or completing a transaction.

Typically, a receiving device, referred to herein as a Reader, wirelessly receives the profile from the PDK in order to process a transaction or provide access to secure digital or physical assets. In one embodiment, the Reader acquires a biometric input from the individual carrying the PDK at the point of transaction. The biometric input can be acquired by, for example, a fingerprint scan, iris scan, retinal scan, palm scan, face scan, DNA analysis, signature analysis, voice analysis or any other input mechanism that provides physical or behavioral characteristics uniquely associated with the individual. The Reader compares the biometric profile received from the PDK to the biometric input obtained at the point of transaction to determine if a transaction should be authorized.

In one embodiment, the Reader is further adapted to communicate with one or more remote registries to provide an additional layer of security in the authentication process. Information transmitted from the PDK can be compared to entries stored in the registries to ensure the PDK (and its owner) have not participated in any fraudulent use and that the PDK is not invalid, lost or stolen. In yet another embodiment, one or more biometric authentications, remote registry authentications or other types of authentication are used in combination.

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, specification 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 subject matter.

BRIEF DESCRIPTION OF THE FIGURES

FIG. 1 is a high level block diagram illustrating a system for secure electronic authentication.

FIG. 2 is a block diagram illustrating one embodiment of a Personal Digital Key (PDK).

FIG. 3 is a block diagram illustrating one embodiment of a Reader.

FIG. 4 is a flowchart illustrating one embodiment of a process for authorizing a transaction using secure authentication.

FIG. 5 is a flowchart illustrating one embodiment of a process for device authentication by a Reader.

FIG. 6 is a flowchart illustrating one embodiment of a process for profile authentication by a Reader.

FIG. 7A is a flowchart illustrating one embodiment of a process for profile testing using a biometric input.

FIG. 7B is a flowchart illustrating one embodiment of a process for profile testing using a personal identification number.

FIG. 7C is a flowchart illustrating one embodiment of a process for profile testing using a picture profile.

FIG. 7D is a flowchart illustrating one embodiment of a process for profile testing using a private or central registry.

FIG. 8 is a flowchart illustrating one embodiment of a process for single step authentication of a transaction using proximity and biometric input.

FIG. 9 is a flowchart illustrating a second embodiment of a process for single step authentication of a transaction using proximity and biometric input.

FIG. 10 is a flowchart illustrating a third embodiment of a process for single step authentication of a transaction using proximity and biometric input.

The figures depict various embodiments of the present invention for purposes of illustration only. One skilled in the art will readily recognize from the following discussion that alternative embodiments of the structures and methods illustrated herein may be employed without departing from the principles of the invention described herein.

DETAILED DESCRIPTION

FIG. 1 is a high level block diagram illustrating a system for securely authenticating an individual for transaction-processing and/or access control applications. The system 100 comprises a Personal Digital Key (PDK) 102, a Reader 108, a network 110 and one or more external databases including a validation database 112, a Central Registry 114 and one or more private registries 116. The Reader 108 is coupled to the PDK 102 by a wireless link 106 and coupled to a network 110 by either a wired or wireless link. The Reader 108 is also adapted to receive a biometric input 104 from a user and is capable of displaying status to a user. The network 110 couples the validation database 112, the Central Registry 114 and two private registries 116 to the Reader 108. In alternative embodiments, different or additional external registries or databases may be coupled to the network 110. In another embodiment, the Reader 108 operates as a standalone device without a connection to the network 110.

The system 100 addresses applications where it is important to ensure a specific individual is authorized to perform a given transaction. A transaction as used herein can include executing a purchase or financial dealing, enabling access to physical and/or digital items, verifying identification or personal information or executing other tasks where it is important to authenticate an individual for use. Generally, the Reader 108 wirelessly receives information stored in the PDK 102 that uniquely identifies the PDK 102 and the individual carrying the PDK 102. The Reader 108 can also receive a biometric input 104 from the individual. Based on the received information, the Reader 108 determines if the transaction should be authorized. Beneficially, the system 100 provides comprehensive authentication without the need for PINs or passwords. Moreover, personal biometric information need not be stored in any local or remote storage database and is only stored on the user's own PDK. Furthermore, in one embodiment, purchase transactions can be efficiently completed without requiring the use of physical credit cards, tokens or other user action beyond initiating the transaction.

The credibility of the system 100 is ensured by the use of a PDK 102 that stores trusted information. The PDK 102 is a compact, portable uniquely identifiable wireless device typically carried by an individual. The PDK 102 stores digital information in a tamper-proof format that uniquely associates the PDK 102 with an individual. Example embodiments of PDKs are described in more detail in U.S. patent application Ser. No. 11/292,330 entitled “Personal Digital Key And Receiver/Decoder Circuit System And Method”; U.S. patent application Ser. No. 11/620,581 entitled “Wireless Network Synchronization Of Cells And Client Devices On A Network”; and U.S. patent application Ser. No. 11/620,577 entitled “Dynamic Real-Time Tiered Client Access”, the entire contents of which are all incorporated herein by reference.

To establish the trust, credibility and confidence of the authentication system, information stored in the PDK 102 is acquired by a process that is trusted, audited and easily verified. The process is ensured by a trusted third-party system, referred to herein as a Notary that administers the acquisition and storage of information in the PDK 102 according to defined security protocols. In one embodiment, the Notary is a system and/or a trusted individual that witnesses the acquisition and storage either in person or remotely. In another embodiment, the Notary comprises trusted hardware that administers the initialization process by an automated system. Thus, once initialized by the trusted process, the PDK 102 can prove that the information it stores is that of the individual. Example embodiments of the initialization process are described in U.S. patent application Ser. No. 11/744,832, (now U.S. Pat. No. 8,412,949, entitled “Personal Digital Key Initialization and Registration For Secure Transaction, ” the entire contents of which are incorporated herein by reference.

The Reader 108 wirelessly communicates with the PDK 102 when the PDK 102 is within a proximity zone of the Reader 108. The proximity zone can be, for example, several meters in radius and can be adjusted dynamically by the Reader 108. Example embodiments of a Reader with a dynamically adjustable proximity zone are described in U.S. patent application Ser. No. 11/620,600, filed Jan. 5, 2007, entitled “Dynamic Cell Size Variation Via Wireless Link Parameter Adjustment”, the entire contents of which are incorporated herein by reference. Thus, in contrast to many conventional RF ID devices, the Reader 108 can detect and communicate with the PDK 102 without requiring the owner to remove the PDK 102 from his/her pocket, wallet, purse, etc. Also, in contrast to many conventional RFID devices, the Reader 108 and PDK 102 are designed to operate in a dense client environment—not on a one-by-one reader to client-held device basis. Example embodiments of a Reader that provides dense, coordinated system operation is described in U.S. patent application Ser. No. 11/620,581, filed Jan. 5, 2007, entitled “Wireless Network Synchronization Of Cells And Client Devices On A Network”, the entire contents of which are incorporated herein by reference. Generally, the Reader 108 receives uniquely identifying information from the PDK 102 and initiates an authentication process for the individual carrying the PDK 102. In one embodiment, the Reader 108 is adapted to receive a biometric input 104 from the individual. The biometric input 104 comprises a representation of physical or behavioral characteristics unique to the individual. For example, the biometric input 104 can include a fingerprint, a palm print, a retinal scan, an iris scan, a photograph, a signature, a voice sample or any other biometric information such as DNA, RNA or their derivatives that can uniquely identify the individual. The Reader 108 compares the biometric input 104 to information received from the PDK 102 to determine if a transaction should be authorized. Alternatively, the biometric input 104 can be obtained by a biometric reader on the PDK 102 and transmitted to the Reader 108 for authentication. In additional alternative embodiment, some or all of the authentication process can be performed by the PDK 102 instead of the Reader 108.

The Reader 108 is further communicatively coupled to the network 110 in order to receive and/or transmit information to remote databases for remote authentication. In an alternative embodiment, the Reader 108 includes a non-volatile data storage that can be synchronized with one or more remote databases 112 or registries 114-116. Such an embodiment relaxes the requirement for a continuous connection to the network 110 and allows the Reader 108 to operate in a standalone mode and for the local data storage to be updated when a connection is available. For example, a standalone Reader 108 can periodically download updated registry entries and perform authentication locally without any remote lookup.

The network 110 provides communication between the Reader 108 and the validation database 112, Central Registry 114 and one or more private registries 116. In alternative embodiments, one or more of these connections may not be present or different or additional network connections may be present. In one embodiment, the network 110 uses standard communications technologies and/or protocols. Thus, the network 110 can include links using technologies such as Ethernet, 802.11, 802.16, integrated services digital network (ISDN), digital subscriber line (DSL), asynchronous transfer mode (ATM), etc. Similarly, the networking protocols used on the network 110 can include the transmission control protocol/Internet protocol (TCP/IP), the hypertext transport protocol (HTTP), the simple mail transfer protocol (SMTP), the file transfer protocol (FTP), etc. The data exchanged over the network 110 can be represented using technologies and/or formats including the hypertext markup language (HTML), the extensible markup language (XML), etc. In addition, all or some of links can be encrypted using conventional encryption technologies such as the secure sockets layer (SSL), Secure HTTP and/or virtual private networks (VPNs). In another embodiment, the entities can use custom and/or dedicated data communications technologies instead of, or in addition to, the ones described above.

The validation database 112 stores additional information that may be used for authorizing a transaction to be processed at the Reader 108. For example, in purchase transactions, the validation database 112 is a credit card validation database that is separate from the merchant providing the sale. Alternatively, a different database may be used to validate different types of purchasing means such as a debit card, ATM card or bank account number.

The registries 114-116 are securely-accessible databases coupled to the network 110 that store, among other items, PDK, Notary, and Reader information. In one embodiment, the registries 114-116 do not store biometric information. Information stored in the registries can be accessed by the Reader 108 via the network 110 for use in the authentication process. There are two basic types of registries illustrated: private registries 116 and the Central Registry 114. Private registries 116 are generally established and administered by their controlling entities (e.g., a merchant, business authority, or other entity administering authentication). Private registries 116 can be custom configured to meet the specialized and independent needs of each controlling entity. The Central Registry 114 is a single highly-secured, centrally-located database administered by a trusted third-party organization. In one embodiment, all PDKs 102 are registered with the Central Registry 114 and may be optionally registered with one or more selected private registries 116. In alternative embodiments, a different number or different types of registries may be coupled to the network 110.

Turning now to FIG. 2, an example embodiment of a PDK 102 is illustrated. The PDK 102 comprises a memory 210, a programmer I/O 240, control logic 250, and a transceiver 260, coupled by a bus 270. The PDK 102 can be standalone as a portable, physical device or can be integrated into commonly carried items. For example, a PDK 102 can be integrated into a portable electronic device such as a cell phone, Personal Digital Assistant (PDA), or GPS unit, an employee identification tag, or jewelry items such as watches, rings, necklaces or bracelets.

The memory 210 can be a read-only memory, a once-programmable memory, a read/write memory or any combination of memory types including physical access secured and tamperproof memories. The memory 210 typically stores a unique PDK ID 212 and one or more profiles 220. The PDK ID 212 comprises a public section and a private section of information, each of which can be used for identification and authentication. In one embodiment, the PDK ID 212 is stored in a read-only format that cannot be changed subsequent to manufacture. The PDK ID 212 is used as an identifying feature of a PDK 102 and distinguishes between PDKs 102 in private 116 or Central 114 registry entries. The PDK ID 212 can also be used in basic PDK authentication to ensure that the PDK 102 is a valid device.

The profile fields 220 can be initially empty at the time of manufacture but can be written to by authorized individuals (e.g., a Notary) and/or hardware (e.g., a Programmer). In one embodiment, each profile 220 comprises a profile history 222 and profile data 230. Many different types of profiles 220 are possible. A biometric profile, for example, includes profile data 230 representing physical and/or behavioral information that can uniquely identify the PDK owner. A PDK 102 can store multiple biometric profiles, each comprising a different type of biometric information. In one embodiment, the biometric profile 220 comprises biometric information transformed by a mathematical operation, algorithm, or hash that represents the complete biometric information (e.g., a complete fingerprint scan). In one embodiment, a mathematical hash is a “one-way” operation such that there is no practical way to re-compute or recover the complete biometric information from the biometric profile. This both reduces the amount of data to be stored and adds an additional layer of protection to the user's personal biometric information. In one embodiment, the PDK 102 also stores one or more biometric profile “samples” associated with each biometric profile. The biometric profile sample is a subset of the complete profile that can be used for quick comparisons of biometric data. In one embodiment, the profile samples can be transmitted over a public communication channel or transmitted with a reduced level of encryption while the full biometric profiles are only transmitted over secure channels. In the case of fingerprint authentication, for example, the biometric profile sample may represent only a small portion area of the full fingerprint image. In another embodiment, the fingerprint profile sample is data that describes an arc of one or more lines of the fingerprint. In yet another embodiment, the fingerprint profile sample can be data representing color information of the fingerprint.

In another embodiment, the stored profiles 220 include a PIN profile that stores one or more PINs or passwords associated with the PDK owner. Here, the number or password stored in the PIN profile can be compared against an input provided by the user at the point of transaction to authenticate the user. In one embodiment, a PIN profile sample is also stored with the PIN profile that comprises a subset of the full PIN. For example, a PIN profile sample can be only the first two numbers of the PIN that can be used to quickly compare the stored PIN profile to a PIN obtained at the point of transaction.

In yet another embodiment, the PDK 102 stores a picture profile that includes one or more pictures of the PDK owner. In a picture profile authentication, the picture stored in the PDK 102 is transmitted to a display at the point of transaction to allow an administrator (e.g., a clerk or security guard) to confirm or reject the identity of the individual requesting the transaction. In another embodiment, an image is captured of the individual at the point of transaction and compared to the picture profile by an automated image analysis means. Furthermore, picture profiles could be used along with other personal identification information, for example, in place of conventional passports or drivers licenses to authenticate the identity of an individual and allow for remote identification of individuals. For example, a police officer following a vehicle could obtain an image and identity of the driver while still maintaining a safe distance from the vehicle. In the hospitality industry, a host could greet a guest at the door of a hotel, casino or restaurant and easily recognize the guest by obtaining the guest's picture profile as he/she enters.

A registry or database profile typically stores information associating the user with a registry. The registry profile can be used to determine if the individual is associated with the controlling entity for that registry and if different types of transactions are authorized for the individual. A registry profile can further include additional user information for use with the registry. For example, a private registry profile associated with a particular merchant may include a credit card number that the user has selected as a default for that merchant. In one embodiment, a profile can further include spending limits that limits the amount of purchases a user can make with a particular vendor or using a particular profile.

A profile can further include personal identification information such as name, address, phone number, etc., bank information, credit/debit card information, or membership information. This information can be useful for certain types of transactions. For example, with purchases that require delivery, a PDK 102 can automatically transmit address information to the Reader 108 at the point of transaction. In one embodiment, a profile can store multiple addresses. At the point of transaction, the Reader 108 displays the address options and allows the user to select which address to use.

Generally, some types of profile information (e.g., a biometric profile) can only be acquired during a trusted initialization process that is administered by a trusted Notary. In one embodiment, other secure information such as credit card information is also stored to the PDK in the presence of a Notary. Alternatively, certain types of low-risk information can be added by the user without a Notary, such as, for example a change of address. In another embodiment, once an initial profile has been stored to the PDK 102, a user can add information to the PDK 102 using a Programmer without a Notary through self-authentication. For example, in one embodiment, a PDK 102 that has a stored biometric profile can be “unlocked” by providing a matching biometric input. Then, once unlocked, the user can add additional profiles, credit cards, personal information, etc. to the PDK 102. In another embodiment, the user can make copies of the PDK 102 or move profiles from one PDK 102 to another once the PDK 102 is unlocked.

The profile history 222 includes a programmer ID field 224, a Notary ID 226, and a site ID field 228. The profile history 222 relates to the specific hardware, Notary, and site used at the time the profile data was created and stored to the PDK. Typically each profile 220 stores its specific profile history 222 along with the profile data 230. The profile history 222 can be recalled for auditing purposes at a later time to ensure the credibility of the stored data. In one embodiment, transaction history can also be stored to the PDK memory 210. Here, the PDK 102 stores information associated with any transactions made with the PDK 102 such as the name of the merchant, the purchase amount, credit card used, etc.

The PDK 102 also includes a programmer I/O 240 that provides an interface to a trusted Programmer (not shown). The Programmer comprises trusted hardware that is used to program the memory 210 of the PDK 102. An example embodiment of a Programmer is described in U.S. patent application Ser. No. 11/744,832 (now Pat. No. 8,412,949), entitled “Personal Digital Key Initialization and Registration For Secure Transaction,” the entire contents of which are incorporated herein by reference. The programmer I/O 240 can be, for example, a USB interface, serial interface, parallel interface, or any other direct or wireless link for transferring information between the PDK 102 and the Programmer. When coupled to the Programmer, the programmer I/O 240 receives initialization data, registration data or other information to be stored in the memory 210.

The control logic 250 coordinates between functions of the PDK 102. In one embodiment, the control logic 250 facilitates the flow of information between the programmer I/O 240, transceiver 260 and memory 210. The control logic 250 can further process data received from the memories 210, programmer I/O 240 and transceiver 260. Note that the control logic 250 is merely a grouping of control functions in a central architecture, and in other embodiments, the control functions can be distributed between the different modules of the PDK 102. The operation of the control logic will be understood to those skilled in the art based on the description below corresponding to FIGS. 4-7D.

The transceiver 260 is a wireless transmitter and receiver for wirelessly communicating with a Reader 108 or other wireless device. The transceiver 260 can send and receive data as modulated electromagnetic signals. Moreover, the data can be encrypted by the transceiver 260 and transmitted over a secure link. Further, the transceiver 260 can actively send connection requests, or can passively detect connection requests from another wireless source. In one embodiment, the transceiver 260 is used in place of a separate programmer I/O 240 and is used to wirelessly communicate with the Programmer for programming. In one embodiment, the transceiver 260 is adapted to communicate over a range of up to around 5 meters.

Optionally, a PDK 102 can also include a built in biometric reader (not shown) to acquire a biometric input from the user. The biometric input can be used to unlock the PDK 102 for profile updates, or for various types of authentication. For example, in one embodiment, a biometric input is received by the PDK 102 and compared to stored biometric information. Then, if the user is authenticated, the PDK 102 can indicate to the Reader 108 that the user is authenticated and transmit additional information (e.g., a credit card number) needed to complete a transaction.

Turning now to FIG. 3, an example embodiment of a Reader 108 is illustrated. The embodiment includes one or more biometric readers 302, a receiver-decoder circuit (RDC) 304, a processor 306, a network interface 308, an I/O port 312 and optionally a credit card terminal I/O 310. In alternative embodiments, different or additional modules can be included in the Reader 108.

The RDC 304 provides the wireless interface to the PDK 102. Generally, the RDC 304 wirelessly receives data from the PDK 102 in an encrypted format and decodes the encrypted data for processing by the processor 306. An example embodiment of an RDC is described in U.S. patent application Ser. No. 11/292,330 entitled “Personal Digital Key And Receiver/Decoder Circuit System And Method”, the entire contents of which are incorporated herein by reference. Encrypting data transmitted between the PDK 102 and Reader 108 minimizes the possibility of eavesdropping or other fraudulent activity. In one embodiment, the RDC 304 is also configured to transmit and receive certain types of information in an unencrypted, or public, format.

The biometric reader 302 receives and processes the biometric input 104 from an individual at the point of transaction. In one embodiment, the biometric reader 302 is a fingerprint scanner. Here, the biometric reader 302 includes an image capture device adapted to capture the unique pattern of ridges and valleys in a fingerprint also known as minutiae. Other embodiments of biometric readers 302 include retinal scanners, iris scanners, facial scanner, palm scanners, DNA/RNA analyzers, signature analyzers, cameras, microphones, and voice analyzers. Furthermore, the Reader 108 can include multiple biometric readers 302 of different types. In one embodiment, the biometric reader 302 automatically computes mathematical representations or hashes of the scanned data that can be compared to the mathematically processed biometric profile information stored in the PDK 102.

The processor 306 can be any general-purpose processor for implementing a number of processing tasks. Generally, the processor 306 processes data received by the Reader 108 or data to be transmitted by the Reader 108. For example, a biometric input 104 received by the biometric reader 302 can be processed and compared to the biometric profile 220 received from the PDK 102 in order to determine if a transaction should be authorized. In different embodiments, processing tasks can be performed within each individual module or can be distributed between local processors and a central processor. The processor 306 further includes a working memory for use in various processes such as performing the method of FIGS. 4-7D.

The network interface 308 is a wired or wireless communication link between the Reader 108 and one or more external databases such as, for example, a validation database 112, the Central Registry 114 or a private registry 116. For example, in one type of authentication, information is received from the PDK 102 at the RDC 304, processed by the processor 306, and transmitted to an external database 112-116 through the network interface 308. The network interface 308 can also receive data sent through the network 110 for local processing by the Reader 108. In one embodiment, the network interface 308 provides a connection to a remote system administrator to configure the Reader 108 according to various control settings.

The I/O port 312 provides a general input and output interface to the Reader 108. The I/O port 312 may be coupled to any variety of input devices to receive inputs such as a numerical or alphabetic input from a keypad, control settings, menu selections, confirmations, and so on. Outputs can include, for example, status LEDs, an LCD, or other display that provides instructions, menus or control options to a user.

The credit card terminal I/O 310 optionally provides an interface to an existing credit card terminal 314. In embodiments including the credit card terminal I/O 310, the Reader 108 supplements existing hardware and acts in conjunction with a conventional credit card terminal 314. In an alternative embodiment, the functions of an external credit card terminal 314 are instead built into the Reader 108. Here, a Reader 108 can completely replace an existing credit card terminal 314.

In one embodiment, a Reader 108 is adapted to detect and prevent fraudulent use of PDKs that are lost, stolen, revoked, expired or otherwise invalid. For example, the Reader 108 can download lists of invalid PDKs 102 from a remote database and block these PDKs 102 from use with the Reader 108. Furthermore, in one embodiment, the Reader 108 can update the blocked list and/or send updates to remote registries 114-116 or remote Readers 108 upon detecting a fraudulently used PDK 102. For example, if a biometric input 104 is received by the Reader 108 that does not match the biometric profile received from the PDK 102, the Reader 108 can obtain the PDK ID 212 and add it to a list of blocked PDKs. In another embodiment, upon detecting fraudulent use, the Reader 108 can send a signal to the PDK 102 that instructs the PDK 102 to deactivate itself. The deactivation period can be, for example, a fixed period of time, or until the rightful owner requests re-activation of the PDK 102. In yet another embodiment, the Reader 108 can send a signal instructing the fraudulently obtained PDK 102 to send beacon signals indicating that the PDK 102 is a stolen device. Here, a stolen PDK 102 can be tracked, located and recovered by monitoring the beacon signals. In one embodiment, the Reader 108 stores biometric or other identifying information from an individual that attempts to fraudulently use a PDK 102 so that the individual's identity can be determined.

Generally, the Reader 108 is configured to implement at least one type of authentication prior to enabling a transaction. In many cases, multiple layers of authentication are used. A first layer of authentication, referred to herein as “device authentication”, begins any time a PDK 102 moves within range of a Reader 108. In device authentication, the Reader 108 and the PDK 102 each ensure that the other is valid based on the device characteristics, independent of any profiles stored in the PDK 102. In some configurations, when fast and simple authentication is desirable, only device authentication is required to initiate the transaction. For example, a Reader 108 may be configured to use only device authentication for low cost purchases under a predefined amount (e.g., $25). The configuration is also useful in other types of low risk transactions where speed is preferred over additional layers of authentication.

Other configurations of the Reader 108 require one or more additional layers of authentication, referred to herein as “profile authentication” based on one or more profiles stored in the PDK 102. Profile authentication can include, for example, a biometric authentication, a PIN authentication, a photo authentication, a registry authentication, etc. or any combination of the above authentication types. Profile authentications are useful when a more exhaustive authentication process is desired, for example, for high purchase transactions or for enabling access to classified assets.

FIG. 4 illustrates an example embodiment of a process for secure authentication of a transaction. When a PDK 102 comes within range of a Reader 108, communication is automatically established 402 between the RDC 304 of the Reader 108 and the PDK 102. In one embodiment, the RDC 304 continually transmits beacons that are detected by the PDK 102 when it enters a proximity zone of the Reader 108. In an alternative embodiment, the communication is instead initiated by the PDK 102 and acknowledged by the Reader 108. Generally, initial communication between the Reader 108 and the PDK 102 is not encrypted in order to provide faster and more power efficient communication.

In step 404, a device authentication is performed. Here, the Reader 108 establishes if the PDK 102 is a valid device and PDK 102 establishes if the Reader 108 is valid. Furthermore, device authentication determines if the PDK is capable of providing the type of authentication required by the Reader 108.

An example embodiment of a method for performing 404 device authentication is illustrated in FIG. 5. The RDC 304 receives and analyzes 502 information from the PDK 102; and the PDK 102 receives and analyzes 502 information received from the RDC 304. Generally, this initial information is transmitted over a public communication channel in an unencrypted format. Based on the received information, each device 102, 304 determines 504 if the other is valid. As will be apparent to one of ordinary skill in the art, a number of different protocols can be used for this type of authentication such as, for example, a challenge-response authentication or a challenge handshake authentication protocol (CHAP). If either of the devices 102, 304 is invalid 512, the process ends. If both the PDK 102 and the RDC 304 are determined by the other to be valid, the Reader 108 requests and receives 506 authentication type information from the PDK 102 indicating the different types of authentication the PDK 102 is capable of satisfying based on the types of profiles the PDK 102 stores. The available profile types in the PDK 102 are compared against the authentication types that can be used by the Reader 108. For example, a particular Reader 108 may be configured to perform only a fingerprint authentication and therefore any PDK without a fingerprint biometric profile cannot be used with the Reader 108. In one embodiment, the Reader 108 can allow more than one type of profile to be used. In another embodiment, the Reader 108 requires more than one type of profile for authentication, while in yet further embodiments no profile authentications are required. Next, the method determines 508 whether the PDK 102 has one or more profiles sufficient for authentication. If the PDK 102 does not have one or more profiles sufficient for authentication with the Reader 108, the devices 102, 304 are determined to be invalid 512 because they cannot be used with each other. If the PDK 102 does have one or more sufficient types of profiles, the devices are valid 510.

Turning back to FIG. 4, if either the PDK 102 or RDC 304 is not found valid during device authentication 404, the transaction is not authorized 418 and the process ends. If the devices are valid, the RDC 304 temporarily buffers 408 the received PDK information. It is noted that in one embodiment, steps 402-408 are automatically initiated each time a PDK 102 enters the proximity zone of the Reader 108. Thus, if multiple PDKs 102 enter the proximity zone, the Reader 108 automatically determines which PDKs 102 are valid and buffers the received information from each valid PDK 102.

The method next determines 410 whether profile authentication is required based on the configuration of the Reader 108, the type of transaction desired or by request of a merchant or other administrator. If the Reader 108 configuration does not require a profile authentication in addition to the PDK authentication, then the Reader 108 proceeds to complete the transaction for the PDK 102. If the Reader 108 does require profile authentication, the profile authentication is performed 412 as will be described below with references to FIGS. 6-7D. If a required profile is determined 414 to be valid, the Reader 108 completes 416 the transaction. Otherwise, the Reader 108 indicates that the transaction is not authorized 418. In one embodiment, completing 416 the transaction includes enabling access to secure physical or digital assets (e.g., unlocking a door, opening a vault, providing access to a secured hard drive, etc.). In another embodiment, completing 416 the transaction includes charging a credit card for a purchase. Alternatively, bank information, debit/check/ATM card information, coupon codes, or any other purchasing means information (typically stored in a profile memory field 232) can be transmitted by the PDK 102 in place of credit card information. In one embodiment, the PDK 102 is configured with multiple purchasing means and a default is configured for different types of transactions. In another embodiment, each credit card or other purchasing means is displayed to the customer by the Reader 108 and the customer is allowed to select which to use for the transaction.

Turning now to FIG. 6, an embodiment of a process for profile authentication is illustrated. In step 602, a secure communication channel is established between the RDC 304 and the PDK 102. Information sent and received over the secure channel is in an encrypted format that cannot be practically decoded, retransmitted, reused, or replayed to achieve valid responses by an eavesdropping device. The Reader 108 transmits 604 profile authentication requests to the PDK 102 requesting transmission of one or more stored profiles over the secure channel. At 608, the process determines whether a “trigger” is required for authentication. The requirement for a trigger depends on the configuration of the Reader 108, the specific type of transaction to be executed and the type of authentication requested.

In a first configuration, a trigger is required to continue the process because of the type of authentication being used. For example, in biometric authentication, the authentication process cannot continue until the Reader detects a biometric contact and receives biometric information. It is noted that biometric contact is not limited to physical contact and can be, for example, the touch of a finger to a fingerprint scanner, the positioning of a face in front of a facial or retinal scanner, the receipt of a signature, the detection of a voice, the receipt of a DNA sample, RNA sample, or derivatives or any other action that permits the Reader 108 to begin acquiring the biometric input 104. By supplying the biometric contact, the user indicates that the authentication and transaction process should proceed. For example, a PDK holder that wants to make a withdrawal from an Automated Teller Machine (ATM) equipped with a Reader 108 initiates the withdrawal by touching a finger to the Reader 108. The ATM then begins the transaction process for the withdrawal.

In a second configuration, some other user action is required as a trigger to proceed with the transaction even if the authentication process itself doesn't necessarily require any input. This can be used for many purchasing transactions to ensure that the purchase is not executed until intent to purchase is clear. For example, a Reader 108 at a gas station can be configured to trigger the transaction when a customer begins dispensing gas. At a supermarket, a Reader 108 can be configured to trigger the transaction when items are scanned at a checkout counter.

In a third configuration, no trigger is used and the Reader 108 automatically completes the remaining authentication/transaction with no explicit action by the user. This configuration is appropriate in situations where the mere presence of a PDK 102 within range of the Reader 108 is by itself a clear indication of the PDK owner's desire to complete a transaction. For example, a Reader 108 can be positioned inside the entrance to a venue hosting an event (e.g., a sporting event, a concert, or a movie). When a PDK owner walks through the entrance, the Reader 108 detects the PDK 102 within range, authenticates the user, and executes a transaction to purchase an electronic ticket for the event. In another embodiment, the electronic ticket can be purchased in advance, and the Reader 108 can confirm that the user is a ticket holder upon entering the venue. Other examples scenarios where this configuration is useful include boarding a transportation vehicle (e.g., a train, bus, airplane or boat), entering a hotel room, or accessing secure facilities or other assets. Thus, if no trigger is required, the process next performs 614 the requested profile authentication tests.

If a trigger is required, the Reader monitors 610 its inputs (e.g., a biometric reader, key pad, etc.) and checks for the detection 612 of a trigger. If the required trigger is detected, the process continues to perform 614 one or more profile authentication test. FIGS. 7A-7D illustrate various embodiments of profile authentication tests. According to different configurations of the Reader 108, one or more of the illustrated authentication processes may be used. Further, in some embodiments, one or more of the processes may be repeated (e.g., for different types of biometric inputs).

Referring first to FIG. 7A, it illustrates a process for biometric authentication. In biometric authentication, a Reader 108 compares a biometric profile stored in the PDK 102 to the biometric input 104 acquired by the biometric reader 302. Advantageously, the biometric input 104 is not persistently stored by the Reader 108, reducing the risk of theft or fraudulent use. If 702 biometric authentication is requested, the Reader 108 scans 704 the biometric input 104 supplied by the user. In one embodiment, scanning 704 includes computing a mathematical representation or hash of the biometric input 104 that can be directly compared to the biometric profile.

Furthermore, in one embodiment, scanning 704 also includes obtaining a biometric input sample from the biometric input according to the same function used to compute the biometric profile sample stored in the PDK 102. Optionally, the Reader 108 receives 708 a biometric profile sample from the PDK 102 and determines 710 if the biometric profile sample matches the biometric input sample. If the biometric profile sample does not match the input sample computed from the scan, the profile is determined to be invalid 718. If the biometric profile sample matches, the full biometric profile 712 is received from the PDK 102 to determine 714 if the full biometric profile 712 matches the complete biometric input 104. If the profile 712 matches the scan, the profile 712 is determined to be valid 720, otherwise the profile 712 is invalid 718. It is noted that in one embodiment, steps 708 and 710 are skipped and only a full comparison is performed.

It will be apparent to one of ordinary skill that in alternative embodiments, some of the steps in the biometric profile authentication process can be performed by the PDK 102 instead of the Reader 108 or by an external system coupled to the Reader 108. For example, in one embodiment, the biometric input 104 can be scanned 704 using a biometric reader built into the PDK 102. Furthermore, in one embodiment, the steps of computing the mathematical representation or hash of the biometric input and/or the steps of comparing the biometric input to the biometric profile can be performed by the PDK 102, by the Reader 108, by an external system coupled to the Reader 108, or by any combination of the devices. In one embodiment, at least some of the information is transmitted back and forth between the PDK 102 and the Reader 108 throughout the authentication process. For example, the biometric input 104 can be acquired by the PDK 102, and transmitted to the Reader 108, altered by the Reader 108, and sent back to the PDK 102 for comparison. Other variations of information exchange and processing are possible without departing from the scope of the invention. The transfer of data between the PDK 102 and the Reader 108 and/or sharing of processing can provide can further contribute to ensuring the legitimacy of each device.

FIG. 7B illustrates a process for PIN authentication. If PIN authentication is requested 724, a PIN is acquired 726 from the user through a keypad, mouse, touch screen or other input mechanism. Optionally, the Reader 108 receives 728 a PIN sample from the PDK 102 comprising a subset of data from the full PIN. For example, the PIN sample can comprise the first and last digits of the PIN. If the Reader 108 determines 730 that the PIN sample does not match the input, the profile is immediately determined to be invalid 736. If the PIN sample matches, the full PIN profile is received 732 from the PDK and compared to the input. If the Reader 108 determines 734 that the profile matches the input, the profile is determined to be valid and is otherwise invalid 736. It is noted that in one embodiment, steps 728 and 730 are skipped.

FIG. 7C illustrates a process for a picture authentication. If the Reader 108 determines 724 that picture authentication is requested, a picture profile is received 744 from the PDK 102 by the Reader 108 and displayed 746 on a screen. An administrator (e.g., a clerk, security guard, etc.) is prompted 748 to compare the displayed picture to the individual and confirms or denies if the identities match. If the administrator confirms that the identities match, the picture profile is determined to be valid 764 and is otherwise invalid 752. In an alternative embodiment, the process is automated and the administrator input is replaced with a process similar to that described above with reference to FIG. 7A. Here, an image of the user is captured and face recognition is performed by comparing picture profile information received from the PDK 102 to the captured image.

FIG. 7D illustrates a process for authentication with a private registry 114 or the Central Registry 116. If the Reader 108 determines that registry authentication is requested, a secure communication channel is established 762 over the network 110 between the Reader 108 and one or more registries (e.g., the Central Registry 114, any private registry 116, or other validation database 112). If any additional information is needed to process the registry authentication (e.g., a credit card number), the Reader 108 requests and receives the additional information from the PDK 102. Identification information is transmitted 764 from the Reader 108 to the registry 114-116 through the network interface 308. The PDK status is received 766 from the registry to determine 768 if the status is valid 772 or invalid 770. In one embodiment, the information is processed remotely at the registry 114-116 and the registry 114-116 returns a validation decision to the Reader 108. In another embodiment, the Reader 108 queries the private 116 or Central registry 114 for information that is returned to the Reader 108. The information is then analyzed by the Reader 108 and the authorization decision is made locally. In one embodiment, the process involves transmitting credit card (or other purchasing information) to a validation database 112 to authorize the purchase and receive the status of the card. Status information may include, for example, confirmation that the card is active and not reported lost or stolen and that sufficient funds are present to execute the purchase.

Referring now to FIGS. 8-10, additional embodiments of the present invention are described to show a method for single step transaction authentication. In particular, the present invention can be used to initiate and process transactions based on a single step, namely the inputting or receiving of a biometric input. This is particularly advantageous because of the ease of use for the end user. To authorize any type of purchase, the user need only perform the simplest of steps and allow his biometric data to be scanned. For ease of understanding and convenience, these embodiments of the present invention will now be described in a context where the biometric input is a finger print scan. However, it should be understood that this method can alternatively use any type of biometric characteristic including but not limited to fingerprint, retinal, iris, face, palm, DNA, RNA, or their derivatives used to establish identity, voice or signature characteristics that can each be uniquely associated with the individual. It should be noted the present invention is also advantageous because it provides multiple levels of authentication. While only requiring the user to scan their finger, the present invention provides multiple levels of authentication because of the employment of the PDK. The PDK allows the method to provide authentication of the PDK, and authentication of the biometric input responsive to receiving the finger print scan before authorizing or completing the transaction. Additionally for ease of understanding and convenience, these embodiments of the present invention will now be described in a context making a purchase of goods such as at any store.

Referring now to FIG. 8, one embodiment of a basic method for single step transaction authentication will be described. In this embodiment, only biometric input and wireless communication with the PDK 102 that stores a biometric reference is required. As has been noted above, this method is advantageous because the user need only place his finger on a scanner and the transaction is authorized and completed in a very secure manner. The method begins by receiving 802 biometric input. In this embodiment, the input of biometric data is also used as a trigger to begin the transaction. For example, the user need only place his finger on the biometric reader 302 of Reader 108, and a finger print scan is captured. In an alternate embodiment where the PDK 102 includes a biometric reader, the user simply places his finger on the reader built into the PDK 102 and the biometric input is captured. In this embodiment, the PDK 102 does the biometric comparison or the biometric input can be transmitted to the Reader 108 for processing. Next, the Reader 108 receives 804 biometric data from the PDK 102. As has been described above with reference to FIGS. 4-6 this communication process between the PDK 102 and the Reader 108 can take a variety of different formats, be done with a partially or completely secure communication channel, and include multiple levels of security. It should be understood that another advantageous feature of the claimed method is that the PDK 102 and the Reader 108 communicate wirelessly, and that the Reader 108 automatically detects when the PDK 102 is in proximity. Moreover, the operational frequency and power for communication between the PDK 102 and the Reader 108 are such that the user does not need to remove the PDK 102 from its location on his person. The PDK 102 can remain in the user's pocket, wallet, purse or other location, and does not need to be removed for communication with the Reader 108. Thus, the user literally need only have their finger print scanned to initiate and complete the transaction. The data transmitted from the PDK 102 to the Reader 108 for this embodiment requires biometric data for verification of the biometric input. Additional information can be transmitted by the PDK 102 as will be described in detail below with reference to FIG. 2.

Once the data from the PDK 102 has been received, the method compares 806 the biometric input received in 802 with the biometric data or profile received from the PDK 102 in 804. Then the method determines 808 whether the biometric input matches the biometric reference or profile. If not, the method rejects 810 the transaction and it is not approved. If, however, the biometric data matches the biometric input, the transaction is authorized 812 and completed. For example, the Reader 108 can complete the transaction by sending credit card and other information to a conventional credit card processing center to have the transaction approved by the credit card company. In this embodiment to minimize communication with the PDK 102 may be saved on a network accessible by the Reader 108. Similarly, the Reader 108 may initiate and process other level of security and authentication on the PDK data or profile provide according to the requirement or specification of any particular transaction.

Referring now to FIG. 9, a second embodiment 900 for single step authentication of a transaction using proximity, biometric input and PDK authentication will be described. The second embodiment 900 of the method uses many of the same processes that have been described above for the first embodiment 800. Therefore, for ease understanding and convenience like processes are labeled with like references numerals and their detailed description will not be repeated here. Rather, the differences between the second embodiment 900 and the first embodiment 800 of the method of the present invention will be described. It should be noted that the second embodiment 900 is similar to the first 800, however it provides an additional level of authentication by receiving additional information from the PDK 102 and validating the PDK 102. FIG. 9 also illustrates how the validation of the PDK 102 may occur before the biometric input thereby reducing the time the user must wait for the transaction to be authorized and completed. This is particularly important for live transaction processing such as when used by a cashier at any store. The process begins by receiving data 804 from the PDK 102. This process first automatically secures a communication link between the PDK 102 and the Reader 108 when the two devices are within a predefined proximity of each other. In this embodiment 900, receiving data 804 from the PDK 102 includes the biometric data as described above, but also includes PDK data that is required by the Reader to authenticate the PDK 102. For example, the PDK data may include a PDK identification number, a profile history and a data profile having security information according to the level of security required for authentication like profile authentication and profile testing described above. For most financial transactions, the data transmitted from the PDK 102 to the Reader 108 will also include credit card information and other security information for the transaction. Next, the method uses this received information to validate 902 the PDK. The data that was received wirelessly from the PDK 102 along with other information and algorithms in the Reader 108 are used to authenticate the PDK 102 as a valid one. This step may also include validating the RDC 304 of the Reader 108 as a valid RDC 304 as has been described above. While the PDK authentication has been described above as occurring before the biometric input, those skilled in the art will recognize that these steps could occur prior to or contemporaneously with the biometric input 802. Then method continues as has been described above by comparing 806 the biometric input received in 802 with the biometric profile received from the PDK 102 in 804, determining 808 whether the biometric input matches the biometric reference or profile, and either rejecting 810 the transaction or authorizing 812 and completing the transaction. In this embodiment, the Reader 108 can complete the transaction by sending credit card and other information to a conventional credit card processing center to have the transaction approved by the credit card company since the PDK wirelessly communicated this information to the Reader 108 in step 804. Similarly, the Reader 108 may initiate and process other level of security and authentication on the PDK data or profile provide according to the requirement or specification of any particular transaction. The reader can validate the parties and the transaction against third party system as has been described above. This second embodiment is illustrative of 1) two levels of authentication—biometric and PDK, 2) the independence of the order in which the biometric authentication and the PDK authentication occur; 3) the same minimal step required of the user for biometric input, for example, scanning the user's finger.

Referring now to FIG. 10, a third embodiment 1000 of a process for single step authentication of a transaction using proximity and biometric input. The third embodiment 1000 provides more detail of on a specific implementation. The third embodiment also illustrates more directly the specific device or entity performing the steps of this embodiment of the present invention. FIG. 10 is divided into four vertical sections with each section depicting portions of the process that are performed by that device or entity. The first and left most section shows the steps performed by the user, the second section and the next to the right show the steps performed by the PDK 102, the third section shows the steps performed by the Reader 108 and the right most section show the steps performed by a third party system such as the validation database 112, the central registry 114, a private registry 116 or the system of a credit card company. As is readily apparent from FIG. 10, the method of the present invention requires minimal but sufficient involvement from the user, namely the positioning of the user's body for biometric reading. This advantageously requires the user do almost nothing to approve a highly secure transaction, yet obtains user consent by capturing biometric information sufficient to ensure that the user is authorizing and agreeing to the transaction.

The process begins with the Reader 108 sending out a beacon signal to start the proximity authentication process. The beacon signal is preferably repeatedly sent such as at a periodic interval. The PDK 102 monitors 1002 for a beacon signal from any Reader 108 in range. If there is no such signal then the PDK 102 is outside the proximity range of any Reader 108. Once the PDK 102 detects a beacon, the PDK 102 responds by sending information to set up a secure communication channel. This process has been described above with reference to FIGS. 4-7. Any of the embodiments disclosed above may be used here. Once the secure communication channel has been established, the PDK 102 sends 1006 PDK data and biometric data to the Reader 108, in particular, the RDC 308. Then the Reader 108 receives 1008 the PDK data and biometric data, and temporarily store the data in working memory of the Reader 108. The Reader 108 then authenticates the PDK 102 using the PDK data. For example, the PDK data may include a profile 220. The Reader 108 validates the PDK 102 according to Reader's requirements and the requirements specified in the profile 200. This may be any number of types or combinations of authentication as has been described above with reference to FIGS. 6 and 7. In one alternate embodiment shown in FIG. 10 with dashed lines, the Reader 108 may communicate with a third party system such as a registry 112, 114, 116 to validate 1012 the PKD 102 and/or the Reader 108. After either step 1010 or 1012, the method continues with the user positioning 1014 his body for a biometric read. In one embodiment, this is swiping his finger over a reader. For the other type of biometric scanning, the user need only perform the affirmative act of allowing his body to be scanned such as for a retinal, face, palm, DNA analysis etc. Once the user has performed then inputting step 1014, the Reader 108 receives 1016 the biometric input. In this embodiment, the biometric reader 302 is part of Reader 108 so receipt is automatic. However, where the biometric reader is on the PDK 102, the PDK 102 wirelessly transmits the biometric input to the Reader 108 that in turn receives it. Next, the Reader 108 compares the biometric input from step 1016 to the biometric data from step 1008. If they do not match the process is complete and the transaction is rejected. If the biometric input matches the biometric data, the method initiates a transaction 1020 and communicates with a third party system to authorize and approve 1022 the transaction in the third party system. For example, this may be initiating the transaction by sending credit card information, associated credit card security information, information about the parties and the transaction to the credit card company. The credit card company then authorizes and approves 1022 the transaction in their system. A credit card company is used only by way of example, and the third party system could be a bank, any other financial institution, an electronic payment system such as PayPal®, immigration office, security administrator, or other like third party systems. Moreover, the Reader 108 could be a conventional computer with a transceiver and with access to the internet and third party system via secure connections. Once the transaction has been approved or denied by the third party system, the status is send back to the Reader 108 and presented 1024 to the user. Thus, from FIG. 10 and the above associated description it should be apparent how the present invention provides a very easy to used system 1000 that allow the user to engage in very secure transactions with multiple levels of security while only requiring a simple biometric input.

It should be noted that the biometric authentication described above is performed without the requirement of an external database containing biometric data to be searched. The security of maintaining all biometric data to be searched within the user-owned and carried PDK is apparent, as is the vastly improved speed in searching only those immediately surrounding PDK's for a match. Additionally, it will be noticed that in order to complete the transaction, the person possessing the PDK containing the secure data must provide the Reader 108 with a scan (or sample) of biologically identifying material. The importance of the foregoing to the tracking and apprehension of anyone fraudulently attempting to use another person's PDK will be understood by those skilled in the art, as well as extensions of this technology to act as an aid in law enforcement in the detection, tracking and retrieval of lost, stolen or fraudulently obtained PDK's.

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.

Claims

1. A method for electronic transaction processing comprising: after a first personal digital key device has entered a proximity zone of a reader device, wirelessly receiving, at the reader device, from the first personal digital key device a first biometric sample associated with a valid user of the first personal digital key device, the first personal digital key device storing a biometric profile, the first biometric sample being a subset of the biometric profile;automatically capturing, at the reader device, a biometric input of a user at a point of a transaction without user intervention;comparing, at the reader device, the biometric input with a plurality of biometric samples received from a plurality of personal digital key devices within the proximity zone, the plurality of biometric samples wireles sly received from the plurality of personal digital key devices within the proximity zone including the first biometric sample wireles sly received from the first personal digital key device after the first personal digital key device entered the proximity zone;identifying, at the reader device, a match between the biometric input and the first biometric sample based on the comparison of the biometric input with the plurality of biometric samples received from the plurality of personal digital key devices within the proximity zone; andresponsive to the identification of the match between the biometric input and the first biometric sample, associating the first personal digital key device with the transaction, determining that the biometric input matches the biometric profile associated with the valid user of the first personal digital key device, and initiating, at the reader device, the transaction using the first personal digital key device.
2. The method of claim 1, wherein automatically receiving capturing the biometric input includes performing at least one of a retinal scan, an iris scan, and a facial scan.
3. The method of claim 1, wherein the reader device temporarily stores the biometric input.
4. The method of claim 1, further comprising: authenticating the first personal digital key device after the first personal digital key device has entered a readable coverage area.
5. The method of claim 4, further comprising: authorizing the transaction responsive to authenticating the first personal digital key device and determining that the biometric input matches the biometric profile associated with the valid user of the first personal digital key device.
6. The method of claim 4, wherein authenticating the first personal digital key device begins before identifying the match and identifying the match is performed before authenticating the first personal digital key device.
7. The method of claim 4, wherein authenticating the first personal digital key device includes receiving data from the first personal digital key device and comparing it against data from an external system.
8. The method of claim 4, wherein the proximity zone and the readable coverage area are associated with a reader device and the reader device receives the biometric input, authenticates the first personal digital key device, and identifies the match between the biometric input and the biometric profile.
9. The method of claim 1, wherein the first personal digital key device determines that the biometric input of the user matches the biometric profile associated with the valid user of the first personal digital key device.
10. The method of claim 1, further comprising: obtaining, responsive to the biometric input matching the first biometric sample from the first personal digital key device and determining that the first personal digital key device is associated with the transaction, the biometric profile associated with the valid user of the first personal digital key device from the first personal digital key device.
11. The method of claim 1, wherein the biometric input received is a calculated representation of one or more of a physical and a behavioral characteristic based on input received by a biometric sensor.
12. The method of claim 1, wherein authorizing the transaction comprises: communicating with another system to authorize and approve the transaction; andpresenting a status for the transaction.
13. The method of claim 1, further comprising the steps of: receiving a picture profile from the first personal digital key device, the picture profile including a picture associated with the valid user of the first personal digital key device; anddisplaying the picture profile associated with the valid user of the first personal digital key device to an administrator.
14. The method of claim 1, further comprising: using at least one of financial information, credit card information and personal identification information received from the first personal digital key device to complete the transaction, the transaction being a financial transaction, the first personal digital key device including the at least one of the financial information, the credit card information, and the personal identification information.
15. A system comprising: one or more processors; and
16. The system of claim 15, wherein the user provides the biometric input and the transaction is authorized without further action by the user.
17. The system of claim 15, wherein the instructions further cause the one or more processors to use at least one of financial information, credit card information and personal identification information received from the first personal digital key device to complete the transaction, the transaction being a financial transaction, the first personal digital key device including the at least one of the financial information, the credit card information, and the personal identification information.
18. The system of claim 15, wherein the instructions further cause the one or more processors to: authenticate the first personal digital key device after the first personal digital key device has entered a readable coverage area including comparing a first personal digital key device identifier associated with the first personal digital key device against data from an external system, the external system including one or more of a central registry, a validation database, and a private registry.
19. The system of claim 16, wherein the biometric input received is a calculated representation of one or more of a physical and a behavioral characteristic based on input received by a biometric sensor.
20. A computer program product comprising a non-transitory computer usable medium including a computer readable program, wherein the computer readable program when executed on a computing device causes the computing device to: after a first personal digital key device has entered a proximity zone of a reader device, wireles sly receive, at the reader device, from the first personal digital key device a first biometric sample associated with a valid user of the first personal digital key device, the first personal digital key device storing a biometric profile, the first biometric sample being a subset of the biometric profile;automatically capture, at the reader device, a biometric input of a user at a point of a transaction without user intervention;comparing, at the reader device, the biometric input with a plurality of biometric samples received from a plurality of personal digital key devices within the proximity zone, the plurality of biometric samples wireles sly received from the plurality of personal digital key devices within the proximity zone including the first biometric sample wireles sly received from the first personal digital key device after the first personal digital key device entered the proximity zone;identify, at the reader device, a match between the biometric input and the first biometric sample based on the comparison of the biometric input with the plurality of biometric samples received from the plurality of personal digital key devices within the proximity zone; andresponsive to the identification of the match between the biometric input and the first biometric sample, associating the first personal digital key device with the transaction, determining that the biometric input matches the biometric profile associated with the valid user of the first personal digital key device, and initiating, at the reader device, the transaction using the first personal digital key device.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of and claims priority to U.S. application Ser. No. 11/745,249, filed May 7, 2007, titled “Single Step Transaction Authentication Using Proximity and Biometric Input,” which claims the benefit of U.S. Provisional Application No. 60/798,172 entitled “Touch Pay” filed on May 5, 2006; U.S. Provisional Application No. 60/798,843 entitled “Touch Pay” filed on May 8, 2006; U.S. Provisional Application No. 60/838,788 entitled “Personal Digital Key Accessible Storage Device and Processor” filed on Aug. 17, 2006; U.S. Provisional Application No. 60/824,758 entitled “Truprox Touch Technology” filed on Sep. 6, 2006; and U.S. Provisional Application No. 60/894,608 entitled “TruProx Stored-Photo Extension” filed on Mar. 13, 2007, the entire contents of which are all herein incorporated by reference. Applicants hereby notify the USPTO that the claims of the present application are different from those of the parent application (U.S. patent application Ser. No. 11/745,249) and any other related applications. Therefore, Applicants rescind any disclaimer of claim scope made in the parent application or any other predecessor application in relation to the present application. The Examiner is therefore advised that any such disclaimer and the cited reference that it was made to avoid may need to be revisited at this time. Furthermore, the Examiner is also reminded that any disclaimer made in the present application should not be read into or against the parent application, the grandparent application or any other related application.

US Referenced Citations (1123)

Number	Name	Date	Kind
3665313	Trent	May 1972	A
3739329	Lester	Jun 1973	A
3761883	Alvarez et al.	Sep 1973	A
3906166	Cooper et al.	Sep 1975	A
4101873	Anderson et al.	Jul 1978	A
4430705	Cannavino et al.	Feb 1984	A
4476469	Lander	Oct 1984	A
4598272	Cox	Jul 1986	A
4661821	Smith	Apr 1987	A
4759060	Hayashi et al.	Jul 1988	A
4814742	Morita et al.	Mar 1989	A
4871997	Adriaenssens et al.	Oct 1989	A
4993068	Piosenka et al.	Feb 1991	A
5043702	Kuo	Aug 1991	A
5052049	Andros et al.	Sep 1991	A
5187352	Blair et al.	Feb 1993	A
5224164	Elsner	Jun 1993	A
5296641	Stelzel	Mar 1994	A
5307349	Shloss et al.	Apr 1994	A
5317572	Satoh	May 1994	A
5325285	Araki	Jun 1994	A
5392287	Tiedemann et al.	Feb 1995	A
5392433	Hammersley et al.	Feb 1995	A
5410588	Ito	Apr 1995	A
5416780	Patel	May 1995	A
5422632	Bucholtz et al.	Jun 1995	A
5428684	Akiyama et al.	Jun 1995	A
5450489	Ostrover et al.	Sep 1995	A
5473690	Grimonprez et al.	Dec 1995	A
5481265	Russell	Jan 1996	A
5506863	Meidan et al.	Apr 1996	A
5517502	Bestler et al.	May 1996	A
5541583	Mandelbaum	Jul 1996	A
5544321	Theimer et al.	Aug 1996	A
5552776	Wade et al.	Sep 1996	A
5563947	Kikinis	Oct 1996	A
5589838	Mcewan	Dec 1996	A
5594227	Deo	Jan 1997	A
5598474	Johnson	Jan 1997	A
5611050	Theimer et al.	Mar 1997	A
5615277	Hoffman	Mar 1997	A
5619251	Kuroiwa et al.	Apr 1997	A
5623552	Lane	Apr 1997	A
5629980	Stefik et al.	May 1997	A
5644354	Thompson et al.	Jul 1997	A
5666412	Handelman et al.	Sep 1997	A
5689529	Johnson	Nov 1997	A
5692049	Johnson et al.	Nov 1997	A
5719387	Fujioka	Feb 1998	A
5729237	Webb	Mar 1998	A
5760705	Glessner et al.	Jun 1998	A
5760744	Sauer	Jun 1998	A
5773954	Vanhorn	Jun 1998	A
5784464	Akiyama et al.	Jul 1998	A
5799085	Shona	Aug 1998	A
5821854	Dorinski et al.	Oct 1998	A
5825876	Peterson, Jr.	Oct 1998	A
5835595	Fraser et al.	Nov 1998	A
5838306	O'Connor et al.	Nov 1998	A
5854891	Postlewaite et al.	Dec 1998	A
5857020	Peterson, Jr.	Jan 1999	A
5886634	Muhme	Mar 1999	A
5892825	Mages et al.	Apr 1999	A
5892900	Ginter et al.	Apr 1999	A
5894551	Huggins et al.	Apr 1999	A
5898880	Ryu	Apr 1999	A
5910776	Black	Jun 1999	A
5917913	Wang	Jun 1999	A
5923757	Hocker et al.	Jul 1999	A
5928327	Wang et al.	Jul 1999	A
5942985	Chin	Aug 1999	A
5991399	Graunke et al.	Nov 1999	A
5991749	Morril, Jr.	Nov 1999	A
6016476	Maes et al.	Jan 2000	A
6018739	McCoy	Jan 2000	A
6025780	Bowers	Feb 2000	A
6035038	Campinos et al.	Mar 2000	A
6035329	Mages et al.	Mar 2000	A
6038334	Hamid	Mar 2000	A
6038666	Hsu	Mar 2000	A
6040786	Fujioka	Mar 2000	A
6041410	Hsu et al.	Mar 2000	A
6042006	Van Tilburg et al.	Mar 2000	A
6045039	Stinson	Apr 2000	A
6055314	Spies et al.	Apr 2000	A
6068184	Barnett	May 2000	A
6069647	Sullivan	May 2000	A
6070796	Sirbu	Jun 2000	A
6076164	Tanaka et al.	Jun 2000	A
6088450	Davis et al.	Jul 2000	A
6088730	Kato et al.	Jul 2000	A
6104290	Naguleswaran	Aug 2000	A
6104334	Allport	Aug 2000	A
6110041	Walker et al.	Aug 2000	A
6121544	Petsinger	Sep 2000	A
6134283	Sands et al.	Oct 2000	A
6137480	Shintani	Oct 2000	A
6138010	Rabe et al.	Oct 2000	A
6148142	Anderson	Nov 2000	A
6148210	Elwin et al.	Nov 2000	A
6161179	Seidel	Dec 2000	A
6175921	Rosen	Jan 2001	B1
6177887	Jerome	Jan 2001	B1
6185316	Buffam	Feb 2001	B1
6189105	Lopes	Feb 2001	B1
6209089	Selitrennikoff	Mar 2001	B1
6219109	Raynesford	Apr 2001	B1
6219439	Burger	Apr 2001	B1
6219553	Panasik	Apr 2001	B1
6237848	Everett	May 2001	B1
6240076	Kanerva et al.	May 2001	B1
6247130	Fritsch	Jun 2001	B1
6249869	Drupsteen et al.	Jun 2001	B1
6256737	Bianco	Jul 2001	B1
6266415	Campinos	Jul 2001	B1
6270011	Gottfried	Aug 2001	B1
6279111	Jensenworth et al.	Aug 2001	B1
6279146	Evans et al.	Aug 2001	B1
6295057	Rosin	Sep 2001	B1
6307471	Xydis	Oct 2001	B1
6325285	Baratelli	Dec 2001	B1
6336121	Lyson	Jan 2002	B1
6336142	Kato et al.	Jan 2002	B1
6343280	Clark	Jan 2002	B2
6345347	Biran	Feb 2002	B1
6363485	Adams et al.	Mar 2002	B1
6367019	Ansell et al.	Apr 2002	B1
6369693	Gibson	Apr 2002	B1
6370376	Sheath	Apr 2002	B1
6381029	Tipirneni	Apr 2002	B1
6381747	Wonfor et al.	Apr 2002	B1
6385596	Wiser et al.	May 2002	B1
6392664	White et al.	May 2002	B1
6397387	Rosin et al.	May 2002	B1
6401059	Shen et al.	Jun 2002	B1
6411307	Rosin et al.	Jun 2002	B1
6424249	Houvener	Jul 2002	B1
6424715	Saito	Jul 2002	B1
6425084	Rallis et al.	Jul 2002	B1
6434403	Ausems et al.	Aug 2002	B1
6434535	Kupka et al.	Aug 2002	B1
6446004	Cao et al.	Sep 2002	B1
6446130	Grapes	Sep 2002	B1
6463534	Geiger et al.	Oct 2002	B1
6480101	Kelly et al.	Nov 2002	B1
6480188	Horsley	Nov 2002	B1
6484182	Dunphy	Nov 2002	B1
6484260	Scott et al.	Nov 2002	B1
6484946	Matsumoto et al.	Nov 2002	B2
6487663	Jaisimha et al.	Nov 2002	B1
6490443	Freeny, Jr.	Dec 2002	B1
6510350	Steen, III et al.	Jan 2003	B1
6522253	Saltus	Feb 2003	B1
6523113	Wehrenberg	Feb 2003	B1
6529949	Getsin et al.	Mar 2003	B1
6546418	Schena et al.	Apr 2003	B2
6550011	Sims, III	Apr 2003	B1
6563465	Frecska	May 2003	B2
6563805	Ma et al.	May 2003	B1
6564380	Murphy	May 2003	B1
6577238	Whitesmith et al.	Jun 2003	B1
6593887	Luk et al.	Jul 2003	B2
6597680	Lindskog et al.	Jul 2003	B1
6607136	Atsmon et al.	Aug 2003	B1
6624752	Klitsgaard et al.	Sep 2003	B2
6628302	White et al.	Sep 2003	B2
6632992	Hasegawa	Oct 2003	B2
6633981	Davis	Oct 2003	B1
6645077	Rowe	Nov 2003	B2
6647417	Hunter et al.	Nov 2003	B1
6657538	Ritter	Dec 2003	B1
6658566	Hazard	Dec 2003	B1
6667684	Waggamon et al.	Dec 2003	B1
6669096	Saphar et al.	Dec 2003	B1
6671808	Abbott et al.	Dec 2003	B1
6683954	Searle	Jan 2004	B1
6697944	Jones et al.	Feb 2004	B1
6709333	Bradford et al.	Mar 2004	B1
6711464	Yap et al.	Mar 2004	B1
6714168	Berenbaum	Mar 2004	B2
6715246	Frecska et al.	Apr 2004	B1
6728397	McNeal	Apr 2004	B2
6737955	Ghabra et al.	May 2004	B2
6758394	Maskatiya et al.	Jul 2004	B2
6771969	Chinoy et al.	Aug 2004	B1
6775655	Peinado et al.	Aug 2004	B1
6785474	Hirt	Aug 2004	B2
6788640	Celeste	Sep 2004	B2
6788924	Knutson et al.	Sep 2004	B1
6795425	Raith	Sep 2004	B1
6804825	White et al.	Oct 2004	B1
6806887	Chernock et al.	Oct 2004	B2
6819219	Bolle	Nov 2004	B1
6839542	Sibecas et al.	Jan 2005	B2
6850147	Prokoski	Feb 2005	B2
6853988	Dickinson	Feb 2005	B1
6859812	Poynor	Feb 2005	B1
6861980	Rowitch et al.	Mar 2005	B1
6873975	Hatakeyama et al.	Mar 2005	B1
6879567	Callaway et al.	Apr 2005	B2
6879966	Lapsley	Apr 2005	B1
6886741	Salveson	May 2005	B1
6889067	Willey	May 2005	B2
6891822	Gubbi et al.	May 2005	B1
6892307	Wood et al.	May 2005	B1
6930643	Byrne et al.	Aug 2005	B2
6947003	Huor	Sep 2005	B2
6950941	Lee et al.	Sep 2005	B1
6957086	Bahl et al.	Oct 2005	B2
6961858	Fransdonk	Nov 2005	B2
6963270	Gallagher et al.	Nov 2005	B1
6963971	Bush	Nov 2005	B1
6973576	Giobbi	Dec 2005	B2
6975202	Rodriguez et al.	Dec 2005	B1
6980087	Zukowski	Dec 2005	B2
6983882	Cassone	Jan 2006	B2
6999032	Pakray et al.	Feb 2006	B2
7012503	Nielsen	Mar 2006	B2
7020635	Hamilton	Mar 2006	B2
7031945	Donner	Apr 2006	B1
7049963	Waterhouse et al.	May 2006	B2
7055171	Martin et al.	May 2006	B1
7058806	Smeets et al.	Jun 2006	B2
7061380	Orlando et al.	Jun 2006	B1
7068623	Barany et al.	Jun 2006	B1
7072900	Sweitzer et al.	Jul 2006	B2
7079079	Jo et al.	Jul 2006	B2
7080049	Truitt	Jul 2006	B2
7082415	Robinson	Jul 2006	B1
7090126	Kelly et al.	Aug 2006	B2
7090128	Farley	Aug 2006	B2
7100053	Brown et al.	Aug 2006	B1
7107455	Merkin	Sep 2006	B1
7111789	Rajasekaran et al.	Sep 2006	B2
7112138	Hedrick et al.	Sep 2006	B2
7119659	Bonalle et al.	Oct 2006	B2
7123149	Nowak et al.	Oct 2006	B2
7130668	Chang et al.	Oct 2006	B2
7131139	Meier	Oct 2006	B1
7137008	Hamid	Nov 2006	B1
7137012	Kamibayashi et al.	Nov 2006	B1
7139914	Arnouse	Nov 2006	B2
7155416	Shatford	Dec 2006	B2
7159114	Zajkowski	Jan 2007	B1
7159765	Frerking	Jan 2007	B2
7167987	Angelo	Jan 2007	B2
7168089	Nguyen et al.	Jan 2007	B2
7176797	Zai et al.	Feb 2007	B2
7185363	Narin	Feb 2007	B1
7188110	Ludtke	Mar 2007	B1
7191466	Hamid et al.	Mar 2007	B1
7194438	Sovio et al.	Mar 2007	B2
7209955	Major et al.	Apr 2007	B1
7218944	Cromer	May 2007	B2
7225161	Lam	May 2007	B2
7230908	Vanderaar et al.	Jun 2007	B2
7231068	Tibor	Jun 2007	B2
7231451	Law et al.	Jun 2007	B2
7239226	Berardi et al.	Jul 2007	B2
7242923	Perera	Jul 2007	B2
7249177	Miller	Jul 2007	B1
7272723	Abbott et al.	Sep 2007	B1
7277737	Vollmer et al.	Oct 2007	B1
7278025	Saito	Oct 2007	B2
7283650	Sharma	Oct 2007	B1
7295119	Rappaport et al.	Nov 2007	B2
7305560	Giobbi	Dec 2007	B2
7310042	Seifert	Dec 2007	B2
7314164	Bonalle	Jan 2008	B2
7317799	Hammersmith	Jan 2008	B2
7319395	Puzio et al.	Jan 2008	B2
7330108	Thomas	Feb 2008	B2
7333002	Bixler et al.	Feb 2008	B2
7333615	Jarboe et al.	Feb 2008	B1
7336181	Nowak et al.	Feb 2008	B2
7336182	Baranowski et al.	Feb 2008	B1
7337326	Palmer et al.	Feb 2008	B2
7341181	Bonalle	Mar 2008	B2
7342503	Light et al.	Mar 2008	B1
7349557	Tibor	Mar 2008	B2
7356393	Schlatre et al.	Apr 2008	B1
7356706	Scheurich	Apr 2008	B2
7361919	Setlak	Apr 2008	B2
7363494	Brainard et al.	Apr 2008	B2
7370366	Lacan	May 2008	B2
7378939	Sengupta et al.	May 2008	B2
7380202	Lindhorst et al.	May 2008	B1
7382799	Young et al.	Jun 2008	B1
7387235	Gilbert et al.	Jun 2008	B2
7401731	Pletz et al.	Jul 2008	B1
7404088	Giobbi	Jul 2008	B2
7408799	Kang	Aug 2008	B1
7424134	Chou	Sep 2008	B2
7437330	Robinson	Oct 2008	B1
7447911	Chou et al.	Nov 2008	B2
7448087	Ohmori et al.	Nov 2008	B2
7458510	Zhou	Dec 2008	B1
7460836	Smith et al.	Dec 2008	B2
7461444	Deaett et al.	Dec 2008	B2
7464053	Pylant	Dec 2008	B1
7464059	Robinson	Dec 2008	B1
7466232	Neuwirth	Dec 2008	B2
7472280	Giobbi	Dec 2008	B2
7512806	Lemke	Mar 2009	B2
7525413	Jung et al.	Apr 2009	B2
7529944	Hamid	May 2009	B2
7533809	Robinson	May 2009	B1
7545312	Kiang et al.	Jun 2009	B2
7565329	Lapsley	Jul 2009	B2
7573382	Choubey et al.	Aug 2009	B2
7573841	Lee et al.	Aug 2009	B2
7574734	Fedronic et al.	Aug 2009	B2
7578442	Knowles	Aug 2009	B2
7583238	Cassen et al.	Sep 2009	B2
7583643	Smith et al.	Sep 2009	B2
7587611	Johnson et al.	Sep 2009	B2
7594611	Arrington, III	Sep 2009	B1
7595765	Hirsch et al.	Sep 2009	B1
7603564	Adachi	Oct 2009	B2
7606733	Shmueli et al.	Oct 2009	B2
7617523	Das	Nov 2009	B2
7620184	Marque Pucheu	Nov 2009	B2
7624073	Robinson	Nov 2009	B1
7624417	Dua	Nov 2009	B2
7640273	Wallmeier	Dec 2009	B2
7644443	Matsuyama et al.	Jan 2010	B2
7646307	Plocher et al.	Jan 2010	B2
7652892	Shiu et al.	Jan 2010	B2
7676380	Graves et al.	Mar 2010	B2
7689005	Wang	Mar 2010	B2
7701858	Werb et al.	Apr 2010	B2
7706896	Music et al.	Apr 2010	B2
7711152	Davida et al.	May 2010	B1
7715593	Adams et al.	May 2010	B1
7724713	Del Prado Pavon et al.	May 2010	B2
7724717	Porras et al.	May 2010	B2
7724720	Korpela et al.	May 2010	B2
7764236	Hill et al.	Jul 2010	B2
7765164	Robinson	Jul 2010	B1
7765181	Thomas	Jul 2010	B2
7768960	Barratt	Aug 2010	B1
7773754	Buer	Aug 2010	B2
7774613	Lemke	Aug 2010	B2
7780082	Handa et al.	Aug 2010	B2
7796551	Machiraju et al.	Sep 2010	B1
7813822	Hoffberg	Oct 2010	B1
7865448	Pizarro	Jan 2011	B2
7865937	White	Jan 2011	B1
7883003	Giobbi et al.	Feb 2011	B2
7883417	Bruzzese et al.	Feb 2011	B2
7904718	Giobbi	Mar 2011	B2
7943868	Anders et al.	May 2011	B2
7957536	Nolte	Jun 2011	B2
7961078	Reynolds et al.	Jun 2011	B1
7984064	Fusari	Jul 2011	B2
7996514	Baumert	Aug 2011	B2
8026821	Reeder et al.	Sep 2011	B2
8036152	Brown et al.	Oct 2011	B2
8077041	Stern et al.	Dec 2011	B2
8081215	Kuo et al.	Dec 2011	B2
8082160	Collins et al.	Dec 2011	B2
8089354	Perkins	Jan 2012	B2
8112066	Ben Ayed	Feb 2012	B2
8125624	Jones et al.	Feb 2012	B2
8135624	Ramalingam	Mar 2012	B1
8171528	Brown	May 2012	B1
8193923	Rork et al.	Jun 2012	B2
8200980	Robinson	Jun 2012	B1
8215552	Rambadt	Jul 2012	B1
8219129	Brown et al.	Jul 2012	B2
8248263	Shervey et al.	Aug 2012	B2
8258942	Lanzone et al.	Sep 2012	B1
8294554	Shoarinejad et al.	Oct 2012	B2
8296573	Bolle et al.	Oct 2012	B2
8307414	Zerfos et al.	Nov 2012	B2
8325011	Butler et al.	Dec 2012	B2
8340672	Brown et al.	Dec 2012	B2
8352730	Giobbi	Jan 2013	B2
8373562	Heinze et al.	Feb 2013	B1
8387124	Smetters et al.	Feb 2013	B2
8390456	Puleston et al.	Mar 2013	B2
8395484	Fullerton	Mar 2013	B2
8410906	Dacus et al.	Apr 2013	B1
8412949	Giobbi et al.	Apr 2013	B2
8421606	Collins et al.	Apr 2013	B2
8424079	Adams et al.	Apr 2013	B2
8432262	Talty	Apr 2013	B2
8433919	Giobbi	Apr 2013	B2
8448858	Kundu	May 2013	B1
8457672	Brown et al.	Jun 2013	B2
8473748	Sampas	Jun 2013	B2
8484696	Gatto et al.	Jul 2013	B2
8494576	Bye et al.	Jul 2013	B1
8508336	Giobbi	Aug 2013	B2
8511555	Babcock	Aug 2013	B2
8519823	Rinkes	Aug 2013	B2
8522019	Michaelis	Aug 2013	B2
8558699	Butler et al.	Oct 2013	B2
8572391	Golan et al.	Oct 2013	B2
8577091	Ivanov et al.	Nov 2013	B2
8646042	Brown	Feb 2014	B1
8659427	Brown et al.	Feb 2014	B2
8678273	McNeal	Mar 2014	B2
8717346	Claessen	May 2014	B2
8738925	Park et al.	May 2014	B1
8799574	Corda	Aug 2014	B2
8838993	Giobbi et al.	Sep 2014	B2
8856539	Weiss	Oct 2014	B2
8857716	Giobbi et al.	Oct 2014	B1
8886954	Giobbi	Nov 2014	B1
8907861	Hirt	Dec 2014	B2
8914477	Gammon	Dec 2014	B2
8918854	Giobbi	Dec 2014	B1
8931698	Ishikawa et al.	Jan 2015	B2
8979646	Moser et al.	Mar 2015	B2
9020854	Giobbi	Apr 2015	B2
9037140	Brown	May 2015	B1
9042819	Dua	May 2015	B2
9049188	Brown	Jun 2015	B1
9113464	Brown et al.	Aug 2015	B2
9165233	Testanero	Oct 2015	B2
9189788	Robinson	Nov 2015	B1
9230399	Yacenda	Jan 2016	B2
9235700	Brown	Jan 2016	B1
9251326	Giobbi et al.	Feb 2016	B2
9251332	Giobbi	Feb 2016	B2
9265043	Brown et al.	Feb 2016	B2
9265450	Giobbi	Feb 2016	B1
9269221	Brown et al.	Feb 2016	B2
9276914	Woodward	Mar 2016	B2
9298905	Giobbi	Mar 2016	B1
9305312	Kountotsis	Apr 2016	B2
9322974	Giobbi	Apr 2016	B1
9405898	Giobbi	Aug 2016	B2
9418205	Giobbi	Aug 2016	B2
9450956	Giobbi	Sep 2016	B1
9542542	Giobbi	Jan 2017	B2
9613483	Giobbi	Apr 2017	B2
9679289	Brown	Jun 2017	B1
9728080	Giobbi et al.	Aug 2017	B1
9807091	Giobbi	Oct 2017	B2
9830504	Masood	Nov 2017	B2
9892250	Giobbi	Feb 2018	B2
9898662	Tsuda	Feb 2018	B2
9904816	Giobbi et al.	Feb 2018	B1
9990628	Giobbi	Jun 2018	B2
10026253	Giobbi	Jul 2018	B2
10073960	Brown	Sep 2018	B1
10110385	Rush et al.	Oct 2018	B1
10171460	Giobbi	Jan 2019	B2
10217339	Giobbi	Feb 2019	B1
10229294	Giobbi et al.	Mar 2019	B1
10313336	Giobbi	Jun 2019	B2
10334541	Brown	Jun 2019	B1
10374795	Giobbi et al.	Aug 2019	B1
10383112	Brown et al.	Aug 2019	B2
10403128	Giobbi et al.	Sep 2019	B2
10437976	Giobbi	Oct 2019	B2
10455533	Brown	Oct 2019	B2
10469456	Giobbi	Nov 2019	B1
10698989	Giobbi	Jun 2020	B2
10764044	Giobbi et al.	Sep 2020	B1
10769939	Brown et al.	Sep 2020	B2
10817964	Guillama et al.	Oct 2020	B2
10909229	Giobbi	Feb 2021	B2
10943471	Giobbi	Mar 2021	B1
11212797	Brown et al.	Dec 2021	B2
11219022	Brown et al.	Jan 2022	B2
20010000535	Lapsley et al.	Apr 2001	A1
20010021950	Hawley et al.	Sep 2001	A1
20010024428	Onouchi	Sep 2001	A1
20010026619	Howard, Jr.	Oct 2001	A1
20010027121	Boesen	Oct 2001	A1
20010027439	Holtzman et al.	Oct 2001	A1
20010044337	Rowe	Nov 2001	A1
20020004783	Paltenghe et al.	Jan 2002	A1
20020007456	Peinado	Jan 2002	A1
20020010679	Felsher	Jan 2002	A1
20020013772	Peinado	Jan 2002	A1
20020014954	Fitzgibbon	Feb 2002	A1
20020015008	Kishida	Feb 2002	A1
20020015494	Nagai	Feb 2002	A1
20020019811	Lapsley et al.	Feb 2002	A1
20020022455	Salokannel et al.	Feb 2002	A1
20020023032	Pearson et al.	Feb 2002	A1
20020023217	Wheeler et al.	Feb 2002	A1
20020026424	Akashi	Feb 2002	A1
20020037732	Gous et al.	Mar 2002	A1
20020052193	Chetty	May 2002	A1
20020055908	Di Giorgio	May 2002	A1
20020056043	Glass	May 2002	A1
20020059114	Cockrill et al.	May 2002	A1
20020062249	Iannacci	May 2002	A1
20020068605	Stanley	Jun 2002	A1
20020069364	Dosch	Jun 2002	A1
20020071559	Christensen	Jun 2002	A1
20020073042	Martzen et al.	Jun 2002	A1
20020076051	Nii	Jun 2002	A1
20020080969	Giobbi	Jun 2002	A1
20020083178	Brothers	Jun 2002	A1
20020083318	Larose	Jun 2002	A1
20020086690	Takahashi et al.	Jul 2002	A1
20020089890	Fibranz et al.	Jul 2002	A1
20020091646	Lake	Jul 2002	A1
20020095586	Doyle et al.	Jul 2002	A1
20020095587	Doyle et al.	Jul 2002	A1
20020097876	Harrison	Jul 2002	A1
20020098888	Rowe et al.	Jul 2002	A1
20020100798	Farrugia et al.	Aug 2002	A1
20020103027	Rowe et al.	Aug 2002	A1
20020103881	Granade et al.	Aug 2002	A1
20020104006	Boate et al.	Aug 2002	A1
20020104019	Chatani	Aug 2002	A1
20020105918	Yamada et al.	Aug 2002	A1
20020108049	Xu et al.	Aug 2002	A1
20020109580	Shreve et al.	Aug 2002	A1
20020111919	Weller et al.	Aug 2002	A1
20020112183	Baird et al.	Aug 2002	A1
20020116615	Nguyen	Aug 2002	A1
20020124251	Hunter et al.	Sep 2002	A1
20020128017	Virtanen	Sep 2002	A1
20020129262	Kutaragi et al.	Sep 2002	A1
20020138438	Bardwell	Sep 2002	A1
20020138767	Hamid et al.	Sep 2002	A1
20020140542	Prokoski	Oct 2002	A1
20020141586	Margalit et al.	Oct 2002	A1
20020143623	Dayley	Oct 2002	A1
20020143655	Elston et al.	Oct 2002	A1
20020144116	Giobbi	Oct 2002	A1
20020144117	Faigle	Oct 2002	A1
20020147653	Shmueli et al.	Oct 2002	A1
20020148892	Bardwell	Oct 2002	A1
20020150282	Kinsella	Oct 2002	A1
20020152391	Willins et al.	Oct 2002	A1
20020153996	Chan et al.	Oct 2002	A1
20020158121	Stanford-Clark	Oct 2002	A1
20020158750	Almalik	Oct 2002	A1
20020158765	Pape et al.	Oct 2002	A1
20020160820	Winkler	Oct 2002	A1
20020174348	Ting	Nov 2002	A1
20020177460	Beasley et al.	Nov 2002	A1
20020178063	Gravelle et al.	Nov 2002	A1
20020184208	Kato	Dec 2002	A1
20020187746	Cheng et al.	Dec 2002	A1
20020191816	Martizen et al.	Dec 2002	A1
20020196963	Bardwell	Dec 2002	A1
20020199120	Schmidt	Dec 2002	A1
20030022701	Gupta	Jan 2003	A1
20030034877	Miller et al.	Feb 2003	A1
20030036416	Pattabiraman et al.	Feb 2003	A1
20030036425	Kaminkow et al.	Feb 2003	A1
20030046228	Berney	Mar 2003	A1
20030046237	Uberti	Mar 2003	A1
20030046552	Hamid et al.	Mar 2003	A1
20030048174	Stevens et al.	Mar 2003	A1
20030051173	Krueger	Mar 2003	A1
20030054868	Paulsen et al.	Mar 2003	A1
20030054881	Hedrick et al.	Mar 2003	A1
20030055689	Block et al.	Mar 2003	A1
20030055792	Kinoshita et al.	Mar 2003	A1
20030061172	Robinson	Mar 2003	A1
20030063619	Montano et al.	Apr 2003	A1
20030079133	Breiter et al.	Apr 2003	A1
20030087601	Agam et al.	May 2003	A1
20030088441	McNerney	May 2003	A1
20030105719	Berger	Jun 2003	A1
20030109274	Budka et al.	Jun 2003	A1
20030115351	Giobbi	Jun 2003	A1
20030115474	Khan	Jun 2003	A1
20030117969	Koo et al.	Jun 2003	A1
20030117980	Kim et al.	Jun 2003	A1
20030120934	Ortiz	Jun 2003	A1
20030127511	Kelly et al.	Jul 2003	A1
20030128866	Mcneal	Jul 2003	A1
20030137404	Bonneau et al.	Jul 2003	A1
20030139190	Steelberg et al.	Jul 2003	A1
20030142041	Barlow	Jul 2003	A1
20030146835	Carter	Aug 2003	A1
20030149744	Bierre	Aug 2003	A1
20030156742	Witt	Aug 2003	A1
20030159040	Hashimoto et al.	Aug 2003	A1
20030163388	Beane	Aug 2003	A1
20030167207	Berardi et al.	Sep 2003	A1
20030169697	Suzuki et al.	Sep 2003	A1
20030172028	Abell et al.	Sep 2003	A1
20030172037	Jung	Sep 2003	A1
20030174839	Yamagata et al.	Sep 2003	A1
20030176218	LeMay et al.	Sep 2003	A1
20030177102	Robinson	Sep 2003	A1
20030186739	Paulsen et al.	Oct 2003	A1
20030195842	Reece	Oct 2003	A1
20030196084	Okereke	Oct 2003	A1
20030199267	Iwasa et al.	Oct 2003	A1
20030204526	Salehi-Had	Oct 2003	A1
20030204721	Barrus et al.	Oct 2003	A1
20030213840	Livingston et al.	Nov 2003	A1
20030223394	Parantainen et al.	Dec 2003	A1
20030225703	Angel	Dec 2003	A1
20030226031	Proudler et al.	Dec 2003	A1
20030233458	Kwon et al.	Dec 2003	A1
20040002347	Hoctor et al.	Jan 2004	A1
20040015403	Moskowitz et al.	Jan 2004	A1
20040022384	Flores	Feb 2004	A1
20040029620	Karaoguz	Feb 2004	A1
20040029635	Giobbi	Feb 2004	A1
20040030764	Birk et al.	Feb 2004	A1
20040030894	Labrou et al.	Feb 2004	A1
20040035644	Ford et al.	Feb 2004	A1
20040039909	Cheng	Feb 2004	A1
20040044627	Russell et al.	Mar 2004	A1
20040048570	Oba et al.	Mar 2004	A1
20040048609	Kosaka	Mar 2004	A1
20040059682	Hasumi et al.	Mar 2004	A1
20040059912	Zizzi	Mar 2004	A1
20040064728	Scheurich	Apr 2004	A1
20040068656	Lu	Apr 2004	A1
20040073792	Noble et al.	Apr 2004	A1
20040081127	Gardner et al.	Apr 2004	A1
20040082385	Silva et al.	Apr 2004	A1
20040088558	Candelore	May 2004	A1
20040090345	Hitt	May 2004	A1
20040098597	Giobbi	May 2004	A1
20040114563	Shvodian	Jun 2004	A1
20040117644	Colvin	Jun 2004	A1
20040123106	D'Angelo et al.	Jun 2004	A1
20040123127	Teicher	Jun 2004	A1
20040127277	Walker et al.	Jul 2004	A1
20040128162	Schlotterbeck et al.	Jul 2004	A1
20040128389	Kopchik	Jul 2004	A1
20040128500	Cihula et al.	Jul 2004	A1
20040128508	Wheeler et al.	Jul 2004	A1
20040128519	Klinger et al.	Jul 2004	A1
20040129787	Saito et al.	Jul 2004	A1
20040132432	Moores et al.	Jul 2004	A1
20040137912	Lin	Jul 2004	A1
20040153649	Rhoads et al.	Aug 2004	A1
20040158746	Hu et al.	Aug 2004	A1
20040166875	Jenkins et al.	Aug 2004	A1
20040167465	Mihai et al.	Aug 2004	A1
20040181695	Walker	Sep 2004	A1
20040193925	Safriel	Sep 2004	A1
20040194133	Ikeda	Sep 2004	A1
20040201755	Norskog	Oct 2004	A1
20040203566	Leung	Oct 2004	A1
20040203923	Mullen	Oct 2004	A1
20040208139	Iwamura	Oct 2004	A1
20040209690	Bruzzese et al.	Oct 2004	A1
20040209692	Schober et al.	Oct 2004	A1
20040214582	Lan et al.	Oct 2004	A1
20040215615	Larsson et al.	Oct 2004	A1
20040217859	Pucci et al.	Nov 2004	A1
20040218581	Cattaneo	Nov 2004	A1
20040222877	Teramura et al.	Nov 2004	A1
20040230488	Beenau et al.	Nov 2004	A1
20040230809	Lowensohn et al.	Nov 2004	A1
20040234117	Tibor	Nov 2004	A1
20040243519	Perttila et al.	Dec 2004	A1
20040246103	Zukowski	Dec 2004	A1
20040246950	Parker et al.	Dec 2004	A1
20040250074	Kilian-Kehr	Dec 2004	A1
20040252012	Beenau	Dec 2004	A1
20040252659	Yun et al.	Dec 2004	A1
20040253996	Chen et al.	Dec 2004	A1
20040254837	Roshkoff	Dec 2004	A1
20040255139	Giobbi	Dec 2004	A1
20040255145	Chow	Dec 2004	A1
20050001028	Zuili	Jan 2005	A1
20050002028	Kasapi	Jan 2005	A1
20050005136	Chen et al.	Jan 2005	A1
20050006452	Aupperle	Jan 2005	A1
20050009517	Maes	Jan 2005	A1
20050020322	Ruuska et al.	Jan 2005	A1
20050021561	Noonan	Jan 2005	A1
20050025093	Yun et al.	Feb 2005	A1
20050028168	Marcjan	Feb 2005	A1
20050035897	Perl et al.	Feb 2005	A1
20050039027	Shapiro	Feb 2005	A1
20050040961	Tuttle	Feb 2005	A1
20050044372	Aull et al.	Feb 2005	A1
20050044387	Ozolins	Feb 2005	A1
20050047386	Yi	Mar 2005	A1
20050049013	Chang et al.	Mar 2005	A1
20050050208	Chatani	Mar 2005	A1
20050050324	Corbett et al.	Mar 2005	A1
20050054431	Walker	Mar 2005	A1
20050055242	Bello et al.	Mar 2005	A1
20050055244	Mullan et al.	Mar 2005	A1
20050058292	Diorio et al.	Mar 2005	A1
20050074126	Stanko	Apr 2005	A1
20050076242	Breuer	Apr 2005	A1
20050081040	Johnson et al.	Apr 2005	A1
20050084137	Kim	Apr 2005	A1
20050086115	Pearson	Apr 2005	A1
20050086501	Woo	Apr 2005	A1
20050086515	Paris	Apr 2005	A1
20050089000	Bae et al.	Apr 2005	A1
20050090200	Karaoguz et al.	Apr 2005	A1
20050091338	de la Huerga	Apr 2005	A1
20050091553	Chien et al.	Apr 2005	A1
20050094657	Sung et al.	May 2005	A1
20050096053	Liu et al.	May 2005	A1
20050097037	Tibor	May 2005	A1
20050105600	Culum et al.	May 2005	A1
20050105734	Buer	May 2005	A1
20050108164	Salafia, III	May 2005	A1
20050109836	Ben-Aissa	May 2005	A1
20050109841	Ryan	May 2005	A1
20050113070	Okabe	May 2005	A1
20050114149	Rodriguez et al.	May 2005	A1
20050114150	Franklin	May 2005	A1
20050116020	Smolucha et al.	Jun 2005	A1
20050117530	Abraham	Jun 2005	A1
20050119979	Murashita et al.	Jun 2005	A1
20050124294	Wentink	Jun 2005	A1
20050125258	Yellin et al.	Jun 2005	A1
20050137827	Takamiya	Jun 2005	A1
20050137977	Wankmueller	Jun 2005	A1
20050138390	Adams et al.	Jun 2005	A1
20050138576	Baumert	Jun 2005	A1
20050139656	Arnouse	Jun 2005	A1
20050141451	Yoon et al.	Jun 2005	A1
20050152394	Cho	Jul 2005	A1
20050154897	Holloway et al.	Jul 2005	A1
20050161503	Remery et al.	Jul 2005	A1
20050165684	Jensen et al.	Jul 2005	A1
20050166063	Huang	Jul 2005	A1
20050167482	Ramachandran et al.	Aug 2005	A1
20050169292	Young	Aug 2005	A1
20050177716	Ginter et al.	Aug 2005	A1
20050180385	Jeong et al.	Aug 2005	A1
20050182661	Allard et al.	Aug 2005	A1
20050182975	Guo et al.	Aug 2005	A1
20050187792	Harper	Aug 2005	A1
20050192748	Andric et al.	Sep 2005	A1
20050195975	Kawakita	Sep 2005	A1
20050200453	Turner et al.	Sep 2005	A1
20050201389	Shimanuki et al.	Sep 2005	A1
20050203682	Omino et al.	Sep 2005	A1
20050203844	Ferguson	Sep 2005	A1
20050210270	Rohatgi et al.	Sep 2005	A1
20050212657	Simon	Sep 2005	A1
20050215233	Perera	Sep 2005	A1
20050216313	Claud et al.	Sep 2005	A1
20050216639	Sparer et al.	Sep 2005	A1
20050218215	Lauden	Oct 2005	A1
20050220046	Falck et al.	Oct 2005	A1
20050221869	Liu et al.	Oct 2005	A1
20050229007	Bolle et al.	Oct 2005	A1
20050229240	Nanba	Oct 2005	A1
20050231328	Castle et al.	Oct 2005	A1
20050242921	Zimmerman et al.	Nov 2005	A1
20050243787	Hong et al.	Nov 2005	A1
20050249385	Kondo	Nov 2005	A1
20050251688	Nanavati et al.	Nov 2005	A1
20050253683	Lowe	Nov 2005	A1
20050256878	Brown et al.	Nov 2005	A1
20050257102	Moyer et al.	Nov 2005	A1
20050264416	Maurer	Dec 2005	A1
20050268111	Markham	Dec 2005	A1
20050269401	Spitzer et al.	Dec 2005	A1
20050272403	Ryu et al.	Dec 2005	A1
20050277385	Daum	Dec 2005	A1
20050281215	Budampati et al.	Dec 2005	A1
20050281320	Neugebauer	Dec 2005	A1
20050282558	Choi et al.	Dec 2005	A1
20050284932	Sukeda et al.	Dec 2005	A1
20050287985	Balfanz et al.	Dec 2005	A1
20050288015	Azizi et al.	Dec 2005	A1
20050288069	Arunan et al.	Dec 2005	A1
20050289473	Gustafson et al.	Dec 2005	A1
20060001525	Nitzan et al.	Jan 2006	A1
20060009216	Welnick et al.	Jan 2006	A1
20060014430	Liang et al.	Jan 2006	A1
20060022042	Smets et al.	Feb 2006	A1
20060022046	Iwamura	Feb 2006	A1
20060022800	Krishna et al.	Feb 2006	A1
20060025180	Rajkotia et al.	Feb 2006	A1
20060026673	Tsuchida	Feb 2006	A1
20060030279	Leabman	Feb 2006	A1
20060030353	Jun	Feb 2006	A1
20060034250	Kim et al.	Feb 2006	A1
20060041746	Kirkup et al.	Feb 2006	A1
20060046664	Paradiso et al.	Mar 2006	A1
20060058102	Nguyen	Mar 2006	A1
20060063575	Gatto et al.	Mar 2006	A1
20060064605	Giobbi	Mar 2006	A1
20060069814	Abraham et al.	Mar 2006	A1
20060072586	Callaway et al.	Apr 2006	A1
20060074713	Conry et al.	Apr 2006	A1
20060076401	Frerking	Apr 2006	A1
20060078176	Abiko et al.	Apr 2006	A1
20060087407	Stewart et al.	Apr 2006	A1
20060089138	Smith et al.	Apr 2006	A1
20060097949	Luebke et al.	May 2006	A1
20060110012	Ritter	May 2006	A1
20060111955	Winter et al.	May 2006	A1
20060113381	Hochstein et al.	Jun 2006	A1
20060116935	Evans	Jun 2006	A1
20060117013	Wada	Jun 2006	A1
20060120287	Foti et al.	Jun 2006	A1
20060129838	Chen	Jun 2006	A1
20060136728	Gentry et al.	Jun 2006	A1
20060136742	Giobbi	Jun 2006	A1
20060143441	Giobbi	Jun 2006	A1
20060144943	Kim	Jul 2006	A1
20060156027	Blake	Jul 2006	A1
20060158308	Mcmullen et al.	Jul 2006	A1
20060163349	Neugebauer	Jul 2006	A1
20060165060	Dua	Jul 2006	A1
20060169771	Brookner	Aug 2006	A1
20060170530	Nwosu et al.	Aug 2006	A1
20060170565	Husak et al.	Aug 2006	A1
20060172700	Wu	Aug 2006	A1
20060173846	Omae et al.	Aug 2006	A1
20060173991	Piikivi	Aug 2006	A1
20060183426	Graves	Aug 2006	A1
20060183462	Kolehmainen	Aug 2006	A1
20060184795	Doradla et al.	Aug 2006	A1
20060185005	Graves	Aug 2006	A1
20060187029	Thomas	Aug 2006	A1
20060190348	Ofer et al.	Aug 2006	A1
20060190413	Harper	Aug 2006	A1
20060194598	Kim et al.	Aug 2006	A1
20060195576	Rinne et al.	Aug 2006	A1
20060198337	Hoang et al.	Sep 2006	A1
20060200467	Ohmori et al.	Sep 2006	A1
20060205408	Nakagawa et al.	Sep 2006	A1
20060208066	Finn et al.	Sep 2006	A1
20060208853	Kung et al.	Sep 2006	A1
20060222042	Teramura et al.	Oct 2006	A1
20060226950	Kanou et al.	Oct 2006	A1
20060229909	Kaila et al.	Oct 2006	A1
20060236373	Graves et al.	Oct 2006	A1
20060237528	Bishop et al.	Oct 2006	A1
20060238305	Loving et al.	Oct 2006	A1
20060268891	Heidari-Bateni et al.	Nov 2006	A1
20060273176	Audebert et al.	Dec 2006	A1
20060274711	Nelson et al.	Dec 2006	A1
20060279412	Holland et al.	Dec 2006	A1
20060286969	Talmor et al.	Dec 2006	A1
20060288095	Torok et al.	Dec 2006	A1
20060288233	Kozlay	Dec 2006	A1
20060290473	Mahasenan et al.	Dec 2006	A1
20060290580	Noro et al.	Dec 2006	A1
20060292986	Bitran et al.	Dec 2006	A1
20060293925	Flom	Dec 2006	A1
20060294388	Abraham et al.	Dec 2006	A1
20070003111	Awatsu et al.	Jan 2007	A1
20070005403	Kennedy et al.	Jan 2007	A1
20070007331	Jasper et al.	Jan 2007	A1
20070008070	Friedrich	Jan 2007	A1
20070008916	Haugli et al.	Jan 2007	A1
20070011724	Gonzalez et al.	Jan 2007	A1
20070016800	Spottswood et al.	Jan 2007	A1
20070019845	Kato	Jan 2007	A1
20070029381	Braiman	Feb 2007	A1
20070032225	Konicek et al.	Feb 2007	A1
20070032288	Nelson et al.	Feb 2007	A1
20070033072	Bildirici	Feb 2007	A1
20070033150	Nwosu	Feb 2007	A1
20070036396	Sugita	Feb 2007	A1
20070038751	Jorgensen	Feb 2007	A1
20070043594	Lavergne	Feb 2007	A1
20070050259	Wesley	Mar 2007	A1
20070050398	Mochizuki	Mar 2007	A1
20070050845	Das	Mar 2007	A1
20070051794	Glanz	Mar 2007	A1
20070051798	Kawai et al.	Mar 2007	A1
20070055630	Gauthier et al.	Mar 2007	A1
20070060095	Subrahmanya et al.	Mar 2007	A1
20070060319	Block	Mar 2007	A1
20070064742	Shvodian	Mar 2007	A1
20070069852	Mo et al.	Mar 2007	A1
20070070040	Chen et al.	Mar 2007	A1
20070072636	Worfolk et al.	Mar 2007	A1
20070073553	Flinn et al.	Mar 2007	A1
20070084523	McLean	Apr 2007	A1
20070084913	Weston	Apr 2007	A1
20070087682	DaCosta	Apr 2007	A1
20070087834	Moser	Apr 2007	A1
20070100507	Simon	May 2007	A1
20070100939	Bagley et al.	May 2007	A1
20070109117	Heitzmann et al.	May 2007	A1
20070112676	Kontio	May 2007	A1
20070118891	Buer	May 2007	A1
20070120643	Lee	May 2007	A1
20070132586	Plocher et al.	Jun 2007	A1
20070133478	Armbruster et al.	Jun 2007	A1
20070136407	Rudelic	Jun 2007	A1
20070142032	Balsillie	Jun 2007	A1
20070147332	Lappetelainen et al.	Jun 2007	A1
20070152826	August et al.	Jul 2007	A1
20070156850	Corrion	Jul 2007	A1
20070157249	Cordray et al.	Jul 2007	A1
20070158411	Krieg	Jul 2007	A1
20070159301	Hirt	Jul 2007	A1
20070159994	Brown et al.	Jul 2007	A1
20070164847	Crawford et al.	Jul 2007	A1
20070169121	Hunt et al.	Jul 2007	A1
20070174809	Brown	Jul 2007	A1
20070176756	Friedrich	Aug 2007	A1
20070176778	Ando et al.	Aug 2007	A1
20070180047	Dong	Aug 2007	A1
20070187266	Porter et al.	Aug 2007	A1
20070192601	Spain et al.	Aug 2007	A1
20070194882	Yokota et al.	Aug 2007	A1
20070198436	Weiss	Aug 2007	A1
20070204078	Boccon-Gibod et al.	Aug 2007	A1
20070205860	Jones et al.	Sep 2007	A1
20070205861	Nair et al.	Sep 2007	A1
20070207750	Brown et al.	Sep 2007	A1
20070213048	Trauberg	Sep 2007	A1
20070214492	Gopi et al.	Sep 2007	A1
20070218921	Lee et al.	Sep 2007	A1
20070219926	Korn	Sep 2007	A1
20070220272	Campisi et al.	Sep 2007	A1
20070229268	Swan et al.	Oct 2007	A1
20070245157	Giobbi	Oct 2007	A1
20070245158	Giobbi	Oct 2007	A1
20070247366	Smith et al.	Oct 2007	A1
20070258626	Reiner	Nov 2007	A1
20070260883	Giobbi	Nov 2007	A1
20070260888	Giobbi et al.	Nov 2007	A1
20070266257	Camaisa et al.	Nov 2007	A1
20070268862	Singh et al.	Nov 2007	A1
20070271194	Walker et al.	Nov 2007	A1
20070271433	Takemura	Nov 2007	A1
20070277044	Graf et al.	Nov 2007	A1
20070280509	Owen et al.	Dec 2007	A1
20070285212	Rotzoll	Dec 2007	A1
20070285238	Batra	Dec 2007	A1
20070288263	Rodgers	Dec 2007	A1
20070288752	Chan	Dec 2007	A1
20070293155	Liao et al.	Dec 2007	A1
20070294755	Dadhia et al.	Dec 2007	A1
20070296544	Beenau et al.	Dec 2007	A1
20080001783	Cargonja et al.	Jan 2008	A1
20080005432	Kagawa	Jan 2008	A1
20080008359	Beenau	Jan 2008	A1
20080011842	Curry et al.	Jan 2008	A1
20080012685	Friedrich et al.	Jan 2008	A1
20080012767	Caliri et al.	Jan 2008	A1
20080016004	Kurasaki et al.	Jan 2008	A1
20080019578	Saito et al.	Jan 2008	A1
20080028227	Sakurai	Jan 2008	A1
20080028453	Nguyen et al.	Jan 2008	A1
20080040609	Giobbi	Feb 2008	A1
20080046366	Bemmel	Feb 2008	A1
20080046715	Balazs et al.	Feb 2008	A1
20080049700	Shah et al.	Feb 2008	A1
20080061941	Fischer et al.	Mar 2008	A1
20080071577	Highley	Mar 2008	A1
20080072063	Takahashi et al.	Mar 2008	A1
20080088475	Martin	Apr 2008	A1
20080090548	Ramalingam	Apr 2008	A1
20080095359	Schreyer et al.	Apr 2008	A1
20080107089	Larsson et al.	May 2008	A1
20080109895	Janevski	May 2008	A1
20080111752	Lindackers et al.	May 2008	A1
20080127176	Lee et al.	May 2008	A1
20080129450	Riegebauer	Jun 2008	A1
20080129463	Tuttle	Jun 2008	A1
20080148351	Bhatia et al.	Jun 2008	A1
20080149705	Giobbi	Jun 2008	A1
20080150678	Giobbi	Jun 2008	A1
20080156866	McNeal	Jul 2008	A1
20080164997	Aritsuka et al.	Jul 2008	A1
20080169909	Park et al.	Jul 2008	A1
20080186166	Zhou et al.	Aug 2008	A1
20080188308	Shepherd et al.	Aug 2008	A1
20080195863	Kennedy	Aug 2008	A1
20080201768	Koo et al.	Aug 2008	A1
20080203107	Conley et al.	Aug 2008	A1
20080208016	Hughes et al.	Aug 2008	A1
20080209571	Bhaskar et al.	Aug 2008	A1
20080218416	Handy et al.	Sep 2008	A1
20080222701	Saaranen et al.	Sep 2008	A1
20080223918	Williams	Sep 2008	A1
20080228524	Brown	Sep 2008	A1
20080235144	Phillips	Sep 2008	A1
20080238625	Rofougaran et al.	Oct 2008	A1
20080250388	Meyer et al.	Oct 2008	A1
20080251579	Larsen	Oct 2008	A1
20080278325	Zimman et al.	Nov 2008	A1
20080289030	Poplett	Nov 2008	A1
20080289032	Aoki et al.	Nov 2008	A1
20080303637	Gelbman et al.	Dec 2008	A1
20080313728	Pandrangi et al.	Dec 2008	A1
20080314971	Faith et al.	Dec 2008	A1
20080316045	Sriharto et al.	Dec 2008	A1
20090002134	McAllister	Jan 2009	A1
20090013191	Popowski	Jan 2009	A1
20090016573	McAfee, II	Jan 2009	A1
20090024584	Dharap et al.	Jan 2009	A1
20090033464	Friedrich	Feb 2009	A1
20090033485	Naeve et al.	Feb 2009	A1
20090036164	Rowley	Feb 2009	A1
20090041309	Kim	Feb 2009	A1
20090045916	Nitzan et al.	Feb 2009	A1
20090052389	Qin et al.	Feb 2009	A1
20090070146	Haider et al.	Mar 2009	A1
20090076849	Diller	Mar 2009	A1
20090081996	Duggal et al.	Mar 2009	A1
20090096580	Paananen	Apr 2009	A1
20090121890	Brown et al.	May 2009	A1
20090125401	Beenau et al.	May 2009	A1
20090140045	Evans	Jun 2009	A1
20090157512	King	Jun 2009	A1
20090165123	Giobbi	Jun 2009	A1
20090176566	Kelly	Jul 2009	A1
20090177495	Abousy et al.	Jul 2009	A1
20090195461	Hirt	Aug 2009	A1
20090199206	Finkenzeller et al.	Aug 2009	A1
20090206992	Giobbi	Aug 2009	A1
20090232362	Otsubo et al.	Sep 2009	A1
20090237245	Brinton et al.	Sep 2009	A1
20090237253	Neuwirth	Sep 2009	A1
20090239667	Rowe et al.	Sep 2009	A1
20090253516	Hartmann et al.	Oct 2009	A1
20090254448	Giobbi	Oct 2009	A1
20090254971	Herz	Oct 2009	A1
20090264712	Baldus	Oct 2009	A1
20090310514	Jeon et al.	Dec 2009	A1
20090313689	Nystroem et al.	Dec 2009	A1
20090319788	Zick et al.	Dec 2009	A1
20090320118	Mueller et al.	Dec 2009	A1
20090322510	Berger et al.	Dec 2009	A1
20090328182	Malakapalli et al.	Dec 2009	A1
20100005526	Tsuji et al.	Jan 2010	A1
20100007498	Jackson	Jan 2010	A1
20100022308	Hartmann et al.	Jan 2010	A1
20100023074	Powers et al.	Jan 2010	A1
20100037255	Sheehan et al.	Feb 2010	A1
20100062743	Jonsson	Mar 2010	A1
20100077214	Jogand-Coulomb et al.	Mar 2010	A1
20100117794	Adams et al.	May 2010	A1
20100134257	Puleston et al.	Jun 2010	A1
20100169442	Liu et al.	Jul 2010	A1
20100169964	Liu et al.	Jul 2010	A1
20100172567	Prokoski	Jul 2010	A1
20100174911	Isshiki	Jul 2010	A1
20100188226	Seder et al.	Jul 2010	A1
20100214100	Page	Aug 2010	A1
20100277283	Burkart et al.	Nov 2010	A1
20100277286	Burkart et al.	Nov 2010	A1
20100291896	Corda	Nov 2010	A1
20100305843	Yan et al.	Dec 2010	A1
20100328033	Kamei	Dec 2010	A1
20110072034	Sly et al.	Mar 2011	A1
20110072132	Shafer et al.	Mar 2011	A1
20110082735	Kannan et al.	Apr 2011	A1
20110085287	Ebrom et al.	Apr 2011	A1
20110091136	Danch	Apr 2011	A1
20110116358	Li et al.	May 2011	A9
20110126188	Bernstein	May 2011	A1
20110221568	Giobbi	Sep 2011	A1
20110227740	Wohltjen	Sep 2011	A1
20110238517	Ramalingam	Sep 2011	A1
20110246790	Koh et al.	Oct 2011	A1
20110266348	Denniston, Jr.	Nov 2011	A1
20110307599	Saretto	Dec 2011	A1
20120028609	Hruska	Feb 2012	A1
20120030006	Yoder	Feb 2012	A1
20120069776	Caldwell et al.	Mar 2012	A1
20120086571	Scalisi et al.	Apr 2012	A1
20120182123	Butler et al.	Jul 2012	A1
20120212322	Idsoee	Aug 2012	A1
20120226451	Bacot	Sep 2012	A1
20120226565	Drozd	Sep 2012	A1
20120226907	Hohberger	Sep 2012	A1
20120238287	Scherzer	Sep 2012	A1
20120278188	Attar	Nov 2012	A1
20120300753	Brown et al.	Nov 2012	A1
20120310720	Balsan	Dec 2012	A1
20130019295	Park	Jan 2013	A1
20130019323	Arvidsson et al.	Jan 2013	A1
20130044111	Vangilder et al.	Feb 2013	A1
20130111543	Brown	May 2013	A1
20130135082	Xian	May 2013	A1
20130179201	Fuerstenberg	Jul 2013	A1
20130219186	Giobbi et al.	Aug 2013	A1
20130276140	Coffing	Oct 2013	A1
20130277425	Sharma	Oct 2013	A1
20130297514	Giobbi	Nov 2013	A1
20130315210	Brown et al.	Nov 2013	A1
20130331063	Cormier	Dec 2013	A1
20140074696	Glaser	Mar 2014	A1
20140147018	Argue	May 2014	A1
20140266604	Masood	Sep 2014	A1
20140266713	Sehgal et al.	Sep 2014	A1
20140337920	Giobbi	Nov 2014	A1
20150026480	Giobbi et al.	Jan 2015	A1
20150039451	Bonfiglio	Feb 2015	A1
20150138330	Krishnamoorthi	May 2015	A1
20150294293	Signarsson	Oct 2015	A1
20150310385	King et al.	Oct 2015	A1
20150310440	Hynes	Oct 2015	A1
20160005020	Fernando	Jan 2016	A1
20160093081	Kim	Mar 2016	A1
20160133123	Giobbi et al.	May 2016	A1
20160171200	Giobbi	Jun 2016	A1
20160203349	Giobbi	Jul 2016	A1
20160205682	Brown et al.	Jul 2016	A1
20160210614	Hall	Jul 2016	A1
20160300236	Wiley	Oct 2016	A1
20160306956	Giobbi	Oct 2016	A1
20170041315	Giobbi	Feb 2017	A1
20170085564	Giobbi	Mar 2017	A1
20170091548	Agrawal	Mar 2017	A1
20170270738	Giobbi	Sep 2017	A1
20170309165	Brown et al.	Oct 2017	A1
20170353500	Jacobsen	Dec 2017	A1
20180019998	Giobbi	Jan 2018	A1
20180129799	Giobbi	May 2018	A1
20180322718	Qian	Nov 2018	A1
20180357475	Honda	Dec 2018	A1
20190065721	Giobbi	Feb 2019	A1
20190172281	Einberg	Jun 2019	A1
20190260724	Hefetz et al.	Aug 2019	A1
20190289562	Brown	Sep 2019	A1
20200351873	Brown et al.	Nov 2020	A1
20210219869	Ryu	Jul 2021	A1
20220210643	Hynds	Jun 2022	A1

Foreign Referenced Citations (14)

Number	Date	Country
1536306	Jun 2005	EP
10-049604	Feb 1998	JP
9956429	Nov 1999	WO
WO200062505	Oct 2000	WO
WO200122724	Mar 2001	WO
0135334	May 2001	WO
WO200175876	Oct 2001	WO
WO200177790	Oct 2001	WO
2004010774	Feb 2004	WO
2004038563	May 2004	WO
2005031663	Apr 2005	WO
WO2005050450	Jun 2005	WO
WO2005086802	Sep 2005	WO
2007087558	Aug 2007	WO

Non-Patent Literature Citations (163)

Entry
Zhang (A User-Centric M-Payment Solution) (Year: 2005).
Labrou et al (Wireless Wallet) (Year: 2004).
“Say Hello to Bluetooth,” Bluetooth Web site, 5 pages.
Lewis, Sony and Visa in On-Line Entertainment Venture, New York Times, v145, Nov. 16, 1995, 1 page.
Firecrest Shows How Truly Commercially-Minded Companies Will Exploit the Internet, Computergram International, Jan. 18, 1996, 2 pages.
Fasca, Chad, “The Circuit,” Electronic News, 45(45) (Nov. 8, 1999), 2 pages.
Dennis, Digital Passports Need Not Infringe Civil Liberties, Newsbytes, Dec. 2, 1999, 2 pages.
Wallace, Bob, “The Internet Unplugged,” InformationWeek, 765(22), (Dec. 13, 1999), 5 pages.
Weber, Thomas E., “In the Age of Napster, Protecting Copyright is a Digital Arms Race,” Wall Street Journal, (Jul. 24, 2000), 2 pages.
Article, “Sound Waves Could Help Ease Web-Fraud Woes,” Wall Street Journal, Aug. 14, 2000, 2 pages.
Sapsford, Jathon, “E-Business: Sound Waves Could Help Ease Web-Fraud Woes,” Wall Street Journal, (Aug. 14, 2000), B1.
Press Release, “Thompson Multimedia Unveils Copy Protection Proposal Designed to Provide Additional Layeof Dil=) ital Content Security,” www.thomDson-multimedia.com, May 30, 2001, 2 pages.
Press Release, “Thompson Bets on Smart Cards For Video Encryption,” www.informationweek.com, Jun. 7, 2001, 1 page.
Press Release, “Micronas and Thomson Multimedia Showcase a New Copy Protection System that Will Drive the Future of Digital Television,” www.micronas.com, Jan. 8, 2002, 3 pages.
Press Release, “Content Protection Plan Targets Wireless Home Networks,” www.eetimes.com, Jan. 11, 2002, 2 pages.
“Applying Biometrics to Door Access,” Security Magazine, Sep. 26, 2002 [online] [Retrieved on Jan. 7, 2007] Retrieved from the I nternet<U RL: http://www.securitymagazine.com/CDAIArticles/Technologies/3ae61 Oeaa34d801OVgnVCM 1 OOOOOf932a8cO >, 5 pages.
Wade, W., “Using Fingerprints to Make Payments at POS Slowly Gaining Popularity,” Credit Union Journal, International Biometric Group, Apr. 21, 2003, [online] [Retrieved on Jan. 7, 2007] Retrieved from theInternet<URL: http://www.biometricgroup.com/in the news/04.21.03.html>, 3 pages.
Mciver, R. et al., “Identification and Verification Working Together,” Bioscrypt™, Aug. 27, 2004, [online] [Retrieved on Jan. 7, 2007] Retrieved from theI nternet< U RL: http://www.ibia.org/membersad min/whitepapers/pdfl15l1dentification%20and%20Verification %20Workin!=)%20To!=)ether.pdf>, 5 pages.
International Search Report and Written Opinion for PCT/US04/38124, dated Apr. 7, 2005, 10 pages.
Alliance Activities: Publications: Identity—Smart Card Alliance, Smart Card Alliance, 1997-2007, [online][Retrieved on Jan. 7, 2007] Retrieved from theI nternet< U RL: http://www.smartcardalliance.org/pages/pu bl ications-identity, 3 pages.
“Frequently Asked Questions (FAQs) About BioPay,” BioPay, LLC, 2007, [online] [Retrieved on Jan. 7, 2007] Retrieved from the Internet<URL:http://www.biopay.com/faqs-lowes.asp>, 5 pages.
“SAFModule™: A Look Into Strong Authentication,” saflink Corporation, [online] [Retrieved on Jan. 7, 2007] Retrieved from the Internet<URL:http://www.ibia.or?=)/membersadmin/whitepapers/pdf/6/SAFmod WP.pdf>, 8 pages.
PCT International Search Report and Written Opinion, PCT/US05/43447, dated Feb. 22, 2007, 7 pages.
PCT International Search Report and Written Opinion, PCT/US05/46843, dated Mar. 1, 2007, 10 pages.
PCT International Search Report and Written Opinion, PCT/US07/11103, dated Apr. 23, 2008, 9 pages.
PCT International Search Report and Written Opinion, PCT/US07/11104, dated Jun. 26, 2008, 9 pages.
PCT International Search Report and Written Opinion, PCT/US07/11102, dated Oct. 3, 2008, 11 pages.
PCT International Search Report and Written Opinion, PCT/US07/11105, dated Oct. 20, 2008, 10 pages.
What is a File?, Apr. 30, 1998, URL: http://unixhelp.ed.ac.uk/editors/whatisafile.html, accessed Mar. 11, 2010 via http://waybackmachine.org/1 9980615000000' lhttp://unixhelp.ed.ac.uk/editors/whatisafile.html, 1 page.
Debow, Credit/Debit Debuts in Midwest Smart Card Test, Computers in Banking, v6, n11, Nov. 1989, 4 pages.
Paget, Paul, “The Security Behind Secure Extranets,” Enterprise Systems Journal, (Dec. 1999),4 pgs.
Vainio, Juha., “Bluetooth Security”, dated 2000, Helskinki University of Technology, 17 pages.
Van Winkle, William, “Bluetooth, the King of Connectivity,” Laptop Buyer's Guide and Handbook, (Jan. 2000), 6 pages.
Blum, Jonathan, “Digital Rights Management May Solver the Napster “Problem”,” Technology Investor Industrysector, (Oct. 2000), 4 pages.
Lake, Matt, “Downloading for Dollars,” Sound & Vision, (Nov. 2000), 2 pages.
Antonoff, Michael, “Visiting Video Valley,” Sound & Vision, 3 pages, Nov. 2001.
Katz et al., “Smart Cards and Biometrics in Privacy-Sensitive Secure Personal Identification System”, dated May 2002, Smart Card Alliance, p. 1-29.
“Smart Cards and Biometrics White Paper,” Smart Card Alliance, May 2002, [online] [Retrieved on Jan. 7, 2007] Retrieved from theInternet<URL:http://www.securitymanagement.com/library/smartcard faqtech0802.pdf>, 7 pages.
Nilsson, J. et al., “Match-On-Card for Java Cards,” Precise Biometrics, White Paper, Apr. 2004, [online] [Retrieved on Jan. 7, 2007] Retrieved from theI nternet< U RL: http://www.ibia.org/membersadmin/whitepapers/pdf/ 17iPrecise%20Match-on-Card%20for%20Java%20Cards.pdf>, 5 pages.
Nordin, B., “Match-On-Card Technology,” Precise™ Biometrics, White Paper, Apr. 2004, [online] [Retrieved on Jan. 7, 2007] Retrieved from theI nternet< U RL: http://www.ibia.org/membersadmin/whitepapers/pdf/ 17 IPrecise%20Match-on-Card%2Otechnolo!=)y.pdf>, 7 pages.
Pope, Oasis Digital Signature Services: Digital Signing without the Headaches, Internet Computing—IEEE, vol. 10, 2006, pp. 81-84.
Farouk, “Authentication Mechanisms in Grid Computing Environment; Comparative Study”, 2012, IEEE, p. 1-6.
Chen, et al. “On Enhancing Biometric Authentication with Data Protection.” KES2000. Fourth International Conference on Knowledge-Based Intelligent Engineering Systems and Allied Technologies. Proceedings (Cat. No. 00TH8516), vol. 1, 2000, pp. 249-252 vol. 1.
Govindan, G, et al. “Real Time Security Management Using RFID, Biometric and Smart Messages.” 2009 3rd International Conference on Anti-Counterfeiting, Security, and Identification in Communication, 2009, pp. 282-285.
Jeyaprakash, R, et al. “Secured Smart Card Using Palm Vein Biometric On-Card-Process.” 2008 International Conference on Convergence and Hybrid Information Technology, 2008, pp. 548-551.
Noore, A. “Highly Robust Biometric Smart Card Design.” IEEE Transactions on Consumer Electronics, vol. 46, No. 4, 2000, pp. 1059-1063.
Singh, Sweta, et al. “A Constraint-Based Biometric Scheme on ATM and Swiping Machine.” 2016 International Conference on Computational Techniques in Information and Communication Technologies (ICCTICT), 2016, pp. 74-79.
Anonymous, “IEEE 802.15.4-2006—Wikipedia, the free encyclopedia,” Wikipedia, last modified Mar. 21, 2009, retrieved from http://en.wikipedia.org/wiki/IEEE_802.15.4-2006 on Apr. 30, 2009, 5 pgs.
Apple et al., “Smart Card Setup Guide,” 2006, downloaded from http://manuals.info.apple.com/en_US/Smart_Card_Setup_Guide.pdf on or before May 3, 2012, 16 pgs.
Balanis, “Antenna Theory: A Review,” Jan. 1992, Proceedings of the IEEE, vol. 80, No. 1, p. 13.
Beaufour, “Personal Servers as Digital Keys,” Proceedings of the Second IEEE Annual Conference on Pervasive Computing and Communications (PERCOM'04), Mar. 14-17, 2004, pp. 319-328.
BlueProximity, “BlueProximity—Leave it—it's locked, come back, it's back too . . . ” Aug. 26, 2007, retrieved from http://blueproximity.sourceforge.net/viahttp://www.archive.org/ on or before Oct. 11, 2011, 1 pg.
Bohrsatom et al., “Automatically unlock PC when entering proximity,” Dec. 7, 2005, retrieved from http://salling.com/forums/viewtopic.php?t=3190 on or before Oct. 11, 2011, 3 pgs.
Brown, “Techniques for Privacy and Authentication in Personal Communication Systems,” Personal Communications, IEEE, Aug. 1995, vol. 2, No. 4, pp. 6-10.
Cisco Systems, Inc., “Antenna Patterns and Their Meaning,” 1992-2007, p. 10.
Costa, “Imation USB 2.0 Micro Hard Drive,” Nov. 22, 2005, retrieved from http://www.pcmag.com/article2/0,2817,1892209,00 asp on or before Oct. 11, 2011, 2 pgs.
Dagan, “Power over Ethernet (PoE) Midspan—The Smart Path to Providign Power for IP Telephony,” Product Manager, Systems, Aug. 2005, Power Dsine Inc., 28 pgs.
Derfler, “How Networks Work,” Bestseller Edition, 1996, Ziff-Davis Press, Emeryville, CA, all pages.
Giobbi, Specification of U.S. Appl. No. 60/824,758, filed Sep. 6, 2006, all pages.
Gralla, “How the Internet works,” Millennium Edition, 1999, Que Corporation, Indianapolis, IN, all pages.
Hendron, “File Security, Keychains, Encryptioin, and More with Mac OS X (10.3+)” Apr. 4, 2005, downloaded from http://www.johnhendron.net/documents/OSX_Security.pdf on or before May 3, 2012, 30 pgs.
IEEE Computer Society, “IEEE Std 802.15.4™—Part 15.4: Wireless Medium Access Control (MAC) and Physical Layer (PHY) Specifications for Low-Rate Wireless Personal Area Networks (LR-WPANs),” The Institute of Electrical and Electronics Engineers, Inc., New York, NY, Oct. 1, 2003, 679 pgs.
International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2007/011103, dated Nov. 11, 2008, 6 pages.
International Search Report and Written Opinion for International Application No. PCT/US05/00349, dated Mar. 19, 2008, 10 pgs.
International Search Report and Written Opinion for International Application No. PCT/US08/83060, dated Dec. 29, 2008, 9 pgs.
International Search Report and Written Opinion for International Application No. PCT/US08/87835, dated Feb. 11, 2009, 8 pgs.
International Search Report and Written Opinion for International Application No. PCT/US09/34095, dated Mar. 25, 2009, 11 pgs.
International Search Report and Written Opinion for International Application No. PCT/US2009/039943, dated Jun. 1, 2009, 9 pgs.
International Search Report and Written Opinion for International Application No. PCT/US2014/037609, dated Dec. 9, 2014, 13 pgs.
International Search Report received for PCT Patent Application No. PCT/US2001/049916, dated Apr. 25, 2002, 1 page.
Lee et al., “Effects of dielectric superstrales on a two-layer electromagnetically coupled patch antenna,” Antennas and Propagation Society International Symposium, Jun. 1989, AP-S. Digest, vol. 2, pp. 26-30, found at http://ieeexplore.ieee.org/stamp/stamp.jsp?tp=&arnumber=1347.
Muller, “Desktop Encyclopedia of the Internet,” 1999, Artech House Inc., Norwood, MA, all pages.
National Criminal Justice Reference Service, “Antenna Types,” Dec. 11, 2006, online at http://ncjrs.gov/pdfffiles1/nij/185030b.pdf, retrieved from http://web.archive.erg/web/*/http://www.ncjrs.gov/pdffiles1/nij/185030b.pdf on Jan. 12, 2011, 1 pg.
Nel et al., “Generation of Keys for use with the Digital Signature Standard (DSS),” Communications and Signal Processing, Proceedings of the 1993 IEEE South African Symposium, Aug. 6, 1993, pp. 6-11.
Nerd Vitiles, “magicJack: Could It Be the Asterisk Killer?” Aug. 1, 2007, retrieved from http://nerdvittles.com/index.php?p=187 on or before Oct. 11, 2011, 2 pgs.
Pash, “Automate proximity and location-based computer actions,” Jun. 5, 2007, retrieved from http://lifehacker.com/265822/automate-proximity-and-location+based-computer-actionson or before Oct. 11, 2011, 3 pgs.
SplashID, “SplashID—Secure Password Manager for PDA's and Smartphones,” Mar. 8, 2007, retrieved from http://www.splashdata/com/splashid/ via http://www.archive.org/ on or before Oct. 11, 2011, 2 pgs.
Srivastava, “Is internet security a major issue with respect to the slow acceptance rate of digital signatures,” Computer Law & Security Report, 2005, p. 392-404.
White, “How Computers Work,” Millennium Edition, 1999, Que Corporation, Indianapolis, IN, all pages.
Yoshida, “Content Protection Plan Targets Wireless Home Networks,” EE Times, Jan. 11, 2002, retrieved from www.eetimes.com/story/OEG20020111S0060 on Mar. 4, 2002, 2 pgs.
Dai et al., “Toward Blockchain-Based Accounting and Assurance”, 2017, Journal of Information Systems, pp. 5-21 (Year: 2017).
Bluetooth, www.bluetoothcom, Printed Jlllle I, 2000.
Content protection plan targets wireless home networks, www.eetimes.com, Jan. 11, 2002.
Liu et al. 2001. A Practical Guide to Biometric Security Technology. IT Professional 3, 1 (Jan. 2001), 27-32. DOI=10.1109/6294.899930 http://dx.doi.org/10.1109/6294.899930.
PCT International Search Report and Written Opinion, PCT/US05/07535, dated Dec. 6, 2005, 6 pages.
Smart Card Alliance Report, Contactless Technology for Secure Physical Access: Technology and Standsards Choices, Smart Card Alliance, Oct. 2002, p. 1-48.
Beaufour et al., “Personal servers as digital keys,” Proceedings of the Second IEEE Annual Conference on Pervasive Computing and Communications, 2004, pp. 319-328, doi: 10.1109/PERCOM.2004.1276869.
Callaway, Wireless Sensor Networks: Architectures and Protocols, Jan. 1, 2004, Auerbach Publications, 366 pgs.
Dvorak, IEEE 802.15.4 and Zigbee Overview, Sep. 27, 2005, Motorola, 26 pgs.
Hester et al., “neuRFon(TM) Netform: A Self-Organizing Wireless Sensor Network”, Oct. 14, 2002, Proceedings of the Eleventh International Conference on Computer Communications and Networks, pp. 364-369.
Honkanen et al., “Low End Extension for Bluetooth”, Sep. 19, 2004, Proceedings of the 2004 IEEE Radio and Wireless Conference, Atlanta, GA, pp. 199-202.
Jonker et al., “Digital rights management in consumer electronics products,” IEEE Signal Processing Magazine, vol. 21, No. 2, pp. 82-91, Mar. 2004, doi: 10.1109/MSP.2004.1276116.
Adams, “Designing with 802.15.4 and Zigbee,” presented at Industrial Wireless Applications Summit, San Diego, California, Mar. 9, 2004, 22 pgs.
Adams, “Meet the ZigBee Standard,” Sensors Online, Jun. 2003, 7 pgs., archived at https://web.archive.org/web/20031008191032/http:/sensorsmag.com/articles/0603/14/pf_main.shtml.
Adams, “Zigbee vital in industrial applications,” EE Times, Jul. 29, 2003, 3 pgs., archived at https://web.archive.org/web/20031013062940/http:/www.eetimes.com/story/OEG20030727S0002.
Blip Systems, “Mar. 8, 2004—Bluetooth at the office?” at least as early as Oct. 11, 2004, archived at https://web.archive.org/web/20041011094320/http:/www.blipsystems.com/Default.asp?ID=16&M=News&PID=25&NewsID=9.
Blip Systems, “BlipManager,” at least as early as May 17, 2004, 1 pg., archived at https://web.archive.org/web/20040517050728/http:/www.blipsystems.com/Default.asp?ID=11.
Blip Systems, “BlipMobility,” at least as early as Apr. 7, 2004, archived at https://web.archive.org/web/20040407212934/http:/www.blipsystems.com/Default.asp?ID=118.
Blip Systems, “BlipNet API,” at least as early as May 18, 2004, 1 pg., archived at https://web.archive.org/web/20040518060132/http:/www.blipsystems.com/Default.asp?ID=92.
Blip Systems, “BlipNet Explore a wireless world . . . of great opportunities,” brochure available Sep. 2002, 6 pgs., availabe online at https://web.archive.org/web/20031012184406/http:/www.blipsystems.com/products_blipnet.shtml.
Blip Systems, “BlipNet Technical Overview,” Mar. 2003, 30 pgs., archived at https://web.archive.org/web/20031012184406/http:/www.blipsystems.com/products_blipnet.shtml.
Blip Systems, “BlipNode,” at least as early as May 16, 2004, 1 pg., archived at https://web.archive.org/web/20040516001554/http:/www.blipsystems.com/Default.asp?ID=10.
Blip Systems, “BlipServer,” at least as early as May 17, 2004, 1 pg., archived at https://web.archive.org/web/20040517044955/http:/www.blipsystems.com/Default.asp?ID=9.
Blip Systems, “Bluetooth Networks: Products: Bluetooth infracture,” product description, at least as early as Oct. 2003, archived at https://web.archive.org/web/20031012184406/http:/www.blipsystems.com/products_blipnet.shtml.
Blip Systems, “Product Information—BlipNet—Presentation of BlipNet 1.0—A Bluetooth Access System,” Aug. 2002, 2 pgs., archived at https://web.archive.org/web/20031012184406/http:/www.blipsystems.com/products_blipnet.shtml.
Bluetooth Sig, Inc. “Specification of the Bluetooth System,” Version 12, Nov. 5, 2003, 82 pgs., archived at https://web.archive.org/web/20031119092849/http:/www.bluetooth.com/dev/spec.v12.asp.
Callaway, “Wireless Sensor Networks: Architectures and Protocols,” book description, Motorola Labs, Auerbach Publications, Aug. 26, 2003, 3 pgs., archived at https://web.archive.org/web/20031023101953/http:/www.crcpress.com/shopping_cart/products/product_detail.asp?sku=AU1823.
Chi et al., “Industrial Wireless Sensor Networking: A Market Dynamics Study,” ON World, Jun. 28, 2004, 5 pgs., archived at https://web.archive.org/web/20040710182216/http:/onworld.com:80/html/industrialwirelesssensor.htm.
Disclosed Anonymously (Method and Apparatus for Mobile Identity Authentication)., An IP.com Prior Art Database Technical IP.com No. IPCOM000194545D., IP.com Electronic Publication Date: Mar. 29, 2010 (Year: 2010).
Duflot et al., “A Formal Analysis of Bluetooth Device Discovery,” presented at the 1st International Symposium on Leveraging Applications of Formal Methods (ISOLA'04), Oct. 30-Nov. 2, 2004, Paphos, Cyprus, and published in the International Journal on Software Tools for Technology Transfer 8, pp. 621-632, 16 pgs., https://doi.org/10.1007/s10009-006-0014-x.
Eshed, “Bluetooth Wireless Technology Application for the Retail Market,” published at www.tadlys.com on May 2001, 8 pgs.
Freescale Semicondcutor, Inc., “Freescale Events,” see ZigBee Open House Event, Aug. 18, 2004, 6 pgs., archived at https://web.archive.org/web/20040909082726/https://www.freescale.com/webapp/sps/site/overview.jsp?nodeId=02XPgQ7JgbBqJQ#zigbee_openhouse_04.
Freescale Semiconductor, Inc., “Overview,” ZigBee General Information, at least as early as Aug. 17, 2004, 1 pg., archived at https://web.archive.org/web/20040817210006/http:/www.freescale.com/webapp/sps/site/overview.jsp?nodeId=02XPgQhHPRjdyB37087725.
Freescale Semiconductor, Inc., “ZigBeeTM,” Freescale Semiconductor Wireless Standards, at least as early as Aug. 18, 2004, 2 pgs., archived at https://web.archive.org/web/20040818075046/http:/www.freescale.com/webapp/sps/site/overview.jsp?nodeId=02XPgQhHPRjdyB.
Freescale Semiconductor, Inc., “ZigBeeTM,” Freescale Semiconductor Wireless Standards, at least as early as Jun. 11, 2004, 2 pgs., archived at https://web.archive.org/web/20040611051834/http:/e-www.motorola.com/webapp/sps/site/overview.jsp?nodeId=02XPgQhHPRjdyB.
Freescale Semiconductor, Inc., “Freescale's ZigBeeTM-ready Platform Wins Sensors Magazine Best of Sensors Expo Award,” Freescale Semiconductor Wireless, at least as early as Aug. 17, 2004, 1 pg., archived at https://web.archive.org/web/20040817203409mp_/http:/www.freescale.com/webapp/sps/site/overview.jsp?nodeId=02XPgQ6988.
Freescale Semiconductor, Inc., “ZigBee Alliance Successfully Concludes First Multi-node Network Test,” press release, Jul. 6, 2004, 2 pgs., archived at https://web.archive.org/web/20040717113733/http:/www.zigbee.org/documents/First-Multi-Node_Testing_FINAL_000.pdf.
Freescale Semiconductor, Inc., “ZigBeeTM Technology from Freescale,” Freescale Semiconductor, Inc. white paper, 2004, 4 pgs., archived at https://web.archive.org/web/20050513024652/http:/www.freescale.com/files/wireless_comm/doc/brochure/BRZIGBEETECH.pdf.
Freescale Semiconductor, Inc., “ZRP-1 : ZigBee-ready Platform,” at least as early as Oct. 19, 2005, 6 pgs., archived at https://web.archive.org/web/20051019122919/http://www.freescale.com/webapp/sps/site/prod_summaryjsp?code=ZRP-1&nodeId=02XPgQhCQ6m6cy7103.
Freescale Semiconductor, Inc., M68HC08 microcontroller ordering web page, at least as early as Aug. 17, 2004, 5 pgs., archived at https://web.archive.org/web/20040817014804/http:/www.freescale.com/webapp/sps/site/taxonomy.jsp?nodeId=01624684498634.
IBM Corporation, “Tadlys' Bluetooth Wireless Local Network for Corporate,” Wireless e-business, at least as early as May 6, 2004, 2 pgs., archived at https://web.archive.org/web/20040621130525/http://www.tadlys.com/media/downloads/Corporate%20PVDEE01005-3.pdf.
IBM Corporation, “Tadlys' Bluetooth Wireless Local Network for Hotspots,” Wireless e-business, at least as early as May 6, 2004, 2 pgs., archived at https://web.archive.org/web/20040508123915/http://www.tadlys.com/media/downloads/Hotspots%20PVDEE01006-3.pdf.
IEEE, “IEEE 802.15 WPANTM Task Group 4 (TG4)” exemplary web page, Aug. 24, 2004, 2 pgs., archived at https://web.archive.org/web/20040824085452/http:/www.ieee802.org/15/pub/TG4.html.
Korzeniowski, “First Intelligent, Wireless Consumer Devices About To Hit Market,” TechNewsWorld, Jul. 28, 2004, 3 pgs., archived at https://web.archive.org/web/20040821061130/http:/www.technewsworld.com/story/35376.html%20com/.
Malan, “Here come Wireless Sensors,” Machine Design, Jun. 10, 2004, 3 pgs., archived at https://web.archive.org/web/20040610131354/http:/wwww.machinedesign.com/ASP/viewSelectedArticle.asp?strArticleId=56796&strSite=MDSite&Screen=CURRENTISSUE.
MIT Computer Science and Artificial Intelligence Laboratory, “Cricket v2 User Manual,” Cricket Project, MIT Computer Science and Artificial Intelligence Lab, Cambridge, MA, Jan. 2005, 57 pgs., available online at https://web.archive.org/web/20041206144922/http:/cricket.csail.mit.edu/v2man.html.
MIT Computer Science and Artificial Intelligence Laboratory, “The Cricket Indoor Location System,” at least as early as Nov. 19, 2004, 6 pgs., archived at https://web.archive.org/web/20041119183049/http://cricket.csail.mit.edu/.
Motorola, Inc., “Motorola First to Demonstrate ZigBee 2.4 GHz Wireless Networking Technology,” press release, Mar. 27, 2003, 2 pgs., archived at https://web.archive.org/web/20050205053308/http:/www.motorola.com/mediacenter/news/detail/0,1958,2743_2228_23,00.html.
Priyantha, “The Cricket Indoor Location System,” Ph.D. thesis submitted to Department of Electrical Engineering and Computer Science, Massachusetts Institute of Technology, Jun. 2005, 199 pgs.
Rodriguez et al., “In-building location using Bluetooth,” Proceedings of the International Workshop on Wireless Ad-Hoc Networks (IWWAN 2005), May 23-26, 2005, London, England, 7 pgs.
Tadlys Ltd., “‘Hotspot’ Gaming Arcade,” at least as early as Dec. 9, 2004, 2 pgs., archived at https://web.archive.org/web/20041209234518/http://www.tadlys.com/media/downloads/Tadlys_gaming_arcade.pdf.
Tadlys Ltd., “About Tadlys,” at least as early as Apr. 5, 2001, 1 pg., archived at https://web.archive.org/web/20010405044249/http:/www.tadlys.com/about.html.
Tadlys Ltd., “An Advertisers' Dream—From direct marketing to sales,” Nov. 2004, 2 pgs., archived at https://web.archive.org/web/20041101092944/http://www.tadlys.com/media/downloads/m-commerce_app.pdf.
Tadlys Ltd., “Bluetooth Glossary,” at least as early as Jun. 2004, 12 pgs., archived at https://web.archive.org/web/20040531082349/http://www.tadlys.com/pages/Downloads_content.asp?intGlobalId=1.
Tadlys Ltd., “First Demo of Distribution and Redemption of e-Coupons over Bluetooth,” Tadlys Company News and Events, Jun. 5, 2001, 1 pg., archived at https://web.archive.org/web/20040601051516/http://tadlys.com/Pages/news_content.asp?iGlobalID=17.
Tadlys Ltd., “Indoor Location Networks,” at least as early as Apr. 3, 2004, 1 pg., archived at https://web.archive.org/web/20040403200221/http:/www.tadlys.com/Pages/Product_content.asp?iGlobalId=2.
Tadlys Ltd., “Operator Systems,” at least as early as Nov. 1, 2004, 2 pgs., archived at https://web.archive.org/web/20041101101402/http://www.tadlys.com/media/downloads/operator_network.pdf.
Tadlys Ltd., “Tadlys Announces Range of Bluetooth Access Network Solutions,” Tadlys Company News and Events, Jan. 22, 2001, 1 pg., archived at https://web.archive.org/web/20040624122319/http://www.tadlys.com/Pages/news_content.asp?iGlobalID=16.
Tadlys Ltd., “Tadlys' Wire free networking solutions,” Feb. 2001, 2 pgs., archived at https://web.archive.org/web/20010204012700/http:/www.tadlys.com/solutions.html.
Tadlys Ltd., “Wireless hospital network,” at least as early as Jul. 1, 2004, 2 pgs., archived at https://web.archive.org/web/20040701105046/http://www.tadlys.com/media/downloads/tadlys_hospital_wireless_network.pdf.
Tadlys Ltd., “Wireless Museum Information,” at least as early as Dec. 12, 2005, 2 pgs., archived at https://web.archive.org/web/20051212162456/http://www.tadlys.com/media/downloads/Tadlys_wireless_museum_network.pdf.
Tadlys Ltd., “Corporate Systems,” at least as early as Nov. 1, 2004, 2 pgs., archived at https://web.archive.org/web/20041101095441/http://www.tadlys.com/media/downloads/Corporate_network.pdf.
Schneier, Applied Cryptography, Second Edition: Protocols, Algorithms, and Source Doe in C, Jan. 1, 1996, John Wiley & Sons, Inc., 1027 pgs.
Thongthammachart et al., “Bluetooth Enables In-door Mobile Location Services,” Proceedings of the 57th IEEE Semiannual Vehicular Technology Conference, Apr. 22-25, 2003, 5 pgs.
University of Birmingham, “PRISM: Probabilistic Symbolic Model Checker,” at least as early as Aug. 3, 2004, 3 pgs., archived at https://web.archive.org/web/20040803193058/http://www.cs.bham.ac.uk/˜dxp/prism/casestudies/index.html.
Weissman, “Indoor Location,” Tadlys Ltd. white paper, at least as early as Oct. 31, 2004, 15 pgs., archived at https://web.archive.org/web/20041031125859/http:/www.tadlys.com/media/downloads/Indoors_Location_Systems.pdf.
Zigbee Alliance, “Welcome to the ZigBeeTM Alliance,” exemplary web page, at least as early as Sep. 24, 2004, 2 pgs., archived at https://web.archive.org/web/20040924045517/http://zigbee.org/.
Zigbee Alliance, “ZigBee Specification,” ZigBee Document 053474r06, Version 1.0, Dec. 14, 2004, 378 pgs.
Zigbee Alliance, “The ZigBeeTM Buzz Is Growing: New Low-Power Wireless Standard Opens Powerful Possibilities,” Electronic Design, Jan. 12, 2004, 12 pgs., archived at https://web.archive.org/web/20040411172015/http:/www.elecdesign.com/Files/29/7186/7186_01.pdf.
Zigbee Alliance, “ZigBeeTM Positioned to Drive Wireless Networking in Building Automation, Industrial and Residential Control and Sensors Markets in 2004,” press release, Feb. 17, 2004, 3 pgs., archived at https://web.archive.org/web/20040423220244/http:/www.zigbee.org/documents/04036r5ZB_MWG-Momentum-Release_FINAL.pdf.
David et al., Security Issues for Contactless Smart Cards, Sep. 1, 1997, conference paper, available online at https://link.springer.com/chapter/10.1007/BFb0054029, 6 pgs.
Kuhn et al., Introduction to Public Key Technology and the Federal PKI Infrastructure, Feb 26, 2001, National Institute of Standards and Technology, 54 pgs.
Petition for Inter Partes Review of U.S. Pat. No. 10,698,989, Aug 26, 2021, 3356 pgs.
Petition for Inter Partes Review of U.S. Pat. No. 8,352,730, Aug 26, 2021, 2450 pgs.
Petition for Inter Partes Review of U.S. Pat. No. 9,049,188, Aug 26, 2021, 800 pgs.
Petition for Inter Partes Review of U.S. Pat. No. 9,235,700, Aug 26, 2021, 466 pgs.
Petition for Inter Partes Review of U.S. Pat. No. 9,298,905, Aug 26, 2021, 1941 pgs.
Request for Ex Parte Reexamination of U.S. Pat. No. 10,698,989, Jun 8, 2022, 1505 pgs.
Request for Ex Parte Reexamination of U.S. Pat. No. 8,352,730, Jun 8, 2022, 1401 pgs.
Request for Ex Parte Reexamination of U.S. Pat. No. 9,298,905, Jun 8, 2022, 1123 pgs.
Smart Card Alliance, Contactless Payment and the Retail Point of Sale: Applications, Technologies and Transaction Models, Mar 1, 2003, a Smart Card Alliance Report, 50 pgs.
Smart Card Alliance, Smart Card Alliance—The Alliance, Jan 22, 2001, http://www.smartcardalliance.org, 1 pg.
Agourare et al., “Authentication and location control via RFID analysis,”2009 IEEE Conference on Emerging Technologies & Factory Automation, Sep. 1, 2009, 8 pgs.

Related Publications (1)

	Number	Date	Country
	20170085564 A1	Mar 2017	US

Provisional Applications (5)

Number	Date	Country
60894608	Mar 2007	US
60824758	Sep 2006	US
60838788	Aug 2006	US
60798843	May 2006	US
60798172	May 2006	US

Continuations (1)

	Number	Date	Country
Parent	11745249	May 2007	US
Child	15364039		US

Single step transaction authentication using proximity and biometric input

Information

Patent Number

Date Filed

Date Issued

Inventors

Original Assignees

Examiners

Agents

CPC

Field of Search

CPC

International Classifications

Disclaimer

Term Extension

Abstract