MPLS Inactive Path Validation via Extended Echo Requests

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional MPLS network systems cannot effectively validate inactive paths, leading to potential network outages when active paths fail, as they only test and validate active paths, neglecting the necessity of ensuring backup paths are functional and ready for protection.

Innovation Solution

The development of a Network Management System (NMS) that extends existing protocols like RFC 8029 to enable the detection and validation of both active and inactive paths within an MPLS network, allowing for automated testing and validation of protection paths directly from the LSP head end without individual node checks, using enhanced MPLS echo request and reply messages with additional TLV data sets for detailed mapping and validation results.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If conventional MPLS network systems only test and validate active paths using existing protocols like RFC 8029, then the validation process is simple and straightforward, but inactive paths cannot be detected or validated, leading to potential network outages when active paths fail

Engineering Contradiction:
Improvenetwork reliabilityVSAvoidvalidation system complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent applies preliminary action by validating inactive paths before they are needed for protection. The system proactively sends echo requests along inactive paths to detect and validate them in advance, ensuring they are functional before a failure occurs. This prevents the false negative scenario where an inactive path appears valid but fails when activated.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent uses an intermediary approach by introducing a new echo request message format with extended TLV data sets that enable inactive path validation. This intermediary message structure allows the system to distinguish between active and inactive paths and validate them appropriately without requiring complete system redesign.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Measurement precision

If the system validates both active and inactive paths using extended echo requests with additional TLV data sets, then path validation completeness is improved, but the complexity of message processing and protocol implementation increases

Engineering Contradiction:
Improvepath validation precisionVSAvoidprotocol implementation complexity
Core Design Contradiction:
Measurement precisionVSDevice complexity

Solution Approach 1:

The patent applies segmentation by dividing the validation process into distinct components: active path validation and inactive path validation. The echo request message is segmented with specific TLV data sets for each type of path validation, allowing independent processing and validation of each path type with precise control over validation depth and scope.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent uses parameter changes by modifying the echo request message parameters to include additional TLV data sets that specify validation type, depth, and scope. By changing these parameters, the system can dynamically adjust validation precision for active versus inactive paths without requiring different message formats or protocols.

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentUS11516122B2Validating active and inactive paths in a multiprotocol label switching (MPLS) network
Publication Date: 2022.11.29 CIENA CORP
  • US11516122B2 patent drawing
  • US11516122B2 patent drawing
  • US11516122B2 patent drawing

AI summary

Systems and methods for detecting, testing, and validating inactive paths or backup/protection paths of Label Switched Paths (LSPs) in a Multiprotocol Label Switching (MPLS) network are provided. A method, according to one implementation, includes the step of identifying an active path defining a traffic route along which data packets are transmitted from an ingress node to an egress node via one or more intermediate nodes. The method also includes sending an echo request from the ingress node to the one or more intermediate nodes, wherein the echo request allows the one or more intermediate nodes to detect and validate one or more inactive paths. The one or more inactive paths are configured as one or more protection paths when an event is detected that impedes the transmission of the data packets along the active path.