Source Label Preservation in MPLS Networks
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Multiprotocol Label Switching (MPLS) networks face complexity due to the need for multiple signaling protocols, leading to delayed fault recovery and increased operational complexity, which complicates source identification preservation and Operations, Administration, and Maintenance (OAM) tasks.
Innovation Solution
The introduction of a source label that is pushed onto the label stack of packets in MPLS networks, allowing for source identification preservation by indicating the source node for OAM purposes, without affecting forwarding processes, and using explicit reserved label identifiers to locate the source label within the stack.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If multiple signaling protocols (LDP, RSVP-TE, multicast-LDP) are used to support label push, swap, and pop operations, then MPLS can deliver a wide range of functionalities and services, but the control protocol complexity increases significantly
Solution Approach 1:
The patent extracts the source identification function from the complex MPLS label stack operations. By introducing a dedicated source label that is pushed onto the label stack at the ingress node and popped at the egress node, the patent separates source tracking from the main label switching operations, thereby reducing control protocol complexity while preserving source identification capability for OAM purposes
Solution Approach 2:
The source label serves multiple functions: it identifies the source node for OAM operations, enables packet and byte counter updates, supports traffic matrix management, and facilitates fault recovery. This multi-functional approach consolidates several OAM requirements into a single mechanism, reducing the need for multiple specialized protocols
2Stability of the object's composition
If label path signaling executes only after underlying unicast topology convergence, then routing stability is ensured, but fault recovery is delayed
Solution Approach 1:
The source label is pushed onto the label stack at the ingress node before the packet enters the MPLS network, and is preserved throughout the label switching path. This preliminary establishment of source identification allows the egress node to immediately perform OAM operations and detect faults without waiting for complete topology convergence, thereby accelerating fault recovery while maintaining routing stability
3Ease of operation
If destination-based forwarding is used in MPLS networks, then forwarding simplicity is achieved, but source identification is lost
Solution Approach 1:
The source label is nested within the MPLS label stack, positioned as the bottom-most label. This nesting allows the source identification to be carried along with the packet through the entire label switching path without interfering with the destination-based forwarding operations. The source label is popped at the egress node after destination processing is complete, thus preserving source information while maintaining forwarding simplicity
Data Source
AI summary
A source Multiprotocol Label Switching (MPLS) network element, a destination MPLS network element, and a MPLS method are disclosed which introduce the concept of a source label into the MPLS label stack for source identification preservation. The source label can located at the bottom of the label stack thereby being a last item popped in the MPLS stack at the destination node, or indicated subsequent to an explicit reserved label identifier. The source label is used for maintaining Operations, Administration, and Maintenance (OAM) data efficiently without requiring deep packet inspection.