Emulating UP MEPs with Hardware DOWN MEPs for Service Continuity
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current networking solutions face challenges in implementing scalable and compliant UP MEP functionality for monitoring service continuity across maintenance domains, as existing hardware-based solutions primarily offer DOWN MEP functionality, which does not meet the requirements for monitoring service connectivity between the entry and exit of maintenance domains, and software-based solutions fail to comply with warm restart requirements.
Innovation Solution
The system emulates a hardware UP Maintenance End Point (MEP) using one or more hardware-based DOWN MEPs, with processing circuitry configured to create and manage Continuity Check Messages (CCMs) between DOWN MEPs, allowing for accurate state maintenance and compliance with IEEE 802.1ag standards, even across different hardware units, and adjusts CCM transmission based on Spanning Tree Protocol or G.8032 Ethernet Ring Protection Protocol state transitions.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If hardware-based DOWN MEP functionality is used, then scalability and hardware integration are improved, but the ability to monitor service connectivity between entry and exit of maintenance domains (UP MEP functionality) deteriorates
Solution Approach 1:
The patent makes hardware DOWN MEP circuitry perform both DOWN MEP monitoring and UP MEP monitoring functions by emulating UP MEP behavior through software configuration on top of hardware DOWN MEP entities, allowing a single hardware component to serve multiple monitoring purposes
Solution Approach 2:
The patent creates virtual copies of UP MEP entities using software that run on top of hardware DOWN MEP circuitry, where the software emulation layer replicates UP MEP functionality without requiring separate dedicated hardware for each MEP type
2Adaptability or versatility
If additional hardware (NPU, FPGA) is deployed to implement UP MEP functionality, then service connectivity monitoring capability is improved, but device complexity and cost increase
Solution Approach 1:
The patent enables existing hardware DOWN MEP circuitry to perform both DOWN MEP and UP MEP monitoring functions through software configuration, eliminating the need for separate NPU or FPGA resources and reducing overall device complexity
Solution Approach 2:
The hardware DOWN MEP entities serve themselves by having software emulate UP MEP functionality on top of them, allowing the same hardware resource to provide multiple monitoring services without requiring additional dedicated hardware components
3Adaptability or versatility
If software-based UP MEP solutions are used, then UP MEP functionality is achieved, but compliance with warm restart requirements and scalability deteriorate
Solution Approach 1:
The patent creates software-emulated UP MEP entities that run on top of hardware DOWN MEP circuitry, where the software layer provides the necessary flexibility for warm restart compliance while the hardware layer ensures scalability and reliability
Solution Approach 2:
The hybrid architecture allows the system to leverage hardware reliability for warm restart compliance while maintaining software flexibility, enabling the same infrastructure to provide both UP MEP functionality and meet operational requirements
Data Source
AI summary
A node configured to emulate a hardware UP Maintenance End Point (MEP) using one or more DOWN MEPs includes a plurality of ports; a switching fabric configured to switch data between the plurality of ports; and processing circuitry communicatively coupled to the plurality of ports and configured to emulate an UP MEP on a first port of the plurality of ports using at least a first DOWN MEP on a second port of the plurality of ports. The DOWN MEP can be implemented in hardware on the second port and the processing circuitry can be configured to execute application software configured to emulate the UP MEP.