Cloud Storage Retainment Module for Local Deletion
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Cloud storage systems inadvertently delete files universally when a user deletes content locally, either accidentally or maliciously, leading to unintended data loss across multiple devices.
Innovation Solution
Implementing a storage service with a retainment module that detects local deletions and retains content, preventing universal deletion by tagging devices or folders as 'local deletes only' and allowing modified content to be re-downloaded during synchronization.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Stability of the object's composition
If automatic synchronization is implemented across multiple clients, then content consistency is improved, but vulnerability to accidental or malicious deletion is worsened
Solution Approach 1:
The patent introduces a cloud storage provider as an intermediary between clients, which mediates the synchronization process. The cloud provider receives content from clients and can selectively propagate or block deletion commands, preventing direct peer-to-peer deletion propagation that causes the reliability issue while maintaining content consistency across clients.
Solution Approach 2:
The system implements feedback mechanisms where the cloud storage provider monitors deletion requests from clients and can respond by blocking unintended deletions. The provider tracks which deletions should be propagated versus which should be retained, using feedback from user intent detection and synchronization state to make intelligent decisions about deletion propagation.
2Adaptability or versatility
If local deletion is allowed for storage management, then local storage flexibility is improved, but risk of universal data loss is worsened
Solution Approach 1:
The patent segments the deletion authority between local and cloud levels. Local devices can delete content for storage management purposes, but the cloud storage provider segments the propagation of this deletion, allowing selective retention of content at the cloud level while permitting local deletion flexibility. This creates independent deletion zones with different policies.
Solution Approach 2:
The cloud storage provider performs preliminary actions by pre-configuring retention policies and monitoring deletion requests before universal deletion occurs. The system can detect unintended deletions and take preliminary protective actions to prevent data loss before the deletion propagates to all synchronized devices.
3Productivity
If deletion propagation is enabled across the network, then synchronization efficiency is improved, but exposure to harmful deletion actions is worsened
Solution Approach 1:
The cloud storage provider acts as an intermediary that receives deletion commands from clients and selectively propagates them to other clients. This intermediary layer maintains synchronization efficiency by quickly propagating legitimate deletions while blocking harmful ones, preventing direct exposure between clients and filtering out malicious or accidental deletion actions.
Solution Approach 2:
The system converts the potential harm of deletion propagation into a benefit by using the propagation mechanism itself to detect and respond to harmful actions. The cloud provider monitors deletion patterns and can identify malicious behavior, then uses the same synchronization infrastructure to block harmful deletions while maintaining efficient propagation of legitimate ones.
Data Source
Figure 1
Figure 2
Figure 3A
AI summary
Cloud-based storage services are provided for storing and/or sharing content across multiple devices, where the content is periodically synchronized between the devices and the storage service. Conventionally, if locally stored content is deleted from a device, the delete would be propagated to the storage service causing the content to not only be deleted from the storage service but from any other devices where the content was locally stored and synchronized with the storage service. Embodiments are directed to retainment of locally deleted content at the storage service to prevent accidental or nefarious deletions of locally stored content on a device from further causing the content to be deleted universally from the storage service and/or multiple other devices. For example, the storage service may be configured to receive content stored locally on the device, detect a deletion of the content on the device, and retain the content at the storage service.