Load balancing between LNSs using virtual LNS with minimal LAC configuration

• US 7,225,236 B1
• Filed: 08/07/2001
• Issued: 05/29/2007
• Est. Priority Date: 08/07/2001
• Status: Expired due to Term

• Current Assignee: Valtrus Innovations Limited (f/k/a Dolya Holdco 9 Limited) (Key Patent Innovations Limited)
• Original Assignee: 3Com Corporation (HP Inc.)
• Inventors: Puthiyandyil, Sanil Kumar, Radhakrishnan, Shaji, Ramankutty, Rajesh, Amara, Satish
• Primary Examiner(s): Meky, Moustafa M.
• Application Number:
  US09/923,895
• Time in Patent Office: 2,121 Days
• Field of Search: 709/239, 709/238, 709/235, 709/237, 709200-203, 709217-229, 709/245, 709/249, 370/237
• US Class Current: 709/218
• CPC Class Codes: H04L 12/2856 Access arrangements, e.g. Internet access asynchronous transfer mode networks H04L12/5601; broadband local area networks H04L12/2801; optical access or distribution networks H04Q11/0067; access to open networks H04L12/5691; digital subscriber line end-user equipment and bit-level processing of data on a PSTN-based network H04M11/00; home network gateways H04L12/2834; wireless access networks H04W
• CPC Class Codes: H04L 12/2859 Point-to-point connection between the data network and the subscribers encapsulation H04L12/4633; virtual LANs H04L12/4641; routing of packets H04L45/00
• CPC Class Codes: H04L 12/2876 Handling of subscriber policies group policies management H04L41/0893
• CPC Class Codes: H04L 12/4633 Interconnection of networks using encapsulation techniques, e.g. tunneling
• CPC Class Codes: H04L 67/1001 for accessing one among a plurality of replicated servers
• 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/1023 based on a hash applied to IP addresses or costs
• CPC Class Codes: H04L 67/1029 using data related to the state of servers by a load balancer

Abstract

A system for load balancing, the system includes a LAC, a contact LNS, and a plurality of load balancing LNSs. The LAC includes a contact LNS address, the contact LNS address specifies the address of a contact LNS. The contact LNS is communicatively coupled to the LAC and the plurality of load balancing LNSs are communicatively coupled to the contact LNS and to the LAC. The LAC sends a message to the contact LNS, the message informing the LAC of its availability and the contact LNS sends a response message containing IP address of a selected one of the plurality of load balancing LNSs to which the LAC should establish a session.

Claims

1. A system for load balancing, the system comprising:

a contact L2TP Network Server (LNS) that can determine whether to establish a session between the contact LNS and an L2TP Access Concentrator (LAC), the contact LNS being communicatively coupled to the LAC;

the LAC, the LAC including an address of the contact LNS, the LAC using the address of the contact LNS to send to the contact LNS at least a first message to request establishment of the session between the contact LNS and the LAC and to inform the contact LNS of the availability of the LAC for participating in load balancing; and

a plurality of load balancing LNSs communicatively coupled to the contact LNS and to the LAC,

wherein if the contact LNS determines the contact LNS can handle establishing the requested session, the contact LNS establishes the requested session with the LAC, and

wherein if the contact LNS determines the contact LNS cannot handle establishing the requested session, the contact LNS sends to the LAC a response message containing an Internet Protocol (IP) address of a selected load balancing LNS of the plurality of load balancing LNSs to which the LAC should establish a session.

2. The system of claim 1 wherein the contact LNS is included within a virtual LNS.

3. The system of claim 1, wherein the at least a first message to request establishment of the session between the contact LNS and the LAC and to inform the contact LNS of the availability of the LAC for participating in load balancing includes an Incoming Call Request (ICRQ) message.

4. The system of claim 1 wherein the response message is an Incoming Call Response (ICRP) message.

5. The system of claim 1 further including a customer premise equipment (CPE) coupled to the LAC.

6. The system of claim 1, wherein the contact LNS includes a list of LNSs available to provide LNS functions if the contact LNS determines the contact LNS cannot handle a session with the LAC.

7. The system of claim 1, wherein each of the plurality of load balancing LNSs transmits heartbeat signals to the contact LNS so that the contact LNS can determine which LNSs of the plurality of load balancing LNSs are available to participate in load balancing.

8. A method of load balancing, the method comprising:

using an address of a contact L2TP Network Server (LNS) to establish an L2TP tunnel between the contact L2TP Network Server (LNS) and an L2TP Access Concentrator (LAC), the LAC containing the address of the contact LNS;

sending to the contact LNS from the LAC at least a first message to request establishment of a session between the contact LNS and the LAC and to inform the contact LNS that the LAC can participate in load balancing; and

determining whether the contact LNS can handle the session between the contact LNS and the LAC,

wherein, if the contact LNS can handle the session between the contact LNS and the LAC, the method further comprises establishing the session between the contact LNS and the LAC, and

