MPTCP Load Balancing with Flow Mapping for Consistent Server Routing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing network load balancing methods fail to ensure that Multi-Path Transmission Control Protocol (MPTCP) messages from the same host are sent to the same target server, leading to abnormal access in communication systems.
Innovation Solution
A network load balancing method that determines a target flow direction and generates a message conversion rule to direct both subflows and main flows to the same target server using verification information and device information, reducing the need for load balancing device involvement.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If a load balancing device determines target servers for MPTCP subflows independently, then load distribution across servers is improved, but messages from the same host may be directed to different target servers causing access abnormalities
Solution Approach 1:
The load balancing device performs preliminary actions by determining the target server for the main flow before subflows are established. The device stores the mapping relationship between the main flow's verification information and its target server in advance. When subflows arrive, the device queries this pre-stored mapping to ensure they are directed to the same target server as the main flow, thereby maintaining access normality while still achieving load distribution across different server groups.
Solution Approach 2:
The invention segments the MPTCP connection handling into two independent parts: main flow handling and subflow handling. The main flow is processed through the load balancing device which determines the target server and stores the mapping. Subflows are then handled by querying this stored mapping. This segmentation allows the load balancing device to maintain control over server selection while enabling efficient subflow routing without re-evaluating each subflow independently.
2Reliability
If the load balancing device processes all MPTCP messages (main flows and subflows), then comprehensive control is achieved, but the device load increases significantly
Solution Approach 1:
The invention extracts the subflow processing function from the load balancing device. Instead of the load balancing device processing all MPTCP messages, it only handles main flows to establish target server mappings. Subflows are routed based on queries to pre-stored mapping information, extracting the intensive processing burden from the load balancing device while maintaining comprehensive control over message routing consistency.
Solution Approach 2:
The system enables self-service by storing the main flow's target server mapping in advance. When subflows arrive, the load balancing device simply queries this pre-stored information rather than performing complex analysis on each subflow. This self-service mechanism significantly reduces the processing load on the load balancing device while maintaining reliable control over message routing.
3Speed
If MPTCP subflows are routed without verification information checking, then routing speed is improved, but the ability to ensure subflows reach the correct target server is reduced
Solution Approach 1:
The target server mapping based on verification information is determined and stored in advance during main flow processing. When subflows arrive, the routing decision is made by querying this pre-established mapping rather than performing new analysis. This preliminary action ensures both high routing speed and accurate target server identification, as the verification information has already been processed and stored for quick retrieval.
Data Source
AI summary
Provided are a network load balancing method and apparatus, an electronic device, a medium, and a program product. After receiving a first packet sent by a client, a virtual switch of the client determines a target flow direction of the first packet according to destination device information in the first packet, determines a packet conversion rule according to verification information carried in the first packet and the target flow direction of the first packet, converts source device information or the destination device information in the first packet on the basis of the packet conversion rule to obtain a second packet, and sends the second packet to a second destination device according to the destination device information in the second packet. Therefore, a sub-stream and a main stream can be directed to the same target server, thereby ensuring normal access.