Ethernet Maintenance Endpoint Address Resolution
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The existing Ethernet CFM standard, as defined in IEEE 802.1ag, assumes every node supports full functionalities, including MAC addresses, which is not feasible in broadband access networks where customer premises equipment typically lacks MAC addresses or full protocol suite support, making it difficult for service providers to monitor physical connection paths and perform OAM functions effectively.
Innovation Solution
Implementing a multicast-based mechanism to resolve the address of a user-line MEP without continuous CCMs, using virtual Maintenance End Points (vMEPs) that emulate MEPs on broadband access nodes, allowing for seamless interworking between legacy OAM schemes and 802.1ag signals, and enabling proactive and reactive monitoring without requiring continuous address advertising.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If continuous CCMs are used for address advertising and monitoring, then OAM functions can be performed effectively, but network resources are overwhelmed with multicast messages
Solution Approach 1:
The patent implements periodic continuity check messages (CCMs) instead of continuous address advertising. MEPs send unicast CCMs at configured intervals to maintain connectivity monitoring, reducing network traffic while ensuring reliable OAM functions. The periodic transmission allows the network to detect faults while avoiding resource exhaustion from constant messaging.
Solution Approach 2:
The patent extracts the address advertising function from continuous CCM transmission. Instead of continuously advertising addresses through multicast, the system uses event-driven unicast CCMs that are triggered only when necessary, such as when a fault is detected or when address resolution is needed. This separates the monitoring function from continuous traffic generation.
2Productivity
If multicast-based address resolution is implemented, then MEP addresses can be resolved without continuous CCMs, but compatibility with legacy OAM schemes must be maintained
Solution Approach 1:
The patent introduces a dual-mode MEP architecture that acts as an intermediary between legacy OAM schemes and 802.1ag signals. The MEP can operate in either mode depending on the communication partner, translating between different OAM protocols as needed. This mediator approach enables seamless interworking while maintaining the efficiency benefits of the multicast-based resolution mechanism.
Solution Approach 2:
The patent implements dynamic operational modes for MEPs that can adapt their behavior based on the communication context. A MEP can switch between legacy mode and 802.1ag mode, and can adjust its address resolution strategy based on whether it is communicating with legacy equipment or 802.1ag-compliant equipment. This dynamic adaptability maintains compatibility while optimizing performance.
3Adaptability or versatility
If virtual MEPs are used to emulate MEPs on broadband access nodes, then OAM functions can be performed without full protocol support at customer premises, but complexity of the access node increases
Solution Approach 1:
The patent creates virtual MEPs that are software-based copies of physical MEP functionality. Instead of requiring full protocol stacks and MAC address support at customer premises equipment, the system creates virtual representations of MEPs on the broadband access node that emulate the required OAM behavior. This copying approach moves the complexity to the network side while keeping customer equipment simple.
Solution Approach 2:
The patent implements a universal OAM framework where a single broadband access node architecture can handle multiple protocol types and service requirements through virtual MEPs. The virtual MEP infrastructure provides multi-functionality, allowing the same hardware platform to support legacy OAM schemes, 802.1ag, and hybrid modes without requiring separate dedicated equipment for each protocol type.
Data Source
AI summary
A method of operation for a node of an Ethernet access network includes issuing a multicast message on the Ethernet access network by a maintenance end point (MEP) of the node. The multicast message contains a name of a target MEP. The node is further operable to receive a unicast reply message from the target MEP, the unicast message reply containing a MEP identifier (MEP-ID) and a MEP Media Access Control (MAC) address of the target MEP.