Bulk event scheduling
US-2016267404-A1 · Sep 15, 2016 · US
US10558619B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-10558619-B2 |
| Application number | US-201615238934-A |
| Country | US |
| Kind code | B2 |
| Filing date | Aug 17, 2016 |
| Priority date | Aug 8, 2016 |
| Publication date | Feb 11, 2020 |
| Grant date | Feb 11, 2020 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
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. Embodiments are directed to detection of bulk operations associated with content stored at a storage service to protect users both proactively and remedially from accidental and/or nefarious content alterations propagating to the storage service and/or other devices. A model based on a usage pattern monitored and provided by a client device may be received at the client device from the storage service. An attempted operation performed on the content may be detected, and the attempted operation may be compared to the model to determine whether the operation deviates from the usage pattern. If the attempted operation deviates from the usage pattern, execution of the attempted operation and synchronization of the content with the storage service may be prevented until the attempted operation is approved.
Opening claim text (preview).
What is claimed is: 1. A method to detect bulk operations associated with content stored at a storage service, the method comprising: monitoring a usage pattern associated with the content that is stored locally to provide to the storage service; receiving, from the storage service, a model based on the usage pattern, the model defining a change threshold based on one or more of a type of altered content, an amount of altered content, and an amount of altered content within a particular period; detecting an attempted operation performed on the content; comparing the attempted operation to the model to determine whether the operation deviates from the usage pattern; and in response to a determination that the attempted operation exceeds the change threshold, preventing execution of the attempted operation and synchronization of the content with the storage service until the attempted operation is approved. 2. The method of claim 1 further comprising: in response to a determination that the attempted operation does not exceed the change threshold, enabling execution of the attempted operation and synchronization of the content with the storage service. 3. The method of claim 1 , further comprising: in response to the determination that the attempted operation exceeds the change threshold, presenting a notification of the attempted operation through a display. 4. The method of claim 1 , further comprising: enabling a previous version of the content preserved at the storage service to be restored. 5. The method of claim 4 , further comprising: presenting a restoration option through a display, wherein a user is enabled to select the restoration option to restore the previous version of the content preserved at the storage service. 6. The method of claim 1 , further comprising: determining the usage pattern associated with the content based on previous operations performed on the content by a user, a size of the user's account, and a frequency at which the user performed operations on the content. 7. A client device configured to detect bulk operations associated with content stored at a storage service, the client device comprising: a communication interface configured to facilitate communication between the storage service and the client device; a memory configured to store instructions; and one or more processors coupled to the memory, wherein the one or more processors, in conjunction with the instructions stored in the memory, are configured to: monitor a usage pattern associated with the content that is stored locally on the client device to provide to the storage service; receive, from the storage service, a model based on the usage pattern that defines a change threshold based on one or more of a type of altered content, an amount of altered content, and an amount of altered content within a particular period; detect an attempted operation performed on the content through the client device; and in response to a determination that the type of altered content, the amount of altered content, and/or the amount of altered content within the particular period during the attempted operation exceeds the change threshold, prevent execution of the attempted operation and synchronization of the content with the storage service until the attempted operation is approved. 8. The client device of claim 7 , wherein the attempted operation is one of a creation, a deletion, an encryption, and an update performed on the content. 9. The client device of claim 7 , wherein the change threshold is one of a static, learned, or calculated value based on previous operations performed on the content by a user, a size of the user's account, and frequency at which the user performed operations on the content. 10. The client device of claim 7 , wherein the notification requests for a user to one of approve or reject the attempted operation, and the one or more processors are configured to: enable execution of the attempted operation and the synchronization process if the user approves the attempted operation; and fail the attempted operation if the user rejects the attempted operation. 11. The client device of claim 10 , wherein the one or more processors are configured to: present a selectable restoration option through a display of the client device, wherein the restoration option enables a previous version of the content preserved at the storage service to be restored to the client device. 12. A method to detect bulk operations associated with content stored at a storage service, the method comprising: monitoring a usage pattern associated with the content that is stored locally; defining a change threshold based on one or more of a type of altered content, an amount of altered content, and an amount of altered content within a particular period; detecting an attempted operation performed on the content; and in response to a determination that the type of altered content, the amount of altered content, and/or the amount of altered content within the particular period during the attempted operation exceeds the change threshold, preventing execution of the attempted operation and synchronization of the content with the storage service until the operation is approved. 13. The method of claim 12 , further comprising: presenting a notification of the attempted operation through a display. 14. The method of claim 13 , further comprising: enabling the user to approve or reject the attempted operation through the notification. 15. The method of claim 14 , further comprising: prompting the user to provide authentication through the notification in order to approve the attempted operation. 16. The method of claim 12 , further comprising: in response to an execution of the attempted operation, presenting a restoration option through a display. 17. The method of claim 16 , further comprising: enabling a user to select the restoration option to restore a previous version of the content preserved at the storage service. 18. The method of claim 12 , further comprising: enabling synchronization of the content with the storage service if the attempted operation is executed such that the content as altered by the operation is synchronized.
involving event detection and direct action · CPC title
Monitoring users, programs or devices to maintain the integrity of platforms, e.g. of processors, firmware or operating systems · CPC title
Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes · CPC title
for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS] · CPC title
Details of monitoring file system events, e.g. by the use of hooks, filter drivers, logs · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.