Dynamic Aggressor Queue Mitigation Threshold for Memory

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Memory devices face challenges in managing aggressor queues effectively, leading to situations where the queue becomes full, necessitating controller intervention and reducing memory availability, due to the fixed mitigation threshold not adapting to the queue's fill level.

Innovation Solution

The mitigation threshold is dynamically adjusted based on the number of filled slots in the aggressor queue, increasing as the queue fills up, allowing for more lenient identification of aggressors when space is plentiful and stricter criteria when space is scarce, thereby reducing the likelihood of queue overflow and controller intervention.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If a fixed mitigation threshold is used for aggressor identification, then the identification criteria remain consistent, but the queue becomes full more frequently requiring controller intervention

Engineering Contradiction:
Improvememory availabilityVSAvoidcontroller intervention time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent applies dynamics by making the mitigation threshold adjustable rather than fixed. The threshold is dynamically modified based on the aggressor queue fill status - when the queue is nearly full, the threshold is increased to be more selective about which addresses are added, preventing queue overflow and reducing controller interventions.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The system implements feedback by monitoring the aggressor queue fill level and using this information to adjust the mitigation threshold. The threshold calculation incorporates the number of filled slots in the aggressor queue, creating a closed-loop control mechanism that adapts to current system conditions.

Inventive Principle:
Principle #23Feedback

2Reliability

If the mitigation threshold is lowered to identify more aggressors, then more victim rows can be protected, but the queue fills up faster requiring more frequent controller intervention

Engineering Contradiction:
Improvedata protection coverageVSAvoidmemory operation continuity
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The mitigation threshold is dynamically adjusted based on queue conditions. When the aggressor queue has available space, the threshold allows more aggressive identification of potential threats. When the queue is filling up, the threshold increases to be more selective, balancing protection needs with operational continuity.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The patent changes the threshold parameter based on queue fill level. The threshold is calculated as a function of the number of filled slots in the aggressor queue, transforming a static parameter into a variable one that adapts to system state, thereby balancing protection coverage with queue management.

Inventive Principle:
Principle #35Parameter changes

3Productivity

If the mitigation threshold is increased to reduce queue fills, then fewer addresses are added to the queue, but victim rows in danger may not be refreshed in time

Engineering Contradiction:
Improvememory operation continuityVSAvoiddata integrity
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The threshold dynamically adapts to queue conditions rather than remaining fixed. This allows the system to maintain higher thresholds when needed for continuity while still providing adequate protection when queue capacity is available, resolving the trade-off between productivity and reliability.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The mitigation threshold parameter is changed based on the aggressor queue fill status. By making the threshold a function of queue occupancy, the system can adjust its selectivity in real-time, ensuring data integrity when capacity permits while maintaining operational continuity when the queue is full.

Inventive Principle:
Principle #35Parameter changes

4Measurement precision

If a low mitigation threshold is used, then aggressors are identified more readily, but the aggressor queue becomes full requiring controller intervention

Engineering Contradiction:
Improveaggressor detection sensitivityVSAvoidcontroller intervention delay
Core Design Contradiction:
Measurement precisionVSLoss of time

Solution Approach 1:

The detection sensitivity is dynamically adjusted through the threshold modification. When the aggressor queue has space, the threshold allows sensitive detection of potential aggressors. When the queue is filling up, the threshold becomes less sensitive to prevent overflow, thereby avoiding controller intervention delays.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The system uses feedback from the aggressor queue fill level to adjust the detection threshold. The threshold calculation incorporates the number of filled slots, creating a feedback mechanism that balances detection sensitivity with queue management to prevent overflow and controller interventions.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS20240427497A1Apparatuses and methods for aggressor queue based mitigation threshold
Publication Date: 2024.12.26 MICRON TECHNOLOGY INC
  • US20240427497A1 patent drawing
  • US20240427497A1 patent drawing
  • US20240427497A1 patent drawing

AI summary

Apparatuses and methods aggressor queue mitigation based threshold. A memory device detects aggressor rows by changing a count value associated with the row when it is accessed and comparing the count value to a mitigation threshold. Identified aggressor rows are stored in an aggressor queue. The value of the mitigation threshold is set based on a number of addresses which are stored in the aggressor queue. For example the threshold may increase as the number of addresses in the queue increases.