Autonomous Vehicle Memory Logging for Crash Data Retention
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing memory systems in autonomous vehicles do not automatically log data generated by vehicle systems, leading to data loss in volatile memory during adverse events like accidents, making it difficult to determine the cause of such events.
Innovation Solution
A memory device that autonomously collects and stores data from various vehicle systems without host controller intervention, transferring critical data to non-volatile memory and transmitting it to a central server for analysis, enabling real-time configuration updates.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Speed
If sensor data is stored in volatile memory during vehicle operation, then data can be accessed quickly for real-time processing, but data is lost during power loss or adverse events
Solution Approach 1:
The memory device proactively copies data from volatile memory to non-volatile memory before power loss or adverse events occur. The memory device monitors for conditions indicating potential data loss risk and performs preliminary data preservation actions, ensuring data survives power interruptions while maintaining fast access during normal operation.
Solution Approach 2:
The system creates a copy of sensor data from volatile memory to non-volatile memory. The memory device reads data from the volatile memory region and writes duplicate copies to non-volatile memory, ensuring data persistence while allowing the original volatile storage to maintain fast access characteristics.
2Productivity
If a host controller manages data logging in memory systems, then data collection can be coordinated with vehicle systems, but the system requires complex host controller intervention and configuration
Solution Approach 1:
The memory device performs data logging autonomously without requiring host controller management. The memory device independently receives sensor data from vehicle systems, determines what data to log, and stores it in non-volatile memory regions. This self-service capability eliminates complex host controller intervention while maintaining efficient data collection.
Solution Approach 2:
The memory device is divided into distinct regions: volatile memory for fast access, non-volatile memory for persistent storage, and specific regions allocated for logging different sensor data types. This segmentation allows independent management of each region without requiring centralized host controller coordination, simplifying the overall system architecture.
3Loss of information
If all sensor data is retained in uncompressed form, then data quality for analysis is maximized, but storage requirements and memory system complexity increase
Solution Approach 1:
Different regions of non-volatile memory are allocated for different data retention policies. Critical safety-related sensor data is stored in uncompressed form to maintain maximum quality for analysis, while less critical data may be compressed or aggregated. This local quality differentiation optimizes storage usage while preserving data quality where most needed.
Data Source
AI summary
A method for an autonomous vehicle includes: controlling at least one system of the vehicle by a host system; automatically collecting, by a memory device, data generated by the at least one system, where the data is collected by the memory device independently of control by the host system; and storing the data in the memory device.