Techniques for firmware updates with accessories

Patent metadata

Field	Value
Publication number	US-2021397436-A1
Application number	US-202117338568-A
Country	US
Kind code	A1
Filing date	Jun 3, 2021
Priority date	Jun 19, 2020
Publication date	Dec 23, 2021
Grant date	—

Abstract

Techniques are provided for updating firmware of an accessory device. An accessory development kit of the accessory device can communicate with an accessory update daemon using a home management daemon of a controller device. Based at least in part on a firmware update policy of the accessory device, the accessory update daemon will check for firmware updates. When firmware updates are available, the accessory update daemon can instruct the home management daemon to stage the update. The home management daemon will notify the accessory development kit to be in a stage mode. The accessory update daemon will download the firmware update and send the firmware update to the accessory development kit of the accessory device using an interface for the secure channel provided by the home management daemon. The accessory device can be a third party accessory device that does not have its own firmware updating application.

First claim

What is claimed is:

1 . A method for applying an asset to an accessory device, the method comprising:
monitoring, by a first controller device, status information of the accessory device; determining, by the first controller device, to send a first offer to the accessory device based at least in part on the status information of the accessory device; receiving, by the first controller device, acceptance of the first offer from the accessory device; receiving, by the first controller device, first asset identifying information identifying first data associated with the asset to send to the accessory device; establishing, by the first controller device, a first connection with the accessory device; sending, by the first controller device, the first data associated with the asset to the accessory device through the first connection; disconnecting, by the first controller device, the first connection with the accessory device and stopping the sending of the first data associated with the asset; monitoring, by the first controller device, the status information of the accessory device; and determining, by the first controller device, that a second controller device is sending second data associated with the asset to the accessory device through a second connection, wherein the second data resumes from an end of the first data sent by the first controller device, wherein the first controller device monitors the status information of the accessory device while the second controller device sends the second data to the accessory device.

2 . The method according to claim 1 , further comprising:
determining, by the first controller device, whether the sending of data associated with the asset to the accessory device is complete; in response to determining that the sending of data associated with the asset to the accessory device is not complete, determining, by the first controller device, whether the second controller device is sending data to the accessory device; in response to determining that the second controller device is not sending data to the accessory device, sending, by the first controller device, a second offer associated with the asset to the accessory device based at least in part on the status information of the accessory device; receiving, by the first controller device, acceptance of the second offer from the accessory device; receiving, by the first controller device, second asset identifying information identifying third data associated with the asset to send to the accessory device, wherein the third data resumes from an end of the second data sent by the second controller device; establishing, by the first controller device, a third connection with the accessory device; and sending, by the first controller device, the third data associated with the asset to the accessory device through the third connection.

3 . The method according to claim 1 , wherein the asset comprises a firmware update.

4 . The method according to claim 1 , wherein the first data comprises a first offset and a first length associated with the asset.

5 . The method according to claim 4 , wherein the second data comprises a second offset and a second length associated with the asset that is different from the first offset and the first length.

6 . The method according to claim 1 , wherein the monitoring the status information of the accessory device comprises determining current status variables of the accessory device.

7 . The method according to claim 6 , wherein the current status variables comprises a current state variable of the accessory device identifying a current state of the accessory device, a current version variable identifying a current version of a firmware on the accessory device, and a staged version variable identifying a version of the firmware staged on the accessory device.

8 . The method according to claim 1 , wherein the first connection comprises a wired or wireless connection.

9 . A method for applying an asset to an accessory device, the method comprising:
monitoring, by a second controller device, status information of the accessory device; determining, by the second controller device, that a first controller device is sending first data associated with the asset to the accessory device through a first connection; determining, by the second controller device, whether the sending of data associated with the asset to the accessory device is complete; in response to determining that the sending of data associated with the asset to the accessory device is not complete, determining, by the second controller device, whether the first controller device is sending data to the accessory device; in response to determining that the first controller device is not sending data to the accessory device, sending, by the second controller device, a first offer associated with the asset to the accessory device based at least in part on the status information of the accessory device; receiving, by the second controller device, acceptance of the first offer from the accessory device; receiving, by the second controller device, first asset identifying information identifying second data associated with the asset to send to the accessory device, wherein the second data resumes from an end of the first data sent by the first controller device; establishing, by the second controller device, a second connection with the accessory device; and sending, by the second controller device, the second data associated with the asset to the accessory device through the second connection.

10 . The method according to claim 9 , further comprising:
disconnecting, by the second controller device, the second connection with the accessory device and stopping the sending of the second data associated with the asset; determining, by the second controller device, whether the sending of data associated with the asset to the accessory device is complete; in response to determining that the sending of the data associated with the asset is not complete, determining, by the second controller device, whether the first controller device is sending data to the accessory device; in response to determining that the first controller device is not sending data to the accessory device, sending, by the second controller device, a second offer associated with the asset to the accessory device based on the status information of the accessory device; receiving, by the second controller device, acceptance of the second offer from the accessory device; receiving, by the second controller device, second asset identifying information identifying third data associated with the asset to send to the accessory device, wherein the third data resumes from an end of the second data sent by the second controller device; establishing, by the second controller device, a third connection with the accessory device; and sending, by the second controller device, the third data associated with the asset to the accessory device through the third connection.

11 . The method according to claim 9 , wherein the asset comprises a firmware update.

12 . The method according to claim 9 , wherein the first data comprises a first offset and a first length associated with the asset.

13 . The method according to claim 12 , wherein the second data comprises a second offset and a second length associated with the asset that is different from the first offset and the first length.

14 . The method according to claim 9 , wherein the monitoring the status information of the accessory device comprises determining current status variables of the accessory device.

Assignees

• Apple Inc

Inventors

• Le Hung Q
• Ashraf Zaka Ur Rehman
• Rauenbuehler Keith W
• Zimmermann Christopher B
• Bisset Keith R
• Ganesan Sivaramachandran
• Lee Wayne A
• Chegondi Praveen
• Coffman Patrick L

Classifications

• G06F9/4411 Primary

  Configuring for operating with peripheral devices; Loading of device drivers · CPC title

• G06F8/65 Primary

  Updates (security arrangements therefor G06F21/57) · CPC title

• G06F8/61

  Installation · CPC title

• G06F9/4418

  Suspend and resume; Hibernate and awake · CPC title

• G06F8/656 Primary

  while running · CPC title