SSD Controller Data Erasure Processing Function

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing solid state drives (SSDs) using NAND flash memory face inefficiencies in data erasure, as logical erasure of data does not immediately release storage blocks, leading to unused areas and potential storage shortages, which current garbage collection methods do not consistently address.

Innovation Solution

The SSD controller actively monitors NAND flash memory states, specifies partition formats and file systems, and physically erases data when logical erasure is detected, using a data erasure processing function to identify and free up blocks, even without host instructions.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If logical erasure of data is performed, then data is marked as deleted, but storage blocks are not immediately released and may remain unused

Engineering Contradiction:
Improvedata erasure completenessVSAvoidavailable storage capacity
Core Design Contradiction:
ReliabilityVSQuantity of substance

Solution Approach 1:

The controller proactively monitors the non-volatile memory for logically erased data and initiates physical erasure operations before storage blocks are completely filled with new data. This preliminary action ensures that storage blocks are released in a proactive manner, preventing the scenario where blocks remain unused while new data needs to be written.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The controller continuously monitors the state of the non-volatile memory, detecting when data has been logically erased. Based on this feedback, the controller automatically initiates physical erasure operations to release storage blocks, creating a closed-loop system that responds to data erasure events and maintains optimal storage utilization.

Inventive Principle:
Principle #23Feedback

2Quantity of substance

If garbage collection is performed to release storage blocks, then available capacity increases, but the process is not consistent and may be triggered only under specific conditions

Engineering Contradiction:
Improveavailable storage capacityVSAvoidconsistency of block release
Core Design Contradiction:
Quantity of substanceVSReliability

Solution Approach 1:

The controller autonomously monitors and manages the physical erasure process without requiring external intervention or being limited by specific trigger conditions. The system self-regulates by detecting logically erased data and automatically initiating physical erasure operations, ensuring consistent and reliable block release regardless of host operations or timing conditions.

Inventive Principle:
Principle #25Self-service

3Ease of operation

If the controller waits for host instructions to erase data, then operation simplicity is maintained, but storage performance deteriorates due to delayed block release

Engineering Contradiction:
Improvecontroller operation simplicityVSAvoidSSD performance
Core Design Contradiction:
Ease of operationVSProductivity

Solution Approach 1:

The controller performs physical erasure operations proactively before the host needs to write new data, eliminating delays. By monitoring for logically erased data and initiating erasure in advance, the system maintains ease of operation (the host simply writes data normally) while dramatically improving performance through immediate block availability.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS11907567B2Memory system having a controller with a data erasure processing function
Publication Date: 2024.02.20 KIOXIA CORP
  • US11907567B2 patent drawing
  • US11907567B2 patent drawing
  • US11907567B2 patent drawing

AI summary

According to one embodiment, a memory system is connectable to a host. The memory system includes a non-volatile memory and a controller electrically connected to the non-volatile memory and configured to control the non-volatile memory. The controller is configured to specify a partition format of a predetermined partition included in the non-volatile memory based on master boot record information stored in the non-volatile memory. The controller is configured to specify a file system that manages the predetermined partition. The controller is configured to specify logically erased first data and physically erase the first data when logical erasure of data in the predetermined partition is detected by a method consistent with the specified file system.