Storage Copy Mapping for Background Data Transfer

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing storage devices inefficiently execute copy commands by requiring host devices to wait for internal read and write operations to complete before notifying completion, leading to communication overhead.

Innovation Solution

The storage device performs read and write operations associated with copy commands in the background after notifying the host device of completion, allowing internal operations to proceed without host intervention.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If the storage device waits for internal read and write operations to complete before notifying the host device, then data accuracy is ensured, but communication efficiency deteriorates and processing time increases

Engineering Contradiction:
Improvedata accuracyVSAvoidprocessing time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The storage device performs the read operation first and updates the mapping table to map the destination logical address to the source physical address before notifying the host device. This preliminary action allows the write operation to be deferred to background processing, reducing the host wait time while ensuring data accuracy through proper mapping updates.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

Instead of completing both read and write operations before notifying the host (traditional sequence), the invention inverts the sequence by notifying the host after only the read operation and mapping update, then performing the write operation in the background. This inversion resolves the contradiction by decoupling the notification timing from the completion of all data transfer operations.

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

2Loss of energy

If the storage device notifies the host device after completing all internal operations, then communication overhead is reduced, but processing speed deteriorates

Engineering Contradiction:
Improvecommunication overheadVSAvoidprocessing speed
Core Design Contradiction:
Loss of energyVSSpeed

Solution Approach 1:

The storage device performs the read operation and mapping table update as preliminary actions before notifying the host device. This allows the notification to be sent earlier, reducing communication overhead, while the write operation continues in the background to maintain processing speed efficiency.

Inventive Principle:
Principle #10Preliminary action

3Reliability

If the storage device performs read and write operations in the foreground, then operation reliability is ensured, but productivity deteriorates due to host device waiting

Engineering Contradiction:
Improveoperation reliabilityVSAvoidcopy command processing efficiency
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The read operation and mapping table update are performed as preliminary actions before notifying the host device. This ensures operation reliability through proper mapping establishment while improving productivity by allowing the host device to proceed without waiting for the background write operation to complete.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The write operation is performed continuously in the background after the host device has been notified, ensuring that the data transfer process continues without interruption. This maintains operation reliability while improving productivity by eliminating host device waiting time.

Inventive Principle:
Principle #20Continuity of useful action

Data Source

PatentUS12585404B2Storage device performing copy operation in background and operating method thereof
Publication Date: 2026.03.24 SAMSUNG ELECTRONICS CO LTD
  • US12585404B2 patent drawing
  • US12585404B2 patent drawing
  • US12585404B2 patent drawing

AI summary

An operating method of a storage device which includes a nonvolatile memory device and a controller controlling the nonvolatile memory device includes receiving, by the controller from a host device, a first logical address of a source range entry, a second logical address of a destination range entry, and a first copy command including a first flag that indicates a background copy is set, mapping, at the controller, a first physical address on the second logical address, mapping, at the controller, a second physical address on the second logical address and/or the first physical address, transmitting, by the controller to the host device, a first notification of a completion of the first copy command, and after the controller transmits the first notification, reading, at the nonvolatile memory device, first data stored at the first physical address and writing the first data at the second physical address.