Vehicle Odometer Storage Across ECUs and e-Fuses
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The security of odometer information in vehicles is vulnerable to manipulation, as it is typically managed by a single electronic control unit (ECU, making it susceptible to fraud and tampering.
Innovation Solution
Storing odometer information in multiple ECUs, including an in-vehicle infotainment (IVI) ECU and e-Fuses, and using a usage table to determine when to write this information to the e-Fuses, ensuring redundancy and security.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If odometer information is stored in a single ECU, then the system is simple and easy to operate, but the security and reliability of the odometer information is poor
Solution Approach 1:
The patent divides the odometer information storage function into multiple separate ECUs (odometer ECU, IVI ECU, and e-Fuse ECU) rather than using a single centralized storage unit. Each ECU stores a portion or copy of the odometer information, creating a distributed storage system that prevents single-point failure and manipulation, directly addressing the security vulnerability of centralized storage.
Solution Approach 2:
The patent introduces an e-Fuse as an intermediary component that permanently records odometer information in a tamper-resistant manner. The e-Fuse acts as a mediator between the odometer ECU and the IVI ECU, providing a secure reference point that cannot be easily modified, thereby enhancing the overall security of the odometer information system.
2Reliability
If odometer information is distributed across multiple ECUs, then the security and reliability is improved, but the device complexity increases
Solution Approach 1:
The system segments the odometer information storage across three distinct ECUs: the odometer ECU that generates the information, the IVI ECU that stores it for display and access, and the e-Fuse ECU that provides tamper-resistant permanent storage. This segmentation ensures that no single component holds complete control, improving integrity while distributing the complexity across specialized units.
Solution Approach 2:
The patent implements multiple copies of odometer information stored in different ECUs with different access characteristics. The IVI ECU holds a readable copy for user access, while the e-Fuse holds a protected copy for verification purposes. This copying strategy ensures data integrity through comparison while allowing each copy to serve its specific function.
3Object-affected harmful factors
If e-Fuse is used to store odometer information, then the resistance to manipulation is improved, but the ease of operation and access decreases
Solution Approach 1:
The e-Fuse serves as a secure intermediary that permanently stores odometer information in a tamper-resistant format. While the e-Fuse itself is not directly accessible for modification, it provides verification data that can be read and compared against the IVI ECU's stored information, maintaining both security and operational accessibility through controlled reading operations.
Solution Approach 2:
Different ECUs are assigned different quality characteristics: the IVI ECU provides easy read-access for normal operation and display, while the e-Fuse provides write-once read-many (WORM) protection for security verification. This local differentiation of access qualities allows the system to optimize for both ease of operation and resistance to manipulation in appropriate locations.
Data Source
AI summary
Example embodiments of the present disclosure provide enhancement on security of odometer information of a vehicle. According to embodiments, a method for enhancing security of odometer information is provided. The method may be performed by a system implemented in a vehicle may include: obtaining, from an odometer electronic controller unit (ECU), one or more odometer information; storing the one or more odometer information into an in-vehicle infotainment (IVI) ECU; obtaining a usage table; determining whether or not a boundary condition defined in the usage table is met; and based on determining that the boundary condition is met, storing the one or more odometer information into an e-Fuse based on the usage table.