Vehicle Data Recorder Lock Flag Mechanism
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing data recorders in vehicles face challenges in ensuring data integrity and preventing overwriting of critical interaction data recorded around the time of events like collisions, which is essential for forensic investigations, especially with the increasing complexity of ADAS and autonomous driving systems.
Innovation Solution
A vehicle system comprising a first data recorder that stores interaction data between the autonomous driving system and the driver, and a second data recorder that stores event data, with mechanisms to protect critical interaction data by setting a lock flag and prioritizing its upload to a remote server, ensuring it is not overwritten and is uploaded successfully.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If the first data recorder continuously overwrites old interaction data with new interaction data to maintain storage efficiency, then storage productivity is improved, but data integrity is compromised when critical event-related data is overwritten
Solution Approach 1:
The system performs preliminary actions by setting a lock flag on interaction data before it can be overwritten. When the second data recorder detects an event, it sends a locking request signal that pre-protects the relevant interaction data from being overwritten, ensuring critical data is preserved before the overwrite operation occurs.
Solution Approach 2:
A lock flag mechanism acts as an intermediary between the first data recorder's overwrite operation and the interaction data. The lock flag serves as a mediator that blocks the overwrite operation when set, allowing the system to reconcile the conflicting needs of continuous storage and data preservation.
2Reliability
If the system prioritizes uploading critical interaction data to the remote server to ensure data integrity, then data reliability is improved, but transmission time and complexity increase
Solution Approach 1:
The system applies different quality treatments to different data based on their importance. Critical interaction data associated with events (marked with lock flag) receives priority upload treatment, while non-critical data follows normal upload procedures. This local differentiation optimizes transmission time by focusing resources on important data.
Solution Approach 2:
The second data recorder provides feedback to the first data recorder by sending locking request signals when events are detected. This feedback mechanism enables the first recorder to identify and prioritize upload of critical data, reducing unnecessary transmission time for non-critical data while ensuring timely upload of event-related data.
3Reliability
If the system implements a locking mechanism to protect critical interaction data from overwriting, then data integrity is improved, but device complexity increases due to additional flags and signals
Solution Approach 1:
The system changes a simple parameter (the lock flag state) to control data protection rather than implementing a complex protection mechanism. By toggling a single flag parameter between locked and unlocked states, the system achieves data integrity protection with minimal added complexity.
Solution Approach 2:
The lock flag is a simple copied state that can be replicated across multiple data records without significant complexity. When the second data recorder sends a locking request, the first data recorder copies the locked state to multiple interaction data records that need protection, efficiently extending protection coverage without proportional increases in system complexity.
Data Source
AI summary
An embodiment vehicle system includes a telecommunication device that enables communication between a vehicle and a remote server, a first data recorder configured to store, in a first internal storage, a plurality of interaction data indicating timestamped interactions that occur between an autonomous driving system of the vehicle and a driver while driving and configured to protect main interaction data of the plurality of interaction data that is stored proximate to a point in time of an occurrence of a predefined event from being overwritten with new interaction data without first being uploaded to the remote server, and a second data recorder configured to store, in a second internal storage, event data indicating a state of the vehicle for a predetermined time before and after the event occurs.