In-Vehicle Software Update Timing for Usable ECU Updates
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Vehicles cannot be started during software updates, and if an error occurs, the user cannot use the vehicle due to incomplete updates.
Innovation Solution
A software update system that acquires update process information from a server, requests user consent, estimates the update time, and executes the process based on user response, allowing continued vehicle use.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If software update is executed in-vehicle, then software is updated to newer version, but vehicle cannot be used during update process
Solution Approach 1:
The system performs preliminary actions by downloading and storing update data in storage memory before executing the update. This allows the update process to be prepared in advance, reducing the time the vehicle is unavailable and enabling a smoother transition to new software without interrupting vehicle operation.
Solution Approach 2:
The update process is segmented into distinct phases: data download, storage, execution, and rollback preparation. By dividing the update process and maintaining separate software versions (old and new), the system can switch between versions if needed, ensuring vehicle usability is maintained even if update issues occur.
2Reliability
If software update is executed, then software version is improved, but system becomes unable to determine which software to execute when error occurs
Solution Approach 1:
The system implements feedback mechanisms by continuously monitoring update execution status and comparing it against expected outcomes. When an error is detected or update completion is confirmed, the system receives feedback and automatically adjusts by either confirming the new software or rolling back to the old version, ensuring deterministic software selection.
Solution Approach 2:
The system changes the state parameter of software versions by maintaining clear version identifiers and execution status flags. By tracking parameters such as update completion status and version identifiers, the system can deterministically determine which software to execute, reducing complexity despite multiple versions existing.
3Measurement precision
If update process is monitored for completion, then update status is tracked, but update may fail if not completed within estimated time
Solution Approach 1:
The system prepares cushioning measures in advance by creating rollback data and maintaining backup software versions before the update executes. This allows the system to recover from failures that occur during or after update execution, ensuring reliability even when update completion monitoring indicates failure.
Solution Approach 2:
The system uses estimated completion times to determine when to skip waiting for update completion and proceed with verification or rollback. By rushing through the monitoring phase when time exceeds estimates, the system avoids indefinite waiting while maintaining reliable update status through alternative verification methods.
Data Source
AI summary
A software update device updates software for an in-vehicle control device mounted in a vehicle. An information acquisition unit acquires, from a server provided outside the vehicle, update process information. The output unit outputs consent request information. The execution unit executes the update process. The calculation unit calculates an estimated time required for the update. The communication status acquisition unit acquires communication status information related to communication status with the server. The correction unit corrects the estimated time based on the communication status information. The notification unit outputs information on the corrected estimated time. The notification unit, when the corrected estimated time is shorter than the estimated time before correction, does not output information on the corrected estimated time.