Speculative caching in a content delivery network

• US 10,645,186 B2
• Filed: 04/23/2018
• Issued: 05/05/2020
• Est. Priority Date: 04/23/2018
• Status: Active Grant

• Current Assignee: Level 3 Communications LLC (Lumen Technologies, Inc.)
• Original Assignee: Level 3 Communications LLC (Lumen Technologies, Inc.)
• Inventors: Jensen, Daniel Lee, Crowder, William, Newton, Christopher, Power, William R.
• Primary Examiner(s): Georgandellis, Andrew C
• Application Number:
  US15/960,393
• Publication Number:
  US 20190327326A1
• Time in Patent Office: 743 Days
• CPC Class Codes: H04L 67/01 Protocols
• CPC Class Codes: H04L 67/568 Storing data temporarily at an intermediate stage, e.g. caching
• CPC Class Codes: H04W 4/00 Services specially adapted for wireless communication networks; Facilities therefor

Abstract

A server in a content delivery (CD) network that distributes content on behalf of one or more subscribers. Responsive to a request from a client for a particular resource, if the particular resource is already in a cache on the server, serving the particular to the client from the cache; otherwise if the particular resource is not already cached on the server, when a count value exceeds a first threshold value, obtaining, caching, and serving the particular resource. When the count value is less than a second threshold value, obtaining and serving the particular resource. When the count value is: (i) not less than the second threshold value, and (ii) not greater than the first threshold value, then obtaining the particular resource and selectively caching the particular resource; and serving the particular resource to the client.

Claims

1. A computer-implemented method operable on a server in a content delivery (CD) network, wherein said CD network (CDN) distributes content on behalf of one or more subscribers, the method comprising, at said server:

in response to a request from a client for a particular resource (R),

(A) when said particular resource (R) is already in a cache on said server, serving said particular to said client from said cache;

otherwise

(B) when said particular resource (R) is not already in said cache,

(B)(1) determining whether a count value (Count(R)) associated with said particular resource (R) exceeds a first threshold value (min uses), and, based on said determining, when said count value (Count(R)) exceeds said first threshold value (min_uses),

(B)(1)(1) obtaining said particular resource (R) from another server;

(B)(1)(2) caching said particular resource (R) obtained in (B)(1)(1) in said cache regardless of the amount of free space in said cache; and

(B)(1)(3) serving said particular resource (R) obtained in (B)(1)(1) to said client; and

,

(B)(2) based on said determining in (B)(1), when said count value (Count(R)) is determined to be less than a second threshold value (min_uses_floor),

(B)(2)(1) obtaining said particular resource (R) from another server; and

(B)(2)(2) serving said particular resource (R) obtained in (B)(1)(1) to said client, wherein said particular resource (R) is not cached in said cache when said count value (Count(R)) is determined to be less than said second threshold value (min_uses_floor); and

,

(B)(3) when said count value (Count(R)) is determined to be;

(i) greater than said second threshold value (min_uses_floor), and (ii) less than said first threshold value (min_uses), then

(B)(3)(1) obtaining said particular resource (R) from another server;

(B)(3)(2) selectively caching said particular resource (R) in said cache when the amount of free space in said cache exceeds a third threshold; and

(B)(3)(3) serving said particular resource (R) obtained in (B)(3)(2) to said client.

2. The method of claim 1, further comprising:

setting said first threshold value (min_uses) and said second threshold value (min_uses_floor).

3. The method of claim 1, further comprising:

prior to said obtaining in (B)(3)(1), determining said amount of space available in cache.

4. The method of claim 3, wherein said cache is divided into multiple parts, and wherein said particular resource (R) maps to one of said parts for caching.

5. The method of claim 4, wherein determining said amount of space comprises determining an amount of space in the one of said parts into which the particular resource (R) maps for caching.

6. The method of claim 1, wherein said other server is selected from:

(i) an origin server; and

(ii) a peer server of said server.

7. The method of claim 1, wherein said request from said client comprises a uniform resource locator (URL) associated with said particular resource (R).

8. The method of claim 7, wherein said method further comprises:

modifying a request header associated with said request from said client prior to said obtaining in (B)(1)(1) and said obtaining in (B)(3)(1).

9. The method of claim 8, wherein said request header is modified to remove at least one range header item.

10. The method of claim 1, further comprising:

incrementing said count value (Count(R)) associated with said particular resource (R).

11. An article of manufacture comprising a non-transitory computer-readable medium having program instructions stored thereon, the program instructions, operable on a server in a content delivery (CD) network, said instructions, when executed by a processor of said server, cause said server to:

in response to a request from a client for a particular resource (R),

(a) when said particular resource (R) is already in a cache on said server, serve said particular to said client from said cache;

otherwise

(b) when said particular resource (R) is not already in said cache,

(b)(1) determine whether a count value (Count(R)) associated with said particular resource (R) exceeds a first threshold value (min uses), and, based on said determining, when said count value (Count(R)) exceeds said first threshold value (min uses),

(b)(1)(1) obtain said particular resource (R) from another server;

(b)(1)(2) cache said particular resource (R) obtained in (b)(1)(1) in said cache regardless of the amount of free space in said cache; and

(b)(1)(3) serve said particular resource (R) obtained in (b)(1)(1) to said client; and

,

(b)(2) based on said determining in (b)(1), when said count value (Count(R)) is determined to be less than a second threshold value (min_uses_floor),

(b)(2)(1) obtain said particular resource (R) from another server; and

(b)(2)(2) serve said particular resource (R) obtained in (b)(1)(1) to said client, wherein said particular resource (R) is not cached in said cache when said count value (Count(R)) is determined to be less than said second threshold value (min_uses_floor); and

,

(b)(3) when said count value (Count(R)) is determined to be;

(i) greater than said second threshold value (min_uses_floor), and (ii) less than said first threshold value (min_uses), then

(b)(3)(1) obtain said particular resource (R) from another server;

(b)(3)(2) selectively cache said particular resource (R) in said cache when the amount of free space in said cache exceeds a third threshold; and

(b)(3)(3) serve said particular resource (R) obtained in (b)(3)(2) to said client.