WO2012152478A1

WO2012152478A1 - Data structure for assisting a vehicle diagnosis, method for data navigation on data relating to a vehicle diagnosis and method for forming a data structure for assisting a vehicle diagnosis

Info

Publication number: WO2012152478A1
Application number: PCT/EP2012/054466
Authority: WO
Inventors: Pia Schabel; Klaus Schneider
Original assignee: Robert Bosch Gmbh
Priority date: 2011-05-06
Filing date: 2012-03-14
Publication date: 2012-11-15
Also published as: DE102011075432A1

Abstract

The invention provides a data structure (10) for assisting a vehicle diagnosis which maps a component model (19) of a vehicle with components of the vehicle, wherein each component is assigned attributes (21-25) using a terminology with terminology terms composed of specialist terms for uniquely denoting the attributes. In this context, the data structure (10) has components, data relating to components and/or attributes and structures with relationships between the components and/or attributes. Components can contain other components. In the data collection, navigation is possible under components or attributes by means of a navigation perspective, wherein data are displayed which are logically combined with the component or the attribute under the navigation perspective.

Description

Description title

Data structure to support a vehicle diagnostics. A method for data navigation to data on a vehicle diagnostics and method for forming a data structure to support vehicle diagnostics

The present invention relates to a data structure for supporting a

Vehicle diagnosis, a method for data navigation to data on a

Vehicle diagnostics and a method of forming a data structure to support vehicle diagnostics.

State of the art

Information on vehicle diagnostics or service and maintenance of automobiles is offered today in various systems and by many manufacturers. Here you can distinguish systems of vehicle manufacturers themselves or systems from independent providers. Examples of diagnostic systems are Bosch ESI [tronic], described at http://aa.bosch.de/aa/de/esitronic/start/index.htm, and STAR Diagnosis, described below

http://service-parts.mercedes-benz.com/dcagportal/DCAGPortal/menu.action?pageld=33. A parts catalog is provided by CENTROdigital, http://www.centro-digital.de, and technical data is provided by TecDoc, described at http://www.tecdoc.de.

Furthermore, one can make a distinction with regard to the information content, so provides a first database information for vehicle identification, a second

Database technical information. A spare parts information system provides work values and installation instructions of spare parts from various manufacturers for a variety of vehicle types from different manufacturers. Another example is workshop management systems that provide different information, such as

Correlate / installation descriptions, site maps, feature descriptions, ECU diagnostics, test instructions, diagnostic troubleshooting codes (DTC). Nowadays, such information is rigidly linked with each other, eg, a test manual may contain a list of the error codes relevant to it or refer to the corresponding component installation / installation descriptions. The information is linked only by its validity, ie in relation to a specific vehicle, and is offered to the user in parallel. He can then access the various information - according to his needs.

An example of further networking of information is the applicant's ESI [tronic] system. There, a control unit diagnosis is provided, actual values are determined with the control unit diagnosis, setpoints are provided, and the measured actual values are compared, evaluated and logged together with setpoint values. All other information required for troubleshooting is displayed in a troubleshooting guide or electronic repair manual. Error codes are determined and described in plain text. The troubleshooting guide contains the electrical connection diagram and the installation position of the components.

The information in today's systems is statically linked to each other, according to the WEB1.0 approach. Characteristic here is that on the one hand the maintenance effort for the incorporation of the relationships, e.g. Schematic ->

Component descriptions or test procedure -> circuit diagram, with which the amount of information grows quickly and thus can only be displayed on a coarse granularity. Adding or omitting information is a hassle as relationships must be maintained to avoid errors such as "dead" links or missing links.

Disclosure of the invention

The invention provides a data structure for assisting a vehicle diagnosis according to claim 1, a method for data navigation to data for a vehicle diagnosis according to claim 3 and a method for forming a data structure in support of a vehicle diagnosis according to claim 13.

According to the invention, a model of vehicle components is created in which all relevant information is linked to one another. On this basis will be

Defines various navigation perspectives that allow the product user not "all" information, but to display the "correct" information.

For this purpose, the various semantic references that are stored in the component model are evaluated. These navigation perspectives are used for context-oriented filtering of information.

For information such as It is necessary to standardize and structure circuit diagrams, troubleshooting instructions, removal / installation instructions and to ensure that the information relates to clearly defined terms.

In the prior art terminologies are defined and used to identify subject-specific terms. Content of such a terminology store is a list of terms such as e.g. Temperature sensor, speed sensor, engine control.

Normally, a term memory is already due to the otherwise high

Translation costs are introduced, since in this way the number of concepts to be translated greatly reduced and, moreover, the quality of the information increases.

