Today the Bluetooth SIG officially adopted the latest Bluetooth 6.3 specification. It doesn’t introduce any major changes, but adds improvements in four key areas, especially the Bluetooth Channel Sounding introduced in Bluetooth 6.0:
- Channel Sounding Inline PCT Transfer
- PHY-specific RTT accuracy improvements
- Fixes for “running out of bits” in protocol signaling
- RF requirement harmonization (ACP and C/I limits)
These may sound subtle changes, but they address real limitations we developers have been dealing with when trying to build productions with Bluetooth. Let’s break each one down.
Channel Sounding Gets an Upgrade
Channel sounding was the headline feature of Bluetooth 6.0. It allowed two devices to measure distance with far greater accuracy than RSSI-based methods. Now Bluetooth 6.3 improves this capability in a meaningful way but solving a few issues that have been limiting the usefulness of CS.
The Problem with Traditional Channel Sounding
In earlier implementations, Bluetooth channel sounding required a lot of digital post-processing to correct phase errors. This worked, but cause some issues:
- Higher processing overhead
- Increased latency
- Sensitivity to oscillator errors
When you’re trying to get centimeter-level accuracy, every single aspect matters, and the latency and oscillators errors were causing significant issues.
Inline PCT Transfer (IPT) To The Rescue
Bluetooth 6.3 introduces Inline Phase Correction Transfer (IPT).
Instead of correcting phase errors after the fact, IPT applies corrections during the signal flow itself. By letting the reflector to transfer the phase-aligned tones directly into the hardware, the reflector doesn’t need to send the Imaginary component of the Phase Correction terms to the Host. This reduces the amount of data and more importantly speeds up the Channel Sounding Procedure
This is a significant shift in to the protocol
What IPT Changes
- Moves phase correction earlier in the pipeline
- Reduces reliance on heavy digital processing
- Improves accuracy by minimizing accumulated errors
The result is cleaner measurements with less computational cost.
More Accurate Distance Measurement with PHY-specific RTT Accuracy
Originally the Bluetooth CHannel Sounding protocol used a single Round-Trip-Time accuracy for all the Phys.
Before this, Channel sounding accuracy depended on assumptions about the PHY layer. That meant that accuracy varied depending on the PHY used and there was no standard way to account for that variation.
Bluetooth 6.3 lets this to be defined for each PHY separately which allows the system to use a PHY optimal value. This improves the location performance in cases where multiple PHYs are used.
This is a big deal for system designers.
Instead of treating distance measurements as generic values, you now get:
- PHY-aware accuracy reporting
- More predictable ranging performance
- Better calibration options
This allows developers to build systems that adapt based on PHY conditions rather than guessing.
Fixing a Real Problem: Running Out of Bits
As Bluetooth has evolved, more features were added to the protocol. Over time, the system used to signal these features started running out of space.
In other words, Bluetooth was literally running out of bits to describe new capabilities.
Bluetooth 6.3 introduces new command versioning mechanisms.
This allows:
- Expansion of feature signaling
- Better future compatibility
- Cleaner feature discovery across devices
The change is to extend HCI by expanding the Supported Commands bitmask from 64 to 251 bytes, and the LE Event Mask from 8 to 255 bytes which ensures that long terms there is plenty of space to add new features as the specification grows.
RF Improvements: ACP and C/I Relaxation for Bluetooth Classic
Bluetooth 6.3 also touches RF performance, which is where things get very practical.
What Are ACP and C/I?
- ACP (Adjacent Channel Power) measures how much signal leaks into adjacent channels
- C/I (Carrier-to-Interference) defines how well a signal can tolerate interference
Before these changes, Bluetooth Classic (BR/EDR) and Bluetooth LE had different requirements for ACP and C/I. This meant additional tests and different design targets.
The Bluetooth Classic requirements were much more stringent for really no reason. Bluetooth 6.3 updates these limits so that these tests are the same
These changes are helpful for Certification and RF coexistence for products that use Bluetooth Classic, and they’re also an indication that Low Energy is fully in the driver seat and that slowly Bluetooth Classic is starting to move towards that.
Bluetooth 6.3 harmonizes ACP limits across implementations and aligns C/I performance requirements
Backward Compatibility and Adoption
Like previous versions, Bluetooth 6.3 maintains backward compatibility.
That means:
- New devices will still work with older ones
- New features only activate when both sides support them
This is critical for ecosystem adoption.
The reality is that widespread support will depend on:
- Chipset vendors
- Mobile OS updates
- Stack implementations
So while the spec is available now, real-world adoption will take time. However some of these features will depend on using devices that support the latest release.
Final Thoughts
Bluetooth 6.3 is a quiet but important release, especially for product developers that are building Channel Sounding devices. It doesn’t introduce flashy features, but it fixes real problems. It’s also a signal that many more features are coming to the specification.
If Bluetooth 6.0 was about redefining what Bluetooth can do, Bluetooth 6.3 is about making those capabilities practical.
For product developers, that’s often the difference between a product on paper and a product released to the field.
