Non-Volatile Memory PPR Data Tracking

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Memory modules face inefficiencies in resource utilization and tracking of post-package repairs (PPRs) due to a lack of centralized data on repair unit availability and PPR completion, leading to wasted time and resources when attempting repairs.

Innovation Solution

Storing PPR data in non-volatile memory allows for efficient tracking and utilization of repair units across reboots, enabling a memory controller to determine the availability of repair units and initiate PPRs systematically, reducing resource wastage by maintaining up-to-date information on repair unit availability and PPR completion.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If PPR data is not stored in non-volatile memory, then the memory module uses less complex storage infrastructure, but the memory controller cannot track repair unit availability across reboots leading to resource wastage

Engineering Contradiction:
Improvetracking of repair unit availabilityVSAvoidstorage infrastructure
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent applies preliminary action by pre-storing PPR data in non-volatile memory before system operation. This allows the memory controller to retrieve repair unit availability information immediately upon startup without needing to perform discovery operations, thereby maintaining reliable tracking across reboots while avoiding the complexity of implementing persistent discovery mechanisms in volatile memory systems

Inventive Principle:
Principle #10Preliminary action

2Loss of information

If the memory controller performs discovery operations to determine repair unit availability, then it can identify available repair units, but it wastes time and resources by not knowing availability beforehand

Engineering Contradiction:
Improveinformation on repair unit availabilityVSAvoiddiscovery operation time
Core Design Contradiction:
Loss of informationVSLoss of time

Solution Approach 1:

The patent implements preliminary action by pre-calculating and storing PPR data including repair unit availability information in non-volatile memory before system operation. This eliminates the need for time-consuming discovery operations at startup, as the memory controller can directly retrieve the pre-computed availability information, thereby preventing both information loss and time wastage

Inventive Principle:
Principle #10Preliminary action

3Reliability

If PPR data is stored in volatile memory only, then the storage mechanism is simpler, but the data is lost during system reboot requiring redundant resource usage

Engineering Contradiction:
Improvedata persistence across rebootsVSAvoidmemory storage type
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent applies preliminary action by storing PPR data in non-volatile memory, ensuring data persistence is established before system operation begins. This approach maintains reliability across reboots while avoiding the complexity of implementing volatile memory with persistent storage mechanisms or frequent data refresh operations

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS10068661B2Post package repair (PPR) data in non-volatile memory
Publication Date: 2018.09.04 HEWLETT PACKARD ENTERPRISE DEV LP
  • US10068661B2 patent drawing
  • US10068661B2 patent drawing
  • US10068661B2 patent drawing

AI summary

Example implementations relate to post package repair (PPR) data in non-volatile memory. In example implementations, PPR data may be stored in non-volatile memory on a memory module. PPR data may indicate how many PPRs have been performed on the memory module.