VPN Label Allocation for Remote PE Packet Source Identification
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In existing L3VPN networks, the inability to distinguish packets from different remote PEs hinders fault management and performance measurement due to the use of LDP LSPs, which are multi-point in nature and do not allow the egress node to determine the source of packets based on tunnel labels.
Innovation Solution
A network label allocation method where a local PE generates and sends a VPN label route to each remote PE, ensuring the VPN labels are unique and allowing the remote PE to match IP addresses and route targets, enabling the local PE to differentiate packets from different remote PEs by carrying distinct VPN labels.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If LDP LSP is used to bear the L3VPN, then the L3VPN can be established with multi-point connectivity, but the egress node cannot determine the source of packets according to the LSP tunnel label
Solution Approach 1:
The patent segments the label space by allocating different VPN labels to different remote PEs. Instead of using a single shared label for all remote PEs, the local PE divides the label resource so that each remote PE receives a unique label, enabling source identification while maintaining multi-point connectivity.
Solution Approach 2:
The patent applies local quality by making the label property specific to each remote PE. Each remote PE is assigned a distinct VPN label that reflects its identity, allowing the egress node to determine the source of packets based on the label carried in the packet.
2Ease of manufacture
If all remote PEs carry the same VPN label, then the L3VPN can be established with simplified label allocation, but the local PE cannot distinguish packets from different remote PEs
Solution Approach 1:
The patent segments the label allocation process so that instead of assigning a single label to all remote PEs, each remote PE receives a segmented, unique label. This segmentation enables the local PE to distinguish packet sources while maintaining systematic label management.
Solution Approach 2:
The patent changes the label parameter from a shared, identical value to a unique value for each remote PE. By modifying the label parameter to be source-specific, the system enables precise packet source distinction while maintaining structured label allocation.
3Measurement precision
If unique VPN labels are allocated to each remote PE, then the local PE can distinguish packets from different remote PEs, but the label allocation complexity increases
Solution Approach 1:
The patent applies universality by using the same BGP routing information exchange mechanism for both VPN label distribution and source identification. The multi-functionality of BGP to handle both label allocation and source tracking reduces overall system complexity despite the increased precision in packet source distinction.
Solution Approach 2:
The patent implements self-service by enabling remote PEs to autonomously match their own IP addresses and route targets with the received VPN label routes. This self-matching capability reduces the need for complex centralized management and automates the label allocation process.
4Reliability
If separate VPN label routes are sent to each remote PE, then fault management and performance measurement become possible, but the routing information exchange overhead increases
Solution Approach 1:
The patent uses BGP routing information to simultaneously achieve multiple functions: VPN label distribution, source identification, and fault management. This multi-functionality reduces the need for separate signaling protocols and minimizes overall routing information overhead while enabling comprehensive network management capabilities.
Data Source
AI summary
Embodiments of the present invention provide a network label allocation method, a device, and a system, which enable a local PE to distinguish packets from different remote PEs. The method includes: generating, by a local provider edge PE, a VPN label route for each remote PE, where VPN labels in VPN label routes of different remote PEs are different, and the remote PE and the local PE at least belong to a same VPN; and sending the VPN label route to the remote PE, so that the remote PE separately matches an IP address of the remote PE with a target device IP address in the VPN label route, and matches an import route target RT of each VRF of the remote PE with a route target RT in the VPN label route, a packet related to a successfully matched VRF.