Legal claims defining the scope of protection, as filed with the USPTO.
1. A method comprising: receiving, at a supporting device, an event message from a primary device, the event message identifying an event type from a plurality of event types; determining, by the supporting device, based at least in part on the identified event type, whether event-related data should be provided to the primary device; in response to determining that event-related data should be provided to the primary device: determining, by the supporting device, based at least in part on the identified event type, whether the event-related data is static data or dynamic data; in response to determining that the event related data is static data, retrieving the event-related data from a local storage subsystem of the supporting device; in response to determining that the event related data is dynamic data, retrieving the event related data from a remote source via a wireless network; and providing the retrieved event-related data to the primary device; and presenting information at a user interface of the supporting device based at least in part on the identified event type.
2. The method of claim 1 wherein presenting the information includes selecting the information to be presented based in part on the identified event type and in part on an event history including one or more previously received event messages.
3. The method of claim 1 wherein presenting the information includes displaying information on a display of the supporting device.
4. The method of claim 1 wherein the event-related data is determined to be static data in response to the identified event type corresponding to a request for personal information.
5. The method of claim 1 wherein the event-related data is determined to be dynamic data in response to the identified event type corresponding to a request for non-personal information that is variable with time.
6. The method of claim 1 further comprising: in response to receiving the event message, updating state information including a history of received event messages, wherein presenting the information at the user interface of the supporting device is based at least in part on the updated state information.
7. An electronic device comprising: a primary device interface configured to communicate with a primary device; a network interface to communicate with a remote data source via a network; a local user interface; a local storage subsystem to store static data; and a processor coupled to the primary device interface, the network interface, the local user interface, and the local storage subsystem, the processor being configured to: receive an event message from the primary device via the primary device interface, the event message identifying an event type from a plurality of event types; determine, based at least in part on the identified event type, whether event-related data should be provided to the primary device; in response to determining that event-related data should be provided to the primary device: determine whether the event-related data is static data or dynamic data; in response to determining that the event related data is static data, retrieve the event-related data from the local storage subsystem; in response to determining that the event related data is dynamic data, retrieve the event related data from the remote data source via the network interface; and provide the retrieved event-related data to the primary device via the primary device interface; and present information at the local user interface based at least in part on the identified event type.
8. The electronic device of claim 7 wherein the primary device interface includes a wired interface.
9. The electronic device of claim 7 wherein the network interface is configured to connect to a wide area network.
10. The electronic device of claim 7 wherein the network interface includes a wireless interface.
11. The electronic device of claim 7 wherein the processor is further configured to select the information to be presented at the local user interface based in part on the identified event type and in part on an event history including one or more previously received event messages.
12. The electronic device of claim 7 wherein the processor is further configured such that the event-related data is determined to be static data in response to the identified event type corresponding to a request for personal information.
13. The electronic device of claim 7 wherein the processor is further configured such that the event-related data is determined to be dynamic data in response to the identified event type corresponding to a request for non-personal information that is variable with time.
14. A method comprising: detecting, at a local user interface of a primary device, a first user input; generating, by the primary device, an event message based at least in part on the first user input, the event message including an identification of an event type from a plurality of event types; communicating, by the primary device, the event message to a supporting device; determining, by the supporting device, based at least in part on the identified event type, whether event-related data should be provided to the primary device; in response to determining that event-related data should be provided to the primary device: determining, by the supporting device whether the event-related data is static data or dynamic data; in response to determining that the event related data is static data, retrieving, by the supporting device, the event-related data from a local storage subsystem of the supporting device; in response to determining that the event related data is dynamic data, retrieving, by the supporting device, the event related data from a remote source via a wireless network; and communicating, by the supporting device, the retrieved event-related data to the primary device via the primary device interface; presenting event-relevant information at a local user interface of the supporting device based at least in part on the identified event type; and presenting, at the local user interface of the primary device, a response to the first user input, wherein presenting the response includes: determining, by the primary device, based at least in part on the identified event type, whether event-related data should be received from the supporting device; in the event that event-related data should be received from the supporting device, presenting the response after receiving the retrieved event-related data from the supporting device, the response based at least in part on the retrieved event-related data; and in the event that event-related data should not be received from the supporting device, presenting the response without waiting for event-related data from the supporting device.
15. The method of claim 14 further comprising: in response to receiving the event message, updating, by the supporting device, state information including a history of received event messages, wherein presenting the information at the local user interface of the supporting device is based at least in part on the updated state information.
16. The method of claim 14 wherein the event-related data is determined to be static data in response to the identified event type corresponding to a request for personal information.
17. The method of claim 14 wherein the event-related data is determined to be dynamic data in response to the identified event type corresponding to a request for non-personal information that is variable with time.
18. The method of claim 14 wherein the communication between the primary device and the supporting device is performed via a wired point-to-point connection between the primary device and the supporting device.
19. The method of claim 14 wherein presenting the response to the user input at the primary device is independent of whether the retrieved event-related data is static data or dynamic data.
20. The method of claim 14 further comprising: detecting, at the local user interface of the supporting device, a second user input; and presenting, by the supporting device, a response to the second user input at the local user interface of the supporting device, wherein the primary device is agnostic to the second user input.
Unknown
August 1, 2017
Browse 5M+ US patents with plain-English claim translations and AI-generated analysis.