Emulated radio frequency identification

Information

  • Patent Grant
  • 9405947
  • Patent Number
    9,405,947
  • Date Filed
    Friday, January 25, 2013
    11 years ago
  • Date Issued
    Tuesday, August 2, 2016
    8 years ago
Abstract
A mobile communication device is equipped with hardware and/or software components to enable the device to output a data in a form of a radio frequency signal, emulating outputting of the data by either an active or a passive RFID transponder. The data may be a security key or an identifier. Emulation of an active RFID transponder includes facilitating selection of the data and instruction to output by a user. Emulation of a passive RFID transponder includes detecting for proximal presence of a RFID reader. Either case, provision of the data to the mobile communication device may include provision of associated signal attribute(s).
Description
FIELD OF THE INVENTION

The present invention relates to the fields of security, communication, and data processing. More specifically, the present invention is related to an emulated radio frequency data input method.


BACKGROUND OF THE INVENTION

It wasn't that long ago, even residents in medium size cities still feel secured enough to leave their homes unlocked and/or their garages open. In general, one can access one's place of employment, including parking facilities as well as one's office without identification or access keys.


In the world of commerce, things were also simpler. One typically may shop and consume goods and services, at relatively low prices, without having to be affiliated with any programs or entities.


However, the world has become a lot more complex in recent years. Virtually, all properties of any value, premises, including one's home, have to be secured, even for relatively small towns and cities. One can hardly shop and consume any goods and services, without having signed up with some promotional frequent “usage” programs or becoming affiliated with the commercial entities. The employment of affinity marketing has reached a point even neighboring grocery chains employ them, and not just airlines, hotels, or wholesale discount retailers.


As a result, it is not uncommon to find a person having to carry a number of physical keys and access/identification cards/tags to gain access to secured premises, such as one's home, office, parking garage, and so forth. Additionally, the person is likely to carry a number of remote security control devices, such as a key with remote control for gaining access to his/her vehicle, a garage door opener for gaining access to the person's garage at home, and so forth. The person is also likely to carry a number of affinity identification cards with member identifiers identifying the person as being affiliated with certain co-op or frequent patronage programs, such as wholesale discount retailers, airline or hotel frequent traveler program, and so forth, that entitle the person to certain benefits, such as discounts or rewards.





BRIEF DESCRIPTION OF THE DRAWINGS

The present invention will be described by way of exemplary embodiments, but not limitations, illustrated in the accompanying drawings in which like references denote similar elements, and in which:



FIG. 1 illustrates an overview of the present invention, in accordance with one embodiment;



FIG. 2 illustrates a method view of the present invention, in accordance with one embodiment;



FIG. 3 illustrates the relevant hardware elements of the device of FIG. 1 in further details, in accordance with one embodiment;



FIG. 4 illustrates the transceiver of FIG. 3 in further details, in accordance with another embodiment;



FIGS. 5a-5b illustrate the exploded views of two embodiments of the mobile communication device of FIG. 1;



FIGS. 5c-5d illustrate an exploded view of another embodiment of the mobile communication device of FIG. 1;



FIG. 6a-6h illustrate a number of example screens of an end user interface, suitable for use to practice the present invention, in accordance with one embodiment; and



FIG. 7 illustrates the operational flow of the relevant aspects of the software in support of the RFD feature of the present invention, in accordance with one embodiment.





DETAILED DESCRIPTION OF EMBODIMENTS OF THE INVENTION

Embodiments of the present invention includes an emulated RFID method, more specifically, an emulated RFID method, using a mobile communication device, including the device itself, and certain hardware and/or software embodied therein for the practice of the emulated RFID method.


In the following description, various aspects of the illustrative embodiments of the present invention will be described. However, alternate embodiments may be practiced with only some or all aspects of the illustrative embodiments of the present invention. For purposes of explanation, specific numbers, materials and configurations are set forth in order to provide a thorough understanding of the present invention. However, alternate embodiments may be practiced without the specific details. In other instances, well-known features are omitted or simplified in order not to obscure the essence of the illustrative embodiments of the present invention.


TERMINOLOGY

Parts of the description will be presented in data processing terms, such as data, selection, retrieval, generation, and so forth, consistent with the manner commonly employed by those skilled in the art to convey the substance of their work to others skilled in the art. As well understood by those skilled in the art, these quantities take the form of electrical, magnetic, or optical signals capable of being stored, transferred, combined, and otherwise manipulated through electrical and/or optical components of a processor and its subsystems.


Part of the descriptions will employ various abbreviations, including but are not limited to:


















CDROM
Compact Disc Read Only Memory



DDRAM
Dynamic Direct Random Access Memory



DVD
Digital Versatile Disc



EEPROM
Electrically Eraseable Programmable Read-Only-




Memory



HTTP
HyperText Transmission Protocol



SDRAM
Statis Direct Random Access Memory



SMS
Small Messaging Service










