Positioning

Bluetooth 6.0 Channel Sounding vs UWB: What Accuracy Really Ships

New silicon makes BLE ranging real in 2026, but bandwidth physics still favors UWB. Where each wins, and why fusion patents settle asset tracking deals.

Hayat Amin, President of IP, Position Imaging Hayat AminPresident of IP, Position Imaging 5 min read
The short answer

Bluetooth 6.0 channel sounding, shipping in 2026 silicon like Nordic's nRF54L15 and NXP's KW47, delivers 10 to 30 cm accuracy in line of sight and 0.5 to 1 m or worse around metal and people. UWB still holds 10 to 30 cm through that same multipath because its 500 MHz channels resolve reflections that channel sounding's roughly 80 MHz span cannot. Channel sounding wins on tag cost and installed BLE infrastructure; UWB keeps precision use cases; patented fusion techniques decide contracts that demand p99 guarantees.

Key takeaways

  • Channel sounding spans about 80 MHz of 2.4 GHz spectrum; UWB channels are 500 MHz wide, and range resolution scales with bandwidth.
  • Expect 10 to 30 cm from channel sounding in line of sight and 0.5 to 1 m or worse around racking; UWB holds 10 to 30 cm through the same multipath.
  • Channel sounding wins on single-chip tag cost, coin-cell life, and reuse of installed BLE gateway infrastructure.
  • Pilot in your worst aisle and score p95 and p99 error, not the median from an open room.
  • No single radio meets a 99% accuracy clause; fusion with inertial, vision, and map-constrained filters does, and that layer is where granted patents concentrate.
  • Licensing proven positioning IP delivers the fusion layer plus freedom to operate in months instead of the 12 to 24 it takes to rebuild.

What accuracy does Bluetooth 6.0 channel sounding actually deliver?

Channel sounding, ratified in Bluetooth 6.0 in September 2024, measures distance two ways at once: phase-based ranging across up to 72 channels in the 2.4 GHz band, and round-trip time as a check against spoofed responses. The physics problem is bandwidth. Those 72 channels span roughly 80 MHz end to end, while a single 802.15.4z UWB channel is about 500 MHz wide. Range resolution scales with bandwidth, so a UWB receiver can separate a direct path from a shelf reflection arriving 2 nanoseconds later, while channel sounding has to estimate distance through the combined smear.

What that means in numbers:

  • Line of sight, open room: vendor demos on Nordic nRF54L15 and NXP KW47 silicon show 10 to 30 cm error. Believe those numbers in those conditions.
  • Real facilities: around steel racking, forklifts, and people, expect a median closer to 0.5 to 1 m, with occasional multi-meter outliers when the direct path is blocked and the strongest reflection wins.

Buyers get burned when the lobby demo becomes the spec they promise customers. Plan for the tail, not the demo.

Where does UWB still beat channel sounding outright?

UWB earns its accuracy in the time domain. A 500 MHz channel produces pulses around 2 nanoseconds long, so reflected paths that differ by 60 cm arrive as separate, distinguishable pulses. That is why systems built on Qorvo DW3000 or NXP Trimension parts hold 10 to 30 cm through the same multipath that pushes channel sounding past a meter, and why UWB error grows gradually instead of jumping when line of sight breaks.

Three requirements keep deals in the UWB column:

  • Sub-30 cm accuracy. Forklift anti-collision, robot docking, and bin-level pick verification sit below what 80 MHz of spectrum can deliver.
  • Dense, fast tag populations. TDoA infrastructure with UWB anchors tracks thousands of tags per zone at multiple updates per second. Channel sounding runs as a connected procedure per link, and nobody has published results at that tag density yet.
  • Secure ranging with a track record. The scrambled timestamp sequence in 802.15.4z already protects car access under the CCC Digital Key specification. Channel sounding's protections are newer and less field-tested.

Below 30 cm, UWB is still the answer.

Why channel sounding will still win plenty of 2026 deals

Cost structure, not accuracy, is channel sounding's weapon. The ranging capability lives in the same single-chip 2.4 GHz radio that already runs the BLE beacon: one SoC, one antenna, one coin cell that lasts years at typical asset-tracking update rates. A UWB tag adds a second radio, a second antenna, and a power budget that forces harder duty-cycling. That difference compounds across 20,000 pallets or 5,000 infusion pumps.

Infrastructure follows the same logic. Hospitals and warehouses that spent the last decade installing BLE gateways for RSSI-based zone tracking can move to real ranging by swapping tags and gateways to channel sounding silicon, staying inside one radio ecosystem instead of adding a parallel UWB anchor network with its own cabling and site survey.

So for requirements like "which room holds the pump" or "which aisle holds the pallet," where 1 to 2 m is genuinely sufficient, channel sounding will underbid UWB on price per tracked asset. Cheaper and good enough wins the RFP.

