MULTIPLE CHUNK SOFTWARE UPDATES

• US 20150286475A1
• Filed: 04/02/2014
• Published: 10/08/2015
• Est. Priority Date: 04/02/2014
• Status: Active Grant

• Current Assignee: Ford Global Technologies, LLC (Ford Motor Company)
• Original Assignee: Ford Global Technologies, LLC (Ford Motor Company)
• Inventors: PETERSEN, Brian, PANDYA, Ritesh, YALAVARTY, Praveen, VANGELOV, John
• Granted Patent: US 10,140,110 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06F 8/65 Updates security arrangements therefor G06F21/57
• CPC Class Codes: G06F 8/71 Version control security arrangements therefor G06F21/57; Configuration management

Abstract

A system may include a vehicle-based computing system. The vehicle-based computing system may identify from a first software update chunk retrieved from a subscribed topic for receiving vehicle updates, a number of chunks of the update, retrieve additional chunks of the update by subscription to each of a sequence of subtopics to the subscribed topic, each subtopic associated with a respective remaining one of the number of chunks, and update the software utilizing the retrieved chunks.

Claims

1. A system, comprising:

a vehicle-based computing system configured to

identify, from a first software update chunk retrieved from a subscribed topic for receiving vehicle updates, a number of chunks of the update,

retrieve additional chunks of the update by subscription to each of a sequence of subtopics to the subscribed topic, each subtopic associated with a respective remaining one of the number of chunks, and

update the software utilizing the retrieved chunks.

2. The system of claim 1, wherein the vehicle-based computing system is further configured to identify the number of chunks according to a number-of-chunks field included in header information of the retrieved first software update chunk.

3. The system of claim 1, wherein the vehicle-based computing system is further configured to subscribe to the topic for receiving vehicle updates upon receiving an update notification in one of:

(i) a subscribed topic for receiving notification of updates associated with a software version installed to the vehicle and (ii) a subscribed topic for receiving notifications of updates associated with a unique identifier of the vehicle.

4. The system of claim 3, wherein the update notification specifies a notification configuration file, and the vehicle-based computing system is further configured to determine a desired software version according to a version level of the software with which the configuration file indicates it is compatible.

5. The system of claim 4, wherein the vehicle-based computing system is further configured to:

install a default configuration file for version of the software of the software utilizing the retrieved chunks, and

upon performing the update of the software utilizing the retrieved chunks, install the notification configuration file in place of the default configuration file.

6. The system of claim 1, wherein the software update is configured to update a telematics unit of the vehicle.

7. The system of claim 1, wherein the vehicle-based computing system is further configured to unsubscribe to subscribed topic for receiving vehicle updates and each of the sequence of subtopics to the subscribed topic upon performing the update of the software utilizing the retrieved chunks.

8. A method comprising:

identifying by a computing system of a vehicle, from a retrieved first software update chunk retrieved from a subscribed topic for receiving vehicle updates, a number of chunks of the update;

retrieving additional chunks of the update by subscription to each of a sequence of subtopics to the subscribed topic, each subtopic associated with a respective remaining one of the number of chunks; and

updating the software utilizing the retrieved chunks.

9. The method of claim 8, further comprising identifying the number of chunks according to a number-of-chunks field included in header information of the retrieved first software update chunk.

10. The method of claim 8, further comprising subscribing to the topic for receiving vehicle updates upon receiving an update notification in one of:

(i) a subscribed topic for receiving notification of updates associated with a software version installed to the vehicle and (ii) a subscribed topic for receiving notifications of updates associated with a unique identifier of the vehicle.

11. The method of claim 10, wherein the update notification specifies a notification configuration file, and further comprising determining a desired software version according to a version level of the software with which the configuration file indicates it is compatible.

12. The method of claim 11, further comprising:

installing a default configuration file for version of the software of the software utilizing the retrieved chunks, and

upon performing the update of the software utilizing the retrieved chunks, installing the notification configuration file in place of the default configuration file.

13. The method of claim 8, further comprising applying the software update to a telematics unit of the vehicle.

14. The method of claim 8, further comprising unsubscribing to subscribed topic for receiving vehicle updates and each of the sequence of subtopics to the subscribed topic upon performing the update of the software utilizing the retrieved chunks.

15. A non-transitory computer-readable medium including instructions that when executed by a computing system of a vehicle cause the vehicle to:

identify, from a first software update chunk retrieved from a subscribed topic for receiving vehicle updates, a number of chunks of the update;

retrieve additional chunks of the update by subscription to each of a sequence of subtopics to the subscribed topic, each subtopic associated with a respective remaining one of the number of chunks; and

update the software utilizing the retrieved chunks.

16. The computer-readable medium of claim 15, further including instructions configured to cause the vehicle to identify the number of chunks according to a number-of-chunks field included in header information of the retrieved first software update chunk.

17. The computer-readable medium of claim 15, further including instructions configured to cause the vehicle to subscribe to the topic for receiving vehicle updates upon receiving an update notification in one of:

(i) a subscribed topic for receiving notification of updates associated with a software version installed to the vehicle and (ii) a subscribed topic for receiving notifications of updates associated with a unique identifier of the vehicle.

18. The computer-readable medium of claim 17, wherein the update notification specifies a notification configuration file, and further including instructions configured to cause the vehicle to determine a desired software version according to a version level of the software with which the configuration file indicates it is compatible.

19. The computer-readable medium of claim 18, further including instructions configured to cause the vehicle to:

install a default configuration file for version of the software of the software utilizing the retrieved chunks, and

upon performing the update of the software utilizing the retrieved chunks, install the notification configuration file in place of the default configuration file.

20. The computer-readable medium of claim 15, further including instructions configured to cause the vehicle to unsubscribe to subscribed topic for receiving vehicle updates and each of the sequence of subtopics to the subscribed topic upon performing the update of the software utilizing the retrieved chunks.