Context-based data pre-fetching and notification for mobile applications
US-9009292-B2 · Apr 14, 2015 · US
US11500696B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-11500696-B2 |
| Application number | US-201816155154-A |
| Country | US |
| Kind code | B2 |
| Filing date | Oct 9, 2018 |
| Priority date | Jun 7, 2012 |
| Publication date | Nov 15, 2022 |
| Grant date | Nov 15, 2022 |
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.
An application monitoring infrastructure that enables application configuration changes on multiple machines across multiple OS types to be tracked by identifying data containers that are to be monitored for changes, detecting a change to a monitored data container, and storing data representative of a changed version of the monitored data container responsive to detecting that the monitored container was changed. The data containers that are to be monitored for changes are identified from templates, and a unique template is provisioned for each of the applications.
Opening claim text (preview).
We claim: 1. A method comprising: detecting a plurality of change events on the data container; identifying an installed application for the data container; selecting the data container to monitor for changes made thereto based on data container being specified in a monitoring template of the installed application; determining whether the plurality of change events can be transformed into a single normalized event without using any type of OS-specific knowledge; based on the determining, transforming the plurality of change events into the single normalized event without using any type of OS-specific knowledge; and processing the single normalized event. 2. The method of claim 1 , further comprising determining that the plurality of change events occur during a defined period of time; and based on determining that the plurality of change events occur during the defined period of time, determining whether the plurality of change events can be transformed into a single normalized event without any OS-specific knowledge. 3. The method of claim 2 , wherein the defined period of time is two milliseconds. 4. The method of claim 1 , further comprising caching the template in system memory of a monitored machine executing the application. 5. The method of claim 1 , wherein transforming the plurality of change events into the single normalized event is performed without any current or previous OS-specific knowledge. 6. The method of claim 1 , wherein transforming the plurality of change events into the single normalized event is performed without any OS-specific knowledge when the plurality of change events are triggered for a same file within a particular period of time. 7. The method of claim 1 , wherein each of the plurality of change events are relating to effectively the same change. 8. A system comprising; a monitored machine executing an application having a data container associated therewith; a monitoring component; and one or more processors programmed to: detect a plurality of change events on the data container; determine to monitor the data container for changes made thereto based on data container being specified in a monitoring template of the application; determine whether the plurality of change events can be transformed into a single normalized event without any OS-specific knowledge; based on the determining, transforming the plurality of change events into the single normalized event without using any OS-specific knowledge; and processing the single normalized event. 9. The system of claim 8 , further comprising determining that the plurality of change events occur during a defined period of time; and based on determining that the plurality of change events occur during the defined period of time, determining whether the plurality of change events can be transformed into a single normalized event without any OS-specific knowledge. 10. The system of claim 9 , wherein the defined period of time is two milliseconds. 11. The system of claim 8 , wherein the one or more processors are further programmed to cache the template in a system memory of the monitored machine. 12. The system of claim 8 , wherein the one or more processors are further programmed to issue a changed event upon transforming the plurality of change events. 13. The system of claim 12 , wherein issuing the change event includes an ID of the application and paths to files in the data container. 14. The system of claim 8 , wherein each of the plurality of change events are relating to effectively the same change. 15. One or more non-transitory computer-readable media comprising computer-executable instructions that when executed by a processor, cause the processor to perform operations comprising: detecting a plurality of change events on the data container; identifying an installed application for the data container; selecting the data container to monitor for changes made thereto based on data container being specified in a monitoring template of the installed application; determining whether the plurality of change events can be transformed into a single normalized event without any OS-specific knowledge; based on the determining, transforming the plurality of change events into a single normalized event without using any OS-specific knowledge; and processing the single normalized event. 16. The one or more non-transitory computer-readable media of claim 15 , further comprising determining that the plurality of change events occur during a defined period of time; and based on determining that the plurality of change events occur during the defined period of time, determining whether the plurality of change events can be transformed into a single normalized event without any OS-specific knowledge. 17. The one or more non-transitory computer-readable media of claim 16 , wherein the defined period of time is two milliseconds. 18. The one or more non-transitory computer-readable media of claim 15 , wherein the computer-executable instructions further cause the processor to perform operations comprising caching the template in a system memory of the monitored machine. 19. The one or more non-transitory computer-readable media of claim 15 , wherein the computer-executable instructions further cause the processor to perform operations comprising issuing a changed event upon transforming the plurality of change events. 20. The one or more non-transitory computer-readable media of claim 19 , wherein issuing the change event includes an ID of the application and paths to files in the data container.
Data logging (G06F11/14, G06F11/2205 take precedence) · CPC title
Timestamp · CPC title
Event-based monitoring · CPC title
Change logging, detection, and notification (replication G06F16/27) · CPC title
Monitoring of software · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.