Memory Controller Transaction Flag Mapping Management

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing memory systems face inefficiencies in managing mapping information for write data, particularly in handling transactions, which can lead to increased load and difficulty in storing and retrieving data effectively.

Innovation Solution

A memory system with a controller that includes a volatile memory for managing mapping information, where the controller checks whether write data are grouped into transactions, sets a transaction flag, and selectively stores mapping information based on this flag, ensuring efficient storage and retrieval by avoiding unnecessary data transfer and maintaining data integrity.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Loss of energy

If mapping information for all write data is stored in memory blocks, then data retrieval is straightforward, but storage efficiency decreases and unnecessary data transfer increases

Engineering Contradiction:

Improveunnecessary data transferVSAvoiddata storage efficiency

Core Design Contradiction:

Loss of energyVSProductivity

Solution Approach 1:

The patent segments mapping information into two categories: mapping information for data grouped into transactions (marked with transaction flag) and mapping information for data not grouped into transactions. Only the latter is stored in memory blocks, while the former is retained only in the volatile memory of the controller, thereby avoiding unnecessary storage and transfer of transaction-related mapping information.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The patent applies different storage strategies to different types of mapping information based on their characteristics. Mapping information without transaction flags is stored in non-volatile memory blocks for persistence, while mapping information with transaction flags is kept only in volatile memory, reflecting its temporary nature until transaction commit. This localized quality approach optimizes both storage efficiency and data retrieval.

Inventive Principle:

Principle #3Local quality

2Productivity

If mapping information is stored in volatile memory only, then storage efficiency improves, but data integrity and persistence are compromised

Engineering Contradiction:

Improvestorage efficiencyVSAvoiddata integrity

Core Design Contradiction:

ProductivityVSReliability

Solution Approach 1:

The patent dynamically determines whether to store mapping information in memory blocks or only in volatile memory based on the transaction flag status. When a transaction is committed, the mapping information transitions from volatile-only storage to persistent storage in memory blocks. This dynamic approach ensures data integrity is maintained for committed transactions while preserving storage efficiency for uncommitted or aborted transactions.

Inventive Principle:

Principle #15Dynamics

Solution Approach 2:

The system uses transaction commit status as feedback to determine the storage destination of mapping information. The transaction flag acts as a marker that provides feedback about the transactional nature of data, guiding the controller to appropriately manage mapping information storage and ensure data integrity only when transactions are successfully committed.

Inventive Principle:

Principle #23Feedback

3Reliability

If transaction management is implemented for all write data, then data integrity improves, but system complexity increases

Engineering Contradiction:

Improvetransaction managementVSAvoidsystem complexity

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The patent applies transaction management selectively rather than universally. The transaction flag mechanism allows the system to identify and apply transactional processing only to specific groups of write data that require it, while leaving other data to be processed through simpler pathways. This partial application of transaction management reduces overall system complexity while maintaining data integrity where needed.

Inventive Principle:

Principle #16Partial or excessive action

4Speed

If all mapping information is selectively managed based on transaction flags, then data retrieval efficiency improves, but management complexity increases

Engineering Contradiction:

Improvedata retrieval efficiencyVSAvoidmapping information management

Core Design Contradiction:

SpeedVSDevice complexity

Solution Approach 1:

The patent performs preliminary classification of mapping information by setting transaction flags at the time of write operation. This preliminary action tags mapping information with transactional context before storage decisions are made, enabling efficient retrieval later without requiring complex analysis during data access. The flagging mechanism simplifies subsequent management by pre-categorizing information based on its transactional nature.

Inventive Principle:

Principle #10Preliminary action

Data Source

PatentUS10838874B2Memory system managing mapping information corresponding to write data and operation method thereof

Publication Date: 2020.11.17 SK HYNIX INC

AI summary

A memory system includes a non-volatile memory device including a plurality of memory blocks; and a controller comprising a volatile memory and configured to: store a plurality of write data delivered from a host in the memory blocks to the plurality of memory blocks; and managing mapping information corresponding to the stored write data in the volatile memory, wherein the controller is configured to check whether the plurality of write data are grouped into a transaction, selectively set a transaction flag to the mapping information based on a check result; and selectively store the mapping information in the memory blocks when the transaction flag is not set.