# US 8,150,951 B2 · System and method for communicating in a loadbalancing environment > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 8,150,951 B2 - Document ID: US8150951B2 - Status: Granted - Kind: B2 - Application number: 10/192,919 - Filed: 2002-07-10 - Published: 2005-08-25 - Granted: 2012-04-03 - Earliest claimed: 2002-07-10 - Assignees: Cisco Technology, Inc. - Inventors: Chris O'Rourke; Robert M. Batz; Rabih A. Dabboussi; John M. Glotzer; Louis F. Menditto; Alpesh S. Patel; Kent K. Leung - Web page: https://patentgrep.com/patent/US8150951B2 ## CPC - 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)} - H04L 12/4633: {Interconnection of networks using encapsulation techniques, e.g. tunneling} - H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M) ## Abstract A method for communicating in a loadbalancing environment is provided that in a particular embodiment includes receiving a request packet from a network access server (NAS) to initiate a communication session. The request packet is then communicated to a tunneling protocol network server (TPNS) and a response packet is received in response to the request packet. The response packet establishes a tunnel that facilitates the communication session and that includes an identification element associated with the TPNS such that a data transfer associated with the communication session is executed between the NAS and the TPNS. ## Claims ### Claim 1 A method for communicating in a loadbalancing environment, the method comprising: receiving, at a loadbalancer, a request packet from a network access server (NAS) requesting loadbalancing among a group of tunneling protocol network servers (TPNSs) distinct from the NAS in order to facilitate a communication session for an end user; selecting a tunneling protocol network server (TPNS) from the group of tunneling protocol network servers distinct from the NAS by the loadbalancer to balance a processing load among the group of tunneling protocol network servers; communicating, by the loadbalancer, the request packet to the TPNS; receiving, at the loadbalancer, a first response packet comprising an identification element associated with the TPNS in response to the request packet, the first response packet establishing a tunnel comprising the NAS, the loadbalancer, and the TPNS that facilitates the communication session; communicating, from the loadbalancer, a second response packet to the NAS in response to receiving the first response packet; wherein data transfers from the NAS to the TPNS and data transfers from the TPNS to the NAS occurring subsequent to the establishment of the tunnel associated with the communication session are executed without going through the loadbalancer; and wherein the loadbalancer does not maintain state information regarding the communication session subsequent to the establishment of the tunnel associated with the communication session. ### Claim 2 (depends on 1) The method of claim 1, further comprising: authenticating the end user associated with the communication session before establishing the tunnel that facilitates the communication session. ### Claim 3 (depends on 1) The method of claim 1, wherein the identification element includes an internet protocol (IP) address associated with the TPNS such that the NAS may communicate the data transfer to the TPNS. ### Claim 4 (depends on 1) The method of claim 1, further comprising: providing a communicative interface between the NAS and the TPNS that uses an access network. ### Claim 5 (depends on 1) The method of claim 1, wherein the request packet is received from the end user through a radio access network (RAN) and the NAS. ### Claim 6 (depends on 1) The method of claim 1, further comprising: receiving, at a second network access server (NAS-2) serving a different coverage area than the NAS, packets for the communication session from the end user; sending, by the NAS-2, the packets from the end user to the NAS; and sending, by the NAS, the packets to the TPNS selected by the loadbalancer without going through the loadbalancer. ### Claim 7 Software for communicating in a loadbalancing environment that is embodied in non-transitory computer readable media and operable to: receive, at a loadbalancer, a request packet from a network access server (NAS) requesting loadbalancing among a group of tunneling protocol network servers (TPNSs) distinct from the NAS in order to facilitate a communication session for an end user; select a tunneling protocol network server (TPNS) from the group of tunneling protocol network servers distinct from the NAS by the loadbalancer to balance a processing load among the group of tunneling protocol network servers; communicate, by the loadbalancer, the request packet to the TPNS; receive, at the loadbalancer, a first response packet comprising an identification element associated with the TPNS in response to the request packet, the first response packet establishing a tunnel comprising the NAS, the loadbalancer, and the TPNS that facilitates the communication session; and communicate, from the loadbalancer, a second response packet to the NAS in response to receiving the first response packet; wherein data transfers from the NAS to the TPNS and data transfers from the TPNS to the NAS occurring subsequent to the establishment of the tunnel associated with the communication session are executed without going through the loadbalancer; and wherein the loadbalancer does not maintain state information regarding the communication session subsequent to the establishment of the tunnel associated with the communication session. ### Claim 8 (depends on 7) The software of claim 7, further operable to: authenticate the end user associated with the communication session before establishing the tunnel that facilitates the communication session. ### Claim 9 (depends on 7) The software of claim 7, wherein the identification element includes an internet protocol (IP) address associated with the TPNS such that the NAS may communicate the data transfer to the TPNS. ### Claim 10 (depends on 7) The software of claim 7, further operable to: provide a communicative interface between the NAS and the TPNS that uses an access network. ### Claim 11 (depends on 7) The software of claim 7 wherein the request packet is received from the end user through a radio access network (RAN) and the NAS. ### Claim 12 A system for communicating in a loadbalancing environment, comprising: a network access server (NAS) operable to send a request packet to request loadbalancing among a group of tunneling protocol network servers (TPNSs) distinct from the NAS in order to facilitate a communication session for an end user; a first interface to the NAS; a second interface to a group of tunneling protocol network servers; and a loadbalancer comprising at least one processor operable to: receive a request packet from the first interface; select a tunneling protocol network server (TPNS) from the group of tunneling protocol network servers distinct from the NAS to balance a processing load among the group of tunneling protocol network servers; communicate the request packet to the TPNS through the second interface; receive a first response packet through the second interface comprising an identification element associated with the TPNS in response to the request packet, the response packet establishing a tunnel comprising the NAS, the loadbalancer, and the TPNS that facilitates the communication; and communicate a second response packet to the NAS in response to receiving the first response packet; wherein data transfers from the NAS to the TPNS and data transfers from the TPNS to the NAS occurring subsequent to the establishment of the tunnel associated with the communication session are executed without going through the loadbalancer; and wherein the loadbalancer does not maintain state information regarding the communication session subsequent to the establishment of the tunnel associated with the communication session. ### Claim 13 (depends on 12) The system of claim 12, further comprising: an authentication, authorization, and accounting (AAA) server operable to authenticate the end user associated with the communication session before establishing the tunnel that facilitates the communication session. ### Claim 14 (depends on 12) The system of claim 12, wherein the identification element includes an internet protocol (IP) address associated with the TPNS such that the NAS may communicate the data transfer to the TPNS. ### Claim 15 (depends on 12) The system of claim 12, further comprising: a communicative interface between the NAS and the TPNS that uses an access network. ### Claim 16 (depends on 12) The system of claim 12 wherein the request packet is received from the end user through a radio access network (RAN) and the NAS. ### Claim 17 An apparatus for communicating in a loadbalancing environment, comprising: a loadbalancer comprising at least one processor operable to: receive a request packet from a network access server (NAS) that requests loadbalancing among a group of tunneling protocol network servers (TPNSs) distinct from the NAS in order to facilitate a communication session for an end user; select a tunneling protocol network server (TPNS) from the group of tunneling protocol network servers distinct from the NAS to balance a processing load among the group of tunneling protocol network servers; communicate the request packet to the TPNS; receive a first response packet comprising an identification element associated with the TPNS from the TPNS in response to the request packet, the response packet establishing a tunnel comprising the NAS, the loadbalancer, and the TPNS that facilitates the communication session; and communicate a second response packet to the NAS in response to receiving the first response packet; wherein data transfers from the NAS to the TPNS and data transfers from the TPNS to the NAS occurring subsequent to the establishment of the tunnel associated with the communication session are executed without going through the loadbalancer; and wherein the loadbalancer does not maintain state information regarding the communication session subsequent to the establishment of the tunnel associated with the communication session.