Bluetooth group chose WiMedia UWB (2006)

What was announced or reported

The group expected the combination to support larger data transfers and richer audio or video use while keeping compatibility with low-power Bluetooth devices such as keyboards, mice and headsets. The target for the specification was the first quarter of 2007.

Context and limits

The source contrasted then-current transfer rates with a projected much higher rate for the UWB-enhanced version. These were roadmap and performance expectations in 2006, not a description of a later standard or device capability.

Why the distinction matters

The proposal tried to join a high-throughput radio path with Bluetooth’s established low-power use cases. Specification plans are not product guarantees, and the record does not establish which later devices, if any, implemented the stated approach. The planned specification date does not establish eventual implementation.

A proposed radio marriage had two design goals

The Bluetooth SIG described UWB integration as a way to raise data transfer capability while retaining the low-power, low-cost, ad-hoc qualities associated with Bluetooth. This is a useful design tension: a new performance goal must coexist with the traits that made the original technology appropriate for small peripherals and short-range connections.

Higher transfer speed and low-power use were separate goals

The Bluetooth SIG proposal sought a faster path through WiMedia UWB while retaining the qualities associated with existing Bluetooth peripherals. Those are not identical design jobs. Large transfers and richer media call for more throughput, whereas keyboards, mice and headsets depend on the low-power, short-range behaviour already associated with Bluetooth. The proposal attempted to keep both roles in one broader specification direction.

Compatibility protected the installed peripheral role

Backward compatibility mattered because it preserved the usefulness of familiar small devices while a higher-rate path was being planned for larger data tasks. That is a practical architecture choice: new capability should not make the established peripheral relationship disappear. The 2006 target date was a roadmap milestone, so the item explains the intended balance between performance and compatibility without turning that plan into a claim about later products.

UWB was aimed at larger transfers

Backward compatibility was therefore not a decorative promise. It was part of the value proposition for devices such as mice, keyboards, and headsets, while the faster path was aimed at larger synchronisation and media tasks. A specification plan can express that division of roles without proving that compatible consumer products will arrive on the announced timetable.

Peripherals anchored the compatibility requirement

For a product team, the relevant question would be which user task needs the higher rate and which installed devices must continue to work. The article reports an intended specification direction in 2006. It does not establish that the target specification, products, performance figures, or UWB-enhanced Bluetooth became available as described.