Dynamic image delivery system

• US 7,653,706 B2
• Filed: 12/10/2004
• Issued: 01/26/2010
• Est. Priority Date: 07/19/2000
• Status: Expired due to Fees

• Current Assignee: Akamai Technologies, Inc.
• Original Assignee: Akamai Technologies, Inc.
• Inventors: Liu, Edward, Swildens, Eric Sven-Johan, Day, Richard David
• Primary Examiner(s): Jean; Frantz B
• Application Number:
  US11/009,273
• Publication Number:
  US 20050097445A1
• Time in Patent Office: 1,873 Days
• Field of Search: 709/203, 709/217, 709/219, 709/224, 718/105, 707/200, 707/204, 705/52, 455/453
• US Class Current: 709/219
• CPC Class Codes: H04L 12/14 Charging , metering or billing arrangements for data wireline or wireless communications
• CPC Class Codes: H04L 41/5029 Service quality level-based billing, e.g. dependent on measured service level customer is charged more or less
• CPC Class Codes: H04L 41/5064 Customer relationship management
• CPC Class Codes: H04L 41/5083 wherein the managed service relates to web hosting
• CPC Class Codes: H04L 41/509 wherein the managed service relates to media content delivery, e.g. audio, video or TV
• CPC Class Codes: H04L 43/0888 Throughput
• CPC Class Codes: H04L 61/4511 using domain name system [DNS]
• CPC Class Codes: H04L 61/4541 Directories for service discovery
• CPC Class Codes: H04L 63/1458 Denial of Service
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/06 specially adapted for file transfer, e.g. file transfer protocol [FTP]
• CPC Class Codes: H04L 67/1001 for accessing one among a plurality of replicated servers
• CPC Class Codes: H04L 67/10015 Access to distributed or replicated servers, e.g. using brokers
• CPC Class Codes: H04L 67/1006 with static server selection, e.g. the same server being selected for a specific client
• CPC Class Codes: H04L 67/1008 based on parameters of servers, e.g. available memory or workload monitoring of computer activity G06F11/30
• CPC Class Codes: H04L 67/101 based on network conditions
• CPC Class Codes: H04L 67/1027 Persistence of sessions during load balancing
• CPC Class Codes: H04L 67/1029 using data related to the state of servers by a load balancer
• CPC Class Codes: H04L 67/1034 Reaction to server failures by a load balancer
• CPC Class Codes: H04L 67/1038 Load balancing arrangements to avoid a single path through a load balancer
• 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/289 : Intermediate processing functionally located close to the data consumer application, e.g. in same machine, in same home or in same sub-network
• CPC Class Codes: H04L 67/5681 : Pre-fetching or pre-delivering data based on network characteristics
• CPC Class Codes: H04L 67/5682 : Policies or rules for updating, deleting or replacing the stored data
• CPC Class Codes: H04L 69/329 : in the application layer [OSI layer 7]

Abstract

A dynamic image delivery system receives a client request for an image at an image caching server. The image caching server measures the client'"'"'s network access speed and looks for an appropriate pre-rendered copy of the requested image that is rendered for the client'"'"'s network access speed in local storage. If the appropriate rendered copy is found, then the image caching server sends the rendered image to the client. If it is not found, then the image caching server dynamically renders a copy of the image and sends it to the client.

Claims

1. A computer implemented method, comprising:

receiving a client'"'"'s request for an image file on a DNS server;

selecting, by the DNS server using load balancing as a selection factor, an image caching server that is appropriate to serve the requested image file;

wherein the image caching server is one of a plurality of image caching servers distributed across a network;

determining whether the client'"'"'s network access speed is stored in a local storage device, when the client'"'"'s network access speed is not found in the local storage device, determining the client'"'"'s network access speed and storing the client'"'"'s network access speed on the local storage device; and

sending an appropriate rendered copy of the requested image that is rendered for the client'"'"'s network access speed.

2. The method of claim 1, wherein the determining step calculates the client'"'"'s network access speed from the client'"'"'s download of a Web page.

