SUBSYSTEM FOR A VEHICLE AND CORRESPONDING VEHICLE

• US 20160259639A1
• Filed: 02/24/2016
• Published: 09/08/2016
• 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
• Granted Patent: US 10,007,504 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• 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 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 download client 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.

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

at least one device management client for managing a device of the vehicle; and

a device management client for guiding the device management, which is connected to the vehicle update client and to a device management server of the back-end via the air interface.

3. The subsystem as recited in claim 1 further comprising:

at least one device management client for managing a device of the vehicle.

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

device management agents connected to the device management client.

5. 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.

6. 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.

7. The subsystem as recited in claim 6, 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.

8. The subsystem as recited in claim 7, 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.

9. The subsystem as recited in claim 8, 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.

10. The subsystem as recited in claim 8, 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.

11. The subsystem as recited in claim 9, 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.

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

a device management client 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 download client 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.