Flash Memory Management Wear Leveling

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Flash memory, particularly NAND flash memory, faces performance degradation due to the high number of write and erase cycles, leading to wear and tear, which reduces its longevity and efficiency in data storage and retrieval.

Innovation Solution

A method and system for managing flash memory by writing unsecure and secure data records to specific blocks based on available space and versioning, incrementing record version values, and efficiently deleting records to minimize the number of write and erase cycles, thereby reducing wear and tear and improving rewrite execution time.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If data is rewritten in flash memory, then data storage functionality is maintained, but the number of write and erase cycles increases causing performance degradation

Engineering Contradiction:
Improvedata storage functionalityVSAvoidperformance degradation
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent segments the flash memory into multiple blocks and implements a wear-leveling mechanism that distributes write and erase cycles across different blocks. By maintaining multiple copies of data in different blocks and selectively erasing only the necessary blocks, the system reduces the concentration of wear on any single block, thereby extending overall memory lifespan and maintaining performance.

Inventive Principle:
Principle #1Segmentation

2Reliability

If entire blocks are erased for rewriting data, then data integrity is ensured, but the number of erase cycles increases reducing memory longevity

Engineering Contradiction:
Improvedata integrityVSAvoidmemory longevity
Core Design Contradiction:
ReliabilityVSDuration of action of stationary object

Solution Approach 1:

The patent applies local quality by implementing selective block erasure rather than erasing entire blocks uniformly. The system identifies and erases only the specific blocks that contain outdated or obsolete data versions, while preserving other blocks that still contain valid data. This localized approach maintains data integrity where needed while minimizing unnecessary erase cycles in other areas, thereby extending memory longevity.

Inventive Principle:
Principle #3Local quality

3Reliability

If multiple versions of data records are stored, then data versioning and recovery are improved, but storage space efficiency decreases

Engineering Contradiction:
Improvedata versioningVSAvoidstorage space efficiency
Core Design Contradiction:
ReliabilityVSQuantity of substance

Solution Approach 1:

The patent implements a versioning system that allows multiple data record versions to be stored temporarily, but automatically discards older versions when they are no longer needed for recovery or rollback operations. The system tracks version references and actively manages the lifecycle of data versions, recovering storage space by removing superseded versions while maintaining sufficient version history for data integrity and recovery purposes.

Inventive Principle:
Principle #34Discarding and recovering

Data Source

PatentUS9311229B2System and method for managing flash memory
Publication Date: 2016.04.12 MALIKIE INNOVATIONS LTD
  • US9311229B2 patent drawing
  • US9311229B2 patent drawing
  • US9311229B2 patent drawing

AI summary

A system and method for flash memory management is provided. In particular, the system and methods herein provide for management of flash memory, particularly NAND flash memory, in a manner that potentially reduces the number of write/erase cycles typically experienced by a data storage device. When unsecure data records are to be written to the flash memory, the new or updated unsecure data records are stored in the first available location in the flash memory (e.g. a block) providing a best fit for the data records. Where the data records are updates, the updated version is stored with an incremented version number to indicate that the updated version is the current version. Older versions of the data records are deleted during garbage collection. When secure data records are to be written to the flash memory, new or updated secure data records are stored in the location in the flash memory with the most available space. Any older versions of secure data records are immediately deleted.