System and method for optimizing sessions and network resources in a loadbalancing environment

[0001] This invention relates in general to the field of communications, and, more particularly, to a system and a method for avoiding stale sessions on a server in a loadbalancing environment.

[0002] Networking architectures have grown increasingly complex in communications environments. In addition, the augmentation of clients or end users wishing to communicate in a network environment has caused many networking configurations and systems to respond by adding elements to accommodate the increase in networking traffic. Communication tunnels or links may be used in order to establish or to gain access to a network, whereby an end user or an object may initiate a tunneling protocol by invoking a selected location or a network node. The network node or central location may then provide a platform that the end user may use to conduct a communication session.

[0003] As the subscriber base of end users increases, proper routing and efficient management of communication sessions and data flows becomes even more critical. Having access to, or being aware of, accurate network node activity is important for executing proper loadbalancing techniques. In cases where improper loadbalancing protocols are executed, certain network components may be overwhelmed, while other (potentially more capable) network resources remain untapped. This overburdening may decrease throughput and unnecessarily restrict the flow of network traffic (potentially causing congestion or bottlenecks in the system).

[0004] Additionally, stale sessions, which are generally prevalent in any network communications, may be problematic because they inhibit bandwidth capabilities and preclude additional communications tunnels or end users from being accommodated by a given architecture. Stale sessions may be a problem for a database, a table, or any other storage component relegated the task of accounting for a resource-consuming entity. Stale sessions create an inefficiency because network components may still continue to maintain certain data segments even though the corresponding network activity has ceased. The network activity (e.g. connections or channels), which initially required, spawned, or otherwise triggered these resources, is no longer occurring and, thus, their network resources should be liberated or their responsibilities should be relinquished such that they can be deployed for additional connections and channels.

[0005] Thus, designing an optimal loadbalancing configuration for any network architecture provides a significant challenge to component manufacturers, system administrators, and network operators.

[0006] From the foregoing, it may be appreciated by those skilled in the art that a need has arisen for an improved communications approach that provides for optimal loadbalancing between two end points or nodes. In accordance with one embodiment of the present invention, a system and a method for loadbalancing in a network environment are provided that greatly reduce disadvantages and problems associated with conventional loadbalancing techniques.

[0007] According to one embodiment of the present invention, a method for loadbalancing in a network environment is provided that includes receiving a create request from an end user for a communications link provided by a network node and communicating a response to the end user in order to establish a communication session. The method further includes identifying a selected one of a plurality of network nodes to facilitate the communication session. The identification of the selected network node is achieved through binding of a session identifier associated with the end user to the selected network node.

[0008] Certain embodiments of the present invention may provide a number of technical advantages. For example, according to one embodiment of the present invention a communications approach is provided that allows a loadbalancer to more properly distribute work to multiple network nodes. This is a result of a loadbalancer that can optimally appropriate usage of network resource (IP address pools, gateway memory), consistently route user data to its proper connection, and systematically avoid double-billing scenarios.

[0009] The present invention can offer a tighter coupling between the GGSN and the PDP create requests: such a coupling being achieved through the loadbalancer. This, in turn, yields a significant efficiency in utilizing network resources. Moreover, by localizing an end user to a given GGSN, the present invention offers enhanced control for manipulating the end user's experience and resources.

[0010] Certain embodiments of the present invention may enjoy some, all, or none of these advantages. Other technical advantages may be readily apparent to one skilled in the art from the following figures, description, and claims.

[0016] FIG. 1 is a simplified block diagram of a communication system 10 for communicating data in a network environment. Communication system 10 includes an end user 12, a radio access network (RAN) 14, a serving general packet radio service (GPRS) support node (SGSN) 18, and GPRS internet protocol (IP) network 20. Additionally, communication system 10 may include a loadbalancer 26 (that may include an international mobile station identifier (IMSI) table 28) and multiple gateway GPRS support nodes (GGSNs) 30a-b. FIG. 1 may be generally configured or arranged to represent 2.5G communication architecture applicable to a Global System for Mobile (GSM) environment in accordance with a particular embodiment of the present invention. However, the 2.5G architecture is offered for purposes of example only and may alternatively be substituted with any suitable networking protocol or arrangement that provides a communicative platform for communication system 10. For example, communication system 10 may cooperate with any version of a GPRS tunneling protocol (GTP) that includes loadbalancing operations. This may be inclusive of first generation, 2G, and 3G architectures that provide features for workload distribution.

