Contact Us
  • Home
  • BLOG
  • Which Timing Does a 5G Radio Unit Need: SyncE or PTP?

Which Timing Does a 5G Radio Unit Need: SyncE or PTP?

Most 5G radio units need both, and the two carry different things. SyncE delivers frequency: one clock for every node in the chain. PTP delivers time and phase, which is what a TDD radio needs to put its uplink and downlink slots in the same place as its neighbours. A board that only has to hold a carrier, on an FDD radio or on a unit with its own GNSS receiver, can live on SyncE alone. A board that has to know when, in a cell that shares a frequency by time division, needs PTP with hardware timestamping, and it usually keeps SyncE underneath as the frequency reference that holds the servo through a GNSS outage.

The rest of the decision is a budget. A TDD network works to 1.5 microseconds against a common reference, 65 nanoseconds inside a MIMO array, and around 30 nanoseconds of allowed error per boundary clock. Those three numbers decide which parts go on the board.

What each one carries

SyncE is a physical layer job. The PHY recovers the clock from the incoming line, cleans it with a jitter attenuator and passes it to the next port, while ESMC messages carry the quality level so each node knows what it is following. Every node in the path has to be synchronous, and a node that is not breaks the chain for everything downstream. What SyncE never carries is a date: it hands you a ruler with the right spacing and no zero on it. A G.8262 Option 1 clock free runs at 4.6 ppm, which is 4.6 microseconds of slip every second.

PTP carries the zero. Sync messages are timestamped at the port, a servo in the slave steers its local clock, and boundary clocks at each hop timestamp on ingress and egress so that switch queueing does not land in the measurement. In the telecom profile with full on path support, G.82p is PTP aware and the default Sync rate is 16 messages a second, one every 62.5 milliseconds. G.8275.2 runs the same protocol with partial support, which is what a radio unit behind a network that is not PTP aware ends up using, with GNSS assistance at the edge.

Read as a pair, SyncE gives the spacing and PTP gives the zero.

Why the numbers are what they are

3GPP sets cell phase accuracy at better than 3 microseconds between cells that overlap on the same frequency, which a network reads as plus or minus 1.5 microseconds against a common reference. Inside one radio, time alignment error is 65 nanoseconds for MIMO and 260 nanoseconds for intra band contiguous carrier aggregation. Frequency accuracy for a wide area base station is 0.05 ppm.

Put the budget on a board and the parts show up. One microsecond is one part per million for one second, so a local oscillator at 0.5 ppm loses the whole 1.5 microsecond allowance in three seconds. Holding 1.5 microseconds across an hour of GNSS outage needs 0.42 ppb, which is a heated OCXO and not a TCXO. A phase locked loop cannot fix that, because the error is in the reference it is locked to.

Then the network side. Light in fibre runs at about 4.9 nanoseconds per metre, so 1.5 microseconds is 306 metres of path. Fibre is not symmetric: the two directions travel at different wavelengths and take slightly different routes, and the residual shows up as a fixed offset of a few nanoseconds per kilometre, which is why a PTP system carries an asymmetry constant somebody has to measure. A 10 GbE port holding 12 kilobytes in its queue delays a packet by 9.6 microseconds, six times the whole budget. That single number is why boundary clocks exist and why software timestamping cannot work.

Three ways these boards go wrong

Timestamping in software. A PHY without a PTP hardware clock, or a driver that timestamps in the network stack, adds jitter in the tens of microseconds before the servo ever sees it. No filter setting recovers 65 nanoseconds from that. The timestamp point has to sit close to the connector, in the PHY or the MAC, and the 1PPS output has to come out to a test point so the result can be measured against a reference.

A SyncE chain feeding a TDD radio. Every node synchronous, frequency inside 0.05 ppm, and no time origin anywhere in the chain. The radio comes up with an arbitrary frame start. One cell in a lab looks perfect. Two cells on the same frequency with overlapping coverage interfere, and the first symptom is throughput at the cell edge, not an alarm.

Holdover left to the cheap oscillator. A TCXO that holds 0.5 ppm is fine while GNSS or PTP is present and useless the moment it is not. An OCXO adds about a watt of heater power, wants thermal distance from the power amplifier, and needs the 1PPS path and the time of day link treated as timing nets rather than as ordinary digital signals. Boards that get this wrong pass every test in the lab and fail in the first site with a flaky uplink.

How SUPERB supports a timing board build

The carrier boards these modules sit on are not difficult in layer count and very difficult in tolerance. SUPERB PCB supports RF and high speed work to 68 layers, 0.05 mm lines and spaces, impedance held to plus or minus 5 percent and plus or minus 2 percent on critical nets, back drilled stubs at 0.25 mm, layer to layer registration of 0.025 to 0.06 mm, and a TDR coupon on every panel. Mixed stack ups with Rogers or PTFE cores and FR-4 are routine where a reference clock has to leave the digital section without picking up the switching noise around it.

SUPERB Assembly places and tests the module on seven SMT lines in a 5,000 square metre ESD controlled area, 01005 up to 57 mm at 40,000 CPH, with 3D SPI before reflow, 3D AOI after it, X-ray and CT to IPC-7095, twelve zone nitrogen reflow below 500 ppm oxygen, then ICT, flying probe and functional test on a fixture built for the product. Oscillators, GNSS modules and PHY devices come through 7,000 plus authorized channels with a 730 day warranty.

The 5G timing work sits on the SyncE timing distribution board and the IEEE 1588 PTP grandmaster board pages, with the network side described under 5G network synchronization. SUPERB Tech runs these builds as build-to-print from your Gerber, BOM and assembly drawing, with no engineering fee in the quotation.

What to send for a quote

Send the timing budget the radio has to meet, the PHY and PTP device you have chosen, the oscillator family, the 1PPS and time of day connectors, the stack up and the annual quantity. If the budget is not written down yet, send the deployment instead: how many hops to the grandmaster, whether GNSS is at the site, and how long a holdover has to last. The answer that changes the price is almost always the oscillator, and the oscillator is decided by the holdover number, not by the board.

Need a quote or a review of your files against these criteria? pcba@superb-tech.com · WhatsApp +86 133 9608 1443