URF Header Encapsulation for Scalable Packet Forwarding
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing mechanisms and protocols for traditional routers are not suitable for controlling packet forwarding in United Router Farm (URF) architectures, particularly in ring topologies, due to limitations such as requiring direct connectivity between master and slave nodes and restricted scalability by VLAN approaches.
Innovation Solution
Implementing a URF header encapsulation/decapsulation scheme using MPLS, which includes a L2 header with MAC addresses and labels to indicate tunnels and ports, enabling packet forwarding between master and slave nodes without processing IP or L3 addresses, suitable for both hub and spoke and ring topologies.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If VLAN approach is used for packet forwarding in URF, then direct connectivity between master and slave nodes is achieved, but network topology flexibility deteriorates (ring topology not supported)
Solution Approach 1:
The patent introduces MPLS labels as an intermediary mechanism to enable indirect packet forwarding through intermediate nodes. Instead of requiring direct VLAN-based connectivity, packets are forwarded using MPLS label switching through a chain of intermediate nodes, allowing ring topology support while maintaining reliable delivery.
Solution Approach 2:
The patent adds the MPLS label dimension to the traditional VLAN forwarding approach. By encapsulating packets with MPLS labels that contain tunnel endpoint information, the system enables forwarding in an additional dimensional space (label space) rather than relying solely on VLAN MAC address-based direct connectivity.
2Productivity
If VLAN approach is used for packet forwarding in URF, then simple forwarding is achieved, but network scalability deteriorates (limited to 4000 VLAN tags)
Solution Approach 1:
The patent changes the identification parameter from VLAN tags (limited to 4000 values) to MPLS labels (supporting up to 16 million values). This parameter change maintains the simplicity of label-based forwarding while dramatically expanding the network scalability to support hundreds of thousands of nodes.
3Extent of automation
If traditional router mechanisms are used in URF, then routing control functionality is distributed, but device complexity increases
Solution Approach 1:
The patent extracts the complex routing control functionality from individual slave nodes and concentrates it in the master node. Slave nodes are simplified to perform only label switching based on MPLS labels, while the master node handles routing protocol processing and forwarding table distribution, reducing slave node complexity while maintaining distributed control.
Data Source
AI summary
A network component for supporting packet forwarding in a United Router Farm (URF), the network component comprising a processor configured to receive a packet, encapsulate the packet using a URF header comprising a URF Layer Two (L2) header that indicates Media Access Control (MAC) addresses of current and next hops, an outer label that indicates a tunnel to a destination node in the URF, and an inner label that indicates an egress port on the destination node, and send the packet to a next hop in the URF after encapsulating the packet.