FlexE Client OAM Fields for Fault Isolation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Flexible Ethernet (FlexE) clients lack defined Operations, Administration, and Maintenance (OAM) functionality, limiting their ability to be transported and switched as a service in provider networks, which is critical for fault isolation and error checking, especially in applications requiring variable Ethernet rates.
Innovation Solution
Incorporating OAM fields into FlexE clients, including monitoring fields that use Bit Interleaved Parity (BIP) codes and multiframe schemes, to provide error checking and fault indication, independent of standard Local and Remote Fault information, and locating these fields in the Reconciliation Sublayer or frame headers.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If OAM functionality is added to FlexE clients, then fault isolation and error checking capability is improved, but device complexity increases
Solution Approach 1:
The patent segments OAM functionality into distinct fields (connectivity/trace field, link fault field, remote fault field, maintenance states field, test signals field) that can be independently implemented and managed within the FlexE client structure, reducing overall complexity while maintaining comprehensive fault isolation capability
Solution Approach 2:
The patent introduces an intermediary OAM layer between the physical transport layer and the Ethernet MAC layer, which mediates fault detection and error checking functions, allowing FlexE clients to gain OAM capabilities without fundamentally altering the existing Ethernet architecture
2Loss of energy
If FlexE clients are used as a service in provider networks, then cost and power consumption are reduced, but the need for layer 2 switching functionality is eliminated which may impact network flexibility
Solution Approach 1:
The patent extracts the essential OAM and fault management functions from the layer 2 switching plane and places them directly in the FlexE client service layer, eliminating the need for complex layer 2 switching while retaining the necessary network management and fault isolation capabilities
Solution Approach 2:
The patent changes the operational parameters of FlexE clients by introducing configurable OAM fields (such as connectivity/trace fields and test signals fields) that allow dynamic adjustment of monitoring and fault detection behavior, maintaining network adaptability through parameter configuration rather than structural complexity
3Measurement precision
If monitoring fields with BIP codes are implemented, then error checking precision is improved, but processing overhead increases
Solution Approach 1:
The patent implements partial error checking by applying BIP (Bit Interleaved Parity) codes selectively to specific critical fields within the FlexE client data stream rather than the entire data stream, achieving sufficient error detection precision while minimizing processing overhead and time loss
Data Source
AI summary
A node includes circuitry configured to create a sequence of encoded blocks with the blocks including i) data blocks from a plurality of clients and ii) overhead blocks, insert one or more Operations, Administration, and Maintenance (OAM) fields representing client overhead in the overhead blocks, wherein each client has corresponding client overhead, and transmit the sequence of encoded blocks in an order.