Processing an RF transaction using a routing number

- Xatra Fund MX, LLC

A system and method for securing a Radio Frequency (RF) transaction using a RF identification device transaction device is provided. The invention uses the routing number and customer identifying information associated with a transaction account to secure a RF transaction. Specifically, the customer identifying information is included in an encrypted payload that is provided to a merchant point-of-sale device in a unused field of the RF data transmission. The routing number is provided in the ordinary field location of the data transmission typically reserved for the transaction account number. Additionally, the encrypted payload is provided in the unused field of the data transmission. The routing number is used to locate the corresponding encryption key for validating the RF transaction device, the transaction account and/or customer identifying information without the need for the reader to encrypt the customer identifying information before providing a transaction request to an account issuer.

Skip to: Description  ·  Claims  ·  References Cited  · Patent History  ·  Patent History
Description
CROSS-REFERENCE TO RELATED APPLICATIONS

This invention ('548 application) is a Continuation-in-Part of U.S. patent application Ser. No. 10/711,720, entitled “SYSTEMS AND METHODS FOR MANAGING MULTIPLE ACCOUNTS ON A RF TRANSACTION DEVICE USING SECONDARY IDENTIFICATION INDICIA,” filed Sep. 30, 2004. The '548 application is also a continuation-in-part of U.S. patent application Ser. No. 10/708,545, titled “SYSTEM AND METHOD FOR SECURING RF TRANSACTIONS USING A RADIO FREQUENCY IDENTIFICATION DEVICE INCLUDING A TRANSACTION COUNTER,” filed Mar. 10, 2004. Both the '720 and '545 applications are non-provisional's of U.S. Provisional Application No. 60/507,803, filed Sep. 30, 2003. The '548 application is also a continuation-in-part of U.S. patent application Ser. No. 10/340,352, entitled “SYSTEM AND METHOD FOR INCENTING PAYMENT USING RADIO FREQUENCY IDENTIFICATION IN CONTACT AND CONTACTLESS TRANSACTIONS,” filed Jan. 10, 2003. The '352 application is a non-provisional of U.S. Provisional Patent Application No. 60/396,577, filed Jul. 16, 2002. The '548 application is also a continuation-in-part of 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, and has now issued as U.S. Pat. No. 7,239,226 on Jul. 3, 2007. The '488 is a non-provisional of U.S. Provisional Patent Application No. 60/304,216, filed Jul. 10, 2001. All of the above-listed applications are incorporated herein by reference.

FIELD OF INVENTION

This invention generally relates to a system and method for securing a Radio Frequency (RF) transaction using a RF operable transaction device, and more particularly, to securing a RF transaction using a Radio Frequency Identification (RFID) device module including a transactions counter.

BACKGROUND OF INVENTION

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 portable devices identifiable by hand. For example, RFID modules are being placed in a fob or tag for use in completing financial transactions. A typical fob includes a RF transponder and is typically 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 a RF interrogation signal provided by a RF reader. 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. These are called “passive” RFID devices. Alternatively, the fob may have an internal power source such that interrogation by the reader to activate the fob is not required. These RFID devices are termed “active” RFID devices.

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, such as for example an “acquirer” or account issuer. Once the server receives authorization from the authorizing entity, the authorizing entity sends clearance to the point-of-sale device for completion of the transaction.

Minimizing fraud transactions in the RFID environment is typically important to the account issuer to lessen the loss associated with fraudulent RFID transaction device usage. One conventional method for securing RFID transactions involves requiring the device user to provide a secondary form of identification during transaction completion. For example, the RFID transaction device user may be asked to enter a personal identification number (PIN) into a keypad. The PIN may then be verified against a number associated with the user or the RFID transaction device, where the associated number is stored in an account issuer database. If the PIN number provided by the device user matches the associated number, then the transaction may be cleared for completion.

One problem with the conventional method of securing an RFID transaction is that the time for completing the transaction is increased. This is true since the RFID device user must delay the transaction to provide the alternate identification. The increased time for completing a transaction defeats one real advantage of the RFID transaction device, which is to permit expedient completion of a transaction since the account information may be passed to a reader without merchant involvement.

Another problem associated with conventional securing methods is that the customer identifying information (e.g., customer name, address, customer demographics, etc.) is susceptible to theft when transmitted from the RFID device to the RFID reader. Merchants often print the customer identifying information on a receipt for billing purposes. Alternatively, merchants store the customer identifying information for recordkeeping purposes, such as if the customer identifying information is needed to settle a transaction dispute. Typically, the merchant receives the customer identifying information from the RFID reader which receives the information from the RFID device as unencrypted data (“in-the-clear data”). The unencrypted data therefore may be intercepted by unscrupulous eavesdroppers bent on using the customer's identifying information for fraudulent purposes.

As such, a need exists for a method of securing a RFID transaction which does not increase the time needed to complete the transaction, and which method may be used without device user intervention. A further need exists for a system that secures customer identifying information transmitted in-the-clear.

SUMMARY OF INVENTION

Described herein is a system and method for securing RFID transactions which addresses the problems found in conventional transaction securing methods. The securing method described includes verifying a RFID transaction device counter, which may generate an indicia corresponding to the number of transactions conducted using a particular RFID transaction device. The method involves variously validating a RFID device authentication tag and a RFID reader authentication tag. The method further involves placing the routing number associated with a transaction account in the transmission data field typically reserved for the transaction account number, and placing encrypted card information (e.g., card number and/or expiration date) in an alternate unused field of a transaction request. One implementation will be to use the unused 16 characters at positions 64-79 of the Track 1 format as defined in ISO7813. The encrypted card information is decrypted at the issuer location using a decryption key correlated to the routing number transmitted in the transaction account number field.

In one exemplary embodiment, the invention discloses a system and method for verifying a RFID transaction device and RFID reader operable with a RF transaction system. The method involves presenting a RFID transaction system to a RFID reader, receiving a random number from the RFID reader, creating a RFID transaction device authentication tag using the random number and a counter value, providing the random number, counter value, and RFID transaction device authentication tag to a RFID reader, creating a RFID reader authentication tag using the counter random number, and/or RFID transaction device authentication tag, and providing the RFID reader and RFID transaction device for authentication.

Under a second embodiment, the invention involves verifying the RFID transaction device only. Still under another embodiment, the invention involves verifying the RFID reader without verifying the RFID transaction device.

In yet another embodiment of the invention, the method involves using the data transmission fields to secure a RF transmission. In general, the invention includes placing the routing number in the data transmission field typically reserved for the transaction account number, and forwarding the routing number and an encrypted transaction account number and expiration date to the RFID reader. The RFID reader then places the encrypted account number and expiration date in the data transmission field typically reserved for unused data, such as, for example, positions 64-79 of the 7813 Track 1 format, and forwards the data transmission to the merchant system. The merchant system receives the data transmission and forwards a transaction request to the transaction account issuer for transaction settlement. The account issuer may receive the transaction request and locate a transaction account decryption key useful for decrypting the information stored in the unused field, decrypt the transaction account information, and process the transaction request under issuer-defined business as usual standards.

In still another embodiment, the method involves using the data transmission fields to secure a RF transmission by placing the routing number in the data transmission field typically reserved for the transaction account number, and forwarding the routing number and an encrypted transaction account number, expiration date and customer identifying information to the RFID reader. The RFID reader then places the encrypted account number, expiration date, and customer identifying information in the data transmission field typically reserved for unused data and forwards the data transmission to the merchant system. The merchant system receives the data transmission and forwards a transaction request to the transaction account issuer for transaction settlement. The account issuer may receive the transaction request and locate a transaction account decryption key useful for decrypting the information stored in the unused field, decrypt the transaction account information, and process the transaction request under issuer-defined business as usual standards. The issuer may then forward the decrypted customer information to the merchant system for use in billing or record keeping.

These features and other advantages of the system and method, as well as the structure and operation of various exemplary embodiments of the system and method, are described below.

BRIEF DESCRIPTION OF THE DRAWINGS

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:

FIG. 1 illustrates an exemplary RFID-based system depicting exemplary components for use in RFID transaction completion in accordance with the present invention;

FIG. 2 illustrates an exemplary method for securing a RFID transaction using a counter-generated indicia in accordance with the present invention;

FIG. 3 depicts a flow diagram of an exemplary RFID transaction device and RFID reader authentication flow chart useful with this invention;

FIG. 4 depicts a flow diagram of an exemplary RFID transaction device authentication flow diagram useful with this invention;

FIG. 5 depicts a flow diagram of an exemplary RFID reader authentication flow diagram useful with this invention;

FIG. 6 depicts a flow diagram of an exemplary RFID transaction securing method using a transaction account routing number useful with this invention; and

FIG. 7 depicts a flow diagram of an exemplary RFID transaction securing method using a transaction account routing number and customer identifying information useful with this invention.

 DETAILED DESCRIPTION

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 is noted that the network may be implemented as other types of networks, such as an interactive television network (ITN).

Further still, the terms “Internet” or “network” may refer to the Internet, any replacement, competitor or successor to the Internet, or any public or private inter-network, intranet or extranet that is based upon open or proprietary protocols. Specific information related to the protocols, standards, and application software utilized in connection with the Internet may not be discussed herein. For further information regarding such details, see, for example, Dilip Naik, “Internet Standards and Protocols” (1998); “Java 2 Complete,” various authors, (Sybex 1999); Deborah Ray and Eric Ray, “Mastering HTML 4.0” (1997); Loshin, “TCP/IP Clearly Explained” (1997). All of these texts are hereby incorporated by reference.

By communicating, a signal may travel to/from one component to another. The components may be directly connected to each other or may be connected through one or more other devices or components. The various coupling components for the devices can include but are not limited to the Internet, a wireless network, a conventional wire cable, an optical cable or connection through air, water, or any other medium that conducts signals, and any other coupling device or medium.

Where required, the system user may interact with the system via any input device such as, a keypad, keyboard, mouse, kiosk, personal digital assistant, handheld computer (e.g., Palm Pilot®, Blackberry®), 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.

A variety of conventional communications media and protocols may be used for data links providing physical connections between the various system components. For example, the data links may be an Internet Service Provider (ISP) configured to facilitate communications over a local loop as is typically used in connection with standard modem communication, cable modem, dish networks, ISDN, Digital Subscriber Lines (DSL), or any wireless communication media. In addition, the merchant system, including a POS device and a host network, may reside on a local area network which interfaces to a remote network (not shown) for remote authorization of an intended transaction. The POS may communicate with the remote network via a leased line, such as a T1, D3 line, or the like. Such communications lines are described in a variety of texts, such as, “Understanding Data Communications,” by Gilbert Held, which is incorporated herein by reference.

A transaction device identifier, as used herein, may include any identifier for a transaction device which may be correlated to a user transaction account (e.g., credit, charge debit, checking, savings, reward, loyalty, or the like) maintained by a transaction account provider (e.g., payment authorization center). A typical transaction account identifier (e.g., account number) may be correlated to a credit or debit account, loyalty account, or rewards account maintained and serviced by such entities as American Express, Visa and/or MasterCard, or the like.

To facilitate understanding, the present invention may be described with respect to a credit account. However, it should be noted that the invention is not so limited and other accounts permitting an exchange of goods and services for an account data value is contemplated to be within the scope of the present invention.

A transaction device identifier (e.g., 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. These first five to seven digits may be termed the “routing number” herein. The routing number may typically be included in the account number for use in indicating the transaction completion transmission route corresponding to an account issuer, funding source, or the like. Typically, the routing number may not be used for payment. In this example, the last sixteenth digit is used as a sum check for the sixteen-digit number. The intermediary eight-to-ten digits are used to uniquely identify the customer. The account number is stored as Track 1 and Track 2 data as defined in ISO/IEC 7813, and further may be made unique to the RFID transaction device.

In one exemplary embodiment, the transaction device identifier may include a unique RFID transaction device serial number and user identification number, as well as specific application applets. The transaction device identifier may be stored on a transaction device database located on the transaction device. The transaction device database may be configured to store multiple account numbers issued to the RFID transaction device user by the same or different account providing institutions. In addition, where the device identifier corresponds to a loyalty or rewards account, the RFID transaction device database may be configured to store the attendant loyalty or rewards points data.

In addition to the above, the transaction device identifier may be associated with any secondary form of identification configured to allow the consumer to interact or communicate with a payment system. For example, the transaction device identifier may be associated with, for example, an authorization/access code, personal identification number (PIN), Internet code, digital certificate, biometric data, and/or other secondary identification data used to verify a transaction device user identity.

It should be further noted that conventional components of RFID transaction devices may not be discussed herein for brevity. For instance, one skilled in the art will appreciate that the RFID transaction device and the RFID reader disclosed herein include traditional transponders for transmitting information between the device and the reader, antennas for facilitating RF data transmission, protocol sequence controllers or microprocessors for controlling the operation of the device or reader components, modulators/demodulators and the like for conditioning a RF data transmission to be read by the reader or device, which may be necessary for proper RFID data transmission. As such, those components are contemplated to be included in the scope of the invention.

It should be noted that the transfer of information in accordance with this invention, may be done in a format recognizable by a merchant system or account issuer. In that regard, by way of example, the information may be transmitted from the RFID device to the RFID reader, or from the RFID reader to the merchant system in magnetic stripe or multi-track magnetic stripe format. Because of the proliferation of devices using magnetic stripe format, the standards for coding information in magnetic stripe format were standardized by the International Standards Organization (ISO), which standards are incorporated herein by reference.

Typically, magnetic stripe information is formatted in three tracks. Certain industry information must be maintained on certain portion of the tracks, while other portions of the tracks may have open data fields. The contents of each track and the formatting of the information provided to each track is controlled by ISO standard ISO/IEC 7811. For example, the information must typically be encoded in binary. Track 1 is usually encoded with user information (name) in alphanumeric format. Track 2 is typically comprised of discretionary and nondiscretionary data fields. In one example, the nondiscretionary field may comprise 19 characters and the discretionary field may comprise 13 characters. Track 3 is typically reserved for financial transactions and includes enciphered versions of the user's personal identification number, country code, current units amount authorized per cycle, subsidiary accounts, and restrictions.

As such, where information is provided in accordance with this invention, it may be provided in magnetic stripe format track. For example, the counter values, authentication tags and encrypted identifiers, described herein, may be forwarded encoded in all or a portion of a data stream representing data encoded in, for example, track 2 or track 3 format.

Further still, various components may be described herein in terms of their “validity.” In this context, a “valid” component is one which is authorized for use in completing a transaction request in accordance with the present invention. Contrarily, an “invalid” component is one which is not authorized for transaction completion. In addition, an invalid component may be one which is not recognized as being permitted for use on the secure RF system described herein.

FIG. 1 illustrates an exemplary secure RFID transaction system 100 in accordance with the present invention, wherein exemplary components for use in completing a RF transaction are depicted. In general, system 100 may include a RFID transaction device 102 in RF communication with a RFID reader 104 for transmitting data there between. RFID reader 104 may be in further communication with a merchant point-of-sale (POS) device 106 for providing to POS 106 data received from RFID transaction device 102. POS 106 may be in further communication with an acquirer 110 or an account issuer system 112 via a network 108 for transmitting a transaction request, including information received from RFID reader 104, and receiving authorization concerning transaction completion.

Although point-of-interaction device (POS 106) is described herein with respect to a merchant point-of-sale (POS) device, the invention is not to be so limited. Indeed, a merchant POS device is used herein by way of example, and the point-of-interaction device may be any device capable of receiving transaction device account data. In this regard, the POS may be any point-of-interaction device enabling the user to complete a transaction using transaction device 102. POS device 106 may receive RFID transaction device 102 information and provide the information to host network 108 for processing. In one exemplary embodiment, POS device 106 may receive the transaction device information in ISO/IEC 8583 message format from RFID reader 104.

As used herein, an “acquirer” may be a third-party entity including various databases and processors for facilitating the routing of the transaction request to an appropriate account issuer system 112. Acquirer 112 may route the request to the account issuer in accordance with a routing number provided by RFID transaction device 102. The “routing number” in this context may be a unique network address or any similar device for locating account issuer system 112 on network 108. Traditional means of routing the payment request in accordance with the routing number are well understood. As such, the process for using a routing number to provide the payment request will not be discussed herein for brevity.

Additionally, account issuer system 112 (“account provider”) may be any entity which provides a transaction account for facilitating completion of a transaction request. The transaction account may be any credit, debit, loyalty, direct debit, checking, or savings, or the like. The term “issuer” or “account provider” may refer to any entity facilitating payment of a transaction using a transaction device, and which includes systems permitting payment using at least one of a preloaded and non-preloaded transaction device. Typical issuers may be American Express, MasterCard, Visa, Discover, and the like. In the preloaded value processing context, an exchange value (e.g., money, rewards points, barter points, etc.) may be stored in a preloaded value database (not shown) for use in completing a requested transaction. The preloaded value database and thus the exchange value may not be stored on the transaction device itself, but may be stored remotely, such as, for example, at account issuer system 112 location. Further, the preloaded value database may be debited the amount of the transaction requiring the value to be replenished. The preloaded value may be any conventional value (e.g., monetary, rewards points, barter points, etc.) which may be exchanged for goods or services. In that regard, the preloaded value may have any configuration as determined by issuer system 112.

RFID transaction device 102 may include a database 116 for storing transaction device information including the transaction device account number, customer identification, transaction device encryption and security keys, etc. The merchant database locations maintained on database 116 by server 110 are provided a distinct merchant identifier. Database discussed herein may be a graphical, hierarchical, relational, object-oriented or other database. In one embodiment, databases disclosed are a collection of ASCII or other text files. In another embodiment data is stored in a hierarchical file structure conforming to ISO 7816 file structure standards. Database information is suitably retrieved from the database and provided to transaction processing systems upon request via a server application, as described more fully below.

The database 116 may be in communication with a transaction device microprocessor 114 (e.g., protocol sequence controller) for use in controlling the operation of the internal circuits of RFID transaction device 102. The protocol sequence controller 114 may be in communication with a RFID transaction device counter 118. Counter 118 may be useful for tracking the number of transactions completed by a particular device 102, as described below. Microprocessor 114 facilitates the counting of the transactions by facilitating the incrementing of the counter 118 each occurrence of device 102 usage. The RFID device 102 may further include a transponder (not shown) for use in receiving RF data and configuring the data to be readable by the device 102 circuitry.

In general, during operation of secure system 100, RFID reader 104 may provide an interrogation signal to transaction device 102 for powering device 102 and receiving transaction device related data. The interrogation signal may be received at transaction device antenna 120 and may be received at a RFID transaction device transponder (not shown), which provides the interrogation signal to processor 114. In response, transaction device processor 114 may retrieve a transaction device identifier from transaction device database 116 for providing to RFID reader 104 to complete a transaction request. Typically, the transaction device identifier may be encrypted prior to providing the device identifier to RFID reader 104.

It should be noted that RFID reader 104 and RFID transaction device 102 may engage in mutual authentication prior to transferring any transaction device 102 data to RFID reader 104. For a detailed explanation of a suitable mutual authentication process for use with the invention, please refer to commonly owned U.S. patent application Ser. No. 10/340,352, entitled “System and Method for Incenting Payment Using Radio Frequency Identification in Contact and Contactless Transactions,” filed Jan. 10, 2003, incorporated by reference in its entirety.

In accordance with one embodiment of the present invention, a RF transaction using a RFID transaction device is secured by limiting the number of transactions which may be performed with a particular transaction device. Once the maximum transactions value is reached, the transaction device may automatically disable itself against further usage. Alternatively, account issuer system 112 may flag the transaction account correlating to the transaction device such that the account issuer system automatically prevents completion of transactions using the transaction device

As such, RFID transaction device 102 in accordance with the present invention further includes a counter 118 for recording and reporting the number of transactions performed with a particular transaction device 102. Counter 118 may be any device capable of being initiated with a beginning value and incrementing that value by a predetermined amount when the transaction device is presented for completion of a transaction. Counter 118 may be a discrete electronic device on the transponder, or may be a software or code-based counter as is found in the art.

The initial counter value may be any value from which other similar values may be measured. The value may take any form, such as, alpha, numeric, a formation of symbols, or any combination thereof.

To facilitate understanding, the following description discusses all values to be in numeric units (0, 1, 2, 3 . . . n). Thus, the counter values, the value amount to be incremented, the total transactions counted value, and the maximum transactions value, are all whole numbers.

It should be noted that account issuer system 112 may preset the initial counter value at any initial value as desired. Account issuer system 112 may also predetermine the value amount to be incremented by counter 118 when the transaction device is used to complete a transaction. Further, account issuer system 112 may assign different values to be incremented for each distinct transaction device 102. Further still, account issuer system 112 may determine the maximum transactions value, which may be particular to each individual transaction device 102 issued by account issuer system 112. Where counter 118 value equals a maximum transactions value, the system 100 prevents the usage of the transaction device 102 to complete additional transactions. Account issuer system 112 may prevent the usage of the transaction device 102 where the account issuer flags the transaction account corresponding to the transaction device 102, thereby preventing authorization for using the account to complete transactions. Alternatively, the transaction device 102 may self-disable. For example, counter 118 value may trigger the transaction device processor 114 to provide a signal for preventing the transfer of the transaction device 102 identifier.

For example, account issuer system 112 may preset the initial counter value at 5 units and the counter value to be incremented at 10 units per transaction. Account issuer system 112 may determine that transaction device 102 may be used to complete a total transaction value of 20 transactions. Since counter 118 increments the counter value by the value to be incremented (e.g., 10 units) for each transaction, then for a total of 20 transactions permitted, the maximum transactions value will be 205 units. Once the counter value equals 205 units, then the operation of the transaction device 102 is disabled.

The operation of the exemplary embodiment described above, may be understood with reference to FIG. 1 and to the method of securing a RFID transaction described in FIG. 2. The operation may begin when RFID transaction device 102 is presented for completion of a transaction. Transaction device 102 may be placed in an interrogation field generated by RFID reader 104 (step 202). RFID reader 104 may interrogate RFID transaction device 102 enabling transaction device 102 operation. In response, RFID transaction device 102 may retrieve the transaction device 102 identifier, account issuer system 112 routing number and encrypted transaction device identifier from database 116 for providing to RFID reader 104 (step 204).

Once RFID transaction device 102 detects the interrogation signal provided by RFID reader 104, counter 118 may increment its counter value (step 206). Counter 118 value may be incremented by an amount predetermined by account issuer system 112 (e.g., value amount to be incremented). The resulting counter 118 value after incrementing is the total transactions counted value.

Upon determining the total transactions counted value, RFID transaction device 102 may provide the total transactions counted value, the encrypted transaction device 102 identifier, and account issuer system 112 routing number to RFID reader 104 via RF transmission (step 208). RFID reader 104 may, in turn, convert the transaction device 102 identifier, routing number, and total transactions counted value into merchant POS recognizable format and forward the converted information to merchant POS 106 (step 210). The merchant system including POS 106 may then provide a transaction request to an acquirer 110 via network 106. The transaction request may include the information received from the transaction device 102 along with information (e.g., amount, number of product, product/service identifier) concerning the transaction requested to be completed (step 216). The transaction request may include information relative to RFID reader 104.

Acquirer 110 may receive the transaction request and forward the transaction request to the appropriate account issuer system 112 in accordance with the routing number provided (step 218). The account issuer may then identify that a transaction request is being provided that relates to a transaction device. For example, merchant POS 106 may provide a code appended to the transaction request specially configured for identifying a transaction device transaction which may be recognized by account issuer system 112. Alternatively, the transaction device identifier, or a portion thereof, may be identified by account issuer system 112 as originating with a RFID transaction device 102.

In one exemplary embodiment, account issuer system 112 receives the transaction device 102 identifier and checks to see if the transaction device identifier corresponds to a valid transaction account maintained on account issuer system 112 (step 220). For example, account issuer system 112 may receive the encrypted transaction device identifier and locate the corresponding decryption key relating to the transaction account. If the encrypted ID is invalid, such as, for example, when account issuer system 112 is unable to locate the corresponding decryption key, account issuer system 112 may provide a “Transaction Invalid” message to POS 106 (step 228). Transaction device 102 user may then be permitted to provide an alternate means of satisfying the transaction, or the transaction is ended (step 230).

If the RFID transaction device encrypted identifier corresponding decryption key is located, the encrypted identifier is considered “valid” and account issuer system 112 may then use the corresponding decryption key to “unlock” or locate the transaction device account correlative to the transaction device 102. Account issuer system 112 may then retrieve all information relating to the usage limits which have been predetermined by account issuer system 112. Account issuer system 112 may be able to determine if a particular transaction device 102 has reached its limit of available transactions.

For example, account issuer system 112 may check to see if the total transactions counted value equals or exceeds the maximum transactions allowed (step 224). If the maximum transactions allowed have been reached then the counter value is met or exceeded, and the transaction is considered “invalid.” As such, account issuer system 112 may then provide a “Transaction Invalid” message to POS 106 (step 228). In addition, account issuer system 112 may determine whether the total transactions counted value is the next expected value. If not, then the transaction is considered “invalid” and account issuer system 112 may also provide a “Transaction Invalid” message to POS 106 (step 228). Transaction device 102 user may then be permitted to provide alternate means of completing the transaction (step 226) or the transaction is ended.

Alternatively, where the total transactions counted value does not exceed or meet the maximum transactions allowed value, the counter value is considered valid and a “Transaction Valid” message is sent to merchant POS 106 (step 230). The merchant may then complete the transaction under business as usual standards as are employed by the merchant.

In accordance with the various embodiments described, the present invention addresses the problem of securing a RF transaction completed by a RFID transaction device. The invention provides a system and method for an account issuer to determine if a RFID transaction device is a valid device for completing a transaction on a RF transaction system. The account issuer can determine whether the transaction device is valid by verifying the transaction device counter, and encryption identifier. It should be noted, however, that the present invention contemplates various arrangements wherein the RFID reader may also be validated.

FIG. 3 illustrates another method 300 for usage of the RFID transaction device counter 118 value for securing a RF transaction. In accordance with the method depicted, RFID reader 104 includes a random number generator 120, for producing a random number to be used in the secure transactions. Random number generator 120 may be in communication with a RFID reader microprocessor 122, which may provide the generated random number to RFID transaction device 102 during transaction processing. Random number generator 120 may be any conventional random number generator as is found in the art.

Method 300 may begin when a user presents RFID transaction device 102 for transaction completion (step 302). The user may, for example, place RFID transaction device 102 into the interrogation zone provided by a RFID reader 104. The interrogation zone may be the area or zone defined by the interrogation signal cast by RFID reader 104.

Upon presentment of the transaction device 102, RFID reader 104 may provide the random number to RFID transaction device 102. RFID transaction device 102 may receive the random number and use it to create a RFID transaction device authentication tag (step 306). RFID transaction device 102 may receive the random number and use the random number, the counter value, transaction account number and the RFID transaction device encryption key to create a RFID transaction device authentication tag.

RFID transaction device 102 may provide the RFID transaction device authentication tag to RFID reader 104. RFID transaction device 102 may also provide in-the-clear data, the counter value, random number to RFID reader 104, along with the RFID transaction device authentication tag (step 308). RFID transaction device processor 114 may increment counter 118 using any of the incrementing methods discussed above (step 310).

RFID reader 104 may receive the data provided by RFID reader 104, and use the data to create a RFID reader authentication key using a RFID reader encryption key (step 312). RFID reader 104 may convert the in-the-clear data, random number, counter value, RFID transaction device authentication tag, and RFID reader authentication tag into a format readable by POS 106 (step 314) and provide the converted data to POS 106 (step 316).

POS 106 may seek satisfaction of the transaction (step 318). For example, POS 106 may form a transaction request using the data received from RFID transaction device 102, and RFID reader 104 encryption key and forward the transaction request to an acquirer 110 who may forward the transaction request to an account issuer system 112 using the routing number.

Account issuer system 112 may receive the transaction request and verify that RFID reader 104 and RFID transmission device 102 are valid. Account issuer system 112 may validate the RFID reader authentication tag by decrypting the RFID reader authentication tag using a RFID reader encryption key stored on an account issuer database (not shown) (step 320). If the decryption is unsuccessful, then issuer system 112 may provide a “Transaction Invalid” message to POS 106 (step 322) and the transaction is terminated. Alternatively, if decryption is successful, issuer system 112 may seek to validate the RFID transaction device authentication tag (step 332).

For example, account issuer system 112 may use the RF transaction device account number to locate a RFID transaction device encryption key stored on issuer system 112 database (step 324) and use the RFID transaction device encryption key to decrypt the RFID transaction device authentication tag (step 326). If decryption is unsuccessful then issuer system 112 provides a “Transaction Invalid” message to POS 106 (step 322) and the transaction is terminated. Alternatively, if the decryption is successful, then issuer system 112 may validate the counter value (step 328). Issuer system 112 may compare the counter value to an expected counter value. In another exemplary embodiment, issuer system 112 may subject the counter value received from RFID transaction device 102 to an algorithm the results of which are validated against an expected counter value.

If the counter value is unsuccessfully validated, then issuer system 112 may provide a “Transaction Invalid” message to POS 106. Otherwise, issuer system 112 may process the RFID transaction account number under business as usual standards (step 330). In this way, the transaction is secured using a counter, by using the counter to validate a RFID transaction device authentication tag and a RFID reader authentication tag.

FIG. 4 illustrates another exemplary embodiment of the present invention wherein RFID transaction device 102 is validated using the counter value. In this exemplary embodiment, RFID transaction device 102 is presented (step 302) and RFID reader 104 sends a random number to RFID transaction device 102 (step 304). RFID transaction device 102 receives the random number and creates a RFID transaction device authentication tag using the random number, the in-the-clear data, and a counter value (step 306). RFID transaction device 102 may then provide the RFID transaction device authentication tag, random number, counter value, and in-the-clear data to RFID reader 104 (step 308). RFID transaction device 102 may increment the counter value by a predetermined value (step 310).

RFID reader 104 may receive the RFID transaction device authentication tag, in-the-clear data and counter value and convert the counter value, in-the-clear data and RFID transaction device authentication tag to a merchant POS 106 format (step 414). Merchant POS 106 may then provide the data received from RFID reader 104 to an issuer system 112 (step 316) for transaction satisfaction (step 318). Issuer system 112 may receive the data and verify the RFID transaction device authentication (step 332). For example, issuer system 112 may validate the RFID transaction authentication tag and the counter value in accordance with steps 324-330.

Under yet another embodiment, FIG. 5 illustrates an aspect of the invention wherein RFID reader 104 is validated, when RFID transaction device 102 is not. According to the invention RFID transaction device 102 is validated using the counter value. In this exemplary embodiment, RFID transaction device 102 is presented for transaction completion as described before (step 302). RFID transaction device 102 may then provide the counter and the in-the-clear data to RFID reader 104 (step 508). RFID transaction device 102 may increment the counter value by a predetermined value (step 310).

RFID reader 104 may receive the in-the-clear data and the counter value and prepare RFID reader authentication tag using a RFID reader encryption key (step 512). RFID reader 104 may then convert the in-the-clear data and RFID reader authentication tag to a merchant POS 106 format (step 514). Merchant POS 106 may then provide the data received from RFID reader 104 to an issuer system 112 for transaction satisfaction (step 318). In one exemplary embodiment, merchant POS 106 may provide issuer system 112 with a POS identifier associated with POS 106. Issuer system 112 may receive the POS identifier, and locate a related POS encryption key stored on an issuer system database (not shown). Issuer system 112 may receive the data and verify the RFID transaction device authentication (step 532). For example, issuer system 112 may validate the RFID transaction authentication tag and the counter value in accordance with steps 524-530, in similar manner as is described with respect to steps 324-330 above.

In yet another exemplary embodiment, the counter value is used in conjunction with a routing number to secure a RFID transaction. RFID transaction device 102 provides the routing number to POS 106 which may use the routing number to authenticate (e.g., validate) RFID transaction device 102 and/or decrypt an encrypted transaction account data. Under this method, and undetected by POS 106, the transaction device account number and expiration date (e.g., payload) is encrypted and placed in the unused field of the message provided by RFID reader 104 to POS 106. Issuer system 112 may receive the routing number and the encrypted transaction account data (e.g., transaction account number and expiration date), and use the routing number to validate the transaction device 102, or account number.

FIG. 6 depicts an exemplary method 600 for using the counter value, routing number and encrypted payload to secure a RFID transaction. RFID transaction device 102 may be presented to a RFID reader 104 for transaction completion (step 302), and RFID reader 104 may send a random number to RFID transaction device 102 (step 304). RFID transaction device 102 may receive the random number and retrieve the transaction account number and expiration date (e.g., payload data) associated with RFID transaction device 102, and the routing number associated with the payload data (step 615). RFID transaction device 102 may encrypt the payload (step 617) and create a RFID transaction device authentication tag using the random number, routing number associated with the transaction account number, the counter value, and encrypted payload data (step 606). RFID transaction device 102 may form a RFID transaction device data message including the RFID transaction device authentication tag, counter value, encrypted payload and routing number (step 619). RFID transaction device 102 may place the routing number in a location typically recognizable by POS 106 as the transaction account number (step 621). In this way, POS 106 is unaware that the data received in the ordinary transaction number field of the data message is a routing number. Additionally, RFID transaction device 102 may place the encrypted payload in the unused field of the RFID transaction device data message (step 623). RFID transaction device 102 may provide the data message to RFID reader 104 in the format discussed above (step 625), and RFID reader 104 may provide the data message to POS 106 in any POS recognizable format (step 614). RFID transaction device 102 may then increment the counter value (step 610). The merchant may then seek transaction satisfaction by forwarding the transaction to issuer system 112, for example (step 318).

RFID transaction device 102 may be validated (step 632) by validating the RFID transaction device authentication tag, counter value or the like. For example, issuer system 112 may seek to validate the RFID transaction device authentication tag. Issuer system 112 may, for example, use the routing number to locate a corresponding RFID transaction device authentication tag decryption key stored on issuer system 112 database and use the RFID transaction device decryption key to decrypt the RFID transaction device authentication tag (step 624). If decryption is unsuccessful (step 326) then issuer system 112 provides a “Transaction Invalid” message to POS 106 (step 322) and the transaction is terminated. Alternatively, if the decryption is successful (step 326), then issuer system 112 may validate the counter value (step 328). Issuer system 112 may compare the counter value to an expected counter value. In another exemplary embodiment, issuer system 112 may subject the counter value received from RFID transaction device 102 to an algorithm the results of which are validated against an expected counter value.

If the counter value is unsuccessfully validated, then issuer system 112 may provide a “Transaction Invalid” message to POS 106 (step 322). Otherwise, issuer system 112 may process the RFID transaction account number under business as usual standards. In an alternate embodiment, upon validating the counter value and the RFID transaction device authentication tag, issuer system 112 may use the routing number to locate a decryption key for decrypting the encrypted payload (e.g., “payload encryption key”) and decrypt the payload accordingly (step 630). Alternatively, the payload encryption key and the RFID authentication tag encryption key may be identical, substantially the same key, or different keys entirely.

Notably, since the routing number may be defined as the card number in the data transmitted from the RFID reader 104 to POS 106, the issuing system 112 may readily use the routing number to locate appropriate decryption keys. In this way, the transaction is secured using a counter, by using the counter to validate a RFID transaction device authentication tag and a RFID reader authentication tag.

FIG. 7 depicts yet another method 700 for securing a RF transaction wherein the customer identifying information (called “customer data” herein) is encrypted and provided in the data transmission field, and in one embodiment, in the portion of the data transmission field typically reserved for unused information. In a similar manner as is described with respect to FIG. 6, the routing number associated with a particular transaction account is placed in the data transmission field typically reserved for the transaction account number. Merchant POS 106 may be unaware of the content of the information stored in the transaction account and unused fields, such that the merchant system processes the transaction request as if the fields contained the information typically stored therein.

Operation of method 700 may be understood with reference to FIG. 7 and continued reference to FIGS. 1 and 6. Namely, method 700 may begin with RFID transaction device 102 being presented to a RFID reader 104 for transaction completion (step 302), and RFID reader 104 may send a random number to RFID transaction device 102 (step 304). RFID transaction device 104 may receive the random number and retrieve the transaction account number, expiration date (e.g., payload data), the customer identifying information (e.g., customer name) associated with RFID transaction device 102, and the routing number associated with the payload data (step 715). In this exemplary embodiment, the “payload data” is described as including the customer identification information. RFID transaction device 102 may encrypt the payload data (step 717) and create a RFID transaction device authentication tag using the random number, routing number associated with the transaction account number, the counter value, and encrypted payload data (step 606). RFID transaction device 102 may form a RFID transaction device data message including the RFID transaction device authentication tag, counter value, encrypted payload and routing number (step 619). RFID transaction device 102 may place the routing number in a location typically recognizable by POS 106 as the transaction account number (step 621). In this way, POS 106 may be unaware that the data received in the ordinary transaction number field of the data message is a routing number. Additionally, RFID transaction device 102 may place the encrypted payload in the unused field of the RFID transaction device data message (step 623). RFID transaction device 102 may provide the data message to RFID reader 104 in the format discussed above (step 625), and RFID reader 104 may provide the data message to POS 106 in any POS recognizable format (step 614). RFID transaction device 102 may then increment the counter value (step 610). The merchant may then seek transaction satisfaction by forwarding the transaction to issuer system 112, for example (step 318).

RFID transaction device 102 may be validated (step 732) by validating the RFID transaction device authentication tag, counter value or the like. For example, issuer system 112 may seek to validate the RFID transaction device authentication tag. Issuer system 112 may, for example, use the routing number to locate a corresponding RFID transaction device authentication tag decryption key stored on issuer system 112 database and use the RFID transaction device decryption key to decrypt the RFID transaction device authentication tag (step 724). If decryption is unsuccessful (step 326), then issuer system 112 provides a “Transaction Invalid” message to POS 106 (step 322) and the transaction is terminated. Alternatively, if the decryption is successful (step 326), then issuer system 112 may validate the counter value (step 328). Issuer system 112 may compare the counter value to an expected counter value. In another exemplary embodiment, issuer system 112 may subject the counter value received from RFID transaction device 102 to an algorithm the results of which are validated against an expected counter value.

If the counter value is unsuccessfully validated, then issuer system 112 may provide a “Transaction Invalid” message to POS 106 (step 322). Otherwise, issuer system 112 may send a “Transaction Valid” message to the merchant system and process the RFID transaction account number under business as usual standards. In an alternate embodiment, upon validating the counter value and the RFID transaction device authentication tag, issuer system 112 may locate a decryption key for use in decrypting the payload. For example, the issuer system 112 may use the routing number to locate a payload decryption key for decrypting the encrypted payload (e.g., “payload encryption key”) and decrypt the payload accordingly (step 630). Alternatively, the payload encryption key and the RFID authentication tag encryption key may be identical, substantially the same key, or different keys entirely.

Upon locating the appropriate decryption key, and successfully decrypting the transaction account authentication tag, issuer system 112 may retrieve the customer identifying information from the payload, and provide the customer identifying information to the merchant with the “Transaction valid” message (step 730). The customer identifying information may be provided to the merchant in an unencrypted format or in an encrypted format decrypt-able by the merchant system. The merchant may then use the customer identifying information to fulfill its billing and recordkeeping purposes.

As previously noted, since the routing number may be defined as the card number in the data transmitted from the RFID reader 104 to POS 106, the issuing system 112 may readily use the routing number to locate appropriate decryption keys (step 624). In this way, the transaction is secured by placing the customer identifying information in the unused field of the RF data transmission.

The preceding detailed description of exemplary embodiments of the invention makes reference to the accompanying drawings, which show the exemplary embodiment by way of illustration. While these exemplary embodiments are described in sufficient detail to enable those skilled in the art to practice the invention, it should be understood that other embodiments may be realized and that logical and mechanical changes may be made without departing from the spirit and scope of the invention. For example, the RFID reader may include an RFID reader encrypted identifier stored in the reader database, which may be validated by the account issuer in similar manner as with the transaction device encrypted identifier. Moreover, the counter may increment the total transactions counted value by the predetermined incremental value at the completion of a successful transaction. In addition, the steps recited in any of the method or process claims may be executed in any order and are not limited to the order presented. Further, the present invention may be practiced using one or more servers, as necessary. Thus, the preceding detailed description is presented for purposes of illustration only and not of limitation, and the scope of the invention is defined by the preceding description, and with respect to the attached claims.

Claims

1. A method, comprising:

creating an encrypted authentication tag using a random number and at least one of a transaction account code, a routing number, or a counter value; and
transmitting the encrypted authentication tag and the routing number to a radio frequency identification (RFID) reader using a data transmission format comprising an account code field and an unallocated field,
wherein the encrypted authentication tag is transmitted in the unallocated field of the data transmission format.

2. The method of claim 1, further comprising receiving the random number from the RFID reader.

3. The method of claim 2, further comprising transmitting an RFID reader authentication code to the RFID reader and receiving an encrypted RFID reader authentication code from the RFID reader.

4. The method of claim 3, further comprising verifying the encrypted RFID reader authentication code for authentication of the RFID reader.

5. The method of claim 1, wherein the encrypted authentication tag is created using the routing number.

6. The method of claim 1, further comprising incrementing the counter value by at least one of a random amount or a predetermined amount.

7. The method of claim 1, wherein the routing number is transmitted in a transaction account field.

8. The method of claim 7, wherein the transaction account field is a primary account number (PAN) field as defined by ISO 8583.

9. The method of claim 7, further comprising:

creating a payload data file by encrypting the transaction account code; and
transmitting the payload data file to the RFID reader in at least one of character positions 64-79 of a Track 1 format as defined in ISO 7813.

10. The method of claim 1, wherein the unallocated field includes at least one of character positions 64-79 of a Track 1 format as defined in ISO 7813.

11. The method of claim 1, wherein the unallocated field includes at least one of: a field separator (FS) field, an expiry date (ED) field, a service code (SC) field, a PIN verification value (PVV) field, a discretionary data (DD) field, an end sentinel (ES) field, or a longitude redundancy check (LRC) field, of a Track 1 format as defined in ISO 7813.

12. A radio frequency transaction device, comprising:

a processor configured to create an encrypted authentication tag and a routing number, wherein the processor is configured to create the encrypted authentication tag using at least one of a counter value, the routing number, or a transaction account code; and
a communication device configured to transmit the encrypted authentication tag using a data transmission format comprising an account code field and an unallocated field, wherein the encrypted authentication tag is configured to be transmitted in the unallocated field of the data transmission format.

13. The radio frequency transaction device of claim 12, further comprising a memory configured to store customer identifying information, the counter value, the transaction account code, and an encryption key.

14. The radio frequency transaction device of claim 13, wherein the processor is configured to create the encrypted authentication tag using at least one of the customer identifying information, the encryption key, the counter value, the routing number, or the transaction account code.

15. The radio frequency transaction device of claim 12, further comprising a memory configured to store a payload data file.

16. The radio frequency transaction device of claim 15, wherein the payload data file comprises an encrypted transaction account code.

17. A method, comprising:

receiving an encrypted account payload data file from a radio frequency (RF) transaction device using a data transmission format comprising an account code field and an unallocated field, wherein the encrypted account payload data file is transmitted in the unallocated field of the data transmission format;
receiving a routing number from the RF transaction device in a transaction account field, wherein the transaction account field does not contain a transaction account code; and
using the routing number to transmit the encrypted account payload data file to an account provider.

18. The method of claim 17, further comprising:

providing a random number to the RF transaction device; and
receiving an encrypted authentication tag from the RF transaction device, wherein the encrypted authentication tag is generated using the random number and at least one of the transaction account code, the routing number, or a counter value.

19. The method of claim 18, further comprising converting at least one of the encrypted authentication tag, the counter value, the random number, or the routing number into a merchant point of sale (POS) recognized format.

20. The method of claim 19, wherein the merchant POS recognized format is ISO/IEC 8583 compatible.

21. The method of claim 18, further comprising verifying the encrypted authentication tag using an authentication tag decryption key corresponding to an identification code received from the RF transaction device.

22. The method of claim 17, further comprising decrypting the encrypted account payload data file using a payload decryption key corresponding to an identification code received from the RF transaction device.

23. The method of claim 17, wherein the transaction account field is a primary account number (PAN) field as defined by ISO 8583.

24. The method of claim 17, wherein transmitting the encrypted account payload data file to an account provider is performed without having access to the transaction account code.

25. A method, comprising:

associating radio frequency (RF) transaction device data with a routing number;
receiving an encrypted authentication tag from a merchant in accordance with the routing number using a data transmission format comprising an account code field and an unallocated field, wherein the encrypted authentication tag is transmitted in the unallocated field of the data transmission format;
verifying the encrypted authentication tag using an authentication tag decryption key corresponding to the RF transaction device data; and
decrypting the encrypted authentication tag to process a transaction request.

26. The method of claim 25, wherein the authentication tag decryption key relates to the routing number.

27. The method of claim 25, further comprising:

decrypting the encrypted authentication tag to read a counter value; and
verifying the counter value to facilitate processing the transaction request.

28. The method of claim 27, further comprising receiving a payload data file from the merchant in accordance with the routing number.

29. A method, comprising:

associating radio frequency (RF) transaction device data with a routing number;
receiving an encrypted authentication tag and a payload data file from a merchant in accordance with the routing number;
verifying the encrypted authentication tag using an authentication tag decryption key corresponding to the RF transaction device data; and
decrypting the encrypted authentication tag to process a transaction request and to read a counter value; and
verifying the counter value to facilitate processing the transaction request, wherein processing the transaction request comprises at least one of:
locating a payload decryption key using the routing number;
decrypting customer identifying information from the payload data file using the payload decryption key to create decrypted customer identifying information; or
providing the decrypted customer identifying information to a merchant point of sale (POS) device for processing.

30. A method, comprising:

creating an encrypted authentication tag using a random number;
creating a payload data file by encrypting a transaction account code; and
transmitting the encrypted authentication tag and the payload data file to a radio frequency identification (RFID) reader using a data transmission format comprising an account code field and an unallocated field,
wherein the encrypted authentication tag and the payload data file is transmitted in the unallocated field of the data transmission format.

31. The method of claim 30, further comprising receiving the random number from the RFID reader.

32. The method of claim 31, further comprising transmitting an RFID reader authentication code to the RFID reader and receiving an encrypted RFID reader authentication code from the RFID reader.

33. The method of claim 32, further comprising verifying the encrypted RFID reader authentication code for authentication of the RFID reader.

34. The method of claim 30, wherein the creating the encrypted authentication tag further uses a routing number.

35. The method of claim 30, further comprising incrementing a counter value by at least one of a random amount or a predetermined amount.

36. The method of claim 30, wherein a routing number is transmitted in a transaction account field.

37. The method of claim 36, wherein the transaction account field is a primary account number (PAN) field as defined by ISO 8583.

38. The method of claim 36, further comprising:

creating a payload data file by encrypting the transaction account code; and
transmitting the payload data file to the RFID reader in at least one of character positions 64-79 of a Track 1 format as defined in ISO 7813.

39. The method of claim 30, wherein the unallocated field includes at least one of character positions 64-79 of a Track 1 format as defined in ISO 7813.

40. The method of claim 30, wherein the unallocated field includes at least one of:

a field separator (FS) field, an expiry date (ED) field, a service code (SC) field, a PIN verification value (PVV) field, a discretionary data (DD) field, an end sentinel (ES) field, or a longitude redundancy check (LRC) field, of a Track 1 format as defined in ISO 7813.

41. A radio frequency transaction device, comprising:

a processor configured to: create an encrypted authentication tag using a routing number, and create a payload data file by encrypting a transaction account code; and
a communication device configured to transmit the encrypted authentication tag and payload data file using a data transmission format comprising an account code field and an unallocated field, wherein the encrypted authentication tag and the payload data file are configured to be transmitted in the unallocated field of the data transmission format.

42. The radio frequency transaction device of claim 41, further comprising a memory configured to store customer identifying information, a counter value, a transaction account code, and an encryption key.

43. The radio frequency transaction device of claim 42, wherein the processor is further configured to create the encrypted authentication tag using at least one of the customer identifying information, the encryption key, the counter value, the routing number, or the transaction account code.

44. The radio frequency transaction device of claim 41, further comprising a memory configured to store a payload data file.

45. The radio frequency transaction device of claim 44, wherein the payload data file comprises an encrypted transaction account code.

Referenced Cited
U.S. Patent Documents
D61466 September 1922 Foltz
2767756 October 1956 Niles
3376661 April 1968 Hulett
3446260 May 1969 Osher
3536894 October 1970 Travioli
3573731 April 1971 Schwend
3725647 April 1973 Retzky
3763356 October 1973 Berler
3829662 August 1974 Furahashi
3838252 September 1974 Hynes et al.
3873813 March 1975 Lahr et al.
3894756 July 1975 Ward
3914762 October 1975 Klensch
3929177 December 1975 Reis
3955295 May 11, 1976 Mayer
4044231 August 23, 1977 Beck et al.
4048737 September 20, 1977 McDermott
4056139 November 1, 1977 Murt
4058839 November 15, 1977 Darjany
4066873 January 3, 1978 Schatz
4119361 October 10, 1978 Greenaway
4202491 May 13, 1980 Suzuki
4206965 June 10, 1980 McGrew
4222516 September 16, 1980 Badet et al.
4277863 July 14, 1981 Faneuf
4318554 March 9, 1982 Anderson et al.
4356646 November 2, 1982 Johnson, Jr.
4361757 November 30, 1982 Ehrat
D270303 August 30, 1983 Zautner
D270546 September 13, 1983 Malmberg
4421380 December 20, 1983 McGrew
4436991 March 13, 1984 Albert et al.
4443027 April 17, 1984 McNeely et al.
4450535 May 22, 1984 dePommery et al.
4453074 June 5, 1984 Weinstein
4504084 March 12, 1985 Jauch
4507652 March 26, 1985 Vogt et al.
D280214 August 20, 1985 Opel
4538059 August 27, 1985 Rudland
4547002 October 15, 1985 Colgate, Jr.
4558211 December 10, 1985 Berstein
4563024 January 7, 1986 Blyth
4581523 April 8, 1986 Okuno
4582985 April 15, 1986 Lofberg
4589686 May 20, 1986 McGrew
4593936 June 10, 1986 Opel
4597814 July 1, 1986 Colgate, Jr.
4641017 February 3, 1987 Lopata
4643452 February 17, 1987 Chang
4656463 April 7, 1987 Anders et al.
4663518 May 5, 1987 Borror et al.
4684795 August 4, 1987 Colgate, Jr.
4692394 September 8, 1987 Drexler
4694148 September 15, 1987 Diekemper et al.
4697073 September 29, 1987 Hara
4697363 October 6, 1987 Gamm
4700055 October 13, 1987 Kashkashian, Jr.
4711690 December 8, 1987 Haghiri-Tehrani
4717221 January 5, 1988 McGrew
4725719 February 16, 1988 Oncken et al.
4736094 April 5, 1988 Yoshida
4744497 May 17, 1988 O'Neal
4747147 May 24, 1988 Sparrow
4768811 September 6, 1988 Oshikoshi et al.
4779898 October 25, 1988 Berning et al.
4794142 December 27, 1988 Alberts et al.
4795894 January 3, 1989 Sugimoto et al.
4801790 January 31, 1989 Solo
4816653 March 28, 1989 Anderl et al.
4829690 May 16, 1989 Andros
4837422 June 6, 1989 Dethloff et al.
4839504 June 13, 1989 Nakano
4841570 June 20, 1989 Cooper
4849617 July 18, 1989 Ueda
4852911 August 1, 1989 Hoppe
4853525 August 1, 1989 Vogt et al.
4863819 September 5, 1989 Drexler et al.
4868849 September 19, 1989 Tamaoki
4884507 December 5, 1989 Levy
4889366 December 26, 1989 Fabbiani
4897533 January 30, 1990 Lyszczarz
4897947 February 6, 1990 Kass-Pious
4910521 March 20, 1990 Mellon
4917292 April 17, 1990 Drexler
4918432 April 17, 1990 Pauley et al.
D307979 May 22, 1990 Purvis
4937963 July 3, 1990 Barnes
D310386 September 4, 1990 Michels et al.
4984270 January 8, 1991 LaBounty
4993068 February 12, 1991 Piosenka et al.
4998753 March 12, 1991 Wichael
5004899 April 2, 1991 Ueda
5010243 April 23, 1991 Fukushima et al.
5015830 May 14, 1991 Masuzawa et al.
5016274 May 14, 1991 Micali et al.
5023908 June 11, 1991 Weiss
5025372 June 18, 1991 Burton et al.
5052328 October 1, 1991 Eppenbach
5068894 November 26, 1991 Hoppe
5096228 March 17, 1992 Rinderknecht
5106125 April 21, 1992 Antes
5111033 May 5, 1992 Fujita et al.
5125356 June 30, 1992 Galante
5142383 August 25, 1992 Mallik
5171039 December 15, 1992 Dusek
5175416 December 29, 1992 Mansvelt et al.
5180902 January 19, 1993 Schick et al.
5192947 March 9, 1993 Neustein
5193114 March 9, 1993 Moseley
5198647 March 30, 1993 Mizuta
5202826 April 13, 1993 McCarthy
5206488 April 27, 1993 Teicher
5208110 May 4, 1993 Smith et al.
5217844 June 8, 1993 Fukushima et al.
5234624 August 10, 1993 Bauer et al.
5245329 September 14, 1993 Gokcebay
5251937 October 12, 1993 Ojsler
5256473 October 26, 1993 Kotani et al.
5257656 November 2, 1993 McLeroy
5259649 November 9, 1993 Shomron
5272326 December 21, 1993 Fujita et al.
5276311 January 4, 1994 Hennige
5279019 January 18, 1994 Knickle
5288978 February 22, 1994 Iijima
5300764 April 5, 1994 Hoshino et al.
5304789 April 19, 1994 Lob et al.
5308121 May 3, 1994 Gunn
5311679 May 17, 1994 Birch, Sr.
5321751 June 14, 1994 Ray et al.
5326964 July 5, 1994 Risser
5351052 September 27, 1994 d'Hont et al.
5351142 September 27, 1994 Cueli
5355411 October 11, 1994 MacDonald
5359522 October 25, 1994 Ryan
5365551 November 15, 1994 Snodgrass et al.
5383687 January 24, 1995 Suess et al.
5397881 March 14, 1995 Mannik
5410142 April 25, 1995 Tsuboi et al.
5412192 May 2, 1995 Hoss
5438184 August 1, 1995 Roberts et al.
5453601 September 26, 1995 d'Hont et al.
5461217 October 24, 1995 Claus
5461219 October 24, 1995 Cronvall
5477038 December 19, 1995 Levine et al.
5477040 December 19, 1995 Lalonde
5478629 December 26, 1995 Norman
5479494 December 26, 1995 Clitherow
5479530 December 26, 1995 Parameswaran et al.
5500513 March 19, 1996 Langhans et al.
5503434 April 2, 1996 Gunn
5506395 April 9, 1996 Eppley
5513272 April 30, 1996 Bogosian, Jr.
5513525 May 7, 1996 Schurmann
5514860 May 7, 1996 Berson
5516153 May 14, 1996 Kaule
5518810 May 21, 1996 Nishihara et al.
5520230 May 28, 1996 Sumner, III
5521966 May 28, 1996 Friedes et al.
5528222 June 18, 1996 Moskowitz et al.
5533656 July 9, 1996 Bonaldi
5534857 July 9, 1996 Laing et al.
5537314 July 16, 1996 Kanter
5539825 July 23, 1996 Akiyama
5541582 July 30, 1996 Wagner et al.
5544246 August 6, 1996 Mandelbaum et al.
5548291 August 20, 1996 Meier et al.
5555877 September 17, 1996 Lockwood et al.
5559504 September 24, 1996 Itsumi et al.
5559887 September 24, 1996 Davis et al.
5569897 October 29, 1996 Masuda
5572815 November 12, 1996 Kovner
5575094 November 19, 1996 Leake et al.
5577120 November 19, 1996 Penzias
5577121 November 19, 1996 Davis et al.
5577609 November 26, 1996 Hexter
5578808 November 26, 1996 Taylor
5585787 December 17, 1996 Wallerstein
5590038 December 31, 1996 Pitroda
5590197 December 31, 1996 Chen et al.
5592767 January 14, 1997 Treske
5594227 January 14, 1997 Deo
5602918 February 11, 1997 Chen et al.
5604801 February 18, 1997 Dolan et al.
5608203 March 4, 1997 Finkelstein et al.
5611965 March 18, 1997 Shouji et al.
5613001 March 18, 1997 Bakhoum
5613131 March 18, 1997 Moss et al.
5614703 March 25, 1997 Martin et al.
5621199 April 15, 1997 Calari et al.
5641050 June 24, 1997 Smith et al.
5649118 July 15, 1997 Carlisle et al.
5665439 September 9, 1997 Andersen et al.
5668876 September 16, 1997 Falk et al.
D384971 October 14, 1997 Kawan
5677953 October 14, 1997 Dolphin
5689100 November 18, 1997 Carrithers
5694596 December 2, 1997 Campbell
5697649 December 16, 1997 Dames et al.
5700037 December 23, 1997 Keller
5705101 January 6, 1998 Oi et al.
5705852 January 6, 1998 Orihara et al.
5710421 January 20, 1998 Kokubu
5715399 February 3, 1998 Bezos
5720500 February 24, 1998 Okazaki et al.
5724424 March 3, 1998 Gifford
5725098 March 10, 1998 Seifert et al.
5727140 March 10, 1998 Ohtomo et al.
5727696 March 17, 1998 Valiulis
5734838 March 31, 1998 Robinson et al.
5737439 April 7, 1998 Lapsley et al.
5739512 April 14, 1998 Tognazzini
5742756 April 21, 1998 Dillaway et al.
5742845 April 21, 1998 Wagner
5745571 April 28, 1998 Zuk
5757917 May 26, 1998 Rose et al.
5764789 June 9, 1998 Pare, Jr. et al.
5768385 June 16, 1998 Simon
5769457 June 23, 1998 Warther
5770843 June 23, 1998 Rose et al.
5773812 June 30, 1998 Kreft
5778069 July 7, 1998 Thomlinson
5778173 July 7, 1998 Apte
5786587 July 28, 1998 Colgate, Jr.
5789733 August 4, 1998 Jachimowicz et al.
5791474 August 11, 1998 Hansen
5796831 August 18, 1998 Paradinas et al.
5799087 August 25, 1998 Rosen
5806045 September 8, 1998 Biorge et al.
5808758 September 15, 1998 Solmsdorf
5815252 September 29, 1998 Price-Francis
5815657 September 29, 1998 Williams et al.
5823359 October 20, 1998 Harris et al.
5826241 October 20, 1998 Stein et al.
5826242 October 20, 1998 Montulli
5826243 October 20, 1998 Musmanno et al.
5838257 November 17, 1998 Lambropoulos
5838720 November 17, 1998 Morelli
5838812 November 17, 1998 Pare, Jr.
5852812 December 22, 1998 Reeder
5856048 January 5, 1999 Tahara et al.
5857079 January 5, 1999 Claus et al.
5857152 January 5, 1999 Everett
5857709 January 12, 1999 Chock
5859419 January 12, 1999 Wynn
5859587 January 12, 1999 Alicot et al.
5862325 January 19, 1999 Reed et al.
5864306 January 26, 1999 Dwyer et al.
5864830 January 26, 1999 Armetta et al.
5865470 February 2, 1999 Thompson
5869822 February 9, 1999 Meadows et al.
5875432 February 23, 1999 Sehr
D406861 March 16, 1999 Leedy, Jr.
5878138 March 2, 1999 Yacobi
5878141 March 2, 1999 Daly et al.
5878337 March 2, 1999 Joao et al.
5883377 March 16, 1999 Chapin, Jr.
5883810 March 16, 1999 Franklin et al.
5884271 March 16, 1999 Pitroda
5884280 March 16, 1999 Yoshioka et al.
5884292 March 16, 1999 Baker et al.
5884310 March 16, 1999 Brichta et al.
5886333 March 23, 1999 Miyake
5889941 March 30, 1999 Tushie et al.
D408054 April 13, 1999 Leedy, Jr.
5892211 April 6, 1999 Davis et al.
5897622 April 27, 1999 Blinn et al.
5898838 April 27, 1999 Wagner
5900954 May 4, 1999 Katz et al.
5901239 May 4, 1999 Kamei
5903875 May 11, 1999 Kohara
5903880 May 11, 1999 Biffar
5905908 May 18, 1999 Wagner
5907620 May 25, 1999 Klemba et al.
5909492 June 1, 1999 Payne et al.
5912446 June 15, 1999 Wong et al.
5913203 June 15, 1999 Wong et al.
5914472 June 22, 1999 Foladare et al.
5915016 June 22, 1999 Savalle et al.
5915023 June 22, 1999 Bernstein
5915973 June 29, 1999 Hoehn-Saric et al.
5917168 June 29, 1999 Nakamura et al.
5917913 June 29, 1999 Wang
5917925 June 29, 1999 Moore
5918216 June 29, 1999 Miksovsky et al.
5920058 July 6, 1999 Weber et al.
5920629 July 6, 1999 Rosen
5920847 July 6, 1999 Kolling et al.
5923734 July 13, 1999 Taskell
5923884 July 13, 1999 Peyret et al.
5924080 July 13, 1999 Johnson
5924624 July 20, 1999 Martin
5928788 July 27, 1999 Riedl
5930767 July 27, 1999 Reber et al.
5930777 July 27, 1999 Barber
5932870 August 3, 1999 Berson
5933328 August 3, 1999 Wallace et al.
5936226 August 10, 1999 Aucsmith
5936227 August 10, 1999 Truggelmann et al.
5938010 August 17, 1999 Osterbye
5942761 August 24, 1999 Tuli
5945653 August 31, 1999 Walker et al.
5949044 September 7, 1999 Walker et al.
5949335 September 7, 1999 Maynard
5949876 September 7, 1999 Ginter et al.
5950174 September 7, 1999 Brendzel
5950179 September 7, 1999 Buchanan et al.
5953710 September 14, 1999 Fleming
5955951 September 21, 1999 Wischerop et al.
5956693 September 21, 1999 Geerlings
5956699 September 21, 1999 Wong et al.
5958004 September 28, 1999 Helland et al.
5960411 September 28, 1999 Hartman et al.
5960416 September 28, 1999 Block
5963915 October 5, 1999 Kirsch
5966697 October 12, 1999 Fergerson et al.
5968570 October 19, 1999 Paulucci
5969318 October 19, 1999 Mackenthun
5970470 October 19, 1999 Walker
5970471 October 19, 1999 Hill
5970472 October 19, 1999 Allsop et al.
5970473 October 19, 1999 Gerszberg et al.
5970475 October 19, 1999 Barnes et al.
5971276 October 26, 1999 Sano et al.
5973475 October 26, 1999 Combaluzier
5974238 October 26, 1999 Chase, Jr.
5978348 November 2, 1999 Tamura
5979757 November 9, 1999 Tracy et al.
5979942 November 9, 1999 Ivicic
5982293 November 9, 1999 Everett et al.
5983200 November 9, 1999 Slotznick
5983207 November 9, 1999 Turk et al.
5984180 November 16, 1999 Albrecht
5988497 November 23, 1999 Wallace
5988510 November 23, 1999 Tuttle
5991413 November 23, 1999 Arditti et al.
5991748 November 23, 1999 Taskett
5995014 November 30, 1999 DiMaria
5999914 December 7, 1999 Blinn et al.
6000832 December 14, 1999 Franklin et al.
6006988 December 28, 1999 Behrmann et al.
6009412 December 28, 1999 Storey
6011487 January 4, 2000 Plocher
6012143 January 4, 2000 Tanaka
6012636 January 11, 2000 Smith
6014634 January 11, 2000 Scroggie et al.
6014635 January 11, 2000 Harris et al.
6014636 January 11, 2000 Reeder
6014646 January 11, 2000 Vallee et al.
6014648 January 11, 2000 Brennan
6014650 January 11, 2000 Zampese
6014748 January 11, 2000 Tushi et al.
6016476 January 18, 2000 Maes et al.
6016482 January 18, 2000 Molinari et al.
6016484 January 18, 2000 Williams et al.
6018718 January 25, 2000 Walker et al.
RE36580 February 22, 2000 Bogosian, Jr.
6021943 February 8, 2000 Chastain
6023510 February 8, 2000 Epstein
6024286 February 15, 2000 Bradley et al.
6024385 February 15, 2000 Goda
6025283 February 15, 2000 Roberts
6027028 February 22, 2000 Pieterse et al.
6029147 February 22, 2000 Horadan et al.
6029150 February 22, 2000 Kravitz
6029175 February 22, 2000 Chow
6029890 February 29, 2000 Austin
6029892 February 29, 2000 Miyake
6032136 February 29, 2000 Brake, Jr. et al.
6032866 March 7, 2000 Knighton et al.
6036100 March 14, 2000 Asami
6038292 March 14, 2000 Thomas
6038551 March 14, 2000 Barlow et al.
6041308 March 21, 2000 Walker et al.
6041410 March 21, 2000 Hsu et al.
6041412 March 21, 2000 Timson et al.
6044360 March 28, 2000 Picciallo
6044388 March 28, 2000 DeBellis et al.
6050494 April 18, 2000 Song et al.
6050605 April 18, 2000 Mikelionis et al.
6058418 May 2, 2000 Kobata
6060815 May 9, 2000 Nysen
6061344 May 9, 2000 Wood, Jr.
6061789 May 9, 2000 Hauser et al.
6064751 May 16, 2000 Smithies et al.
6064981 May 16, 2000 Barni et al.
6065675 May 23, 2000 Teicher
6068184 May 30, 2000 Barnett
6068193 May 30, 2000 Kreft
6070150 May 30, 2000 Remington et al.
6070154 May 30, 2000 Tavor et al.
6073112 June 6, 2000 Geerlings
6073236 June 6, 2000 Kusakabe et al.
6076078 June 13, 2000 Camp et al.
6076296 June 20, 2000 Schaeffer
6078906 June 20, 2000 Huberman
6078908 June 20, 2000 Schmitz
6081790 June 27, 2000 Rosen
6082422 July 4, 2000 Kaminski
6084967 July 4, 2000 Kennedy et al.
6085976 July 11, 2000 Sehr
6086971 July 11, 2000 Haas et al.
6088683 July 11, 2000 Jalili
6088717 July 11, 2000 Reed et al.
6088755 July 11, 2000 Kobayashi et al.
6088797 July 11, 2000 Rosen
6089611 July 18, 2000 Blank
6091835 July 18, 2000 Smithies et al.
6092198 July 18, 2000 Lanzy et al.
6095413 August 1, 2000 Tetro et al.
6095567 August 1, 2000 Buell
6098053 August 1, 2000 Slater
6098879 August 8, 2000 Terranova
6099043 August 8, 2000 Story
6100804 August 8, 2000 Brady et al.
6101477 August 8, 2000 Hohle et al.
6104281 August 15, 2000 Heinrich et al.
6104311 August 15, 2000 Lastinger
6104922 August 15, 2000 Baumann
6107920 August 22, 2000 Eberhardt et al.
6108641 August 22, 2000 Kenna et al.
6112191 August 29, 2000 Burke
6112984 September 5, 2000 Snavely
6115040 September 5, 2000 Bladow et al.
6115458 September 5, 2000 Taskett
6116655 September 12, 2000 Thouin et al.
6116736 September 12, 2000 Stark et al.
6120461 September 19, 2000 Smyth
6122625 September 19, 2000 Rosen
6125352 September 26, 2000 Franklin et al.
D432939 October 31, 2000 Hooglander
6128604 October 3, 2000 Sakamaki et al.
6130623 October 10, 2000 MacLellan et al.
6138913 October 31, 2000 Cyr et al.
6138917 October 31, 2000 Chapin, Jr.
6141752 October 31, 2000 Danes et al.
6144916 November 7, 2000 Wood et al.
6144948 November 7, 2000 Walker et al.
6148093 November 14, 2000 McConnell et al.
6148484 November 21, 2000 Andreae, Jr.
6154879 November 2000 Pare et al.
6155168 December 5, 2000 Sakamoto
6157824 December 5, 2000 Bailey
6163771 December 19, 2000 Walker et al.
6168083 January 2, 2001 Berger et al.
6171138 January 9, 2001 Lefebvre et al.
6173269 January 9, 2001 Solokl et al.
6173272 January 9, 2001 Thomas et al.
6173897 January 16, 2001 Halpern
6173898 January 16, 2001 Mande
6173899 January 16, 2001 Rozin
6177859 January 23, 2001 Tuttle et al.
6181287 January 30, 2001 Beigel
6182895 February 6, 2001 Albrecht
6184788 February 6, 2001 Middlemiss et al.
6185307 February 6, 2001 Johnson, Jr.
6189779 February 20, 2001 Verdicchio et al.
6189787 February 20, 2001 Dorf
6195006 February 27, 2001 Bowers et al.
6196465 March 6, 2001 Awano
6197396 March 6, 2001 Haas et al.
6198762 March 6, 2001 Krasnov
6199079 March 6, 2001 Gupta et al.
6199762 March 13, 2001 Hohle
6200272 March 13, 2001 Linden
6213390 April 10, 2001 Oneda
6213391 April 10, 2001 Lewis
6219639 April 17, 2001 Bakis et al.
6220510 April 24, 2001 Everett et al.
6222914 April 24, 2001 McMullin
6223977 May 1, 2001 Hill
6224109 May 1, 2001 Yang
6227424 May 8, 2001 Roegner
6227447 May 8, 2001 Campisano
6233348 May 15, 2001 Fujii et al.
6240989 June 5, 2001 Masoud
6247030 June 12, 2001 Suzuki
6248199 June 19, 2001 Smulson
6248314 June 19, 2001 Nakashimada et al.
6250554 June 26, 2001 Leo et al.
6250557 June 26, 2001 Forslund et al.
6255031 July 3, 2001 Yao et al.
6257620 July 10, 2001 Kenney
6263316 July 17, 2001 Khan et al.
6263446 July 17, 2001 Kausik et al.
6265977 July 24, 2001 Vega et al.
6267292 July 31, 2001 Walker et al.
6268788 July 31, 2001 Gray
6277232 August 21, 2001 Wang et al.
6290137 September 18, 2001 Kiekhaefer
6293462 September 25, 2001 Gangi
6295522 September 25, 2001 Boesch
6296188 October 2, 2001 Kiekhaefer
6297727 October 2, 2001 Nelson, Jr.
6304223 October 16, 2001 Hilton et al.
6307956 October 23, 2001 Black
6309098 October 30, 2001 Wong
6315195 November 13, 2001 Ramacchandran
6315206 November 13, 2001 Hansen et al.
6317750 November 13, 2001 Tortolani et al.
6317755 November 13, 2001 Rakers et al.
6318636 November 20, 2001 Reynolds et al.
6325293 December 4, 2001 Moreno
6327573 December 4, 2001 Walker et al.
6327578 December 4, 2001 Linehan
6329920 December 11, 2001 Morrison et al.
6330544 December 11, 2001 Walker et al.
6331972 December 18, 2001 Harris et al.
6332134 December 18, 2001 Foster
6332193 December 18, 2001 Glass et al.
D453160 January 29, 2002 Pentz et al.
D453161 January 29, 2002 Pentz
6336095 January 1, 2002 Rosen
6338048 January 8, 2002 Mori
6339384 January 15, 2002 Valdes-Rodriguez
D453337 February 5, 2002 Pentz et al.
D453338 February 5, 2002 Pentz et al.
D453516 February 12, 2002 Pentz
D454910 March 26, 2002 Smith et al.
6353420 March 5, 2002 Chung
6353811 March 5, 2002 Weissman
6360953 March 26, 2002 Lin et al.
6378073 April 23, 2002 Davis et al.
D457556 May 21, 2002 Hochschild
6386444 May 14, 2002 Sullivan
6397198 May 28, 2002 Hoffman et al.
6402026 June 11, 2002 Schwier
6404341 June 11, 2002 Reid
6406935 June 18, 2002 Kayanakis et al.
D460455 July 16, 2002 Pentz
6419158 July 16, 2002 Hooglander
6421650 July 16, 2002 Goetz et al.
6422462 July 23, 2002 Cohen
6422472 July 23, 2002 Thevenot et al.
6424249 July 23, 2002 Houvener
RE37822 August 27, 2002 Anthonyson
D461477 August 13, 2002 Pentz
6427910 August 6, 2002 Barnes et al.
6434159 August 13, 2002 Woodward et al.
6435415 August 20, 2002 Calle
6438235 August 20, 2002 Sims, III
6439455 August 27, 2002 Everett et al.
D462965 September 17, 2002 Pentz
D462966 September 17, 2002 Pentz et al.
6445794 September 3, 2002 Shefi
6446862 September 10, 2002 Mann
6457000 September 24, 2002 Witkowski et al.
6460696 October 8, 2002 Meyer
6471127 October 29, 2002 Pentz et al.
6480825 November 12, 2002 Sharma et al.
6480869 November 12, 2002 Fujioka
6481623 November 19, 2002 Grant et al.
6483427 November 19, 2002 Werb
6483477 November 19, 2002 Plonka
6491639 December 10, 2002 Turcott
6494367 December 17, 2002 Zacharias
6496594 December 17, 2002 Prokoski
6501832 December 31, 2002 Saylor et al.
6505772 January 14, 2003 Mollett et al.
6507662 January 14, 2003 Brooks
6520542 February 18, 2003 Thompson et al.
6523292 February 25, 2003 Slavik
6529880 March 4, 2003 McKeen et al.
6539101 March 25, 2003 Black
D474234 May 6, 2003 Nelms et al.
6575361 June 10, 2003 Graves et al.
6587835 July 1, 2003 Treyz et al.
6588673 July 8, 2003 Chan et al.
6591249 July 8, 2003 Zoka
6598024 July 22, 2003 Walker et al.
6601622 August 5, 2003 Young
6601759 August 5, 2003 Fife et al.
6601762 August 5, 2003 Piotrowski
6608551 August 19, 2003 Anderson et al.
6609656 August 26, 2003 Elledge
6609658 August 26, 2003 Sehr
6623039 September 23, 2003 Thompson et al.
6629591 October 7, 2003 Griswold et al.
6631849 October 14, 2003 Blossom
6636620 October 21, 2003 Hoshino
6636833 October 21, 2003 Flitcrofl et al.
6644551 November 11, 2003 Clayman et al.
6651168 November 18, 2003 Kao et al.
6651813 November 25, 2003 Vallans et al.
6651892 November 25, 2003 Hooglander
6657614 December 2, 2003 Ito et al.
6671358 December 30, 2003 Seidman et al.
6681328 January 20, 2004 Harris et al.
6681926 January 27, 2004 De Volpi
6684269 January 27, 2004 Wagner
6685089 February 3, 2004 Terranova et al.
6686847 February 3, 2004 Mittler
6687875 February 3, 2004 Suzuki
6690930 February 10, 2004 Dupre
6697947 February 24, 2004 Matyas, Jr. et al.
6703918 March 9, 2004 Kita
6704039 March 9, 2004 Pena
6704608 March 9, 2004 Azuma
6708375 March 23, 2004 Johnson
6725202 April 20, 2004 Hurta et al.
6732919 May 11, 2004 Macklin et al.
6735081 May 11, 2004 Bishop et al.
6747546 June 8, 2004 Hikita et al.
6749123 June 15, 2004 Lasch et al.
6751805 June 22, 2004 Austion
6763500 July 13, 2004 Black et al.
6764014 July 20, 2004 Lasch et al.
6765470 July 20, 2004 Shinzaki
6766952 July 27, 2004 Luu
6769718 August 3, 2004 Warther et al.
6771981 August 3, 2004 Zalewski et al.
6786400 September 7, 2004 Bucci
6789733 September 14, 2004 Terranova et al.
6793141 September 21, 2004 Graham
6799726 October 5, 2004 Stockhammer
6816058 November 9, 2004 McGregor et al.
6819219 November 16, 2004 Bolle et al.
6823910 November 30, 2004 Elnekaveh
6830193 December 14, 2004 Tanaka
6834270 December 21, 2004 Pagani et al.
6834795 December 28, 2004 Rasmussen et al.
6839840 January 4, 2005 Cooreman
6843415 January 18, 2005 Vogler
6845863 January 25, 2005 Riley
6851617 February 8, 2005 Saint et al.
6853087 February 8, 2005 Neuhaus et al.
6853894 February 8, 2005 Kolls
6853987 February 8, 2005 Cook
6859672 February 22, 2005 Roberts et al.
6873974 March 29, 2005 Schutzer
6877097 April 5, 2005 Hamid et al.
6883715 April 26, 2005 Fruhauf et al.
6895310 May 17, 2005 Kolls
6898299 May 24, 2005 Brooks
H2120 July 5, 2005 Cudlitz
6914517 July 5, 2005 Kinsella
6915277 July 5, 2005 Manchester et al.
6920560 July 19, 2005 Wallace
6924729 August 2, 2005 Aschauer et al.
6925439 August 2, 2005 Pilroda
6925565 August 2, 2005 Black
6928181 August 9, 2005 Brooks
6931538 August 16, 2005 Sawaguchi
6934861 August 23, 2005 Haala
D509243 September 6, 2005 Hunter, Jr. et al.
6940461 September 6, 2005 Nantz et al.
6944402 September 13, 2005 Baker et al.
6944768 September 13, 2005 Siegel et al.
6959874 November 1, 2005 Bardwell
6961448 November 1, 2005 Nichols et al.
6970583 November 29, 2005 Black
6978369 December 20, 2005 Wheeler et al.
6978933 December 27, 2005 Yap et al.
6986099 January 10, 2006 Todd
6990480 January 24, 2006 Burt
6994262 February 7, 2006 Warther
7003497 February 21, 2006 Maes
7003501 February 21, 2006 Ostroff
7004385 February 28, 2006 Douglass
7006993 February 28, 2006 Cheong et al.
7049962 May 23, 2006 Atherton et al.
7051925 May 30, 2006 Schwarz, Jr.
7059159 June 13, 2006 Lanigan et al.
7068148 June 27, 2006 Shanks et al.
7069444 June 27, 2006 Lowensohn et al.
7070112 July 4, 2006 Beenau et al.
7093767 August 22, 2006 Faenza et al.
7096204 August 22, 2006 Chen et al.
7096494 August 22, 2006 Chen
7100821 September 5, 2006 Rasti
7102523 September 5, 2006 Shanks et al.
7103575 September 5, 2006 Linehan
7108190 September 19, 2006 Burgan et al.
7119659 October 10, 2006 Bonalle et al.
7127672 October 24, 2006 Patterson et al.
7131574 November 7, 2006 Sciupac et al.
7132946 November 7, 2006 Waldner et al.
7136835 November 14, 2006 Flitcroft et al.
7150407 December 19, 2006 Berger et al.
7154375 December 26, 2006 Beenau et al.
7171662 January 30, 2007 Misra et al.
7172112 February 6, 2007 Bonalle et al.
7184747 February 27, 2007 Bogat
7213748 May 8, 2007 Tsuei et al.
7237121 June 26, 2007 Cammack et al.
7239226 July 3, 2007 Berardi et al.
7254557 August 7, 2007 Gillin et al.
7281135 October 9, 2007 Black
7287271 October 23, 2007 Riggins
7287695 October 30, 2007 Wankmueller
7299364 November 20, 2007 Noble et al.
7303120 December 4, 2007 Beenau et al.
7314164 January 1, 2008 Bonalle et al.
7314165 January 1, 2008 Bonalle et al.
7318550 January 15, 2008 Bonalle et al.
7325724 February 5, 2008 Bonalle et al.
7341181 March 11, 2008 Bonalle et al.
7363504 April 22, 2008 Bonalle et al.
7363505 April 22, 2008 Black
7419093 September 2, 2008 Blackson et al.
20010003071 June 7, 2001 Mansutti et al.
20010013546 August 16, 2001 Ross
20010013551 August 16, 2001 Ramachandran
20010017584 August 30, 2001 Shinzaki
20010018660 August 30, 2001 Sehr
20010022446 September 20, 2001 Klure
20010029493 October 11, 2001 Pare et al.
20010030238 October 18, 2001 Arisawa
20010032192 October 18, 2001 Putta et al.
20010034720 October 25, 2001 Armes et al.
20010036301 November 1, 2001 Yamaguchi et al.
20010036835 November 1, 2001 Leedom, Jr.
20010040507 November 15, 2001 Eckstein et al.
20010045469 November 29, 2001 Hooglander
20010049628 December 6, 2001 Icho
20010053239 December 20, 2001 Takhar
20010055411 December 27, 2001 Black
20020002468 January 3, 2002 Spagna et al.
20020005774 January 17, 2002 Rudolph et al.
20020014529 February 7, 2002 Tanaka
20020014952 February 7, 2002 Terranova
20020016687 February 7, 2002 Felsenslein et al.
20020019807 February 14, 2002 Halpern
20020024590 February 28, 2002 Pena
20020026419 February 28, 2002 Maritzen et al.
20020026575 February 28, 2002 Wheeler et al.
20020030579 March 14, 2002 Albert et al.
20020030581 March 14, 2002 Janiak et al.
20020036237 March 28, 2002 Atherton et al.
20020038818 April 4, 2002 Zingher et al.
20020040935 April 11, 2002 Weyant
20020040936 April 11, 2002 Wentker et al.
20020041093 April 11, 2002 Cox et al.
20020042782 April 11, 2002 Albazz et al.
20020043566 April 18, 2002 Goodman et al.
20020046341 April 18, 2002 Kazaks et al.
20020062249 May 23, 2002 Iannacci
20020062284 May 23, 2002 Kawan
20020062291 May 23, 2002 Zoka
20020066784 June 6, 2002 Segal et al.
20020072349 June 13, 2002 Geiselman et al.
20020073025 June 13, 2002 Tanner et al.
20020083320 June 27, 2002 Vatanen
20020087869 July 4, 2002 Kim
20020095298 July 18, 2002 Ewing
20020095587 July 18, 2002 Doyle
20020095588 July 18, 2002 Shigematsu et al.
20020097142 July 25, 2002 Janiak et al.
20020099665 July 25, 2002 Burger et al.
20020107791 August 8, 2002 Nobrega et al.
20020108062 August 8, 2002 Nakajima et al.
20020111919 August 15, 2002 Weller et al.
20020112177 August 15, 2002 Voltmer et al.
20020125184 September 12, 2002 Bassinson
20020128977 September 12, 2002 Nambiar et al.
20020129248 September 12, 2002 Wheeler et al.
20020130186 September 19, 2002 Lasch et al.
20020130187 September 19, 2002 Berg et al.
20020133467 September 19, 2002 Hobson et al.
20020133725 September 19, 2002 Roy et al.
20020138351 September 26, 2002 Houvener et al.
20020138425 September 26, 2002 Shimizu et al.
20020139839 October 3, 2002 Catan
20020140542 October 3, 2002 Prokoski et al.
20020147002 October 10, 2002 Trop et al.
20020147600 October 10, 2002 Waters et al.
20020149467 October 17, 2002 Calvesio et al.
20020152123 October 17, 2002 Giordano et al.
20020153410 October 24, 2002 Santini
20020153424 October 24, 2002 Li
20020158747 October 31, 2002 McGregor et al.
20020163421 November 7, 2002 Wang et al.
20020165931 November 7, 2002 Greer et al.
20020166897 November 14, 2002 Hooglander
20020169673 November 14, 2002 Prorock et al.
20020175805 November 28, 2002 Armstrong et al.
20020178063 November 28, 2002 Gravelle et al.
20020178124 November 28, 2002 Lewis
20020178369 November 28, 2002 Black
20020179704 December 5, 2002 Deaton
20020186133 December 12, 2002 Loof
20020186838 December 12, 2002 Brandys
20020188854 December 12, 2002 Heaven et al.
20020188855 December 12, 2002 Nakayama et al.
20020190124 December 19, 2002 Piotrowski
20020191816 December 19, 2002 Maritzen et al.
20020192856 December 19, 2002 Halope et al.
20020193102 December 19, 2002 Hyyppa et al.
20020194137 December 19, 2002 Park et al.
20030001006 January 2, 2003 Lee
20030001755 January 2, 2003 Tiernay et al.
20030004866 January 2, 2003 Huennekens et al.
20030004881 January 2, 2003 Shinzaki et al.
20030005310 January 2, 2003 Shinzaki
20030006901 January 9, 2003 Kim et al.
20030009382 January 9, 2003 DArbeloff et al.
20030018567 January 23, 2003 Flitcrofl et al.
20030018893 January 23, 2003 Hess
20030028481 February 6, 2003 Flitcrofl et al.
20030033697 February 20, 2003 Hicks et al.
20030037264 February 20, 2003 Ezaki et al.
20030037851 February 27, 2003 Hogganvik
20030046237 March 6, 2003 Uberti
20030046540 March 6, 2003 Nakamura et al.
20030047482 March 13, 2003 Jones et al.
20030054836 March 20, 2003 Michot
20030055727 March 20, 2003 Walker et al.
20030061172 March 27, 2003 Robinson
20030074317 April 17, 2003 Hofi
20030086591 May 8, 2003 Simon
20030093187 May 15, 2003 Walker
20030097344 May 22, 2003 Chaum et al.
20030106935 June 12, 2003 Burchette, Jr.
20030112120 June 19, 2003 Mark
20030115126 June 19, 2003 Pitroda
20030120626 June 26, 2003 Piotrowski
20030122120 July 3, 2003 Brazis et al.
20030123714 July 3, 2003 O'Gorman et al.
20030124294 July 3, 2003 Hodson et al.
20030125054 July 3, 2003 Garcia
20030130820 July 10, 2003 Lane, III
20030132132 July 17, 2003 Small
20030132297 July 17, 2003 McCall et al.
20030149661 August 7, 2003 Mitchell et al.
20030149662 August 7, 2003 Shore
20030150911 August 14, 2003 Joseph
20030152252 August 14, 2003 Kondo et al.
20030153356 August 14, 2003 Liu et al.
20030155416 August 21, 2003 Macklin et al.
20030159044 August 21, 2003 Doyle et al.
20030160074 August 28, 2003 Pineda
20030173408 September 18, 2003 Mosher, Jr. et al.
20030177102 September 18, 2003 Robinson
20030178495 September 25, 2003 Jones et al.
20030183695 October 2, 2003 Labree et al.
20030191949 October 9, 2003 Odagawa
20030195037 October 16, 2003 Vuong et al.
20030197593 October 23, 2003 Siegel et al.
20030208439 November 6, 2003 Rast
20030223625 December 4, 2003 Hillhouse et al.
20030226041 December 4, 2003 Palmer et al.
20030229793 December 11, 2003 McCall et al.
20030230514 December 18, 2003 Baker
20030236704 December 25, 2003 Antonucci
20040006497 January 8, 2004 Nestor et al.
20040006539 January 8, 2004 Royer et al.
20040011877 January 22, 2004 Reppermund
20040014457 January 22, 2004 Stevens
20040016796 January 29, 2004 Hanna et al.
20040017934 January 29, 2004 Kocher
20040019494 January 29, 2004 Ridgeway et al.
20040019564 January 29, 2004 Goldthwaite et al.
20040021552 February 5, 2004 Koo
20040024694 February 5, 2004 Lawrence et al.
20040026518 February 12, 2004 Kudo et al.
20040030601 February 12, 2004 Pond et al.
20040031856 February 19, 2004 Atsmon et al.
20040039814 February 26, 2004 Crabtree et al.
20040041021 March 4, 2004 Nugent et al.
20040041690 March 4, 2004 Yamagishi
20040044627 March 4, 2004 Russell et al.
20040046034 March 11, 2004 Ey Yamani et al.
20040049687 March 11, 2004 Orsini
20040050930 March 18, 2004 Rose
20040052406 March 18, 2004 Brooks
20040059923 March 25, 2004 ShamRao
20040061593 April 1, 2004 Lane
20040062423 April 1, 2004 Doi
20040073792 April 15, 2004 Noble et al.
20040083184 April 29, 2004 Tsuei et al.
20040083380 April 29, 2004 Janke
20040084524 May 6, 2004 Ramachandran
20040084542 May 6, 2004 DeYoe et al.
20040089724 May 13, 2004 Lasch et al.
20040098336 May 20, 2004 Flink
20040104266 June 3, 2004 Bolle et al.
20040104268 June 3, 2004 Bailey et al.
20040118930 June 24, 2004 Berardi et al.
20040124104 July 1, 2004 DeVolpi
20040124246 July 1, 2004 Allen et al.
20040127256 July 1, 2004 Goldthwaite et al.
20040129787 July 8, 2004 Saito et al.
20040131237 July 8, 2004 Machida
20040133787 July 8, 2004 Doughty et al.
20040136573 July 15, 2004 Sato
20040144841 July 29, 2004 Tsukamoto et al.
20040144846 July 29, 2004 Lasch et al.
20040149287 August 5, 2004 Zulli
20040155101 August 12, 2004 Royer et al.
20040158723 August 12, 2004 Root
20040160310 August 19, 2004 Chen et al.
20040161135 August 19, 2004 Sano et al.
20040165753 August 26, 2004 Takhiri et al.
20040169071 September 2, 2004 Burgan et al.
20040172541 September 2, 2004 Ando et al.
20040176071 September 9, 2004 Gehrmann et al.
20040177045 September 9, 2004 Brown
20040178063 September 16, 2004 Mirchi et al.
20040180657 September 16, 2004 Yaqub et al.
20040188519 September 30, 2004 Cassone
20040190757 September 30, 2004 Murphy et al.
20040193676 September 30, 2004 Marks
20040195314 October 7, 2004 Lee
20040199469 October 7, 2004 Barillova et al.
20040202354 October 14, 2004 Togino
20040208343 October 21, 2004 Golden et al.
20040215575 October 28, 2004 Garrity
20040222803 November 11, 2004 Tartagni
20040230488 November 18, 2004 Beenau et al.
20040232220 November 25, 2004 Beenau et al.
20040232224 November 25, 2004 Beenau et al.
20040233039 November 25, 2004 Beenau et al.
20040235450 November 25, 2004 Rosenberg
20040236680 November 25, 2004 Luoffo et al.
20040236699 November 25, 2004 Beenau et al.
20040236700 November 25, 2004 Beenau et al.
20040236701 November 25, 2004 Beenau et al.
20040236819 November 25, 2004 Anali et al.
20040239480 December 2, 2004 Beenau et al.
20040240711 December 2, 2004 Hamza et al.
20040255168 December 16, 2004 Murashita et al.
20040257196 December 23, 2004 Kotzin
20040258282 December 23, 2004 Bjorn et al.
20050001711 January 6, 2005 Doughty et al.
20050004921 January 6, 2005 Beenau et al.
20050005172 January 6, 2005 Haala
20050011776 January 20, 2005 Nagel
20050017068 January 27, 2005 Zalewski et al.
20050018658 January 27, 2005 Ikeda et al.
20050020304 January 27, 2005 Shinzaki
20050021457 January 27, 2005 Johnson et al.
20050023157 February 3, 2005 Logan
20050033686 February 10, 2005 Peart et al.
20050033687 February 10, 2005 Beenau et al.
20050033688 February 10, 2005 Peart et al.
20050033689 February 10, 2005 Bonalle et al.
20050033992 February 10, 2005 Inabe
20050035192 February 17, 2005 Bonalle et al.
20050035847 February 17, 2005 Bonalle et al.
20050036665 February 17, 2005 Higuchi
20050038718 February 17, 2005 Barnes et al.
20050040221 February 24, 2005 Schwarz, Jr.
20050045718 March 3, 2005 Bortolin et al.
20050050367 March 3, 2005 Burger et al.
20050054438 March 10, 2005 Rothschild et al.
20050058262 March 17, 2005 Timmins et al.
20050060233 March 17, 2005 Bonalle et al.
20050065842 March 24, 2005 Summers
20050065872 March 24, 2005 Moebs et al.
20050071231 March 31, 2005 Beenau et al.
20050087597 April 28, 2005 Gotfried et al.
20050091325 April 28, 2005 Kuwana et al.
20050097038 May 5, 2005 Yu et al.
20050098621 May 12, 2005 deSylva
20050100199 May 12, 2005 Boshra
20050102524 May 12, 2005 Haala
20050103839 May 19, 2005 Hewel
20050109836 May 26, 2005 Ben-Aissa
20050113137 May 26, 2005 Rodriguez et al.
20050116024 June 2, 2005 Beenau et al.
20050119978 June 2, 2005 Ales
20050122209 June 9, 2005 Black
20050123137 June 9, 2005 McCallum
20050125312 June 9, 2005 Dearing et al.
20050125343 June 9, 2005 Mendelovich
20050127164 June 16, 2005 Wankmueller
20050137977 June 23, 2005 Wankmueller
20050139669 June 30, 2005 Arnouse
20050144133 June 30, 2005 Hoffman et al.
20050149358 July 7, 2005 Sacco et al.
20050149926 July 7, 2005 Saltz
20050160271 July 21, 2005 Brundage et al.
20050160790 July 28, 2005 Tanaka et al.
20050165684 July 28, 2005 Jensen et al.
20050166062 July 28, 2005 Sanchez-Cifuentes
20050169504 August 4, 2005 Black
20050171787 August 4, 2005 Zagami
20050171905 August 4, 2005 Wankmueller
20050180618 August 18, 2005 Black
20050187883 August 25, 2005 Bishop et al.
20050187916 August 25, 2005 Levin et al.
20050197923 September 8, 2005 Kilner et al.
20050203857 September 15, 2005 Friedman
20050207002 September 22, 2005 Liu et al.
20050211784 September 29, 2005 Justin
20050212657 September 29, 2005 Simon
20050216424 September 29, 2005 Gandre et al.
20050221853 October 6, 2005 Silvester
20050223230 October 6, 2005 Zick
20050232471 October 20, 2005 Baer
20050240778 October 27, 2005 Saito
20050246292 November 3, 2005 Sarcanin
20050251688 November 10, 2005 Nanavati et al.
20050261972 November 24, 2005 Black
20050275505 December 15, 2005 Himmelstein
20050278222 December 15, 2005 Northrup
20060000892 January 5, 2006 Bonalle et al.
20060000893 January 5, 2006 Bonalle et al.
20060000894 January 5, 2006 Bonalle et al.
20060000895 January 5, 2006 Bonalle et al.
20060000896 January 5, 2006 Bonalle et al.
20060000897 January 5, 2006 Bonalle et al.
20060000898 January 5, 2006 Bonalle et al.
20060000899 January 5, 2006 Bonalle et al.
20060005022 January 5, 2006 Wakamori et al.
20060005042 January 5, 2006 Black
20060016868 January 26, 2006 Bonalle et al.
20060016869 January 26, 2006 Bonalle et al.
20060016871 January 26, 2006 Bonalle et al.
20060016874 January 26, 2006 Bonalle et al.
20060016875 January 26, 2006 Bonalle et al.
20060016877 January 26, 2006 Bonalle et al.
20060033609 February 16, 2006 Bridgelall
20060034492 February 16, 2006 Siegel et al.
20060066444 March 30, 2006 Steeves
20060069635 March 30, 2006 Ram et al.
20060071756 April 6, 2006 Steeves
20060080552 April 13, 2006 Lauper
20060095369 May 4, 2006 Hofi
20060104485 May 18, 2006 Miller et al.
20060123240 June 8, 2006 Chaiken
20060136336 June 22, 2006 Drummond et al.
20060156395 July 13, 2006 Fontaine
20060158434 July 20, 2006 Zank et al.
20060173291 August 3, 2006 Glossop
20060173791 August 3, 2006 Mann et al.
20060177061 August 10, 2006 Orsini et al.
20060178937 August 10, 2006 Rau et al.
20060190419 August 24, 2006 Bunn et al.
20060202835 September 14, 2006 Thibault
20060208066 September 21, 2006 Finn et al.
20060213986 September 28, 2006 Register et al.
20060229988 October 12, 2006 Oshima et al.
20060237528 October 26, 2006 Bishop et al.
20060242423 October 26, 2006 Kussmaul
20060278723 December 14, 2006 Dan et al.
20070008131 January 11, 2007 Doan et al.
20070046468 March 1, 2007 Davis
20070057797 March 15, 2007 Waldner et al.
20070075841 April 5, 2007 Maltsev et al.
20070112957 May 17, 2007 Shastri et al.
20070119924 May 31, 2007 Register et al.
20070241861 October 18, 2007 Venkatanna et al.
20070252001 November 1, 2007 Kail et al.
20070252010 November 1, 2007 Gonzalez et al.
20070284432 December 13, 2007 Abouyounes
20070296544 December 27, 2007 Beenau et al.
20070296551 December 27, 2007 Beenau et al.
20070299782 December 27, 2007 Beenau et al.
20070299783 December 27, 2007 Beenau et al.
20080006691 January 10, 2008 Bonalle et al.
20080008359 January 10, 2008 Beenau et al.
20080008363 January 10, 2008 Bonalle et al.
20080010214 January 10, 2008 Bonalle et al.
20080011830 January 17, 2008 Bonalle et al.
20080011831 January 17, 2008 Bonalle et al.
20080013796 January 17, 2008 Bonalle et al.
20080013807 January 17, 2008 Bonalle et al.
20080015941 January 17, 2008 Beenau et al.
20080015992 January 17, 2008 Bonalle et al.
20080015993 January 17, 2008 Bonalle et al.
20080015994 January 17, 2008 Bonalle et al.
20080016002 January 17, 2008 Beenau et al.
20080033722 February 7, 2008 Beenau et al.
20080067242 March 20, 2008 Bonalle et al.
20080072065 March 20, 2008 Bonalle et al.
Foreign Patent Documents
2300241 September 2000 CA
689070 August 1997 CH
689680 August 1999 CH
2847756 May 1980 DE
3636921 May 1981 DE
3941070 June 1991 DE
4339460 November 1993 DE
4339460 April 1995 DE
29702538 April 1997 DE
19741726 September 1997 DE
10203926 January 2002 DE
0181770 May 1986 EP
0343829 November 1989 EP
0354817 February 1990 EP
0368570 May 1990 EP
0388090 September 1990 EP
0403134 December 1990 EP
0411602 February 1991 EP
0473998 March 1992 EP
0481388 April 1992 EP
0531605 March 1993 EP
0552047 July 1993 EP
0560318 September 1993 EP
0568185 November 1993 EP
917120 May 1995 EP
0657297 June 1995 EP
0721850 July 1996 EP
0735505 October 1996 EP
0780839 June 1997 EP
927945 July 1997 EP
0789316 August 1997 EP
0854461 July 1998 EP
0866420 September 1998 EP
0894620 February 1999 EP
0916519 May 1999 EP
0917120 May 1999 EP
0927945 July 1999 EP
0949595 October 1999 EP
949595 October 1999 EP
1017030 July 2000 EP
1017030 July 2000 EP
1115095 July 2001 EP
1345146 September 2003 EP
1345146 September 2003 EP
1610273 December 2005 EP
1371254 October 1974 GB
2088110 June 1982 GB
2108906 May 1985 GB
2240948 August 1991 GB
2281714 March 1995 GB
2350021 November 2000 GB
2350021 November 2000 GB
2361790 October 2001 GB
42005596 March 1967 JP
61-100436 May 1986 JP
62-043774 March 1987 JP
62-264999 November 1987 JP
63-071794 April 1988 JP
63-098689 April 1988 JP
63-072721 May 1988 JP
63-175987 July 1988 JP
64-004934 January 1989 JP
64-087395 March 1989 JP
64-087396 March 1989 JP
64-087397 March 1989 JP
02-130737 May 1990 JP
02-252149 October 1990 JP
03-290780 December 1991 JP
42-005596 July 1992 JP
04-303692 October 1992 JP
05-069689 March 1993 JP
05-254283 October 1993 JP
06-183187 July 1994 JP
06-191137 July 1994 JP
06-234287 August 1994 JP
07-173358 July 1995 JP
07-205569 August 1995 JP
08-244385 September 1996 JP
08-324163 December 1996 JP
09-050505 February 1997 JP
09-052240 February 1997 JP
9050505 February 1997 JP
09-274640 October 1997 JP
10-129161 May 1998 JP
10-289296 October 1998 JP
10289296 October 1998 JP
10302160 November 1998 JP
10-334206 December 1998 JP
10-340231 December 1998 JP
10334206 December 1998 JP
10340231 December 1998 JP
11-175640 July 1999 JP
11175640 July 1999 JP
11-227367 August 1999 JP
11-353425 December 1999 JP
11353425 December 1999 JP
2000-048153 February 2000 JP
2000048153 February 2000 JP
2000-163538 June 2000 JP
2000-177229 June 2000 JP
2000163538 June 2000 JP
2000-194799 July 2000 JP
2000194799 July 2000 JP
2000-222176 August 2000 JP
2000222176 August 2000 JP
2000-252854 September 2000 JP
2000252854 September 2000 JP
2001-504406 April 2001 JP
2001-134536 May 2001 JP
2001134536 May 2001 JP
2001-160105 June 2001 JP
2001160105 June 2001 JP
2001-315475 November 2001 JP
2002-032687 January 2002 JP
2002-109584 April 2002 JP
2002109584 April 2002 JP
2002-133335 May 2002 JP
2002-133336 May 2002 JP
2002-157530 May 2002 JP
2002133335 May 2002 JP
2002157530 May 2002 JP
2002-163585 June 2002 JP
2002-183443 June 2002 JP
2002-274087 September 2002 JP
2003-288646 October 2003 JP
2003288646 October 2003 JP
2004-164347 June 2004 JP
2004-348478 December 2004 JP
WO 81/00776 March 1981 WO
WO 89/03760 May 1989 WO
WO 90/08661 August 1990 WO
WO 91/08910 June 1991 WO
WO 92/16913 October 1992 WO
9535546 December 1995 WO
WO 95/35546 December 1995 WO
WO 96/06409 February 1996 WO
WO 96/18972 June 1996 WO
WO 97/09688 March 1997 WO
9740459 October 1997 WO
WO 97/40459 October 1997 WO
9821683 May 1998 WO
WO 98/21683 May 1998 WO
WO 98/22291 May 1998 WO
9845778 October 1998 WO
WO 98/45778 October 1998 WO
WO 99/12136 March 1999 WO
WO 99/14055 March 1999 WO
9921321 April 1999 WO
WO 99/21321 April 1999 WO
WO 99/27492 June 1999 WO
9940548 August 1999 WO
WO 99/40548 August 1999 WO
WO 99/47983 September 1999 WO
WO 99/49424 September 1999 WO
WO 00/49586 August 2000 WO
WO 00/73989 December 2000 WO
WO 01/13320 February 2001 WO
WO 01/18745 March 2001 WO
WO 01/25872 April 2001 WO
WO 01/55955 August 2001 WO
WO 01/78024 October 2001 WO
WO 01/86535 November 2001 WO
WO 01/86599 November 2001 WO
03007623 January 2003 WO
WO 03/007623 January 2003 WO
WO 2004/052657 June 2004 WO
Other references
  • Derfler, “How Networks Work,” Bestseller Edition 1996, Ziff-Davis Press, Emeryville, CA, all pages.
  • White, “How Computers Work,” Millennium Edition, 1999, Que Corporation, Indianapolis, IN, all pages.
  • Gralia, “How the Internet Works,” Millennium Edition, 1999, Que Corporation, Indianapolis, IN, all pages.
  • Muller, “Desktop Encyclopedia of the Internet,” 1999, Artech House Inc., Norwood, MA, all pages.
  • “The Bank Credit Card Business,” American Bankers Association, 1996, all pages.
  • Menezes, et al., “Handbook of Applied Cryptography,” 1997, CRC Press, Chapter 10.
  • U.S. Appl. No. 60/395,606, filed Jul. 15, 2002.
  • “Credit Card Offer Travelers New Benefit,” PR Newswire, Aug. 5, 1987.
  • “Inside's Next Gen Smart Card: The French company plans to introduce an RFID card that uses a 16-bit microprocessor and new encryption technology,” RFID Journal, Oct. 29, 2002.
  • “New Evidence about Positive Three-Tier Co-Pay Performance Presented at Express Scripts 2000 Outcomes Conference,” PR Newswire Association, Inc., Jun. 28, 2000.
  • “Prestige Credit Cards: Those Pricey Plastics,” Changing Times, Apr. 1986.
  • “Shell Introduces Optional Credit Card.” The Associated Press, Sep. 3, 1985.
  • “Shell Introducing Expanded ‘Signature’ Credit Card,” Tulsa Business Chronicle, Sep. 5, 1985.
  • “Shell-Oil: Introduces Shell Signature Travel and Entertainment Credit Card,” Business Wire, Sep. 3, 1985.
  • “The Chase Manhattan Bank Today Announced a Comprehensive Program to Enhance the Value of All of its Credit Cards,” PR Newswire, Dec. 18, 1986.
  • Carey, Gordon, “Multi-tier Copay,” Pharmaceutical Executive, Feb. 2000.
  • Crumbaugh, Darlene M., “Effective Marketing Positions: Check card as consumer lifeline,” Hoosier Banker, Apr. 1998, p. 10, vol. 82, issue 4.
  • Gabber, et al., “Agora: A Minimal Distributed Protocol for Electronic Commerce,” USENIX Oakland, CA, Nov. 18, 1996.
  • Goldwasser, Joan, “Best of the Cash-Back Cards,” Kiplinger's Personal Finance Magazine, Apr. 1999.
  • Kuntz, Mary, “Credit Cards as Good as Gold,” Forbes, Nov. 4, 1985.
  • Lahey, Liam, “Microsoft Bolsters Rebate Structure,” Computer Dealer News, Feb. 8, 2002.
  • Lamond, “Credit Card Transactions Real World and Online,” Copyright 1996.
  • Nyman, Judy, “Free Income Tax Clinics are Opening as Apr. 30 Deadline Draws Nearer,” The Toronto Star, Final Edition, Mar. 25, 1986.
  • Obel, Michael, “Oil Companies Push Marketing, Cost Cutting to Fortify Earnings,” Oil & Gas Journal, Sep. 16, 1985.
  • Schmuckler, Eric, “Playing Your Cards Right,” Forbes, Dec. 28, 1987.
  • “Core One Credit Union—Discover The Advantage,” http://coreone.org/2visa.html, Copyright 2001 (last visited Oct. 9, 2002).
  • Non-Final Office Action issued Apr. 20, 2005 in U.S. Appl. No. 10/192,488.
  • Final Office Action issued Sep. 8, 2005 in U.S. Appl. No. 10/192,488.
  • Advisory Action issued Nov. 10, 2005 in U.S. Appl. No. 10/192,488.
  • Non-Final Office Action issued Jan. 18, 2006 in U.S. Appl. No. 10/192,488.
  • Final Office Action issued Sep. 25, 2006 in U.S. Appl. No. 10/192,488.
  • Notice of Allowance issued Feb. 2, 2007 in U.S. Appl. No. 10/192,488.
  • Examiner's Report dated Oct. 5, 2006 for AU2002318293.
  • Office Action dated Jun. 28, 2007 in CA 2,452,351.
  • Office Action dated Apr. 25, 2008 in CA 2,452,351.
  • Supplemental Search Report dated Nov. 16, 2004 for EP02748120.9.
  • Examination Report dated Mar. 8, 2005 for EP02748120.9.
  • Examination Report dated Feb. 8, 2006 for EP02748120.9.
  • Examination Report dated Oct. 24, 2007 for EP02748120.9.
  • Office Action dated Mar. 9, 2006 in JP2003-513257.
  • Office Action dated Oct. 20, 2006 in JP2003-513257.
  • Office Action dated Aug. 1, 2007 in JP2003-513257.
  • Office Action dated Jan. 29, 2008 in JP2003-513257.
  • Office Action dated Jul. 11, 2007 for MX PA/a/2004/000253.
  • Office Action dated Jan. 27, 2005 in NZ530497.
  • ISR dated Dec. 30, 2002 for PCT/US02/0219903.
  • Office Action dated Dec. 30, 2005 for CN02813783.3.
  • Office Action dated May 16, 2007 for CN02813783.3.
  • Non-Final Office Action mailed Feb. 8, 2008 in U.S. Appl. No. 10/340,352.
  • Final Office Action mailed Jun. 13, 2008 in U.S. Appl. No. 10/340,352.
  • Advisory Action mailed Aug. 19, 2008 in U.S. Appl. No. 10/340,352.
  • Office Action dated Jan. 29, 2007 for CA2458143.
  • Office Action dated Dec. 19, 2007 for CA2458143.
  • Supplemental Search Report dated May 26, 2006 for EP03763325.2.
  • Examination Report dated Oct. 26, 2006 for EP03763325.2.
  • Office Action dated Aug. 3, 2006 in JP2004-562629.
  • Office Action dated Mar. 8, 2007 in JP2004-562629.
  • Final Office Action dated Oct. 4, 2007 in JP2004-562629.
  • ISR dated Apr. 22, 2004 for PCT/US03/21279.
  • Office Action dated Oct. 4, 2007 for JP2007-026166.
  • Non-Final Office Action issued Mar. 26, 2008 in U.S. Appl. No. 10/905,005.
  • Non-Final Office Action issued Nov. 1, 2006 in U.S. Appl. No. 10/905,006.
  • Notice of Allowance issued Jul. 12, 2007 in U.S. Appl. No. 10/905,006.
  • Non-Final Office Action issued Jun. 20, 2006 in U.S. Appl. No. 10/318,480.
  • Notice of Allowance issued Jan. 24, 2007 in U.S. Appl. No. 10/318,480.
  • Supplemental Notice of Allowance issued Mar. 13, 2007 in U.S. Appl. No. 10/318,480.
  • ISR dated Apr. 22, 2004 for PCT/US03/21447.
  • Non-Final Office Action issued Nov. 22, 2005 in U.S. Appl. No. 10/876,822.
  • Final Office Action issued Aug. 3, 2006 in U.S. Appl. No. 10/876,822.
  • Non-Final Office Action issued Feb. 6, 2007 in U.S. Appl. No. 10/876,822.
  • Final Office Action issued Jul. 18, 2007 in U.S. Appl. No. 10/876,822.
  • Non-Final Office Action issued Jan. 28, 2008 in U.S. Appl. No. 10/876,822.
  • Final Office Action issued Aug. 22, 2008 in U.S. Appl. No. 10/876,822.
  • Non-Final Office Action issued Mar. 23, 2006 in U.S. Appl. No. 10/318,432.
  • Restriction Requirement issued Jan. 17, 2007 in U.S. Appl. No. 10/318,432.
  • Non-Final Office Action issued May 1, 2007 in U.S. Appl. No. 10/318,432.
  • Non-Final Office Action issued Dec. 13, 2007 in U.S. Appl. No. 10/318,432.
  • Non-Final Office Action issued Jun. 27, 2008 in U.S. Appl. No. 10/318,432.
  • ISR dated Apr. 22, 2004 for PCT/US03/21280.
  • Non-Final Office Action issued Mar. 10, 2008 in U.S. Appl. No. 11/160,627.
  • Final Office Action issued Jun. 24, 2008 in U.S. Appl. No. 11/160,627.
  • Advisory Action issued Aug. 6, 2008 in U.S. Appl. No. 11/160,627.
  • Non-Final Office Action issued Jul. 8, 2005 in U.S. Appl. No. 10/708,839.
  • Final Office Action issued Nov. 21, 2005 in U.S. Appl. No. 10/708,839.
  • Advisory Action issued Feb. 9, 2006 in U.S. Appl. No. 10/708,839.
  • Non-Final Office Action issued May 2, 2006 in U.S. Appl. No. 10/708,839.
  • Final Office Action issued Jan. 25, 2007 in U.S. Appl. No. 10/708,839.
  • Notice of Abandonment issued Oct. 11, 2007 in U.S. Appl. No. 10/708,839.
  • Non-Final Office Action issued Sep. 17, 2006 in U.S. Appl. No. 10/708,585.
  • Notice of Allowance issued May 11, 2007 in U.S. Appl. No. 10/708,585.
  • Non-Final Office Action issued Nov. 28, 2005 in U.S. Appl. No. 10/708,823.
  • Final Office Action issued May 17, 2006 in U.S. Appl. No. 10/708,823.
  • Notice of Abandonment issued Jan. 5, 2007 in U.S. Appl. No. 10/708,823.
  • Non-Final Office Action issued May 13, 2008 in U.S. Appl. No. 10/708,545.
  • ISR/WO dated Aug. 19, 2008 for PCT/US05/07905.
  • Non-Final Office Action issued Sep. 17, 2006 in U.S. Appl. No. 10/708,550.
  • Notice of Allowance issued May 11, 2007 in U.S. Appl. No. 10/708,550.
  • ISR/WO dated Feb. 16, 2007 for PCT/US05/36848.
  • IPRP (Ch 1) dated Apr. 26, 2007 for PCT/US05/36848.
  • Non-Final Office Action issued Apr. 4, 2007 in U.S. Appl. No. 10/711,965.
  • Non-Final Office Action issued Oct. 16, 2007 in U.S. Appl. No. 10/711,965.
  • Final Office Action issued Mar. 28, 2008 in U.S. Appl. No. 10/711,965.
  • Advisory Action issued Jul. 31, 2008 in U.S. Appl. No. 10/711,965.
  • Final Office Action issued Aug. 18, 2008 in U.S. Appl. No. 10/711,965.
  • Non-Final Office Action issued May 4, 2006 in U.S. Appl. No. 10/711,970.
  • Notice of Allowance issued Feb. 2, 2007 in U.S. Appl. No. 10/711,970.
  • ISR/WO dated Aug. 17, 2006 for PCT/US05/36828.
  • IPRP (Ch 1) dated Apr. 26, 2007 for PCT/US05/36828.
  • Non-Final Office Action issued Feb. 25, 2008 in U.S. Appl. No. 10/711,964.
  • Final Office Action issued Jun. 30, 2008 in U.S. Appl. No. 10/711,964.
  • Advisory Action issued Sep. 10, 2008 in U.S. Appl. No. 10/711,964.
  • Non-Final Office Action issued Oct. 3, 2006 in U.S. Appl. No. 10/711,966.
  • Final Office Action issued May 21, 2007 in U.S. Appl. No. 10/711,966.
  • Non-Final Office Action issued Dec. 11, 2007 in U.S. Appl. No. 10/711,966.
  • Non-Final Office Action issued Nov. 28, 2005 in U.S. Appl. No. 10/708,824.
  • Final Office Action issued Mar. 24, 2005 in U.S. Appl. No. 10/611,563.
  • Advisory Action issued May 18, 2005 in U.S. Appl. No. 10/611,563.
  • Non-Final Office Action issued Jul. 27, 2005 in U.S. Appl. No. 10/611,563.
  • Non-Final Office Action issued Nov. 16, 2005 in U.S. Appl. No. 10/611,563.
  • Final Office Action issued May 31, 2006 in U.S. Appl. No. 10/611,563.
  • Advisory Action issued Oct. 6, 2006 in U.S. Appl. No. 10/611,563.
  • Non-Final Office Action issued Jan. 8, 2007 in U.S. Appl. No. 10/611,563.
  • Non-Final Office Action issued Jun. 18, 2007 in U.S. Appl. No. 10/611,563.
  • Notice of Allowance issued Sep. 24, 2007 in U.S. Appl. No. 10/611,563.
  • ISR dated Mar. 26, 2004 for PCT/US03/34602.
  • WO dated Oct. 13, 2004 for PCT/US03/34602.
  • IPER dated Jan. 20, 2005 for PCT/US03/34602.
  • Office Action dated Feb. 16, 2005 for TW092131042.
  • Office Action dated May 18, 2006 for AR 041912 A1.
  • Office Action dated Mar. 8, 2007 for AR 041912 A1.
  • Non-Final Office Action issued Apr. 1, 2008 in U.S. Appl. No. 10/810,473.
  • Non-Final Office Action issued Oct. 17, 2007 in U.S. Appl. No. 10/710,611.
  • Final Office Action issued May 28, 2008 in U.S. Appl. No. 10/710,611.
  • Advisory Action issued Sep. 5, 2008 in U.S. Appl. No. 10/710,611.
  • Non-Final Office Action issued Mar. 4, 2008 in U.S. Appl. No. 10/711,720.
  • Final Office Action issued Jul. 23, 2008 in U.S. Appl. No. 10/711,720.
  • Non-Final Office Action issued Jul. 17, 2005 in U.S. Appl. No. 10/708,548.
  • Notice of Allowance issued Jan. 31, 2006 in U.S. Appl. No. 10/708,548.
  • Non-Final Office Action issued Feb. 25, 2008 in U.S. Appl. No. 10/708,569.
  • Non-Final Office Action issued Sep. 24, 2007 in U.S. Appl. No. 10/708,547.
  • Final Office Action issued Feb. 14, 2008 in U.S. Appl. No. 10/708,547.
  • Advisory Action issued Jul. 29, 2008 in U.S. Appl. No. 10/708,547.
  • Non-Final Office Action issued Mar. 22, 2006 in U.S. Appl. No. 10/708,597.
  • Final Office Action issued Oct. 10, 2006 in U.S. Appl. No. 10/708,597.
  • Restriction Requirement issued Mar. 22, 2007 in U.S. Appl. No. 10/708,597.
  • Non-Final Office Action issued Aug. 8, 2007 in U.S. Appl. No. 10/708,597.
  • Final Office Action issued Mar. 17, 2008 in U.S. Appl. No. 10/708,597.
  • Advisory Action issued Jul. 11, 2008 in U.S. Appl. No. 10/708,597.
  • Non-Final Office Action issued Nov. 1, 2007 in U.S. Appl. No. 10/746,781.
  • Final Office Action issued Jul. 10, 2008 in U.S. Appl. No. 10/746,781.
  • Ex-Parte Quayle Action issued Dec. 14, 2005 in U.S. Appl. No. 10/708,549.
  • Notice of Allowance issued May 8, 2006 in U.S. Appl. No. 10/708,549.
  • Non-Final Office Action issued May 17, 2007 in U.S. Appl. No. 10/810,469.
  • Final Office Action issued Jan. 11, 2008 in U.S. Appl. No. 10/810,469.
  • Advisory Action issued Apr. 30, 2008 in U.S. Appl. No. 10/810,469.
  • Notice of Allowance issued Aug. 5, 2008 in U.S. Appl. No. 10/810,469.
  • Final Office Action issued Jul. 28, 2005 in U.S. Appl. No. 10/710,307.
  • Final Office Action issued Nov. 21, 2005 in U.S. Appl. No. 10/710,307.
  • Advisory Action issued Feb. 10, 2006 in U.S. Appl. No. 10/710,307.
  • Non-Final Office Action issued May 2, 2006 in U.S. Appl. No. 10/710,307.
  • Final Office Action issued Oct. 10, 2006 in U.S. Appl. No. 10/710,307.
  • Advisory Action issued Jan. 5, 2007 in U.S. Appl. No. 10/710,307.
  • Non-Final Office Action issued Apr. 10, 2007 in U.S. Appl. No. 10/710,307.
  • Notice of Allowance issued Oct. 4, 2007 in U.S. Appl. No. 10/710,307.
  • Supplemental Notice of Allowance issued Nov. 8, 2007 in U.S. Appl. No. 710,307.
  • Final Office Action issued May 17, 2006 in U.S. Appl. No. 10/708,824.
  • Notice of Abandonment issued Jan. 5, 2007 in U.S. Appl. No. 10/708,824.
  • Non-Final Office Action issued Dec. 13, 2005 in U.S. Appl. No. 10/708,825.
  • Final Office Action issued May 11, 2006 in U.S. Appl. No. 10/708,825.
  • Notice of Abandonment issued Jan. 25, 2007 in U.S. Appl. No. 10/708,825.
  • Non-Final Office Action issued Nov. 29, 2005 in U.S. Appl. No. 10/708,826.
  • Final Office Action issued May 17, 2006 in U.S. Appl. No. 10/708,826.
  • Notice of Abandonment issued Jan. 5, 2007 in U.S. Appl. No. 10/708,826.
  • Non-Final Office Action issued Jan. 10, 2006 in U.S. Appl. No. 10/708,827.
  • Final Office Action issued May 9, 2006 in U.S. Appl. No. 10/708,827.
  • Notice of Abandonment issued Jan. 5, 2007 in U.S. Appl. No. 10/708,827.
  • Non-Final Office Action issued Jan. 27, 2006 in U.S. Appl. No. 10/708,828.
  • Final Office Action issued Jul. 21, 2006 in U.S. Appl. No. 10/708,828.
  • Notice of Abandonment issued Mar. 22, 2007 in U.S. Appl. No. 10/708,828.
  • Non-Final Office Action issued Dec. 15, 2005 in U.S. Appl. No. 10/708,829.
  • Final Office Action issued May 25, 2006 in U.S. Appl. No. 10/708,829.
  • Notice of Abandonment issued Jan. 5, 2007 in U.S. Appl. No. 10/708,829.
  • Non-Final Office Action issued Nov. 27, 2006 in U.S. Appl. No. 10/708,832.
  • Notice of Abandonment issued Aug. 16, 2007 in U.S. Appl. No. 10/708,832.
  • Non-Final Office Action issued Jan. 20, 2006 in U.S. Appl. No. 10/708,834.
  • Final Office Action issued May 25, 2006 in U.S. Appl. No. 10/708,834.
  • Notice of Abandonment issued Jan. 5, 2007 in U.S. Appl. No. 10/708,834.
  • Non-Final Office Action issued Dec. 16, 2005 in U.S. Appl. No. 10/708,835.
  • Final Office Action issued May 17, 2006 in U.S. Appl. No. 10/708,835.
  • Notice of Abandonment issued Jan. 5, 2007 in U.S. Appl. No. 10/708,835.
  • Non-Final Office Action issued Dec. 16, 2005 in U.S. Appl. No. 10/708,836.
  • Final Office Action issued May 25, 2006 in U.S. Appl. No. 10/708,836.
  • Notice of Abandonment issued Jan. 5, 2007 in U.S. Appl. No. 10/708,836.
  • Non-Final Office Action issued Aug. 8, 2005 in U.S. Appl. No. 10/708,838.
  • Final Office Action issued Nov. 29, 2005 in U.S. Appl. No. 10/708,838.
  • Advisory Action issued Feb. 9, 2006 in U.S. Appl. No. 10/708,838.
  • Non-Final Office Action issued Apr. 18, 2006 in U.S. Appl. No. 10/708,838.
  • Notice of Abandonment issued Nov. 1, 2006 in U.S. Appl. No. 10/708,838.
  • ISR/WO issued Jan. 29, 2008 in PCT/US06/22542.
  • Non-Final Office Action issued Nov. 1, 2007 in U.S. Appl. No. 10/711,613.
  • Restriction Requirement issued Aug. 17, 2008 in U.S. Appl. No. 10/711,613.
  • Non-Final Office Action issued Dec. 9, 2003 in U.S. Appl. No. 10/242,584.
  • Notice of Allowance issued Jul. 9, 2004 in U.S. Appl. No. 10/242,584.
  • Office Action dated May 23, 2008 for JP2004-543166.
  • ISR dated Mar. 17, 2003 for PCT/US02/32653.
  • WO dated Aug. 27, 2004 for PCT/US02/32653.
  • IPER dated Jan. 10, 2005 for PCT/US02/32653.
  • Ex-Parte Quayle Action issued Jun. 6, 2005 in U.S. Appl. No. 10/710,484.
  • Notice of Allowance issued Aug. 2, 2005 in U.S. Appl. No. 10/710,484.
  • Non-Final Office Action issued May 17, 2005 in U.S. Appl. No. 10/711,773.
  • Final Office Action issued Nov. 1, 2005 in U.S. Appl. No. 10/711,773.
  • Advisory Action issued Feb. 15, 2006 in U.S. Appl. No. 10/711,773.
  • Notice of Allowance issued May 17, 2006 in U.S. Appl. No. 10/711,773.
  • ISR/WO dated Jun. 20, 2005 for PCT/US05/07195.
  • IPRP (Ch 1) dated Apr. 19, 2007 for PCT/US05/07195.
  • Non-Final Office Action issued Oct. 10, 2006 in U.S. Appl. No. 10/710,325.
  • Notice of Abandonment issued Jun. 4, 2007 in U.S. Appl. No. 10/710,325.
  • Non-Final Office Action issued Mar. 22, 2006 in U.S. Appl. No. 10/710,326.
  • Final Office Action issued Oct. 10, 2006 in U.S. Appl. No. 10/710,326.
  • Advisory Action issued Jan. 12, 2007 in U.S. Appl. No. 10/710,326.
  • Non-Final Office Action issued May 1, 2007 in U.S. Appl. No. 10/710,326.
  • Notice of Allowance issued Oct. 4, 2007 in U.S. Appl. No. 10/710,326.
  • Supplemental Notice of Allowance issued Nov. 8, 2007 in U.S. Appl. No. 10/710,326.
  • Non-Final Office Action issued May 1, 2008 in U.S. Appl. No. 11/861,347.
  • Non-Final Office Action issued May 2, 2008 in U.S. Appl. No. 11/861,351.
  • Non-Final Office Action issued May 1, 2008 in U.S. Appl. No. 11/861,354.
  • Non-Final Office Action issued May 25, 2007 in U.S. Appl. No. 10/710,327.
  • Notice of Allowance issued Nov. 13, 2007 in U.S. Appl. No. 10/710,327.
  • Non-Final Office Action issued May 1, 2008 in U.S. Appl. No. 11/861,463.
  • Non-Final Office Action issued May 8, 2008 in U.S. Appl. No. 11/861,481.
  • Non-Final Office Action issued Sep. 21, 2006 in U.S. Appl. No. 10/710,328.
  • Notice of Abandonment issued Jun. 28, 2007 in U.S. Appl. No. 10/710,328.
  • Non-Final Office Action issued Sep. 19, 2006 in U.S. Appl. No. 10/710,329.
  • Notice of Abandonment issued Aug. 23, 2007 in U.S. Appl. No. 10/710,329.
  • Non-Final Office Action issued Mar. 9, 2006 in U.S. Appl. No. 10/710,330.
  • Notice of Abandonment issued Nov. 17, 2006 in U.S. Appl. No. 10/710,330.
  • Non-Final Office Action issued Jul. 29, 2005 in U.S. Appl. No. 10/710,331.
  • Final Office Action issued Nov. 29, 2005 in U.S. Appl. No. 10/710,331.
  • Advisory Action issued Feb. 9, 2006 in U.S. Appl. No. 10/710,331.
  • Non-Final Office Action issued May 3, 2006 in U.S. Appl. No. 10/710,331.
  • Notice of Abandonment issued Jan. 10, 2007 in U.S. Appl. No. 10/710,331.
  • Non-Final Office Action issued Jul. 19, 2005 in U.S. Appl. No. 10/710,332.
  • Final Office Action issued Nov. 21, 2005 in U.S. Appl. No. 10/710,332.
  • Advisory Action issued Feb. 10, 2006 in U.S. Appl. No. 10/710,332.
  • Non-Final Office Action issued May 3, 2006 in U.S. Appl. No. 10/710,332.
  • Final Office Action issued Oct. 10, 2006 in U.S. Appl. No. 10/710,332.
  • Advisory Action issued Jan. 5, 2007 in U.S. Appl. No. 10/710,332.
  • Non-Final Office Action issued Apr. 20, 2007 in U.S. Appl. No. 10/710,332.
  • Notice of Allowance issued Oct. 4, 2007 in U.S. Appl. No. 10/710,332.
  • Supplemental Notice of Allowance issued Nov. 8, 2007 in U.S. Appl. No. 10/710,332.
  • Non-Final Office Action issued May 2, 2008 in U.S. Appl. No. 11/861,600.
  • Non-Final Office Action issued May 1, 2008 in U.S. Appl. No. 11/861,626.
  • Non-Final Office Action issued Jan. 27, 2005 in U.S. Appl. No. 10/710,334.
  • Final Office Action issued Sep. 30, 2005 in U.S. Appl. No. 10/710,334.
  • Advisory Action issued Dec. 19, 2005 in U.S. Appl. No. 10/710,334.
  • Non-Final Office Action issued Apr. 10, 2006 in U.S. Appl. No. 10/710,334.
  • Notice of Abandonment issued Nov. 6, 2006 in U.S. Appl. No. 10/710,334.
  • Non-Final Office Action issued Aug. 8, 2005 in U.S. Appl. No. 10/710,335.
  • Final Office Action issued Dec. 15, 2005 in U.S. Appl. No. 10/710,335.
  • Advisory Action issued Mar. 8, 2006 in U.S. Appl. No. 10/710,335.
  • Non-Final Office Action issued May 9, 2006 in U.S. Appl. No. 10/710,335.
  • Final Office Action issued Oct. 19, 2006 in U.S. Appl. No. 10/710,335.
  • Advisory Action issued Jan. 12, 2007 in U.S. Appl. No. 10/710,335.
  • Non-Final Office Action issued Apr. 19, 2007 in U.S. Appl. No. 10/710,335.
  • Notice of Allowance issued Sep. 19, 2007 in U.S. Appl. No. 10/710,335.
  • Non-Final Office Action issued Feb. 28, 2006 in U.S. Appl. No. 10/709,815.
  • Notice of Allowance issued Sep. 26, 2006 in U.S. Appl. No. 10/709,815.
  • Non-Final Office Action issued Jul. 10, 2008 in U.S. Appl. No. 11/163,595.
  • Non-Final Office Action issued Jul. 12, 2005 in U.S. Appl. No. 10/708,822.
  • Final Office Action issued Nov. 2, 2005 in U.S. Appl. No. 10/708,822.
  • Advisory Action issued Dec. 20, 2005 in U.S. Appl. No. 10/708,822.
  • Non-Final Office Action issued Apr. 17, 2006 in U.S. Appl. No. 10/708,822.
  • Final Office Action issued Oct. 19, 2006 in U.S. Appl. No. 10/708,822.
  • Advisory Action issued Jan. 10, 2007 in U.S. Appl. No. 10/708,822.
  • Non-Final Office Action issued Apr. 23, 2007 in U.S. Appl. No. 10/708,822.
  • Notice of Allowance issued Sep. 19, 2007 in U.S. Appl. No. 10/708,822.
  • ISR/WO dated Nov. 16, 2005 for PCT/US05/09452.
  • IPRP dated Aug. 16, 2006 for PCT/US05/09452.
  • IPRP dated Jan. 5, 2007 for PCT/US05/09452.
  • Non-Final Office Action issued Jan. 22, 2008 in U.S. Appl. No. 11/858,958.
  • Non-Final Office Action issued Jun. 6, 2005 in U.S. Appl. No. 10/708,830.
  • Non-Final Office Action issued Oct. 4, 2005 in U.S. Appl. No. 10/708,830.
  • Notice of Allowance issued Mar. 2, 2006 in U.S. Appl. No. 10/708,830.
  • Supplemental Notice of Allowance issued Aug. 4, 2006 in U.S. Appl. No. 10/708,830.
  • Non-Final Office Action issued May 15, 2007 in U.S. Appl. No. 10/708,831.
  • Notice of Allowance issued Oct. 31, 2007 in U.S. Appl. No. 10/708,831.
  • Notice of Abandonment issued Mar. 6, 2008 in U.S. Appl. No. 10/708,831.
  • Non-Final Office Action issued Jun. 6, 2005 in U.S. Appl. No. 10/708,833.
  • Notice of Allowance issued Dec. 9, 2005 in U.S. Appl. No. 10/708,833.
  • Supplemental Notice of Allowance issued Feb. 23, 2006 in U.S. Appl. No. 10/708,833.
  • Non-Final Office Action issued Mar. 22, 2006 in U.S. Appl. No. 10/708,837.
  • Final Office Action issued Oct. 10, 2006 in U.S. Appl. No. 10/708,837.
  • Advisory Action issued Jan. 12, 2007 in U.S. Appl. No. 10/708,837.
  • Non-Final Office Action issued Apr. 23, 2007 in U.S. Appl. No. 10/708,837.
  • Notice of Allowance issued Oct. 12, 2007 in U.S. Appl. No. 10/708,837.
  • Supplemental Notice of Allowance issued Dec. 20, 2007 in U.S. Appl. No. 10/708,837.
  • Non-Final Office Action issued Dec. 11, 2007 in U.S. Appl. No. 11/851,533.
  • Final Office Action issued Jul. 25, 2008 in U.S. Appl. No. 11/851,533.
  • Advisory Action issued Aug. 29, 2008 in U.S. Appl. No. 11/851,533.
  • Non-Final Office Action issued Jan. 4, 2008 in U.S. Appl. No. 11/851,556.
  • Final Office Action issued Jul. 31, 2008 in U.S. Appl. No. 11/851,556.
  • Non-Final Office Action issued Jan. 10, 2008 in U.S. Appl. No. 10/708,840.
  • Final Office Action issued Jul. 17, 2008 in U.S. Appl. No. 10/708,840.
  • Advisory Action issued Sep. 5, 2008 in U.S. Appl. No. 10/708,840.
  • Non-Final Office Action issued Feb. 8, 2008 in U.S. Appl. No. 11/851,580.
  • Non-Final Office Action issued Feb. 11, 2008 in U.S. Appl. No. 11/851,623.
  • Restriction Requirement issued Aug. 20, 2008 in U.S. Appl. No. 11/851,623.
  • Non-Final Office Action issued Feb. 15, 2008 in U.S. Appl. No. 11/858,393.
  • Non-Final Office Action issued Jan. 30, 2006 in U.S. Appl. No. 10/708,841.
  • Final Office Action issued May 25, 2006 in U.S. Appl. No. 10/708,841.
  • Notice of Allowance issued Oct. 6, 2006 in U.S. Appl. No. 10/708,841.
  • Non-Final Office Action issued Mar. 11, 2008 in U.S. Appl. No. 11/164,352.
  • Final Office Action issued Aug. 18, 2008 in U.S. Appl. No. 11/164,352.
  • ISR/WO dated Jul. 11, 2008 for PCT/US06/07570.
  • Non-Final Office Action issued Aug. 11, 2004 in U.S. Appl. No. 10/611,563.
  • Supplemental Notice of Allowance issued Oct. 25, 2007 in U.S. Appl. No. 10/710,335.
  • Non-Final Office Action issued May 1, 2008 in U.S. Appl. No. 11/862,268.
  • Non-Final Office Action issued Aug. 4, 2008 in U.S. Appl. No. 11/306,617.
  • ISR/WO dated Jul. 9, 2008 for PCT/US06/45362.
  • Non-Final Office Action issued Jun. 24, 2008 in U.S. Appl. No. 11/161,295.
  • Non-Final Office Action issued Sep. 8, 2005 in U.S. Appl. No. 10/906,732.
  • Final Office Action issued Mar. 8, 2006 in U.S. Appl. No. 10/906,732.
  • Advisory Action issued Jul. 5, 2006 in U.S. Appl. No. 10/906,732.
  • Notice of Allowance issued Aug. 11, 2006 in U.S. Appl. No. 10/906,732.
  • Non-Final Office Action issued Oct. 15, 2007 in U.S. Appl. No. 11/161,105.
  • Final Office Action issued Apr. 21, 2008 in U.S. Appl. No. 11/161,105.
  • Notice of Allowance issued Jul. 3, 2008 in U.S. Appl. No. 11/161,105.
  • Non-Final Office Action issued Apr. 11, 2008 in U.S. Appl. No. 11/552,886.
  • Final Office Action issued Aug. 6, 2008 in U.S. Appl. No. 11/552,886.
  • Advisory Action issued Sep. 18, 2008 in U.S. Appl. No. 11/552,886.
  • Office Action dated Mar. 6, 2008 for AU2005270228.
  • Office Action dated Jun. 18, 2008 for AU2005270228.
  • Office Action dated Apr. 14, 2008 for CA2570739.
  • ISR/WO dated Oct. 10, 2006 for PCT/US05/19388.
  • IPRP dated Mar. 15, 2007 for PCT/US05/19388.
  • Non-Final Office Action issued Feb. 26, 2008 in U.S. Appl. No. 11/859,153.
  • Notice of Allowance issued Jun. 20, 2008 in U.S. Appl. No. 11/859,153.
  • Examination Report dated Jun. 22, 2007 for GB 0700319.7.
  • Examination Report dated Nov. 22, 2007 for GB 0700319.7.
  • Search Report dated May 23, 2008 for GB 0700319.7.
  • Non-Final Office Action issued Feb. 26, 2008 in U.S. Appl. No. 11/859,171.
  • Notice of Allowance issued Jun. 19, 2008 in U.S. Appl. No. 11/859,171.
  • Examination Report dated Jun. 16, 2008 for SG200608843-9.
  • Non-Final Office Action issued Jul. 29, 2005 in U.S. Appl. No. 10/710,308.
  • Final Office Action issued Nov. 29, 2005 in U.S. Appl. No. 10/710,308.
  • Advisory Action issued Feb. 10, 2006 in U.S. Appl. No. 10/710,308.
  • Non-Final Office Action issued May 2, 2006 in U.S. Appl. No. 10/710,308.
  • Final Office Action issued Oct. 10, 2006 in U.S. Appl. No. 10/710,308.
  • Advisory Action issued Jan. 8, 2007 in U.S. Appl. No. 10/710,308.
  • Non-Final Office Action issued May 1, 2007 in U.S. Appl. No. 10/710,308.
  • Notice of Allowance issued Sep. 26, 2007 in U.S. Appl. No. 10/710,308.
  • Supplemental Notice of Allowance issued Dec. 11, 2007 in U.S. Appl. No. 10/710,308.
  • Non-Final Office Action issued Mar. 18, 2008 in U.S. Appl. No. 11/860,704.
  • Notice of Allowance issued Jul. 3, 2008 in U.S. Appl. No. 11/860,704.
  • Non-Final Office Action issued Apr. 3, 2008 in U.S. Appl. No. 11/860,726.
  • Notice of Allowance issued Jul. 14, 2008 in U.S. Appl. No. 11/860,726.
  • Non-Final Office Action issued Jul. 19, 2005 in U.S. Appl. No. 10/710,309.
  • Final Office Action issued Nov. 21, 2005 in U.S. Appl. No. 10/710,309.
  • Advisory Action issued Feb. 10, 2006 in U.S. Appl. No. 10/710,309.
  • Non-Final Office Action issued May 2, 2006 in U.S. Appl. No. 10/710,309.
  • Notice of Abandonment issued Dec. 19, 2006 in U.S. Appl. No. 10/710,309.
  • Non-Final Office Action issued May 6, 2005 in U.S. Appl. No. 10/710,310.
  • Final Office Action issued Oct. 19, 2005 in U.S. Appl. No. 10/710,310.
  • Advisory Action issued Dec. 29, 2005 in U.S. Appl. No. 10/710,310.
  • Non-Final Office Action issued Apr. 5, 2006 in U.S. Appl. No. 10/710,310.
  • Notice of Abandonment issued Oct. 20, 2006 in U.S. Appl. No. 10/710,310.
  • Non-Final Office Action issued Sep. 19, 2006 in U.S. Appl. No. 10/710,311.
  • Notice of Abandonment issued Jun. 28, 2007 in U.S. Appl. No. 10/710,311.
  • Non-Final Office Action issued Feb. 9, 2006 in U.S. Appl. No. 10/710,315.
  • Final Office Action issued Jul. 13, 2006 in U.S. Appl. No. 10/710,315.
  • Notice of Abandonment issued Apr. 20, 2007 in U.S. Appl. No. 10/710,315.
  • Non-Final Office Action issued Feb. 9, 2006 in U.S. Appl. No. 10/710,317.
  • Final Office Action issued Jul. 18, 2006 in U.S. Appl. No. 10/710,317.
  • Notice of Abandonment issued Mar. 22, 2007 in U.S. Appl. No. 10/710,317.
  • Non-Final Office Action issued Sep. 19, 2006 in U.S. Appl. No. 10/710,319.
  • Notice of Abandonment issued Aug. 9, 2007 in U.S. Appl. No. 10/710,319.
  • Non-Final Office Action issued Mar. 9, 2006 in U.S. Appl. No. 10/710,323.
  • Notice of Abandonment issued Dec. 12, 2006 in U.S. Appl. No. 10/710,323.
  • Non-Final Office Action issued Oct. 10, 2006 in U.S. Appl. No. 10/710,324.
  • Notice of Abandonment issued Oct. 11, 2007 in U.S. Appl. No. 10/710,324.
  • American Express, “Private Payments (SM) ; A New Level of Security from American Express,” American Express Website, Cards.
  • “ISO Standards,” available from http://www.iso.ch/projects/loading.html.
  • hllp:l/www.semiconductors.phillips.com/news/contenl/file—878.hlml, Apr. 7, 2003.
  • hllp:l/www.palowireless.com/infotoolh/whatis.asp, Apr. 28, 2003.
  • hllp:l/www.palowireless.com/infotoolh/lutorial.asp, Apr. 28, 2003.
  • hllp:l/www.palowireless.com/infotoolh/lutorial/profiles.asp, Apr. 28, 2003.
  • http://www.palowireless.com/infotooth/lutorial/radio.asp, Apr. 28, 2003.
  • http://www.palowireless.com/infotooth/lutorial/baseband.asp, Apr. 28, 2003.
  • http://www.palowireless.com/infotooth/lutorial/Imp.asp, Apr. 28, 2003.
  • http://www.palowireless.com/infotooth/lutorial/hci.asp, Apr. 28, 2003.
  • http://www.palowireless.com/infotooth/lutoria1/12cap.asp, Apr. 28, 2003.
  • http://www.palowireless.com/infotooth/lutorial/rfcomm.asp, Apr. 28, 2003.
  • http://www.palowireless.com/infotooth/lutorial/sdp.asp, Apr. 28, 2003.
  • http://www.palowireless.com/infotooth/lutorial/k1—gap.asp, Apr. 28, 2003.
  • “Sony, Phillips to Test RFID Platform”, RFID Journal, May 8, 2003.
  • US Banker, Article 5, 1995, http://www.banking.com/us-banker/art 5.
  • “Smart Card Technology and Applications”; http://disc.cba/uh/edul-rhirsch/fall96/lara.htm (8 pages).
  • Financial Technology International Bulletin, V14, n1, p. 4, Sep. 1996.
  • Green, Thomas C., “American Express Offers temporary CC numbers for the web,” Sep. 9, 2000, The Register, www.theregister.c.uk/c.
  • CNN.com, U.S. News, “American Express to offer disposable credit card numbers,” Sep. 8, 2000, Associated Press, www.cnn.c.
  • American Express, “Private Payments (SM) ; A New Level of Security from American Express,” American Express Website, Cards, Aug. 22, 2001.
  • Martin, Zack, “One-Time Numbers Stop Web Hackers From Pilfering Data,” Jan. 2001, Card Marketing, Thomson Financial, www.c rdf rum.c.
  • The Dollar Stretcher, “Disposable Credit Card Numbers,” Jan. 2001, CardRatings.org, www.stretcher.c.
  • ISO/IEC 7816-6:1996(E)—First Edition—May 15, 1996.
  • ISO/IEC 7816-4:1995(E)—First Edition—Sep. 1, 1995.
  • Goldman, J., “Internet Security, The Next Generation, When Software Encryption is not Enough,” Web Techniques, Nov. 1997, pp. 43-46.
  • Simmons, J., “Smart Cards Hold the Key to Secure Internet Commerce,” EC World, Dec. 1998, pp. 36-38.
  • Wayner, P., “Digital Cash,” AP Professional, 1996, pp. 76-83, 85-100.
  • “ISO Standards,” available from http://www.iso.ch/projects/loading.html, Oct. 18, 2000.
  • Turban, et al., “Using Smartcards in Electronic Commerce,” Proc. 31st Annual Hawaii Inter. Conf. on System Sciences, vol. 4, 1998, pp. 62-69.
  • Dhem, et al., “SCALPS: Smart Card for Limited Payment Systems,” IEEE Micro, Jun. 1996, pp. 42-51.
  • Smith, M.T., “Smart Cards: Integrating for Portable Complexity,” Computer-Integrated Engineering, Aug. 1998, pp. 110-115.
  • PR Newswire (press release), “Providian Launches Nation's First Clear Chip Card,” Sep. 12, 2000. The press release may be related to the art of the invention, but based upon the information in the press release, it is unclear if the press release is prior art. However, in an abundance of caution the Applicant desires to put the press release into the file wrapper.
  • Geer, et al., “Token-Mediated Certification and Electronic Commerce,” Proc. 2nd USENIX Workshop on Electronic Commerce, Nov. 18-21, 1996, pp. 13-22.
  • Gobioff, et al., “Smart Cards in Hostile Environments,” Proc. 2nd USENIX Workshop in Electronic Commerce, Nov. 18-21, 1996, pp. 23-28.
  • Fancher, C.H., “In Your Pocket Smartcards,” IEEE Spectrum, Feb. 1997, pp. 47-53.
  • Blythe, I., “Smarter, More Secure Smartcards,” BYTE, Jun. 1997, pp. 63-64.
  • Leach, Dr. J., “Dynamic Authentication for Smartcards,” Computers and Security, vol. 14, No. 5, 1995, pp. 385-389.
  • Wu, et al., “Authenticating Passwords Over an Insecure Channel,” Computers and Security, vol. 15, No. 5, 1996, pp. 431-439.
  • Manninger, et al., “Adapting an Electronic Purse for Internet Payments,” ACISP '98 Proceedings, Jul. 13-15, 1998, pp. 205-214.
  • Yan, et al., “Banking on the Internet and Its Applications,” Proc. 13th Annual Hawaii International Conference on System Sciences, vol. 4, 1997, pp. 275-284.
  • Transport Layer Security Working Group, “The SSL Protocol, Version 3.0,” Nov. 18, 1996 (also available at http://home.netscape.com/eng/ssl3/draft302.txt).
  • Business Wire (press release), “Master Card E-Wallet,” Jul. 11, 2000.
  • Obongo.com Website, “Obongo,” Aug. 8, 2000 (Description of wallet toolbar also available at http://www.obongo.com/chabi/website/index.htm).
Patent History
Patent number: RE45416
Type: Grant
Filed: Jun 15, 2012
Date of Patent: Mar 17, 2015
Assignee: Xatra Fund MX, LLC (Wilmington, DE)
Inventors: Fred Bishop (Glendale, AZ), Peter D. Saunders (Salt Lake City, UT)
Primary Examiner: Daniel Hess
Application Number: 13/524,685
Classifications
Current U.S. Class: Credit Or Identification Card Systems (235/380); Authentication (e.g., Identity) (340/5.8); Commodity (e.g., Vending) (340/5.9); Intelligent Token (713/172)
International Classification: H04L 9/32 (20060101); H04B 1/00 (20060101);