NAND Volume Management with Dynamic SLC and MLC Partitioning
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current non-volatile memory devices face challenges in efficiently managing both high and normal reliability data on a single device, with existing multi-mode MLC memory systems prone to errors and requiring external file management systems, which complicates data storage and updates.
Innovation Solution
A non-volatile memory device with a volume management system that includes a meta-volume directory for centralized management of MLC and SLC partitions, allowing dynamic adjustment of memory assignments and error correction codes to ensure data integrity, and tracks bad blocks and wear-leveling operations within the device.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Quantity of substance
If MLC NAND architecture is used to store both user data and high reliability data on a single device, then storage capacity and economy are improved, but data reliability deteriorates
Solution Approach 1:
The patent divides the MLC NAND memory device into distinct operational modes (SLC mode for high reliability data and MLC mode for user data) and spatial partitions (code area for file management system and data areas for different data types). This segmentation allows the same physical memory to serve multiple reliability requirements simultaneously, resolving the contradiction between storage capacity and data reliability.
Solution Approach 2:
The patent applies different quality characteristics to different regions of the memory device. The code area stores the file management system with high reliability requirements, while data areas can operate in either SLC mode (high reliability) or MLC mode (high capacity). This local differentiation of quality allows each region to be optimized for its specific purpose, enabling both high capacity and high reliability where needed.
2Adaptability or versatility
If external file management systems are used to manage MLC and SLC partitions, then management flexibility is improved, but system complexity and error proneness increase
Solution Approach 1:
The patent merges the file management system with the memory device itself by storing it in the code area of the same MLC NAND device. This integration eliminates the need for separate external management systems, reducing overall system complexity while maintaining management flexibility through the unified device architecture. The merged system manages both SLC and MLC partitions internally, reducing error sources at external interfaces.
Solution Approach 2:
The memory device performs its own file management functions through the integrated file management system stored in its code area. The device self-manages partitioning, wear-leveling, and data placement without requiring external management controllers, thereby reducing system complexity and eliminating errors that would occur at external management interfaces.
3Device complexity
If permanent partition assignment is used for SLC and MLC storage regions, then device simplicity is improved, but adaptability and update capability deteriorate
Solution Approach 1:
The patent implements dynamic partition assignment where the file management system can reallocate data areas between SLC and MLC modes based on changing requirements. The partitioning is not fixed but can be adjusted through updates to the file management system, enabling the device to adapt to new applications and data requirements while maintaining operational simplicity through automated management.
Data Source
AI summary
Embodiments for partitioning a non-volatile memory device is described. In one embodiment a memory system includes a first addressable range of memory blocks for storing different types of data. The memory system is partitioned to include a second addressable range of memory blocks capable of storing data indicating attributes of the first addressable range of memory blocks. The second addressable range of memory blocks may also be periodically updated such that the capacities of the first addressable range of memory blocks may be dynamically adjusted depending on application needs and changes to the non-volatile memory device over time. In some embodiments, one partition of a memory device may be configured for high reliability data storage while a second partition is configured for normal reliability storage.