Distributed caching system with distributed notification of current content

• US 10,063,652 B2
• Filed: 09/29/2017
• Issued: 08/28/2018
• Est. Priority Date: 10/04/2013
• Status: Active Grant

• Current Assignee: Akamai Technologies, Inc.
• Original Assignee: Akamai Technologies, Inc.
• Inventors: Flack, Martin T., Steiner, Moritz M., Ludin, Stephen L., Hatala, Jozef
• Primary Examiner(s): Tiv, Backhean
• Application Number:
  US15/719,940
• Publication Number:
  US 20180027089A1
• Time in Patent Office: 333 Days
• Field of Search: None
• CPC Class Codes: H04L 2209/76 Proxy, i.e. using intermediary entity to perform cryptographic operations network architectures or network communication protocols using hop-by-hop encryption H04L63/0464
• CPC Class Codes: H04L 63/0884 by delegation of authentication, e.g. a proxy authenticates an entity to be authenticated on behalf of this entity vis-à-vis an authentication entity
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/1095 Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes
• CPC Class Codes: H04L 67/1097 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 Class Codes: H04L 67/568 Storing data temporarily at an intermediate stage, e.g. caching
• CPC Class Codes: H04N 21/23106 involving caching operations prefetching while addressing of a memory level in which the access to the desired data or data block requires associative addressing means within memory systems or architectures G06F12/0862; caching at an intermediate stage in a data network H04L67/568

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. Tokens may be used to represent a variety of kinds of dependencies expressed in the response, including without limitation data, data ranges, or logic that was a basis for the construction of the response.

Claims

1. A computer-implemented method performed by a content delivery network (CDN) server that has circuitry forming one or more processors and memory holding instructions for execution by the one or more processors, the method comprising:

receiving a response having appended thereto a first token, the first token comprising a moniker and a serial number and the first token corresponding to any of data and logic at a remote source upon which the content of the response depends;

caching the response and the first token;

receiving a message, the message comprising a second token, the second token comprising a moniker and a serial number, and in response to the message, storing the second token in a cache of current tokens;

wherein the moniker of the second token is the same as the moniker of the first token;

after receiving the message, receiving a client request that includes a domain name;

determining that the cached response is responsive to the client request;

before using the cached response to respond to the client request, comparing the serial number of the first token with the serial number of the second token;

upon a determination that the serial number of the first token matches the serial number of the second token, serving the cached response to the client;

upon a determination that the serial number of the first token is different than the serial number of the second token, determining to send a forward request to the remote source to obtain a response with current content.

2. The method of claim 1, wherein the message is received from another CDN server.

3. The method of claim 2, wherein the another CDN server generates the message upon receipt of a write request.

4. The method of claim 1, where the message is received from the remote source.

5. The method of claim 1, further comprising:

subscribing to a subscription channel associated with the domain name to receive invalidation messages for tokens associated with the domain name.

6. The method of claim 5, wherein the subscription channel is provided by another CDN server.

7. The method of claim 1, wherein the domain name is associated with an application programmer interface (API).

8. The method of claim 1, where the client request comprises a request for service from an application programmer interface (API).

9. A computer-implemented method performed by a content delivery network (CDN) server that has circuitry forming one or more processors and memory holding instructions for execution by the one or more processors, the method comprising:

receiving a response having appended thereto a first token, the first token comprising a moniker and a timestamp and the first token corresponding to any of data and logic at a remote source upon which the content of the response depends;

caching the response and the first token;

receiving a message, the message comprising a second token, the second token comprising a moniker and a timestamp, and in response to the message, storing the second token in a cache of current tokens;

wherein the moniker of the second token is the same as the moniker of the first token;

after receiving the message, receiving a client request that includes a domain name;

determining that the cached response is responsive to the client request;

before using the cached response to respond to the client request, comparing the timestamp of the first token with the timestamp of the second token;

upon a determination that the timestamp of the first token matches the timestamp of the second token, serving the cached response to the client;

upon a determination that the timestamp of the first token is different than the timestamp of the second token, determining to send a forward request to the remote source to obtain a response with current content.

10. The method of claim 9, wherein the message is received from another CDN server.

11. The method of claim 10, wherein the another CDN server generates the message upon receipt of a write request.

12. The method of claim 9, where the message is received from the remote source.

13. The method of claim 9, further comprising:

subscribing to a subscription channel associated with the domain name to receive invalidation messages for tokens associated with the domain name.

14. The method of claim 13, wherein the subscription channel is provided by another CDN server.

15. The method of claim 9, wherein the domain name is associated with an application programmer interface (API).

16. The method of claim 9, where the client request comprises a request for service from an application programmer interface (API).