Vehicle ECU Software Alignment Without Server Access
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing vehicle onboard systems face challenges in verifying and aligning software versions across electronic control units (ECUs) when communication with a server is not possible, particularly during ECU exchanges, leading to potential operational malfunctions due to misaligned software versions.
Innovation Solution
The onboard system implements a self-verifying mechanism where each ECU holds a list of software versions and identification information, allowing the master ECU to compare and update its list to ensure alignment without external server communication, enabling operation even when the ECU managing the list has been exchanged.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If the system relies on external server communication for version alignment verification, then the alignment accuracy can be ensured, but the system cannot operate when server communication is unavailable
Solution Approach 1:
The ECU performs self-verification of software version alignment by comparing its own version information with version information of other ECUs through local network communication, eliminating the need for external server intervention and enabling operation in offline conditions
Solution Approach 2:
The system uses the ECU network as an intermediary channel to exchange version information between ECUs, replacing the server-mediated verification process with direct peer-to-peer communication for version alignment checks
2Reliability
If the system performs comprehensive version alignment verification across all ECUs, then the reliability of software compatibility is improved, but the startup time and processing complexity increase
Solution Approach 1:
Version information is pre-collected from all ECUs during system initialization, and the master ECU performs parallel comparison operations using this pre-assembled data, reducing the time required for comprehensive verification
Solution Approach 2:
The verification process is divided into distinct phases: information collection phase where each ECU provides its version data, and comparison phase where the master ECU processes the collected data, allowing for more efficient resource management and potential parallel processing
3Adaptability or versatility
If the system stores complete version information lists in all ECUs, then the capability to perform local verification is improved, but the memory requirements and system complexity increase
Solution Approach 1:
Each ECU stores a copy of the relevant version information list, enabling any ECU to participate in verification processes without requiring complex centralized access control or sophisticated data synchronization protocols
Data Source
AI summary
An onboard system comprising, a plurality of electronic control units (ECUs) coupled together via a network and including a first ECU and a second ECU, the first ECU including a first memory and a first processor coupled to the first memory, the second ECU including a second memory and a second processor coupled to the second memory, wherein, the first memory and the second memory configured to store a list recording a combination of identification information of software of the plurality of ECUs, the first processor is configured to: compare identification information of the list stored in the first memory against identification information of the list stored in the second memory and identify a list which is newer in the lists, and determine whether or not a combination of software of the plurality of ECUs is aligned based on a combination of the software identification information.