Bluetooth Channel Sounding Explained: How BLE Now Measures Distance

For a decade, BLE distance estimation has been a polite fiction. You ask an RSSI reading how far away a device is, and it answers with a shrug and a ±3-meter error bar. Engineers know this. They’ve spent years building workaround heuristics, fingerprinting databases, and multi-anchor triangulation schemes just to get RSSI to behave, and it still falls apart the moment someone opens a door or stands between the antennas. The entire industry accepted this as a fundamental limitation of the BLE radio.

It isn’t. Not anymore.

Bluetooth 6.0 introduced Channel Sounding, a link-layer ranging procedure that achieves 10–50cm accuracy using the same 2.4 GHz BLE radio already on your board. No second radio. No UWB. No additional RF front-end. For most products shipping BLE today (door locks, asset trackers, car keys, spatial audio devices) this changes the calculus on precision ranging entirely. Channel Sounding makes BLE a legitimate distance-measurement technology, and for the majority of use cases, it eliminates the need for UWB.

Here’s how it works, what accuracy you can actually expect, and when it does (and doesn’t) replace UWB.

What Channel Sounding Actually Is

Bluetooth Channel Sounding is a coordinated procedure where two BLE devices, an initiator and a reflector, exchange tones and timed packets across multiple frequency channels to compute the physical distance between them.

The critical distinction: this is a link-layer procedure, not an application-layer hack bolted on top of GATT. It lives in the controller, defined in the Bluetooth 6.0 Core Specification. The host interacts with it through new HCI commands, but the heavy lifting (tone generation, phase measurement, timing) happens in silicon.

You may encounter the name “HADM” (High Accuracy Distance Measurement) in older documentation. That was the working title during development. The official Bluetooth SIG name is Channel Sounding.

+---------------------------------------------+
|           Application Layer                  |
+---------------------------------------------+
|           Host (HCI commands for CS)         |
+---------------------------------------------+
|  Link Layer (Channel Sounding Procedure)     |  <-- CS lives here
+---------------------------------------------+
|  PHY (1M / 2M / Tone Exchange Extensions)    |
+---------------------------------------------+
|           2.4 GHz Radio                      |
+---------------------------------------------+

This architectural position matters. Because Channel Sounding is embedded in the controller, it benefits from hardware-level timing precision and doesn’t compete with application throughput. It’s not a software feature. It’s a radio feature.

The Two Measurement Engines Inside Channel Sounding

Channel Sounding’s accuracy comes from combining two independent measurement techniques that compensate for each other’s weaknesses. Understanding both is essential for evaluating what accuracy you can expect in your environment.

Phase-Based Ranging (PBR), Mode 2

In a Mode 2 step, the initiator and reflector exchange unmodulated continuous-wave tones across multiple BLE channels, up to 72 channels spanning the 2.4 GHz band.

At each channel frequency, both devices measure the phase of the received tone relative to their local oscillator. The phase difference at a given frequency is proportional to the distance, but a single-frequency phase measurement is ambiguous: it wraps every half-wavelength (~6.25 cm at 2.4 GHz). You can’t tell if the device is 10 cm or 16.35 cm away from one tone alone.

The solution is to measure phase across many frequencies. When you plot phase difference against frequency, the slope of that relationship maps directly to time-of-flight. Mathematically, this is equivalent to computing an inverse FFT across the frequency-domain phase measurements to resolve a time-domain distance estimate.

Advantage: Extremely fine distance resolution. Sub-centimeter precision is theoretically achievable from the phase data alone.

Limitation: Phase ambiguity at longer ranges, and susceptibility to multipath when used in isolation. A reflected signal path can shift the measured phase and corrupt the distance estimate.

Round-Trip Timing (RTT), Mode 1

In a Mode 1 step, the initiator transmits a sounding packet on the BLE 1M or 2M PHY. The reflector receives it and responds after a known, pre-agreed turnaround time. The initiator measures the total round-trip time and subtracts the turnaround delay to derive time-of-flight.

