AAA Server Load Balancer for Scalable Authentication Clusters

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing AAA protocols, such as RADIUS and Diameter, face challenges in scalability and reliability, particularly during peak-load periods or device failures, necessitating a solution for efficient and continuous operation of authentication, authorization, and accounting services.

Innovation Solution

A load balancing method and system that distributes AAA requests across a cluster of servers using a load balancer, which manages connections, monitors server health, and applies load balancing algorithms to ensure efficient request distribution and connection redundancy.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If a single AAA server is used to handle authentication requests, then the system structure is simple, but the system cannot scale to handle large numbers of subscribers during peak-load periods

Engineering Contradiction:
ImproveAAA service capacityVSAvoidsystem structure
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent divides the AAA service into multiple independent server instances organized in a cluster. Each server can handle authentication requests independently, allowing the system to scale horizontally by adding more servers to handle increased subscriber loads during peak periods.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces a load balancer as an intermediary component that sits between clients and the AAA server cluster. The load balancer receives client requests, applies load balancing algorithms to select appropriate servers, and forwards requests to the selected server, thereby managing the complexity of distributed service delivery.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If AAA servers are deployed in a cluster to improve scalability, then the system can handle more subscribers, but connection management becomes more complex

Engineering Contradiction:
ImprovescalabilityVSAvoidconnection management
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The load balancer acts as an intermediary that abstracts away the complexity of cluster management from clients. It maintains connection state, manages server selection, and handles failover logic, allowing clients to interact with a single logical endpoint while the backend cluster handles the complexity of distributed connection management.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system implements health monitoring and load status tracking where the load balancer continuously receives feedback about server availability and performance. This feedback mechanism allows the load balancer to dynamically adjust request routing, avoid failed servers, and maintain optimal connection management across the cluster.

Inventive Principle:
Principle #23Feedback

3Reliability

If load balancing is implemented across multiple AAA servers, then service availability improves during failures, but the system complexity increases

Engineering Contradiction:
Improveservice availabilityVSAvoidsystem architecture
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system implements proactive health monitoring and failover mechanisms where the load balancer continuously monitors server health and has pre-configured fallback options. When a server fails, the load balancer can immediately redirect traffic to healthy servers without requiring complex real-time decision-making, thereby maintaining service availability through pre-planned redundancy.

Inventive Principle:
Principle #11Beforehand cushioning (Prior cushioning)

Solution Approach 2:

The load balancer serves as a protective intermediary that shields clients from the complexity of server failures and recovery. It absorbs the complexity of failure detection, server selection, and connection management, providing a simple, reliable interface to clients while handling the architectural complexity of distributed reliability in the background.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS10673938B2Method and system for load balancing over a cluster of authentication, authorization and accounting (AAA) servers
Publication Date: 2020.06.02 RADWARE LTD
  • US10673938B2 patent drawing
  • US10673938B2 patent drawing
  • US10673938B2 patent drawing

AI summary

A method and system for load balancing over a cluster of authentication, authorization and accounting (AAA) servers. The method performs a distribution of AAA requests among AAA servers having an active AAA connection with an AAA client. The method includes establishing TCP connections with a plurality of AAA servers, using a TCP connection request received from at least one AAA client; opening AAA connections with a plurality of AAA servers, using an AAA connection request received from at least one AAA client, and distributing AAA requests to AAA servers with an active AAA connection according to a predefined load balancing algorithm. The method is further capable of multiplexing outbound messages and requests received from a plurality of AAA servers. The AAA protocol supported by the method includes, but is not limited to, a Diameter protocol, a lightweight directory access protocol (LDAP), and the likes.