Packet Sending with QUIC 5-Tuple Changes to Reduce Routing Overhead
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional communication protocols require binding a 5-tuple during connection establishment, leading to high network overheads due to the need to record extensive binding relationship information between clients and service nodes as the number of clients and service nodes increases.
Innovation Solution
Utilizing the flexibility of new protocols like QUIC to allow changing the 5-tuple after connection establishment, enabling direct routing to target service nodes without maintaining binding relationships, thereby reducing network overheads.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Measurement precision
If the server records binding relationship information to correctly route packets to target service nodes, then packet routing accuracy is improved, but network overhead increases
Solution Approach 1:
The patent extracts the service node identification information from the packet payload and places it in the IP header destination address field. This allows the routing information to be carried directly in the network layer header without requiring additional binding relationship tables at the server, thereby reducing network overhead while maintaining routing accuracy.
Solution Approach 2:
The load balancer performs preliminary action by modifying the destination IP address in the packet header before forwarding it to the server. It replaces the original server IP address with the target service node's IP address, so that the server receives packets already addressed to the correct service node without needing to maintain binding relationships.
2Productivity
If the server includes multiple service nodes to handle increased client load, then service capacity is improved, but the amount of binding relationship information to be recorded increases
Solution Approach 1:
The patent removes the need for the server to maintain binding relationship information by extracting the target service node identification from the load balancer's IP address modification. Each service node is independently addressable through its own IP address in the packet header, eliminating the complexity of managing binding relationships between clients and service nodes.
Solution Approach 2:
The load balancer acts as an intermediary that translates client requests to the appropriate service nodes by modifying packet headers. It maintains the mapping between client IP addresses and target service nodes, while the server simply receives packets addressed to its service nodes without needing to maintain any binding relationship information.
3Stability of the object's composition
If the 5-tuple is bound during connection establishment, then connection stability is improved, but the ability to change destination IP address is lost
Solution Approach 1:
The load balancer performs preliminary IP address modification in the packet header before the connection is fully established. It replaces the original destination IP address with the target service node's IP address, so that subsequent packets in the connection use the correct service node IP address without requiring to change the bound 5-tuple. The connection stability is maintained while the IP address is correctly set from the beginning.
Data Source
Figure 1
Figure 2~4
Figure 5~7
AI summary
This application provides a packet sending method, a network device, and a computer-readable storage medium. The method includes: receiving, by a target service node, a first packet sent by a client, where a destination address of the first packet is an IP address of a server; sending, by the target service node, a second packet to the client, where the second packet includes an IP address of the target service node; and receiving, by the target service node, a third packet sent by the client, where a destination address of the third packet is the IP address of the target service node. In the foregoing technical solution, the target service node records the IP address of the node in the second packet. After receiving the second packet, the client changes a destination address from the IP address of the server to the IP address of the target service node to send the third packet, and the server directly forwards the third packet to the target service node with no need to record a correspondence between the client and the target service node, thereby reducing network overheads.