VPN Endpoint Pool Manager for Dynamic Traffic Distribution

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing VPN systems face challenges in scaling and efficiency due to reliance on single VPN endpoints, which can lead to queuing of data packets and reduced performance under high traffic conditions, limiting network resiliency and performance.

Innovation Solution

Implementing a VPN endpoint pool with multiple endpoints associated with a shared Endpoint Pool Address, managed by a VPN endpoint manager that dynamically selects and transfers VPN sessions to optimize traffic distribution and processing, using algorithms for load balancing and traffic management.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If a single VPN endpoint is used, then device complexity is reduced, but productivity deteriorates due to packet queuing and reduced performance under high traffic conditions

Engineering Contradiction:

ImproveVPN traffic processing throughputVSAvoidVPN endpoint pool architecture

Core Design Contradiction:

ProductivityVSDevice complexity

Solution Approach 1:

The system segments the VPN endpoint functionality into multiple independent endpoints (first VPN endpoint, second VPN endpoint, etc.) that share a common address. Each endpoint can independently process VPN packets, eliminating the single-point bottleneck and enabling parallel processing of traffic streams, thereby increasing overall productivity without requiring clients to be aware of the segmentation.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

Multiple VPN endpoints are merged under a single shared Endpoint Pool Address, creating a unified entry point for clients while maintaining distributed processing capabilities. The VPN endpoint manager combines the coordination function of routing packets to appropriate endpoints with the endpoints' individual processing capabilities, achieving both high throughput and simplified client interaction.

Inventive Principle:

Principle #5Merging (Combining)

2Reliability

If multiple VPN endpoints are implemented, then scalability and resiliency are improved, but device complexity increases due to session management and traffic distribution requirements

Engineering Contradiction:

Improvenetwork resiliencyVSAvoidsession management complexity

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The VPN endpoint manager serves as an intermediary between clients and multiple VPN endpoints. It receives VPN packets from clients, determines the appropriate endpoint based on session information, and forwards packets to the selected endpoint. This intermediary layer abstracts the complexity of multi-endpoint management from clients while enabling load distribution and improved reliability through redundant endpoints.

Inventive Principle:

Principle #24Intermediary (Mediator)

Solution Approach 2:

Instead of each client being assigned a dedicated VPN endpoint (traditional approach), the system inverts the model by having multiple endpoints share a single address. Clients connect to the shared address without needing to know about individual endpoints, while the system dynamically routes traffic to available endpoints, improving both reliability and simplifying client configuration.

Inventive Principle:

Principle #13The other way round (Inversion)

3Productivity

If traffic is concentrated on a single VPN endpoint, then device complexity is minimized, but productivity deteriorates due to queuing under high load conditions

Engineering Contradiction:

Improvetraffic processing efficiencyVSAvoidtraffic distribution mechanism

Core Design Contradiction:

ProductivityVSDevice complexity

Solution Approach 1:

The system implements dynamic traffic distribution where the VPN endpoint manager can adaptively route packets to different endpoints based on current load conditions, session requirements, and available capacity. This dynamic allocation allows the system to optimize traffic processing efficiency in real-time, preventing queuing bottlenecks while maintaining relatively simple client-side configurations.

Inventive Principle:

Principle #15Dynamics

Data Source

PatentUS10484279B2Executing multiple virtual private network (VPN) endpoints associated with an endpoint pool address

Publication Date: 2019.11.19 ORACLE INT CORP

AI summary

Techniques for executing multiple Virtual Private Network (VPN) endpoints associated with an Endpoint Pool Address are disclosed. A VPN endpoint manager determines traffic attributes of traffic addressed to the Endpoint Pool Address. The VPN endpoint manager selects a quantity of VPN endpoints to be executed for processing the traffic based on the traffic attributes. The VPN endpoint manager causes execution of a plurality of VPN endpoints corresponding to the selected quantity. The VPN endpoint manager selects one VPN endpoint, from the VPN endpoint pool, to process each data packet addressed to the Endpoint Pool Address. The VPN endpoint manager may select different VPN endpoints to process data packets of different VPN sessions. The VPN endpoint manager may transfer a VPN session from one VPN endpoint to another VPN endpoint. The VPN endpoints in the VPN endpoint pool operate concurrently to process data packets addressed to the Endpoint Pool Address.