Host-Managed Physical Data Mapping Without Flash Translation Layer

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing storage systems rely on a flash translation layer (FTL) in the storage device to manage mapping between logical and physical addresses, which can lead to inefficiencies and increased complexity.

Innovation Solution

A host-based storage system that manages physical data locations directly, eliminating the need for a flash translation layer (FTL) by using a lookup table (LUT) to associate data identification information with physical addresses, allowing the host to control data operations directly.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If a flash translation layer (FTL) is used in the storage device to manage mapping between logical and physical addresses, then the storage device can automatically handle address translation, but the system complexity increases and performance efficiency decreases

Engineering Contradiction:
Improveautomatic address translationVSAvoidstorage system complexity
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The patent extracts and removes the FTL component from the storage device, transferring the address translation function to the host system. The storage device simply stores and retrieves data at physical addresses without performing translation, thereby reducing device complexity while maintaining operational functionality at the host level.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

Instead of having the storage device translate logical addresses to physical addresses (traditional FTL approach), the patent inverts the responsibility to the host system. The host maintains a mapping structure and directly specifies physical addresses to the storage device, reversing the conventional architectural paradigm.

Inventive Principle:
Principle #13The other way round (Inversion)

2Extent of automation

If a flash translation layer (FTL) is used to manage data mapping, then address translation is handled by the storage device, but data management efficiency decreases and overhead increases

Engineering Contradiction:
Improveaddress translation automationVSAvoiddata management efficiency
Core Design Contradiction:
Extent of automationVSProductivity

Solution Approach 1:

The patent extracts the address translation function from the storage device and relocates it to the host system. The storage device performs only simple physical address operations without translation overhead, while the host handles the mapping complexity, thereby improving data management efficiency and reducing system overhead.

Inventive Principle:
Principle #2Taking out (Extraction)

3Adaptability or versatility

If a flash translation layer (FTL) is used in the storage device, then logical address mapping is handled internally, but the host cannot directly manage physical data locations

Engineering Contradiction:
Improveaddress mapping flexibilityVSAvoidhost control capability
Core Design Contradiction:
Adaptability or versatilityVSEase of operation

Solution Approach 1:

The patent inverts the conventional architecture by removing the FTL from the storage device and placing address translation capability in the host. This allows the host to directly manage physical data locations and maintain flexible control over data placement, while the storage device simply executes write and read operations at specified physical addresses.

Inventive Principle:
Principle #13The other way round (Inversion)

Data Source

PatentUS12511230B2Storage system having a host directly manage physical data locations of storage device
Publication Date: 2025.12.30 KIOXIA CORP
  • US12511230B2 patent drawing
  • US12511230B2 patent drawing
  • US12511230B2 patent drawing

AI summary

A storage system includes a host including a processor and a memory unit, and a storage device including a controller and a non-volatile memory unit. The processor is configured to output a write command, write data, and size information of the write data, to the storage device, the write command that is output not including a write address. The controller is configured to determine a physical write location of the non-volatile memory unit in which the write data are to be written, based on the write command and the size information, write the write data in the physical write location of the non-volatile memory unit, and output the physical write location to the host. The processor is further configured to generate, in the memory unit, mapping information between an identifier of the write data and the physical write location.