Memory Controller Bad Block Recovery via Program Sequence Copying
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In memory systems, existing technologies lack effective methods for dynamically managing and reusing memory blocks identified as bad during runtime operations, leading to inefficiencies and reduced operational stability.
Innovation Solution
A method and apparatus for runtime bad block management, where a controller determines reusable memory blocks by analyzing program/erase cycles and operation states, copies relevant information from similar blocks, and updates block information to optimize data input/output operations without external input, thereby improving memory system stability and resource utilization.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If memory blocks are permanently discarded after being identified as bad during runtime operations, then data reliability is improved, but resource utilization and operational stability deteriorate due to loss of potentially recoverable storage capacity
Solution Approach 1:
The patent changes the status parameter of memory blocks from permanent bad block to recoverable block by analyzing program/erase cycle counts and operation states. Blocks are reclassified based on whether their P/E cycles are below a threshold and their operation states are normal, transforming them from discarded status to usable status for data storage
Solution Approach 2:
The patent converts potentially harmful bad blocks into beneficial reusable resources by implementing a recovery mechanism. Instead of permanently discarding blocks flagged as bad, the system analyzes their actual condition and repurposes recoverable blocks for storing less critical data, thereby converting a harmful situation into a beneficial expansion of usable storage capacity
2Reliability
If all memory blocks are thoroughly tested and monitored for bad block identification, then operational stability is improved, but system complexity and processing overhead increase
Solution Approach 1:
The patent performs preliminary analysis of program/erase cycle counts and operation states during normal memory operations to identify potentially recoverable blocks before they are completely discarded. This preliminary assessment allows the system to prepare recovery candidates in advance, reducing the need for complex post-failure analysis and simplifying overall bad block management
Solution Approach 2:
The memory management system performs self-diagnosis and self-recovery by automatically monitoring its own operation states and P/E cycle counts. The controller independently identifies recoverable blocks and reallocates them without requiring external intervention or complex external management systems, thereby reducing overall system complexity
3Productivity
If recoverable memory blocks are reused for data storage, then resource efficiency is improved, but data security and integrity may be compromised
Solution Approach 1:
The patent applies different quality standards to different data types by allocating recoverable blocks specifically for less critical data such as cache data, temporary files, or non-essential storage. Critical data continues to be stored in verified good blocks, while recoverable blocks serve secondary purposes. This local quality differentiation maintains data integrity for important information while maximizing resource efficiency for non-critical data
Data Source
AI summary
A memory system includes a memory device including plural non-volatile memory blocks and a controller configured to determine whether a first memory block among the plural non-volatile memory blocks is re-usable after the first memory block is determined to be a bad block and copy second block information associated with a second memory block including a second program sequence number within a set range of a first program sequence number in the first memory block to first block information of the first memory block.