Proxy Connectivity Fault Management in Bridged VPLS Networks
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current Connectivity Fault Management (CFM) schemes in bridged or virtual private LAN service environments are not scalable due to the flooding of connectivity check messages across the network, leading to increased traffic as the number of maintenance endpoints increases.
Innovation Solution
A network element proxies connectivity check messages and sends fault state change messages across an MPLS/VPLS network, using a local database to identify and manage remote maintenance endpoints, reducing the need for constant connectivity checks across the service provider network.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If connectivity check messages are flooded across the network to detect all maintenance endpoints, then fault detection coverage is improved, but network traffic increases and scalability deteriorates
Solution Approach 1:
The patent introduces intermediary network elements (such as PCEs or controllers) that mediate between maintenance endpoints and the core network. These intermediaries collect connectivity check results from multiple maintenance endpoints locally and only propagate necessary fault information through the core network, eliminating the need to flood connectivity check messages across the entire network while maintaining comprehensive fault detection coverage.
Solution Approach 2:
The patent segments the network into different functional zones with maintenance endpoints attached to local network elements. Instead of treating the entire network as a single flood domain, the system divides connectivity management into local segments that handle fault detection independently, reducing the propagation scope of connectivity check messages and improving scalability.
2Measurement precision
If connectivity check messages are sent to all maintenance endpoints to verify connectivity, then fault detection accuracy is improved, but message traffic increases
Solution Approach 1:
The patent extracts the connectivity check function from the core network and relocates it to edge network elements or intermediaries. By taking out the message generation and propagation function from the core network, the system maintains accurate fault detection at the edge while significantly reducing the quantity of messages traversing the core network infrastructure.
Solution Approach 2:
The patent employs copying of connectivity check results at intermediary nodes. Instead of forwarding original connectivity check messages through the entire network, intermediaries create local copies of the results and only transmit necessary fault state information, reducing message traffic while preserving detection accuracy.
3Adaptability or versatility
If the number of maintenance endpoints increases to cover more network devices, then fault management coverage is improved, but network complexity increases
Solution Approach 1:
The patent implements universal intermediary network elements that can serve multiple maintenance endpoints simultaneously. These multi-functional elements aggregate connectivity check results from numerous maintenance endpoints and provide unified fault management services, allowing the system to scale coverage without proportionally increasing complexity at the core network level.
Solution Approach 2:
The patent merges the functionality of multiple maintenance endpoint management functions into centralized or regional intermediary nodes. By combining local connectivity check operations, result aggregation, and fault propagation functions into single points, the system achieves broader fault management coverage while reducing the distributed complexity that would otherwise increase with each additional maintenance endpoint.
Data Source
AI summary
A first network element that is to be coupled with a second network element over a first network in the same domain is described. The first network element includes a connectivity check detection module and a connectivity check fault state change module. The connectivity check detection module detects, according to a first protocol, a connectivity status of a local maintenance endpoint on a second network changing between not active and active. The connectivity check fault state change module creates and sends a first fault state change message, according to a second protocol, in response to the connectivity status of the local maintenance endpoint changing from not active to active instead of forwarding connectivity check messages periodically received by the first network element to a remote maintenance endpoint coupled to the second network element over a third network.