FlexE Synchronization Data Mapping for Independent Client Timing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing FlexE networks face challenges in maintaining independent synchronization for each client due to alignment with the FlexE carrier frame, leading to loss of synchronization information and limitations in carrying synchronization information for clients with different synchronization sources.
Innovation Solution
Introduce a sync coder and decoder at the transmitter and receiver sides to map timing information of sync clients into FlexE payload, allowing synchronization information to be transmitted in available slots independent of FlexE frame timing, using a new type of sync client that transmits synchronization data in unallocated or FlexE client slots.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Device complexity
If synchronization data is transmitted aligned with FlexE carrier frame timing, then transmission structure is simplified, but synchronization information is lost and independent client synchronization cannot be maintained
Solution Approach 1:
The patent segments the FlexE payload into unallocated slots and client-allocated slots, allowing synchronization data to be transmitted independently in unallocated slots without being constrained by the overall FlexE carrier frame structure. This segmentation enables independent synchronization while maintaining the existing FlexE transmission framework.
Solution Approach 2:
The patent introduces an intermediary mechanism where synchronization data is mapped into available slots in the FlexE payload using a sync coder. This intermediary mapping layer allows synchronization information to be carried within the FlexE structure without direct alignment to carrier frame timing, resolving the conflict between structural simplicity and synchronization integrity.
2Reliability
If FlexE payload slots are strictly allocated to specific clients, then client data transmission is guaranteed, but synchronization data cannot be transmitted in allocated slots
Solution Approach 1:
The patent makes unallocated FlexE payload slots universally available for multiple purposes - they can serve as idle slots for future allocation or as carriers for synchronization data. This multi-functionality allows the same physical slots to adapt between data transmission and synchronization functions based on network needs, without compromising client data guarantees.
Solution Approach 2:
The patent introduces dynamic slot allocation where the function of unallocated slots can change over time. Slots that are currently unallocated can be dynamically used for synchronization data transmission, and can be reallocated to client data transmission when needed, providing flexibility while maintaining reliability for allocated slots.
3Reliability
If separate layer 2 synchronization protocols are used, then independent client synchronization is achieved, but system complexity and protocol overhead increase
Solution Approach 1:
The patent merges the synchronization function with the existing FlexE physical layer transport mechanism. By embedding synchronization data directly into unallocated slots of the FlexE payload using sync coder/decoder, the patent combines what would traditionally require separate layer 2 protocols into the layer 1 transport structure, reducing overall system complexity while maintaining independent synchronization capability.
Data Source
AI summary
Methods and apparatus are provided for transmitting synchronization data over a FlexE communications link. In an example aspect, a method of transmitting synchronization data over a FlexE communications link includes, in response to a synchronization event, selecting a next slot of the FlexE communications link that is unallocated or is allocated to a FlexE client, and transmitting synchronization data associated with the synchronization event in the selected slot.