Handheld devices (“HHDs”), including, for example, mobile devices, personal digital assistants, handheld computers, cameras and Smartphones, are devices that are usually hand held, often pocket-sized devices, with display screens, touch input and/or miniature keyboards. HHDs are most often used for communication purposes. HHDs are becoming ubiquitous and, for many, indispensable for daily lives and activities. As such, there has not been any way to have users be able to control specific preset functions on HHDs based on the HHDs location, or otherwise, without the skills necessary to use a software development kit (SDK) or programming tool set. In an ever more complicated world, there is a need for HHDs to function more seamlessly with their environment for the benefit of the user and for increasing the HHD's flexibility.
HHDs will become even more powerful and prevalent in the near future by being more flexible in function and in how they interact with the user's environment, thereby imparting more value to the end user. Utilizing Radio Frequency Identification (RFID) technology will enable handheld devices to achieve this flexibility and add value to the user's environment. Current HHD products available for RFIDs do not allow user directed commands or messages to be stored on the RFIDs and require interaction with a back-end server to perform functions.
These and other disadvantages are overcome by a method for interactively interfacing HHDs and RFID media. The method includes starting an application on a HHD for interfacing with RFID media, the HHD including a built-in RFID reader, receiving user input relating to the storing of commands or messages of RFID media, creating one or more commands or messages based on the received user input, and storing the one or more commands or messages on a RFID media using the RFID reader.
These and other disadvantages are also overcome by a method for interactively interfacing HHDs and RFID media. The method includes passing a HHD within range of a RFID media that includes one or more commands stored thereon, the HHD including a built-in RFID reader, interrogating the RFID media with the RFID reader, receiving, on the HHD, the one or more commands from the RFID media, the HHD processing the one or more commands from the RFID media, and in response to the processing of the one or more commands, the HHD executing one or more functions.
These and other disadvantages are also overcome by a method for interactively interfacing HHDs and RFID media. The method includes passing a HHD within range of a RFID media that includes one or more messages stored thereon, the HHD including a built-in RFID reader, interrogating the RFID media with the RFID reader, receiving, on the HHD, the one or more messages from the RFID media, the HHD processing the one or more messages from the RFID media, the processing including determining if the one or more messages are intended for the HHD, and in response to the processing of the one or more messages, the HHD displaying the one or more messages.
These and other disadvantages are also overcome by a system for interactively interfacing handheld devices and RFID media. The system includes one or more RFID media capable of having commands and messages stored thereon and a HHD for interfacing with RFID media, the HHD including a built-in RFID reader capable of reading and writing commands and messages from and to RFID media, a central application that includes instructions for receiving user input relating to storing of commands or messages of RFID media, creating one or more commands or messages based on the received input, and storing the one or more commands or messages on a RFID media.
These and other disadvantages are also overcome by a system for interactively interfacing handheld devices and RFID media. The system includes a RFID media capable of having messages stored thereon, the RFID media located on a consumable item and includes a message with information describing the consumable item, and a device capable of reading and writing messages from and to the RFID media, the device including a built-in RFID reader capable of reading and writing messages from and to the RFID media, a processor, and a memory including a central application including instructions executable by the processor for processing messages read by the RFID reader from the RFID media, including the message with information describing the consumable item, creating a message that includes a time stamp and a unique identifier (ID) for the consumable item, and storing the created message on the RFID media on the consumable item.
Embodiments are described with reference with to the following figures, in which like numerals refer to like elements.
Described herein are embodiments of systems and methods for interactively interfacing handheld electronic devices (HHDs) and radio-frequency identification (RFID) media, such as Near Field Communication (NFC) or FeliCa media. Embodiments include systems and methods that code HHDs, control HHDs based on proximity to RFID media, store controls and information internally in HHDs and externally in RFID media, trigger such controls in a location-based context and transfer information to and from HHDs and RFID media. Embodiments are implemented as a HHD application in which a user may modify or change settings on their HHD or in their environment by or based on proximity to RFID media. Embodiments uniquely enable a user to store commands or code on RFID media to cause preset functions to occur on the user's HHD or in the user's environment by being in the presence of the user-modified RFID media.
When the term “user” is used throughout this specification, it is generally meant to refer to end-users that own and operate HHDs and that will use HHDs with the functionality described herein.
HHD users may use certain embodiments to control settings or functions of the users' HHDs; in embodiments, users may control settings or functions of the HHDs based on the location of use of the HHDs (such as in their car, office or home). In these embodiments, specific functions of the HHDs may be activated, or inactivated, (based on user input) based on the given location (e.g., a car). For example, in a car a user may wish to have the HHD's GPS and Bluetooth “ON”, but the HHD's WiFi settings “OFF”. In this example, the RFID reader on the HHD interacts with the RFID tag/sticker placed in the car and configures the HHD based on the unique settings previously programmed by the user. This makes the usage of the phone much more efficient for the user by only turning ON (or OFF, as the case may be) functions or settings the user has pre-specified for a specific location (i.e., at the location at which the RFID tag/sticker is placed). At the same time, valuable battery power of the phone is conserved by not using power intensive features such as WiFi that the user does not regularly use in those specific locations (e.g., in the car).
Embodiments are not limited to configuring the HHD to specific settings and programs based on the HHD's specific and unique location. Embodiments program HHDs (e.g., via an application) to transmit commands (over WiFi or other radiofrequency technology) to, for example, turn on and turn off lights, appliances, etc. For example, embodiments may program a HHD to turn on a television and room lights and turn off an alarm security system when the HHD enters a house (e.g., triggered by the HHD moving into range of certain RFID media).
In other embodiments, specific, unique data is transferred onto RFID tags of produce and other perishables to “time stamp” and give the perishables a unique code. The time stamp may be received and processed by an application to indicate whether the perishable has reached its expiration date or not. The unique code enables multiple units of the same perishable to be distinguished from one another (e.g., to distinguish one milk carton from three otherwise identical milk cartons in the same refrigerator). This embodiment is different than what was is currently described in the art in which an RFID reader simply reads information on the RFID tag that was placed on the produce item by the original manufacturer. There are limitations with this prior art method; one example being the fact that if one places two otherwise identical milk cartons in the refrigerator, the RFID tags on the milk cartons may cancel each other's signals and the reader would record zero milk cartons. To explain, in current RFID readers and tags, the communications protocol between the reader and the tags may use a scheme similar to slotted Aloha in which slots are provided for the tags to send text. Due to physical constraints, tags are unaware of other tags and, therefore, collisions may occur when multiple tags use the same slot for sending text. Since tags choose their slots randomly, collisions may be resolved in subsequent read iterations, and after a number of iterations, identification data from all tags may be retrieved. See, Harald Vogt, “Efficient Object Identification with Passive RFID Tags,” Swiss Federal Institute of Technology (ETH), August 1998. Also there is no way to identify the two milk cartons apart (because they have the same ID tags) and therefore no way to keep track of each of them individually.
In this manner, embodiments may monitor items so that when an item is removed from, e.g., a refrigerator or closet, and not replaced, an RFID reader, e.g., in the refrigerator or closet, via peer-to-peer communication, transfers that information to a HHD (e.g., via the HHD's built-in RFID reader). This data may then be interfaced via an application to a user's shopping list, e.g., stored on the user's HHD (or to a family's shopping list stored in a family “cloud” storage) for shopping purposes or may be automatically transmitted by the HHD to the local produce store for home delivery. Further, when a user at a checkout line uses a HHD to pay for items (e.g., using RFID technology), the information of the items bought may be transferred to an application on the HHD. When receiving this information, the application may remove the item, e.g., a milk carton, from the user's shopping list and all other relevant shopping lists, e.g., via a cloud or other modalities such as peer-to-peer transfer.
In other embodiments, inventory of such items like water cooler water bottles and office supplies kept in supply closets may be tracked with RFID readers. For example, a water cooler may have a built in RFID reader that can interrogate RFID media on the water bottle and time stamp the RFID media of each water bottle uniquely and keep inventory. When the number of water bottles is low (e.g., set as an arbitrary number by a user), the RFID reader transmits that information to a HHD for processing. An application on the HHD may send that information to the water dispensing company for delivery or simply alert the user that the water bottle supply is low. Similarly, an RFID reader time-stamps office supplies, and when a particular office supply item runs low, transmits that information to a HHD for processing. An application on the HHD may send that information to a vendor for delivery or simply alert a user that the supply is low.
HHDs may include known and future mobile telephones, particularly, mobile smartphones, as well as other handheld electronic devices such as handheld computers, cameras and media devices. Such examples include the Apple iPhone™, the Google Android™ phones, and the Blackberry™. HHDs may also include larger devices such as iPads™, notebook, laptops and other mobile computers. In some embodiments of systems and methods described below, a non-mobile, fixed device, such as a RFID interrogator/reader with or without additional functionality may be used instead of a HHD.
The following refers to embodiments for changing the settings of the HHD automatically based on the location of the HHD.
With reference now to
For example, central application 20 enables a user to create and transmit specific command text or sets of command text to an external media, such as RFID media 14 (as also noted below, central application 20 may also enable user to create and transmit specific message text or sets of message text to an external media, such as RFID media 14). The user may place the command or command set by writing through the application to the RFID media 14 for storage. The RFID media 14 storage may be a passive repository known and used in the industry (e.g., a passive RFID tag). This passive media it is not active when not coupled with the RFID reader/interrogator and is only active when it obtains energy from the RFID reader/interrogator when interrogated. In alternative embodiments, RFID media 14 may be an active RFID media (e.g., an active RFID tag). An active RFID media is active and energized through its own or a connected power source.
A unique aspect of embodiments described herein is that commands placed on RFID media 14 may be device-specific. The user may assemble, e.g., using the application, a complex set of commands/instructions specifically for the device and transmit the set for storage on the RFID media 14. The command set may be transmitted with a unique HHD identifier (“HHD ID”) for the HHD 12 to the RFID media 14 and/or a separate user ID. This HHD ID (e.g., PIN, MEI, etc), user ID and/or a RFID media ID may be used to encrypt the command or command sets. In this manner the one or more commands or command sets are associated with the HHD 12, cannot be associated with another HHD or be altered by another HHD or other electronic device. Only the unique HHD 12 may decrypt and execute the command or command set. The storage of the RFID media 14 may be limited and may only allow a limited number of commands to be stored on the RFID media 14. However, the commands stored on the RFID media 14 may be from one or more HHDs so that different, unique sets of commands may be accessed and executed by different HHDs from the same RFID media 14. In embodiments, an HHD 12 has only the authority to restore, replace, or delete any commands with the same HHD ID
With continuing reference to
When HHD 12 is coupled to RFID media 14, RFID interrogator 16 may receive the commands (e.g., specific to HHD 12) from RFID media 14. RFID interrogator 16 may provide the commands to central application 20 for processing. Central application 20 may execute the processed commands simply by passing them on or by issuing necessary code to, executing necessary code to cause, or otherwise instructing, HHD 14 (HHD processor), cooperative applications 22 or hardware 24 to perform the command functions. The commands stored on RFID media 14 may include commands or code for controlling and causing HHD 12, cooperative applications 22 and hardware 24 to execute functions dictated by commands.
The commands and/or code may be stored by central application 20 inside the central application 20 or a cooperative application 22 in the HHD 12 permanent memory or internal memory media (e.g., a memory card) 26, or stored in an external media device, such as RFID media 14. Communications allowing reading and writing to this external media can be through capabilities of HHD 12 (e.g., WiFi, Wireless, Bluetooth, etc) or by external hardware 24 (e.g., RFID reader, NFC, Felica, etc). As noted above, RFID media 14 may be, but is not limited to an active or passive RFID tag. Passive tags come in specific tag formats such as Mifare (ISO 14443A) and associated near-field communications (NFC, ISO 18092/2004) and FeliCa (Japan). The NFC protocol is compliant with the ISO 14443 HF air-interface standard that supports the Mifare and FeliCa protocols, which communicate at 13.56 MHz. There are currently two storage capacities available for passive RFID tags: 1 k and 4 k, respectively. Future RFID tags with larger capacities will work well with embodiments described herein. Although RFID media 14 is NFC-compatible, other RFID media may be used.
With continuing reference to
The command sets may be text-based identifiers, for example two letters or more values, associated with a specific function and an action value. For example, command +GPS could mean turn on Global Positioning System (GPS) function of HHD 12 whereas −GPS would turn off the GPS function. Such functions would be associated with programmable features/applications of HHD 12 made available through the user interface.
Another example would be a command to check the charge status (e.g., BAT) of HHD 12 and recommend placing the HHD 12 into Recharge Mode once inside the home or office. This would be similar to the manual user interface such as those found in the HHD tool set or settings. These could include random sequential change in personalization of the HHD's screen, skin, Wall paper, screen saver, multimedia or connection functions such as Blue tooth, WiFi, radio or external sync (e.g., ear piece) being “ON” or “OFF”.
For example, in an embodiment of system 10, one or more RFID media 14 is located in a user's car. RFID media 14 can be loaded with a set of commands that are read by the user's HHD 12 to execute when within the proximity of the reader and NFC media 14. The command or set of commands are pre-stored to RFID media 14 by the user. These could be commands such as to turn on Bluetooth and GPS, but turn off WiFi, when HHD 12 is in the car.
Another embodiment of system 10, would include one or more RFID media 14 located at the front door of a user's house or at some other entry to the house. When the user's HHD 12 is in proximity to RFID media 14, the specific command set read by RFID interrogator 16 would turn off the Bluetooth and GPS functions of HHD 12 (conserving battery power) but turn on short range telecommunications antenna (e.g., WiFi). Other command sets might be household specific, such as if the house has a command set security function, HHD 12 could be told to inform the security company of the user's presence and make positive identification (e.g., Voice, PIN ID, Biometrics, etc) and disable the security alarm 30 of the house. Other commands might cause HHD 12 to transmit signals turning on television and/or stereo 32, adjust thermostat 34, and activate lights through lighting controls 36. In embodiments, as described above, central application 20 may receive and process commands from RFID interrogator 16 and issue code that causes HHD 12 or other component to perform functions per commands.
With continued reference to
In yet another embodiment of system 10, a user may store one or more messages on a specific RFID media 14. A message may be any type of textual communication that is intended for retrieval by one or more HHDs 12 that pass within interrogation range of RFID media 14. A message may include any amount or type of text (subject to storage limitations of RFID media 14), such as a single character, multiple characters, a word, multiple words, phrases, sentences, numbers, letters, etc. A message may be intended to be displayed (or otherwise output) to a recipient on recipient's HHD 12 or may be intended to only be internally processed by recipient's HHD 12. A message may be a reminder, note, comment, instructions, shopping list, or virtually anything the user intends. Indeed, the message may be intended for the user him/herself, e.g., as a note for later retrieval when next passing by RFID media 14. A message transmitted by HHD 12 and stored on RFID media 14 may be referred to as a “text drop,” i.e., text dropped on RFID media 14 by HHD 12. Messages may convey virtually any information and may convey that information to HHD users or merely for internal processing by the HHD. Messages should not be confused with text messages that are transmitted from one handheld telecommunication device to another via a telecommunication network.
A message may be for any user's HHD 12 that passes proximate to RFID media 14 or only to one or more specific users' HHDs 12 that pass proximate to RFID media 14. Accordingly, messages may include one or more specific user or HHD IDs. The message may be encrypted or otherwise stored with IDs so that only HHDs 12 with necessary IDs can de-crypt or otherwise retrieve and open message. Such messages may be consider to be electronic “Post-It™” notes. For example, a wife can access software on her HHD 12 and write a specific message in the car in presence of RFID media 14 to remind her husband to pick up the dry cleaning when he is next in the car. HHD 12 stores the message on RFID media 14. When her husband is in the car and his HHD's 12 RFID reader 16 interrogates RFID media 14 in the car, the message may be transferred to his HHD 12 for his reading. In embodiments, as described above, central application 20 may enable user to create and store messages on RFID media 14, including storing necessary IDs and encrypting as described herein.
Yet another embodiment of system 10 would include one or more RFID media 14 in areas where certain radio frequency (RF) settings of a phone should be disabled, such as in an airplane or hospital rooms. Such RFID media 14 would include commands stored thereon to disable such settings. For example, when an HHD 12 is within the presence of such RFID media 14 on a plane, the HHD 12 may retrieve commands to turn off the WiFi, GPS, blue tooth, and other network functions of HHD 12. RFID media 14 may also include commands so that when passenger leaves the plane, or other similar area, the RF settings on HHD 12 revert back to original or normal settings (e.g., ON).
In certain embodiments of system 10, RFID media 14 is not installed in any fixed location, but may be portable and carried around by a user, on an item, and animal, a vehicle, or otherwise. Such RFID media 14 may have messages and/or commands stored thereon that convey information to HHDs 12 and/or other RFID readers, or instruct functions be performed, when the RFID media 14 is in proximity to the HHDs 12 or other RFID readers. In these embodiments, it is the presence of the RFID media 14 in the environment, rather than the presence of the HHD 12 in an environment that includes a fixed RFID media 14, that triggers the transfer of messages (e.g., information) or commands. Examples of such embodiments are described herein.
With reference now to
Application may create one or more commands, command sets and/or messages per the input, block 56. As noted above, commands and command sets may be text-based identifiers, for example two letters or more values, associated with a specific function and an action value. The commands and command sets may cause HHD, applications or other hardware to execute the input functions. HHD (e.g., central application) may include instructions for translating the user-specified functions into the necessary commands or command sets to execute the functions. The instructions may include look-up tables identifying the code necessary to execute the functions. In alternate embodiments, received 54 user input may directly specify the commands or command sets (e.g., the code) to execute the functions.
When in range of the intended RFID media, application may transmit and store the one or more commands, command sets and/or messages to and on the intended RFID media, block 58. The application may transmit and store commands, command sets and/or messages to and on intended RFID media via the RFID reader/interrogator in any variety of manners known and understood by those of ordinary skill in the art. The application may transmit and store one or more user, HHD IDs and/or RFID ID, with associated commands, command sets and/or messages, to and on the intended RFID media, block 60. The application may transmit and store the ID(s) in the same step or a separate step with the commands, command sets and/or messages. Likewise, the ID(s) may be associated with the commands, command sets and/or messages on the HHD prior to transmitting or after transmitting on the RFID media. The storing 60 may include encrypting the commands, command sets and/or messages so that only the intended HHD and user may retrieve the commands, command sets and/or messages.
The above describes steps for storing commands, command sets and/or messages on an RFID. In embodiments, RFID media may have pre-stored commands, command sets and/or message. Such preset RFID media may include commands, command sets and/or messages that are stored on the RFID media during manufacturing, at a point of sale (e.g., a car dealership, grocery store, etc) or otherwise prior to installation of the RFID media at a specific location or on a specific item. Whether preset or stored by a user using embodiments described herein, commands, command sets and/or messages on RFID media may be later edited and may be read from RFID media.
With continuing reference to
If one or more messages are received 66 and determined 70 to be intended for HHD, the message(s) may be displayed (or otherwise output to user), block 72. For example, the message may be a message stored on the RFID media by another user for later retrieval by the current user (e.g., an electronic Post-It note, as described above). The message may be a secure or sensitive message or information that is encrypted and stored on the RFID media for retrieval only by a specific user using a specific HHD. The message may be double-encrypted, using known methods, with the user ID and the HHD ID and determining 70 may require the user to enter the user ID and/or a password to successfully decrypt the message (e.g., the user may enter such information through a display/interface provided by the central application). Alternatively, a message may simply be information that is intended to be stored or be internally processed by HHD or an application thereon. For example, if RFID media is, e.g., a RFID tag located on a grocery item or merchandise item on a shopping list, message may simply be information describing the item. The shopping list may be maintained by an application on HHD (e.g., central application or cooperative application) or elsewhere (e.g., home computer). Consequently, processing 68 may extract information and remove item from shopping list, or transmit information describing item to application maintaining shopping list for such removal. Further, a message may simply be information that is intended to be passed on to another device. Passing on this information may be done to indicate the presence of the HHD at the location of the RFID media.
Message may be displayed 72 on display of HHD. Alternatively, message may be converted to audio and output to the user through speakers of HHD. HHD (e.g., central application) may be set up by user to process and output the received 66 message per the user's preferences.
If one or more commands or command sets are received 66 and determined 70 to be intended for HHD, corresponding functions on HHD, cooperative application and/or hardware may be executed/performed, block 74. For example, such HHD settings as GPS and Bluetooth may be turned on while others such as WiFi may be turned off. Likewise, commands and/or command sets on the RFID media may instruct the HHD to transmit commands that affect the environment in which the RFID media and the HHD are located, or elsewhere. For example, HHD may transmit a command(s) to appliances, electronic equipment, light switches, thermostats, etc. (collectively referred here to as “external items”). Consequently, method 50 may transmit one or more commands to external items, block 76. The HHD may transmit such commands over WiFi, other radio frequencies and/or through a network connection, or other known means.
With continuing reference to
With reference now to
Alternatively, RFID reader/interrogator may be part of or connected to a computing device (e.g., with a processor, memory, transmitter, etc) that includes central application described above and/or is otherwise functionally capable of performing functions of HHD described above. Such computing device may be installed on or built-in to the, e.g., a refrigerator, pantry closet, cabinet, or other location where consumable is stored. In such an embodiment, RFID reader/interrogator interrogates 102 RFID media on a consumable item and simply transfers the information to the computing device. The computing device may be a HHD temporarily or permanently installed on, e.g., a refrigerator, pantry closet, cabinet, or other location where consumable is stored.
RFID reader/interrogator may time stamp the item's RFID media, block 104, and/or write a specific, unique identifier (e.g., an ID number) on the item's RFID media, block 106. RFID reader/interrogator may determine time from HHD or network. Likewise, unique identifier may be provided by HHD (e.g., by central application). Indeed, HHD (e.g., central application) may instruct RFID reader/interrogator to time-stamp 104 and write unique identifier on RFID media, block 106, e.g., in response to receiving information interrogated 102 from RFID media. Time-stamping 104 and/or uniquely identifying 106 an item's RFID media enables the item to be uniquely identified and tracked so that it is not confused or mistaken for another item of the same type.
With continuing reference to
If item is determined 110 to still be present, HHD (e.g., central application) may determine whether item is past its expiration date (e.g., by comparing to expiration date transmitted 102 and stored by central application), block 118. If past its expiration date, HHD may notify user (e.g., through central application display, text message, e-mail, etc.) that item has expired and should be thrown out, block 120. If not expired, periodic interrogation 108 may continue.
It is noted that any computer running central or other application may also perform steps performed in method 100 by HHD. For example, RFID reader/interrogator may transfer 102 and 108 interrogated information to central application resident on home desktop or notebook computer. Such application may maintain shopping list and otherwise perform actions performed by central application on HHD as described above.
With reference now to
In alternate embodiment, RFID reader/interrogator 152 is part of a computing device, such as computing device (not shown) described above with reference to
With reference again to
An issue with any language is to encase the functions that work together in a proper and supportive structure. In an embodiment, a role of central application 20 is to do encase the functions that work together on the HHD 12 in a proper and supportive structure. In an embodiment, for every function within central application 20, there is corresponding Object C code. When the functions are strung together with their applicable input and output parameters, central application 20 will take the strung-together functions and parameters and wrap the functions and parameters into an executable program.
With continuing reference to
For example, an embodiment may use an existing and cooperative email application 22, which can share new emails or send out new emails with other applications. At that same time, a cooperative printer application 22 (e.g., Epson iPhone application) can also share functions that allow for printing actions. Being cooperative with central application 20, the email and printer applications 22 can be put together in a short command/code sequence with input/output parameter, and saved to an RFID tag 14 located near the Printer. The later saving to an RFID media 14 may be done by another code sequence saved within central application 20 memory. Accordingly, when HHD 12 comes within range of the RFID tag 14, the RFID tag 14 is read and the command/code sequence on the RFID tag 14 is downloaded and executed. In this case, the executed command/code sequence may cause any new email, based on a time/date stamp as part of the code sequence, to be sent to the printer.
In embodiments described herein, central application 20 gives users control over HHD 12 internal functions and features, as well as, functions and features of cooperative applications 22 and hardware 24. Such commands may be saved internally in HHD 12, but most important they can be saved to external media 14 (e.g., RFIDs, NFCs, FeliCa, etc) for latter recall and use. HHD 12 can then change settings, function, information and processing based on the HHD's 12 location in terms of proximity to these external media 14. Other current products are canned applications that cannot be changed and cannot take advantage of other capabilities provided by third-party applications 24 of HHD 12. Likewise, prior art systems require reference back to a service provider and/or mainframe/server computer to execute changes on HHD 12. Embodiments allow for a simple command codes as functions in one-line or BAT file structures. These codes can be strung together to create simple or complex instructions for HHD 12 or remote devices and can be controlled directly by the end user. Unlike conventional applications that are canned instructions to do specific actions, this string of commands allow a greater or general control of HHD 12. As noted above, basic building blocks of embodiments include a command interpreter, reader interpreter, the cooperative interface to other applications, and memory for the command(s).
As noted above, messages may include virtually any type of information. For example, the information may include patient medical information. Accordingly, when a patient sees a doctor, relevant updated medical information, such as immunization shot records, etc., may be transferred to RFID media 14 (e.g., via peer-to-peer transfer through RFID reader located near RFID media 14) that is conveniently located in the doctor's office. HHD 12 (e.g., central application 20) may encrypt the medical information with a patient identification number (ID) and/or a HHD ID, e.g., as described above, so as to only enable the patient and/or patient guardian to retrieve the information, in order to protect confidentiality of the information. Patients and/or patients' guardians may simply pass their HHD 12 in range of the RFID media 14 to retrieve the relevant medical information. For example, parents of young children have a difficult time keeping track of all their children's immunizations record. When the child's immunization record is updated in the doctor's computer system, a RFID reader may transfer the immunization record to the RFID media 14 in the doctor's office, and then to the parent's HHD 12, or directly to the HHD 12 via peer-to-peer communication between the RFID reader in the doctor's office and RFID reader 16 on HHD 12. Alternatively, parent may simply carry a RFID media card on to which the medical information is transferred by the doctor's office RFID reader. When the parent goes to their house, the medical information can be transferred from HHD 16 (or RFID media 14) to a computer system at home over WiFi or other radiofrequency methods. When a school requests the child's immunization record, the child may take the RFID media card with the immunization record to school, the immunization record may be transferred from the parent's HHD 12 to another RFID media, such as a paper embedded with RFID media, and taken to school, or the information may be otherwise electronically communicated to the school. In the same manner, patients can carry a list of their medications and allergies with them and continuously update them at their doctor's office.
In yet another embodiment, a library utilizes the systems and methods for interactively interfacing handheld device and RFID media. Library books are embedded with RFID tags 14 or other media. When a patron checks out a library book(s), a RFID reader at the library may write the due date and other pertinent information on the RFID tag. The RFID reader may also retrieve the due date and information describing the book(s) from the RFID tag 14 as well as information identifying the patron from the patron's HHD 12. This information is also transferred to the patron's HHD and processed by the HHD 12 (e.g., by the central application 20). The due date for the book(s) may be stored on the HHD 12 (e.g., by the central application 20). At the appropriate time, a due date reminder notice may be displayed on HHD 12 (e.g., by the central application 20), alerting the patron to return the book(s).
As can be seen by these examples, the embodiments described herein may be used for a large variety of purposes and implementations. As is also illustrated, RFID media 14 need not be stationary but may be used as a portable information storage that may be read from or written to by HHDs 12 and other RFID readers. For example, in another embodiment, users may carry RFID media 14 (alternatively, RFID media 14 may even be implanted into user's skin) that includes information relevant to user, such as security clearance, access rights, identifying information, ticket information (section/row, etc.) or other relevant information. Such information may be written to RFID media 14 by a HHD 12 or other RFID reader. When user enters or attempts to enter a secured area (e.g., building or room), a limited access area, an event arena or theater, etc., a HHD 12 or other RFID reader may interrogate the user's RFID media 14 and determine whether the user is entitled to entry. The HHD 12 or other RFID reader may time-stamp the user's RFID media or otherwise store a message on the RFID media indicating, e.g., when the user entered or attempted to enter, how many additional entries the user is entitled to, if any, how long the user is entitled to stay in the area, etc. In this manner, RFID media may act as a flexible and re-writable security or access pass or ticket for user and enable user's user thereof to be regulated and monitored.
With reference now to
HHD 12 may include a memory 404 and a processor 406. HHD 12 may also include an input device 408, a display device 410, an output device 412, and one or more antennas/transmitters 414/416. Memory 404 may include RAM or similar types of memory, and it may store one or more applications for execution by processor 406. Processor 406 executes the application(s), such as central application 20, cooperative applications 22 or other applications 28, which are stored in memory 404, or received from the Internet or other network 402. The processing by processor 406 may be implemented in software, such as software modules, for execution by computers or other machines. These applications preferably include instructions executable to perform the system and methods described above and illustrated in the drawings herein. The applications preferably provide graphical user interfaces (GUIs) through which users may view and interact with central application 20 and RFID media 14.
HHD 12 may store one or more database structures in memory 404, for example, for storing and maintaining information necessary to perform the above-described methods, such as commands, command sets, messages, shopping lists, etc. Alternatively, such databases may be in storage devices separate from HHD 12.
Also, as noted, processor 406 may execute one or more software applications in order to provide the functions described in this specification, specifically to execute and perform the steps and functions in the methods described above. Such methods and the processing may be implemented in software, such as software modules, for execution by computers or other machines. The GUIs may be formatted, for example, as web pages in HyperText Markup Language (HTML), Extensible Markup Language (XML) or in any other suitable form for presentation on a display device depending upon applications used by users to interact with the system.
Input device 408 may include any device for entering information into HHD 12, such as a touch-screen, keyboard, mouse, cursor-control device, touch-screen, microphone, digital camera, video recorder, etc. The input device 408 may be used to enter information into GUIs during performance of the methods described above. Display device 410 may include any type of device for presenting visual information such as, for example, a typical HHD screen. Output device 412 may include speakers or any device for providing information in audio form.
Antenna/transmitter 414/416 may include one or more antennas/transmitters or like devices for connecting to, transmitting to and receiving from a telecommunication network, such as CDMA or GSM mobile network 402. Likewise, antenna/transmitter 414/416 may also include WiFi or other antenna/transmitters for connecting to, transmitting to and receiving from other wireless networks 402 or other HHDs 418 (through peer-to-peer or via other networks 402).
Although only one HHD 12 is shown in detail, embodiments may use multiple HHDs 418 as necessary. HHDs 418 may be connected 420 to network 402. In addition, although HHD 12 is depicted with various components, one skilled in the art will appreciate that the server can contain additional or different components. In addition, although aspects of an implementation consistent with the above are described as being stored in memory, one skilled in the art will appreciate that these aspects can also be stored on or read from other types of computer program products or computer-readable media, such as secondary storage devices, including hard disks, floppy disks, or CD-ROM; or other forms of RAM or ROM. The computer-readable media may include instructions for controlling HHD 12, to perform a particular method, such as methods described above.
The terms and descriptions used herein are set forth by way of illustration only and are not meant as limitations. Those skilled in the art will recognize that many variations are possible within the spirit and scope of the invention as defined in the following claims, and their equivalents, in which all terms are to be understood in their broadest possible sense unless otherwise indicated.
This application claims the priority of U.S. Provisional Application Ser. No. 61/377,728, entitled “System and Method for Controlling and User Coding a Handheld Device, Storing Controls Internally or on an External Media and Triggering Such Controls in a Location-Based Context” and filed Aug. 27, 2010, which is hereby incorporated by reference in its entirety.
Number | Name | Date | Kind |
---|---|---|---|
4688026 | Scribner et al. | Aug 1987 | A |
5628204 | Shanaberger | May 1997 | A |
5732401 | Conway | Mar 1998 | A |
5837983 | Actis et al. | Nov 1998 | A |
5938726 | Reber et al. | Aug 1999 | A |
6297727 | Nelson, Jr. | Oct 2001 | B1 |
6545614 | Kasai | Apr 2003 | B1 |
6563430 | Kemink et al. | May 2003 | B1 |
6671646 | Manegold et al. | Dec 2003 | B2 |
6677852 | Landt | Jan 2004 | B1 |
6783060 | Marappan | Aug 2004 | B2 |
6993393 | Von Arx et al. | Jan 2006 | B2 |
7047159 | Muehl et al. | May 2006 | B2 |
7060030 | Von Arx et al. | Jun 2006 | B2 |
7076255 | Parupudi et al. | Jul 2006 | B2 |
7119659 | Bonalle et al. | Oct 2006 | B2 |
7128274 | Kelley et al. | Oct 2006 | B2 |
7155305 | Hayes et al. | Dec 2006 | B2 |
7172112 | Bonalle et al. | Feb 2007 | B2 |
7180422 | Milenkovic et al. | Feb 2007 | B2 |
7194278 | Cook | Mar 2007 | B1 |
7213766 | Ryan et al. | May 2007 | B2 |
7215978 | Hasegawa | May 2007 | B2 |
7248834 | Matsuo et al. | Jul 2007 | B2 |
7268667 | Beenau et al. | Sep 2007 | B2 |
7268668 | Beenau et al. | Sep 2007 | B2 |
7298266 | Forster | Nov 2007 | B2 |
7333062 | Leizerovich et al. | Feb 2008 | B2 |
7344072 | Gonzalez et al. | Mar 2008 | B2 |
7346061 | Takayama et al. | Mar 2008 | B2 |
7349355 | Sengupta et al. | Mar 2008 | B2 |
7357239 | Schwarzli et al. | Apr 2008 | B2 |
7366552 | Khoo | Apr 2008 | B2 |
7375616 | Rowse et al. | May 2008 | B2 |
7379778 | Hayes et al. | May 2008 | B2 |
7392061 | Hurwitz et al. | Jun 2008 | B2 |
7408887 | Sengupta et al. | Aug 2008 | B2 |
7409231 | Oba et al. | Aug 2008 | B2 |
7412224 | Kotola et al. | Aug 2008 | B2 |
7413124 | Frank et al. | Aug 2008 | B2 |
7420466 | Shafer | Sep 2008 | B2 |
7427926 | Sinclair et al. | Sep 2008 | B2 |
7455218 | Shafer | Nov 2008 | B2 |
7463133 | Bonalle et al. | Dec 2008 | B2 |
7468702 | Leizerovich et al. | Dec 2008 | B2 |
7469151 | Khan et al. | Dec 2008 | B2 |
7471200 | Otranen | Dec 2008 | B2 |
7484664 | Shafer | Feb 2009 | B2 |
7499985 | Linjama et al. | Mar 2009 | B2 |
7500750 | Sabeta | Mar 2009 | B2 |
7512567 | Bemmel et al. | Mar 2009 | B2 |
7519325 | Wakim | Apr 2009 | B2 |
7522879 | Matsuo et al. | Apr 2009 | B2 |
7522882 | Shibuya | Apr 2009 | B2 |
7523242 | Lee et al. | Apr 2009 | B2 |
7535361 | Doan et al. | May 2009 | B2 |
7537169 | Gonzalez et al. | May 2009 | B2 |
7540408 | Levine et al. | Jun 2009 | B2 |
7541930 | Saarisalo et al. | Jun 2009 | B2 |
7548203 | Kalliola et al. | Jun 2009 | B2 |
7565108 | Kotola et al. | Jul 2009 | B2 |
7567828 | Burson | Jul 2009 | B1 |
7570164 | Chakraborty et al. | Aug 2009 | B2 |
7580898 | Brown et al. | Aug 2009 | B2 |
7584153 | Brown et al. | Sep 2009 | B2 |
7586398 | Huang et al. | Sep 2009 | B2 |
7590384 | Dawidowsky | Sep 2009 | B2 |
7590409 | Morita | Sep 2009 | B2 |
7597250 | Finn | Oct 2009 | B2 |
7606533 | Perttila et al. | Oct 2009 | B2 |
7606560 | Labrou et al. | Oct 2009 | B2 |
7616095 | Jones et al. | Nov 2009 | B2 |
7616117 | Streeb et al. | Nov 2009 | B2 |
7623295 | Sabeta | Nov 2009 | B2 |
7646297 | Aaron | Jan 2010 | B2 |
7646316 | Khoo | Jan 2010 | B2 |
7647024 | Wang et al. | Jan 2010 | B2 |
7651535 | Plos | Jan 2010 | B2 |
7652578 | Braun et al. | Jan 2010 | B2 |
7653397 | Pernu et al. | Jan 2010 | B2 |
7657255 | Abel et al. | Feb 2010 | B2 |
7657286 | Kasslin et al. | Feb 2010 | B2 |
7657463 | Shaw et al. | Feb 2010 | B1 |
7664532 | Palin et al. | Feb 2010 | B2 |
7667646 | Kalliola et al. | Feb 2010 | B2 |
7668560 | Brothers | Feb 2010 | B2 |
7668565 | Ylanen et al. | Feb 2010 | B2 |
7668785 | Hammad | Feb 2010 | B1 |
7672297 | Naqvi et al. | Mar 2010 | B2 |
7680691 | Kimball et al. | Mar 2010 | B2 |
7683781 | Kantrowitz et al. | Mar 2010 | B2 |
7688181 | Cargonja et al. | Mar 2010 | B2 |
7688208 | Schuler et al. | Mar 2010 | B2 |
7688270 | Tsushima | Mar 2010 | B2 |
7693229 | Feher | Apr 2010 | B2 |
7693486 | Kasslin et al. | Apr 2010 | B2 |
7702282 | Sandegard et al. | Apr 2010 | B2 |
7702538 | Rau et al. | Apr 2010 | B2 |
7702754 | Dreiling | Apr 2010 | B2 |
7703691 | Patel et al. | Apr 2010 | B2 |
7708194 | Vawter | May 2010 | B2 |
7708401 | Sabeta | May 2010 | B2 |
7711373 | Kasslin et al. | May 2010 | B2 |
7716935 | Kim et al. | May 2010 | B2 |
7724753 | Naqvi et al. | May 2010 | B2 |
7725077 | Jung et al. | May 2010 | B2 |
7729689 | Chakraborty et al. | Jun 2010 | B2 |
7729722 | Rofougaran et al. | Jun 2010 | B2 |
7729776 | Von Arx et al. | Jun 2010 | B2 |
7734299 | Panabaker et al. | Jun 2010 | B2 |
7734307 | Dawidowsky | Jun 2010 | B2 |
7735740 | Shafer | Jun 2010 | B2 |
7738494 | Takayama | Jun 2010 | B2 |
7738569 | Quinn et al. | Jun 2010 | B2 |
7738964 | Von Arx et al. | Jun 2010 | B2 |
7739169 | Hammad | Jun 2010 | B2 |
7743409 | Gonzalez et al. | Jun 2010 | B2 |
7746215 | Bishop | Jun 2010 | B1 |
7747797 | Abraham et al. | Jun 2010 | B2 |
7748031 | Gonzalez et al. | Jun 2010 | B2 |
7748618 | Vawter | Jul 2010 | B2 |
7748636 | Finn | Jul 2010 | B2 |
7750811 | Puzio et al. | Jul 2010 | B2 |
7756467 | Bent et al. | Jul 2010 | B2 |
7775432 | Jalkanen et al. | Aug 2010 | B2 |
7953402 | Carolan et al. | May 2011 | B2 |
7978082 | Braunstein | Jul 2011 | B2 |
20020008140 | Reynolds et al. | Jan 2002 | A1 |
20020167393 | Mabuchi et al. | Nov 2002 | A1 |
20020180588 | Erickson et al. | Dec 2002 | A1 |
20040070491 | Huang et al. | Apr 2004 | A1 |
20040186768 | Wakim et al. | Sep 2004 | A1 |
20040228460 | Keramane | Nov 2004 | A1 |
20060202803 | Yoon et al. | Sep 2006 | A1 |
20060279409 | Yang et al. | Dec 2006 | A1 |
20060293069 | Patel et al. | Dec 2006 | A1 |
20070032261 | Boyer et al. | Feb 2007 | A1 |
20070046434 | Chakraborty | Mar 2007 | A1 |
20070103303 | Shoarinejad | May 2007 | A1 |
20070296552 | Huang et al. | Dec 2007 | A1 |
20070296581 | Schnee et al. | Dec 2007 | A1 |
20080014966 | Chakraborty et al. | Jan 2008 | A1 |
20080057876 | Hsia et al. | Mar 2008 | A1 |
20080068131 | Cargonja et al. | Mar 2008 | A1 |
20080074263 | Rofougaran | Mar 2008 | A1 |
20080079549 | Yamada et al. | Apr 2008 | A1 |
20080094215 | Amador et al. | Apr 2008 | A1 |
20080129458 | Twitchell | Jun 2008 | A1 |
20080160984 | Benes et al. | Jul 2008 | A1 |
20090028334 | Balabine et al. | Jan 2009 | A1 |
20090066484 | Mochizuki et al. | Mar 2009 | A1 |
20100078471 | Lin et al. | Apr 2010 | A1 |
20100078472 | Lin et al. | Apr 2010 | A1 |
20100078475 | Lin et al. | Apr 2010 | A1 |
20100081375 | Rosenblatt et al. | Apr 2010 | A1 |
20100081385 | Lin et al. | Apr 2010 | A1 |
20100082444 | Lin et al. | Apr 2010 | A1 |
20100082445 | Hodge et al. | Apr 2010 | A1 |
20100082448 | Lin et al. | Apr 2010 | A1 |
20100082481 | Lin et al. | Apr 2010 | A1 |
20100082485 | Lin et al. | Apr 2010 | A1 |
20100082489 | Lin et al. | Apr 2010 | A1 |
20100082784 | Rosenblatt et al. | Apr 2010 | A1 |
20100099354 | Johnson | Apr 2010 | A1 |
20100174599 | Rosenblatt et al. | Jul 2010 | A1 |
20100179857 | Kalaboukis et al. | Jul 2010 | A1 |
20100187307 | Phillips et al. | Jul 2010 | A1 |
20110070837 | Griffin et al. | Mar 2011 | A1 |
20110162035 | King et al. | Jun 2011 | A1 |
Number | Date | Country |
---|---|---|
1314299 | Nov 2004 | EP |
1501038 | Jan 2005 | EP |
1569386 | Aug 2005 | EP |
1575183 | Sep 2005 | EP |
1630712 | Mar 2006 | EP |
1653632 | May 2006 | EP |
1657944 | May 2006 | EP |
1681778 | Jul 2006 | EP |
1708405 | Oct 2006 | EP |
1717963 | Nov 2006 | EP |
1722310 | Nov 2006 | EP |
1752915 | Feb 2007 | EP |
1773080 | Apr 2007 | EP |
1793531 | Jun 2007 | EP |
1804475 | Jul 2007 | EP |
1814239 | Aug 2007 | EP |
1841178 | Oct 2007 | EP |
1845632 | Oct 2007 | EP |
1845694 | Oct 2007 | EP |
1855230 | Nov 2007 | EP |
1855483 | Nov 2007 | EP |
1860586 | Nov 2007 | EP |
1871135 | Dec 2007 | EP |
1887459 | Feb 2008 | EP |
1887460 | Feb 2008 | EP |
1895443 | Mar 2008 | EP |
1901086 | Mar 2008 | EP |
1901203 | Mar 2008 | EP |
1912180 | Apr 2008 | EP |
1912339 | Apr 2008 | EP |
1914631 | Apr 2008 | EP |
1916810 | Apr 2008 | EP |
1954008 | Aug 2008 | EP |
1959332 | Aug 2008 | EP |
1959619 | Aug 2008 | EP |
1965522 | Sep 2008 | EP |
1968266 | Sep 2008 | EP |
1976055 | Oct 2008 | EP |
1978665 | Oct 2008 | EP |
1983491 | Oct 2008 | EP |
1986340 | Oct 2008 | EP |
1986395 | Oct 2008 | EP |
1990942 | Nov 2008 | EP |
1995668 | Nov 2008 | EP |
2003573 | Dec 2008 | EP |
2018000 | Jan 2009 | EP |
2018017 | Jan 2009 | EP |
2023675 | Feb 2009 | EP |
2034428 | Mar 2009 | EP |
2043070 | Apr 2009 | EP |
2051179 | Apr 2009 | EP |
2056246 | May 2009 | EP |
2056261 | May 2009 | EP |
2065728 | Jun 2009 | EP |
2073183 | Jun 2009 | EP |
2075921 | Jul 2009 | EP |
2077518 | Jul 2009 | EP |
2077652 | Jul 2009 | EP |
2088748 | Aug 2009 | EP |
1897231 | Sep 2009 | EP |
2009139 | Sep 2009 | EP |
2096591 | Sep 2009 | EP |
2098955 | Sep 2009 | EP |
2104049 | Sep 2009 | EP |
2105904 | Sep 2009 | EP |
2106107 | Sep 2009 | EP |
2106108 | Sep 2009 | EP |
1787139 | Oct 2009 | EP |
2063378 | Nov 2009 | EP |
2120109 | Nov 2009 | EP |
2120111 | Nov 2009 | EP |
2120113 | Nov 2009 | EP |
2120114 | Nov 2009 | EP |
2120115 | Nov 2009 | EP |
2120116 | Nov 2009 | EP |
2124146 | Nov 2009 | EP |
2128830 | Dec 2009 | EP |
2161630 | Mar 2010 | EP |
2161901 | Mar 2010 | EP |
2164014 | Mar 2010 | EP |
2169924 | Mar 2010 | EP |
1829303 | Apr 2010 | EP |
2173135 | Apr 2010 | EP |
2180390 | Apr 2010 | EP |
2192753 | Jun 2010 | EP |
2192810 | Jun 2010 | EP |
2194472 | Jun 2010 | EP |
2196968 | Jun 2010 | EP |
2199996 | Jun 2010 | EP |
2207108 | Jul 2010 | EP |
1976231 | Oct 2010 | EP |
2004200840 | Jul 2004 | JP |
2004215225 | Jul 2004 | JP |
2004334453 | Nov 2004 | JP |
2005045557 | Feb 2005 | JP |
2005168069 | Jun 2005 | JP |
3695463 | Jul 2005 | JP |
3695465 | Jul 2005 | JP |
3695466 | Jul 2005 | JP |
2005204331 | Jul 2005 | JP |
2005210741 | Aug 2005 | JP |
2005218127 | Aug 2005 | JP |
2005159958 | Nov 2005 | JP |
2005332018 | Dec 2005 | JP |
2006074767 | Mar 2006 | JP |
2006121339 | May 2006 | JP |
2006211519 | Aug 2006 | JP |
2007081551 | Mar 2007 | JP |
2007081621 | Mar 2007 | JP |
2007150984 | Jun 2007 | JP |
2008134735 | Jun 2008 | JP |
2008165791 | Jul 2008 | JP |
2008252883 | Oct 2008 | JP |
2008259200 | Oct 2008 | JP |
2008262362 | Oct 2008 | JP |
2008294976 | Dec 2008 | JP |
2009038774 | Feb 2009 | JP |
2009064316 | Mar 2009 | JP |
2009100074 | May 2009 | JP |
2009134393 | Jun 2009 | JP |
2009147845 | Jul 2009 | JP |
2009182902 | Aug 2009 | JP |
2009237974 | Oct 2009 | JP |
2009238225 | Oct 2009 | JP |
2009239431 | Oct 2009 | JP |
2009239567 | Oct 2009 | JP |
2009260666 | Nov 2009 | JP |
2009290869 | Dec 2009 | JP |
2010011418 | Jan 2010 | JP |
2010011419 | Jan 2010 | JP |
2010011420 | Jan 2010 | JP |
2010020453 | Jan 2010 | JP |
2010049645 | Mar 2010 | JP |
2010055603 | Mar 2010 | JP |
2010056593 | Mar 2010 | JP |
2010068106 | Mar 2010 | JP |
WO9848396 | Oct 1998 | WO |
WO0113217 | Feb 2001 | WO |
WO2004077345 | Sep 2004 | WO |
WO2006023857 | Mar 2006 | WO |
WO2006027725 | Mar 2006 | WO |
WO2006035331 | Apr 2006 | WO |
WO2006053677 | May 2006 | WO |
WO2006085269 | Aug 2006 | WO |
WO2006086729 | Aug 2006 | WO |
WO2006095212 | Sep 2006 | WO |
WO2006097760 | Sep 2006 | WO |
WO2006100171 | Sep 2006 | WO |
WO2006102537 | Sep 2006 | WO |
WO2006111782 | Oct 2006 | WO |
WO2006138584 | Dec 2006 | WO |
WO2007002485 | Jan 2007 | WO |
WO2007012909 | Feb 2007 | WO |
WO2007017777 | Feb 2007 | WO |
WO2007020519 | Feb 2007 | WO |
WO2007034457 | Mar 2007 | WO |
WO2007037841 | Apr 2007 | WO |
WO2007046653 | Apr 2007 | WO |
WO2007048399 | May 2007 | WO |
WO2007052117 | May 2007 | WO |
WO2007060616 | May 2007 | WO |
WO2007068993 | Jun 2007 | WO |
WO2007076456 | Jul 2007 | WO |
WO2007082602 | Jul 2007 | WO |
WO2007082604 | Jul 2007 | WO |
WO2007082612 | Jul 2007 | WO |
WO2007099639 | Sep 2007 | WO |
WO2007101992 | Sep 2007 | WO |
WO2007104365 | Sep 2007 | WO |
WO2007112787 | Oct 2007 | WO |
WO2007121791 | Nov 2007 | WO |
WO2007122439 | Nov 2007 | WO |
WO2007124932 | Nov 2007 | WO |
WO2007124965 | Nov 2007 | WO |
WO2007127559 | Nov 2007 | WO |
WO2007129139 | Nov 2007 | WO |
WO2007146470 | Dec 2007 | WO |
WO2007147448 | Dec 2007 | WO |
WO2008005460 | Jan 2008 | WO |
WO2008005974 | Jan 2008 | WO |
WO2008007260 | Jan 2008 | WO |
WO2008009654 | Jan 2008 | WO |
WO2008014800 | Feb 2008 | WO |
WO2008021032 | Feb 2008 | WO |
WO2008026691 | Mar 2008 | WO |
WO2008027620 | Mar 2008 | WO |
WO2008027621 | Mar 2008 | WO |
WO2008031629 | Mar 2008 | WO |
WO2008033898 | Mar 2008 | WO |
WO2008034937 | Mar 2008 | WO |
WO2008039234 | Apr 2008 | WO |
WO2008039559 | Apr 2008 | WO |
WO2008039560 | Apr 2008 | WO |
WO2008042302 | Apr 2008 | WO |
WO2008042455 | Apr 2008 | WO |
WO2008045586 | Apr 2008 | WO |
WO2008048376 | Apr 2008 | WO |
WO2008065232 | Jun 2008 | WO |
WO2008067153 | Jun 2008 | WO |
WO2008082851 | Jul 2008 | WO |
WO2008087431 | Jul 2008 | WO |
WO2008087739 | Jul 2008 | WO |
WO2008098082 | Aug 2008 | WO |
WO2008103871 | Aug 2008 | WO |
WO2008103875 | Aug 2008 | WO |
WO2008103945 | Aug 2008 | WO |
WO2008103988 | Aug 2008 | WO |
WO2008103991 | Aug 2008 | WO |
WO2008113053 | Sep 2008 | WO |
WO2008127967 | Oct 2008 | WO |
WO2008128583 | Oct 2008 | WO |
WO2008147457 | Dec 2008 | WO |
WO2008147728 | Dec 2008 | WO |
WO2008152739 | Dec 2008 | WO |
WO2009002972 | Dec 2008 | WO |
WO2009003707 | Jan 2009 | WO |
WO2009013385 | Feb 2009 | WO |
WO2009018255 | Feb 2009 | WO |
WO2009021220 | Feb 2009 | WO |
WO2009026000 | Feb 2009 | WO |
WO2009036264 | Mar 2009 | WO |
WO2009039419 | Mar 2009 | WO |
WO2009045085 | Apr 2009 | WO |
WO2009057745 | May 2009 | WO |
WO2009058010 | May 2009 | WO |
WO2009058494 | May 2009 | WO |
WO2009059213 | May 2009 | WO |
WO2009062176 | May 2009 | WO |
WO2009063121 | May 2009 | WO |
WO2009064522 | May 2009 | WO |
WO2009069971 | Jun 2009 | WO |
WO2009069989 | Jun 2009 | WO |
WO2009071734 | Jun 2009 | WO |
WO2009076030 | Jun 2009 | WO |
WO2009079330 | Jun 2009 | WO |
WO2009079385 | Jun 2009 | WO |
WO2009081337 | Jul 2009 | WO |
WO2009095048 | Aug 2009 | WO |
WO2009097215 | Aug 2009 | WO |
WO2009098646 | Aug 2009 | WO |
WO2009101534 | Aug 2009 | WO |
WO2009105115 | Aug 2009 | WO |
WO2009111419 | Sep 2009 | WO |
WO2009115115 | Sep 2009 | WO |
WO2009124790 | Oct 2009 | WO |
WO2009127267 | Oct 2009 | WO |
WO2009128032 | Oct 2009 | WO |
WO2009130796 | Oct 2009 | WO |
WO2009138554 | Nov 2009 | WO |
WO2009138559 | Nov 2009 | WO |
WO2009141751 | Nov 2009 | WO |
WO2009141773 | Nov 2009 | WO |
WO2009141805 | Nov 2009 | WO |
WO2009173757 | Nov 2009 | WO |
WO2009148289 | Dec 2009 | WO |
WO2009151833 | Dec 2009 | WO |
WO2009152833 | Dec 2009 | WO |
WO2009158569 | Dec 2009 | WO |
WO2010000462 | Jan 2010 | WO |
WO2010002497 | Jan 2010 | WO |
WO2010005228 | Jan 2010 | WO |
WO2010011670 | Jan 2010 | WO |
WO2010012129 | Feb 2010 | WO |
WO2010015995 | Feb 2010 | WO |
WO2010017237 | Feb 2010 | WO |
WO2010018483 | Feb 2010 | WO |
WO2010018486 | Feb 2010 | WO |
WO2010019668 | Feb 2010 | WO |
WO2010022642 | Mar 2010 | WO |
WO2010023298 | Mar 2010 | WO |
WO2010025157 | Mar 2010 | WO |
WO2010029446 | Mar 2010 | WO |
WO2010030403 | Mar 2010 | WO |
WO2010030415 | Mar 2010 | WO |
WO2010033967 | Mar 2010 | WO |
WO2010033968 | Mar 2010 | WO |
WO2010035256 | Apr 2010 | WO |
WO2010037218 | Apr 2010 | WO |
WO2010042560 | Apr 2010 | WO |
WO2010042977 | Apr 2010 | WO |
WO2010044912 | Apr 2010 | WO |
WO2010047849 | Apr 2010 | WO |
WO2010011055 | May 2010 | WO |
WO2010057390 | May 2010 | WO |
WO2010060118 | May 2010 | WO |
WO2010062077 | Jun 2010 | WO |
WO2010067222 | Jun 2010 | WO |
WO2010068063 | Jun 2010 | WO |
WO2010070539 | Jun 2010 | WO |
WO2010073732 | Jul 2010 | WO |
WO2010078616 | Jul 2010 | WO |
Number | Date | Country | |
---|---|---|---|
61377728 | Aug 2010 | US |