Memory Subsystem Transfer Queue Retention After Program Failure

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing memory sub-systems face inefficiencies in handling program failures, leading to extensive data structure complexities and increased power consumption due to the flushing and reissuing of commands, which result in issues like read disturb, write disturb, and write amplification.

Innovation Solution

The implementation of a memory sub-system transfer queue retention component that maintains a number of commands in the transfer queue after detecting a program failure, eliminating the need for reissuing and reducing data structure complexities.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If commands are flushed and reissued after program failure, then system reliability is improved, but power consumption increases and data traffic increases

Engineering Contradiction:
Improvesystem reliabilityVSAvoidpower consumption
Core Design Contradiction:
ReliabilityVSUse of energy by moving object

Solution Approach 1:

The patent applies preliminary action by retaining commands in the transfer queue before actually executing them after failure detection. Instead of flushing and reissuing commands, the system keeps them in a retained state, ready for execution without requiring reissuance. This eliminates the energy-consuming flush and reissue operations while maintaining system reliability through controlled retry mechanisms.

Inventive Principle:
Principle #10Preliminary action

2Reliability

If commands are flushed and reissued after program failure, then system reliability is improved, but device complexity increases due to data structure complexities

Engineering Contradiction:
Improvesystem reliabilityVSAvoiddata structure complexities
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent extracts the command retention functionality from the traditional flush-and-reissue mechanism. By introducing a dedicated transfer queue retention component that selectively retains commands based on failure type and queue state, the system avoids the complexity of managing extensive data structures for command tracking and reissuance. The retention logic simplifies the overall data structure management while maintaining reliability.

Inventive Principle:
Principle #2Taking out (Extraction)

3Reliability

If commands are flushed and reissued after program failure, then system reliability is improved, but harmful effects increase such as read disturb and write amplification

Engineering Contradiction:
Improvesystem reliabilityVSAvoidread disturb and write amplification
Core Design Contradiction:
ReliabilityVSObject-generated harmful factors

Solution Approach 1:

The patent converts the potential harm of command reissuance into benefit by selectively retaining commands instead of flushing them. By analyzing failure types and queue states, the system determines which commands can be safely retained and executed without causing read disturb or write amplification. This transforms the harmful reissue operation into a beneficial selective execution strategy that maintains reliability while minimizing adverse effects.

Inventive Principle:
Principle #22Blessing in disguise (Convert harm into benefit)

Data Source

PatentUS20250341986A1Memory sub-system transfer queue retention
Publication Date: 2025.11.06 MICRON TECHNOLOGY INC
  • US20250341986A1 patent drawing
  • US20250341986A1 patent drawing
  • US20250341986A1 patent drawing

AI summary

A method includes issuing a program command to a logic unit (LUN) of a memory device, writing a plurality of commands to a transfer queue within the memory device, detecting a program failure for the LUN of the memory device, and maintaining a number of the plurality of commands in the transfer queue.