Energy-Backed Memory Persistent Write Protocol Simplification

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The protocol for persistence handling in non-energy-backed NVDIMM-P is complex, requiring extensive communication and bookkeeping between the host and the memory module, with persistent writes needing explicit commands and unique IDs to ensure data survival during power loss.

Innovation Solution

The introduction of energy-backed memory systems that include both volatile and non-volatile storage, where writes are considered persistent once transferred to the volatile domain, eliminating the need for complex WGID management and allowing data to survive power loss through energy backing, either from a memory-level or system-level backup energy source.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If non-energy-backed NVDIMM-P protocol is used to ensure data persistence, then data can survive power loss, but the protocol becomes complex requiring extensive communication and bookkeeping between host and memory module

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

Solution Approach 1:

The patent extracts the complexity of persistence management from the host system by implementing energy-backed memory that autonomously handles data persistence. The memory module itself maintains power during system shutdown to complete pending write operations, removing the need for complex host-side protocol management while ensuring data survives power loss.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent applies preliminary action by pre-charging capacitors or using backup power sources before a power failure occurs. This stored energy is then used to complete outstanding write operations to non-volatile storage, ensuring data persistence without requiring complex real-time host intervention during the actual power failure event.

Inventive Principle:
Principle #10Preliminary action

2Reliability

If explicit PWRITE commands with WGID are used for each persistent write, then data persistence is ensured, but communication overhead and bookkeeping between host and memory module increases

Engineering Contradiction:
Improvedata persistenceVSAvoidcommunication overhead
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The memory module performs self-service by autonomously managing its own persistence operations using onboard energy storage. Once data is written to the volatile buffer, the memory module uses its internal power source to automatically complete the transfer to non-volatile storage without requiring continuous host communication or tracking of write group IDs.

Inventive Principle:
Principle #25Self-service

3Productivity

If volatile buffers and caches are used to improve write performance, then write speed increases, but data loss occurs during power failure unless complex persistence protocols are implemented

Engineering Contradiction:
Improvewrite performanceVSAvoiddata persistence
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The patent implements beforehand cushioning by providing backup energy sources (capacitors, batteries) that are pre-charged during normal operation. When power failure occurs, this stored energy cushions the system by providing sufficient power to complete the transfer of data from volatile buffers to non-volatile storage, preventing data loss while maintaining high write performance during normal operation.

Inventive Principle:
Principle #11Beforehand cushioning (Prior cushioning)

Data Source

PatentUS11016669B2Persistent write data for energy-backed memory
Publication Date: 2021.05.25 QUALCOMM INC
  • US11016669B2 patent drawing
  • US11016669B2 patent drawing
  • US11016669B2 patent drawing

AI summary

In non-energy-backed memory with persistent storage, a complex protocol is required to handle persistent writes. To address this issue, it is proposed to provide a simple protocol to handle persistent writes in energy-backed memory with persistent storage.