Vehicle Update System Managing OTA Data Usage
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Vehicle controllers experience excessive wireless communication data usage due to repeated failed updates, leading to increased costs, as they often require re-downloading data when integrity issues arise during over-the-air updates.
Innovation Solution
A vehicle update system and method that determines whether a new version of data is present and successful, allowing for efficient data transmission and processing, with retry and rollback mechanisms to manage update failures, minimizing data usage by converting successful updates into rollback data and limiting re-attempts.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If vehicle controllers repeatedly request and download update data from the OTA server after failed updates, then update reliability is improved, but wireless communication data usage increases excessively
Solution Approach 1:
The system performs preliminary actions by storing multiple versions of update data locally in the vehicle controller before they are needed. When an update fails, the controller can immediately retry using the previously stored data without requiring new downloads, thus improving update reliability while minimizing additional wireless data usage.
Solution Approach 2:
The vehicle controller acts as an intermediary by maintaining a local cache of update data and managing the retry logic. This intermediary function allows the controller to handle update failures autonomously using stored data, reducing the need for repeated communications with the OTA server and thereby reducing wireless data consumption.
2Reliability
If vehicle controllers re-download update data after each failed update, then update success rate is improved, but communication cost increases
Solution Approach 1:
Update data is downloaded and stored in advance in the vehicle controller's memory before the update is actually needed. This preliminary action ensures that when updates are attempted, the data is already available locally, eliminating the need for costly re-downloads after failures while maintaining high update success rates.
Solution Approach 2:
The vehicle controller serves itself by maintaining local copies of update data and autonomously managing retry operations. This self-service capability allows the controller to perform multiple update attempts using stored data without incurring additional communication costs, as the data is already available in its own memory.
3Reliability
If the system allows multiple retry attempts for failed updates, then update reliability is improved, but data usage increases
Solution Approach 1:
The system downloads and stores update data in advance in the vehicle controller's memory, creating a local repository of update files. This preliminary action enables multiple retry attempts to be performed using the stored data without requiring additional downloads, thus improving update reliability while keeping data usage limited to the initial download only.
Data Source
AI summary
A vehicle update system includes a server that determines whether a new version of data is present based on an update version of and a final update-failed version of a vehicle controller, and transmits the new version of the data when the new version of the data is present. An update controller executes an update of the vehicle controller based on the new version of the data received from the server, and determines a processing method of the data according to whether the update of the vehicle controller is successful.