[0017] In accordance with the teachings of the present invention, communication system 10 provides a loadbalancing operation that offers optimal communications between end user 12 and selected GGSNs 30a-b. Loadbalancer 26 binds an end user's network access connection to a particular GGSN by building a sticky object, which is based on information present in the access protocol. This would, in turn, eliminate troublesome stale packet data protocol contexts (PDPs) or hanging PDPs. This enhancement (in adequately removing these unsatisfactory PDP elements) can be accomplished by parsing the GTP control stream and by building a persistent sticky object that can be stored in loadbalancer 26. Hence, stickying may be performed based on an access connection or on a PDP or a layer-2 tunnel connectivity coming in from the SGSN. In one respect, this achieves a stickying operation based on layer-2 information.

[0018] Note that, typically, loadbalancing is accomplished through a flow categorizing function that binds the layer-4 flow to the selected gateway. In the mechanism provided by loadbalancer 26, instead of using the layer-4 flow, loadbalancer 26 makes use of a user identifier (e.g. an IMSI or a mobile subscriber ISDN (MSISDN)) for binding purposes. Hence, loadbalancer 26 makes a loadbalancing decision for the very first session create request from the user and forwards subsequent create requests from the same user (same IMSI or MSISDN) to the same gateway. This also greatly reduces the amount of information that needs to be stored and searched within loadbalancer 26, thereby increasing the capacity of loadbalancer 26. To support multiple sessions from the same user (multiple primary PDPs from the same user in GPRS/UMTS world) loadbalancer 26 keeps track of the reference count (‘refcount’) on this binding. When the server deletes this session, it notifies loadbalancer 26 about it by sending an explicit message. Loadbalancer 26, in turn, decreases the refcount on the binding and eventually cleans it up if refcount becomes zero.

[0019] Note that such operations, which minimize consumption of resources in the network, would be particularly beneficial to oversubscribed scenarios where a hanging PDP would take a given IP address out of circulation. The present invention overcomes such a scenario by properly accounting for a hanging PDP such that network resources can be optimized. The present invention offers: improved capacity management in loadbalancer 26, optimal usage of network resources (IP address pools, gateway memory), consistent routing of user data, and a significant reduction in double-billing scenarios. The present invention can achieve a tighter coupling between the GGSN and the PDP create requests through loadbalancer 26. In addition, by localizing an end user to a given GGSN, the present invention offers enhanced control for manipulating the end user's experience and resources.

[0020] Note that for purposes of teaching and discussion, it is useful to provide some overview as to the way in which the following invention operates. The following foundational information may be viewed as a basis from which the present invention may be properly explained. Such information is offered earnestly for purposes of explanation only and, accordingly, should not be construed in any way to limit the broad scope of the present invention and its potential applications.

[0021] In a clustered or loadbalancing environment, a stale user connection could cause problems such as misrouting of user data, double billing, inappropriate release of resources for an active connection, etc. This happens when the same session comes up on a server that is different from the server to which it was previously assigned. Consider, for example, a scenario involving a GPRS/UMTS network. A user (i.e. IMSI) can create multiple sessions identified by a network service access point identifier (NSAPI). When the GGSNs are deployed in a loadbalanced environment, assume a delete request is lost between the SGSN and GGSN so that the PDP becomes stale on the GGSN. Subsequently, if the same create request (same IMSI+NSAPI) comes to the loadbalancer, it loadbalances it afresh because it no longer has the user location information. This may cause the same PDP to exist on two or more GGSNs, which can cause misrouting of user data and inconsistencies in call detail records (CDRs) (e.g. S-CDRs and G-CDRs).

[0022] Problems could also occur because some RADIUS servers assign the same IP address to a user even if the session identifiers are different during the sticky time. In the GPRS/UMTS environment, if the second request arrives within the sticky time, it is generally assigned the same IP address even in cases where the NSAPI (and, thus, the TID) is different. If this session is assigned to a different GGSN, the request is fulfilled, but this could still lead to a problem of the old PDP (eventually) freeing up the IP address of the new one.

[0023] Hence, when a given loadbalancer makes a decision for an assignment of a PDP to a GGSN (within a GGSN cluster), current loadbalancing configurations make a different loadbalancing decision for each create request that is seen. Therefore, traffic for a given end user (or IMSI) could be spread across multiple GGSNs of the GGSN cluster. This could result in one device (e.g. a mobile station) occupying resources (memory, processing, etc.) from multiple GGSNs.

