Handling a shared data object in a communication network
US-2015207862-A1 · Jul 23, 2015 · US
US11855858B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-11855858-B2 |
| Application number | US-202217883335-A |
| Country | US |
| Kind code | B2 |
| Filing date | Aug 8, 2022 |
| Priority date | Jul 11, 2013 |
| Publication date | Dec 26, 2023 |
| Grant date | Dec 26, 2023 |
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.
A method includes receiving a subscription request to obtain notifications of events pertaining to the data file that has been previously uploaded by a user account associated with a user device and stored at the cloud-based file system. The subscription request identifies a destination address for the notifications generated in accordance with the subscription request and one or more events, among multiple events, corresponding to the data file that are to prompt the notifications to be transmitted to the destination address associated with the networked device. The method includes determining that the subscription request is authorized, and identifying an occurrence of an event from the one or more events specified in the subscription request and involving the data file. The method includes transmitting to the destination address a notification indicating the occurrence of the event involving the data file.
Opening claim text (preview).
What is claimed is: 1. A method, comprising: receiving, by a processor, a subscription request to obtain notifications of events pertaining to a data file that has been previously uploaded by a user account associated with a user device and stored at a cloud-based file system, wherein the subscription request identifies a destination address for the notifications generated in accordance with the subscription request and one or more events, among a plurality of events, corresponding to the data file that are to prompt the notifications to be transmitted to the destination address associated with a networked device; determining that the subscription request is authorized; subsequent to determining that the subscription request is authorized, identifying an occurrence of an event from the one or more events specified in the subscription request and involving the data file; and responsive to identifying the occurrence of the event from the one or more events specified in the subscription request and involving the data file, transmitting to the destination address a notification indicating the occurrence of the event involving the data file. 2. The method of claim 1 , wherein the one or more events comprise an access of the data file. 3. The method of claim 2 , wherein the access to the data file comprises a modification to the data file. 4. The method of claim 3 , wherein the modification to the data file comprises an edit to content of the data file. 5. The method of claim 1 , wherein the subscription request comprises a security token. 6. The method of claim 5 , wherein determining that the subscription request is authorized comprises determining that the security token of the subscription request is valid. 7. The method of claim 1 , further comprising: responsive to determining that the subscription request is authorized, recording the subscription request in a data store. 8. The method of claim 1 , further comprising: subsequent to determining that the subscription request is authorized, sending a subscription notification identifying the data file and an identifier identifying a subscription corresponding to the subscription request. 9. The method of claim 1 , wherein the destination address comprises a HyperText Transfer Protocol address. 10. A system comprising: a memory; and a processor, coupled to the memory, to perform operations comprising: receiving a subscription request to obtain notifications of events pertaining to a data file that has been previously uploaded by a user account associated with a user device and stored at a cloud-based file system, wherein the subscription request identifies a destination address for the notifications generated in accordance with the subscription request and one or more events, among a plurality of events, corresponding to the data file that are to prompt the notifications to be transmitted to the destination address associated with a networked device; determining that the subscription request is authorized; subsequent to determining that the subscription request is authorized, identifying an occurrence of an event from the one or more events specified in the subscription request and involving the data file; and responsive to identifying the occurrence of the event from the one or more events specified in the subscription request and involving the data file, transmitting to the destination address a notification indicating the occurrence of the event involving the data file. 11. The system of claim 10 , wherein the one or more events comprise an access of the data file. 12. The system of claim 11 , wherein the access to the data file comprises a modification to the data file. 13. The system of claim 12 , wherein the modification to the data file comprises an edit to content of the data file. 14. The system of claim 11 , wherein the subscription request comprises a security token. 15. The system of claim 14 , wherein determining that the subscription request is authorized comprises determining that the security token of the subscription request is valid. 16. The system of claim 10 , the operations further comprising: responsive to determining that the subscription request is authorized, recording the subscription request in a data store. 17. The system of claim 10 , the operations further comprising: subsequent to determining that the subscription request is authorized, sending a subscription notification identifying the data file and an identifier identifying a subscription corresponding to the subscription request. 18. The system of claim 10 , wherein the destination address comprises a HyperText Transfer Protocol address. 19. A non-transitory computer-readable medium comprising instructions that, responsive to execution by a processor, cause the processor to perform operations comprising: receiving a subscription request to obtain notifications of events pertaining to a data file that has been previously uploaded by a user account associated with a user device and stored at a cloud-based file system, wherein the subscription request identifies a destination address for the notifications generated in accordance with the subscription request and one or more events, among a plurality of events, corresponding to the data file that are to prompt the notifications to be transmitted to the destination address associated with a networked device; determining that the subscription request is authorized; subsequent to determining that the subscription request is authorized, identifying an occurrence of an event from the one or more events specified in the subscription request and involving the data file; and responsive to identifying the occurrence of the event from the one or more events specified in the subscription request and involving the data file, transmitting to the destination address a notification indicating the occurrence of the event involving the data file. 20. The non-transitory computer-readable medium of claim 19 , wherein determining that the subscription request is authorized comprises determining that a security token of the subscription request is valid.
Network service management, e.g. ensuring proper service fulfilment according to agreements · CPC title
Event management; Broadcasting; Multicasting; Notifications · CPC title
Details of monitoring file system events, e.g. by the use of hooks, filter drivers, logs · CPC title
Filtering policies (mail message filtering H04L51/212) · CPC title
Entity profiles · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.