# US 2021/0176304 A1 · Systems and methods for persistence across applications using a content switching server

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2021/0176304 A1
- Document ID: US20210176304A1
- Status: Published application
- Kind: A1
- Application number: 16/705,900
- Filed: 2019-12-06
- Published: 2021-06-10
- Earliest claimed: 2019-12-06
- Assignees: Citrix Systems, Inc.
- Applicants: Citrix Systems, Inc.
- Inventors: Manikam Muthiah; Chiradeep Vittal; Raghav SN; Sanchita Ghai; Vinay Shivananda
- Web page: https://patentgrep.com/patent/US20210176304A1

## CPC

- H04L 67/1004: Server selection for load balancing
- H04L 67/02: based on web technology, e.g. hypertext transfer protocol [HTTP]
- H04L 67/1014: based on the content of a request
- H04L 67/1021: based on client or server locations
- H04L 67/1023: based on a hash applied to IP addresses or costs
- H04L 67/1027: Persistence of sessions during load balancing
- H04L 67/14: Session management (for real-time applications in data packet communications networks H04L65/1066)
- H04L 67/141: Setup of application sessions (admission control or resource allocation in data switching networks H04L47/70)
- H04L 67/145: avoiding end of session, e.g. keep-alive, heartbeats, resumption message or wake-up for inactive or interrupted session
- H04L 67/146: Markers for unambiguous identification of a particular session, e.g. session cookie or URL-encoding
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

Disclosed herein includes a system, a method, and a device for providing persistence across applications using a content switching server. A device can receive a first request from a client for a version of an application having different versions provided by one or more servers. The device can provide access to each version of the application via different load balancing virtual servers. A content switching virtual server of the device can select a load balancing virtual server to handle the first request for the version of the application. The content switching virtual server can generate a session identifier for a session between the client and the version of the application to persist the session with the selected load balancing virtual server for subsequent requests from the client for the version of the application.

## Claims

### Claim 1

A method comprising:
receiving, by a device intermediary to a plurality of clients and a plurality of applications, a first request from a first client of the plurality of clients for a first version of an application of the plurality of applications having different versions provided by one or more servers, the device providing access to each version of the application via a different load balancing virtual server of a plurality of load balancing virtual servers of the device;
selecting, by a content switching virtual server of the device, a load balancing virtual server from the plurality of load balancing virtual servers to handle the first request for the first version of the application;
generating, by the content switching virtual server, a session identifier for a session between the first client and the first version of the application to persist the session with the selected load balancing virtual server for subsequent requests from the first client for the first version of the application;
providing, by the content switching virtual server to the first client, the session identifier for the session between the first client and the first version of the application; and
forwarding, by the content switch virtual server, a second request from the first client to access the first version of the application to the selected load balancing virtual server responsive to identifying the session identifier associated with the second request.

### Claim 2 (depends on 1)

The method of claim 1, further comprising:
receiving, by content switching virtual server, a third request from a second client for at least one version of the application;
selecting, by the content switching virtual server, a second load balancing virtual server from the plurality of load balancing virtual servers to handle the third request, the second load balancing virtual server providing access to a second version of the application; and
routing, by the content switching virtual server using a second session identifier, the third request to the selected second load balancing virtual server to provide access to the second version of the application for the second client.

### Claim 3 (depends on 1)

The method of claim 1, wherein the session identifier includes a data unit included with the request and a value associated with the selected load balancing server; and wherein the data unit includes at least one of a source internet protocol (IP) address, a HyperText Transfer Protocol (HTTP) cookie or a secure sockets layer (SSL) session identifier.

### Claim 4 (depends on 1)

The method of claim 1, further comprising:
determining, by the content switching virtual server, if the session identifier is to be created for the first client through a lookup to the storage of the device using a data unit included with the request; and
generating, by the content switching virtual server, responsive to the lookup, the session identifier for the session between the first client and the first version of the application.

### Claim 5 (depends on 1)

The method of claim 1, comprising:
identifying, by the content switching virtual server, an internet protocol (IP) address associated with the first client; and
generating, by the content switching virtual server, the session identifier for the session between the first client and the first version of the application with the identifier corresponding to the IP address associated with the first client.

### Claim 6 (depends on 1)

The method of claim 1, comprising:
identifying, by the content switching virtual server, a data unit for a secure sockets layer (SSL) session between the first client and the first version of the application; and
generating, by the content switching virtual server, the session identifier for the session between the first client and the first version of the application with the session identifier corresponding to the data unit for the SSL session between the first client and the first version of the application.

### Claim 7 (depends on 1)

The method of claim 1, comprising:
inserting, by the content switching virtual server, a cookie into a header of a response to the first request from the first client, the cookie identifying the selected load balancing virtual server.

