Non-Volatile Memory Root Table Power Recovery

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing data storage devices with non-volatile memory face challenges in ensuring storage reliability due to unexpected power-off events, which disrupt write operations and require inefficient power recovery procedures.

Innovation Solution

A data storage device with a controller that allocates non-volatile memory into blocks, maintaining a root table with metadata updates, allowing for simplified power recovery by copying the root table as metadata, enabling reliable block usage determination without comparing metadata with the root table, and utilizing dummy data to ensure continuous storage.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If the controller compares metadata with the root table to determine block reliability during power recovery, then data integrity can be verified, but the power recovery procedure becomes time-consuming and computationally intensive

Engineering Contradiction:
Improvedata integrityVSAvoidpower recovery time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The controller performs preliminary actions by maintaining the root table in a first block and establishing block usage information beforehand. During power recovery, the controller can directly use this pre-established root table to determine block reliability without needing to perform time-consuming comparisons, as the root table already contains the necessary information about valid and invalid blocks from before the power interruption occurred.

Inventive Principle:
Principle #10Preliminary action

2Reliability

If the controller maintains separate metadata for each block, then block usage information can be tracked accurately, but the data structure becomes complex and requires more storage overhead

Engineering Contradiction:
Improveblock usage trackingVSAvoiddata structure complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The controller merges the root table maintenance function to consolidate block usage information. Instead of maintaining separate metadata structures for each block, the root table in the first block serves as a centralized repository that tracks the validity status of all other blocks. This unified approach reduces data structure complexity while maintaining accurate block usage tracking through a single coherent structure.

Inventive Principle:
Principle #5Merging (Combining)

3Reliability

If the controller performs comprehensive metadata verification during power recovery, then storage reliability is ensured, but computational resources are consumed inefficiently

Engineering Contradiction:
Improvestorage reliabilityVSAvoidcomputational energy
Core Design Contradiction:
ReliabilityVSUse of energy by moving object

Solution Approach 1:

The controller extracts only the essential information needed for power recovery by maintaining the root table that specifically records block validity status. During power recovery, the controller extracts and uses only the relevant block usage information from the root table without performing comprehensive metadata verification across all blocks. This selective extraction approach ensures storage reliability while minimizing computational energy consumption by avoiding unnecessary verification operations.

Inventive Principle:
Principle #2Taking out (Extraction)

Data Source

PatentUS10817215B2Data storage system and control method for non-volatile memory
Publication Date: 2020.10.27 SILICON MOTION INC
  • US10817215B2 patent drawing
  • US10817215B2 patent drawing
  • US10817215B2 patent drawing

AI summary

A data structure for storing specific information of a non-volatile memory is disclosed. To store a file, the non-volatile memory is allocated to provide a first block and a second block to store file content and file system data separately. A root table is maintained on the non-volatile memory, wherein the root table contains usage information of the first block and the second block. When updating the root table to update the usage information of the first block and the second block, the usage information of the first block and the second block is also updated to the second block as metadata. The power restoration procedure is greatly simplified.