VPN Traffic Transport with IP/UDP Header Removal
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The processing and forwarding of VPN traffic between CE network devices through PE network devices is resource-intensive due to the inclusion of IP and UDP headers, which increases computing, memory, and power usage, and affects bandwidth, latency, and reliability performance.
Innovation Solution
PE network devices remove IP and UDP headers from VPN traffic and replace them with MPLS labels, using advertisement messages to update data structures for header reconstruction, enabling efficient header-less traffic transmission.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If IP and UDP headers are included in VPN traffic, then traffic can be properly routed and processed, but computing resources, memory usage, and processing burden on PE network devices increase
Solution Approach 1:
The patent extracts and removes IP and UDP headers from VPN traffic at PE network devices before transmission through the backbone network. Only the essential payload and necessary routing information are transmitted, eliminating redundant header data that consumes computing resources and energy while maintaining proper traffic routing through alternative mechanisms.
Solution Approach 2:
The patent introduces MPLS labels as an intermediary mechanism to replace traditional IP headers for routing decisions in the backbone network. These labels provide necessary routing information without requiring full IP and UDP headers, thereby reducing processing requirements while maintaining reliable traffic steering.
2Reliability
If IP and UDP headers are included in VPN traffic, then traffic can be properly identified and processed, but bandwidth is reduced and latency increases
Solution Approach 1:
The patent extracts and removes IP and UDP headers from VPN traffic before transmission through the backbone network. Only the essential payload and necessary routing information are transmitted, eliminating redundant header data that consumes bandwidth and processing time, thereby improving bandwidth availability and reducing latency.
Solution Approach 2:
The patent changes the parameter of header size from traditional IP/UDP headers (typically 24-64 bytes) to compact MPLS labels (4 bytes). This parameter change dramatically reduces the amount of data transmitted per packet, improving bandwidth efficiency and reducing processing latency while maintaining traffic identification capability.
3Loss of information
If PE network devices process VPN traffic with headers, then complete traffic information is available, but device complexity and processing burden increase
Solution Approach 1:
The patent extracts and removes IP and UDP headers from VPN traffic at PE network devices before transmission through the backbone network. Only the essential payload and necessary routing information are transmitted, eliminating redundant header data that increases processing burden while maintaining traffic information completeness through alternative routing mechanisms.
Solution Approach 2:
The patent introduces MPLS labels as an intermediary mechanism to replace traditional IP headers for routing decisions in the backbone network. These labels provide necessary routing information without requiring full IP and UDP headers, thereby reducing processing requirements while maintaining reliable traffic steering.
Data Source
AI summary
In some implementations, a first PE network device may receive, from a first CE network device, traffic that includes at least an IP header. The first PE network device may determine whether the first PE network device is to remove the IP header, or the IP header and a UDP header included in the traffic, from the traffic. The first PE network device may send, to one or more second PE network devices, the traffic, wherein the first PE network device, prior to sending the traffic, updates the traffic by removing the IP header, or the IP header and a UDP header, when the first PE network device makes a removal determination, and wherein the first PE network device, prior to sending the traffic, does not update the traffic when the first PE network device does not make a removal determination.


