Patent Application
20080041929
The accompanying drawings, which are incorporated in and constitute part of the specification, illustrate various embodiments of the invention. Together with the general description, the drawings serve to explain the principles of the invention. In the drawings:
The following description of the various exemplary embodiments is illustrative in nature and is not intended to limit the invention, its application, or uses. The various embodiments disclosed herein provide methods and systems for scanning a preset area of proximity for RFID tags, for example, by completing the “To:” field in an e-mail program with the e-mail addresses of all the people (with RFID Tags) present within the defined proximity of the sending machine.
RFID tags are small devices that respond to an RF interrogation signal with a RF response at a predetermined frequency. The response may contain data in addition to identification information. RFID Tags may be implemented to either provide a passive response or an active response. Passive RFID tags use the received energy from the interrogation signal to generate a response. The detection range for passive RFID tags may be 15 to 20 feet.
Active RFID tags tend to have a considerably longer range than passive tags because they generate and transmit a response signal using power from a power supply of the active RFID tag (e.g., a battery). Active tags may be queried up to 200 feet or more. Various embodiments of the present invention may use either active RFID tags or passive RFID tags, depending upon the constraints, costs and other engineering considerations of the implementation.
An RFID reader typically includes circuitry configured to transmit an interrogation signal to other RFID tags in the vicinity. Upon receiving the interrogation signal, the other RFID tags in the vicinity return a response to the reader, either actively or passively, as described above. The RFID tags and RFID reader circuitry used to implement the invention may be any of several types of RFID tags and readers, including, for example, the RFID tags and readers described in U.S. Patent Publication 2005/0049760 to Narayanaswami et al., and in U.S. Pat. No. 6,802,659 to Cremon et al., the contents of both documents being hereby incorporated by reference in their respective entireties.
The RFID reader device 101 may be configured to include a silicon microprocessor and a metal coil surrounded by an encapsulating material of glass or polymer material. The metal coil, which serves as the tag's antenna, is typically made of copper or aluminum traces which are wound into a circular pattern on the tag. The size of the coil antenna determines the sensitivity of the RFID reader, and the distance the signals can be transmited. RFID coil antennas often operate at 13.56 MHz but can be designed to be operated at a wide range of other frequencies. In some embodiments, the RFID reader device 101 may be known as or configured as an RFID transceiver.
The RFID tag used in RFID reader device 101 may be an inductively coupled RFID tag which uses energy from the magnetic field generated by the RFID reader. The coil antenna of the RFID tag translates the magnetic energy into an electrical signal which is communicated to the logic of RFID reader device 101. To respond to the interrogation signal of another reader, the RFID tag of reader device 101 modulates the magnetic field, transmitting e-mail data back to the reader which sent the interrogation signal. The RFID tag used in RFID reader device 101 may be implemented as a capacitively coupled RFID as the detection and transmission ranges increase for these devices. Capacitively coupled RFID tend to cost less than inductively coupled RFID tags. Capacitively coupled RFID tags do not have a coil antenna, instead using silicon circuitry to perform the function of the coil antenna. A capacitively coupled RFID tag typically includes a silicon microprocessor and conductive carbon ink which serves as the tag's antenna applied to a paper substrate.
The conductive carbon ink antenna may be applied to the paper substrate through conventional printing means. The paper substrate, in turn, often has an adhesive backing to allow bonding to the email device 120-122.
The RFID reader device 101 may include a programmable memory configured to be modified or updated by an RFID writer. The RFID writer, which may be incorporated in the email device 120, can write to the programmable memory of the RFID reader device 101 to change data stored on it, for example, to change the user's email address stored on the RFID reader device 101. An RFID reader, which may be included as part of the RFID reader device 101, can feature bidirectional communication so as to be able to write to the programmable memory of the RFID reader device 101. In some embodiments, the user's email address can be written to the programmable memory by an RFID writer separate from the RFID reader device 101.
The email devices 120-122 are wirelessly coupled to the base station 210 of the wireless communication system via a wireless communication link. The establishment of a wireless communication link means that the email device 120-122 is registered with the wireless system for communication purposes. The base station 210 is typically connected to a mobile switching center (MSC) of the wireless communication system, which in turn, is connected to the public switched telephone network (PSTN). In some implementations of communication systems the landline portion of the communication link may pass through a portion of the Internet or another type of communications network. Other types and configurations of wireless communication systems known to those of ordinary skill in the art may be used to implement the various embodiments.
The email device 120 may also have a microphone and speaker (not shown) for the user to speak and listen to callers or for entry and feedback of commands to the email device 120 (e.g., speech recognition). In addition the email device 120, when embodied as a mobile telephone, may include a ringer for alerting the user to incoming calls or messages including the detection of RFID tags in the vicinity. A keypad 109 is configured as part of email device 120 for received commands from a user, dialing telephone numbers, or otherwise entering data. Email devices 120 may be configured with a data input/output (I/O) port 115 for downloading data, programs and other information or connecting to a network or the Internet.
In some embodiments an RFID detector 232 wirelessly coupled (or wired) to the system, to the network, or to another conference room device such as a projector. In such embodiments the various email devices 220-228 communicate their e-mail address to the system RFID unit 232, and in turn, receive the e-mail address of the others present within the effective area (e.g., the room within which a meeting is taking place). If more than one system RFID detector 232 is in place (not shown), directional antennas may be used to detect RFIDs from a couple of directions, thus determining which RFIDs are within the conference room or other e-mail address autogenerator boundary. The various email devices 220-228 may be equipped with a directional receiving antenna, for example, such as antennal 230 coupled to email device 220. Some embodiments may have receiver circuitry capable of measuring the signal strength of a received RFID signal. Such embodiments may be set to only accept signals above a certain predefined signal strength level.
The method begins at 301 and proceeds to 303 where the application software for implementing the invention in a wireless device is downloaded, or otherwise programmed into, the wireless device. The application software may be initially loaded onto the wireless device in the factory, purchased by the user from a brick-and-mortar store on floppy disks, downloaded from the Internet, or otherwise communicated to the wireless device. The application software may be in the form of a software product for communicating an e-mail address, and may be in the form of a computer readable program stored on an electronically readable medium (e.g., a compact disk, a DVD, a floppy disk, a dongle memory, a memory chip, or the like). Once the application software is downloaded onto the wireless device the method proceeds to 305 to detect the configuration of the wireless device. This may include detecting the type of operating system, the type of software used for e-mail capabilities, detecting the processor used in the wireless device and the amount and location of memory, detecting the communications formats, determining what user input/output components are available (e.g., touchpad, keyboard, mouse, display screen, speaker, or the like). Once the device configuration has been ascertained in 305 the method proceeds to 307.
In block 307 it is determined whether the user wants to customize the application software themselves, or install a default version of the configuration options. The default version may vary from one type of wireless device to another, so as to enhance the usefulness of a given set of capabilities on that particular wireless device, based on the device configuration detected in block 305. If, in 307 the user opts to customize the configuration, the method proceeds from 307 to 309 via the USER CONFIG branch. In 309 the user is presented with options for setting up the application. The options available to the user may include any type of features affecting the performance, operation or appearance of the RFID e-mail application program. Such features may include options for setting up the menuing system, for specifying the buttons to be used in controlling the program, for providing an input for the RFID reader and tag (if these components are not already integrated into the wireless device), and options for setting up the actual e-mail itself such as specifying a signature line, storing the e-mail in a draft section or leaving it open to be completed, or the like. Once the user has specified the options for the RFID e-mail application program in 309, the method proceeds to 311. Back in 307, if the user opts to go with the default configuration the method proceeds along the DEFAULT branch from 307 to 311.
In block 311 any drivers which may be needed are loaded. For example, if a driver is needed for the program to communicate with the RFID receiver or detector, the driver is loaded in 311. Once all drivers needed to run the application program have been loaded in 311 the method proceeds to 313. In 313 it is determined whether the particular e-mail program in use on the email device is compatible with the application program. That is, it is determined whether the application program of the RFID e-mail address autogenerator can operate in conjunction with the e-mail program to either save e-mail addresses which have been detected or use them to populate an e-mail. If the e-mail program is compatible the method proceeds from 313 along the “YES” branch to 317. If it is determined in 313 that the e-mail program is not compatible, the method proceeds from 313 along the “NO” branch to 315.
In 315 an output method is selected to communicate or otherwise provide any detected e-mail addresses to the e-mail program of the email device. The e-mail address data in the signal may be produced in a format acceptable to an e-mail application program, such as a vCard format or other like format. If the e-mail program will not permit the RFID e-mail address autogenerator application program to open an e-mail and populate it with detected e-mail addresses, the RFID e-mail application program may instead be configured to save the detected e-mail addresses to a file of a predefined format. In this way, the user could open the file from within the e-mail program and access the e-mail addresses.
Alternatively, the user could access the file and cut-and-paste the e-mail addresses into an e-mail being created. In another embodiment, the RFID e-mail application program could itself send an e-mail to the user containing the detected e-mail addresses, so that the user would readily be able to access them. Once the output method is selected in block 315 the method proceeds to 317.
In 317 the storage preferences are set up. Similar to the output method in 315, the RFID e-mail application program may be configured to store any detected e-mail addresses either within the e-mail program of the email device or in a different file, or both. In 317 the directory or other storage location is specified, as well as the formatting of the data (e.g., file format, time stamp, fields to be stored, or the like). Storage of the detected e-mail addresses may be done to provide access to the detected e-mail addresses, or for back up purposes. Once the data storage options have been specified the program proceeds to 319. In 319 the RFID e-mail application program controls and menuing scheme, and other options specifying the look-and-feel and performance of the program are set up. The method then proceeds to 321.
In 321 the RFID output preferences are set up. These preferences may include the e-mail address preferred by the user for communication via RFID, whether or not the user's name and/or additional contact information is to be included with the e-mail address, and any other variable concerning the content of the data to be delivered via RFID. In some embodiments the RFID signal may contain a URL where additional user information can be retrieved (e.g., email addresses, telephone numbers, other URLs, street address or the like). The RFID output preferences may also include the transmitter power level, in the event an active RFID transmitter is used, to set the transmission power level, any encryption scheme or encoding scheme used on the data, as well as the format for sending the data. Once the RFID output preferences have been specified in 321 the method proceeds to 323 to determine whether the setup is complete. If it is determined that the setup is not yet completed or the user want to change one or more values or parameters, the method proceeds from 323 via the “NO” branch back to 307. However, if it is determined in 323 that the setup is completed, the method proceeds along the “YES” branch to 325 where the method ends.
After displaying the detected e-mail identities in 409, the method proceeds to 411 where it is determined whether any e-mail identities are known to be missing from the list. For example, the user may look around the meeting and see that some of the people at the meeting do not have an e-mail address appearing on the list, or see that the number of attendees does not match the number of identities or e-mail addresses on the list. If it is determined that one or more identities is missing from the list, the method may proceed from 411 along the “YES” branch to 413. In 413 the user moves the email device to a better proximity for reception by either adjusting the position of device so the RFID antenna receives a stronger signal, or possibly by simply walking around the room or to a different location. Once the user has done this, the method proceeds to 417 to determine whether the list of detected identities is final.
Back in block 411, if it is determined that no e-mail identities are known to be missing from the list, the method proceeds from 411 along the “NO” branch to 415. In 415 the user is given the option to manually alter the list of e-mail identities. The user may remove any e-mail addresses from the list, if, for example, the user does not want to send an e-mail to that person, or an e-mail identity was detected for someone who was not actually participating in the meeting or otherwise does not belong on the list. The user may also be prompted by the email device to add more e-mail addresses to the list. This could occur, for example, if there are other people present whose e-mail identities were not detected by the user's email device, or the user simply wants to add more names to the e-mail mailing list. In either case, once the user is finished manually altering the list the method proceeds from 415 to 417.
In block 417 it is determined whether the list of e-mail identities is finalized. If the user decides the list is not finalized, the method proceeds from 417 along the “NO” branch to 415. In some instances the user may opt to move to a better proximity for reception as described in 413, rather than manually altering the list. If, in block 417, it is determined that the list of e-mail addresses is complete, the method proceeds from 417 along the “YES” path to 419 to access the e-mail application used on the user's email device, e.g., Lotus Notes, Microsoft Outlook, Eudora, Mozilla Thunderbird, Pegasus, Claris, Blitzmail, Pronto Mail, Mutt, Pine, or the like. In some embodiments, several or all of the functions outlined above for practicing the invention may be done either in the e-mail application program itself or with the RFID e-mail application program working in conjunction with the e-mail application. In some embodiments, rather than accessing or passing data directly to the e-mail application program, a data file associated with the e-mail application program is accessed and modified to include the detected e-mail addresses.
Once the e-mail application has been accessed the method proceeds to 421 to populate an e-mail message with the e-mail addresses that have been obtained using the RFID e-mail application program. Depending up the options chosen by the user, the RFID e-mail application program may set up an e-mail with the user's signature line, ready to content to be added by the user before mailing. For example, the e-mail addresses detected using RFID tags may be used to complete the “To:” field in the e-mail application program. Alternatively, the e-mail address can be stored within the e-mail application in a format conducive to retrieval by the user, for example, as an e-mail group, or in a “contact” folder. In general, the detected e-mail address may be saved in any format convenient to the user, as would be known by those of ordinary skill in the art. Once an e-mail message has been populated or the e-mail addresses have otherwise been saved in block 421, the method proceeds to 423 and ends.
Various steps may be included or excluded as described herein, or performed in a different order, with the rest of the activities still remaining within the scope of at least one exemplary embodiment. For example, a particular user may not be interested in seeing the detected e-mail address displayed and may not want the option of editing the list of detected e-mail addresses. In such instances the blocks 409-417 would be omitted and the method would proceed directly from 407 to 419. It is expected that those of ordinary skill in the art may perform would know to change the order of the activities in other manners as well.
The processing units, processors and controllers described herein (e.g., processor 103 of
The use of the word “exemplary” in this disclosure is intended to mean that the embodiment or element so described serves as an example, instance, or illustration, and is not necessarily to be construed as preferred or advantageous over other embodiments or elements. The term “e-mail application,” as used herein, is intended to mean any software application or routine that sends an electronic e-mail message, for example, over the Internet, and/or is able to receive an e-mail response. The description of the invention provided herein is merely exemplary in nature, and thus, variations that do not depart from the gist of the invention are intended to be within the scope of the embodiments of the present invention. Such variations are not to be regarded as a departure from the spirit and scope of the present invention.