According to the invention, the structuring of the information is no longer based on the terminology, but on a component model of the vehicle components, which uses the terminology. This allows terminology terms to be related to each other, i. To a terminology store are added structures and relationships that are defined. The individual terms do not only exist "loosely" next to each other but are related to each other.

Thus, e.g. "Sensor" and "sensors" can be summarized, a component such as "speed sensor front left" can be assigned to the class RPM sensor, mechanical and electrical components can be distinguished, etc. The resulting component model of a vehicle links all relevant

Information about the individual vehicle components with each other. Advantages of the invention

The invention enables the specific linking of different information. This makes it possible for the product user to represent meaningful relationships between different information and to publish them in a targeted, semantically correct way. An advantage of introducing a component model is the targeted - but loose - coupling of information among each other as well as the exact mapping of the semantic relationships among each other. This makes it easy to add more information without affecting or adjusting existing information.

Such a model enables navigation based on the exact same entity as well as navigation based on semantically similar information.

In the model according to the invention, the relationships are generally described semantically exactly, so that a machine evaluation or representation is possible.

The data structure according to the invention has a common conceptual world or

Terminology across all published information and the associated seamless connection of information with each other. Existing semantic relationships between information allow a concomitant inaccurate "search" of relevant information by the user.

Brief description of the drawings

Fig. 1 shows a schematic representation of a data structure for supporting a vehicle diagnosis with a component model, data and

Navigation perspectives according to an embodiment of the present invention.

2 shows a flowchart of the method for data navigation on data for a vehicle diagnosis according to an embodiment of the present invention.

3 shows a flowchart of the method for forming a data structure to assist in vehicle diagnosis according to an embodiment of the present invention.

Embodiments of the invention

In Fig. 1 is a data structure 10 for supporting a vehicle diagnosis with a component model 19 of vehicle components, data 1 1 -15 and Navigation perspectives 16 are shown according to an embodiment of the present invention.

In the component model 19 data 17 are added to vehicle components from various external data sources. This basic data is fed into the component model 19 by means of a mapping 18. The data structure 10 has a component model 19 and a data memory 20, wherein the component model 19 forms the structure for the management of the data in the data memory 20. Within data store 20, the data is represented as ordered by attributes 21-25 of components. This representation does not have the order at the original one

Storage of the data, but this order of attributes can be generated by the component model 19.

A user uses the data structure 10 with a user interaction 27 in a customer-oriented context 28. The user interaction 27 navigates in the data in the data memory 20 and accesses data about a component or attribute of a component of a vehicle.

The component model 19 maps a component model of a vehicle to components of the vehicle with attributes associated with each component using terminology with terminology terms of technical terms to uniquely identify the attributes. In this case, the data structure 10 has components, data on components and / or attributes and structures with relationships between the components and / or attributes. Components may include other components.

The attributes of a component are features, properties, or subcomponents of components in a broad sense that are related to the component. Examples are the categories schematics, Aus / Einbaubeschreibungen, maps, functional descriptions, ECU diagnostics, test instructions, setpoints and

Diagnostic trouble codes (DTC), product information and dimensions. In Fig. 1, the data is ordered by attributes exemplified

Off / installation description 21, electrical diagram 22, product information 23, mounting positions 24 and attribute 25 is representative of other attributes. The data structure 10 manages the data about the attributes and correlates attributes of several different categories.

FIG. 2 shows a flow diagram 30 of the data navigation method for vehicle diagnosis data according to an embodiment of the present invention. The method begins with method step a) providing access to a

Data structure. In this case, the data structure maps components of the vehicle, wherein attributes are assigned to each component. The data structure includes components, data on components and / or attributes, and structures with relationships between the components and / or attributes.

It follows in step b) a selection of a navigation function. The navigation can be carried out according to a navigation function based on the exact same entity. For example, information I, a component Ki, and a controller function F provide the current sensor value of component Ki. Thus, the user - who just receives information I, presents - the right one

Sensor value are displayed. This although never explicitly referred to the existence of a sensor value in the information. If there is another information l ₂ , eg an installation / removal description, about the component Ki, then this can also be displayed to the user when he is reading.

The navigation can also be carried out according to a navigation function on the basis of semantically similar information. For example, a product user seeks information about the "speed sensor". The component model specifies that "sensor" is synonymous with "sensor" and the component model can therefore provide information about the "speed sensor".

In method step c), an attribute and a selection are selected

Navigation perspective. Depending on the component or attribute, the one

Be clearly assigned to a navigation perspective or multiple perspectives. Preferably, a certain perspective is preset as the default for a component or an attribute.

For the component or attribute, data is determined under a navigation perspective that corresponds to the component or attribute in one of the perspectives

