Network messaging for paired devices

• US 10,680,997 B2
• Filed: 08/22/2018
• Issued: 06/09/2020
• Est. Priority Date: 06/05/2015
• Status: Expired due to Fees

• Current Assignee: Apple Inc.
• Original Assignee: Apple Inc.
• Inventors: Ledwith, Alexander, Jensen, Christopher C., Iarocci, John J., Krochmal, Marc J., Wolkowicki, Ziv, Pollack, Daniel B., Adler, Darin B.
• Primary Examiner(s): Donabed, Ninos
• Application Number:
  US16/108,576
• Publication Number:
  US 20190028423A1
• Time in Patent Office: 657 Days
• Field of Search: None
• CPC Class Codes: H04L 51/56 Unified messaging, e.g. interactions between e-mail, instant messaging or converged IP messaging [CPM]
• CPC Class Codes: H04L 51/58 Message adaptation for wireless communication
• CPC Class Codes: H04L 67/06 specially adapted for file transfer, e.g. file transfer protocol [FTP]
• CPC Class Codes: H04L 67/55 Push-based network services

Abstract

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.

Claims

1. A method of data transfer from a mobile device to a wearable device, the method comprising, at the mobile device:

receiving, by an accessory communications daemon of the mobile device, an information message from a first mobile application, the information message comprising application information intended for an accessory application of the wearable device, wherein the wearable device is paired with the mobile device;

storing, by the accessory communications daemon, the application information in a queue;

determining whether to transmit the application information to the accessory application of the wearable device based on whether the wearable device is in a charging state;

causing transmitting, by the mobile device, of the application information to the accessory application of the wearable device based on the wearable device being in the charging state and being reachable;

pausing transmission of the application information based on a first threshold period of time elapsing since a beginning of the transmission;

transmitting the application information is based on the wearable device being in the charging state or causing the application information to remain in the queue occurs after pausing transmission of the application information; and

causing the application information to remain in the queue after pausing of the application information;

determining whether a data size of the application information is below a predetermined size limit, wherein causing the application information to be transmitted or remain in the queue is further based on whether the data size of the application information is below the predetermined size limit.

2. The method of claim 1, further comprising:

determining whether the accessory application is active on the wearable device, wherein causing the application information to be transmitted or remain in the queue is further based on determining whether the accessory application is active on the wearable device.

3. The method of claim 1, further comprising:

determining that a second threshold time has elapsed since pausing, wherein causing the application information to be transmitted or remain in the queue is further based on determining whether the second threshold time has elapsed since pausing.

4. The method of claim 1, wherein the information message comprises a mode identifier that specifies an information type of the information message and a data size of the application information to be transmitted.

5. The method of claim 4, wherein the mode identifier corresponds to a file transfer mode of a plurality of file transfer modes.

6. The method of claim 5, further comprising selecting, by the accessory communications daemon, the file transfer mode from among the plurality of file transfer modes for transferring the information message to the accessory application, wherein the file transfer mode is selected based on the mode identifier of the information message.

7. The method of claim 6, wherein a protocol associated with the file transfer mode specifies a first set of criteria that the wearable device is in the charging state or the application information is below a predetermined size limit.

8. The method of claim 7, wherein different file transfer modes of the plurality of file transfer modes are associated with different protocols that specify different sets of criteria for determining when to transmit received application information.

9. The method of claim 1, further comprising:

subsequently, determining the wearable device is in a non-charging state causing other application information to remain in the queue, thereby preserving an amount of batter power of the wearable device.

10. A computer product comprising a non-transitory computer readable medium storing instructions that, when executed on one or more processors of a mobile device, cause data transfer from the mobile device to a wearable device paired to the mobile device, the instructions comprising:

receiving, by an accessory communications daemon of the mobile device, an information message from a first companion application, the information message comprising application information intended for an accessory application of the wearable device;

storing, by the accessory communications daemon, the application information in a queue;

determining whether to transmit the application information to the accessory application of the wearable device based on whether the wearable device is in a charging state;

causing transmitting, by the mobile device, of the application information to the accessory application of the wearable device based on the wearable device being in the charging state and being reachable;

pausing transmission of the application information based on a first threshold period of time elapsing since a beginning of the transmission;

transmitting the application information is based on the wearable device being in the charging state or causing the application information to remain in the queue occurs after pausing transmission of the application information; and

causing the application information to remain in the queue after pausing of the application information;

determining whether a data size of the application information is below a predetermined size limit, wherein causing the application information to be transmitted or remain in the queue is further based on whether the data size of the application information is below the predetermined size limit.

11. The computer product of claim 10, the instructions further comprising:

determining whether the accessory application is active on the wearable device, wherein causing the application information to be transmitted or remain in the queue is further based on determining whether the accessory application is active on the wearable device.

12. The computer product of claim 10, the instructions further comprising:

determining that a second threshold time has elapsed since pausing, wherein causing the application information to be transmitted or remain in the queue is further based on determining whether the second threshold time has elapsed since pausing.

13. The computer product of claim 10, wherein the information message comprises a mode identifier that specifies an information type of the information message and a data size of the application information to be transmitted.

14. The computer product of claim 13, wherein the mode identifier corresponds to a file transfer mode of a plurality of file transfer modes.

15. The computer product of claim 14, further comprising selecting, by the accessory communications daemon, the file transfer mode from among the plurality of file transfer modes for transferring the information message to the accessory application, wherein the file transfer mode is selected based on the mode identifier of the information message.

16. The computer product of claim 15, wherein a protocol associated with the file transfer mode specifies a first set of criteria that the wearable device is in the charging state or the application information is below a predetermined size limit.

17. A mobile device comprising:

a display;

a memory;

one or more processors that are communicably coupled with the display and the memory and that are configured to;

receive, by an accessory communications daemon of the mobile device, an information message from a first companion application, the information message comprising application information intended for an accessory application of a wearable device paired to the mobile device;

store, by the accessory communications daemon, the application information in a queue;

determine whether to transmit the application information to the accessory application of the wearable device based on whether the wearable device is in a charging state;

cause transmission, by the mobile device, of the application information to the accessory application of the wearable device based on the wearable device being in the charging state and being reachable; and

pause transmission of the application information based on a first threshold period of time elapsing since a beginning of the transmission;

transmit the application information is based on the wearable device being in the charging state or causing the application information to remain in the queue occurs after pausing transmission of the application information; and

causing the application information to remain in the queue after pausing of the application information;

determining whether a data size of the application information is below a predetermined size limit, wherein causing the application information to be transmitted or remain in the queue is further based on whether the data size of the application information is below the predetermined size limit.