Memory Controller Event Log Indexing for Storage Space Reduction

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current memory systems face challenges in efficiently storing and managing event log information, particularly in three-dimensional NAND memories, where limited storage space requires innovative methods to reduce data volume while maintaining data integrity.

Innovation Solution

The proposed solution involves an operation method for a memory system that records event log information using only index numbers and parameter values, reducing storage space requirements. This method includes generating event log information with index numbers and parameter values when the firmware runs different functional modules, and using a code file to retrieve the complete content of the event log information.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If complete event log information is stored in memory systems, then data integrity is maintained, but storage space is consumed

Engineering Contradiction:
Improvedata integrityVSAvoidstorage space
Core Design Contradiction:
ReliabilityVSQuantity of substance

Solution Approach 1:

The event log information is segmented into two parts: (1) compact index data stored in the memory system containing only index numbers and parameter values, and (2) detailed event log content stored externally in code files. This segmentation allows the memory system to maintain data integrity through indexes while minimizing storage space consumption by storing only essential identifying information locally.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

Instead of storing complete event log information in the memory system, the patent creates simplified copies (indexes) that contain only index numbers and parameter values. The full event log content is copied to external code files, allowing the memory system to reference complete information without physically storing it, thus resolving the contradiction between data integrity and storage space.

Inventive Principle:
Principle #26Copying

2Quantity of substance

If event log information is stored in compact form with index numbers and parameter values, then storage space is reduced, but data completeness may be compromised

Engineering Contradiction:
Improvestorage spaceVSAvoiddata completeness
Core Design Contradiction:
Quantity of substanceVSLoss of information

Solution Approach 1:

Index numbers and parameter values serve as intermediaries between the compact stored data and the complete event log information. These indexes act as references that link to the full event log content in code files, allowing the system to store minimal data while maintaining access to complete information through the intermediary index structure.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent performs preliminary organization of event log data into indexed formats before storage. By pre-processing the data to extract only essential index numbers and parameter values for storage in the memory system, the complete event log information can be retrieved later through code files, ensuring data completeness is preserved without compromising storage efficiency.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS12299281B2Memory systems and operation methods thereof, host devices and operation methods thereof, and computer-readable storage media
Publication Date: 2025.05.13 YANGTZE MEMORY TECH CO LTD
  • US12299281B2 patent drawing
  • US12299281B2 patent drawing
  • US12299281B2 patent drawing

AI summary

Examples of the present disclosure provide a memory system and operation method thereof, a host device and operation method thereof, and a computer-readable storage medium. The memory system includes a memory device and a memory controller coupled to the memory device; The memory controller is configured to: receive a read command, the read command indicating to read event log information generated during running of firmware, the event log information including an index number and a parameter value of an event log; and the firmware runs different functional modules to correspondingly generate different event log elements, the different event log elements corresponding to different index numbers.