Method and apparatus for transmitting data via NFC for mobile applications including mobile payments and ticketing

Information

  • Patent Grant
  • 11694053
  • Patent Number
    11,694,053
  • Date Filed
    Thursday, February 18, 2021
    3 years ago
  • Date Issued
    Tuesday, July 4, 2023
    a year ago
Abstract
A mobile device includes a smartcard controller that does not rely on power received from an interrogating RF field. The mobile device also includes a small inductive device capable of inductive coupling with an RFID reader. The smartcard controller includes circuitry to modulate an impedance of a port coupled to the inductive element when in the presence of an interrogating RF field at substantially 13.56 MHz.
Description
FIELD

The present invention relates generally to contactless communications devices, and more specifically to contactless smartcard devices.


BACKGROUND

RFID “tags” can be separated into two broad categories: active tags and passive tags. Active tags are characterized by a local power source such as a battery. Active tags generally transmit information by broadcasting on an RF carrier frequency of choice using a locally generated RF carrier. Active tags are typically used to transmit over long distances, often referred to as “far field communications” (FFC). Antennas used with active RFID tags tend to be large to allow for the communications over long distances.


Passive tags are not powered. Passive tags derive the energy needed to power the tag from an interrogating RF field, and use that energy to transmit response codes by modulating the impedance that the antenna presents to the interrogating field, thereby modulating the signal reflected back to the reader antenna. Passive tags are typically used to transmit over short distances, often referred to as “near field communications” (NFC). For example, passive tags operating at 13.56 MHz are typically designed to communicate with RFID readers a few centimeters away.


