PToB applies PTP principles to public BLE time broadcasts. Documented T096 configurations measured 70.197 and 76.359 ns uncentered PPS-shadow RMS; ESP32-S3 measured 319.5 ns internal published-prediction RMS in a normal 600-second run.
Published here on . Jonathan Yantis leads protocol design, hardware development, and research; GPT 6.1 contributes implementation, analysis, and documentation.
Results by device and measurement reference
These are separate tested configurations. Values remain in nanoseconds and use the statistic reported in the paper.
Nordic nRF52840 · Warm forward validation
Uncentered RMS
70.197 ns
Scoreable / physical observations
600 / 600
Mean absolute error
57.263 ns
Absolute P99 / maximum
158 / 192 ns
PPS-shadow query of the already-published BLE clock at a separately captured reference edge on the same local hardware counter. Common 10,516 ns edge correction trained separately and frozen before validation; no receiver-GPS training, validation refit, centering, or outlier deletion.
Nordic nRF52840 · Warm reverse validation
Uncentered RMS
76.359 ns
Scoreable / physical observations
598 / 599
Mean absolute error
60.376 ns
Absolute P99 / maximum
219 / 257 ns
PPS-shadow query of the already-published BLE clock at a separately captured reference edge on the same local hardware counter. The same separately trained, frozen 10,516 ns edge correction; one unscoreable causal query retained in the denominator.
Espressif ESP32-S3 · Normal 600-second run
Internal published-prediction RMS
319.5 ns
Scoreable / physical observations
359 / 359
Mean absolute error
244.5 ns
Absolute P99 / maximum
930 / 1010 ns
Internal causal prediction evaluated at physical target events using the previously published clock model. Controller-to-timer mapping.
Fine / coarse / unavailable clock views: 1,123 / 18 / 57 of 1,198 sampled views. Accuracy at scored events does not establish continuous clock availability.
A PPS-shadow query evaluates the already-published BLE clock at a separately captured pulse-per-second reference edge, on the same local hardware counter. The reference validates the BLE clock and does not train it. The reported T096 RMS includes bias; the validation data were not centered or refitted.
The ESP32-S3 result measures internal published predictions at physical target events. It uses a different timing path and measurement reference from the T096 result.
How to interpret these results
RMS describes the stated population; it is not a worst-case bound.
These measurements do not establish independently calibrated absolute UTC accuracy or independent electrical GPIO output accuracy.
The ESP32-S3 run has fine-clock publication gaps; internal prediction accuracy is distinct from continuous service availability.
Results apply to the named tested configurations and profiles, not every BLE MCU or multi-hop mesh path.
Cross-study RMS, MAE, standard deviation, and GPIO means use different references and conditions; they are not a matched output-accuracy or energy benchmark.
PToB proposes receive-only time acquisition, capability-dependent refinement, authorized grandmaster elections, and bounded mesh forwarding. It is not an adopted Bluetooth SIG or IEEE standard. Medical validation, broadcast genlock, holdover, and power qualification require separate evidence.
Source papers
The public proposal describes service profiles and the wire contract. The research preprint documents the calibration and measurements summarized here.