Terminal, method and computer program product for interacting with a signaling tag
A terminal for interacting with a signaling tag includes a controller capable of receiving information regarding a signaling tag at least partially over an air interface. The controller is also capable of determining whether the controller is actively operating an application. In this regard, if the terminal is actively operating an application, the controller is capable of performing a predefined action based upon the application and a state of the application.
Latest NOKIA TECHNOLOGIES OY Patents:
This application is a reissue of U.S. Pat. No. 7,775,432, titled “Terminal, Method and Computer Program Product for Interacting with a Signaling Tag,” issued Aug. 17, 2010, which is hereby incorporated by reference herein in its entirety.
FIELD OF THE INVENTIONThe present invention generally relates to systems and methods of interacting with entities and, more particularly, relates to terminals, methods and computer program products for interacting in a short-range environment to perform actions based on applications capable of operating on the terminal.
BACKGROUND OF THE INVENTIONComputer science researchers have been exploring ideas associated with “smart spaces” or ubiquitous computing for years. One of the most important challenges has been creating new, intuitive user interfaces that are suitable for ubiquitous computing applications, but are not based on traditional personal computing platforms. The challenge is to make these new devices and applications simple and intuitive to use. Donald Norman describes some of the challenges in designing such a user interface in the book, T
In an attempt to address the design challenges of user interfaces suitable for ubiquitous computing applications, there has been significant work in the area of point-and-click user interfaces and the application of point-and-click ideas to ubiquitous computing research. Traditional infrared (IR) remote controls are an obvious example. In this regard, IR remote controls are being developed today to allow users to control a number of different entities from a single controller. Another example of the application of point-and-click ideas to ubiquitous computing research is the “Cooltown” research project within Hewlett-Packard Laboratories. Generally, in accordance with the Cooltown research project, users can interact with entities using wireless communication devices to execute uniform resource locators (URLs) to web resources such that the wireless communication device can thereafter interact with the web resources.
Whereas previous real-world point-and-click techniques allow users to interact with entities in a predetermined manner, such as to control the entity or link to web resources, such techniques are inflexible. In this regard, most systems employing such techniques are single purpose devices. For example. Cooltown uses wireless communication devices to achieve limited, multi-application, point and click functionality. Cooltown protocols are used to send and receive URLs and these URLs are assumed to point to HTML documents. Cooltown can be thought of as a sort of real-world, web browsing system. The flexibility of this approach is limited, however, because it is based on URLs that only point to web resources.
SUMMARY OF THE INVENTIONIn light of the foregoing background, embodiments of the present invention provide an improved terminal, method and computer program product for interacting with signaling tags, such as Radio Frequency Identification (RFID) transponder tags, radio frequency transponders operating as RFID transponder tags, or the like. Embodiments of the present invention create a “point-and-click” style of user interface for ubiquitous computing applications that is based on the use of a terminal, such as a mobile station or portable digital assistant (PDA). Generally, embodiments of the present invention permit terminal users to use a terminal to select electronic tags from which the terminal can read data and/or to which the terminal can write data. Based upon a tag type indicating the tag as being capable of transmitting and/or receiving data, the terminal can perform predefined actions. Advantageously, the terminal can be capable of actively operating an application, such as a software application, and as such, the terminal can be capable of performing the predefined action further based upon the application and the state of the application, such as being in a state of receiving or presenting data.
As indicated above, a signaling tag can comprise a transceiver capable of operating as an electronic tag, where the transceiver is associated with an electronic device. In such instances, the terminal can perform predefined actions such as by reading data from and/or writing data to the electronic device associated with the transceiver. Instead of reading data from and/or writing data to the associated device via the transceiver, the terminal can advantageously be capable of reading data from and/or writing data to the associated device in a manner independent of the transceiver. For example, when the transceiver comprises a radio frequency transceiver, the terminal can be capable of reading data from and/or writing data to the associated device in a manner such as in accordance with infrared, Bluetooth, or any of a number of different wireless networking techniques, including WLAN techniques.
According to one aspect of the present invention. a terminal is provided for interacting with a signaling tag. The terminal includes a controller capable of receiving information regarding a signaling tag, such as a Radio Frequency Identification (RFID) transponder tag, at least partially over an air interface. The controller is also capable of determining whether the terminal is actively operating an application. In this regard, if the terminal is actively operating an application, the controller is capable of performing a predefined action based upon the application and the state of the application. More particularly, the controller can be capable of reading data from the signaling tag into an actively operating application when (a) the information regarding the signaling tag indicates that the signaling tag is capable of at least transmitting data to the terminal (e.g., tag types “Read Only,” “Read/Write”), (b) the controller is actively operating an application. and (c) the application is in a state of receiving data.
The controller can be further capable of selecting a signaling tag before receiving information regarding the signaling tag. In such instances, the signaling tag can comprise a RFID transponder tag. In this regard, the terminal can also include a transceiver such that the controller is capable of selecting a signaling tag by the transceiver being passed within a predefined distance of a signaling tag. After selecting the signaling tag, the controller can then be capable of receiving the information regarding the signaling tag. For example, the controller can be capable of sending an interrogation signal to the RFID transponder tag. In response to the interrogation signal, then, the terminal can receive information regarding a signaling tag comprising a tag type. Alternatively for example, the terminal can be capable of sending at least one interrogation signal to the RFID transponder tag, where each interrogation signal is associated with a different tag type. The terminal can receive a response from the RFID transponder tag to one of the interrogation signal(s) that triggers the response. Then, the terminal can be capable of identifying a tag type based upon the interrogation signal that triggers the response, where the information regarding a signaling tag comprises the identified tag type.
Irrespective of how the terminal receives the information regarding the signaling tag, when the information regarding the signaling tag indicates that the signaling tag is capable of at least transmitting data to the terminal (e.g., tag types “Read Only,” “Read/Write”) and either (a) the controller is not actively operating an application, or (b) the controller is actively operating an application in a state other than a state of receiving data, the controller can be capable of reading data from the signaling tag into the terminal, such as to store the data into the terminal. The controller can be capable of writing data to the signaling tag when (a) the information regarding the signaling tag indicates that the signaling tag is capable of at least receiving data from the terminal (e.g., tag type “Read/Write”), (b) the controller is actively operating an application, and (c) the application is in a state of presenting data. However, when the information regarding the signaling tag indicates that the signaling tag is capable of at least transmitting data to the terminal (e.g., tag type “Read/Write”) and either (a) the controller is not actively operating an application, or (b) the controller is actively operating an application in a state other than a state of one of receiving data and presenting data, the controller can be capable of reading data from the signaling tag into the terminal.
In various instances, the signaling tag comprises a transceiver capable of operating as an electronic tag, such as an RFID transponder tag, where the transceiver is associated with a device. In such instances, when (a) the information regarding the signaling tag indicates that the transceiver is capable of at least transmitting data, (b) the controller is actively operating an application, and (c) the application is in a state of receiving data, the controller can be capable of reading data from a device associated with a transceiver into the actively operating application. The controller can be capable of writing data to the device associated with the transceiver when (a) the information regarding the signaling tag indicates that the transceiver is capable of at least receiving data, (b) the controller is actively operating an application, and (c) the application is in a state of presenting data. Advantageously, the controller can be capable of reading data from and/or writing data to the device in a manner independent of the transceiver. In such instances, the controller can be capable of receiving at least one connection parameter from the device via the transceiver, and thereafter reading data from and/or writing data to the device based upon the connection parameter(s) and in a manner independent of the transceiver.
In instances in which the information regarding the signaling tag indicates that the transceiver is capable of at least transmitting data and either (a) the controller is not actively operating an application, or (b) the controller is actively operating an application in a state other than a state of one of receiving data and presenting data, the controller can be capable of initiating communication with the device associated with the transceiver. Advantageously, in a manner similar to reading data from and/or writing data to the device, the controller can be capable of initiating communication with the device in a manner independent of the transceiver.
A method and computer program product for interacting with a signaling tag are also provided. Embodiments of the present invention therefore provide a terminal, method and computer program product for interacting with signaling tags, such as RFID transponder tags and/or radio frequency transceivers. In contrast to conventional computing systems, embodiments of the present invention allow the terminal to perform different predefined actions, such as reading data to and/or writing data from the signaling tag or a device associated with a signaling tag comprising a transceiver, by selecting different signaling tags. As such, the terminal, method and computer program product of embodiments of the present invention solve the problems identified by prior techniques and provide additional advantages.
Having thus described the invention in general terms, reference will now be made to the accompanying drawings, which are not necessarily drawn to scale, and wherein:
FIG. 4 is a flowchart illustrating various steps in a method of interacting with a signaling tag in accordance with one embodiment of the present invention.
The present invention now will be described more fully hereinafter with reference to the accompanying drawings, in which preferred embodiments of the invention are shown. This invention may, however, be embodied in many different forms and should not be construed as limited to the embodiments set forth herein; rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the invention to those skilled in the art. Like numbers refer to like elements throughout.
Referring to
As shown, a terminal 10 may include an antenna 12 for transmitting signals to and for receiving signals from a base site or base station (BS) 14. The base station is a part of a cellular network that includes elements required to operate the network, such as a mobile switching center (MSC) 16. As well known to those skilled in the art, the cellular network may also be referred to as a Base Station/MSC/Interworking function (BMI) 18. In operation, the MSC is capable of routing calls and messages to and from the terminal when the terminal is making and receiving calls. The MSC also provides a connection to landline trunks when the terminal is involved in a call. Further, the MSC can, but need not, be coupled to a server GTW 20 (Gateway).
The MSC 16 can be coupled to a network, such as a local area network (LAN), a metropolitan area network (MAN), and/or a wide area network (WAN). The MSC can be coupled to the network directly, or if the system includes a GTW 20 (as shown), the MSC can be coupled to the network via the GTW. In one typical embodiment, for example, the MSC is coupled to the GTW, and the GTW is coupled to a WAN, such as the Internet 22. In turn, devices such as processing elements (e.g., personal computers, server computers or the like) can be coupled to the terminal 10 via the Internet. For example, the processing elements can include one or more processing elements associated with an origin server 24. Additionally, the network may be coupled to one or more wireless access points (APs) 26, which may be wirelessly coupled to one or more terminals 10. By directly or indirectly connecting the terminals and the other devices (e.g., origin server) to the Internet, the terminals can communicate with the other devices and with one another, such as according to the Hypertext Transfer Protocol (HTTP), to thereby carry out various functions of the terminal.
Reference is now made to
As shown, in addition to an antenna 12, the mobile station includes a transmitter 28, a receiver 30, and a controller 32 that provides signals to and receives signals from the transmitter and receiver, respectively. These signals include signaling information in accordance with the air interface standard of the applicable cellular system, and also user speech and/or user generated data. In this regard, the mobile station can be capable of operating with one or more air interface standards, communication protocols, modulation types, and access types. More particularly, the mobile station can be capable of operating in accordance with any of a number of first generation (1G), second generation (2G), 2.5G and/or third-generation (3G) communication protocols or the like. For example, the mobile station may be capable of operating in accordance with 2G wireless communication protocols IS-136 (TDMA), GSM, and IS-95 (CDMA). Some narrow-band AMPS (NAMPS), as well as TACS, mobile terminals may also benefit from the teaching of thi s invention, as should dual or higher mode phones (e.g., digital/analog or TDMA/CDMA/analog phones).
It is understood that the controller 32 includes the circuitry required for implementing the audio and logic functions of the mobile station. For example. the controller may be comprised of a digital signal processor device, a microprocessor device, and various analog-to-digital converters, digital-to-analog converters, and other support circuits. The control and signal processing functions of the mobile station are allocated between these devices according to their respective capabilities. The controller can additionally include an internal voice coder (VC) 32A, and may include an internal data modem (DM) 32B. Further. the controller may include the functionally to operate one or more software programs, which may be stored in memory (described below). For example, the controller may be capable of operating a connectivity program, such as a conventional Web browser. The connectivity program may then allow the mobile station to transmit and receive Web content, such as according to the Hypertext Transfer Protocol (HTTP) and/or the Wireless Application Protocol (WAP), for example.
The mobile station also comprises a user interface including a conventional earphone or speaker 34, a ringer 36, a microphone 38, a display 40, and a user input interface, all of which are coupled to the controller 32. The user input interface. which allows the mobile station to receive data, can comprise any of a number of devices allowing the mobile station to receive data, such as a keypad 42, a touch display (not shown) or other input device. In embodiments including a keypad, the keypad includes the conventional numeric (0-9) and related keys (#, *), and other keys used for operating the mobile station. Although not shown, the mobile station can include a battery, such as a vibrating battery pack, for powering the various circuits that are required to operate the mobile station, as well as optionally providing mechanical vibration as a detectable output.
The mobile station can also include one or more means for sharing and/or obtaining data from electronic devices 44, tags 46 or the like. As will be appreciated, the electronic devices and tags can comprise any of a number of different known devices and tags capable of transmitting and/or receiving data in accordance with any of a number of different wireline and/or wireless techniques. For example, the electronic devices can comprise any of a number of different terminals 10, including other mobile stations, portable digital assistants (PDAs), pagers, laptop computers and other types of electronic systems. Likewise, for example, the tags can comprise Radio Frequency Identification (RFID) transponder tags or the like.
As shown in
The mobile station can further include memory, such as a subscriber identity module (SIM) 54, a removable user identity module (R-UIM) or the like, which typically stores information elements related to a mobile subscriber. In addition to the SIM, the mobile station can include other removable and/or fixed memory. In this regard, the mobile station can include volatile memory 56, such as volatile Random Access Memory (RAM) including a cache area for the temporary storage of data. The mobile station can also include other non-volatile memory 58. which can be embedded and/or may be removable. The non-volatile memory can additionally or alternatively comprise an EEPROM, flash memory or the like. The memories can store any of a number of pieces of information, and data, used by the mobile station to implement the functions of the mobile station. The memories can also store one or more applications capable of operating on the mobile station.
The applications capable of operating on the mobile station can comprise any of a number of different applications capable of being executed by the controller 32. For example, the applications can include a printing application capable of directing a printer to print an image. Also, for example, the applications can include a payment application capable of transferring funds, such as credit card funds, to an entity capable of receiving the funds. In addition, for example, the applications can include one or more messaging applications, such as an E-mail application, short messaging service (SMS), multimedia messaging service (MMS) application or the like, capable of sending and receiving messages that may include text, images, audio, video and/or other multimedia. The applications are typically embodied in software, but as will be appreciated, one or more applications can alternatively be embodied in firmware, hardware or the like.
In accordance with embodiments of the present invention, the terminal 10 is capable of reading a tag type from a tag 46, and thereafter performing a predefined action based upon the tag type and a state of the terminal. Each tag can have any of a number of different tag types. For example, one or more tags can have the tag type, “Read Only,” which designates the respective tag(s) as only being capable of transmitting data to the terminal during operation the method of embodiments of the present invention. Also, for example, one or more tags can have the tag type, “Read/Write,” which designates the respective tag(s) as being capable of transmitting data to and/or receiving data from the terminal during operation the method of embodiments of the present invention. In addition, one or more transceivers 49 (e.g., one or more radio frequency transceivers) of one or more other electronic devices 44 may each be capable of operating as a tag during operation of the method of embodiments of the present invention. For more information on such transceivers, see PCT Patent Application PCT/IB03/02900, entitled: Reader Device for Radio Frequency Identification Transponder with Transponder Functionality, filed on Jul. 22, 2003, the contents of which are hereby incorporated by reference in its entirety.
In instances in which one or more transceivers 49 operate as a tag, each transceiver operating as a tag can have the tag type “Transceiver in Show Mode,” which designates the respective transceiver as being capable of operating as a tag, typically havipg a “Read Only” tag type. It should be understood, however, that the tag type “Transceiver in Show Mode,” tag type can designate the respective transceiver as being capable of functionally operating as a tag having a “Read/Write” tag type. As described herein, the term signaling tag can refer to a tag 46 or a transceiver 49 capable of functionally operating as a tag during operation of embodiments of the present invention.
Attention is now drawn to
After selecting the signaling tag, the terminal 10 can receive a tag type from the signaling tag, as shown in block 62. The terminal can receive the tag type in any of a number of different manners, such as via radio frequency transfer from an RFID transponder tag or a radio frequency transceiver. The terminal can directly receive the tag type from the signaling tag. Alternatively, the terminal can indirectly receive the tag type based upon the signaling tag responding to an interrogation signal from the transceiver 48. In such instances, the transceiver may send one or more interrogation signals to the signaling tag, with each interrogation signal associated with a different tag type. The signaling tag, then, can be configured to only respond to a particular interrogation signal. As the transceiver sends each interrogation signal to the signaling tag, the transceiver can monitor for a response from the signaling tag. When the signaling tag responds to an interrogation signal, then, the transceiver can identify the tag type associated with the respective interrogation signal as the tag type of the signaling tag.
Irrespective of how the terminal 10 receives the tag type, after receiving the tag type, the terminal can perform a predefined action based upon the tag type and a state of the terminal. In this regard, if the signaling tag has a tag type “Read Only” and the terminal is actively operating an application in a state of receiving data, as shown in blocks 64 and 66 of
As an example of a context in which a signaling tag may have “Read Only” tag type, presume that a RFID transponder tag is embedded in a paper advertisement for a consumer good, where the tag has a tag type “Read Only” and stores data including information regarding the consumer good, such as a description of the consumer good and a uniform resource locator (URL) to a Web site that includes an order form for ordering the consumer good. Also, presume that the data stored by the tag identifies an E-mail application as being associated with the data. If the terminal is actively operating an E-mail application, upon selecting the tag, the terminal can read the information regarding the consumer good into an E-mail composition such that a user of the terminal can E-mail the information to a friend. Alternatively, if the terminal is actively operating a Web browser, the terminal can read the URL from the information and retrieve the Web site that includes the order form for ordering the consumer good. If the terminal is not actively operating an application. however, the terminal can read the data stored by the RFID transponder tag and store the information regarding the consumer good, such as until subsequent initiation of the E-mail application, at which point in time the stored data may be provided to the application. Additionally, or alternatively, the terminal can read the data, execute an E-mail application identified by the data. and as before. read the information regarding the consumer good into an E-mail composition.
Again referring to
As an example of a context in which a signaling tag may have “Read/Write” tag type, presume that a RFID transponder tag with such a “Read/Write” tag type is embedded in the same paper advertisement as above, except that the data stored by the REID transponder tag identifies an organizer application presenting user contact information as being associated with the data. Also, presume that the paper advertisement indicates that customers interested in receiving more information regarding the consumer good can leave their contact information at the advertisement. If the terminal 10 is actively operating an E-mail application, and the E-mail application is in a state of receiving information into a composition, the terminal can read the information regarding the consumer good into the E-mail composition, as before. Also as before, if the terminal is actively operating a Web browser, and the Web browser is in a state of receiving a URL, the terminal can read the URL from the information and retrieve the Web site.
If the user of the terminal 10 desires to leave contact information (e.g., mailing address) to receive more information regarding the consumer good, and if the terminal is actively operating an organizer application that presents user contact information, the contact information can be written to the RFID transponder tag. Subsequently, then, the contact information can be retrieved, such as by a distributor of the consumer good, and information regarding the consumer good sent to the user based upon the contact information. If. on the other hand, the terminal is not actively operating an application, the terminal can read the data stored by the RFID transponder tag, and store the information regarding the consumer good. Additionally, or alternatively, the terminal can read the data, execute an organizer application identified by the data, and as before, write the user's contact information to the tag.
As described herein, when the signaling tag has a tag type “Read Only” or “Read/Write,” terminal 10 typically reads the data from the tag and acts upon the data when the terminal does not have an active application operating on the terminal. It should be understood, however, that when the terminal does not have an active application operating on the terminal, the terminal need not read data from the tag or act upon the data. In this regard, the terminal can be configured to read data from the tag only when an active application is operating on the terminal.
As explained above, a transceiver 49 can be capable of operating as a tag 46, with the transceiver having a tag type “Transceiver in Show Mode.” Thus, if the signaling tag has a tag type “Transceiver in Show Mode,” as shown in block 84, and if the terminal 10 is actively operating an application, the terminal can perform an action further based upon a state of the active application operating on the terminal. In this regard, the terminal operates when the tag type is “Transceiver in Show Mode” much like the terminal operates when the tag type is “Read/Write.” In contrast to operation when the tag type is “Read/Write,” however, a transceiver operating as a tag typically does not itself store data as does a transponder tag generally. Thus, in contrast to operating the terminal when the tag type is “Read/Write,” when the tag type is “Transceiver in Show Mode” the terminal typically transmits data to and/or receives data from the electronic device 44 associated with the transceiver, as opposed from the transceiver itself.
The data transmitted to and/or received from the electronic device 44 associated with the transceiver 49 can be determined in any of a number of different manners. In one advantageous embodiment, the data transmitted to and/or received from the electronic device associated with the transceiver can be determined based upon an application actively operating on the terminal and/or the electronic device. In this regard, the data transmitted to the electronic device can be determined based upon data presented by an application actively operating on the terminal 10. Also, data received from the electronic device and the manner in which the data is handled can be determined based upon an application actively operating on the electronic device, or based upon data requested by the application actively operating on the terminal. For example, when the electronic device is actively operating an organizer application that presents contact information, the data received from the electronic device can comprise the contact information presented by the organizer application. Further, the data received from the electronic device can comprise default data, such as data stored in a “digital clipboard,” as such is well known to those skilled in the art.
Generally, then, in various instances, data is transmitted to and/or received from a tag 46 or electronic device 44 associated with the transceiver 49 operating as a tag, and the terminal 10 and/or the electronic device are actively operating an application. In such instances, selecting the signaling tag generally expresses an intent to transmit and/or receive data relating to one or more of the actively operating application (s). More particularly, selecting a tag or transceiver operating as a tag when the terminal is actively operating an application can express an intent of the terminal to transmit data from and/or receive data into the actively operating application. Similarly, selecting a transceiver operating as a tag when the associated electronic device is actively operating an application can express an intent of the terminal to transmit data into and/or received data from the actively operating application.
Also, whereas the terminal 10 can transmit and/or receive data from the electronic device 44 via the transceiver 49, the terminal typically transmits and/or receives the data from the electronic device via another means for sharing and/or obtaining data from the electronic device. In this regard, the terminal can communicate with the electronic device via the transceiver to receive one or more connection parameters for another means for sharing and/or obtaining data from the electronic device. Thereafter. the terminal can transmit and/or receive data from the electronic device vie the other means for sharing and/or obtaining data based upon the connection parameters. For example, the terminal can communicate with the electronic device via the transceiver to transmit and receive connection parameters for an infrared, Bluetooth or another wireless networking connection. Then, the terminal can transmit and/or receive data from the other electronic device via a infrared, Bluetooth, or any of a number of different wireless networking techniques, including WLAN techniques such as IEEE 802.11 techniques or the like. Thus, in one typical embodiment, the terminal can receive a tag type (“Transceiver in Show Mode”) from the transceiver, and can also receive one or more connection parameters required for establishing communication with the electronic device associated with the transceiver. Then, the terminal can transmit data to and/or receive data from the electronic device via a infrared, Bluetooth, WLAN or the like.
In operation, then, when the signaling tag has a tag type “Transceiver in Show Mode,” and if the terminal 10 has an active application operating in a state for receiving data, such as into a text field, the terminal can communicate with the electronic device 44 associated with the transceiver 49 (i.e., signaling tag) to receive data from the electronic device (via, e.g., infrared. Bluetooth, and/or WLAN from an active application operating on the electronic device) into the active application, as shown in blocks 86 and 88. If the active application is in a state of presenting data, such as a selected E-mail message, however, the terminal can communicate with the electronic device associated with the transceiver to send the presented data to the electronic device (via, e.g., infrared, Bluetooth, and/or WLAN to an active application operating on the electronic device, to memory, etc.), as shown in blocks 90 and 92. I
If the signaling tag has a tag type “Transceiver in Show Mode,” and the terminal 10 is not actively operating an application, the terminal can initiate communication, such as via infrared, Bluetooth, and/or WLAN, with the electronic device associated with the transceiver, as shown in block 94. The user of the terminal can thereafter operate the terminal to communicate with the electronic device in any of a number of different manners, as desired. For example, the user of the terminal can operate the terminal to transfer files, applications or the like between the terminal and the electronic device.
As will be appreciated. data transmitted to the electronic device 44 from the terminal 10 can, upon receipt, be acted upon by the electronic device in any of a number of different manners. For example, the electronic device can read the data into an application actively operating on the electronic device. If the electronic device is not actively operating an application into which the data can be read, the terminal can execute an application associated with the data or otherwise identified by the data, and read the data into the executed application. In addition to, or in lieu of, reading data into an application, the electronic device can store the data.
As an example of a context in which a signaling tag may have “Transceiver in Show Mode” tag type, presume that a radio frequency transceiver with such a “Transceiver in Show Mode” tag type is associated with a mobile station. If an E-mail application is actively operating on the terminal 10, and the E-mail application is in a state of receiving information into a composition, the terminal can communicate with the mobile station to receive content into the E-mail composition, such as from an active application, “digital clipboard, or another source identified by the E-mail application. If, on the other hand, the terminal is actively operating a photo editing application presenting an image, the terminal can transmit the image to the mobile station. Upon receipt of the image, then, the mobile station can execute a photo editing application (if not already actively operating on the mobile station) and read the image into the photo editing application, and can store the image, if so desired. If the terminal is not actively operating an application, the terminal can initiate communication with the mobile station, after which the user of the terminal can operate the terminal to communicate with the mobile station, such as to transfer files, applications or the like between the terminal and the mobile station.
As described herein, upon reading a tag type from a signaling tag, the terminal 10 can perform a predefined action based upon the tag type, and if the terminal is actively operating an application, further based upon the application and a state of the application. More particularly, depending upon the tag type, the terminal can read data from the signaling tag into an actively operating application when the application is in a state of receiving data, and can write data to the signaling tag when the application is in a state of presenting data. It should be understood, however, that after the terminal receives the tag type, the terminal need not automatically perform the predefined action based upon the tag type and, if the terminal is actively operating an application, the application and state of the application. In this regard, the terminal can determine the tag type from the signaling tag and thereafter notify a user of the terminal (via e.g., user interface speaker 34, ringer 36 and/or display 40, and/or vibrating battery pack) that the terminal can perform one or more predefined actions based upon the tag type. Thereafter. the terminal can be responsive to a user selection to thereby perform a predefined action based upon the tag type and a user selection.
According to one aspect of the present invention, all or a portion of the system of the present invention, such all or portions of the terminal 14, generally operates under control of a computer program product. The computer program product for performing the methods of embodiments of the present invention includes a computer-readable storage medium, such as the non-volatile storage medium, and computer-readable program code portions, such as a series of computer instructions, embodied in the computer-readable storage medium.
In this regard,
Further, FIG. 4 is a flowchart of a method 100. In some embodiments, the method 100 can comprise: receiving information regarding a signaling tag at a terminal at least partially over an air interface via a short-range radio frequency transceiver or interrogator, the information regarding the signaling tag including at least a tag type of the signaling tag, at block 102. In some embodiments, the method 100 can further comprise: determining whether the terminal is actively operating an application, at block 104. In some embodiments, the method 100 can further comprise: if the terminal is actively operating an application, performing a first predefined action based upon the tag type, the application and a state of the application, wherein the first predefined action comprises: initiating communication between the terminal and a device associated with the signaling tag and transmitting data to the device associated with the signaling tag when the tag type indicates that the signaling tag is a radio frequency transceiver and the active application is in a state of presenting data, wherein said transmitting data to the device comprises transmitting the presented data to the device via infra-red, Bluetooth or WLAN communication, at block 106. In some embodiments, the method 100 can further comprise: if the terminal is not actively operating an application, performing a second predefined action based upon the tag type, wherein the second predefined action comprises: reading data from the signaling tag and acting upon the received data when the tag type indicates that the signaling tag comprises a RFID transponder tag capable of at least transmitting data to the terminal, at block 108.
Accordingly, blocks or steps of the flowcharts support combinations of means for performing the specified functions, combinations of steps for performing the specified functions and program instruction means for performing the specified functions. It will also be understood that each block or step of the flowchart, and combinations of blocks or steps in the flowchart, can be implemented by special purpose hardware-based computer systems which perform the specified functions or steps, or combinations of special purpose hardware and computer instructions.
Many modifications and other embodiments of the invention will come to mind to one skilled in the art to which this invention pertains having the benefit of the teachings presented in the foregoing descriptions and the associated drawings. Therefore, it is to be understood that the invention is not to be limited to the specific embodiments disclosed and that modifications and other embodiments are intended to be included within the scope of the appended claims. Although specific terms are employed herein, they are used in a generic and descriptive sense only and not for purposes of limitation.
Claims
1. A method of interacting with a signaling tag, wherein the signaling tag comprises a radio frequency identification (RFID) transponder tag or a radio frequency transceiver, comprising:
- receiving information regarding a signaling tag at a terminal at least partially over an air interface via a short-range radio frequency transceiver or interrogator, the information regarding the signaling tag including at least a tag type of the signaling tag;
- determining whether the terminal is actively operating an application; and
- if the terminal is actively operating an application, performing a first predefined action based upon the tag type, the application and a state of the application, wherein the first predefined action comprises:
- initiating communication between the terminal and a device associated with the signaling tag and transmitting data to the device associated with the signaling tag when the tag type indicates that the signaling tag is a radio frequency transceiver and the active application is in a state of presenting data, wherein said transmitting data to the device comprises transmitting the presented data to the device via infra-red, Bluetooth or wireless local area network (WLAN) communication; and
- if the terminal is not actively operating an application, performing a second predefined action based upon the tag type, wherein the second predefined action comprises:
- reading data from the signaling tag and acting upon the received data when the tag type indicates that the signaling tag comprises a RFID transponder tag capable of at least transmitting data to the terminal.
2. A method according to claim 1, wherein performing a the first predefined action comprises reading data from the signaling tag into an actively operating application when:
- the information regarding the signaling tag indicates that the signaling tag is a RFID transponder tag capable of at least transmitting data to the terminal;
- the terminal is actively operating an application; and
- the application is in a state of receiving data.
3. A method according to claim 1, wherein performing a the first predefined action comprises reading data from the signaling tag into the terminal when the information regarding the signaling tag indicates that the signaling tag is a RFID transponder tag capable of at least transmitting data to the terminal and one of:
- the terminal is not actively operating an application; and
- the terminal is actively operating an application in a state other than a state of receiving data.
4. A method according to claim 1, wherein performing a the first predefined action comprises writing data to the signaling tag when:
- the information regarding the signaling tag indicates that the signaling tag is a RFID transponder tag capable of at least receiving data;
- the terminal is actively operating an application; and
- the application is in a state of presenting data.
5. A method according to claim 1, wherein performing a the first predefined action comprises reading data from the signaling tag into the terminal when:
- the information regarding the signaling tag indicates that the signaling tag is a RFID transponder tag capable of at least transmitting data and one of:
- the terminal is not actively operating an application; and
- the terminal is actively operating an application in a state other than a state of one of receiving data and presenting data.
6. A method according to claim 1, wherein the signaling tag comprises a radio frequency transceiver, wherein performing a the first predefined action comprises reading data from a device associated with the radio frequency transceiver into an actively operating application when:
- the information regarding the signaling tag indicates that the radio frequency transceiver is capable of at least transmitting data;
- the terminal is actively operating an application; and
- the application is in a state of receiving data, and
- wherein reading data from the device comprises reading data from the device in a manner independent of the radio frequency transceiver.
7. A method according to claim 6 further comprising:
- receiving at least one connection parameter from the device via the radio frequency transceiver, wherein reading data from the device comprises reading data from the device based upon the at least one connection parameter and in a manner independent of the radio frequency transceiver.
8. A method according to claim 1, wherein the signaling tag comprises a radio frequency transceiver, wherein performing a the first predefined action comprises writing data to a device associated with the radio frequency transceiver when:
- the information regarding the signaling tag indicates that the radio frequency transceiver is capable of at least receiving data;
- the terminal is actively operating an application; and
- the application is in a state of presenting data, and
- wherein writing data to the device comprises writing data to the device in a manner independent of the radio frequency transceiver.
9. A method according to claim 8 wherein the radio frequency transceiver is one of a short-range radio frequency transceiver or interrogator, the method further comprising:
- receiving at least one connection parameter from the device via the short-range radio frequency transceiver or interrogator, wherein writing data to the device comprises writing data to the device based upon the at least one connection parameter and in a manner independent of the short-range radio frequency transceiver or interrogator.
10. A method according to claim 1, wherein the signaling tag comprises a radio frequency transceiver, wherein performing a the first predefined action comprises initiating communication between the terminal and a device associated with the radio frequency transceiver when the information regarding the signaling tag indicates that the radio frequency transceiver is capable of at least transmitting data and one of:
- the terminal is not actively operating an application; and
- the terminal is actively operating an application in a state other than a state of one of receiving data and presenting data, and
- wherein initiating communication comprises initiating communication between the terminal and the device in a manner independent of the radio frequency transceiver.
11. A method according to claim 1 further comprising:
- selecting a signaling tag before receiving information regarding the signaling tag, wherein the signaling tag comprises a Radio Frequency Identification (RFID) transponder tag.
12. A method according to claim 11 further comprising:
- sending an interrogation signal to the RFID transponder tag, wherein receiving information regarding a signaling tag comprises receiving a tag type from the RFID transponder tag in response to the interrogation signal.
13. A method according to claim 11 further comprising:
- sending at least one interrogation signal to the RFID transponder tag, wherein each interrogation signal is associated with a different tag type;
- receiving a response from the RFID transponder tag to one of the at least one interrogation signal that triggers the response; and
- identifying a tag type based upon the interrogation signal that triggers the response, wherein receiving information regarding a signaling tag comprises receiving the identified tag type.
14. A method according to claim 11, wherein selecting a signaling tag comprises passing the terminal within a predefined distance of a signaling tag.
15. A terminal for interacting with a signaling tag wherein the signaling tag comprises a radio frequency identification (RFID) transponder tag or a radio frequency transceiver, the terminal comprising:
- a controller capable of actively operating an application, wherein the controller is capable of receiving information regarding a signaling tag at least partially over an air interface via a short-range radio frequency transceiver or interrogator, the information regarding the signaling tag including at least a tag type of the signaling tag, wherein the controller is also capable of determining whether the terminal is actively operating an application, and
- if the controller is actively operating an application, performing a first predefined action based upon the tag type, the application and a state of the application, wherein the first predefined action comprises:
- initiating communication between the terminal and a device associated with the signaling tag and transmitting data to the device associated with the signaling tag when the tag type indicates that the signaling tag is a radio frequency transceiver and the active application is in a state of presenting data;
- wherein said transmitting data to the device comprises transmitting the presented data to the device via infra-red, Bluetooth or wireless local area network (WLAN) communication; and
- if the terminal is not actively operating an application, performing a second predefined action based upon the tag type, wherein the second predefined action comprises:
- reading data from the signaling tag and acting upon the received data when the tag type indicates that the signaling tag comprises a RFID transponder tag capable of at least transmitting data to the terminal.
16. A terminal according to claim 15, wherein the controller is capable of performing a the first predefined action by reading data from the signaling tag into an actively operating application when:
- the information regarding the signaling tag indicates that the signaling tag is a RFID transponder tag capable of at least transmitting data to the terminal;
- the controller is actively operating an application; and
- the application is in a state of receiving data.
17. A terminal according to claim 15, wherein the controller is capable of performing a the first predefined action by reading data from the signaling tag into the terminal when the information regarding the signaling tag indicates that the signaling tag is a transponder tag capable of at least transmitting data to the terminal and one of:
- the controller is not actively operating an application; and
- the controller is actively operating an application in a state other than a state of receiving data.
18. A terminal according to claim 15, wherein the controller is capable of performing a the first predefined action by writing data to the signaling tag when:
- the information regarding the signaling tag indicates that the signaling tag is a RFID transponder tag capable of at least receiving data;
- the controller is actively operating an application; and
- the application is in a state of presenting data.
19. A terminal according to claim 15, wherein the controller is capable of performing a the first predefined action by reading data from the signaling tag into the terminal when:
- the information regarding the signaling tag indicates that the signaling tag is a RFID transponder tag capable of at least transmitting data and one of:
- the controller is not actively operating an application; and
- the controller is actively operating an application in a state other than a state of one of receiving data and presenting data.
20. A terminal according to claim 15, wherein the signaling tag comprises a radio frequency transceiver, wherein the controller is capable of performing a the first predefined action by reading data from a device associated with the radio frequency transceiver into an actively operating application when:
- the information regarding the signaling tag indicates that the radio frequency transceiver is capable of at least transmitting data;
- the controller is actively operating an application; and
- the application is in a state of receiving data, and
- wherein the controller is capable of reading data from the device in a manner independent of the radio frequency transceiver.
21. A terminal according to claim 20, wherein the radio frequency transceiver is one of a short-range radio frequency transceiver or an interrogator, wherein the controller is capable of receiving at least one connection parameter from the device via the short-range radio frequency transceiver or interrogator, and wherein the controller is capable of reading data from the device based upon the at least one connection parameter and in a manner independent of the short-range radio frequency transceiver or interrogator.
22. A terminal according to claim 15, wherein the signaling tag comprises a radio frequency transceiver, wherein the controller is capable of performing a the first predefined action by writing data to a device associated with the radio frequency transceiver when:
- the information regarding the signaling tag indicates that the radio frequency transceiver is capable of at least receiving data;
- the controller is actively operating an application; and
- the application is in a state of presenting data, and
- wherein the controller is capable of writing data to the device in a manner independent of the radio frequency transceiver.
23. A terminal according to claim 22, wherein the radio frequency transceiver is one of a short-range radio frequency transceiver or an interrogator, wherein the controller is capable of receiving at least one connection parameter from the device via the short-range radio frequency transceiver or interrogator, and wherein the controller is capable of writing data to the device based upon the at least one connection parameter and in a manner independent of the short-range radio frequency transceiver or interrogator.
24. A terminal according to claim 15, wherein the signaling tag comprises a radio frequency transceiver, wherein the controller is capable of performing a the first predefined action by initiating communication a device associated with the radio frequency transceiver when the information regarding the radio frequency transceiver indicates that the transceiver is capable of at least transmitting data and one of:
- the controller is not actively operating an application; and
- the controller is actively operating an application in a state other than a state of one of receiving data and presenting data, and
- wherein the controller is capable of initiating communication with the device in a manner independent of the radio frequency transceiver.
25. A terminal according to claim 15, wherein the controller is further capable of selecting a signaling tag before receiving information regarding the signaling tag, wherein the signaling tag comprises a Radio Frequency Identification (RFID) transponder tag.
26. A terminal according to claim 25, wherein the radio frequency transceiver is one of a short-range radio frequency transceiver or an interrogator, wherein the controller is further capable of sending an interrogation signal to the RFID transponder tag via the short-range radio frequency transceiver or interrogator, wherein the controller is capable of receiving information regarding a signaling tag comprising a tag type from the RFID transponder tag in response to the interrogation signal.
27. A terminal according to claim 25, wherein the controller is capable of sending at least one interrogation signal to the RFID transponder tag, wherein each interrogation signal is associated with a different tag type, wherein the controller is capable of receiving a response from the RFID transponder tag to one of the at least one interrogation signal that triggers the response, and wherein the controller is also capable of identifying a tag type based upon the interrogation signal that triggers the response, wherein the information regarding a signaling tag comprises the identified tag type.
28. A terminal according to claim 25 further comprising:
- a transceiver coupled to the controller, wherein the controller is capable of selecting a signaling tag by the transceiver being passed within a predefined distance of a signaling tag.
29. A computer program product for interacting with a signaling tag, wherein the signaling tag comprises a radio frequency identification (RFID) transponder tag or a radio frequency transceiver, the computer program product comprising a non-transitory computer-readable storage medium having computer-readable program code portions stored therein, the computer-readable program code portions comprising: a first executable portion receiving information regarding a signaling tag at a terminal at least partially over an air interface via a short-range radio frequency transceiver or interrogator, the information regarding the signaling tag including at least a tag type of the signaling tag; a second executable portion for determining, whether the terminal is actively operating an application; and if the terminal is actively operating an application, a third executable portion for performing a first predefined action based upon the application and a state of the application, wherein the first predefined action comprises: initiating communication between the terminal and a device associated with the signaling tag and transmitting data to the device associated with the signaling tag when the tag type indicates that the signaling tag is a radio frequency transceiver and the active application is in a state of presenting data; wherein said transmitting data to the device comprises transmitting the presented data to the device via infra-red. Bluetooth or wireless local area network (WLAN) communication; and if the terminal is not actively operating an application, performing a second predefined action based upon the tag type, wherein the second predefined action comprises: reading data from the signaling tag and acting upon the received data when the tag indicates that the signaling tag comprises a RFID transponder tag capable of at least transmitting data to the terminal.
30. A computer program product according to claim 29, wherein the third executable portion is adapted to perform a the first predefined action by reading data from the signaling tag into an actively operating application when:
- the information regarding the signaling tag indicates that the signaling tag is a RFID transponder tag capable of at least transmitting data to the terminal;
- the terminal is actively operating an application; and
- the application is in a state of receiving data.
31. A computer program product according to claim 29, wherein the third executable portion is adapted to perform a the first predefined action by reading data from the signaling tag into the terminal when the information regarding the signaling tag indicates that the signaling tag is a RFID transponder tag capable of at least transmitting data to the terminal and one of:
- the terminal is not actively operating an application; and
- the terminal is actively operating an application in a state other than a state of receiving data.
32. A computer program product according to claim 29, wherein the third executable portion is adapted to perform a the first predefined action by writing data to the signaling tag when:
- the information regarding the signaling tag indicates that the signaling tag is a RFID transponder tag capable of at least receiving data;
- the terminal is actively operating an application; and
- the application is in a state of presenting data.
33. A computer program product according to claim 32, wherein the third executable portion is adapted to perform a the first predefined action by reading data from the signaling tag into the terminal when:
- the information regarding the signaling tag indicates that the signaling tag is a RFID transponder tag capable of at least transmitting data and one of:
- the terminal is not actively operating an application; and
- the terminal is actively operating an application in a state other than a state of one of receiving data and presenting data.
34. A computer program product according to claim 29, wherein the signaling tag comprises a radio frequency transceiver, wherein the third executable portion is adapted to perform a the first predefined action by reading data from a device associated with the radio frequency transceiver into an actively operating application when:
- the information regarding the signaling tag indicates that the radio frequency transceiver is capable of at least transmitting data;
- the terminal is actively operating an application; and
- the application is in a state of receiving data, and
- wherein the third executable portion is adapted to read data from the device in a manner independent of the radio frequency transceiver.
35. A computer program product according to claim 34 wherein the radio frequency transceiver is one of a short-range radio frequency transceiver or an interrogator, the computer program product further comprising:
- a fourth executable portion for receiving at least one connection parameter from the device via the short-range radio frequency transceiver or interrogator, wherein the third executable portion is adapted to perform a the first predefined action by reading data from the device based upon the at least one connection parameter and in a manner independent of the short-range radio frequency transceiver or interrogator.
36. A computer program product according to claim 29, wherein the signaling tag comprises a radio frequency transceiver, wherein the third executable portion is adapted to perform a the first predefined action by writing data to a device associated with the radio frequency transceiver when:
- the information regarding the signaling tag indicates that the radio frequency transceiver is capable of at least receiving data;
- the terminal is actively operating an application; and
- the application is in a state of presenting data, and
- wherein the third executable portion is adapted to write data to the device in a manner independent of the radio frequency transceiver.
37. A computer program product according to claim 36 wherein the radio frequency transceiver is one of a short-range radio frequency transceiver or an interrogator, the computer program product further comprising:
- a fourth executable portion for receiving at least one connection parameter from the device via the short-range radio frequency transceiver or interrogator, wherein the third executable portion is adapted to perform a the first predefined action by writing data to the device based upon the at least one connection parameter and in a manner independent of the short-range radio frequency transceiver or interrogator.
38. A computer program product according to claim 29, wherein the signaling tag comprises a radio frequency transceiver, wherein the third executable portion is adapted to perform a the first predefined action by initiating communication between the terminal and the device associated with the radio frequency transceiver when the information regarding the signaling tag indicates that the radio frequency transceiver is capable of at least transmitting data and one of:
- the terminal is not actively operating an application; and
- the terminal is actively operating an application in a state other than a state of one of receiving data and presenting data, and
- wherein the third executable portion is adapted to initiate communication between the terminal and the device in a manner independent of the radio frequency transceiver.
39. A computer program product according to claim 29 further comprising:
- a fourth executable portion for selecting a signaling tag before the first executable portion receives information regarding the signaling tag, wherein the signaling tag comprises a Radio Frequency Identification (RFID) transponder tag.
40. A computer program product according to claim 39 further comprising:
- a fifth executable portion for sending an interrogation signal to the RFID transponder tag, wherein the first executable portion is adapted to receive information regarding a signaling tag comprising a tag type from the RFID transponder tag in response to the interrogation signal.
41. A computer program product according to claim 39 further comprising:
- a fifth executable portion for sending at least one interrogation signal to the RFID transponder tag, wherein each interrogation signal is associated with a different tag type;
- a sixth executable portion for receiving a response from the RFID transponder tag to one of the at least one interrogation signal that triggers the response; and
- a seventh executable portion for identifying a tag type based upon the interrogation signal that triggers the response, wherein the first executable portion is adapted to receive information regarding a signaling tag comprising the identified tag type.
| 5530702 | June 25, 1996 | Palmer et al. |
| 5850187 | December 15, 1998 | Carrender et al. |
| 5947256 | September 7, 1999 | Patterson |
| 6122329 | September 19, 2000 | Zai et al. |
| 6169483 | January 2, 2001 | Ghaffari et al. |
| 6617962 | September 9, 2003 | Horwitz et al. |
| 6628938 | September 30, 2003 | Rachabathuni et al. |
| 6747567 | June 8, 2004 | Amano et al. |
| 6816063 | November 9, 2004 | Kubler et al. |
| 6826756 | November 30, 2004 | Herrod et al. |
| 6892052 | May 10, 2005 | Kotola et al. |
| 7075412 | July 11, 2006 | Reynolds et al. |
| 7102640 | September 5, 2006 | Aholainen et al. |
| 7151764 | December 19, 2006 | Heinonen et al. |
| 7170857 | January 30, 2007 | Stephens et al. |
| 7274909 | September 25, 2007 | Perttila |
| 7516201 | April 7, 2009 | Kovacs et al. |
| 7519682 | April 14, 2009 | Smith et al. |
| 7676194 | March 9, 2010 | Rappaport |
| 7775432 | August 17, 2010 | Jalkanen et al. |
| 7909252 | March 22, 2011 | Jalkanen et al. |
| 7920827 | April 5, 2011 | Huomo |
| 8210433 | July 3, 2012 | Jalkanen et al. |
| 8306065 | November 6, 2012 | Kako |
| 8308065 | November 13, 2012 | Jalkanen et al. |
| 8366000 | February 5, 2013 | Jalkanen et al. |
| 20010045460 | November 29, 2001 | Reynolds et al. |
| 20020021809 | February 21, 2002 | Salo et al. |
| 20020022961 | February 21, 2002 | Sepanaho |
| 20020023264 | February 21, 2002 | Aaltonen et al. |
| 20020062251 | May 23, 2002 | Anandan et al. |
| 20020069406 | June 6, 2002 | Aaltonen et al. |
| 20020080031 | June 27, 2002 | Mann et al. |
| 20020087997 | July 4, 2002 | Dahlstrom |
| 20020116268 | August 22, 2002 | Fukuda |
| 20020143624 | October 3, 2002 | Catan |
| 20020191998 | December 19, 2002 | Cremon et al. |
| 20030011628 | January 16, 2003 | Piatek |
| 20030043041 | March 6, 2003 | Zeps et al. |
| 20030084177 | May 1, 2003 | Mulligan |
| 20030097304 | May 22, 2003 | Hunt |
| 20030120745 | June 26, 2003 | Katagishi et al. |
| 20030134653 | July 17, 2003 | Sarkkinen et al. |
| 20040087273 | May 6, 2004 | Perttila et al. |
| 20040193676 | September 30, 2004 | Marks |
| 20040203413 | October 14, 2004 | Harumoto |
| 20040203638 | October 14, 2004 | Chan et al. |
| 20040225199 | November 11, 2004 | Evanyk et al. |
| 20050014468 | January 20, 2005 | Salokannel et al. |
| 20050054290 | March 10, 2005 | Logan et al. |
| 20050108317 | May 19, 2005 | Someya et al. |
| 20050215280 | September 29, 2005 | Twitchell, Jr. |
| 20060119471 | June 8, 2006 | Rudolph et al. |
| 20070275746 | November 29, 2007 | Bitran |
| 20080055632 | March 6, 2008 | Oshiumi et al. |
| 20080146151 | June 19, 2008 | Lyu et al. |
| 20090215397 | August 27, 2009 | Thorn et al. |
| 20090276439 | November 5, 2009 | Rosenblatt et al. |
| 20100093280 | April 15, 2010 | Ahn et al. |
| 20100241529 | September 23, 2010 | Kim |
| 20120015605 | January 19, 2012 | Sole |
| 20120169473 | July 5, 2012 | Jalkanen et al. |
| 20120228374 | September 13, 2012 | Jalkanen et al. |
| 1349639 | May 2002 | CN |
| 1662920 | August 2005 | CN |
| 1708922 | December 2005 | CN |
| 102254131 | November 2011 | CN |
| 60 2004 015 322 | July 2017 | DE |
| 1 182 833 | February 2002 | EP |
| 1 244 043 | September 2002 | EP |
| 1 556 965 | July 2005 | EP |
| 2 073 514 | June 2009 | EP |
| 2 355 563 | August 2011 | EP |
| 2 424 281 | February 2012 | EP |
| H10-162245 | June 1998 | JP |
| 2003-198451 | July 2003 | JP |
| 2005 108044 | April 2005 | JP |
| WO 00/51293 | August 2000 | WO |
| WO 00/67221 | November 2000 | WO |
| WO 01/45319 | June 2001 | WO |
| WO 01 50224 | July 2001 | WO |
| WO 01/52179 | July 2001 | WO |
| WO 01/67265 | September 2001 | WO |
| WO 01/79988 | October 2001 | WO |
| WO 02/11074 | February 2002 | WO |
| WO 02/15601 | February 2002 | WO |
| WO 2002/021709 | March 2002 | WO |
| WO 02/27422 | April 2002 | WO |
| WO 02/063894 | August 2002 | WO |
| WO 03/081787 | October 2003 | WO |
| WO 2004/003801 | January 2004 | WO |
| WO 2005/008575 | January 2005 | WO |
| WO 2007/040398 | April 2007 | WO |
| WO 2009/013646 | January 2009 | WO |
- Busboom, A. et al., Unambiguous Device Identification and Fast Connection Setup in Bluetooth, 5 pages.
- Langheinrich, M. et al., First Steps Towards an Event-Based Infrastructure for Smart Things, Ubiquitous Computing Workshop (PACT 2000) (2000) 13 pages.
- Rekimoto, J. et al., Proximal Interactions: A Direct Manipulation Technique for Wireless Networking, Interact. vol. 3 (2003) 8 pages.
- Rekimoto, J. et al., DataTiles: A Modular Platform For Mixed Physical and Graphical Interactions, Proceedings of the SIGCHI Conference on Human Factors in Computing Systems, ACM (2001) 8 pages.
- Want, R. et al., Bridging Physical and Virtual Worlds With Electronic Tags, CHI. vol. 99 (May 1999) 370-3377.
- Judgement , Bundespatentgericht Federal Patent Court, File No. 5 NI 40/13 (EP) regarding European Patent No. 1 685 689 (DE 60 2004 015 322) dated Nov. 23, 2016, 51 pages (with 44 pages translated).
- Near-field communication—Wikipedia [online] [retrieved Jul. 17, 2019]. Retrieved from the Internet: <https://web.archive.org/web/20190110093705/http://en.wikipedia.org/wiki/wiki/Near_field_communication>. (dated Dec. 23, 2018) 8 pages.
- Android O-click NEC sharing demonstrated in Ice Cream Sandwich (video) [online] [retrieved Jul. 17, 2019]. Retrieved from the Internet: <https://www.engadget.com/2011/05/11/android-o-click-nfc-sharing-demonstrated-in-ice-cream-sandwich>, (dated May 11, 2011) 9 pages.
- Near Field Communication | Android Developers [online] [retrieved Jul. 17, 2019]. Retrieved from the Internet: <https://web.archive.org/web/20170717095658/https://developer.android.com/guide/topics/nfc/index.html>. (undated) 2 pages.
- Information Technology—Telecommunications and Information Exchange Between Systems—Near Field Communication—Interface and Protocol (NFCIP-1) ISO/IEC 18092 (Apr. 1, 2004) 66 pages.
- International Written Opinion for Application No. PCT/IB2004/052029 dated Apr. 6, 2005, 5 pages.
- Widmer, P., Smart Box Software Framework, Vision Document, Jul. 4, 2003, 23pages.
- Office Action for Chinese Application No. 200480037125.6 dated Feb. 13, 2009.
- Communication for European Application No. 04 791 807.3 dated Aug. 29, 2006.
- Communication for European Application No. 04 791 807.3 dated Apr. 25, 2007.
- Extended Search Report for European Application No. 08 006 467.8 dated Nov. 2, 2011.
- Office Action for Japanese Application No. 2006-534881 dated Dec. 2, 2008.
- Office Action for Korean Application No. 10-2006-7009441 dated Apr. 23, 2007.
- Notice of Allowance for Korean Application No. 10-2006-7009441 dated Jan. 7, 2008.
- Search Report for International Application No. PCT/IB2004/052029 dated Apr. 6, 2005.
- Office Action from U.S. Appl. No. 13/107,145, dated Oct. 11, 2012.
- Office Action for U.S. Appl. No. 13/481,327 dated Jul. 9, 2012.
- Notice of Allowance for U.S. Appl. No. 13/481,327 dated Nov. 15, 2012.
- Notice of Allowance for U.S. Appl. No. 13/419,019 dated Aug. 3, 2012.
- Notice of Allowance for U.S. Appl. No. 13/419,019 dated Jun. 8, 2012.
- Office Action for U.S. Appl. No. 13/419,019 dated May 10, 2012.
- Notice of Allowance for U.S. Appl. No. 12/830,170 dated Nov. 12, 2010.
- Notice of Allowance for U.S. Appl. No. 12/830,170 dated Oct. 7, 2010.
- Notice of Allowance for U.S. Appl. No. 12/830,164 dated Mar. 2, 2012.
- Office Action for U.S. Appl. No. 12/830,164 dated Aug. 17, 2011.
- Advisory Action for U.S. Appl. No. 10/687,036 dated Jun. 15, 2006.
- Office Action for U.S. Appl. No. 10/687,036 dated Aug. 21, 2007.
- Office Action for U.S. Appl. No. 10/687,036 dated Jul. 27, 2005.
- Examiner's Answer for U.S. Appl. No. 10/687,036 dated Apr. 15, 2008.
- Notice of Allowance for U.S. Appl. No. 10/687,036 dated Apr. 22, 2010.
- Nokia 9210 Communicator User's Guide, Part No. 9352303, Issue No. 3, 2001 (279 pages).
- Nokia 3600 and Nokia 3650 User's Guide, Part No. 9356743, Issue No. 1, 2003 (217 pages).
- SES Technology R&D Group, Introduction to the IrDA Protocol, Technology Development Group, Mar. 3, 1997 (22 pages).
- Rekimoto, J. et al., Proximal Interactions: A Direct Manipulation Technique for Wireless Networking, Sony Computer Science Laboratories, Inc., Aug. 18, 2003, pp.
- Römer, K. et al., Smart Playing Cards: A Ubiquitous Computing Game, Personal and Ubiquitous Computing, 2002, pp. 371-377.
- Finkenzeller, Klaus, Fundamentals and Applications in Contactless Smart Cards and Idenfication, RFID Handbook, Second Edition, ISBN: 0-470-844-2-7, Jul. 21, 2003 (434 pages).
- Hall, E. S. et al., RF Rendez-Blue: Reducing Power and Inquiry Costs in Bluetooth-Enabled Mobile Systems, Proceedings Eleventh International Conference on Computer Communications and Networks, Oct. 14-16, 2002, pp. 640-645.
- U.S. Appl. No. 09/515,297, filed Feb. 29, 2000; In re: Richter, entitled RFID Tag With Embedded Internet Address.
- Fletcher, R. et al., Application of Smart Materials to Wireless ID Tags and Remote Sensors, In Materials the Smart Systems II (pp. 557-562) Materials Research Society (1997) 6 pages.
- Megowan et al., “IrDA Object Exchange Protocol”, Infrared Data Association, irOBEX, (Mar. 18, 1999), 86 pages.
- Rhodes et al., “Palm Programming: The Developer's Guide”, O'Reilly Media, Inc., (Dec. 1998), 178 pages.
- “Ice Cream Sandwich—Android 4.0”, [online] [retrieved Jul. 15, 2021]. Retrieved from the Internet via the Wayback Machine: <URL:https://web.archive.org/web/20120623222715/http://developer.android.com/about/versions/android-4.0-highlights.html> (Jun. 23, 2012), 9 pages.
- “Android 4.1 for Developers—Jelly Bean”, [online] [retrieved Jul. 15, 2021]. Retrieved from the Internet via the Wayback Machine: <URL:https://web.archive.org/web/20120628222155/https://developer.android.com/about/versions/jelly-bean.html> (Jun. 28, 2012), 6 pages.
- “Glu Adds Android Beam to Gun Bros Game”, NFC World [online] [retrieved Jul. 15, 2021]. Retrieved from the Internet: <URL:http://www.nfcworld.com/2012/02/27/313930/glu-adds-android-beam-to-gun-bros-game>(Feb. 27, 2012), 2 pages.
- “Nokia Communicator—Wikipedia”[online] [retrieved Jul. 15, 2021]. Retrieved from the Internet: <URL:https://en.wikipedia.org/w/index.php?oldid=542621124> (Mar. 7, 2013), 2 pages.
- Statement of Complaint for Nullity, HTC Corporation/HTX Europe Co., Ltd./HTC Germany GmbH vs. Nokia Corporation regarding EP 1 685 689 (DE 60 2004 015 322.2) (Mar. 6, 2013), 20 pages.
- Statement of Grounds for Nullity, HTC Europe Co., Ltd. vs Nokia Corporation regarding EP 1 685 689 (DE 60 2004 015 322.2), File No. 5 Ni 26/13, (Jan. 27, 2014, 39 pages.
- Complaint against EP 1 685 689 (DE 60 2004 015 322.2), HTC Corporation et al. vs Nokia Corporation (Jun. 14, 2013), 98 pages.
- Extension of Complaint and Statement of Reply, Google Inc. vs Nokia Technologies Oy regarding EP 1 685 689 (DE 60 2004 015 322.2), File No. 5 Ni 40/13, (Sep. 3, 2015), 85 pages.
- Response to Extension of Action and Reply of Invalidity Claimant dated Sep. 3, 2015 Google Inc. vs Nokia Corporation, File No. 5 Ni 40/13, (Feb. 19, 2016), 45 pages.
- Response to Defendant's Pleading of Mar. 30, 3016, Google Inc. vs Nokia Technologies Oy, File No. 5 Ni 40/13, (Jul. 8, 2016), 14 pages.
- Summons to Attend Oral Hearing, Federal Patent Court, Google Inc. vs Nokia Technoliges Oy, File No. 5 Ni 40/13, (Jul. 19, 2016), 21 pages.
- Response to Qualified Instruction, Google Inc. vs Nokia Technologies Oy, File No. 5 Ni 40/13, (Aug. 22, 2016), 66 pages.
- Position Statement, Google Inc. vs Nokia Technologies Oy, File No. 5 Ni 40/13, (Sep. 26, 2016), 19 pages.
- Response to Plaintiff's Pleading of Aug. 22, 2016, Google Inc. vs Nokia Technologies Oy, File No. 5 Ni 40/13, (Sep. 29, 2016), 112 pages.
- Position Statement, Google Inc. vs Nokia Technologies Oy, File No. 5 Ni 40/13, (Nov. 11, 2016), 50 pages.
- Response to Qualified Notice dated Jul. 19, 2016, Google Inc. vs Nokia Corporation, File No. 5 Ni 40/13, (Aug. 22, 2016), 34 pages.
- Nullity Complaint and FPC Response, Google Inc. vs Nokia Corporation, File No. 5 Ni 40/13, (Oct. 15, 2013), 56 pages.
- Minutes of the Oral Proceeding and Decision, Google Inc. vs Nokia Technologies Oy, File No. 5 Ni 40/13, (Nov. 23, 2016), 28 pages.
- Response to Judicial Release dated Nov. 23, 2016, Google Inc. vs Nokia Corporation, File No. 5 Ni 40/13, (Dec. 19, 2013), 7 pages.
- Decision regarding Security Bonds as Issued by the FPC, Google Inc. vs Nokia Corporation, File No. 5 Ni 40/13, (Feb. 19, 2014), 6 pages.
- Response to the Decision regarding Security Bonds, Google Inc vs Nokia Corporation, File No. 5 Ni 40/13, (Jan. 7, 2014), 3 pages.
- Declaration Requesting to Dismiss Annulment Action, Google Inc vs Nokia Corporation, File No. 5 Ni 40/13, (Nov. 15, 2013), 5 pages.
- Radio Frequency Identification RFID—A basic primer, AIM Inc. White Paper; Aug. 23, 2001; 17 pages; 1.2; The Association of the Automatic Identification and Data Capture Industry (AIM Inc.); WP-98/002R2.
- Notice and Filing of Opposition in European Patent 1 685 689.
- Reply to Notice of Opposition in European Patent 1 685 689.
Type: Grant
Filed: Jan 11, 2019
Date of Patent: Dec 28, 2021
Assignee: NOKIA TECHNOLOGIES OY (Espoo)
Inventors: Janne Jalkanen (Helsinki), Heikki Huomo (Oulu), Petri Vesikivi (Espoo)
Primary Examiner: Jalatee Worjloh
Application Number: 16/245,622
International Classification: H04M 1/72412 (20210101); H04W 76/14 (20180101); H04W 4/80 (20180101); G06Q 20/20 (20120101); G06Q 30/02 (20120101); H04M 1/72445 (20210101); H04M 1/7243 (20210101); H04W 8/24 (20090101); H04W 48/08 (20090101); H04W 48/16 (20090101); H04W 88/06 (20090101);
