Storage Controller Read Count Management for Data Disturbance

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Data storage devices face challenges in managing read operations across multiple memory regions, leading to potential data damage due to read disturbance, and existing solutions do not effectively prevent unnecessary read reclaim operations.

Innovation Solution

A data storage device with a controller that manages read counts and reference information across multiple memory regions, selectively increasing read counts based on the sequence of read operations and performing management operations to prevent data damage and unnecessary read reclaim operations.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If read operations are performed frequently on multiple memory regions, then data access efficiency is improved, but read disturbance increases causing data damage

Engineering Contradiction:
Improvedata access efficiencyVSAvoidread disturbance
Core Design Contradiction:
ProductivityVSObject-affected harmful factors

Solution Approach 1:

The controller performs preliminary actions by tracking read sequences and proactively increasing read counts for memory regions that are likely to be read again soon. This preliminary tracking and count adjustment prevents data damage by preparing recovery mechanisms before read disturbance actually occurs, rather than waiting for damage to manifest.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system implements feedback by continuously monitoring read operations and using the read sequence information to dynamically adjust read counts. The controller receives feedback from each read operation, analyzes the sequence pattern, and adjusts the read count accordingly, creating a closed-loop system that adapts to actual access patterns and prevents read disturbance damage.

Inventive Principle:
Principle #23Feedback

2Reliability

If read count is increased for all memory regions, then data damage prevention is improved, but unnecessary read reclaim operations increase

Engineering Contradiction:
Improvedata damage preventionVSAvoidunnecessary read reclaim operations
Core Design Contradiction:
ReliabilityVSLoss of energy

Solution Approach 1:

Instead of uniformly increasing read counts across all memory regions, the controller applies local quality by selectively increasing read counts only for specific memory regions based on their read sequence characteristics. Memory regions that exhibit patterns indicating imminent re-reading receive increased read counts, while other regions maintain normal read counts, thereby preventing unnecessary read reclaim operations.

Inventive Principle:
Principle #3Local quality

Solution Approach 2:

The controller applies partial action by increasing read counts only when necessary based on read sequence analysis, rather than applying excessive action to all memory regions. This selective approach ensures that read count increases are applied minimally and precisely where needed to prevent data damage, avoiding the waste of unnecessary read reclaim operations on regions that don't require protection.

Inventive Principle:
Principle #16Partial or excessive action

Data Source

PatentUS10073642B2Data storage device and operating method thereof
Publication Date: 2018.09.11 SK HYNIX INC
  • US10073642B2 patent drawing
  • US10073642B2 patent drawing
  • US10073642B2 patent drawing

AI summary

A method for operating a data storage device including a plurality of memory regions. The method includes performing a read operation for a first memory region, increasing a read count based on read sequences of the first memory region and a second memory region which has been read before the read operation for the first memory region, and performing a management operation for the plurality of memory regions based on the read count.