H04L67/1027

METHOD AND SYSTEM FOR PERSISTING SESSION DATA

A method for facilitating session data persistence and management is disclosed. The method includes receiving a first indication from an application, the first indication relating to an initiation of a first session; compiling session data from the application, the session data relating to a state of the application; receiving a termination indication from the application, the termination indication relating to a termination of the first session; persisting, in a session cache, the session data based on the termination indication; receiving a second indication from the application, the second indication relating to an initiation of a second session; identifying the corresponding session data in the session cache by using the second indication; and automatically injecting the identified session data into the application.

Enabling planned upgrade/downgrade of network devices without impacting network sessions

Exemplary embodiments for enabling planned network changes such as an upgrade or downgrade of a network device are disclosed. The systems and methods provide for planned upgrades and downgrades for network devices without impacting existing network sessions, by utilizing two network devices simultaneously, and creating a redirect network session for a predetermined period of time. In so doing, all network traffic may be gradually transferred to the second network device, until the sessions processed by the first network device time out. The first network device can then be taken offline for upgrade or downgrade, without any disruption to the network service or loss of network traffic.

METHOD FOR DYNAMIC RETENTION OF HTTP SESSION INFORMATION AND WEB APPLICATION SERVER AND WEB SERVER USING THE SAME
20170310760 · 2017-10-26 ·

A web server is provided. The web server includes a communication part for receiving an HTTP request from an entity connected by network and communicating with at least one WAS; and a processor for performing at least one of (i) a process of transmitting the HTTP request received from the entity to a specific WAS selected among the at least one WAS and then receiving information on an HTTP session corresponding to the specific WAS from the specific WAS when receiving an HTTP response from the specific WAS in response to the HTTP request, thereby retaining the information on the HTTP session and (ii) a process of transmitting a PING signal and then receiving the information on the HTTP session corresponding to the specific WAS from the specific WAS when receiving a PONG signal in response to the PING signal, thereby retaining the information on the HTTP session.

SYSTEM AND METHOD FOR SESSION RESTORATION AFTER NODE FAILURE
20170310763 · 2017-10-26 ·

A system and method for restoring a session state of a client device has been provided. The system comprises a memory with instructions executable by a processor to receive a first request from the client device, where the first request is a first type of request and is associated with a new session of the client device; process the first request without persisting a session state of the new session in the database node; receive a second request from the client device, where the second request is a first instance of a second type of request and is associated with the new session; and in response to determining to restore a persisted session state, restore the persisted session state for the client device from the database node, and assign the persisted session state as the session state of the new session of the client device.

Method and apparatus for load balancing in network based telephony application

Techniques are disclosed for load balancing in networks such as those networks handling telephony applications. By way of example, such techniques direct requests associated with calls to servers in a system comprised of a network routing calls between a plurality of callers and at least one receiver wherein a load balancer sends requests associated with calls to a plurality of servers as follows. A request associated with a call, a caller, or a receiver is received, depending on the particular load balancing technique. A server is selected to receive the request. A subsequent request is received. A determination is made whether or not the subsequent request is associated with the call, the caller, or the receiver, depending on the particular load balancing technique. The subsequent request is sent to the server based on determining that the subsequent request is associated with the call, the caller, or the receiver, again depending on the particular load balancing technique.

Load balancing among a cluster of firewall security devices

A method for balancing load among firewall security devices (FSDs) is provided. According to one embodiment, a switching device performs adaptive load balancing among cluster units of an HA cluster of firewall security devices. A load balancing (LB) function implemented by the switching device is configured based on information received from a network administrator. A LB table is maintained that forms associations between hash values output by the LB function and corresponding ports of the switching device to which the cluster units are coupled. Network traffic received by the switching device is directed to appropriate cluster units based on the LB function and the LB table. A traffic load on each of the cluster units is monitored. Responsive to a deviation from a predefined ideal traffic distribution, an attempt is made to improve performance of the HA cluster by dynamically adjusting the LB balancing table to address the deviation.

Load balancing and session persistence in packet networks
09826068 · 2017-11-21 · ·

A node may generate a data packet comprising an Internet Protocol (IP) header and a destination options extension header (DOEH). The DOEH may comprise one or more data fields and an IP payload. The node may send the data packet to another node in a data network.

Load balancing requests such that target resources serve a single client

Various embodiments of methods and apparatus for load balancing requests such that target resources serve a single client are described. In at least some embodiments, a single resource, such as a compute instance, is assigned to only one client, and that single resource is used for all subsequent connections and communications from that client. Some embodiments comprise a resource selection system which provides identifying information of an available resource, in order for a connection to be established between the client and the resource. The resource selection system then removes that identifying information from its memory. In some of these embodiments, a routing layer interfaces with the resource selection system to establish the connection between the client and the available resource. When a client is assigned to a resource, other clients may be prevented from establishing connections with the resource.

Load balancing requests such that target resources serve a single client

Various embodiments of methods and apparatus for load balancing requests such that target resources serve a single client are described. In at least some embodiments, a single resource, such as a compute instance, is assigned to only one client, and that single resource is used for all subsequent connections and communications from that client. Some embodiments comprise a resource selection system which provides identifying information of an available resource, in order for a connection to be established between the client and the resource. The resource selection system then removes that identifying information from its memory. In some of these embodiments, a routing layer interfaces with the resource selection system to establish the connection between the client and the available resource. When a client is assigned to a resource, other clients may be prevented from establishing connections with the resource.

Load-Balanced, Persistent Connection Techniques

Techniques for creating a persistent connection between client devices and one or more remote computing resources, which may form a portion of a network-accessible computing platform. This connection may be considered “permanent” or “nearly permanent” to allow the client device to both send data to and receive data from the remote resources at nearly any time. In addition, both the client device and the remote resources may establish virtual channels over this single connection. If no data is exchanged between the client device and the remote computing resources for a threshold amount of time, then the connection may be severed and the client device may attempt to establish a new connection with the remote computing resources.