Memory Cache Release Timing for Verified Program Operations

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing cache program operations in memory sub-systems result in data recovery issues and degraded performance due to the premature commitment of data to memory arrays before verification status is known, leading to inefficient cache storage management and reduced throughput.

Innovation Solution

Implementing a cache program operation with data encoding and multiple cache release sub-operations to optimize the timing of cache storage release, allowing early storage of data for subsequent operations, using a reduced set of data caches (PDC0, PDC1, and PDC2) to manage cache storage efficiently.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If data is committed to memory arrays before verification status is known, then memory bandwidth is utilized efficiently, but data recovery issues occur and reliability deteriorates

Engineering Contradiction:
Improvememory bandwidth utilizationVSAvoiddata recovery
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The patent applies preliminary action by performing verification of programmed data before committing it to the memory array. The cache holds the verified data ready for commitment, ensuring that only confirmed good data is written to the memory array, thus preventing data recovery issues while maintaining efficient bandwidth utilization.

Inventive Principle:
Principle #10Preliminary action

2Reliability

If cache storage is released only after complete program operation, then data integrity is maintained, but cache storage efficiency and throughput deteriorate

Engineering Contradiction:
Improvedata integrityVSAvoidthroughput
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent segments the cache release process into multiple stages corresponding to different verification completion points. Instead of releasing the entire cache only after complete verification, the cache is released in segments as verification of different data portions is completed, thereby improving throughput while maintaining data integrity through staged commitment.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The cache is released preliminarily as soon as verification status is known, before the complete program operation finishes. This allows subsequent operations to proceed without waiting for full verification completion, improving throughput while data integrity is preserved because commitment to the memory array occurs only after verification.

Inventive Principle:
Principle #10Preliminary action

3Device complexity

If a reduced set of data caches is used, then device complexity is reduced, but cache management capability deteriorates

Engineering Contradiction:
Improvenumber of data cachesVSAvoidcache management capability
Core Design Contradiction:
Device complexityVSAdaptability or versatility

Solution Approach 1:

The patent changes the parameter of cache organization from multiple separate data caches to a reduced set of data caches with enhanced encoding capability. By modifying how data is encoded and managed in the reduced cache structure, the system maintains adequate cache management capability while reducing device complexity.

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentUS12566711B2Cache management during execution of a program operation
Publication Date: 2026.03.03 MICRON TECHNOLOGY INC
  • US12566711B2 patent drawing
  • US12566711B2 patent drawing
  • US12566711B2 patent drawing

AI summary

Control logic in a memory device executes a first programming operation to program the set of memory cells to a set of programming levels. A first cache ready signal is generated, the first cache ready signal indicating to a host system to send first data associated with a second programming operation to an input/output (I/O) data cache of the memory device. A second cache ready signal is generated, the second cache ready signal indicating to the host system to send second data associated with the next programming operation to the I/O data cache. The first data associated with the second programming operation is caused to be stored in a cache storage of the memory device.