Server initiated multipath content delivery

• US 9,866,655 B2
• Filed: 04/14/2014
• Issued: 01/09/2018
• Est. Priority Date: 03/31/2014
• Status: Active Grant

• Current Assignee: Akamai Technologies, Inc.
• Original Assignee: Akamai Technologies, Inc.
• Inventors: Steiner, Moritz M., Flack, Martin T., Ludin, Stephen L., Holland, Mark C.
• Primary Examiner(s): ALRIYASHI, ABDULKADER MOHAMED
• Application Number:
  US14/252,640
• Publication Number:
  US 20150281331A1
• Time in Patent Office: 1,366 Days
• CPC Class Codes: H04L 67/1001 for accessing one among a plurality of replicated servers
• CPC Class Codes: H04L 67/1014 based on the content of a request
• CPC Class Codes: H04L 67/1038 Load balancing arrangements to avoid a single path through a load balancer
• CPC Class Codes: H04L 69/14 Multichannel or multilink protocols

Abstract

Described herein are—among other things—systems, methods, and apparatus for accelerating and increasing the reliability of content delivery by serving objects redundantly over multiple paths from multiple servers. In preferred embodiments, the decision to use such multipath delivery is made on the server side. A content server can modify or generate a given web page so as to invoke multipath, e.g., by injecting markup language directives and/or script instructions that will cause the client device to make multiple requests for a given object on the page. Preferably the multiple requests are made to separate content servers in separate points of presence. The teachings hereof may be advantageously implemented, without limitation, in intermediary servers such as caching proxy servers and/or in origin servers.

Claims

1. A multipath content delivery system having a plurality of content servers with differing network paths to client devices, comprising:

a first content server;

a second content server that is distinct from the first content server;

a client device that sends a request for a markup language document to the first content server, the first content server acting as a primary content server in the multipath content delivery system;

the first content server programmed to respond to the request with the markup language document, where the markup language document contains two or more universal resource locators (URLs) for an object, the hostname of one of the two or more URLs resolving to the first content server and the hostname of another of the two or more URLs resolving to the second content server;

the client device programmed to generate and send, in response to the two or more URLs for the object, at least a first and a second request for the object, wherein the first request is sent to the first content server and the second request is sent to the second content server;

wherein the first request is distinct from the second request at least because the client device includes a hint in the second request that indicates to the second content server that the second content server is acting as a secondary content server in the multipath content delivery system.

2. The system of claim 1, the client device is programmed to receive at least two copies of the object in response to the first and second requests, and use only the first object received when rendering a web page described by the markup language document.

3. The system of claim 2, wherein the client device is programmed to remember, the content server from which the first object was received, and further programmed to send requests to that remembered content server rather than generating multiple requests.

4. The system of claim 1, wherein the client device is programmed to send information to the first content server or second content server indicating that a recipient of the information served the first object to be received by the client.

5. The system of claim 1, wherein the second content server is programmed to perform any of the following, as a result of acting as the secondary content server in the multipath content delivery system:

(i) suppress a forward request operation for the object and (ii) ignoring the second request if needed.

6. The system of claim 1, wherein the hint is comprises any of:

a request header, a URL parameter, or a subdomain.

7. The system of claim 1, wherein the first content server is programmed to parse the markup language document to find a URL for the object, and to convert the URL for the object into the two or more different URLs for the object.

8. The system of claim 7, wherein the first content server is programmed to convert the URL for the object upon meeting one or more criteria.

9. The system of claim 1, wherein the first content server and the second content server are in distinct points of presence from one another.

10. The system of claim 1, wherein the markup language document is an HTML document.

11. The system of claim 1, wherein the client device includes a hint in the first request that indicates to the first content server that the first content server is acting as a primary content server in the multipath content delivery system.

12. The system of claim 1, wherein the second content server is programmed to, as a result of acting as a secondary content server in the multipath content delivery system:

suppress a follow-on action otherwise performed after serving the object request.

