Method for improving web performance by client characterization-driven server adaptation

• US 20020198961A1
• Filed: 08/07/2002
• Published: 12/26/2002
• Est. Priority Date: 08/27/1999
• Status: Abandoned Application

• Current Assignee: AT&T Corporation (AT&T, Inc.)
• Original Assignee: AT&T Corporation (AT&T, Inc.)
• Inventors: Krishnamurthy, Balachander, Wills, Craig Ellis
• Application Number:
  US10/213,587
• Publication Number:
  US 20020198961A1
• Time in Patent Office: Days
• US Class Current: 709/217
• CPC Class Codes: G06F 16/957 Browsing optimisation, e.g. caching or content distillation
• CPC Class Codes: H04L 67/563 Data redirection of data network streams
• CPC Class Codes: H04L 67/565 Conversion or adaptation of application format or content adding application control or application functional data H04L67/561
• CPC Class Codes: H04L 67/566 Grouping or aggregating service requests, e.g. for unified processing
• CPC Class Codes: H04L 69/329 in the application layer [OSI layer 7]
• CPC Class Codes: H04L 9/40 Network security protocols

Abstract

The present invention is a method for improving delivery of content to a client communicating with a server on the Web. The client is categorized based on information about the client that can be determined by the server. That information is used to help drive tailored actions on the part of Web servers. Users with poor connectivity may choose not to spend much time at a Web site if it takes a long time to receive a page, even if the Web server at the site is not the bottleneck. Retaining such clients may be of interest to a Web site. Better-connected clients may be able to receive enhanced representations of Web pages such as with higher quality images.

Once a client is characterized as poor, a variety of server actions can be taken by the server, including altering the manner in which content is delivered, including guiding server policy decisions, aiding in caching decisions or deciding when to redirect the client to a mirror site. The method may also use network-aware client clustering techniques to provide client categorization. Such a cluster categorization can then be used to categorize subsequent clients from that cluster, even if a client-specific categorization is not available.

Claims

1. A method for delivering content to a client through a connection, the method comprising the steps of:

classifying the client according to at least one criterion indicative of the connection;

receiving a request from the client to serve content through the connection;

altering a manner in which the content is to be delivered in accordance with the classification of the client; and

delivering the content in the altered manner.

2. The method as claimed in claim 1, wherein the step of altering the manner of delivery comprises redirecting the client to a mirror server.

3. The method as claimed in claim 1, wherein the step of altering the manner of delivery comprises altering meta-information delivered with the content.

4. The method as claimed in claim 3, wherein the step of altering meta-information results in extending a freshness lifetime of an object in the content.

5. The method as claimed in claim 3, wherein the step of altering meta-information results in altering a policy of including cache validation requests with other messages exchanged with a server.

6. The method as claimed in claim 1, wherein the step of altering the manner of delivery comprises increasing a length of allowed TCP sessions.

7. The method as claimed in claim 1, further comprising altering the requested content before delivery.

8. The method as claimed in claim 1, wherein the step of classifying the client according to a connection criterion includes placing the client in one of a poor, a normal and a rich class.

9. The method as claimed in claim 8, wherein the client is initially placed in the normal class.

10. The method as claimed in claim 1, wherein the step of classifying the client includes receiving client characterization information from the client.

11. The method as claimed in claim 1, wherein the step of classifying the client includes measuring a time between accepting a TCP connection from the client and receipt of a first HTTP request from the client.

12. The method as claimed in claim 1, wherein the step of classifying the client includes the steps of:

in response to a client request, sending a redirect response, and

measuring a time between the client request and a redirected client request.

13. The method as claimed in claim 1, wherein the step of classifying the client includes measuring a time between transmittal of a container document to the client and receipt of a first request for an object in the document.

14. The method as claimed in claim 1, wherein the step of classifying the client includes measuring a time between transmittal of a container document to the client and receipt of a last request for an object in the document.

15. The method as claimed in claim 1, wherein the step of classifying the client includes measuring a criterion based on of a plurality of server requests.

16. The method as claimed in claim 15, wherein a criterion value E_first is adjusted based on a new measurement E_measured according to a formula:

E_first=α

E_first+(1−

α

)E_measured

wherein α

is a smoothing value in a range from 0 to 1.

17. The method as claimed in claim 1, wherein the step of classifying the client comprises classifying the client in a class of a group of clients to which the client belongs.

18. The method as claimed in claim 17, wherein the group comprises clients under common administrative control.

19. The method as claimed in claim 1, further comprising the steps of generating a cookie containing a result of the classification step, and transmitting the cookie to the client.

20. The method as claimed in claim 1, wherein the step of classifying the client includes transmitting an executable to the client for measuring the criterion indicative of the connection.

21. The method as claimed in claim 1, wherein the step of altering the manner of delivery of the content includes maintaining the content without alteration.

22. A server for delivering content to a client through a connection, the server configured to perform the steps of:

classifying the client according to at least one criterion indicative of the connection;

receiving a request from the client to serve content through the connection;

altering a manner in which the content is to be delivered in accordance with the classification of the client; and

delivering the content in the altered manner.

23. The server as claimed in claim 22, wherein the step of altering the manner of delivery comprises redirecting the client to a mirror server.

24. The server as claimed in claim 22, wherein the step of altering the manner of delivery comprises altering meta-information delivered with the content.

25. The server as claimed in claim 24, wherein the step of altering meta-information results in extending a freshness lifetime of an object in the content.

26. The server as claimed in claim 24, wherein the step of altering meta-information results in altering a policy of including cache validation requests with other messages exchanged with a server.

27. The server as claimed in claim 22, wherein the step of altering the manner of delivery comprises increasing a length of allowed TCP sessions.

28. The server as claimed in claim 22, further configured to perform the step of altering the requested content before delivery.

29. The server as claimed in claim 22, wherein the step of classifying the client according to a connection criterion includes placing the client in one of a poor, a normal and a rich class.

30. The server as claimed in claim 29, configured to initially place the client in the normal class.

31. The server as claimed in claim 22, wherein the step of classifying the client includes receiving client characterization information from the client.

32. The server as claimed in claim 22, wherein the step of classifying the client includes measuring a time between accepting a TCP connection from the client and receipt of a first HTTP request from the client.

33. The server as claimed in claim 22, wherein the step of classifying the client includes the steps of:

in response to a client request, sending a redirect response, and

measuring a time between the client request and a redirected client request.

34. The server as claimed in claim 22, wherein the step of classifying the client includes measuring a time between transmittal of a container document to the client and receipt of a first request for an object in the document.

35. The server as claimed in claim 22, wherein the step of classifying the client includes measuring a time between transmittal of a container document to the client and receipt of a last request for an object in the document.

36. The server as claimed in claim 22, wherein the step of classifying the client includes measuring a criterion based on of a plurality of server requests.

37. The server as claimed in claim 36, wherein a criterion value E_first is adjusted based on a new measurement E_measured according to a formula:

E_first=α

E_first+(1−

α

)E_measured

wherein α

is a smoothing value in a range from 0 to 1.

38. The server as claimed in claim 22, wherein the step of classifying the client comprises classifying the client in a class of a group of clients to which the client belongs.

39. The server as claimed in claim 38, wherein the group comprises clients under common administrative control.

40. The server as claimed in claim 22, further configured to perform the steps of generating a cookie containing a result of the classification step, and transmitting the cookie to the client.

41. The server as claimed in claim 22, wherein the step of classifying the client includes transmitting an executable to the client for measuring the criterion indicative of the connection.

42. The server as claimed in claim 22, wherein the step of altering the manner of delivery of the content includes maintaining the content without alteration