Operating system replacement for in-vehicle computing system

• US 9,910,660 B2
• Filed: 08/04/2014
• Issued: 03/06/2018
• Est. Priority Date: 08/05/2013
• Status: Active Grant

• Current Assignee: Harman International Industries Incorporated (Samsung Electronics Co. Ltd.)
• Original Assignee: Harman International Industries Incorporated (Samsung Electronics Co. Ltd.)
• Inventors: Muench-Casanova, Stephen, Beets, Paul, Bolinger, Brian, Klochko, Alexander, Montealegre, Steven Edward
• Primary Examiner(s): MORSHED, HOSSAIN M
• Application Number:
  US14/451,296
• Publication Number:
  US 20150040113A1
• Time in Patent Office: 1,310 Days
• Field of Search: 717168, 717171, 717172, 717173
• CPC Class Codes: G06F 8/65 Updates security arrangements therefor G06F21/57
• CPC Class Codes: G06F 9/4406 Loading of operating system

Abstract

Embodiments are disclosed for a method of replacing an original operating system with a new operating system. In one example embodiment, a method to selectively replace a first in-vehicle operating system includes receiving a temporary update including a second in-vehicle operating system for storage in a memory location of the first in-vehicle operating system and receiving a request to update the first in-vehicle operating system based on the temporary update. The method may further include triggering a reboot of the first in-vehicle operating system including installing the second in-vehicle operating system.

Claims

1. A method to selectively replace a first in-vehicle operating system of an in-vehicle computing system of a vehicle, the method comprising:

receiving a temporary update including a second in-vehicle operating system for storage in a first memory location of a storage device of the first in-vehicle operating system;

receiving a script comprising instructions in a language supported by the first in-vehicle operating system to store an image file system (IFS) for the second in-vehicle operating system and initial program loader (IPL) files for the second in-vehicle operating system onto the storage device of the in-vehicle computing system, wherein one or more components of the IFS file is compressed using one or more compression levels;

receiving a request to update the first in-vehicle operating system based on the temporary update;

triggering a reboot of the first in-vehicle operating system responsive to receiving the request to update the first in-vehicle operating system; and

after performing the reboot of the first in-vehicle operating system, automatically loading the script and moving one or more files from the temporary update from the first memory location to a second memory location of the storage device, the second memory location being different from the first memory location and the second memory location being specified by a processor of the in-vehicle computing system to be a boot sector location from which the system reboots in order to run the second in-vehicle operating system, wherein loading of the IFS file is performed in order of the compression levels of the components of the IFS file.

2. The method of claim 1, further comprising automatically restarting under the second in-vehicle operating system following installing the second in-vehicle operating system responsive to a state of the vehicle.

3. The method of claim 1, wherein the boot sector location comprises a master boot record and/or sector, and wherein the script includes binaries for installing the second in-vehicle operating system, the binaries including a driver that performs an internal storage device write or rewrite to store the IFS and IPL files for the second in-vehicle operating system.

4. The method of claim 1, wherein receiving the request to update the first in-vehicle operating system based on the temporary update triggers loading an internal memory rewrite driver.

5. The method of claim 1, wherein receiving the request to update the first in-vehicle operating system based on the temporary update triggers loading a user mode driver initialization application for the second in-vehicle operating system where the user mode driver initialization application is added to an auto-start list for the first in-vehicle operating system.

6. The method of claim 5, further comprising resetting one or more watchdog timers in response to receiving or running the user mode driver initialization application prior to expiration of the one or more watchdog timers.

7. The method of claim 1, further comprising copying user preferences in the first in-vehicle operating system to a third memory location for use by the second in-vehicle operating system.

8. A method of replacing an original operating system with a new operating system for an in-vehicle computing system, the method comprising:

receiving an image file system (IFS) and initial program loader (IPL) files for the new operating system at an external storage device interface of the in-vehicle computing system during operation of the in-vehicle computing system under the original operating system, one or more files for the original operating system being stored at a boot sector location of the in-vehicle computing system, the boot sector location specifying a location from which the in-vehicle computing system reboots;

receiving a binary script comprising instructions in a language supported by the original operating system to store the IFS for the new operating system and the IPL files for the new operating system onto a storage device of the in-vehicle computing system, wherein one or more components of the IFS file is compressed using one or more compression levels;

storing the IFS and the IPL files in a first memory location of the in-vehicle computing system;

