The present application is related to co-pending U.S. patent application Ser. No. 14/596,508, filed Jan. 14, 2015, entitled “System and Method for Requesting Reconciliation of Electronic Transaction Records for Enhanced Security”; U.S. patent application Ser. No. 14/596,472, filed Jan. 14, 2015, entitled “System and Method for Comparing Electronic Transaction Records for Enhanced Security”; U.S. patent application Ser. No. 14/596,420, filed Jan. 14, 2015, entitled “System and Method for Reconciling Electronic Transaction Records for Enhanced Security”; and U.S. patent application Ser. No. 14/596,572, filed Jan. 14, 2015, entitled “Smart Card Systems Comprising a Card and a Carrier”; U.S. patent application Ser. No. 14/603,703, filed Jan. 23, 2015, entitled “Biometric Device Utilizing Finger Sequence for Authentication,” the disclosures of which are incorporated herein by reference.
The present disclosure relates generally to smart cards, and more particularly, smart card systems and methods utilizing multiple Answer to Reset (ATR) messages.
Electronic transactions, such as credit card transactions, can be conducted using smart cards. A smart card is a device that includes an embedded integrated circuit chip that can be either a secure processing module (e.g., microprocessor, microcontroller or equivalent intelligence) with an internal or external memory or a memory chip alone. The smart card can be connected to a reader via direct physical contact or via a contactless (e.g., RF) interface. Smart cards come in many different form factors, including plastic cards, fobs, SIM cards used in mobile phones, and USB tokens. Smart cards can provide identification, authentication, data storage, and application processing, as well as serving as credit or ATM debit cards, phone or fuel cards, and high-security access-control cards for granting access to a building or computer.
Some smart cards and the corresponding reader terminals conform to international standards such as ISO 7816 and ISO 14443 that specify physical characteristics and various communication and security protocols. In the ISO 7816 standard, for example, communication between a reader (master) and a smart card (slave) takes place over a single bi-directional, half-duplex data line. Parameters such as protocol format, type of smart card, baud rate and other electrical parameters are read out of the smart card right after reset. This is known as the Answer to Reset, or ATR. Based on the information given in the ATR, the reader can adapt to the transmission format supported by the card. Similar messages are utilized in the early communication between ISO 14443 compliant terminals and smart cards.
When a smart card is inserted into the reader, all the contacts are disconnected from the reader, including ground. The reason for this is that the contacts in the terminal slide over the smart card contacts while the card is inserted. Applying power to the wrong pins could in theory damage the card or the reader. When the card is properly inserted, there is usually an electrical contact that breaks connection, indicating to the reader that the card is fully inserted. Once inserted, the reader initiates a power on and reset sequence. The interface is responsible for the timing of the sequence. A conventional ISO smart card startup process is illustrated in the timing diagram of
The conventional startup and transaction process utilizing a single ATR message illustrated in
According to various embodiments of the disclosed technology, a method of facilitating communication between a smart card and a terminal is provided, comprising receiving a first ATR message at a first time that is within a first predetermined clock cycles after a reset; waiting for a second ATR message indicative of a successful biometric authentication from the smart card; receiving a second ATR message at a second time that is within a second predetermined clock cycles after the first time; and exchanging transaction-related messages with the smart card.
According to various embodiments of the disclosed technology, a method of facilitating communication between a smart card and a terminal is provided, comprising sending a first answer-to-reset (ATR) message at a first time that is within a first predetermined clock cycles after a reset; performing a biometric authentication of a user requesting a transaction involving the smart card; determining that the biometric authentication was successful; sending a second ATR message to the terminal at a second time that is within a second predetermined clock cycles after the first time; and exchanging transaction-related message with the terminal.
According to various embodiments of the disclosed technology, a terminal for communicating with a smart card is provided, comprising an interface configured to be coupled to a smart card; a processor coupled to the interface and configured to: wait for a first answer-to-reset (ATR) message from the smart card after a reset; receive the first ATR message via the interface at a first time that is within a first predetermined clock cycles after the reset; wait for a second ATR message indicative of a successful biometric authentication from the smart card; receive the second ATR message via the interface at a second time that is within a second predetermined clock cycles after the first time; and exchange transaction-related messages with the smart card via the interface.
According to various embodiments of the disclosed technology, a smart card is provided, comprising an interface configured to be coupled to a terminal; a biometric module coupled to the processor and configured to obtain a biometric signature of a user requesting a transaction; and a processor coupled to the interface and the biometric module and configured to: send a first answer-to-reset (ATR) message to the terminal via the interface at a first time that is within a first predetermined clock cycles after a reset; send a second ATR message indicative of a successful biometric authentication to the terminal via the interface at a second time that is within a second predetermined clock cycles after the first time; and exchange transaction-related messages with the terminal via the interface.
Other features and aspects of the disclosed technology will become apparent from the following detailed description, taken in conjunction with the accompanying drawings, which illustrate, by way of example, the features in accordance with embodiments of the disclosed technology. The summary is not intended to limit the scope of any inventions described herein, which are defined solely by the claims attached hereto.
The technology disclosed herein, in accordance with one or more various embodiments, is described in detail with reference to the following figures. The drawings are provided for purposes of illustration only and merely depict typical or example embodiments of the disclosed technology. These drawings are provided to facilitate the reader's understanding of the disclosed technology and shall not be considered limiting of the breadth, scope, or applicability thereof. It should be noted that for clarity and ease of illustration these drawings are not necessarily made to scale.
The figures are not intended to be exhaustive or to limit the invention to the precise form disclosed. It should be understood that the invention can be practiced with modification and alteration, and that the disclosed technology be limited only by the claims and the equivalents thereof.
Embodiments of the technology disclosed herein are directed toward a system for and method of facilitating communication between a biometric smart card and a terminal (e.g., a smart card reader). More particularly, the various embodiments of the technology disclosed herein relate to smart card systems and methods utilizing multiple ATR messages.
In the following detailed description, numerous specific details are set forth to provide a full understanding of various aspects of the subject disclosure. It will be apparent, however, to one ordinarily skilled in the art that various aspects of the subject disclosure may be practiced without some of these specific details. In other instances, well-known structures and techniques have not been shown in detail to avoid unnecessarily obscuring the subject disclosure.
Before describing the technology disclosed in detail, it is useful to describe an example environment within which the technology can be implemented.
The PTD 110 can conduct various types of electronic transactions with the TPS 130 via the interface device 120. For financial transaction applications, the PTD 110 can be a smart payment card such as a smart credit, debit, and/or prepaid card, or a smartphone with a payment transaction application. The TPS 130 can be a payment processing system of a merchant (e.g., Target®), a bank (e.g., Bank of America®), or a card issuer (e.g., Visa®). The interface device 120 can be a point of sale (POS) terminal that can communicate with the PTD 110 using a contact method (e.g., matching male and female contact pads) or a contactless method (e.g., RFID, Bluetooth, NFC, Wi-Fi, ZigBee).
In some embodiments, the PTD 110 may communicate directly with the TPS 130 without an interface such as the interface device 120. For example, the PTD 110 can be equipped with a transceiver that can communicate with a cellular network such as a 3G UMTS or 4G LTE network. In some embodiments, the PTD 110 can be a smart phone capable of communicating with a cellular network.
For access control applications, the PTD 110 can be a smart access card, smart fob, or smart key for providing access to a facility or computer. For example, a PTD 110 in accordance with the present disclosure may be required to gain access to one or more of a secured facility, specific areas within a facility, a particular computing device or piece of equipment, a computer network, or a combination thereof. The TPS 130 can be a server in a central computer system, or a dedicated access controller that controls access to a facility or computer. Interface device 120 can be a card, fob, or key reader that can communicate with the PTD 110 using a contact method (e.g., contact pads) or a contactless method (e.g., RFID, Bluetooth, NFC, Wi-Fi, ZigBee).
In various embodiments, interface 120 may communicate with TPS 130 over network 140. Network 140 may be any communications network, such as a cellular or data network, a satellite network, an intranet, an extranet, a virtual private network (VPN), a local area network (LAN), a wireless LAN (WLAN), a wide area network (WAN), a personal area network (PAN), a portion of the Internet, a portion of the Public Switched Telephone Network (PSTN), or any combination thereof. Accordingly, network 140 may employ various communication media, such as a coaxial cable, fiber optic cable system, Ethernet, radio waves, etc.
In the illustrated example of
There are many examples of biometric devices with which the present disclosure can be implemented. One example is the biometric smart card illustrated in
Smart card 200 includes a transaction interface 216. Transaction interface 216 is communicatively coupled to processing module 212. In various embodiments, transaction interface 216 is configured to communicate with TPS 130 through interface device 120 described above with respect to
In other embodiments, smart card 200 may include additional components to allow direct communication with TPS 130 without the need of interface device 120. Smart card 200 may include components required to allow RFID, Bluetooth, NFC, Wi-Fi, or ZigBee communication with TPS 130.
As shown in
Controller 226 is a processing module configured to execute authentication application programming stored in memory 224. For ease of discussion, the controller 226 and the rest of the disclosure will describe the technology in regards to biometric authentication utilizing fingerprint images. Although described as such, the technology disclosed herein is applicable for any biometric authentication process, including authentication based on a user's iris scan, voice recognition, DNA sampling, or other biometric signature. The description should not be interpreted to limit the scope of the technology disclosed to any particular biometric authentication process.
In various embodiments, controller 226 may accept a fingerprint image input from scanner 222 and perform additional processing (e.g., extracting, focusing, aligning, rotating, scaling, normalizing, filtering and/or formatting) operations on the image to generate a fingerprint template that can be compared to a stored fingerprint template associated with an authorized (e.g., registered) user. In other embodiments, controller 226 can receive an already processed fingerprint template from scanner 222. Controller 226 is coupled to processing module 212 through connection 228. In various embodiments, controller 226 may be a separate hardware processing module from processing module 212. In various embodiments, controller 226 may be implemented in software, such as a virtual machine (VM) executed using processing module 212. In such an embodiment, additional security features may be implemented within processing module 212, such as partitioning between the VM and the card operating system to ensure that no unauthorized access to the controller module occurs. In various embodiments, the authentication application programming executed by controller 226 may be stored in memory 214 and accessible by controller 226 through processing module 212. In various embodiments, controller 226 may have direct access to memory 214.
Biometric sensor 222 is a biometric reader or scanner capable of reading or scanning a user's fingerprints. As discussed above, the biometric input from scanner 222 can be sent directly to controller 226 in order to allow controller 226 to perform formatting operations to generate a fingerprint template. In various embodiments, scanner 222 may be capable of formatting the fingerprint image prior to sending the fingerprint image to controller 226. As discussed above, the biometric authentication process may utilize any biometric signature unique to the user. Accordingly, in embodiments utilizing a different biometric signature for authentication, the biometric sensor 222 may be a sensor other than a fingerprint scanner, such as an iris scanner, a microphone, a blood collector, scent sensor, or other biometric-recording module.
Other biometric devices with which the present disclosure may be implemented include smart fobs, smart keys, and mobile devices, among others. For ease of discussion, the authentication process and embodiments thereof are discussed with regards to the biometric-enabled smart card shown in
To biometrically authenticate the identity of a person requesting a new transaction involving the biometric smart card 200 utilizing fingerprint authentication, a processor in the smart card 200 can perform a comparison and a matching of one or more fingerprint templates associated with the person (the templates generated from fingerprint images received from biometric sensor 222) to one or more fingerprint templates associated with a registered user stored in a memory (e.g., memory 224 or memory 214). In some embodiments, the controller 226 performs both the generation of fingerprint templates associated with the person and the comparison and matching of the fingerprint templates to the stored fingerprint templates associated with the registered user. In other embodiments, the controller 226 performs the generation of fingerprint templates associated with the person and the processing module 212 performs the comparison and matching of the fingerprint templates to the stored fingerprint templates associated with the registered user.
In various embodiments, smart card 200 may have only a single component for processing both the transaction and authentication functions of smart card 200. In various embodiments, this single processing component may be processing module 212, and processing module 212 may be configured to execute both transaction applications and the functions of controller 226 described above. This eliminates the need for multiple processing units on the card and lowers the complexity of the design. In those embodiments employing a single processing component, the single processing component performs the generation of fingerprint templates associated with a person requesting a new transaction and the comparison and matching of the fingerprint templates to stored fingerprint templates associated with a registered user.
PTD interface 126 and transaction interface 216 on smart card 200 provide a communication link between smart card 200 and interface device 120. Using this communication link, smart card 200 can communicate authentication- and/or transaction-related data with interface device 120 and/or TPS 130. In various embodiments, interface device 120 may be a terminal and PTD interface 126 may be a physical card reader or scanner. In such embodiments, card 200 interacts with interface device 120 by inserting smart card 200 into the card reader, or scanning transaction interface 216 of smart card 200 with the card scanner of interface device 120. In other embodiments, smart card 200 may include components necessary to enable contactless transactions, such as transceivers required for RFID, Bluetooth, NFC, or ZigBee communication. In various embodiments, interface device 120 supplies power to smart card 200 through this physical connection. In other embodiments, card 200 may include on on-board power source to supply power to the card components. In still other embodiments, smart card 200 may include wires or coils configured to receive power through induction principles, such as induction through NFC. For ease of discussion, smart card 200 was used in descripting transaction system 300. This use, however, should not be read to limit the scope of the present disclosure. Transaction system 300 may be implemented in the same fashion using any PTD 110.
At t=T1, a biometric smart card 200 is inserted into a terminal 120 through a connection made between the interface 126 at the terminal 120 and the interface 216 at the smart card 200. In various embodiments, the interfaces 126 and 216 comprise a pair of matching (e.g., male and female) contact pads. The contact pads can include a pair of matching Input or Output (I/O) pads for exchanging (i.e., transmitting and receiving) various messages between the interface and the smart card. In some embodiments, the messages are exchanged through an I/O pad in a serial fashion during either a transmission mode or a reception mode. The contact pads can also include a pair of matching pads for transmitting a reset (RST) signal from the terminal 120 to the smart card 200. The contact pads can also include a pair of matching pads for providing power from the terminal 120 to the smart card 200.
At t=T2, power is provided to the smart card 200 by applying a voltage Vcc to the power pads. In the illustrated example, the I/O pads are also made ready by having them pulled high. At t=T3, a clock (CLK) is started. Subsequent timing windows, including the arrivals of ATR messages, are measured in terms of clock cycles associated with the clock. At t=T4, a reset (RST) signal is indicated within an initial number of clock cycles (N0) after the clock is started at T3. In the illustrated embodiment, the RST signal is indicated by having the RST signal transition from low to high. In certain embodiments, the RST signal is provided from the terminal 120 to the smart card 200 via a reset pad. In other embodiments, the RST signal is internally generated at the smart card 200.
At t=T5, a first answer-to-reset (ATR) message is transmitted from the smart card 200 to the terminal 120 via the I/O pads within a first predetermined number (N1) of cycles after the reset is indicated at T4. In various embodiments, the first ATR message can include one or more data items (indicated as ATR data #1) indicative of protocol format, type of smart card, and/or baud rate. For contactless transactions, the smart card 200 may transmit an answer-to-select (ATS) or other message indicative of a request by a contactless smart card to conduct a transaction. The compliant terminal would then construct the ATR message based on the ATS or other message transmitted by the contactless smart card 200.
After transmission of the first ATR message at t=T4, a user requesting the transaction involving the smart card 200 is asked to input a biometric signature by, for example, presenting a finger or an iris on a biometric scanner. The biometric scanner can be part of the smart card 200 or the terminal 120. At t=T6, a biometric authentication determination based on the biometric signature of the user received from the biometric scanner. In various embodiments, the determination can involve comparing a biometric template generated from a biometric signature received from a biometric reader/scanner with a reference biometric template associated with an authorized user stored in a memory.
At t=T7, a second ATR message is transmitted from the smart card 200 to the terminal 120 via the I/O pads within a second predetermined number of clock cycles (N2) after T5. In some embodiments, the second ATR message can include data items (indicated as ATR data #2) indicating whether the biometric authentication of the user was successful. In other embodiments, the reception of the second ATR itself indicates that the biometric authentication was successful. In other words, if the biometric authentication was not successful, the smart card does not send a second ATR message to the terminal. Either way, if the biometric authentication was successful, the smart card 200 and the terminal 120 exchange transaction-related messages via the I/O pads within a third predetermined number of allowed clock cycles (N4) after T7. At t=T8, the communication link between the smart card 200 and the terminal 120 is disconnected. In the illustrated example, power (Vcc) applied to the power pad is disabled, the clock is stopped, and the RST and I/O signals become low.
On the other hand, if, at the query state 506, it is determined that a first ATR message is received (e.g., via an I/O pad) at a first time (e.g., T5 of
On the other hand, if, at the query state 510, a second ATR message indicative of a successful biometric authentication of the user is received at a second time that is within Nx clock cycles after the first time, the process 500 proceeds to operation 512 where the terminal 120 exchanges transaction-related messages with the smart card 200 during a third predetermined number of cycles (e.g., N3 of
The process 600 proceeds to operation 604 where the smart card 200 sends a first ATR message to the terminal 120 (e.g., via an I/O pad) at a first time (e.g., T5 of
Those skilled in the art shall understand that a smart card system utilizing two ATR messages in accordance with the present disclosure can perform a biometric authentication of a user without having the system timed out and the communication link between the terminal and the smart card disconnected. In this regard, the value of N2 clock cycles and the corresponding allowed time between the two ATR messages should be set sufficiently high to permit the biometric authentication. In various embodiments, the allowed time can be set to a value between 5 seconds to 30 seconds, depending on the type of biometric authentication employed. In some embodiments, more than two ATR messages may be utilized. A smart card system may employ multiple biometric authentications such as, for example, a fingerprint-based authentication and a voice-based authentication. In such a system, three ATR messages may be provided such that the second ATR message is sent after a successful fingerprint-based biometric authentication and the third ART message is sent after a successful voice-based biometric authentication.
As used herein, the term set may refer to any collection of elements, whether finite or infinite. The term subset may refer to any collection of elements, wherein the elements are taken from a parent set; a subset may be the entire parent set. The term proper subset refers to a subset containing fewer elements than the parent set. The term sequence may refer to an ordered set or subset. The terms less than, less than or equal to, greater than, and greater than or equal to, may be used herein to describe the relations between various objects or members of ordered sets or sequences; these terms will be understood to refer to any appropriate ordering relation applicable to the objects being ordered.
As used herein, the term module might describe a given unit of functionality that can be performed in accordance with one or more embodiments of the technology disclosed herein. As used herein, a module might be implemented utilizing any form of hardware, software, or a combination thereof. For example, one or more processors, controllers, ASICs, PLAs, PALs, CPLDs, FPGAs, logical components, software routines or other mechanisms might be implemented to make up a module. In implementation, the various modules described herein might be implemented as discrete modules or the functions and features described can be shared in part or in total among one or more modules. In other words, as would be apparent to one of ordinary skill in the art after reading this description, the various features and functionality described herein may be implemented in any given application and can be implemented in one or more separate or shared modules in various combinations and permutations. Even though various features or elements of functionality may be individually described or claimed as separate modules, one of ordinary skill in the art will understand that these features and functionality can be shared among one or more common software and hardware elements, and such description shall not require or imply that separate hardware or software components are used to implement such features or functionality.
Where components or modules of the technology are implemented in whole or in part using software, in one embodiment, these software elements can be implemented to operate with a computing or processing module capable of carrying out the functionality described with respect thereto. One such example computing module is shown in
Referring now to
Computing module 700 might include, for example, one or more processors, controllers, control modules, or other processing devices, such as a processor 704. Processor 704 might be implemented using a general-purpose or special-purpose processing engine such as, for example, a microprocessor, controller, or other control logic. In the illustrated example, processor 704 is connected to a bus 702, although any communication medium can be used to facilitate interaction with other components of computing module 700 or to communicate externally.
Computing module 700 might also include one or more memory modules, simply referred to herein as main memory 706. For example, preferably random access memory (RAM) or other dynamic memory, might be used for storing information and instructions to be executed by processor 704. Main memory 706 might also be used for storing temporary variables or other intermediate information during execution of instructions to be executed by processor 704. Computing module 700 might likewise include a read only memory (“ROM”) or other static storage device coupled to bus 702 for storing static information and instructions for processor 704.
The computing module 700 might also include one or more various forms of information storage mechanism 708, which might include, for example, a media drive 710 and a storage unit interface 714. The media drive 710 might include a drive or other mechanism to support fixed or removable storage media 712. For example, a hard disk drive, a floppy disk drive, a magnetic tape drive, an optical disk drive, a CD or DVD drive (R or RW), or other removable or fixed media drive might be provided. Accordingly, storage media 712 might include, for example, a hard disk, a floppy disk, magnetic tape, cartridge, optical disk, a CD or DVD, or other fixed or removable medium that is read by, written to or accessed by media drive 710. As these examples illustrate, the storage media 712 can include a computer usable storage medium having stored therein computer software or data.
In alternative embodiments, information storage mechanism 708 might include other similar instrumentalities for allowing computer programs or other instructions or data to be loaded into computing module 700. Such instrumentalities might include, for example, a fixed or removable storage unit 716 and an interface 714. Examples of such storage units 716 and interfaces 714 can include a program cartridge and cartridge interface, a removable memory (for example, a flash memory or other removable memory module) and memory slot, a PCMCIA slot and card, and other fixed or removable storage units 716 and interfaces 714 that allow software and data to be transferred from the storage unit 716 to computing module 700.
Computing module 700 might also include a communications interface 720. Communications interface 720 might be used to allow software and data to be transferred between computing module 700 and external devices. Examples of communications interface 720 might include a modem or softmodem, a network interface (such as an Ethernet, network interface card, WiMedia, IEEE 802.XX or other interface), a communications port (such as for example, a USB port, IR port, RS232 port Bluetooth® interface, or other port), or other communications interface. Software and data transferred via communications interface 720 might typically be carried on signals, which can be electronic, electromagnetic (which includes optical) or other signals capable of being exchanged by a given communications interface 720. These signals might be provided to communications interface 720 via a channel 722. This channel 722 might carry signals and might be implemented using a wired or wireless communication medium. Some examples of a channel might include a phone line, a cellular link, an RF link, an optical link, a network interface, a local or wide area network, and other wired or wireless communications channels.
In this document, the terms “computer program medium” and “computer usable medium” are used to generally refer to media such as, for example, memory 706, storage unit 716, media 712, and channel 722. These and other various forms of computer program media or computer usable media may be involved in carrying one or more sequences of one or more instructions to a processing device for execution. Such instructions embodied on the medium, are generally referred to as “computer program code” or a “computer program product” (which may be grouped in the form of computer programs or other groupings). When executed, such instructions might enable the computing module 700 to perform features or functions of the disclosed technology as discussed herein.
While various embodiments of the disclosed technology have been described above, it should be understood that they have been presented by way of example only, and not of limitation. Likewise, the various diagrams may depict an example architectural or other configuration for the disclosed technology, which is done to aid in understanding the features and functionality that can be included in the disclosed technology. The disclosed technology is not restricted to the illustrated example architectures or configurations, but the desired features can be implemented using a variety of alternative architectures and configurations. Indeed, it will be apparent to one of skill in the art how alternative functional, logical or physical partitioning and configurations can be implemented to implement the desired features of the technology disclosed herein. Also, a multitude of different constituent module names other than those depicted herein can be applied to the various partitions. Additionally, with regard to flow diagrams, operational descriptions and method claims, the order in which the steps are presented herein shall not mandate that various embodiments be implemented to perform the recited functionality in the same order unless the context dictates otherwise.
Although the disclosed technology is described above in terms of various exemplary embodiments and implementations, it should be understood that the various features, aspects and functionality described in one or more of the individual embodiments are not limited in their applicability to the particular embodiment with which they are described, but instead can be applied, alone or in various combinations, to one or more of the other embodiments of the disclosed technology, whether or not such embodiments are described and whether or not such features are presented as being a part of a described embodiment. Thus, the breadth and scope of the technology disclosed herein should not be limited by any of the above-described exemplary embodiments.
Terms and phrases used in this document, and variations thereof, unless otherwise expressly stated, should be construed as open ended as opposed to limiting. As examples of the foregoing: the term “including” should be read as meaning “including, without limitation” or the like; the term “example” is used to provide exemplary instances of the item in discussion, not an exhaustive or limiting list thereof; the terms “a” or “an” should be read as meaning “at least one,” “one or more” or the like; and adjectives such as “conventional,” “traditional,” “normal,” “standard,” “known” and terms of similar meaning should not be construed as limiting the item described to a given time period or to an item available as of a given time, but instead should be read to encompass conventional, traditional, normal, or standard technologies that may be available or known now or at any time in the future. Likewise, where this document refers to technologies that would be apparent or known to one of ordinary skill in the art, such technologies encompass those apparent or known to the skilled artisan now or at any time in the future.
The presence of broadening words and phrases such as “one or more,” “at least,” “but not limited to” or other like phrases in some instances shall not be read to mean that the narrower case is intended or required in instances where such broadening phrases may be absent. The use of the term “module” does not imply that the components or functionality described or claimed as part of the module are all configured in a common package. Indeed, any or all of the various components of a module, whether control logic or other components, can be combined in a single package or separately maintained and can further be distributed in multiple groupings or packages or across multiple locations.
Additionally, the various embodiments set forth herein are described in terms of exemplary block diagrams, flow charts and other illustrations. As will become apparent to one of ordinary skill in the art after reading this document, the illustrated embodiments and their various alternatives can be implemented without confinement to the illustrated examples. For example, block diagrams and their accompanying description should not be construed as mandating a particular architecture or configuration.
Number | Name | Date | Kind |
---|---|---|---|
4453074 | Weinstein et al. | Jun 1984 | A |
4582985 | Loefberg | Apr 1986 | A |
4725719 | Oncken et al. | Feb 1988 | A |
4747147 | Sparrow | May 1988 | A |
4910521 | Mellon | Mar 1990 | A |
4993068 | Piosenka et al. | Feb 1991 | A |
5175416 | Mansvelt et al. | Dec 1992 | A |
5180901 | Hiramatsu | Jan 1993 | A |
5180902 | Schick et al. | Jan 1993 | A |
5193114 | Moseley et al. | Mar 1993 | A |
5245329 | Gokcebay | Sep 1993 | A |
5259649 | Shomron | Nov 1993 | A |
5321751 | Ray et al. | Jun 1994 | A |
5438184 | Roberts et al. | Aug 1995 | A |
5461217 | Claus et al. | Oct 1995 | A |
5513272 | Bogosian et al. | Apr 1996 | A |
5521363 | Tannenbaum | May 1996 | A |
5521966 | Friedes et al. | May 1996 | A |
5534857 | Laing et al. | Jul 1996 | A |
5539825 | Akiyama et al. | Jul 1996 | A |
5541985 | Ishii | Jul 1996 | A |
5559504 | Itsumi et al. | Sep 1996 | A |
5559887 | Davis et al. | Sep 1996 | A |
5577121 | Davis et al. | Nov 1996 | A |
5578808 | Taylor et al. | Nov 1996 | A |
5581630 | Bonneau et al. | Dec 1996 | A |
5590038 | Pitroda | Dec 1996 | A |
5590197 | Chen et al. | Dec 1996 | A |
5602918 | Chen et al. | Feb 1997 | A |
5604801 | Dolan et al. | Feb 1997 | A |
5613001 | Bakhoum | Mar 1997 | A |
5677953 | Dolphin | Oct 1997 | A |
5703753 | Mok | Dec 1997 | A |
5721781 | Deo et al. | Feb 1998 | A |
5737439 | Lapsley et al. | Apr 1998 | A |
5739512 | Tognazzini | Apr 1998 | A |
5742756 | Dillaway et al. | Apr 1998 | A |
5742845 | Wagner | Apr 1998 | A |
5757917 | Rose et al. | May 1998 | A |
5764789 | Pare, Jr. et al. | Jun 1998 | A |
5778173 | Apte et al. | Jul 1998 | A |
5796831 | Paradinas et al. | Aug 1998 | A |
5799087 | Rosen | Aug 1998 | A |
5806045 | Biorge et al. | Sep 1998 | A |
5815252 | Price et al. | Sep 1998 | A |
5815657 | Williams et al. | Sep 1998 | A |
5826241 | Stein et al. | Oct 1998 | A |
5826243 | Musmanno et al. | Oct 1998 | A |
5835894 | Adcock et al. | Nov 1998 | A |
5838818 | Herley et al. | Nov 1998 | A |
5857079 | Claus et al. | Jan 1999 | A |
5869822 | Meadows et al. | Feb 1999 | A |
5875432 | Sehr | Feb 1999 | A |
5884271 | Pitroda | Mar 1999 | A |
5884292 | Baker et al. | Mar 1999 | A |
5889941 | Tushie | Mar 1999 | A |
5892211 | Davis et al. | Apr 1999 | A |
5898838 | Wagner | Apr 1999 | A |
5901239 | Kamei | May 1999 | A |
5905908 | Wagner | May 1999 | A |
5907620 | Klemba et al. | May 1999 | A |
5912446 | Wong et al. | Jun 1999 | A |
5915973 | Hoehn et al. | Jun 1999 | A |
5917913 | Wang et al. | Jun 1999 | A |
5917925 | Moore et al. | Jun 1999 | A |
5920058 | Weber et al. | Jul 1999 | A |
5920629 | Rosen | Jul 1999 | A |
5920847 | Kolling et al. | Jul 1999 | A |
5930767 | Reber et al. | Jul 1999 | A |
5931917 | Nguyen et al. | Aug 1999 | A |
5936226 | Aucsmith | Aug 1999 | A |
5942761 | Tuli | Aug 1999 | A |
5978495 | Thomopoulos | Nov 1999 | A |
5987155 | Dunn et al. | Nov 1999 | A |
5988497 | Wallace et al. | Nov 1999 | A |
5991411 | Kaufman | Nov 1999 | A |
5995014 | DiMaria | Nov 1999 | A |
6012039 | Hoffman et al. | Jan 2000 | A |
6012636 | Smith et al. | Jan 2000 | A |
6016476 | Maes et al. | Jan 2000 | A |
6018739 | McCoy et al. | Jan 2000 | A |
6041410 | Shi et al. | Mar 2000 | A |
6045956 | Kato | Apr 2000 | A |
6047281 | Wilson et al. | Apr 2000 | A |
6047282 | Wilson et al. | Apr 2000 | A |
6060815 | Nysen | May 2000 | A |
6070159 | Wilson et al. | May 2000 | A |
6091835 | Smithies et al. | Jul 2000 | A |
6095413 | Tetro et al. | Aug 2000 | A |
6095519 | Shoemaker, Jr. | Aug 2000 | A |
6101477 | Hohle et al. | Aug 2000 | A |
6104311 | Lastinger | Aug 2000 | A |
6104922 | Baumann et al. | Aug 2000 | A |
6116736 | Stark et al. | Sep 2000 | A |
6120461 | Smyth | Sep 2000 | A |
6130623 | MacLellan et al. | Oct 2000 | A |
6148093 | McConnell et al. | Nov 2000 | A |
6154879 | Pare, Jr. et al. | Nov 2000 | A |
6175656 | Hoang | Jan 2001 | B1 |
6182892 | Angelo et al. | Feb 2001 | B1 |
6199079 | Gupta et al. | Mar 2001 | B1 |
6199762 | Hohle | Mar 2001 | B1 |
6219639 | Bakis et al. | Apr 2001 | B1 |
6223984 | Renner et al. | May 2001 | B1 |
6233348 | Fujii et al. | May 2001 | B1 |
6256690 | Carper | Jul 2001 | B1 |
6257486 | Teicher et al. | Jul 2001 | B1 |
6257620 | Kenney | Jul 2001 | B1 |
6263446 | Kausik et al. | Jul 2001 | B1 |
6265977 | Vega et al. | Jul 2001 | B1 |
6268788 | Gray | Jul 2001 | B1 |
6269348 | Pare, Jr. et al. | Jul 2001 | B1 |
6270011 | Gottfried | Aug 2001 | B1 |
6272562 | Scott et al. | Aug 2001 | B1 |
6275353 | Briggs | Aug 2001 | B1 |
6282649 | Lambert | Aug 2001 | B1 |
6298146 | Ilan et al. | Oct 2001 | B1 |
6307956 | Black | Oct 2001 | B1 |
6325285 | Baratelli | Dec 2001 | B1 |
6327578 | Linehan | Dec 2001 | B1 |
6332193 | Glass et al. | Dec 2001 | B1 |
6338048 | Mori | Jan 2002 | B1 |
6338435 | Carper | Jan 2002 | B1 |
6345761 | Seelbach et al. | Feb 2002 | B1 |
6357663 | Takahashi et al. | Mar 2002 | B1 |
6360953 | Lin et al. | Mar 2002 | B1 |
6390374 | Carper et al. | May 2002 | B1 |
6424249 | Houvener | Jul 2002 | B1 |
6442286 | Kramer | Aug 2002 | B1 |
6446862 | Mann | Sep 2002 | B1 |
6480825 | Sharma et al. | Nov 2002 | B1 |
6480935 | Carper et al. | Nov 2002 | B1 |
6483929 | Murakami et al. | Nov 2002 | B1 |
6483932 | Martinez et al. | Nov 2002 | B1 |
6490443 | Freeny, Jr. | Dec 2002 | B1 |
6496594 | Prokoski | Dec 2002 | B1 |
6507662 | Brooks | Jan 2003 | B1 |
6519565 | Clements et al. | Feb 2003 | B1 |
6539101 | Black | Mar 2003 | B1 |
6560581 | Fox et al. | May 2003 | B1 |
6588660 | Buescher et al. | Jul 2003 | B1 |
6588673 | Chan et al. | Jul 2003 | B1 |
6591249 | Zoka | Jul 2003 | B2 |
6601759 | Fife et al. | Aug 2003 | B2 |
6601762 | Piotrowski | Aug 2003 | B2 |
6609656 | Elledge | Aug 2003 | B1 |
6615191 | Seeley | Sep 2003 | B1 |
6628813 | Scott et al. | Sep 2003 | B2 |
6629591 | Griswold et al. | Oct 2003 | B1 |
6631201 | Dickinson et al. | Oct 2003 | B1 |
6636620 | Hoshino | Oct 2003 | B1 |
6655585 | Shinn | Dec 2003 | B2 |
6657614 | Ito et al. | Dec 2003 | B1 |
6658164 | Irving et al. | Dec 2003 | B1 |
6662166 | Pare, Jr. et al. | Dec 2003 | B2 |
6669086 | Abdi et al. | Dec 2003 | B2 |
6681328 | Harris et al. | Jan 2004 | B1 |
6687391 | Scott et al. | Feb 2004 | B1 |
6697947 | Matyas, Jr. et al. | Feb 2004 | B1 |
6703918 | Kita | Mar 2004 | B1 |
6719200 | Wiebe | Apr 2004 | B1 |
6732919 | Macklin et al. | May 2004 | B2 |
6734887 | Field | May 2004 | B2 |
6744909 | Kostrzewski et al. | Jun 2004 | B1 |
6744910 | McClurg et al. | Jun 2004 | B1 |
6765470 | Shinzaki | Jul 2004 | B2 |
6776332 | Allen et al. | Aug 2004 | B2 |
6799726 | Stockhammer | Oct 2004 | B2 |
6816058 | McGregor et al. | Nov 2004 | B2 |
6819219 | Bolle et al. | Nov 2004 | B1 |
6826000 | Lee et al. | Nov 2004 | B2 |
6828299 | Yang et al. | Dec 2004 | B2 |
6828960 | Parry | Dec 2004 | B2 |
6834795 | Rasmussen et al. | Dec 2004 | B1 |
6867850 | McClurg | Mar 2005 | B2 |
6870946 | Teng | Mar 2005 | B1 |
6873974 | Schutzer | Mar 2005 | B1 |
6877097 | Hamid et al. | Apr 2005 | B2 |
6886104 | McClurg et al. | Apr 2005 | B1 |
6892940 | Kocarev et al. | May 2005 | B2 |
6901154 | Dunn | May 2005 | B2 |
6914517 | Kinsella | Jul 2005 | B2 |
6917695 | Teng et al. | Jul 2005 | B2 |
6925439 | Pitroda | Aug 2005 | B1 |
6925565 | Black | Aug 2005 | B2 |
6928181 | Brooks | Aug 2005 | B2 |
6928195 | Scott et al. | Aug 2005 | B2 |
6929413 | Schofield | Aug 2005 | B2 |
6931538 | Sawaguchi | Aug 2005 | B1 |
6934861 | Haala | Aug 2005 | B2 |
6944768 | Siegel et al. | Sep 2005 | B2 |
6954260 | Arnold et al. | Oct 2005 | B2 |
6968453 | Doyle et al. | Nov 2005 | B2 |
6970582 | Langley | Nov 2005 | B2 |
6971031 | Haala | Nov 2005 | B2 |
6983062 | Smith | Jan 2006 | B2 |
6988665 | Schofield | Jan 2006 | B2 |
6996259 | Cannon et al. | Feb 2006 | B2 |
6997381 | Arnouse | Feb 2006 | B2 |
7010148 | Irving et al. | Mar 2006 | B2 |
7028893 | Goodman et al. | Apr 2006 | B2 |
7049962 | Atherton et al. | May 2006 | B2 |
7051925 | Schwarz, Jr. | May 2006 | B2 |
7059159 | Lanigan et al. | Jun 2006 | B2 |
7059531 | Beenau et al. | Jun 2006 | B2 |
7068822 | Scott | Jun 2006 | B2 |
7073711 | Fernandez et al. | Jul 2006 | B2 |
7079007 | Siegel et al. | Jul 2006 | B2 |
7095880 | Martinez et al. | Aug 2006 | B2 |
7102523 | Shanks et al. | Sep 2006 | B2 |
7103201 | Scott et al. | Sep 2006 | B2 |
7127088 | Grajewski et al. | Oct 2006 | B1 |
7132946 | Waldner et al. | Nov 2006 | B2 |
7155039 | Lo | Dec 2006 | B1 |
7162060 | Barton et al. | Jan 2007 | B1 |
7164440 | Cannon | Jan 2007 | B2 |
7165716 | Mödl et al. | Jan 2007 | B1 |
7171662 | Misra et al. | Jan 2007 | B1 |
7181017 | Nagel et al. | Feb 2007 | B1 |
7203344 | McClurg et al. | Apr 2007 | B2 |
7218202 | Bacchiaz et al. | May 2007 | B2 |
7239227 | Gupta et al. | Jul 2007 | B1 |
7266848 | Moyer et al. | Sep 2007 | B2 |
7271881 | Arnold et al. | Sep 2007 | B2 |
7278025 | Saito et al. | Oct 2007 | B2 |
7289649 | Walley et al. | Oct 2007 | B1 |
7303120 | Beenau et al. | Dec 2007 | B2 |
7305563 | Bacchiaz et al. | Dec 2007 | B2 |
7308122 | McClurg et al. | Dec 2007 | B2 |
7314164 | Bonalle et al. | Jan 2008 | B2 |
7314165 | Bonalle et al. | Jan 2008 | B2 |
7319565 | Arnold et al. | Jan 2008 | B2 |
7325724 | Bonalle et al. | Feb 2008 | B2 |
7364071 | Esplin | Apr 2008 | B2 |
7466348 | Morikawa et al. | Dec 2008 | B2 |
7506172 | Bhakta | Mar 2009 | B2 |
7543337 | D'Agnolo | Jun 2009 | B2 |
7724137 | Page | May 2010 | B2 |
7730526 | Lamplough | Jun 2010 | B2 |
7751593 | Hombo | Jul 2010 | B2 |
7938329 | Tran | May 2011 | B2 |
7946501 | Borracci | May 2011 | B2 |
7992789 | Borracci | Aug 2011 | B2 |
8045956 | Sun | Oct 2011 | B2 |
8095519 | Delia | Jan 2012 | B2 |
8186580 | Cannon et al. | May 2012 | B2 |
8253531 | Davis et al. | Aug 2012 | B2 |
8275353 | Sun | Sep 2012 | B2 |
8276816 | Gardner | Oct 2012 | B2 |
8307207 | Bacchiaz et al. | Nov 2012 | B2 |
8360322 | Bonalle et al. | Jan 2013 | B2 |
8485442 | McNeal | Jul 2013 | B2 |
8490872 | Kim | Jul 2013 | B2 |
8499164 | Ortiz et al. | Jul 2013 | B2 |
8553251 | Iizuka | Oct 2013 | B2 |
8572395 | Ito | Oct 2013 | B2 |
8598981 | Idsøe et al. | Dec 2013 | B2 |
8607063 | Ikeuchi | Dec 2013 | B2 |
8708230 | Cannon et al. | Apr 2014 | B2 |
8713660 | Carper | Apr 2014 | B2 |
8756680 | Shashidhar | Jun 2014 | B2 |
8782427 | Fedronic et al. | Jul 2014 | B2 |
8783578 | Kim | Jul 2014 | B2 |
8786033 | Saito | Jul 2014 | B2 |
8799167 | Carper | Aug 2014 | B2 |
9697388 | Jacobson | Jul 2017 | B1 |
20010049785 | Kawan | Dec 2001 | A1 |
20020059523 | Bacchiaz et al. | May 2002 | A1 |
20020095587 | Doyle et al. | Jul 2002 | A1 |
20020153424 | Li | Oct 2002 | A1 |
20030046554 | Leydier | Mar 2003 | A1 |
20030159044 | Doyle | Aug 2003 | A1 |
20040039909 | Cheng | Feb 2004 | A1 |
20040129787 | Saito et al. | Jul 2004 | A1 |
20040188519 | Cassone | Sep 2004 | A1 |
20040266267 | Inaba | Dec 2004 | A1 |
20050035200 | Hendrick | Feb 2005 | A1 |
20050125674 | Nishiki | Jun 2005 | A1 |
20050139685 | Kozlay | Jun 2005 | A1 |
20050144354 | Murashita | Jun 2005 | A1 |
20050161503 | Remery | Jul 2005 | A1 |
20050182947 | Bacchiaz et al. | Aug 2005 | A1 |
20050240778 | Saito | Oct 2005 | A1 |
20060032905 | Bear | Feb 2006 | A1 |
20060070114 | Wood | Mar 2006 | A1 |
20060113381 | Hochstein et al. | Jun 2006 | A1 |
20060161789 | Doughty | Jul 2006 | A1 |
20060208066 | Finn | Sep 2006 | A1 |
20070033150 | Nwosu | Feb 2007 | A1 |
20070040017 | Kozlay | Feb 2007 | A1 |
20070043594 | Lavergne | Feb 2007 | A1 |
20070073619 | Smith | Mar 2007 | A1 |
20070124536 | Carper | May 2007 | A1 |
20070154018 | Watanabe | Jul 2007 | A1 |
20070186106 | Ting | Aug 2007 | A1 |
20070194131 | Brown | Aug 2007 | A1 |
20070220273 | Campisi | Sep 2007 | A1 |
20070228154 | Tran | Oct 2007 | A1 |
20070251997 | Brown | Nov 2007 | A1 |
20080005425 | Saito | Jan 2008 | A1 |
20080016370 | Libin | Jan 2008 | A1 |
20080019578 | Saito et al. | Jan 2008 | A1 |
20080040615 | Carper et al. | Feb 2008 | A1 |
20080054875 | Saito | Mar 2008 | A1 |
20080072065 | Bonalle et al. | Mar 2008 | A1 |
20080097924 | Carper et al. | Apr 2008 | A1 |
20080126260 | Cox | May 2008 | A1 |
20080148059 | Shapiro | Jun 2008 | A1 |
20080164325 | Borracci | Jul 2008 | A1 |
20080201658 | Saito et al. | Aug 2008 | A1 |
20080223921 | Salazar | Sep 2008 | A1 |
20080223925 | Saito et al. | Sep 2008 | A1 |
20080230613 | Leibenguth | Sep 2008 | A1 |
20080282334 | Yves | Nov 2008 | A1 |
20090084858 | Borracci | Apr 2009 | A1 |
20090094125 | Killian | Apr 2009 | A1 |
20090313493 | Ide | Dec 2009 | A1 |
20090322477 | Celorio | Dec 2009 | A1 |
20100039234 | Soliven et al. | Feb 2010 | A1 |
20100080425 | Bebis | Apr 2010 | A1 |
20100148312 | Jung | Jun 2010 | A1 |
20100153451 | Delia | Jun 2010 | A1 |
20100161488 | Evans | Jun 2010 | A1 |
20100215224 | Saito | Aug 2010 | A1 |
20100257359 | Currie | Oct 2010 | A1 |
20100260388 | Garrett | Oct 2010 | A1 |
20100275259 | Adams | Oct 2010 | A1 |
20110238540 | Carrington | Sep 2011 | A1 |
20110256832 | Park | Oct 2011 | A1 |
20120016798 | Carper | Jan 2012 | A1 |
20120022957 | Sun | Jan 2012 | A1 |
20120079273 | Bacchiaz et al. | Mar 2012 | A1 |
20120120013 | Kurz | May 2012 | A1 |
20120218079 | Kim | Aug 2012 | A1 |
20120241524 | Blot et al. | Sep 2012 | A1 |
20120297467 | Carper | Nov 2012 | A1 |
20120313754 | Bona | Dec 2012 | A1 |
20130026230 | Cannon et al. | Jan 2013 | A1 |
20130036463 | Shashidhar | Feb 2013 | A1 |
20130056540 | Blot et al. | Mar 2013 | A1 |
20130080788 | Bacchiaz et al. | Mar 2013 | A1 |
20130290136 | Sheets | Oct 2013 | A1 |
20140006277 | Rao | Jan 2014 | A1 |
20140046785 | Jenkins | Feb 2014 | A1 |
20140232526 | Carper | Aug 2014 | A1 |
20140251997 | Bitton | Sep 2014 | A1 |
20150067348 | Webber | Mar 2015 | A1 |
20150127553 | Sundaram | May 2015 | A1 |
20150262170 | Bouda | Sep 2015 | A1 |
20150379033 | Agarwal | Dec 2015 | A1 |
20160191512 | Tatourian | Jun 2016 | A1 |
20170170513 | Sakamoto | Jun 2017 | A1 |
20170323130 | Dickinson | Nov 2017 | A1 |
Number | Date | Country |
---|---|---|
200238203 | Nov 2002 | AU |
757159 | Feb 2003 | AU |
2003274967 | Apr 2004 | AU |
2004218720 | Nov 2004 | AU |
784438 | Apr 2006 | AU |
2006311596 | May 2007 | AU |
2007229728 | Oct 2007 | AU |
2010224455 | Jan 2011 | AU |
2346592 | Nov 2001 | CA |
2498288 | Mar 2004 | CA |
2564707 | Nov 2005 | CA |
2629435 | May 2007 | CA |
2748563 | Mar 2012 | CA |
2844003 | Feb 2013 | CA |
60111892 | Aug 2005 | DE |
10393215 | Sep 2005 | DE |
994439 | Apr 2000 | EP |
1256908 | Nov 2002 | EP |
1418486 | May 2004 | EP |
1537526 | Jun 2005 | EP |
1157906 | Jul 2005 | EP |
1647942 | Apr 2006 | EP |
1716660 | Nov 2006 | EP |
1759337 | Mar 2007 | EP |
1840788 | Oct 2007 | EP |
1924976 | May 2008 | EP |
1952244 | Aug 2008 | EP |
2290625 | Mar 2011 | EP |
2434462 | Mar 2012 | EP |
2569735 | Mar 2013 | EP |
2953619 | Jun 2011 | FR |
2959847 | Nov 2011 | FR |
2473283 | Mar 2011 | GB |
02088859 | Mar 1990 | JP |
H0288859 | Mar 1990 | JP |
02118790 | May 1990 | JP |
11039483 | Feb 1999 | JP |
2001250064 | Sep 2001 | JP |
2001323691 | Nov 2001 | JP |
2002183706 | Jun 2002 | JP |
2005242650 | Sep 2005 | JP |
2005326995 | Nov 2005 | JP |
2006257871 | Sep 2006 | JP |
200748118 | Feb 2007 | JP |
2007048118 | Feb 2007 | JP |
2007058649 | Mar 2007 | JP |
2007156785 | Jun 2007 | JP |
2007265321 | Oct 2007 | JP |
2008078820 | Apr 2008 | JP |
2010262586 | Nov 2010 | JP |
2011090686 | May 2011 | JP |
2012074011 | Apr 2012 | JP |
2014134845 | Jul 2014 | JP |
20030042639 | Jun 2003 | KR |
9718653 | May 1997 | WO |
2001016707 | Mar 2001 | WO |
2001016759 | Mar 2001 | WO |
2001016865 | Mar 2001 | WO |
2001016873 | Mar 2001 | WO |
2001016874 | Mar 2001 | WO |
2001039427 | Mar 2001 | WO |
2004025545 | Mar 2004 | WO |
2005104704 | Nov 2005 | WO |
2006102625 | Sep 2006 | WO |
2007022423 | Feb 2007 | WO |
2007056476 | May 2007 | WO |
2007064429 | Jun 2007 | WO |
2007143670 | Dec 2007 | WO |
2007146681 | Dec 2007 | WO |
2008010899 | Jan 2008 | WO |
2008079491 | Jul 2008 | WO |
2010019961 | Feb 2010 | WO |
2010077999 | Jul 2010 | WO |
2010133469 | Nov 2010 | WO |
2010133496 | Nov 2010 | WO |
2011067543 | Jun 2011 | WO |
2011141659 | Nov 2011 | WO |
Entry |
---|
ISO 7816 Part 3: Electronic Signals and Transmission Protocols, www.cardwerk.com/smartcards/smartcard_standard_ISO7816-3.aspx, Jan. 12, 2015. |
John Fenske, “Biometrics Move to Smart Cards and Smartphones for Access Control”, John Fenske, Jul. 30, 2013. |
Patent Cooperation Treaty, International Search Report for PCT/IB2016/000026, dated May 17, 2016, pp. 4-5. |
Patent Cooperation Treaty, International Search Report for PCT/US2016/000020, dated May 24, 2016, pp. 4-5. |
Patent Cooperation Treaty, International Search Report for PCT/IB2016/000048, dated Apr. 15, 2016, p. 5. |
Patent Cooperation Treaty, International Search Report for PCT/IB2016/000324, dated Oct. 18, 2016, pp. 4-5. |
Patent Cooperation Treaty, International Preliminary Report on Patentability PCT/IB2016/000020, dated Jul. 18, 2017, p. 4. |
Patent Cooperation Treaty, International Preliminary Report on Patentability for PCT/IB2016/000048, dated Apr. 26, 2016, p. 4. |
Patent Cooperation Treaty, International Search Report for PCT/IB2016/00093, dated Sep. 5, 2017, p. 7. |
Patent Cooperation Treaty, International Preliminary Report on Patentability for PCT/IB2016/000093, dated Sep. 26, 2017, p. 4. |
Patent Cooperation Treaty, International Preliminary Report on Patentability for PCT/IB2016/000026, dated Jul. 18, 2017, p. 4. |
Patent Cooperation Treaty, International Preliminary Report on Patentability for PCT/IB2016/000324, dated Sep. 26, 2017, p. 4. |
Patent Cooperation Treaty, International Preliminary Report on Patentability for PCT/IB2016/000048, dated Jul. 25, 2017, p. 4. |
Patent Cooperation Treaty, International Search Report for PCT/IB2016/00020, dated May 24, 2017, pp. 2-3. |
Jung, Stefan, “A Low-Power and High-Performance CMOS Fingerprint Sensing and Encoding Architecture,” IEEE Journal of Solid-State Circuits, Jul. 1999, pp. 978-984, vol. 34, No. 7. |
Noore, Afzel, “Highly Robust Biometric Smart Card Design,” IEEE Transactions on Consumer Electronics, Nov. 2000, pp. 1059-1063, vol. 46, No. 4. |
Sanchez-Reillo, Raul, et al., “Fingerprint Verification Using Smart Cards for Access Control Systems,” 2001, pp. 250-253. |
Sanchez-Reillo, Raul, et al., “Microprocessor Smart Cards with Fingerprint User Authorization,” IEEE AESS Systems Magazine, Mar. 2003, pp. 22-24. |
Sung, Bum Pan, et al., “An Ultra-Low Memory Fingerprint Matching Algorithm and Its Implementation on a 32-bit Smart Card,” IEEE, Mar. 26, 2003, pp. 453-459. |
Kim, Dong-Sun, “On the Design of an Embedded Biometric Smart Card Reader,” IEEE, Apr. 16, 2008, pp. 573-577. |
Kim, Seong-Jin, “A CMOS Fingerprint System-on-a-Chip With Adaptable Pixel Networks and Column-Parallel Processors for Image Enhancement and Recognition,” IEEE Journal of Solid-State Circuits, Nov. 2008, pp. 2558-2567, vol. 43, No. 11. |
Nixon, Jenny, “Reconciling your Quicken Account with the Bank Statement,” University of Nebraska, Lincoln, 2005. |
“Biometric Technology for Secure Access,” Sep. 18, 2007, Biometric Associates, Inc., Baltimore, MD, USA. |
Anonymous: “ISO/IEC 7816-3 Identification cards—Integrated circuit cards—Part 3: Cards with contacts—Electrical interface and transmission protocols”, Nov. 1, 2006 (Nov. 1, 2006), XP055438640, Retrieved from the Internet: URL:http://read.pudn.com/downloads132/doc/comm/563504/ISO-IEC 7816/ISO+IEC7816-3-2006.pdf [retrieved on Jan. 8, 2018]. |
Number | Date | Country | |
---|---|---|---|
20160232517 A1 | Aug 2016 | US |