Domain Controller Diagnostics for Vehicle Software Fault Analysis

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing vehicle diagnostic methods struggle to diagnose software faults and performance reliability issues in domain controller units due to the limitations of conventional diagnostic techniques that rely on reading trouble codes and data streams.

Innovation Solution

A vehicle diagnostic method and apparatus that utilizes a domain controller unit to receive diagnostic instructions from a server, obtain to-be-diagnosed data, and perform diagnostics using intelligent diagnostic applications, enabling comprehensive analysis of software faults and performance reliability problems.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If conventional diagnostic techniques reading trouble codes and data streams are used, then hardware faults of ECU components can be diagnosed, but software faults and performance reliability issues of domain controller units cannot be diagnosed

Engineering Contradiction:
Improvediagnostic capabilityVSAvoidapplicability to domain controller units
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The patent changes the diagnostic parameters from traditional trouble codes and data streams to comprehensive logs including system logs, application logs, and performance data. This parameter transformation enables the diagnostic system to detect software faults and performance reliability issues that were previously undetectable by conventional methods

Inventive Principle:
Principle #35Parameter changes

Solution Approach 2:

The patent creates a universal diagnostic method that can handle both traditional ECU hardware faults and domain controller software faults through a unified approach. The diagnostic system is designed to work across different controller types by collecting and analyzing multiple types of logs and data, making it adaptable to various fault scenarios

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

2Ease of operation

If remote diagnostic is applied to read trouble codes and data streams, then diagnostic convenience is improved, but the amount of diagnostic information obtained is limited

Engineering Contradiction:
Improvediagnostic convenienceVSAvoiddiagnostic information completeness
Core Design Contradiction:
Ease of operationVSLoss of information

Solution Approach 1:

The patent implements preliminary action by pre-collecting and storing comprehensive logs including system logs, application logs, and performance data in the domain controller before diagnostic analysis. This preparation ensures that when remote diagnostic is performed, sufficient information is already available for thorough analysis without requiring additional information loss

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent introduces an intermediary diagnostic analysis module that processes and analyzes the collected logs and data. This intermediary component bridges the gap between raw data collection and comprehensive diagnostic results, enabling remote diagnostic to obtain complete diagnostic information while maintaining operational convenience

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentEP4711874A1Vehicle diagnosis method, and apparatus
Publication Date: 2026.03.18 YINWANG INTELLIGENT TECHNOLOGIES CO LTD
  • EP4711874A1 patent drawingFigure 1~2
  • EP4711874A1 patent drawingFigure 3
  • EP4711874A1 patent drawingFigure 4

AI summary

A vehicle diagnostic method and apparatus are disclosed. The method is applied to a vehicle including at least one component. The at least one component includes at least one domain controller unit. The method includes: A first domain controller unit in the at least one domain controller unit receives a diagnostic instruction from a server (S1001), where the diagnostic instruction is used to initiate diagnostic on a to-be-diagnosed component, and the to-be-diagnosed component is one or more of the at least one component included in the vehicle; and then, the first domain controller unit obtains to-be-diagnosed data for the to-be-diagnosed component based on the diagnostic instruction (S1002), where the to-be-diagnosed data is used to diagnose the to-be-diagnosed component. The method can resolve a problem that it is difficult to diagnose a software fault, a performance reliability problem, and the like of a domain controller unit in the vehicle by reading a trouble code, a data stream, and the like, thereby implementing diagnostic on the domain controller unit in the vehicle.