Volatile Memory Partition for Secure File Operations
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing methods for protecting and controlling applications and data on electronic terminals are burdensome and insufficiently safeguard user interests, particularly when shared with others, as they require network connectivity and are not easily reversible.
Innovation Solution
An electronic terminal that switches between normal and volatile memory access modes, where files in the volatile partition are copied or deleted to prevent changes to the normal memory partition, allowing users to hand over control without worrying about data modifications, with automated operations to revert to the original state.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If cloud backup and restore is used to protect applications and data, then data protection is improved, but the process requires network connectivity and takes lengthy time making it impractical for frequent use
Solution Approach 1:
The system creates a volatile memory partition in advance before any file operations occur. This partition is pre-configured with read-only attributes and isolation mechanisms, so when file operations need to be protected, the system can immediately redirect writes to this pre-prepared partition without needing to perform time-consuming backup operations first.
Solution Approach 2:
The memory is segmented into at least two partitions: a normal memory partition for regular file operations and a volatile memory partition for protected operations. This segmentation allows the system to isolate protected files in a separate partition that can be quickly switched to, avoiding the need for lengthy cloud-based backup and restore processes.
2Reliability
If cloud backup and restore is used to protect applications and data, then data protection is improved, but network connectivity is required making the process complex and limited in availability
Solution Approach 1:
The invention extracts the protection mechanism from the external cloud-based system and implements it locally within the electronic terminal. By creating a volatile memory partition that operates independently of network connectivity, the system removes the dependency on external cloud services while maintaining local data protection capabilities.
Solution Approach 2:
The volatile memory partition acts as an intermediary between the application and the normal memory partition. When file protection is needed, write operations are redirected to this intermediate partition instead of directly modifying the normal memory, providing protection without requiring complex cloud-based intervention.
3Adaptability or versatility
If another person is allowed to use the electronic terminal, then sharing capability is improved, but unwanted changes to applications and data occur
Solution Approach 1:
The system dynamically switches between protected and unprotected modes based on user needs. When sharing the terminal with another person, the system can activate the volatile memory partition to protect critical files. When the owner needs to make changes, the protection can be temporarily suspended. This dynamic switching allows both sharing capability and data integrity to coexist.
4Reliability
If files are copied to volatile memory partition for protection, then data protection is improved, but additional memory operations are required
Solution Approach 1:
The system creates a copy of the normal memory partition as a volatile memory partition. This copy contains the same files and data structures, allowing the system to redirect file operations to the copy when protection is needed. The copying mechanism is implemented once during partition creation, after which the copy can be used repeatedly without additional complexity.
Data Source
AI summary
An electronic terminal (100) switches (500) from a normal memory access mode to a volatile memory access mode responsive to receiving user input. An open-write command is received (510) from an application to open a first file for writing. A determination (512) is made whether the first file is located in a volatile memory partition of the at least one memory. Based on determining the first file is not located in the volatile memory partition of the at least one memory, the first file is copied (516) from a normal memory partition of the at least one memory to the volatile memory partition, and the first file located in the volatile memory partition is opened (518) for writing. In contrast, based on determining the first file is located in the volatile memory partition, the first file located in the volatile memory partition is opened (520) for writing. Write commands from the application are directed (524) to the first file located in the volatile memory partition.