Hierarchy system for controlling a vehicle

• US 6,092,006 A
• Filed: 03/06/1998
• Issued: 07/18/2000
• Est. Priority Date: 03/07/1997
• Status: Expired due to Fees

• Current Assignee: Robert Bosch GmbH
• Original Assignee: Robert Bosch GmbH
• Inventors: Mueller, Jens-Olaf, Hermsen, Wolfgang, Grosse, Christian, Bertram, Torsten, Bellmann, Holger, Dominke, Peter, Volkart, Asmus
• Primary Examiner(s): Cuchlinski, Jr., William A.
• Assistant Examiner(s): Hernandez, Olga
• Application Number:
  US09/035,790
• Time in Patent Office: 865 Days
• Field of Search: 701/1, 701/27, 701/57, 701/77, 701/106, 701/40, 701/44, 701/98, 370/539, 370/541
• US Class Current: 701/1
• CPC Class Codes: B60T 2220/02 Driver type; Driving style; Driver adaptive features
• CPC Class Codes: B60T 2260/08 Coordination of integrated systems
• CPC Class Codes: B60T 8/175 Brake regulation specially adapted to prevent excessive wheel spin during vehicle acceleration, e.g. for traction control safety devices for propulsion unit control responsive to, or preventing, skidding of wheels B60K28/16
• CPC Class Codes: B60T 8/17616 Microprocessor-based systems
• CPC Class Codes: B60W 10/06 including control of combustion engines
• CPC Class Codes: B60W 10/18 including control of braking systems
• CPC Class Codes: B60W 2050/0045 using databus protocols
• CPC Class Codes: B60W 30/18 Propelling the vehicle
• CPC Class Codes: B60W 50/0098 Details of control systems ensuring comfort, safety or stability not otherwise provided for
• CPC Class Codes: F02D 41/26 using computer, e.g. microprocessor

Abstract

A control system for a motor vehicle has several components for carrying out different tasks to control the vehicle. The data, which are necessary from the components, are acquired independently by the components either via data interrogation or via request relationships.

Claims

1. A control system for a vehicle, the control system comprising:

a plurality of components arranged in the context of a hierarchy at different levels thereof;

at least a first one of said components being at a first one of said levels;

at least a second one of said components being at a second one of said levels lower than said first level;

said second component being adapted to receive and execute commands from said first component for controlling said vehicle;

a plurality of data generators which make data available;

said components being adapted to evaluate said data for executing said commands and with said data generators making said data available;

data inquiries (?) and request relationships (!) being defined as types of communication between each one of said components and every other one of said components and between said components and said data generators;

when transmitting a data inquiry, the transmitting component or data generator being a transmitter and the receiving component or data generator being a receiver and the transmitter having data and said data being made available to the receiver and, for request relationships, the transmitter making data available to the receiver which are to be converted by the receiver;

for each component, the permitted data inquiries (?) and request relationships (!) are pregiven;

a first portion of said components defining a first system and communication relationships being permitted for each component to every other component within said system;

a second portion of said components defining a second system at a level above or below said first system;

for communication relationships to another system beyond the boundaries of the system, only communication relationships are permitted from a system at a lower level to a system at a higher level;

in a system, a communication relationship coming from outside said system is transmitted to components at a lower level; and

,

said data generators, which determine the needed data, are assigned to the highest level of the hierarchy wherein the data for forming the command or to process the command are needed, these data being determined by the data generator.

2. The system of claim 1, wherein one of said components, as a command hierarchy, is subdivided into a plurality of subcomponents defining a subsystem.

3. The system of claim 2, wherein the communication relationship for acquiring information between components within a system is such that a data interrogation and/or a request relationship is possible for each component to every other component.

4. The system of claim 3, wherein the data interrogation and/or request relationships across system boundaries only occur in the direction of higher levels.

5. The system of claim 1, wherein a target component and/or a source component of a data interrogation and/or a request relationship is precisely one component of another system for communication relationships between individual systems.