Bluetooth low energy
Bluetooth low energy or Bluetooth LE, marketed as Bluetooth Smart, is a wireless personal area network technology designed and marketed by the Bluetooth Special Interest Group aimed at novel applications in the healthcare, fitness, security, and home entertainment industries. Compared to Classic Bluetooth, Bluetooth Smart is intended to provide considerably reduced power consumption and cost while maintaining a similar communication range.
Bluetooth Smart was originally introduced under the name Wibree by Nokia in 2006. It was merged into the main Bluetooth standard in 2010 with the adoption of the Bluetooth Core Specification Version 4.0.
Mobile operating systems including iOS, Android, Windows Phone and BlackBerry, as well as OS X, Linux, and Windows 8, natively support Bluetooth Smart. The Bluetooth SIG predicts more than 90 percent of Bluetooth-enabled smartphones will support Bluetooth Smart by 2018.
- 1 Compatibility
- 2 Bluetooth Smart branding
- 3 Target market
- 4 History
- 5 Applications
- 6 Implementation
- 7 Technical details
- 8 See also
- 9 References
- 10 External links
Bluetooth Smart is not backward-compatible with the previous, often called Classic, Bluetooth protocol. The Bluetooth 4.0 specification permits devices to implement either or both of the LE and Classic systems.
Bluetooth Smart branding
In 2011, the Bluetooth SIG announced the Bluetooth Smart logo scheme intended to clarify compatibility between low energy devices.
- Bluetooth Smart Ready indicates a dual-mode device compatible with both Classic and low energy peripherals.
- Bluetooth Smart indicates a low energy-only device which requires either a Smart Ready or another Smart device in order to function.
The Bluetooth SIG identifies a number of markets for low energy technology, particularly in the smart home, health, sport and fitness sectors. Cited advantages include:
- low power requirements, operating for "months or years" on a button cell
- small size and low cost
- compatibility with a large installed base of mobile phones, tablets and computers
In 2001, researchers at Nokia determined various scenarios contemporary wireless technologies did not address. The company began developing a wireless technology adapted from the Bluetooth standard which would provide lower power usage and cost while minimizing its differences from Bluetooth technology. The results were published in 2004 using the name Bluetooth Low End Extension.
After further development with partners, e.g., within EU FP6 project MIMOSA, the technology was released to the public in October 2006 with the brand name Wibree. After negotiations with Bluetooth SIG members, an agreement was reached in June 2007 to include Wibree in future Bluetooth specification as a Bluetooth ultra-low-power technology, now known as Bluetooth Smart technology.
Integration of Bluetooth Smart with version 4.0 of the Core Specification was completed in early 2010. The first smartphone to implement the 4.0 specification was the iPhone 4S, released in October 2011. A number of other manufacturers released Bluetooth Smart Ready devices in 2012.
Borrowing from the original Bluetooth specification, the Bluetooth SIG defines several profiles — specifications for how a device works in a particular application — for low energy devices. Manufacturers are expected to implement the appropriate specifications for their device in order to ensure compatibility. A device may contain implementations of multiple profiles.
All current low energy application profiles are based on the generic attribute profile, or GATT, a general specification for sending and receiving short pieces of data known as attributes over a low energy link. Bluetooth 4.0 provides low power consumption with higher baud rates.
In 2014 a Bluetooth Smart protocol with the name CSR mesh was published - CSR is for Cambridge Silicon Radio. The protocol supports internet of things. E.g. by QR Codes it is possible to switch groups of e.g. CSR mesh equipped electronic light bulbs on or off - or individually.
Health care profiles
There are many profiles for Bluetooth Smart devices in healthcare applications. The Continua Health Alliance consortium promotes these in cooperation with the Bluetooth SIG.
- HTP — for medical temperature measurement devices.
- GLP — for blood glucose monitors.
- BLP — for blood pressure measurement.
Sports and fitness profiles
Profiles for sporting and fitness accessories include:
- HRP — for devices which measure heart rate.
- CSCP — for sensors attached to a bicycle or exercise bike to measure cadence and wheel speed.
- RSCP — running speed and cadence profile.
- CPP — cycling power profile.
- LNP — location and navigation profile.
"Electronic leash" applications are well suited to the long battery life possible for 'always-on' devices. Manufacturers of iBeacon devices implement the appropriate specifications for their device to make use of proximity sensing capabilities supported by Apple Inc. compatible iDevices.
Relevant application profiles include:
- FMP — the "find me" profile — allows one device to issue an alert on a second misplaced device.
- PXP — the proximity profile — allows a proximity monitor to detect whether a proximity reporter is within a close range. Physical proximity can be estimated using the radio receiver's RSSI value, although this does not have absolute calibration of distances. Typically, an alarm may be sounded when the distance between the devices exceeds a set threshold.
Alerts and time profiles
- The phone alert status profile and alert notification profile allow a client device to receive notifications such as incoming call alerts from another device.
- The time profile allows current time and time zone information on a client device to be set from a server device, such as between a wristwatch and a mobile phone's network time.
Starting in late 2009, Bluetooth Smart integrated circuit implementations were announced by a number of manufacturers. Implementations commonly use software radio so updates to the specification can be accommodated through a firmware upgrade.
Current mobile devices are commonly released with hardware and software support for both Classic Bluetooth and the Bluetooth Smart standard. The Bluetooth SIG maintains a list of devices.
- iOS 5 and later
- Windows Phone 8.1, Windows Phone 8 (no developer API)
- Android 4.3 and later
- BlackBerry 10
- Linux 3.4 and later through BlueZ 5.0
- Unison OS 5.2 
Bluetooth Smart technology operates in the same spectrum range (the 2.400 GHz-2.4835 GHz ISM band) as Classic Bluetooth technology, but uses a different set of channels. Instead of the Classic Bluetooth 79 1-MHz channels, Bluetooth Smart has 40 2-MHz channels. Within a channel, data is transmitted using Gaussian frequency shift modulation, similar to Classic Bluetooth's Basic Rate scheme. The bit rate is 1Mbit/s, and the maximum transmit power is 10 mW. Further details are given in Volume 6 Part A (Physical Layer Specification) of the Bluetooth Core Specification V4.0.
Bluetooth Smart uses frequency hopping to counteract narrowband interference problems. Classic Bluetooth also uses frequency hopping but the details are different; as a result, while both FCC and ETSI classify Bluetooth technology as an FHSS scheme, Bluetooth Smart is classified as a system using digital modulation techniques or a direct-sequence spread spectrum.
|Technical Specification||Classic Bluetooth technology||Bluetooth Smart technology|
|Distance/Range (theoretical max.)||100 m (330 ft)||<100 m (<330 ft)|
|Over the air data rate||1–3 Mbit/s||1 Mbit/s|
|Application throughput||0.7–2.1 Mbit/s||0.27 Mbit/s|
|Active slaves||7||Not defined; implementation dependent|
|Security||56/128-bit and application layer user defined||128-bit AES with Counter Mode CBC-MAC and application layer user defined|
|Robustness||Adaptive fast frequency hopping, FEC, fast ACK||Adaptive frequency hopping, Lazy Acknowledgement, 24-bit CRC, 32-bit Message Integrity Check|
|Latency (from a non-connected state)||Typically 100 ms||6 ms|
|Total time to send data (det.battery life)||100 ms||3 ms [not in citation given]|
|Power consumption||1 as the reference||0.01 to 0.5 (depending on use case)|
|Peak current consumption||<30 mA||<15 mA|
|Primary use cases||Mobile phones, gaming, headsets, stereo audio streaming, smart homes, wearables, automotive, PCs, security, proximity, healthcare, sports & fitness, etc.||Mobile phones, gaming, PCs, watches, sports and fitness, healthcare, security & proximity, automotive, home electronics, automation, Industrial, etc.|
More technical details may be obtained from official specification as published by the Bluetooth SIG. Note that power consumption is not part of the Bluetooth specification.
All Bluetooth Smart devices use the Generic Attribute Profile (GATT). The application programming interface offered by a Bluetooth Smart aware operating system will typically be based around GATT concepts. GATT has the following terminology:
- A device that initiates GATT commands and requests, and accepts responses, for example a computer or smartphone.
- A device that receives GATT commands and requests, and returns responses, for example a temperature sensor.
- A data value transferred between client and server, for example the current battery voltage.
- A collection of related characteristics, which operate together to perform a particular function. For instance, the Health Thermometer service includes characteristics for a temperature measurement value, and a time interval between measurements.
- A descriptor provides additional information about a characteristic. For instance, a temperature value characteristic may have an indication of its units (e.g. Celsius), and the maximum and minimum values which the sensor can measure. Descriptors are optional - each characteristic can have any number of descriptors.
Some service and characteristic values are used for administrative purposes - for instance, the model name and serial number can be read as standard characteristics within the Generic Access service. Services may also include other services as sub-functions; the main functions of the device are so-called primary services, and the auxiliary functions they refer to are secondary services.
Services, characteristics, and descriptors are collectively referred to as attributes, and identified by UUIDs. Any implementer may pick a random or pseudorandom UUID for proprietary uses, but the Bluetooth SIG have reserved a range of UUIDs (of the form xxxxxxxx-0000-1000-8000-00805F9B34FB ) for standard attributes. For efficiency, these identifiers are represented as 16-bit or 32-bit values in the protocol, rather than the 128 bits required for a full UUID. For example, the Device Information service has the short code 0x180A, rather than 0000180A-1000-... . The full list is kept in the Bluetooth Assigned Numbers document online.
The GATT protocol provides a number of commands for the client to discover information about the server. These include:
- Discover UUIDs for all primary services
- Find a service with a given UUID
- Find secondary services for a given primary service
- Discover all characteristics for a given service
- Find characteristics matching a given UUID
- Read all descriptors for a particular characteristic
Commands are also provided to read (data transfer from server to client) and write (from client to server) the values of characteristics:
- A value may be read either by specifying the characteristic's UUID, or by a handle value (which is returned by the information discovery commands above).
- Write operations always identify the characteristic by handle, but have a choice of whether or not a response from the server is required.
- 'Long read' and 'Long write' operations can be used when the length of the characteristic's data exceeds the MTU of the radio link.
Finally, GATT offers notifications and indications. The client may request a notification for a particular characteristic from the server. The server can then send the value to the client whenever it becomes available. For instance, a temperature sensor server may notify its client every time it takes a measurement. This avoids the need for the client to poll the server, which would require the server's radio circuitry to be constantly operational.
An indication is similar to a notification, except that it requires a response from the client, as confirmation that it has received the message.
Bluetooth Low Energy (BLE) is designed to enable devices low power consumption. Devices with peripheral and central roles have different power requirements. Peripherals, such as proximity beacons, usually function for 2 years with a 1,000mAh battery, whereas a continuous scan for the same beacons in central role can consume 1,000 mAh power in few hours.
GATT is described in full in Volume 3, Part G of the Bluetooth 4.0 Core Specification.
- ANT and ANT+
- IEEE 802.15 / IEEE 802.15.4-2006
- Indoor positioning system (IPS)
- Ultra wideband (UWB)
- UWB Forum
- WiMedia Alliance
- Wireless USB
- bluetooth.com: Bluetooth Smart
- HowStuffWorks.com: Wibree
- "Mobile Telephony Market". Bluetooth Special Interest Group. Retrieved January 16, 2014.
- Bluetooth SMART marks, Bluetooth SIG press release
- Bluetooth Smart Marks FAQ
- Bluetooth SIG 'Markets' pages
- The Future of Things, Nokia's Wibree and the Wireless Zoo]
- M. Honkanen, A. Lappetelainen, K. Kivekas, "Low end extension for Bluetooth", Radio and Wireless Conference, 2004 IEEE, 19–22 September 2004
- "Bluetooth rival unveiled by Nokia", BBC News, 4 October 2006
- Wibree Bluetooth press release 12 June 2007
- "Wibree becomes Ultra low power Bluetooth technology". electronicsweekly.com. Retrieved 2008-09-09.
- "Bluetooth Low Energy". Bluetooth.com. Retrieved 2012-08-23.
- "iPhone 4S claims title of first Bluetooth 4.0 smartphone, ready to stream data from your cat". Engadget.com. Retrieved 2014-02-09.
- Bluetooth SIG Adopted specifications
- 9 Jul 2014, theregister.co.uk: New Bluetooth tech lets you control 4 BILLION lightbulbs at once Quote: "...The CSR mesh protocol uses Bluetooth low energy with device-to-device communications to allow one bulb to speak to the next...Each bulb has a 128 bit identifier so that it can be addressed individually or in a group. Each group can have 64,000 bulbs and users can create up to 64,000 groups. One device can be in multiple groups...Samsung is planning to launch a $20 LED lightbulb which supports the technology in the next month or so..."
- 25 Feb 2014, csr.com: Game-changing Bluetooth® Smart solution enables whole home control from the smartphone for the first time Quote: "...CSR Mesh allows for an almost unlimited number of Bluetooth Smart enabled devices to be simply networked together and controlled directly from a single smartphone, tablet or PC for the first time...It will allow consumers to control any Bluetooth Smart enabled device in the home from wherever they are, including lighting, heating, appliances and security systems. Crucially for the consumer experience, solutions based on the protocol don’t require the complex setup, pairing, or use of an access device such as a router..."
- Video: CSR Mesh - Putting the smartphone at the centre of the Internet of Things
- Casio watch with Bluetooth low energy profile
- Inside iOS 7: iBeacons enhance apps' location awareness via Bluetooth LE
- Find Me Profile specification
- Brynte (2014-05-04). "Windows Phone 8.1 for Developers–Introducing Bluetooth LE". MSDN Blogs. Retrieved 2014-05-18.
- Gustavo Padovan (2013-02-22). "The big changes of BlueZ 5". "As the MGMT interface is the only one to support the new Bluetooth Low Energy devices, BlueZ developers decided to drop support for the old interface once MGMT was completed. As a result, you need to be running Linux Kernel 3.4 or newer to use BlueZ 5."
- Bluetooth Smart
- See for example Apple's Core Bluetooth framework
- See sec 2.5.1 of the Bluetooth 4.0 Core Specification
- "iBeacon Battery Drain on Apple vs Android: A Technical Report - Aislelabs". Aislelabs. 2014-08-14. Retrieved 2014-08-18.