US 7,239,226 B2Grant
System and method for payment using radio frequency identification in contact and contactless transactions
Issue Date:2007-07-03
•12 Claims
•13 Drawing Sheets
Abstract
A transponder-reader payment system includes a fob including a transponder, and a RFID reader for interrogating the transponder. The system may further include a personalization system for populating onto the fob and RFID reader identifying information and security and authentication keys which may be used during mutual authentication of the fob and the reader and for completing a transaction. In exemplary operation, the fob and RFID reader may be personalized, the fob may be presented to the RFID reader for interrogation, the fob and reader may engage in mutual authentication, and fob identifying information may be provided to the reader for transaction completion. In another exemplary embodiment, operation of the transponder-reader payment system may be controlled by an activation circuit. Further, the fob may be responsive to multiple interrogation signals.
Metadata
Assignee
- American Express Travel Related Services Company, Inc.
Inventors
- Michael J. Berardi
- Michal Bliman
- David S. Bonalle
- Jennifer Anne Elwood
- Matthew C. Hood
- Susan E. Isenberg
- Alexandra Mayers
- Peter D. Saunders
- Kathryn D. Scheding
- Sejal Ajit Shah
- John R. Williamson
Application Information
Application Number:US 10/192,488
Filing Date:2002-07-09
Priority Date:2001-07-10
Art Unit:2612
Classifications
IPC:
H04Q1/00
Patent Drawings (13 sheets)
Description
Related Applications
[0001] This invention claims priority to U.S. Provisional Application No. 60/304,216, entitled “SYSTEM AND METHOD FOR RFID PAYMENT,” filed on Jul. 10, 2001 and incorporated herein by reference.
Field of Invention
[0002] This invention generally relates to a system and method for completing a transaction, and more particularly, to completing a financial transaction using Radio Frequency Identification (RFID) in contact and contactless transactions.
Background of the Invention
[0003] Like barcode and voice data entry, RFID is a contactless information acquisition technology. RFID systems are wireless, and are usually extremely effective in hostile environments where conventional acquisition methods fail. RFID has established itself in a wide range of markets, such as, for example, the high-speed reading of railway containers, tracking moving objects such as livestock or automobiles, and retail inventory applications. As such, RFID technology has become a primary focus in automated data collection, identification and analysis systems worldwide.
[0004] Of late, companies are increasingly embodying RFID data acquisition technology in a fob or tag for use in completing financial transactions. A typical fob includes a transponder and is ordinarily a self-contained device which may be contairied on any portable form factor. In some instances, a battery may be included with the fob to power the transponder. In which case the internal circuitry of the fob (including the transponder) may draw its operating power from the battery power source. Alternatively, the fob may exist independently of an internal power source. In this instance the internal circuitry of the fob (including the transponder) may gain its operating power directly from an RF interrogation signal. U.S. Pat. No. 5,053,774 issued to Schuermann describes a typical transponder RF interrogation system which may be found in the prior art. The Schuermann patent describes in general the powering technology surrounding conventional transponder structures. U.S. Pat. No. 4,739,328 discusses a method by which a conventional transponder lilay respond to a RF interrogation signal. Other typical modulation techniques which may be used include, for example, ISO/IEC 14443 and the like.
[0005] In the conventional fob powering technologies used, the fob is typically activated upon presenting the fob in an interrogation signal. In this regard, the fob may be activated irrespective of whether the user desires such activation. Inadvertent presentation of the fob may result in initiation and completion of an unwanted transaction. Thus, a fob system is needed which allows the fob user to control activation of the fob to limit transactions being undesirably completed.
[0006] One of the more visible uses of the RFID technology is found in the introduction of Exxon/Mobil's Speedpass® and Shell's EasyPay® products. These products use transponders placed in a fob or tag which enables automatic identification of the user when the fob is presented at a Point of Sale (POS) device. Fob identification data is typically passed to a third party server database, where the identification data is referenced to a customer (e.g., user) credit or debit account. In an exemplary processing method, the server seeks authorization for the transaction by passing the transaction and account data to an authorizing entity. Once authorization is received by the server, clearance is sent to the point of sale device for completion of the transaction. In this way, the conventional transaction processing method involves an indirect path which causes undue overhead due to the use of the third-party server.
[0007] A need exists for a transaction authorization system which allows Fob transactions to be authorized while eliminating the cost associated with using third-party servers.
[0008] In addition, conventional fobs are limited in that they must be used in proximity to the Point of Sale device. That is, for fob activation, conventional fobs must be positioned within the area of transmission cast by the RF interrogation signal. More particularly, conventional fobs are not affective for use in situations where the user wishes to conduct a transaction at a point of interaction such as a computer interface.
[0009] Therefore, a need exists for a fob embodying RFID acquisition technology, which is capable of use at a point of interaction device and which is additionally capable of facilitating transactions via a computer interface connected to a network (e.g., the Internet).
[0010] Existing transponder-reader payment systems are also limited in that the conventional fob used in the systems is only responsive to one interrogation signal. Where multiple interrogation signals are used, the fob is only responsive to the interrogation signal to which it is configured. Thus, if the RFID reader of the system provides only an interrogation signal to which the fob is incompatible, the fob will not be properly activated.
[0011] Therefore, a need exists for a fob which is responsive to more than one interrogation signal.
Summary of the Invention
[0012] Described herein is a system and method for using RFID technology to initiate and complete financial transactions. The transponder-reader payment system described herein may include a RFID reader operable to provide a RF interrogation signal for powering a transponder system, receiving a transponder system RF signal, and providing transponder system account data relative to the transponder system RF signal. The transponder-reader payment system may include a RFID protocol/sequence controller in electrical communication with one or more interrogators for providing an interrogation signal to a transponder, a RFID authentication circuit for authenticating the signal received from the transponder, a serial or parallel interface for interfacing with a point of interaction device, and an USB or serial interface for use in personalizing the RFID reader and/or the transponder. The transponder-reader payment system may further include a fob including one or more transponders (e.g., modules) responsive to one or more interrogation signal and for providing an authentication signal for verifying that the transponder and/or the RFID reader are authorized to operate within the transponder-reader payment system. In this way, the transponder may be responsive to multiple interrogation signals provided at different frequencies. Further, the for may include a USB or serial interface for use with a computer network or with the RFID reader.
[0013] The RFID system and method according to the present invention may include a transponder which may be embodied in a fob, tag, card or any other form factor (e.g., wristwatch, keychain, cell phone, etc.), which may be capable of being presented for interrogation. In that regard, although the transponder is described herein as embodied in a fob, the invention is not so limited.
[0014] The system may further include a RFID reader configured to send a standing RFID recognition signal which may be transmitted from the RFID reader via radio frequency (or electromagnetic) propagation. The fob may be placed within proximity to the RFID reader such that the RFID signal may interrogate the fob and initialize fob identification procedures.
[0015] In one exemplary embodiment, as a part of the identification process, the fob and the RFID reader may engage in mutual authentication. The RFID reader may identify the fob as including an authorized system transponder for receiving encrypted information and storing the information on the fob memory. Similarly, the fob, upon interrogation by the RFID reader, may identify the RFID reader as authorized to receive the encrypted and stored information. Where the RFID reader and the fob successfully mutually authenticate, the fob may transmit to the RFID reader certain information identifying the transaction account or accounts to which the fob is associated. The RFID reader may receive the information and forward the information to facilitate the completion of a transaction. In one exemplary embodiment, the RFID reader may forward the information to a point of interaction device (e.g., POS or computer interface) for transaction completion. The mutual authorization process disclosed herein aids in ensuring fob transponder-reader payment system security.
[0016] In another exemplary embodiment, the fob according to the present invention, includes means for completing transactions via a computer interface. The fob may be connected to the computer using a USB or serial interface fob account information may be transferred to the computer for use in completing a transaction via a network (e.g., the Internet).
[0017] These features and other advantages of the system and method, as well as the structure and operation of various exemplary embodiments of the system and method, are described below.
Brief Description of the Drawings
[0018] The accompanying drawings, wherein like numerals depict like elements, illustrate exemplary embodiments of the present invention, and together with the description, serve to explain the principles of the invention. In the drawings:
[0019] FIG. 1A illustrates an exemplary RFID-based system in accordance with the present invention, wherein exemplary components used for fob transaction completion are depicted;
[0020] FIG. 1B illustrates an exemplary personalization system in accordance with the present invention;
[0021] FIG. 2 is a schematic illustration of an exemplary fob in accordance with the present invention;
[0022] FIG. 3 is a schematic illustration of an exemplary RFID reader in accordance with the present invention;
[0023] FIG. 4 is an exemplary flow diagram of an exemplary authentication process in accordance with the present invention;
[0024] FIG. 5 is an exemplary flow diagram of an exemplary decision process for a protocol/sequence controller in accordance with the present invention;
[0025] FIGS. 6A-B are an exemplary flow diagram of a fob personalization process in accordance with the present invention;
[0026] FIGS. 7A-B are an exemplary flow diagram of a RFID reader personalization process in accordance with the present invention;
[0027] FIG. 8 is a flow diagram of an exemplary payment/transaction process in accordance with the present invention; and
[0028] FIG. 9 is another schematic illustration of an exemplary fob in accordance with the present invention.
Detailed Description
[0029] The present invention may be described herein in terms of functional block components, screen shots, optional selections and various processing steps. Such functional blocks may be realized by any number of hardware and/or software components configured to perform to specified functions. For example, the present invention may employ various integrated circuit components, e.g., memory elements, processing elements, logic elements, look-up tables, and the like, which may carry out a variety of functions under the control of one or more mircroprocessors or other control devices. Similarly, the software elements of the present invention may be implemented with any programming or scripting language such as C, C++, Java, COBOL, assembler, PERL, extensible markup language (XML), JavaCard and MULTOS with the various algorithms being implemented with any combination of data structures, objects, processes, routines or other programming elements. Further, it should be noted that the present invention may employ any number of conventional techniques for data transmission, signaling, data processing, network control, and the like. For a basic introduction on cryptography, review a text written by Bruce Schneier entitled “Applied Cryptography: Protocols, Algorithms, and Source Code in C,” published by John Wiley & Sons (second edition, 1996), herein incorporated by reference.
[0030] In addition, many applications of the present invention could be formulated. The exemplary network disclosed herein may include any system for exchanging data or transacting business, such as the internet, an intranet, an extranet, WAN, LAN, satellite communications, and/or the like. It is noted that the network may be implemented as other types of networks, such as an interactive television network (ITN).
[0031] Where required, the system user may interact with the system via any input device such as, a keypad, keyboard, mouse, kiosk, personal digital assistant, handheld computer (e.g., Palm Pilot®, Blueberry®), cellular phone and/or the like. Similarly, the invention could be used in conjunction with any type of personal computer, network computer, work station, minicomputer, mainframe, or the like running any operating system such as any version of Windows, Windows NT, Windows 2000, Windows 98, Windows 95, MacOS, OS/2, BeOS, Linux, UNIX, Solaris or the like. Moreover, although the invention may frequently be described as being implemented with TCP/IP communications protocol, it should be understood that the invention could also be implemented using SNA, IPX, Appletalk, IPte, NetBIOS, OSI or any number of communications protocols. Moreover, the system contemplates, the use, sale, or distribution of any goods, services or information over any network having similar functionality described herein.
[0032] FIG. 1A illustrates an exemplary RFID transaction system 100A in accordance with the present invention, wherein exemplary components for use in completing a fob transaction are depicted. In general, the operation of system 100A may begin when fob 102 is presented for payment, and is interrogated by RFID reader 104 or, alternatively, interface 134. Fob 102 and RFID reader 104 may then engage in mutual authentication after which the transponder 102 may provide the transponder identification and/or account identifier to the RFID reader 104 which may further provide the information to the merchant system 130 POS device 110.
[0033] System 100A may include a fob 102 having a transponder 114 and a RFID reader 104 in RF communication with fob 102. Although the present invention is described with respect to a fob 102, the invention is not to be so limited. Indeed, system 100 may include any device having a transponder which is configured to communicate with a RFID reader 104 via RF communication. Typical devices may include, for example, a key ring, tag, card, cell phone, wristwatch or any such form capable of being presented for interrogation.
[0034] The RFID reader 104 may be configured to communicate using a RFID internal antenna 106. Alternatively, RFID reader 104 may include an external antenna 108 for communications with fob 102, where the external antenna may be made remote to the RFID reader 104 using a suitable cable and/or data link 120. RFID reader 104 may be further in communication with a merchant system 130 via a data link 122. The system 100A may include a transaction completion system including a point of interaction device such as, for example, a merchant point of sale (POS) device 110 or a computer interface (e.g., user interface) 134. In one exemplary embodiment the transaction completion system may include a merchant system 130 including the POS device 110 in communication with a RFID reader 104 (via data link 122). As described more fully below, the transaction completion system may include the user interface 134 connected to a network 136 and to the transponder via a USB connector 132.
[0035] Although the point of interaction device is described herein with respect to a merchant point of sale (POS) device, the invention is not to be so limited. Indeed, a merchant POS device is used herein by way of example, and the point of interaction device may be any device capable of receiving fob account data. In this regard, the POS may be any point of interaction device enabling the user to complete a transaction using a fob 102. POS device 110 may be in further communication with a customer interface 118 (via data link 128) for entering at least a customer identity verification information. In addition, POS device 110 may be in communication with a merchant host network 112 (via data link 124) for processing any transaction request. In this arrangement, information provided by RFID reader 104 is provided to the POS device 110 of merchant system 130 via data link 122. The POS device 110 may receive the information (and alternatively may receive any identity verifying information from customer interface 118 via data link 128) and provide the information to host system 112 for processing.
[0036] A variety of conventional communications media and protocols may be used for data links 120, 122, 124, and 128. For example, data links 120, 122, 124, and 128 may be an Internet Service Provider (ISP) configured to facilitate communications over a local loop as is typically used in connection with standard modem communication, cable modem, dish networks, ISDN, Digital Subscriber Lines (DSL), or any wireless communication media. In addition, the merchant system 130 including the POS device 110 and host network 112 may reside on a local area network which interfaces to a remote network (not shown) for remote authorization of an intended transaction. The merchant system 130 may communicate with the remote network via a leased line, such as a T1, D3 line, or the like. Such communications lines are described in a variety of texts, such as, “Understanding Data Communications,” by Gilbert Held, which is incorporated herein by reference.
[0037] An account number, as used herein, may include any identifier for an account (e.g., credit, charge debit, checking, savings, reward, loyalty, or the like) which may be maintained by a transaction account provider (e.g., payment authorization center) and which may be used to complete a financial transaction. A typical account number (e.g., account data) may be correlated to a credit or debit account, loyalty account, or rewards account maintained and serviced by such entities as American Express®, Visa® and/or MasterCard® or the like. For ease in understanding, the present invention may be described with respect to a credit account. However, it should be noted that the invention is not so limited and other accounts permitting an exchange of goods and services for an account data value is contemplated to be within the scope of the present invention.
[0038] In addition, the account number (e.g., account data) may be associated with any device, code, or other identifier/indicia suitably configured to allow the consumer to interact or communicate with the system, such as, for example, authorization/access code, personal identification number (PIN), Internet code, digital certificate, biometric data, and/or other identification indicia. The account number may be optionally located on a rewards card, charge card, credit card, debit card, prepaid card, telephone card, smart card, magnetic stripe card, bar code card, and/or the like. The account number may be distributed and stored in any form of plastic, electronic, magnetic, and/or optical device capable of transmitting or downloading data to a second device. A customer account number may be, for example, a sixteen-digit credit card number, although each credit provider has its own numbering system, such as the fifteen-digit numbering system used by American Express®. Each company's credit card numbers comply with that company's standardized format such that the company using a sixteen-digit format will generally use four spaced sets of numbers, as represented by the number “0000 0000 0000 0000”. In a typical example, the first five to seven digits are reserved for processing purposes and identify the issuing bank, card type and etc. In this example, the last sixteenth digit is used as a sum check for the sixteen-digit number. The intermediary eight-to-ten digits are used to uniquely identify the customer. The account number stored as Track 1 and Track 2 data as defined in ISO/IEC 7813, and further may be made unique to fob 102. In one exemplary embodiment, the account number may include a unique fob serial number and user identification number, as well as specific application applets. The account number may be stored in fob 102 inside a database 214, as described more fully below. Database 214 may be configured to store multiple account numbers issued to the fob 102 user by the same or different account providing institutions. Where the account data corresponds to a loyalty or rewards account, the database 214 may be configured to store the attendant loyalty or rewards points data.
[0039] FIG. 2 illustrates a block diagram of the many functional blocks of an exemplary fob 102 in accordance with the present invention. Fob 102 may be a RFID fob 102 which may be presented by the user to facilitate an exchange of funds or points, etc., for receipt of goods or services. As described herein, by way of example, the fob 102 may be a RFID fob which may be presented for facilitating payment for goods and/or services.
[0040] Fob 102 may include an antenna 202 for receiving an interrogation signal from RFID reader 104 via antenna 106 (or alternatively, via external antenna 108). Fob antenna 202 may be in communication with a transponder 114. In one exemplary embodiment, transponder 114 may be a 13.56 MHz transponder compliant with the ISO/IEC 14443 standard, and antenna 202 may be of the 13 MHz variety. The transponder 114 may be in communication with a transponder compatible modulator/demodulator 206 configured to receive the signal from transponder 114 and configured to modulate the signal into a format readable by any later connected circuitry. Further, modulator/demodulator 206 may be configured to format (e.g., demodulate) a signal received from the later connected circuitry in a format compatible with transponder 114 for transmitting to RFID reader 104 via antenna 202. For example, where transponder 114 is of the 13.56 MHz variety, modulator/demodulator 206 may be ISO/IEC 14443-2 compliant.
[0041] Modulator/demodulator 206 may be coupled to a protocol/sequence controller 208 for facilitating control of the authentication of the signal provided by RFID reader 104, and for facilitating control of the sending of the fob 102 account number. In this regard, protocol/sequence controller 208 may be any suitable digital or logic driven circuitry capable of facilitating determination of the sequence of operation for the fob 102 inner-circuitry. For example, protocol/sequence controller 208 may be configured to determine whether the signal provided by the RFID reader 104 is authenticated, and thereby providing to the RFID reader 104 the account number stored on fob 102.
[0042] Protocol/sequence controller 208 may be further in communication with authentication circuitry 210 for facilitating authentication of the signal provided by RFID reader 104. Authentication circuitry may be further in communication with a non-volatile secure memory database 212. Secure memory database 212 may be any suitable elementary file system such as that defined by ISO/IEC 7816-4 or any other elementary file system allowing a lookup of data to be interpreted by the application on the chip. Database 212 may be any type of database, such as relational, hierarchical, object-oriented, and/or the like. Common database products that may be used to implement the databases include DB2 by IBM (White Plains, N.Y.), any of the database products available from Oracle Corporation (Redwood Shores, Calif.), Microsoft Access or MSSQL by Microsoft Corporation (Redmond, Wash.), or any other database product. Database 212 may be organized in any suitable manner, including as data tables or lookup tables. Association of certain data may be accomplished through any data association technique known and practiced in the art. For example, the association may be accomplished either manually or automatically. Automatic association techniques may include, for example, a database search, a database merge, GREP, AGREP, SQL, and/or the like. The association step may be accomplished by a database merge function, for example, using a “key field” in each of the manufacturer and retailer data tables. A “key field” partitions the database according to the high-level class of objects defined by the key field. For example, a certain class may be designated as a key field in both the first data table and the second data table, and the two data tables may then be merged on the basis of the class data in the key field. In this embodiment, the data corresponding to the key field in each of the merged data tables is preferably the same. However, data tables having similar, though not identical, data in the key fields may also be merged by using AGREP, for example.
[0043] The data may be used by protocol/sequence controller 208 for data analysis and used for management and control purposes, as well as security purposes. Authentication circuitry may authenticate the signal provided by RFID reader 104 by association of the RFID signal to authentication keys stored on database 212. Encryption circuitry may use keys stored on database 212 to perform encryption and/or decryption of signals sent to or from the RFID reader 104.
[0044] In addition, protocol/sequence controller 208 may be in communication with a database 214 for storing at least a fob 102 account data, and a unique fob 102 identification code. Protocol/sequence controller 208 may be configured to retrieve the account number from database 214 as desired. Database 214 may be of the same configuration as database 212 described above. The fob account data and/or unique fob identification code stored on database 214 may be encrypted prior to storage. Thus, where protocol/sequence controller 208 retrieves the account data, and or unique fob identification code from database 214, the account number may be encrypted when being provided to RFID reader 104. Further, the data stored on database 214 may include, for example, an unencrypted unique fob 102 identification code, a user identification, Track 1 and 2 data, as well as specific application applets.
[0045] Fob 102 may be configured to respond to multiple interrogation frequency transmissions provided by RFID reader 104. That is, as described more fully below, RFID reader 104 may provide more than one RF interrogation signal. In this case, fob 102 may be configured to respond to the multiple frequencies by including in fob 102 one or more additional RF signal receiving/transmitting units 226. RF signal receiving/transmitting unit 226 may include an antenna 218 and transponder 220 where the antenna 218 and transponder 220 are compatible with at least one of the additional RF signals provided by RFID reader 104. For example, in one exemplary embodiment, fob 102 may include a 134 KHz antenna 218 configured to communicate with a 134 KHz transponder 220. In this exemplary configuration, an ISO/IEC 14443-2 compliant modulator/demodulator may not be required. Instead, the 134 KHz transponder may be configured to communicate directly with the protocol/sequence controller 208 for transmission and receipt of authentication and account number signals as described above.
[0046] In another embodiment, fob 102 may further include a universal serial bus (USB) connector 132 for interfacing fob 102 to a user interface 134. User interface 134 may be further in communication with a POS device 110 via a network 136. Network 136 may be the Internet, an intranet, or the like as is described above with respect to network 112. Further, the user interface 134 may be similar in construction to any conventional input devices and/or computing systems aforementioned for permitting the system user to interact with the system. In one exemplary embodiment, fob 102 may be configured to facilitate online Internet payments. A USB converter 222 may be in communication with a USB connector 232 for facilitating the transfer of information between the modulator/demodulator 206 and USB connector 132. Alternatively, USB converter 222 may be in communication with protocol/sequence controller 208 to facilitate the transfer of information between protocol/sequence controller 208 and USB connector 132.
[0047] Where fob 102 includes a USB connector 132, fob 102 may be in communication with, for example, a USB port on user interface 134. The information retrieved from fob 102 may be compatible with credit card and/or smart card technology enabling usage of interactive applications on the Internet. No RFID reader may be required in this embodiment since the connection to POS device 110 may be made using a USB port on user interface 134 and a network 136.
[0048] Fob 102 may include means for enabling activation of the fob by the user. In one exemplary embodiment, a switch 230 which may be operated by the user of the fob 102. The switch 230 on fob 102 may be used to selectively or inclusively activate the fob 102 for particular uses. In this context, the term “selectively” may mean that the switch 230 enables the user to place the fob 102 in a particular operational mode. For example, the user may place the fob 102 in a mode for enabling purchase of a good or of a service using a selected account number. Alternatively, the fob may be placed in a mode as such that the fob account number is provided by USB port 132 (or serial port) only and the fob transponder 114 is disabled. In addition, the term “inclusively” may mean that the fob 102 is placed in an operational mode permitting the fob 102 to be responsive to the RF interrogation and interrogation via the USB connector 132. In one particular embodiment, the switch 230 may remain in an OFF position ensuring that one or more applications or accounts associated with the fob 102 are non-reactive to any commands issued by RFID reader 104. As used herein, the OFF position may be termed the “normal” position of the activation switch 230, although other normal positions are contemplated.
[0049] In another exemplary embodiment, when the switch 230 is moved from the OFF position, the fob 102 may be deemed activated by the user. That is, the switch 230 may activate internal circuitry in fob 102 for permitting the fob to be responsive to RF signals (e.g., commands from RFID reader 104). In this way, switch 230 may facilitate control of the active and inactive states of the fob 102. Such control increases the system security by preventing inadvertent or illegal use of the fob 102.
[0050] In one exemplary embodiment, switch 230 may be a simple mechanical device in communication with circuitry which may electrically prevent the fob from being powered by a RFID reader. That is, when switch 230 is in its normal position, switch 230 may provide a short to the fob 102 internal circuitry, preventing fob 102 from being responsive to interrogation by RF or via the USB connector 230. In this arrangement, the switch 230 may be, for example, a “normally closed” (NC) configured switch, which may be electrically connected to the antenna 202 at the interface of the antenna 202 and the transponder 114. The switch 230 may be depressed, which may open the switch 230 fully activating the antenna 202.
[0051] In yet another exemplary embodiment, the fob 102 may include a biometric sensor and biometric membrane configured to operate as switch 230 and activate the fob 102 when provided biometric signal from the fob 102 user. Such biometric signal may be the digital reading of a fingerprint, thumbprint, or the like. Typically, where biometric circuitry is used, the biometric circuitry may be powered by an internal voltage source (e.g., battery). In this case, the switch may not be a simple mechanical device, but a switch which is powered. In yet another exemplary embodiment, switch 230 may be battery powered though no biometric circuitry is present in the fob 102.
[0052] In yet another embodiment, the switch 230 may be a logic switch. Where switch 230 is a logic switch the switch 230 control software may be read from the sequence controller 208 to selectively control the activation of the various fob 102 components.
[0053] FIG. 3 illustrates an exemplary block diagram of a RFID reader 104 in accordance with an exemplary embodiment of the present invention. RFID reader 104 includes, for example, an antenna 106 coupled to a RF module 302, which is further coupled to a control module 304. In addition, RFID reader 104 may include an antenna 108 positioned remotely from the RFID reader 104 and coupled to RFID reader 104 via a suitable cable 120, or other wire or wireless connection.
[0054] RF module 302 and antenna 106 may be suitably configured to facilitate communication with fob 102. Where fob 102 is formatted to receive a signal at a particular RF frequency, RF module 302 may be configured to provide an interrogation signal at that same frequency. For example, in one exemplary embodiment, fob 102 may be configured to respond to an interrogation signal of about 13.56 MHz. In this case, RFID antenna 106 may be 13 MHz and may be configured to transmit an interrogation signal of about 13.56 MHz. That is, fob 102 may be configured to include a first and second RF module (e.g., transponder) where the first module may operate using a 134 kHz frequency and the second RF module may operate using a 13.56 MHz frequency. The RFID reader 104 may include two receivers which may operate using the 134 kHz frequency, the 13.56 MHz frequency or both. When the reader 104 is operating at 134 kHz frequency, only operation with the 134 kHz module on the fob 102 may be possible. When the reader 104 is operating at the 13.56 MHz frequency, only operation with the 13.56 MHz module on the fob 102 may be possible. Where the reader 104 supports both a 134 kHz frequency and a 13.56 MHz RF module, the fob 102 may receive both signals from the reader 104. In this case, the fob 102 may be configured to prioritize selection of the one or the other frequency and reject the remaining frequency. Alternatively, the reader 104 may receive signals at both frequencies from the fob upon interrogation. In this case, the reader 104 may be configured to prioritize selection of one or the other frequency and reject the remaining frequency.
[0055] Further, protocol/sequence controller 314 may include an optional feedback function for notifying the user of the status of a particular transaction. For example, the optional feedback may be in the form of an LED, LED screen and/or other visual display which is configured to light up or display a static, scrolling, flashing and/or other message and/or signal to inform the fob 102 user that the transaction is initiated (e.g., fob is being interrogated), the fob is valid (e.g., fob is authenticated), transaction is being processed, (e.g., fob account number is being read by RFID reader) and/or the transaction is accepted or denied (e.g., transaction approved or disapproved). Such an optional feedback may or may not be accompanied by an audible indicator (or may present the audible indicator singly) for informing the fob 102 user of the transaction status. The audible feedback may be a simple tone, multiple tones, musical indicator, and/or voice indicator configured to signify when the fob 102 is being interrogated, the transaction status, or the like.
[0056] RFID antenna 106 may be in communication with a transponder 306 for transmitting an interrogation signal and receiving at least one of an authentication request signal and/or an account data from fob 102. Transponder 306 may be of similar description as transponder 114 of FIG. 2 . In particular, transponder 306 may be configured to send and/or receive RF signals in a format compatible with antenna 202 in similar manner as was described with respect to fob transponder 114. For example, where transponder 306 is 13.56 MHz RF rated antenna 202 may be 13.56 MHz compatible. Similarly, where transponder 306 is ISO/IEC 14443 rated, antenna 106 may be ISO/IEC 14443 compatible.
[0057] RF module 302 may include, for example, transponder 306 in communication with authentication circuitry 308 which may be in communication with a secure database 310. Authentication circuitry 308 and database 310 may be of similar description and operation as described with respect to authentication circuitry 210 and secure memory database 212 of FIG. 2 . For example, database 310 may store data corresponding to the fob 102 which are authorized to transact business over system 100. Database 310 may additionally store RFID reader 104 identifying information for providing to fob 102 for use in authenticating whether RFID reader 104 is authorized to be provided the fob account number stored on fob database 214.
[0058] Authentication circuitry 308 may be of similar description and operation as authentication circuitry 210. That is, authentication circuitry 308 may be configured to authenticate the signal provided by fob 102 in similar manner that authentication circuitry 210 may be configured to authenticate the signal provided by RFID reader 104. As is described more fully below, fob 102 and RFID reader 104 engage in mutual authentication. In this context, “mutual authentication” may mean that operation of the system 100 may not take place until fob 102 authenticates the signal from RFID reader 104, and RFID reader 104 authenticates the signal from fob 102.
[0059] FIG. 4 is a flowchart of an exemplary authentication process in accordance with the present invention. The authentication process is depicted as one-sided. That is, the flowchart depicts the process of the RFID reader 104 authenticating the fob 102, although similar steps may be followed in the instance that fob 102 authenticates RFID reader 104.
[0060] As noted, database 212 may store security keys for encrypting or decrypting signals received from RFID reader 104. In an exemplary authentication process, where RFID reader 104 is authenticating fob 102, RFID reader 104 may provide an interrogation signal to fob 102 (step 402). The interrogation signal may include a random code generated by the RFID reader authentication circuit 210, which is provided to the fob 102 and which is encrypted using an unique encryption key corresponding to the fob 102 unique identification code. For example, the protocol/sequence controller 314 may provide a command to activate the authentication circuitry 308. Authentication circuitry 308 may provide from database 310 a fob interrogation signal including a random number as a part of the authentication code generated for each authentication signal. The authentication code may be an alphanumeric code which is recognizable (e.g., readable) by the RFID reader 104 and the fob 102. The authentication code may be provided to the fob 102 via the RFID RF interface 306 and antenna 106 (or alternatively antenna 108).
[0061] Fob 102 receives the interrogation signal (step 404). The interrogation signal including the authorization code may be received at the RF interface 114 via antenna 202. Once the fob 102 is activated, the interrogation signal including the authorization code may be provided to the modulator/demodulator circuit 206 where the signal may be demodulated prior to providing the signal to protocol/sequence controller 208. Protocol/sequence controller 208 may recognize the interrogation signal as a request for authentication of the fob 102, and provide the authentication code to authentication circuit 210. The fob 102 may then encrypt the authentication code (step 406). In particular, encryption may be done by authentication circuit 210, which may receive the authentication code and encrypt the code prior to providing the encrypted authentication code to protocol/sequence controller 208. Fob 102 may then provide the encrypted authentication code to the RFID reader 104 (step 408). That is, the encrypted authentication code may be provided to the RFID reader 104 via modulator/demodulator circuit 206, RF interface 114 (e.g., transponder 114) and antenna 202.
[0062] RFID reader 104 may then receive the encrypted authentication code and decryption it (step 410). That is, the encrypted authentication code may be received at antenna 106 and RF interface 306 and may be provided to authentication circuit 308. Authentication circuit 308 may be provided a security authentication key (e.g., transponder system decryption key) from database 310. The authentication circuit may use the authentication key to decrypt (e.g., unlock) the encrypted authorization code. The authentication key may be provided to the authentication circuit based on the fob 102 unique identification code. For example, the encrypted authentication code may be provided along with the unique fob 102 identification code. The authentication circuit may receive the fob 102 unique identification code and retrieve from the database 310 a transponder system decryption key correlative to the unique fob 102 identification code for use in decrypting the encrypted authentication code.
[0063] Once the authentication code is decrypted, the decrypted authentication code is compared to the authentication code provided by the RFID reader 104 at (step 402 (step 412) to verify its authenticity. If the decrypted authorization code is not readable (e.g., recognizable) by the authentication circuit 308, the fob 102 is deemed to be unauthorized (e.g., unverified) (step 416) and the operation of system 100 is terminated (step 418). Contrarily, if the decrypted authorization code is recognizable (e.g., verified) by the fob 102, the decrypted authorization code is deemed to be authenticated (step 412), and the transaction is allowed to proceed (step 414). In one particular embodiment, the proceeding transaction may mean that the fob 102 may authenticate the RFID reader 104 prior to the RFID reader 104 authenticating fob 102 although, it should be apparent that the RFID reader 104 may authenticate the fob 102 prior to the for 102 authenticating the RFID reader 104.
[0064] It should be noted that in an exemplary verification process, the authorization circuit 308 may determine whether the unlocked authorization code is identical to the authorization code provided in step 402. If the codes are not identical then the fob 102 is not authorized to access system 100. Although, the verification process is described with respect to identicality, identicality is not required. For example, authentication circuit 308 may verify the decrypted code through any protocol, steps, or process for determining whether the decrypted code corresponds to an authorized fob 102.
[0065] Authentication circuitry 308 may additionally be in communication with a protocol/sequence controller 314 of similar operation and description as protocol/sequence controller 208 of FIG. 2 . That is, protocol/sequence device controller 314 may be configured to determine the order of operation of the RFID reader 104 components. For example, FIG. 5 illustrates and exemplary decision process under which protocol/sequence controller 314 may operate. Protocol/sequence controller 314 may command the different components of RFID reader 104 based on whether a fob 102 is present (step 502). For example, if a fob 102 is not present, then protocol/sequence controller 314 may command the RFID reader 104 to provide an uninterrupted interrogation signal (step 504). That is, the protocol/sequence controller may command the authentication circuit 308 to provide an uninterrupted interrogation signal until the presence of a fob 102 is realized. If a fob 102 is present, the protocol/sequence controller 314 may command the RFID reader 104 to authenticate the fob 102 (step 506).
[0066] As noted above, authentication may mean that the protocol/sequence controller 314 may command the authentication circuit 308 to provide fob 102 with an authorization code. If a response is received from fob 102, protocol/sequence controller may determine if the response is a response to the RFID reader 104 provided authentication code, or if the response is a signal requiring authentication (step 508). If the signal requires authentication, then the protocol/sequence controller 314 may activate the authentication circuit as described above (step 506). On the other hand, if the fob 102 signal is a response to the provided authentication code, then the protocol/sequence controller 314 may command the RFID reader 104 to retrieve the appropriate security key for enabling recognition of the signal (step 510). That is, the protocol/sequence controller 314 may command the authentication circuit 308 to retrieve from database 310 a security key (e.g., transponder system decryption key), unlock the signal, and compare the signal to the signal provided by the RFID reader 104 in the authentication process (e.g., step 506). If the signal is recognized, the protocol/sequence controller 314 may determine that the fob 102 is authorized to access the system 100. If the signal is not recognized, then the fob is considered not authorized. In which case, the protocol/sequence controller 314 may command the RFID controller to interrogate for authorized fobs (step 504).
[0067] Once the protocol/sequence controller determines that the fob 102 is authorized, the protocol/sequence controller 314 may seek to determine if additional signals are being sent by fob 102 (step 514). If no additional signal is provided by fob 102, then the protocol/sequence controller 314 may provide all the components of RFID reader 104 to remain idle until such time as a signal is provided (step 516). Contrarily, where an additional fob 102 signal is provided, the protocol/sequence controller 314 may determine if the fob 102 is requesting access to the merchant point of sale terminal 110 (e.g., POS device) or if the fob 102 is attempting to interrogate the RFID reader 104 for return (e.g., mutual) authorization (step 518). Where the fob 102 is requesting access to a merchant point of sale terminal 110, the protocol/sequence controller 314 may command the RFID reader to open communications with the point of sale terminal 110 (step 524). In particular, the protocol/sequence controller may command the point of sale terminal communications interface 312 to become active, permitting transfer of data between the RFID reader 104 and the merchant point of sale terminal 110.
[0068] On the other hand, if the protocol/sequence controller determines that the fob 102 signal is a mutual interrogation signal, then the protocol/sequence controller may command the RFID reader 104 to encrypt the signal (step 520). The protocol/sequence controller 314 may command the encryption authentication circuit 318 to retrieve from database 320 the appropriate encryption key in response to the fob 102 mutual interrogation signal. The protocol/sequence controller 314 may then command the RFID reader 104 to provide the encrypted mutual interrogation signal to the fob 102. The protocol/sequence controller 314 may command the authentication circuit 318 to provide an encrypted mutual interrogation signal for the fob 102 to mutually authenticate. Fob 102 may then receive the encrypted mutual interrogation signal and retrieve from authentication circuitry 212 a RFID reader decryption key.
[0069] Although an exemplary decision process of protocol/sequence controller 314 is described, it should be understood that a similar decision process may be undertaken by protocol/sequence controller 208 in controlling the components of fob 102. Indeed, as described above, protocol/sequence controller 314 may have similar operation and design as protocol/sequence controller 208. In addition, to the above, protocol/sequence controllers 208 and 314 may incorporate in the decision process appropriate commands for enabling USB interfaces 222 and 316, when the corresponding device is so connected.
[0070] Encryption/decryption component 318 may be further in communication with a secure account number database 320 which stores the security keys necessary for decrypting the encrypted fob account number. Upon appropriate request from protocol/sequence controller 314, encryption/decryption component (e.g., circuitry 318) may retrieve the appropriate security key, decrypt the fob account number and forward the decrypted account number to protocol sequence controller 314 in any format readable by any later connected POS device 110. In one exemplary embodiment, the account number may be forwarded in a conventional magnetic stripe format compatible with the ISO/IEC 7813 standard. Upon receiving the account number in magnetic stripe format, protocol/sequence controller 314 may forward the account number to POS device 110 via a communications interface 312 and data link 122, as best shown in FIG. 1 . POS device 110 may receive the decrypted account number and forward the magnetic stripe formatted account number to a merchant network 112 for processing under the merchant's business as usual standard. In this way, the present invention eliminates the need of a third-party server. Further, where the POS device 110 receives a response from network 112 (e.g., transaction authorized or denied), protocol/sequence controller 314 may provide the network response to the RF module 302 for optically and/or audibly communicating the response to the fob 102 user.
[0071] RFID reader 104 may additionally include a USB interface 316, in communication with the protocol/sequence controller 314. In one embodiment, the USB interface may be a RS22 serial data interface. Alternatively, the RFID reader 104 may include a serial interface such as, for example, a RS232 interface in communication with the protocol/sequence controller 314. The USB connector 316 may be in communication with a personalization system 116 (shown in FIG. 1B ) for initializing RFID reader 104 to system 100 application parameters. That is, prior to operation of system 100, RFID reader 104 may be in communication with personalization system 116 for populating database 310 with a listing of security keys belonging to authorized fobs 102, and for populating database 320 with the security keys to decrypt the fob 102 account numbers placing the account numbers in ISO/IEC 7813 format. In this way, RFID reader 104 may be populated with a unique identifier (e.g., serial number) which may be used by fob authentication circuitry 210 to determine if RFID reader 104 is authorized to receive a fob 102 encrypted account number.
[0072] FIG. 1B illustrates an exemplary personalization system 10B, in accordance with the present invention. In general, typical personalization system 100B may be any system for initializing the RFID reader 104 and fob 102 for use in system 100A. With reference to FIG. 1B , the similar personalization process for fob 102 may be illustrated. For example, personalization system 116 may be in communication with fob 102 via RF ISO 14443 interface 114 for populating fob database 212 with the security keys for facilitating authentication of the unique RFID reader 104 identifier. In addition, personalization system 116 may populate on database 212 a unique fob 102 identifier for use by RFID reader 104 in determining whether fob 102 is authorized to access system 100. Personalization system 116 may populate (e.g., inject) the encrypted fob 102 account number into fob database 214 for later providing to an authenticated RFID reader 104.
[0073] In one exemplary embodiment, personalization system 116 may include any standard computing system as described above. For example, personalization system 116 may include a standard personal computer containing a hardware security module operable using any conventional graphic user interface. Prior to populating the security key information account number and unique identifying information into the fob 102 or RFID reader 104, the hardware security module may authenticate the fob 102 and RFID reader 104 to verify that the components are authorized to receive the secure information.
[0074] FIGS. 6A-B illustrate an exemplary flowchart of a personalization procedure which may be used to personalize fob 102 and/or RFID reader 104. Although the following description discusses mainly personalization of fob 102, RFID reader 104 may be personalized using a similar process. The personalization process, which occurs between the personalization system 116 and the device to be personalized (e.g., fob 102 or RFID reader 104), may begin, for example at step 602. Mutual authentication may occur between the personalization system 116 and the device to be authenticated in much the same manner as was described above with regard to fob 102 mutually authenticating with RFID reader 104. That is, personalization system 116 may transmit a personalization system 116 identifier to the device to be authenticated which is compared by the device authentication circuitry 210, 308 against personalization system identifiers stored in the device database 212, 310. Where a match does not occur (step 604), the personalization process may be aborted (step 612). Where a match occurs (step 604), the personalization system may prepare a personalization file to be provided to the device to be personalized (step 606). If the personalization system is operated manually, the personalization file may be entered into the personalization system 116 using any suitable system interface such as, for example, a keyboard (step 606). Where the personalization system 116 operator elects to delay the preparation of the personalization files, the system 116 may abort the personalization process (step 610). In this context, the personalization file may include the unique fob 102 or RFID reader 104 identifier, security key for loading into database 212 and 310, and/or security keys for decrypting a fob account number which may be loaded in database 320.
[0075] Fob 102 may be personalized by direct connection to the personalization system 116 via RF ISO/IEC 14443 interface 114, or the fob 102 may be personalized using RFID reader 104. Personalization system 116 and RFID reader 104 may engage in mutual authentication and RFID reader 104 may be configured to transmit the fob personalization file to fob 102 via RF. Once the fob 102 is presented to RFID reader 104 (steps 608, 614) for personalization, fob 102 and RFID reader 104 may engage in mutual authentication (step 614). Where the fob 102 is not presented to the RFID reader 104 for personalization, the personalization process may be aborted (step 610).
[0076] If the fob 102 is detected, the personalization system 116 may create as a part of the personalization file, a unique identifier for providing to the fob 102 (step 616). The identifier is unique in that one identifier may be given only to a single fob. That is, no other fob may have that same identifier. The fob may then be configured and loaded with that identifier (step 618).
[0077] The encrypted fob 102 account number may be populated into fob 102 in the same manner as is described with respect to the fob 102 unique identifier. That is, personalization system 116 may pre-encrypt the account data (step 640) and inject the encrypted account into fob database 214 (step 622). The encrypted account data may be loaded (e.g., injected) into the fob 102 using RFID reader 104 as discussed above.
[0078] Once the personalization file is populated into the fob 102, the populated information is irreversibly locked to prevent alteration, unauthorized reading and/or unauthorized access (step 624). Personalization system 116 may then create a log of the personalization file information for later access and analysis by the personalization system 116 user (step 626).
[0079] It should be noted that in the event the personalization process is compromised or interrupted (step 628), the personalization system 116 may send a security alert to the user (step 630) and the personalization process may be aborted (step 612). On the other hand, where no such compromising or interruption exists, the personalization system 116 may be prepared to begin initialization on a second device to be personalized (step 632).
[0080] FIGS. 7A-B illustrate another exemplary embodiment of a personalization process which may be used to personalize RFID reader 104. RFID reader 104 may be in communication with a personalization system 116 via RFID reader USB connection 316 (step 702). Once connected, personalization system 116 may establish communications with the RFID reader 104 and RFID reader 104 may provide personalization system 116 any RFID reader 104 identification data presently stored on the RFID reader 104 (step 704). In accordance with step 708, where the RFID reader 104 is being personalized for the first time (step 706) the RFID reader 104 and the personalization system 116 may engage in mutual authentication as described above with respect to FIGS. 6A-B . After the mutual authentication is complete, personalization system 116 may verify that RFID reader 104 is properly manufactured or configured to operate within system 100. The verification may include evaluating the operation of the RFID reader 104 by determining if the RFID reader will accept predetermined default settings. That is, the personalization system 116 may then provide the RFID reader 104 a set of default settings (step 708) and determine if the RFID reader 104 accepts those settings (step 712). If RFID reader 104 does not accept the default settings, personalization system 116 may abort the personalization process (step 714).
[0081] If the personalization system 116 determines that the personalization process is not the first personalization process undertaken by the RFID reader 104 (step 706), personalization system 116 and RFID reader 104 may engage in a mutual authentication process using the existing security keys already stored on RFID reader 104 (step 710). If authentication is unsuccessful (step 712), the personalization system 116 may abort the personalization process (step 714).
[0082] Where the personalization system 116 and the RFID reader 104 successfully mutually authenticate, the personalization system 116 may update the RFID reader 104 security keys (step 716). Updating the security keys may take place at any time as determined by a system 100 manager. The updating may take place as part of a routine maintenance or merely to install current security key data. The updating may be performed by downloading firmware into RFID reader 104 (step 718). In the event that the personalization system determines in step 706 that the RFID reader 104 is undergoing an initial personalization, the firmware may be loaded into the RFID reader 104 for the first time. In this context, “firmware” may include any file which enables the RFID reader 102 to operate under system 100 guidelines. For example, such guidelines may be directed toward the operation of RFID reader protocol/sequence controller 314.
[0083] Personalization system 116 may then determine if the personalization keys (e.g., security keys, decryption keys, RFID identifier) need to be updated or if the RFID reader 104 needs to have an initial installation of the personalization keys (step 720). If so, then personalization system 116 may download the personalization keys as appropriate (step 722).
[0084] Personalization system 116 may then check the RFID reader 104 to determine if the fob 102 identifiers and corresponding security keys should be updated or initially loaded (step 724). If no updating is necessary the personalization system 116 may end the personalization procedure (step 732). Contrarily, if the personalization system 116 determines that the fob 102 identifiers and corresponding keys need to be updated or installed, the personalization system 116 may download the information onto RFID reader 104 (step 726). The information (e.g., fob security keys and identifiers) may be downloaded in an encrypted format and the RFID reader 104 may store the information in the RFID reader database 310 as appropriate (step 728). The personalization system 116 may then create or update a status log cataloging for later use and analysis by the personalization system 116 user (step 730). Upon updating the status log, the personalization process may be terminated (step 732).
[0085] It should be noted that, in some instances it may be necessary to repersonalize the RFID reader in similar manner as described above. In that instance, the personalization process described in FIGS. 7A and 7B may be repeated.
[0086] FIG. 8 illustrates an exemplary flow diagram for the operation of system 100A. The operation may be understood with reference to FIG. 1A , which depicts the elements of system 100A which may be used in an exemplary transaction. The process is initiated when a customer desires to present a fob 102 for payment (step 802). Upon presentation of the fob 102, the merchant initiates the RF payment procedure via an RFID reader 104 (step 804). In particular, the RFID reader sends out an interrogation signal to scan for the presence of fob 102 (step 806). The RF signal may be provided via the RFID reader antenna 106 or optionally via an external antenna 108. The customer then may present the fob 102 for payment (step 808) and the fob 102 is activated by the RF interrogation signal provided.
[0087] The fob 102 and the RFID reader 104 may then engage in mutual authentication (step 810). Where the mutual authentication is unsuccessful, an error message may be provided to the customer via the RFID optical and/or audible indicator (step 814) and the transaction may be aborted (step 816). Where the mutual authentication is successful (step 814), the RFID reader 104 may provide the customer with an appropriate optical and/or audible message (e.g., “transaction processing” or “wait”) (step 818). The fob protocol/sequence controller 208 may then retrieve from database 214 an encrypted fob account number and provide the encrypted account number to the RFID reader 104 (step 820).
[0088] The RFID reader 104 may then decrypt the account number and convert the account number into magnetic stripe (ISO/IEC 7813) format (step 822) and provide the unencrypted account number to the merchant system 130 (step 828). In particular, the account number may be provided to the POS 110 device for transmission to the merchant network 112 for processing under known business transaction standards. The POS device 110 may then send an optical and/or audible transaction status message to the RFID reader 104 (step 830) for communication to the customer (step 832).
[0089] It should be noted that the transaction account associated with the fob 102 may include a restriction, such as, for example, a per purchase spending limit, a time of day use, a day of week use, certain merchant use and/or the like, wherein an additional verification is required when using the fob outside of the restriction. The restrictions may be personally assigned by the fob 102 user, or the account provider. For example, in one exemplary embodiment, the account may be established such that purchases above $X (i.e., the spending limit) must be verified by the customer. Such verification may be provided using a suitable personal identification number (PIN) which may be recognized by the RFID reader 104 or a payment authorization center (not shown) as being unique to the fob 102 holder (e.g., customer) and the correlative fob 102 transaction account number. Where the requested purchase is above the established per purchase spending limit, the customer may be required to provide, for example, a PIN, biometric sample and/or similar secondary verification to complete the transaction.
[0090] Where a verification PIN is used as secondary verification the verification PIN may be checked for accuracy against a corroborating PIN which correlates to the fob 102 transaction account number. The corroborating PIN may be stored locally (e.g., on the fob 102, or on the RFID reader 104) or may be stored on a database (not shown) at the payment authorization center. The payment authorization center database may be any database maintained and operated by the fob 102 transaction account provider.
[0091] The verification PIN may be provided to the POS device 110 using a conventional merchant (e.g., POS) PIN key pad 118 in communication with the POS device 110 as shown in FIG. 1 , or a RFID keypad in communication with the RFID reader 104. PIN keypad may be in communication with the POS device 110 (or alternatively, RFID reader 104) using any conventional data link described above. Upon receiving the verification PIN, the RFID reader 104 may seek to match the PIN to the corroborating PIN stored on the RFID reader 104 at database 310 or 320. Alternatively, the verification PIN may be provided to a payment authorization center to determine whether the PIN matches the PIN stored on the payment authorization center database which correlates to the fob 102 account. If a match is made, the purchase may no longer be restricted, and the transaction may be allowed to be completed.
[0092] In an alternate embodiment, verification of purchases exceeding the established spending limit may involve biometrics circuitry included in fob 102. FIG. 9 is a schematic block diagram of an exemplary fob 102 wherein fob 102 includes a biometric security system 902. Biometric security system 902 may include a biometric sensor 904 for sensing the fingerprint of the fob 102 user. The biometric sensor 902 may be in communication with a sensor interface/driver 906 for receiving the sensor fingerprint and activating the operation of fob 102. In communication with the biometric sensor 904 and sensor interface 906 may be a battery 903 for providing the necessary power for operation of the biometric security system components.
[0093] In one exemplary application of the fob 102 including the biometric security system 902, the customer may place his finger on the biometric sensor to initiate the mutual authentication process between the fob 102 and the RFID reader 104, or to provide secondary verification of the user's identity. The sensor fingerprint may be digitized and compared against a digitized fingerprint stored in a database (e.g., security database 212) included on fob 102. Such comparison step may be controlled by protocol/sequence controller 208 and may be validated by authentication circuit 210. Where such verification is made, the mutual authentication between fob 102 and RFID reader 104 may begin, and the transaction may proceed accordingly. Alternatively, the comparison may be made with a digitized fingerprint stored on a database maintained by the fob 102 transaction account provider system (not shown). The digitized fingerprint may be verified in much the same way as is described above with respect to the PIN.
[0094] In one exemplary application of the fob 102 including the biometric security system 902, the system 902 may be used to authorize a purchase exceeding the established per purchase spending limit. In this case, where the customer's intended purchase exceeds the spending limit, the customer may be asked to provide assurance that the purchase is authorized. Accordingly, the customer may provide such verification by placing his finger over the biometric sensor 904. The biometric sensor 904 may then digitize the fingerprint and provide the digitized fingerprint for verification as described above. Once verified, fob 102 may provide a transaction authorized signal to RF transponder 202 (or alternatively to transponder 220) for forwarding to RFID reader 104. RFID reader 104 may then provide the transaction authorized signal to the POS device 110 in similar manner as is done with convention PIN driven systems and the POS device 110 may process the transaction under the merchant's business as usual standard.
[0095] The preceding detailed description of exemplary embodiments of the invention makes reference to the accompanying drawings, which show the exemplary embodiment by way of illustration. While these exemplary embodiments are described in sufficient detail to enable those skilled in the art to practice the invention, it should be understood that other embodiments may be realized and that logical and mechanical changes may be made without departing from the spirit and scope of the invention. Thus, the preceding detailed description is presented for purposes of illustration only and not of limitation, and the scope of the invention is defined solely by the appended claims and their legal equivalents when properly read in light of the preceding description. For example, the steps recited in any of the method or process claims may be executed in any order and are not limited to the order presented.
Claims
Certificate of Correction present
The claims shown below may not include correction changes. Use the corrected PDF for authoritative text.
We claim:
1. A transponder-reader payment system comprising:
a Radio Frequency Identification (RFID) reader configured to provide a first radio frequency (RF) interrogation signal for powering a transponder system, to receive a transponder system RF signal, and to communicate transponder system account data related to said transponder system RF signal to a merchant system, said RFID reader including,
a first interrogator for providing said first RF interrogation signal;
an RFID reader authentication circuit in communication with said first interrogator for authenticating said transponder system RF signal;
an RFID reader database for storing RFID reader data, said RFID reader database in communication with said RFID reader authentication circuit;
an RFID reader protocol/sequence controller in communication with at least one of said first interrogator, said RFID reader authentication circuit, and said RFID reader database, said RFID reader protocol/sequence controller configured to facilitate control of an order of operation of said first interrogator, said RFID reader authentication circuit, and said RFID reader database; and
an RFID reader communications interface configured to communicate with said merchant system, said RFID reader communications interface configured to provide said transponder system account data,
wherein said transponder system is configured to receive said first RF interrogation signal, to authenticate said first RF interrogation signal, and to transmit said transponder system account data, said transponder system further comprising:
a first transponder responsive to said first RF interrogation signal;
a transponder system authentication circuit in communication with said first transponder, said transponder system authentication circuit configured to authenticate said first RF interrogation signal;
a transponder system database for storing said transponder system account data, said transponder system database in communication with said transponder system authentication circuit; and
a transponder system protocol/sequence controller in communication with at least one of said first transponder, said transponder system authentication circuit, and said transponder system database, said transponder system protocol/sequence controller configured to control the order of operation of said first transponder, said transponder system authentication circuit, and said transponder system database,
wherein said transponder system protocol/sequence controller is configured to activate said transponder system authentication circuit in response to said first RF interrogation signal having an RFID reader authentication code, said transponder system authentication circuit configured to encrypt said RFID reader authentication code to provide an encrypted RFID reader authentication code, said transponder system authentication circuit configured to provide said encrypted RFID reader authentication code to said first transponder for providing to said RFID reader,
wherein said RFID reader is configured to receive said encrypted RFID reader authentication code, and wherein said RFID reader protocol/sequence controller is configured to activate said RFID reader authentication circuit in response to said encrypted RFID reader authentication code,
wherein said RFID reader database is configured to provide a transponder system decryption security key to said RFID reader authentication circuit in response to said encrypted RFID reader authentication code, said transponder system decryption security key for use in decrypting said encrypted RFID reader authentication code to form a decrypted RFID reader authentication code, said transponder system decryption security key provided to said RFID reader based on an unique transponder identification code,
wherein said RFID reader authentication circuit is configured to compare said decrypted RFID reader authentication code and said RFID reader authentication code to determine whether a match exists, and
wherein said RFID reader protocol/sequence controller is configured to activate said RFID reader communications interface where said RFID reader authentication circuit matches said decrypted RFID reader authentication code and said RFID reader authentication code.
2. The system according to claim 1, wherein said transponder system protocol/sequence controller activates said transponder system authentication circuit in response to said first RF interrogation signal.
3. The claim according to claim 2, wherein said transponder system authentication circuit is configured to provide a transponder authentication code to said first transponder for providing to said RFID reader.
4. The system according to claim 3, wherein said RFID reader authentication circuit is configured to receive said transponder authentication code, said RFID reader protocol/sequence controller activating said RFID reader authentication circuit in response to said transponder authentication code, said RFID reader authentication circuit configured to encrypt said transponder authentication code to form an encrypted transponder authentication code.
5. The system according to claim 4, wherein said RFID reader is configured to provide said encrypted transponder authentication code to said transponder system.
6. The system according to claim 5, wherein said transponder system database is configured to store at least one of a transponder system identification data and an RFID reader decryption security key.
7. The system according to claim 6, wherein said transponder system database is configured to provide said RFID reader decryption security key to said transponder system authentication circuit in response to said encrypted transponder authentication code, said RFID reader decryption security key for use in decrypting said encrypted transponder authentication code to form a decrypted transponder authentication code.
8. The system according to claim 7, wherein said transponder system authentication circuit is configured to compare said decrypted transponder authentication code and said transponder authentication code to determine whether a match exists.
9. The system according to claim 8, wherein said transponder system account data is in magnetic stripe format.
10. The system according to claim 9, wherein said transponder system account data is encrypted as a pre-encrypted transponder system account data.
11. The system according to claim 10, wherein said transponder system database is configured to provide said pre-encrypted transponder system account data to said RFID reader when said transponder system authentication circuit matches said decrypted transponder authentication code and said transponder authentication code.
12. The system according to claim 11, wherein said RFID reader communications interface is configured to provide a transponder system PIN and said pre-encrypted transponder system account data when said transponder authentication code matches said decrypted transponder authentication code, and said decrypted RFID reader authentication code matches said RFID reader authentication code.
Patent Citations (484)
| Patent | Date | Inventor | Cited By |
|---|---|---|---|
| US3914762(A) | 1975-10-01 | Klensch | Examiner |
| US4303904(A) | 1981-12-01 | Chasek | Applicant |
| US4475308(A) | 1984-10-01 | Heise et al. | Applicant |
| US4583766(A) | 1986-04-01 | Wessel | Applicant |
| US4639765(A) | 1987-01-01 | d'Hont | Applicant |
| US4656463(A) | 1987-04-01 | Anders et al. | Examiner |
| US4672021(A) | 1987-06-01 | Blumel et al. | Applicant |
| US4739328(A) | 1988-04-01 | Koelle et al. | Applicant |
| US4918432(A) | 1990-04-01 | Pauley et al. | Examiner |
| US4961142(A) | 1990-10-01 | Elliott et al. | Applicant |
| US4984270(A) | 1991-01-01 | LaBounty | Applicant |
| US5023782(A) | 1991-06-01 | Lutz et al. | Applicant |
| US5053774(A) | 1991-10-01 | Schuermann et al. | Applicant |
| US5099226(A) | 1992-03-01 | Andrews | Examiner |
| US5101200(A) | 1992-03-01 | Swett | Applicant |
| US5197140(A) | 1993-03-01 | Balmer | Applicant |
| US5206488(A) | 1993-04-01 | Teicher | Applicant |
| US5212777(A) | 1993-05-01 | Gove et al. | Applicant |
| US5221838(A) | 1993-06-01 | Gutman et al. | Applicant |
| US5222282(A) | 1993-06-01 | Sukonnik et al. | Applicant |
| US5226989(A) | 1993-07-01 | Sukonnik | Applicant |
| US5239654(A) | 1993-08-01 | Ing-Simmons et al. | Applicant |
| US5247304(A) | 1993-09-01 | d'Hont | Applicant |
| US5274392(A) | 1993-12-01 | d'Hont et al. | Applicant |
| US5285100(A) | 1994-02-01 | Byatt | Applicant |
| US5305002(A) | 1994-04-01 | Holodak et al. | Applicant |
| US5329617(A) | 1994-07-01 | Asal | Applicant |
| US5331138(A) | 1994-07-01 | Saroya | Applicant |
| US5339447(A) | 1994-08-01 | Balmer | Applicant |
| US5349357(A) | 1994-09-01 | Schurmann et al. | Applicant |
| US5351052(A) | 1994-09-01 | d'Hont et al. | Applicant |
| US5371896(A) | 1994-12-01 | Gove et al. | Applicant |
| US5373303(A) | 1994-12-01 | d'Hont | Applicant |
| US5407893(A) | 1995-04-01 | Koshizuka et al. | Applicant |
| US5408243(A) | 1995-04-01 | d'Hont | Applicant |
| US5410649(A) | 1995-04-01 | Gove | Applicant |
| US5428363(A) | 1995-06-01 | d'Hont | Applicant |
| US5453747(A) | 1995-09-01 | d'Hont et al. | Applicant |
| US5471592(A) | 1995-11-01 | Gove et al. | Applicant |
| US5485510(A) | 1996-01-01 | Colbert | Applicant |
| US5488376(A) | 1996-01-01 | Hurta et al. | Applicant |
| US5489411(A) | 1996-02-01 | Jha et al. | Applicant |
| US5489908(A) | 1996-02-01 | Orthmann et al. | Applicant |
| US5490079(A) | 1996-02-01 | Sharpe et al. | Applicant |
| US5491483(A) | 1996-02-01 | d'Hont | Applicant |
| US5491484(A) | 1996-02-01 | Schuermann | Applicant |
| US5491715(A) | 1996-02-01 | Flaxl | Applicant |
| US5493312(A) | 1996-02-01 | Knebelkamp | Applicant |
| US5497121(A) | 1996-03-01 | d'Hont | Applicant |
| US5500651(A) | 1996-03-01 | Schuermann | Applicant |
| US5513525(A) | 1996-05-01 | Schurmann | Applicant |
| US5519381(A) | 1996-05-01 | Marsh et al. | Applicant |
| US5522083(A) | 1996-05-01 | Gove et al. | Applicant |
| US5525992(A) | 1996-06-01 | Froschermeier | Applicant |
| US5525994(A) | 1996-06-01 | Hurta et al. | Applicant |
| US5530232(A) | 1996-06-01 | Taylor | Applicant |
| US5541604(A) | 1996-07-01 | Meier | Applicant |
| US5543798(A) | 1996-08-01 | Schuermann | Applicant |
| US5544246(A) | 1996-08-01 | Mandelbaum et al. | Applicant |
| US5548291(A) | 1996-08-01 | Meier et al. | Applicant |
| US5550536(A) | 1996-08-01 | Flaxl | Applicant |
| US5550548(A) | 1996-08-01 | Schuermann | Applicant |
| US5552789(A) | 1996-09-01 | Schuermann | Applicant |
| US5557279(A) | 1996-09-01 | d'Hont | Applicant |
| US5557516(A) | 1996-09-01 | Hogan | Applicant |
| US5561430(A) | 1996-10-01 | Knebelkamp | Applicant |
| US5563582(A) | 1996-10-01 | d'Hont | Applicant |
| US5569187(A) | 1996-10-01 | Kaiser | Applicant |
| US5572226(A) | 1996-11-01 | Tuttle | Examiner |
| US5577109(A) | 1996-11-01 | Stimson et al. | Applicant |
| US5581630(A) | 1996-12-01 | Bonneau, Jr. | Applicant |
| US5592150(A) | 1997-01-01 | d'Hont | Applicant |
| US5592405(A) | 1997-01-01 | Gove et al. | Applicant |
| US5594233(A) | 1997-01-01 | Kenneth et al. | Applicant |
| US5594448(A) | 1997-01-01 | d'Hont | Applicant |
| US5597534(A) | 1997-01-01 | Kaiser | Applicant |
| US5600175(A) | 1997-02-01 | Orthmann | Applicant |
| US5602538(A) | 1997-02-01 | Orthmann et al. | Applicant |
| US5602919(A) | 1997-02-01 | Hurta et al. | Applicant |
| US5604342(A) | 1997-02-01 | Fujioka | Applicant |
| US5606520(A) | 1997-02-01 | Gove et al. | Applicant |
| US5606594(A) | 1997-02-01 | Register et al. | Applicant |
| US5607522(A) | 1997-03-01 | McDonnell | Applicant |
| US5608406(A) | 1997-03-01 | Eberth et al. | Applicant |
| US5608778(A) | 1997-03-01 | Partridge, III | Applicant |
| US5613146(A) | 1997-03-01 | Gove et al. | Applicant |
| US5619207(A) | 1997-04-01 | d'Hont | Applicant |
| US5621396(A) | 1997-04-01 | Flaxl | Applicant |
| US5621411(A) | 1997-04-01 | Hagl et al. | Applicant |
| US5621412(A) | 1997-04-01 | Sharpe et al. | Applicant |
| US5625366(A) | 1997-04-01 | d'Hont | Applicant |
| US5625370(A) | 1997-04-01 | d'Hont | Applicant |
| US5625695(A) | 1997-04-01 | M'Raihi et al. | Applicant |
| US5629981(A) | 1997-05-01 | Nerlikar | Applicant |
| US5638080(A) | 1997-06-01 | Orthmann et al. | Applicant |
| US5640002(A) | 1997-06-01 | Ruppert et al. | Applicant |
| US5646607(A) | 1997-07-01 | Schurmann et al. | Applicant |
| US5657388(A) | 1997-08-01 | Weiss | Applicant |
| US5660319(A) | 1997-08-01 | Falcone et al. | Applicant |
| US5673106(A) | 1997-09-01 | Thompson | Applicant |
| US5675342(A) | 1997-10-01 | Sharpe | Applicant |
| US5686920(A) | 1997-11-01 | Hurta et al. | Applicant |
| US5691731(A) | 1997-11-01 | van Erven | Applicant |
| US5692132(A) | 1997-11-01 | Hogan | Applicant |
| US5696913(A) | 1997-12-01 | Gove et al. | Applicant |
| US5698837(A) | 1997-12-01 | Furuta | Applicant |
| US5699528(A) | 1997-12-01 | Hogan | Applicant |
| US5701127(A) | 1997-12-01 | Sharpe | Applicant |
| US5704046(A) | 1997-12-01 | Hogan | Applicant |
| US5705798(A) | 1998-01-01 | Tarbox | Applicant |
| US5710421(A) | 1998-01-01 | Kokubu | Applicant |
| US5721781(A) | 1998-02-01 | Deo et al. | Applicant |
| US5729053(A) | 1998-03-01 | Orthmann | Applicant |
| US5729236(A) | 1998-03-01 | Flaxl | Applicant |
| US5731957(A) | 1998-03-01 | Brennan | Applicant |
| US5732579(A) | 1998-03-01 | d'Hont et al. | Applicant |
| US5748137(A) | 1998-05-01 | d'Hont | Applicant |
| US5748737(A) | 1998-05-01 | Daggar | Applicant |
| US5758195(A) | 1998-05-01 | Balmer | Applicant |
| US5761306(A) | 1998-06-01 | Lewis | Applicant |
| US5761493(A) | 1998-06-01 | Blakeley et al. | Applicant |
| US5768609(A) | 1998-06-01 | Gove et al. | Applicant |
| US5774882(A) | 1998-06-01 | Keen et al. | Applicant |
| US5777903(A) | 1998-07-01 | Piosenka | Applicant |
| US5778067(A) | 1998-07-01 | Jones et al. | Applicant |
| US5785680(A) | 1998-07-01 | Niezink et al. | Applicant |
| US5789733(A) | 1998-08-01 | Jachimowicz et al. | Applicant |
| US5792337(A) | 1998-08-01 | Padovani et al. | Applicant |
| US5793324(A) | 1998-08-01 | Aslanidis et al. | Applicant |
| US5794095(A) | 1998-08-01 | Thompson | Applicant |
| US5797060(A) | 1998-08-01 | Thompson | Applicant |
| US5797085(A) | 1998-08-01 | Beuk et al. | Applicant |
| US5797133(A) | 1998-08-01 | Jones et al. | Applicant |
| US5798709(A) | 1998-08-01 | Flaxl | Applicant |
| US5809142(A) | 1998-09-01 | Hurta et al. | Applicant |
| US5809288(A) | 1998-09-01 | Balmer | Applicant |
| US5809633(A) | 1998-09-01 | Mundigl et al. | Applicant |
| US5825007(A) | 1998-10-01 | Jesadanont | Applicant |
| US5825302(A) | 1998-10-01 | Stafford | Examiner |
| US5826077(A) | 1998-10-01 | Blakeley et al. | Applicant |
| US5828044(A) | 1998-10-01 | Jun et al. | Applicant |
| US5834756(A) | 1998-11-01 | Gutman et al. | Applicant |
| US5838257(A) | 1998-11-01 | Lambropoulos | Examiner |
| US5838720(A) | 1998-11-01 | Morelli | Examiner |
| US5841364(A) | 1998-11-01 | Hagl et al. | Applicant |
| US5842088(A) | 1998-11-01 | Thompson | Applicant |
| US5844218(A) | 1998-12-01 | Kawan et al. | Applicant |
| US5844230(A) | 1998-12-01 | Lalonde | Applicant |
| US5845267(A) | 1998-12-01 | Ronen | Applicant |
| US5851149(A) | 1998-12-01 | Xidos et al. | Applicant |
| US5854891(A) | 1998-12-01 | Postlewaite et al. | Applicant |
| US5858006(A) | 1999-01-01 | Van der AA et al. | Applicant |
| US5859779(A) | 1999-01-01 | Giordano et al. | Applicant |
| US5864323(A) | 1999-01-01 | Berthon | Applicant |
| US5867100(A) | 1999-02-01 | d'Hont | Applicant |
| US5870031(A) | 1999-02-01 | Kaiser et al. | Applicant |
| US5870915(A) | 1999-02-01 | d'hont | Applicant |
| US5878215(A) | 1999-03-01 | Kling et al. | Applicant |
| US5878403(A) | 1999-03-01 | DeFrancesco et al. | Applicant |
| US5880675(A) | 1999-03-01 | Trautner | Applicant |
| US5881272(A) | 1999-03-01 | Balmer | Applicant |
| US5887266(A) | 1999-03-01 | Heinonen et al. | Applicant |
| US5890137(A) | 1999-03-01 | Koreeda | Applicant |
| US5898783(A) | 1999-04-01 | Rohrbach | Applicant |
| US5903830(A) | 1999-05-01 | Joao et al. | Applicant |
| US5905798(A) | 1999-05-01 | Nerlikar et al. | Applicant |
| US5912678(A) | 1999-06-01 | Saxena et al. | Applicant |
| US5920628(A) | 1999-07-01 | Indeck et al. | Applicant |
| US5929801(A) | 1999-07-01 | Aslanidis et al. | Applicant |
| US5931917(A) | 1999-08-01 | Nguyen et al. | Applicant |
| US5933624(A) | 1999-08-01 | Balmer | Applicant |
| US5943624(A) | 1999-08-01 | Fox et al. | Applicant |
| US5948116(A) | 1999-09-01 | Aslanidis et al. | Applicant |
| US5950179(A) | 1999-09-01 | Buchanan | Applicant |
| US5953512(A) | 1999-09-01 | Cai et al. | Applicant |
| US5955717(A) | 1999-09-01 | Vanstone | Applicant |
| US5955951(A) | 1999-09-01 | Wischerop et al. | Applicant |
| US5955969(A) | 1999-09-01 | d'Hont | Applicant |
| US5956024(A) | 1999-09-01 | Strickland et al. | Applicant |
| US5963924(A) | 1999-10-01 | Williams et al. | Applicant |
| US5970148(A) | 1999-10-01 | Meier | Applicant |
| USRE36365(E) | 1999-11-01 | Levine et al. | Applicant |
| US5978840(A) | 1999-11-01 | Nguyen et al. | Applicant |
| US5983208(A) | 1999-11-01 | Haller | Applicant |
| US5987140(A) | 1999-11-01 | Rowney et al. | Applicant |
| US5987155(A) | 1999-11-01 | Dunn et al. | Applicant |
| US5987498(A) | 1999-11-01 | Athing et al. | Applicant |
| US5989950(A) | 1999-11-01 | Wu | Applicant |
| US5991608(A) | 1999-11-01 | Leyten | Applicant |
| US5991750(A) | 1999-11-01 | Watson | Applicant |
| US5996076(A) | 1999-11-01 | Rowney et al. | Applicant |
| US6002438(A) | 1999-12-01 | Hocevar et al. | Applicant |
| US6002767(A) | 1999-12-01 | Kramer | Applicant |
| US6003014(A) | 1999-12-01 | Lee et al. | Applicant |
| US6005942(A) | 1999-12-01 | Chan et al. | Applicant |
| US6006216(A) | 1999-12-01 | Griffin et al. | Applicant |
| US6012049(A) | 2000-01-01 | Kawan | Applicant |
| US6014645(A) | 2000-01-01 | Cunningham | Applicant |
| US6018717(A) | 2000-01-01 | Lee et al. | Applicant |
| US6024286(A) | 2000-02-01 | Bradley et al. | Applicant |
| US6029149(A) | 2000-02-01 | Dykstra et al. | Applicant |
| US6038584(A) | 2000-03-01 | Balmer | Applicant |
| US6047888(A) | 2000-04-01 | Dethloff | Applicant |
| US6052675(A) | 2000-04-01 | Checchio | Applicant |
| US6064320(A) | 2000-05-01 | d'Hont et al. | Applicant |
| US6068193(A) | 2000-05-01 | Kreft | Applicant |
| US6070003(A) | 2000-05-01 | Gove et al. | Applicant |
| US6072870(A) | 2000-06-01 | Nguyen et al. | Applicant |
| US6073840(A) | 2000-06-01 | Marion | Applicant |
| US6078888(A) | 2000-06-01 | Johnson, Jr. | Applicant |
| USRE36788(E) | 2000-07-01 | Mansvelt et al. | Applicant |
| US6088686(A) | 2000-07-01 | Walker et al. | Applicant |
| US6092057(A) | 2000-07-01 | Zimmerman et al. | Applicant |
| US6098879(A) | 2000-08-01 | Terranova | Applicant |
| US6101174(A) | 2000-08-01 | Langston | Applicant |
| US6102162(A) | 2000-08-01 | Teicher | Applicant |
| US6102672(A) | 2000-08-01 | Woollenweber | Applicant |
| US6105008(A) | 2000-08-01 | Davis et al. | Applicant |
| US6105013(A) | 2000-08-01 | Curry et al. | Applicant |
| US6105865(A) | 2000-08-01 | Hardesty | Applicant |
| US6107920(A) | 2000-08-01 | Eberhardt et al. | Applicant |
| US6109525(A) | 2000-08-01 | Blomqvist et al. | Applicant |
| US6112152(A) | 2000-08-01 | Tuttle | Applicant |
| US6115360(A) | 2000-09-01 | Quay et al. | Applicant |
| US6116423(A) | 2000-09-01 | Troxtell, Jr. et al. | Applicant |
| US6116505(A) | 2000-09-01 | Withrow | Applicant |
| US6118189(A) | 2000-09-01 | Flaxl | Applicant |
| US6121544(A) | 2000-09-01 | Petsinger | Applicant |
| US6123223(A) | 2000-09-01 | Watkins | Applicant |
| US6129274(A) | 2000-10-01 | Suzuki | Applicant |
| US6130623(A) | 2000-10-01 | MacLellan et al. | Applicant |
| US6133834(A) | 2000-10-01 | Eberth et al. | Applicant |
| US6141651(A) | 2000-10-01 | Riley et al. | Applicant |
| US6157824(A) | 2000-12-01 | Bailey | Applicant |
| US6163771(A) | 2000-12-01 | Walker et al. | Applicant |
| US6167236(A) | 2000-12-01 | Kaiser et al. | Applicant |
| US6177860(B1) | 2001-01-01 | Cromer et al. | Applicant |
| US6179205(B1) | 2001-01-01 | Sloan | Applicant |
| US6179206(B1) | 2001-01-01 | Matsumori | Applicant |
| US6185307(B1) | 2001-02-01 | Johnson, Jr. | Applicant |
| US6188994(B1) | 2001-02-01 | Egendorf | Applicant |
| US6192255(B1) | 2001-02-01 | Lewis et al. | Applicant |
| US6198728(B1) | 2001-03-01 | Hulyalkar et al. | Applicant |
| US6198875(B1) | 2001-03-01 | Edenson et al. | Applicant |
| US6202927(B1) | 2001-03-01 | Bashan et al. | Applicant |
| US6205151(B1) | 2001-03-01 | Quay et al. | Applicant |
| US6206293(B1) | 2001-03-01 | Gutman et al. | Applicant |
| US6213391(B1) | 2001-04-01 | Lewis | Applicant |
| US6215437(B1) | 2001-04-01 | Schurmann et al. | Applicant |
| US6216219(B1) | 2001-04-01 | Cai et al. | Applicant |
| US6219439(B1) | 2001-04-01 | Burger | Applicant |
| USD442627(S) | 2001-05-01 | Webb et al. | Applicant |
| USD442629(S) | 2001-05-01 | Webb et al. | Applicant |
| US6223984(B1) | 2001-05-01 | Renner et al. | Applicant |
| US6226382(B1) | 2001-05-01 | M'Raihi et al. | Applicant |
| US6230270(B1) | 2001-05-01 | Laczko, Sr. | Applicant |
| US6232917(B1) | 2001-05-01 | Baumer et al. | Applicant |
| US6233683(B1) | 2001-05-01 | Chan et al. | Applicant |
| US6237848(B1) | 2001-05-01 | Everett | Applicant |
| US6239675(B1) | 2001-05-01 | Flaxl | Applicant |
| US6240187(B1) | 2001-05-01 | Lewis | Applicant |
| US6257486(B1) | 2001-07-01 | Teicher et al. | Applicant |
| US6259769(B1) | 2001-07-01 | Page | Applicant |
| US6260026(B1) | 2001-07-01 | Tomida et al. | Applicant |
| US6260088(B1) | 2001-07-01 | Gove et al. | Applicant |
| US6263316(B1) | 2001-07-01 | Khan et al. | Applicant |
| US6264106(B1) | 2001-07-01 | Bridgelall | Applicant |
| US6266754(B1) | 2001-07-01 | Laczko, Sr. et al. | Applicant |
| US6273335(B1) | 2001-08-01 | Sloan | Applicant |
| US6282522(B1) | 2001-08-01 | Davis et al. | Applicant |
| USD447515(S) | 2001-09-01 | Faenza, Jr. et al. | Applicant |
| US6286763(B1) | 2001-09-01 | Reynolds et al. | Applicant |
| US6289324(B1) | 2001-09-01 | Kawan | Applicant |
| US6315193(B1) | 2001-11-01 | Hogan | Applicant |
| US6317721(B1) | 2001-11-01 | Hurta et al. | Applicant |
| US6318636(B1) | 2001-11-01 | Reynolds et al. | Applicant |
| US6323566(B1) | 2001-11-01 | Meier | Applicant |
| US6325285(B1) | 2001-12-01 | Baratelli | Applicant |
| US6326934(B1) | 2001-12-01 | Kinzie | Applicant |
| US6331972(B1) | 2001-12-01 | Harris et al. | Applicant |
| US6339384(B1) | 2002-01-01 | Valdes-Rodriguez | Applicant |
| US6342844(B1) | 2002-01-01 | Rozin | Applicant |
| US6364208(B1) | 2002-04-01 | Stanford et al. | Applicant |
| US6367011(B1) | 2002-04-01 | Lee et al. | Applicant |
| US6374245(B1) | 2002-04-01 | Park | Applicant |
| US6377034(B1) | 2002-04-01 | Ivanov | Applicant |
| US6388533(B2) | 2002-05-01 | Swoboda | Applicant |
| US6390375(B2) | 2002-05-01 | Kayanakis | Applicant |
| US6400272(B1) | 2002-06-01 | Holtzman et al. | Applicant |
| US6402028(B1) | 2002-06-01 | Graham, Jr. et al. | Applicant |
| US6411611(B1) | 2002-06-01 | van der Tuijn | Applicant |
| US6415978(B1) | 2002-07-01 | McAllister | Applicant |
| US6422464(B1) | 2002-07-01 | Terranova | Applicant |
| US6424029(B1) | 2002-07-01 | Giesler | Applicant |
| USRE37822(E) | 2002-08-01 | Anthonyson | Applicant |
| US6442532(B1) | 2002-08-01 | Kawan | Applicant |
| US6457996(B1) | 2002-10-01 | Shih | Applicant |
| US6466804(B1) | 2002-10-01 | Pecen et al. | Applicant |
| US6473500(B1) | 2002-10-01 | Risafi et al. | Applicant |
| US6480100(B1) | 2002-11-01 | Frieden et al. | Applicant |
| US6480101(B1) | 2002-11-01 | Kelly et al. | Applicant |
| US6481621(B1) | 2002-11-01 | Herrendoerfer et al. | Applicant |
| US6481632(B2) | 2002-11-01 | Wentker et al. | Applicant |
| US6484937(B1) | 2002-11-01 | Devaux et al. | Applicant |
| US6490443(B1) | 2002-12-01 | Freeny, Jr. | Applicant |
| US6491229(B1) | 2002-12-01 | Berney | Applicant |
| US6494380(B2) | 2002-12-01 | Jarosz | Applicant |
| US6507762(B1) | 2003-01-01 | Amro et al. | Applicant |
| US6510983(B2) | 2003-01-01 | Horowitz et al. | Applicant |
| US6510998(B1) | 2003-01-01 | Stanford et al. | Applicant |
| US6513015(B2) | 2003-01-01 | Ogasawara | Applicant |
| US6529880(B1) | 2003-03-01 | McKeen et al. | Applicant |
| US6535726(B1) | 2003-03-01 | Johnson | Applicant |
| US6546373(B1) | 2003-04-01 | Cerra | Applicant |
| US6547133(B1) | 2003-04-01 | DeVries, Jr. et al. | Applicant |
| US6549912(B1) | 2003-04-01 | Chen | Applicant |
| US6560581(B1) | 2003-05-01 | Fox et al. | Applicant |
| US6577229(B1) | 2003-06-01 | Bonneau et al. | Applicant |
| US6578768(B1) | 2003-06-01 | Binder et al. | Applicant |
| US6581839(B1) | 2003-06-01 | Lasch et al. | Applicant |
| US6588660(B1) | 2003-07-01 | Buescher et al. | Applicant |
| US6589119(B1) | 2003-07-01 | Orus et al. | Applicant |
| US6608995(B1) | 2003-08-01 | Kawasaki et al. | Applicant |
| US6609655(B1) | 2003-08-01 | Harrell | Applicant |
| US6626356(B2) | 2003-09-01 | Davenport et al. | Applicant |
| US6628961(B1) | 2003-09-01 | Ho et al. | Applicant |
| US6636833(B1) | 2003-10-01 | Flitcroft et al. | Applicant |
| US6650887(B2) | 2003-11-01 | McGregor et al. | Applicant |
| US6665405(B1) | 2003-12-01 | Lenstra | Applicant |
| US6674786(B1) | 2004-01-01 | Nakamura et al. | Applicant |
| US6679427(B1) | 2004-01-01 | Kuroiwa | Applicant |
| US6681328(B1) | 2004-01-01 | Harris et al. | Applicant |
| US6684269(B2) | 2004-01-01 | Wagner | Applicant |
| US6685089(B2) | 2004-02-01 | Terranova et al. | Applicant |
| US6686847(B1) | 2004-02-01 | Mittler | Examiner |
| US6687714(B1) | 2004-02-01 | Kogen et al. | Applicant |
| US6690930(B1) | 2004-02-01 | Dupre | Applicant |
| US6693513(B2) | 2004-02-01 | Tuttle | Examiner |
| US6705530(B2) | 2004-03-01 | Kiekhaefer | Applicant |
| US6711262(B1) | 2004-03-01 | Watanen | Applicant |
| US6732936(B1) | 2004-05-01 | Kiekhaefer | Applicant |
| US6742120(B1) | 2004-05-01 | Markakis et al. | Applicant |
| US6760581(B2) | 2004-07-01 | Dutta | Applicant |
| US6789012(B1) | 2004-09-01 | Childs et al. | Applicant |
| US6830193(B2) | 2004-12-01 | Tanaka | Applicant |
| US6924729(B1) | 2005-08-01 | Aschauer et al. | Examiner |
| US7069444(B2) | 2006-06-01 | Lowensohn et al. | Applicant |
| US2001/0013542(A1) | 2001-08-01 | Horowitz et al. | Applicant |
| US2001/0024157(A1) | 2001-09-01 | Hansmann et al. | Applicant |
| US2001/0034565(A1) | 2001-10-01 | Leatherman | Applicant |
| US2001/0039617(A1) | 2001-11-01 | Buhrlen et al. | Applicant |
| US2002/0011519(A1) | 2002-01-01 | Shults | Applicant |
| US2002/0028704(A1) | 2002-03-01 | Bloomfield et al. | Applicant |
| US2002/0035548(A1) | 2002-03-01 | Hogan et al. | Applicant |
| US2002/0052839(A1) | 2002-05-01 | Takatori | Applicant |
| US2002/0062284(A1) | 2002-05-01 | Kawan | Applicant |
| US2002/0074398(A1) | 2002-06-01 | Lancos | Applicant |
| US2002/0077837(A1) | 2002-06-01 | Krueger et al. | Applicant |
| US2002/0077895(A1) | 2002-06-01 | Howell | Applicant |
| US2002/0077992(A1) | 2002-06-01 | Tobin | Applicant |
| US2002/0079367(A1) | 2002-06-01 | Montani | Applicant |
| US2002/0092914(A1) | 2002-07-01 | Pentz et al. | Applicant |
| US2002/0095343(A1) | 2002-07-01 | Barton et al. | Applicant |
| US2002/0095389(A1) | 2002-07-01 | Gaines | Applicant |
| US2002/0095587(A1) | 2002-07-01 | Doyle et al. | Applicant |
| US2002/0097144(A1) | 2002-07-01 | Collins et al. | Applicant |
| US2002/0107007(A1) | 2002-08-01 | Gerson | Applicant |
| US2002/0107742(A1) | 2002-08-01 | Magill | Applicant |
| US2002/0109580(A1) | 2002-08-01 | Shreve et al. | Applicant |
| US2002/0111210(A1) | 2002-08-01 | Luciano, Jr. et al. | Applicant |
| US2002/0113082(A1) | 2002-08-01 | Leatherman et al. | Applicant |
| US2002/0116274(A1) | 2002-08-01 | Hind et al. | Applicant |
| US2002/0120584(A1) | 2002-08-01 | Hogan et al. | Applicant |
| US2002/0126010(A1) | 2002-09-01 | Trimble et al. | Applicant |
| US2002/0131567(A1) | 2002-09-01 | Maginas | Applicant |
| US2002/0138438(A1) | 2002-09-01 | Bardwell | Applicant |
| US2002/0140542(A1) | 2002-10-01 | Prokoski et al. | Applicant |
| US2002/0145043(A1) | 2002-10-01 | Challa et al. | Applicant |
| US2002/0147913(A1) | 2002-10-01 | Lun Yip | Applicant |
| US2002/0148892(A1) | 2002-10-01 | Bardwell | Applicant |
| US2002/0152123(A1) | 2002-10-01 | Glordano et al. | Applicant |
| US2002/0166891(A1) | 2002-11-01 | Stoutenburg et al. | Applicant |
| US2002/0176522(A1) | 2002-11-01 | Fan | Applicant |
| US2002/0178063(A1) | 2002-11-01 | Gravelle et al. | Applicant |
| US2002/0178369(A1) | 2002-11-01 | Black | Applicant |
| US2002/0185543(A1) | 2002-12-01 | Pentz et al. | Applicant |
| US2002/0188501(A1) | 2002-12-01 | Lefkowith | Applicant |
| US2002/0190125(A1) | 2002-12-01 | Stockhammer | Applicant |
| US2002/0194303(A1) | 2002-12-01 | Suila et al. | Applicant |
| US2002/0194503(A1) | 2002-12-01 | Faith et al. | Applicant |
| US2002/0196963(A1) | 2002-12-01 | Bardwell | Applicant |
| US2003/0009382(A1) | 2003-01-01 | D'Arbelott et al. | Applicant |
| US2003/0014307(A1) | 2003-01-01 | Heng | Applicant |
| US2003/0014357(A1) | 2003-01-01 | Chrisekos et al. | Applicant |
| US2003/0014891(A1) | 2003-01-01 | Nelms et al. | Applicant |
| US2003/0018532(A1) | 2003-01-01 | Dudek et al. | Applicant |
| US2003/0025600(A1) | 2003-02-01 | Blanchard | Applicant |
| US2003/0028481(A1) | 2003-02-01 | Flitcroft et al. | Applicant |
| US2003/0046228(A1) | 2003-03-01 | Berney | Applicant |
| US2003/0054836(A1) | 2003-03-01 | Michot | Applicant |
| US2003/0057226(A1) | 2003-03-01 | Long | Applicant |
| US2003/0057278(A1) | 2003-03-01 | Wong | Applicant |
| US2003/0069828(A1) | 2003-04-01 | Blazey et al. | Applicant |
| US2003/0069846(A1) | 2003-04-01 | Marcon | Applicant |
| US2003/0112972(A1) | 2003-06-01 | Hattick et al. | Applicant |
| US2003/0120554(A1) | 2003-06-01 | Hogan et al. | Applicant |
| US2003/0121969(A1) | 2003-07-01 | Wankmueller | Applicant |
| US2003/0132284(A1) | 2003-07-01 | Reynolds et al. | Applicant |
| US2003/0140228(A1) | 2003-07-01 | Binder | Applicant |
| US2003/0163699(A1) | 2003-08-01 | Pailles et al. | Applicant |
| US2003/0167207(A1) | 2003-09-01 | Berardi et al. | Applicant |
| US2003/0177347(A1) | 2003-09-01 | Schneier et al. | Applicant |
| US2003/0183689(A1) | 2003-10-01 | Swift et al. | Applicant |
| US2003/0183699(A1) | 2003-10-01 | Masui | Applicant |
| US2003/0187786(A1) | 2003-10-01 | Swift et al. | Applicant |
| US2003/0187787(A1) | 2003-10-01 | Freund | Applicant |
| US2003/0187790(A1) | 2003-10-01 | Swift et al. | Applicant |
| US2003/0187796(A1) | 2003-10-01 | Swift et al. | Applicant |
| US2003/0195842(A1) | 2003-10-01 | Reece | Applicant |
| US2003/0195843(A1) | 2003-10-01 | Matsuda et al. | Applicant |
| US2003/0200184(A1) | 2003-10-01 | Dominguez et al. | Applicant |
| US2003/0218066(A1) | 2003-11-01 | Fernandes et al. | Applicant |
| US2003/0220876(A1) | 2003-11-01 | Burger et al. | Applicant |
| US2003/0222153(A1) | 2003-12-01 | Pentz et al. | Applicant |
| US2003/0225623(A1) | 2003-12-01 | Wankmueller | Applicant |
| US2003/0225713(A1) | 2003-12-01 | Atkinson et al. | Applicant |
| US2003/0227550(A1) | 2003-12-01 | Manico et al. | Applicant |
| US2003/0233334(A1) | 2003-12-01 | Smith | Applicant |
| US2004/0010462(A1) | 2004-01-01 | Moon et al. | Applicant |
| US2004/0015451(A1) | 2004-01-01 | Sahota et al. | Applicant |
| US2004/0016796(A1) | 2004-01-01 | Hanna et al. | Applicant |
| US2004/0029569(A1) | 2004-02-01 | Khan et al. | Applicant |
| US2004/0039860(A1) | 2004-02-01 | Mills et al. | Applicant |
| US2004/0139021(A1) | 2004-07-01 | Reed et al. | Applicant |
| US2004/0176071(A1) | 2004-09-01 | Gehrmann et al. | Applicant |
| US2004/0177045(A1) | 2004-09-01 | Brown | Applicant |
| US2004/0180657(A1) | 2004-09-01 | Yaqub et al. | Applicant |
| US2005/0033686(A1) | 2005-02-01 | Peart et al. | Applicant |
| US2005/0122209(A1) | 2005-06-01 | Black | Applicant |
| CH689070 | 1988-08-01 | Applicant | |
| EP358525 | 1990-03-01 | Applicant | |
| EP484726(A1) | 1990-10-01 | Applicant | |
| EP933717(A2) | 1999-08-01 | Applicant | |
| EP956818(A1) | 1999-11-01 | Applicant | |
| EP959440(A2) | 1999-11-01 | Applicant | |
| EP984404(A2) | 2000-03-01 | Applicant | |
| EP1039403(A2) | 2000-09-01 | Applicant | |
| EP1104909(A2) | 2001-06-01 | Applicant | |
| EP1113387(A2) | 2001-07-01 | Applicant | |
| EP1199684(A2) | 2002-04-01 | Applicant | |
| EP1251450(A1) | 2002-10-01 | Applicant | |
| GB2347537(A) | 2000-09-01 | Applicant | |
| JP2000-11109(A) | 2000-01-01 | Applicant | |
| JP2000015288(A) | 2000-01-01 | Applicant | |
| JP2000-40181(A) | 2000-02-01 | Applicant | |
| JP2000067312(A) | 2000-03-01 | Applicant | |
| JP2000207641(A) | 2000-07-01 | Applicant | |
| JP2001-5931(A) | 2001-01-01 | Applicant | |
| JP2001283122(A) | 2001-10-01 | Applicant | |
| WO95-32919(A1) | 1995-12-01 | Applicant | |
| WO99/03057(A1) | 1999-01-01 | Applicant | |
| WO99/12136(A1) | 1999-03-01 | Applicant | |
| WO/10144(A1) | 2000-02-01 | Applicant | |
| WO/38088(A2) | 2000-06-01 | Applicant | |
| WO1/04825(A1) | 2001-01-01 | Applicant | |
| WO1/15098(A1) | 2001-03-01 | Applicant | |
| WO1/43095(A2) | 2001-06-01 | Applicant | |
| WO1/72224(A1) | 2001-10-01 | Applicant | |
| WO1/77856(A1) | 2001-10-01 | Applicant | |
| WO1/80473(A2) | 2001-10-01 | Applicant | |
| WO1/86535(A1) | 2001-11-01 | Applicant | |
| WO1/90962(A1) | 2001-11-01 | Applicant | |
| WO1/95243(A2) | 2001-12-01 | Applicant | |
| WO2/01485(A1) | 2002-01-01 | Applicant | |
| WO2/13134(A2) | 2002-02-01 | Applicant | |
| WOPCT/US02/21903 | 2002-07-01 | Applicant | |
| WO2/063545(A2) | 2002-08-01 | Applicant | |
| WO2/065246(A2) | 2002-08-01 | Applicant | |
| WO2/065404(A2) | 2002-08-01 | Applicant | |
| WO2/069221(A1) | 2002-09-01 | Applicant | |
| WO2/073512(A1) | 2002-09-01 | Applicant | |
| WO2/086665(A2) | 2002-10-01 | Applicant | |
| WO2/091281(A2) | 2002-11-01 | Applicant | |
| WO2/101670(A2) | 2002-12-01 | Applicant |
Non-Patent Literature (24)
- European Search Report dated Nov. 16, 2004.Applicant
- Functional Specification, Standard Card IC MF1 IC S50, Philips Semiconductors, Product Specification Rev. 5.1 May 2001.Applicant
- “Bank Extends RFID Payment Pilot: Bank of America will continue to test its Quick Wave RFID payment card for another three months”, RFID Journal, Jan. 23, 2003.Applicant
- “MasterCard to Test RFID Card: Pilot will test whether consumers, merchants and credit card issuers value “contactless” payments”, RFID Journal, Dec. 20, 2002.Applicant
- “Vendors Target Amusement Parks: Protecting children and enabling cashless payments make RFID an appealing option for the entertainment industry”, RFID Journal, Nov. 27, 2002.Applicant
- “Inside's Next-Gen Smart Card: The French company plans to introduce an RFID card that uses a 16-bit microprocessor and new encryption technology”, RFID Journal, Oct. 29, 2002.Applicant
- “Sony, Philips Creating RFID Link: Consumer electronics giants are jointly developing a new RFID standard for payments and for communication between devices”, RFID Journal, Sep. 17, 2002.Applicant
- “Japan Gets Digital Ticket System: A national ticket seller and phone company are teaming up to create an electronic-ticket network”, RFID Journal, Aug. 21, 2002.Applicant
- “Security for Wireless Java: NTRU, a starup that offers security software, has relased a Java version of its NTRU encryption algorithm”, RFID Journal, Jun. 27, 2002.Applicant
- “Making RFID Payments Ubiquitous: Philips and Visa want people to be able to pay for goods and services anywhere by using RFID chips embedded in phones and other devices”, RFID Journal, Jun. 2, 2003.Applicant
- “RFID Smart Cards Gain Ground: The convenience of contactless transactions is driving widespread adoption of contactless smart cards”, RFID Journal, Apr. 9, 2003.Applicant
- “T1 Embraces Prox Card Standard: Texas Instrument's ISO 14443 payment platform promises faster data transfer rates and more security”, RFID Journal, Mar. 6, 2003.Applicant
- “Multiple Frequency Transponders: Volume production of dual-band RFID chips begins”, Frontline Solutions, Jul. 16, 2003.Applicant
- “What's New: Timex Watch Features Speedpass System”, http://www.speedpass.com/news/article.jsp?id=51 (1 page).Applicant
- “Physical Reality: A Second Look”, Ken Sharp, Senior Technical Editor, http://www.idsystems.com/reader/1999—03/phys0399—pt2/phys0399—pt2.htm (6 pages).Applicant
- “Magic Wands' to Speed Mobile Sales”, BobBrewin, Jan. 15, 2001, http://www.computerworld.com/mobiletopics/mobile/story/1,10801,563300.html (4 pages).Applicant
- “Mobile Speedpass Goes Global as Mobil Singapore Rolls Out Asia's First RFID-Based Pay-At-The-Pump System”, Press Release, Apr. 5, 1999, http://www.ti.com/tiris/docs/news—releases/rel12.htm (3 pages).Applicant
- “Speedpass Unleashed”, Jun. 4, 2002 http://www.cardweb.com/cardtrak/news/cf2—20a—97.html (2 pages).Applicant
- Prophecy Central Update #9, Oct. 10, 1997, http://www.bible-prophecy.com/pcu9.htm (5 pages).Applicant
- International Newsletter of the TI RFID Group, Issue 20, 2000 (12 pages).Applicant
- “CES: Microsoft's SPOT Technology has Humble Origins”, by James Niccolai, Jan. 10, 2003, http://archive.inforworld.com/articles/hn/xml/03/01/10/030110hnspot.xml?s=IDGNS (3 pages).Applicant
- “Microsoft: See SPOT Run On Your Wrist”, by Richard Shim, Jun. 5, 2003, http://news.com.com/2100-1041—3-1013442.html?tag=fd—top (1 page).Applicant
- “Networking: Microsoft SPOT”, by Jeremy A. Kaplan, Jul. 1, 2003, http://www.pcmag.com/print—article/0,3048,a=43561,00.asp (2 pages).Applicant
- “Microsoft Launches Smart Personal Object Technology Initiative”, Press Release from COMDEX Fall 2002, Nov. 17, 2002, http://www.Microsoft.com/presspass/features/2002/nov02/11-17SPOT.asp (4 pages).Applicant