Memory Refresh Scheduling for Low-Latency Data Storage

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Data storage devices face reliability issues due to errors in stored data, leading to increased latency as they spend time correcting errors during read operations, and existing refresh methods like HMR are not customizable and inefficient.

Innovation Solution

Implement a data storage device with a controller that allows for targeted refresh operations on specific memory areas on demand, providing full visibility to the host on reliability status and enabling efficient, power-saving refresh processes.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If the data storage device performs background refresh operations on the entirety of memory, then reliability is improved, but time consumption and power consumption increase

Engineering Contradiction:
Improvedata reliabilityVSAvoidrefresh time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent segments the memory into multiple blocks and allows the host to selectively identify and refresh only specific blocks that need reliability improvement. This segmentation enables targeted refresh operations rather than refreshing the entire memory, thereby reducing time consumption while maintaining reliability for critical data areas.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent implements local quality by allowing different refresh operations on different memory blocks based on their specific reliability needs. The host can identify particular blocks requiring refresh and send targeted refresh commands, so that only those specific areas receive the refresh treatment, optimizing both time and power efficiency.

Inventive Principle:
Principle #3Local quality

2Reliability

If the data storage device performs error correction during read operations, then data reliability is improved, but latency increases

Engineering Contradiction:
Improvedata reliabilityVSAvoidread latency
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent applies preliminary action by performing refresh operations on memory blocks before the host requests read operations. The host can proactively identify blocks that need refreshing and initiate refresh commands in advance, so that when data is subsequently read from these blocks, the reliability is already improved and no additional error correction time is needed during the read operation.

Inventive Principle:
Principle #10Preliminary action

3Reliability

If the data storage device performs full memory refresh operations, then all data reliability is improved, but power consumption increases

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

Solution Approach 1:

The patent segments memory into multiple refreshable blocks and enables selective refreshing of only those blocks identified by the host as needing reliability improvement. This segmentation prevents power consumption associated with refreshing entire memory when only specific blocks require attention, thereby optimizing power efficiency.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent implements partial action by allowing the host to specify exactly which memory blocks need refreshing rather than performing a complete memory refresh. This partial refresh approach consumes only the necessary power required for the identified blocks, avoiding excessive power consumption from unnecessary refresh operations on other memory areas.

Inventive Principle:
Principle #16Partial or excessive action

4Adaptability or versatility

If the data storage device allows host-manual refresh commands, then refresh customization is improved, but device complexity increases

Engineering Contradiction:
Improverefresh customizationVSAvoidcontroller complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent applies universality by designing the controller to handle both automatic background refresh operations and host-manual refresh commands through a unified interface. The same controller infrastructure supports multiple refresh modes (automatic and manual, full and partial), reducing the need for separate dedicated circuits and thereby limiting the increase in device complexity despite enhanced functionality.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Data Source

PatentUS12573441B2Data storage device and method for optimized refresh
Publication Date: 2026.03.10 SANDISK TECHNOLOGIES LLC
  • US12573441B2 patent drawing
  • US12573441B2 patent drawing
  • US12573441B2 patent drawing

AI summary

A data storage device and method for optimized refresh are provided. In one embodiment, a data storage device is provided comprising a memory and a controller. The controller is configured to: receive, from a host, an identification of a location in the memory; calculate an estimated time to refresh the location in the memory; send the estimated time to the host; and refresh the location in the memory. Other embodiments are provided, and each of the embodiments can be used alone or in combination.