Mobile Device Backup and Restore Mirror Database Memory Items
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Mobile devices with limited memory capacity face challenges in managing memory space and preserving historical user data, such as photo albums and navigation histories, which are often lost when applications are deleted or upgraded, due to the lack of standardized methods for backup and restore.
Innovation Solution
A method and system for backup and restore capabilities in mobile applications, involving a server communication link with mobile devices to store and retrieve historical records of user interactions and data, using a server-side mirror database to maintain and restore memory items like photo albums and navigation histories, even when the application is re-downloaded.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Quantity of substance
If applications are deleted to free memory space on mobile devices, then memory capacity is improved, but historical user data and preferences are lost
Solution Approach 1:
The patent extracts historical data from the application package and stores it separately in a backup database on the server. When an application is deleted from the mobile device, the historical data remains preserved in the server's backup database, allowing users to restore it later if needed, thus resolving the contradiction between freeing memory and preserving information.
Solution Approach 2:
The patent introduces a server-side backup database as an intermediary between the mobile device and the application data. This intermediary stores historical data independently, allowing the mobile device to delete applications for memory management while the intermediary preserves the historical information for potential restoration.
2Quantity of substance
If applications are frequently deleted and re-loaded to manage memory, then memory management is improved, but user experience deteriorates due to loss of historical information
Solution Approach 1:
The patent performs preliminary backup of historical data to the server before application deletion. This preliminary action ensures that when users need to re-load applications, their historical data is already preserved and can be automatically restored, maintaining user experience while enabling flexible memory management.
3Loss of information
If backup of all historical data is maintained locally on mobile devices, then data preservation is improved, but memory capacity is consumed
Solution Approach 1:
The patent moves the backup storage from the same dimension (local mobile device memory) to another dimension (server-side database). This dimensional shift allows historical data to be preserved without consuming宝贵的 local memory resources on mobile devices, as the backup resides in a different storage dimension accessible via network.
Data Source
AI summary
The need for backup and restore arises in a mobile device based system when a client application is discarded along with its historical record. In a system that provides the backup and restore capability, a server is configured with a request handler, an application storage upload/download handler, and a device storage mirror database. In a mobile device (also client), the transaction listener provides a transaction associated with memory items to the crumb sticker which, in turn, sends to the request handler a recording request with the transaction along with a request URL (uniform resource locator). The data for the recording request is channeled from the client storage to the device storage mirror database via the application storage upload/download handler. The memory items are accumulated in a file at the client and in a backup at the device storage mirror database, and are restorable to the client from the backup.