OAM Data Transmission in FlexE Systems
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
There is no effective OAM data transmission mechanism in communications systems that utilize flexible Ethernet (FlexE) technology or extended Ethernet technologies, hindering the transmission of OAM data across multi-hop devices.
Innovation Solution
The method involves creating a first data flow by deleting redundant blocks or modifying OAM data blocks in a second data flow, and inserting OAM data blocks to facilitate OAM data transmission across multi-hop nodes, ensuring a fixed relative sequence of valid data blocks and enabling OAM data transmission in communications systems using FlexE or extended Ethernet technologies.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If OAM data transmission mechanism is implemented in FlexE technology, then fault detection capability is improved, but device complexity increases
Solution Approach 1:
The patent segments OAM data into discrete OAM data blocks that are inserted into specific timeslots of the FlexE group. Each OAM data block is independently transmitted and can be separately detected, enabling fault detection without requiring complex end-to-end OAM mechanisms across the entire FlexE interface.
Solution Approach 2:
The patent introduces an intermediary mechanism where OAM data blocks are inserted into the data flow between the FlexE client layer and the physical medium. These OAM blocks act as mediators that carry fault detection information through the FlexE timeslots without requiring modification of the underlying FlexE protocol stack.
2Reliability
If OAM data blocks are inserted into data flow, then OAM data transmission is enabled, but data flow complexity increases
Solution Approach 1:
The patent implements periodic insertion of OAM data blocks into the data flow at regular intervals within the FlexE timeslots. This periodic action enables continuous OAM data transmission while maintaining a predictable and manageable data flow structure that does not require complex real-time processing.
Solution Approach 2:
The patent applies local quality by inserting OAM data blocks only in specific timeslots of the FlexE group rather than uniformly across all timeslots. This allows OAM data transmission to be enabled where needed while keeping the overall data flow structure simple and maintaining compatibility with existing FlexE operations in other timeslots.
3Productivity
If redundant blocks are deleted and OAM blocks are inserted, then OAM data transmission efficiency is improved, but data flow modification complexity increases
Solution Approach 1:
The patent discards redundant blocks from the data flow and recovers their space by inserting OAM data blocks in their place. This approach improves OAM data transmission efficiency by utilizing otherwise wasted bandwidth while the modification process is simplified by following predetermined rules for block deletion and insertion positions.
Solution Approach 2:
The patent performs preliminary actions by pre-defining which timeslots will carry OAM data blocks and which redundant blocks should be deleted. This preliminary configuration simplifies the actual data flow modification process during operation, as the system only needs to follow the pre-established pattern rather than making complex real-time decisions about block management.
Data Source
AI summary
The present disclosure relates to operation, administration and maintenance (OAM) data transmission methods and apparatuses. One example method includes obtaining, by a first node, a first data flow of a client. The first node inserts an OAM data block in the first data flow of the client to obtain a second data flow of the client, where the OAM data block is a 64B/66B code block that carries OAM data. The first node distributes the second data flow of the client to at least one slot of a channel corresponding to the client.