Control Plane Bridging for Up MEP CCM Processing

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Network devices lacking hardware capabilities for proper handling of Continuity Check Message (CCM) Protocol Data Units (PDUs) due to limitations such as the absence of Operation, Administration, and Management (OAM) processors or egress/ingress pipeline trapping/injection functionalities, hinder effective Layer 2 connectivity checks.

Innovation Solution

Implementing control plane bridging to facilitate the handling of CCM PDUs by bypassing data plane processing limitations, using software bridging to trap and inject CCM PDUs through control circuitry, thereby enabling proper transmission and reception even in hardware-limited network devices.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If network devices use hardware-based data plane processing for CCM PDU handling, then processing speed and efficiency are improved, but device complexity increases due to requirements for OAM processors and pipeline trapping/injection functionalities

Engineering Contradiction:

ImproveCCM PDU processing efficiencyVSAvoidhardware complexity

Core Design Contradiction:

ProductivityVSDevice complexity

Solution Approach 1:

The patent replaces the hardware-based data plane processing mechanism (requiring OAM processors and pipeline trapping/injection) with a software-based control plane bridging mechanism. The control circuitry emulates data plane bridging behavior through software control, allowing CCM PDU handling without specialized hardware components. This substitution resolves the contradiction by eliminating hardware complexity requirements while maintaining processing functionality.

Inventive Principle:

Principle #28Mechanics substitution (Replace mechanical system)

Solution Approach 2:

The patent introduces control circuitry as an intermediary between the data plane and control plane. This intermediary component performs CCM PDU trapping, processing, and injection through control plane bridging, eliminating the need for direct hardware support in the data plane. The control circuitry acts as a mediator that provides CCM handling capability without requiring complex hardware modifications.

Inventive Principle:

Principle #24Intermediary (Mediator)

2Adaptability or versatility

If network devices implement up MEP functionality without hardware support, then adaptability to different hardware configurations is improved, but reliability of CCM PDU handling deteriorates

Engineering Contradiction:

Improvehardware compatibilityVSAvoidCCM PDU handling reliability

Core Design Contradiction:

Adaptability or versatilityVSReliability

Solution Approach 1:

The patent replaces unreliable hardware-dependent CCM handling with a software-based control plane bridging approach. By implementing CCM PDU processing through control circuitry that emulates data plane bridging behavior, the system achieves reliable functionality without hardware support. The control plane mechanism ensures consistent CCM handling across different hardware configurations, resolving the reliability issue while maintaining adaptability.

Inventive Principle:

Principle #28Mechanics substitution (Replace mechanical system)

3Device complexity

If network devices use control plane bridging to handle CCM PDUs, then device complexity is reduced by eliminating hardware requirements, but processing speed decreases compared to hardware-based solutions

Engineering Contradiction:

Improvehardware complexityVSAvoidCCM PDU processing speed

Core Design Contradiction:

Device complexityVSSpeed

Solution Approach 1:

The patent accepts the speed trade-off by substituting hardware-based processing with control plane bridging. While software-based processing is inherently slower than hardware acceleration, the control circuitry optimizes the bridging process to minimize performance impact. This substitution is justified by eliminating hardware complexity requirements and enabling up MEP functionality on previously unsupported devices.

Inventive Principle:

Principle #28Mechanics substitution (Replace mechanical system)

Data Source

PatentUS20250300876A1Control Plane Bridging for Maintenance End Point (MEP)

Publication Date: 2025.09.25 ARISTA NETWORKS INC

AI summary

A network device may include a maintenance end point such as an up maintenance end point. The network device may include control circuitry that provides control plane bridging to facilitate the reception and transmission of continuity check messages by the up maintenance end point. For reception, the ingress processing pipeline for a peer interface with respect to the up maintenance end point may trap continuity check messages for control plane bridging. For transmission, the control circuitry may generate continuity check messages and perform control plane bridging prior to injecting the continuity check messages into the egress processing pipeline for the peer interface.