Network Switching Device Abstract MAC Address Replacement
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing router devices struggle to handle large IP routing tables and high bandwidth requirements simultaneously, with OpenFlow-controlled devices unable to manage 500,000 routes and Linux-based virtual routers unable to handle the necessary bandwidth, leading to costly solutions and inefficiencies.
Innovation Solution
A method and system for routing packet data that involves receiving a data packet with an abstract MAC address, replacing it with a real MAC address, and forwarding it to the next hop destination, using a network switching device that can handle both large routing tables and bandwidth, without requiring additional data-plane support for MPLS or control plane support for VLANs.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If OpenFlow-controlled devices with dedicated routing hardware are used, then bandwidth handling capability is improved, but the ability to handle large IP routing tables (500,000 routes) deteriorates
Solution Approach 1:
The patent segments the routing function into two parts: routing decisions are made by Linux-based virtual routers using software data planes that can handle large routing tables, while packet forwarding is handled by OpenFlow devices with dedicated hardware that provide high bandwidth. This segmentation allows each component to specialize in what it does best, resolving the contradiction between bandwidth handling and routing table capacity.
2Adaptability or versatility
If Linux-based virtual routers with software data planes are used, then the ability to handle large IP routing tables (500,000 routes) is improved, but bandwidth handling capability deteriorates
Solution Approach 1:
The patent divides the routing system into control plane functions (routing decisions) handled by Linux virtual routers and data plane functions (packet forwarding) handled by OpenFlow devices. This segmentation allows the Linux side to manage large routing tables while the hardware-accelerated OpenFlow side handles high bandwidth traffic, resolving the contradiction between routing table capacity and bandwidth handling.
3Adaptability or versatility
If multiple COTS Linux virtual routers are used to handle routing decisions, then routing table capacity is improved, but system complexity increases due to requiring multiple systems
Solution Approach 1:
The patent makes the Linux-based virtual routers multi-functional by having them perform both routing decision-making and packet forwarding through the OpenFlow interface. This universality allows a single type of device to handle both routing table management and traffic forwarding, reducing system complexity compared to requiring completely separate routing and forwarding infrastructure.
4Productivity
If MPLS labels are used for tagging routing decisions, then packet forwarding efficiency is improved, but compatibility with Linux deteriorates due to lack of MPLS support
Solution Approach 1:
The patent changes the tagging parameter from MPLS labels to VLAN tags, which are natively supported by Linux. This parameter change maintains the efficiency benefits of tagged packet forwarding while ensuring compatibility with Linux-based virtual routers, resolving the contradiction between forwarding efficiency and Linux compatibility.
5Adaptability or versatility
If VLAN tags are used for tagging routing decisions, then Linux compatibility is improved, but standards-based mapping between routes and VLAN identifiers deteriorates
Solution Approach 1:
The patent introduces a controller as an intermediary that manages the mapping between routes and VLAN tags. This controller provides the standards-based mapping functionality that is missing from native VLAN support, while allowing Linux-based virtual routers to use VLAN tags for packet marking. The controller mediates between the routing decisions and the VLAN tagging mechanism, resolving the contradiction between Linux compatibility and mapping standardization.
Data Source
AI summary
Measures, including methods, systems, non-transitory computer-readable storage mediums and computer programs for use in routing packet data. At a network switching device, a data packet is received from a device located upstream of the network switching device. The received data packet comprises routing data associated with a routing decision which has been taken for the data packet upstream of the network switching device. The routing data comprises an abstract media access control (MAC) address corresponding to a next hop destination for the data packet located downstream of the network switching device. At the network switching device, the abstract MAC address in the data packet is replaced with a real MAC address of the next hop downstream destination. At the network switching device, the data packet is forwarded towards the next hop downstream destination.