[0024] This presents a number of salient issues for the loadbalancer. For example, consider a case where a second PDP create request is seen by the loadbalancer, which then assigns the second PDP to a GGSN other than the GGSN assigned for the first PDP create. However (in this example), in between these two create messages, the end user may have timed out of a given session (e.g. the powered down his phone, the mobile station departed silently, the network lost or misrouted a delete request, etc.). Note that the loadbalancer is not maintaining state information and, therefore, the loadbalancer does not know the context for this second PDP create (e.g., the loadbalancer does not know if an end user is reconnecting). This could present a problem, for example, in that another IP address could be allocated for the end user. In such a case, multiple IP addresses could be removed from an IP address pool, whereby several GGSNs are consuming resources for only a single end user.

[0025] The root cause of the problems described above is that the loadbalancer makes a fresh load balancing decision for every new request from the user. To solve this problem, a mechanism is needed to make a loadbalancing decision only once for a subscriber and, thereafter, stick to it by forwarding all subsequent create requests from the same subscriber to the GGSN selected.

[0026] In order to resolve these issues (and others), loadbalancer 26 provides a protocol that can identify the device making the PDP create request and, based on that information, deliver data associated with this PDP create request to the same GGSN. This may occur until such time that the GGSN provides feedback to loadbalancer 26 and indicates that the user is truly logged off the network (i.e. the GGSN has given up its resources for this end user).

[0027] Note that the concept of building a sticky object to bind a user to a loadbalanced device is not new. Loadbalancers in the market today build sticky object based on layer-3 information (user IP address), or application information, such as HTTP cookies. In contrast to these operations, loadbalancer 26 is operable to create an object (e.g. an IMSI sticky), in order to create a persistent binding between the IMSI and the actual GGSN servicing that IMSI. In essence, the more tightly coupled the loadbalancer is to the GGSN, the better the performance of the system. The present invention can localize an end user to a given GGSN. Additional details relating to these binding operations are provided below with reference to corresponding FIGURES.

[0028] Turning now to the infrastructure of FIG. 1, end user 12 is a client or a customer wishing to initiate a communication in communication system 10 via GPRS IP network 20. End user 12 may be inclusive of devices used to initiate a communication, such as a computer, a personal digital assistant (PDA), a laptop or an electronic notebook, a telephone, a mobile station, or any other device, component, element, or object capable of initiating voice or data exchanges within communication system 10. End user 12 may also be inclusive of a suitable interface to the human user, such as a microphone, a display, a keyboard, or other terminal equipment (such as for example an interface to a personal computer or to a facsimile machine in cases where end user 12 is used as a modem). End user 12 may also be any device that seeks to initiate a communication on behalf of another entity or element, such as a program, a database, or any other component, device, element, or object capable of initiating a voice or a data exchange within communication system 10. Data, as used herein in this document, refers to any type of numeric, voice, video, audio-visual, or script data, or any type of source or object code, or any other suitable information in any appropriate format that may be communicated from one point to another.

[0029] RAN 14 is a communications interface between end user 12 and SGSN 18. RAN 14 may comprise a base transceiver station and a base station controller. The communications interface provided by RAN 14 offers connectivity and allows data to be exchanged between end user 12 and any number of selected elements within communication system 10. RAN 14 facilitates the delivery of a request packet generated by end user 12 and the reception of information sought by end user 12. RAN 14 is only one example of a communications interface between end user 12 and SGSN 18. Other types of communications interfaces may be used for a desired network design based on particular needs.

[0030] GPRS IP network 20 represents a series of points or nodes of interconnected communication paths for receiving and transmitting packets of information that propagate through communication system 10. GPRS IP network 20 offers a communicative interface between end user 12 and selected GGSNs 30a-b and may be any local area network (LAN), wireless local area network (WLAN), metropolitan area network (MAN), wide area network (WAN), virtual private network (VPN), or any other appropriate architecture or system that facilitates communications in a network environment. GPRS IP network 20 implements a user datagram protocol (UDP)/internet protocol (UDP/IP) communication language protocol in a particular embodiment of the present invention. However, GPRS IP network 20 may alternatively implement any other suitable communication protocol for transmitting and receiving data or information within communication system 10.

