What changed in Core 6.3

The Bluetooth SIG adopted Bluetooth Core Specification 6.3 on May 5, 2026. The SIG’s release material describes improvements in ranging precision, interface capacity, and radio efficiency. Two highlighted Channel Sounding changes are Inline PCT Transfer and PHY-specific round-trip-time accuracy reporting.

The specification page identifies version 6.3 and its version date. The SIG published a separate overview article on May 6. The adoption date and publication date should not be conflated, and neither date proves availability in a shipping controller.

Inline PCT Transfer allows a Channel Sounding reflector to transfer phase-aligned tones directly into hardware. The SIG says this can reduce unnecessary reporting overhead and improve the efficiency of the procedure. PHY-specific RTT Accuracy lets a device report RTT accuracy separately for each PHY instead of using one value across PHYs.

The release also contains host-controller interface and radio-efficiency changes. Their exact normative requirements belong in the Core Specification and related qualification material, not in a summary article.

What the changes mean for a product

Channel Sounding products need an honest chain from radio capability to application claim. More precise or better-described inputs can improve a ranging pipeline, but enclosure design, antenna geometry, multipath, calibration, implementation, and threat model still determine measured product behavior.

PHY-specific accuracy reporting is useful because a host can reason from a more accurate statement of controller capability. It does not automatically calibrate a system or guarantee distance accuracy in a target environment. Inline transfer may change controller and host implementation choices, but the benefit must be measured on the selected silicon.

Interface-capacity changes matter to controller, host-stack, and test-tool teams even when an end user never sees a new Bluetooth feature. Compatibility across host and controller versions should remain explicit.

Bluetooth controller and host-stack vendors need to assess implementation and qualification changes. Product teams using Channel Sounding should review silicon roadmaps, security assumptions, accuracy models, and test plans. Device makers that do not use the affected capabilities may only need normal specification and qualification tracking.

Test labs and qualification owners need the adopted specification, changes document, test case references, and applicable program rules. Marketing teams should not turn a Core version number into an unsupported ranging claim.

Evidence to collect before adoption

Identify the exact 6.3 features relevant to the product rather than adopting a version label as a goal. Ask silicon and stack vendors which features are implemented, in which revisions, and with what qualification status. Keep host, controller, firmware, and test-tool compatibility in the release matrix.

For Channel Sounding, repeat accuracy and threat testing in the final enclosure and deployment environment. Record PHY, antenna configuration, calibration, environmental conditions, and the controller-reported accuracy inputs. Test degraded and adversarial conditions rather than reporting only a clean lab result.

Review whether new interface behavior changes buffers, event handling, power, or failure recovery. Update product claims only after measurements on shipping-equivalent hardware.

Do not replace working silicon merely to advertise Core 6.3. Do not assume an existing controller gains new features through a host update. Do not publish a distance-accuracy number from the specification announcement. Do not skip qualification or regulatory review because the change appears internal.

Products unrelated to Channel Sounding or the changed interfaces can track vendor support through their normal maintenance process rather than creating an urgent migration.

When to revisit the decision

Watch the Bluetooth SIG qualification resources and the “changes since previous version” material, then track controller and stack release notes from selected suppliers. For a shipping product, maintain a matrix of implemented Core features rather than a single “Bluetooth 6.3” boolean. Revisit this signal when production silicon, test coverage, or qualification guidance changes the decision—not whenever a marketing page repeats the version number.

The version, date, and summarized features are facts from the Bluetooth SIG. Product implications, risk questions, and recommended tests are IoT 01 analysis. Any claim about a particular chipset requires that vendor’s current documentation and product measurements, which are outside this signal.