How should you pilot channel sounding against UWB?

Run the head-to-head in your worst aisle, not a conference room. A useful protocol:

  • Survey 20 reference points with a laser rangefinder, including positions behind racking, near metal walls, and at floor level where pallets actually sit.
  • Log raw per-link range estimates, not just the filtered position output, so you see what the radio delivers before software cleans it up.
  • Report median, p95, and p99 error separately. A 40 cm median with a 4 m p99 fails a search-and-find use case even though the average looks fine.
  • Add motion. Run forklifts through the test zone; both technologies degrade when large metal reflectors move.
  • Mount tags realistically. A tag against a metal surface or a liquid container, IV bags, beverage pallets, behaves nothing like one taped to a tripod.
  • Measure battery at the real ranging rate. A 1 Hz channel sounding schedule and a once-per-two-minutes schedule give very different coin-cell lifetimes.

Your worst aisle is the honest benchmark.

Why fusion patents decide who actually wins the deal

RFPs do not ask for a radio; they ask for guarantees. A typical clause reads like a percentile: locate any tagged asset within 2 m, 99% of the time, around the clock. Neither channel sounding nor UWB meets that alone through metal, liquid, and crowds. The systems that win layer techniques on top of the raw ranges:

  • Motion models and particle filters constrained by the facility map
  • Detection of non-line-of-sight links so bad ranges get down-weighted instead of averaged in
  • Fusion with inertial data on the tag, and with camera identification at chokepoints like dock doors
  • Handoff logic that keeps identity when an asset moves between radio zones

This processing layer, not the radio protocol, is where granted patents concentrate, because it is where a decade of hard-won methods lives. Two vendors can buy the same NXP silicon; the one with the better fusion stack posts the better p99 and takes the contract. The filter wins the deal, not the radio.

Should you build the fusion layer or license it?

Building it means hiring estimation and RF engineers, collecting months of labeled multipath data from real facilities, and then running freedom-to-operate analysis across a field that has been patented steadily since the early 2010s. Teams that go this route typically spend 12 to 24 months before their p99 numbers stabilize, and they still carry infringement risk on whatever methods they converge on, because good engineers rediscover the same solutions the patents already claim.

Licensing inverts that. Position Imaging licenses hundreds of granted patents across radio-frequency ranging, real-time positioning, computer vision, and machine learning, IP that Apple, Bosch, and other major firms cite in their own filings. Granted patents in the portfolio, including US 11,774,249, US 12,079,006, US 12,066,561, and US 12,000,947, cover positioning and tracking techniques that apply whether your radio is channel sounding, UWB, or both. You get proven methods plus freedom to operate in one agreement, and your team spends its time on product instead of re-deriving filters.

License the hard part, ship the product.

Patents referenced
US 11,774,249US 12,079,006US 12,066,561US 12,000,947

Frequently asked questions

Is Bluetooth 6.0 channel sounding accurate enough for warehouse asset tracking?

For aisle-level and room-level requirements, 1 to 2 m, yes, and it does that at BLE tag prices. For sub-30 cm jobs like bin-level verification or forklift safety, no, the 2.4 GHz band does not carry enough bandwidth. Match the radio to the percentile your contract actually specifies, not to the demo number.

Will channel sounding replace UWB in asset tracking?

No. It will take price-sensitive, meter-accuracy deployments away from both UWB and RSSI beacons, but UWB keeps every use case below 30 cm. Apple's AirTag already shows the likely pattern: BLE for cheap, always-on discovery and UWB for the final precise fix. Expect dual-radio designs, not a winner-take-all outcome.

Which chips support Bluetooth channel sounding in 2026?

Nordic Semiconductor's nRF54L series and NXP's KW47 family support it, with more vendors following. Channel sounding needs hardware support in the radio, so you cannot add it to already-deployed BLE 5.x tags with a firmware update. Tag fleets get replaced, not patched.

Does using channel sounding or UWB create patent risk?

The radio standards come with their participants' licensing commitments, but the processing layer on top, multipath rejection, sensor fusion, NLOS detection, tracking handoffs, is covered by granted patents held outside the standards bodies. That layer is where freedom-to-operate work should focus before you ship.

Can one tracking system use both channel sounding and UWB?

Yes, and high-end systems will. A common design uses channel sounding for low-cost, always-on coarse tracking across the whole fleet and reserves UWB anchors for zones that need sub-30 cm precision. The fusion methods that combine multiple ranging sources are exactly the techniques worth licensing rather than reinventing.

Talk to the IP team

Tell us what your product needs to locate and how precisely, and we will map it to the granted patents that fit.

Tell us the product. We map the exact scope, what a license covers, and how fast you can ship, all in a 20-minute call.

Book a 20-minute call