13. The system of claim 1, wherein the first content server is programmed to parse the markup language document to find a URL for the object, and to insert a script into the markup language document to make requests for the object using the two or more URLs.

14. A plurality of computer apparatus, comprising:

a first content server comprising circuitry forming one or more processors and memory holding computer program instructions that, when executed by the one or more processors, operate the first content server to;

receive a request from a client device for a markup language document;

retrieve a markup language document from a local storage device or another content server;

parse the markup language document to find a universal resource locator (URL) pointing to a copy of an object;

modify the markup language document to cause a client to make a request to each of two or more URLs, each pointing to a copy of the object on a content server distinct from content servers pointed to by the other URLs;

send the modified markup language document to the client device in response to the request from the client device for the markup language document;

a second content server comprising circuitry forming one or more processors and memory holding computer program instructions that, when executed by the one or more processors, operate the second content server to;

receive an object request from the client device for one of the two or more URLs;

determine that the object request includes a hint;

based on the hint, determining that the second content server is acting as a secondary content server in a multipath content delivery system, wherein a secondary content server is distinct from a primary content server in the multipath delivery system at least because a secondary content server is operative to perform at least one of the following;

(i) suppress a forward request operation for the object, (ii) ignore the second request due to load on the second content server, and (iii) suppress a follow-on action otherwise performed after serving the object request.

15. The apparatus of claim 14, further comprising computer program instructions that, when executed by the one or more processors of the first content server, operate the first content server to:

determine whether to modify the markup language document based on at least on one of the following;

(i) bandwidth to the client device, (ii) a device characteristic of the client device, and (iii) a configuration setting associated with the markup language document.

16. The apparatus of claim 14, further comprising computer program instructions that, when executed by the one or more processors of the first content server, operate the first content server to:

prior to modifying the markup language document, determining whether the object is cacheable at the content server.

17. The apparatus of claim 14, wherein each of the distinct content servers are located in distinct points of presence.

18. The apparatus of claim 14, further comprising computer program instructions that, when executed by the one or more processors of the first content server, operate the first content server to:

insert a script into the markup language document, the script including instructions executable by the client device to cause the client device to make a request to each of two or more URLs.

19. The apparatus of claim 14, further comprising computer program instructions that, when executed by the one or more processors of the first content server, operate the first content server to:

insert a script into the markup language document, the script including instructions executable by the client device to cause the client device to use only a single copy of the object, from amongst multiple copies of the object received by the client device, when rendering a web page described by the markup language document.

20. The apparatus of claim 19, further comprising computer program instructions that, when executed by the one or more processors of the first content server, operate the first content server to:

insert a script into the markup language document that includes instructions executable by the client device to remember, for a limited time period, the identity of a content server that sent the copy of the object that the client device used.

21. The apparatus of claim 14, further comprising computer program instructions that, when executed by the one or more processors of the second content server, operate the second content server to:

receive a request for the object from the client device and then a cancellation of the request from the client device; and

,

upon receiving the cancellation, send a message to another server.

22. The apparatus of claim 14, wherein the two or more URLs are in HTML tags.

23. The apparatus of claim 14, wherein the two or more URLs have different hostnames but the same paths.

24. The apparatus of claim 14, wherein any of the first and second content servers is a caching proxy server.

25. A multipath content delivery system having at least a first and a second content server with differing network paths to a client device, comprising:

a first content server;

a second content server that is distinct from and remote from the first content server;

a client device that sends a request for a markup language document to the first content server, the first content server acting as a primary content server in the multipath content delivery system;

the first content server programmed to respond to the request with the markup language document, where the markup language document contains two or more URLs, each pointing to a copy of an object;

the client device programmed to generate, in response to the two or more URLs and at substantially the same time, two or more requests for the object, wherein the two or more requests comprise a first request to the first content server and a second request to the second content server;

wherein the second request indicates to the second content server that the second content server is acting as a secondary content server in a multipath content delivery system rather than a primary content server, at least by including a hint in the second request.