What Is Bluetooth Channel Sounding?

For years, Bluetooth products have tried to answer a simple question with a very imperfect tool:

How far away is the other device?

The usual answer was RSSI, or Received Signal Strength Indicator.

Strong signal? Probably close.

Weak signal? Probably far away.

That is useful for rough proximity. It is not a great ruler.

Put the phone in a pocket. Close the plastic enclosure. Add a battery near the antenna. Turn around. Walk behind a wall. Mount the product beside metal.

The RSSI number changes.

Sometimes it changes enough to make a product behave strangely.

Bluetooth Channel Sounding exists because "nearby" is not precise enough for many modern products. A smart lock, a digital key, a tool tracker or a medical asset workflow may need to know distance, not just signal strength.

Why RSSI was never enough

RSSI is attractive because almost every BLE product can read it.

It is also dangerous because it looks more precise than it really is.

A product team may test a BLE prototype on a desk and decide:

If RSSI is stronger than this value, the user is close.

Then the product goes outside the lab.

The same phone produces different RSSI values depending on orientation, clothing, human body blocking, room reflections, enclosure material, antenna tuning and nearby metal. The device did not necessarily move. The radio environment changed.

That is why RSSI works better for questions like:

• Is this device roughly nearby?
• Is the signal improving or getting worse?
• Should we show a near/far hint?

It works less well for questions like:

• Is the user within 30 cm?
• Is the key inside the car or outside the car?
• Which asset is closest to this workstation?
• Should this door unlock now?

Those are distance questions. RSSI is a signal-strength measurement.

What Channel Sounding changes

Bluetooth Channel Sounding changes the product conversation from:

Can I hear the device?

to:

Can I estimate how far away the device is?

That sounds like a small difference. It is not.

Once distance becomes a usable input, the product can make better decisions:

• unlock only when the key is close enough
• guide a user during the final few metres of finding an item
• understand which tool is closest to an operator
• trigger smart-home behaviour based on distance, not only presence
• reduce false positives in proximity authentication

Bluetooth SIG introduced Channel Sounding with Bluetooth Core 6.0. The feature uses two main ranging methods: Phase-Based Ranging and Round-Trip Timing. Bluetooth SIG also describes Channel Sounding as a secure, fine-ranging feature for Bluetooth LE.

RSSI vs Bluetooth Channel Sounding

The important word is capable.

An existing BLE product does not automatically become a Channel Sounding product because it uses Bluetooth. The controller, SDK, stack, antenna design, host APIs and the other device all matter.

How Bluetooth Channel Sounding works

At a high level, two devices take part in the ranging procedure.

Bluetooth commonly describes them as:

• Initiator: the device that starts the Channel Sounding procedure
• Reflector: the device that participates and reflects/responds during the procedure

The devices exchange special radio signals. Those measurements are then used to estimate distance.

There are two core ideas behind the measurement.

Phase-Based Ranging

Phase-Based Ranging, often shortened to PBR, is the most interesting part for many product teams.

The initiator and reflector exchange signals across multiple Bluetooth frequencies. As a radio wave travels, its phase changes. By comparing phase measurements across frequencies, the system can estimate how far the signal travelled.

Very simplified:

Send signal
Measure phase
Change frequency
Measure again
Repeat across channels
Estimate distance from the pattern

Using multiple frequencies matters because one RF measurement can be misleading. Reflections, nearby surfaces and antenna orientation can distort the picture. Multiple measurements give the ranging algorithm more evidence.

This is where product engineering becomes important. Bluetooth can produce measurements, but the final ranging performance depends on the device design and how the measurement data is processed.

Round-Trip Timing

Round-Trip Timing, or RTT, is easier to picture.

Device A sends a signal. Device B responds. The system measures the round-trip time.

A --------------> B
A <-------------- B

time of flight -> distance clue

In Channel Sounding, RTT is not only about another way to estimate distance. It also helps with secure distance bounding.

That matters because some proximity systems are vulnerable to relay attacks. A criminal may try to relay communication between a real key and a lock or car, making the system believe the key is nearby when it is not.

Channel Sounding is designed with secure ranging in mind, which is why it is especially interesting for digital keys, access control and proximity-based authentication.

Where Channel Sounding can be useful

The best use cases are not "we want Bluetooth 6".

The best use cases are products where distance changes the decision.

Digital keys and access

A digital key should not unlock something only because a phone can be detected.

It should unlock when the phone is close enough, in the right place and inside the intended usage flow.

That could apply to:

• cars
• smart locks
• office access
• hotel rooms
• industrial machines
• secure equipment cabinets

