Memory Controller Table Error Correction via RAID Decoding

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The management of memory devices, particularly in UFS communications architecture, is complicated due to frequent access and changes in internal management information, leading to increased processing time and error prevention needs, with existing solutions lacking effective methods to handle these issues without introducing side effects.

Innovation Solution

A method and apparatus for table management in memory devices using table error correction, specifically employing RAID protection mechanisms to manage internal tables by searching for parity identifiers and performing RAID decoding to generate recovered table pages, thereby reducing processing load and enhancing performance.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If multiple types of internal management information are changed frequently to manage memory devices, then the memory device can adapt to frequent access and file management, but the processing time is increased

Engineering Contradiction:
Improvememory device adaptabilityVSAvoidprocessing time
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The patent segments internal management information into multiple types (e.g., L2P mapping tables, P2L mapping tables, valid page count tables) and organizes them into heterogeneous RAID protection groups. This segmentation allows selective management and protection of different table types, reducing the processing overhead when updating management information while maintaining adaptability.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent implements preliminary RAID protection by pre-configuring heterogeneous RAID protection groups for different types of internal management information tables. This preliminary action ensures that when management information needs to be updated, the protected structure is already in place, reducing the time required for error prevention and recovery operations.

Inventive Principle:
Principle #10Preliminary action

2Reliability

If RAID protection mechanism is applied to protect internal management tables, then data reliability is improved, but device complexity is increased

Engineering Contradiction:
Improvetable protection reliabilityVSAvoidmanagement structure complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent applies local quality by implementing heterogeneous RAID protection selectively for different types of internal management information tables based on their specific protection needs. Not all tables receive the same level or type of protection, allowing the system to achieve reliable protection where needed while avoiding unnecessary complexity for less critical tables.

Inventive Principle:
Principle #3Local quality

Solution Approach 2:

The patent creates a universal heterogeneous RAID protection framework that can accommodate multiple types of management tables (L2P, P2L, valid page counts, etc.) within a unified protection structure. This multi-functional approach simplifies the overall management complexity by providing a single protection mechanism that handles diverse table types, rather than requiring separate protection schemes for each.

Inventive Principle:
Principle #6Universality (Multi-functionality)

3Reliability

If more processing operations are performed to prevent errors during unwanted events, then system reliability is improved, but processing time is further increased

Engineering Contradiction:
Improveerror prevention capabilityVSAvoiderror handling time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent implements beforehand cushioning by pre-establishing RAID protection groups and configuring redundancy for internal management tables before unwanted events occur. This prior cushioning ensures that when errors or unwanted events happen, the recovery process can proceed efficiently using the pre-configured protection structure, rather than requiring extensive processing to establish protection from scratch.

Inventive Principle:
Principle #11Beforehand cushioning (Prior cushioning)

4Reliability

If heterogeneous tables are protected with RAID protection mechanism, then table management reliability is improved, but processing complexity is increased

Engineering Contradiction:
Improveheterogeneous table protectionVSAvoidprocessing complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent applies parameter changes by implementing heterogeneous RAID protection with configurable parameters for different table types. The protection mechanism can adjust its behavior based on the specific characteristics of each table type (e.g., different redundancy levels, different recovery priorities), allowing reliable protection while managing processing complexity through parameterized control rather than fixed complex procedures.

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentUS12050783B1Method and apparatus for performing table management of memory device in predetermined communications architecture with aid of table error correction
Publication Date: 2024.07.30 SILICON MOTION INC
  • US12050783B1 patent drawing
  • US12050783B1 patent drawing
  • US12050783B1 patent drawing

AI summary

A method for performing table management of a memory device in a predetermined communications architecture with aid of table error correction and associated apparatus are provided. The method may include: utilizing the memory controller to perform a table error correction procedure to manage at least one table regarding internal management of the memory device, for example: when any error of any table page occurs, searching for a first parity identifier backward, and searching for a second parity identifier forward; selecting a next page of a page storing the first parity identifier to be a first page, selecting a page storing the second parity identifier to be a last page, and preparing at least a set of pages among multiple RAID-protection pages, for being decoded; and performing a RAID decoding operation on the set of pages to generate a recovered table page to be a replacement of the any table page.