Fronthaul Network Unit Synchronization During TDD Traffic Gaps
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing synchronization protocols in fronthaul networks suffer from Packet Delay Variation (PDV) due to synchronization messages competing with data packets in network switches, leading to inaccurate timing alignment and increased costs when using PTP-aware switches or TSN features.
Innovation Solution
A method for a fronthaul network unit to synchronize with another unit by obtaining control and local timing information to determine time intervals with low or high risk of competition with data traffic, allowing for more accurate synchronization by processing synchronization messages based on their susceptibility to delay variation.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Measurement precision
If synchronization messages are transmitted over the fronthaul network, then timing alignment is achieved, but packet delay variation increases due to competition with data packets in network switches
Solution Approach 1:
The patent segments synchronization messages into different priority levels (high-priority and low-priority messages) based on the timing criticality of the fronthaul traffic. High-priority synchronization messages are transmitted during periods when data traffic is minimal or absent, while low-priority messages are transmitted during periods when data traffic is active. This segmentation allows the system to maintain timing alignment accuracy by ensuring that critical synchronization messages are not delayed by data packet competition in network switches.
Solution Approach 2:
The patent implements dynamic priority assignment for synchronization messages based on the current state of fronthaul traffic. The system continuously monitors the timing characteristics of fronthaul traffic and dynamically adjusts the priority level of synchronization messages accordingly. When fronthaul traffic exhibits low timing variation, synchronization messages are transmitted with normal priority. When timing variation increases due to data packet competition, the system dynamically elevates the priority of synchronization messages to ensure accurate timing alignment is maintained.
2Reliability
If PTP-aware switches or TSN features are deployed to reduce packet delay variation, then synchronization accuracy improves, but network cost and complexity increase
Solution Approach 1:
The patent enables the fronthaul network to self-regulate synchronization message transmission by monitoring its own timing characteristics and dynamically adjusting message priority accordingly. The system uses locally available timing measurement data to determine when to transmit high-priority versus low-priority synchronization messages, eliminating the need for external PTP-aware switches or TSN features. This self-service approach maintains synchronization accuracy while avoiding the complexity and cost of specialized network infrastructure.
Solution Approach 2:
The patent changes the priority parameter of synchronization messages dynamically based on measured timing characteristics of the fronthaul traffic. By adjusting this single parameter (message priority) based on real-time conditions, the system achieves accurate synchronization without requiring changes to the physical network infrastructure. This parameter-based control approach replaces the need for complex hardware solutions with a flexible software-based mechanism.
Data Source
AI summary
A method performed by a first fronthaul network unit (RU1, RU2, . . . , RUm) for synchronizing with a second fronthaul network unit (GM; DU1, DU2, . . . , DUn) across a fronthaul network (100) carrying TDD radio transmissions through obtaining control information indicating UL and DL time periods of TDD radio transmissions and local timing information in a first fronthaul network unit and determining: a first set of synchronization messages transferred between the units within determined fronthaul DL and UL intervals during which there are no TDD transmissions, and a second set of synchronization messages transferred outside of the determined intervals, and synchronizing, based on the synchronization messages, depending on which set the synchronization message belongs to.