Source: https://patents.justia.com/patent/10198687
Timestamp: 2019-06-20 03:04:36
Document Index: 750533871

Matched Legal Cases: ['art 510', 'art 910', 'art 910', 'art 920', 'art 920', 'art 930', 'art 930', 'art 921', 'art 920', 'art 930', 'Application No. 2008340226', 'Application No. 08865573', 'Application No. 08865573']

US Patent for Cards and devices with multifunction magnetic emulators and methods for using same Patent (Patent # 10,198,687 issued February 5, 2019) - Justia Patents Search
Justia Patents ConductiveUS Patent for Cards and devices with multifunction magnetic emulators and methods for using same Patent (Patent # 10,198,687)
Aug 1, 2016 - DYNAMICS INC.
A payment card (e.g., credit and/or debit card) is provided with a magnetic emulator operable of communicating information to a magnetic stripe reader. Information used in validating a financial transaction is encrypted based on time such that a validating server requires receipt of the appropriate encrypted information for a period of time to validate a transaction for that period of time. Such dynamic information may be communicated using such an emulator such that a card may be swiped through a magnetic stripe reader—yet communicate different information based on time. An emulator may receive information as well as communicate information to a variety of receivers (e.g., an RFID receiver).
Determination of Robotic Step Path
Slip detection for robotic locomotion
Motor and controller integration for a legged robot
This application is a continuation of U.S. patent application Ser. No. 13/557,525, filed on Jul. 25, 2012, which claims the benefit of U.S. Pat. No. 8,517,276, filed on Dec. 19, 2008, which claims the benefit of United States Provisional Patent Application Nos. 61/016,491 filed on Dec. 24, 2007, 61/026,846filed on Feb. 7, 2008, 61/027,807 filed on Feb. 11, 2008, 61/081,003 filed on Jul. 15, 2008, 61/086,239 filed on Aug. 5, 2008, 61/090,423 filed on Aug. 20, 2008, 61/097,401 filed Sep. 16, 2008, 61/112,766 filed on Nov. 9, 2008, 61/117,186 filed on Nov. 23, 2008, 61/119,366 filed on Dec. 2, 2008, and 61/120,813 filed on Dec. 8, 2008, all of which are hereby incorporated by reference herein in their entirety.
The processor may drive an emulator through a switching circuit. The switching circuit may control the direction and magnitude of current that flows through at least a portion of an emulator such that the switching circuit controls the direction and magnitude of the electromagnetic field created by at least that portion of the emulator. An electromagnetic field may be generated by the emulator such that the emulator is operable to electrically couple with a read-head from a magnetic stripe reader without making physical contact with the read-head. Particularly, for example, an emulator that is driven with increased current can be operable to couple with the read-head of a magnetic stripe reader even when placed outside and within the proximity of (e.g., 0.25 inches) the read-head.
A magnetic emulator may be operated to electrically couple, and transmit data to, devices other than a magnetic stripe reader. For example, a magnetic emulator may be operated to electrically couple, and transmit data to, a device using a Radio Frequency IDentification (RFID) protocol. Accordingly, a processor may drive the emulator at a frequency and magnitude in order to electrically couple with a read-head of a magnetic stripe reader and then drive the emulator at a different frequency and a different magnitude in order to electronically couple with an RFID reader.
A processor may receive information from a magnetic stripe reader detector and/or an RFID receiver detector. A processor may detect, for example, the presence of a read-head of a magnetic stripe reader by receiving signals from a magnetic stripe reader detector and, in response, the processor may drive a magnetic emulator in a manner that allows the emulator to couple with the magnetic stripe reader. The processor may also detect, for example, the presence of and RFID receiver by receiving signals from an RFID receiver detector and, in response, the processor may drive a magnetic emulator in a manner that allows the emulator to couple with the RFID receiver. More than one emulator may be provided on a card or other device and a processor may drive such emulators in a variety of different manners.
A circuit may be provided on a credit card that is operable to receive data from a magnetic stripe encoder and/or an RFID transmitter. Such a circuit may electrically couple with an RFID transmitter and/or magnetic stripe encoder and deliver information to a processor. In this manner, a card, or other device, may communicate bi-directionally with a device.
FIG. 4 is an illustration of cards constructed in accordance with the principles of the present invention;
FIG. 5 is an illustration of process flow charts constructed in accordance with the principles of the present invention;
FIG. 6 is an illustration of the electrical coupling between a card and a reader constructed in accordance with the principles of the present invention;
FIG. 7 is an illustration of the electrical coupling between a card and a reader constructed in accordance with the principles of the present invention;
FIG. 8 is an illustration of magnetic shielding in accordance with the principles of the present invention;
FIG. 11 is an illustration of a card constructed in accordance with the principles of the present invention; and
FIG. 12 is an illustration of a personal electronic device constructed in accordance with the principles of the present invention.
For example, a particular number of digits of a credit card number (e.g., the last 3 digits) may be provided as dynamic information. Such dynamic information may be changed periodically (e.g., once every hour). Information may be changed via, for example, encryption. Software may be provided at, for example, the payment verification servers that verifies the dynamic information for each period of time such that a payment can be validated and processed for a particular user. A user may be identifies using, for example, static information that is used to form a credit card number or other static information (e.g., information 120). Additionally, identification information may be derived (e.g., embedded) in dynamic information. Persons skilled in the art will appreciate that a credit card number may have, for example, a length of 15 or 16 digits. A credit card number may also have a length of up to 19 digits. A verification code may be used with some payment systems and such a verification code may be provided statically on the card or may be provided as dynamic information. Such a verification code may be provided on a second display located on, for example, the front or rear surface of card 100. Alternatively, a verification code may be displayed on the same display as other dynamic information (e.g., dynamic information 112). A display may be, for example, a flexible electronic ink display. Such a flexible electronic ink display may, for example, utilize power to change displayed information, but may not utilize power to display information after the information is changed.
Card 150 may be provided. Card 150 may include static magnetic stripe tracks 153 and 152. A magnetic emulator may be provided as device 151. Device 151 may be operable to electrically couple with a read-head of a magnetic stripe reader. Persons skilled in the art will appreciate that a read-head housing of a magnetic stripe reader may be provided with one, two, or three active read-heads that are operable to each couple with a separate magnetic track of information. A reader may also have more than one read-head housing and each read-head housing may be provided with one, two, or three active read-heads that are operable to each couple with a separate magnetic track of information. Such read-head housings may be provided different surfaces of a magnetic stripe reader. For example, the read-head housings may be provided on opposite walls of a trough sized to accept payment cards. Accordingly, the devices on the opposite sides of the trough may be able to read a credit card regardless of the direction that the credit card was swiped.
A static magnetic stripe may be provide to transmit data for one or more tracks to a magnetic strip reader where dynamic information is not desired. Card 150, for example, may include static magnetic track 153 and static magnetic track 152. Information on static magnetic tracks 152 and 153 may be encoded via a magnetic stripe encoder. Device 151 may include an emulator such that dynamic information may be communicated through emulator 151. Any combination of emulators and static magnetic tracks may be utilized for a card or device.
One or more batteries, such as flexible lithium polymer, batteries may be utilized to form card 100. Such batteries may be electrically coupled in a serial combination to provide a source of power to the various components of card 100. Alternatively, separate batteries may provide power to different components of card 100. For example, a battery may provide power to a processor and/or display of card 100, while another battery provides a source of energy to one or more magnetic emulators of card 100. In doing so, for example, a processor may operate even after the battery that supplies power to an emulator completely discharges. Accordingly, the processor may provide information to another component of card 100. For example, the processor may display information on a display to indicate to a user that the magnetic emulator is not longer operational due to power exhaustion. Batteries may be, for example, rechargeable and contacts, or other devices, may be provided on card 100 such that the battery may be recharged.
RFID antenna 210 may be provided on card 200. Such an RFID antenna may be operable to transmit information provided by processor 220. In doing so, for example, processor 220 may communicate with an RFID device using RFID antenna 210 and may communicate with a magnetic stripe reader using magnetic emulator 204. Both RFID antenna 210 and magnetic emulator 204 may be utilized to communicate payment card information (e.g., credit card information) to a reader. Processor 240 may also be coupled to display 240 such that dynamic information can be displayed on display 240. Button array 230 may also be coupled to processor 220 such that the operation of card 200 may be controlled, at least in part, by manual input received by button array 230.
Card 250 may be provided and may include static magnetic track 253, magnetic emulators 251 and 252, and magnetic read-heads 254-257). Persons skilled in the art will appreciate that static magnetic track 253 may be a read-write track such that information may be written to magnetic track 253 from a magnetic stripe reader that includes a head operable to magnetically encode data onto a magnetic track. Information may be written to magnetic track 253 as part of a payment process (e.g., a credit card or debit card transaction). Persons skilled in the art will appreciate that a static magnetic track may include a magnetic material that includes ferromagnetic materials that provide for flux-reversals such that a magnetic stripe reader can read the flux-reversals from the static magnetic track. Persons skilled in the art will also appreciate that a magnetic emulator may communicate information that remains the same from payment card transaction to payment card transaction (e.g., static information) as well as information that changes between transactions (e.g., dynamic information).
FIG. 3 shows card 300 that may include magnetic encoders 302 and 302 without, for example, a static magnetic track. Read-head detectors 304-307 may also be provided. Persons skilled in the art will appreciate that a magnetic reader may include the ability to read two tracks of information (e.g., may include at least two read-heads). All of the information needed to perform a financial transaction (e.g., a credit/debit card transaction) may be included on two magnetic tracks. Alternatively, all of the information needed to perform a financial transaction (e.g., a gift card transaction) may be included on one magnetic track. Accordingly, particular cards, or other devices, may include the ability, for example, to only transmit data associated with the tracks that are needed to complete a particular financial transaction. Persons skilled in the art will appreciate that for systems with three tracks of information, the bottom two tracks may be utilized for credit card information. Persons skilled in the art will also appreciate that a secure credit card transaction may be provided by only changing, for example, one of two magnetic tracks utilized in a credit card transaction (for those transactions that utilize two tracks). Accordingly, one track may be a static magnetic track constructed from a magnetic material and the other track may be provided as a magnetic emulator. Persons skilled in the art will also appreciate that numerous additional fields of data may be provided on a magnetic track in addition to a credit card number (or a security code). Dynamic information may be provided in such additional fields in order to complete a particular financial transaction. For example, such additional dynamic information may be numbers (or characters), encrypted with time and synced to software, at a validating server, operable to validate the encrypted number for a particular period of time.
Card 350 includes processor 360. RFID field detector 353 may provide information to processor 350. Additionally, magnetic stripe detectors may provide information to processor 350. An RFID receiver may produce an electromagnetic field that an RFID antenna is operable to electrically couple with and communicate information to. An RFID receiver may act as a source of electrical power to an RFID antenna. Such a power may be harvested (e.g., via RFID 210 of FIG. 2) to charge a rechargeable battery of a card or other device. An RFID field detector may thus be provided to detect an RFID field.
Emulator 351 may be able to generate electromagnetic fields of different frequencies and magnitudes, and operate in different manners, depending on drive signals provided by processor 360. Accordingly, emulator 351 may be driven to electrically couple with an RFID receiver and emulator 351 may also be driven to electrically couple with a magnetic stripe reader. Accordingly, processor 360 may drive emulator 351 to communicate information (e.g., payment information that includes dynamic information) to an RFID receiver when an RFID field is present and to a magnetic stripe reader when a magnetic stripe is present. Accordingly, for example, a multi-purpose emulator is provided. In instances where, for example, both an RFID field and a magnetic stripe reader is detected, processor 360 may select a default communications methodology (e.g., an RFID or magnetic stripe methodology). Processor 360 may be operable to communicate at least two different drive signals to emulator 351 (e.g., signals 391 and 392).
Card 400 shows card 400 that may include processor 400, emulator 401, read-heads 402 and 403, and magnetic stripe encoding receiver 420. Magnetic stripe encoding receiver 420 may be a coil such that a current is induced in the coil when a magnetic stripe encoder attempts to provide a signal that would encode a static magnetic track. Accordingly, receiver 420 may receive information via an encoder such that bi-directional communication can be established with a magnetic stripe reader that includes an encoding capability. Persons skilled in the art will appreciate that a magnetic emulator may be provided that can both transmit data to a read-head of a magnetic stripe reader as well as receive data from an encoding-head of a magnetic stripe reader.
Card 450 includes emulator 451 that includes active region 454 operable to communicate data serially to a magnetic stripe reader. Similarly, for example, emulator 451 may receive information for a magnetic stripe encoder. Persons skilled in the art will appreciate that emulator 451 includes a tail that is spread-out. Such a tail may include the return lines of emulator 451 and may be spaced such that a magnetic reader is not able to pick up the electromagnetic fields generated by such a tail. Accordingly, active region 454 may be spaced close together such that a magnetic stripe reader is able to pick up the cumulative electromagnetic field generated by such an active region. Processor 453 may drive emulator 451 via switching circuitry 452. Switching circuitry 452 may include, for example, one or more transistors that may be utilized to control the direction of current via emulator 451 (e.g., the polarity of voltage(s) across a drive resistor).
FIG. 5 shows flow chart 510 that may includes steps 511-513. Step 511 may be utilized to determine, of example, whether an RFID or a magnetic stripe reader is within the proximity of a card (or other device). Step 512 may be utilized to run an emulator as an RFID or magnetic stripe in response to step 511. Step 513 may be utilized to determine an RFID and magnetic stripe reader such that the process may be repeated.
Process 520 may be included and may include step 521 to detect a read-head. Step 522 may be included to transmit information using an emulator in a transmitting mode. Step 523 may be utilized to receive information from an emulator (or receiving coil) in a receiving mode. Persons skilled in the art will appreciate that an emulator may be operating in a receiving mode and a transmitting mode at the same time.
Process 530 may be included and may include step 531 to encode data into static magnetic tracks fabricated from a magnetic material. Step 532 may be provided to program data into a processor to be utilized in a subsequent step (e.g., step 533). Step 533 may be utilized to emulate data using an emulator driven by the data programmed in the processor.
FIG. 6 shows environment 600 that may include magnetic stripe reader 610, read-head housing 640, card 620, and magnetic emulator 630. Read-head housing 640 may include any number of read-head's such as, for example, one, two, or three read-heads. Each read-head may independently receive magnetic fields from magnetic emulator 630 (or a magnetic stripe, such as a magnetic stripe encoded on-card by card 620). Emulator 630 may be positioned to be adjacent to any one or more read-heads of read-head housing 640 or may be positioned to communicate information to any one or more read-heads of read-head housing 640. Persons skilled in the art will appreciate that emulators with longer lengths may be located within the proximity of one or more read-heads for a longer duration of time when a card is swiped. In doing so, for example, more information may be transmitted from an emulator to a read-head when a card is being swiped.
FIG. 7 includes environment 700 that may include cards 720 and 730 as well as magnetic stripe reader 710. Read-head housing 711 may be included on a wall of a trough of magnetic stripe reader 710. The trough may be sized to accept cards (e.g., credit cards).
Card 720 may include emulator 721. Emulator 721 may provide electromagnetic field 791 that may transmit through a portion of the housing of magnetic stripe reader 710 (e.g., through a wall of a trough to get to read-head housing 711). Accordingly, card 720 may be located outside of a reader—yet still be operable to communicate information to a magnetic stripe reader. A reader may be provided with an outer wall, for example, with a thickness of a quarter of an inch or more. Emulator 721 can provide electromagnetic field 791 over a distance of, for example, a quarter of an inch or more.
Persons skilled in the art will appreciate that card 720 may be coupled to a device via a permanent or removable cable. Such a device may provide power to card 720 as well as control information—such as control information for emulator 730. An external source of power may be utilized, for example, to provide a larger amount of electrical energy to emulator 721 than from a source of power located within card 720. Persons skilled in the art will appreciate that a car having an internal battery may still be able to receive a cable from a device having its own source of electrical energy.
Card 730 may be provided with emulator 731 and may electrically couple with a read-head of magnetic stripe reader 710. Any number of emulators may be provided in card 730 in any number of orientations such that the appropriate electromagnetic field may couple with a read head of read-head housing 711 regardless of the orientation of card 720 with respect to read-head 711. More particularly, for example, additional read-head housings may be provided in magnetic stripe reader 710 at different locations about the reader to electrically couple with a emulators in a number of different configurations. A sticker and/or guide-structures may be provided on a magnetic stripe reader to, for example, direct a user on how to position his/her card (or other device) for contactless transmission of data (e.g., credit card data) to a read-head housing without using the trough that includes that read-head housing.
Persons skilled in the art will appreciate that a magnetic stripe reader may include a trough that includes two (or more) read-head housings 711 located in approximately the same vertical position on a card-swiping trough, but at different horizontal locations on opposite walls of the trough. In doing so, for example, a magnetic stripe may be read regardless of the direction that a card having the magnetic stripe is facing when the card is swiped. Magnetic emulator 721 may, for example, communicate magnetic fields outside both the front and read surfaces of a card. Accordingly, a single emulator 721 may, for example, couple with a single read-head regardless of the direction the card was facing when swiped. In doing so, for example, the costs of readers may be reduced as only a single read-head may be need to receive information regardless of the direction a card is facing when swiped. Accordingly, magnetic readers do not need stickers and/or indicia to show a user the correct orientation to swipe a card through a magnetic stripe reader. An adapter may be provided that coupled directly to a read-head that allows a device not operable to fit in a trough to electrically couple with a read-head.
An dynamic magnetic communications device, such as a emulator, may be positioned about a surface of a card (or other device), beneath a surface of a device, or centered within a card. The orientation of a magnetic emulator in a card may provide different magnetic fields (e.g., different strength's of magnetic fields) outside different surfaces of a card. Persons skilled in the art will appreciate that a magnetic emulator may be printed via PCB printing. A card may include multiple flexible PCB layers (e.g., FR4 layers) and may be laminated to form a card. Portions of an electronic ink display may also be fabricated on a layer during a PCB printing process.
Magnetic shielding may be provided to limit an electromagnetic field of an emulator. For example, layer 810 may include magnetic shielding 811 (which may be a magnetic material). Magnetic shielding may block magnetic fields from emulator 851 on layer 820. Accordingly, for example, a card may not interact with read-heads blocked from emulator 851 from magnetic shielding 811. In doing so, for example, a magnetic stripe reader may receive information from a single read-head housing at any given time. Layer 830 may be provided, for example, with magnetic shielding 831 that includes an active-region space 832. Accordingly, layer 830 may block magnetic fields from emulator 851 except for those fields generated by active portion 854 (e.g., if space 832 is aligned with active portion 854).
FIG. 9 shows processes 900 that may include flow chart 910. Flow chart 910 may include step 911, in which a first layer of magnetic shielding may be provided (e.g., printed). Step 912 may be provided such that, for example, an emulator is provided (e.g., printed). Step 913 may be included such that, for example, a second layer of shielding may be provided (e.g., printed).
Flow chart 920 may be included. Step 921 may be included in flow chart 920. A read-head may be detected in step 921, a first level of current may be provided through an emulator in step 922, and the direction of the current through the emulator may be switched in step 923 in order to transmit data.
Flow chart 930 may be included. Step 931 may be included in flow chart 930. A button press may be detected in step 931, a second level of current may be provided through an emulator in step 932, and the direction of the current through the emulator may be switched in step 933 in order to transmit data. Flow chart 921 and 931 may be utilized together, for example, to provide a multi-function emulator. For example, an emulator may provide a magnetic-stripe signal to a magnetic stripe reader in flow chart 920 and may provide an RFID signal to an RFID receiver in flow chart 930.
Persons skilled in the art will appreciate that different emulators may be controlled by different switching circuitry (e.g., different transistors). Opto-isolators may be included to protect the processor from any voltage swings driving a magnetic emulator.
FIG. 10 shows card 1000 that may include, for example, one or more IC chips 1030 (e.g., EMV chips), RFID antennas 1020, processors 1040, displays 1050, dynamic magnetic communications devices 1010 (e.g., magnetic encoders and/or magnetic emulators), batteries 1060, and buttons 1051 and 1052. Additional circuitry 1098 may be provided which may be, for example, one or more oscillators or emulator driving circuits. Persons skilled in the art will appreciate that button 1051 may, for example, be utilized by a user to select one encryption algorithm for a number displayed on display 1050 while button 1052 may be utilized by a user to select a different encryption algorithm. Persons skilled in the art will appreciate that the components of card 1000 may be provided on either surface of a card (e.g., a front or rear surface of the card) or inside of a card. A logo (e.g., of a card issuer) and logo may be provided on either surface of a card.
A button, such as button 1051, may be utilized, for example, to display a number. Such a number may be, for example, encrypted from a secure number based on time or use. For example, one-time use numbers (e.g., a payment number or code) may be retrieved from a list of numbers on memory each time button 1051 is pressed and displayed on display 1050. A processor may only go through each number once on a list. A registration process may be provided in which a user may be requested to enter in a sequence of numbers such that a remote server may validate the card and learn where in a sequence of a list a card currently resides. Numbers may be repeated on a list or may only occur once on a list. All of the numbers available by the length of the number may be utilized by the list or only a portion of the numbers available by the length of the number may be provided by the list. A secret number may be encrypted on a card and a verification server may also have knowledge of this secret number. Accordingly, the remote server may perform the same encryption function as the card on the secret number and verify that the resultant encrypted number is the same as the resultant encrypted number on a card. Alternatively, for example, the remote server may decrypt the received encrypted number to determine the authenticity of the encrypted number and validate an activity (e.g., validate a security access request or a purchase transaction).
FIG. 11 shows card 1100 that may include, for example, signature area 1140 that may include a material operable to receive marks from a pen (e.g., a signature). Card 1100 may also include, for example, displays 1120 and 1130. Display 1120 may, for example, display a payment number while display 1130 displays a security code (e.g., for online purchase authentication). Display 1120 as well as display 1130 may be utilized on the same side as, for example, dynamic magnetic communications device 1110.
FIG. 12 shows personal electronic device 1200 which may be, for example, a portable telephonic device, portable media player, or any type of electronic device. Persons skilled in the art will appreciate that the functionality of a card may be provided on a personal device and displayed through a graphical user interface. Personal electronic device 1200 may include, for example, user inputs 1240 and display 1210. Virtual card 1220 may be displayed on display 1220. Display 1220 may be a touch-sensitive display such that, for example, virtual button 1230 may be provided on virtual card 1220. Persons skilled in the art will appreciate that cards may be provided as virtual cards and a user may interact with such virtual cards in order to provide a variety of functions. Personal electronic device 1200 may communicate to a card reader such as, for example, an RFID reader.
Persons skilled in the art will appreciate that a string of a particular bit of data (e.g., a string of logic zeros “0s”) may be communicated before as well as after information is communicated through a magnetic emulator. A magnetic stripe reader may utilize such data, for example, to determine base timing information such that the magnetic stripe reader has a timing reference that the reader can utilize to assist in determining timing changes of perceived flux transverals. Accordingly, for example, a magnetic emulator may send data at different overall frequencies and a magnetic stripe reader may be able to reconfigure itself to receive data at such overall frequencies. Information may be encoded using, for example, Frequency/Double Frequency (F2F) encoding such that magnetic stripe readers may perform, F2F decoding.
an emulator operable to electrically couple to a read-head of a magnetic stripe reader;
an RFID operable to electrically couple to a RFID reader; and
a processor for controlling the emulator; and
wherein the emulator is operable to electrically couple to and communicate the data to the read-head when the device is located outside and within proximity of the magnetic stripe reader.
2. The device of claim 1, wherein the device is thicker than a credit card.
3. The device of claim 1, wherein the device is a wireless communication device.
4. The device of claim 1, wherein the device is a portable telephonic device.
5. The device of claim 1, wherein the device is a portable media player.
6. The device of claim 1, further comprising a display operable to display a virtual card.
7. The device of claim 1, further comprising a touch-sensitive display operable to display a virtual card.
8. The device of claim 1, wherein the processor is operable to drive the emulator to electrically couple to the read-head and then to drive the emulator to electrically couple to the RFID reader after driving the emulator to electrically couple to the read-head.
9. The device of claim 1, wherein the processor is operable to drive the emulator to electrically couple to the read-head and, in parallel, to drive the emulator to electrically couple to the RFID reader.
10. The device of claim 1, wherein the processor is operable to drive the emulator to electrically couple to the RFID reader and then to drive the emulator to electrically couple to the read-head after driving the emulator to electrically couple to the RFID reader.
11. The device of claim 1, wherein the emulator comprises a magnetic emulator and an RFID antenna.
12. The device of claim 1, wherein the RFID is an RFID receiver detector.
13. The device of claim 1, wherein the RFID is operable to receive electrical power.
wherein the RFID is operable to receive electrical power and recharge the rechargeable battery with the electrical power.
wherein the RFID is operable to receive electrical power from and RFID receiver and recharge the rechargeable battery with the electrical power.
wherein the device is operable to wirelessly recharge the rechargeable battery.
17. The device of claim 1, wherein the device is operable to communicate payment card information from the RFID and the emulator during a transaction.
18. The device of claim 1, wherein the device is operable to communicate payment card information from the RFID and the emulator during a transaction, the payment card information being communicated from the RFID before being communicated from the emulator.
4077242 March 7, 1978 Sedley
4296315 October 20, 1981 Weimer et al.
4789776 December 6, 1988 Inoue
5166774 November 24, 1992 Banerji et al.
5288942 February 22, 1994 Godfrey
5434400 July 18, 1995 Scherzer
5521831 May 28, 1996 May
5535078 July 9, 1996 Warwick
5671271 September 23, 1997 Henderson et al.
5838549 November 17, 1998 Nagata et al.
5844230 December 1, 1998 Lalonde
5883377 March 16, 1999 Chapin
5886874 March 23, 1999 Onoda et al.
5941375 August 24, 1999 Kamens et al.
6012636 January 11, 2000 Smith
6241149 June 5, 2001 Baitz et al.
6402029 June 11, 2002 Gangi
6425061 July 23, 2002 Kaise et al.
6552869 April 22, 2003 Takahashi et al.
6574058 June 3, 2003 Aruga et al.
6883714 April 26, 2005 Keogh
7039221 May 2, 2006 Tumey et al.
7073721 July 11, 2006 Kano et al.
7093757 August 22, 2006 Boucher et al.
7195160 March 27, 2007 Ison et al.
7357319 April 15, 2008 Lin et al.
7364092 April 29, 2008 Narendra et al.
7370805 May 13, 2008 Smith et al.
7375631 May 20, 2008 Moskowitz et al.
7441709 October 28, 2008 Chan et al.
7461788 December 9, 2008 Iwamura
7591416 September 22, 2009 Blossom
7900845 March 8, 2011 Stagg
7946501 May 24, 2011 Borracci
7954725 June 7, 2011 Blythe
7996318 August 9, 2011 Marcon
8181874 May 22, 2012 Wan
8245923 August 21, 2012 Merrill, Jr. et al.
8286876 October 16, 2012 Mullen et al.
8485446 July 16, 2013 Mullen et al.
8517276 August 27, 2013 Mullen et al.
20010009485 July 26, 2001 Furuya
20010050247 December 13, 2001 Myer, Sr.
20020032657 March 14, 2002 Singh
20020043566 April 18, 2002 Goodman et al.
20020070976 June 13, 2002 Tanner et al.
20020073025 June 13, 2002 Tanner et al.
20020073042 June 13, 2002 Maritzen et al.
20020153424 October 24, 2002 Chuan
20020188505 December 12, 2002 Burrus, IV
20030030935 February 13, 2003 Yamamoto
20030071120 April 17, 2003 Orii
20030085286 May 8, 2003 Kelley et al.
20030098780 May 29, 2003 Taylor et al.
20030111527 June 19, 2003 Blossom
20030209608 November 13, 2003 Blossom
20040011877 January 22, 2004 Reppermund
20040055770 March 25, 2004 Babb
20040064302 April 1, 2004 Cunin
20040117514 June 17, 2004 Nelms
20040150091 August 5, 2004 Stobbs
20040159700 August 19, 2004 Khan et al.
20040205273 October 14, 2004 Mowery et al.
20040212831 October 28, 2004 Imai et al.
20040251303 December 16, 2004 Cooper
20050006482 January 13, 2005 Kano et al.
20050068868 March 31, 2005 Hasegawa
20050092830 May 5, 2005 Blossom
20050133590 June 23, 2005 Rettenmyer et al.
20050133606 June 23, 2005 Brown
20050178835 August 18, 2005 Akiho et al.
20050194452 September 8, 2005 Nordentoft et al.
20050230788 October 20, 2005 Kato et al.
20050274803 December 15, 2005 Lee
20060017570 January 26, 2006 Moskowitz et al.
20060017571 January 26, 2006 Arnold et al.
20060054699 March 16, 2006 Osterweil
20060085043 April 20, 2006 Stevenson
20060124748 June 15, 2006 Osborn et al.
20060131396 June 22, 2006 Blossom
20060161789 July 20, 2006 Doughty et al.
20060186209 August 24, 2006 Narendra et al.
20060187055 August 24, 2006 Colby
20060213973 September 28, 2006 Chan et al.
20060217792 September 28, 2006 Hussein et al.
20060227523 October 12, 2006 Pennaz et al.
20060241236 October 26, 2006 Kuznetsov et al.
20060249574 November 9, 2006 Brown et al.
20060262655 November 23, 2006 Persson
20060283958 December 21, 2006 Osterweil
20070023532 February 1, 2007 Narendra et al.
20070029110 February 8, 2007 Matsumoto et al.
20070034700 February 15, 2007 Poidomani
20070063804 March 22, 2007 Watanabe
20070136211 June 14, 2007 Brown et al.
20070152052 July 5, 2007 Sines
20070158439 July 12, 2007 Conner et al.
20070189591 August 16, 2007 Nordentoft et al.
20070267503 November 22, 2007 Dewan
20070290049 December 20, 2007 Ratcliffe
20080093467 April 24, 2008 Narendra et al.
20080116283 May 22, 2008 Newbrough
20080116285 May 22, 2008 Shoemaker
20080121726 May 29, 2008 Brady et al.
20080126262 May 29, 2008 Brady et al.
20080148393 June 19, 2008 Wendt
20080150123 June 26, 2008 Li et al.
20080217396 September 11, 2008 Boalt
20080223937 September 18, 2008 Preta et al.
20080227437 September 18, 2008 Lewis
20080262825 October 23, 2008 Haid
20080290166 November 27, 2008 von Mueller
20090006262 January 1, 2009 Brown et al.
20090023476 January 22, 2009 Saarisalo et al.
20090026277 January 29, 2009 Phillips
20090048971 February 19, 2009 Hathaway et al.
20090055893 February 26, 2009 Manessis et al.
20090078761 March 26, 2009 Sines
20090134218 May 28, 2009 Yuzon et al.
20090159668 June 25, 2009 Mullen
20090159670 June 25, 2009 Mullen
20090159682 June 25, 2009 Mullen
20090159704 June 25, 2009 Mullen
20090159710 June 25, 2009 Mullen
20090166435 July 2, 2009 Blythe
20090206165 August 20, 2009 Laackmann et al.
20090261167 October 22, 2009 Iwayama
20090261161 October 22, 2009 Blossom
20090296605 December 3, 2009 Lewis
20100127830 May 27, 2010 Nielsen et al.
20100265617 October 21, 2010 Isuyama
20100270373 October 28, 2010 Poidomani et al.
20110084149 April 14, 2011 Faith et al.
20110117838 May 19, 2011 Bosquet et al.
20110140538 June 16, 2011 Jung et al.
20110140841 June 16, 2011 Bona et al.
20110174874 July 21, 2011 Poznansky et al.
20110178924 July 21, 2011 Briscoe et al.
20110218911 September 8, 2011 Spodak
20110240748 October 6, 2011 Doughty et al.
20110272465 November 10, 2011 Mullen et al.
20110272475 November 10, 2011 Mullen et al.
20110272482 November 10, 2011 Mullen et al.
20110278364 November 17, 2011 Mullen et al.
20120196530 August 2, 2012 Moosavi et al.
20120235797 September 20, 2012 Poidomani et al.
20120241524 September 27, 2012 Blot et al.
20120286037 November 15, 2012 Mullen et al.
20120286936 November 15, 2012 Mullen et al.
20120318871 December 20, 2012 Mullen et al.
20130024372 January 24, 2013 Spodak et al.
20130083787 April 4, 2013 Restiau et al.
20130140360 June 6, 2013 Graylin
20130146661 June 13, 2013 Melbrod et al.
20130214044 August 22, 2013 Sperduti et al.
20130248591 September 26, 2013 Look et al.
20130320080 December 5, 2013 Olson et al.
20140138447 May 22, 2014 Goldman et al.
20140138449 May 22, 2014 Goldman et al.
20140144984 May 29, 2014 Olson et al.
20140183258 July 3, 2014 DiMuro
20140263385 September 18, 2014 Martin
20140293980 October 2, 2014 Shibata
20150069126 March 12, 2015 Leon
20150073983 March 12, 2015 Bartenstein et al.
20150134513 May 14, 2015 Olson et al.
0203683 December 1986 EP
2420098 May 2006 GB
11087989 March 1999 JP
2004165400 December 2005 JP
WO06066322 June 2006 WO
WO06080929 August 2006 WO
WO06105092 October 2006 WO
WO06116772 November 2006 WO
WO07141779 December 2007 WO
WO08064403 June 2008 WO
USPTO, International Search Report, dated Apr. 28, 2009.
EPO, Extended European Search Report, dated Jan. 26, 2012.
Patent Examination Report No. 1, Australian Patent Application No. 2008340226, dated Oct. 11, 2012.
Article 94(3) EPC communication in European Patent Application No. 08865573.3-2221, dated Feb. 5, 2013.
Magnetic stripe card, Mindmatrix (this document is presented by the European Patent Office without a link).
Summons to Oral Proceedings in European Patent Application No. 08865573.3-2221, dated Sep. 18, 2013.
Patent Publication Number: 20160342878
Inventors: Jeffrey D. Mullen (Glenshaw, PA), David Lambeth (Pittsburgh, PA), Bruce Cloutier (Jeanette, PA)
Application Number: 15/225,122
International Classification: G06K 19/08 (20060101); G06K 19/06 (20060101); G06K 19/07 (20060101); G06K 19/077 (20060101); G06Q 20/18 (20120101); G06Q 20/20 (20120101); G06Q 20/34 (20120101); G06Q 20/38 (20120101); G06Q 30/02 (20120101); G06Q 30/06 (20120101); G07F 7/08 (20060101); G07F 7/10 (20060101); G06K 7/08 (20060101); G06K 19/073 (20060101); G06K 7/00 (20060101); G06F 3/0488 (20130101); G06K 7/10 (20060101); G06Q 20/40 (20120101);