Self-Load Balancing Access Gateway Using HTTP Redirection

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing systems face challenges in load balancing access gateways, leading to user delays when accessing resources, as they rely on costly dedicated devices and may experience bottlenecks if these devices become unavailable.

Innovation Solution

A self-load balancing system where a master access gateway receives load metrics from multiple access gateways and determines whether to redirect client requests to the receiving gateway or another gateway based on load metrics, using HyperText Transfer Protocol (HTTP) redirection responses and flags to manage session redirection.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If a dedicated load balancing device is introduced, then load distribution and user access efficiency are improved, but system cost and device complexity increase

Engineering Contradiction:
Improveuser access efficiencyVSAvoidsystem cost
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The access gateways themselves perform load balancing decisions by evaluating their own load metrics and making redirection determinations, eliminating the need for an external dedicated load balancing device. Each gateway monitors its own capacity and autonomously participates in the load distribution process.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The access gateways are designed to perform multiple functions: they simultaneously handle client requests, monitor their own load metrics, make load balancing decisions, and redirect clients as needed. This multi-functionality replaces the specialized dedicated load balancing device with the existing gateway infrastructure.

Inventive Principle:
Principle #6Universality (Multi-functionality)

2Productivity

If a dedicated load balancing device is introduced, then load distribution is improved, but system reliability deteriorates due to potential single point of failure

Engineering Contradiction:
Improveload distributionVSAvoidsystem availability
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The load balancing functionality is segmented and distributed across multiple independent access gateways rather than centralized in a single dedicated device. Each gateway independently evaluates its own load and makes local redirection decisions, eliminating the single point of failure associated with a centralized load balancer.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The gateways exchange load metric information with each other to enable informed load balancing decisions. This peer-to-peer information sharing mechanism replaces the intermediary role of a dedicated load balancing device while maintaining the benefits of load distribution.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Measurement precision

If load metrics are collected and evaluated in real-time, then request redirection accuracy is improved, but processing overhead and system complexity increase

Engineering Contradiction:
Improveload assessment accuracyVSAvoidsystem complexity
Core Design Contradiction:
Measurement precisionVSDevice complexity

Solution Approach 1:

The system collects and evaluates only the essential load metrics needed for redirection decisions (such as current request queue length and processing capacity) rather than comprehensive system performance data. This partial monitoring approach provides sufficient accuracy for load balancing while minimizing processing overhead and complexity.

Inventive Principle:
Principle #16Partial or excessive action

Data Source

PatentUS9037712B2Systems and methods for self-loading balancing access gateways
Publication Date: 2015.05.19 CITRIX SYSTEMS INC
  • US9037712B2 patent drawing
  • US9037712B2 patent drawing
  • US9037712B2 patent drawing

AI summary

The present invention is directed towards systems and methods for self-load balancing access gateways. The systems and methods include a master access gateway that receives load metrics and capabilities from a plurality of access gateways. The master access gateway also receives requests to determine if a request to start a new session is to be redirected to an access gateways. The master access gateways uses the load metrics and capabilities to select an access gateway to service the request.