Flash Memory Version Number Recycling

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Flash memory devices face challenges in managing a large number of information instances, leading to overflow of reserved space for version identification values, which necessitates efficient management and recycling of version number values to prevent space overflow and optimize storage usage.

Innovation Solution

A management component within the flash memory device recycles version number values, allowing a smaller reserved space to be used for version number storage, thereby freeing up space for other uses and managing instances effectively by assigning and reassigning version numbers in a cyclical or decremental order.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If version number values are assigned to each information instance, then information instances can be tracked and managed, but the reserved space for version identification values will overflow when the quantity of instances becomes large

Engineering Contradiction:
Improveinformation instance trackingVSAvoidreserved space capacity
Core Design Contradiction:
ReliabilityVSQuantity of substance

Solution Approach 1:

The patent recycles version number values by identifying when a version number is no longer needed (when all information instances with that version number have been erased) and reassigning it to new information instances. This discarding of obsolete version numbers and recovering them for reuse prevents the reserved space from overflowing while maintaining reliable tracking of information instances.

Inventive Principle:
Principle #34Discarding and recovering

Solution Approach 2:

The system monitors its own version number usage and automatically recycles version numbers when they become available. The flash memory device itself manages the version number allocation and recycling without external intervention, detecting when version numbers can be reused and reassigning them to maintain efficient space utilization.

Inventive Principle:
Principle #25Self-service

2Reliability

If a large reserved space is allocated for version identification values, then overflow can be prevented, but less space is available for other uses

Engineering Contradiction:
Improveversion number storage capacityVSAvoidavailable storage space
Core Design Contradiction:
ReliabilityVSQuantity of substance

Solution Approach 1:

Instead of allocating a large fixed reserved space, the patent implements dynamic recycling of version number values. Version numbers are discarded from the reserved space when no longer needed and recovered for reuse, allowing the same reserved space to serve many more information instances than its capacity would suggest, thereby freeing up space for other uses.

Inventive Principle:
Principle #34Discarding and recovering

Solution Approach 2:

The version number allocation system transitions from a static, fixed allocation approach to a dynamic recycling approach. The reserved space size remains constant, but its effective capacity increases through continuous reuse of version numbers, allowing the system to adapt to varying information instance quantities without expanding the reserved space.

Inventive Principle:
Principle #15Dynamics

3Reliability

If version number values are continuously incremented, then each information instance receives a unique identifier, but the version identification value will eventually overflow

Engineering Contradiction:
Improveunique identificationVSAvoidversion identification value range
Core Design Contradiction:
ReliabilityVSQuantity of substance

Solution Approach 1:

The patent abandons the continuous increment approach in favor of recycling version numbers. When a version number reaches its maximum value or becomes unavailable, the system discards the exhausted sequence and recycles earlier version numbers that have been freed up by erasure operations, preventing overflow while maintaining unique identification for active information instances.

Inventive Principle:
Principle #34Discarding and recovering

Solution Approach 2:

The version number allocation follows a periodic pattern rather than a linear continuous increment. Version numbers are reused in cycles, with the system periodically recycling version numbers from the past when they become available again, creating a repeating sequence that prevents overflow while ensuring unique identification within each active cycle.

Inventive Principle:
Principle #19Periodic action

Data Source

PatentUS12118216B2Recycled version number values in flash memory
Publication Date: 2024.10.15 MICRON TECHNOLOGY INC
  • US12118216B2 patent drawing
  • US12118216B2 patent drawing
  • US12118216B2 patent drawing

AI summary

Various embodiments include methods, apparatus, and systems for assigning a plurality of version number values to instances of a logical entity of a memory device. Each version number value of the plurality version number values may be separately assigned to one of the instances of the logical entity. The version number values may be recycled after the plurality of version number values are assigned. Other embodiments including additional methods, apparatus, and systems are disclosed.