3. The method of claim 1, wherein the client sends the image caching server its calculated network access speed and the determining step stores the calculated network access speed on the local storage device.

4. The method of claim 1, wherein the image caching server searches for an appropriate rendered copy of the requested image on the local storage device for the client'"'"'s network access speed, and wherein the sending step sends the appropriate rendered copy to the client when the appropriate rendered copy is found on the local storage device.

5. The method of claim 4, wherein a plurality of rendered copies of the requested image are pre-rendered for different network access speeds and stored on the local storage device prior to the client'"'"'s image request.

6. The method of claim 4, wherein storage space occupied by rendered copies of images on the local storage device is reclaimed by deleting rendered images based on any of:

time, popularity, or pre-determined priority.

7. The method of claim 4, further comprising:

rendering an appropriate copy of the requested image for the client'"'"'s network access speed when an appropriate rendered copy is not found on the local storage device.

8. The method of claim 7, wherein the rendering step stores the rendered appropriate copy on the local storage device.

9. The method of claim 7, wherein the rendering step discards the rendered appropriate copy after it is sent to the client.

10. The method of claim 1, wherein the sending step sends the client rendered layers of the requested image that create a cumulatively higher resolution image as each rendered layer is overlaid upon a previous layer(s), each layer having been rendered without information overlap with other rendered layers, and rendered layers are sent to the client until a time limit is met or all rendered layers have been sent before the time limit is met.

11. The method of claim 1, wherein the image caching server receives a configuration file from an administrator that tells the image server how to render and store images.

12. The method of claim 1, wherein the client'"'"'s request is load balanced among the plurality of image caching servers.

13. The method of claim 1, wherein a customer that stores images on an image caching server is charged a fee for the use of the image caching server.

14. The method of claim 13, wherein the fee is based upon demand for the customer'"'"'s images.

15. The method of claim 13, wherein the fee is based upon the customer'"'"'s choice of rendering and storage requirements.

16. A computer-readable medium carrying one or more sequences of instructions for dynamic image delivery, which instructions, when executed by one or more processors, cause the one or more processors to carry out the steps of, comprising:

receiving a client'"'"'s request for an image file on a DNS server;

selecting, by the DNS server using load balancing as a selection factor, an image caching server that is appropriate to serve the requested image file;

wherein the image caching server is one of a plurality of image caching servers distributed across a network;

determining whether the client'"'"'s network access speed is stored in a local storage device, when the client'"'"'s network access speed is not found in the local storage device, determining the client'"'"'s network access speed and storing the client'"'"'s network access speed on the local storage device; and

sending an appropriate rendered copy of the requested image that is rendered for the client'"'"'s network access speed.

17. A computer-readable medium as recited in claim 16, wherein the determining step calculates the client'"'"'s network access speed from the client'"'"'s download of a Web page.

18. A computer-readable medium as recited in claim 16, wherein the client sends the image caching server its calculated network access speed and the determining step stores the calculated network access speed on the local storage device.

19. A computer-readable medium as recited in claim 16, wherein the image caching server searches for an appropriate rendered copy of the requested image on the local storage device for the client'"'"'s network access speed, and wherein the sending step sends the appropriate rendered copy to the client when the appropriate rendered copy is found on the local storage device.

20. A computer-readable medium as recited in claim 19, wherein a plurality of rendered copies of the requested image are pre-rendered for different network access speeds and stored on the local storage device prior to the client'"'"'s image request.

21. A computer-readable medium as recited in claim 19, wherein storage space occupied by rendered copies of images on the local storage device is reclaimed by deleting rendered images based on any of:

time, popularity, or pre-determined priority.

22. A computer-readable medium as recited in claim 19, further comprising:

rendering an appropriate copy of the requested image for the client'"'"'s network access speed when an appropriate rendered copy is not found on the local storage device.

23. A computer-readable medium as recited in claim 22, wherein the rendering step stores the rendered appropriate copy on the local storage device.

