Vehicle OTA Update Control for Decryption Failure Recovery
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Vehicles face challenges in decrypting update data received from OTA centers due to issues such as ECU replacement, software version incompatibility, corrupted data, or tampering, leading to failed software updates.
Innovation Solution
An OTA master system that includes processors to manage software updates, capable of performing decryption processes, sending failure notifications to the OTA center, and facilitating decryption by the ECU when necessary, and providing detailed failure information to enable appropriate measures.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If update data is encrypted for security, then security is improved, but decryption may fail due to ECU replacement, software version changes, or data corruption
Solution Approach 1:
The system implements a feedback mechanism where the OTA master monitors decryption operations and sends notifications to the OTA center when decryption fails. This allows the OTA center to receive feedback about decryption failures and take appropriate corrective actions, such as resending update data with different encryption settings or providing alternative decryption keys.
Solution Approach 2:
The system performs preliminary verification of decryption capability before attempting to update. The OTA master checks whether the ECU can decrypt the received update data by attempting decryption or verifying compatibility information. If decryption is predicted to fail, the system can take preliminary actions such as requesting new update data from the OTA center before the actual update process, preventing wasted time and resources.
2Ease of operation
If decryption is attempted by the OTA master, then decryption control is improved, but processing time increases when decryption fails and notifications must be sent
Solution Approach 1:
The OTA master performs a partial decryption attempt or verification check rather than a complete decryption process. This allows the system to quickly determine whether decryption will succeed or fail without investing excessive time in a decryption operation that is likely to fail. If the preliminary check indicates failure, the system stops further processing and sends a notification, minimizing time loss.
3Reliability
If update data is resent with different encryption, then decryption success rate is improved, but communication overhead increases
Solution Approach 1:
Before resending update data with different encryption, the system performs preliminary actions to determine the cause of decryption failure. The OTA master analyzes the failure reason (ECU replacement, software version mismatch, data corruption) and only requests new update data when necessary. This preliminary diagnosis prevents unnecessary communication overhead by avoiding redundant data transmissions for issues that can be resolved through other means.
Data Source
AI summary
An OTA master configured to control a software update on an ECU mounted on a vehicle includes one or more processors. The one or more processors are configured to: download update data of software on the ECU from an OTA center; control the software update on the ECU using the update data; and when the update data has been encrypted and a decryption process is necessary but the decryption process fails, send a notification indicating that the decryption process fails to the OTA center.