Flash Memory Wear Mitigation via RAM Aggregation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Flash memory in devices, especially those used in IoT and M2M environments, experiences rapid wear-out due to the limited number of program/erase cycles, leading to premature failure as third-party applications generate an unlimited number of cycles, rendering the system inoperable.

Innovation Solution

A memory control process that aggregates program/erase requests in RAM and sends them to flash memory at intervals, reducing the number of actual write cycles and extending the flash memory's lifespan by using a RAM/cache for third-party applications, thereby mitigating wear-out.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If third-party applications write/read data to/from flash memory frequently, then application functionality is improved, but flash memory wear increases and lifetime decreases

Engineering Contradiction:
Improveapplication functionalityVSAvoidflash memory lifetime
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The patent introduces a file system layer as an intermediary between applications and flash memory. This file system implements wear-leveling algorithms that distribute write operations across different physical blocks, preventing any single block from being overused. It also manages read operations to minimize unnecessary writes, thereby protecting flash memory while maintaining application functionality.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent dynamically changes the mapping parameters between logical file system addresses and physical flash memory blocks. By implementing dynamic block allocation and remapping strategies, the system adapts the storage parameters based on wear patterns and usage frequencies, extending flash memory lifetime without affecting application performance.

Inventive Principle:
Principle #35Parameter changes

2Productivity

If flash memory is used for frequent data writes, then data storage capability is improved, but the number of program/erase cycles increases leading to premature failure

Engineering Contradiction:
Improvedata storage capabilityVSAvoidflash memory operational duration
Core Design Contradiction:
ProductivityVSDuration of action of stationary object

Solution Approach 1:

The patent divides the flash memory into multiple logical blocks and sub-blocks that can be independently managed. By segmenting the storage space and implementing a block allocation strategy, the system can perform writes to specific segments while leaving others intact, thereby reducing the frequency of full-program/erase cycles and extending overall memory operational duration.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent performs preliminary wear-leveling and block allocation actions before actual data writes occur. The file system pre-maps logical addresses to physical blocks in a way that distributes future write operations evenly, preventing concentrated wear on specific blocks and extending the flash memory's operational duration.

Inventive Principle:
Principle #10Preliminary action

3Productivity

If multiple program/erase operations are performed on flash memory, then data update capability is improved, but power consumption increases

Engineering Contradiction:
Improvedata update capabilityVSAvoidpower consumption
Core Design Contradiction:
ProductivityVSUse of energy by moving object

Solution Approach 1:

The patent implements periodic buffering of write operations in RAM before flushing them to flash memory in batch operations. By accumulating multiple small writes in volatile memory and then performing consolidated periodic writes to non-volatile memory, the system reduces the total number of program/erase cycles, thereby lowering power consumption while maintaining data update capability.

Inventive Principle:
Principle #19Periodic action

Solution Approach 2:

The patent maintains continuous write operations in the file system cache while deferring actual flash memory programming. By keeping the write stream continuous in RAM and only initiating power-intensive flash programming when the cache is full or a timeout occurs, the system optimizes the balance between data update capability and power consumption.

Inventive Principle:
Principle #20Continuity of useful action

Data Source

PatentUS10474570B2Flashware usage mitigation
Publication Date: 2019.11.12 CISCO TECHNOLOGY INC
  • US10474570B2 patent drawing
  • US10474570B2 patent drawing
  • US10474570B2 patent drawing

AI summary

In one embodiment, a memory control process of a device receives a plurality of program/erase (P/E) requests for a flash memory of the device. The memory control process then stores data associated with the plurality of P/E requests in a random access memory (RAM) of the device, and aggregates the plurality of P/E requests into a single P/E operation. The memory control process may then send the single P/E operation to the flash memory at a given interval to update the flash memory with the data stored in the RAM.