The term “number” as used In this application to describe a data, including both its usage in the specification and the claims, typically refers to numeric data, as the word “number” is conventionally used in mathematics. However, in certain contexts, the “number” may also include alphabet or special characters, as the term is conventionally understood by those skilled in the art in those contexts. For examples, a drivers license number, a passport number, an employee number, or a student ID number, as each of these terms is conventionally used, often includes one or more alphabets or special characters, even though they are referred to as “numbers”. The term accordingly is to be given the meaning that is consistent with the context under which the term is used.


Section Headings, Order of Descriptions and Embodiments

Section headings are merely employed to improve readability, and they are not to be construed to restrict or narrow the present invention.


Various operations will be described as multiple discrete steps in turn, in a manner that is most helpful in understanding the present invention, however, the order of description should not be construed as to imply that these operations are necessarily order dependent. In particular, these operations need not be performed in the order of presentation.


The phrase In one embodiment” is used repeatedly. The phrase generally does not refer to the same embodiment, however, it may, The terms “comprising”, “having” and Including” are synonymous, unless the context dictates otherwise.


Overview

Refer now to FIG. 1, wherein a block diagram illustrating an overview of the present invention 100, in accordance with one embodiment, is shown. As illustrated, for the embodiment, mobile communication device 102 is equipped with hardware and/or software elements 104 to perform its primary function, which is to facilitate a user of device 102 to engage in communication with another user of another communication device (not shown). In various embodiments, the communication may be audio (such as phone calls), textual (such as messaging) and/or visual (such as airtexting using light sources). Additionally, for the embodiment, mobile communication device 102 is equipped with hardware and/or software elements 106 to facilitate provision or transfer of a key/identifier in a form a radio frequency signal 110, which may be read e.g. by a radio frequency identifier (RFID) reader 120. In turn, the provision of RFID 110 may be responded to by a system (not shown) with which RFID reader 120 is a part or coupled to.


As depicted in FIG. 1, blocks 104 and 106 “Intersect” with one another. The “intersection” represents the fact that in preferred embodiments of the present invention, substantial portions of the hardware and/or software elements employed to provide a RFID, are the same elements employed to facilitate the primary function of device 102, i.e. to facilitate a user in communicating with another user of another communication device.


In other words, Illustrative embodiments of the present invention advantageously leverage on existing elements of mobile communication device 102, and supplement them, to enable mobile communication device 102 to be able to provide a RFID, emulating a RFID transponder, as well as facilitating user communication.


As will be described in more detail below, in preferred embodiments, mobile communication device 102 is equipped to provide RFID, emulating an active and/or a passive RFID transponder.


Further, RFID 110 may be any keys and/or identifiers, including but not limited to security keys, such as garage door “keys”, exterior or interior door keys, or identifiers, such as, employee numbers, driver's license numbers, social security numbers, credit card numbers (optionally, including expiration dates), affinity program member identifiers, and so forth.


Continue to refer to FIG. 1, except for the present invention incorporated therein, mobile communication device 102 represents a broad range of mobile communication devices known in the art, including but are not limited to wireless mobile phones and personal digital assistants equipped with communication capability.


The term “wireless mobile phone” as used herein, including the specification and the claims, refers to the class of telephony devices equipped to facilitate a user in communicating with another user of another communication device, notwithstanding the user's movement around different geographic areas, so long the wireless mobile phone is In contact with a base/service station of a wireless network service provider. The term includes the analog as well as the digital subclasses. Communication may be voice and/or data, audio, textual and/or visual. The other user/communication device may be mobile or land line based.


RFID reader 120 represents a broad range of such devices known in the art or to be designed. Currently, most RFID readers 120 employ proprietary formats/protocols. That is, RFID readers 120 of different manufacturers tend to employ different frequencies, amplitudes, and/or keying Schemes (which may be frequency shifting keying (FSK), amplitude shifting keying (ASK) or phase shifting keying (PSK)).


Various embodiments of the methods of the present inventions, including elements 106, in particular, added elements, will be described in turn below.


Method


FIG. 2 illustrates a method view of the present invention, in accordance with one embodiment. As illustrated, device 102 is first provided with the RFIDs, block 202. The RFIDs may be provided in any one of a number of known or to be designed manners, including but are not limited to

    • manual entry, using a keypad of device 102,
    • read into device 102, from an access/identification card, using a magnetic or optical card reader of device 102,
    • downloaded Into device 102, from a coupled computing device, through a serial/parallel port of device 102 or through a network interface of device 102 using SMS or HTTP messages.


Typically, provision of a RFID will include the manner the RFID is to be outputted, i.e. signaled. As alluded to earlier, the manner it is to be signaled is dependent on the format/protocol employed by the Intended RFID reader 120. For examples, for a garage door key, the format/protocol employed by RFID reader 120 of the garage opener system, and for an affinity program member identifier, the format/protocol employed by RFID reader 120 of the point-of-sale system of the entity offering the affinity program.


Alternatively, a default signaling format/protocol, such as an industry standard, the most popular proprietary format/protocol, or a selected proprietary format/protocol maybe assumed instead, when one is not provided.


During operation, in response to a user instruction, typically after the user has selected the RFID to be outputted from a number of RFIDs stored in device 102, block 203, device 102 outputs the selected RFID as instructed, emulating an active RFID transponder, block 204.


