Data Storage Device Accidental Delete Protection

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Users often lose data due to accidental deletion, especially in professions handling large amounts of data, and existing solutions either slow down data storage devices or are ineffective in restoring deleted data due to overwriting or garbage collection processes.

Innovation Solution

A data storage device with a controller that manages separate sets of physical blocks with distinct logical-to-physical address tables and block lists, allowing for versioning and prioritization of data, enabling the host to hint for enhanced accidental delete protection by moving critical data to a secondary set of blocks with different memory characteristics for backup and restoration.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If data is duplicated for backup protection, then data reliability is improved, but device complexity and storage space requirements increase

Engineering Contradiction:
Improvedata reliabilityVSAvoiddevice complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent segments the storage device into multiple blocks with different characteristics (first block with fast write speed, second block with high retention). This segmentation allows critical data to be stored in the second block for protection while non-critical data resides in the first block, achieving data reliability without duplicating all data and thus avoiding excessive device complexity

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent applies local quality by assigning different storage characteristics to different blocks. The second block is specifically optimized for data retention to protect critical information, while the first block maintains fast write performance for general data. This localized optimization provides reliability where needed without compromising overall system performance or requiring full data duplication

Inventive Principle:
Principle #3Local quality

2Reliability

If all data is duplicated for backup, then accidental delete protection is improved, but write speed decreases due to the large amount of data to be written

Engineering Contradiction:
Improveaccidental delete protectionVSAvoidwrite speed
Core Design Contradiction:
ReliabilityVSSpeed

Solution Approach 1:

The patent implements partial action by duplicating only critical data that requires accidental delete protection, rather than duplicating all data. The controller identifies and moves only the necessary critical data to the second block for backup, thereby maintaining fast write speeds for non-critical data while still providing protection where needed

Inventive Principle:
Principle #16Partial or excessive action

3Reliability

If critical data is moved to a secondary block for protection, then accidental delete protection is improved, but data access time increases

Engineering Contradiction:
Improveaccidental delete protectionVSAvoiddata access time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent introduces an intermediary component - the controller - that manages data between the first and second blocks. The controller maintains mapping relationships between logical addresses and physical block locations, enabling fast data access by directing reads to the appropriate block without requiring the host system to be aware of the data's physical location. This intermediary management minimizes access time while maintaining protection

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS11960766B2Data storage device and method for accidental delete protection
Publication Date: 2024.04.16 SANDISK TECHNOLOGIES LLC
  • US11960766B2 patent drawing
  • US11960766B2 patent drawing
  • US11960766B2 patent drawing

AI summary

A data storage device and method for accidental delete protection are provided. In one embodiment, a data storage device comprises a memory and a controller. The memory comprises a first set of physical blocks and a second set of physical blocks, where the first and second sets of physical blocks are associated with separate logical-to-physical address tables and/or separate block lists. The controller is configured to write data received from a host in the first set of physical blocks and move the data from the first set of physical blocks to the second set of physical blocks in response to the host requesting that a modified version of the data be written in the memory. Other embodiments are possible, and each of the embodiments can be used alone or together in combination.