Vehicle ECU OTA Software Switching for Server Compatibility
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Software updates for vehicle electronic control units (ECUs) cannot be performed via over-the-air (OTA) when the OTA software on the server changes, due to compatibility issues between different vendors.
Innovation Solution
A software update device and method that allows software updates via OTA by switching between different software versions on the client-side, ensuring compatibility with updated server-side software, even when vendors change, using a dual-data storage approach in ECUs and intelligent software switching mechanisms.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If the OTA software on the server is changed to a newer version or different vendor, then the server can provide updated software distribution capabilities, but the client-side OTA software becomes incompatible and cannot communicate with the server
Solution Approach 1:
The client device dynamically switches between first OTA software and second OTA software based on server compatibility requirements. The system monitors server communication status and automatically selects the appropriate software version to maintain functional compatibility, transforming a static software installation model into a dynamic adaptation model.
Solution Approach 2:
The system changes the software version parameter on the client side by switching between different OTA software versions. When the first OTA software becomes incompatible with the updated server software, the system transitions to using the second OTA software, effectively changing the software parameter to restore compatibility.
2Device complexity
If the client device installs only one version of OTA software, then the device structure remains simple, but the device cannot adapt to server software changes from different vendors
Solution Approach 1:
The client device is designed with multi-functionality by incorporating both first OTA software and second OTA software. This universal design enables the device to communicate with servers from different vendors or different software versions, making the client adaptable to various server environments without requiring hardware changes.
Solution Approach 2:
The system introduces a software selection mechanism that acts as an intermediary between the client device and the server. This intermediary selectively activates the appropriate OTA software version based on server compatibility, mediating the interaction between the client and varying server environments.
3Reliability
If the client device continuously monitors and switches OTA software versions, then compatibility with server updates is maintained, but the system complexity and software switching control become more complex
Solution Approach 1:
The system implements a feedback mechanism where the client device monitors the result of OTA software execution and server communication status. When incompatibility is detected (e.g., failed server communication or error messages), the system receives feedback and automatically triggers a switch to the alternative OTA software version, creating a closed-loop compatibility assurance system.
Solution Approach 2:
The client device performs self-service by automatically detecting compatibility issues and switching between OTA software versions without requiring manual intervention. The system monitors its own operational status and autonomously selects the appropriate software version to maintain functionality.
Data Source
Figure 1
Figure 2~3
Figure 4~5
AI summary
A software update device (11) is configured to control software update of an electronic control unit (13a, 13b, 13c, 13d) mounted on a vehicle. The software update device (11) includes: one or more storage devices (34) configured to store first software and second software for downloading update data of the electronic control unit (13a, 13b, 13c, 13d) from a server (1), the first software and the second software being different from each other; and one or more processors (31) configured to download the update data from the server (1) by executing any of the first software and the second software.