This is conceptually identical to UWB’s two-way ranging, just executed with a narrower-bandwidth BLE signal.

Advantage: Provides an absolute distance measurement with no ambiguity. RTT doesn’t wrap. It gives you a coarse but unambiguous range estimate regardless of distance.

Limitation: Coarser resolution than PBR. BLE’s signal bandwidth limits the timing precision, so RTT alone yields accuracy on the order of ~1 meter. Useful, but not competitive with UWB or PBR.

Combined Mode (Mode 3), Where the Precision Comes From

Mode 3 is the operational sweet spot, and it’s what most implementations will use. It interleaves PBR tone steps and RTT sounding steps within a single Channel Sounding procedure.

The logic is elegant: RTT provides a coarse but unambiguous distance estimate that resolves PBR’s phase ambiguity. PBR then refines that coarse estimate down to centimeter-level precision. Each technique patches the other’s blind spot.

The multi-channel frequency-hopping pattern adds a third layer of robustness. Because tones are exchanged across dozens of channels spread across 80 MHz of bandwidth, narrowband multipath fading on any individual channel gets averaged out. A reflected signal that corrupts the phase measurement on channel 14 has no effect on channel 57. This is the same principle that makes BLE’s frequency hopping resilient for data, applied here for ranging.

  Initiator                          Reflector
     |                                   |
     |--- RTT Sounding Packet ---------> |
     |<-- RTT Response Packet ---------- |  (Mode 1 step: measure round-trip time)
     |                                   |
     |--- Tone @ Ch 1 ~~~~~~~~~~~~~~~~> |
     |<-- Tone @ Ch 1 ~~~~~~~~~~~~~~~~~ |  (Mode 2 step: measure phase difference)
     |                                   |
     |--- Tone @ Ch 2 ~~~~~~~~~~~~~~~~> |
     |<-- Tone @ Ch 2 ~~~~~~~~~~~~~~~~~ |
     |          ...                      |
     |--- Tone @ Ch N ~~~~~~~~~~~~~~~~> |
     |<-- Tone @ Ch N ~~~~~~~~~~~~~~~~~ |
     |                                   |
     |--- RTT Sounding Packet ---------> |
     |<-- RTT Response Packet ---------- |  (additional RTT step)
     |                                   |
     v  [Combine PBR + RTT → Distance]  v

The result: high-accuracy BLE distance measurement from a single 2.4 GHz radio.

What Accuracy to Actually Expect

The Bluetooth SIG targets sub-meter accuracy, with sub-10cm achievable in favorable conditions. Here’s what early silicon is actually delivering:

In line-of-sight indoor environments, demos from Nordic (nRF54H20) and Infineon (CYW20829) show 10–30cm accuracy consistently. In cluttered non-line-of-sight conditions (through walls, around furniture, in warehouse aisles) accuracy degrades to 50cm–1m, which is still an order of magnitude better than RSSI.

These are early results. Algorithm improvements, better antenna characterization, and silicon maturation will push these numbers down. But even today’s performance is sufficient for the vast majority of BLE ranging applications.

An honest comparison:

The key row is “Requires Separate Radio.” That single line represents millions of dollars in BOM cost, board space, and RF design complexity across a product line.

Why Channel Sounding Is the Default Over UWB

This isn’t a close call for most products.

Channel Sounding wins on cost and simplicity. If your product already ships BLE (and nearly every connected product does) Channel Sounding is a silicon upgrade, not an architecture change. No second antenna. No additional RF matching network. No second power rail. For high-volume consumer products, eliminating a $1.50–$3.00 UWB module across a million units is $1.5–3M back on the table.

Channel Sounding wins on ecosystem scale. There are billions of BLE devices in the field, and every new BLE 6.0-capable device joins the Channel Sounding ecosystem automatically. UWB, despite years of investment from Apple, Samsung, and the CCC (Car Connectivity Consortium), remains a niche radio present in fewer than 10% of smartphones and almost no low-cost IoT devices.

