Application Overview
5G networks require precise timing synchronization to support demanding applications including Carrier Aggregation (CA), Coordinated Multi-Point (CoMP), and Time Division Duplexing (TDD). The synchronization requirement varies by deployment scenario: eMBB applications typically require 1.5μs timing accuracy, while URLLC ultra-reliable low-latency communications demand sub-1μs precision. This reference design provides a complete solution for 5G small cells and macro base stations, ensuring compliance with 3GPP TS 38.133 specifications for both frequency and phase synchronization.
The architecture addresses the critical challenge of maintaining timing accuracy during GNSS outages through advanced holdover capabilities. Modern 5G networks must handle various interference scenarios, including jamming and spoofing attacks on GNSS signals, making robust backup timing sources essential for network reliability. This design integrates GNSS discipline with high-stability rubidium oscillators to deliver carrier-grade synchronization performance.
System Architecture
+------------------+
| GNSS Antenna |
| (GPS/BeiDou) |
+--------+---------+
|
v
+------------------+
| STW-TD |
| Satellite Time |
| & Frequency |
| Equipment |
+--------+---------+
|
+--------------+--------------+
| |
v v
+------------------+ +------------------+
| STM-Rb-N | | STW-NT |
| Rubidium Clock |<-------->| Network Time |
| (Holdover Ref) | 1PPS | Server (PTP/NTP)|
+--------+---------+ +--------+---------+
| |
| 10MHz | PTP/NTP
v v
+------------------+ +------------------+
| STZ-PF | | PTP Switch |
| Frequency |==========>| (Boundary/ |
| Distributor | | Transparent) |
+--------+---------+ +--------+---------+
| |
+--------+---------+ +--------+---------+
| | | | | |
v v v v v v
[BBU1] [BBU2] [BBU3] [Cell1] [Cell2] [Cell3]
5G NR 5G NR 5G NR Small Macro MacroSignal Flow Description
- Primary Path (GNSS Disciplined): GNSS antenna receives satellite signals → STW-TD extracts precise timing → disciplines STM-Rb-N via 1PPS → rubidium output feeds STZ-PF distributor → distributed to BBU units
- Backup Path (Holdover): Upon GNSS loss, STM-Rb-N maintains frequency accuracy via internal atomic reference → STW-NT continues PTP/NTP distribution → network elements experience seamless transition
- Network Distribution: STW-NT generates PTP packets with hardware timestamps → PTP-aware switches maintain timing accuracy → end devices receive sub-microsecond synchronization
Key Design Decisions
1. Dual-Constellation GNSS Reception
Using STW-TD with BeiDou/GPS/GLONASS multi-constellation support provides resilience against single-constellation failures and improves availability in challenging RF environments. The STW-TD includes built-in interference and spoofing detection to identify compromised timing sources.
Decision Rationale: Urban canyon environments often have partial sky visibility; multi-constellation increases position fix availability from ~60% (single GPS) to >95% (multi-GNSS).
2. Rubidium Holdover Architecture
The STM-Rb-N rubidium clock provides frequency stability of ≤3×10⁻¹²/τ, enabling holdover performance better than 1μs over 24 hours after GNSS loss. This exceeds 3GPP requirements for most deployment scenarios.
Decision Rationale: Critical infrastructure requires timing continuity during GNSS outages caused by weather, interference, or scheduled maintenance.
3. Hardware Timestamping Distribution
STW-NT implements hardware timestamping for both PTP and NTP packets, achieving ≤25ns accuracy to UTC. Software-based solutions typically exhibit 100-500μs variability due to OS scheduling.
Decision Rationale: URLLC use cases demand deterministic timing that only hardware timestamping can guarantee.
4. Frequency Distribution with Phase Preservation
The STZ-PF frequency distributor maintains channel-to-channel phase jitter below 3fs, ensuring that distributed 10MHz references maintain coherence across multiple BBU units for carrier aggregation.
Decision Rationale: CoMP and CA require phase-coherent references; even 10fs of added jitter would degrade performance.
Bill of Materials (BOM)
| Item | BRIDZA Model | Function | Qty | Notes |
|---|---|---|---|---|
| ------ | ------------- | ---------- | ----- | ------- |
| GNSS Timing Receiver | STW-TD | Multi-constellation GNSS timing, PTP Grandmaster | 1 | 1U form factor, ≤10ns RMS accuracy |
| Rubidium Frequency Standard | STM-Rb-N | Holdover oscillator, frequency reference | 1 | 1PPS disciplining, ≤3×10⁻¹²/τ stability |
| Frequency Distributor | STZ-PF | Multi-channel frequency distribution, phase preservation | 1 | ≤3fs channel jitter, 4+ outputs |
| Network Time Server | STW-NT | PTP/NTP generation, network timing distribution | 1 | >140,000 NTP/sec, PTP Master mode |
| Coaxial Cable | - | RF connections (not supplied) | As required | 50Ω impedance, low loss |
| GNSS Antenna | - | GNSS signal reception (not supplied) | 1 | Active antenna with LNA |
Performance Targets
| Parameter | Requirement | Achieved | Notes |
|---|---|---|---|
| ----------- | ------------ | ---------- | ------- |
| SyncE Frequency Accuracy | ±4.6×10⁻⁶ | ±1×10⁻¹² | After GNSS discipline |
| Phase Sync (eMBB) | ≤1.5μs | ≤100ns | Hardware timestamp via PTP |
| Phase Sync (URLLC) | ≤1μs | ≤50ns | With STW-TD internal correction |
| Holdover (24h) | <1.5μs | <500ns | STM-Rb-N holdover performance |
| GNSS to UTC | <100ns RMS | <10ns RMS | STW-TD specification |
| PTP Accuracy | <1μs | <100ns | Hardware timestamp |
| NTP Accuracy | <1ms | <25ns | Hardware timestamp |
Implementation Notes
Physical Installation
The STW-TD and STW-NT are designed for 1U-3U rack installation in telecom equipment rooms. Ensure adequate ventilation (minimum 1U spacing between units). The STM-Rb-N can operate in 1U rack mount or bench configuration. All units support dual redundant power inputs for carrier-grade reliability.
GNSS Antenna Placement
GNSS antenna should be installed with clear sky view (minimum 30° elevation to horizon) to maximize satellite visibility. The antenna should be grounded properly and located away from potential interference sources including radar systems and strong RF transmitters. STW-TD supports up to 100m cable runs with appropriate amplification.
Network Configuration
For PTP deployment, configure STW-NT as Boundary Clock (BC) or Transparent Clock (TC) based on network topology. For NTP-only scenarios, STW-NT can serve >140,000 clients per second without accuracy degradation. VLAN segregation is recommended for timing traffic to ensure QoS prioritization.
Holdover Configuration
The STM-Rb-N should be disciplined for minimum 24 hours before entering holdover mode to achieve optimal drift performance. STW-TD continuously monitors GNSS health and automatically transitions between disciplined and holdover states. Alarm outputs can trigger network management notifications.
Test & Verification Approach
Synchronization Testing
- PTP Path Delay Measurement: Use PTP analyzers to measure end-to-end synchronization error, verifying <100ns requirement
- Frequency Accuracy Test: Measure 10MHz output against reference cesium standard over 24-hour period
- Holdover Test: Disconnect GNSS antenna, measure timing drift over 24-72 hours
- Recovery Test: Reconnect GNSS, verify <1 hour lock time and <100ns final accuracy
Network Integration Test
- PTP Traffic Analysis: Monitor PTP packets with Wireshark, verify hardware timestamps
- NTP Query Test: Use ntpq -p to verify stratum level and offset
- Failover Test: Simulate primary failure, verify automatic switchover and alarm generation
Alternative Configurations
High-Capacity Option (Stadium/Venue)
For venues requiring >100 small cells, add STZ-MF pulse distributor for 1PPS distribution to multiple STW-NT units. This architecture scales horizontally while maintaining timing accuracy.
Additional Components: STZ-MF (2-in/16-out PPS distribution)
Cost-Optimized Option (Rural/Microwave Backhaul)
For areas with existing microwave timing, replace STW-TD with GNSS-disciplined OCXO module. Reduces cost by ~60% while maintaining <5μs accuracy suitable for rural eMBB deployments.
Component Changes: Replace STW-TD with GNSS-disciplined OCXO (third-party)
Enhanced Holdover Option (Critical Infrastructure)
For extremely long GNSS outage scenarios, add second STM-Rb-N in hot-standby configuration with STZ-SC seamless switch. Achieves <100ns drift over 7 days.
Additional Components: STM-Rb-N (secondary), STZ-SC seamless switch