Method for preconnecting to a server on a network

• US 6,606,645 B1
• Filed: 10/29/2001
• Issued: 08/12/2003
• Est. Priority Date: 10/29/1998
• Status: Expired due to Term

• Current Assignee: AT&T Corporation (AT&T, Inc.)
• Original Assignee: AT&T Corporation (AT&T, Inc.)
• Inventors: Kaplan, Haim, Zwick, Uri, Cohen, Edith
• Primary Examiner(s): Harrell, Robert B.
• Application Number:
  US10/021,459
• Time in Patent Office: 652 Days
• Field of Search: 709/200, 709/203, 709/217, 709/218, 709/223
• US Class Current: 709/203
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/10 in which an application is distributed across nodes in the network software deployment G06F8/60; multiprogramming arrangements G06F9/46
• CPC Class Codes: H04L 67/14 Session management for real-time applications in data packet communications networks H04L65/1066
• CPC Class Codes: H04L 69/329 in the application layer [OSI layer 7]
• CPC Class Codes: H04L 9/40 Network security protocols

Abstract

A method is disclosed for reducing user-perceived latency due to the time required to establish a connection to a server in a network. In accordance with the present invention, an open connection is established to a set of servers, there being some probability the user will contact one of the servers in the near future. This is referred to as preconnecting or prefetching the connection. In the context of a Web client-server network, a list of likely servers can be deduced from links on a current Web page a user is looking at or from a more sophisticated analysis of the user'"'"'s browsing habits. When the user requests a resource from one of the identified servers, the network connection has already been established, thereby reducing latency and improving service quality, especially for higher bandwidth clients for whom the delay is most noticeable. In contrast to conventional document prefetching, preconnecting does not hog network bandwidth or consume cache space, and hence can be used with much less scrutiny. Moreover, the technique can be implemented in Web browsers without protocol modifications or changes to Web server code.

Claims

1. A computer relable medium containing executable program instructions for performing a method on a computer connected to a network comprising the steps of:

identifying a server with a probability of being accessed;

establishing an open connection to said server;

waiting for a user request to use said connection; and

utilizing the open connection after a user request to use said connection is received.

2. The computer readable medium of claim 1 wherein said connection is established to provide access to a resource on said server.

3. The computer readable medium of claim 2 further comprising the step of:

retrieving information regarding said resource without retrieving said resource.

4. The computer readable medium of claim 2 further comprising the step of:

where said resource on said server has been cached, validating said cached resource.

5. The computer readable medium of claim 1 wherein said server is a World Wide Web server.

6. The computer readable medium of claim 5 wherein the step of identifying a server further comprises the steps of:

analyzing a World Wide Web page currently being viewed by a user for a link to a server; and

identifying a server referenced in said link on said World Wide Web page.

7. The computer readable medium of claim 1 wherein said connection is a TCP connection.

8. The computer readable medium of claim 1 further comprising the step of:

where said server is redirected to a second server, establishing an open connection to said second server prior to a request to use said connection to said second server.

9. The computer readable medium of claim 1 wherein said server is a DNS server and wherein said connection is established to provide an address of a second server with a probability of being accessed.

10. The computer readable medium of claim 1 further comprising the step of:

closing the open connection if a user request to use said connection is not received.

11. The method of claim 1 further comprising the step of:

closing the open connection if a user request to use said connection is not received.

12. A method of reducing delay in connecting to a server comprising the step of:

identifying a server with probability of being accessed;

establishing an open connection to said server;

waiting for a user request to use said connection; and

utilizing the open connection after a user request to use said connection is recieved.

13. The method of claim 12 wherein said server is a World Wide Web server.

14. The method of claim 13 wherein the step of identifying a server further comprises the steps of:

analyzing a World Wide Web page currently being viewed by a user for a link to a server; and

identifying a server referenced in said link on said World Wide Web page.

15. The method of claim 12 further comprising the step of:

where said server is redirected to a second server, establishing an open connection to said second server prior to a request to use said connection to said second server.

16. The method of claim 15 further comprising the step of:

where said resource on said server has been cached, validating said cached resource.

17. The method of claim 12 wherein said connection is established to provide access to a resource on said server.

18. The method of claim 17 further comprising the step of:

retrieving information regarding said resource without retrieving said resource.

19. The method of claim 12 wherein said connection is a TCP connection.

20. The method of claim 12 wherein said server is a DNS server and wherein said connection is established to provide an address of a second server with a probability of being accessed.