For the embodiment, one RFID, e.g. an access key/identifier (such as an employee number), may also be selected/designated as a default RFID, the output of which may be emulated in a passive manner. That is, the selected/designated default RFID will be outputted automatically, whenever device 102 is within the proximal presence, or more specifically, the operational space, of an intended RFID reader 120.


Accordingly, device 102 monitors for probing signals of an intended RFID reader 120 (or a type of RFID readers 120), to determine whether device 102 is within the operational space of such a RFID reader 120, block 205. On so determining, device 102 outputs the designated RFID automatically, emulating a passive RFID transponder, block 206.


A Hardware/Software Implementation


FIG. 3 illustrates the relevant elements of device 102, in accordance with one embodiment. As illustrated, for the embodiment, device 102 includes processor 302, memory 304, persistent store 306, transceiver 308, and a number of other components 310, coupled to each other via bus 312.


Persistent store 306 and memory 304 are employed to store permanent and working copies of a software implementation of the operating logic 320 of device 102, including the supplemental RFID feature 322. In various embodiments, persistent store 306 may be an EEPROM (or like kind variants, such as a Flash Memory, a Memory Stick), a magnetic or optical disk drive, a CDROM, a DVD drive and so forth. Memory 304 may be any SORAM, DDRAM or other high speed volatile as way as non-volatile storage devices known in the art.


Processor 302 is employed to execute operating logic 320, including RFID feature 322. As will be readily apparent from the description to follow, operating logic 320 may be implemented in any one of a number of suitable system programming languages, including but not limited to high level languages that may be compiled into executable instructions supported by processor 302. Processor 302 may be any one of a number of processors designed or to be designed for mobile devices.


Except for transceivers 308, RHO feature 322 and the manner the various elements of FIG. 3 are used to practice the present Invention, the other illustrated elements are known in the art, and accordingly will not be further described. One embodiment of transceiver 308 will be described referencing FIG. 4, and one embodiment of RFD feature 322 will be described, referencing FIG. 6-7.


As described earlier, processor 302, memory 304, persistent store 306 and bus 312 may be shared elements of device 102, also employed to implement the primary communication function of device 102. However, in alternate embodiments, dedicated elements may be employed for some or all of these elements instead.


In one embodiment, device 102 is a wireless mobile telephone, an exploded view of which is illustrated in FIG. 5a. Wireless mobile phone 500, in addition to the earlier described elements, also includes display 506, control buttons 504, keypad 502, antenna 508, body 512 and cover 514. Body 512 is substantially rectangular in shape. Further, body 512 is palm-sized or smaller.


For the embodiment, cover 514 includes embedded electronic components having instructions, data, and/or locations to obtain such instructions and/or data to personalize, customize and/or enhance phone 500. Phone 500 includes complementary electronic component interface 516 in support of such personalization, customization and/or enhancement.


Cover 514 may form a part of housing 512, i.e. a required element to complete phone 500, or it may be an accessory to be adorned by phone 500, i.e. not a required element to complete phone 500.


In another embodiment, device 102 is a PDA, an exploded view of which, is illustrated in FIG. 5b. PDA 502, in addition to the earlier described elements, also includes display 524, control buttons 522, antenna 526, body 532, and cover 534. Body 530 is also substantially rectangular in shape, as well as palm-sized or smaller.


Similarly, for the embodiment, cover 534 includes embedded electronic components having instructions, data, and/or locations to obtain such instructions and/or data to personalize, customize and/or enhance PDA 520. PDA 520 includes complementary electronic component interface 536 in support of such personalization, customization and/or enhancement.


Cover 534 may form a part of housing 532, i.e. a required element to complete PDA 520, or it may be an accessory to be adorned by PDA 520, i.e. not a required element to complete PDA 520.



FIG. 5c-5d illustrate yet another embodiment of device 102, another wireless mobile telephone, an exploded view of which is illustrated. Wireless mobile phone 540 is similarly constituted as the earlier described embodiments, including body 542 and cover 544. However, body 542 has a substantially boomerang or banana shape. Body 542. is also typically palm-sized or smaller.


For the embodiment, cover 544 also includes embedded electronic components having instructions, data, and/or locations to obtain such Instructions and/or data to personalize, customize and/or enhance phone 540. Phone 540 includes complementary electronic component interface (not shown) in support of such personalization, customization and/or enhancement.


Cover 544 may form a part of housing 542, i.e. a required element to complete phone 540, or it may be an accessory to be adorned by phone 540, i.e. not a required element to complete phone 540.


In all or selected one(s) of these embodiments, some or all elements 106 in support of the RFID feature of the present invention may be provided through embedded electronic components of the housing/accessory covers.


Smart covers are the subject matters of subject matter of co-pending U.S. application Ser. No. 10/087,098, filed Mar. 1, 2002, entitled “Personalizing Electronic Devices and Smart Covering”, and U.S. application Ser. No., <insert>, filed May 2, 2003, entitled “Personalization of Mobile Electronic Devices and Smart Accessory Cover”, which specifications are hereby fully incorporated by reference.


