Opportunistic Memory Data Integrity Scans

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Fixed schedules for background data integrity scans in memory subsystems often collide with host system requests, leading to delays and reduced quality of service, especially in systems with multiple servers.

Innovation Solution

Performing background data integrity scans on an opportunistic basis, where scans are conducted during idle periods or when activity levels are below a threshold, allowing for flexibility and minimizing collisions with host requests.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If background data integrity scans are performed on a fixed schedule, then data reliability is maintained, but quality of service deteriorates due to collisions with host system requests

Engineering Contradiction:
Improvedata reliabilityVSAvoidquality of service
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The patent applies dynamics by transitioning from a static fixed schedule to a dynamic opportunistic scanning approach. The memory subsystem controller continuously monitors host system activity levels and adapts the timing of background data integrity scans based on real-time conditions. When host activity is low, scans are performed; when host activity is high, scans are delayed or cancelled. This dynamic adaptation resolves the contradiction by maintaining data reliability through regular scans while preserving quality of service by avoiding collisions with host requests.

Inventive Principle:
Principle #15Dynamics

2Reliability

If background data integrity scans are performed frequently, then data reliability is improved, but time consumption increases due to collisions with host requests

Engineering Contradiction:
Improvedata reliabilityVSAvoidtime consumption
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent implements feedback by having the memory subsystem controller monitor host system activity levels and use this information to determine when to perform background data integrity scans. The controller receives feedback about host request patterns and adjusts scan timing accordingly. This feedback mechanism ensures scans are performed frequently enough to maintain data reliability while avoiding time-consuming collisions with host requests, as the controller learns from past activity patterns to optimize scan scheduling.

Inventive Principle:
Principle #23Feedback

3Ease of operation

If background data integrity scans are delayed to avoid host requests, then quality of service is improved, but data reliability deteriorates due to longer intervals between scans

Engineering Contradiction:
Improvequality of serviceVSAvoiddata reliability
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The patent applies preliminary action by proactively identifying and executing background data integrity scans during predicted or actual idle periods in host system activity. Rather than passively delaying scans until conflicts arise, the controller anticipates suitable scanning windows by monitoring host request patterns and schedules scans in advance during these opportunistic periods. This ensures scans are performed regularly enough to maintain data reliability while preserving quality of service by completing scans during naturally occurring gaps in host activity.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS12067253B2Opportunistic background data integrity scans
Publication Date: 2024.08.20 MICRON TECHNOLOGY INC
  • US12067253B2 patent drawing
  • US12067253B2 patent drawing
  • US12067253B2 patent drawing

AI summary

Exemplary methods, apparatuses, and systems include determining that a memory component to be subjected to a background data integrity scan does not currently satisfy an activity threshold. The background data integrity scan is delayed in response to determining memory component does not satisfy the activity threshold. In response to detecting a background data integrity scan trigger event, the background data integrity scan is performed.