UDP Port-Based VRF Delimiting in IP-in-IP Tunnels
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing network technologies face challenges in identifying different services through Virtual Routing and Forwarding (VRF) instances in layer 3 tunnels without relying on MPLS labels or VXLAN Network Identifiers, particularly in next-generation data centers using IP-in-IP tunnels, which do not scale well and incur high provisioning overhead.
Innovation Solution
Utilizing unique UDP port numbers to identify different connectivity services or VRFs within IP-in-IP tunnels, enabling service delimiting by allocating a UDP destination port value for each VRF instance and associating a forwarding table, with information exchange through BGP messages or other protocols.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Measurement precision
If different IP loopback addresses are used as tunnel destination addresses for different services, then service identification is achieved, but scalability deteriorates and provisioning overhead increases
Solution Approach 1:
The patent changes the identification parameter from IP loopback addresses to UDP port numbers. Instead of using different destination IP addresses to identify different VRF instances, the invention uses UDP port numbers within a single IP address framework, thereby maintaining service identification capability while reducing provisioning overhead and improving scalability.
Solution Approach 2:
The invention makes a single IP address serve multiple functions by using different UDP port numbers to identify different services. Instead of requiring a unique IP address for each service, the same IP address can handle multiple VRF instances through port differentiation, thus reducing the number of required tunnel destination addresses.
2Measurement precision
If MPLS labels or VXLAN Network Identifiers are used to identify VRF instances, then service delimiting is achieved, but compatibility with pure IP fabric networks deteriorates
Solution Approach 1:
The patent introduces UDP port numbers as an intermediary mechanism for service identification. Instead of directly using MPLS labels or VXLAN VNIs that require specific encapsulation protocols, the invention uses UDP port numbers that work within standard IP protocols, thereby bridging the gap between service delimiting requirements and pure IP fabric compatibility.
Solution Approach 2:
The invention replaces the MPLS/VXLAN encapsulation mechanism with a UDP-based IP-in-IP tunneling mechanism. By substituting the proprietary encapsulation protocols with standard UDP ports, the system achieves service delimiting functionality while maintaining compatibility with pure IP fabric networks that do not support MPLS or VXLAN.
3Adaptability or versatility
If IP-in-IP tunnels are used for overlay, then flexibility in underlay network choice is improved, but service identification scalability deteriorates
Solution Approach 1:
The patent changes the service identification parameter from IP addresses to UDP port numbers within the IP-in-IP tunneling framework. This parameter change allows the system to maintain underlay network flexibility while solving the scalability issue of service identification, as UDP port numbers provide a more efficient and scalable mechanism for identifying multiple services over a single tunnel destination.
Data Source
AI summary
Different services through Virtual Routing and Forwarding instances (VRFs) are identified without needing a Multiprotocol Label Switching (MPLS) label or a Virtual Extensible Local Area Network (VXLAN) Network Identifier (VNI) by using, for example, different UDP port numbers to identify different connectivity services (e.g., customers, VRFs) when IP-in-IP (also referred to as IP over UDP) is used as a tunneling mechanism (e.g., in the data center).