While all three embodiments of FIG. 5a-5d have been illustrated with smart covers and external antennas. In alternate embodiments, the present invention may be practiced without smart covers and/or external antennas. The present invention may be practiced with conventional covers, without embedded intelligence and/or internal antennas.


Transceiver


FIG. 4 illustrates transceiver 308 of FIG. 3 in further details, in accordance with one embodiment. As illustrated, for the embodiment, transceiver 308 includes a joint radio frequency (RF) transmit/receive (TX/RX) section 402, separate signal processing sections 408 and 410 for a range of higher frequencies and a range of low frequencies, switch 404 and splitter 406. The elements are coupled to each other as shown.


For the embodiment, joint RF TX/RX 402 includes in particular, switch 420, filters 412 and 422, low noise amplifier 424 and power amplifier 414, coupled to one another as shown. Switch 420 is employed to switch between transmitting and receiving RF signals. Filters 412 and 422, low noise amplifier 424 and power amplifier 414 are employed to perform their conventional filtering and amplification functions on the transmit and receive signals.


For transmission, switch 404 switches between the output of high frequency signal processing 410 and the output of low frequency signal processing 408 to the transmit path of Joint RF TX/RX 402.


For reception, splitter 406 splits the output of the receive path of Joint RF TX/RX 402 and provides the receive signal to high frequency signal processing 410 as well as low frequency signal processing 406.


For the embodiment, high frequency signal processing 410 performs up and down conversions of the transmit and receive signals of the primary communication function of mobile communication device 102, e.g. the transmit and receive signals of a voice call. In one embodiment, the transmit and receive signals are transmitted and received In the GHz ranges:


Low frequency signal processing 408, on the other hand, performs up and down conversions of the transmit and receive signals of the RFID feature, e.g. the output signal of a RFID to emulate either an active or a passive transponder, and the received probing signal of a RFID reader. In one embodiment, the transmit and receive signals are transmitted and received in the MHz ranges.


Up and down conversions, filtering, amplifications, and so forth, in and of themselves, except for the manner they are being used to provide RFIDs using a mobile communication device, are known in the art, accordingly, will not be further described.


RFID Feature


FIGS. 6-7 illustrate selected portions of an example end user interface, and the operational flow of the relevant aspects of RFD feature 322 respectively, in accordance with one embodiment. FIG. 6 comprises FIG. 6a-6h.


As illustrated in FIG. 6a, for the embodiment, the user interface Includes screen 602 having selectable text display “RFID” 604, with which a user may interact to launch the RFID function (by selecting text display 604, using e.g. control keys 604).


As illustrated in FIG. 6b, for the embodiment, the user interface further includes screen 612 enumerating a list of RFIDs 614 stored in device 102. List 614 may be displayed for example, among other situations, in response to a user's selection of text display 604 of screen 602. A user may select one of the RFIDs, and instruct device 102 to output the selected RFD in a form of an appropriate radio frequency signal, emulating provision of the RFID by an active RFID transponder, using e.g. a “send/call” key of device 102.


Screen 612 also includes selectable “option” button 616, with which a user may interact to display a list of RFID management options, using e.g. control keys 504.


As illustrated in FIG. 6c, for the embodiment, the user interface further includes screen 622 enumerating a list of RFID management options 624, such as “add”, “edit” or “delete” RFIDs. List 624 may be displayed for example, among other situations, in response to a users selection of “option” 616 of screen 612.


As illustrated in FIG. 6d, for the embodiment, the user interface further includes screen 632 displaying field 634, through which a user may enter/edit a RFID name. Field 634 may be displayed for example, among other situations, in response to a users selection of “add” or “edit” of screen 622.


As illustrated in FIG. 6e, for the embodiment, the user interface further includes screen 642 displaying field 644, through which a user may enter/edit a RFID. Field 644 may be displayed for example, among other situations, in response to a user indicating completion of entry of a RFID name using screen 632.


As illustrated in FIG. 6f, for the embodiment, the user interface further includes screen 652 displaying a list of RFID types 654, with which a user may select and associate with a RFID. List 654 may be displayed for example, among other situations, in response to a user indicating completion of entry of a RED, using screen 642, thereby allowing the user to associate a RFID reader type with the entered RFID.


Each RFD reader type is assumed to have a deterministic RFID signaling format/protocol. Accordingly, by selecting the RFID reader type, the user is effectively selecting or specifying the RFID signaling format/protocol. in alternate embodiment, a user may be requested to select the RFD signaling format/protocol explicitly, as opposed to implicitly, in the illustrated embodiment.


As illustrated in FIG. 6g, for the embodiment, the user interface further includes screen 662 displaying a request 664 to confirm whether a RFD is to be selected or designated as the default RFID to be used for emulation of passive transponders. Request 664 may be displayed for example, among other situations, in response to a user selecting a RFID reader type, using screen 652, thereby allowing the user to (implicitly) associate a RFID format/protocol with the entered RFID.


As illustrated in FIG. 6f, for the embodiment, the user interface further includes screen 672 displaying a RFID and its details, including but not limited the intended RFID reader type, whether to be designated as the default RFID for use in emulating passive RFID. Request 674 may be displayed for example, among other situations, in response to a user selecting the “edit” option, using screen 622, or on completion of designating a RFID as the default RFID for emulating Passive transponders, using screen 662.


