SPECULATIVE CACHING IN A CONTENT DELIVERY NETWORK

• US 20190327326A1
• Filed: 04/23/2018
• Published: 10/24/2019
• 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.
• Granted Patent: US 10,645,186 B2
• Time in Patent Office: 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) if said particular resource is already in a cache on said server, serving said particular to said client from said cache;

otherwise

(B) if said particular resource (R) is not already cached on said server,

(B)(1) determining whether a count value (Count(R)) associated with said particular resource 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);

(B)(1)(2) caching said particular resource (R) obtained in (B)(1)(1); 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); and

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

,

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

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

(B)(3)(1) obtaining said particular resource (R);

(B)(3)(2) based on an amount of space available in cache, selectively caching said particular resource (R); 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), said second threshold value being less than or equal to said first threshold value.

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 obtaining in (B)(1)(1) and in (B)(2)(1) and in (B)(3)(1) obtains said particular resource from a location distinct from said server.

7. The method of claim 6, wherein said location is selected from:

(i) an origin server; and

(ii) a peer server of said server.

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

9. The method of claim 8, 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).

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

11. The method of claim 1, further comprising:

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

12. 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:

(A) setting a first threshold value (min_uses) and a second threshold value (min_uses_floor), said second threshold value being less than or equal to said first threshold value; and

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

(B)(1) if said particular resource is already in a cache on said server, serving said particular to said client from said cache;

otherwise

(C) if said particular resource (R) is not already cached on said server,

(C)(1) scaling said first threshold value to produce a scaled first threshold value based on (i) said second threshold value, and (ii) an amount of space available in cache, and

(C)(2) determining whether a count value (Count(R)) associated with said particular resource exceeds said scaled first threshold value (min_uses), and,

(C)(3) based on said determining in (C)(2), when said count value (Count(R)) exceeds said scaled first threshold value,

(C)(3)(1) obtaining said particular resource (R);

(C)(3)(2) caching said particular resource (R) obtained in (C)(3)(1); and

(C)(3)(3) serving said particular resource (R) to said client; and

,

(C)(4) based on said determining in (C)(2), when said count value (Count(R)) is does not exceed said scaled second threshold value,

(C)(4)(1) obtaining said particular resource (R); and

(C)(4)(2) serving said particular resource (R) to said client.

13. The method of claim 12, wherein said cache is divided into multiple parts, and wherein said particular resource (R) maps to one of said parts for caching, and wherein said amount of space available in cache comprises an amount of space in the one of said parts into which the particular resource (R) maps for caching.

14. The method of claim 12, wherein said obtaining in (C)(3)(1) and in (B)(4)(1) obtains said particular resource from a location distinct from said server.

15. The method of claim 14, wherein said location is selected from:

(i) an origin server; and

(ii) a peer server of said server.

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

17. The method of claim 16, wherein said method further comprises:

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

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

19. The method of claim 12, further comprising:

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

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

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

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

otherwise

(b) if said particular resource (R) is not already cached on said server,

(b)(1) determine whether a count value (Count(R)) associated with said particular resource 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);

(b)(1)(2) cache said particular resource (R) obtained in (b)(1)(1); 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); and

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

,

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

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

(b)(3)(1) obtain said particular resource (R);

(b)(3)(2) based on an amount of space available in cache, selectively cache said particular resource (R); and

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