Passive tags are typically connected to “loop antennas.” One example of a loop antenna is shown in U.S. Pat. No. 6,568,600, issued to Carpier et al. on May 27, 2003 (the '600 patent). The device described in the '600 patent is recognizable as a “credit card sized” passive RFID card (more specifically, a card that conforms to ISO 7816 size requirements). The loop antenna is necessarily large because passive tags are powered using energy received by the antenna from signals transmitted by the RFID reader.



FIG. 12 shows a power supply voltage developed over time by rectifying a voltage induced in a loop antenna in the presence of an interrogating RF field. Once the power supply voltage reaches a critical value, the tag is powered up and can operate. As the antenna size is reduced, it takes longer for the power supply voltage to reach the critical value, and the tag operation may not meet response time specifications. Below a certain antenna size, the power supply voltage may never reach the critical value, and the tag may never power up.


Antenna design for RFID applications is described in a Microchip Technology, Inc. application note entitled “Antenna Circuit Design for RFID Applications” by Youbok Lee, Ph.D., published in 2003 (no month given). Dr. Lee's application note describes in great detail how to determine size requirements for a passive RFID tag antenna to operate at 13.56 MHz. On page 5 of the application note, Dr. Lee shows that the optimum radius of the loop antenna coil is equal to 1.414 times the required read range. This analysis confirms that for a read range on the order of a few centimeters, a credit card sized loop antenna can be made near optimal.


Passive tags are seeing widespread use in many applications. For example, mobile device manufacturers are embedding passive RFID tags in mobile devices for NFC applications. Example mobile applications include, but are not limited to, ticketing and mobile payments. U.S. Pat. No. 7,333,062 issued to Leizerovich et al. on Feb. 19, 2008 (the '062 patent) shows a mobile phone with an integrated loop antenna for an NFC device. As shown in the '062 patent, the mobile phone provides the real estate necessary to implement a loop antenna at 13.56 MHz.


There have been attempts to implement passive tags in smaller mobile devices. These attempts have been met with limited success due in part to the size of the loop antenna. For example, FIG. 13 shows an RFID tag implementation in a secure digital (SD) memory card manufactured by Wireless Dynamics, Inc. of Calgary, Alberta, Canada. Card 1300 includes an antenna, but the SD card is significantly oversized as a result. Also for example, U.S. Patent Application Publication No.: US 2006/0124755 A1 shows a memory card having a passive tag, but the card must be inserted into a slot to access a loop antenna on a different device. In this implementation, mobile device real estate is still relied upon for loop antenna implementation. It can be seen, therefore, that the size of antennas are proving to be a barrier to further miniaturization of passive RFID tags.



FIG. 14 shows a prior art smartcard controller and antenna in combination. Smartcard controller 330 includes a contactless interface that includes two pads 1472 and 1474 intended for connection to a coil (antenna 1480). Smartcard controller 330 also includes bridge rectifier 1420 to rectify an alternating voltage present on pads 1472 and 1474 when antenna 1480 is inductively coupled to another device and in the presence of an interrogating RF field. Capacitor 1440 is typically tuned to create a resonant circuit at the frequency of interest (e.g., 13.56 MHz). When antenna 1480 is a large loop antenna, then bridge rectifier 1420 provides power to internal circuits as shown in FIG. 12. Demodulator 1430 demodulates data present in the interrogating RF field, and load modulation driver circuit 1410 modulates an impedance seen by the device presenting the interrogating RF field when the coil (antenna 1480) is inductively coupled to a separate device that is presenting the interrogating RF field. This creates a half-duplex communications path between the device presenting the interrogating RF field and smartcard controller 330. Examples of smartcard controllers are the “SmartMX” controllers sold by NXP Semiconductors N.V. of Eindhoven, The Netherlands.


A need exists for a small footprint RFID tag that does not rely on an external device to house an antenna. A need also exists for a memory card compatible RFID tag that is compatible with standard memory card slots on mobile devices.





BRIEF DESCRIPTION OF THE DRAWINGS


FIG. 1 shows a mobile computing device and a small RFID card compatible with a memory card slot;



FIG. 2 shows a block diagram of a mobile computing device;



FIGS. 3A-3B show block diagrams of memory card compatible RFID cards with integrated inductive elements;



FIG. 4 shows a memory card compatible RFID card with an integrated inductive element;



FIG. 5 shows a data portion of a memory card write command;



FIGS. 6-11 show flowcharts of methods in accordance with various embodiments of the present invention;



FIG. 12 shows a power supply voltage developed over time by rectifying a voltage induced in a loop antenna in the presence of an interrogating RF field;



FIG. 13 shows a prior art RFID tag implementation in a secure digital (SD) memory card;



FIG. 14 shows a prior art smartcard controller and antenna in combination;



FIG. 15 shows a smartcard controller with performance enhancement circuits including a load modulation driver circuit and an antenna in accordance with various embodiments of the present invention;



FIG. 16 shows frequency spectrum used in RFID communications;



FIG. 17 shows a smartcard controller with performance enhancement circuits including a load modulation driver circuit and separate receive and transmit antennas in accordance with various embodiments of the present invention;



FIG. 18 shows frequency spectrum used in RFID communications;



FIG. 19 shows a smartcard controller with performance enhancement circuits including a load modulation driver circuit and multiple transmit antennas in accordance with various embodiments of the present invention;



FIG. 20 shows frequency spectrum used in RFID communications;



FIG. 21 shows a smartcard controller with performance enhancement circuits including an active transmit driver circuit and an antenna in accordance with various embodiments of the present invention;



FIG. 22 shows a smartcard controller with performance enhancement circuits including an active transmit driver circuit and separate receive and transmit antennas in accordance with various embodiments of the present invention;



FIG. 23 shows a smartcard controller with performance enhancement circuits including an active transmit driver circuit and multiple transmit antennas in accordance with various embodiments of the present invention;



FIG. 24 shows a smartcard controller with a pad to provide digital data output;



FIG. 25 shows a smartcard controller with digital data output and performance enhancement circuits including a load modulation driver circuit and an antenna in accordance with various embodiments of the present invention;



FIG. 26 shows a smartcard controller with digital data output and performance enhancement circuits including a load modulation driver circuit and separate receive and transmit antennas in accordance with various embodiments of the present invention;



FIG. 27 shows a smartcard controller with digital data output and performance enhancement circuits including a load modulation driver circuit and multiple transmit antennas in accordance with various embodiments of the present invention;



FIG. 28 shows a smartcard controller with digital data output and performance enhancement circuits including an active transmit driver circuit and an antenna in accordance with various embodiments of the present invention;



FIG. 29 shows a smartcard controller with digital data output and performance enhancement circuits including an active transmit driver circuit and separate receive and transmit antennas in accordance with various embodiments of the present invention;



FIG. 30 shows a smartcard controller with digital data output and performance enhancement circuits including an active transmit driver circuit and multiple transmit antennas in accordance with various embodiments of the present invention;



FIGS. 31-34 show performance enhancing application specific integrated circuits (ASICs) coupled to various smartcard controllers in accordance with various embodiments of the present invention;



FIG. 35 shows a memory card with integrated smartcard controller, performance enhancement circuits and antennas in accordance with various embodiments of the present invention;



FIG. 36 shows a memory card with integrated smartcard controller and performance enhancement circuits in accordance with various embodiments of the present invention;



FIG. 37 shows a subscriber identity module (SIM) card with integrated smartcard controller, performance enhancement circuits and antennas in accordance with various embodiments of the present invention;



FIG. 38 shows a subscriber identity module (SIM) card with integrated smartcard controller and performance enhancement circuits in accordance with various embodiments of the present invention; and



FIG. 39 shows a mobile device with a smartcard controller, enhancement circuits, and antenna(s).





DESCRIPTION OF EMBODIMENTS

In the following detailed description, reference is made to the accompanying drawings that show, by way of illustration, various embodiments of an invention. These embodiments are described in sufficient detail to enable those skilled in the art to practice the invention. It is to be understood that the various embodiments of the invention, although different, are not necessarily mutually exclusive. For example, a particular feature, structure, or characteristic described in connection with one embodiment may be implemented within other embodiments without departing from the spirit and scope of the invention. In addition, it is to be understood that the location or arrangement of individual elements within each disclosed embodiment may be modified without departing from the spirit and scope of the invention. The following detailed description is, therefore, not to be taken in a limiting sense, and the scope of the present invention is defined only by the appended claims, appropriately interpreted, along with the full range of equivalents to which the claims are entitled. In the drawings, like numerals refer to the same or similar functionality throughout the several views.



FIG. 1 shows a mobile computing device and a small RFID card compatible with a memory card slot. Mobile computing device 110 is shown as a mobile phone in FIG. 1, but this is not a limitation of the present invention. For example, mobile computing device 110 may be a personal digital assistant (PDA), a smartphone, a mobile phone, a handheld computer, a desktop computer, or any other device capable of operating as described herein.


Mobile computing device 110 includes memory card slot 112. Memory card slot 112 is a slot capable of accepting RFID card 120. For example, memory card slot 112 may have physical dimensions compatible with RFID card 120, and may have a communications interface that operates using a protocol compatible with RFID card 120. In some embodiments of the present invention, memory card slot 112 is a memory card slot designed to accept and communicate with memory cards. As used herein, the term “memory card slot” refers to any add-on slot capable of accepting a card having memory accessible by a mobile computing device such as that shown in FIG. 1. For example, a memory card slot may be compatible with an industry standard communications protocol, or may be compatible with a widely accepted communications protocol that is not necessarily formally documented as an industry standard. Examples include slots that are compatible with the Multimedia Memory Card (MMC) protocol, Memory Stick DUO protocol, secure digital (SD) protocol, and Smart Media protocol. The foregoing list is meant to be exemplary, and not exhaustive. Memory card slot 112 may be compatible with many memory card slot protocols other than those explicitly listed above without departing from the scope of the invention. Further, in some embodiments, memory card slot 112 accepts a subscriber identity module (SIM) card. Memory card slot 112 may be exposed on an edge of mobile computing device 110 as shown, or may be behind a cover. For example, memory card slot 112 may be behind a battery cover, behind a battery, or anywhere else on mobile computing device 110.


RFID card 120 includes electrical contacts 122 as part of a host interface that communicates with memory card slot 112. For example, electrical contacts 122 may provide connectivity compliant with a communications protocol for memory cards. RFID card 120 includes RFID functionality, and may also include memory accessible by mobile computing device 110. For example, in some embodiments, RFID card 120 includes a smartcard controller and an inductive element capable of interacting with an NFC reader (e.g., an ISO 14443 compliant interface). In other embodiments, RFID card 120 does not include memory accessible by mobile computing device 110. RFID card 120 may include functionality beyond memory and RFID. Electrical contacts 122 may also be compliant with a smartcard “contact” interface (e.g., ISO 7816).


In various embodiments of the present invention, the RFID functionality in RFID card 120 is accessed by mobile computing device 110 using memory card access commands already defined for use in memory card slot 112. Accordingly, the various embodiments of the present invention enable the implementation of RFID functions beyond memory accesses without defining new commands. In some embodiments, new commands for the RFID card are embedded inside the data bits subsequent to memory card read/write commands. RFID card 120 then decides if the incoming data bits are meant for regular read/write memory functions or for RFID functions. In other words, functions in addition to standard memory card functions may be accessed through commands “hidden” in the data stream that can be exchanged using existing memory card access commands and functions. According to the various embodiments of the invention, both existing memory card functions and RFID functions may be implemented without requiring changes in how the host protocol is built.


The combination of mobile computing device 110 and RFID card 120 may be used for any purpose. For example, in some embodiments, RFID card 120 may interact with a point-of-sale payment device to effect mobile payments. Also for example, in some embodiments, RFID card 120 may be used in wave-and-pay ticketing in mass transit environments, such as MIFARE.



FIG. 2 shows a block diagram of a mobile computing device. Mobile computing device 110 includes antenna 240, radio circuits 230, processor 210, memory 220, and memory card slot 112. In some embodiments, mobile computing device 110 is a mobile phone, or includes mobile phone functionality. For example, antenna 240 and radio circuits 230 may be utilized to communicate with a cellular telephone network. Further, in some embodiments, mobile computing device 110 is a wireless local area network (WLAN) or wireless wide area network (WWAN) device. For example, antenna 240 and radio circuits 230 may be utilized to communicate with a wireless access point. In some embodiments, antenna 240 and radio circuits 230 are omitted, and mobile computing device 110 does not utilize wireless connectivity.


Processor 210 represents a processor capable of communicating with the other blocks shown in mobile computing device 110. For example, processor 210 may be a microprocessor, a digital signal processor (DSP), a microcontroller, or the like. Further, processor 210 may be formed from state machines or other sequential logic. In operation, processor 210 may read instructions from memory 220 and perform actions in response thereto. For example, processor 210 may execute program instructions that influence communications between mobile computing device 110 and a device coupled to memory card slot 112.


Memory card slot 112 is described above with reference to FIG. 1. Memory card slot 112 includes circuitry compatible with RFID card 120. Mobile computing device 110 may communicate with RFID card 120 by using a standard set of memory card access commands. For example, processor 210 may use memory card write commands to write to memory in RFID card 120, and may use memory card read commands to read from memory in RFID card 120. Mobile computing device 110 may also communicate with RFID card 120 using an ISO 7816 compatible interface or the like. For example, when RFID card 120 is a SIM card, mobile computing device 110 may communicate with a smartcard controller within the SIM card.


Mobile computing device 110 may access the RFID functionality in RFID card 120 using “hidden” commands embedded in memory card access commands. For example, a memory card write command may include a unique data string to identify the memory card write command as a command to be diverted for purposes other than a memory write. In addition, the sector address provided with the memory card write command may be set to a particular address value to further identify the memory card write command as a command to be diverted. In addition to specific address/data values to identify the memory card access command as a command to be diverted for a purpose other than a memory access, the memory access command may include data bits to further specify the type and function of hidden command. Example formats of hidden commands are described further below. In some embodiments, a read command is issued right after a write command to enable data flow from the non-memory card functions to the host, where the write command's data had the hidden commands. The combination of a memory card write command and a memory card read command can be used in this manner to form a hidden read command.


In some embodiments, memory card slot 112 is powered down after periods of inactivity to save power. For example, memory card slot 112 may be powered up when processor 210 issues a memory card write or read command, but may then be powered down to save power. When memory card slot 112 is powered down, any device coupled to the memory card slot is also powered down. For example, if RFID card 120 (FIG. 1) is coupled to the memory card slot, then RFID card 120 is powered down when memory card slot 112 is powered down.


In various embodiments of the present invention, processor 210 executes software resident in memory 220 to maintain power to memory card slot 112 (and to RFID card 120). For example, periodic hidden commands may be sent to RFID card 120 for the purpose of keeping power applied while RFID card 120 is expected to be providing RFID functionality. Also for example, a hidden command may be sent to RFID card 120 for the purpose of cycling power to a smartcard controller resident on the card. These hidden commands are described further below with respect to later figures.



FIG. 3A shows a block diagram of a memory card compatible RFID card with an integrated inductive element. RFID card 300 represents possible embodiments of RFID card 120 (FIG. 1). RFID card 300 includes host interface 310, memory card controller 340, memory 360, smartcard controller 340, program memory 332, and small inductive element 350. RFID card 300 is capable of communicating with a memory card slot in a mobile computing device. Further, RFID card 300 does not require memory card slots to implement extended input/output functions. For example, and not by way of limitation, in SD and micro SD embodiments, RFID card 300 is operable in any SD or microSD memory card slot, and does not require a secure digital input output (SDIO) memory card slot.


Host interface 310 includes electrical contacts to interface with a memory card slot. For example, host interface 310 includes contacts such as contacts 122 (FIG. 1). Also for example, in some embodiments, host interface 310 includes recessed electrical contacts. Host interface 310 may also include circuitry such as drivers, receivers, terminations, and the like.


In embodiments represented by FIG. 3A, memory card controller 340 communicates with the mobile device using memory card access commands. Memory card controller 340 also communicates with memory 360. Memory card controller 340 determines whether each command should result in a memory operation with memory 360, whether a hidden command should be diverted to smartcard controller 330, or whether memory card controller 340 should take action in response to a hidden command. In some embodiments, memory card controller 340 executes instructions that are stored in an internal memory or stored in memory 360. In some embodiments, memory card controller 340 includes special purpose hardware useful to determine whether a command should be diverted. In other embodiments, memory card controller 340 may be a microcontroller identical in all respects to a controller found in memory cards, except for the program that it executes.


Memory 360 may be any type of volatile or non-volatile memory. For example, memory 360 may be volatile memory such as static random access memory (SRAM) or dynamic random access memory (DRAM). Also for example, memory 360 may be nonvolatile memory such as NOR FLASH memory or NAND FLASH memory. In various embodiments of the present invention, memory 360 represents memory that is accessed by a mobile computing device using memory card access commands defined for that purpose.


When RFID card 300 is communicating with a memory card slot in a mobile computing device, the mobile computing device may send a memory card access command in order to access memory 360. Also, for example, the mobile computing device may send a memory card access command that contains a hidden command. Memory card controller 340 detects the presence of the hidden command, and diverts all or a portion of the memory access command to smartcard controller 330 using communication bus 342. Communication bus 342 may have any number of conductors and may take any form. For example, communication bus 342 may be a serial port, a parallel port, or may include multiple data conductors, multiple address conductors, and/or conductors to carry control signals such as clock signals. In some embodiments, memory card controller 340 takes one or more actions in response to a hidden command. For example, memory card controller 340 may modify clock signals in response to a hidden command.


Memory card controller 340 can detect the hidden command in many ways. For example, in some embodiments, the memory card access command may include a specific address value or a specific data value. Memory card controller 340 detects commands that include one or both of the specific address value or specific data value and routes the command appropriately. The specific address value and specific data value used for this purpose are referred to herein as the hidden command address value and the hidden command data value.


In some embodiments, memory card controller 340 detects the presence of hidden commands based only on the hidden command address value. In these embodiments, memory card controller 340 checks the address value included in a memory card access command, and diverts the command (or takes some other action) if it matches the hidden command address value. In some embodiments, memory card controller 340 detects the presence of hidden commands based only on the hidden command data value. In these embodiments, memory card controller 340 checks a data value included in the memory card access command, and diverts all or a portion of the command if it matches the hidden command data value. In still further embodiments, memory card controller 340 detects the presence of hidden commands based on both the hidden command address value and the hidden command data value. In these embodiments, memory card controller 340 diverts the command only if both the memory card access address and data match the hidden command address value and data value, respectively.


The hidden command address value and hidden command data value may be specified in many ways. For example, all RFID cards may be issued with fixed values. In these embodiments, each time the RFID functions are accessed, the same hidden command address and/or data value is included in the memory card access command. Also, for example, different RFID cards may be issued with unique values. In these embodiments, each RFID card may provide these values to a mobile computing device when queried. Also, for example, hidden command address and/or data values may be specified by the mobile computing device. In still further embodiments, hidden command address and data values may be dynamic. The hidden command address and data values may change each time power is applied or on a periodic basis.


Smartcard controller 330 receives hidden commands diverted by memory card controller 340. Smartcard controller 330 further interprets the hidden commands and performs actions in response thereto. Smartcard controller 330 executes instructions stored in program memory 332. In some embodiments, program memory 332 is embedded in smartcard controller 330, and in other embodiments, program memory 332 is part of memory 360.


Smartcard controller 330 is a dual interface smartcard controller with one of the interfaces including RFID functionality. In some embodiments, smartcard controller 330 is compatible with passive RFID tag readers in NFC applications. For example, smartcard controller 330 may be a device capable of implementing all or part of the ISO 14443 standard for contactless NFC devices. Also, for example, smartcard controller 330 may be a dual interface smartcard controller capable of implementing both ISO 7816 and ISO 14443 standards for contact/contactless requirements. The “SmartMX” family of controllers available from NXP Semiconductors N.V. of The Netherlands are examples of suitable dual interface smartcard controllers. These controllers provide RFID functionality at 13.56 MHz. The various embodiments of the present invention operate at 13.56 MHz, but are not limited to operation at this frequency. In some embodiments, smartcard controller interoperates with MIFARE systems for ticketing applications.


Smartcard controller 330 receives power from the host interface. By not receiving power from the interrogating RF field, the necessity of a loop antenna for power generation is negated. Smartcard controller 330 includes a contactless interface that in turn includes antenna port 334. Antenna port 334 includes at least two pads for connection to an antenna, shown as 1742 and 1744 in FIG. 14 and later figures. In FIG. 3A, antenna port 334 is coupled to small inductive element 350.


Small inductive element 350 includes a coil wound around a magnetic core. As described with reference to later figures, small inductive element may include one or more coils or antennas. The coil of small inductive element is too small to draw power from the interrogating RF field, but this is not necessary since smartcard controller 330 is powered by the host device through host interface 310. Small inductive element 350 interacts with an antenna in an RFID reader similar to the way that primary and secondary coils in a transformer interact. The RFID reader has a coil resonant at 13.56 MHz functioning as the primary coil of a transformer. Small inductive element 350 functions as the secondary coil of the transformer. Accordingly, the transmitter “sees” the impedance of the secondary coil (small inductive element 350). Smartcard controller 330 is able to modulate reflected RF signals using circuitry to modify the impedance at the antenna port 334.


Small inductive element 350 can be made very small. For example, in some embodiments, RFID card 120 is a miniSD card, microSD card, or SIM card, and small inductive element 350 is small enough to be completely contained in the miniSD, microSD, or SIM form factor. A specific embodiment of a small inductive element in a memory card form factor is described below with reference to FIG. 4.


In various embodiments of the invention, memory card controller 340 and smartcard controller 330 are implemented in many different ways. For example, in some embodiments, the various components are implemented in hardware. In these embodiments, the various components may be implemented as separate integrated circuits, or in a combined integrated circuit. Also, for example, in some embodiments, the various components may be implemented in software, or in a combination of hardware and software. In some embodiments, RFID card 300 may include a microprocessor, and the components may be implemented as software modules running on the microprocessor. In other embodiments, RFID card 300 may include multiple processors, and the components may be implemented as software modules distributed across the multiple processors.



FIG. 3B shows a block diagram of a memory card compatible RFID card with an integrated inductive element. RFID card 302 represents possible embodiments of RFID card 120 (FIG. 1). RFID card 302 includes host interface 310, memory card controller 340, memory 360, smartcard controller 340, program memory 332, and small inductive element 350, all of which are described above with reference to FIG. 3A. RFID card 302 is capable of communicating with a memory card slot in a mobile computing device. Further, RFID card 302 does not require memory card slots to implement extended input/output functions. For example, and not by way of limitation, in SD and microSD embodiments, RFID card 302 is operable in any SD or microSD memory card slot, and does not require a secure digital input output (SDIO) memory card slot.


In embodiments represented by FIG. 3B, smartcard controller 330 receives power from memory controller 340. In these embodiments, memory controller 340 has direct control over the power provided to smartcard controller 330. Memory controller 340 may apply and/or remove power from smartcard controller 330 in response to commands received over the host interface. For example, memory controller 340 may receive a hidden command to reset smartcard controller 330 by causing a reboot through a power cycle.



FIG. 4 shows a memory card compatible RFID card with an integrated inductive element. RFID card 120 is shown in an SD card form factor, although this is not a limitation of the present invention. For example, other form factors within the scope of the present invention include, but are not limited to, microSD form factors and SIM card form factors. RFID card 120 includes electrical contacts 122, memory card controller 340, smartcard controller 330, memory 360, magnetic core 450, and coil 452, all affixed to circuit board 402.


Magnetic core 450 and coil 452 implement small inductive element 350 (FIGS. 3A, 3B). As can be seen in FIG. 4, the small inductive element fits entirely within the memory card form factor. The small inductive element does not provide power generation for smartcard controller 330, and so does not need to be made large for that purpose.



FIG. 5 shows a data portion of a memory card write command. Included are hidden command data value 510, status field 520, password field 530, device ID 532, command index 540, and hidden command related data 550. In the example of FIG. 5, the data portion is 512 bytes in length, although this is not a limitation of the present invention. Any amount of data may be included in the write command, and each field shown in FIG. 5 may be any length.


In the example of FIG. 5, the hidden command data value is 256 bits long, although any length may be used without departing from the scope of the present invention. In some embodiments, hidden command data value 510 is used to identify a memory write command as a hidden command. When a write command is received having data in the first 256 bits that match the hidden command data value, the command is identified as one to be diverted to the smartcard controller. As described above, a hidden command address value may be used in conjunction with, or instead of, a hidden command data value to identify the memory write command as a hidden command.


The remaining fields have significance when the memory write is a hidden command. For example, if the first 256 bits do not match the hidden command data value (or if the write address does not match the hidden command address value, or both) then the remaining bits in the data field are to be treated as data in a normal memory write command. In contrast, when the memory write is a hidden command, the remaining fields are used to further interpret the hidden command.


Memory card controller 340 (FIGS. 3, 4) inspect the hidden command data value 510, status field 520, and possibly password field 530 and device ID 532. In some embodiments, if the command is identified as a hidden command, memory card controller 340 forwards the password 530, command index 540, and related data 550 to smartcard controller 330. In other embodiments, memory card controller 340 may directly take actions based on the hidden command.


Status field 520 may include any information relating to the status of the hidden command. For example, status field 520 may include one or more bits to signify to memory card controller 340 whether the host (mobile computing device) is expecting the smartcard controller to return data in response to the hidden command. For example, when status field 520 signifies a write, memory card controller 340 forwards the password, device ID, command index, and related data without expecting to return any data to the host. Also for example, when status field 520 signifies a read, memory card controller 340 forwards the password, device ID, command index, and related data with the expectation that smartcard controller 330 may provide data to be sent to the host in response to a memory card read command. The combination of a memory card write command followed shortly thereafter by a memory card read command may be used to provide “read” functionality to the smartcard controller. Read operations from the smartcard controller are described further below with reference to FIG. 8.


Password field 530 includes a password to allow smartcard controller 330 to authenticate the host to the RFID card. In some embodiments, every hidden command includes a password. Each time the password, device ID, command index, and related data is diverted to the smartcard controller, the password is checked to authenticate the host to the RFID card.


Device ID 532 uniquely identifies the host (mobile computing device). The device ID may be checked by the smartcard controller to ensure that the RFID card is inserted in the host to which it is authenticated. Some embodiments of the present invention enforce a unique host/card pairing using the device ID, and other embodiments allow smartcard controller functions to be accessed by any host.


Command index 540 identifies the type of hidden command. The number of possible hidden commands is limited only by the number of bits allocated thereto. Any number of bits may be allocated to command index 540 without departing from the scope of the present invention. Hidden command related data 550 may be utilized differently for each type of hidden command. Any number of bits may be used for hidden command related data 550.


The data shown in FIG. 5 is provided as an example, and the data field of a memory card access command may include more or fewer data fields than those shown in FIG. 5. The present invention is not limited by the number or content of the fields in a memory card access command.



FIG. 6 shows a flowchart in accordance with various embodiments of the present invention. In some embodiments, method 600 may be used by a mobile computing device to communicate with an RFID card in a memory card slot. In some embodiments, method 600, or portions thereof, is performed by a mobile computing device with a memory card slot, and in other embodiments, method 600, or portions thereof, is performed by software. The various actions in method 600 may be performed in the order presented, in a different order, or simultaneously. Further, in some embodiments, some actions listed in FIG. 6 are omitted from method 600.


Method 600 begins at 610 in which a data pattern and an address value are received from an RFID card in a memory card slot. The data pattern corresponds to the hidden command data value, and the address value corresponds to the hidden command address value. In some embodiments, the mobile device may receive the data value and in other embodiments, the mobile device may receive the address value. In some embodiments, the actions of 610 may occur once when the RFID card is first inserted in the memory card slot. The mobile computing device may then use the address and data values each time it creates a hidden command. In other embodiments, the actions of 610 may occur each time the RFID card is inserted in the memory slot. In still further embodiments, the actions of 610 may occur periodically. Each time the actions 610 occur, the data pattern may be the same or different, and the address value may be the same or different.


At 620, a data field of a memory card access command is populated with the data pattern to cause the command to be diverted to a smartcard controller on the RFID card. For example, the data pattern may be written to the data field as the hidden command data value 510 (FIG. 5).


At 630, an address field of the memory card access command is populated with the address value to further cause the command to be diverted to the smartcard controller. In some embodiments, only one of 620 or 630 is utilized. In these embodiments, the presence of a hidden command is signified by the data pattern alone, or the address value alone.


At 640, the data field of the memory card access command is populated with a command string to specify a purpose other than a memory card access. For example, the command string may be written to the data field as the command index 540 for the smart card controller. This command may be used for any purpose. For example, one or more hidden commands may have as a sole purpose keeping power provided to the memory card slot so that the RFID card continues to receive power.


At 650, the data field of a memory card access command is populated with a password to authenticate access to the RFID card coupled to the memory card slot. In some embodiments, a password is included in the data field for every hidden command. In other embodiments, a password is only included at the beginning of an exchange.


At 660, the memory card access command is sent to the RFID card coupled to the memory card slot. For example, a mobile computing device (110, FIGS. 1, 2) may send the memory card access command to an RFID card (120, FIGS. 1, 3, 4) in a memory card slot (112, FIGS. 1, 2). The RFID card includes a memory card controller (340, FIG. 3) to divert the command (or take some other action) based on the data fields populated in method 600.



FIG. 7 shows a flowchart in accordance with various embodiments of the present invention. In some embodiments, method 700 may be used by an RFID card in a memory card slot. In some embodiments, method 700, or portions thereof, may be performed by a memory card controller within a memory card compatible RFID card, and in other embodiments, method 700, or portions thereof, is performed by software. The various actions in method 700 may be performed in the order presented, in a different order, or simultaneously. Further, in some embodiments, some actions listed in FIG. 7 are omitted from method 700.


Method 700 begins at 710 in which a memory card access command is received from a mobile computing device via a host interface. The actions of 710 correspond to an RFID card in a memory card slot of a mobile computing device receiving a memory card access command.


At 720, the memory card controller checks criteria in the memory card access command to determine if the memory card access command should be diverted to a smartcard controller resident on the RFID card. The criteria may be one or both of a hidden command data value, a hidden command address value, or both. If there is a criteria match at 730, then a hidden command is present, and at least a portion of the memory card access command is diverted at 740. If there is not a criteria match, then no hidden command is present, and a memory access is performed at 750.



FIG. 8 shows a flowchart in accordance with various embodiments of the present invention. In some embodiments, method 800 may be used by an RFID card in a memory card slot. In some embodiments, method 800, or portions thereof, is performed by a memory card controller within an RFID card, and in other embodiments, method 800, or portions thereof, is performed by software. The various actions in method 800 may be performed in the order presented, in a different order, or simultaneously. Further, in some embodiments, some actions listed in FIG. 8 are omitted from method 800.


Method 800 begins at 810 in which a memory card write command is received from a mobile computing device via a host interface. If the memory card write command is determined to be a hidden command, processing continues with 840; otherwise, a memory write is performed at 830.


At 840, the hidden command is diverted to a smartcard controller. In some embodiments, this corresponds to sending command index 540 and hidden command related data 550 (FIG. 5) to the smartcard controller. If the hidden command is determined to be a “read” at 850, processing continues at 860; otherwise, the hidden command processing is done. At 860, the memory card controller retrieves non-memory data from the smartcard controller, and at 870, a memory card read command is received from the mobile computing device. At 880, the non-memory data is returned to the mobile computing device.


Method 800 demonstrates how a mobile computing device can perform a read from a smartcard controller in a memory card compatible RFID card. The mobile computing device issues a memory card write command with a hidden command having a status field designating a read, and then the mobile computing device issues a memory card read command. The processing in the card receives the hidden command, identifies it as a read, and then returns data to the mobile computing device in response to a subsequent memory card read command.



FIG. 9 shows a flowchart in accordance with various embodiments of the present invention. In some embodiments, method 900 may be used by an RFID card in a memory card slot. In some embodiments, method 900, or portions thereof, is performed by a smartcard controller within an RFID card, and in other embodiments, method 900, or portions thereof, is performed by software. The various actions in method 900 may be performed in the order presented, in a different order, or simultaneously. Further, in some embodiments, some actions listed in FIG. 9 are omitted from method 900.


Method 900 begins at 910 in which a smartcard controller receives a command from the memory card controller. This command corresponds to a hidden command received by the memory card controller. At 950, the smartcard controller determines whether the command is a “dummy” command used solely for the purpose of maintaining power to the memory card slot. If no, then the smartcard function specified in the command is performed at 930. If yes, then the command is disregarded at 960.


Method 900 allows a memory card compatible RFID card in a memory card slot to remain powered during periods when the memory card slot in the host device would otherwise remove power to save energy. This is a coordinated effort between software building hidden commands in a memory card access command, the memory card controller diverting the hidden command to the smartcard controller, and the smartcard controller disregarding the command. According to embodiments represented by FIG. 3A, providing power to the RFID card also provides power the smartcard controller, thereby allowing the use of a small inductive device such as those shown in FIGS. 3 and 4.



FIG. 10 shows a flowchart in accordance with various embodiments of the present invention. In some embodiments, method 1000 may be used by an RFID card in a memory card slot. In some embodiments, method 1000, or portions thereof, is performed by a memory card controller within an RFID card, and in other embodiments, method 1000, or portions thereof, is performed by software. The various actions in method 1000 may be performed in the order presented, in a different order, or simultaneously. Further, in some embodiments, some actions listed in FIG. 10 are omitted from method 1000.


Method 1000 begins at 1010 in which a memory card controller receives a hidden command from a mobile computing device. If at 1020, the memory card controller determines that the hidden command is to be diverted to the smartcard controller, then the command is diverted at 1030. In some embodiments, this corresponds to sending command index 540 and hidden command related data 550 (FIG. 5) to the smartcard controller. If the command is not to be diverted, then the memory card controller does not divert the command; however, the memory card controller may take other actions at 1040 based on the hidden command. For example, the memory card controller may modify a clock signal provided to the smartcard controller. Also for example, the memory card controller may assert a reset signal to the smartcard controller. Still for example, the memory card controller may cycle power to the smartcard controller. The memory card controller is able to cycle power to the smartcard controller in embodiments represented by FIG. 3B.


Cycling power to the smartcard controller may be a coordinated effort between the hosting computing device and the memory card controller in the RFID card. For example, power to the memory card slot may be maintained by supplying dummy hidden commands to the RFID card as described above with reference to FIG. 9. While power is maintained to the memory card slot, hidden commands may be used to cause the memory card controller to cycle power to the smartcard controller.



FIG. 11 shows a method authenticating a mobile computing device to one or more functions in a memory card compatible RFID card. Method 1100 begins at block 1110 in which an activation code is received at an RFID card from a mobile computing device. At 1120, the received activation code is compared to a code stored in the RFID card. If the activation code matches, the RFID card receives a password from the mobile computing device at 1140, and stores the password in the RFID card for later use at 1150. If the activation code does not match, the RFID card determines whether a number of allowable tries has been exceeded at 1160. If the number of allowable tries has been exceeded, the RFID card issuer is contacted at 1170, and if the number of allowable tries has not been exceeded, the method repeats until either the activation code matches or the number of allowable tries has been exceeded.


Method 1100 may be performed when an RFID card is issued to a user. For example, the RFID card may be a mobile payment card issued by a financial institution. The user may be provided an activation code to “activate” the RFID card. When the user successfully enters the activation code, the user is prompted for a password, and that password is stored for use in future hidden commands.


In some embodiments, multiple non-memory functions in an RFID card are authenticated using method 1100. For example, each of multiple non-memory functions may have stored activation codes, and each is activated separately. Each of the separately activated functions may have a different password, or the multiple functions may share a password.


Embodiments described thus far include a power delivery mechanism from the host to the smartcard controller that allow the antenna or coil to be very small. The small antenna or coil allows for higher levels of integration, but may also reduce the maximum distance at which the RFID card may function. For example, referring to FIG. 14, the voltage produced by the antenna needs to overcome the diode drops of the bridge rectifier before data can be demodulated within the smartcard controller. As the antenna shrinks in size, the RFID card needs to be closer to the device producing the interrogating RF field in order to produce a large enough voltage to overcome the bridge rectifier diode drops, thereby reducing the maximum usable distance.



FIG. 15 shows a smartcard controller with performance enhancement circuits including a load modulation driver circuit and an antenna in accordance with various embodiments of the present invention. Antenna 1542 is a small inductive element as described above. Capacitor 1544 is in parallel with antenna 1542 and together they form tuned circuit 1540 that is tuned to be resonant at the frequency of operation (e.g., 13.56 MHz). The performance enhancement circuits include an amplifier 1510, outgoing data extraction circuit 1520, and load modulation driver circuit 1530. Amplifier 1510 amplifies the voltage received at antenna 1542, and the amplified voltage is provided to the smartcard controller. This increases the maximum distance at which the RFID card can operate while receiving data, but also creates a unidirectional data path where a bidirectional data path previously existed. In other words, amplifier 1510 forms a simplex communication path where a half duplex path previously existed.


In order to restore the outgoing data path and re-create a half duplex communications system, the RFID card includes outgoing data extraction circuit 1520 and load modulation driver circuits 1530. Outgoing data extraction circuit 1520 receives a signal that is formed by the interrogating RF field having been load modulated by the smartcard controller. For example, the impedance of the antenna port is modulated by load modulation driver circuit 1410 (FIG. 14), where the modulating signal is the data. Outgoing data extraction circuit 1520 recovers the data, and then load modulation driver circuit 1530 modulates the impedance of the tuned circuit 1540 to form the outgoing data path.


Outgoing data extraction circuit 1520 may include one or more filters to extract the data. For example, referring now to FIG. 16, the load modulation driver circuit within the smartcard controller creates frequency sidebands 1610 about the carrier frequency 1620 of the interrogating RF field. Outgoing data extraction circuit 1520 may include conventional filters to isolate one or more sidebands and extract the data. As shown in FIG. 16, in some 13.56 MHz embodiments, the bandwidth of the carrier frequency of the interrogating RF field may be on the order of 850 KHz and the bandwidth of the sidebands may be on the order of 100-200 KHz, although this is not a limitation of the present invention.


Load modulation driver circuit 1530 receives the extracted data from outgoing data extraction circuit 1520, and load modulates the tuned circuit 1540 in response thereto. Load modulation driver circuits are generally well known, and may be as simple as a switched transistor that adds and removes a reactive element from tuned circuit 1540. In some embodiments, load modulation driver circuit 1530 substantially duplicates the load modulation driver circuit 1410 within smartcard controller 330.


Amplifier 1510 is shown coupled to smartcard controller pad 1472, and data extraction circuit 1520 is shown coupled to smartcard controller pad 1474, but this is not a limitation of the present invention. For example, outgoing data extraction circuit 1520 may be coupled to smartcard controller pad 1472 while amplifier 1510 may be coupled to smartcard controller pad 1474. Also for example, both circuit 1520 and amplifier 1510 may be coupled to either pad 1472 or pad 1474 without departing from the scope of the present invention.



FIG. 17 shows a smartcard controller with performance enhancement circuits including a load modulation driver circuit and separate receive and transmit antennas in accordance with various embodiments of the present invention. FIG. 17 shows smartcard controller 330, amplifier 1510, outgoing data extraction circuit 1520, and load modulation driver circuit 1530, all of which are described above. FIG. 17 also shows tuned circuits 1740 and 1750. Tuned circuit 1740 includes receive antenna 1742 and capacitor 1744. Tuned circuit 1750 includes transmit antenna 1752 and capacitor 1754. In some embodiments, receive antenna 1742 and transmit antenna 1752 are small inductive elements as described above.


Separate transmit and receive antennas allow for different tuning, both in frequency and bandwidth, or “Q.” For example, tuned circuit 1740 may be tuned with relatively high Q for receive as shown at 1820 in FIG. 18, while tuned circuit 1750 may be tuned for a lower Q to envelope both sidebands for transmit as shown at 1830 in FIG. 18. The higher Q tuning for the receive antenna may further increase the maximum usable distance when the RFID card is receiving.



FIG. 19 shows a smartcard controller with performance enhancement circuits including a load modulation driver circuit and multiple transmit antennas in accordance with various embodiments of the present invention. FIG. 19 shows smartcard controller 330, amplifier 1510, outgoing data extraction circuit 1520, load modulation driver circuit 1530, and tuned receive circuit 1740, all of which are described above. FIG. 19 also shows two tuned transmit circuits 1950 and 1960. Tuned circuit 1950 includes antenna 1952 and capacitor 1954, and tuned circuit 1960 includes antenna 1962 and capacitor 1964. Antennas 1952 and 1962 may be small inductive elements as described above.


Separate transmit antennas allow separate tuning for the two sidebands. For example, tuned circuit 1950 may be tuned for the lower sideband tuned circuit 1960 may be tuned for the upper sideband as shown in FIG. 20. Higher Q tuning of the transmit antennas for the separate sidebands may further increase the maximum usable distance when the RFID card is transmitting.



FIG. 21 shows a smartcard controller with performance enhancement circuits including an active transmit driver circuit and an antenna in accordance with various embodiments of the present invention. The circuits shown in FIG. 21 are similar to FIG. 15 except the load modulation driver is replaced with an active transmit driver circuit 2130. Active transmit driver circuit 2130 may include circuits to actively transmit a signal rather than simply load modulate tuned circuit 1540. For example, active transmit driver circuit 2130 may include one or more amplifiers, filters, oscillators, modulators, etc., to form a signal that mimics the sidebands 1610 (FIG. 16) as if the interrogating RF field experienced load modulation. Active transmission can make use of power available on the RFID card and can further increase the usable distance when smartcard controller 330 is transmitting.



FIG. 22 shows a smartcard controller with performance enhancement circuits including an active transmit driver circuit and separate receive and transmit antennas in accordance with various embodiments of the present invention. The circuits shown in FIG. 22 are similar to FIG. 17 except the load modulation driver is replaced with an active transmit driver circuit 2130. Active transmit driver circuit 2130 is described above with reference to FIG. 21.



FIG. 23 shows a smartcard controller with performance enhancement circuits including an active transmit driver circuit and multiple transmit antennas in accordance with various embodiments of the present invention. The circuits shown in FIG. 23 are similar to FIG. 19 except the load modulation driver is replaced with an active transmit driver circuit 2130. Active transmit driver circuit 2130 is described above with reference to FIG. 21.



FIG. 24 shows a smartcard controller with a pad to provide a digital data output. Smartcard controller 2430 includes the antenna pads 1472 and 1474 as described above. Smartcard controller 2430 also includes pad 2410 which provides the digital data output directly. By providing the digital data output directly, smartcard controller 2430 enables various embodiments of the invention to eliminate the outgoing data extraction circuit.



FIG. 25 shows a smartcard controller with digital data output and performance enhancement circuits including a load modulation driver circuit and an antenna in accordance with various embodiments of the present invention. FIG. 25 shows smartcard controller 2430, amplifier 1510, load modulation driver circuits 1530, and tuned circuit 1540, all of which are described above. Note that because smartcard controller 2430 provides digital data directly, the outgoing data extraction circuit 1520 (FIG. 15) can be omitted, thereby reducing parts count and cost.



FIG. 26 shows a smartcard controller with digital data output and performance enhancement circuits including a load modulation driver circuit and separate receive and transmit antennas in accordance with various embodiments of the present invention. FIG. 26 shows circuits similar to those shown in FIG. 25, except that separate transmit and receive antennas are provided. Separate transmit and receive antennas (and associated tuned circuits) allow for a higher Q tuning of the receive antenna, thereby increasing the maximum usable distance when RFID card is receiving. See FIG. 18.



FIG. 27 shows a smartcard controller with digital data output and performance enhancement circuits including a load modulation driver circuit and multiple transmit antennas in accordance with various embodiments of the present invention. FIG. 27 shows circuits similar to those shown in FIG. 26, except that multiple transmit antennas are provided. Multiple separate transmit antennas (and associated tuned circuits) allow for a higher Q tuning of each transmit antenna, thereby increasing the maximum usable distance when RFID card is transmitting. See FIG. 20.



FIG. 28 shows a smartcard controller with digital data output and performance enhancement circuits including an active transmit driver circuit and a single antenna in accordance with various embodiments of the present invention. The circuits shown in FIG. 28 are similar to FIG. 25 except the load modulation driver is replaced with an active transmit driver circuit 2130. Active transmit driver circuit 2130 is described above with reference to FIG. 21. In general, the term “driver” as used herein refers to an active transmit driver or a load modulation driver or any other method of driving the transmit output data.



FIG. 29 shows a smartcard controller with digital data output and performance enhancement circuits including an active transmit driver circuit and separate receive and transmit antennas in accordance with various embodiments of the present invention. The circuits shown in FIG. 29 are similar to FIG. 26 except the load modulation driver is replaced with an active transmit driver circuit 2130. Active transmit driver circuit 2130 is described above with reference to FIG. 21.



FIG. 30 shows a smartcard controller with digital data output and performance enhancement circuits including an active transmit driver circuit and multiple transmit antennas in accordance with various embodiments of the present invention. The circuits shown in FIG. 30 are similar to FIG. 27 except the load modulation driver is replaced with an active transmit driver circuit 2130. Active transmit driver circuit 2130 is described above with reference to FIG. 21.



FIGS. 31-34 show performance enhancing application specific integrated circuits (ASICs) coupled to various smartcard controllers in accordance with various embodiments of the present invention. FIGS. 31 and 32 show ASICs coupled to smartcard controller 330. Both ASICs include amplifier 1510 and outgoing data extraction circuits 1520. The ASIC of FIG. 31 includes load modulation driver circuits 1530 and the ASIC of FIG. 32 includes active transmit driver circuit 2130. FIGS. 33 and 34 show ASICs coupled to receive direct digital data from smartcard controller 2430. Accordingly, the outgoing data extraction circuits are omitted. The ASIC of FIG. 33 includes amplifier 1510 and load modulation driver circuits 1530, and the ASIC of FIG. 34 includes amplifier 1510 and active transmit driver circuit 2130.


By combining a smartcard controller and an ASIC as described herein, the performance of an RFID card may be enhanced with a reduced parts count. Further, any of ASICs shown may be used with separate receive and transmit antennas, multiple transmit antennas, or any combination. Further, one ASIC may be provided with all of the functionality shown in FIGS. 31-34 and the manner in which it is connected to a smartcard controller may dictate which functional blocks (e.g., data extraction, load modulation, active transmit) are utilized.



FIG. 35 shows a memory card with integrated smartcard controller, performance enhancement circuits, and antennas in accordance with various embodiments of the present invention. Host interface 310, memory card controller 340, and memory 360 are described above. Smartcard controller 3520 may be any smartcard controller described herein, including smartcard controller 330 or smartcard controller 2430. Enhancement circuits 3550 may include any of the enhancement circuits described herein including any combination of amplifier 1510, outgoing data extraction circuits 1520, load modulation driver circuits 1530, and active transmit driver circuit 2130. Antenna(s) 3560 may include any number or type of antennas. For example, antenna(s) 3560 may include one antenna, separate transmit and receive antennas, or a receive antenna and multiple transmit antennas.



FIG. 36 shows a memory card with integrated smartcard controller and performance enhancement circuits in accordance with various embodiments of the present invention. The memory card of FIG. 36 shows circuits similar to FIG. 35 with the exception of antenna(s) 3560. Instead, the memory card of FIG. 36 is intended for use with a host device that includes antenna(s). In some embodiments, antenna(s) 3560 are included in the memory card of FIG. 36, thereby allowing the host device to decide whether to use the antennas on the memory card, or the antennas on the host device. The form factor of the memory card in FIGS. 35 and 36 is shown as a microSD card, but this is not a limitation of the present invention. Any form factor may be employed.



FIG. 37 shows a subscriber identity module (SIM) card with integrated smartcard controller, performance enhancement circuits and antennas in accordance with various embodiments of the present invention. Smartcard controller 3520, enhancement circuits 3550, and antenna(s) 3560 are described above with reference to FIG. 35.



FIG. 38 shows a subscriber identity module (SIM) card with integrated smartcard controller and performance enhancement circuits in accordance with various embodiments of the present invention. The SIM card of FIG. 38 shows circuits similar to FIG. 37 with the exception of antenna(s) 3560. Instead, the SIM card of FIG. 38 is intended for use with a host device that includes antenna(s). In some embodiments, antenna(s) 3560 are included in the SIM card of FIG. 38, thereby allowing the host device to decide whether to use the antennas on the SIM card, or the antennas on the host device.



FIG. 39 shows a mobile device with a smartcard controller, enhancement circuits, and antenna(s). The mobile device of FIG. 39 includes a built-in smartcard controller for RFID functionality as opposed to accepting a separate RFID card as described above. The mobile device may be any electronic device including a mobile phone, a tablet computer, or the like.


Although the present invention has been described in conjunction with certain embodiments, it is to be understood that modifications and variations may be resorted to without departing from the spirit and scope of the invention as those skilled in the art readily understand. Such modifications and variations are considered to be within the scope of the invention and the appended claims.

Claims
  • 1. A mobile device comprising: a power source;a smartcard controller coupled to the power source to receive power;an antenna tuned to operate at substantially 13.56 MHz, wherein the antenna interacts with a Near Field Communication (NFC) reader external to the mobile device; andan active transmit driver circuit coupled to the power source to receive the power, wherein the active transmit driver circuit affects transmission of data between the antenna and the NFC reader.
  • 2. The mobile device of claim 1, wherein the transmitted data includes ticketing information for a mass transit system.
  • 3. The mobile device of claim 1, wherein the transmitted data includes transaction information for a mobile payment.
  • 4. The mobile device of claim 1, wherein the NFC reader is a point-of-sale NFC reader.
  • 5. The mobile device of claim 1, wherein the antenna includes an inductive element.
  • 6. The mobile device of claim 1, wherein the active transmit driver circuit includes one or more of an amplifier filter, oscillator, and/or modulator.
  • 7. The mobile device of claim 1 comprising an amplifier coupled to the power source to receive the power, wherein the amplifier is further coupled to the antenna.
  • 8. The mobile device of claim 7, wherein the amplifier amplifies a signal received at the antenna and generates an amplified signal, and provides the amplified signal to the smartcard controller.
  • 9. The mobile device of claim 1, wherein the smartcard controller includes a bridge rectifier.
  • 10. A method of activation, the method comprising: receiving a first communication via a network including a request for activation; andsending a second communication to a mobile device via a network, wherein the second communication comprises an activation code provided in response to the request for activation, wherein verification of the activation code results in activation of a built-in RFID functionality in the mobile device, wherein the mobile device comprises: a smartcard controller to provide the built-in RFID functionality and coupled to receive power from the mobile device;an antenna tuned to operate at substantially 13.56 MHz; andan active transmit driver circuit coupled to receive power from the mobile device, and wherein the activated built-in RFID functionality comprises transmission of data between the antenna and an external RFID reader, the transmission effected by the active transmit driver circuit.
  • 11. The method of claim 10, wherein the RFID functionality is a Near Field Communication (NFC) functionality and the external RFID reader is an NFC reader.
  • 12. The method of claim 10, wherein the transmitted data includes ticketing information for a mass transit system.
  • 13. The method of claim 10, wherein the transmitted data includes transaction information for a mobile payment.
  • 14. The method of claim 10, wherein the antenna includes an inductive element.
  • 15. The method of claim 10, wherein the active transmit driver circuit includes one or more of an amplifier filter, oscillator, and/or modulator.
  • 16. The method of claim 10, wherein the mobile device further comprises an amplifier coupled to the antenna and further coupled to receive power from the mobile device, and wherein the amplifier operates to amplify a signal received by the antenna.
  • 17. A method of near field communication between a mobile device and an NFC reader, the method comprising: coupling a smartcard controller and an active transmit driver circuit to a power source of the mobile device;providing power to the smartcard controller and the active transmit driver circuit from the power source of the mobile device;coupling the active transmit driver circuit to an antenna of the mobile device, wherein the antenna is tuned to operate at substantially 13.56 MHz; anddriving transmission of data by the active transmit driver circuit from the antenna to the NFC reader.
  • 18. The method of claim 17 further comprising: amplifying a signal received from the antenna to generate an amplified signal; andproviding the amplified signal to the smartcard controller.
  • 19. The method of claim 10 or 17, wherein the transmitted data includes ticketing information for a mass transit system.
  • 20. The method of claim 10 or 17, wherein the transmitted data includes transaction information for a mobile payment.
CLAIM FOR PRIORITY

This application is a continuation of, and claims the benefit of priority to U.S. patent application Ser. No. 16/791,609, filed Feb. 14, 2020, and now issued as U.S. Pat. No. 10,949,726 on Mar. 16, 2021, which is a continuation of, and claims the benefit of priority to U.S. patent application Ser. No. 16/393,275, filed Apr. 24, 2019, now issued on Mar. 31, 2020 as U.S. Pat. No. 10,607,129, which is a continuation of, and claims the benefit of priority to U.S. patent application Ser. No. 15/904,328, filed on Feb. 24, 2018, now issued on Jun. 11, 2019 as U.S. Pat. No. 10,318,855, which is a continuation of, and claims the benefit of priority to U.S. patent application Ser. No. 15/338,436, filed Oct. 30, 2016, now issued on Feb. 27, 2019, as U.S. Pat. No. 9,904,887, which is a continuation of, and claims the benefit of priority to U.S. patent application Ser. No. 14/517,585, filed Oct. 17, 2014, now issued on Nov. 8, 2016, as U.S. Pat. No. 9,489,608, which is a continuation of, and claims priority to U.S. patent application Ser. No. 14/460,647, filed Aug. 15, 2014, now issued on Jan. 20, 2015, as U.S. Pat. No. 8,937,549, which is a continuation of, and claims the benefit of priority to U.S. patent application Ser. No. 13/871,849, on Apr. 26, 2013, now issued on Oct. 21, 2014, as U.S. Pat. No. 8,866,614, which is a continuation of, and claims the benefit of priority to, U.S. patent application Ser. No. 13/038,341, filed Mar. 1, 2011, now issued on May 28, 2013, as U.S. Pat. No. 8,451,122, which is a continuation-in-part of, and claims the benefit of priority to U.S. patent application Ser. No. 12/188,346, filed Aug. 8, 2008, now issued on Jun. 14, 2011, as U.S. Pat. No. 7,961,101 and which are incorporated by reference in their entirety.

US Referenced Citations (280)
Number Name Date Kind
1178450 LaChapelle Apr 1916 A
4701601 Francini et al. Oct 1987 A
4786791 Hodama Nov 1988 A
4791283 Burkhardt Dec 1988 A
4864109 Minematsu et al. Sep 1989 A
5212478 Moseley May 1993 A
5378887 Kobayashi Jan 1995 A
5386106 Kumar Jan 1995 A
5537584 Miyai et al. Jul 1996 A
5574273 Nakagawa et al. Nov 1996 A
5585787 Wallerstein Dec 1996 A
5629981 Nerlikar May 1997 A
5700037 Keller et al. Dec 1997 A
5710421 Kokubu et al. Jan 1998 A
5834756 Gutman et al. Nov 1998 A
5909491 Luo Jun 1999 A
5940510 Curry et al. Aug 1999 A
5949880 Curry et al. Sep 1999 A
5952641 Korshun Sep 1999 A
5955961 Wallerstein Sep 1999 A
6016476 Maes et al. Jan 2000 A
6021944 Arakaki Feb 2000 A
6039260 Eisele Mar 2000 A
6045043 Bashan et al. Apr 2000 A
6068184 Barnett May 2000 A
6105013 Curry et al. Aug 2000 A
6182891 Furuhashi et al. Feb 2001 B1
6189786 Itou et al. Feb 2001 B1
6206293 Gutman et al. Mar 2001 B1
6219439 Burger Apr 2001 B1
6223954 Carow May 2001 B1
6223984 Renner et al. May 2001 B1
6237095 Curry et al. May 2001 B1
6250557 Forslund et al. Jun 2001 B1
6315195 Ramachandran Nov 2001 B1
6402029 Gangi Jun 2002 B1
6450407 Freeman et al. Sep 2002 B1
6481623 Grant et al. Nov 2002 B1
6568600 Carpier et al. May 2003 B1
6588660 Buescher et al. Jul 2003 B1
6592044 Wong Jul 2003 B1
6594759 Wang Jul 2003 B1
6598031 Ice Jul 2003 B1
6607127 Wong Aug 2003 B2
6609654 Anderson et al. Aug 2003 B1
6631849 Blossom Oct 2003 B2
6636833 Flitcroft et al. Oct 2003 B1
6669487 Nishizawa Dec 2003 B1
6705520 Pitroda et al. Mar 2004 B1
6712277 Spencer Mar 2004 B2
6715679 Infosino Apr 2004 B1
6721196 Grassl Apr 2004 B1
6747547 Benson Jun 2004 B2
6764005 Cooper Jul 2004 B2
6769607 Pitroda et al. Aug 2004 B1
6805288 Routhenstein et al. Oct 2004 B2
6811082 Wong Nov 2004 B2
6836843 Seroussi et al. Dec 2004 B2
6857566 Wankmueller Feb 2005 B2
6882900 Terranova Apr 2005 B1
6883718 Le et al. Apr 2005 B1
6905072 Ramachandran Jun 2005 B2
6907123 Schier Jun 2005 B1
6908030 Rajasekaran et al. Jun 2005 B2
6925568 Heinonen Aug 2005 B1
6937526 Furukawa Aug 2005 B2
6952788 Rommelmann et al. Oct 2005 B2
6995651 Amtmann et al. Feb 2006 B2
7059520 Shtesl Jun 2006 B1
7088246 Fukuoka Aug 2006 B2
7185146 Masuyama et al. Feb 2007 B2
7213766 Ryan et al. May 2007 B2
7221473 Jeran et al. May 2007 B2
7281101 Mizushima et al. Oct 2007 B2
7295790 Morimoto et al. Nov 2007 B2
7333062 Leizerovich et al. Feb 2008 B2
7350717 Conner et al. Apr 2008 B2
7353993 Fujimoto Apr 2008 B2
7410102 Winkler Aug 2008 B2
7493484 Lee Feb 2009 B2
7558107 Sakurai et al. Jul 2009 B2
7558110 Mizushima et al. Jul 2009 B2
7559464 Routhenstein Jul 2009 B2
7581678 Narendra et al. Sep 2009 B2
7607580 Takita et al. Oct 2009 B2
7673080 Yu et al. Mar 2010 B1
RE41352 Wood, Jr. May 2010 E
7716082 Blalock May 2010 B1
RE41471 Wood, Jr. Aug 2010 E
7789303 Fukasawa Sep 2010 B2
7792516 Soderstrom Sep 2010 B2
7828214 Narendra et al. Nov 2010 B2
RE42254 Wood, Jr. Mar 2011 E
7898994 Zhao et al. Mar 2011 B2
7933571 Black et al. Apr 2011 B2
7941197 Jain et al. May 2011 B2
7948356 Kawamura et al. May 2011 B2
7954715 Narendra et al. Jun 2011 B2
7954716 Narendra et al. Jun 2011 B2
7954717 Narendra et al. Jun 2011 B2
7961101 Narendra et al. Jun 2011 B2
7991158 Narendra et al. Aug 2011 B2
8072331 Narendra et al. Dec 2011 B2
8082575 Doughty et al. Dec 2011 B2
8083145 Narendra et al. Dec 2011 B2
8091786 Narendra et al. Jan 2012 B2
8103881 Doughty et al. Jan 2012 B2
20010001035 Kayanakis May 2001 A1
20010002035 Kayanakis May 2001 A1
20010006902 Ito Jul 2001 A1
20010013551 Ramachandran Aug 2001 A1
20010034246 Hutchison, IV et al. Oct 2001 A1
20020007434 Campardo Jan 2002 A1
20020025796 Taylor et al. Feb 2002 A1
20020043566 Goodman et al. Apr 2002 A1
20020044043 Chaco et al. Apr 2002 A1
20020095588 Shigematsu et al. Jul 2002 A1
20020096570 Wong et al. Jul 2002 A1
20020099665 Burger et al. Jul 2002 A1
20020130187 Berg et al. Sep 2002 A1
20020138422 Natsuno Sep 2002 A1
20020138735 Felt et al. Sep 2002 A1
20020139849 Gangi Oct 2002 A1
20020148892 Bardwell Oct 2002 A1
20020153424 Li Oct 2002 A1
20020158747 McGregor et al. Oct 2002 A1
20020178124 Lewis Nov 2002 A1
20020180584 McGregor et al. Dec 2002 A1
20020186845 Dutta et al. Dec 2002 A1
20030080183 Rajasekaran et al. Jan 2003 A1
20030025939 Jeran et al. Feb 2003 A1
20030028481 Flitcroft et al. Feb 2003 A1
20030038177 Morrow Feb 2003 A1
20030052168 Wong Mar 2003 A1
20030057278 Wong Mar 2003 A1
20030061168 Routhenstein Mar 2003 A1
20030079096 Murakami Apr 2003 A1
20030084220 Jones et al. May 2003 A1
20030085288 Luu May 2003 A1
20030115126 Pitroda Jun 2003 A1
20030128124 Amtmann et al. Jul 2003 A1
20030159050 Gantman et al. Aug 2003 A1
20030200180 Phelan et al. Oct 2003 A1
20030209604 Harrison Nov 2003 A1
20030220876 Burger et al. Nov 2003 A1
20030231550 Macfarlane Dec 2003 A1
20040006654 Bando Jan 2004 A1
20040027881 Furukawa Feb 2004 A1
20040030660 Shatford Feb 2004 A1
20040035942 Silverman Feb 2004 A1
20040050930 Rowe Mar 2004 A1
20040058705 Morgan et al. Mar 2004 A1
20040064612 Pinto et al. Apr 2004 A1
20040065733 Fukuoka Apr 2004 A1
20040077372 Halpern Apr 2004 A1
20040087339 Goldthwaite et al. May 2004 A1
20040094624 Fernandes et al. May 2004 A1
20040122685 Bunce Jun 2004 A1
20040133787 Doughty et al. Jul 2004 A1
20040162932 Mizushima et al. Aug 2004 A1
20040177045 Brown Sep 2004 A1
20040188519 Cassone Sep 2004 A1
20040199469 Barillova et al. Oct 2004 A1
20040227859 Liang Nov 2004 A1
20040243785 Shanmugasundaram et al. Dec 2004 A1
20040243806 McKinley et al. Dec 2004 A1
20040251303 Cooper Dec 2004 A1
20040255145 Chow Dec 2004 A1
20050006462 Rouille et al. Jan 2005 A1
20050017068 Zalewski et al. Jan 2005 A1
20050022002 Poisner Jan 2005 A1
20050029349 McGregor et al. Feb 2005 A1
20050038736 Saunders Feb 2005 A1
20050039027 Shapiro Feb 2005 A1
20050050367 Burger et al. Mar 2005 A1
20050052924 Nishizawa et al. Mar 2005 A1
20050060586 Burger et al. Mar 2005 A1
20050071282 Lu et al. Mar 2005 A1
20050077349 Bonalle et al. Apr 2005 A1
20050044044 Burger et al. May 2005 A1
20050092830 Blossom May 2005 A1
20050108096 Burger et al. May 2005 A1
20050109838 Linlor May 2005 A1
20050116026 Burger et al. Jun 2005 A1
20050121512 Wankmueller Jun 2005 A1
20050122209 Black Jun 2005 A1
20050127164 Wankmueller Jun 2005 A1
20050127166 Minemura Jun 2005 A1
20050133606 Brown Jun 2005 A1
20050136964 Saint et al. Jun 2005 A1
20050168339 Arai et al. Aug 2005 A1
20050177724 Ali et al. Aug 2005 A1
20050197859 Wilson et al. Sep 2005 A1
20050204077 Kou Sep 2005 A1
20050204092 Masuyama et al. Sep 2005 A1
20050212657 Simon Sep 2005 A1
20050223143 Kang et al. Oct 2005 A1
20050224589 Park et al. Oct 2005 A1
20050240778 Saito et al. Oct 2005 A1
20050246546 Takagi et al. Nov 2005 A1
20050253687 Martinez et al. Nov 2005 A1
20050258245 Bates et al. Nov 2005 A1
20050268058 Drasnin et al. Dec 2005 A1
20050268330 Di Rienzo Dec 2005 A1
20060011731 Anders et al. Jan 2006 A1
20060027655 Smets et al. Feb 2006 A1
20060045555 Morimoto et al. Mar 2006 A1
20060077039 Ibi et al. Apr 2006 A1
20060097851 Amtmann et al. May 2006 A1
20060124755 Ito Jun 2006 A1
20060169778 Chung Aug 2006 A1
20060172606 Irisawa Aug 2006 A1
20060186209 Narendra et al. Aug 2006 A1
20060219776 Finn Oct 2006 A1
20060226217 Narendra et al. Oct 2006 A1
20060268764 Harris Nov 2006 A1
20060279413 Yeager Dec 2006 A1
20070033334 Katayama et al. Feb 2007 A1
20070076877 Camp et al. Apr 2007 A1
20070108280 Li et al. May 2007 A1
20070145135 Jogand-Coulomb et al. Jun 2007 A1
20070145152 Jogand-Coulomb et al. Jun 2007 A1
20070110404 Sawai et al. Aug 2007 A1
20070195458 Sawai et al. Aug 2007 A1
20070205864 Mutti et al. Sep 2007 A1
20070257797 Rancien et al. Nov 2007 A1
20070293202 Moshir et al. Dec 2007 A1
20080046649 Ito Feb 2008 A1
20080065830 Aoki et al. Mar 2008 A1
20080068173 Alexis et al. Mar 2008 A1
20080073436 Nishizawa et al. Mar 2008 A1
20080136619 Moran Jun 2008 A1
20080147950 Chen Jun 2008 A1
20080148077 Lee et al. Jun 2008 A1
20080153416 Washiro Jun 2008 A1
20080186174 Alexis et al. Aug 2008 A1
20080214111 Moshir et al. Sep 2008 A1
20080244208 Narendra et al. Oct 2008 A1
20080279381 Narendra et al. Nov 2008 A1
20080311849 Washiro Dec 2008 A1
20080318535 Black et al. Dec 2008 A1
20090065571 Jain Mar 2009 A1
20090065572 Jain Mar 2009 A1
20090069049 Jain Mar 2009 A1
20090069050 Jain et al. Mar 2009 A1
20090069051 Jain et al. Mar 2009 A1
20090069052 Jain et al. Mar 2009 A1
20090070272 Jain Mar 2009 A1
20090070691 Jain Mar 2009 A1
20090070861 Jain Mar 2009 A1
20090108063 Jain et al. Apr 2009 A1
20090150610 Hsu et al. Jun 2009 A1
20090152361 Narendra et al. Jun 2009 A1
20090166421 Finn Jul 2009 A1
20090199283 Jain Aug 2009 A1
20090250521 Fujita et al. Oct 2009 A1
20090265552 Moshir et al. Oct 2009 A1
20090270127 Kakimoto Oct 2009 A1
20090290582 Suenaga et al. Nov 2009 A1
20090298540 Narendra et al. Dec 2009 A1
20090315667 Kawamura et al. Dec 2009 A1
20100033307 Narendra et al. Feb 2010 A1
20100033310 Narendra et al. Feb 2010 A1
20100049878 Yu et al. Feb 2010 A1
20100213265 Narendra et al. Aug 2010 A1
20110000960 Harris Jan 2011 A1
20110053644 Narendra et al. Mar 2011 A1
20110073663 Narendra et al. Mar 2011 A1
20110073665 Narendra et al. Mar 2011 A1
20110077052 Narendra et al. Mar 2011 A1
20110110404 Washiro May 2011 A1
20110171996 Narendra et al. Jul 2011 A1
20110180610 Narendra et al. Jul 2011 A1
20110220726 Narendra et al. Sep 2011 A1
20110223972 Narendra et al. Sep 2011 A1
20110269438 Narendra et al. Nov 2011 A1
20110271044 Narendra et al. Nov 2011 A1
20110272468 Narendra et al. Nov 2011 A1
20110272469 Narendra et al. Nov 2011 A1
20160234359 Itay Aug 2016 A1
Foreign Referenced Citations (61)
Number Date Country
3632294 Apr 1988 DE
10028813 Dec 2001 DE
10054890 Apr 2002 DE
0161060 Nov 1985 EP
161060 Nov 1985 EP
0818757 Jan 1998 EP
1014290 Jun 2000 EP
1117068 Jul 2001 EP
1178450 Feb 2002 EP
1189465 Mar 2002 EP
1291748 Mar 2003 EP
1308874 May 2003 EP
1801741 Jul 2008 EP
2965082 Mar 2012 FR
2316908 Mar 1998 GB
4102112 Apr 1992 JP
04102112 Apr 1992 JP
2000010668 Jan 2000 JP
2000010668 Jan 2000 JP
2005018671 Jan 2005 JP
2005018671 Jan 2005 JP
2007199847 Aug 2007 JP
2007199847 Aug 2007 JP
2007328689 Dec 2007 JP
2007328689 Dec 2007 JP
200905471 Feb 2009 TW
201020934 Jun 2010 TW
201023662 Jun 2010 TW
1336449 Jan 2011 TW
201126422 Aug 2011 TW
9626500 Aug 1996 WO
9626500 Aug 1996 WO
1996026500 Aug 1996 WO
9812674 Mar 1998 WO
199812674 Mar 1998 WO
1998012674 Mar 1998 WO
1998012674 Jul 1998 WO
200014678 Mar 2000 WO
2000014678 Mar 2000 WO
01088659 Nov 2001 WO
2001088659 Jan 2003 WO
2001088659 Jan 2003 WO
03029942 Apr 2003 WO
2003029942 Apr 2003 WO
2003077473 Sep 2003 WO
03081519 Oct 2003 WO
2003081519 Oct 2003 WO
2003081519 Jan 2004 WO
2003029942 Feb 2004 WO
2004012352 Feb 2004 WO
2004095169 Nov 2004 WO
2005027030 Mar 2005 WO
2005119607 Dec 2005 WO
2005119608 Dec 2005 WO
2006091709 Aug 2006 WO
2006091709 Aug 2006 WO
2006108184 Dec 2006 WO
2007011937 Jan 2007 WO
2008121566 Oct 2008 WO
2009147548 Dec 2009 WO
2010099093 Sep 2010 WO
Non-Patent Literature Citations (89)
Entry
2nd Notice of Allowance notified Aug. 15, 2011 for U.S. Appl. No. 13/081,775.
Final Office Action notified Dec. 12, 2012 for U.S. Appl. No. 13/184,204.
Final Office Action notified Feb. 4, 2013 for U.S. Appl. No. 13/552,633.
Final Office Action notified Sep. 30, 2014 for U.S. Appl. No. 13/592,323.
International Preliminary Report & Written Opinion notified Dec. 4, 2006 for PCT Patent Application No. PCT/US2005/019988.
International Preliminary Report & Written Opinion notified Dec. 4, 2006 for PCT Patent Application No. PCT/US2005/022993.
International Preliminary Report & Written Opinion notified Jan. 22, 2008 for UPCT Patent Application No. PCT/US2006/027847, 10 pages.
International Preliminary Report & Written Opinion notified Sep. 9, 2011 for PCT Patent Application No. PCT/US2010/025014, 6 pages.
International Preliminary Report on Patentability & Written Opinion notified Aug. 28, 2007 for UPCT Patent Application No. PCT/US2006/006361, 8 pages.
International Search Report & Written Opinion notified Sep. 22, 2006 for UPCT Patent Application No. PCT/US2006/006361, 13 pages.
International Search Report notified Jan. 9, 2006 for PCT Patent Application No. PCT/US2006/013603, 3 pages.
International Search Report notified Oct. 21, 2005 PCT Patent Application No. PCT/US2005/022993.
International Written Opinion notified Aug. 7, 2008 for PCT Patent Application No. PCT/US2008/057588, 5 pages.
International Written Opinion notified Oct. 9, 2007 for PCT Patent Application No. PCT/US2006/013603, 7 pages.
Non-Final Office Action notified Apr. 19, 2018 for U.S. Appl. No. 15/658,208.
Non-Final Office Action notified Jul. 5, 2013 for U.S. Appl. No. 13/592,323.
Non-Final Office Action notified May 22, 2015 for U.S. Appl. No. 14/680,684.
Non-Final Office Action notified Sep. 16, 2016 for U.S. Appl. No. 14/929,297.
Non-Final Office Action notified Sep. 25, 2015 for U.S. Appl. No. 14/747,770.
Notice of Allowance notified Feb. 18, 2015 for U.S. Appl. No. 13/592,323.
Notice of Allowance notified Jun. 19, 2015 for U.S. Appl. No. 14/680,684.
Notice of Allowance notified Mar. 24, 2017 for U.S. Appl. No. 14/948,325.
Notice of Allowance notified Oct. 26, 2015 for U.S. Appl. No. 14/747,770.
Notice of Allowance notified Oct. 28, 2015 for U.S. Appl. No. 14/833,113.
Official Letter from Taiwan Patent Office notified Jan. 26, 2010 for U.S. Appl. No. 95/105,997.
International Search Report & Written Opinion notified Jan. 11, 2006 for PCT Patent Application No. PCT/US2005/019988, 8 pages.
Lee, Y., “Anntenna Circuit Design for RFID Applications”, Microchip, AN710, 2003, Microchip Technology Inc., 50 pages.
Lee, Y., “Antenna Circuit Design for RFID Applications”, Microchip, AN710, 2003 Microchip Technology, Inc., 50 pages (2003).
Advisory Action notified Feb. 7, 2013 for U.S. Appl. No. 12/960,070.
Final Office Action notified Dec. 11, 2012 for U.S. Appl. No. 12/960,070.
Final Office Action notified Oct. 25, 2014 for U.S. Appl. No. 12/960,070.
International Preliminary Report & Written Opinion notified Sep. 9, 2011 for PCT Patent Application No. PCT/US2010/025014.
International Preliminary Report on Patentability & Written Opinion notified Aug. 28, 2007 for PCT Patent Application No. PCT/US2006/006361.
International Preliminary Report on Patentability and Written Opinion notified Aug. 2, 2007 for PCT Patent Application No. PCT/US2006/006361.
International Preliminary Report on Patentability and Written Opinion notified Aug. 2, 2007 for PCT Patent Application No. PCT/US2006/013603.
International Preliminary Report on Patentability and Written Opinion notified Aug. 2, 2007 for PCT Patent Application No. PCT/US2006/027847.
International Preliminary Report on Patentability and Written Opinion notified Oct. 6, 2009 for PCT Patent Application No. PCT/US2008/057588.
International Search Report & Written Opinion notified Jan. 11, 2006 for PCT Patent Application No. PCT/US2005/019988.
International Search Report & Written Opinion notified Sep. 22, 2006 for PCT Patent Application No. PCT/US2006/006361.
International Search Report and Written Opinion notified Apr. 15, 2010 for PCT Patent Application No. PCT/US2010/025014.
International Search Report notified Aug. 7, 2008 for PCT Patent Application No. PCT/US2008/057588.
International Search Report notified Dec. 16, 2005 for PCT Patent Application No. PCT/US2005/019988.
International Search Report notified Jan. 9, 2006 for PCT Patent Application No. PCT/US2006/013603.
International Search Report notified Mar. 29, 2007 for PCT Patent Application No. PCT/US2006/027847.
International Search Report notified Oct. 9, 2007 for PCT Patent Application No. PCT/US2006/013603.
International Search Report notified Oct. 21, 2005 PCT for PCT Patent Application No. PCT/US2005/022993.
International Search Report notified Sep. 22, 2006 for PCT Patent Application No. PCT/US2006/006361.
International Written Opinion notified Aug. 7, 2008 for PCT Patent Application No. PCT/US2008/057588.
International Written Opinion notified Oct. 9, 2007 for PCT Patent Application No. PCT/US2006/013603.
Lee, Y., “Antenna Circuit Design for RFID Applications”, Microchip, AN710, 2003, Microchip Technology Inc., 50 pages.
Non-Final Office Action notified Apr. 3, 2013 for U.S. Appl. No. 13/426,500.
Non-Final Office Action notified Aug. 3, 2011 for U.S. Appl. No. 13/114,473.
Non-Final Office Action notified Dec. 20, 2012 for U.S. Appl. No. 13/593,492.
Non-Final Office Action notified Feb. 1, 2013 for U.S. Appl. No. 13/184,227.
Non-Final Office Action notified Feb. 3, 2011 for U.S. Appl. No. 12/962,953.
Non-Final Office Action notified Jan. 18, 2013 for U.S. Appl. No. 13/651,365.
Non-Final Office Action notified Jul. 3, 2012 for U.S. Appl. No. 13/184,227.
Non-Final Office Action notified Jun. 22, 2012 for U.S. Appl. No. 13/184,204.
Non-Final Office Action notified Jun. 27, 2012 for U.S. Appl. No. 12/960,070.
Non-Final Office Action notified Mar. 15, 2013 for U.S. Appl. No. 13/304,662.
Non-Final Office Action notified Mar. 18, 2011 for U.S. Appl. No. 12/941,410.
Non-Final Office Action notified Mar. 30, 2011 for U.S. Appl. No. 12/960,070.
Non-Final Office Action notified Nov. 5, 2015 for U.S. Appl. No. 14/866,998.
Non-Final Office Action notified Nov. 9, 2012 for U.S. Appl. No. 13/552,633.
Non-Final Office Action notified Nov. 25, 2011 forU.S. Appl. No. 13/184,240.
Non-Final Office Action notified Nov. 29, 2019 for U.S. Appl. No. 16/218,733.
Non-Final Office Action notified Sep. 20, 2016 for U.S. Appl. No. 14/948,325.
Non-Final Office Action notified Sep. 21, 2012 for U.S. Appl. No. 13/311,247.
Non-Final Office Action notified Sep. 24, 2015 for U.S. Appl. No. 14/833,113.
Non-Final Office Action notified Sep. 29, 2020 for U.S. Appl. No. 16/791,609.
Non-Final Office Action notified Sep. 30, 2010 for U.S. Appl. No. 12/188,346.
Notice of Allowance notified Apr. 14, 2011 forU.S. Appl. No. 12/941,410.
Notice of Allowance notified Apr. 18, 2011 for U.S. Appl. No. 12/962,953.
Notice of Allowance notified Apr. 25, 2011 for U.S. Appl. No. 12/188,346.
Notice of Allowance notified Aug. 15, 2011 for U.S. Appl. No. 13/081,775.
Notice of Allowance notified Dec. 21, 2015 for U.S. Appl. No. 14/866,998.
Notice of Allowance notified Feb. 14, 2013 for U.S. Appl. No. 13/311,247.
Notice of Allowance notified Feb. 21, 2013 for U.S. Appl. No. 13/651,365.
Notice of Allowance notified Jan. 10, 2012 for U.S. Appl. No. 13/184,240.
Notice of Allowance notified Jun. 18, 2020 for U.S. Appl. No. 16/218,733.
Notice of Allowance notified Mar. 3, 2017 for U.S. Appl. No. 14/929,297.
Notice of Allowance notified May 13, 2013 for U.S. Appl. No. 13/426,500.
Notice of Allowance notified Nov. 16, 2011 for U.S. Appl. No. 13/114,473.
Notice of Allowance notified Nov. 20, 2020 for U.S. Appl. No. 16/791,609.
Notice of Allowance notified Oct. 28, 2011 for U.S. Appl. No. 13/081,775.
Notice of Allowance notified Oct. 28, 2015 for U.S. Appl. No. 14/833,133.
Notice of Allowance notified Sep. 19, 2018 for U.S. Appl. No. 15/658,208.
Official Letter notified Jan. 26, 2010 for Taiwan Patent Application No. 95105997.
Restriction Requirement notified Aug. 16, 2010 for U.S. Appl. No. 12/188,346.
Related Publications (1)
Number Date Country
20210174158 A1 Jun 2021 US
Continuations (9)
Number Date Country
Parent 16791609 Feb 2020 US
Child 17179237 US
Parent 16393275 Apr 2019 US
Child 16791609 US
Parent 15904328 Feb 2018 US
Child 16393275 US
Parent 15338436 Oct 2016 US
Child 15904328 US
Parent 14517585 Oct 2014 US
Child 15338436 US
Parent 14460647 Aug 2014 US
Child 14517585 US
Parent 13871849 Apr 2013 US
Child 14460647 US
Parent 13038341 Mar 2011 US
Child 13871849 US
Parent 12188346 Aug 2008 US
Child 13038341 US