Virtual Maintenance Endpoint for Legacy OAM Interworking
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The existing Ethernet connectivity fault management protocols, such as IEEE 802.1ag, assume every node has a MAC address and supports the full protocol suite, which is not feasible for customer premises equipment (CPE) in broadband access networks using legacy link OAM schemes like ATM OAM, making it difficult for service providers to check physical connection paths between Residential Gateways and Broadband Network Gateways.
Innovation Solution
The introduction of virtual Maintenance Endpoints (vMEPs) that emulate MEPs on broadband access nodes, allowing the use of legacy OAM loopback messages for integrity checks and signaling response states within the Ethernet access network using 802.1ag continuity check messages, enabling seamless interworking between 802.1ag CFM and legacy link level OAM schemes.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If IEEE 802.1ag CFM protocols are used for Ethernet OAM, then connectivity fault management capability is improved, but compatibility with legacy CPE equipment using ATM OAM is lost
Solution Approach 1:
The patent introduces a virtual Maintenance Endpoint (vMEP) as an intermediary entity that resides on the service provider's network equipment (BRAS or BBNG). This vMEP acts as a mediator between the 802.1ag CFM system and legacy ATM OAM CPE equipment. The vMEP translates and forwards OAM messages, enabling the service provider to perform connectivity fault management using standard 802.1ag protocols while maintaining compatibility with legacy CPE that only supports ATM OAM or basic Ethernet OAM without full 802.1ag implementation.
2Reliability
If full 802.1ag protocol suite is implemented on every node, then OAM functionality is improved, but device complexity and cost increase
Solution Approach 1:
The patent segments the OAM functionality by separating the full 802.1ag CFM implementation from the CPE equipment and concentrating it on the service provider's network infrastructure. Instead of requiring every node (including legacy CPE) to implement the complete 802.1ag protocol suite, the functionality is divided such that the service provider's BRAS/BBNG devices handle the complex CFM operations while CPE devices can use simpler legacy ATM OAM or basic Ethernet OAM. This segmentation reduces device complexity and cost for CPE while maintaining full OAM functionality in the service provider network.
3Adaptability or versatility
If legacy ATM OAM schemes are used in broadband access networks, then compatibility with existing CPE is maintained, but ability to perform end-to-end connectivity checks is reduced
Solution Approach 1:
The patent creates a virtual copy of a Maintenance Endpoint on the service provider's network equipment. This vMEP replicates the functionality needed for end-to-end connectivity checks without requiring the physical CPE to support full 802.1ag. The virtual MEP on the BRAS/BBNG can generate and process CFM OAM messages, effectively copying the endpoint functionality to where it is most useful for service provider monitoring and management, thereby enabling end-to-end connectivity checks while maintaining compatibility with legacy CPE.
Data Source
AI summary
A broadband access node includes a port for connection with a Digital Subscriber Line and a processor to run code that implements a virtual maintenance end point (vMEP). The vMEP translates an IEEE 802.1ag Loopback Message (LBM) received from a device on an Ethernet access network into a legacy operations and maintenance (OAM) message that is transmitted to a residential gateway (RG) device. The legacy OAM message determines a link-level connectivity status between broadband access node and the RG device. The vMEP also transmits a reply message back to the device on an Ethernet access network in compliance with the IEEE 802.1ag specification. It is emphasized that this abstract is provided to comply with the rules requiring an abstract that will allow a searcher or other reader to quickly ascertain the subject matter of the technical disclosure. It is submitted with the understanding that it will not be used to interpret or limit the scope or meaning of the claims. 37 CFR 1.72(b).