The Bluetooth core specification now reaches 6.3, with 6.0, 6.1, 6.2 and 6.3 all adopted. Which version a new project files under directly sets its test items and its later maintenance window — this is not a free pick.
Watch the exit timetable, but keep two nodes separate. The SIG spec page lists both Deprecation and Withdrawal for every core version: 5.0 and Appendix 6 carry a deprecation node of 1 February 2027, after which you cannot use these two versions for new qualification listings, while already-certified products stay valid; full withdrawal waits until 1 February 2032. Old projects still hanging on 5.0 should plan an upgrade this year rather than pile up at the node.
The later versions' deprecation nodes sit further out: 5.1 to February 2029, 5.2 to February 2030, 5.3 to February 2032, 5.4 to February 2033, 6.0 to February 2035. Withdrawal generally trails deprecation by another five years — do not remember just one number. Match your own version when planning production.
This is the spot most people trip this year. The SIG spec page lists Erratum 28108 — which aligns BR/EDR and LE on adjacent-channel power and carrier-to-interference requirements — as a mandatory erratum for declaring compliance with Core 6.0. A 6.0-onward project that omits it has an incomplete declaration.
Version 6.2 also carries its signature change: Channel Sounding phase ranging raises resistance to distance attacks, and the shortest connection interval drops from 7.5 ms to 0.375 ms. These are the genuinely public, speakable points of 6.2 — more informative than quoting a single erratum.
Which attached files each major version carries, check against the spec page before filing. These expedited updates are not optional extras; they are mandatory items bound to the version.
The Bluetooth SIG has always required claims layered by capability and profile; the core version number does not belong alone in a product name, nor as the only way to say "supports Bluetooth." This is the SIG brand-usage guidance's consistent direction — write to the current guide.
The correct approach is to list by specific capability: whether it supports high-accuracy ranging, broadcast audio and the like; then write out the profiles in use, such as audio streaming, calls and media audio, hearing aids, public broadcast and ranging. Claiming something you have not tested is false claiming, and a spot check makes you liable.
It is fine to mention not-yet-formally-adopted capabilities, but you must mark "based on working draft," and the draft may change. Do not publish draft features as finished features.
High-accuracy ranging is the headline of recent years — phase ranging for centimetre-level positioning, used in digital car keys, anti-loss and access control. It has its own ranging profile; hanging a core version number does not cover it.
Broadcast audio is also spreading fast; public-broadcast and hearing-aid related profiles already have corresponding test items. Makers of audio and in-vehicle products will likely be asked this year whether to add them.
The Asset Tracking profile and similar new members have also been adopted. Once a product claims the corresponding function, it must go through the matching test items; the test volume follows the claims — more claims, more test items.
① The core version number and the mandatory errata bound to that version — check against the spec page before filing; miss one and the declaration is incomplete. ② The product's supported capabilities and profile list, mapped one-to-one to the test items; claiming something untested draws spot-check attention. ③ For certified modules used, keep the module maker's derivative authorisation files and numbers ready; a broken authorisation chain means a top-up test. ④ Lock the sample and firmware version, fully matching the documents — a version mismatch is a frequent cause of return; set the core version and attached errata at case opening to avoid overturning the test plan mid-way.
BlueAsia reminds project owners not to carry old-core provisions into new projects; new applications follow the SIG's current core requirements, and the exact transition node follows the official announcement.
Contact: King Email: king.guo@cblueasia.comAddress: Building C, Hongjingda Industrial Park, No. 107 Beihuan Road, Shiyan Street, Bao'an District, Shenzhen, China BlueAsia delivers more than service!
Related News
