Systems and methods for caching content with notification-based invalidation with extension to clients

• US 9,813,515 B2
• Filed: 10/06/2014
• Issued: 11/07/2017
• Est. Priority Date: 10/04/2013
• Status: Active Grant

• Current Assignee: Akamai Technologies, Inc.
• Original Assignee: Akamai Technologies, Inc.
• Inventors: Flack, Martin T., Ludin, Stephen L., Steiner, Moritz M.
• Primary Examiner(s): Tiv, Backhean
• Application Number:
  US14/507,601
• Publication Number:
  US 20150100664A1
• Time in Patent Office: 1,128 Days
• Field of Search: None
• CPC Class Codes: H04L 67/2885 Hierarchically arranged intermediate devices, e.g. for hierarchical caching
• CPC Class Codes: H04L 67/55 Push-based network services
• CPC Class Codes: H04L 67/56 Provisioning of proxy services store-and-forward switching systems in data switching networks H04L12/54
• CPC Class Codes: H04L 67/5682 Policies or rules for updating, deleting or replacing the stored data

Abstract

Described herein are systems, devices, and methods for content delivery on the Internet. In certain non-limiting embodiments, a caching model is provided that can support caching for indefinite time periods, potentially with infinite or relatively long time-to-live values, yet provide prompt updates when the underlying origin content changes. In one approach, an origin server can annotate its responses to content requests with tokens, e.g., placing them in an appended HTTP header or otherwise. The tokens can drive the process of caching, and can be used as handles for later invalidating the responses within caching proxy servers delivering the content. This caching and invalidation model can be extended out to clients, such that clients may be notified of invalid data and obtain timely updates.

Claims

1. A computer-implemented method operable in one or more servers that include circuitry forming one or more processors and memory holding instructions for execution by the one or more processors to perform the method, the method comprising:

receiving a request from a client device;

in response to the request, generating a forward request to a source;

receiving a response to the forward request, the response comprising responsive content and at least one token, the at least one token corresponding to information stored at the source upon which the responsive content depends, wherein the information is distinct from the responsive content and was a basis for the source'"'"'s construction of the responsive content;

serving the responsive content and the at least one token to the client device, in response to the client device'"'"'s request;

subsequent to serving the responsive content, receiving a first message indicating that the at least one token is invalid; and

sending a second message to the client device indicating that the at least one token is invalid.

2. The computer implemented method of claim 1, wherein the client device caches the responsive content locally and treats the cached responsive content as invalid because the responsive content is associated with the at least one token that was indicated to be invalid in the second message.

3. The computer implemented method of claim 2, further comprising receiving from the client device a second request for the content, upon the client treats the cached responsive content as invalid.

4. The computer implemented method of claim 1, wherein the one or more servers subscribe to a channel for invalidation messages on behalf of the client device.

5. The computer implemented method of claim 1, wherein a subscription request from the client device is received with the request.

6. The computer implemented method of claim 1, wherein the one or more servers prefetch an updated version of the responsive content from the source, upon receiving the first message.

7. The computer implemented method of claim 1, where the first message is received from the source.

8. The computer implemented method of claim 1, wherein the one or more servers represent one or more nodes in a content delivery network (CDN), and the first message is received from another node in the CDN.

9. The computer implemented method of claim 1, where the request comprises a request for service from an application programmer interface (API), and the response is an API response.

10. The computer implemented method of claim 1, where the source comprises an origin server.

11. The computer implemented method of claim 1, where the one or more servers comprise one or more proxy servers in a content delivery network (CDN).

12. The computer implemented method of claim 1, wherein the second message is any of (i) the same as the first message or (ii) different than the second message.

13. A system, comprising:

one or more servers having one or more hardware processors, and computer memory storing computer program instructions executed by the one or more hardware processors, the computer program instructions comprising;

program code operable to receive a request from a client device, and in response to the request, generate a forward request to a source;

program code operable to receive a response to the forward request, the response comprising responsive content and at least one token, the at least one token corresponding to information stored at the source upon which the responsive content depends, wherein the information is distinct from the responsive content and was a basis for the source'"'"'s construction of the responsive content;

program code operable to serve the responsive content and the at least one token to the client device, in response to the client device'"'"'s request;

program code operable to, subsequent to serving the responsive content, receive a first message indicating that the at least one token is invalid; and

program code operable to send a second message to the client device indicating that the at least one token is invalid.

14. The system of claim 13, wherein the client device caches the responsive content locally and treats the cached responsive content as invalid because the responsive content is associated with the at least one token that was indicated to be invalid in the second message.

15. The system of claim 14, wherein the client device makes a second request to the one or more servers for the content, in response to receiving the indication that the at least one token is invalid in the second message.

16. The system of claim 13, wherein the one or more servers subscribe to a channel for invalidation messages on behalf of the client device.

17. The system of claim 13, wherein the one or more servers prefetch an updated version of the responsive content from the source, upon receiving the first message.

18. The system of claim 13, where the first message is received from the source.

19. The system of claim 13, wherein the one or more servers represent one or more nodes in a content delivery network (CDN), and the first message is received from another node in the CDN.

20. The system of claim 13, where the request comprises a request for service from an application programmer interface (API), and the response is an API response.

21. The system of claim 13, where the source comprises an origin server.

22. The system of claim 13, where the one or more servers comprise one or more proxy servers in a content delivery network (CDN).

23. The system of claim 13, wherein the second message is any of (i) the same as the first message or (ii) different than the second message.