Non-Volatile Memory Mapping Management for Write Efficiency
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional mapping management methods for non-volatile memory, such as Flash memory, face inefficiencies due to the need for table scanning and complex data management when integrating block and page mapping modes, leading to reduced write efficiency and increased time consumption for data merging and access.
Innovation Solution
A mapping management system and method that integrates block and page mapping modes without scanning specific tables, using a processing module to decompose read/write commands into sub-commands with mapping directory numbers, block offsets, and page offsets to locate appropriate tables and access data directly, allowing seamless switching between block and page mapping modes based on data access patterns.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Device complexity
If block mapping mode is used to simplify data management, then device complexity is reduced, but write efficiency deteriorates due to the need to erase the original physical data block before writing
Solution Approach 1:
The patent segments the mapping management into two distinct modes: block mapping mode for simplified management and page mapping mode for efficient writing. The system dynamically selects which mode to use based on the specific operation requirements, allowing each mode to excel at its intended function without compromising the other.
Solution Approach 2:
The patent implements dynamic switching between block mapping mode and page mapping mode based on data access patterns and operation types. This dynamic adaptation allows the system to optimize performance for each specific operation, achieving both simplified management and high write efficiency as needed.
2Productivity
If page mapping mode is used to improve write efficiency, then productivity is improved, but device complexity increases due to complex data distribution and the need for page mapping tables
Solution Approach 1:
The patent divides the mapping management functionality into separate block mapping mode and page mapping mode, allowing the system to use page mapping only when necessary for write operations, rather than maintaining complex page mapping structures for all operations.
Solution Approach 2:
The patent applies different mapping strategies to different data access scenarios: block mapping is used for read operations and scenarios requiring simplicity, while page mapping is used specifically for write operations requiring efficiency. This localized application of different qualities optimizes overall system performance.
3Productivity
If the area of page mapping is increased to reduce data merge frequency, then productivity is improved, but system efficiency deteriorates due to lengthy table scanning procedures
Solution Approach 1:
The patent segments the mapping tables into block mapping tables and page mapping tables, allowing the system to query the appropriate table type based on the operation. This segmentation eliminates the need to scan through a large unified page mapping table, as the system can directly use block mapping tables for operations where they are applicable.
Solution Approach 2:
The patent dynamically determines which mapping mode and corresponding table to use based on the operation type and data access patterns. This dynamic selection prevents the system from unnecessarily scanning large page mapping tables when block mapping would suffice, reducing table scanning time while maintaining appropriate page mapping coverage.
4Loss of time
If the area of page mapping is decreased to improve system efficiency, then system efficiency is improved, but productivity deteriorates as the page mapping area is easily filled, requiring frequent data merges
Solution Approach 1:
The patent segments mapping management into block and page modes, allowing the system to use block mapping for operations that do not require page-level granularity. This segmentation effectively increases the available mapping capacity without expanding the page mapping table size, as block mapping handles the bulk of mapping operations.
Solution Approach 2:
The patent dynamically switches between block mapping mode and page mapping mode based on the specific operation requirements. This dynamic approach allows the system to maintain a smaller page mapping area while still handling large data volumes efficiently by using block mapping for appropriate operations, thereby reducing both table scanning time and data merge frequency.
Data Source
AI summary
Mapping management methods and systems are provided. First, a sub-read command comprising mapping directory number, block offset and page offset is obtained. Then, a specific block mapping table is located from a plurality of block mapping tables according to the mapping directory number, and a first specific entry is located from the specific block mapping table according to the block offset, wherein the first specific entry comprises a mapping mode setting and block information. When the mapping mode setting is a page mapping mode, a second specific entry is located from a page mapped block table according to the block information, and a page mapping table is located corresponding to a specific page mapped block. Thereafter, a third specific entry is located from the page mapping table according to the page offset, and a page of data is located from a storage unit according to the third specific entry.