Flash Memory Controller Latency Management

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Isochronous systems face challenges with unpredictable latency times in NAND flash memory, which is problematic for read operations and data integrity, especially in environments where flow control is not feasible, leading to issues with inventory management and system responsiveness.

Innovation Solution

A flash memory storage device with mechanisms within the controller to accommodate physical limitations and host processor needs, including error correction and scrub operations to maintain data integrity, allowing for efficient use in read-intensive and isochronous systems without wait or flow control signals.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If NAND flash memory is used to replace ROM for rapid access, then adaptability and reprogrammability are improved, but latency predictability and reliability deteriorate due to background operations

Engineering Contradiction:
ImprovereprogrammabilityVSAvoidlatency predictability
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The controller performs background operations (error correction, scrub operations, wear leveling) in advance or during idle periods before they would interfere with critical read operations. This preliminary action ensures that when a read command is received, the memory is already in a ready state with predictable latency, while still maintaining the reprogrammability benefits of flash memory.

Inventive Principle:
Principle #10Preliminary action

2Reliability

If flow control signals are introduced to manage latency, then latency predictability is improved, but device complexity and system interface complexity increase

Engineering Contradiction:
Improvelatency predictabilityVSAvoidinterface complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The flash memory controller autonomously manages its own background operations and latency issues without requiring external flow control signals. The controller internally schedules and executes error correction, scrub operations, and wear leveling in a manner that does not interfere with read operations, making the memory device self-sufficient and eliminating the need for additional control signals or complex interface protocols.

Inventive Principle:
Principle #25Self-service

3Reliability

If background operations are performed to ensure data integrity, then reliability is improved, but read operation speed and responsiveness deteriorate

Engineering Contradiction:
Improvedata integrityVSAvoidread operation speed
Core Design Contradiction:
ReliabilityVSSpeed

Solution Approach 1:

The controller performs data integrity operations (error correction, scrub operations) in advance during idle periods or before critical read operations are needed. This ensures that when a read command is received, the data is already verified and ready, maintaining both data integrity and read speed without conflict.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

Background operations are performed periodically during idle periods rather than continuously or on-demand. The controller schedules error correction and scrub operations at regular intervals when the system is not experiencing high read traffic, ensuring data integrity while minimizing impact on read operation speed during active periods.

Inventive Principle:
Principle #19Periodic action

Data Source

PatentUS8099632B2Urgency and time window manipulation to accommodate unpredictable memory operations
Publication Date: 2012.01.17 SANDISK TECHNOLOGIES LLC
  • US8099632B2 patent drawing
  • US8099632B2 patent drawing
  • US8099632B2 patent drawing

AI summary

The variable latency associated with flash memory due to background data integrity operations is managed in order to allow the flash memory to be used in isochronous systems. A system processor is notified regularly of the nature and urgency of requests for time to ensure data integrity. Minimal interruptions of system processing are achieved and operation is ensured in the event of a power interruption.