24. A computer-readable medium as recited in claim 22, wherein the rendering step discards the rendered appropriate copy after it is sent to the client.

25. A computer-readable medium as recited in claim 16, wherein the sending step sends the client rendered layers of the requested image that create a cumulatively higher resolution image as each rendered layer is overlaid upon a previous layer(s), each layer having been rendered without information overlap with other rendered layers, and rendered layers are sent to the client until a time limit is met or all rendered layers have been sent before the time limit is met.

26. A computer-readable medium as recited in claim 16, wherein the image caching server receives a configuration file from an administrator that tells the image server how to render and store images.

27. A computer-readable medium as recited in claim 16, wherein the client'"'"'s request is load balanced among the plurality of image caching servers.

28. A computer-readable medium as recited in claim 16, wherein a customer that stores images on an image caching server is charged a fee for the use of the image caching server.

29. A computer-readable medium as recited in claim 28, wherein the fee is based upon demand for the customer'"'"'s images.

30. A computer-readable medium as recited in claim 28, wherein the fee is based upon the customer'"'"'s choice of rendering and storage requirements.

31. An apparatus, comprising:

a client request receiving subsystem on a DNS server that receives a client'"'"'s request for an image file;

an image caching server selecting subsystem on the DNS server that selects, by using load balancing as a selection factor, an image caching server that is appropriate to serve the requested image file;

wherein the image caching server is one of a plurality of image caching servers distributed across a network;

a network access determining subsystem that determines whether the client'"'"'s network access speed is stored in a local storage device, when the client'"'"'s network access speed is not found in the local storage device, determining the client'"'"'s network access speed and storing the client'"'"'s network access speed on the local storage device; and

an image sending subsystem sending an appropriate rendered copy of the requested image that is rendered for the client'"'"'s network access speed.

32. The apparatus of claim 31, wherein the determining subsystem calculates the client'"'"'s network access speed from the client'"'"'s download of a Web page.

33. The apparatus of claim 31, wherein the client sends the image caching server its calculated network access speed and the network access determining subsystem stores the calculated network access speed on the local storage device.

34. The apparatus of claim 31, wherein the image caching server searches for an appropriate rendered copy of the requested image on the local storage device for the client'"'"'s network access speed, and wherein the sending subsystem sends the appropriate rendered copy to the client when the appropriate rendered copy is found on the local storage device.

35. The apparatus of claim 34, wherein a plurality of rendered copies of the requested image are pre-rendered for different network access speeds and stored on the local storage device prior to the client'"'"'s image request.

36. The apparatus of claim 34, wherein storage space occupied by rendered copies of images on the local storage device is reclaimed by deleting rendered images based on any of:

time, popularity, or pre-determined priority.

37. The apparatus of claim 34, further comprising:

a rendering subsystem that renders an appropriate copy of the requested image for the client'"'"'s network access speed when an appropriate rendered copy is not found on the local storage device.

38. The apparatus of claim 37, wherein the rendering subsystem stores the rendered appropriate copy on the local storage device.

39. The apparatus of claim 37, wherein the rendering subsystem discards the rendered appropriate copy after it is sent to the client.

40. The apparatus of claim 31, wherein the sending subsystem sends the client rendered layers of the requested image that create a cumulatively higher resolution image as each rendered layer is overlaid upon a previous layer(s), each layer having been rendered without information overlap with other rendered layers, and rendered layers are sent to the client until a time limit is met or all rendered layers have been sent before the time limit is met.

41. The apparatus of claim 31, wherein the image caching server receives a configuration file from an administrator that tells the image server how to render and store images.

42. The apparatus of claim 31, wherein the client'"'"'s request is load balanced among the plurality of image caching servers.

43. The apparatus of claim 31, wherein a customer that stores images on an image caching server is charged a fee for the use of the image caching server.

44. The apparatus of claim 43, wherein the fee is based upon demand for the customer'"'"'s images.

45. The apparatus of claim 43, wherein the fee is based upon the customer'"'"'s choice of rendering and storage requirements.