The systems and methods of the invention relate to transponder devices and related technologies.
Radio-frequency identification (RFID) devices are known. In particular, it is known to provide a sticker, adapted to be affixed to a surface, that includes an RFID transponder. The RFID transponder may interface with various other devices, and is provided appropriate circuitry and memory to perform desired tasks.
However, known RFID devices are lacking. In particular, known RFID devices, and RFID systems, do not provide desired capabilities to be altered in the field, i.e., after the RFID device has been put into use by a customer, for example. The invention addresses this and other shortcomings of known technology.
Transponder alteration systems and methods are provided for altering the state of a transponder device in the field, the transponder device used by a transponder user. The system may comprise an alteration portion, disposed in a banking system, the alteration portion inputting an alteration request from a user for an additional application to be disposed upon the user's transponder device. The processing of the alteration portion may include (1) accessing a database to retrieve data to process the alteration request; (2) generating an information packet for the user based on the retrieved data, and outputting the information packet to the user; and (3) generating a data packet based on the retrieved data, and outputting the data packet to an interim device, such that the interim device interfaces with the transponder device to transmit the data packet to the transponder device.
The invention can be more fully understood by reading the following detailed description together with the accompanying drawings, in which like reference indicators are used to designate like elements, and in which:
Hereinafter, aspects of methods and systems in accordance with various embodiments of the invention will be described. As used herein, any term in the singular may be interpreted to be in the plural, and alternatively, any term in the plural may be interpreted to be in the singular.
The invention provides an RFID device that is readily alterable in the field. Aspects of the invention include both electronic/circuitry attributes, as well as the particular physical components used in the system. In particular, the RFID device may be in the form of a sticker attached to a cell phone. The invention may include the RFID device being provided with a chip that includes multiple file structures. The file structures may be dedicated to respective features, applications and/or operations. Each file structure may be provided its own key management component.
In particular, each of the key management components may be responsible for locking or unlocking a respective application that is on the RFID device. Such an application, when in an unlocked state, provides the user with various functionality associated with the application, (e.g. a loyalty application).
Further, the invention is not limited to merely unlocking applications that are already on the RFID device. Rather, new applications may be loaded on a particular user's RFID device, i.e., on a chip of the RFID device, assuming that the particular chip is provided for such processing.
In accordance with one example of the invention, a customer is provided with the RFID device 500, i.e., the customer is provided with an RFID device or some other suitable transponder. The customer's RFID device 500 may, for example, be in the form of a sticker (an RFID sticker). The RFID sticker may be positioned on their cell phone, or some other personal item.
Illustratively, the customer, subsequent to being provided the RFID device 500, desires to participate in, i.e., subscribe to, a “loyalty” program, for example. The customer logs onto a particular web site (e.g. of a bank) and accesses their account after satisfying appropriate security measures, e.g. user id and password. Through interfacing with the web site, the customer indicates that she wishes to participate in the loyalty program, and that she wishes to use her RFID sticker in conjunction with such participation. In response, the bank's system 140 outputs instructions to the customer, and in harmony with the instructions, initiates the processing to place the requested loyalty application on the customer's RFID sticker 500.
Thereafter, in one embodiment of the invention, the bank's system 140 outputs a data packet to what might be characterized as an “interim interface device”, i.e., the interim interface device 400 of
The “interim interface device” 400 may be in a variety of forms. For example, the interim interface device may be a processing portion with power supply disposed in a sleeve, in which the cell phone is disposed, or a sticker cover, which is adhered to the cell phone with the RFID sticker placed inside, as to conceal the sticker. The sleeve might be constructed of suitable elastomer material, for example, so as to both secure the cell phone and afford for embedding of the processing portion in the sleeve. Alternatively, the interim interface device might be the user's computer, or the cell phone itself (if provided with a suitable processing portion). The interim interface device 400 might be integrated with the cell phone (or other device) processing portion. Accordingly, the cell phone 520 (or other device) might talk directly to the transponder device 500. Alternatively, the interim interface device 400 might be constituted by a separate processing portion that is disposed with the cell phone processing portion, such as in the case 510. Alternatively, the interim interface device might be a permanently disposed system to which a user must go (to have the application loaded to their RFID device). For example, a user might have to go to a metro station (to load a metro application via a suitable reader, over which the phone is passed)). In one embodiment of the invention, processing may be used to both trigger the loading of an application, as well as convey when an application load is completed.
The interim interface device 400 may be provided with an interface 490, i.e., a user interface. The interface 490 may be provided to convey (to a user) the status of operation or state of the interim interface device 400. For example, the interface 490 might reflect whether the interim interface device 400 is interfacing with the alteration portion 300, the transponder device 500, or some other device. The interface 490 may convey the progress of such communications. In general, the interface 490 may be provided to convey any aspect of the operation of the interim interface device 400. For example, in order to communicate, the interface 490 might include a display, a text display, a status bar, lights, a screen, a character display (e.g. text), and/or other suitable interface mechanism. As described above, the invention might be used in conjunction with a cell phone. However, the invention might also be used in conjunction with other devices, such as PDAs. Further, while Bluetooth technology might be used as described above, any suitable personal area or other network might be used so as to provide communication between the alteration portion 300, the interim interface device 400, the transponder device 500 and other processing components.
The invention may include various other features as described below. The RFID device might display certain attributes under particular conditions (such as when a particular application in the RFID device is utilized, when particular processing is performed, when an account balance is low, or when a particular account is accessed, for example). A button (or other interface) might be provided on the RFID device to control processing, e.g. what account is to be debited.
As described above, the invention provides an RFID device that is readily alterable in the field. Aspects of the invention include both electronic/circuitry attributes, as well as the particular physical components and methodology used in the system. The adaptable RFID device as described herein may be used in a variety of applications. However, in particular, the RFID device described herein may be used to effect financial transactions.
In order to provide further context of the invention, hereinafter, the processing of an RFID transaction will illustratively be described with reference to
In embodiments, as described in detail below, transponder 500 may be programmable and able to receive program modules, update programmable instructions, unlock programs or instructions, as well as to have electronic memory erased or updated during transactions, for example. Receiver 106 may include an electromagnetic antenna to couple with transponder 500, generally within the range of a few feet of the device.
In the embodiment illustrated in
In the operation of the transponder device 500, a user approaches the receiver 106 at the point of sale device 108 to initiate and complete a purchase or other transaction, such as at a restaurant or grocery market checkout line, or some other point of sale.
In the embodiment illustrated in
In the implementation of this embodiment of the invention, receiver 106 is configured to receive the account table 532 and apply an amount being executed at the point of sale device 108 to the account reflected within the account table 532. For instance, a patron who has subscribed to an account according to the system of the invention may approach receiver 106 in a restaurant line and wave a cell phone, watch or other article containing transponder 500 in proximity of the receiver 106. When transponder 500 comes within range of receiver 106, transponder 500 may be inductively coupled to the coils of an electromagnetic antenna within receiver 106 inducing electrical energy within transponder 500, to establish the RF link 104 with the receiver 106. Upon activation of transponder 500 and radiation of transponder ID to the receiver 106, the receiver 106 may respond with an acknowledge signal to the transponder 500. The point of sale device 108 may indicate on a display screen or otherwise that a transaction is ready to be commenced. Once the point of sale device 108 generates total amount due for the transaction, the receiver 106 may interrogate transponder 500 to obtain account table information from account table 532 for application to the sale.
For instance, if a patron has purchased a meal in a restaurant line at point of sale device 108, the total purchase price may be validated for completion of the transaction. Conversely, if the amount of the transaction cannot be validated, the point of sale device 108 may indicate “cash required” or another message that transponder validation or authorization has failed. If the transaction amount is validated, receiver 106 enters the transaction amount and transmits the revised account table 532 information over the RF link 104 to the transponder 500. A transaction completion signal may be emitted by receiver 106, which in one embodiment may turn off or decouple the transponder 500 via RF link 104.
In further explanation of the above transaction processing, overall transaction processing is illustrated in the flowchart of
In step 612, transaction information is input from the transponder. After step 612, the process passes to step 613.
In step 613, an end of transaction signal is sent to transponder 500. Then, in step 614, transponder 500 decouples from the receiver 106.
In step 615 of
If the account to be applied to the pending transaction is validated at step 614, in step 618, the point of sale device 108 and receiver 106 communicate with transponder 500 to indicate transaction acceptance, and modify information within account table 532 if appropriate. In step 624, processing ends.
Accordingly, as set forth above, the processing of an transponder/RFID transaction was illustratively described with reference to
In accordance with embodiments of the invention, the invention provides a transponder device 500 that is alterable in the field. However, prior to being disposed in the field and used by customer, the transponder device 500 is issued to a customer and registered in some manner. Relatedly,
In particular (in addition to various other processing components, the processing system 10 of
In terms of new accounts registration as illustrated in
As shown in
In setting up a new account, the transponder ID, particulars of the user, as well as other information are transmitted from the user (at the client workstation 118) to the registration portion 100. The registration portion 100 initiates operation of the transponder device 500, and associates such operation with an account or accounts, as desired. The client workstation 118 may be in the form of various devices, including a computer, cell phone, a PDA (personal digital assistant), a BLACKBERRY, a kiosk, or other suitable device.
The account may illustratively include or be more than one type of account 124a . . . 124n, such as cash accounts, debit accounts, credit card accounts, special purpose vending accounts, telephone card accounts, or others. The registration portion 100 may validate the transponder ID 110, and interrogate a new subscriber (user) at client work station 118 to identify or select which one or more of accounts 124a . . . 124n the user wishes to associate with the transponder 500.
For instance, the registration 100 may accept a preexisting credit card number for registration with the transponder 500 and execution of future transactions. Once the new account is established, and the transponder device 500 is operational, the bank system 140 may communicate via network connection to the point of sale device 108 and receiver 106, i.e., to authorize transactions at the point of sale 108.
Accordingly,
As shown in
The alteration portion 300 includes an alteration processing portion 330, an alteration communication portion 340, and an alteration memory portion 350.
The alteration processing portion 330 performs a variety of processing, including inputting a request from a customer for an additional application to be loaded upon their transponder device, authenticating the request to determine if the customer has credentials for the particular requested application, preparing data packets to effect the placement of the new application on the customer's transponder device, and various related processing. The alteration communication portion 340 provides for the alteration portion 300 to effect various communications, such as communications with the interim interface device. The alteration memory portion 350 of the alteration portion 300 store a variety of data used in the processing of the alteration processing portion 330.
Various further features and aspects of the alteration portion 300 will be described below.
As described herein, various applications are disposed on the transponder device 500, e.g. such as a loyalty application, a transit application, and others. The applications may interface with other devices (including merchant devices) on respective frequencies. Further, the respective applications may use respective and different handshakes to interface with other devices. In accordance with one embodiment of the invention, the respective frequencies and handshakes (that will be utilized in operation of the particular application on the transponder device 500) may be coordinated ahead of time, i.e., prior to loading the file structure and/or application on the transponder device 500. Alternatively, the respective frequencies and handshakes may be coordinated in some dynamic manner. For example, the interim interface device 400 may be provided to determine which frequencies/handshakes are already in use on the transponder device 500, and provide that a new application (that is being loaded on the transponder device 500) have a different frequency/handshake. Further, in accordance with one embodiment of the invention, the frequencies and/or handshakes used by the transponder device 500 may be updated by the interim interface device 400, or other suitable device.
Relatedly, it is of course appreciated that various distinct handshakes may be utilized. That is, a first handshake may be utilized in the interface of the alteration portion 300 vis-à-vis the interim interface device 400. A further handshake may be utilized in the interface of the interim interface device 400 vis-à-vis the transponder device 500. A further handshake may be utilized in the interface of the transponder device 500 vis-à-vis a merchant device, i.e., in use of the transponder device 500.
The systems and methods of embodiments as described herein relate to the loading of a further application on a customer's transponder device. Illustratively, features of the invention are described herein with reference to a loyalty application. Various other applications may be loaded upon a customer's transponder device 500 as desired (assuming the needed file structure and other particulars are suitably provided). Thus, applications loaded on the transponder device might include a loyalty application, a rewards application, a public transportation application, building access applications, transit related applications, account or fund access related applications, micropayment applications, discount applications, as well as applications relating to other financial tasks or operations, boarding passes, copy machines, computer access, access to facilities, usage capabilities, access and use in a particular environment (such as on a college campus), dining, student ID info, and others, for example.
The interim interface device 400 includes a IID (interim interface device) processing portion 430, an IID communication portion 440, and an IID memory portion 450. The IID processing portion 430 in general handles the processing performed by the interim interface device 400, e.g. including the processing described below with reference to
The transponder device 500 of
The transponder memory portion 550 includes various file structures. In accordance with one embodiment of the invention, each of the file structures supports (or is provided to support) a particular application. That is, for example, the transponder memory portion 550 includes a file structure for a first application 551, a file structure for a second application 552, and a file structure for a third application 554. The file structures 551 and 552 reflect that the file structures are for a particular application, and that those applications are indeed loaded in the file structure and are ready for use. On the other hand, the file structure for application 554 reflects that the file structure is for a particular application, but that the application is not yet been loaded on the transponder memory portion 550.
Further, as shown in
Hereinafter, further aspects of the processing of the processing system 10 will be described with reference to
As shown in
Returning now to
After step 710 of
In step 720, the alteration portion 300 retrieves data from alteration portion database 310 to confirm that requested new application is available to the user. Then, in step 730, the alteration portion outputs an information packet to the user. For example, the information packet might simply advise the user that the loading of the additional application is underway and/or the information packet might instruct the user that a particular action is needed on their part, in order to effect the loading of the new application. For example, the user may have to go to a particular physical location at which the interim interface device 400 is disposed, e.g. a metro station. After step 730, the process passes to step 740.
In step 740, the alteration portion 300 outputs a data packet to the interim interface device 400. Then, the process passes to step 750.
In step 750, the data in the data packet is input by the interim interface device 400. Further, in step 750, at least some of the data in the data packet is transferred from the interim interface device 400 to the transponder device 500. Further details of the processing of step 750 are described below with reference to
After step 750, the process passes to step 760. In step 760, the interim interface device 400 transmits a communication back to the alteration portion 300 that the new application has been successfully transferred to the transponder device 500.
Then, in step 770, the process ends.
As shown in
In step 770, the interim interface device interfaces with the transponder to load the new application into the transponder. Further details of step 770 are described below with reference to
Once the new application is loaded in step 770, the process passes to step 757.
In step 757, the interim interface device 400 prepares a communication to the alteration portion 300 (via the cell phone) that the load of the application is complete. Then, the process passes to step 759.
In step 759, the process returns to
In accordance with a further embodiment of the invention,
The process of
As reflected in
In step 763, the interim interface device 400 identifies that the transponder is in proximity to the interim interface device, and initiates communication with the transponder. Then, the process passes to step 770.
In step 770, the interim interface device interfaces with the transponder to load the new application into the transponder. Further details of step 770 are described below with reference to
Once the new application is loaded in step 770, the process passes to step 767.
In step 767, the interim interface device 400 initiates the communication to the alteration portion 300 (via a hard line or other communication interface) that the load of the application is complete. Then, the process passes to step 769.
In step 769, the process returns to
As noted above,
In further explanation of the processing of
The subprocess of
In step 774, with the specified file structure in the transponder device 500 being unlocked, the interim interface device 400 loads the new application into the specified file structure.
Then, in step 775, the interim interface device 400 verifies that the updates and loading of new application(s) is complete. Such verification might be performed in any suitable manner, such as testing the newly updated/loaded software. After step 775, the process passes to step 776.
In step 776, the interim interface device 400 locks the specified file structure in the transponder device 500. Thereafter, the particular application that was loaded is ready for use. After step 776, the process passes to step 778.
In step 778 of
After step 778 of
The communications link 120 described above, as well as the various other communications links as described herein, may be, include or access any one or more of, for instance, the Internet, an intranet, a PAN (Personal Area Network), a LAN (Local Area Network), a WAN (Wide Area Network) or a MAN (Metropolitan Area Network), a frame relay connection, an Advanced Intelligent Network (AIN) connection, a synchronous optical network (SONET) connection, a digital T1, T3 or E1 line, Digital Data Service (DDS) connection, DSL (Digital Subscriber Line) connection, an Ethernet connection, an ISDN (Integrated Services Digital Network) line, a dial-up port such as a V.90, V.34 or V.34bis analog modem connection, a cable modem, an ATM (Asynchronous Transfer Mode) connection, or FDDN (Fiber Distributed Data Networks) or CDDI (Copper Distributed Data Interface) connections.
Communications link 120 may furthermore be, include or access any one or more of a WAP (Wireless Application Protocol) link, a GPRS (General Packet Radio Service) link, a GSM (Global System for Mobile Communication) link, a CDMA (Code Division Multiple Access) or TDMA (Time Division Multiple Access) link such as a cellular phone channel, a GPS (Global Positioning System) link, CDPD (cellular digital packet data), a RIM (Research in Motion, Limited) duplex paging type device, a Bluetooth radio link, or an IEEE 802.11-based radio frequency link. Communications link 120 may yet further be, include or access any one or more of an RS-232 serial connection, an IEEE-1394 (Firewire) connection, an IrDA (infrared) port, a SCSI (Small Computer Serial Interface) connection, a USB (Universal Serial Bus) connection or other wired or wireless, digital or analog interface or connection.
As described above, the transponder device 500 includes a transponder communication portion 540. The transponder communication portion 540 provides for communications to the interim interface device 400, as well as for other communications. As shown in
The transponder user interface 542 is provided to display certain attributes under particular conditions (such as when a particular application in the RFID device is utilized, when particular processing is performed, when an account balance is low, or when a particular account is accessed, for example). For example, the interface 490 might include the nature or particulars of a transaction (that was or is being performed), or which application on the transponder device 500 is being used. The transponder user interface 542 may include a button (or other interface) to control aspects of processing, e.g. what account is to be debited. The transponder device 500 as described herein may well be used over a long period of time and in a variety of environments and situations. For example, a user might well take their a cell phone with them virtually everywhere. Accordingly, there is potential for lose or theft of a device to which the transponder device 500 is connected. Accordingly, the transponder device 500, in accordance with one embodiment of the invention, is provided with a self destruct portion 590, as shown in
A variety of events may be used which result in the destruction of an application or applications in the transponder device 500, including, for example: (1) The trigger event may include a time period. For example, the transponder device 500 may need to be refreshed periodically, e.g. every month, or else the device will become inoperative; (2) a signal from the bank system (or other source) might be output to the transponder device 500 and result in the destruction of the device; (3) the non-receipt of a signal or input, e.g. from the customer or bank system, for example, at a predetermined time may result in the destruction of the device; and/or (4) an attempt to use the device in some abnormal way, e.g. such as repeatedly entering the wrong password or other authentication.
As used herein, the destruction of, i.e., to destroy, the transponder device 500 includes the disablement of the device. Accordingly, “destruction” of the device may include either that the device is permanently destroyed or merely disabled (such that the device might later be enabled). Further, the transponder device may selectively determine whether the device is permanently destroyed or merely disabled (such that the device might later be enabled), i.e., based on some trigger events, the transponder device may be permanently destroyed, whereas based on other trigger events, the transponder device may be merely disabled (such that the device might later be enabled).
As used herein, information and data are used interchangeably.
Hereinafter, further aspects of implementation of the invention will be described. As described above,
The system of the invention or portions of the system of the invention may be in the form of a “processing machine,” such as a general purpose computer, for example. As used herein, the term “processing machine” is to be understood to include at least one processor that uses at least one memory. The at least one memory stores a set of instructions. The instructions may be either permanently or temporarily stored in the memory or memories of the processing machine. The processor executes the instructions that are stored in the memory or memories in order to process data. The set of instructions may include various instructions that perform a particular task or tasks, such as those tasks described above in the flowcharts. Such a set of instructions for performing a particular task may be characterized as a program, software program, or simply software.
As noted above, the processing machine executes the instructions that are stored in the memory or memories to process data. This processing of data may be in response to commands by a user or users of the processing machine, in response to previous processing, in response to a request by another processing machine and/or any other input, for example.
As noted above, the processing machine used to implement the invention may be a general purpose computer. However, the processing machine described above may also utilize any of a wide variety of other technologies including a special purpose computer, a computer system including a microcomputer, mini-computer or mainframe for example, a programmed microprocessor, a micro-controller, a peripheral integrated circuit element, a CSIC (Customer Specific Integrated Circuit) or ASIC (Application Specific Integrated Circuit) or other integrated circuit, a logic circuit, a digital signal processor, a programmable logic device such as a FPGA, PLD, PLA or PAL, or any other device or arrangement of devices that is capable of implementing the steps of the process of the invention.
It is appreciated that in order to practice the method of the invention as described above, it is not necessary that the processors and/or the memories of the processing machine be physically located in the same geographical place. That is, each of the processors and the memories used in the invention may be located in geographically distinct locations and connected so as to communicate in any suitable manner. Additionally, it is appreciated that each of the processor and/or the memory may be composed of different physical pieces of equipment. Accordingly, it is not necessary that the processor be one single piece of equipment in one location and that the memory be another single piece of equipment in another location. That is, it is contemplated that the processor may be two pieces of equipment in two different physical locations. The two distinct pieces of equipment may be connected in any suitable manner. Additionally, the memory may include two or more portions of memory in two or more physical locations.
To explain further, processing as described above is performed by various components and various memories. However, it is appreciated that the processing performed by two distinct components as described above may, in accordance with a further embodiment of the invention, be performed by a single component. Further, the processing performed by one distinct component as described above may be performed by two distinct components. In a similar manner, the memory storage performed by two distinct memory portions as described above may, in accordance with a further embodiment of the invention, be performed by a single memory portion. Further, the memory storage performed by one distinct memory portion as described above may be performed by two memory portions.
Further, various technologies may be used to provide communication between the various processors and/or memories, as well as to allow the processors and/or the memories of the invention to communicate with any other entity; i.e., so as to obtain further instructions or to access and use remote memory stores, for example. Such technologies used to provide such communication might include a network, the Internet, Intranet, Extranet, LAN, an Ethernet, or any client server system that provides communication, for example. Such communications technologies may use any suitable protocol such as TCP/IP, UDP, or OSI, for example.
As described above, a set of instructions is used in the processing of the invention. The set of instructions may be in the form of a program or software. The software may be in the form of system software or application software, for example. The software might also be in the form of a collection of separate programs, a program module within a larger program, or a portion of a program module, for example The software used might also include modular programming in the form of object oriented programming. The software tells the processing machine what to do with the data being processed.
Further, it is appreciated that the instructions or set of instructions used in the implementation and operation of the invention may be in a suitable form such that the processing machine may read the instructions. For example, the instructions that form a program may be in the form of a suitable programming language, which is converted to machine language or object code to allow the processor or processors to read the instructions. That is, written lines of programming code or source code, in a particular programming language, are converted to machine language using a compiler, assembler or interpreter. The machine language is binary coded machine instructions that are specific to a particular type of processing machine, i.e., to a particular type of computer, for example. The computer understands the machine language.
Any suitable programming language may be used in accordance with the various embodiments of the invention. Illustratively, the programming language used may include assembly language, Ada, APL, Basic, C, C++, COBOL, dBase, Forth, Fortran, Java, Modula-2, Pascal, Prolog, REXX, Visual Basic, and/or JavaScript, for example. Further, it is not necessary that a single type of instructions or single programming language be utilized in conjunction with the operation of the system and method of the invention. Rather, any number of different programming languages may be utilized as is necessary or desirable.
Also, the instructions and/or data used in the practice of the invention may utilize any compression or encryption technique or algorithm, as may be desired. An encryption module might be used to encrypt data. Further, files or other data may be decrypted using a suitable decryption module, for example.
As described above, the invention may illustratively be embodied in the form of a processing machine, including a computer or computer system, for example, that includes at least one memory. It is to be appreciated that the set of instructions, i.e., the software for example, that enables the computer operating system to perform the operations described above may be contained on any of a wide variety of media or medium, as desired. Further, the data that is processed by the set of instructions might also be contained on any of a wide variety of media or medium. That is, the particular medium, i.e., the memory in the processing machine, utilized to hold the set of instructions and/or the data used in the invention may take on any of a variety of physical forms or transmissions, for example. Illustratively, the medium may be in the form of paper, paper transparencies, a compact disk, a DVD, an integrated circuit, a hard disk, a floppy disk, an optical disk, a magnetic tape, a RAM, a ROM, a PROM, a EPROM, a wire, a cable, a fiber, communications channel, a satellite transmissions or other remote transmission, as well as any other medium or source of data that may be read by the processors of the invention.
Further, the memory or memories used in the processing machine that implements the invention may be in any of a wide variety of forms to allow the memory to hold instructions, data, or other information, as is desired. Thus, the memory might be in the form of a database to hold data. The database might use any desired arrangement of files such as a flat file arrangement or a relational database arrangement, for example.
In the system and method of the invention, a variety of “user interfaces” may be utilized to allow a user to interface with the processing machine or machines that are used to implement the invention. As used herein, a user interface includes any hardware, software, or combination of hardware and software used by the processing machine that allows a user to interact with the processing machine. A user interface may be in the form of a dialogue screen for example. A user interface may also include any of a mouse, touch screen, keyboard, voice reader, voice recognizer, dialogue screen, menu box, list, checkbox, toggle switch, a pushbutton or any other device that allows a user to receive information regarding the operation of the processing machine as it processes a set of instructions and/or provide the processing machine with information. Accordingly, the user interface is any device that provides communication between a user and a processing machine. The information provided by the user to the processing machine through the user interface may be in the form of a command, a selection of data, or some other input, for example.
As discussed above, a user interface is utilized by the processing machine that performs a set of instructions such that the processing machine processes data for a user. The user interface is typically used by the processing machine for interacting with a user either to convey information or receive information from the user. However, it should be appreciated that in accordance with some embodiments of the system and method of the invention, it is not necessary that a human user actually interact with a user interface used by the processing machine of the invention. Rather, it is contemplated that the user interface of the invention might interact, i.e., convey and receive information, with another processing machine, rather than a human user. Accordingly, the other processing machine might be characterized as a user. Further, it is contemplated that a user interface utilized in the system and method of the invention may interact partially with another processing machine or processing machines, while also interacting partially with a human user.
It will be readily understood by those persons skilled in the art that the present invention is susceptible to broad utility and application. Many embodiments and adaptations of the present invention other than those herein described, as well as many variations, modifications and equivalent arrangements, will be apparent from or reasonably suggested by the present invention and foregoing description thereof, without departing from the substance or scope of the invention.
Accordingly, while the present invention has been described here in detail in relation to its exemplary embodiments, it is to be understood that this disclosure is only illustrative and exemplary of the present invention and is made to provide an enabling disclosure of the invention. Accordingly, the foregoing disclosure is not intended to be construed or to limit the present invention or otherwise to exclude any other such embodiments, adaptations, variations, modifications and equivalent arrangements.
Number | Name | Date | Kind |
---|---|---|---|
3468046 | Makishima | Sep 1969 | A |
3532543 | Nole et al. | Oct 1970 | A |
3537195 | Gerds | Nov 1970 | A |
3546022 | Busch et al. | Dec 1970 | A |
3806369 | Dey et al. | Apr 1974 | A |
4058839 | Darjany | Nov 1977 | A |
4523297 | Ugon et al. | Jun 1985 | A |
4544834 | Newport et al. | Oct 1985 | A |
4582985 | Lofberg | Apr 1986 | A |
4634845 | Riley | Jan 1987 | A |
4689478 | Hale et al. | Aug 1987 | A |
4746787 | Okada | May 1988 | A |
4747620 | Kay et al. | May 1988 | A |
4750036 | Martinez | Jun 1988 | A |
4754418 | Hara | Jun 1988 | A |
4766293 | Boston | Aug 1988 | A |
4825052 | Ugon | Apr 1989 | A |
4833048 | Dejonghe et al. | May 1989 | A |
4849618 | Namikawa et al. | Jul 1989 | A |
4859837 | Halpern | Aug 1989 | A |
4868376 | Lessin et al. | Sep 1989 | A |
4876441 | Hara et al. | Oct 1989 | A |
4897533 | Lyszczarz | Jan 1990 | A |
4916296 | Streck | Apr 1990 | A |
4922111 | Kuwano | May 1990 | A |
4923288 | Allen et al. | May 1990 | A |
4968873 | Dethloff et al. | Nov 1990 | A |
4977455 | Young | Dec 1990 | A |
4999617 | Uemura | Mar 1991 | A |
5025373 | Keyser, Jr. | Jun 1991 | A |
5047614 | Bianco | Sep 1991 | A |
5055662 | Hasegawa | Oct 1991 | A |
5080748 | Bonomi | Jan 1992 | A |
5097115 | Ogasawara et al. | Mar 1992 | A |
5154731 | Winger | Oct 1992 | A |
5162175 | Visco et al. | Nov 1992 | A |
5168151 | Nara | Dec 1992 | A |
5173589 | Diehl | Dec 1992 | A |
5227614 | Danielson | Jul 1993 | A |
5233654 | Harvey et al. | Aug 1993 | A |
5241161 | Zuta | Aug 1993 | A |
5247190 | Friend et al. | Sep 1993 | A |
5249044 | Von Kohorn | Sep 1993 | A |
5252815 | Pernet | Oct 1993 | A |
5276311 | Hennige | Jan 1994 | A |
5285278 | Holman | Feb 1994 | A |
5287181 | Holman | Feb 1994 | A |
5299940 | Uenaka et al. | Apr 1994 | A |
5317137 | Wilkins | May 1994 | A |
5321240 | Takahira | Jun 1994 | A |
5328809 | Holmes et al. | Jul 1994 | A |
5339239 | Manabe et al. | Aug 1994 | A |
5340969 | Cox | Aug 1994 | A |
5359183 | Skodlar | Oct 1994 | A |
5396650 | Terauchi | Mar 1995 | A |
5399502 | Friend et al. | Mar 1995 | A |
5401827 | Holmes et al. | Mar 1995 | A |
5412192 | Hoss | May 1995 | A |
5425497 | Sorensen | Jun 1995 | A |
5450479 | Alesio | Sep 1995 | A |
5451763 | Pickett et al. | Sep 1995 | A |
5488571 | Jacobs | Jan 1996 | A |
5492370 | Chatwin et al. | Feb 1996 | A |
5504664 | Ostema | Apr 1996 | A |
5506394 | Plesko | Apr 1996 | A |
5508731 | Kohorn | Apr 1996 | A |
5510828 | Lutterbach | Apr 1996 | A |
5511114 | Stimson et al. | Apr 1996 | A |
5512654 | Holmes et al. | Apr 1996 | A |
5513102 | Auriemma | Apr 1996 | A |
5516598 | Visco et al. | May 1996 | A |
5521363 | Tannenbaum | May 1996 | A |
5523179 | Chu | Jun 1996 | A |
5523794 | Mankovitz | Jun 1996 | A |
5530235 | Stefik et al. | Jun 1996 | A |
5535147 | Jacobs | Jul 1996 | A |
5544246 | Mandelbaum et al. | Aug 1996 | A |
5559313 | Claus et al. | Sep 1996 | A |
5563948 | Diehl | Oct 1996 | A |
5568441 | Sanemitsu | Oct 1996 | A |
5569898 | Fisher et al. | Oct 1996 | A |
5572004 | Raimann | Nov 1996 | A |
5577109 | Stimson et al. | Nov 1996 | A |
5582623 | Chu | Dec 1996 | A |
5585787 | Wallerstein | Dec 1996 | A |
5590038 | Pitroda | Dec 1996 | A |
5594493 | Nemirofsky | Jan 1997 | A |
5604542 | Dedrick | Feb 1997 | A |
5613095 | Moss et al. | Mar 1997 | A |
5621787 | McKoy et al. | Apr 1997 | A |
5629977 | Fonseca | May 1997 | A |
5649118 | Carlisle et al. | Jul 1997 | A |
5652602 | Fishman | Jul 1997 | A |
5663766 | Sizer, II | Sep 1997 | A |
5664110 | Green et al. | Sep 1997 | A |
5664157 | Takahira et al. | Sep 1997 | A |
5672678 | Holmes et al. | Sep 1997 | A |
5690412 | Sheldon | Nov 1997 | A |
5710458 | Iwasaki | Jan 1998 | A |
5721781 | Deo et al. | Feb 1998 | A |
5727153 | Powell | Mar 1998 | A |
5728998 | Novis et al. | Mar 1998 | A |
5734154 | Jachimowicz et al. | Mar 1998 | A |
5736727 | Nakata | Apr 1998 | A |
5736728 | Matsubara | Apr 1998 | A |
5744789 | Kashi | Apr 1998 | A |
5751953 | Sheils | May 1998 | A |
5760381 | Stich et al. | Jun 1998 | A |
5761624 | Mooney | Jun 1998 | A |
5763862 | Jachimowicz | Jun 1998 | A |
5767896 | Nemirofsky | Jun 1998 | A |
5770843 | Rose et al. | Jun 1998 | A |
5770849 | Novis et al. | Jun 1998 | A |
5777305 | Smith et al. | Jul 1998 | A |
5777306 | Masuda | Jul 1998 | A |
5777903 | Piosenka et al. | Jul 1998 | A |
5778067 | Jones et al. | Jul 1998 | A |
5789732 | McMahon | Aug 1998 | A |
5789733 | Jachimowicz et al. | Aug 1998 | A |
5793502 | Bianco et al. | Aug 1998 | A |
5804806 | Haddad | Sep 1998 | A |
5806044 | Powell | Sep 1998 | A |
5806045 | Biorge | Sep 1998 | A |
5807627 | Friend et al. | Sep 1998 | A |
5815127 | Jacobs | Sep 1998 | A |
5815658 | Kuriyama | Sep 1998 | A |
5817207 | Leighton | Oct 1998 | A |
5819234 | Slavin et al. | Oct 1998 | A |
5844230 | Lalonde | Dec 1998 | A |
5854595 | Williams | Dec 1998 | A |
5857079 | Claus et al. | Jan 1999 | A |
5857709 | Chock | Jan 1999 | A |
5859419 | Wynn | Jan 1999 | A |
5870155 | Erlin | Feb 1999 | A |
5877941 | Ryu | Mar 1999 | A |
5880769 | Nemirofsky | Mar 1999 | A |
5884271 | Pitroda | Mar 1999 | A |
5887271 | Powell | Mar 1999 | A |
5890135 | Powell | Mar 1999 | A |
5920844 | Hotta et al. | Jul 1999 | A |
5930217 | Kayanuma | Jul 1999 | A |
5952639 | Ohki | Sep 1999 | A |
5952641 | Korshun | Sep 1999 | A |
5955961 | Wallerstein | Sep 1999 | A |
RE36356 | Gloton et al. | Oct 1999 | E |
5988503 | Kuo | Nov 1999 | A |
5995372 | Asakura | Nov 1999 | A |
6002383 | Shimada | Dec 1999 | A |
6003770 | Schilling | Dec 1999 | A |
6004681 | Epstein et al. | Dec 1999 | A |
6005183 | Akai et al. | Dec 1999 | A |
6016954 | Abe et al. | Jan 2000 | A |
6019284 | Freeman et al. | Feb 2000 | A |
6025283 | Roberts | Feb 2000 | A |
6027028 | Pieterse et al. | Feb 2000 | A |
6036099 | Leighton | Mar 2000 | A |
6045042 | Ohno | Apr 2000 | A |
6049463 | O'Malley et al. | Apr 2000 | A |
6087954 | McSpadden et al. | Jul 2000 | A |
6089284 | Kaehler et al. | Jul 2000 | A |
6091817 | Bertina et al. | Jul 2000 | A |
6095072 | Kaufhold | Aug 2000 | A |
6095412 | Bertina et al. | Aug 2000 | A |
D431039 | Wilson | Sep 2000 | S |
D431252 | Wilson | Sep 2000 | S |
6121069 | Boyko et al. | Sep 2000 | A |
D431573 | Wilson | Oct 2000 | S |
D432141 | Wilson | Oct 2000 | S |
D432548 | Wilson | Oct 2000 | S |
D432552 | Wilson | Oct 2000 | S |
D433031 | Wilson | Oct 2000 | S |
D433032 | Wilson | Oct 2000 | S |
D433033 | Wilson | Oct 2000 | S |
D433034 | Wilson | Oct 2000 | S |
D433035 | Wilson | Oct 2000 | S |
D433036 | Wilson | Oct 2000 | S |
D433037 | Wilson | Oct 2000 | S |
D433059 | Okumura et al. | Oct 2000 | S |
6128599 | Walker et al. | Oct 2000 | A |
D433420 | Wilson | Nov 2000 | S |
D433421 | Wilson | Nov 2000 | S |
D433422 | Wilson | Nov 2000 | S |
D433423 | Wilson | Nov 2000 | S |
D433424 | Wilson | Nov 2000 | S |
D434041 | Burke | Nov 2000 | S |
6146741 | Ogawa et al. | Nov 2000 | A |
6164548 | Curiel | Dec 2000 | A |
6170745 | Schilling | Jan 2001 | B1 |
D437882 | Creighton | Feb 2001 | S |
6214155 | Leighton | Apr 2001 | B1 |
6250555 | Inamoto | Jun 2001 | B1 |
6294241 | Kaule et al. | Sep 2001 | B1 |
6308887 | Korman et al. | Oct 2001 | B1 |
6315195 | Ramachandran | Nov 2001 | B1 |
6318536 | Korman | Nov 2001 | B1 |
6328342 | Belousov et al. | Dec 2001 | B1 |
6337752 | Heckenkamp et al. | Jan 2002 | B1 |
6382506 | Van Der Valk | May 2002 | B1 |
6441736 | Leighton | Aug 2002 | B1 |
6471128 | Corcoran et al. | Oct 2002 | B1 |
6482330 | Bajorek | Nov 2002 | B1 |
6492717 | Gore et al. | Dec 2002 | B1 |
6514367 | Leighton | Feb 2003 | B1 |
6533180 | Wood | Mar 2003 | B1 |
6549912 | Chen | Apr 2003 | B1 |
6557766 | Leighton | May 2003 | B1 |
6609658 | Sehr | Aug 2003 | B1 |
D481068 | Blossom et al. | Oct 2003 | S |
6631849 | Blossom | Oct 2003 | B2 |
6644551 | Clayman et al. | Nov 2003 | B2 |
6702181 | Ramachandran | Mar 2004 | B2 |
6715797 | Curiel | Apr 2004 | B2 |
6734887 | Field | May 2004 | B2 |
6796490 | Drummond et al. | Sep 2004 | B1 |
6957334 | Goldstein | Oct 2005 | B1 |
6965868 | Bednarek | Nov 2005 | B1 |
7025256 | Drummond et al. | Apr 2006 | B1 |
7040533 | Ramachandran | May 2006 | B1 |
7150393 | Drummond et al. | Dec 2006 | B1 |
7239226 | Berardi et al. | Jul 2007 | B2 |
7376583 | Rolf | May 2008 | B1 |
7424441 | George et al. | Sep 2008 | B2 |
7562813 | Humphrey et al. | Jul 2009 | B2 |
7774231 | Pond et al. | Aug 2010 | B2 |
7827115 | Weller et al. | Nov 2010 | B2 |
7917123 | Juntunen | Mar 2011 | B2 |
7982609 | Padmanabhan et al. | Jul 2011 | B2 |
20010011250 | Paltenghe et al. | Aug 2001 | A1 |
20020117846 | Kaule et al. | Aug 2002 | A1 |
20030009382 | D'Arbeloff et al. | Jan 2003 | A1 |
20030024995 | Conner et al. | Feb 2003 | A1 |
20030047253 | Robinson et al. | Mar 2003 | A1 |
20030187787 | Freund | Oct 2003 | A1 |
20030202151 | Hinata | Oct 2003 | A1 |
20040049451 | Berardi | Mar 2004 | A1 |
20040121257 | Kaminsky et al. | Jun 2004 | A1 |
20040159709 | Ohta et al. | Aug 2004 | A1 |
20040217178 | Lasch et al. | Nov 2004 | A1 |
20050012326 | Keller et al. | Jan 2005 | A1 |
20050194453 | Conner et al. | Sep 2005 | A1 |
20060102729 | Gandel et al. | May 2006 | A1 |
20060106674 | Muller | May 2006 | A1 |
20060124753 | Scholz et al. | Jun 2006 | A1 |
20060214008 | Asami et al. | Sep 2006 | A1 |
20070170264 | Lasch et al. | Jul 2007 | A1 |
20070174116 | Keith et al. | Jul 2007 | A1 |
20070203825 | Hanifin et al. | Aug 2007 | A1 |
Number | Date | Country |
---|---|---|
0855659 | Jul 1998 | EP |
9837524 | Aug 1998 | WO |
Entry |
---|
Epper, A Player Goes After Big Bucks in Cyberspace, American Banker, vol. 160, No. 86, ISSN: 0002-7561, May 5, 1995, p. 17. |
Sotto, An RFID Code of Conduct, RFID Journal, Featured Opinions, May 30, 2005. |
BSI2000 Files Patent Application for Optical Bank Card Press Release, printed Apr. 27, 2004. |
Brehl, Banks issue cash-card pledge, The Toronto Star, Oct. 9, 1997, 1 page. |
Card Flash, Daily Payment Card News, www.CardWeb.com, printed Aug. 10, 2004. |
Rosen, Cash Just Isn't Flexible Enough: Shops of the Future Will Only Take Cards, Daily Express, Technology Section, Feb. 10, 1995, 1 page. |
Hesseldahl, China Goes Smartcard Crazy, www.forbes.com, Jun. 12, 2001. |
Schwartz, Digital Cash Payoff. |
E-Z Pass, Web page, http://www.ezpass.com-Disc—portNewYork.html, Nov. 12, 2001. |
E-Z Pass, Web page, http:\\www.ezpass.com-Disc—ny—annual.html, Nov. 12, 2001. |
E-Z Pass, Web page, http:\\www.ezpass.com-frameMain.html, Nov. 12, 2001. |
E-Z Pass, Web page, http:\\www.ezpass.com-whatis.html, Nov. 12, 2001. |
Business Times, Electronic Purse Can Free You from ATM Drag, Business Times, www.btimes.co.za, printed Feb. 23, 2001, 1 page. |
Electronic Purse, SCIA (Smart Card Industry Association), About Smart Cards, www.scia.org, printed Feb. 23, 2001, 1 page. |
Sanchez-Klein, Electronic purse alliance planned, Computerworld Online News, Jul. 29, 1998, printed Feb. 23, 2001, 2 pages. |
Electronic purse card to be launched tomorrow, New Straits Times, News Clippings, Sep. 18, 1999, printed Feb. 23, 2001, 3 pages. |
Frequently asked questions, ECARD, www.eregard.com, printed Sep. 23, 2001, 7 pages. |
Machlis, Have it the smart way: Burger King program drives smart-card use, Computerworld, printed Feb. 23, 2001, 1 page. |
Nokia Announces the World's First NFC Enabled Mobile Product for Contactless Payment and Ticketing, PRNewswire, Feb. 9, 2005. |
Proton world and Europay to co-operate in creation of new CEPS-compliant e-purse application, Press Release 1999, Waterloo, Belgium, Jun. 28, 1999, 2 pages. |
Purse Application for Cross Border Use in Euro, Cordis, Pace 1st 1999-11531 Pace, www.cordis.lu, printed Feb. 23, 2001, 3 pages. |
RFID Tags, Contactless Smart Card Technology and Electronic Passports: Frequently Asked Questions, www.smartcardalliance.org, Feb. 17, 2005. |
RFID Tags, Contactless Smart Card Technology: Comparing and Contrasting Applications and Capabilities, www.smartcardalliance.org, Feb. 17, 2005. |
SK100 Smart Card Electronic Purse Balance Reader, SK100 Balance Reader, http://perso.wanadoo.fr, printed Feb. 23, 2001, 1 page. |
Gilhooly, Smart Cards, Smart Move?, Computerworld, May 21, 2001, pp. 1-5. |
Smart card for loyalty and e-purse applications eclipses capability of conventional mag-stripe cards, Press Release, www.1.sib.com, Apr. 21, 1997, printed Feb. 23, 2001, 3 pages. |
SmartAxis: Load Cash on to your E-Purse Card, Supported Currencies and Schemes, www.smartaxis.co.uk, printed Feb. 23, 2001, 9 pages. |
Dvorak, Smartcards Get Smarter, www.forbes.com, Jun. 1, 2001. |
Hesseldahl, Stock Focus: Smartcard Companies, www.forbes.com, Jun. 18, 2001. |
The Electronic Purse Reaches the Car Park, http:\\docs.vircom.net/mobility/parking, printed Feb. 23, 2001, 2 pages. |
Stuber, The electronic purse: An overview of recent development and issues, Bank of Canada, Technical Report No. 74, www.bankofcanada.ca, Jan. 1996, printed Feb. 23, 2001, 2 pages. |
Transponders: Cash in a Flash, www.forbes.com, Jul. 31, 2001. |
Hesseldahl, U.S. Getting Wise to Smart Cards, Forbes.com, May 25, 2000. |
Understanding the benefits: Smartcity offers a number of important benefits to both the card issuers and their customers, http://www.icl.com/smartcards/benefits.htm, printed Feb. 27, 2001, 2 pages. |
Visa first to launch electronic purse load via GSM mobile phone, www.cellular.co.za, Johannesburg, ZA, printed Feb. 23, 2001, 4 pages. |
Hansell, Visa to unveil electronic purse cards, New York Times, printed Feb. 23, 2001, 2 pages. |
Visa, MBNA and De La Rue Launch Multi-Function Smart Card Program, www.findarticles.com, Jul. 6, 1998. |
Machlis et al., Will smart cards replace ATMS?, Computerworld, printed Feb. 23, 2001, 3 pages. |