Directed Data Migration Using Physical-Location Context Metadata

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing storage systems struggle to efficiently manage memory operations and provide context information to hosts without requiring extensive host mechanisms for tracking, especially in systems using address translation or log-structured file systems where data origins are unclear.

Innovation Solution

Storing context metadata, such as back references or object identifiers, with data writes to enable hosts to understand the characteristics of data at any physical memory location, facilitating efficient data migration and management.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If address translation or log-structured file systems are used to manage storage, then storage efficiency and flexibility are improved, but the ability to track data origins and context is lost

Engineering Contradiction:
Improvestorage efficiencyVSAvoiddata context
Core Design Contradiction:
Adaptability or versatilityVSLoss of information

Solution Approach 1:

The patent segments the storage system into distinct components: address translation layers for flexibility and context metadata structures for tracking. By separating these functions, the system achieves both storage efficiency through address translation and data context preservation through dedicated metadata structures that record origin information independently of the translation mechanisms.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces context metadata as an intermediary element that bridges address translation operations and data origin tracking. This metadata acts as a mediator that carries context information through the address translation process, allowing the system to maintain data provenance information even when physical addresses are transformed or obfuscated by translation layers.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Measurement precision

If hosts track data context themselves, then data management precision is improved, but host complexity increases

Engineering Contradiction:
Improvedata context trackingVSAvoidhost mechanisms
Core Design Contradiction:
Measurement precisionVSDevice complexity

Solution Approach 1:

The patent implements self-service by having the storage system automatically generate, maintain, and manage context metadata without requiring host intervention. The storage system autonomously tracks data origins, updates context information during write operations, and preserves this metadata through address translation, thereby achieving precise data context tracking while keeping the host simple and unaware of the underlying complexity.

Inventive Principle:
Principle #25Self-service

3Reliability

If data is migrated to optimize performance or wear, then storage reliability is improved, but data context information may be lost

Engineering Contradiction:
Improvestorage reliabilityVSAvoidcontext metadata
Core Design Contradiction:
ReliabilityVSLoss of information

Solution Approach 1:

The patent applies preliminary action by pre-associating context metadata with data at the time of initial write operations. This context information is prepared and attached in advance, creating a persistent link between data and its origin information. When data migration occurs for wear leveling or performance optimization, this pre-established metadata linkage ensures context information is automatically preserved and transferred with the migrated data, eliminating the need for complex tracking during migration events.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS12578900B1Techniques for directed data migration
Publication Date: 2026.03.17 RADIAN MEMORY SYSTEMS INC
  • US12578900B1 patent drawing
  • US12578900B1 patent drawing
  • US12578900B1 patent drawing

AI summary

A host stores “context” metadata for logical block addresses (LBAs) in a manner tied to physical location. Notwithstanding log-structured or copy on write processes, the host is then provided with immediate context when the host is called upon to assist a memory controller with data identified by physical location, for example, for memory reconfiguration, garbage collection, wear leveling or other processes. The metadata for example can provide the host with insight as to which data may be moved to enhance performance optimization and where that data can be placed. In one embodiment, the host writes back one or more references that span multiple layers of indirection in concert with write of the underlying data; in another embodiment, the context can point to other metadata.