Virtual Load Balancer Multi-Carrier Traffic Forwarding

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In cloud platform load balancing, the number of virtual load balancers required is excessively high due to a positive correlation with the number of carriers, leading to low resource utilization.

Innovation Solution

A method and system where a virtual load balancer receives a pending response data packet from a Linux virtual server, forwards it to a real server through a rear terminal sub interface, and then transmits the response back to the Linux virtual server through the original front terminal sub interface, reducing the need for multiple virtual load balancers and improving resource utilization.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If multiple VPN routing forwarding tables are deployed with separate virtual load balancers for each carrier, then carrier isolation and load balancing services are achieved, but the number of virtual load balancers increases excessively and resource utilization decreases

Engineering Contradiction:
Improvecarrier isolationVSAvoidnumber of virtual load balancers
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

A single virtual load balancer is designed to handle multiple carriers' traffic simultaneously by implementing multi-carrier access functionality. The VLB uses VPN routing forwarding tables to differentiate and route traffic from different carriers, allowing one VLB instance to serve multiple carriers instead of requiring separate VLB instances for each carrier.

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

Solution Approach 2:

Multiple virtual load balancer functions are merged into a single VLB instance. The patent combines the capabilities of handling multiple carriers' load balancing into one unified VLB that uses routing tables to distinguish between different carriers' traffic, thereby reducing the total number of VLB instances from m*n to m.

Inventive Principle:
Principle #5Merging (Combining)

2Productivity

If one virtual load balancer serves multiple carriers, then resource utilization improves, but the complexity of routing management increases

Engineering Contradiction:
Improveresource utilizationVSAvoidrouting management complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The routing management is segmented through the use of VPN routing forwarding tables that are divided into multiple routing dimensions. Each routing table contains routes for different carriers, allowing the system to manage complex multi-carrier routing in an organized, tabular format that simplifies lookup and management compared to a monolithic routing structure.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS10693785B2Method and system for forwarding data, virtual load balancer, and readable storage medium
Publication Date: 2020.06.23 PING AN TECH (SHENZHEN) CO LTD
  • US10693785B2 patent drawing
  • US10693785B2 patent drawing
  • US10693785B2 patent drawing

AI summary

Disclosed are a method and a system for forwarding data, as well as a virtual load balancer and a readable storage medium. The method for forwarding data includes: sending the pending response data packet to the real server RS through a rear terminal sub interface, when the virtual load balancer VLB receives a pending response data packet sent by the Linux virtual server LVS from a front terminal sub interface, wherein the forward network port of the VLB corresponds to at least one front terminal sub interface, and a front terminal sub interface corresponds to a carrier's data interface; and the RS receives and responds to the pending response data packet, getting a response data packet and sending the response data packet to the VLB from the rear terminal sub interface; and the VLB receives the response data packet.