Memory Controller Refresh Logic for Read Disturb vs Retention Loss

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current memory systems fail to distinguish between read disturb-induced charge loss (RDCL) and data retention charge loss (DR), leading to inefficient and resource-wasting refresh operations, which accelerate wear and reduce the lifespan of memory devices.

Innovation Solution

A memory controller that selectively refreshes data based on distinguishing between RDCL and DR charge loss by performing an RDCL scan operation, immediately refreshing data if RDCL is detected and delaying refreshes for DR charge loss until a certain threshold is reached.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If refresh operations are performed frequently to maintain data integrity, then data reliability is improved, but memory device wear increases and lifespan decreases

Engineering Contradiction:
Improvedata integrityVSAvoidmemory device lifespan
Core Design Contradiction:
ReliabilityVSDuration of action of stationary object

Solution Approach 1:

The system dynamically changes the refresh interval parameter based on detected charge loss patterns. When RDCL is detected, refresh operations are triggered immediately; when only DR is present, refresh operations are delayed until thresholds are reached. This adaptive parameter adjustment optimizes the balance between data integrity and device lifespan.

Inventive Principle:
Principle #35Parameter changes

Solution Approach 2:

The memory system performs self-diagnosis by monitoring its own charge loss patterns and automatically adjusts refresh operations accordingly. The system serves itself by detecting RDCL versus DR conditions and making autonomous decisions about when refresh operations are necessary, eliminating the need for external control.

Inventive Principle:
Principle #25Self-service

2Reliability

If refresh operations are performed immediately upon detecting charge loss, then data reliability is improved, but computational overhead and resource consumption increase

Engineering Contradiction:
Improvedata reliabilityVSAvoidcomputational overhead
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system changes the operational parameter from immediate refresh to conditional refresh based on the type of charge loss detected. By distinguishing between RDCL and DR, the system adjusts the refresh timing parameter to avoid unnecessary immediate refreshes while maintaining data reliability.

Inventive Principle:
Principle #35Parameter changes

Solution Approach 2:

Instead of performing full refresh operations for all charge loss cases, the system applies partial action by delaying refreshes for DR conditions until necessary. This reduces the frequency and intensity of refresh operations while still addressing reliability issues when RDCL is detected.

Inventive Principle:
Principle #16Partial or excessive action

3Reliability

If all charge loss is treated as RDCL requiring immediate refresh, then data reliability is improved, but unnecessary refresh operations waste resources and accelerate wear

Engineering Contradiction:
Improvedata reliabilityVSAvoidresource efficiency
Core Design Contradiction:
ReliabilityVSLoss of energy

Solution Approach 1:

The system segments charge loss into two distinct categories: RDCL (read disturb-induced charge loss) and DR (data retention charge loss). This segmentation allows differentiated handling where only RDCL triggers immediate refresh operations, while DR is managed with delayed refreshes, optimizing resource efficiency while maintaining reliability.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system changes the refresh policy parameter based on the type of charge loss. For RDCL, immediate refresh is applied; for DR, delayed refresh until threshold is reached is applied. This parameter change based on charge loss classification eliminates unnecessary refresh operations and optimizes resource efficiency.

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentUS20260024595A1Differentiating read disturb from retention charge loss
Publication Date: 2026.01.22 MICRON TECHNOLOGY INC
  • US20260024595A1 patent drawing
  • US20260024595A1 patent drawing
  • US20260024595A1 patent drawing

AI summary

Systems and methods for providing a memory sub-system controller selectively refresh data by differentiating between read disturb charge loss from data retention charge loss. The controller performs a read disturb induced charge loss (RDCL) scan operation on a portion of a set of memory components. The controller determines that a first bit error count (BEC) associated with the RDCL scan operation on the portion of the set of memory components transgresses a threshold value and determines whether the first BEC corresponds to a second BEC that represents data retention (DR) charge loss. The controller selectively refreshes data stored in the portion of the set of memory components based on determining whether the first BEC corresponds to the second BEC that represents DR charge loss.