Ethernet MEP Continuity Check Mis-Check Prevention
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In Ethernet OAM systems, configuration time differences and MEP leaving events can lead to mis-checks of continuity, causing false failure reports due to incomplete information dissemination among MEPs within a maintenance domain or entity group.
Innovation Solution
A method and system where an MD group information base is maintained to store information about MEPs, allowing for coordinated continuity checks and ensuring that all MEPs are configured before initiating checks, with mechanisms for joining, querying, and leaving to prevent mis-alarm generation.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If MEPs are configured at different times in a maintenance domain, then the configuration process can be completed, but continuity mis-checks occur due to time differences in configuration delivery
Solution Approach 1:
The patent applies preliminary action by requiring MEPs to send a 'ready' indication message before actually sending CCM frames. This preliminary step ensures all MEPs are configured and ready simultaneously, preventing continuity mis-checks that would otherwise occur due to configuration time differences. The ready indication message acts as a synchronization mechanism that coordinates the start of continuity checking across all MEPs.
2Adaptability or versatility
If an MEP leaves the maintenance domain during operation, then the network can be reconfigured, but false failure reports are generated due to continuity check mechanisms
Solution Approach 1:
The patent applies feedback by implementing a readiness confirmation mechanism where MEPs must indicate they are ready before continuity checking begins. When an MEP leaves the maintenance domain, this feedback mechanism allows the system to detect the absence of expected readiness indications or CCM frames, thereby distinguishing between legitimate failures and normal MEP lifecycle events. The feedback loop ensures accurate failure detection while allowing dynamic MEP management.
3Reliability
If all MEPs in a maintenance domain must be configured before continuity checks start, then mis-checks are prevented, but the system complexity increases
Solution Approach 1:
The patent uses an intermediary approach by introducing a simple readiness indication message as a mediator between configuration completion and continuity checking. This intermediary signal coordinates all MEPs without requiring complex centralized control or sophisticated synchronization protocols. The readiness indication acts as a simple flag that all MEPs can set and check, providing the necessary coordination while keeping the overall system complexity low.
Data Source
Figure 1~2
Figure 3~4
Figure 5~7
AI summary
A continuity check method includes the following steps. A maintenance domain (MD) group is maintained in a network, in which the MD group includes a plurality of maintenance end points (MEPs) in the network, and an MD group information base is configured, and the MD group information base stores information about the plurality of MEPs. According to the information stored in the MD group information base, a continuity check message is initiated, and then, the continuity in the network is determined according to information returned from the plurality of MEPs in the MD. An MEP network system is further provided. Through the method and the system, no mis-check of the continuity will occur when the MEPs in the MD group initiate the continuity check.