Cloud Server Scaling via Load Balancer Rekey Routing

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Cloud-based systems face challenges in scaling down network resources, such as security gateway instances, during non-peak traffic periods without disrupting secure connections, as existing methods require disconnecting from connected devices or rely on centralized state backups, leading to overhead and inefficiency.

Innovation Solution

Implementing a monitoring module that detects network metrics and initiates a rekey routine to transfer secure connections to other available servers, allowing minimally loaded instances to be scaled down without impacting connectivity, using a load balancer to reroute tunnel sessions and establish new secure connections.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If secure connections are maintained on cloud-based servers, then connection reliability is improved, but server scalability deteriorates

Engineering Contradiction:

Improveconnection reliabilityVSAvoidserver scalability

Core Design Contradiction:

ReliabilityVSAdaptability or versatility

Solution Approach 1:

The system performs preliminary actions by initiating rekey requests and establishing new secure connections before terminating existing ones. When a server needs to be scaled down, the load balancer proactively sets up alternative secure connections on other servers and completes the key exchange process before disconnecting devices from the original server, ensuring seamless transition without disrupting connectivity.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The load balancer acts as an intermediary between devices and cloud-based servers. It manages the complex process of transferring secure connections by intercepting rekey requests, routing them to appropriate servers, and coordinating the transition. This intermediary role abstracts the complexity of connection management from both devices and servers, enabling scalable architecture while maintaining connection reliability.

Inventive Principle:

Principle #24Intermediary (Mediator)

2Adaptability or versatility

If centralized state backup is implemented for connection management, then connection transfer capability is improved, but system overhead increases

Engineering Contradiction:

Improveconnection transfer capabilityVSAvoidsystem overhead

Core Design Contradiction:

Adaptability or versatilityVSLoss of energy

Solution Approach 1:

The patent extracts the connection state management function from a centralized backup system and distributes it to individual servers. Each server maintains its own connection state locally, eliminating the need for centralized state backup and reduction. This extraction reduces system overhead while preserving the ability to transfer connections through the load balancer's routing capabilities.

Inventive Principle:

Principle #2Taking out (Extraction)

Solution Approach 2:

Servers perform self-service by maintaining their own connection states and handling their own secure connections independently. Rather than relying on centralized state backup, each server autonomously manages its connections, and the load balancer coordinates transfers by routing rekey requests appropriately. This self-service approach minimizes overhead while maintaining connection transfer capability.

Inventive Principle:

Principle #25Self-service

3Productivity

If security gateway instances are scaled down during non-peak periods, then resource efficiency is improved, but connection continuity may deteriorate

Engineering Contradiction:

Improveresource efficiencyVSAvoidconnection continuity

Core Design Contradiction:

ProductivityVSReliability

Solution Approach 1:

Before scaling down security gateway instances during non-peak periods, the system performs preliminary actions by initiating rekey requests to establish new connections on remaining servers. The load balancer proactively routes these rekey requests and ensures new secure connections are fully established before terminating connections to be scaled-down instances, maintaining connection continuity throughout the scaling process.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The system dynamically adjusts the number of active security gateway instances based on real-time traffic conditions. During non-peak periods, instances can be scaled down, but the load balancer dynamically manages the transition by redistributing connections to remaining instances through rekey requests. This dynamic approach allows resource efficiency to improve while connection continuity is maintained through adaptive connection management.

Inventive Principle:

Principle #15Dynamics

Data Source

PatentUS10904322B2Systems and methods for scaling down cloud-based servers handling secure connections

Publication Date: 2021.01.26 CISCO TECHNOLOGY INC

AI summary

The disclosed technology relates to systems and methods for automatically scaling down network resources, such as servers or gateway instances, based on predetermined thresholds. A system is configured to detect a reduction in one or more network metrics related to a first server, and instruct the first server to issue a rekey request to a plurality of devices connected to the first server. The system is further configured to instruct a load balancer to route to at least one other server responses from the plurality of devices to the rekey request, and determine a number of connections remaining between the first server and the plurality of devices. The system may be further configured to instruct the load balancer to terminate the first server based on the detected number of connections remaining between the first server and the plurality of devices.