Data Object Restoration via Pointer-Based Recycle Bin
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Operating systems on smartphones often lack a mechanism for restoring data objects after they have been blocked, such as deleted or renamed, without providing a recycle bin functionality, and existing solutions do not offer a generic solution independent of the operating system or application.
Innovation Solution
A method and system that involve storing a pointer to the physical location of a data object, associating it with a logical location, and copying the object to a recycle bin upon blocking events, using API functions like the 'open' function to retrieve and manage these pointers, ensuring real-time identification and restoration of blocked data objects, and employing a queue mechanism for prioritizing file access when resources are limited.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a recycle bin mechanism is implemented to restore blocked data objects, then data accessibility and reliability are improved, but device complexity increases
Solution Approach 1:
The patent introduces a recycle bin as an intermediary data repository between the original data location and permanent deletion. When a data object is blocked (deleted, moved, or renamed), the system copies the object to the recycle bin rather than immediately removing it, allowing potential restoration while managing complexity through a dedicated intermediate storage mechanism.
Solution Approach 2:
The system performs preliminary actions by proactively monitoring file system events and copying data objects to the recycle bin before permanent deletion occurs. This preliminary backup action ensures data can be restored if needed, addressing the reliability improvement while the automated nature of the process helps manage the complexity burden.
2Speed
If real-time monitoring of blocking events is implemented, then data restoration speed is improved, but use of energy and processing resources increases
Solution Approach 1:
The patent implements a feedback mechanism by monitoring file system events (delete, move, rename operations) in real-time. When such events are detected, the system immediately responds by copying the affected data object to the recycle bin. This event-driven feedback approach enables fast restoration response while avoiding continuous monitoring overhead by triggering actions only when necessary.
Solution Approach 2:
The system employs periodic monitoring of file system events rather than continuous scanning. By waiting for specific blocking events to occur and then responding, the system achieves fast restoration response time when needed while reducing overall processing resource consumption compared to constant active monitoring.
3Adaptability or versatility
If a generic solution independent of operating system is implemented, then adaptability is improved, but device complexity increases
Solution Approach 1:
The patent creates a universal recycle bin mechanism that operates independently of the underlying operating system. The system provides cross-platform compatibility by implementing a layer of abstraction that handles data object restoration generically, whether the data originates from Android, iOS, Windows, or other file systems. This universal approach improves adaptability while the standardized interface helps manage implementation complexity.
Solution Approach 2:
The recycle bin serves as an operating-system-agnostic intermediary layer between different file systems and the user. By capturing data objects in this universal intermediate storage before permanent deletion, the system achieves cross-platform compatibility without being tied to any specific operating system's native restore mechanisms, thereby improving adaptability while managing complexity through a unified approach.
Data Source
AI summary
The subject matter discloses a method for handling a data object. The method comprises the steps of storing a pointer to a physical location of the data object in a first data repository; associating, in the first data repository, the pointer with a logical location of the data object; receiving an event indicating a blocking of a user access to the data object; retrieving the pointer from the first data repository as a result of the receiving of the event; accessing the physical location by using the retrieved pointer; and copying the data object from the physical location to a second data repository, thereby enabling the restoring of said data object.