Channel Sounding wins on power in always-connected scenarios. When two devices already maintain a BLE connection for data transfer, Channel Sounding piggybacks on that existing link. UWB ranging requires waking an entirely separate radio, which carries its own startup energy cost regardless of how efficient the ranging burst itself is.

Channel Sounding wins on accuracy for 90%+ of use cases. Access control (car keys, smart locks) needs to distinguish “within 1 meter of the door” from “across the parking lot.” Asset tracking needs room-level or zone-level accuracy. Find-my applications need directional proximity. None of these require <10cm precision at 10+ meters.

Where UWB still earns its place:

• Applications requiring <5cm accuracy at ranges beyond 10 meters: precision robotics, surgical tool positioning, or high-precision warehouse automation.
• Regulatory or certification contexts where UWB’s impulse-radio time-of-flight method is explicitly mandated (certain automotive Digital Key profiles during the transition period).
• Scenarios demanding simultaneous angle-of-arrival and distance with sub-millisecond latency in a single measurement cycle.

These are real requirements, but they describe a narrow slice of the ranging market. If your product’s accuracy spec reads “sub-meter” or “sub-50cm,” you don’t need UWB. Full stop.

What You Need to Build With Channel Sounding

Silicon: Channel Sounding requires PHY-level hardware changes. You cannot firmware-upgrade an existing BLE 5.x chip. Confirmed Channel Sounding–capable SoCs include the Nordic nRF54H20 and nRF54L series, Infineon AIROC CYW20829, TI CC2340 family, and Qualcomm QCC series. Dev kits are available now from multiple vendors.

Stack support: Since Channel Sounding is a controller-level feature, host-stack changes are minimal, primarily new HCI commands for configuring and triggering CS procedures. Zephyr has active Channel Sounding support in development. Vendor SDKs from Nordic and Infineon include early CS APIs. NimBLE support is on the roadmap.

Antenna design: This is where teams underestimate the effort. Phase-Based Ranging accuracy is directly sensitive to antenna phase-center stability. A PCB antenna with a poorly characterized or frequency-dependent phase center will inject systematic errors into every PBR measurement. Use a single-element antenna with a well-characterized, stable phase response across the 2.4 GHz band. Invest in antenna simulation early. This is not an afterthought.

Security: Channel Sounding includes a built-in CS Security Start procedure with random sequence generation, specifically designed to resist relay attacks. This directly addresses the vulnerability that plagued RSSI-based proximity detection and provides a BLE-native answer to UWB’s CCC Digital Key security profile. If relay-attack resistance is a requirement (automotive, access control), Channel Sounding has you covered at the spec level.

Topology: Channel Sounding is currently point-to-point (1:1 ranging). If you need full 2D/3D localization via multi-anchor triangulation, you’ll orchestrate multiple sequential ranging sessions at the application layer and fuse the results, the same approach UWB systems use today.

The Right Ranging Technology for Your Next Product

The default has shifted. For a decade, the answer to “how do I measure distance with BLE?” was “you don’t, not accurately.” Then it became “you add UWB.” The answer now is “you use Channel Sounding.”

If you’re in the evaluation phase for a new product, here’s what to do: get a Channel Sounding dev kit from Nordic or Infineon, run ranging tests in your actual target environment, and measure what accuracy you get. Compare that against your product’s accuracy requirement, not against UWB’s theoretical best-case number on a datasheet, but against what you actually need. For most teams, Channel Sounding will meet the bar.

If you’re currently shipping UWB and your accuracy requirement is ≥30cm, prototype a Channel Sounding replacement and quantify the BOM savings. At volume, the economics are compelling.

Bluetooth Channel Sounding will benefit from the same network-effect flywheel that made BLE dominant for wireless connectivity: more silicon vendors support it, more devices ship with it, more developers build on it, and the ecosystem compounds. UWB won’t have that flywheel. For precision BLE distance measurement, the pragmatic choice is the one that’s already on your board.

Hubble Network connects Bluetooth devices directly to satellites—extending BLE’s reach from meters to global coverage. See how it works →