Pseudo proxy server providing instant overflow capacity to computer networks

• US 6,526,448 B1
• Filed: 12/22/1998
• Issued: 02/25/2003
• Est. Priority Date: 12/22/1998
• Status: Expired due to Fees

• Current Assignee: AT&T Corporation (AT&T, Inc.)
• Original Assignee: AT&T Corporation (AT&T, Inc.)
• Inventors: Blewett, Charles Douglas
• Primary Examiner(s): Sheikh, Ayaz
• Assistant Examiner(s): DINH, KHANH Q
• Application Number:
  US09/217,610
• Time in Patent Office: 1,526 Days
• Field of Search: 709/218, 709/222, 709/224, 709/238, 709/239, 709/242, 709/241, 713/201, 713/10, 455/448
• US Class Current: 709/238
• CPC Class Codes: H04L 67/1001 for accessing one among a plurality of replicated servers
• CPC Class Codes: H04L 67/1012 based on compliance of requirements or conditions with available server resources
• CPC Class Codes: H04L 67/1017 based on a round robin mechanism
• CPC Class Codes: H04L 67/1038 Load balancing arrangements to avoid a single path through a load balancer

Abstract

A pseudo proxy server is provided for a host network when the host network experiences periods of congestion. The host network determines whether an arrival rate of data requests exceeds a predetermined threshold. If so, the host network adds an address of a pseudo proxy server to a list of servers aliased to the host network. Thereafter, data requests are routed to the pseudo proxy server on a round robin basis. The pseudo proxy server may be engaged without first loading information content from the host network on the pseudo proxy server.

Claims

1. A method for managing overflow capacity in a computer network, comprising:

when a data request is received at the computer network, determining whether an arrival rate of data requests exceeds a predetermined threshold,

if the predetermined threshold is exceeded, adding an address of a pseudo proxy server to a list of servers aliased to the computer network and sending a recruitment message to the pseudo proxy server.

2. The method of claim 1, further comprising, thereafter routing data requests to the pseudo proxy server on a round robin basis with other servers of the computer network.

3. The method of claim 1, wherein the predetermined threshold is a predetermined capacity of servers in the computer network.

4. The method of claim 1, wherein the predetermined threshold is a predetermined bandwidth limit of a communications input to the computer network.

5. The method of claim 1, wherein the pseudo proxy server is added to the list of servers without first loading information content from the computer network on the pseudo proxy server.

6. A method for managing overflow capacity in a computer network, comprising:

determining whether the network is operating in a congested state, and

when the network is operating in a congested state, adding an address of a pseudo proxy server to a list of servers aliased to computer network and sending a recruitment message to the pseudo proxy server.

7. The method of claim 6, wherein the list is a DNS pool.

8. The method of claim 6, wherein the list associates a machine name of the network with IP addresses of servers that are members of the network.

9. The method of claim 6, wherein the adding occurs without a prior loading of information content from the network to the pseudo proxy server.

10. The method of claim 9, further comprising, at the pseudo proxy server:

receiving subsequent data requests addressed to the network,

determining whether information content responsive to the data request is stored on the pseudo proxy server, and

if not, retrieving responsive information content from another server on the computer network.

11. The method of claim 6, wherein a congestion decision is determined based on availability of communication resources in the network.

12. The method of claim 6, wherein a congestion decision is determined based on available disk resources in the network.

13. The method of claim 6, wherein a congestion decision is determined based on available processor resources in the network.

14. The method of claim 6, wherein a congestion decision is determined from a http log monitoring process at the network.

15. A method for managing overflow capacity in a computer network, comprising:

when a data request is received at the computer network, determining whether an arrival rate of data requests exceeds a predetermined threshold,

if the predetermined threshold is exceeded, adding an address of a pseudo proxy server to a list of servers aliased to the computer network and sending a recruitment message to a server to temporarily act as the pseudo proxy server to manage overflow capacity in the computer network.

16. The method of claim 15, further comprising, thereafter routing data requests to the pseudo proxy server on a round robin basis with other servers of the computer network.

17. The method of claim 15, wherein the predetermined threshold is a predetermined capacity of servers in the computer network.

18. The method of claim 15, wherein the predetermined threshold is a predetermined bandwidth limit of a communications input to the computer network.

19. The method of claim 15, wherein the pseudo proxy server is added to the list of servers without first loading information content from the computer network on the pseudo proxy server.

20. A method for managing overflow capacity in a computer network, comprising:

determining whether the network is operating in a congested state, and

when the network is operating in a congested state, adding an address of a pseudo proxy server to a list of servers aliased to computer network and sending a recruitment message to an unregistered server to act as the pseudo proxy server to manage overflow capacity in the computer network.

21. The method of claim 20, wherein the list is a DNS pool.

22. The method of claim 20, wherein the list associates a machine name of the network with IP addresses of servers that are members of the network.

23. The method of claim 20, wherein the adding occurs without a prior loading of information content from the network to the pseudo proxy server.

24. The method of claim 23, further comprising, at the pseudo proxy server:

receiving subsequent data requests addressed to the network,

determining whether information content responsive to the data request is stored on the pseudo proxy server, and

if not, retrieving responsive information content from another server on the computer network.

25. The method of claim 20, wherein a congestion decision is determined based on availability of communication resources in the network.

26. The method of claim 20, wherein a congestion decision is determined based on available disk resources in the network.

27. The method of claim 20, wherein a congestion decision is determined based on available processor resources in the network.

28. The method of claim 20, wherein a congestion decision is determined from a http log monitoring process at the network.