Flash Memory Mapping Backup for Accurate Data Merging
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In rewritable non-volatile memory modules, updating logical-to-physical mapping tables during data transfer can result in incorrect mapping relationships due to simultaneous writing and transferring of valid data, making it difficult to determine accurate mapping updates.
Innovation Solution
A backup table of logical-to-physical mapping is established during data merging operations, with mapping relationships recorded first, followed by a comparison to determine accurate updates to the logical-to-physical mapping table.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If the logical-to-physical mapping table is updated during data transfer, then the mapping relationship can be maintained, but mapping errors occur when valid data is written concurrently
Solution Approach 1:
The patent creates a backup table before performing data merging operations. This backup table stores the mapping relationships before the merge, allowing the system to compare and verify updates afterward. By preparing the backup in advance, the system prevents mapping errors without requiring complex real-time validation mechanisms during the data transfer process.
Solution Approach 2:
The patent copies the logical-to-physical mapping table into a backup table before data merging. This copy serves as a reference to verify the correctness of mapping updates during concurrent writes. The backup table contains identical mapping relationships at the time of copying, enabling accurate verification without adding significant complexity to the overall system structure.
2Reliability
If a backup table is created during data merging, then mapping accuracy is ensured, but additional memory and processing resources are consumed
Solution Approach 1:
The backup table is created only when necessary - specifically before data merging operations that could cause mapping conflicts. This selective creation avoids consuming memory resources during normal operations while ensuring protection when needed. The system determines when a backup is required based on the data transfer context, optimizing memory usage.
Solution Approach 2:
After the data merging operation completes and the mapping table is updated, the backup table is discarded. This temporary backup serves its purpose during the critical update phase and is then removed to free memory resources. The system recovers memory by eliminating the backup table once verification is complete, avoiding permanent memory consumption.
3Measurement precision
If mapping relationships are recorded before update, then correct mapping can be verified, but the update process becomes more complex
Solution Approach 1:
The patent copies the mapping table into a backup table, creating a static snapshot of the mapping relationships before updates. This copy provides precise verification capability - the system can compare the backup table with the updated table to verify correctness. The copying operation is simple and direct, avoiding complex verification algorithms while ensuring measurement precision.
Solution Approach 2:
The backup table provides feedback information about the mapping relationships before updates. By comparing the backup with the updated mapping table, the system receives feedback on whether the updates were correct. This feedback mechanism simplifies verification - instead of complex real-time validation, the system uses a straightforward comparison between the backup snapshot and the updated table.
Data Source
AI summary
A memory management method is provided for a rewritable non-volatile memory module. The method includes: initiating a data merging operation; selecting a source physical unit and a target physical unit from the rewritable non-volatile memory module to perform the data merging operation; determining whether to create a backup table corresponding to a logical-to-physical mapping table; if it is determined to create the backup table, copying first data located at a first physical address in the source physical unit to a second physical address in the target physical unit, and recording the second physical address in the backup table; and determining whether to update the second physical address to the logical-to-physical mapping table based on information in the backup table.