Vehicle Software Version Checks for Consistent Control Startup
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing vehicle control systems fail to adequately prevent unexpected vehicle control due to inconsistent versions of on-board software, despite systems like JP 2009-53920 A confirming dependency relations during updates.
Innovation Solution
A vehicle control system with a representative on-board device that checks software versions upon vehicle power-up, transmitting inconsistencies to an external server for secondary verification, and allowing software updates or reverting to previous versions if necessary to ensure consistency.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If software updates are performed without comprehensive version consistency checks, then update speed and productivity are improved, but system reliability deteriorates due to unexpected vehicle control from inconsistent software versions
Solution Approach 1:
The system performs preliminary version consistency checks before executing software updates. A representative on-board device verifies version consistency among multiple on-board devices prior to update execution, preventing inconsistent software states that would compromise vehicle control reliability.
Solution Approach 2:
The system implements feedback mechanisms where version information is continuously monitored and reported. When version inconsistencies are detected during or after updates, the system provides feedback to trigger corrective actions such as rolling back updates or notifying users, thereby maintaining system reliability.
2Reliability
If comprehensive version consistency checks are performed at all times, then vehicle control reliability is improved, but system complexity and communication requirements worsen
Solution Approach 1:
The consistency check system is segmented into two operational modes: a first mode performing comprehensive checks involving communication between representative and other on-board devices, and a second mode performing simplified checks when communication is unavailable. This segmentation reduces overall system complexity while maintaining reliability.
Solution Approach 2:
The system dynamically adapts its consistency checking behavior based on communication availability. When communication is available, comprehensive checks are performed; when communication is unavailable, the system switches to simplified local verification. This dynamic adaptation reduces complexity without sacrificing reliability.
3Ease of operation
If software updates are performed without version verification, then ease of operation is improved, but harmful effects increase due to unexpected vehicle control behavior
Solution Approach 1:
The on-board devices automatically perform version consistency checks and manage update execution without requiring manual verification by users. The representative device coordinates with other devices to verify versions and control update propagation, maintaining ease of operation while preventing harmful effects through automated safety checks.
4Manufacturing precision
If version consistency is verified through continuous communication between all devices, then manufacturing precision of software configuration is improved, but loss of energy and communication overhead worsen
Solution Approach 1:
Version information is collected and verified in advance before updates are propagated across the network. The representative device obtains version information from other devices prior to initiating updates, ensuring configuration accuracy without requiring continuous communication during the update process.
Solution Approach 2:
The system performs version consistency checks periodically at key moments such as before update execution and after updates complete, rather than continuously monitoring all devices. This periodic verification maintains software configuration accuracy while minimizing communication energy consumption.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
A specific on-board device, that is any one of a plurality of on-board devices, is configured to acquire the versions of software included in other on-board devices when the power source of a vehicle is turned on. The specific on-board device determines whether or not the versions of the software of all the on-board devices that constitute a vehicle control system are consistent, by comparing the version of the software of the specific on-board device and the versions of the software acquired from the other on-board devices with first consistency information prestored.