[0031] SGSN 18 and GGSNs 30a-b are network elements that cooperate in order to facilitate a communication session involving end user 12. GGSNs 30a-b are communications or network nodes that may be working in conjunction with multiple SGSNs 18 to provide a communications medium in a GPRS service network environment in communicating data exchanges within communication system 10. GPRS represents a packet-based data bearer service for communication services that may be delivered as a network overlay for any type of suitable network configuration or platform. GPRS generally applies packet-radio and packet switching principles to transfer data packets in an efficient way between GSM elements or units and external packet data networks. GPRS may support multiple internet communication protocols and may enable existing IP, X.25, or any other suitable applications or platforms to operate over GSM connections.

[0032] Loadbalancer 26 is an element or a device that receives requests and then distributes those requests to the next available server or node. The available server or node may be any computer or device on a network that manages network resources or that processes data. For example, the network node may be a selected GGSN 30a-b or a selected network access server (NAS). Such loadbalancing decisions may be executed based on suitable algorithms, software, or hardware provided in loadbalancer 26.

[0033] Loadbalancer 26 may also perform other suitable loadbalancing tasks, such as dividing the amount of work that an element has to do between two or more elements to ensure more work gets done in the same amount of time and, in general, accommodating end users 12 more quickly. The term ‘loadbalancer’ encompasses any suitable network element such as a router, a switch, a bridge, a gateway, a server, or any other suitable element, component, device, or object operable to facilitate data reception or transmission in a network environment. Additionally, loadbalancer 26 and/or GGSNs 30a-b may include any appropriate hardware, software, (or a combination of both) or any appropriate component, device, element, or object that suitably assists or facilitates the operations described herein. In certain embodiments, GGSNs 30a-b may be equipped with elements that allow them to provide feedback to loadbalancer 26. In a similar vein, loadbalancer 26 may be equipped with elements that can receive and process such feedback information.

[0034] In operation of an example embodiment, loadbalancer 26 may execute loadbalancing decisions for selected GGSNs 30a-b. Inbound and outbound signaling traffic to and from SGSN 18 and GGSNs 30a-b may flow through loadbalancer 26 (in whole or in part). Loadbalancer 26 may filter the traffic using any appropriate criterion, such as source IP address, destination IP address, source port, destination port, protocol tuple, or any other suitable parameter or characteristic. Filtering may be implemented to inspect all signaling traffic to and from SGSN 18 and selected GGSNs 30a-b (that may be co-located in a GGSN farm or cluster). Loadbalancer 26 may initially create a session on the first (primary) create request and ‘sticky’ the identifier (e.g. IMSI) to the selected GGSN. A session may be identified by the client (SGSN) IP address and port, server (GGSN) IP address and port, protocol and session key, or any other suitable parameters where appropriate. For GTP version one, loadbalancer 26 may create a session per tunnel end point identifier (TEID) and, thus, a session on loadbalancer 26 may identify all PDP contexts (one primary and several secondary) with the same PDP address and access point name (APN) combination.

[0035] FIG. 2 is a simplified block diagram of a table 28 in accordance with one embodiment of the present invention. Table 28 may be provided internal to loadbalancer 26 or provided external to loadbalancer 26 and suitably coupled thereto. In one example, table 28 is an IMSI table, as is illustrated in the example of FIG. 2. However, in other embodiments, table 28 could be any storage element that is operable to include one or more identifying elements, which would assist in the routing of flows to their appropriate GGSN, as outlined herein.

[0036] Table 28 may include any suitable software, hardware, algorithms, or other suitable elements to effectuate its operations. Table 28 may also include any suitable information associated with session objects, allocations made for each GGSN 30a-b, or other networking data in accordance with particular needs. Table 28 may include a primary NSAPI column, a secondary NSAPI column, a connection counter, an IP address column, a GSN type column, a recovery information element (I.E.) column, a message sequence number, and a timer column. Table 28 may also include a row for session 5 tuple parameters, including: the client address, the client port, the server address, the server port, and a key. Table 28 may also include a column for a v-server, which corresponds to a virtual GGSN address that is used to represent a cluster of GGSNs for the network. Within the GPRS header, there is a tunnel endpoint identifier (TEID), which is represented as the key in table 28. The “client” (e.g. Y.Y.Y.Y) is the IP address of the SGSN. In addition, the “real” is the assigned GGSN of the cluster.

