Thursday, May 8th 2025

Bluetooth SIG Announces Bluetooth 6.1 with Improved Power Efficiency and Security
The Bluetooth Core Specification recently moved to a bi-annual release schedule. This shift enables more frequent and consistent delivery of completed features, fostering faster innovation and continuous improvements across the Bluetooth ecosystem. Developers and manufacturers now have quicker access to the latest Bluetooth advancements, powering wireless innovation and enhancing overall market responsiveness.
"Moving to a bi-annual release cycle for the Bluetooth Core Specification represents a pivotal step forward for the entire Bluetooth technology ecosystem," said Alain Michaud, chair of the Bluetooth SIG Board of Directors. "This new cadence will ensure that incremental improvements and features can reach developers and manufacturers faster, fueling innovation and helping them meet the evolving needs of the market with greater agility."The first release under the new bi-annual release schedule, Bluetooth Core 6.1, published on 6 May 2025. This release introduces Bluetooth Randomized RPA (resolvable private address) Updates, a feature designed to enhance privacy and power efficiency in Bluetooth devices.
Key benefits of Bluetooth Randomized RPA Updates:
Reminder: Bluetooth SIG members should avoid referencing the Bluetooth Core Specification version against which a product was qualified (e.g., Bluetooth Core 6.1) when describing Bluetooth functionality. Instead, members should focus on clearly communicating the specific Bluetooth capabilities (e.g., Bluetooth features) supported, especially those most relevant to your target customers, in product packaging, documentation, and marketing materials.
Source:
Bluetooth SIG
"Moving to a bi-annual release cycle for the Bluetooth Core Specification represents a pivotal step forward for the entire Bluetooth technology ecosystem," said Alain Michaud, chair of the Bluetooth SIG Board of Directors. "This new cadence will ensure that incremental improvements and features can reach developers and manufacturers faster, fueling innovation and helping them meet the evolving needs of the market with greater agility."The first release under the new bi-annual release schedule, Bluetooth Core 6.1, published on 6 May 2025. This release introduces Bluetooth Randomized RPA (resolvable private address) Updates, a feature designed to enhance privacy and power efficiency in Bluetooth devices.
Key benefits of Bluetooth Randomized RPA Updates:
- Increased device privacy: Randomizing the timing of address changes makes it much more difficult for third parties to track or correlate device activity over time
- Improved power efficiency: The Bluetooth Randomized RPA Updates feature offloads the address change operation to the Controller, helping conserve battery life
Reminder: Bluetooth SIG members should avoid referencing the Bluetooth Core Specification version against which a product was qualified (e.g., Bluetooth Core 6.1) when describing Bluetooth functionality. Instead, members should focus on clearly communicating the specific Bluetooth capabilities (e.g., Bluetooth features) supported, especially those most relevant to your target customers, in product packaging, documentation, and marketing materials.
12 Comments on Bluetooth SIG Announces Bluetooth 6.1 with Improved Power Efficiency and Security
But seriously, up till now, BT has thankfully avoided the clusterflook that is USB, with its multiple gens + multiple versions +.x.xx.xxxx etc etc, so lets hope that continues....
with wifi, we can easily transfer 100MB/s++, bluetooth if not power-capped (spec-wise) i think can do same thing
A 1.2GHz standard would be ideal for this task, as we do not need raw gigabit style throughput like WiFi, and would allow them to reduce power requirements, and make the signal more robust. I just don't understand why the Bluetooth SIG does not push for this going forward. I mean, Bluetooth has barely improved in throughput for the last 15 years. It's obvious that basing it on 2.4GHz was a huge mistake.
Some adaptive data buffering could also be implemented (if not done already), so if there have to be audio dropouts, there are as few as possible in a given situation.
But yes, a few megabytes of buffer, would always be a smart idea with a streaming device. 4MB would be enough to store 3 seconds of uncompressed 192/24 bit audio or 5 seconds of the same audio, losslessly compressed.
I'm sure that if you limited the bandwidth to say 800KBs, it would be more than enough when using lossless encoding.
Anyway, I'm only dreaming about what could be!