Mobile Device File Management with Over-the-Air Refresh
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Mobile devices face challenges in managing files efficiently, particularly with limited memory, where storing and updating files with dependencies can lead to storage issues and outdated information, requiring effective retrieval and deletion mechanisms to maintain relevant data.
Innovation Solution
A system and method for mobile device file management involving a client application that retrieves files via over-the-air communication, stores them with storage information, and a background application that refreshes or deletes files based on specified time periods and user preferences, using file and relationship indices to manage dependencies without parsing parent files.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Speed
If files are stored in the file system for future requests, then file retrieval speed is improved, but memory storage is consumed
Solution Approach 1:
The system performs preliminary actions by storing files in the file system before they are actually needed again. When a file is requested, the client application checks the file system first, and if found, retrieves it immediately without needing to re-download, thus improving retrieval speed while managing storage proactively
Solution Approach 2:
The system changes the state of files by implementing automated refresh mechanisms. The background application monitors storage information and periodically refreshes files to ensure they remain current, transforming static stored files into dynamically updated resources that maintain relevance without permanent storage of all versions
2Loss of information
If dependent files are parsed from parent files, then file relationships are identified, but processing time is increased
Solution Approach 1:
The system extracts dependent file identifiers from parent files during the initial retrieval process. The client application parses the parent file to identify embedded dependent files and their identifiers, separating this identification task from the main file serving operation. This allows relationship mapping to occur in advance, reducing processing time when files are subsequently requested
Solution Approach 2:
The system performs preliminary parsing and relationship identification when files are first downloaded and stored. By identifying dependent files and creating relationship indices during the initial storage phase rather than during retrieval, the system prepares the file relationship map in advance, significantly reducing processing time during actual file serving operations
3Loss of information
If files are automatically refreshed in the background, then information currency is improved, but energy consumption is increased
Solution Approach 1:
The system implements periodic background refresh operations instead of continuous monitoring. The background application checks storage information at intervals and refreshes files based on time-based criteria, providing updated information while consuming energy only during these periodic checks rather than continuously
Solution Approach 2:
The system uses feedback mechanisms where the background application monitors storage information and file timestamps to determine when refreshes are necessary. By comparing current time with stored time information and checking for version changes, the system intelligently refreshes only when needed, optimizing the balance between information currency and energy consumption
4Device complexity
If multiple files with dependencies are managed separately, then storage organization is simplified, but file completeness is compromised
Solution Approach 1:
The system segments file management into separate components: the file system stores individual files, the file index tracks file locations, and the relationship index maps dependencies between files. This segmentation allows simple storage organization where each file is managed independently, while the indexing structures maintain awareness of relationships and ensure completeness when files are retrieved together
Solution Approach 2:
The system introduces relationship indices as intermediary structures that connect parent files with their dependent files. These indices act as mediators that track file relationships without requiring the actual parent files to be present, enabling the system to manage files separately in storage while maintaining knowledge of their dependencies for complete retrieval when needed
Data Source
AI summary
A system is provided for mobile device file management. A client application determines whether a requested file associated with a file identifier is stored in a file system in a mobile device. If the file is not stored in the file system, the client application retrieves the file via over-the-air communication, stores the file with storage information in the file system, and provides the file for presentation on a user interface on the mobile device. If a background application determines that the client application is inactive and that a current time and the storage information indicate to refresh the provided file, the background application retrieves at least apart of a refreshed file via over-the-air communication. If the background application determines that the provided file is not the same version as the refreshed file, the background application stores the refreshed file with refreshed storage information in the file system.