### Claim 8 (depends on 7)

The method of claim 7, comprising:
receiving, by the content switching virtual server, a third request from the first client for the first version of the application, the third request including the cookie; and
determining, by the content switching virtual server, the session identifier associated with the first client using the cookie, the session identifier corresponding to the session between the first client and the first version of the application.

### Claim 9 (depends on 8)

The method of claim 8, comprising:
routing, by the content switching virtual server using the session identifier, the third request to the selected load balancing virtual server to provide access to the first version of the application.

### Claim 10

A method comprising:
establishing, by a device intermediary to a plurality of clients and an application, a different load balancing virtual server of a plurality of load balancing virtual servers of the device for accessing each version of a plurality of versions of the application provided by one or more servers;
identifying, by a content switching virtual server of the device, a first identifier of a first request received by a client of the plurality of clients to access a first version of the plurality of versions of the application;
determining, by the content switching virtual server using the first identifier, a first load balancing virtual server of the plurality of load balancing virtual servers was selected for the first client to access the first version of the application responsive to a previous request between the first client and the first version of the application; and
routing, by the content switching virtual server, the first request to the first load balancing virtual server to provide the first client access to the first version of the application.

### Claim 11 (depends on 10)

The method of claim 10, further comprising:
receiving, by content switching virtual server, a second request from a second client for the version of the application; and
identifying, by the content switching virtual server, a second identifier included with the second request.

### Claim 12 (depends on 11)

The method of claim 11, further comprising:
performing, by the content switching virtual server, using the second identifier included with the second request, a lookup to a storage of the device for a session identifier associated with the second client; and
determining, by the content switching virtual server responsive to the lookup, that a session identifier is to be generated for the second client.

### Claim 13 (depends on 11)

The method of claim 11, further comprising:
selecting, by the content switching virtual server, a second load balancing virtual server to provide a second version of the application to the second client, the second version different from the first version.

### Claim 14 (depends on 13)

The method of claim 13, further comprising:
generating, by the content switching virtual server, a session identifier for a session between the second client and the second version of the application, the session identifier comprising the first identifier included with the second request and a value associated with the second load balancing server; and
routing, by the server, the second request to the second load balancing server to provide access to the second version of the application for the second client.

### Claim 15

A system comprising:
a device intermediary to a plurality of clients and a plurality of applications, the device comprising one or more processors coupled to memory; and
the one or more processors configured to:
receive a first request from a first client of the plurality of clients for a first version of an application of the plurality of applications having different versions provided by one or more servers, the device providing access to each version of the application via a different load balancing virtual server of a plurality of load balancing virtual servers of the device;
select, via a content switching virtual server of the device, a load balancing virtual server from the plurality of load balancing virtual servers to handle the first request for the first version of the application;
generate a session identifier for a session between the first client and the first version of the application to persist the session with the selected load balancing virtual server for subsequent requests from the first client for the first version of the application;
provide, to the first client, the session identifier for the session between the first client and the first version of the application; and
forward a second request from the first client to access the first version of the application to the selected load balancing virtual server responsive to identifying the session identifier associated with the second request.

### Claim 16 (depends on 15)

The system of claim 15, wherein the one or more processors are further configured to:
receive a third request from a second client for at least one version of the application;
select a second load balancing virtual server from the plurality of load balancing virtual servers to handle the third request, the second load balancing virtual server providing access to a second version of the application; and
route, using a second session identifier, the third request to the selected second load balancing virtual server to provide access to the second version of the application for the second client.

### Claim 17 (depends on 15)

The system of claim 15, wherein the session identifier includes a data unit included with the request and a value associated with the selected load balancing server; and wherein the data unit includes at least one of a source internet protocol (IP) address, a HyperText Transfer Protocol (HTTP) cookie or a secure sockets layer (SSL) session identifier.

### Claim 18 (depends on 15)

The system of claim 15, wherein the one or more processors are further configured to:
determine if the session identifier is to be created for the first client through a lookup to the storage of the device using a data unit included with the request; and
generate, responsive to the lookup, the session identifier for the session between the first client and the first version of the application.

### Claim 19 (depends on 15)

The system of claim 15, wherein the one or more processors are further configured to:
identify an internet protocol (IP) address associated with the first client; and
generate the session identifier for the session between the first client and the first version of the application with the identifier corresponding to the IP address associated with the first client.

### Claim 20 (depends on 15)

The system of claim 15, wherein the one or more processors are further configured to:
receive a third request from the first client for the first version of the application, the third request including the cookie;
determine the session identifier associated with the first client using the cookie, the session identifier corresponding to the session between the first client and the first version of the application; and
route, using the session identifier, the third request to the selected load balancing virtual server to provide access to the first version of the application.