rebooting the in-vehicle computing system while operating under the original operating system, the rebooting including shutting down the in-vehicle computing system and restarting the in-vehicle computing system to the original operating system by accessing and reading from the boot sector location;

after rebooting the in-vehicle computing system, automatically loading the binary script and moving the IFS and the IPL files for the new operating system from the first memory location of the storage device to a second memory location of the storage device, the second memory location being different from the first memory location and comprising the boot sector location such that one or more of the IPL files for the new operating system replaces the one or more files for the original operating system stored at the boot sector location; and

after moving the IFS and the IPL files for the new operating system, rebooting the in-vehicle computing system while operating under the original operating system, the rebooting including shutting down the in-vehicle computing system and automatically restarting the in-vehicle computing system under the new operating system by accessing and reading from the boot sector location, wherein loading of the IFS file is performed in order of the compression levels of the components of the IFS file.

9. The method of claim 8, further comprising, while operating under the original operating system, locating user preferences in the storage device of the in-vehicle computing system and copying the user preferences to a known memory location of the in-vehicle computing system.

10. The method of claim 9, further comprising, while operating under the new operating system, restoring the user preferences stored in the known memory location of the in-vehicle computing system.

11. The method of claim 8, wherein storing the IFS and the IPL files in the first memory location of the in-vehicle computing system includes loading a script from an external storage device including binaries for an application.

12. The method of claim 11, wherein the binaries include a driver that performs an internal memory rewrite to store the IFS and the IPL files in the first memory location, and wherein the IFS is divided into a low level compressed IFS and a high level compressed IFS, the low level compressed IFS being loaded before the high level compressed IFS.

13. The method of claim 12, wherein the binaries include a user mode application that initializes the driver.

14. The method of claim 13, wherein the user mode application is added to an auto-start list for the original operating system, the auto-start list including applications that are run automatically responsive to starting the original operating system.

15. The method of claim 14, wherein the user mode application is configured to service one or more watchdog timers of the in-vehicle computing system by resetting the one or more watchdog timers before the one or more watchdog timers expire, the watchdog timers being serviced while the original operating system is replaced with the new operating system.

16. The method of claim 8, wherein moving the IFS and the IPL files from the first memory location to the second memory location includes writing a compressed form of the IFS and IPL files to the second memory location comprising the boot sector location, wherein the boot sector location comprises a master boot record and/or sector, and wherein the master boot record and/or sector determines a boot loading sequence for the in-vehicle computing system.

17. The method of claim 16, further comprising decompressing the IPL files and copying the IFS from a first sector to a second sector.

18. The method of claim 17, further comprising restarting the in-vehicle computing system while operating under the new operating system and copying application binaries into the storage device of the in-vehicle computing system.

19. An in-vehicle computing system comprising:

an audio device interface for communicating with one or more audio devices of a vehicle;

a storage device;

an external device interface;

a memory device configured to store instructions; and

a processor configured to execute the instructions to;

receive an image file system (IFS) and initial program loader (IPL) files at the external device interface during operation of the in-vehicle computing system under an original operating system;

install an application for installing a new operating system within the original operating system, the application comprising a binary script including instructions in a language supported by the original operating system to store the IFS and the IPL files for the new operating system onto the storage device of the in-vehicle computing system, wherein one or more components of the IFS file is compressed using one or more compression levels;

determine whether an operating system replacement is allowed based on one or more of a state of the vehicle and a presence of a user in the vehicle;

responsive to determining that the operating system replacement is allowed, reboot the in-vehicle computing system to the original operating system while operating under the original operating system;

after rebooting the in-vehicle computing system, run the application to rewrite the IFS and the IPL files from a first memory location to a second memory location, the first memory location being different from the second memory location, and the second memory location being specified by the processor as a location from which the in-vehicle computing system reboots; and

after rewriting the IFS and the IPL files, reboot the in-vehicle computing system to the new operating system while operating under the original operating system, rebooting the in-vehicle computing system to the new operating system including automatically restarting the in-vehicle computing system under the new operating system, wherein loading of the IFS file is performed in order of the compression levels of the components of the IFS file.

20. The in-vehicle computing system of claim 19, wherein the processor includes a first processor for controlling operation of an operating system and a human-machine interface of the in-vehicle computing system and a second processor for controlling power to the in-vehicle computing system and communication between the in-vehicle computing system and other elements of the vehicle, and wherein the second memory location comprises a boot sector location including a master boot record and/or sector.