Ethernet OAM to MPLS Protocol Translation for Network Connectivity
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Troubleshooting network connectivity issues is challenging for service providers due to differences in networking technologies between their high-performance core networks and customer networks, which prevents automatic response to Operations, Administration, and Maintenance (OAM) messages across protocols like Ethernet and MPLS.
Innovation Solution
A system that enables the reception, interpretation, and response to Ethernet OAM messages, such as 802.1ag, in a core network utilizing MPLS, by configuring access devices and provider edge devices to translate Ethernet OAM messages into actions affecting the core network, allowing for proactive management of connectivity issues across different protocols.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Power
If service providers use different networking technologies for core networks and customer networks, then high-performance core network is achieved, but troubleshooting network connectivity issues becomes difficult
Solution Approach 1:
The patent introduces OAM (Operations, Administration, and Maintenance) messages as an intermediary mechanism that enables monitoring and troubleshooting across different network domains. These messages traverse the boundary between customer networks and service provider core networks, allowing service providers to detect and diagnose connectivity issues even when using different networking technologies (Ethernet vs. MPLS) in different network segments.
2Adaptability or versatility
If service providers cannot access or control customer networking equipment, then customer network autonomy is maintained, but automatic response to OAM messages across protocols is prevented
Solution Approach 1:
The patent employs protocol translation and mapping mechanisms as intermediaries that enable automatic OAM response without requiring direct access to customer equipment. The service provider network translates OAM messages between different protocols (Ethernet OAM to MPLS OAM), allowing automated response while respecting customer network autonomy and equipment control boundaries.
Solution Approach 2:
The patent changes the protocol parameters and message formats to enable cross-domain OAM functionality. By transforming OAM messages between different protocol suites while preserving the essential monitoring and diagnostic information, the system achieves automatic response capability across protocol boundaries without compromising customer equipment independence.
3Extent of automation
If protocol translation is implemented between Ethernet and MPLS, then automatic OAM response is enabled, but device complexity increases
Solution Approach 1:
The patent implements universal OAM message structures and standardized translation rules that can handle multiple protocol combinations (Ethernet to MPLS, and vice versa) through a single unified mechanism. This multi-functional approach reduces device complexity by avoiding the need for separate translation implementations for each protocol pair, as the same OAM framework handles all translations.
Data Source
AI summary
Network connectivity management includes monitoring a circuit, wherein the circuit is a virtual connection between multiple networks via a provider core network. A device receives a plurality of network management messages associated with the circuit, and a determination is made regarding whether the circuit is experiencing a connectivity issue based on the network management messages. When it is determined that the circuit is experiencing a connectivity issue, then certain actions can be initiated.