Updating control software on a network-connected HVAC controller

• US 10,387,136 B2
• Filed: 11/12/2014
• Issued: 08/20/2019
• Est. Priority Date: 09/30/2012
• Status: Active Grant

• Current Assignee: Google LLC (Alphabet Inc.)
• Original Assignee: Google LLC (Alphabet Inc.)
• Inventors: Gourlay, Alastair R., Bourne, David A., Erickson, Grant M., Schultz, Richard J., Sloo, David, Solnit, Jonathan
• Primary Examiner(s): Nguyen, Mongbao
• Application Number:
  US14/539,398
• Publication Number:
  US 20150074658A1
• Time in Patent Office: 1,742 Days
• CPC Class Codes: F22B 3/00 Other methods of steam generation; Steam boilers not provided for in other groups of this subclass
• CPC Class Codes: F24F 11/30 for purposes related to the operation of the system, e.g. for safety or monitoring
• CPC Class Codes: F24F 11/46 Improving electric energy efficiency or saving
• CPC Class Codes: F24F 11/523 for displaying temperature data
• CPC Class Codes: F24F 11/58 using Internet communication
• CPC Class Codes: F24F 11/62 characterised by the type of control or by internal processing, e.g. using fuzzy logic, adaptive control or estimation of values
• CPC Class Codes: F24F 11/63 Electronic processing
• CPC Class Codes: G05B 15/02 electric
• CPC Class Codes: G05B 2219/23306 Load program from host, remote load, non volatile card to volatile, ram
• CPC Class Codes: G05B 2219/2614 HVAC, heating, ventillation, climate control
• CPC Class Codes: G06F 8/61 Installation
• CPC Class Codes: G06F 8/65 Updates security arrangements therefor G06F21/57
• CPC Class Codes: G06F 9/44 Arrangements for executing specific programs
• CPC Class Codes: H04L 67/01 Protocols
• CPC Class Codes: H04L 67/025 for remote control or remote monitoring of applications
• CPC Class Codes: H04L 67/12 specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
• CPC Class Codes: H04L 67/34 involving the movement of software or configuration parameters network booting or remote initial program loading [RIPL] G06F9/4416

Abstract

Apparatus, systems, methods, and computer program products are disclosed for providing software updates to client devices. A client device (such as a thermostat) executes software to perform one or more functionalities of the device. Upon receiving an indicating that a software update is available, the device waits to download the software update until pre-download conditions are satisfied. Once the software update is downloaded, the device then waits to install the software update until pre-install conditions are satisfied. If the software update is non-critical and received during an initial installation of the device, the software update may not be installed until after installation of the device is complete. If the device is a thermostat, the device may delay installation of the software update until a controlled HVAC system in inactive. Control of the HVAC system may be disabled during installation of the software update.

Claims

1. A machine-implementable method for updating software on a client device from a remote server, comprising:

receiving a device identifier for the client device at a registration server;

determining, by the registration server, a software version identifier that corresponds to an appropriate software version to provide to the client device;

determining, by the registration server, a server address for a software update server that can provide the appropriate software version;

transmitting, by the registration server, the software version identifier, credentials that authorize the software update server to communicate with the client device, and the server address to the client device;

receiving the credentials and a request for the appropriate software version at the software update server;

determining that the credentials authorize the software update server to communicate with the client device; and

transmitting the appropriate software version from the software update server to the client device.

2. The machine-implementable method for updating software on a client device of claim 1, wherein the registration server and the software update server that can provide the appropriate software version are different servers in communication with one another.

3. The machine-implementable method for updating software on a client device of claim 1, wherein the registration server and the software update server that can provide the appropriate software version are the same server.

4. The machine-implementable method for updating software on a client device of claim 1, further comprising transmitting an update criticality indicator to the client device with the software version identifier and the server address.

5. The machine-implementable method for updating software on a client device of claim 4, wherein the criticality indicator indicates whether installation of the appropriate software version is allowed to interrupt an initial setup of the client device.

6. The machine-implementable method for updating software on a client device of claim 1, wherein determining the software version identifier comprises determining a software version identifier for a software package that will entirely replace software executing on the client device.

7. The machine-implementable method for updating software on a client device of claim 1, wherein determining the software version identifier comprises determining a device type of the client device, and determining the appropriate software version based on the device type.

8. The machine-implementable method for updating software on a client device of claim 7, wherein:

determining the device type of the client device comprises determining that the client device comprises a first component and a second component; and

determining the appropriate software version based on the device type comprises determining one or both of a first software version required by the first component and a second software version required by the second component.

9. The machine-implementable method for updating software on a client device of claim 8, wherein the first component is a back plate, and the second component is a head unit.

10. The machine-implementable method for updating software on a client device of claim 1, further comprising:

determining, by the registration server, a synchronization server configured to synchronize information at the client device with information stored in a storage element of the remote server; and

transmitting a synchronization server address for the synchronization server to the client device.

11. The machine-implementable method for updating software on a client device of claim 10, further comprising:

connecting the synchronization server with the client device; and

synchronizing the information at the client device with information stored in the storage element of the remote server.

12. The machine-implementable method for updating software on a client device of claim 11, further comprising:

identifying a user account associated with the client device;

identifying one or more additional devices that are associated with the user account; and

synchronizing information at one of the additional devices with information stored in the storage element of the remote server.

13. A software product, comprising instructions stored in non-transitory computer-readable storage media, wherein the instructions, when executed by one or more processors, perform steps of the machine-implementable method of claim 1.

14. A remote server for updating software on a client device, comprising:

a registration server configured to;

receive device identifiers from a plurality client devices, and for each device identifier thus received;

determine a software version identifier of an appropriate software version for the corresponding client device,

determine a server address for a software update server that can provide the appropriate software version; and

transmit the software version identifier, credentials that authorize the software update server to communicate with the client device, and the server address to the client device; and

the software update server, configured to;

receive the credentials and upgrade requests from a plurality of client devices, and for each upgrade request thus received;

determine that the credentials authorize the software update server to communicate with the client device; and

transmit the appropriate software version to the corresponding client device.

15. The remote server of claim 14, the registration server being further configured to transmit an update criticality indicator, with the software version identifier and the server address, to the corresponding client device.

16. The remote server of claim 14, the registration server being further configured to determine whether the software version required by the corresponding client device is a replacement version or an incremental upgrade.

17. The remote server of claim 14, wherein the remote server is a distributed computing entity that includes at least the registration server and the software update server.

18. The remote server of claim 14, the registration server being further configured to determine a device type of the corresponding client device, and to determine the appropriate software version based on the device type.

19. The remote server of claim 18, the registration server being further configured to

determine the device type of the corresponding client device as comprising a first component and a second component;

and

determining one or both of a first software version required by the first component and a second software version required by the second component.

20. The remote server of claim 14, further comprising

a storage element;

and

a synchronization server configured to synchronize information at the client device with information stored in the storage element;

and wherein;

the registration server is further configured to transmit a synchronization server identifier for the synchronization server to the corresponding client device.

21. The remote server of claim 20, wherein the registration server is further configured to identify:

a user account associated with the corresponding client device, and

one or more additional devices that are associated with the user account;

and wherein the synchronization server is further configured to synchronize information at one of the additional devices with information stored in the storage element.