wherein, if the contact LNS cannot handle the session between the contact LNS and the LAC, the method further comprises the LAC;

(i) receiving from the contact LNS an address of a next available LNS, (ii) establishing a connection with the next available LNS, and then establishing a session with the next available LNS, and (iii) receiving data and forwarding the data to the next available LNS.

9. The method of claim 8, wherein the at least a first message to request establishment of a session between the contact LNS and the LAC and to inform the contact LNS that the LAC can participate in load balancing includes an Incoming Call Request (ICRQ) message.

10. The method of claim 9 wherein the address of the next available LNS is included in an Incoming Call Response (ICRP) message.

11. The method of claim 9 wherein the contact LNS is included in a virtual LNS.

12. The method of claim 8, wherein the at least a first message to request establishment of a session between the contact LNS and the LAC and to inform the contact LNS that the LAC can participate in load balancing comprises a Start-Control-Connection-Request (SCCRQ) message.

13. The method of claim 9, wherein the ICRQ message comprises an attribute-value pair that indicates the LAC is capable of performing load balancing.

14. A method for load balancing between a contact L2TP Network Server (LNS), an L2TP Access Concentrator (LAC), and a next LNS, the method comprising:

sending to the contact LNS from the LAC at least a first message to request establishment of a session between the contact LNS and the LAC and to inform the contact LNS that the LAC can participate in load balancing;

at the contact LNS, determining whether the contact LNS can handle the L2TP session between the contact LNS and the LAC;

sending to the LAC from the contact LNS at least a second message that (i) indicates whether the contact LNS can handle the L2TP session between the contact LNS and the LAC, and (ii) contains an address of the next LNS if the contact LNS cannot handle the L2TP session between the contact LNS and the LAC;

wherein, if the contact LNS can handle the L2TP session between the contact LNS and the LAC, the method further comprises establishing the L2TP session between the contact LNS and the LAC; and

wherein if the contact LNS cannot handle the L2TP session between the contact LNS and the LAC, the method further comprises establishing a connection between the next LNS and the LAC using the next LNS address, and then establishing an L2TP session between the next LNS and the LAC.

15. The method of claim 14 wherein the contact LNS is included in a virtual LNS.

16. The method of claim 15 including the further step of determining the identity of the contact LNS within the virtual LNS.

17. The method of claim 14,

wherein if the contact LNS can handle the L2TP session, then after establishing the L2TP session between the contact LNS and the LAC, the method further comprising sending user data between (i) the LAC and the contact LNS, and (ii) the LAC and a customer premises equipment (CPE), and

wherein if the contact LNS cannot handle the L2TP session, then after establishing the session between the next LNS and the LAC, the method further comprising sending user data between (i) the LAC and the next LNS, and (ii) the LAC and the CPE.

18. The method of claim 14, wherein the function of determining whether the contact LNS can handle the L2TP session includes determining whether the contact LNS is overloaded.

19. A system for load balancing, the system comprising:

a Customer Premise Equipment (CPE);

an L2TP Access Concentrator (LAC) coupled to the CPE;

a first network coupled to the LAC;

a second network coupled to the first network;

a contact L2TP Network Server (LNS) coupled to the first network; and

a next LNS coupled to the second network, the next LNS having an Internet Protocol (IP) address,

wherein the LAC sends to the contact LNS via the first network a message informing the contact LNS of the availability of the LAC for participating in load balancing,

wherein the contact LNS determines whether the contact LNS can handle a session with the LAC,

wherein if the contact LNS determines the contact LNS can handle the session, the contact LNS establishes the session with the LAC, and

wherein if the contact LNS determines the contact LNS cannot handle the session, the contact LNS sends to the LAC a message containing the IP address of the next LNS, and the LAC establishes a session with the next LNS via the second network.

20. The system of claim 19 wherein the contact LNS includes a table and the address of the next LNS is stored in the table.

21. The system of claim 19 wherein the contact LNS is included in a virtual LNS.

22. A system for load balancing, the system comprising:

means for an L2TP Access Concentrator (LAC) to obtain an address of a contact L2TP Network Server (LNS);

means for sending to the contact LNS from the LAC a message that indicates the LAC is available for participating in load balancing;

means for receiving from the contact LNS an address of a next available LNS;

means for establishing a connection and a session with the next available LNS; and

means for receiving data and forwarding the data to the next available LNS.

23. A computer readable medium for an L2TP Access Concentrator (LAC), the computer readable medium having stored therein program code executable by a processing unit of the LAC, the program code comprising:

first program code for causing the LAC to obtain an address of a contact L2TP Network Server (LNS);

second program code for causing the LAC to send to the contact LNS at the address of the contact LNS a message that indicates the LAC is available for participating in load balancing;

third program code for receiving from the contact LNS an address of a next available LNS;

fourth program code for establishing a connection and a session with the next available LNS; and

fifth program code for receiving data and forwarding the data to the next available LNS.