Multi-Protocol Storage Device Attribute Mapping
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Multi-protocol flash storage devices face disruptions in meeting host storage requirements when switching between different operation modes, such as NVMe and SD modes, due to the lack of consistent storage attribute-based mapping across modes, leading to reduced capacity and compatibility issues.
Innovation Solution
The storage device stores attribute configurations in non-volatile memory during one mode of operation and applies them in another mode, ensuring that blocks are mapped to logical addresses based on endurance, performance, and protection levels, maintaining compatibility and capacity across mode switches.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If the storage device switches between NVMe and SD modes without storing attribute mappings, then the device can operate in multiple protocols, but the storage requirements of the host are disrupted and capacity is reduced
Solution Approach 1:
The controller stores the mapping of storage attributes to logical regions in memory during the first operation mode (e.g., NVMe mode) before switching to the second operation mode (e.g., SD mode). This preliminary action ensures that when the device switches modes, the attribute mapping information is already available, preventing disruption to host storage requirements and maintaining capacity consistency across protocol switches.
2Productivity
If the device maintains separate block mappings for each mode, then mode-specific optimization is achieved, but device complexity increases
Solution Approach 1:
The controller uses a single, unified mapping structure that stores storage attributes (such as endurance, performance, and protection levels) associated with logical regions, rather than maintaining separate mapping tables for each mode. This universal mapping approach allows the same data structure to serve both NVMe and SD modes, achieving mode-specific optimization without increasing device complexity.
3Speed
If blocks are allocated without considering storage attributes during mode switching, then allocation speed is improved, but compatibility and capacity are reduced
Solution Approach 1:
The controller automatically retrieves the stored attribute mapping from memory when switching to the second operation mode and uses it to map blocks to logical addresses. This self-service mechanism eliminates the need for external reconfiguration or manual mapping setup during mode transitions, maintaining both fast allocation speed and host compatibility through attribute-aware block assignment.
Data Source
AI summary
Aspects of a multi-protocol storage device including a memory and a controller are provided which allow for endurance and other storage requirements of a host to be maintained for different logical regions of memory without disruption due to protocol switching. The memory includes blocks that are each associated with a storage attribute such as high endurance, performance, or protection. While operating in a first mode such as NVMe, the controller receives a mapping of storage attributes to different logical regions and stores the mapping in memory. The controller also associates blocks to logical addresses based on the mapping. When the controller switches to a second mode such as SD in response to a host command, the controller reads the mapping from memory and similarly associates blocks to logical addresses based on the mapping in the second mode. Storage attributes thus remain applicable across modes when mapping and storing data.