Vehicle ECU Session Information Volatile Non-Volatile Memory Management
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing onboard systems face challenges in quickly restoring secure communication after a communication anomaly due to limitations in writing to non-volatile memory, which either requires excessive writes or fails to restore security if session information is not stored.
Innovation Solution
The system employs ECUs with both volatile and non-volatile memory, where session information is stored in volatile memory initially and then transferred to non-volatile memory upon detecting a communication anomaly, with the option to generate new session information that excludes sequence numbers and includes updated vehicle-specific values, reducing the number of writes to non-volatile memory.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If all session information is stored in non-volatile memory, then secure communication can be restored quickly after reset, but the number of writes to non-volatile memory becomes excessive
Solution Approach 1:
The patent divides session information storage into two parts: volatile memory for active session data and non-volatile memory for backup session data. This segmentation allows the system to maintain quick restoration capability while reducing write operations to non-volatile memory, as only necessary backup operations are performed rather than continuous updates of all session information.
Solution Approach 2:
The system performs preliminary actions by storing session information in volatile memory first, then selectively copying to non-volatile memory only when communication anomalies are detected. This preliminary storage in volatile memory ensures quick restoration is possible while avoiding excessive writes to non-volatile memory.
2Loss of energy
If session information is not stored in non-volatile memory, then the number of writes is reduced, but secure communication cannot be restored quickly after reset
Solution Approach 1:
By segmenting storage between volatile and non-volatile memory, the system achieves both reduced write operations and maintained restoration capability. Volatile memory handles active sessions while non-volatile memory provides selective backup, resolving the contradiction between write frequency and restoration speed.
Solution Approach 2:
Volatile memory acts as an intermediary between active session operations and non-volatile memory storage. It temporarily holds session information and mediates the selective copying process to non-volatile memory only when needed, enabling both low write counts and quick restoration.
3Reliability
If session information is frequently updated in non-volatile memory, then communication anomalies can be detected, but the writing frequency increases excessively
Solution Approach 1:
The system performs preliminary anomaly detection in volatile memory before triggering non-volatile memory writes. This allows communication anomalies to be detected and handled efficiently while minimizing the frequency of writes to non-volatile memory, as only confirmed anomalies trigger backup operations.
Solution Approach 2:
The system uses feedback from volatile memory anomaly detection to control non-volatile memory write operations. When anomalies are detected in volatile memory, the system feedbacks this information to trigger selective writes to non-volatile memory, ensuring reliable anomaly detection while avoiding excessive writing frequency.
Data Source
AI summary
An onboard system includes a first ECU and a second ECU respectively installed in a vehicle and configured to communicate with each other via a transmission path using session information. A first processor and a second processor are configured to detect a precursor to a communication anomaly. In a case in which the communication anomaly precursor has not been detected, the first processor and the second processor cause first session information to be stored in first volatile memory and second volatile memory, while not causing the first session information to be stored in second non-volatile memory or fourth non-volatile memory. In a case in which the communication anomaly precursor has been detected, the first processor and the second processor cause the first session information to be stored in at least the second non-volatile memory and the fourth non-volatile memory.