Remote Switching Device Local Packet Forwarding
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In cloud computing data networks, efficiently interconnecting thousands of backend systems and client devices is complex, leading to bandwidth consumption and latency issues, particularly when relying on traditional switch controllers and virtual machines for packet forwarding.
Innovation Solution
Implementing a satellite or remote switching device that operates as a port or fabric extender of a parent switching device, allowing for autonomous local switching by synchronizing forwarding tables between parent and remote devices, reducing the need for direct communication and thereby minimizing bandwidth usage and latency.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of energy
If traditional switch controllers and virtual machines are used for packet forwarding, then packet forwarding functionality is provided, but bandwidth consumption increases and latency occurs
Solution Approach 1:
The network switching function is segmented between parent switching devices and remote switching devices. The remote switching device handles local packet forwarding autonomously for packets within its domain, while the parent switching device handles inter-domain routing. This segmentation eliminates the need for all packets to traverse through virtual machines and traditional switch controllers, reducing bandwidth consumption and latency.
Solution Approach 2:
The remote switching device acts as an intermediary between end devices and the parent switching device. It receives packets from local end devices, performs local forwarding decisions using its own forwarding table, and only sends packets to the parent switching device when the destination is outside its local domain. This intermediary function reduces unnecessary bandwidth consumption and latency associated with traditional centralized switching.
2Productivity
If remote switching devices perform autonomous local switching, then bandwidth consumption and latency are reduced, but device complexity increases
Solution Approach 1:
Instead of the traditional approach where the parent switching device maintains the complete forwarding table and all switching decisions are made centrally, this invention inverts the model: the remote switching device maintains its own forwarding table and makes local switching decisions autonomously. The parent switching device still maintains the master forwarding table for inter-domain routing. This inversion distributes complexity but enables local autonomy that improves productivity.
Solution Approach 2:
The remote switching device receives a copy of the relevant portion of the parent switching device's forwarding table and uses it to build its own local forwarding table. This copying mechanism allows the remote device to make autonomous forwarding decisions without requiring complex real-time communication with the parent device for every packet, thus improving productivity while managing device complexity through table replication.
3Device complexity
If centralized packet forwarding through parent switching device is used, then forwarding control is simplified, but bandwidth consumption increases
Solution Approach 1:
The forwarding control is made local to each remote switching device's domain. Each remote switching device has its own forwarding table tailored to its local network segment, enabling it to make forwarding decisions independently for local packets. This local quality approach means that forwarding control complexity is distributed rather than centralized, and simultaneously eliminates the bandwidth consumption associated with all packets traversing through the parent switching device.
Data Source
Figure 1
Figure 2
Figure 3A
AI summary
A data packet is received, at a parent switching device, from a first host device via a remote switching device. The data packet has a first source media access control (MAC) address corresponding to the first host device and information indicative that the data packet passed through the remote switching device via a first port. An entry is added to a parent switching table in the parent switching device, the parent switching table associating the first MAC address and the first port of the remote switching device with one another. A switching table entry update message is sent to the remote switching device indicating that the first MAC address and the first port are associated with one another so as to enable a subsequent data packet destined for the first host device and received at the remote switching device to be switched directly to the first host.