Vehicle Controller Log Coordination via Diagnostic Master
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current vehicle diagnostic systems face challenges in pinpointing the root cause of failures due to uncoordinated and large vehicle log data from multiple interconnected controllers, making it difficult for technicians to navigate and identify the source of issues.
Innovation Solution
A vehicle system architecture that includes multiple controllers acting as nodes, with a diagnostic agent on each node to collect logs and a diagnostic master to coordinate the process, facilitating the capture and coordination of logs across nodes to root cause failures, using a security token for authentication and upload to a remote server.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If logs are collected from multiple controllers independently without coordination, then each controller can capture its own logs, but the log data becomes uncoordinated and difficult to navigate
Solution Approach 1:
The system segments the log collection process by assigning a diagnostic master to specific controllers (nodes) based on failure events. Each node collects logs independently when designated, but the segmentation is coordinated through the analytics library that identifies which controllers are related to specific failures, preventing complete uncoordination while maintaining independent collection capabilities.
Solution Approach 2:
The patent introduces an intermediary coordination mechanism where the analytics library acts as a mediator between controllers and the log collection process. The analytics library identifies related controllers and coordinates which nodes should collect logs for specific failure events, creating an intermediate layer of organization that makes the overall log data more navigable without preventing independent collection.
2Reliability
If all controller logs are collected and uploaded together, then complete diagnostic data is available, but the data volume becomes large and complex to manage
Solution Approach 1:
The system extracts only the necessary log data by using the analytics library to identify which controllers are related to specific failure events. Instead of collecting logs from all controllers universally, the system extracts and collects logs only from relevant nodes, reducing overall data volume while maintaining diagnostic completeness for each specific failure type.
Solution Approach 2:
The patent implements partial action by having only the diagnostic master (specific controller) collect logs for each failure event rather than all controllers collecting all logs. This partial collection approach is sufficient for diagnosing specific failures while significantly reducing the total log data volume and management complexity compared to universal collection.
3Ease of operation
If a centralized system collects all logs, then coordination is simplified, but the system requires more centralized control infrastructure
Solution Approach 1:
The system implements self-service by enabling each controller node to autonomously determine whether it should collect logs based on failure events it detects or receives notifications about. The analytics library on each node identifies related controllers and triggers local log collection without requiring centralized coordination infrastructure, allowing distributed self-service while maintaining coordination through shared analytics logic.
Data Source
AI summary
A vehicle includes a first controller; and a second controller, wherein the first controller is programmed to responsive to detecting a failure, generate a failure event, identify the second controller as related to the failure event, identify logs of the first controller and second controller as related to the failure event, collect logs of the first controller, and transmit a failure message including a request for the logs of the second controller to the second controller, and the second controller is programmed to responsive to receiving the failure message from the first controller, collect logs of the second controller as requested, and send a request for a security token to a server, and responsive to receiving the security token from the server, upload the logs of the second controller, as collected using the security token, to the server, and send the security token to the first controller.