[0037] Note that a session object generally represents a communication tunnel or link. A suitable element may be provided internally to table 28 (or in cooperation therewith) that tracks the number of open PDP contexts for a given tunnel. In this example, the NSAPI may be provided to identify and record the number of open PDP contexts per tunnel. As loadbalancer 26 snoops or gleans information associated with secondary creates, this information may be taken into account when making a loadbalancing decision. Accordingly, a loadbalancing decision may be based on the total number of PDP contexts associated with a given GGSN 30a-b. Table 28 may monitor the number of open tunnels and the number of open PDP contexts associated with these tunnels. Table 28 may comprise session objects and NSAPI objects, which reflect a number corresponding to the secondary PDP contexts. For example, a given tunnel may have sixteen NSAPIs.

[0038] The NSAPI may also identify the application being used by end user 12 (e.g. image session, web browser session, etc.). For example, voice over IP may require a higher quality of service than web traffic. Thus, a secondary PDP with a different NSAPI number may be provided that corresponds to a higher level of service for the voice over IP. Other data may simply traverse the other PDP provided. As used herein this document, ‘PDP’ connotes the relationship between end user 12 and a corresponding network node. Each PDP may additionally include information associated with quality of service or policy routing considerations, where such is appropriate. When an IP address is needed, a PDP context may need to be established. Each PDP context may be associated with an NSAPI, and each NSAPI may map to one primary or secondary PDP context. There are generally four bits allocated for NSAPIs with values of zero-four being reserved.

[0039] Note that such columns or categories of information are not exhaustive and may certainly be added to or modified significantly. The categories of information have been provided for purposes of example only and should be construed as such. Table 28 may be used in order to time responses to messages from selected GGSNs in communication system 10. Table 28 may be suitably created or updated by loadbalancer 26 or appropriately configured or designed in accordance with particular needs.

[0040] FIG. 3A is a simplified timing diagram illustrating an example interaction between conventional elements within a loadbalancing system. FIG. 3A illustrates how a given session table 60 in a loadbalancer would look without the teachings of the present invention. In this example, session table 60 includes a row for session 5 tuple parameters, including the client address, the client port, the server address, the server port, and a key. Session table 60 also includes a column for a v-server, which is the virtual GGSN address that is used to represent a cluster of GGSNs to the network. In the GPRS header, there is the TEID, which is represented as the key in session table 60. The client in this example (e.g. Y.Y.Y.Y) is the IP address of the SGSN. In addition, the real (e.g. A.A.A.A) is the assigned GGSN of the cluster.

[0041] In previous loadbalancing scenarios, a loadbalancer would loadbalance the PDP create messages for the GGSN. Multiple creates are reflected in Steps 1, 2, and 3 such that the end user is effectively distributed over multiple GGSNs. The issue is that multiple primary PDP create messages can have different NSAPIs. Hence, the primary PDP creates could be loadbalanced to different GGSNs and the loadbalancer is somewhat oblivious to the state of the network. In this example scenario, the loadbalancing decision is based on session 5 tuple data that includes: the client address, the client port, the server address, the server port, and the session key, where the tunnel identifier=IMSI+NSAPI.

[0042] Step 1 reflects a primary create PDP request with an NSAPI equal to 7. The corresponding session 5 tuple is also provided. When the session lookup fails, a new entry is created and a fresh loadbalancing decision is made. Step 2 reflects another primary create PDP request with an NSAPI of 9. Again, the session 5 tuple is illustrated in session table 60. In this case, the session lookup fails, a new entry is again created, and a fresh loadbalancing decision is made.

[0043] Note that in Steps 1 and 2, there are two create requests coming in from the same client or subscriber. The key in these instances is composed of the IMSI and the NSAPI. Note also that the loadbalancer is (incorrectly) assigning these requests to different real server IP addresses.

[0044] Step 3 reflects yet another primary create PDP request with an NSAPI of 11. In this case, the session lookup failed and a new entry is created. A fresh loadbalancing decision is also made. Note that, at this point, the first PDP create may have already disappeared (e.g. gone through a tunnel and gone away silently). But the loadbalancer cannot recognize this condition. This results in an inefficient scenario where the end user's activity is across multiple GGSNs. At Step 4, a delete PDP request is generated having an NSAPI=7. The delete request is operable to clear NSAPI 7 (i.e. the A.A.A.A assignment) from session table 60. Such a delete request is not necessarily recognized by the loadbalancer such that it responds by freeing up resources for this particular end user. The delete request may be lost or simply unaccounted for by the loadbalancer.

