Storage Device Namespace Mapping for Data Criticality
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing storage devices lack the capability to designate data criticality and priority for each namespace, leading to inefficient management and access of data based on its importance.
Innovation Solution
A storage device and its operating method that allow for the designation of data criticality and priority for each namespace, enabling internal management and access of data based on these designations through the generation of a namespace mapping table.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If data is stored in a single namespace without criticality designation, then the storage device structure is simple, but data management efficiency and access speed for critical data deteriorate
Solution Approach 1:
The storage device divides the namespace into multiple domains based on data criticality (first domain for first criticality level, second domain for second criticality level). This segmentation allows critical data to be stored in dedicated domains, improving data management efficiency and access speed without requiring complete restructuring of the storage device.
Solution Approach 2:
Different domains are assigned different quality characteristics based on data criticality. The first domain is optimized for critical data with higher reliability requirements, while the second domain is optimized for non-critical data. This local quality differentiation improves overall system performance without requiring the entire system to be optimized for the highest criticality level.
2Speed
If all data is treated with equal priority, then the storage device operation is simple, but access latency for critical data increases
Solution Approach 1:
The storage device segments namespaces into multiple domains according to data criticality levels. Critical data is directed to the first domain while non-critical data goes to the second domain, enabling faster access to critical data without requiring complex priority management across the entire storage system.
Solution Approach 2:
The storage device performs preliminary classification of data into different criticality domains before actual storage operations. By pre-designating domains for different criticality levels and pre-establishing the namespace mapping table, the system reduces access latency for critical data without adding complexity during data access operations.
3Reliability
If critical data is stored without dedicated domains, then the storage device structure is simple, but data reliability for mission-critical data deteriorates
Solution Approach 1:
The storage device divides memory blocks into multiple domains based on data criticality requirements. The first domain is specifically designated for storing critical data with higher reliability requirements, while the second domain stores non-critical data. This segmentation ensures that critical data receives dedicated storage resources, improving reliability without requiring complete system restructuring.
Solution Approach 2:
Different domains are assigned different reliability characteristics matching the data they store. The first domain is configured with higher reliability features for critical data, while the second domain uses standard configuration for non-critical data. This local quality optimization improves critical data reliability without unnecessarily increasing complexity or cost for the entire storage device.
Data Source
AI summary
Disclosed is a method of operating a storage device which includes a non-volatile memory device. The method includes informing a host that a designation functionality for designating a data criticality and a priority to namespaces of the non-volatile memory device is possible, enabling the designation functionality in response to receiving an approval of the designation functionality, receiving, from the host, a first request for designating a data criticality and a priority for a first namespace of the namespaces, and generating a namespace mapping table in response to the first request.