ECU Secure Update Validation via Timestamp and Hash Verification
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The increasing complexity of vehicles and the prevalence of over-the-air updates for electronic control units (ECUs) pose challenges in ensuring that only authorized entities can update vehicle software and firmware, while also preventing malicious attacks and ensuring correct installation.
Innovation Solution
The proposed solution involves a vehicle ECU configured to receive an update package from a remote source, verify timestamps, obtain a unique vehicle identifier, calculate and validate hash values using secure configuration data, and modify the ECU only if the validation is successful.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If remote over-the-air updates are enabled for ECUs, then update speed and convenience are improved, but security risks and vulnerability to malicious attacks increase
Solution Approach 1:
The system performs preliminary security validations before applying updates. Timestamp verification ensures updates are current, hash value validation confirms integrity, and vehicle identifier matching prevents unauthorized updates. These preliminary checks block malicious updates before they can compromise the ECU, enabling fast remote updates while maintaining security.
Solution Approach 2:
The patent introduces intermediary verification mechanisms between the remote update source and the ECU. The timestamp, hash values, and vehicle identifier act as intermediaries that mediate the update process, verifying authenticity and integrity without requiring direct trusted connection between the update source and ECU, thus enabling remote updates with enhanced security.
2Reliability
If multiple validation checks are performed on update packages, then security and integrity are improved, but processing time and complexity increase
Solution Approach 1:
The validation process is segmented into distinct, modular checks: timestamp verification, vehicle identifier matching, and hash value validation. Each check is an independent unit that can be processed sequentially. This segmentation makes the complex validation process more manageable and efficient, as each segment can be optimized independently and failed segments don't require re-execution of all checks.
3Reliability
If timestamp verification is performed to prevent outdated updates, then update freshness is improved, but processing overhead increases
Solution Approach 1:
The timestamp is verified as a preliminary check before more intensive validation steps. This early rejection of outdated updates based on simple timestamp comparison avoids wasting processing time on subsequent hash calculations and validations for obviously invalid updates, thus minimizing processing overhead while ensuring update freshness.
Data Source
AI summary
A vehicle ECU receives an ECU update package from a remote source. The ECU verifies a first timestamp included with the ECU update package postdates a second timestamp stored onboard the vehicle in conjunction with a last-successful update of the ECU and obtains a unique vehicle identifier from the vehicle bus. The ECU obtains secure configuration data for the ECU included in a payload of the update package and calculates a first hash value using at least the unique vehicle identifier and the secure configuration data. Also, the ECU validates the update package based on comparison of the first hash value matching a second hash value included in the update package and, responsive to the first timestamp post-dating the second timestamp and validation of the update package, modifies the ECU through use of the secure configuration data.