PCE Synchronization-Aware LSP Path Computation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional path computation element (PCE) architectures in MPLS networks do not consider synchronization between routers, leading to incorrect ping statistics and increased vulnerability to outages, disrupting traffic engineering services.
Innovation Solution
A PCE system that receives synchronization status information for routing nodes and computes label-switched paths based on this information, using explicit route objects to ensure synchronization-aware path determination and validation.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If conventional PCE architectures compute LSPs without considering router synchronization, then path computation is simpler and faster, but the LSPs are prone to incorrect ping statistics and increased vulnerability to outages
Solution Approach 1:
The PCE obtains synchronization status information from routing nodes before computing the LSP path. This preliminary action ensures that the path computation considers synchronization requirements in advance, preventing incorrect ping statistics and outage vulnerabilities without adding complex real-time synchronization monitoring during path computation
Solution Approach 2:
The patent introduces synchronization status information as an intermediary parameter that mediates between the path computation process and router synchronization states. This intermediary allows the PCE to make informed routing decisions based on synchronization status without directly managing router clock synchronization, maintaining PCE functionality while improving LSP reliability
2Measurement precision
If the PCE considers synchronization status information when computing LSPs, then ping statistics accuracy improves and outage vulnerability decreases, but the path computation process becomes more complex
Solution Approach 1:
The PCE obtains synchronization status information from routing nodes before computing the LSP path. This preliminary acquisition of synchronization status enables accurate ping statistics and outage prevention to be achieved without adding complex real-time synchronization monitoring during the actual path computation process
Solution Approach 2:
The patent incorporates synchronization status as an additional parameter in the path computation process. By treating synchronization status as a routing parameter similar to bandwidth or latency, the PCE can compute accurate paths without fundamentally changing the path computation algorithm structure, thus improving measurement precision while limiting complexity increase
3Device complexity
If LSPs are computed without synchronization awareness, then the PCE architecture remains simple, but control plane functioning becomes more vulnerable to disruptions
Solution Approach 1:
The PCE obtains synchronization status information from routing nodes before computing the LSP path. This preliminary action ensures that the path computation considers synchronization requirements in advance, preventing control plane disruptions without adding complex real-time synchronization monitoring during path computation
Solution Approach 2:
The patent introduces synchronization status information as an intermediary parameter that mediates between the path computation process and router synchronization states. This intermediary allows the PCE to make informed routing decisions based on synchronization status without directly managing router clock synchronization, maintaining PCE functional simplicity while improving control plane stability
Data Source
AI summary
Methods, systems, and computer readable media for computing label-switched data communication paths are disclosed. An example method includes receiving, by a path computation element (PCE) implemented on at least one processor, synchronization status information for routing nodes in a label-switched network. The method includes receiving, by the PCE, a request for a label-switched path (LSP) from a client. The method includes determining, by the PCE, a responsive LSP based at least in part on the synchronization status information. The method includes sending, by the PCE, an explicit route object (ERO) for the responsive LSP to the client.