Policy-Based Edge Routing With Compact Packet Labels
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing routing protocols in edge networks, particularly in cloud and containerized environments, suffer from high overhead and inefficiencies due to large header sizes and complex processing requirements, leading to congestion and resource scarcity, especially in low-powered devices.
Innovation Solution
Implementing a custom header with unique identifiers (UIDs) for packet tagging in software-defined networks (SDNs), reducing header sizes and processing overhead by converting packets at ingress and egress points, and using programmable switches to manage network policies and telemetry.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If standard TCP/IP routing protocols are used in edge networks, then compatibility with legacy devices is maintained, but substantial overhead is produced particularly for small packets
Solution Approach 1:
The packet structure is segmented into a simplified header and payload, where only the essential routing information is retained in the header. The standard TCP/IP headers are stripped away, keeping only the minimum necessary fields for routing decisions, thereby reducing overhead while maintaining compatibility through selective retention of essential protocol elements.
Solution Approach 2:
The unnecessary TCP/IP header fields are extracted and removed from the packet structure. Only the essential routing information is kept, eliminating the bulk of the overhead (60 bytes of standard headers reduced to minimal fields). This extraction process removes the harmful overhead while preserving the core routing functionality needed for legacy compatibility.
2Adaptability or versatility
If VXLAN encapsulation is used for containerized applications, then end-to-end connectivity is provided, but header overhead increases to over 93%
Solution Approach 1:
The VXLAN encapsulation headers are extracted and removed from the packet structure. The patent replaces the verbose VXLAN header format with a compact identifier system that achieves the same tunneling and routing functionality with minimal overhead, reducing header size from 54+ bytes to just a few essential fields.
Solution Approach 2:
The packet format parameters are changed from the standard VXLAN specification to a customized compact format. The header fields are redefined with smaller sizes and fewer fields, changing the structural parameters of the encapsulation to achieve the same connectivity function with dramatically reduced overhead (from 93% to minimal overhead).
3Reliability
If FCS is performed for each network packet, then error detection is achieved, but congestion occurs particularly where resources are scarce
Solution Approach 1:
The FCS checksum calculation and verification process is extracted and eliminated from the packet processing path. The patent accepts a trade-off where error detection is reduced or handled at higher layers, removing this source of congestion and processing overhead from the data plane operations in resource-constrained edge devices.
4Ease of operation
If all packet headers are processed by the switch in sequence, then routing decisions can be made, but processing cost increases with the number of headers to parse
Solution Approach 1:
The unnecessary header fields are extracted and removed from the packet structure, leaving only the essential routing information that switches need to process. This eliminates the need to parse through multiple layers of standard TCP/IP and VXLAN headers, reducing the processing time and computational cost while maintaining the ability to make routing decisions based on the remaining essential fields.
Data Source
AI summary
Policy based routing in networks including software-based networks is disclosed. Packets ingested into a software defined network are altered to include a label header that identifies a source and destination of a packet. If the packets leave or egress the network, the packets are converted back to regular packets by removing the label header. Adding the label header reduces overhead. Further routing can be performed while enforcing policies.