[0045] FIG. 3B is a simplified timing diagram illustrating an example interaction between multiple elements that may be included within communication system 10, which does not have the shortcomings identified above in FIG. 3A. FIG. 3B includes a session table 70 that reflects a scenario, which highlights the features of the present invention. In such a case, a loadbalancing decision is based on the IMSI. Loadbalancer 26 can extract information in the end user's layer-2 connection (IMSI) from the GTP create request and use it for making loadbalancing decisions. Additionally, loadbalancer 26 can store the decision in a persistent “sticky” table, which (for example) can be indexed by IMSI, for future use. This allows for all sessions having an identical IMSI to be forwarded to the same GGSN.

[0046] Turing to the particular operations involved in such a scenario, at Step 1 a primary create PDP request is generated with an NSAPI=7. In this example, the IMSI lookup fails, whereby a new entry is created. The loadbalancing decision is made and the session is assigned to real A.A.A.A. At Step 2, another primary create PDP request is generated with an NSAPI=9. A corresponding IMSI is found at this point. Loadbalancer 26 forwards the session to the assigned real A.A.A.A and, subsequently, the reference count (refcount) is incremented.

[0047] Note that in Steps 1 and 2, there are two create requests coming in from the same client or subscriber. The key in these instances is composed of the IMSI and the NSAPI. Note also that loadbalancer 26 is assigning these requests to the same real server IP addresses.

[0048] At Step 3, another primary create PDP request is received with an NSAPI=11. In this case, the IMSI is found and the session is forwarded to the assigned real A.A.A.A. Again, the refcount is incremented. Note that between Steps 3 and 4, the NSAPI list goes from 7, 9, 11 to 9, 11. This condition illustrates a deleted message from the GGSN, which decouples that binding. Hence, Step 4 reflects the generation of a delete PDP request with an NSAPI of 7. Here, the resources are freed up for this session and the refcount is decremented. Thus, the GGSN can provide feedback to loadbalancer 26 in deleting the sticky entry from session table 70. When the GGSN finally gives up the resources for a given IMSI, it can signal this to loadbalancer 26 such that loadbalancer 26 can clear this IMSI sticky entry. This achieves a localizing of the IMSI to a specific GGSN (in this particular case, it is A.A.A.A) in the cluster.

[0049] Some of the steps illustrated in FIG. 3B may be changed or deleted where appropriate and additional steps may also be added to the flowchart. These changes may be based on specific communication architectures or particular interfacing arrangements and configurations of associated elements and do not depart from the scope or the teachings of the present invention.

[0050] Although the present invention has been described in detail with reference to IP communications, communication system 10 may be used for any tunneling protocol involving a loadbalancing environment. The use of end user 12 and IP communications have only been offered for purposes of teaching and should not be construed to limit the scope of the present invention in any way. Thus, the present invention may be used outside GPRS and mobile environments.

[0051] In addition, communication system 10 may be extended to any scenario in which end user 12 is provided with mobility (in the context of a wired or a wireless connection or coupling) and communicates with some type of access server (e.g. a network access server (NAS), foreign agents, any other access point element, etc.). End user 12 may use a dedicated connection of some form or use forms of multiple access protocols where appropriate. Access may be associated with point-to-point protocol (PPP) or alternatively with layer three protocols over an L2 layer in accordance with particular needs. Such an embodiment may include any suitable tunnel terminators and/or tunnel initiators that may be operable to communicate with loadbalancer 26.

[0052] Additionally, loadbalancer 26 may be implemented effectively for network handoffs or handovers. Such a scenario may occur when end user 12 roams from one location to another. NSAPIs or IMSIs may be spread over multiple tunnels. Using PDP tracking provided by loadbalancer 26, the handoff may be accommodated between PDP contexts. This may be executed by creating two session objects that share an NSAPI table. Each NSAPI may belong to a different session.

[0053] Moreover, although communication system 10 has been illustrated with reference to particular elements facilitating the loadbalancing process, these elements may be replaced by any suitable architecture or configuration that achieves the intended functionality of communication system 10. Loadbalancer 26 executes loadbalancing decision based on IMSI stickying and, therefore, may receive information pertaining to such a decision via any suitable element or object. Additionally, loadbalancer 26 may execute loadbalancing decisions for any appropriate corresponding element using information provided, which is associated with an open number of PDP contexts for a given network node.

[0054] Numerous other changes, substitutions, variations, alterations, and modifications may be ascertained by those skilled in the art and it is intended that the present invention encompass all such changes, substitutions, variations, alterations, and modifications as falling within the spirit and scope of the appended claims. Moreover, the present invention is not intended to be limited in any way by any statement in the specification that is not otherwise reflected in the appended claims.