Software update method, apparatus and system

• US 20050055595A1
• Filed: 09/17/2002
• Published: 03/10/2005
• Est. Priority Date: 09/17/2001
• Status: Abandoned Application

• Current Assignee: Quarterhill Inc. (f/k/a Wi-LAN Inc.)
• Original Assignee: Wi-LAN Inc.
• Inventors: Frazer, Mark, Rivard, Philippe A.
• Application Number:
  US10/489,777
• Publication Number:
  US 20050055595A1
• Time in Patent Office: Days
• US Class Current: 713/400
• CPC Class Codes: G06F 11/1417 Boot up procedures
• CPC Class Codes: G06F 11/1433 during software upgrading
• CPC Class Codes: G06F 8/654 using techniques specially adapted for alterable solid state memories, e.g. for EEPROM or flash memories
• CPC Class Codes: G06F 9/4401 Bootstrapping security arrangements therefor G06F21/57

Abstract

A system for remotely updating software on at least one electronic device connected to a network. The electronic devices have a non-volatile rewritable storage unit divided into at least two partitions, one of which will contain core firmware and the other of which will contain auxiliary software. When an update is received at the device, the updated core firmware is written to overwrite the partition in the rewritable storage unit that contained the auxiliary software. When this is completed and verified, the previous version of the core firmware stored in the storage unit is disabled from execution by the device. Next, the updated auxiliary software is written to overwrite the old version of the core firmware. When this write is complete, the device determines a suitable time for it to be rebooted to execute the updated software. In another embodiment, the present core firmware in the device is copied from the partition it is in to the other partition, overwriting the auxiliary software stored there. The new core firmware received to update the device is overwritten into the first partition, the old copied core firmware being present in case of an upgrade failure, and upon a successful update of the first partition, the auxiliary software is written to the second partition, overwriting the copied old core firmware. In this manner, the position of the core firmware and auxiliary software within the partitions is preserved during normal operation of the device.

Claims

1. A method of updating software in a plurality of remote devices each of which has insufficient non-volatile rewritable storage capacity to store both an updated and a previous version of the software and each of which is connected to a network, comprising the steps of:

(i) placing the update onto an update server, the update comprising at least a core firmware update;

(ii) identifying the devices connected to the network to be updated;

(iii) transferring the update from the update server to the identified devices through the network, each identified device verifying the reception of the update, requesting retransmission of and receiving any previously incorrectly received portion of the update;

(iv) writing the core firmware portion of the received update into a non-volatile rewritable storage unit so as not to overwrite the previous version of the core firmware that is present in the storage unit;

(v) verifying the core firmware portion of the received update written into the storage unit;

(vi) identifying the verified updated core firmware as being the valid core firmware to be used by the device and identifying the previous version of the core firmware as being unusable; and

(vii) rebooting the device to load and execute the updated software.

2. The method of claim 1 wherein, between steps (iii) and (iv), the previous version of the core firmware is copied over auxiliary software stored in the storage unit and verified, the copy identified as the valid core firmware to be used by the device and the original identified as being unusable.

3. The method of claim 2 wherein the update further includes updated auxiliary software and the auxiliary software is received and verified by the device and wherein, between steps (vi) and (vii), the unusable previous version of the core firmware is overwritten with the auxiliary software update.

4. The method of claim 1 wherein the update further includes updated auxiliary software and the auxiliary software is received and verified by the device and wherein, between steps (vi) and (vii), the unusable previous version of the core firmware is overwritten with the auxiliary software update.

5. The method of claim 1, wherein step (ii) also comprises the device informing the network whether or not it is available to be updated.

6. A system for remotely updating core firmware in at least one electronic device across a communications link, the system comprising

a memory sub-system within the at least one electronic device including:

non-volatile rewritable memory in which the core firmware is stored and which is sufficiently large to store auxiliary software but not large enough to simultaneously store the core firmware, an updated version of the core firmware, and the auxiliary software, the core firmware including instructions for

writing an updated version of the core firmware into the non-volatile rewritable memory so as not to overwrite the previous version of the core firmware, and then

disabling the previous version of the core firmware such that on rebooting of the at least one electronic device the updated version of the core firmware will be loaded and executed; and

