TL;DR
- ▸Neutral host operators face a particular timing challenge: many distributed sites where centralised PTP distribution isn't always practical.
- ▸Ballast Networks uses TimeBeat hardware at every cell site for local primary reference time clock without depending on transport-network PTP.
- ▸Edge-integrated GNSS timing eliminates transport-side PTP complexity at the cost of more GNSS receivers to operate.
The neutral host challenge
Neutral host operators deploy private 5G or shared infrastructure across many sites — venues, campuses, factories, public spaces — often in environments where centralised timing distribution isn't practical. Each site needs its own precision time source, and operating dozens or hundreds of independent grandmasters across a distributed footprint is operationally heavy if the architecture isn't designed for it.
Ballast Networks has built its operational model around edge-integrated GNSS timing. Rather than distributing PTP from a central reference across a transport network the operator may not control, Ballast deploys a TimeBeat grandmaster at every cell site with its own local GNSS reference. The architecture eliminates transport-side PTP complexity at the cost of more GNSS receivers to operate.
Why edge-integrated PRTC fits this use case
Three reasons. First, neutral host deployments often span sites with different transport providers, different network architectures and different operational ownership — the timing fabric can't depend on transport-side PTP support that may not exist. Second, the deployments are typically dense at each site (multiple radios needing precise sync) but sparse across sites, so a per-site grandmaster serves the local radios efficiently. Third, the operational model of running a local grandmaster per site fits neutral host's broader site-level provisioning model.
The trade-off is GNSS exposure. Every site has its own antenna, its own line-of-sight constraints, and its own potential for jamming or spoofing. Hardening the GNSS receiver and antenna at every site is more operational work than hardening a small number of central reference sites — but for the neutral host architecture, it's the right trade-off.
Where this fits
Edge-integrated PRTC is the right architecture when the transport-side PTP capability is uncertain, when each site is dense enough to justify a local grandmaster, and when the operational model already includes per-site provisioning. Neutral host deployments fit all three.
What the case study covers
The full case study covering the deployment architecture, the GNSS antenna placement strategy across the Ballast Networks footprint, the holdover characterisation under realistic outage scenarios, and the operational results is being written jointly with the Ballast engineering team. We'll publish it on the TimeBeat blog when the joint write-up is ready.
Frequently asked questions
What is a neutral host operator?+
Why does neutral host need its own timing fabric?+
Why edge-integrated GNSS instead of centralised PRTC?+
Related reading
Blog · Neutral host
Neutral Host in a Stadium
Stadium neutral host deployments have to deliver multi-operator coverage to tens of thousands of users on shared infrastructure. The timing fabric is what makes it work — and what most operators underestimate.
Blog · Neutral host
Indoor Dense Urban Neutral Host
Indoor dense urban neutral host deployments are the next frontier of shared mobile infrastructure. What the timing fabric has to look like to deliver multi-operator coverage in environments where GNSS doesn't reach.