Traffic Forwarding With Device ID Routing Across Availability Zones
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The migration of local network functions to the cloud results in non-accessible forward and reverse traffic to the same network device, especially in scenarios with multiple availability zones, limiting the usability of complex network devices.
Innovation Solution
A traffic forwarding method that adds device identification information to forward and reverse traffic, ensuring consistency by routing both types of traffic to the same network device through a virtual switch across multiple availability zones.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If a gateway load balancer (GWLB) technology is adopted to ensure forward and reverse traffic accessibility, then traffic forwarding capability is improved, but network device consistency cannot be ensured in multi-availability zone scenarios
Solution Approach 1:
The patent introduces a session continuity record as an intermediary element that mediates between forward traffic and reverse traffic routing. This record stores the mapping relationship between terminal devices and network devices, enabling the system to maintain device consistency across multiple availability zones by referencing this intermediate storage mechanism rather than relying solely on direct traffic routing.
Solution Approach 2:
The patent adds a new dimension to traffic routing by incorporating availability zone information and session continuity records into the routing decision process. Instead of making routing decisions based only on traditional network paths, the system now considers the availability zone dimension and uses session continuity records to bridge different zones, ensuring that both forward and reverse traffic can access the same network device even when distributed across multiple zones.
2Adaptability or versatility
If network functions are migrated to the cloud across multiple availability zones, then system availability and scalability are improved, but forward and reverse traffic cannot access the same network device
Solution Approach 1:
The session continuity record serves a universal function across multiple availability zones, acting as a common reference point that enables both forward and reverse traffic to locate the appropriate network device regardless of which availability zone they traverse. This multi-functional mechanism allows the system to maintain device consistency while operating across distributed zones, effectively making the routing system adaptable to different zone configurations.
Solution Approach 2:
The system performs preliminary action by creating and storing session continuity records before traffic routing occurs. These records pre-establish the mapping relationships between terminal devices and network devices across availability zones, so when traffic needs to be routed, the system can quickly reference these pre-established records rather than performing complex real-time routing decisions, thereby ensuring both availability and accessibility.
Data Source
AI summary
Provided in the present disclosure is a traffic forwarding method. The method includes: receiving forward traffic from a source device in a source network, where the forward traffic is targeted at a destination device in a destination network for transmission; distributing the forward traffic to a target network device in an intermediate network for processing; and transmitting, to the destination device, processed forward traffic carrying device identification information of the target network device, to enable reverse traffic returned by the destination device to the source device to carry the device identification information of the target network device, where the device identification information is used for instructing a virtual switch to forward the reverse traffic to the target network device for processing, where the virtual switch corresponds to a routing access point receiving the reverse traffic in the intermediate network.