Device for the reliable integration of a software component into a motor vehicle

Patent metadata

Field	Value
Publication number	US-9710290-B2
Application number	US-201514717828-A
Country	US
Kind code	B2
Filing date	May 20, 2015
Priority date	May 20, 2014
Publication date	Jul 18, 2017
Grant date	Jul 18, 2017

Abstract

A coupling device for coupling a software component, which transmits a setting command for setting an actuator on a control system of a motor vehicle, to the control system, the coupling device including a monitoring unit, which is designed to carry out an assessment for each setting command as to whether its implementation will transfer the motor vehicle into a dangerous state, the coupling device being further designed to transmit, as a function of this assessment, a monitored setting command corresponding to the setting command to an implementation unit, the implementation unit being designed to control the actuator.

First claim

What is claimed is:

1. A coupling device for coupling a software component to a control system of a motor vehicle to control a setting of an actuator by the control system, the coupling device comprising:
a monitoring unit that is configured to:
obtain, via an application program interface, a setting command generated by an on-board processor of the control system of the motor vehicle executing the software component;
assess the setting command as to whether an implementation of the setting command will transfer the motor vehicle into a dangerous state;
generate, as a function of the assessment, a monitored setting command corresponding to the obtained setting command; and
pass the generated monitored setting command to the on-board processor to control the actuator based on the monitored setting.

2. The coupling device as recited in claim 1 , wherein the monitored setting command is set to be the same as the obtained setting command if the assessment is that the implementation of the obtained setting command does not transfer the motor vehicle into the dangerous state.

3. The coupling device as recited in claim 1 , wherein the monitored setting command is set to be different than the obtained setting command if the assessment is that the implementation of the obtained setting command transfers the motor vehicle into the dangerous state.

4. The coupling device as recited in claim 3 , wherein the monitored setting command is selected so that an implementation of the monitored setting command does not transfer the motor vehicle into the dangerous state.

5. The coupling device as recited in claim 3 , wherein the monitored setting command represents a limitation of the obtained setting command.

6. The coupling device as recited in claim 1 , wherein the monitoring unit is configured to respond to the assessment being that the implementation of the obtained setting command transfers the motor vehicle into the dangerous state by not passing any setting command for control of the actuator based on the obtained setting command.

7. The coupling device as recited in claim 1 , wherein the monitoring unit is configured to carry out the assessment as a function of an ascertained driving situation.

8. The coupling device as recited in claim 1 , wherein the monitoring unit carries out a prediction of variables that describe dynamics of the motor vehicle, and carries out the assessment as a function of values of the variables.

9. The coupling device as recited in claim 1 , further comprising a management unit for checking, before an installation of the software component, whether a correct installation of the software component is possible.

10. The coupling device as recited in claim 9 , wherein the management unit assigns a storage area in a working memory to the software component, and connects the software component to the application program interface.

11. The coupling device as recited in claim 1 , wherein the monitoring unit is configured to compare a value of the obtained setting command to a limit value, and, responsive to determining that the value of the obtained setting command does not meet the limit value, modify the value to satisfy the limit value, the modified value being used for the monitored setting command.

12. A control system of, and on board, a motor vehicle comprising:
an interface;
a data storage; and
a processor;
wherein the processor is configured to:
receive, via the interface and from off board the vehicle, a new software component;
store the received software component locally in the data storage;
execute the stored software component using an application program interface to obtain a setting command;
execute a monitoring function to:
assess the setting command as to whether an implementation of the setting command will transfer the motor vehicle into a dangerous state; and
generate, as a function of the assessment, a monitored setting command corresponding to the obtained setting command; and

execute actuator controlling software to control an actuator based on the monitored setting.

Assignees

• Bosch Gmbh Robert

Inventors

• Haenger Jochen Ulrich
• Schweizer Markus
• Gebauer Carsten
• Mueller Bernd
• Lasarczyk Christian
• Heinz Thomas
• Amarnath Rakshith

Classifications

• G06F21/53

  by executing in a restricted environment, e.g. sandbox or secure virtual machine · CPC title

• B60R16/02 Primary

  electric {constitutive elements} · CPC title

• G06F2201/865

  Monitoring of software · CPC title

• G05B9/02

  electric · CPC title

• G06F11/302

  where the computing system component is a software system · CPC title