Cached data detection

• US 10,079,907 B2
• Filed: 11/09/2015
• Issued: 09/18/2018
• Est. Priority Date: 04/06/2011
• Status: Active Grant

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Inventors: Mastrangelo, Michael P., Nassar, Aladdin A., Alongi, David M., Miranda-Steiner, Emmanuel Jose, Lee, Tze Meng
• Primary Examiner(s): Abad, Jackie Zuniga
• Application Number:
  US14/936,410
• Publication Number:
  US 20160173637A1
• Time in Patent Office: 1,044 Days
• CPC Class Codes: G06F 11/3419 by assessing time
• CPC Class Codes: G06F 11/3466 Performance evaluation by tracing or monitoring
• CPC Class Codes: G06F 11/3476 Data logging G06F11/14, G06F11/2205 take precedence
• CPC Class Codes: G06F 2201/865 Monitoring of software
• CPC Class Codes: G06F 2201/875 Monitoring of systems including the internet
• CPC Class Codes: G06F 2201/885 Monitoring specific for caches
• CPC Class Codes: H04L 67/10 in which an application is distributed across nodes in the network software deployment G06F8/60; multiprogramming arrangements G06F9/46
• CPC Class Codes: H04L 67/568 Storing data temporarily at an intermediate stage, e.g. caching

Abstract

A service assigns session identifiers to usage sessions of a program on a computing device, and maintains records in a log of received page requests and associated session identifiers, as well as received cached data detection requests and associated session identifiers. This log can be used to determine how many usage sessions existed over a particular amount of time, and how many of the usage sessions used data from a local cache rather than from the service. The service also returns, in response to a received cached data detection request, a response including an indication that the response is from the service. The program can determine that the response was received from the service if the indication is included in the response, and that the response was received from a local cache of the computing device if the indication is not included in the response.

Claims

1. A method implemented in a service, the method comprising:

receiving, from programs running on computing devices, page requests for one or more pages from the service;

storing, for each page request, information regarding the page request and a session identifier associated with a usage session of the program from which the page request is received;

receiving, from one or more of the programs, both a cached data detection request and the session identifier associated with the usage session of the program from which the cached data detection request is received;

storing, for each cached data detection request, information regarding the cached data detection request and the session identifier, the cached data detection request comprising a request for particular data;

applying a set of rules to alter a behavior of the one or more of the programs in requesting file data, at least two of the set of rules corresponding to altering a rate at which files are requested from the service by the computing device and altering whether files are requested from the service in parallel or serially; and

returning, in response to the cached data detection request, the particular data as well as a cookie indicating that the response to the cached data detection request is from the service.

2. A method as recited in claim 1, further comprising:

assigning the session identifier associated with the usage session in response to an initial page request to the service for the usage session; and

returning both the session identifier and the requested page in response to the initial page request.

3. A method as recited in claim 1, further comprising assigning an expiration time to the particular data corresponding to storage by the one or more programs of the particular data in a local cache, the expiration time being assigned in accordance with a cache retention policy, and assigning a second expiration time to the cookie corresponding to storage of the cookie in the local cache.

4. A method as recited in claim 3, the cached data detection request identifying the particular data by a uniform resource locator (URL), the URL including a version identifier that is updated each time one or more files of the service are updated.

5. A method as recited in claim 3, wherein at least one of the second expiration time being shorter than an expiration time of the particular data or the particular data having a same expiration time as one or more other files of the service.

6. A method as recited in claim 1, further comprising determining a latency or a bandwidth between the computing device and the service, and altering a behavior of the program running on the computing device based on the latency or the bandwidth between the computing device and the service.

7. A method as recited in claim 1, further comprising based upon hardware resource information corresponding to latency of bandwidth, altering the rate at which files are requested from the service by the computing device or altering whether files are requested from the service in parallel or serially.

8. A method as recited in claim 1, further comprising determining, based on the stored information, how many usage sessions existed over a particular amount of time, and how many of the usage sessions used data from the local cache rather than from the service.

9. Computer storage hardware having stored thereon multiple instructions implementing a program that, when executed by one or more processors of a computing device, cause the one or more processors to:

receive, from a remote service in response to a page request, a page and a session identifier associated with a usage session of the program;

send a cached data detection request targeting the remote service;

receive a response to the cached data detection request; and

determine, based on whether a cookie is received with the response or if a cache retention policy indicates an expiration of a time to live for data from the remote resource, that the data is not in the local cache; and

receive the data by requesting additional files in groups and if a bandwidth and/or latency falls below a threshold amount, displaying a graphical user interface element as an option allowing the user to request that smaller files be returned.

10. Computer storage hardware as recited in claim 9, the instructions that cause the one or more processors to send the cached data detection request including instructions that cause the one or more processors to alter a rate at which files are requested from the remote service based on whether the cached data detection response is provided by the remote service or by the local cache of the computing device.

11. Computer storage hardware as recited in claim 9, the particular indication comprising a cookie, and the instructions that cause the one or more processors to determine whether the cached data detection response is provided by the remote service or by the local cache including instructions that cause the one or more processors to determine whether the cached data detection response is provided by the remote service or by a local cache of the computing device and determine that data for the remote service is not in the local cache if the cached data detection response is provided by the remote service.

12. Computer storage hardware as recited in claim 9, the instructions including instructions that further cause the one or more processors to determine whether to request files from the remote service in parallel or serially.

13. Computer storage hardware as recited in claim 9, the instructions including instructions that further cause the one or more processors to alter a behavior of the program based on the response to the cache detection request.

14. Computer storage hardware as recited in claim 9, the instructions including instructions that further cause the one or more processors to alter a rate at which files are requested from the service by the computing device.

15. Computer storage hardware as recited in claim 9, the cached data detection request comprising a request for a particular file or data.

16. Computer storage hardware as recited in claim 15, the cached data detection request identifying the files by a uniform resource locator (URL).

17. Computer storage hardware as recited in claim 15, the particular file or data having a same cache retention policy as one or more other files provided to the program from the service.

18. Computer storage hardware as recited in claim 15, the URL including a version identifier that is updated each time one or more files of the service are updated.

19. Computer storage hardware as recited in claim 9, the program comprising a Web browser.

20. A method implemented in a service, the method comprising:

receiving, from programs running on computing devices, page requests for one or more pages from the service;

storing, for each page request, information regarding the page request and a session identifier associated with a usage session of the program from which the page request is received;

receiving, from one or more of the programs, both a cached data detection request and the session identifier associated with the usage session of the program from which the cached data detection request is received, the cached data detection request comprising a request for files identified by a uniform resource locator (URL);

storing, for each cached data detection request, information regarding the cached data detection request and the session identifier;

assigning a cache retention policy to the files corresponding to storage by the programs of the files in a local cache; and

returning, in response to each cached data detection request, a response with both the files and a cookie indicating that the response with the files are being returned by the service, the files having a different cache retention policy as other files provided to the program from the service if a bandwidth and/or latency corresponding to the programs fall below a threshold amount, the returning comprising communicating in parallel the files.