Memory Namespace Management for Data Without NSID

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Memory devices face challenges in managing data without a corresponding namespace identifier (NSID), particularly for data types like booting or system use, such as image data and firmware code, which do not have associated NSIDs, requiring additional access methods or mappings.

Innovation Solution

A memory device with a processor and internal memory that includes a namespace table and index table, where the processor assigns an internal NSID to data without a corresponding NSID from the host device, allowing for management using these tables.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If additional access methods or mapping methods are created to handle data without NSID, then data management capability is improved, but device complexity increases

Engineering Contradiction:
Improvedata management capabilityVSAvoidaccess method complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The namespace table is designed to serve dual purposes: managing data with NSIDs (traditional function) and managing data without NSIDs (new function). By adding an internal NSID field to the existing namespace table structure, the system achieves multi-functionality without requiring separate management mechanisms, thus improving adaptability while avoiding increased complexity

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

Solution Approach 2:

The patent merges the management of data with NSIDs and data without NSIDs into a single unified namespace table. The internal NSID field is combined with the existing NSID field, allowing both types of data to be managed through the same access methods and mapping mechanisms, eliminating the need for separate systems

Inventive Principle:
Principle #5Merging (Combining)

2Adaptability or versatility

If separate management systems are implemented for data with and without NSIDs, then data management completeness is improved, but ease of operation deteriorates

Engineering Contradiction:
Improvedata management completenessVSAvoidaccess method simplicity
Core Design Contradiction:
Adaptability or versatilityVSEase of operation

Solution Approach 1:

The namespace table and index table are designed to handle both NSID-based and internal NSID-based data access uniformly. The processor executes the same namespace management commands for both data types, maintaining ease of operation while achieving complete data management coverage

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

Solution Approach 2:

The system automatically determines whether data has an NSID or requires an internal NSID and manages it accordingly through the same interface. The processor autonomously handles the differentiation and routing without requiring different operational procedures from the host device

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS11614876B2Memory device and method for accessing memory device with namespace management
Publication Date: 2023.03.28 MACRONIX INTERNATIONAL CO LTD
  • US11614876B2 patent drawing
  • US11614876B2 patent drawing
  • US11614876B2 patent drawing

AI summary

The invention provides a memory device including a memory array, an internal memory, and a processor. The memory array stores node mapping tables for access data in the memory array. The internal memory includes a namespace table and an index table The processor obtains a data access command from a host device to determine whether a data of the data access command contains one of the NSIDs, assigns the at least one internal NSID to the data of the data access command according to the data access command in response to the data of the data access command that does not contain the namespace identifier, and, the processor manages the data with the internal NSID by the namespace table and the index table.