SSD Data Path Signatures for Soft Error Detection and Correction

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional systems inadequately address soft errors in Solid State Drives (SSDs), particularly in components like SRAM, DRAM, and digital logic, which can lead to device hang, data corruption, and unrecoverable errors due to ionizing radiation, affecting system reliability.

Innovation Solution

The implementation of a soft error detection and correction mechanism that generates and uses multiple signatures (e.g., E2E and ECC) to validate data integrity along the data path between the host and non-volatile memory, allowing real-time detection and correction of soft errors without increasing overhead on NAND flash memory devices, optimizing data path protection and storage utilization.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If soft error detection and correction mechanisms are implemented in SSD components, then system reliability is improved, but device complexity increases

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

Solution Approach 1:

The patent applies preliminary action by generating signatures (such as CRC or hash values) of data before it is written to or read from volatile memory components. These signatures are stored in non-volatile memory alongside the data. When data is read back, the signature is regenerated and compared with the stored signature to detect soft errors before they propagate, preventing reliability issues without requiring complex real-time monitoring during data transmission.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent introduces signatures as intermediary elements that mediate between the data and the error detection process. Instead of directly monitoring data integrity through complex hardware, the signature acts as a simplified intermediary that can be easily computed and compared. This intermediary mechanism enables reliable error detection while keeping the overall device complexity manageable by avoiding direct complex monitoring of data paths.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Measurement precision

If multiple signatures are used to validate data integrity, then measurement precision is improved, but device complexity increases

Engineering Contradiction:
Improvedata integrity validation accuracyVSAvoiddevice complexity
Core Design Contradiction:
Measurement precisionVSDevice complexity

Solution Approach 1:

The patent segments the error detection process into multiple independent signature validations. Instead of using one complex validation mechanism, it employs multiple simpler signatures (e.g., different CRC polynomials or hash functions) that are computed and compared separately. This segmentation allows for higher measurement precision in detecting data integrity issues while keeping each individual signature computation simple and manageable.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent applies partial action by using multiple signatures only when necessary for critical data paths or high-reliability requirements. For less critical operations, a single signature or no signature validation may suffice. This selective application of multiple signatures achieves high measurement precision where needed while avoiding the full complexity overhead in all operations, balancing accuracy with device complexity.

Inventive Principle:
Principle #16Partial or excessive action

Data Source

PatentUS12189476B2Soft error detection and correction for data storage devices
Publication Date: 2025.01.07 KIOXIA CORP
  • US12189476B2 patent drawing
  • US12189476B2 patent drawing
  • US12189476B2 patent drawing

AI summary

Various implementations described herein relate to systems and methods for detecting soft errors, including but not limited to, errors introduced after reading a codeword from a non-volatile memory, and before providing data to a host. Embodiments can include generating the codeword from the non-volatile memory to obtain at least input data, and determining validity of the input data using a first signature after processing the input data through a data path. If it is determined that the input data is valid using the first signature, the input data is sent to a host.