Memory Subsystem Error Handling with Selective Recovery Flows

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing error handling (EH) flows in memory sub-systems are inefficient as they perform a fixed sequence of operations regardless of the specific error mechanism, leading to increased latency and resource consumption due to unnecessary operations.

Innovation Solution

Utilize memory management data to identify specific error mechanisms and selectively perform only the necessary operations of the EH flow, bypassing those not directed at the identified errors.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If a fixed sequence of EH flow operations is performed regardless of specific error mechanisms, then comprehensive error coverage is achieved, but latency and resource consumption increase due to unnecessary operations

Engineering Contradiction:
Improveerror coverageVSAvoidlatency
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The EH flow is segmented into multiple operations (e.g., read retry, program-verify-read, RAIN recovery) that can be independently selected and executed. Each operation targets specific error mechanisms, allowing the system to divide the comprehensive error handling process into discrete, conditionally-executable segments rather than performing a monolithic fixed sequence.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The EH flow transitions from a static fixed sequence to a dynamic adaptive process. The controller dynamically determines which operations to execute based on real-time analysis of memory management data and identified error mechanisms. This dynamic adaptation allows the system to adjust the EH flow execution path according to actual error conditions, reducing unnecessary operations while maintaining comprehensive coverage for actual errors.

Inventive Principle:
Principle #15Dynamics

2Reliability

If a fixed sequence of EH flow operations is performed regardless of specific error mechanisms, then all error types are addressed, but resource consumption increases due to unnecessary operations

Engineering Contradiction:
Improveerror handling completenessVSAvoidresource consumption
Core Design Contradiction:
ReliabilityVSUse of energy by moving object

Solution Approach 1:

The system applies partial action by executing only the subset of EH flow operations necessary to address the identified error mechanisms. Instead of performing all operations (excessive action), the controller selects and executes only the relevant operations based on memory management data analysis, thereby reducing resource consumption while maintaining sufficient error handling completeness.

Inventive Principle:
Principle #16Partial or excessive action

Solution Approach 2:

The system changes the execution parameters of the EH flow based on detected error conditions. By analyzing memory management data and identifying specific error mechanisms, the controller adjusts which operations are executed, effectively changing the operational parameters of the error handling process to match actual needs rather than following a fixed parameter set.

Inventive Principle:
Principle #35Parameter changes

3Productivity

If memory management data is analyzed to identify error mechanisms and selectively perform EH operations, then latency and resource consumption are reduced, but system complexity increases

Engineering Contradiction:
Improveerror handling efficiencyVSAvoiderror handling logic
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The system performs preliminary analysis of memory management data before executing EH operations. By pre-analyzing workload characteristics, error rates, and memory conditions, the controller identifies likely error mechanisms in advance and prepares to execute only the relevant EH operations. This preliminary action simplifies the decision-making process during actual error handling, reducing the apparent complexity during critical operations.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system implements feedback loops where memory management data is continuously monitored and analyzed to inform EH flow execution decisions. The controller uses feedback from workload patterns, error rates, and memory conditions to dynamically adjust which operations are executed. This feedback mechanism automates the complexity of error handling logic, making it adaptive rather than statically complex.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS12451209B2Error handling
Publication Date: 2025.10.21 MICRON TECHNOLOGY INC
  • US12451209B2 patent drawing
  • US12451209B2 patent drawing
  • US12451209B2 patent drawing

AI summary

Respective error handling (EH) flags can be set based at least in part on media management data of a memory device. Whether any of the EH flags are set can be determined. In response to determining that at least one of the EH flags is set, a subset of a plurality of operations of an EH flow associated with the set EH flags can be performed.