Operationally, as illustrated in FIG. 7, upon receipt of a request to launch the RFID function, support logic of the RFID feature 322 is loaded and given execution control, block 702. Thereafter, support logic 322 waits for user inputs, block 704.


On receipt of a user input/request, support logic 322 determines the nature of the input/request, block 706, taking into the context, i.e. the portion of the user interface being displayed, and with which the user just interacted in submitting the input/request.


As illustrated, on determining that the user has requested a current display list to be scrolled (e.g. RFID list 614 of screen 612), support logic 322 causes the list to be scrolled as requested. Thereafter, support logic 322 returns to block 708 and waits for further input.


Similarly, on determining that the user has requested a selected RFID to be sent (emulating output of the RFID by an active RFID transponder), support logic 322 causes the RFID to be outputted in a form of an appropriate RF signal (in accordance with the associated intended RFID reader type). Thereafter, support logic 322 again returns to block 710 and waits for further input.


On determining that the user has requested a list of options to be displayed (e.g. selection of “option” 616 of screen 612), support logic 322 causes the list of options to be displayed as requested. Thereafter, support logic 322 return to block 712 and waits for further input.


On determining that the user has requested to add a RFID (e.g. selection of “Add” of screen 622), support logic 322 facilitates addition of a RFID (e.g. successively guiding user entry of a RFID using screens 632-662. Thereafter, support logic 322 returns to block 714 and waits for further input.


These are a few examples of user inputs/requests support logic 322 may support. The present invention contemplates other user inputs/requests may also be supported, and handled accordingly, block 716.


CONCLUSION AND EPILOGUE

Thus, it can be seen from the above descriptions, a novel emulated RFID input method, using a mobile communication device, has been described. The present invention advantageously improved the ease of use for a user to provide data captured in a device to another system, especially for data captured in e.g. a mobile device.


While the present invention has been described in terms of the earlier described embodiments, those skilled in the art will. recognize that the invention is not limited to the embodiments described. The present invention can be practiced with modification and alteration within the spirit and scope of the appended claims. Thus, the description is to be regarded as illustrative instead of restrictive on the present invention.

Claims
  • 1. A method for operating a mobile communication device comprising: receiving, by the mobile communication device, a radio frequency identification (RFID) probing signal from an RFID reader external to the mobile communication device;executing, on processing circuitry in the mobile communication device, instructions stored in a memory in the mobile communication device, the instructions configured to cause the mobile communication device to: output an RFID signal and output a voice call signal, wherein the RFID signal is output in response to the mobile communication device determining the mobile communication device is in an operational space of the RFID reader based upon receipt of the RFID probing signal, and wherein the voice call signal is output over a wireless network and within a radio frequency range that is different than a radio frequency range used to output the RFID signal.
  • 2. The method of claim 1, wherein the RFID signal includes RFID data comprising a selected one of a security key and an identifier.
  • 3. The method of claim 2, wherein the security key comprises a selected one of a garage door key, an exterior door key, an interior door key, and a motor vehicle door key.
  • 4. The method of claim 2, wherein the identifier comprises a selected one of a social security number, a driver's license number, an affinity program account number, and a credit card number.
  • 5. The method of claim 2, wherein the method further comprises facilitating a user in selecting the RFID data from a plurality of the RFID data using the mobile communication device.
  • 6. The method of claim 2, wherein the method further comprises facilitating provision of the RFID data to the mobile communication device.
  • 7. The method of claim 6, wherein facilitating provisioning of the RFID data to the mobile communication device includes facilitating provision of at least a signaling attribute associated with the outputting of the RFID data.
  • 8. The method of claim 1, wherein the mobile communication device is one of a wireless mobile phone and a personal digital assistant equipped with communication capability.
  • 9. A method for operating a mobile communication device comprising: executing, on processing circuitry in the mobile communication device, instructions stored in a memory in the mobile communication device, the instructions configured to cause the mobile communication device to monitor, output an RFID signal, and output a voice call signal;wherein the monitoring comprises monitoring for a proximal presence of a radio frequency identification (RFID) reader external to the mobile communication device and determining the mobile communication device is in an operational space of the RFID reader based on an RFID probing signal received by the mobile communication device from the RFID reader;wherein the outputting of the RFID signal comprises outputting the RFID signal in response to determining the mobile communication device is within the proximal presence of the RFID reader based u on receipt of the RFID robin signal; andwherein the outputting of the voice call signal comprises outputting the voice call signal over a wireless network in a radio frequency range different than a radio frequency range in which the RFID signal is output.
  • 10. The method of claim 9, wherein the RFID signal includes RFID data comprising a security key.
  • 11. The method of claim 10, wherein the security key comprises a door key.
  • 12. The method of claim 11, wherein the door key comprises a selected one of a garage door key, an exterior door key, an interior door key, and a motor vehicle door key.
  • 13. The method of claim 10, wherein the instructions are further configured to cause the mobile communication device to facilitate provision of the RFID data to the mobile communication device.
  • 14. The method of claim 13, wherein facilitating provisioning of the RFID data to the mobile communication device includes facilitating provision of at least a signaling attribute associated with the outputting of the RFID data.
  • 15. The method of claim 9, wherein the mobile communication device is one of a wireless mobile phone and a personal digital assistant equipped with communication capability.
  • 16. A mobile communication device comprising: communication circuitry configured to output voice call signals in a first radio frequency range over a wireless network and output radio frequency identification (RFID) signals in a second radio frequency range, which is different than the first radio frequency range;processing circuitry; anda storage medium including instructions, which, when executed by the processing circuitry cause the mobile communication device to: monitor for a proximal presence of an RFID reader external to the mobile communication device via the communication circuitry, the monitoring comprising determining the mobile communication device is in an operational space of the RFID reader based on an RFID probing signal received by the mobile device from the RFID reader;output a voice call signal for transmission over a wireless network via the communication circuitry in the first radio frequency range; andoutput an RFID signal via the communication circuitry in response to detection of the proximal presence of the RFID reader external to the mobile communication device based upon receipt of the RFID probing signal, wherein the RFID signal is output in the second radio frequency range.
  • 17. The mobile communication device of claim 16, wherein the RFID signal includes RFID data comprising a selected one of a security key and an identifier.
  • 18. The mobile communication device of claim 17, wherein the security key comprises a door key.
  • 19. The mobile communication device of claim 18, wherein the door key comprises a selected one of a garage door key, an exterior door key, an interior door key, and a motor vehicle door key.
  • 20. The mobile communication device of claim 17, wherein the identifier comprises a selected one of a social security number, a driver's license number, an affinity program account number, and a credit card number.
  • 21. The mobile communication device of claim 17, wherein the instructions are further configured to cause the mobile communication device to facilitate a user in selecting the RFID data from a plurality of RFID data.
  • 22. The mobile communication device of claim 17, wherein the instructions are further configured to cause the mobile communication device to facilitate provision of the RFID data to the mobile communication device.
  • 23. The mobile communication device of claim 22, wherein the instructions are further configured to cause the mobile communication device to include provisioning of at least a signaling attribute associated with the RFID data in the form of a radio frequency signal.
  • 24. The mobile communication device of claim 17, wherein the RFID data includes information identifying a user.
  • 25. The mobile communication device of claim 16, wherein the mobile communication device is one of a wireless mobile phone and a personal digital assistant equipped with communication capability.
  • 26. A mobile communication device comprising: communication circuitry configured to transmit voice call signals in a first radio frequency range over a wireless network;processing circuitry; anda memory storing instructions, which, when executed by the processing circuitry cause the mobile communication device to: monitor for a proximal presence of a radio frequency identification (RFID) reader external to the mobile communication device via the communication circuitry, the monitoring comprising determining the mobile communication device is in an operational space of the RFID reader based on an RFID probing signal received by the mobile communication device from the RFID reader;in response to determining the mobile communication device is in the operational space of the RFID reader based upon the receipt of the RFID probing signal, output an RFID signal via the communication circuity in a second radio frequency range that is different than the first radio frequency range; andtransmit a voice call signal to another mobile communication device via the communication circuitry at least in part over a wireless network in the first radio frequency range.
  • 27. The mobile communication device of claim 26, wherein the RFID signal includes RFID data comprising a security key.
  • 28. The mobile communication device of claim 27, wherein the security key comprises a door key.
  • 29. The mobile communication device of claim 28, wherein the door key comprises a selected one of a garage door key, an exterior door key, an interior door key, and a motor vehicle door key.
  • 30. The mobile communication device of claim 26, wherein the instructions are further configured to cause the mobile communication device to facilitate provision of RFID data to the mobile communication device.
  • 31. The mobile communication device of claim 30, wherein the instructions are further configured to cause the mobile communication device to include provisioning of at least a signaling attribute associated with the outputting of the RFID data in the form of a radio frequency signal.
  • 32. The mobile communication device of claim 26, wherein the mobile communication device is one of a wireless mobile phone and a personal digital assistant equipped with communication capability.
RELATED APPLICATION

This application is a continuation of U.S. patent application Ser. No. 13/363,202, filed Jan. 31, 2012 and entitled “Emulated Radio Frequency Identification,” now U.S. Pat. No. 8,381,974, which is a continuation of U.S. patent application Ser. No. 10/560,262, filed Dec. 9, 2005 and entitled “Emulated Radio Frequency Identification,” now U.S. Pat. No. 8,127,984, which was the National Stage of International Application No. PCT/US04/18397, filed Jun. 10, 2004 and entitled “Emulated Radio Frequency Identification,” which itself claims the benefit of U.S. Provisional Application No. 60/478,245, entitled “Radio Frequency Identification Using Mobile Communication Device” and filed Jun. 13, 2003.

US Referenced Citations (150)
Number Name Date Kind
4119800 Girardi Oct 1978 A
5335276 Thompson et al. Aug 1994 A
5448620 Gershkovich et al. Sep 1995 A
5473318 Martel Dec 1995 A
5530702 Palmer et al. Jun 1996 A
5590038 Pitroda Dec 1996 A
5793843 Morris Aug 1998 A
5957995 Beckmann et al. Sep 1999 A
6026308 Hsieh Feb 2000 A
6032054 Schwinke Feb 2000 A
6112984 Snavely Sep 2000 A
6164551 Altwasser Dec 2000 A
6167128 Fuller et al. Dec 2000 A
6314281 Chao et al. Nov 2001 B1
6359866 Svensson et al. Mar 2002 B1
6421347 Borgstahl et al. Jul 2002 B1
6434395 Lubin et al. Aug 2002 B1
6476708 Johnson Nov 2002 B1
6771981 Zalewski et al. Aug 2004 B1
6837427 Overhultz Jan 2005 B2
6892052 Kotola et al. May 2005 B2
7110792 Rosenberg Sep 2006 B2
7155411 Blinn et al. Dec 2006 B1
7245997 Kitao et al. Jul 2007 B2
7274909 Perttilä et al. Sep 2007 B2
7277809 DeWitt, Jr. et al. Oct 2007 B1
7280810 Feher Oct 2007 B2
7283044 Bandy Oct 2007 B2
7324476 Agrawal et al. Jan 2008 B2
7375616 Rowse et al. May 2008 B2
7440743 Hara et al. Oct 2008 B2
7502615 Wilhoite et al. Mar 2009 B2
7605701 Lee Oct 2009 B2
8127984 Zatloukal Mar 2012 B2
8260199 Kowalski Sep 2012 B2
8321346 Celi et al. Nov 2012 B2
8381974 Zatloukal et al. Feb 2013 B2
8393546 Yen et al. Mar 2013 B1
8519847 Honkanen et al. Aug 2013 B2
8618913 Bailey et al. Dec 2013 B1
20010028302 Degrauwe et al. Oct 2001 A1
20020052193 Chetty May 2002 A1
20020081987 Yoshida et al. Jun 2002 A1
20020123325 Cooper Sep 2002 A1
20020160775 Pecen et al. Oct 2002 A1
20020171534 Ashwin Nov 2002 A1
20020187779 Freeny, Jr. Dec 2002 A1
20030025603 Smith Feb 2003 A1
20030069048 Liu et al. Apr 2003 A1
20030104848 Brideglall Jun 2003 A1
20030114186 Goetz Jun 2003 A1
20030155416 Macklin et al. Aug 2003 A1
20030158785 Erca Aug 2003 A1
20030220711 Allen Nov 2003 A1
20040030601 Pond et al. Feb 2004 A1
20040067778 Sata et al. Apr 2004 A1
20040069852 Seppinen et al. Apr 2004 A1
20040077313 Oba et al. Apr 2004 A1
20040077352 Mahany Apr 2004 A1
20040087273 Perttila et al. May 2004 A1
20040093274 Vanska et al. May 2004 A1
20040111360 Albanese Jun 2004 A1
20040127256 Goldthwaite et al. Jul 2004 A1
20040171373 Suda et al. Sep 2004 A1
20040198233 Pratt Oct 2004 A1
20040204038 Suzuki et al. Oct 2004 A1
20040248616 Pecen et al. Dec 2004 A1
20040255138 Nakae Dec 2004 A1
20040263319 Huomo Dec 2004 A1
20050014468 Salokannel et al. Jan 2005 A1
20050040951 Zalewski et al. Feb 2005 A1
20050085226 Zalewski et al. Apr 2005 A1
20050088285 Jei Apr 2005 A1
20050099309 Hum May 2005 A1
20050116050 Jei Jun 2005 A1
20050127156 Yoo et al. Jun 2005 A1
20050171898 Bishop et al. Aug 2005 A1
20050184856 Pourchot Aug 2005 A1
20050242921 Zimmerman Nov 2005 A1
20050270185 Esterberg Dec 2005 A1
20050280537 Feltz Dec 2005 A1
20060003772 Semper Jan 2006 A1
20060017544 Tanaka et al. Jan 2006 A1
20060022802 Bridgelall Feb 2006 A1
20060044111 Kollar et al. Mar 2006 A1
20060052055 Rowse et al. Mar 2006 A1
20060097848 Davidson et al. May 2006 A1
20060111053 Wu et al. May 2006 A1
20060116127 Wilhoite et al. Jun 2006 A1
20060229113 Rowse Oct 2006 A1
20060237528 Bishop et al. Oct 2006 A1
20060238297 Tang et al. Oct 2006 A1
20060280149 Kuhl et al. Dec 2006 A1
20070018832 Beigel et al. Jan 2007 A1
20070030124 Lee Feb 2007 A1
20070032261 Boyer et al. Feb 2007 A1
20070037605 Logan Feb 2007 A1
20070060212 Shah Mar 2007 A1
20070066278 Hong Mar 2007 A1
20070120679 Shin et al. May 2007 A1
20070138299 Mitra Jun 2007 A1
20070159330 Chakraborty et al. Jul 2007 A1
20070178935 Shim et al. Aug 2007 A1
20070197261 Humbel Aug 2007 A1
20070262134 Humphrey et al. Nov 2007 A1
20070263595 Charrat Nov 2007 A1
20070274242 Lamacraft et al. Nov 2007 A1
20070286171 Guan Dec 2007 A1
20070293202 Moshir et al. Dec 2007 A1
20080011833 Saarisalo Jan 2008 A1
20080018433 Pitt-Pladdy Jan 2008 A1
20080027815 Johnson et al. Jan 2008 A1
20080040242 Chang et al. Feb 2008 A1
20080057876 Hsia et al. Mar 2008 A1
20080059374 Gangi Mar 2008 A1
20080068130 Batta Mar 2008 A1
20080078831 Johnson et al. Apr 2008 A1
20080100419 Jatschka May 2008 A1
20080143487 Hulvey Jun 2008 A1
20080146167 Rofougaran Jun 2008 A1
20080171579 Grubek Jul 2008 A1
20090058652 Hardy et al. Mar 2009 A1
20090090783 Killian et al. Apr 2009 A1
20090102660 Evans et al. Apr 2009 A1
20090143013 Hatano et al. Jun 2009 A1
20090170519 Wilhoite et al. Jul 2009 A1
20090209283 Yang Aug 2009 A1
20090221232 Estevez et al. Sep 2009 A1
20090243810 Pendlebury et al. Oct 2009 A1
20090291634 Saarisalo Nov 2009 A1
20100001838 Miodownik et al. Jan 2010 A1
20100026454 Rowse et al. Feb 2010 A1
20100128642 Bossler et al. May 2010 A1
20100137024 Maguire Jun 2010 A1
20100158077 Mahany Jun 2010 A1
20100217707 Phillips Aug 2010 A1
20100239079 Bao Sep 2010 A1
20100281261 Razzell Nov 2010 A1
20110021246 Rofougaran Jan 2011 A1
20110312271 Ma Dec 2011 A1
20120019363 Fein Jan 2012 A1
20120133483 Zatloukal et al. May 2012 A1
20120150601 Fisher Jun 2012 A1
20120284194 Liu et al. Nov 2012 A1
20130178159 Xie et al. Jul 2013 A1
20130337770 Huque et al. Dec 2013 A1
20140145823 Aase May 2014 A1
20140162721 Zatloukal et al. Jun 2014 A1
20140167914 Zatloukal et al. Jun 2014 A1
20150208245 Robinton et al. Jul 2015 A1
Foreign Referenced Citations (3)
Number Date Country
0074406 Dec 2000 WO
2004114239 Dec 2004 WO
2004114239 Dec 2004 WO
Non-Patent Literature Citations (18)
Entry
International Search Report and Written Opinion mailed Feb. 15, 2005 for PCT Application No. PCT/US04/18397, 11 pages.
Non-Final Office Action for U.S. Appl. No. 10/560,262, mailed Mar. 4, 2009, 5 pages.
Final Office Action for U.S. Appl. No. 10/560,262, mailed Aug. 17, 2009, 6 pages.
Advisory Action for U.S. Appl. No. 10/560,262, mailed Nov. 13, 2009, 3 pages.
Non-Final Office Action for U.S. Appl. No. 10/560,262, mailed Dec. 24, 2009, 6 pages.
Final Office Action for U.S. Appl. No. 10/560,262, mailed Jun. 22, 2010, 14 pages.
Notice of Non-Compliant Amendment (37 CFR 1.121) and Advisory Action for U.S. Appl. No. 10/560,262, mailed Sep. 8, 2010, 5 pages.
Advisory Action for U.S. Appl. No. 10/560,262, mailed Oct. 13, 2010, 3 pages.
Non-Final Office Action for U.S. Appl. No. 10/560,262, mailed Mar. 31, 2011, 12 pages.
Notice of Allowance for U.S. Appl. No. 10/560,262, mailed Nov. 1, 2011, 13 pages.
Non-Final Office Action for U.S. Appl. No. 13/363,202, mailed Jul. 16, 2012, 5 pages.
Notice of Allowance for U.S. Appl. No. 13/363,202, mailed Nov. 27, 2012, 8 pages.
Non-Final Office Action for U.S. Appl. No. 14/097,141, mailed Mar. 14, 2014, 10 pages.
Final Office Action for U.S. Appl. No. 14/097,141, mailed Sep. 16, 2014, 12 pages.
Non-Final Office Action for U.S. Appl. No. 14/097,152, mailed Mar. 31, 2014, 11 pages.
Final Office Action for U.S. Appl. No. 14/097,152, mailed Jul. 21, 2014, 12 pages.
Non-final Office Action for U.S. Appl. No. 14/097,152, mailed Oct. 28, 2015, 9 pages.
Final Office Action for U.S. Appl. No. 14/097,152, mailed May 20, 2016, 10 pages.
Related Publications (1)
Number Date Country
20130207777 A1 Aug 2013 US
Provisional Applications (1)
Number Date Country
60478245 Jun 2003 US
Continuations (2)
Number Date Country
Parent 13363202 Jan 2012 US
Child 13750970 US
Parent 10560262 US
Child 13363202 US