Error Entry Classification for Motor Vehicle Data Bus

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In modern motor vehicles, the large number of error entries in data bus control units leads to inefficient error detection and storage, straining hardware and making it difficult to quickly identify service-relevant errors due to unnecessary entries and incorrect masking of safety-critical errors.

Innovation Solution

A method where detected errors are classified into two categories, with immediate error entry for safety-relevant errors and conditional error entry for non-safety-relevant errors, allowing for targeted storage and notification, and utilizing a hierarchical structure for error handling and storage.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If error entries are created for every detected error independently of error type, then complete error recording is achieved, but error memory is unnecessarily strained and service-relevant errors become difficult to identify

Engineering Contradiction:
Improveerror detection completenessVSAvoiderror memory strain
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent segments error entries into two distinct categories: service-relevant error entries and non-service-relevant error entries. This segmentation is achieved by introducing a service relevance flag that distinguishes between errors requiring service action and those that do not. By separating these error types, the system reduces the burden on error memory while ensuring that service-relevant errors remain easily identifiable for diagnostic purposes.

Inventive Principle:
Principle #1Segmentation

2Reliability

If error entries are created for every detected error, then complete error recording is achieved, but the number of write cycles exceeds hardware specifications and hardware breakdown occurs

Engineering Contradiction:
Improveerror recording accuracyVSAvoiderror memory lifespan
Core Design Contradiction:
ReliabilityVSDuration of action of stationary object

Solution Approach 1:

The patent extracts non-service-relevant errors from the error memory writing process. By evaluating the service relevance of each detected error and only creating error entries for service-relevant errors (or errors requiring further investigation), the system significantly reduces the number of write cycles to error memory. This extraction approach extends the operational lifespan of error memory hardware while maintaining accurate recording of all service-relevant errors.

Inventive Principle:
Principle #2Taking out (Extraction)

3Productivity

If masking is applied based on error type criteria, then quick identification of safety-critical errors is enabled, but service-relevant errors may be incorrectly masked

Engineering Contradiction:
Improveerror search speedVSAvoiderror classification accuracy
Core Design Contradiction:
ProductivityVSMeasurement precision

Solution Approach 1:

The patent applies local quality by introducing a service relevance flag that provides specific, localized information about each error entry's importance. Rather than applying blanket masking rules based on error type, the system evaluates each error individually and assigns appropriate service relevance status. This allows diagnostic systems to quickly identify service-relevant errors through the flag while avoiding incorrect masking, as each error's service relevance is determined by specific criteria rather than general classification.

Inventive Principle:
Principle #3Local quality

Data Source

PatentUS8452485B2Method for preparing error entries
Publication Date: 2013.05.28 BAYERISCHE MOTOREN WERKE AG
  • US8452485B2 patent drawing
  • US8452485B2 patent drawing
  • US8452485B2 patent drawing

AI summary

A method for preparing error entries of the user of a data bus in a motor vehicle is provided. When an error is detected, the detecting user is put into an error state and outputs an error message to a second user, a request to prepare an error entry is output by the second user to the detecting user after receiving such an error message as a function of at least one predefined condition, and an error entry is instigated by the detecting user in case of receiving such a request.