GSLB Virtual Server SSL VPN User Metrics Load Balancing

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing load balancing systems do not effectively manage network traffic across multiple sites based on the number of SSL VPN users, leading to inefficient resource allocation and potential congestion.

Innovation Solution

A global server load balancing (GSLB) system that utilizes SSL VPN user metrics to determine the optimal distribution of network traffic across sites by receiving requests from load balancing virtual servers and forwarding them based on the number of current SSL VPN users, employing methods like least connection, least response time, and round trip time.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If traditional load balancing systems are used without SSL VPN user metrics, then the system structure remains simple, but resource allocation becomes inefficient and congestion occurs

Engineering Contradiction:
Improveresource allocation efficiencyVSAvoidsystem complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The GSLB system implements feedback by continuously monitoring SSL VPN user metrics from multiple sites and using this information to dynamically adjust load balancing decisions. The system collects real-time data about the number of SSL VPN users at each site and uses this feedback to redirect traffic away from congested sites, thereby improving resource allocation efficiency without significantly increasing system complexity.

Inventive Principle:
Principle #23Feedback

2Productivity

If load balancing based on SSL VPN user metrics is implemented, then resource allocation efficiency improves, but the system complexity increases due to additional monitoring and control mechanisms

Engineering Contradiction:
Improveload balancing efficiencyVSAvoidmonitoring system complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The load balancing virtual servers at each site autonomously monitor their own SSL VPN user metrics and report this information to the GSLB system. Each site independently tracks its own congestion levels and makes self-service decisions about traffic distribution, eliminating the need for centralized complex monitoring infrastructure while still achieving efficient load balancing across the enterprise network.

Inventive Principle:
Principle #25Self-service

3Object-affected harmful factors

If GSLB directs traffic based on real-time SSL VPN user data, then network congestion is reduced, but the difficulty of detecting and measuring user metrics increases

Engineering Contradiction:
Improvenetwork congestionVSAvoidSSL VPN user metric measurement
Core Design Contradiction:
Object-affected harmful factorsVSDifficulty of detecting and measuring

Solution Approach 1:

The patent introduces load balancing virtual servers as intermediary components that simplify the measurement of SSL VPN user metrics. These virtual servers act as mediators between the complex SSL VPN infrastructure and the GSLB decision-making process, providing standardized, easy-to-collect metrics about the number of active SSL VPN users at each site without requiring direct complex measurement of individual user connections.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS9781196B2Systems and methods for GSLB based on SSL VPN users
Publication Date: 2017.10.03 CITRIX SYSTEMS INC
  • US9781196B2 patent drawing
  • US9781196B2 patent drawing
  • US9781196B2 patent drawing

AI summary

The present invention provides a system and a method for global server load balancing of a plurality of sites based on a number of Secure Socket Layer Virtual Private Network (SSL VPN) users. The SSL VPN users may access servers at each of the plurality of sites. A global server load balancing virtual server (GSLB) may receive a request to access a server. The GSLB virtual server may load balance a plurality of sites wherein each of the plurality of sites may further comprising a load balancing virtual server load balancing users accessing the server accessing servers via an SSL VPN session. GSLB may receive from a first load balancing virtual server at a first site, a first number of current SSL VPN users accessing servers from the first site via SSL VPN sessions. The GSLB may also receive from a second load balancing virtual server at a second site, a second number of current SSL VPN users of the users accessing servers from the second site via SSL VPN sessions. GSLB may determine to forward the request to one of the first load balancing virtual server of the first site or the second load balancing virtual server of the second site by load balancing SSL VPN users across the plurality of sites based on the first number of current SSL VPN users and the second number of current SSL VPN users.