an update server, operable to transfer an update to the at least one electronic device across the communications link, the update comprising the updated version of the core firmware.

7. The system of claim 6, wherein the core firmware includes instructions for writing an updated version of the auxiliary software into the non-volatile rewritable memory so as to overwrite at least a portion of the disabled previous version of the core firmware, but not to overwrite the updated version of the core firmware.

8. The system of claim 7, wherein the memory sub-system additionally comprises:

non-volatile memory including instructions that are executed when the electronic device reboots and cause the non-volatile rewritable memory to be scanned for a version of the core firmware that is not disabled and that version of the core firmware to be loaded and executed.

12. The system as claimed in claim 6, wherein writes to the non-volatile rewritable memory are verified.

13. The system as claimed in claim 12 wherein the update client is further operable to inform the update server as to whether the at least one electronic device is available for updating at a given time, the update server being responsive to the information received from the update client to delay updates to the electronic device when the electronic device is not available for updating.

14. The system as claimed in claim 13 wherein the update server can prioritize an update such that the update client will make the electronic device available for the update that would otherwise be unavailable.

9. (Cancelled)

10. (Cancelled)

11. (Cancelled)

15. A memory sub-system for use in an electronic device, comprising:

non-volatile rewritable memory in which core firmware and auxiliary software are stored, the core firmware including instructions for

writing an updated version of the core firmware into the non-volatile rewritable memory so as to overwrite at least a portion of the auxiliary software, but not to overwrite the previous version of the core firmware,

verifying the updated version of the core firmware, and

disabling the previous version of the core firmware such that on rebooting of the electronic device the updated version of the core firmware will be loaded and executed.

17. The memory sub-system of claim 15, wherein the core firmware includes instructions for writing an updated version of the auxiliary software into the non-volatile rewritable memory so as to overwrite at least a portion of the disabled previous version of the core firmware, but not to overwrite the updated version of the core firmware.

18. The memory sub-system of claim 17, additionally comprising:

non-volatile memory including instructions that are executed when the electronic device reboots and cause

the non-volatile rewritable memory to be scanned for a version of the core firmware that is not disabled and

the version of the core firmware that is not disabled to be loaded and executed.

16. (Cancelled)

19. (Cancelled)

20. (Cancelled)

21. (Cancelled)

22. A method of updating core firmware stored in non-volatile rewritable memory of an electronic device together with auxiliary software with an updated version of the core firmware, comprising the steps of:

(i) writing the updated version of the core firmware into the non-volatile rewritable memory so as to overwrite at least a portion of the auxiliary software, but not to overwrite the previous version of the core firmware; and

(ii) disabling the previous version of the core firmware such that on rebooting of the electronic device the updated version of the core firmware will be loaded and executed.

24. The method of claim 22, wherein when the electronic device is rebooted, the non-volatile rewritable memory is scanned for a version of the core firmware that is not disabled and that version of the core firmware is then loaded and executed.

23. (Cancelled)

25. (Cancelled)

26. A system for remotely updating at least one electronic device across a communications link, where said system comprises:

an update server, operable to transfer an update to the at least one electronic device across the communications link, the update comprising core firmware and auxiliary software;

a volatile memory to temporarily store the transfer received from the update server;

a non-volatile re-writable storage unit within said at least one electronic device divided into at least first and second partitions, the first partition storing one of a version of core firmware and auxiliary software and the second of the partitions storing the other of a version of core firmware and auxiliary software; and

an update client executing on the device and operable;

(i) to overwrite the version of the auxiliary software stored in one of the first and second partitions with the received updated core firmware stored in the volatile memory and to verify the success of this write;

(ii) to configure the device to execute the core firmware stored in (i) upon the next reboot of the device;

(iii) to overwrite the version of the core firmware stored in the other of the first and second partition with the received updated auxiliary software store in the volatile memory and to verify the success of this write; and

(iv) to reboot the device to execute the updated core firmware and updated auxiliary software.

27. The system as claimed in claim 26 wherein said update client is further operable to inform the update server as to whether the device is available for updating at a given time, the update server being responsive to the information received from the update server to delay updates to the device when the device is not available for updating.

28. The system as claimed in claim 27 wherein the update server can prioritize an update such that the update client will make a device available for the update that would otherwise be unavailable.