Non-Volatile Memory Controller Spare Block Recycling
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current non-volatile memory control techniques are inefficient in managing spare blocks and data transfer, leading to reduced storage capacity and increased wear on flash memory due to unnecessary dummy data writing and inadequate recycling of source blocks during power failures.
Innovation Solution
A controller allocates spare blocks to manage active blocks for data transfer, using a single active block for small-amount garbage collection and limiting source blocks to optimize spare block recycling, while utilizing a flag to determine data transfer paths and prevent excessive block usage.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If traditional non-volatile memory control techniques are used for managing spare blocks and data transfer, then the storage device can operate, but spare block consumption is excessive and flash memory wear increases
Solution Approach 1:
The patent implements a source block recycling mechanism where blocks that have completed data transfer are released back to the spare block pool. The controller identifies source blocks whose valid data has been completely transferred to destination blocks, and releases these source blocks as spare blocks for future use. This recovering mechanism reduces spare block consumption and extends flash memory life by maximizing the utilization of available blocks.
2Productivity
If traditional data transfer methods are used, then data can be transferred between blocks, but unnecessary dummy data writing occurs reducing storage efficiency
Solution Approach 1:
The patent implements a selective data transfer mechanism that transfers only the necessary valid data from source blocks to destination blocks, avoiding the transfer of dummy data. The controller identifies and transfers only the valid data portions based on valid data indicators, performing partial action rather than complete block transfers. This eliminates unnecessary dummy data writing operations, improving storage efficiency and reducing energy consumption.
3Reliability
If source blocks are not properly released after data transfer, then data integrity is maintained, but spare block pool is depleted reducing future operational capacity
Solution Approach 1:
The patent implements a feedback mechanism where the controller continuously monitors the status of data transfer operations and the validity of data in source blocks. After completing data transfer to a destination block, the controller detects that the source block's valid data has been fully transferred, and triggers a release operation to return the source block to the spare block pool. This feedback-based management ensures data integrity is maintained while dynamically replenishing the spare block pool.
4Adaptability or versatility
If multiple active blocks are used for data transfer, then data transfer flexibility increases, but block management complexity and spare block consumption increase
Solution Approach 1:
The patent segments the block management into distinct roles: active blocks for current data operations, source blocks for data transfer origins, and destination blocks for data transfer targets. Each block type has specific management rules and transition conditions. This segmentation provides structured flexibility for data transfer operations while maintaining manageable complexity through clear role definitions and transition protocols.
Data Source
AI summary
High-efficiency control technology for non-volatile memory is shown. A controller allocates spare blocks of a non-volatile memory to provide a first active block and writes data issued by a host to the first active block. When the number of spare blocks is less than a threshold number and valid data of a first source block is less than a critical data amount, the controller uses the first active block as a data transfer destination for the valid data from the first source block.