Synonymous Labels for MPLS Packet Source Identification
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In MPLS networks, counting packets from a specific source is difficult due to the lack of source addresses in MPLS packets, and introducing source address labels would expand the label stack, which is problematic for low-end platforms and requires significant changes to the MPLS architecture. Additionally, running RFC 6374 packet loss measurement across systems that do not understand MPLS GAL can cause issues on commodity platforms.
Innovation Solution
A communication system that replaces a label in a packet's stack with a synonymous label, which identifies the source without expanding the stack, allowing for packet loss measurement and counting without deep packet inspection, and enabling RFC 6374 operation over UDP/IP with minimal changes to the MPLS architecture, supporting dual IP and IP-free designs.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Difficulty of detecting and measuring
If source address labels are introduced to identify packet sources in MPLS networks, then packet source identification capability is improved, but label stack expansion occurs which increases device complexity and requires significant changes to MPLS architecture
Solution Approach 1:
The patent introduces a synonymous label as an intermediary element that enables source identification without directly modifying the original label stack structure. The synonymous label acts as a mediator between the need for source identification and the constraint of maintaining MPLS architecture integrity, allowing measurement functions to be added without expanding the core label stack
Solution Approach 2:
The patent creates a copy of the label stack with synonymous labels that reference the original labels. This copying approach allows source identification functionality to be implemented by working with label copies rather than modifying the original label structure, thus avoiding label stack expansion while enabling measurement capabilities
2Adaptability or versatility
If RFC 6374 packet loss measurement is run across systems that do not understand MPLS GAL, then measurement coverage is improved, but compatibility issues arise on commodity platforms
Solution Approach 1:
The patent implements a universal label structure where synonymous labels can function across different platform types (MPLS-aware and MPLS-unaware systems). The label design enables the same measurement mechanism to operate on commodity platforms without requiring specialized MPLS GAL understanding, thus achieving both broad measurement coverage and platform compatibility
Solution Approach 2:
The patent changes the parameter space of label usage by introducing synonymous labels that can be interpreted differently by different platform types. This parameter change allows the same label structure to convey measurement information to MPLS-aware systems while remaining compatible with standard MPLS processing on commodity platforms
3Loss of information
If label stack is expanded to support source identification, then packet source identification capability is improved, but processing overhead increases affecting network performance
Solution Approach 1:
The patent extracts the source identification function from the label stack expansion problem by using synonymous labels that carry measurement information without requiring additional stack depth. This extraction separates the information-carrying function from the structural expansion, maintaining forwarding performance while enabling source identification
Data Source
Figure 1
Figure 2
Figure 3
AI summary
Particular embodiments described herein provide for a communication system that can be configured to identify a system that includes network traffic, where at least a portion of the network traffic includes packets, at least a portion of the packets include a stack, and at least a portion of each stack includes one or more previously allocated labels. The communication system can further be configured to determine a synonymous label that triggers an action and to replace a label from the one of the one or more previously allocated labels in a specific stack of a specific packet with the synonymous label. In an example, the synonymous label can be used to identify a subset of packets in the network traffic or a source of the specific packet.