Memory Controller Read Count Management for Data Reliability

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current memory systems face inefficiencies in data processing due to the lack of effective mechanisms for managing read counts and performing operations like erase and reclaim, leading to potential data loss and system malfunctions.

Innovation Solution

A memory system with a controller that counts read operations for each page, determines if a read count initialization is required at check-pointing periods, and updates the read counts accordingly, enabling efficient data management and reducing the likelihood of data loss by selectively programming and updating read count information.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If read counts are updated at every check-pointing period, then data reliability is improved, but system productivity deteriorates due to excessive write operations

Engineering Contradiction:
Improvedata reliabilityVSAvoidsystem productivity
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent applies partial action by updating read counts selectively rather than at every check-pointing period. The controller determines whether update is necessary based on specific conditions (erase operations, reclaim operations, read count thresholds), performing updates only when needed rather than continuously, thus reducing unnecessary write operations while maintaining data reliability.

Inventive Principle:
Principle #16Partial or excessive action

2Productivity

If read counts are not updated frequently, then system productivity is improved, but data reliability deteriorates due to potential data loss

Engineering Contradiction:
Improvesystem productivityVSAvoiddata reliability
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The patent implements feedback mechanisms where the controller continuously monitors read counts and determines update necessity based on current system state. The controller receives feedback about erase operations, reclaim operations, and read count values, and uses this feedback to dynamically decide whether to update read counts, ensuring reliability while optimizing productivity.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The patent applies preliminary action by initializing read counts to zero before erase operations and updating read counts before reclaim operations. This ensures that read count information is prepared and available before needed, preventing data loss while avoiding unnecessary continuous updates.

Inventive Principle:
Principle #10Preliminary action

3Reliability

If read reclaim operations are performed frequently, then data reliability is improved, but device complexity increases due to additional management mechanisms

Engineering Contradiction:
Improvedata reliabilityVSAvoiddevice complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent applies local quality by implementing read reclaim operations selectively for specific pages rather than uniformly across all pages. The controller identifies pages with high read counts or specific conditions and performs reclaim operations only on those pages, maintaining reliability while avoiding unnecessary complexity in managing all pages.

Inventive Principle:
Principle #3Local quality

4Reliability

If erase operations are performed frequently, then data reliability is improved, but loss of time increases due to operation overhead

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

Solution Approach 1:

The patent applies periodic action by performing erase operations based on check-pointing periods and accumulated read counts rather than continuously. The controller monitors read counts over time and performs erase operations when specific conditions are met, balancing reliability requirements with time efficiency by avoiding excessive erase operations.

Inventive Principle:
Principle #19Periodic action

Data Source

PatentUS11922065B2Memory system and operating method thereof
Publication Date: 2024.03.05 SK HYNIX INC
  • US11922065B2 patent drawing
  • US11922065B2 patent drawing
  • US11922065B2 patent drawing

AI summary

A memory system includes a memory device and a controller suitable for controlling the memory device based on read counts for a plurality of pages of the memory device, wherein the controller counts at least one of the read counts in response to a read request, determines whether there is a page whose read count is initialized at every check-pointing period to generate a determination result, and controls the memory device to update the read counts based on the determination result.