Traffic-Triggered LSP Setup in MPLS Networks
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current Label Switched Path (LSP) setup methods in MPLS networks are not scalable, do not adapt well to changing network conditions, and inefficiently utilize resources, as they either require manual configuration, rely on routing updates, or are limited to specific scenarios.
Innovation Solution
Implementing a mechanism that uses incoming traffic information to automatically trigger LSP setup and teardown based on predefined data rate thresholds, utilizing a metering device and MPLS signaling to ensure LSPs are established only when necessary, and torn down when traffic falls below the threshold.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If LSP-setup is triggered by explicit user configuration, then LSP tunnels can be established with specific routing paths, but the approach is not scalable and does not adapt well to changing network conditions
Solution Approach 1:
The system enables LSPs to be automatically set up and torn down based on traffic flow detection, eliminating the need for manual user configuration. The network infrastructure itself monitors traffic patterns and triggers LSP setup when flows are detected, making the system self-configuring and adaptive to changing conditions
Solution Approach 2:
The LSP setup mechanism transitions from static explicit configuration to dynamic automatic setup based on real-time traffic conditions. LSPs are created when traffic flows are detected and removed when flows cease, allowing the network to adapt dynamically to changing traffic patterns and network conditions
2Productivity
If LSP-setup is triggered by routing updates, then LSPs are established for destination prefixes, but LSPs remain underutilized in the absence of traffic
Solution Approach 1:
The system dynamically creates and removes LSPs based on actual traffic flow presence. LSPs are established only when traffic flows are detected and are torn down when flows cease, ensuring that network resources are utilized only when needed and eliminating the overhead of maintaining unused LSPs
Solution Approach 2:
The system discards (tears down) LSPs when traffic flows are no longer present and recovers network resources by removing the LSP overhead. This ensures that network resources are not wasted on maintaining LSPs for destinations with no active traffic
3Adaptability or versatility
If LSP-setup is triggered by client signaling across MPLS UNI, then LSPs connect Customer Equipment across the network, but the approach is limited to specific scenarios and mandates a point of operation
Solution Approach 1:
The system eliminates the need for client signaling by enabling the network infrastructure to automatically detect traffic flows and trigger LSP setup independently. This removes the dependency on MPLS-UNI capable clients and makes the system universally applicable to any traffic flow scenario
Solution Approach 2:
The LSP setup mechanism transitions from static client-triggered signaling to dynamic automatic setup based on real-time traffic flow detection. The system adapts to any traffic scenario without requiring specific client capabilities or predetermined points of operation
Data Source
Figure 1
Figure 2
Figure 3
AI summary
An automated Label Switched Path (LSP) control mechanism in a packet-switched network. A metering device in an Ingress Label Edge Router (LER) determines whether a data rate for a packet flow class exceeds a predefined limit. If so, the metering device sends an LSP-setup message to a Multi-Protocol Label Switching (MPLS) signaling function for setting up an LSP. When a calculated long-term data rate falls below a second predefined limit, the metering device sends an LSP-teardown message to the MPLS signaling function, which tears down the LSP. Current LSP status information and Next- Hop Label Forwarding Entries (NHLFE) information are stored in an associated database.