Modular subsystem for a vehicle for updating and device management

• US 10,007,504 B2
• Filed: 02/24/2016
• Issued: 06/26/2018
• Est. Priority Date: 03/03/2015
• Status: Active Grant

• Current Assignee: Robert Bosch GmbH
• Original Assignee: Robert Bosch GmbH
• Inventors: Blaschke, Volker, Zymeri, Gafur, Schneider, Klaus, Luebben, Ralf
• Primary Examiner(s): Aponte, Francisco
• Application Number:
  US15/052,743
• Publication Number:
  US 20160259639A1
• Time in Patent Office: 853 Days
• Field of Search: 717173
• CPC Class Codes: G06F 8/65 Updates security arrangements therefor G06F21/57

Abstract

A subsystem for a vehicle includes a device management client for exchanging device, vehicle, and diagnostic as well as software update information, which is connected to a device management server of the back-end via an air interface, a download client for downloading a software update from the back-end into the vehicle, which is connected to a download server of the back-end via an air interface, software update clients for applying the software update, which are connected to the download client and a vehicle update client for coordinating the software update, which is connected to the download client and the software update clients.

Claims

1. A subsystem for a vehicle, comprising:

a device management client, situated in the vehicle, for exchanging device, vehicle, diagnostic and software update information, the device management client being connectable to a device management server of a back-end via an air interface;

a plurality of device management agents, situated in the vehicle, each of the device management agents executing in a different runtime environment relative to the others of the device management agents, each of the device management agents aggregating and channeling device management objects to the device management client;

a download client, situated in the vehicle, for downloading a software update from the back-end into the vehicle, the download client being connectable to a download server of the back-end via an air interface;

software update clients for applying the software update, the software update clients being connectable to the download client; and

a vehicle update client for coordinating the software update, the vehicle update client being connectable to the download client and the software update clients;

wherein the device management client and the download client are separate components relative to one another, and wherein the device management server and the download server are separate components relative to one another.

2. The subsystem as recited in claim 1, wherein the device management client manages a device of the vehicle, and guides the device management, wherein the device management client is connected to the vehicle update client.

3. The subsystem as recited in claim 1, wherein the device management client manages a device of the vehicle.

4. The subsystem as recited in claim 1, further comprising:

at least one content memory for storing the software update; and

a content management for managing the content memory, the content management being connected to the download client, the software update clients and the vehicle update client.

5. The subsystem as recited in claim 1, wherein the software update clients include at least one application software update client and at least one firmware update client.

6. The subsystem as recited in claim 5, further comprising:

a vehicle electronics domain including at least the firmware update client;

an entertainment electronics domain including at least the download client; and

a secured communication connecting the vehicle electronics domain and the entertainment electronics domain.

7. The subsystem as recited in claim 6, further comprising:

at least one embedded system included by the vehicle electronics domain; and

at least one IP-capable system included by the vehicle electronics domain.

8. The subsystem as recited in claim 7, wherein:

the embedded system includes at least one central gateway or an engine control or a driving transmission of the vehicle and is consistent with an open vehicle system architecture;

the IP-capable system includes at least the firmware update client and an entertainment electronics proxy;

the entertainment electronics domain includes a security profile of at least the download client, an application security engine and a vehicle electronics proxy; and

the secured communication connects the entertainment electronics proxy and the vehicle electronics proxy.

9. The subsystem as recited in claim 7, wherein:

the vehicle electronics domain includes an operating system adapted to the vehicle electronics domain, which carries out the entertainment electronics proxy; and

the entertainment electronics domain includes an operating system adapted to the entertainment electronics domain, which carries out the vehicle electronics proxy.

10. The subsystem as recited in claim 8, wherein the entertainment electronics domain further includes a control unit update client carried out by the operating system, which is adapted to the entertainment electronics domain.

11. A vehicle including a subsystem, the subsystem including:

a device management client, situated in the vehicle, for exchanging device, vehicle, diagnostic and software update information, he device management client being connectable to a device management server of a back-end via an air interface;

a download client, situated in the vehicle, for downloading a software update from the back-end into the vehicle, the download client being connectable to a download server of the back-end via an air interface;

a plurality of device management agents, situated in the vehicle, each of the device management agents executing in a different runtime environment relative to the others of the device management agents, each of the device management agents aggregating and channeling device management objects to the device management client;

software update clients for applying the software update, the software update clients being connectable to the download client; and

a vehicle update client for coordinating the software update, the vehicle update client being connectable to the download client and the software update clients;

wherein the device management client and the download client are separate components relative to one another, and wherein the device management server and the download server are separate components relative to one another.