En Puede 6, 2026, el Bluetooth Special Interest Group released Especificación de núcleo de Bluetooth 6.3. It is an incremental update in Decir’s bi-annual release cycle—not a new radio mode, but a set of engineering refinements that make Sonido de canal more efficient and dual-mode products easier to design.

If you are evaluating módulos BLE for digital key, asset tracking, access control, or dual-mode audio/data products, 6.3 is worth understanding. It will not change every module datasheet overnight, but it shapes the direction of precision ranging and RF design for the next product generation.

Bluetooth 6.0 VS. 6.3: capability vs. refinement

Bluetooth 6.0 (Septiembre 2024) introduced Sonido de canal—secure, high-accuracy ranging via Phase-Based Ranging (PBR) y Round-Trip Time (RTT). Decir describes this as centimeter-level distance awareness, a major advance over RSSI-based proximity.

Bluetooth 6.3 builds on that foundation with four targeted updates:

Feature What it improves
Inline PCT Transfer (IPT)
Ranging speed & HCI efficiency
PHY-specific RTT Accuracy
Multi-PHY distance measurement
Running Out of Bits (ROOB)
HCI scalability for future features
ACP/C/I Limit Relaxation
Dual-mode (BR/EDR + Bolle) RF design

6.0 answered “can Bluetooth range precisely?” 6.3 answers “can we make it practical at scale?”

1. Inline PCT Transfer: leaner, faster Channel Sounding

In phase-based ranging, initiator and reflector each use independent local oscillators (LOs). LO phase offsets carry no distance information and must be eliminated before calculating range.

Traditional flow: both sides measure phase → reflector reports full I/Q PCT data over HCI → initiator digitally cancels LO error after both measurements complete.

IPT flow: the reflector performs analog phase pre-compensation, phase-aligning its retransmitted tone. The initiator measures 2θ_CH more directly. The reflector’s PCT report simplifies to Q = 0 (amplitude only).

Benefits: less HCI traffic, lower initiator processing load, shorter latency, better tolerance of LO drift.

Nota: IPT is negotiable—both devices must support and enable it. Non-IPT devices continue using the legacy two-way digital cancellation method with full backward compatibility.

Primary beneficiaries: digital key, smart access control, y high-frequency asset ranging—applications where Feasycom automotive-grade BLE modules are already deployed in digital key and passive entry projects.

2. PHY-specific RTT accuracy: one size no longer fits all

Previamente, a device declared a single RTT accuracy value across all PHY modes— inadequate when LE 1M, LE 2M, and LE 2M 2BT behave differently under real RF conditions.

6.3 enables per-PHY RTT declarations, specifying how many CS_SYNC exchanges are needed to reach 10 ns or 150 ns time-of-flight precision for each supported PHY and mode.

Systems can now select the optimal PHY/precision combination, reduce unnecessary radio-on time, and improve multi-vendor interoperability. Implementation requires HCl [v2] CS capability commands.

3. Running Out of Bits: HCI capacity for the next decade of features

Bolle’s feature set has grown rapidly, and HCI bitmasks were nearing capacity—Supported Commands capped at 512 brocas (64 octets), LE Event Mask at 64 brocas (8 octets).

6.3 introduces versioned [v2] commands expanding capacity to 251 octets (commands) y 255 octets (LE events), with conditional support rules preserving backward compatibility.

Users will not “see” ROOB directly, but it removes an architectural bottleneck that would otherwise limit future protocol growth.

4. ACP/C/I relaxation: simpler dual-mode RF—Classic only

Dual-mode products (Bluetooth clásico + Bolle) have long faced divergent RF requirements. Designers often over-constrained front-end performance to satisfy whichever standard was stricter.

6.3 relaxes BR/EDR ACP and C/I limits to align with the LE 1M framework. LE-side requirements are unchanged.

Example: BR/EDR adjacent channel power at offsets ≥ 3 megahercio moves from -40 DBM a -30 dbm.

This directly benefits TWS earbuds, automotive connectivity, and industrial printers—categories where dual-mode Bluetooth modules y Wifi + Bluetooth combo modules are commonly used.

Who benefits—and who should wait

Solicitud Impact of 6.3 Realistic expectation
Digital key / passive entry
Faster ranging, better boundary detection
Requires stack + firmware adoption; complements UWB/NFC in many designs
Asset & personnel tracking
Higher ranging throughput, lower overhead
Builds on 6.0 Channel Sounding—6.3 optimizes, not replaces
Medical wearables
RF harmonization, future HCI headroom
Benefits arrive with next-gen chip platforms
Dual-mode audio / data
Immediate RF design simplification
Most tangible near-term win

For positioning-heavy designs, Feasycom also offers faro y AOA/UWB positioning solutions alongside standard módulos BLE.

Decir and ABI Research project annual Bluetooth device shipments growing from ~5.4 billion in 2025 to over 8.1 billion by 2030, with LE innovations including Channel Sounding among the growth drivers.

What to ask your Módulo Bluetooth vendor

  1. Is Sonido de canal supported or on the firmware roadmap?
  2. Will IPT y PHY-specific RTT be enabled in production firmware?
  3. For dual-mode designs, does the module benefit from harmonized BR/EDR limits?
  4. What is the OTA path as stack features evolve?
  5. Are you communicating specific Bluetooth capabilities (per SIG guidance)—not just a core spec version number?

Resumen

Bluetooth Core 6.3 is a quiet but meaningful release: IPT makes Channel Sounding leaner, PHY-specific RTT makes multi-PHY ranging smarter, ROOB future-proofs HCI, and ACP/C/I harmonization makes dual-mode RF easier to build.

It strengthens the technical foundation for secure ranging and dual-mode connectivity—without replacing the need for careful Módulo Bluetooth evaluation based on your actual application requirements.

Explore Feasycom Bluetooth modules o contact our team to discuss ranging-ready and dual-mode options for your next design.

Preguntas frecuentes

Main difference between Bluetooth 6.0 y 6.3?
6.0 introduced Channel Sounding. 6.3 optimizes it (IPT, PHY RTT), expands HCI (ROOB), and harmonizes BR/EDR RF limits.

Does 6.3 add mandatory centimeter-level positioning?
No—that capability originates from Channel Sounding in 6.0. 6.3 improves implementation efficiency.

What is Inline PCT Transfer in plain terms?
The reflector cancels LO phase error in analog hardware instead of sending full correction data over HCI—faster and leaner ranging.

Does ACP/C/I relaxation affect módulos BLE?
No. Only Classic Bluetooth BR/EDR limits change, aligned to the LE 1M framework.

Will my existing Bluetooth 5.3/5.4 modules auto-support 6.3?
No. Chipset, stack, and firmware updates plus interoperability testing are all required.

Related Resources

Official — Bluetooth SIG

Feasycom.com

Feasycom.cn (SRRC-certified models, Chinese documentation & solution notes)