Bluetooth Low Energy and the Radio Designed for Battery-Powered Devices

Classic Bluetooth was not optimized for every tiny battery-powered device

Bluetooth’s original strengths included direct cable replacement and audio, but many sensors and wearables needed shorter radio activity and much lower energy use. Nokia’s retrospective describes work on a low-energy radio that was announced as Wibree in 2006 for devices expected to run for long periods on small batteries.^[1]

Wibree was designed to coexist with phones

The goal included a low-power peripheral radio that could work alongside existing Bluetooth capabilities without requiring a completely separate consumer-device ecosystem.

Wibree entered the Bluetooth standards process

Nokia contributed the technology for development within the Bluetooth SIG, where it evolved into Bluetooth Low Energy.^[1] The transition illustrates how a company-specific wireless technology can gain much wider reach through a shared interoperability standard.

Standardization created a multi-vendor target

Chip vendors, operating systems and device makers could implement one common protocol rather than a proprietary sensor-radio stack.

Bluetooth 4.0 formally introduced Low Energy in 2010

The Bluetooth Core Specification history records version 4.0 as adopted on June 30, 2010 and identifies Low Energy as its major new feature.^[2]

Low Energy was more than a reduced-power mode

Version 4.0 added a distinct LE physical and link layer together with host protocols and profiles tailored to its communication model.

ATT and GATT gave applications a common data model

The Bluetooth Core change history identifies the Attribute Protocol and Generic Attribute Profile among the major Low Energy additions in version 4.0.^[3] GATT represents application data as services, characteristics and descriptors.

Standard services made device capabilities discoverable

A client can discover structured data exposed by a peripheral without knowing its internal firmware implementation.

Advertising reduced the need for permanent connections

The Bluetooth LE primer explains GAP procedures for advertising, discovery and connectionless communication and describes how GATT and ATT fit above the controller.^[4] Short advertising events allow devices to announce information while remaining inactive much of the time.

The radio architecture targets efficient intermittent communication

The current Bluetooth Core specification defines the Low Energy controller separately from the classic BR/EDR controller and specifies dedicated LE physical and link layers.^[5] This reflects BLE’s role as a distinct architecture rather than merely a software profile.

BLE expanded from sensors into a broad device ecosystem

Fitness devices, beacons, peripherals, smart-home products and medical sensors could communicate with phones using a radio stack designed around low duty cycle. Later Bluetooth versions increased throughput, range and advertising capabilities while retaining the Low Energy lineage.^[4]

Why Bluetooth Low Energy belongs in ubiquitous-computing history

BLE connected two trends: increasingly capable smartphones and increasingly numerous tiny battery-powered devices. Wibree supplied the low-energy design lineage, Bluetooth 4.0 standardized it, and GATT supplied a common application model.^[1][3] That combination made short-range wireless connectivity practical for devices that could not behave like always-on radios.

RESEARCH / PROVENANCE

Works Cited

5 SOURCES

1. 01
   Nokia — How Nokia Triggered the Global Rise of Bluetooth LE ↗nokia.com
2. 02
   Bluetooth SIG — Core Specification 4.0 ↗bluetooth.com
3. 03
   Bluetooth Core Specification — Change History for Version 4.0 ↗bluetooth.com
4. 04
   Bluetooth SIG — Bluetooth Low Energy Primer ↗bluetooth.com
5. 05
   Bluetooth SIG — Current Core Specification ↗bluetooth.com

CodeHistory is a living archive. Citations document the evidence used for this edition; later evidence may refine the account.