Non-Volatile Memory File System Management for Data Security
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Non-volatile memory systems face challenges in securely managing and preserving data due to susceptibility to unintended erasure during formatting, especially when access rights are not adhered to, leading to data security and access issues.
Innovation Solution
A method and system for managing multiple file systems on a non-volatile memory system, where a controller dynamically adjusts the size of logical address ranges and allocates free space to prevent unintended erasure by hiding or resizing file systems, allowing secure data to be protected from formatting operations.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If a single file system is used in non-volatile memory, then ease of operation is improved, but data security deteriorates due to susceptibility to unintended erasure during formatting
Solution Approach 1:
The patent divides the non-volatile memory into multiple independent file systems (e.g., first file system and second file system), each with separate access controls. This segmentation allows secure data to be isolated in one file system while maintaining ease of operation on another, resolving the contradiction between operational simplicity and data security.
Solution Approach 2:
The controller acts as an intermediary between the host and multiple file systems, managing mounting and unmounting operations. It implements access control logic that prevents formatting operations on mounted file systems, thereby protecting secure data while maintaining user-friendly operation through automated protection mechanisms.
2Reliability
If multiple file systems are implemented in non-volatile memory, then data security is improved through access control, but device complexity increases
Solution Approach 1:
The controller is designed with multi-functional capabilities to manage multiple file systems simultaneously, including mounting, unmounting, and access control operations. This universal design consolidates complexity into a single component that handles diverse file system management tasks, reducing overall system complexity while maintaining security.
Solution Approach 2:
The file system structure is made dynamic through runtime mounting and unmounting operations. File systems can be dynamically activated or deactivated based on access requirements, allowing the system to adapt its complexity level - presenting a simple single-file-system view when security is not needed, and enabling multiple file systems when security is required.
3Reliability
If file systems are dynamically mounted and unmounted, then secure data protection is improved, but loss of time occurs due to mounting operations
Solution Approach 1:
The system performs preliminary actions by pre-configuring multiple file systems with their access control parameters and mounting states before actual data operations. This preparation ensures that secure file systems are already mounted and protected when needed, eliminating the need for time-consuming mounting operations during critical data access scenarios.
Solution Approach 2:
Secure file systems are kept in a continuously mounted state to maintain constant protection, while non-secure file systems are mounted only when needed. This continuous mounting of secure file systems eliminates repeated mounting/unmounting cycles, reducing time loss while maintaining security protection throughout system operation.
Data Source
AI summary
A system and method for managing multiple file systems on a single non-volatile memory system is described. The system may include a non-volatile memory system with non-volatile memory having first and second file systems, each associated with respective files, and having a common pool of free space. The controller may be configured to update a file system to be mounted to reflect a capacity relating to only the respective files for that file system and all of the common pool of free space, while hiding from the host the file system not being mounted. The method may include the controller only presenting a single file system and hiding the unmounted file system, or may include the controller managing multiple file systems by presenting multiple file systems concurrently.