corresponding relationship. Within the component model 19 in FIG. 1, navigation takes place under a navigation perspective 16, which makes it possible for the product user not to "all"

Information but to display the respective "correct" information. For this purpose, the various semantic relationships that are stored in the component model 10 are evaluated. These navigation perspectives 16 are used for context-oriented filtering of information, wherein further information is offered for an attribute according to a context. This can be done, for example, by displaying the

Information, by offering a link or providing a print version. Now some navigation perspectives 16 are presented.

A navigation perspective Symptom View uses the error symptoms of a component. For example, with the symptom "engine jerky," the navigation may display a list of suspect components, a list of relevant test procedures, setpoints, and so forth.

A navigation perspective Function view is based on a function of a component. For example, for the "lambda control" function, the navigation can provide or display a list of the components involved, functional description,.

A navigation perspective schematic view uses a schematic of a schematic

Vehicle component. For example, you can navigate to the elements displayed in the schematic, as well as additional information such as

Off / show installation instructions.

A navigation perspective component view uses a vehicle component directly. Thus, for example, to a component "speed sensor front left" the navigation could here all information that relate to this component, ie Aus / installation position, test procedure circuit diagram, ... offer.

A navigation perspective control unit view is at a control unit as

Component helpful. For example, the electronic control unit (ECU) is a motor controller. Then the navigation can put together all the actual values that can be called up by this ECU, installation positions all components, .... A Navigation Perspective Location view uses the spatial arrangement of a component in the vehicle. For example, for the "front left" layout, the navigation may display a list of all the components that are also "front left" in that vehicle.

A Navigation Perspective tool view uses a tool to handle a component. For example, for the "lift" tool, the navigation can list all the inspection and maintenance work that also requires a lift to perform.

Finally, in method step d), data associated with the selected attribute under the navigation perspective is displayed.

FIG. 3 shows a flow chart 40 of the method for forming a data structure in support of vehicle diagnosis according to an embodiment of the present invention. It comprises the following method steps: a) generation of terminology with terminology terms from technical terms; b) describing components and their attributes with the terminology terms; c) storing data on components and their attributes; and d) forming structures having relationships between the components and / or attributes.

Claims

Claims 1. Data structure (10) for supporting a vehicle diagnosis, thereby

in that the data structure (10) is a component model (19) of a

Vehicle with components of the vehicle, wherein each component attributes (21 -25) are assigned, using a terminology with terminology terms of technical terms to uniquely identify the attributes, the data structure (10) components, data on components and / or attributes and structures having relationships between the components and / or attributes.

2. Data structure (10) according to claim 1, characterized in that the attributes (21-25) at least four elements from a set consisting of the categories

Schematics, installation instructions, site plans, functional descriptions,

ECU Diagnostics, Test Instructions, Diagnostic Trouble Codes (DTC).

3. A method for data navigation on data for a vehicle diagnosis with the method steps

a) providing access to a data structure, wherein the data structure

Maps components of the vehicle, each attribute being associated with attributes, the data structure comprising components, data on components and / or attributes, and structures having relationships between the components and / or attributes;

b) selecting a navigation function;

c) selecting a component or attribute and a navigation perspective; d) Display data related to the component or attribute under the

Navigation perspective.

4. The method according to claim 3, characterized in that a first

Navigation function performs a navigation for exact information and a second navigation function performs a navigation for similar information.

5. The method according to claim 3 or 4, characterized in that a component or an attribute is associated with a navigation perspective, according to the data are determined, which is to the component or the attribute in one of

Perspective appropriate relationship.

6. The method according to claim 4 to 5, characterized in that

A navigation perspective depicts a symptom view that uses component error symptoms.

A method according to any one of claims 4 to 6, characterized in that a navigation perspective depicts a functional view using a function of a component.

8. The method according to any one of claims 4 to 7, characterized in that a navigation perspective maps a schematic view using a circuit diagram of a component.

9. The method according to any one of claims 4 to 8, characterized in that a navigation perspective depicts a component view that uses a component.

10. The method according to any one of claims 4 to 9, characterized in that a navigation perspective depicts a control unit view using a control unit of a component.

1 1. Method according to one of claims 4 to 10, characterized in that a navigation perspective maps a situation view using a spatial arrangement of a component.

12. The method according to any one of claims 4 to 1 1, characterized in that a navigation perspective depicts a tool view, which is a tool for

Treatment of a component used.

13. A method of forming a data structure to support a vehicle diagnostic with the method steps

a) generating terminology with terminology terms from technical terms;

b) describing components and their attributes with the terminology terms; c) storing data on components and their attributes; and

d) Forming structures with relationships between the components and / or attributes.