Multi-OS Vehicle Backup Control for Power-Loss Data Consistency
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Integrated vehicular devices face challenges in ensuring data consistency across multiple operating systems, particularly when backing up data due to the limited rewrite capabilities of non-volatile storage units and the volatility of main memory, which can lead to inconsistencies and difficulties in maintaining data integrity during power state changes and system failures.
Innovation Solution
The implementation of a vehicular device with multiple operating systems, a control unit, non-volatile storage, and a backup unit that synchronizes backup timing and data passing between systems, using a notification unit to manage power state changes and prevent data updates during backup processes, ensuring consistency and reliability across systems.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Stability of the object's composition
If data is stored in non-volatile first storage unit, then data persistence is improved, but the limited rewrite capability causes wear and potential data loss
Solution Approach 1:
The storage system is segmented into two distinct storage units: a non-volatile first storage unit for persistent data and a volatile second storage unit for temporary data. This segmentation allows each storage unit to be optimized for its specific function, reducing wear on the non-volatile storage while maintaining data persistence requirements.
Solution Approach 2:
The system performs preliminary backup actions by copying data from the volatile second storage unit to the non-volatile first storage unit before power loss can occur. This preliminary action ensures that important data is preserved in persistent storage before the volatile memory loses its contents.
2Adaptability or versatility
If multiple operating systems operate independently, then system functionality is improved, but data consistency across systems deteriorates
Solution Approach 1:
The backup units from different operating systems are merged into a coordinated system. When one OS detects a power state change, it triggers backup operations that other OSes can participate in, combining their backup capabilities to ensure comprehensive data consistency across all systems.
Solution Approach 2:
The system implements feedback mechanisms where backup units monitor each other's operations and power state changes. When one OS completes a backup or detects a power state change, this information is fed back to other OSes, allowing them to coordinate their backup operations and maintain data consistency.
3Reliability
If backup operations are performed frequently, then data integrity is improved, but the limited rewrite capability of non-volatile storage is exhausted faster
Solution Approach 1:
The system performs partial backup operations, copying only the necessary data from the volatile second storage unit to the non-volatile first storage unit based on power state changes rather than continuously backing up all data. This reduces the frequency of rewrite operations while maintaining data integrity.
Solution Approach 2:
Backup operations are performed periodically based on power state changes (AC power connection/disconnection events) rather than continuously. This periodic action triggered by specific events reduces wear on the non-volatile storage while ensuring data is backed up at appropriate intervals.
4Speed
If volatile second storage unit is used for temporary data, then write speed is improved, but data loss occurs upon power loss
Solution Approach 1:
The system performs preliminary backup actions by copying data from the volatile second storage unit to the non-volatile first storage unit before power loss can occur. This preliminary action ensures that important data is preserved in persistent storage before the volatile memory loses its contents.
Solution Approach 2:
The non-volatile first storage unit acts as an intermediary between the volatile second storage unit and permanent data storage. Data is temporarily held in the fast volatile memory for quick access and writing, then transferred through the non-volatile storage as an intermediary to ensure persistence, combining the speed advantages of volatile memory with the safety of non-volatile storage.
Data Source
AI summary
A vehicular device includes a control unit, a non-volatile first storage unit, a second storage unit, a notification unit, and a backup unit. Multiple operating systems operate in the control unit. The backup unit is provided in each operating system and is configured to back up, on the first storage unit, data temporarily stored in the second storage unit. The backup unit is configured to back up the data on the first storage unit upon being notified of the change in the power supply state by the notification unit. The backup unit running on one operating system is configured to pass, to the backup unit provided in another operating system, target data or information identifying the target data. When a failure occurred in the one operating system, the backup unit provided in the other operating system backs up the target data or the information identifying the target data.