Network messaging for paired devices
Messaging between a companion device and an accessory device is controlled such that different modes of communication may be utilized. The different modes can implement different messaging strategies, each of which is intended for efficient power management, in view of the limited electrical power that is typically available at the accessory device. A received request message for sending from the companion device to the accessory device is sent if predetermined conditions apply, and similarly for messages from the accessory device to the companion device.
1. A method of data transfer from a mobile device to a wearable device, the method comprising, at the mobile device:
receiving refresh preferences for updating application information intended for a particular accessory application of the wearable device, wherein the wearable device is paired with the mobile device;
identifying a trigger for sending updated application information to the wearable device;
receiving the identified trigger;
responsive to the identified trigger, obtaining new application data;
determining a current state of the wearable device;
determining, by a wearable device communication daemon, whether to send the new application data to an accessory application of the wearable device, wherein the determination of whether to send the new application data is made according to the refresh preferences, the current state of the wearable device, and a number of updates of the application information that have been sent to the wearable device within a predetermined time period being below a predetermined threshold number of updates; when the number of updates exceeds the predetermined threshold number of updates, waiting until the number of updates within a new time period is below the predetermined threshold number of updates prior to transmitting an update and then sending the new application data to the wearable device; and
responsive to determining to send the new application data, sending the new application data to the wearable device.
2. The method of claim 1 , wherein the trigger is a periodic trigger generated by a system routine on the mobile device.
3. The method of claim 1 , further comprising:
receiving a push message from a server when new data is generated, the push message containing the new data and acting as the trigger;
launching a companion application to the particular accessory application of the wearable device; and
processing the new data to send to the wearable device.
4. The method of claim 1 , wherein the trigger is an end of a period for a sports event.
5. The method of claim 1 , further comprising: budgeting the predetermined threshold number of updates to occur within a particular window of activity in a day.
6. The method of claim 1 , further comprising: budgeting the predetermined threshold number of updates to be evenly distributed in time over a day.
7. A mobile device, comprising: a processor; and a memory coupled to the processor, the memory storing instructions, which when executed by the processor, cause the mobile device to perform operations including:
receive refresh preferences for updating application information intended for a particular accessory application of a wearable device, wherein the wearable device is paired with the mobile device;
identify a trigger for sending updated application information to the wearable device; receive the identified trigger;
responsive to the identified trigger, obtain new application data;
determine a current state of the wearable device;
determine, by a wearable device communication daemon, whether to send the new application data to an accessory application of the wearable device, wherein the determination of whether to send the new application data is made according to the refresh preferences, the current state of the wearable device, and a number of updates of the application information that have been sent to the wearable device within a predetermined time period being below a predetermined threshold number of updates; when the number of updates exceeds the predetermined threshold number of updates, waiting until the number of updates within a new time period is below the predetermined threshold number of updates prior to transmitting an update and then sending the new application data to the wearable device; and
responsive to determining to send the new application data, send the new application data to the wearable device.
8. The mobile device of claim 7 , wherein the trigger is a periodic trigger generated by a system routine on the mobile device.
9. The mobile device of claim 7 , further comprising additional instructions, which when executed by the processor, cause the mobile device to perform further operations including:
receiving a push message from a server when new data occurs, the push message containing the new data and acting as the trigger;
launching a companion application; and
processing the new data to send to the wearable device.
10. The mobile device of claim 7 , wherein the trigger is an end of a period for a sports event.
11. The mobile device of claim 7 , wherein the operations further comprise: budgeting the predetermined threshold number of updates to occur within a particular window of activity in a day.
12. The mobile device of claim 7 , wherein the operations further comprise: budgeting the predetermined threshold number of updates to be evenly distributed in time over a day.
13. A non-transitory computer-readable medium storing a plurality of instructions that, when executed by one or more processors of a mobile device, cause the one or more processors to perform operations comprising:
receiving refresh preferences for updating application information intended for a particular accessory application of a wearable device, wherein the wearable device is paired with the mobile device;
identifying a trigger for sending updated application information to the wearable device;
receiving the identified trigger;
responsive to the identified trigger, obtaining new application data;
determining a current state of the wearable device;
determining, by a wearable device communication daemon, whether to send the new application data to an accessory application of the wearable device, wherein the determination of whether to send the new application data is made according to the refresh preferences, the current state of the wearable device, and a number of updates of the application information that have been sent to the wearable device within a predetermined time period being below a predetermined threshold number of updates; when the number of updates exceeds the predetermined threshold number of updates, waiting until the number of updates within a new time period is below the predetermined threshold number of updates prior to transmitting an update and then sending the new application data to the wearable device;
and responsive to determining to send the new application data, sending the new application data to the wearable device.
14. The non-transitory computer-readable medium of claim 13 , wherein the trigger is a periodic trigger generated by a system routine on the mobile device.
15. The non-transitory computer-readable medium of claim 13 , wherein the operations further comprise:
receiving a push message from a server when new data occurs, the push message containing the new data and acting as the trigger;
launching a companion application; and
processing the new data to send to the wearable device.
16. The non-transitory computer-readable medium of claim 13 , wherein the trigger is an end of a period for a sports event.
17. The non-transitory computer-readable medium of claim 13 , wherein the operations further comprise budgeting the predetermined threshold number of updates to occur within a particular window of activity in a day.