Channel Sounding gives designers another tool for making that decision more robust.

Find My and asset tracking

Traditional BLE trackers can tell you an item is nearby.

That is helpful until you are standing in the room and still cannot find it.

Distance-aware Bluetooth can improve the final search experience. Instead of only showing "near" or "far", a product can guide the user with a better estimate of how close they are.

This does not automatically mean perfect indoor positioning. It means the last few metres can become less vague.

Industrial tools and workflows

In a factory, warehouse or service environment, distance can become part of the workflow.

For example:

• Which tool is closest to this station?
• Is the operator near the machine before enabling an action?
• Has a calibrated instrument left its expected area?
• Which device should this gateway connect to first?

For industrial products, the challenge is usually not the demo. It is making the behaviour repeatable around machines, metal, human movement and noisy RF conditions.

Medical and healthcare assets

Hospitals and clinics often have many movable assets: pumps, monitors, carts, portable diagnostic devices and emergency equipment.

Better proximity and distance information can help with finding assets, guiding staff and reducing time wasted searching for equipment.

But healthcare environments also raise the bar for validation. If the product affects clinical workflow, the distance feature has to be tested like a real system feature, not a nice UI enhancement.

Smart-home experiences

Presence is useful.

Distance is more useful.

A smart-home product can behave differently when a user is across the room, beside the device or walking away. That can make interfaces feel less mechanical and more context-aware.

The trick is restraint. If the product reacts too eagerly, it becomes annoying. Good distance-aware design needs stable thresholds, hysteresis, fallback behaviour and a clear reason to use ranging in the first place.

Does Channel Sounding replace UWB?

Not automatically.

Ultra-Wideband already has a strong position in precise ranging and secure access applications. Bluetooth Channel Sounding gives product teams another option, especially because Bluetooth is already present in phones, laptops, wearables, cars, gateways and IoT accessories.

That ecosystem advantage is real.

But the right choice still depends on:

• required accuracy
• required distance
• power budget
• phone and platform support
• security model
• BOM cost
• antenna constraints
• certification path
• user experience
• field environment

There is no universal winner.

Can an existing BLE product use Channel Sounding?

Not automatically.

Bluetooth Channel Sounding is an optional Bluetooth LE controller feature. Both sides of the procedure need the required capability. Product teams should check support across the full chain, not only the chip headline.

Before you plan around Channel Sounding, verify:

• MCU or radio support
• Bluetooth controller support
• SDK support
• mobile operating system support
• host APIs
• antenna and enclosure constraints
• calibration needs
• measurement data access
• ranging algorithm availability
• certification and qualification implications

One easy mistake is to assume the Bluetooth specification gives you a complete product algorithm.

It does not.

Bluetooth defines the measurement capability. The product still needs to turn those measurements into decisions that behave correctly in the real world.

What changed after Bluetooth Core 6.0?

Channel Sounding did not stop at its first release.

Bluetooth Core 6.0 introduced the feature. Bluetooth Core 6.3, released in May 2026, added Channel Sounding improvements including Inline PCT Transfer and PHY-specific RTT accuracy reporting.

In normal product language, that means the feature is still maturing. The Bluetooth ecosystem is improving how ranging information is generated, reported and used.

For a product team, that is both exciting and slightly inconvenient.

Exciting because the capability is becoming stronger.

Inconvenient because you must check the actual silicon, SDK, phone support and stack behaviour available for your launch timeline.

Product questions before using Channel Sounding

Ask these before making it part of the product architecture:

The useful way to think about it

Bluetooth used to answer:

Can these two devices communicate?

Channel Sounding lets Bluetooth products start asking:

How far apart are they?

That changes the product design space.

Before

Device detected?
   -> yes / no

With distance awareness

Device detected?
   -> how far?
   -> is that distance trusted?
   -> what should the product do now?

This is the real shift. Distance becomes another input into the product logic.

Final thought

RSSI was never a very good ruler.

Bluetooth Channel Sounding gives BLE products a better way to reason about distance while staying inside the Bluetooth ecosystem.

For digital keys, access control, asset finding, industrial tools, smart homes and connected medical workflows, that opens genuinely useful product possibilities.

But the hard part will not be making it work once on a clean bench.

The hard part will be making it work reliably inside the enclosure, around people, near metal, across environments and in the final product.

That is where the engineering work lives.

References

• Bluetooth SIG: Bluetooth Channel Sounding
• Bluetooth SIG: Bluetooth Core 6.0 feature overview
• Bluetooth SIG: Bluetooth Core 6.3 release notes