Electronic Control Unit and Method for Specifying a Software Architecture for an Electronic Control Unit

• US 20070271551A1
• Filed: 06/24/2004
• Published: 11/22/2007
• Est. Priority Date: 06/24/2003
• Status: Abandoned Application

• Current Assignee: Robert Bosch GmbH
• Original Assignee: Robert Bosch GmbH
• Inventors: Zurawka, Thomas, Schaeuffele, Joerg
• Application Number:
  US10/561,737
• Publication Number:
  US 20070271551A1
• Time in Patent Office: Days
• US Class Current: 717/120
• CPC Class Codes: G05B 19/042 using digital processors G05B19/05 takes precedence
• CPC Class Codes: G05B 2219/23188 Software independent and dependent of hardware
• CPC Class Codes: G05B 2219/25184 Number of modules interfaces optimized in relation to applications with which to link
• CPC Class Codes: G05B 2219/2637 Vehicle, car, auto, wheelchair

Abstract

An electronic control unit having implemented on it, and made up of components, a software and a plurality of software interfaces, optimized with respect to the exchange of data, for the optional coupling in of a plurality of applications, the software including at least one application-specific software code of a component for each application capable of being coupled in, which is activated when the application is coupled in. The present arrangement also relates to a corresponding method for the specification of a software architecture of an electronic control unit.

Claims

1-11. -11. (canceled)

12. An electronic control unit, comprising:

a software module including software that includes components, wherein;

the software includes a plurality of software interfaces that are optimized with respect to an exchange of data and provided for an optional coupling in of a plurality of applications, and

the software includes at least one application-specific software code of a component for each application capable of being coupled in, the at least one application-specific code being activated when the application is coupled in.

13. The electronic control unit as recited in claim 12, wherein:

the software has a hierarchical layer architecture with respect to a mutual access possibility of the software components, each software component being assigned to a layer.

14. The electronic control unit as recited in claim 13, wherein:

the hierarchical layer architecture implements a separation of hardware-independent software components from hardware-dependent software components.

15. The electronic control unit as recited in claim 12, wherein:

the software interfaces are grouped into “

on board” and

“

off board”

interfaces as a function of the respective applications that may be coupled to them.

16. The electronic control unit as recited in claim 12, wherein:

the software assumes in each case one of several possible operating states, as a function of data present at the software interfaces and therein supports exclusively condition-specific functionalities.

17. The electronic control unit as recited in claim 12, wherein:

the software may assume, as the operating state, one of a “

software update”

state, a “

software parameterization”

state, a “

software diagnosis”

state, a “

coasting”

state, a “

monitoring”

state”

, and an “

on”

state.

18. The electronic control unit as recited in claim 12, wherein the electronic control unit is used in an automobile electronic system for controlling operating sequences in a vehicle.

19. A method for specifying a software architecture for an electronic control unit, comprising:

after a specification of defined software interfaces, of software components, of software layers, and of software operating states, automatically assigning in each case the software components to the software layers and to the software operating states; and

verifying assignments made by the automatically assigning step by performing a subsequent analysis and checking interactions implemented based on the assignments.

20. The method as recited in claim 19, further comprising:

in the case of insufficient assignments, subdividing at least one of the software components into specified subcomponents, the software layers into specified sublayers, and the software operating states into specified substates; and

automatically carrying out a renewed assignment.

21. A computer program having a program code that when executed results in a performance of the following:

after a specification of defined software interfaces, of software components, of software layers, and of software operating states, automatically assigning in each case the software components to the software layers and to the software operating states; and

verifying assignments made by the automatically assigning step by performing a subsequent analysis and checking interactions implemented based on the assignments 22. The computer program as recited in claim 21, wherein;

the computer program is embodied in a computer program product.