Patent Grant
7768379
The present invention relates generally to the use of Radio Frequency Identification (RFID) in contactless environments, for commercial transactions and, more particularly, to a method and system for conveniently storing, retrieving, and updating data related to a fob user's travel information in the context of contactless environments.
Despite advances in information technology and process streamlining with respect to travel arrangements, the modern traveler may be often subjected to unnecessary delays, petty inconveniences, and oppressive paperwork. These travel burdens are most evident in the airline, hotel, and rental car industries, where arranging and paying for services and accommodations can involve significant time delays due to miscommunication, poor record-keeping, and a host of other administrative inefficiencies.
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.
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 contained 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 independent 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 may respond to a RF interrogation signal. Other typical modulation techniques which may be used include, for example, ISO/IEC 14443 and the like.
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.
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.
A need exists for a transaction authorization system which allows Fob transactions, particularly travel-related transactions, to be authorized while eliminating the cost associated with using third-party servers.
The present invention provides a system and methods for an RFID system which securely and conveniently integrates important travel-related applications. In accordance with one aspect of the present invention, an RFID system comprises a RFID fob identification application and various additional applications useful in particular travel contexts; for example, airline, hotel, rental car, and payment-related applications. In accordance with another aspect of the present invention, an RFID system further comprises space and security features within specific applications which provide partnering organizations the ability to construct custom and secure file structures.
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:
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 microprocessors 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.
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 may be noted that the network may be implemented as other types of networks, such as an interactive television network (ITN).
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 Pilots®, 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.
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 may be described with respect to a fob 102, the invention may be not to be so limited. Indeed, system 100 may include any device having a transponder which may be 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.
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.
Although the point of interaction device may be described herein with respect to a merchant point of sale (POS) device, the invention may be not to be so limited. Indeed, a merchant POS device may be 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), an issuer host network, and/or any other access point for processing any transaction request. In this arrangement, information provided by RFID reader 104 may be 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.
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 may be 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 may be incorporated herein by reference.
An account number, as used herein, may include any identifier for an account (e.g., credit, charge debit, checking, savings, reward, loyalty, travel 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, travel 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 card account. However, it should be noted that the invention may be not so limited and other accounts permitting an exchange of goods and services for an account data value may be contemplated to be within the scope of the present invention.
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 may be 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. Track 1 and Track 2 data may be described in more detail below. 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.
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 may be of the 13.56 MHz variety, modulator/demodulator 206 may be ISO/IEC 14443-2 compliant.
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 may be authenticated, and thereby providing to the RFID reader 104 the account number stored on fob 102.
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 DB 2 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 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 may be, in one embodiment, the same. However, data tables having similar, though not identical, data in the key fields may also be merged by using AGREP, for example.
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.
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.
In accordance with another exemplary embodiment, the account number may be stored in magnetic stripe format. For example, where the account number may be in magnetic stripe format, the account number portions are governed by the International Standards Organization ISO/IEC 7811, et al. standard, which are hereby incorporated by reference. The standard requires the magnetic stripe information to be encoded in three “tracks” (i.e., track 1, track 2, and track 3).
Data stored in track 1 may be typically used to verify the user's identity. Track 1 may be reserved for encoding the transaction account identifier, the name of the accountholder, and at least the expiration date of the transaction account or the transaction device. The information encoded in track 1 may be alpha-numeric and may be encoded at about 7 Bits/Character. In an exemplary layout of the data stored in track 1, track 1 may be segmented into several distinct predetermined portions (e.g., “fields”) for encoding the various account identifying information. The following table may be useful for determining the field definitions of the information provided.
Track 2 may be the track most commonly used by the American Banking Association associated banking institutions. Track 2 may be typically reserved for a duplicate version of the transaction account identifier and the expiration date of the transaction account or the transaction device stored in track 1. In addition, track 2 may include an encrypted Personal Identification Code, and other discretionary data. However, the data in track 2 may be encoded at a lower Bit per Character density than the data encoded in track 1. The data in track 2 may be numeric only and may be encoded at about 5 Bits/Character. The lower density ratio in track 2 may be designed to ensure compatibility with older technology readers and to provide redundancy when reading with newer technology readers.
Track 3 may be of similar description as Track 2. With the International Standards Organization adoption of standard ISO/IEC 4909, track 3 of the magnetic stripe format was no longer used by the banking industry. However, other transaction devices including a magnetic stripe, such as drivers licenses, use track 3, which may include both numeric only and alpha numeric characters. Track 3 may be unique in that track 3 was intended to have data read and WRITTEN on it. Cardholders would have account information UPDATED right on the magnetic stripe. The present invention anticipates that a fob user's travel-related information profile and/or account information may be updated using track 3. Unfortunately, track 3 may be almost an orphaned standard, since most readers currently in operation are not configured to write data onto a magnetic stripe. The original design of track 3 was to control off-line ATM transactions by recording transaction data for later reference by the banking institution. But since ATMs are now on-line, the usage of track 3 has been drastically reduced.
The most common technique used to encode data in magnetic stripe format may be known as Aiken Biphase, or “two-frequency coherent-phase encoding.” The American National Standards Institute (ANSI) and the International Standards Organization (ISO) have chosen two standards to guide the encoding process. The ISO encoding protocol specifies that each of tracks 1, 2 and 3 must begin and end with a length of all Zero bits, called CLOCKING BITS. These are used to synch the self-clocking feature of bi-phase decoding. In addition, most transaction devices which use magnetic stripe encoding protocol use either the ANSI/ISO ALPHA Data format or the ANSI/ISO BCD Data format. For example, track 1 may be typically encoded in ANSI/ISO ALPHA Data format which may be a 7 bit, 6 data bits+1 parity bit (odd) format, where the data may be read least significant bit first. The ANSI/ISO ALPHA format character set contains 64 characters, 43 alphanumeric, 3 framing/field characters and 18 control/special characters. On the other hand, tracks 2 and 3 are typically encoded in ANSI/ISO BCD Data format, which may be a 5 bit, 4 data bits+1 parity bit(odd) format. The character set for the ANSI/ISO BCD Data format character set contains 16 characters, 10 alphanumeric, 3 framing/field characters and 3 control/special characters.
Ordinarily, a proxy account number (e.g., a portion of the transaction account number) includes essential identifying information, such as, for example, any information that may be common to the account provider. The common information (also called “common character,” herein) may include the account provider routing number, or common source indicator such as the character spaces reserved to indicate the identification of the issuing bank. Thus, where the proxy transaction account identifier corresponds to an American Express account, the proxy transaction account identifier may include the common character number 3, encoded the field location where such common character may be ordinarily encoded in traditional magnetic stripe format.
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.
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 may be 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.
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.
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 may be provided by USB port 132 (or serial port) only and the fob transponder 114 may be disabled. In addition, the term “inclusively” may mean that the fob 102 may be 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.
In another exemplary embodiment, when the switch 230 may be 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.
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 may be 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.
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 may be 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 may be powered. In yet another exemplary embodiment, switch 230 may be battery powered though no biometric circuitry may be present in the fob 102.
In yet another embodiment, the switch 230 may be a logic switch. Where switch 230 may be 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.
RF module 302 and antenna 106 may be suitably configured to facilitate communication with fob 102. Where fob 102 may be 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 sing 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 may be operating at 134 kHz frequency, only operation with the 134 kHz module on the fob 102 may be possible. When the reader 104 may be 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.
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 may be 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 may be initiated (e.g., fob may be being interrogated), the fob may be valid (e.g., fob may be authenticated), transaction may be being processed, (e.g., fob account number may be being read by RFID reader) and/or the transaction may be 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 may be being interrogated, the transaction status, or the like.
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
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
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 may be 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.
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 may be 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 may be provided to the fob 102 and which may be 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 may be 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).
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 may be 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.
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.
Once the authentication code may be decrypted, the decrypted authentication code may be 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 may be not readable (e.g., recognizable) by the authentication circuit 308, the fob 102 may be deemed to be unauthorized (e.g., unverified) (step 416) and the operation of system 100 may be terminated (step 418). Contrarily, if the decrypted authorization code may be recognizable (e.g., verified) by the fob 102, the decrypted authorization code may be deemed to be authenticated (step 412), and the transaction may be allowed to proceed (step 414). In one particular embodiment, the proceeding transaction may mean that the fob 102 may authenticate the RFID reader 104, although, it should be apparent that the RFID reader 104 may authenticate the fob 102 prior to the fob 102 authenticating the RFID reader 104.
It should be noted that in an exemplary verification process, the authorization circuit 308 may determine whether the unlocked authorization code may be identical to the authorization code provided in step 402. If the codes are not identical then the fob 102 may be not authorized to access system 100. Although, the verification process may be described with respect to identicality, identicality may be 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.
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
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 may be received from fob 102, protocol/sequence controller may determine if the response may be a response to the RFID reader 104 provided authentication code, or if the response may be 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 may be 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 may be recognized, the protocol/sequence controller 314 may determine that the fob 102 may be authorized to access the system 100. If the signal may be not recognized, then the fob may be considered not authorized. In which case, the protocol/sequence controller 314 may command the RFID controller to interrogate for authorized fobs (step 504).
Once the protocol/sequence controller determines that the fob 102 may be 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 may be 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 may be provided (step 516). Contrarily, where an additional fob 102 signal may be provided, the protocol/sequence controller 314 may determine if the fob 102 may be requesting access to the merchant point of sale terminal 110 (e.g., POS device) or if the fob 102 may be attempting to interrogate the RFID reader 104 for return (e.g., mutual) authorization (step 518). Where the fob 102 may be 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.
On the other hand, if the protocol/sequence controller determines that the fob 102 signal may be 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.
Although an exemplary decision process of protocol/sequence controller 314 may be 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 may be so connected.
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
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
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, unique identifying information, and travel-related 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.
Fob 102 may be personalized by direct connection to the personalization system 116 via RF ISO/IEC 14443 interface face 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 may be 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 may be not presented to the RFID reader 104 for personalization, the personalization process may be aborted (step 610).
If the fob 102 may be 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 may be 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).
The encrypted fob 102 account number may be populated into fob 102 in the same manner as may be described with respect to the fob 102 unique identifier. That is, personalization system 116 may pre-encrypt the account data (step 620) 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.
Once the personalization file may be populated into the fob 102, the populated information may be 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).
It should be noted that in the event the personalization system 116 process may be compromised or interrupted (step 628), the personalization system 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 may be prepared to begin initialization on a second device to be personalized (step 632).
If the personalization system 116 determines that the personalization process may be 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 may be unsuccessful (step 712), the personalization system may abort the personalization process (step 714).
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 may be 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.
Personalization system 116 may then determine if the personalization keys (e.g., security keys, decryption keys, RFID identifier, travel-related information) 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).
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 may be necessary the personalization system 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 may download the information onto RFID reader 104 (step 726). The information (e.g., fob security keys, identifiers, and travel-related information) 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 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).
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 method described in
The fob 102 and the RFID reader 104 may then engage in mutual authentication (step 810). Where the mutual authentication may be 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 may be successful (step 812), 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).
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) and the transaction completed (step 834).
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 may be 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 may be 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.
Where a verification PIN may be 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 and/or the fob user's travel-related information. 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.
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
In another exemplary embodiment of the present invention, system 100 may be configured with one or more biometric scanners, processors and/or systems. A biometric system may include one or more technologies, or any portion thereof, such as, for example, recognition of a biometric. As used herein, a biometric may include a user's voice, fingerprint, facial, ear, signature, vascular patterns, DNA sampling, hand geometry, sound, olfactory, keystroke/typing, iris, retinal or any other biometric relating to recognition based upon any body part, function, system, attribute and/or other characteristic, or any portion thereof. While the example discussed herein may include a particular biometric system or sample, the invention contemplates any of the biometrics discussed herein in any of the embodiments.
The biometric system may be configured as a security system and may include a registration procedure in which a user of transaction instrument (e.g., fob 102) proffers a sample of his fingerprints, DNA, retinal scan, voice, and/or other biometric sample to an authorized sample receiver (ASR). An ASR may include a local database, a remote database, a portable storage device, a host system, an issuer system, a merchant system, a fob issuer system, an employer, a financial institution, a non-financial institution, a loyalty point provider, a company, the military, the government, a school, a travel entity, a transportation authority, a security company, and/or any other system or entity that is authorized to receive and store biometric samples and associate the samples with specific biometric databases and/or transaction instruments (e.g., fobs 102). As used herein, a user of a fob, fob user, or any similar phrase may include the person or device holding or in possession of the fob, or it may include any person or device that accompanies or authorizes the fob owner to use the fob. By proffering one or more biometric samples, a biometric may be scanned by at least one of a retinal scan, iris scan, fingerprint scan, hand print scan, hand geometry scan, voice print scan, vascular scan, facial and/or ear scan, signature scan, keystroke scan, olfactory scan, auditory emissions scan, DNA scan, and/or any other type of scan to obtain a biometric sample.
Upon scanning the sample, the system may submit the scanned sample to the ASR in portions during the scan, upon completing the scan or in batch mode after a certain time period. The scanned sample may include a hardcopy (e.g., photograph), digital representation, an analog version or any other configuration for transmitting the sample. The ASR receives the sample and the ASR may also receive copies of a fob user's biometric data along with the sample or at a different time (or within a different data packet) from receiving the sample.
The ASR and/or fob user 102 may store the sample in digital and/or any storage medium known in the art and correlate and/or register the sample with fob user information. By storing the sample in digital format, the ASR may digitize any information contained in one of the biometric scans described herein. By storing the sample in any storage medium, the ASR may print and/or store any biometric sample. Hardcopy storage may be desirable for back-up and archival purposes. As used herein, registered samples may include samples that have been proffered, stored and associated with user information.
The biometric sample may also be associated with user information. The sample may be associated with user information at any step in the process such as, for example, prior to submission, during submission and/or after submission. In one embodiment, the user may input a PIN number or zip code into the POS terminal, then scan the biometric to create the biometric sample. The local POS system may associate the biometric sample data with the PIN and zip code, then transmit the entire packet of information to the ASR. In another embodiment, the POS may facilitate transmitting the sample to an ASR, and during the transmission, the sample may be transmitted through a third system which adds personal information to the sample.
The information associated with the biometric sample may include any information such as, for example, fob user information, fob 102 information, fob 102 identifier information, fob 102 vender information, fob 102 operability information, and/or fob 102 manufacturing information. Fob 102 information is not limited to transponder information and may include information related to any transaction instrument such as smart cards, credit cards, debit cards, merchant-specific cards, loyalty point cards, cash accounts and any other transaction instruments and/or accounts. The fob user information may also contain information about the user including personal information—such as name, address, and contact details; financial information—such as one or more financial accounts associated with the fob user; loyalty point information—such as one or more loyalty point accounts (e.g., airline miles, charge card loyalty points, frequent diner points) associated with the fob user; and/or non-financial information—such as employee information, employer information, medical information, family information, and/or other information that may be used in accordance with a fob user.
For example, fob user may have previously associated a credit card account, a debit card account, and a frequent flier account with his biometric sample which is stored at an ASR. Later, when fob user desires to purchase groceries, fob user may submit his biometric sample while using fob 102 for the purchase at a POS. The POS may facilitate sending the biometric sample to the ASR such that the ASR authorizes the biometric sample and checks a look-up table in the ASR database to determine if any information is associated with the sample. If information (e.g., financial accounts) is associated with the sample, the ASR may transmit the information to the POS terminal. The POS terminal may then present fob user with a list of the three accounts associated with the biometric sample. Fob user and/or a merchant may then chose one of the accounts in order to continue and finalize the transaction.
The ASR and/or fob user may associate a specific fob 102 identifier with the biometric sample by any method known in the art for associating an identifier (e.g., through the use of software, hardware and/or manual entry.) The ASR may additionally verify the fob user and/or fob 102 by using one or more forms of the user's secondary identification. For example, the ASR may verify the fob user by matching the fob information to information retrieved from scanning information from a fob user's driver's license. The ASR may verify fob 102 by contacting the vendor of fob 102 to confirm that fob 102 was issued to a specific fob user. In another embodiment, the ASR may activate fob 102 during the registration procedure to confirm that the fob 102 transponder identifier and other information is properly associated with the fob user and the fob user's specific biometric samples. The ASR may additionally employ one or more verification methods to confirm that the biometric sample belongs to the user, such as, for example, the ASR may request from the user demographic information, further biometric samples and/or any other information. As used herein, “confirm”, “confirmation” or any similar term includes verifying or substantially verifying the accuracy, existence, non-existence, corroboration, and/or the like of the information, component, or any portion thereof. The ASR may additionally employ one or more additional processing methods in order to facilitate association of a biometric sample. As used herein, the term processing may include scanning, detecting, associating, digitizing, printing, comparing, storing, encrypting, decrypting, and/or verifying a biometric and/or a biometric sample, or any portion thereof.
Upon association, authentication and/or verification of the biometric sample and fob 102, the system may store the sample and fob 102 identifier in one or more databases on and/or in communication with system 100 via a network, server, computer, or any other means of communicating as described herein. The database(s) may be any type of database described herein. For example, a biometric sample stored on fob 102 may be stored in database 212. The database(s) may be located at or operated by any of the entities discussed herein such as, for example, the ASR and/or by a third party biometric database operator.
The system may further protect the samples by providing additional security with the sample. The security may include, for example, encryption, decryption, security keys, digital certificates, firewalls and/or any other security methods known in the art and discussed herein. One or more security vendors may utilize the security methods to store and/or access the biometric samples. The present invention anticipates that storage of the biometric samples may be such that a sample is first encrypted and/or stored under a security procedure, such that the sample may only be accessed by a vendor with the proper level of access or security which corresponds to or provides access to the stored sample. The samples may be accessible by certain vendors such as, for example, fob 102 transaction account provider system, an issuer system, a merchant system, a fob issuer system, an employer, a financial institution, a non-financial institution, a loyalty-point provider, a company, the military, the government, a school, a travel entity, a transportation authority, and/or a security company.
The fob of the invention may include a particular security system wherein the security system incorporates a particular biometric system. As shown in
In one exemplary application of fob 102 incorporating biometric security system 902, the user may place his finger on the biometric sensor to initiate the mutual authentication process between fob 102 and RFID reader 104, and/or to provide verification of the user's identity. Fob 102 may digitize the fingerprint and compare it against a digitized fingerprint stored in a database (e.g., security database 212) included on fob 102. The fingerprint information may additionally be compared with information from one or more third-party databases communicating with fob 102 through any communication software and/or hardware, including for example, RFID reader 104, a USB connection, a wireless connection, a computer, a network and/or any other means for communicating. This transfer of information may include use of encryption, decryption, security keys, digital certificates and/or other security devices to confirm the security of the sample. Fob 102 may additionally communicate with third-party databases to facilitate a comparison between fob 102 identifier and other fob identifiers stored with the biometric samples. As used herein, compare, comparison and similar terms may include determining similarities, differences, existence of elements, non-existence of elements and/or the like.
Protocol/sequence controller 208 may facilitate the local comparison to authenticate the biometric and authentication circuit 210 may validate the information. Any of the embodiments may alternatively or additionally include remote comparisons performed or controlled by one or more third-party security vendors. One or more comparison techniques and/or technologies may be used for comparisons. For example, for fingerprint comparisons, protocol/sequence controller 208 may utilize an existing database to compare fingerprint minutia such as, for example, ridge endings, bifurcation, lakes or enclosures, short ridges, dots, spurs and crossovers, pore size and location, Henry System categories such as loops, whorls, and arches, and/or any other method known in the art for fingerprint comparisons.
Fob 102 may additionally be configured with secondary security procedures to confirm that fake biometric samples are not being used. For example, to detect the use of fake fingers, fob 102 may be further configured to measure blood flow, to check for correctly aligned ridges at the edges of the fingers, and/or any other secondary procedure to reduce biometric security fraud. Other security procedures for ensuring the authenticity of biometric samples may include monitoring pupil dilation for retinal and/or iris scans, pressure sensors, blinking sensors, human motion sensors, body heat sensors and/or any other procedures known in the art for authenticating the authenticity of biometric samples.
After verifying the biometric information, fob 102 and RFID reader 104 may begin mutual authentication, and the transaction may proceed accordingly. However, the invention contemplates that the verification of biometric information may occur at any point in the transaction such as, for example, after the mutual authentication. At any point in the transaction, the system may additionally request fob user to enter a PIN and/or other identifier associated with the transaction account and/or biometric sample to provide further verification of fob user's identification. As part of the transaction, fob user payer may be requested to select from one of the financial accounts, loyalty accounts, credit accounts, debit account, and/or other accounts associated with the biometric sample. The user may be presented with a list of account options on a display associated with RFID reader 104, fob 102, a third-party security device and/or any other financial or transaction device association with a transaction. In another embodiment, a payee may select one of the accounts. For example, a department store payee may manually and/or automatically select a department store issued account, if available, for a transaction.
Having thus described an exemplary fob 102 and databases 214, 310, an overview of a fob file structure contained on a database in accordance with the present invention will now be described. Referring now to
Fob user verification data 1004 houses, in one embodiment, data useful in verifying fob user identity during a transaction. In a preferred embodiment, fob user verification data 1004 comprises a fob user verification number (i.e., PIN number).
Fob user ID application 1006 suitably comprises various files related to personal information of the fob user (e.g., name, addresses, payment accounts, driver's license, personal preferences and the like). Fob user ID application 1006 may also comprise various files relating to transponder 114, including a transponder identifier. The phrases “fob user identification” and “transponder user identification” may be used interchangeably. Fob user ID application 1006 may be described in greater detail below in conjunction with
Payment system application 1008 suitably comprises information useful in effecting commercial transactions, e.g., account number and expiration date information traditionally stored on a magnetic-stripe credit card. Alternatively, payment system application 1008 comprises a full EMV-compliant application suitable for a wide range of financial transactions. Payment system application 1008 may be described further below in conjunction with
Airline application 1010 suitably comprises data helpful in streamlining commercial airline travel; for example, relevant personal preferences, electronic tickets, and frequent flier information. Airline application 1010 may be discussed in greater detail below in conjunction with
Hotel application 1012 suitably comprises information useful for securing and paying for hotel reservations, including an array of information and preferences associated with a list of preferred hotels as well space for electronic keys. Hotel application 1012 may be discussed in greater detail below in conjunction with
Rental car application 1014 suitably comprises data useful in expediting the process of car rental and return, including, for example, car preference and frequent rental information. Rental car application 1014 may be described in further detail below in conjunction with
In each of the above mentioned applications, sophisticated access and encryption schemes are, in one embodiment, utilized in order to allow multiple parties to make use of certain file structures while preventing unauthorized entry into others. More specifically, partnering organizations (e.g., hotel chains, airlines, and rental car agencies) may create their own tailor-made file structures (i.e., “partner file structures”) within fob 102. Details of the various security measures employed are described in further detail below in conjunction with Table 39.
Referring now to
Partnering organizations 1706(a), 1706(b), and so on, comprise the various hotel chains, rental-car agencies, airlines, and the like, who have access to appropriate data regions within fob 102. Each partnering organization 1706 suitably comprises a database 1714 and appropriate hardware and software components necessary for completing a transaction over network 136, 112. Network 136, 112 may comprise one or more communication modes (e.g., the public switched telephone network (PSTN), the Internet, digital and analog wireless networks, and the like).
Each POS device 110 suitably comprises an appropriate RFID reader for interfacing with fob 102 as well as hardware and software suitable for interfacing with a fob user and performing a transaction over network 136, 112. POS devices 110 are, in one embodiment, located in areas providing convenient access for traveling fob user's or fob user's preparing travel arrangements. Such POS devices 110 may be located, for example, in airline ticketing and gate areas, rental car facilities, hotel lobbies, travel agencies, and stand-alone kiosks in malls. In addition, businesses might see fit to host POS device 110 to streamline their employees” business travel. Furthermore, an individual fob user might configure his or her personal computer to act as a POS using appropriate software and peripheral hardware.
In a preferred embodiment of the present invention, data files and directories are stored in a “tree” structure as illustrated in
The MF and each of the DFs and EFs are assigned a unique two-byte file identifier (FID). By convention, the MF may be traditionally assigned an FID of “3F00” hex. Selection of an EF or DF by the operating system may then be performed by tracing its entire path starting at the MF. Thus, if the MF contains a DF with a FID “A100”, and this DF in turn contains an EF with a FID “A101”, then this EF could be referenced absolutely by successive selection of FIDs 3F00, A100, and A101. It will be appreciated that the FID may be essentially a file name used by the operating system to select directories and files; it may be not intended to indicate a physical address within database 212.
Each file, in one embodiment, has an associated file header containing various indicia of the particular EF, DF, or MF. More particularly, the file header associated with a particular file, in one embodiment, includes the file identifier (FID), file size, access conditions, and file structure. In this regard, fob 102 suitably employs one of four file structures: transparent, linear fixed, linear variable, or cyclic. For the sake of completeness, the nature of these file structures will be briefly reviewed.
A transparent file structure consists of a string of bytes accessed by specifying an offset and byte count. For example, with reference to Table 1 below, given a n-byte string of data, bytes 7 through 10 would be accessed using an offset of six and a length of four.
A linear fixed file structure comprises a plurality of records of equal length (e.g., a list of phone numbers), wherein access to an individual record may be achieved through reference to a record number. In addition, it may be possible to refer to the “next” or “previous” record relative to the “current” record (i.e., the most recently accessed record). In contrast, a linear variable file structure comprises records of arbitrary but known length, and may be therefore typically more compact than linear fixed data structures.
A cyclic file structure may be a type of linear fixed file wherein a pointer may be used to point to the last data set written to. After the last data record may be written to, the pointer returns to the first record. That is, a cyclic file comprises a series of records arranged in a “ring”. A data structure particularly important with regard to storing records as well as secure messaging in fob applications may be the BER tag-length-value or “TLV” structure in accordance with ISO/IEC 8825, hereby incorporated by reference. In a TLV object, information regarding the type and length of the information may be included along with the actual data. Thus, a TLV object comprises a tag which identifies the type of data (as called out by the appropriate specification), a length field which indicates the length in bytes of the data to follow, and a value field, which comprises the primary data. For example, the TLV object illustrated in Table 2 below encodes the text “phoenix”, which has a length of 7 bytes, and corresponds to a the “city” tag of “8C” hex (a hypothetical tag designation).
It will be appreciated that the meaning of the various tag values must be known to the system a priori. That is, in order for the tag field to be useful, the fob and any external systems communicating with the fob must conform to the same tag specification. In this regard, ISO/IEC 7816-6 defines a series of tags useful in the context of the present invention, as does the IBM MFC 3.2 specification. ISO/IEC 8825 sets forth the basic encoding rules for a TLV system and defines a “template” data object which can be used as a container for multiple TLV objects. That is, it may be often advantageous to encapsulate primitive TLV objects within a larger template which may be itself a TLV object.
Referring now to
In the detailed description to follow, various acronyms and abbreviations will be used to refer to particular data types, formats, and the like. A key to these acronyms and abbreviations may be presented in Table 3 below.
In the discussion that follows, the various features of a preferred data structure are in some cases described using particular file structure types (i.e., transparent, fixed, etc.). Those skilled in the art will realize, however, that any of the common fob file structure types are typically suitable for implementing any particular data structure. For example, when a file structure may be described as including “a plurality of records,” it will be understood that such a structure may be designed, for example, using a list of records assembled in a linear fixed file wherein each record may be itself a transparent file (and offset values correspond to the various fields). Alternatively, such a structure may be designed using TLV strings assembled in a linear fixed file or within a larger template TLV. This may be the case notwithstanding the fact that particular tag values which are for the most part arbitrary are not explicitly listed in the tables that follow.
Referring now to
More particularly, fob user ID application 1006, in one embodiment, comprises directory EF 1132, user_ID DF 1102 and miscellaneous DF 1130. User_ID DF 1102, in one embodiment, comprises ID EF 1104, home EF 1106, business EF 1108, preferences EF 1114, passport EF 1116, authentication EF 1120, biometric EF 1122, and driver EF 1118. Miscellaneous EF 1130, in one embodiment, comprises Payment account EF 1110, sequence EF 1112, issuance EF 1111, preferred programs EF 1128, and fob identifier EF 1126. These files and their respective functions are discussed in detail below.
Directory EF 1132 provides a list of application identifiers and labels for the various high-level DF's existing under fob user ID application 1006. That is, this file serves the function of a high-level directory listing which specifies the location (i.e., FID) and application label for each DF in this case, user_ID DF 1102 and miscellaneous DF 1130. In a particular embodiment, directory EF 1132 may be structured in accordance with EMV 3.0 as shown in Table 4 below. In one embodiment, each major application (e.g., hotel, airline, etc.) has an associated directory file with a substantially same file structure.
ID EF 1104 in one embodiment, includes personal information related to the fob user, e.g., name, date of birth, emergency contact, general preferences, and the like. In a particular embodiment, member EF 1104 comprises the fields set forth in Table 5 below. Italicized field names indicate a subcategory within a particular field.
In the above table, and the tables to follow, both internal and external data formats are listed. As the conservation of database space may be of paramount importance, the “internal” format of data (i.e., within database 212) may be different from the “external” format of the data (i.e., as read by the RFID reader at POS device 110). Thus, for example, a date field might consist of a four-byte BCD record within the fob, but upon reading and processing by the terminal, this data might be converted to an eight-byte decimal value for more convenient processing.
Home EF 1106, in one embodiment, includes data related to one or more of the fob user's home addresses. In a particular embodiment, home EF 1106 comprising the fields set forth in Table 6 below. The personal travel charge account pointer may be, in one embodiment, used to designate a preferred payment account, and consists of a number corresponding to one of the payment account records within Payment account EF 1110 (detailed below).
Business EF 1108, in one embodiment, includes various data related to the fob user's business (i.e., addresses, phone numbers, and the like). In a particular embodiment, business EF 1108 comprising the fields set forth in Table 7 below. In this regard, the credit card pointer field may be, in one embodiment, used to point to a payment account record within Payment account EF 1110 (detailed below). The cost center, dept., division, and employee ID fields are employer-specific, and may or may not apply in a given case.
Preferences EF 1114, in one embodiment, comprises data related to the fob user's default personal preferences. In a particular embodiment, preferences EF 1114 includes a field comprising an array of preferences as set forth in Table 8 below. Preference values are, in one embodiment, chosen from a list of preference tags as set forth in Table 39.
Passport EF 1116 may be, in one embodiment, used to store fob user passport information. In a particular embodiment, passport EF 1116 comprises the fields set forth in Table 9 below.
Driver EF 1116, in one embodiment, comprises fob user driver license data. In a particular embodiment, driver EF 1118 comprising the fields set forth in Table 10 below.
Biometric EF 1122 may be used to store biometric data (e.g., encoded) such as fingerprint data, retina scan data, or any other sufficiently unique indicia the fob user's physical or behavioral characteristics. In a particular embodiment, biometric EF 1122 comprises a single data string as set forth in Table 11 below.
Authentication EF 1120, in one embodiment, comprises information for static authentication of the fob user ID 1006 application. This data may be unique for each fob, and may be sufficiently complex such that counterfeit values cannot feasibly be created. This prevents creation of “new” counterfeit fobs (i.e., fobs with new authentication data), but does not prevent creation of multiple copies of the current fob.
In a particular embodiment, authentication EF 1120 includes public key certificate fields as shown in Table 12 below, wherein the external format may be identical to the internal format. In one embodiment, the issuer RSA key may be 640 bits long, and the CA key may be 768 bits long.
Turning now to files under miscellaneous DF 1130, preferred programs EF 1128, in one embodiment, comprises data related to the fob user's preferences as to airline companies, hotels, and rental car agencies. Specifically, this EF, in a particular embodiment, comprises a plurality of records (e.g., three) indicating preferred companies for each type of travel partner as shown in Table 13. The actual data values conform to an arbitrary convention; that is, each airline, hotel, and rental car agency may be assigned an arbitrary three-byte code.
Payment account EF 1110 may be, in one embodiment, used to catalog information related to the fob user's various payment accounts, i.e., debit accounts, credit card accounts, and the like. In a particular embodiment, Payment account EF comprises account numbers and expiration dates for two accounts as shown in Table 14. The “ISO” and “non-ISO” designations refer to ISO-7813, which specifies a particular payment account number format. Thus, in a preferred embodiment, either an ISO or non-ISO account number scheme may be used. Moreover, it will be appreciated that this data set may be sufficient only for “fob not present” transactions, for example, transactions taking place remotely where only the account number and expiration date are required to effect a transaction. Data stored within payment system application 1008 (described below) must be used to effect a “fob present” transaction.
Sequence EF 1112, in one embodiment, includes information used to provide synchronization of the host and fob databases. In a particular embodiment, sequence EF 1112 comprises a plurality of records comprising the field set forth in Table 15 below. This number may be analogous to a “version” number for the data stored in the application.
Fob identifier EF 1126 may be used to record a unique identifier identifying the fob, and may also be used for key derivation (as described in further detail below). In one embodiment, fob identifier EF 1126 comprises a eight-byte string as set forth in Table 16 below.
Issuance EF 1111 may be used to record various details related to the manner in which the application (i.e., fob user ID DF 1006) was created. This file includes information related to the identity of the organization that created the application, as well as information related to the application itself. In a particular embodiment, issuance EF 1111 comprises fields as set forth in Table 17 below.
The personalizer code field shown in Table 17 refers to the organization that actually “personalizes” the file. That is, before a fob may be issued to the fob user, the database structure must be created within database 212 (
Referring now to
Directory EF 1310, in one embodiment, includes a list of application identifiers and labels as described above in the context of fob user ID application 1006.
Issuer DF 1302 comprises pay1 DF 1304, which includes data that would traditionally be stored within tracks on a magnetic stripe card (i.e., debit cards, charge cards, and the like). In a preferred exemplary embodiment, pay1 DF 1304 comprises a plurality of records having commonly known magnetic-stripe fields as specified in Table 18 below.
Referring now to
Directory EF 1430, in one embodiment, includes a list of application identifiers and labels as described above in the context of fob user ID application 406.
Common DF 1402 generally includes data accessible to all participating airlines, while issuer DF 1404 generally includes data which can only be read or written to by the fob issuer. Airline application 1010, in one embodiment, further comprises at least one (may be three) additional DF 1403 for use by airline partnering organizations. That is, one airline partner may have access to and specify the structure of data stored within DF 1403(a) (as well as common EF 1402), while another airline might have similar access to DF 1403(b). These partner DFs, in one embodiment, conform to the relevant portions of the IATA specification.
Common DF 1402 suitably comprises common data which would be of use to any of the various partnering airlines, i.e., passenger EF 1406, frequent flier EF 1408, IET EF 1410, boarding EF 1412, and biometric EF 1414. Issuer DF 1404, in contrast, comprises information readable by all, but updateable only by the card issuer, i.e., preferences EF 1416, PIN EF 1418, and issuance EF 1420.
Referring now to information stored within common EF 1402, passenger EF 1406, in one embodiment, comprises various records related to the passenger as specified in Table 19 below.
In a particular embodiment, frequent flyer EF 1408 comprises a plurality of frequent flier numbers (e.g., ten numbers) having the structure specified in Table 20 below.
IET EF 1410, in one embodiment, comprises a plurality of electronic ticket records as set forth in Table 21 below. The format of these electronic tickets, in one embodiment, conforms to the IATA standard.
In a particular embodiment, boarding EF 1412 comprises boarding data to be used during check in as specified in Table 22. The format of this data, in one embodiment, conforms to the IATA specification.
Biometric EF 1414 may be suitably used to store biometric data associated with the fob user, e.g., retina scan data, fingerprint data, or any other sufficiently unique indicia of the fob user's physical or behavioral characteristics. In a particular embodiment, biometric EF 1414 comprises data as specified in Table 23 below.
Issuance EF 1420 may be suitably used to hold data related to the issuance of the various applications. In a particular embodiment, issuance EF 1420 comprises a data structure as specified in Table 24 below.
PIN EF 1418 may be suitably used to store PIN values corresponding to each of the participating airline partners. In a particular embodiment, PIN EF 1418 comprises a plurality of records having the structure specified in Table 25 below, wherein each record may be related to the corresponding entry in frequent flyer EF 1408 (i.e., record one in EF 1418 corresponds to record one in EF 1408, and so on.)
Preferences EF 1416, in a particular embodiment, comprises a preferences array as shown in Table 26 below. The preference values stored in this file correspond to those discussed below in conjunction with Table 38.
Referring now to
In a particular embodiment, preferences EF 1505 comprises a set of preferences arrays file structure as shown in Table 27 below. A preferred list of preference codes for use in each of these arrays may be described below in conjunction with Table 38.
Rental_car_id 1507 may be used to store frequent rental information, upgrade information, insurance information, and the like. In a particular embodiment, rental_car_id 1507 comprises a file structure as shown in Table 28 below.
Reservation EF 1509 may be used to store confirmation numbers corresponding to one or more rental car reservations. In a particular embodiment, reservation EF 1509 comprises a plurality of records (e.g., two) having a file structure as shown in Table 29 below.
Expenses EF 1511 may be used to record expenses incurred by the fob user during car rental (e.g., the total rental charge). In a particular embodiment, expenses EF 1511 comprises a plurality of records (e.g., five) having a file structure as shown in Table 30 below.
Referring now to
Hotel chain EFs 1602(a), 1602(b), and so on, comprise preferences EF 1604 and stayer ID EF 1606 associated with individual hotel chains. In contrast, property EFs 1603(a), 1603(b), and so on, comprise a similar file structure associated with individual hotel properties (i.e., independent of whether the particular hotel may be a member of a nationwide chain).
In a particular embodiment, reservation EF 1618 comprises a plurality of records having the structure shown in Table 31 below. In general, this EF may be used to store confirmation numbers transmitted to fob 102 when the fob user makes a reservation at a given hotel (designated in the property code field). The date field stores the date on which the confirmation number was dispensed.
Preferences EF 1612, in one embodiment, comprises three sets of array preferences. The particular codes used in these arrays are discussed below in conjunction with Table 38.
Expenses EF 1616, in one embodiment, comprises a list of recent hotel expenses, for example, room costs, dinner expenses, and the like. In a particular embodiment, expenses EF 1616 comprises a plurality of records (for example, fifteen) arranged in a cyclic file structure and comprising the fields shown in Table 33 below. Thus, the fob user may be able to examine and print a list of recently incurred expenses by type (a code fixed by convention), date, amount, and property code.
Key-of-the-room EF 1610, in one embodiment, comprises electronic key values that can be used in conjunction with RFID readers to provide access to particular hotel rooms. In a particular embodiment, key-of-the-room EF 1610 comprises a plurality of alphanumeric key values as shown in Table 34 below.
Stayer ID EF 1606, in one embodiment, comprises frequent stayer data for a particular hotel chain. In a particular embodiment, Stayer ID EF 1606 comprises frequent stayer information as shown in Table 35 below.
Preferences EF 1604, in one embodiment, comprises three sets of array preferences as shown in Table 36. The particular codes used in these arrays are discussed below in conjunction with Table 38.
Property DFs 1603(a), 1603(b), etc., are used in cases where the partnering hotel may be not part of a major chain, or when the hotel chooses to employ its own data set independent of its affiliation. In one embodiment, these property DFs are identical in structure to hotel chain DFs 1602, except that much of the frequent stayer ID information may be removed. More specifically, a typical property DF 1603 comprises a preferences EF 1638 identical to preferences 1604 described above, along with a stayer ID EF 1634 which includes only the CDP, event counter, and hotel frequent stayer PIN fields described in conjunction with Table 33 above. Alternatively, a particular hotel chain or property might choose to implement a different file structure than that described above.
As mentioned briefly above, a preferred embodiment may be configured such that preferences are located in several files distributed throughout fob 102; i.e., in preferences EF 1114, airline preferences EF 1416, hotel preferences EF 1612 and 1604, and car preferences EF 1505. This allows apparently conflicting preferences to coexist within the fob depending on context. For example, it may be possible to opt for non-smoking in the fob user ID application while choosing the smoking option within the hotel application. In the case of conflict, preferences are read from the top level to the bottom level, and each level supersedes the previous one.
An exemplary set of codification rules are set forth in Table 37 below:
More specifically, in a preferred exemplary embodiment, preference flags are coded as set forth in Table 38 below.
In the context of fob transactions, data security has five primary dimensions: 1) data confidentiality, 2) data integrity, 3) access control, 4) authentication, and 5) non-repudiation. Each of these dimensions may be addressed through a variety of security mechanisms. Data confidentiality, which deals with keeping information secret (i.e., unreadable to those without access to a key), may be substantially ensured using encryption technology. Data integrity (and data source verification) focuses on ensuring that data remains unchanged during transfer, and typically employs message authentication techniques. Access control involves fob user verification and other requirements necessary in order for a party to read or update a particular file. Authentication involves ensuring that the fob and/or the external device may be what it purports to be, and non-repudiation deals with the related task of ensuring that the source of the data or message may be authentic, i.e., that a consumer may not repudiate a transaction by claiming that it was “signed” by an unauthorized party.
Authentication may be, in one embodiment, performed using a “challenge/response” algorithm. In general, authentication through a challenge/response system involves: 1) generation of a random number by a first party; 2) transmission of the random number to a second party (the “challenge”, 3) encryption of the random number by the second party in accordance with a key known to both parties, 4) transmission of the encrypted random number to the first party (the “response”), 5) encryption of the random number by the first party, and 6) comparison by the first party of the two resulting numbers. In the case where the two numbers match, authentication may be successful; if not, the authentication may be unsuccessful. Note that authentication can work both ways: the external world might request authentication of a fob (internal authentication), and a fob might request authentication of the external world (external authentication). A more detailed account of a preferred challenge/response algorithm can be found in the IBM MFC specification.
In a preferred embodiment, the DES algorithm (Data Encryption Standard) may be employed for the various security functions; however, it will be appreciated that any number of other symmetrical or asymmetrical techniques may be used in the context of the present invention. More particularly, there are two general categories of encryption algorithms: symmetric and asymmetric. Symmetric algorithms use the same key for encryption and decryption, for example, DEA (data encryption algorithm) which uses a 56-bit key to encrypt 64-bit blocks of data. Asymmetric algorithms, in contrast, use two different keys: one secret key and one public key. The RSA algorithm, for example, uses two such keys and exploits the computational complexity of factoring very large prime numbers. Additional information these and other cryptographic principles can be found in a number of standard texts, for example: Seberry & Pieprzyk, “Cryptography: An Introduction to Computer Security” (1989); Rhee, “Cryptography and Secure Communications” (1994); Stinson, “Cryptography: Theory and Practice” (1995); “Contemporary Cryptography: The Science of Information Integrity” (1992); and Schneier, “Applied Cryptography” (2d ed. 1996), the contents of which are hereby incorporated by reference.
Access control may be suitably provided by including access conditions within the header of each EF and DF. This prevents a particular operation (e.g., reading or updating) from being performed on a file unless the required access conditions have been fulfilled. Many different access conditions are appropriate in a fob context. For example, the fob might require fob user verification (i.e., request that the fob user enter a PIN) before a file operation may be allowed. Similarly, internal and/or external authentication as described above might be required.
Another important access condition (referred to herein as the SIGN condition) corresponds to the case where a particular file may be “protected” and where updating of a record requires “signing” of the data using a message authentication code (MAC). A MAC can be thought of as a form of electronic seal used to authenticate the content of the message. In a paradigmatic signing procedure, a shortened, encrypted representation of the message (the MAC) may be created using a message authentication algorithm (MAA) in conjunction with a key known to both the fob and external device. The MAC may be then appended onto the message and sent to the fob (or external device, depending on context), and the fob itself generates a MAC based on the received message and the known key. The fob then compares the received MAC with the its own internally-generated MAC. If either the message or MAC was altered during transmission, or the sending party did not use the correct key, then the two MACs will not match, and the access condition will not be fulfilled. If the two MACs correspond, then the access condition may be fulfilled, and the particular file operation can proceed.
A MAC may be generated using a variety of MAAs, for example, the ANSI X9.9 method using an eight-byte key, or the ANSI X9.19 method using a sixteen-byte key. Furthermore, the actual key may be “diversified” through encryption with a random number or other appropriate value. These and other details regarding MAC generation can be found in the references cited above as well as the IBM MFC specification.
Two other important access conditions are the NEVER and FREE conditions. The NEVER condition corresponds to the case where a certain file operation (typically updating) may be never allowed. The FREE condition, on the other hand, corresponds to the case where either updating or reading a file record may be always allowed, without any additional preconditions for access.
In contrast to the MAC techniques discussed briefly above, non-repudiation may be necessarily performed using asymmetrical techniques. That is, as symmetrical techniques such as MAC “sealing” use a key known to more than one party, such techniques can not be used by a third party to ascertain whether the source of the message may be correct. Thus, non-repudiation typically employs a public key encryption scheme (e.g., the Zimmerman's PGP system), wherein the sender uses a secret key to “sign” the message, and the receiving party uses the corresponding public key to authenticate the signature. In the context of the present invention, this function may be suitably performed by allocating an EF for public and secret key rings, which are well known in the art, along with suitable encryption software resident in the fob for assembling the signed message.
Having thus given a brief overview of typical fob security procedures, an exemplary set of access conditions may be set forth below in Table 39. In this regard, the various access conditions for each EF are tabulated with regard to whether the file may be being read or updated. In each case, the access condition (FREE, SIGN, etc.), key “owner” (issuer, partner, user, etc.), and key name are listed. In this regard, it will be appreciated that the key name may be arbitrary, and may be listed here for the sake of completeness.
Having thus given a detailed description of an exemplary fob 102 and a preferred data structure 1000, the various details related to transactions involving fob 102 will now be described. In general, a typical fob session involves: (1) activation of the RFID reader; (2) Information exchange between fob and host; and, at the conclusion of a session, (3) deactivation of RFID reader.
First, fob 102 communicates with RFID reader 104 provided at POS device 110, and suitable communications are made between transponder 114 on fob 102 and RFID reader 104 according to the methods described herein.
In the context of the present invention, command classes and instructions are provided for 1) working with application data (i.e., files stored within the various applications), 2) ensuring data security, 3) fob management, and 4) performing miscellaneous functions.
Application data commands are suitably directed at selecting, reading, and updating individual records or groups of records within files. Security commands suitably include commands for performing the challenge/response authentication process, generating random numbers, loading or updating cryptographic keys, and changing and verifying the fob user verification codes (e.g., PIN numbers). Fob management commands suitably include commands which allow for the creation and deletion of directories (DFs) and elementary files (EFs). Miscellaneous commands are suitably provided for modifying the baud rate and reading various fob statistics (e.g., data logged during production of the fob.) It will be appreciated that many different command sets could be designed for implementing these basic functions.
Referring again to
Consider, as another example, the typical hotel transaction. As detailed above, the fob user uses fob 102 to communicate with RFID reader 104 deployed at a suitable POS device 110. After appropriate initialization procedures take place, the fob user may be presented, through the use of a graphical user interface, the option to make a hotel reservation. Upon choosing this option, the software may interrogate the hotel preferences field in preferred programs EF 1128 in fob user ID application 1006 and display these hotels first within the list of possible choices.
After the fob user selects a specific hotel property, the software contacts the appropriate partner 1706 over network 136, 112 and requests a hotel room for a particular set of dates. This step might involve an interrogation of the various files within hotel system application 1012 to which the particular hotel has access (i.e., a hotel chain DF 1602 or property DF 1603), or this step may be deferred until check-in (as described below).
Once a reservation has been made, the associated confirmation number supplied by the hotel may be downloaded into the confirmation number field in reservation EF 1618 along with the date and the property code of the hotel. This step might require the fob user to transmit appropriate credit card account information, which may be suitably retrieved from pay1 EF 1304.
Upon arrival at the hotel, the fob user may use fob 102 to access a kiosk or other convenient POS provided for check-in. Thus, check-in may take place unassisted by hotel personnel and/or may involve a more traditional person-to-person interaction where fob 102 may be used primarily to streamline the check-in process initiated by personnel at the front desk.
At check-in, the confirmation number information may be retrieved from reservation EF 1618., and a particular room may be assigned (if not assigned previously). This step will typically involve retrieving, from the appropriate preference file (i.e., preferences EF 1604 or 1612), a list of preferences regarding bed size, room type, and the like. This list may be matched against the hotel's database of available rooms, thereby helping to streamline the room assignment process.
Once a room is assigned, a digital key corresponding to the assigned room (e.g., a numeric value or alphanumeric string) may be stored in key-of-the-room EF 1610. RFID readers may then be employed as part of the door lock apparatus for each room, which are configured to open only upon receiving the correct key.
At check-out time, payment may take place using payment account information stored in Payment account EF 1110 and pay1 EF 1304. Again, a suitable fob reader (i.e., RFID reader 104 configured at POS device 110), may be provided in any location convenient for check out, e.g., the hotel lobby or within the individual hotel rooms them-selves. The fob user may then acquire frequent stayer points, which would involve updating one of the stayer ID EFs 1606 (or 1636). During the course of his stay at the hotel, the fob user may have incurred any number of expenses related to room-service, on-site dining, film viewing, and the like. These expenses, or a subset thereof, may be conveniently downloaded into expenses EF 1616 for later retrieval, printout, or archiving.
Use of fob 102 in a rental car context would necessarily involve many of the same steps described above. The task of assigning a car would involve retrieving car preferences stored within preferences EF 1505 and comparing them to a database of available automobiles. Upon returning the automobile, the fob user might then be awarded frequent rental points (through update of frequent renter EF 1507), and an expense record might be stored within expenses EF 1511.
In the airline context, fob 102 could be used to make reservations, record preferences, and provide a payment means as described above. In addition, electronic tickets may be downloaded (EF IET 1410), and boarding information may be supplied via boarding EF 1412. Frequent flyer EF 1408 may then be used to update the fob user's frequent flyer miles.
While the example transactions set forth above are described in general terms, the particular nature of data flow to and from the appropriate database locations within the fob will be apparent to those skilled in the art.
Moreover, although the inventions set forth herein have been described in conjunction with the appended drawing figures, those skilled in the art will appreciate that the scope of the invention may be not so limited. For example, although the preferred embodiment of the invention may be discussed in the context of a standard fob with external contacts, it will be appreciated that virtually any portable memory device suitably configured may be utilized to practice this invention, for example, smart cards, optical cards, minicards, “super-smart” cards, and the like. Hence, various modifications in the design and arrangement of the components and steps discussed herein may be made without departing from the scope of the invention as set forth in the appended claims. For a detailed explanation of storing travel-related data on a smartcard in accordance with the present invention, see U.S. Pat. No. 6,101,477, issued Aug. 8, 2000, entitled “A SYSTEM AND METHODS FOR A TRAVEL-RELATED MULTI-FUNCTION SMARTCARD,” incorporated herein by reference.
This invention may be a continuation in part of U.S. Ser. No. 10/340,352, filed on Jan. 10, 2003, and entitled “SYSTEM AND METHOD FOR INCENTING PAYMENT USING RADIO FREQUENCY IDENTIFICATION IN CONTACT AND CONTACTLESS TRANSACTIONS.” The '352 application itself claims priority to U.S. patent application Ser. No. 10/192,488, entitled “SYSTEM AND METHOD FOR PAYMENT USING RADIO FREQUENCY IDENTIFICATION IN CONTACT AND CONTACTLESS TRANSACTIONS,” filed on Jul. 9, 2002 (which itself claims priority to U.S. Provisional No. 60/304,216, filed on Jul. 10, 2001); U.S. patent application Ser. No. 10/318,432, entitled “SYSTEM AND METHOD FOR SELECTING LOAD OPTIONS FOR USE IN RADIO FREQUENCY IDENTIFICATION IN CONTACT AND CONTACTLESS TRANSACTIONS,” filed Dec. 13, 2002; U.S. patent application Ser. No. 10/318,480, entitled “SYSTEM AND METHOD FOR PAYMENT USING RADIO FREQUENCY IDENTIFICATION IN CONTACT AND CONTACTLESS TRANSACTIONS,” filed Dec. 13, 2002; and, U.S. Provisional Patent Application Ser. No. 60/396,577, filed Jul. 16, 2002. All of the above applications are hereby incorporated by reference.
| Number | Name | Date | Kind |
|---|---|---|---|
| 4072930 | Lucero et al. | Feb 1978 | A |
| 4303904 | Chasek | Dec 1981 | A |
| 4443027 | McNeely et al. | Apr 1984 | A |
| 4450535 | de Pommery et al. | May 1984 | A |
| 4475308 | Heise et al. | Oct 1984 | A |
| 4583766 | Wessel | Apr 1986 | A |
| 4639765 | dHont | Jan 1987 | A |
| 4672021 | Blumel et al. | Jun 1987 | A |
| 4700055 | Kashkashian, Jr. | Oct 1987 | A |
| 4736094 | Yoshida | Apr 1988 | A |
| 4739328 | Koelle et al. | Apr 1988 | A |
| 4837422 | Dethloff et al. | Jun 1989 | A |
| 4839504 | Nakano | Jun 1989 | A |
| 4868849 | Tamaoki | Sep 1989 | A |
| 4961142 | Elliott et al. | Oct 1990 | A |
| 5006983 | Wayne et al. | Apr 1991 | A |
| 5016274 | Micali et al. | May 1991 | A |
| 5023782 | Lutz et al. | Jun 1991 | A |
| 5023908 | Weiss | Jun 1991 | A |
| 5025372 | Burton et al. | Jun 1991 | A |
| 5053774 | Schuermann et al. | Oct 1991 | A |
| 5099226 | Andrews | Mar 1992 | A |
| 5101200 | Swett | Mar 1992 | A |
| 5197140 | Balmer | Mar 1993 | A |
| 5202826 | McCarthy | Apr 1993 | A |
| 5212777 | Gove et al. | May 1993 | A |
| 5221838 | Gutman et al. | Jun 1993 | A |
| 5222282 | Sukonnik et al. | Jun 1993 | A |
| 5226989 | Sukonnik | Jul 1993 | A |
| 5231273 | Caswell et al. | Jul 1993 | A |
| 5239654 | IngSimmons et al. | Aug 1993 | A |
| 5247304 | dHont | Sep 1993 | A |
| 5274392 | dHont et al. | Dec 1993 | A |
| 5276311 | Hennige | Jan 1994 | A |
| 5285100 | Byatt | Feb 1994 | A |
| 5305002 | Holodak et al. | Apr 1994 | A |
| 5326964 | Risser | Jul 1994 | A |
| 5329617 | Asal | Jul 1994 | A |
| 5331138 | Saroya | Jul 1994 | A |
| 5339447 | Balmer | Aug 1994 | A |
| 5349357 | Schurmann et al. | Sep 1994 | A |
| 5350906 | Brody et al. | Sep 1994 | A |
| 5351052 | dHont et al. | Sep 1994 | A |
| 5365551 | Snodgrass et al. | Nov 1994 | A |
| 5371896 | Gove et al. | Dec 1994 | A |
| 5373303 | dHont | Dec 1994 | A |
| 5397881 | Mannik | Mar 1995 | A |
| 5407893 | Koshizuka et al. | Apr 1995 | A |
| 5408243 | dHont | Apr 1995 | A |
| 5410649 | Gove | Apr 1995 | A |
| 5428363 | dHont | Jun 1995 | A |
| 5453601 | Rosen | Sep 1995 | A |
| 5453747 | dHont et al. | Sep 1995 | A |
| 5461217 | Claus | Oct 1995 | A |
| 5471592 | Gove et al. | Nov 1995 | A |
| 5485510 | Colbert | Jan 1996 | A |
| 5488376 | Hurta et al. | Jan 1996 | A |
| 5489411 | Jha et al. | Feb 1996 | A |
| 5489908 | Orthmann et al. | Feb 1996 | A |
| 5490079 | Sharpe et al. | Feb 1996 | A |
| 5491483 | dHont | Feb 1996 | A |
| 5491484 | Schuermann | Feb 1996 | A |
| 5491715 | Flaxl | Feb 1996 | A |
| 5493312 | Knebelkamp | Feb 1996 | A |
| 5497121 | dHont | Mar 1996 | A |
| 5500513 | Langhans et al. | Mar 1996 | A |
| 5500651 | Schuermann | Mar 1996 | A |
| 5504808 | Hamrick, Jr. | Apr 1996 | A |
| 5513525 | Schurmann | May 1996 | A |
| 5519381 | Marsh et al. | May 1996 | A |
| 5522083 | Gove et al. | May 1996 | A |
| 5525992 | Froschermeier | Jun 1996 | A |
| 5525994 | Hurta et al. | Jun 1996 | A |
| 5530232 | Taylor | Jun 1996 | A |
| 5537314 | Kanter | Jul 1996 | A |
| 5541604 | Meier | Jul 1996 | A |
| 5543798 | Schuermann | Aug 1996 | A |
| 5544246 | Mandelbaum et al. | Aug 1996 | A |
| 5548291 | Meier et al. | Aug 1996 | A |
| 5550536 | Flaxl | Aug 1996 | A |
| 5550548 | Schuermann | Aug 1996 | A |
| 5552789 | Schuermann | Sep 1996 | A |
| 5557279 | dHont | Sep 1996 | A |
| 5557516 | Hogan | Sep 1996 | A |
| 5561430 | Knebelkamp | Oct 1996 | A |
| 5563582 | dHont | Oct 1996 | A |
| 5569187 | Kaiser | Oct 1996 | A |
| 5572226 | Tuttle | Nov 1996 | A |
| 5577109 | Stimson et al. | Nov 1996 | A |
| 5577120 | Penzias | Nov 1996 | A |
| 5578808 | Taylor | Nov 1996 | A |
| 5581630 | Bonneau, Jr. | Dec 1996 | A |
| 5585787 | Wallerstein | Dec 1996 | A |
| 5590038 | Pitroda | Dec 1996 | A |
| 5592150 | dHont | Jan 1997 | A |
| 5592405 | Gove et al. | Jan 1997 | A |
| 5594227 | Deo | Jan 1997 | A |
| 5594233 | Kenneth et al. | Jan 1997 | A |
| 5594448 | dHont | Jan 1997 | A |
| 5597534 | Kaiser | Jan 1997 | A |
| 5600175 | Orthmann | Feb 1997 | A |
| 5602538 | Orthmann et al. | Feb 1997 | A |
| 5602919 | Hurta et al. | Feb 1997 | A |
| 5604342 | Fujioka | Feb 1997 | A |
| 5606520 | Gove et al. | Feb 1997 | A |
| 5606594 | Register et al. | Feb 1997 | A |
| 5607522 | McDonnell | Mar 1997 | A |
| 5608406 | Eberth et al. | Mar 1997 | A |
| 5608778 | Partridge, III | Mar 1997 | A |
| 5613146 | Gove et al. | Mar 1997 | A |
| 5614703 | Martin et al. | Mar 1997 | A |
| 5619207 | dHont | Apr 1997 | A |
| 5621396 | Flaxl | Apr 1997 | A |
| 5621411 | Hagl et al. | Apr 1997 | A |
| 5621412 | Sharpe et al. | Apr 1997 | A |
| 5625366 | dHont | Apr 1997 | A |
| 5625370 | dHont | Apr 1997 | A |
| 5625695 | MRaihi et al. | Apr 1997 | A |
| 5629981 | Nerlikar | May 1997 | A |
| 5638080 | Orthmann et al. | Jun 1997 | A |
| 5640002 | Ruppert et al. | Jun 1997 | A |
| 5641050 | Smith et al. | Jun 1997 | A |
| 5646607 | Schurmann et al. | Jul 1997 | A |
| 5649118 | Carlisle | Jul 1997 | A |
| 5657388 | Weiss | Aug 1997 | A |
| 5660319 | Falcone et al. | Aug 1997 | A |
| 5673106 | Thompson | Sep 1997 | A |
| 5675342 | Sharpe | Oct 1997 | A |
| 5686920 | Hurta et al. | Nov 1997 | A |
| 5689100 | Carrithers | Nov 1997 | A |
| 5691731 | vanErven | Nov 1997 | A |
| 5692132 | Hogan | Nov 1997 | A |
| 5696913 | Gove et al. | Dec 1997 | A |
| 5698837 | Furuta | Dec 1997 | A |
| 5699528 | Hogan | Dec 1997 | A |
| 5701127 | Sharpe | Dec 1997 | A |
| 5704046 | Hogan | Dec 1997 | A |
| 5705798 | Tarbox | Jan 1998 | A |
| 5715399 | Bezos | Feb 1998 | A |
| 5721781 | Deo et al. | Feb 1998 | A |
| 5724424 | Gifford | Mar 1998 | A |
| 5729053 | Orthmann | Mar 1998 | A |
| 5729236 | Flaxl | Mar 1998 | A |
| 5731957 | Brennan | Mar 1998 | A |
| 5732579 | dHont et al. | Mar 1998 | A |
| 5734838 | Robinson et al. | Mar 1998 | A |
| 5742756 | Dillaway et al. | Apr 1998 | A |
| 5742845 | Wagner | Apr 1998 | A |
| 5748137 | dHont | May 1998 | A |
| 5748737 | Daggar | May 1998 | A |
| 5758195 | Balmer | May 1998 | A |
| 5761306 | Lewis | Jun 1998 | A |
| 5761493 | Blakeley et al. | Jun 1998 | A |
| 5768385 | Simon | Jun 1998 | A |
| 5768609 | Gove et al. | Jun 1998 | A |
| 5770843 | Rose | Jun 1998 | A |
| 5774882 | Keen et al. | Jun 1998 | A |
| 5777903 | Piosenka et al. | Jul 1998 | A |
| 5778067 | Jones et al. | Jul 1998 | A |
| 5778069 | Thomlinson | Jul 1998 | A |
| 5785680 | Niezink et al. | Jul 1998 | A |
| 5792337 | Padovani et al. | Aug 1998 | A |
| 5793324 | Aslanidis et al. | Aug 1998 | A |
| 5794095 | Thompson | Aug 1998 | A |
| 5797060 | Thompson | Aug 1998 | A |
| 5797085 | Buek et al. | Aug 1998 | A |
| 5797133 | Jones et al. | Aug 1998 | A |
| 5798709 | Flaxl | Aug 1998 | A |
| 5809142 | Hurta et al. | Sep 1998 | A |
| 5809288 | Balmer | Sep 1998 | A |
| 5809633 | Mundigl et al. | Sep 1998 | A |
| 5825007 | Jesadanont | Oct 1998 | A |
| 5825302 | Stafford | Oct 1998 | A |
| 5826077 | Blakeley et al. | Oct 1998 | A |
| 5826241 | Stein | Oct 1998 | A |
| 5826242 | Montulli | Oct 1998 | A |
| 5826243 | Musmanno et al. | Oct 1998 | A |
| 5828044 | Jun et al. | Oct 1998 | A |
| 5834756 | Gutman et al. | Nov 1998 | A |
| 5835894 | Adcock et al. | Nov 1998 | A |
| 5841364 | Hagl et al. | Nov 1998 | A |
| 5842088 | Thompson | Nov 1998 | A |
| 5844218 | Kawan et al. | Dec 1998 | A |
| 5844230 | Lalonde | Dec 1998 | A |
| 5845267 | Ronen | Dec 1998 | A |
| 5851149 | Xidos et al. | Dec 1998 | A |
| 5852812 | Reeder | Dec 1998 | A |
| 5854891 | Postlewaite et al. | Dec 1998 | A |
| 5858006 | Van der AA et al. | Jan 1999 | A |
| 5859419 | Wynn | Jan 1999 | A |
| 5859779 | Giordano et al. | Jan 1999 | A |
| 5862325 | Reed et al. | Jan 1999 | A |
| 5864306 | Dwyer et al. | Jan 1999 | A |
| 5864323 | Berthon | Jan 1999 | A |
| 5864830 | Armetta et al. | Jan 1999 | A |
| 5867100 | dHont | Feb 1999 | A |
| 5870031 | Kaiser et al. | Feb 1999 | A |
| 5870915 | dHont | Feb 1999 | A |
| 5878138 | Yacobi | Mar 1999 | A |
| 5878141 | Daly et al. | Mar 1999 | A |
| 5878215 | Kling et al. | Mar 1999 | A |
| 5878337 | Joao et al. | Mar 1999 | A |
| 5878403 | DeFrancesco et al. | Mar 1999 | A |
| 5880675 | Trautner | Mar 1999 | A |
| 5881272 | Balmer | Mar 1999 | A |
| 5883810 | Franklin et al. | Mar 1999 | A |
| 5884280 | Yoshioka et al. | Mar 1999 | A |
| 5887266 | Heinonen et al. | Mar 1999 | A |
| 5890137 | Koreeda | Mar 1999 | A |
| 5897622 | Blinn et al. | Apr 1999 | A |
| 5898783 | Rohrbach | Apr 1999 | A |
| 5898838 | Wagner | Apr 1999 | A |
| 5903830 | Joao et al. | May 1999 | A |
| 5903875 | Kohara | May 1999 | A |
| 5903880 | Biffar | May 1999 | A |
| 5905798 | Nerlikar et al. | May 1999 | A |
| 5905908 | Wagner | May 1999 | A |
| 5909492 | Payne et al. | Jun 1999 | A |
| 5912678 | Saxena et al. | Jun 1999 | A |
| 5913203 | Wong et al. | Jun 1999 | A |
| 5914472 | Foladare et al. | Jun 1999 | A |
| 5915023 | Bernstein | Jun 1999 | A |
| 5917168 | Nakamura et al. | Jun 1999 | A |
| 5918216 | Miksovsky et al. | Jun 1999 | A |
| 5920628 | Indeck et al. | Jul 1999 | A |
| 5923734 | Taskett | Jul 1999 | A |
| 5929801 | Aslanidis et al. | Jul 1999 | A |
| 5930767 | Reber et al. | Jul 1999 | A |
| 5930777 | Barber | Jul 1999 | A |
| 5931917 | Nguyen et al. | Aug 1999 | A |
| 5933624 | Balmer | Aug 1999 | A |
| 5943624 | Fox et al. | Aug 1999 | A |
| 5948116 | Aslanidis et al. | Sep 1999 | A |
| 5949044 | Walker et al. | Sep 1999 | A |
| 5949876 | Ginter et al. | Sep 1999 | A |
| 5953512 | Cai et al. | Sep 1999 | A |
| 5953710 | Fleming | Sep 1999 | A |
| 5955717 | Vanstone | Sep 1999 | A |
| 5955969 | dHont | Sep 1999 | A |
| 5956024 | Strickland et al. | Sep 1999 | A |
| 5956699 | Wong et al. | Sep 1999 | A |
| 5958004 | Helland et al. | Sep 1999 | A |
| 5960411 | Hartman et al. | Sep 1999 | A |
| 5963915 | Kirsch | Oct 1999 | A |
| 5963924 | Williams et al. | Oct 1999 | A |
| 5966697 | Fergerson et al. | Oct 1999 | A |
| 5970148 | Meier | Oct 1999 | A |
| 5970471 | Hill | Oct 1999 | A |
| 5970472 | Allsop et al. | Oct 1999 | A |
| 5970473 | Gerszberg et al. | Oct 1999 | A |
| 5970475 | Barnes et al. | Oct 1999 | A |
| RE36365 | Levine et al. | Nov 1999 | E |
| 5978840 | Nguyen et al. | Nov 1999 | A |
| 5979757 | Tracy et al. | Nov 1999 | A |
| 5982293 | Everett et al. | Nov 1999 | A |
| 5983207 | Turk et al. | Nov 1999 | A |
| 5983208 | Haller et al. | Nov 1999 | A |
| 5987140 | Rowney et al. | Nov 1999 | A |
| 5987155 | Dunn et al. | Nov 1999 | A |
| 5987498 | Athing et al. | Nov 1999 | A |
| 5989950 | Wu | Nov 1999 | A |
| 5991413 | Arditti et al. | Nov 1999 | A |
| 5991608 | Leyten | Nov 1999 | A |
| 5991748 | Taskett | Nov 1999 | A |
| 5991750 | Watson | Nov 1999 | A |
| 5996076 | Rowney et al. | Nov 1999 | A |
| 5999914 | Blinn et al. | Dec 1999 | A |
| 6000832 | Franklin et al. | Dec 1999 | A |
| 6002438 | Hocevar et al. | Dec 1999 | A |
| 6002767 | Kramer | Dec 1999 | A |
| 6003014 | Lee et al. | Dec 1999 | A |
| 6005942 | Chan et al. | Dec 1999 | A |
| 6006216 | Griffin et al. | Dec 1999 | A |
| 6009412 | Storey | Dec 1999 | A |
| 6011487 | Plocher | Jan 2000 | A |
| 6012039 | Hoffman et al. | Jan 2000 | A |
| 6012049 | Kawan | Jan 2000 | A |
| 6012143 | Tanaka | Jan 2000 | A |
| 6012636 | Smith | Jan 2000 | A |
| 6014634 | Scroggie et al. | Jan 2000 | A |
| 6014635 | Harris et al. | Jan 2000 | A |
| 6014636 | Reeder | Jan 2000 | A |
| 6014645 | Cunningham | Jan 2000 | A |
| 6014646 | Vallee et al. | Jan 2000 | A |
| 6014648 | Brennan | Jan 2000 | A |
| 6014650 | Zampese | Jan 2000 | A |
| 6014748 | Tushi et al. | Jan 2000 | A |
| 6016482 | Molinari et al. | Jan 2000 | A |
| 6016484 | Williams et al. | Jan 2000 | A |
| 6018717 | Lee et al. | Jan 2000 | A |
| 6018718 | Walker et al. | Jan 2000 | A |
| 6021943 | Chastain | Feb 2000 | A |
| 6023510 | Epstein | Feb 2000 | A |
| 6024286 | Bradley et al. | Feb 2000 | A |
| 6029147 | Horadan et al. | Feb 2000 | A |
| 6029149 | Dykstra et al. | Feb 2000 | A |
| 6029150 | Kravitz | Feb 2000 | A |
| 6029890 | Austin | Feb 2000 | A |
| 6029892 | Miyake | Feb 2000 | A |
| 6032136 | Brake et al. | Feb 2000 | A |
| 6038292 | Thomas | Mar 2000 | A |
| 6038551 | Barlow et al. | Mar 2000 | A |
| 6038584 | Balmer | Mar 2000 | A |
| 6041308 | Walker et al. | Mar 2000 | A |
| 6044360 | Picciallo | Mar 2000 | A |
| 6047888 | Dethloff | Apr 2000 | A |
| 6052675 | Checchio | Apr 2000 | A |
| 6058418 | Kobata | May 2000 | A |
| 6061344 | Wood, Jr. | May 2000 | A |
| 6061789 | Hauser et al. | May 2000 | A |
| 6064320 | dHont et al. | May 2000 | A |
| 6064981 | Barni et al. | May 2000 | A |
| 6070003 | Gove et al. | May 2000 | A |
| 6070150 | Remington et al. | May 2000 | A |
| 6070154 | Tavor et al. | May 2000 | A |
| 6070156 | Hartsell, Jr. | May 2000 | A |
| 6072870 | Nguyen et al. | Jun 2000 | A |
| 6073840 | Marion | Jun 2000 | A |
| 6076078 | Camp et al. | Jun 2000 | A |
| 6078888 | Johnson, Jr. | Jun 2000 | A |
| 6078906 | Huberman | Jun 2000 | A |
| 6078908 | Schmitz | Jun 2000 | A |
| 6081790 | Rosen | Jun 2000 | A |
| RE36788 | Mansvelt et al. | Jul 2000 | E |
| 6088683 | Jalili | Jul 2000 | A |
| 6088686 | Walker et al. | Jul 2000 | A |
| 6088717 | Reed et al. | Jul 2000 | A |
| 6088797 | Rosen | Jul 2000 | A |
| 6089284 | Kaehler et al. | Jul 2000 | A |
| 6092057 | Zimmerman et al. | Jul 2000 | A |
| 6092198 | Lanzy et al. | Jul 2000 | A |
| 6098053 | Slater | Aug 2000 | A |
| 6098879 | Terranova | Aug 2000 | A |
| 6101174 | Langston | Aug 2000 | A |
| 6102162 | Teicher | Aug 2000 | A |
| 6102672 | Woollenweber | Aug 2000 | A |
| 6105008 | Davis et al. | Aug 2000 | A |
| 6105013 | Curry et al. | Aug 2000 | A |
| 6105865 | Hardesty | Aug 2000 | A |
| 6108641 | Kenna et al. | Aug 2000 | A |
| 6109525 | Blomqvist et al. | Aug 2000 | A |
| 6112152 | Tuttle | Aug 2000 | A |
| 6112191 | Burke | Aug 2000 | A |
| 6115360 | Quay et al. | Sep 2000 | A |
| 6115458 | Taskett | Sep 2000 | A |
| 6116423 | Troxtell, Jr. et al. | Sep 2000 | A |
| 6116505 | Withrow | Sep 2000 | A |
| 6118189 | Flaxl | Sep 2000 | A |
| 6121544 | Petsinger | Sep 2000 | A |
| 6122625 | Rosen | Sep 2000 | A |
| 6123223 | Watkins | Sep 2000 | A |
| 6125352 | Franklin et al. | Sep 2000 | A |
| 6129274 | Suzuki | Oct 2000 | A |
| 6133834 | Eberth et al. | Oct 2000 | A |
| 6141651 | Riley et al. | Oct 2000 | A |
| 6141752 | Dancs et al. | Oct 2000 | A |
| 6163771 | Walker et al. | Dec 2000 | A |
| 6167236 | Kaiser et al. | Dec 2000 | A |
| 6173269 | Sokol et al. | Jan 2001 | B1 |
| 6173272 | Thomas et al. | Jan 2001 | B1 |
| 6177860 | Cromer et al. | Jan 2001 | B1 |
| 6179205 | Sloan | Jan 2001 | B1 |
| 6179206 | Matsumori | Jan 2001 | B1 |
| 6188994 | Egendorf | Feb 2001 | B1 |
| 6189787 | Dorf | Feb 2001 | B1 |
| 6192255 | Lewis et al. | Feb 2001 | B1 |
| 6198728 | Hulyalkar et al. | Mar 2001 | B1 |
| 6198875 | Edenson et al. | Mar 2001 | B1 |
| 6202927 | Bashan et al. | Mar 2001 | B1 |
| 6205151 | Quay et al. | Mar 2001 | B1 |
| 6206293 | Gutman et al. | Mar 2001 | B1 |
| 6213390 | Oneda | Apr 2001 | B1 |
| 6215437 | Schurmann et al. | Apr 2001 | B1 |
| 6216219 | Cai et al. | Apr 2001 | B1 |
| 6219439 | Burger | Apr 2001 | B1 |
| 6220510 | Everett et al. | Apr 2001 | B1 |
| 6222914 | McMullin | Apr 2001 | B1 |
| D442627 | Webb et al. | May 2001 | S |
| D442629 | Webb et al. | May 2001 | S |
| 6223984 | Renner et al. | May 2001 | B1 |
| 6226382 | MRaihi et al. | May 2001 | B1 |
| 6227447 | Campisano | May 2001 | B1 |
| 6230270 | Laczko, Sr. | May 2001 | B1 |
| 6232917 | Baumer et al. | May 2001 | B1 |
| 6233683 | Chan et al. | May 2001 | B1 |
| 6237848 | Everett | May 2001 | B1 |
| 6239675 | Flaxl | May 2001 | B1 |
| 6240187 | Lewis | May 2001 | B1 |
| 6248199 | Smulson | Jun 2001 | B1 |
| 6257486 | Teicher et al. | Jul 2001 | B1 |
| 6259769 | Page | Jul 2001 | B1 |
| 6260026 | Tomida et al. | Jul 2001 | B1 |
| 6260088 | Gove et al. | Jul 2001 | B1 |
| 6263316 | Khan et al. | Jul 2001 | B1 |
| 6263319 | Leatherman | Jul 2001 | B1 |
| 6264106 | Bridgelall | Jul 2001 | B1 |
| 6266754 | Laczko, Sr. et al. | Jul 2001 | B1 |
| 6267292 | Walker et al. | Jul 2001 | B1 |
| 6269348 | Pare, Jr. et al. | Jul 2001 | B1 |
| 6273335 | Sloan | Aug 2001 | B1 |
| 6282522 | Davis et al. | Aug 2001 | B1 |
| D447515 | Faenza, Jr. et al. | Sep 2001 | S |
| 6286763 | Reynolds et al. | Sep 2001 | B1 |
| 6289324 | Kawan | Sep 2001 | B1 |
| 6293462 | Gangi | Sep 2001 | B1 |
| 6315193 | Hogan | Nov 2001 | B1 |
| 6315195 | Ramachandran | Nov 2001 | B1 |
| 6317721 | Hurta et al. | Nov 2001 | B1 |
| 6318636 | Reynolds et al. | Nov 2001 | B1 |
| 6323566 | Meier | Nov 2001 | B1 |
| 6325285 | Baratelli | Dec 2001 | B1 |
| 6325293 | Moreno | Dec 2001 | B1 |
| 6326934 | Kinzie | Dec 2001 | B1 |
| 6327573 | Walker et al. | Dec 2001 | B1 |
| 6330544 | Walker et al. | Dec 2001 | B1 |
| 6332193 | Glass et al. | Dec 2001 | B1 |
| 6336095 | Rosen | Jan 2002 | B1 |
| 6342844 | Rozin | Jan 2002 | B1 |
| 6353811 | Weissman | Mar 2002 | B1 |
| 6364208 | Stanford et al. | Apr 2002 | B1 |
| 6367011 | Lee et al. | Apr 2002 | B1 |
| 6374245 | Park | Apr 2002 | B1 |
| 6377034 | Ivanov | Apr 2002 | B1 |
| 6378073 | Davis et al. | Apr 2002 | B1 |
| 6388533 | Swoboda | May 2002 | B2 |
| 6390375 | Kayanakis | May 2002 | B2 |
| 6400272 | Holtzman et al. | Jun 2002 | B1 |
| 6402026 | Schwier | Jun 2002 | B1 |
| 6402028 | Graham, Jr. et al. | Jun 2002 | B1 |
| 6411611 | Van der Tuijn | Jun 2002 | B1 |
| 6415978 | McAllister | Jul 2002 | B1 |
| 6422464 | Terranova | Jul 2002 | B1 |
| 6424029 | Giesler | Jul 2002 | B1 |
| RE37822 | Anthonyson | Aug 2002 | E |
| 6427910 | Barnes et al. | Aug 2002 | B1 |
| 6438235 | Sims, III | Aug 2002 | B2 |
| 6439455 | Everett et al. | Aug 2002 | B1 |
| 6442532 | Kawan | Aug 2002 | B1 |
| 6445794 | Shefi | Sep 2002 | B1 |
| 6457996 | Shih | Oct 2002 | B1 |
| 6466804 | Pecen et al. | Oct 2002 | B1 |
| 6473500 | Risafi et al. | Oct 2002 | B1 |
| 6480100 | Frieden et al. | Nov 2002 | B1 |
| 6480101 | Kelly et al. | Nov 2002 | B1 |
| 6481621 | Herrendoerfer et al. | Nov 2002 | B1 |
| 6481632 | Wentker et al. | Nov 2002 | B2 |
| 6483427 | Werb | Nov 2002 | B1 |
| 6483477 | Plonka | Nov 2002 | B1 |
| 6483929 | Murakami et al. | Nov 2002 | B1 |
| 6484937 | Devaux et al. | Nov 2002 | B1 |
| 6490443 | Freeny, Jr. | Dec 2002 | B1 |
| 6491229 | Berney | Dec 2002 | B1 |
| 6494380 | Jarosz | Dec 2002 | B2 |
| 6507762 | Amro et al. | Jan 2003 | B1 |
| 6509829 | Tuttle | Jan 2003 | B1 |
| 6510983 | Horowitz et al. | Jan 2003 | B2 |
| 6510998 | Stanford et al. | Jan 2003 | B1 |
| 6513015 | Ogasawara | Jan 2003 | B2 |
| 6519565 | Clements et al. | Feb 2003 | B1 |
| 6520542 | Thompson et al. | Feb 2003 | B2 |
| 6529880 | McKeen et al. | Mar 2003 | B1 |
| 6535726 | Johnson | Mar 2003 | B1 |
| 6546373 | Cerra | Apr 2003 | B1 |
| 6547133 | DeVries, Jr. et al. | Apr 2003 | B1 |
| 6549912 | Chen | Apr 2003 | B1 |
| 6560581 | Fox et al. | May 2003 | B1 |
| 6577229 | Bonneau et al. | Jun 2003 | B1 |
| 6578768 | Binder et al. | Jun 2003 | B1 |
| 6581839 | Lasch et al. | Jun 2003 | B1 |
| 6587835 | Treyz et al. | Jul 2003 | B1 |
| 6588660 | Buescher et al. | Jul 2003 | B1 |
| 6589119 | Orus et al. | Jul 2003 | B1 |
| 6598024 | Walker et al. | Jul 2003 | B1 |
| 6608995 | Kawasaki et al. | Aug 2003 | B1 |
| 6609655 | Harrell | Aug 2003 | B1 |
| 6623039 | Thompson et al. | Sep 2003 | B2 |
| 6626356 | Davenport et al. | Sep 2003 | B2 |
| 6628961 | Ho et al. | Sep 2003 | B1 |
| 6629591 | Griswold et al. | Oct 2003 | B1 |
| 6636833 | Flitcroft et al. | Oct 2003 | B1 |
| 6650887 | McGregor et al. | Nov 2003 | B2 |
| 6662166 | Pare, Jr. et al. | Dec 2003 | B2 |
| 6665405 | Lenstra | Dec 2003 | B1 |
| 6669086 | Abdi et al. | Dec 2003 | B2 |
| 6671358 | Seidman et al. | Dec 2003 | B1 |
| 6674786 | Nakamura et al. | Jan 2004 | B1 |
| 6679427 | Kuroiwa | Jan 2004 | B1 |
| 6681328 | Harris et al. | Jan 2004 | B1 |
| 6684269 | Wagner | Jan 2004 | B2 |
| 6687714 | Kogen et al. | Feb 2004 | B1 |
| 6690930 | Dupre | Feb 2004 | B1 |
| 6693513 | Tuttle | Feb 2004 | B2 |
| 6703918 | Kita | Mar 2004 | B1 |
| 6705530 | Kiekhaefer | Mar 2004 | B2 |
| 6711262 | Watanen | Mar 2004 | B1 |
| 6732936 | Kiekhaefer | May 2004 | B1 |
| 6742120 | Markakis et al. | May 2004 | B1 |
| 6747546 | Hikita et al. | Jun 2004 | B1 |
| 6760581 | Dutta | Jul 2004 | B2 |
| 6769718 | Warther et al. | Aug 2004 | B1 |
| 6771981 | Zalewski et al. | Aug 2004 | B1 |
| 6789012 | Childs et al. | Sep 2004 | B1 |
| 6834270 | Pagani et al. | Dec 2004 | B1 |
| 6851617 | Saint et al. | Feb 2005 | B2 |
| 6853087 | Neuhaus et al. | Feb 2005 | B2 |
| 6853894 | Kolls | Feb 2005 | B1 |
| 6853987 | Cook | Feb 2005 | B1 |
| 6857566 | Wankmueller | Feb 2005 | B2 |
| 6859672 | Roberts et al. | Feb 2005 | B2 |
| 6895310 | Kolls | May 2005 | B1 |
| 6952156 | Arshad et al. | Oct 2005 | B2 |
| 6994262 | Warther | Feb 2006 | B1 |
| 7003501 | Ostroff | Feb 2006 | B2 |
| 7069444 | Lowensohn et al. | Jun 2006 | B2 |
| 7096204 | Chen et al. | Aug 2006 | B1 |
| 7100821 | Rasti | Sep 2006 | B2 |
| 7103575 | Linehan | Sep 2006 | B1 |
| 7110880 | Breed et al. | Sep 2006 | B2 |
| 7136835 | Flitcroft et al. | Nov 2006 | B1 |
| 7213748 | Tsuei et al. | May 2007 | B2 |
| 20010013542 | Horowitz et al. | Aug 2001 | A1 |
| 20010024157 | Hansmann et al. | Sep 2001 | A1 |
| 20010034565 | Leatherman | Oct 2001 | A1 |
| 20010034720 | Armes | Oct 2001 | A1 |
| 20010039617 | Buhrlen et al. | Nov 2001 | A1 |
| 20010049628 | Icho | Dec 2001 | A1 |
| 20020011519 | Shults | Jan 2002 | A1 |
| 20020026419 | Maritzen et al. | Feb 2002 | A1 |
| 20020028704 | Bloomfield et al. | Mar 2002 | A1 |
| 20020035548 | Hogan et al. | Mar 2002 | A1 |
| 20020046341 | Kazaks et al. | Apr 2002 | A1 |
| 20020052839 | Takatori | May 2002 | A1 |
| 20020062284 | Kawan | May 2002 | A1 |
| 20020074398 | Lancos et al. | Jun 2002 | A1 |
| 20020077837 | Krueger et al. | Jun 2002 | A1 |
| 20020077895 | Howell | Jun 2002 | A1 |
| 20020077992 | Tobin | Jun 2002 | A1 |
| 20020079367 | Montani | Jun 2002 | A1 |
| 20020092914 | Pentz et al. | Jul 2002 | A1 |
| 20020095298 | Ewing | Jul 2002 | A1 |
| 20020095343 | Barton et al. | Jul 2002 | A1 |
| 20020095389 | Gaines | Jul 2002 | A1 |
| 20020095587 | Doyle et al. | Jul 2002 | A1 |
| 20020097144 | Collins et al. | Jul 2002 | A1 |
| 20020107007 | Gerson | Aug 2002 | A1 |
| 20020107742 | Magill | Aug 2002 | A1 |
| 20020109580 | Shreve et al. | Aug 2002 | A1 |
| 20020111210 | Luciano, Jr. et al. | Aug 2002 | A1 |
| 20020111917 | Hoffman et al. | Aug 2002 | A1 |
| 20020113082 | Leatherman et al. | Aug 2002 | A1 |
| 20020116274 | Hind et al. | Aug 2002 | A1 |
| 20020120584 | Hogan et al. | Aug 2002 | A1 |
| 20020126010 | Trimble et al. | Sep 2002 | A1 |
| 20020131567 | Maginas | Sep 2002 | A1 |
| 20020138438 | Bardwell | Sep 2002 | A1 |
| 20020140542 | Prokoski et al. | Oct 2002 | A1 |
| 20020145043 | Challa et al. | Oct 2002 | A1 |
| 20020147913 | Yip | Oct 2002 | A1 |
| 20020148892 | Bardwell | Oct 2002 | A1 |
| 20020152123 | Giordano et al. | Oct 2002 | A1 |
| 20020154795 | Lee et al. | Oct 2002 | A1 |
| 20020166891 | Stoutenburg et al. | Nov 2002 | A1 |
| 20020174067 | Hoffman et al. | Nov 2002 | A1 |
| 20020176522 | Fan | Nov 2002 | A1 |
| 20020178063 | Gravelle et al. | Nov 2002 | A1 |
| 20020178369 | Black | Nov 2002 | A1 |
| 20020185543 | Pentz et al. | Dec 2002 | A1 |
| 20020188501 | Lefkowith | Dec 2002 | A1 |
| 20020190125 | Stockhammer | Dec 2002 | A1 |
| 20020194303 | Suila et al. | Dec 2002 | A1 |
| 20020194503 | Faith et al. | Dec 2002 | A1 |
| 20020196963 | Bardwell | Dec 2002 | A1 |
| 20030009382 | DArbelott et al. | Jan 2003 | A1 |
| 20030014307 | Heng | Jan 2003 | A1 |
| 20030014357 | Chrisekos et al. | Jan 2003 | A1 |
| 20030014891 | Nelms et al. | Jan 2003 | A1 |
| 20030018532 | Dudek et al. | Jan 2003 | A1 |
| 20030018567 | Flitcroft et al. | Jan 2003 | A1 |
| 20030025600 | Blanchard | Feb 2003 | A1 |
| 20030028481 | Flitcroft et al. | Feb 2003 | A1 |
| 20030046228 | Berney | Mar 2003 | A1 |
| 20030054836 | Michot | Mar 2003 | A1 |
| 20030055727 | Walker et al. | Mar 2003 | A1 |
| 20030057226 | Long | Mar 2003 | A1 |
| 20030057278 | Wong | Mar 2003 | A1 |
| 20030069828 | Blazey et al. | Apr 2003 | A1 |
| 20030069846 | Marcon | Apr 2003 | A1 |
| 20030112972 | Hattick et al. | Jun 2003 | A1 |
| 20030120554 | Hogan et al. | Jun 2003 | A1 |
| 20030121969 | Wankmueller | Jul 2003 | A1 |
| 20030130820 | Lane, III | Jul 2003 | A1 |
| 20030132284 | Reynolds et al. | Jul 2003 | A1 |
| 20030140228 | Binder | Jul 2003 | A1 |
| 20030163699 | Pailles et al. | Aug 2003 | A1 |
| 20030167207 | Berardi et al. | Sep 2003 | A1 |
| 20030177347 | Schneier et al. | Sep 2003 | A1 |
| 20030183689 | Swift et al. | Oct 2003 | A1 |
| 20030183699 | Masui | Oct 2003 | A1 |
| 20030187786 | Swift et al. | Oct 2003 | A1 |
| 20030187787 | Freund | Oct 2003 | A1 |
| 20030187790 | Swift et al. | Oct 2003 | A1 |
| 20030187796 | Swift et al. | Oct 2003 | A1 |
| 20030195037 | Vuong et al. | Oct 2003 | A1 |
| 20030195842 | Reece | Oct 2003 | A1 |
| 20030195843 | Matsuda et al. | Oct 2003 | A1 |
| 20030200184 | Dominguez et al. | Oct 2003 | A1 |
| 20030218066 | Fernandes et al. | Nov 2003 | A1 |
| 20030220876 | Burger et al. | Nov 2003 | A1 |
| 20030222153 | Pentz et al. | Dec 2003 | A1 |
| 20030225623 | Wankmueller | Dec 2003 | A1 |
| 20030225713 | Atkinson et al. | Dec 2003 | A1 |
| 20030227550 | Manico et al. | Dec 2003 | A1 |
| 20030233334 | Smith | Dec 2003 | A1 |
| 20040006539 | Royer et al. | Jan 2004 | A1 |
| 20040010462 | Moon et al. | Jan 2004 | A1 |
| 20040015451 | Sahota et al. | Jan 2004 | A1 |
| 20040016796 | Hann et al. | Jan 2004 | A1 |
| 20040020982 | Hoffman et al. | Feb 2004 | A1 |
| 20040029569 | Khan et al. | Feb 2004 | A1 |
| 20040030601 | Pond et al. | Feb 2004 | A1 |
| 20040039814 | Crabtree et al. | Feb 2004 | A1 |
| 20040039860 | Mills et al. | Feb 2004 | A1 |
| 20040044627 | Russell et al. | Mar 2004 | A1 |
| 20040083184 | Tsuei et al. | Apr 2004 | A1 |
| 20040139021 | Reed et al. | Jul 2004 | A1 |
| 20050017068 | Zalewski et al. | Jan 2005 | A1 |
| 20050038718 | Barnes et al. | Feb 2005 | A1 |
| 20050040272 | Argumedo et al. | Feb 2005 | A1 |
| 20050119978 | Ates | Jun 2005 | A1 |
| 20050121512 | Wankmueller | Jun 2005 | A1 |
| Number | Date | Country |
|---|---|---|
| 689070 | Aug 1998 | CH |
| 0 358 525 | Mar 1990 | EP |
| 0 424 726 | Oct 1990 | EP |
| 0 484 726 | May 1992 | EP |
| 0 933 717 | Aug 1999 | EP |
| 0 956 818 | Nov 1999 | EP |
| 0 959 440 | Nov 1999 | EP |
| 0 984 404 | Mar 2000 | EP |
| 1 016 947 | Jul 2000 | EP |
| 1 039 403 | Sep 2000 | EP |
| 1 104 909 | Jun 2001 | EP |
| 1 113 387 | Jul 2001 | EP |
| 1 115 095 | Jul 2001 | EP |
| 1 199 684 | Apr 2002 | EP |
| 1 251 450 | Oct 2002 | EP |
| 2347537 | Sep 2000 | GB |
| 2 361 790 | Oct 2001 | GB |
| 2000-1109 | Jan 2000 | JP |
| 2000-015288 | Jan 2000 | JP |
| 2000011109 | Jan 2000 | JP |
| 2000-40181 | Feb 2000 | JP |
| 2000-67312 | Mar 2000 | JP |
| 2000-207641 | Jul 2000 | JP |
| 2001-5931 | Jan 2001 | JP |
| 2001-283122 | Oct 2001 | JP |
| WO 9532919 | Dec 1995 | WO |
| 9709688 | Mar 1997 | WO |
| WO 9903057 | Jan 1999 | WO |
| 9949424 | Sep 1999 | WO |
| WO 0010144 | Feb 2000 | WO |
| WO 0038088 | Jun 2000 | WO |
| 0049586 | Aug 2000 | WO |
| WO 0104825 | Jan 2001 | WO |
| WO 0115098 | Mar 2001 | WO |
| WO 0143095 | Jun 2001 | WO |
| WO 0172224 | Oct 2001 | WO |
| WO 0177856 | Oct 2001 | WO |
| WO 0180473 | Oct 2001 | WO |
| WO 0186535 | Nov 2001 | WO |
| WO 0190962 | Nov 2001 | WO |
| WO 0195243 | Dec 2001 | WO |
| WO 0201485 | Jan 2002 | WO |
| WO 0213134 | Feb 2002 | WO |
| WO 0221903 | Mar 2002 | WO |
| WO 02063545 | Aug 2002 | WO |
| WO 02065246 | Aug 2002 | WO |
| WO 02065404 | Aug 2002 | WO |
| WO 02069221 | Sep 2002 | WO |
| WO 02073512 | Sep 2002 | WO |
| WO 02086665 | Oct 2002 | WO |
| WO 02091281 | Nov 2002 | WO |
| WO 02097575 | Dec 2002 | WO |
| WO 02101670 | Dec 2002 | WO |
| 03007623 | Jan 2003 | WO |
| Number | Date | Country | |
|---|---|---|---|
| 20050038741 A1 | Feb 2005 | US |
| Number | Date | Country | |
|---|---|---|---|
| 60304216 | Jul 2001 | US | |
| 60396577 | Jul 2002 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 10340352 | Jan 2003 | US |
| Child | 10710567 | US | |
| Parent | 10192488 | Jul 2002 | US |
| Child | 10340352 | US | |
| Parent | 10318432 | Dec 2002 | US |
| Child | 10192488 | US | |
| Parent | 10318480 | Dec 2002 | US |
| Child | 10318432 | US |
