No active runs
xaitel-xem · us-east-2EKS Pilot

Release 15

The Release-15 Agnostic Client Bridge and the Celona Private 5G vendor profile. Any 3GPP Rel-15 core reaches XPF through five integration routes; the bridge is a compatibility and orchestration layer only — it computes no position and stores no fused location, and every route delegates the solve to XPF. Capability states are evidence-backed, unavailable capabilities return typed errors, and the quality class reported for a fix is what the evidence actually supports — sub-metre classes require a certified ground-truth benchmark.

Rel-15 client bridge — routes

Any 3GPP Release-15 core reaches XPF via these five routes. The bridge computes no position and stores no fused location — XPF stays authoritative.

A
LMF external solver
/xpf-bridge/v1/sessions
Session: buffer measurements → solve via XPF
B
GMLC bridge
/xpf-bridge/v1/gmlc/location
LCS privacy gate → XPF retrieval
C
NEF bridge
/xpf-bridge/v1/nef/location
Precision-tier entitlement + quota + metering
D
RAN / sensor sidecar
/xpf-bridge/v1/sidecar/measurements
Validate + forward to XPF ingest
E
Hybrid orchestrator
/xpf-bridge/v1/hybrid/locate
Core identity + external measurements → XPF
Route C — advertised capabilities (live)
Press Check to query the bridge.

Positioning readiness

What this deployment can actually do today, and the authorization gates in the way.

Celona capability discovery

Evidence-backed. A capability is never inferred AVAILABLE from chipset specs — the gated rows are the actual blockers to precision.

End-to-end locate

Celona → XPF locate

Serving-cell measurements → client bridge → device pseudonymised → canonical → real XPF fusion → honest quality class. Raw SUPI never reaches XPF.

APLatLonRSRP dBmTx dBmTA m