Storage Sub-System Using Write-Once Memory for Critical Code Protection
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current solid state non-volatile memory sub-systems for computers are expensive and fail to protect critical operating code from malicious overwriting.
Innovation Solution
A solid state non-volatile storage sub-system that combines write-once and write-many memory devices with a page-based interface, where critical file system structures are stored in write-once memory to prevent overwriting, and updated structures are stored in write-many memory, enabling protection and recovery of system configurations.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If present solid state non-volatile memory sub-systems are used, then storage capacity is provided, but cost is high and critical code protection is failed
Solution Approach 1:
The storage sub-system is segmented into two distinct memory devices: a write-once memory device for storing critical file system structures and a write-many memory device for storing updated structures. This segmentation allows critical code to be protected from overwriting while maintaining cost-effectiveness by using different memory types for different purposes.
Solution Approach 2:
Different quality levels of memory protection are applied locally to different data types. Critical file system structures stored in write-once memory receive maximum protection (write-once property), while non-critical data in write-many memory allows flexible updates. This local differentiation optimizes both security and cost.
2Reliability
If write-once memory is used for critical structures, then protection from overwriting is achieved, but device complexity increases
Solution Approach 1:
The storage sub-system is divided into two separate memory devices with distinct access characteristics. The write-once memory device stores critical file system structures that require protection, while the write-many memory device stores updateable data. This segmentation provides protection without requiring complex protection mechanisms within a single device.
Solution Approach 2:
The system uses an intermediary approach where the write-once memory acts as a protective layer for critical structures, while the write-many memory serves as a flexible storage layer for updates. The controller manages interactions between these two memory types, providing protection without direct complex intervention in the memory cells themselves.
3Reliability
If separate write-once and write-many memory devices are used, then critical code protection is achieved, but device complexity increases
Solution Approach 1:
The storage system is segmented into two memory devices with clearly defined roles: write-once memory for critical protection and write-many memory for flexible storage. This functional segmentation simplifies the control logic compared to implementing complex protection mechanisms within a single device, as each memory type operates with its native, simple access characteristics.
Data Source
AI summary
Methods and apparatus for a solid state non-volatile storage sub-system of a computer is provided. The storage sub-system may include a write-many storage sub-system memory device including write-many memory cells, a write-once storage sub-system memory device including write-once memory cells, and a page-based interface that is adapted to read and write the write-once and write-many storage sub-system memory devices. Numerous other aspects are provided.