Backend Server Error Pattern Matching for Vehicle Diagnostics

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current methods for handling vehicle error reports are inefficient, as they require manual analysis by quality experts and lack automated linking of known problems across service institutions, leading to repetitive processing of individual diagnostic data and inadequate focus on emerging customer issues.

Innovation Solution

A method for remotely handling error reports involves sending data from vehicles to a back-end server, where error patterns are automatically matched with configuration requirements to generate a troubleshooting operation, allowing for remote correction of errors during or outside of a garage, using sensor technology and data comparison algorithms.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Measurement precision

If manual analysis of error reports is performed by quality experts, then accuracy in identifying error patterns is improved, but time consumption and processing efficiency deteriorate

Engineering Contradiction:
Improveaccuracy in identifying error patternsVSAvoidtime consumption for error analysis
Core Design Contradiction:
Measurement precisionVSLoss of time

Solution Approach 1:

The system enables self-service by automatically analyzing error reports using onboard diagnostic data and backend server algorithms. The vehicle's own diagnostic system identifies and communicates errors without requiring manual expert analysis, thus reducing time consumption while maintaining accuracy through automated pattern recognition.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The manual mechanical process of expert analysis is replaced by an automated electronic system. The backend server uses algorithms to process diagnostic data, identify error patterns, and generate troubleshooting operations, substituting human expert manual work with automated computational analysis.

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

2Ease of operation

If individual vehicle diagnostic data is processed by service providers, then specific vehicle issues are addressed, but repetitive processing of the same errors across multiple vehicles increases time consumption

Engineering Contradiction:
Improveability to address specific vehicle issuesVSAvoidrepetitive processing time across multiple vehicles
Core Design Contradiction:
Ease of operationVSLoss of time

Solution Approach 1:

The system merges individual vehicle diagnostic data with a centralized backend server that aggregates error patterns across multiple vehicles. By combining individual case processing with collective pattern recognition, the system addresses specific vehicle issues while simultaneously learning from and applying knowledge from other vehicles, eliminating repetitive analysis.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The backend server provides universal functionality by serving multiple service providers and vehicles simultaneously. It processes individual vehicle diagnostics while maintaining a shared knowledge base of error patterns that can be applied universally across all connected vehicles, allowing one system to handle both specific and general error resolution.

Inventive Principle:
Principle #6Universality (Multi-functionality)

3Reliability

If alarm systems predict possible errors, then early warning is provided, but lack of concrete troubleshooting information reduces operational effectiveness

Engineering Contradiction:
Improveearly error detection capabilityVSAvoidconcrete troubleshooting information availability
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The system implements feedback by not only detecting errors but also providing structured troubleshooting operations back to the service provider. The backend server analyzes diagnostic data, identifies error patterns, and returns specific actionable troubleshooting steps, creating a closed-loop feedback system that transforms raw error detection into effective corrective action.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The system performs preliminary action by pre-calculating and storing troubleshooting operations in the backend server. When an error is detected, the system retrieves pre-prepared troubleshooting steps rather than requiring real-time expert analysis, thus providing both early warning and immediate actionable guidance.

Inventive Principle:
Principle #10Preliminary action

4Device complexity

If one-way alarm communication is used, then error notification is simple, but lack of two-way communication prevents direct interaction between service providers and error databases

Engineering Contradiction:
Improvecommunication system simplicityVSAvoidcommunication capability between service providers and databases
Core Design Contradiction:
Device complexityVSAdaptability or versatility

Solution Approach 1:

The backend server acts as an intermediary between service providers and the error database system. It receives diagnostic data from vehicles, processes it through pattern recognition algorithms, and communicates troubleshooting operations back to service providers, enabling two-way communication while maintaining system simplicity through a centralized mediation point.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS12001272B2Method for the remote-controlled handling of an error finding in a means of transport, means of transport, backend server and system
Publication Date: 2024.06.04 BAYERISCHE MOTOREN WERKE AG
  • US12001272B2 patent drawing
  • US12001272B2 patent drawing

AI summary

The invention relates to a method for remotely handling a conspicuity pattern or error report of a means of transport (1a-1d) comprising the steps of: receiving the conspicuity pattern of error report (ER) from the means of transport (1a-1d) on a back-end server (3); automatically determining an error pattern (F1-F6) stored on the back-end server (3) as a function of the error report (ER), in response thereto automatically determining a configuration requirement as a function of the stored knowledge; automatically generating and sending a configuration request representing a union set of the respective configuration requirements to the means of transport (1a-1d); receiving (500) a configuration specification in response to the configuration request on the back-end server (3); and automatically determining an action, like e.g. a troubleshooting operation or an information based on the configuration specification by the back-end server (3).