|Developed by||Bluetooth Special Interest Group|
|Industry||Personal area networks|
|Compatible hardware||Personal computers|
|Physical range||Typically less than 10 m (33 ft), up to 100 m (330 ft)|
Bluetooth 5.0: 40–400 m (100–1,000 ft)
Bluetooth is a wireless technology standard for exchanging data between fixed and mobile devices over short distances using short-wavelength UHF radio waves in the industrial, scientific and medical radio bands, from 2.400 to 2.485 GHz, and building personal area networks (PANs). It was originally conceived as a wireless alternative to RS-232 data cables.
Bluetooth is managed by the Bluetooth Special Interest Group (SIG), which has more than 30,000 member companies in the areas of telecommunication, computing, networking, and consumer electronics. The IEEE standardized Bluetooth as IEEE 802.15.1, but no longer maintains the standard. The Bluetooth SIG oversees development of the specification, manages the qualification program, and protects the trademarks. A manufacturer must meet Bluetooth SIG standards to market it as a Bluetooth device. A network of patents apply to the technology, which are licensed to individual qualifying devices.
- 1 History
- 2 Name and logo
- 3 Implementation
- 4 Uses
- 5 Computer requirements
- 6 Specifications and features
- 7 Technical information
- 7.1 Architecture
- 7.2 Bluetooth protocol stack
- 7.2.1 Link Manager
- 7.2.2 Host Controller Interface
- 7.2.3 Logical Link Control and Adaptation Protocol
- 7.2.4 Service Discovery Protocol
- 7.2.5 Radio Frequency Communications
- 7.2.6 Bluetooth Network Encapsulation Protocol
- 7.2.7 Audio/Video Control Transport Protocol
- 7.2.8 Audio/Video Distribution Transport Protocol
- 7.2.9 Telephony Control Protocol
- 7.2.10 Adopted protocols
- 7.3 Baseband error correction
- 7.4 Setting up connections
- 7.5 Pairing and bonding
- 8 Security
- 9 Health concerns
- 10 Award programs
- 11 See also
- 12 References
- 13 External links
The development of the "short-link" radio technology, later named Bluetooth, was initiated in 1989 by Nils Rydbeck, CTO at Ericsson Mobile in Lund, Sweden and by Johan Ullman. The purpose was to develop wireless headsets, according to two inventions by Johan Ullman, SE 8902098-6, issued 1989-06-12 and SE 9202239, issued 1992-07-24 . Nils Rydbeck tasked Tord Wingren with specifying and Jaap Haartsen and Sven Mattisson with developing. Both were working for Ericsson in Lund. Invented by Dutch electrical engineer Jaap Haartsen, working for telecommunications company Ericsson in 1994. The first consumer Bluetooth device launched in 1999. It was a hand free mobile headset which earned the "Best of show Technology Award" at COMDEX. The first Bluetooth mobile phone was the Ericsson T36 but it was the revised T39 model which actually made it to store shelves in 2001.
Name and logo
The name Bluetooth is an Anglicised version of the Scandinavian Blåtand/Blåtann (Old Norse blátǫnn), the epithet of the tenth-century king Harald Bluetooth who united dissonant Danish tribes into a single kingdom. The implication is that Bluetooth unites communication protocols.
The idea of this name was proposed in 1997 by Jim Kardach of Intel who developed a system that would allow mobile phones to communicate with computers. At the time of this proposal he was reading Frans G. Bengtsson's historical novel The Long Ships about Vikings and King Harald Bluetooth.
Bluetooth operates at frequencies between 2402 and 2480 MHz, or 2400 and 2483.5 MHz including guard bands 2 MHz wide at the bottom end and 3.5 MHz wide at the top. This is in the globally unlicensed (but not unregulated) industrial, scientific and medical (ISM) 2.4 GHz short-range radio frequency band. Bluetooth uses a radio technology called frequency-hopping spread spectrum. Bluetooth divides transmitted data into packets, and transmits each packet on one of 79 designated Bluetooth channels. Each channel has a bandwidth of 1 MHz. It usually performs 1600 hops per second, with adaptive frequency-hopping (AFH) enabled. Bluetooth Low Energy uses 2 MHz spacing, which accommodates 40 channels.
Originally, Gaussian frequency-shift keying (GFSK) modulation was the only modulation scheme available. Since the introduction of Bluetooth 2.0+EDR, π/4-DQPSK (differential quadrature phase-shift keying) and 8-DPSK modulation may also be used between compatible devices. Devices functioning with GFSK are said to be operating in basic rate (BR) mode where an instantaneous bit rate of 1 Mbit/s is possible. The term Enhanced Data Rate (EDR) is used to describe π/4-DPSK and 8-DPSK schemes, each giving 2 and 3 Mbit/s respectively. The combination of these (BR and EDR) modes in Bluetooth radio technology is classified as a BR/EDR radio.
Bluetooth is a packet-based protocol with a master/slave architecture. One master may communicate with up to seven slaves in a piconet. All devices share the master's clock. Packet exchange is based on the basic clock, defined by the master, which ticks at 312.5 µs intervals. Two clock ticks make up a slot of 625 µs, and two slots make up a slot pair of 1250 µs. In the simple case of single-slot packets, the master transmits in even slots and receives in odd slots. The slave, conversely, receives in even slots and transmits in odd slots. Packets may be 1, 3 or 5 slots long, but in all cases the master's transmission begins in even slots and the slave's in odd slots.
The above excludes Bluetooth Low Energy, introduced in the 4.0 specification, which uses the same spectrum but somewhat differently.
Communication and connection
A master BR/EDR Bluetooth device can communicate with a maximum of seven devices in a piconet (an ad-hoc computer network using Bluetooth technology), though not all devices reach this maximum. The devices can switch roles, by agreement, and the slave can become the master (for example, a headset initiating a connection to a phone necessarily begins as master—as an initiator of the connection—but may subsequently operate as the slave).
The Bluetooth Core Specification provides for the connection of two or more piconets to form a scatternet, in which certain devices simultaneously play the master role in one piconet and the slave role in another.
At any given time, data can be transferred between the master and one other device (except for the little-used broadcast mode). The master chooses which slave device to address; typically, it switches rapidly from one device to another in a round-robin fashion. Since it is the master that chooses which slave to address, whereas a slave is (in theory) supposed to listen in each receive slot, being a master is a lighter burden than being a slave. Being a master of seven slaves is possible; being a slave of more than one master is possible. The specification is vague as to required behavior in scatternets.
|Class||Max. permitted power||Typ. range |
(BT 5 Vol 6 Part A Sect 3)
Bluetooth is a standard wire-replacement communications protocol primarily designed for low power consumption, with a short range based on low-cost transceiver microchips in each device. Because the devices use a radio (broadcast) communications system, they do not have to be in visual line of sight of each other; however, a quasi optical wireless path must be viable. Range is power-class-dependent, but effective ranges vary in practice. See the table "Ranges of Bluetooth devices by class".
Officially Class 3 radios have a range of up to 1 metre (3 ft), Class 2, most commonly found in mobile devices, 10 metres (33 ft), and Class 1, primarily for industrial use cases,100 metres (300 ft). Bluetooth Marketing qualifies that Class 1 range is in most cases 20–30 metres (66–98 ft), and Class 2 range 5–10 metres (16–33 ft). The actual range achieved by a given link will depend on the qualities of the devices at both ends of the link, as well as the air conditions in between, and other factors.
The effective range varies depending on propagation conditions, material coverage, production sample variations, antenna configurations and battery conditions. Most Bluetooth applications are for indoor conditions, where attenuation of walls and signal fading due to signal reflections make the range far lower than specified line-of-sight ranges of the Bluetooth products.
Most Bluetooth applications are battery-powered Class 2 devices, with little difference in range whether the other end of the link is a Class 1 or Class 2 device as the lower-powered device tends to set the range limit. In some cases the effective range of the data link can be extended when a Class 2 device is connecting to a Class 1 transceiver with both higher sensitivity and transmission power than a typical Class 2 device. Mostly, however, the Class 1 devices have a similar sensitivity to Class 2 devices. Connecting two Class 1 devices with both high sensitivity and high power can allow ranges far in excess of the typical 100m, depending on the throughput required by the application. Some such devices allow open field ranges of up to 1 km and beyond between two similar devices without exceeding legal emission limits.
The Bluetooth Core Specification mandates a range of not less than 10 metres (33 ft), but there is no upper limit on actual range. Manufacturers' implementations can be tuned to provide the range needed for each case.
To use Bluetooth wireless technology, a device must be able to interpret certain Bluetooth profiles, which are definitions of possible applications and specify general behaviors that Bluetooth-enabled devices use to communicate with other Bluetooth devices. These profiles include settings to parameterize and to control the communication from the start. Adherence to profiles saves the time for transmitting the parameters anew before the bi-directional link becomes effective. There are a wide range of Bluetooth profiles that describe many different types of applications or use cases for devices.
List of applications
- Wireless control and communication between a mobile phone and a handsfree headset. This was one of the earliest applications to become popular.
- Wireless control of and communication between a mobile phone and a Bluetooth compatible car stereo system.
- Wireless control of and communication with iOS and Android device phones, tablets and portable wireless speakers.
- Wireless Bluetooth headset and Intercom. Idiomatically, a headset is sometimes called "a Bluetooth".
- Wireless streaming of audio to headphones with or without communication capabilities.
- Wireless streaming of data collected by Bluetooth-enabled fitness devices to phone or PC.
- Wireless networking between PCs in a confined space and where little bandwidth is required.
- Wireless communication with PC input and output devices, the most common being the mouse, keyboard and printer.
- Transfer of files, contact details, calendar appointments, and reminders between devices with OBEX.
- Replacement of previous wired RS-232 serial communications in test equipment, GPS receivers, medical equipment, bar code scanners, and traffic control devices.
- For controls where infrared was often used.
- For low bandwidth applications where higher USB bandwidth is not required and cable-free connection desired.
- Sending small advertisements from Bluetooth-enabled advertising hoardings to other, discoverable, Bluetooth devices.
- Wireless bridge between two Industrial Ethernet (e.g., PROFINET) networks.
- Seventh and eighth generation game consoles such as Nintendo's Wii, and Sony's PlayStation 3 use Bluetooth for their respective wireless controllers.
- Dial-up internet access on personal computers or PDAs using a data-capable mobile phone as a wireless modem.
- Short-range transmission of health sensor data from medical devices to mobile phone, set-top box or dedicated telehealth devices.
- Allowing a DECT phone to ring and answer calls on behalf of a nearby mobile phone.
- Real-time location systems (RTLS) are used to track and identify the location of objects in real time using "Nodes" or "tags" attached to, or embedded in, the objects tracked, and "Readers" that receive and process the wireless signals from these tags to determine their locations.
- Personal security application on mobile phones for prevention of theft or loss of items. The protected item has a Bluetooth marker (e.g., a tag) that is in constant communication with the phone. If the connection is broken (the marker is out of range of the phone) then an alarm is raised. This can also be used as a man overboard alarm. A product using this technology has been available since 2009.
- Calgary, Alberta, Canada's Roads Traffic division uses data collected from travelers' Bluetooth devices to predict travel times and road congestion for motorists.
- Wireless transmission of audio (a more reliable alternative to FM transmitters)
- Live video streaming to the visual cortical implant device by Nabeel Fattah in Newcastle university 2017.
- Connection of motion controllers to a PC when using VR headsets
Bluetooth vs. Wi-Fi (IEEE 802.11)
Bluetooth and Wi-Fi (Wi-Fi is the brand name for products using IEEE 802.11 standards) have some similar applications: setting up networks, printing, or transferring files. Wi-Fi is intended as a replacement for high-speed cabling for general local area network access in work areas or home. This category of applications is sometimes called wireless local area networks (WLAN). Bluetooth was intended for portable equipment and its applications. The category of applications is outlined as the wireless personal area network (WPAN). Bluetooth is a replacement for cabling in a variety of personally carried applications in any setting, and also works for fixed location applications such as smart energy functionality in the home (thermostats, etc.).
Wi-Fi and Bluetooth are to some extent complementary in their applications and usage. Wi-Fi is usually access point-centered, with an asymmetrical client-server connection with all traffic routed through the access point, while Bluetooth is usually symmetrical, between two Bluetooth devices. Bluetooth serves well in simple applications where two devices need to connect with a minimal configuration like a button press, as in headsets and remote controls, while Wi-Fi suits better in applications where some degree of client configuration is possible and high speeds are required, especially for network access through an access node. However, Bluetooth access points do exist, and ad-hoc connections are possible with Wi-Fi though not as simple as with Bluetooth. Wi-Fi Direct was recently developed to add a more Bluetooth-like ad-hoc functionality to Wi-Fi.
Bluetooth exists in numerous products such as telephones, speakers, tablets, media players, robotics systems, laptops, and console gaming equipment as well as some high definition headsets, modems, hearing aids and even watches. Given the variety of devices which use the Bluetooth, coupled with the contemporary deprecation of headphone jacks by Apple, Google, and other companies, and the lack of regulation by the FCC, the technology is prone to interference. Nonetheless Bluetooth is useful when transferring information between two or more devices that are near each other in low-bandwidth situations. Bluetooth is commonly used to transfer sound data with telephones (i.e., with a Bluetooth headset) or byte data with hand-held computers (transferring files).
Bluetooth protocols simplify the discovery and setup of services between devices. Bluetooth devices can advertise all of the services they provide. This makes using services easier, because more of the security, network address and permission configuration can be automated than with many other network types.
A personal computer that does not have embedded Bluetooth can use a Bluetooth adapter that enables the PC to communicate with Bluetooth devices. While some desktop computers and most recent laptops come with a built-in Bluetooth radio, others require an external adapter, typically in the form of a small USB "dongle."
Operating system implementation
For Microsoft platforms, Windows XP Service Pack 2 and SP3 releases work natively with Bluetooth v1.1, v2.0 and v2.0+EDR. Previous versions required users to install their Bluetooth adapter's own drivers, which were not directly supported by Microsoft. Microsoft's own Bluetooth dongles (packaged with their Bluetooth computer devices) have no external drivers and thus require at least Windows XP Service Pack 2. Windows Vista RTM/SP1 with the Feature Pack for Wireless or Windows Vista SP2 work with Bluetooth v2.1+EDR. Windows 7 works with Bluetooth v2.1+EDR and Extended Inquiry Response (EIR). The Windows XP and Windows Vista/Windows 7 Bluetooth stacks support the following Bluetooth profiles natively: PAN, SPP, DUN, HID, HCRP. The Windows XP stack can be replaced by a third party stack that supports more profiles or newer Bluetooth versions. The Windows Vista/Windows 7 Bluetooth stack supports vendor-supplied additional profiles without requiring that the Microsoft stack be replaced. It is generally recommended to install the latest vendor driver and its associated stack to be able to use the Bluetooth device at its fullest extent.
Linux has two popular Bluetooth stacks, BlueZ and Fluoride. The BlueZ stack is included with most Linux kernels and was originally developed by Qualcomm. Fluoride, earlier known as Bluedroid is included in Android OS and was originally developed by Broadcom. There is also Affix stack, developed by Nokia. It was once popular, but has not been updated since 2005.
DragonFly BSD has had NetBSD's Bluetooth implementation since 1.11 (2008). A netgraph-based implementation from FreeBSD has also been available in the tree, possibly disabled until 2014-11-15, and may require more work.
Specifications and features
The specifications were formalized by the Bluetooth Special Interest Group (SIG) and formally announced on the 20 of May 1998. Today it has a membership of over 30,000 companies worldwide. It was established by Ericsson, IBM, Intel, Nokia and Toshiba, and later joined by many other companies.
The Bluetooth Core Specification Working Group (CSWG) produces mainly 4 kinds of specifications:
- The Bluetooth Core Specification, release cycle is typically a few years in between
- Core Specification Addendum (CSA), release cycle can be as tight as a few times per year
- Core Specification Supplements (CSS), can be released very quickly
- Errata (Available with a user account: Errata login)
Bluetooth 1.0 and 1.0B
Versions 1.0 and 1.0B had many problems, and manufacturers had difficulty making their products interoperable. Versions 1.0 and 1.0B also included mandatory Bluetooth hardware device address (BD_ADDR) transmission in the Connecting process (rendering anonymity impossible at the protocol level), which was a major setback for certain services planned for use in Bluetooth environments.
- Ratified as IEEE Standard 802.15.1–2002
- Many errors found in the v1.0B specifications were fixed.
- Added possibility of non-encrypted channels.
- Received Signal Strength Indicator (RSSI).
Major enhancements include:
- Faster Connection and Discovery
- Adaptive frequency-hopping spread spectrum (AFH), which improves resistance to radio frequency interference by avoiding the use of crowded frequencies in the hopping sequence.
- Higher transmission speeds in practice than in v1.1, up to 721 kbit/s.
- Extended Synchronous Connections (eSCO), which improve voice quality of audio links by allowing retransmissions of corrupted packets, and may optionally increase audio latency to provide better concurrent data transfer.
- Host Controller Interface (HCI) operation with three-wire UART.
- Ratified as IEEE Standard 802.15.1–2005
- Introduced Flow Control and Retransmission Modes for L2CAP.
Bluetooth 2.0 + EDR
This version of the Bluetooth Core Specification was released in 2004. The main difference is the introduction of an Enhanced Data Rate (EDR) for faster data transfer. The bit rate of EDR is 3 Mbit/s, although the maximum data transfer rate (allowing for inter-packet time and acknowledgements) is 2.1 Mbit/s. EDR uses a combination of GFSK and phase-shift keying modulation (PSK) with two variants, π/4-DQPSK and 8-DPSK. EDR can provide a lower power consumption through a reduced duty cycle.
The specification is published as Bluetooth v2.0 + EDR, which implies that EDR is an optional feature. Aside from EDR, the v2.0 specification contains other minor improvements, and products may claim compliance to "Bluetooth v2.0" without supporting the higher data rate. At least one commercial device states "Bluetooth v2.0 without EDR" on its data sheet.
Bluetooth 2.1 + EDR
Bluetooth Core Specification Version 2.1 + EDR was adopted by the Bluetooth SIG on 26 July 2007.
Version 2.1 allows various other improvements, including extended inquiry response (EIR), which provides more information during the inquiry procedure to allow better filtering of devices before connection; and sniff subrating, which reduces the power consumption in low-power mode.
Bluetooth 3.0 + HS
Version 3.0 + HS of the Bluetooth Core Specification was adopted by the Bluetooth SIG on 21 April 2009. Bluetooth v3.0 + HS provides theoretical data transfer speeds of up to 24 Mbit/s, though not over the Bluetooth link itself. Instead, the Bluetooth link is used for negotiation and establishment, and the high data rate traffic is carried over a colocated 802.11 link.
The main new feature is AMP (Alternative MAC/PHY), the addition of 802.11 as a high-speed transport. The high-speed part of the specification is not mandatory, and hence only devices that display the "+HS" logo actually support Bluetooth over 802.11 high-speed data transfer. A Bluetooth v3.0 device without the "+HS" suffix is only required to support features introduced in Core Specification Version 3.0 or earlier Core Specification Addendum 1.
- L2CAP Enhanced modes
- Enhanced Retransmission Mode (ERTM) implements reliable L2CAP channel, while Streaming Mode (SM) implements unreliable channel with no retransmission or flow control. Introduced in Core Specification Addendum 1.
- Alternative MAC/PHY
- Enables the use of alternative MAC and PHYs for transporting Bluetooth profile data. The Bluetooth radio is still used for device discovery, initial connection and profile configuration. However, when large quantities of data must be sent, the high-speed alternative MAC PHY 802.11 (typically associated with Wi-Fi) transports the data. This means that Bluetooth uses proven low power connection models when the system is idle, and the faster radio when it must send large quantities of data. AMP links require enhanced L2CAP modes.
- Unicast Connectionless Data
- Permits sending service data without establishing an explicit L2CAP channel. It is intended for use by applications that require low latency between user action and reconnection/transmission of data. This is only appropriate for small amounts of data.
- Enhanced Power Control
- Updates the power control feature to remove the open loop power control, and also to clarify ambiguities in power control introduced by the new modulation schemes added for EDR. Enhanced power control removes the ambiguities by specifying the behaviour that is expected. The feature also adds closed loop power control, meaning RSSI filtering can start as the response is received. Additionally, a "go straight to maximum power" request has been introduced. This is expected to deal with the headset link loss issue typically observed when a user puts their phone into a pocket on the opposite side to the headset.
The high-speed (AMP) feature of Bluetooth v3.0 was originally intended for UWB, but the WiMedia Alliance, the body responsible for the flavor of UWB intended for Bluetooth, announced in March 2009 that it was disbanding, and ultimately UWB was omitted from the Core v3.0 specification.
On 16 March 2009, the WiMedia Alliance announced it was entering into technology transfer agreements for the WiMedia Ultra-wideband (UWB) specifications. WiMedia has transferred all current and future specifications, including work on future high-speed and power-optimized implementations, to the Bluetooth Special Interest Group (SIG), Wireless USB Promoter Group and the USB Implementers Forum. After successful completion of the technology transfer, marketing, and related administrative items, the WiMedia Alliance ceased operations.
In October 2009 the Bluetooth Special Interest Group suspended development of UWB as part of the alternative MAC/PHY, Bluetooth v3.0 + HS solution. A small, but significant, number of former WiMedia members had not and would not sign up to the necessary agreements for the IP transfer. The Bluetooth SIG is now in the process of evaluating other options for its longer term roadmap.
The Bluetooth SIG completed the Bluetooth Core Specification version 4.0 (called Bluetooth Smart) and has been adopted as of 30 June 2010[update]. It includes Classic Bluetooth, Bluetooth high speed and Bluetooth Low Energy (BLE) protocols. Bluetooth high speed is based on Wi-Fi, and Classic Bluetooth consists of legacy Bluetooth protocols.
Bluetooth Low Energy, previously known as Wibree, is a subset of Bluetooth v4.0 with an entirely new protocol stack for rapid build-up of simple links. As an alternative to the Bluetooth standard protocols that were introduced in Bluetooth v1.0 to v3.0, it is aimed at very low power applications powered by a coin cell. Chip designs allow for two types of implementation, dual-mode, single-mode and enhanced past versions. The provisional names Wibree and Bluetooth ULP (Ultra Low Power) were abandoned and the BLE name was used for a while. In late 2011, new logos "Bluetooth Smart Ready" for hosts and "Bluetooth Smart" for sensors were introduced as the general-public face of BLE.
Compared to Classic Bluetooth, Bluetooth Low Energy is intended to provide considerably reduced power consumption and cost while maintaining a similar communication range. In terms of lengthening the battery life of Bluetooth devices, BLE represents a significant progression.
- In a single-mode implementation, only the low energy protocol stack is implemented. Dialog Semiconductor, STMicroelectronics, AMICCOM, CSR, Nordic Semiconductor and Texas Instruments have released single mode Bluetooth Low Energy solutions.
- In a dual-mode implementation, Bluetooth Smart functionality is integrated into an existing Classic Bluetooth controller. As of March 2011[update], the following semiconductor companies have announced the availability of chips meeting the standard: Qualcomm-Atheros, CSR, Broadcom and Texas Instruments. The compliant architecture shares all of Classic Bluetooth's existing radio and functionality resulting in a negligible cost increase compared to Classic Bluetooth.
Cost-reduced single-mode chips, which enable highly integrated and compact devices, feature a lightweight Link Layer providing ultra-low power idle mode operation, simple device discovery, and reliable point-to-multipoint data transfer with advanced power-save and secure encrypted connections at the lowest possible cost.
General improvements in version 4.0 include the changes necessary to facilitate BLE modes, as well the Generic Attribute Profile (GATT) and Security Manager (SM) services with AES Encryption.
Core Specification Addendum 2 was unveiled in December 2011; it contains improvements to the audio Host Controller Interface and to the High Speed (802.11) Protocol Adaptation Layer.
Core Specification Addendum 3 revision 2 has an adoption date of 24 July 2012.
Core Specification Addendum 4 has an adoption date of 12 February 2013.
The Bluetooth SIG announced formal adoption of the Bluetooth v4.1 specification on 4 December 2013. This specification is an incremental software update to Bluetooth Specification v4.0, and not a hardware update. The update incorporates Bluetooth Core Specification Addenda (CSA 1, 2, 3 & 4) and adds new features that improve consumer usability. These include increased co-existence support for LTE, bulk data exchange rates—and aid developer innovation by allowing devices to support multiple roles simultaneously.
New features of this specification include:
- Mobile Wireless Service Coexistence Signaling
- Train Nudging and Generalized Interlaced Scanning
- Low Duty Cycle Directed Advertising
- L2CAP Connection Oriented and Dedicated Channels with Credit-Based Flow Control
- Dual Mode and Topology
- LE Link Layer Topology
- 802.11n PAL
- Audio Architecture Updates for Wide Band Speech
- Fast Data Advertising Interval
- Limited Discovery Time
Notice that some features were already available in a Core Specification Addendum (CSA) before the release of v4.1.
Released on December 2, 2014, it introduces features for the Internet of Things.
The major areas of improvement are:
- Low Energy Secure Connection with Data Packet Length Extension
- Link Layer Privacy with Extended Scanner Filter Policies
- Internet Protocol Support Profile (IPSP) version 6 ready for Bluetooth Smart things to support connected home
The Bluetooth SIG presented Bluetooth 5 on 16 June 2016. Its new features are mainly focused on emerging Internet of Things technology. The Samsung Galaxy S8 launched with Bluetooth 5 support in April 2017. In September 2017, the iPhone 8, 8 Plus and iPhone X launched with Bluetooth 5 support as well. Apple also integrated Bluetooth 5 in their new HomePod offering released on February 9, 2018. Marketing drops the point number; so that it is just "Bluetooth 5" (unlike Bluetooth 4.0). The change is for the sake of "Simplifying our marketing, communicating user benefits more effectively and making it easier to signal significant technology updates to the market."
Bluetooth 5 provides, for BLE, options that can double the speed (2 Mbit/s burst) at the expense of range, or up to fourfold the range at the expense of data rate, and eightfold the data broadcasting capacity of transmissions, by increasing the packet lengths. The increase in transmissions could be important for Internet of Things devices, where many nodes connect throughout a whole house. Bluetooth 5 adds functionality for connectionless services such as location-relevant navigation of low-energy Bluetooth connections.
The major areas of improvement are:
- Slot Availability Mask (SAM)
- 2 Mbit/s PHY for LE
- LE Long Range
- High Duty Cycle Non-Connectable Advertising
- LE Advertising Extensions
- LE Channel Selection Algorithm #2
Features Added in CSA5 – Integrated in v5.0:
- Higher Output Power
The following features were removed in this version of the specification:
- Park State
The Bluetooth SIG presented Bluetooth 5.1 on 21 January 2019.
The major areas of improvement are:
- Angle of Arrival (AoA) and Angle of Departure (AoD) which are used for location and tracking of devices
- Advertising Channel Index
- GATT Caching
- Minor Enhancements batch 1:
- HCI support for debug keys in LE Secure Connections
- Sleep clock accuracy update mechanism
- ADI field in scan response data
- Interaction between QoS and Flow Specification
- Host channel classification for secondary advertising
- Allow the SID to appear in scan response reports
- Specify the behavior when rules are violated
- Periodic Advertising Sync Transfer
Features Added in Core Specification Addendum (CSA) 6 – Integrated in v5.1:
- Mesh-based model hierarchy
The following features were removed in this version of the specification:
- Unit keys
Seeking to extend the compatibility of Bluetooth devices, the devices that adhere to the standard use as an interface between the host device (laptop, phone, etc.) and the Bluetooth device as such (Bluetooth chip) an interface called HCI (Host Controller Interface)
High-level protocols such as the SDP (Protocol used to find other Bluetooth devices within the communication range, also responsible for detecting the function of devices in range), RFCOMM (Protocol used to emulate serial port connections) and TCS (Telephony control protocol) interact with the baseband controller through the L2CAP Protocol (Logical Link Control and Adaptation Protocol). The L2CAP protocol is responsible for the segmentation and reassembly of the packets
The hardware that makes up the Bluetooth device is made up of, logically, two parts; which may or may not be physically separate. A radio device, responsible for modulating and transmitting the signal; and a digital controller. The digital controller is likely a CPU, one of whose functions is to run a Link Controller; and interfaces with the host device; but some functions may be delegated to hardware. The Link Controller is responsible for the processing of the baseband and the management of ARQ and physical layer FEC protocols. In addition, it handles the transfer functions (both asynchronous and synchronous), audio coding and data encryption. The CPU of the device is responsible for attending the instructions related to Bluetooth of the host device, in order to simplify its operation. To do this, the CPU runs software called Link Manager that has the function of communicating with other devices through the LMP protocol.
Bluetooth protocol stack
Bluetooth is defined as a layer protocol architecture consisting of core protocols, cable replacement protocols, telephony control protocols, and adopted protocols. Mandatory protocols for all Bluetooth stacks are LMP, L2CAP and SDP. In addition, devices that communicate with Bluetooth almost universally can use these protocols: HCI and RFCOMM.
The Link Manager is the system that manages to establish the connection between devices. It is responsible for the establishment, authentication and configuration of the link. The Link Manager locates other managers and communicates with them thanks to the management protocol of the LMP link. In order to perform its function as a service provider, the LM uses the services included in the link controller (LC, "Link Controller"). The Link Manager Protocol basically consists of a number of PDUs (Protocol Data Units) that are sent from one device to another. The following is a list of supported services:
- Transmission and reception of data.
- Name request
- Request of the link addresses.
- Establishment of the connection.
- Negotiation of link mode and connection establishment.
Host Controller Interface
The Host Controller Interface provides a command interface for the controller and for the link manager, which allows access to the hardware status and control registers. This interface provides an access layer for all Bluetooth devices. The HCI layer of the machine exchanges commands and data with the HCI firmware present in the Bluetooth device. One of the most important HCI tasks that must be performed is the automatic discovery of other Bluetooth devices that are within the coverage radius.
Logical Link Control and Adaptation Protocol
The Logical Link Control and Adaptation Protocol (L2CAP) is used to multiplex multiple logical connections between two devices using different higher level protocols. Provides segmentation and reassembly of on-air packets.
In Basic mode, L2CAP provides packets with a payload configurable up to 64 kB, with 672 bytes as the default MTU, and 48 bytes as the minimum mandatory supported MTU.
In Retransmission and Flow Control modes, L2CAP can be configured either for isochronous data or reliable data per channel by performing retransmissions and CRC checks.
Bluetooth Core Specification Addendum 1 adds two additional L2CAP modes to the core specification. These modes effectively deprecate original Retransmission and Flow Control modes:
- Enhanced Retransmission Mode (ERTM)
- This mode is an improved version of the original retransmission mode. This mode provides a reliable L2CAP channel.
- Streaming Mode (SM)
- This is a very simple mode, with no retransmission or flow control. This mode provides an unreliable L2CAP channel.
Reliability in any of these modes is optionally and/or additionally guaranteed by the lower layer Bluetooth BDR/EDR air interface by configuring the number of retransmissions and flush timeout (time after which the radio flushes packets). In-order sequencing is guaranteed by the lower layer.
Only L2CAP channels configured in ERTM or SM may be operated over AMP logical links.
Service Discovery Protocol
The Service Discovery Protocol (SDP) allows a device to discover services offered by other devices, and their associated parameters. For example, when you use a mobile phone with a Bluetooth headset, the phone uses SDP to determine which Bluetooth profiles the headset can use (Headset Profile, Hands Free Profile, Advanced Audio Distribution Profile (A2DP) etc.) and the protocol multiplexer settings needed for the phone to connect to the headset using each of them. Each service is identified by a Universally Unique Identifier (UUID), with official services (Bluetooth profiles) assigned a short form UUID (16 bits rather than the full 128).
Radio Frequency Communications
Radio Frequency Communications (RFCOMM) is a cable replacement protocol used for generating a virtual serial data stream. RFCOMM provides for binary data transport and emulates EIA-232 (formerly RS-232) control signals over the Bluetooth baseband layer, i.e. it is a serial port emulation.
RFCOMM provides a simple reliable data stream to the user, similar to TCP. It is used directly by many telephony related profiles as a carrier for AT commands, as well as being a transport layer for OBEX over Bluetooth.
Many Bluetooth applications use RFCOMM because of its widespread support and publicly available API on most operating systems. Additionally, applications that used a serial port to communicate can be quickly ported to use RFCOMM.
Bluetooth Network Encapsulation Protocol
The Bluetooth Network Encapsulation Protocol (BNEP) is used for transferring another protocol stack's data via an L2CAP channel. Its main purpose is the transmission of IP packets in the Personal Area Networking Profile. BNEP performs a similar function to SNAP in Wireless LAN.
Audio/Video Control Transport Protocol
The Audio/Video Control Transport Protocol (AVCTP) is used by the remote control profile to transfer AV/C commands over an L2CAP channel. The music control buttons on a stereo headset use this protocol to control the music player.
Audio/Video Distribution Transport Protocol
The Audio/Video Distribution Transport Protocol (AVDTP) is used by the advanced audio distribution (A2DP) profile to stream music to stereo headsets over an L2CAP channel intended for video distribution profile in the Bluetooth transmission.
Telephony Control Protocol
The Telephony Control Protocol – Binary (TCS BIN) is the bit-oriented protocol that defines the call control signaling for the establishment of voice and data calls between Bluetooth devices. Additionally, "TCS BIN defines mobility management procedures for handling groups of Bluetooth TCS devices."
TCS-BIN is only used by the cordless telephony profile, which failed to attract implementers. As such it is only of historical interest.
Adopted protocols are defined by other standards-making organizations and incorporated into Bluetooth's protocol stack, allowing Bluetooth to code protocols only when necessary. The adopted protocols include:
- Point-to-Point Protocol (PPP)
- Internet standard protocol for transporting IP datagrams over a point-to-point link.
- Foundation Protocols for TCP/IP protocol suite
- Object Exchange Protocol (OBEX)
- Session-layer protocol for the exchange of objects, providing a model for object and operation representation
- Wireless Application Environment/Wireless Application Protocol (WAE/WAP)
- WAE specifies an application framework for wireless devices and WAP is an open standard to provide mobile users access to telephony and information services.
Baseband error correction
Depending on packet type, individual packets may be protected by error correction, either 1/3 rate forward error correction (FEC) or 2/3 rate. In addition, packets with CRC will be retransmitted until acknowledged by automatic repeat request (ARQ).
Setting up connections
Any Bluetooth device in discoverable mode transmits the following information on demand:
- Device name
- Device class
- List of services
- Technical information (for example: device features, manufacturer, Bluetooth specification used, clock offset)
Any device may perform an inquiry to find other devices to connect to, and any device can be configured to respond to such inquiries. However, if the device trying to connect knows the address of the device, it always responds to direct connection requests and transmits the information shown in the list above if requested. Use of a device's services may require pairing or acceptance by its owner, but the connection itself can be initiated by any device and held until it goes out of range. Some devices can be connected to only one device at a time, and connecting to them prevents them from connecting to other devices and appearing in inquiries until they disconnect from the other device.
Every device has a unique 48-bit address. However, these addresses are generally not shown in inquiries. Instead, friendly Bluetooth names are used, which can be set by the user. This name appears when another user scans for devices and in lists of paired devices.
Most cellular phones have the Bluetooth name set to the manufacturer and model of the phone by default. Most cellular phones and laptops show only the Bluetooth names and special programs are required to get additional information about remote devices. This can be confusing as, for example, there could be several cellular phones in range named T610 (see Bluejacking).
Pairing and bonding
Many services offered over Bluetooth can expose private data or let a connecting party control the Bluetooth device. Security reasons make it necessary to recognize specific devices, and thus enable control over which devices can connect to a given Bluetooth device. At the same time, it is useful for Bluetooth devices to be able to establish a connection without user intervention (for example, as soon as in range).
To resolve this conflict, Bluetooth uses a process called bonding, and a bond is generated through a process called pairing. The pairing process is triggered either by a specific request from a user to generate a bond (for example, the user explicitly requests to "Add a Bluetooth device"), or it is triggered automatically when connecting to a service where (for the first time) the identity of a device is required for security purposes. These two cases are referred to as dedicated bonding and general bonding respectively.
Pairing often involves some level of user interaction. This user interaction confirms the identity of the devices. When pairing successfully completes, a bond forms between the two devices, enabling those two devices to connect to each other in the future without repeating the pairing process to confirm device identities. When desired, the user can remove the bonding relationship.
During pairing, the two devices establish a relationship by creating a shared secret known as a link key. If both devices store the same link key, they are said to be paired or bonded. A device that wants to communicate only with a bonded device can cryptographically authenticate the identity of the other device, ensuring it is the same device it previously paired with. Once a link key is generated, an authenticated Asynchronous Connection-Less (ACL) link between the devices may be encrypted to protect exchanged data against eavesdropping. Users can delete link keys from either device, which removes the bond between the devices—so it is possible for one device to have a stored link key for a device it is no longer paired with.
Bluetooth services generally require either encryption or authentication and as such require pairing before they let a remote device connect. Some services, such as the Object Push Profile, elect not to explicitly require authentication or encryption so that pairing does not interfere with the user experience associated with the service use-cases.
Pairing mechanisms changed significantly with the introduction of Secure Simple Pairing in Bluetooth v2.1. The following summarizes the pairing mechanisms:
- Legacy pairing: This is the only method available in Bluetooth v2.0 and before. Each device must enter a PIN code; pairing is only successful if both devices enter the same PIN code. Any 16-byte UTF-8 string may be used as a PIN code; however, not all devices may be capable of entering all possible PIN codes.
- Limited input devices: The obvious example of this class of device is a Bluetooth Hands-free headset, which generally have few inputs. These devices usually have a fixed PIN, for example "0000" or "1234", that are hard-coded into the device.
- Numeric input devices: Mobile phones are classic examples of these devices. They allow a user to enter a numeric value up to 16 digits in length.
- Alpha-numeric input devices: PCs and smartphones are examples of these devices. They allow a user to enter full UTF-8 text as a PIN code. If pairing with a less capable device the user must be aware of the input limitations on the other device; there is no mechanism available for a capable device to determine how it should limit the available input a user may use.
- Secure Simple Pairing (SSP): This is required by Bluetooth v2.1, although a Bluetooth v2.1 device may only use legacy pairing to interoperate with a v2.0 or earlier device. Secure Simple Pairing uses a form of public key cryptography, and some types can help protect against man in the middle, or MITM attacks. SSP has the following authentication mechanisms:
- Just works: As the name implies, this method just works, with no user interaction. However, a device may prompt the user to confirm the pairing process. This method is typically used by headsets with very limited IO capabilities, and is more secure than the fixed PIN mechanism this limited set of devices uses for legacy pairing. This method provides no man-in-the-middle (MITM) protection.
- Numeric comparison: If both devices have a display, and at least one can accept a binary yes/no user input, they may use Numeric Comparison. This method displays a 6-digit numeric code on each device. The user should compare the numbers to ensure they are identical. If the comparison succeeds, the user(s) should confirm pairing on the device(s) that can accept an input. This method provides MITM protection, assuming the user confirms on both devices and actually performs the comparison properly.
- Passkey Entry: This method may be used between a device with a display and a device with numeric keypad entry (such as a keyboard), or two devices with numeric keypad entry. In the first case, the display presents a 6-digit numeric code to the user, who then enters the code on the keypad. In the second case, the user of each device enters the same 6-digit number. Both of these cases provide MITM protection.
- Out of band (OOB): This method uses an external means of communication, such as near-field communication (NFC) to exchange some information used in the pairing process. Pairing is completed using the Bluetooth radio, but requires information from the OOB mechanism. This provides only the level of MITM protection that is present in the OOB mechanism.
SSP is considered simple for the following reasons:
- In most cases, it does not require a user to generate a passkey.
- For use cases not requiring MITM protection, user interaction can be eliminated.
- For numeric comparison, MITM protection can be achieved with a simple equality comparison by the user.
- Using OOB with NFC enables pairing when devices simply get close, rather than requiring a lengthy discovery process.
Prior to Bluetooth v2.1, encryption is not required and can be turned off at any time. Moreover, the encryption key is only good for approximately 23.5 hours; using a single encryption key longer than this time allows simple XOR attacks to retrieve the encryption key.
- Turning off encryption is required for several normal operations, so it is problematic to detect if encryption is disabled for a valid reason or for a security attack.
Bluetooth v2.1 addresses this in the following ways:
- Encryption is required for all non-SDP (Service Discovery Protocol) connections
- A new Encryption Pause and Resume feature is used for all normal operations that require that encryption be disabled. This enables easy identification of normal operation from security attacks.
- The encryption key must be refreshed before it expires.
Link keys may be stored on the device file system, not on the Bluetooth chip itself. Many Bluetooth chip manufacturers let link keys be stored on the device—however, if the device is removable, this means that the link key moves with the device.
Bluetooth implements confidentiality, authentication and key derivation with custom algorithms based on the SAFER+ block cipher. Bluetooth key generation is generally based on a Bluetooth PIN, which must be entered into both devices. This procedure might be modified if one of the devices has a fixed PIN (e.g., for headsets or similar devices with a restricted user interface). During pairing, an initialization key or master key is generated, using the E22 algorithm. The E0 stream cipher is used for encrypting packets, granting confidentiality, and is based on a shared cryptographic secret, namely a previously generated link key or master key. Those keys, used for subsequent encryption of data sent via the air interface, rely on the Bluetooth PIN, which has been entered into one or both devices.
An overview of Bluetooth vulnerabilities exploits was published in 2007 by Andreas Becker.
In September 2008, the National Institute of Standards and Technology (NIST) published a Guide to Bluetooth Security as a reference for organizations. It describes Bluetooth security capabilities and how to secure Bluetooth technologies effectively. While Bluetooth has its benefits, it is susceptible to denial-of-service attacks, eavesdropping, man-in-the-middle attacks, message modification, and resource misappropriation. Users and organizations must evaluate their acceptable level of risk and incorporate security into the lifecycle of Bluetooth devices. To help mitigate risks, included in the NIST document are security checklists with guidelines and recommendations for creating and maintaining secure Bluetooth piconets, headsets, and smart card readers.
Bluetooth v2.1 – finalized in 2007 with consumer devices first appearing in 2009 – makes significant changes to Bluetooth's security, including pairing. See the pairing mechanisms section for more about these changes.
Bluejacking is the sending of either a picture or a message from one user to an unsuspecting user through Bluetooth wireless technology. Common applications include short messages, e.g., "You've just been bluejacked!" Bluejacking does not involve the removal or alteration of any data from the device. Bluejacking can also involve taking control of a mobile device wirelessly and phoning a premium rate line, owned by the bluejacker. Security advances have alleviated this issue.
History of security concerns
In 2001, Jakobsson and Wetzel from Bell Laboratories discovered flaws in the Bluetooth pairing protocol and also pointed to vulnerabilities in the encryption scheme. In 2003, Ben and Adam Laurie from A.L. Digital Ltd. discovered that serious flaws in some poor implementations of Bluetooth security may lead to disclosure of personal data. In a subsequent experiment, Martin Herfurt from the trifinite.group was able to do a field-trial at the CeBIT fairgrounds, showing the importance of the problem to the world. A new attack called BlueBug was used for this experiment. In 2004 the first purported virus using Bluetooth to spread itself among mobile phones appeared on the Symbian OS. The virus was first described by Kaspersky Lab and requires users to confirm the installation of unknown software before it can propagate. The virus was written as a proof-of-concept by a group of virus writers known as "29A" and sent to anti-virus groups. Thus, it should be regarded as a potential (but not real) security threat to Bluetooth technology or Symbian OS since the virus has never spread outside of this system. In August 2004, a world-record-setting experiment (see also Bluetooth sniping) showed that the range of Class 2 Bluetooth radios could be extended to 1.78 km (1.11 mi) with directional antennas and signal amplifiers. This poses a potential security threat because it enables attackers to access vulnerable Bluetooth devices from a distance beyond expectation. The attacker must also be able to receive information from the victim to set up a connection. No attack can be made against a Bluetooth device unless the attacker knows its Bluetooth address and which channels to transmit on, although these can be deduced within a few minutes if the device is in use.
In January 2005, a mobile malware worm known as Lasco surfaced. The worm began targeting mobile phones using Symbian OS (Series 60 platform) using Bluetooth enabled devices to replicate itself and spread to other devices. The worm is self-installing and begins once the mobile user approves the transfer of the file (Velasco.sis) from another device. Once installed, the worm begins looking for other Bluetooth enabled devices to infect. Additionally, the worm infects other .SIS files on the device, allowing replication to another device through the use of removable media (Secure Digital, CompactFlash, etc.). The worm can render the mobile device unstable.
In April 2005, Cambridge University security researchers published results of their actual implementation of passive attacks against the PIN-based pairing between commercial Bluetooth devices. They confirmed that attacks are practicably fast, and the Bluetooth symmetric key establishment method is vulnerable. To rectify this vulnerability, they designed an implementation that showed that stronger, asymmetric key establishment is feasible for certain classes of devices, such as mobile phones.
In June 2005, Yaniv Shaked and Avishai Wool published a paper describing both passive and active methods for obtaining the PIN for a Bluetooth link. The passive attack allows a suitably equipped attacker to eavesdrop on communications and spoof if the attacker was present at the time of initial pairing. The active method makes use of a specially constructed message that must be inserted at a specific point in the protocol, to make the master and slave repeat the pairing process. After that, the first method can be used to crack the PIN. This attack's major weakness is that it requires the user of the devices under attack to re-enter the PIN during the attack when the device prompts them to. Also, this active attack probably requires custom hardware, since most commercially available Bluetooth devices are not capable of the timing necessary.
In August 2005, police in Cambridgeshire, England, issued warnings about thieves using Bluetooth enabled phones to track other devices left in cars. Police are advising users to ensure that any mobile networking connections are de-activated if laptops and other devices are left in this way.
In April 2006, researchers from Secure Network and F-Secure published a report that warns of the large number of devices left in a visible state, and issued statistics on the spread of various Bluetooth services and the ease of spread of an eventual Bluetooth worm.
In October 2006, at the Luxemburgish Hack.lu Security Conference, Kevin Finistere and Thierry Zoller demonstrated and released a remote root shell via Bluetooth on Mac OS X v10.3.9 and v10.4. They also demonstrated the first Bluetooth PIN and Linkkeys cracker, which is based on the research of Wool and Shaked.
In April 2017, security researchers at Armis discovered multiple exploits in the Bluetooth software in various platforms, including Microsoft Windows, Linux, Apple iOS, and Google Android. These vulnerabilities are collectively called "BlueBorne." The exploits allow an attacker to connect to devices or systems without authentication and can give them "virtually full control over the device." Armis contacted Google, Microsoft, Apple, Samsung and Linux developers allowing them to patch their software before the coordinated announcement of the vulnerabilities on September 12, 2017.
Bluetooth uses the microwave radio frequency spectrum in the 2.402 GHz to 2.480 GHz range, which is non-ionizing radiation, of similar bandwidth to the one used by wireless and mobile phones. No specific demonstration of harm has been demonstrated up to date, even if wireless transmission has been included by IARC in the possible carcinogen list. Maximum power output from a Bluetooth radio is 100 mW for class 1, 2.5 mW for class 2, and 1 mW for class 3 devices. Even the maximum power output of class 1 is a lower level than the lowest-powered mobile phones. UMTS and W-CDMA output 250 mW, GSM1800/1900 outputs 1000 mW, and GSM850/900 outputs 2000 mW.
The Bluetooth Innovation World Cup, a marketing initiative of the Bluetooth Special Interest Group (SIG), was an international competition that encouraged the development of innovations for applications leveraging Bluetooth technology in sports, fitness and health care products. The aim of the competition was to stimulate new markets.
The Bluetooth Innovation World Cup morphed into the Bluetooth Breakthrough Awards in 2013. Bluetooth SIG subsequently launched the Imagine Blue Award in 2016 at Bluetooth World. The Breakthrough Awards Bluetooth program highlights the most innovative products and applications available today, prototypes coming soon, and student-led projects in the making.
- Bluetooth stack – Key firmware to use bluetooth feature
- BlueSoleil – proprietary driver
- Bluetooth Low Energy Beacons (AltBeacon, iBeacon, Eddystone)
- Bluetooth Mesh
- Continua Health Alliance
- Headset (audio)
- Hotspot (Wi-Fi)
- Java APIs for Bluetooth
- Key finder
- Near-field communication
- RuBee – secure wireless protocol alternative
- Wi-Fi HaLow
- ZigBee – low-power lightweight wireless protocol in the ISM band
- bluAir. "Bluetooth Range: 100m, 1km, or 10km?". bluair.pl. Retrieved 4 June 2015.
- "Basics | Bluetooth Technology Website". Bluetooth.com. 23 May 2010.
- "About us - Bluetooth Technology Website". Bluetooth.com. Retrieved 8 May 2019.
- Template:Citep web
- "The Bluetooth Blues". Information Age. 24 May 2001. Archived from the original on 22 December 2007. Retrieved 1 February 2008.
- "Bluetooth traveler". hoovers.com. Archived from the original on 11 January 2011. Retrieved 9 April 2010.
- "Milestones in the Bluetooth advance". Ericsson Technology Licensing. 22 March 2004. Archived from the original on 20 June 2004.
- "'So, that's why it's called Bluetooth!' and other surprising tech name origins". PCWorld. Retrieved 16 August 2017.
- Kardach, Jim (5 March 2008). "Tech History: How Bluetooth got its name". Retrieved 11 June 2013.
- Mark Forsyth. The etymologicon. - Icon Books Ltd. London N79DP, 2011. p. 139.
- "Bluetooth on Twitter".
- "Bluetooth Experience Icons" (PDF). Bluetooth Special Interest Group. Retrieved 21 October 2016.
Bluetooth Experience Icons borrow two of these three features: the blue color and the rune-inspired symbol.
- "Bluetooth Radio Interface, Modulation & Channels". Radio-Electronics.com.
- Bluetooth Specification Version 5.0 (PDF download). Bluetooth Special Interest Group. Retrieved from Bluetooth Core Specifications, December 1, 2017. Page 2535.
- Kurawar, Arwa; Koul, Ayushi; Patil, Viki Tukaram (August 2014). "Survey of Bluetooth and Applications". International Journal of Advanced Research in Computer Engineering & Technology. 3: 2832–2837. ISSN 2278-1323.
- "How Bluetooth Technology Works". Bluetooth SIG. Archived from the original on 17 January 2008. Retrieved 1 February 2008.
- Newton, Harold. (2007). Newton’s telecom dictionary. New York: Flatiron Publishing.
- "Class 1 Bluetooth Dongle Test". Amperordirect.com. Retrieved 4 September 2010.
- "WT41 Long Range Bluetooth Module".
- "BluBear Industrial Long Range Bluetooth 2.1 Module with EDR". Archived from the original on 17 July 2013.
- "OEM Bluetooth Serial Port Module OBS433".
- "Profiles Overview". Bluetooth.com. Retrieved 3 June 2013.
- Ian, Paul. "Wi-Fi Direct vs. Bluetooth 4.0: A Battle for Supremacy". PC World. Retrieved 27 December 2013.
- "History of the Bluetooth Special Interest Group". Bluetooth.com.
- "Portable Wireless Bluetooth Compatible Speakers". Trusound Audio.
- "Bluetooth Revisited". www.techpayout.com. Retrieved 10 May 2016.
- "Bluetooth Technology". mobileinfo.com.
- John Fuller. "How Bluetooth Surveillance Works". howstuffworks. Retrieved 26 May 2015.
- "Wii Controller". Bluetooth SIG. Archived from the original on 20 February 2008. Retrieved 1 February 2008.
- "Telemedicine.jp". Telemedicine.jp. Retrieved 4 September 2010.
- "Tai nghe bluetooth nokia". tainghebluetooth.com.
- "Real Time Location Systems" (PDF). clarinox. Retrieved 4 August 2010.
- "Tenbu's nio Is Kind of Like a Car Alarm for Your Cellphone". OhGizmo!. Retrieved 4 June 2015.
- "Wireless waves used to track travel times". CTV Calgary News. 26 November 2012. Retrieved 11 July 2013.
- "Wireless Data and Power Transfer of an Optogenetic Implantable Visual Cortex Stimulator (PDF Download Available)". ResearchGate. Retrieved 20 September 2017.
- Mroz, Mandy (21 May 2018). "Bluetooth hearing aids: Hearing aids with Bluetooth technology use today's wireless technology to help you easily stay connected to iOS and Android phones, televisions, tablets and other favorite audio devices". Healthy Hearing. Retrieved 15 July 2018.
- "Watch". Bluetooth.com. Archived from the original on 18 September 2010. Retrieved 4 September 2010.
- Eizikowitz, Grant (5 March 2018). "Why does Bluetooth still suck?". Business Insider. Retrieved 15 July 2018.
- "How Bluetooth Works". How Stuff Works. 30 June 2010.
- "Specification Documents". Bluetooth.com. 30 June 2010.
- "Bluetooth for Programmers" (PDF). MIT Computer Science And Artificial Intelligence Laboratory.
- "Bluetooth Wireless Technology FAQ – 2010". Retrieved 4 September 2010.
- "Network Protection Technologie". Changes to Functionality in Microsoft Windows XP Service Pack 2. Microsoft Technet. Archived from the original on 1 January 2008. Retrieved 1 February 2008.
- "Apple Introduces "Jaguar," the Next Major Release of Mac OS X" (Press release). Apple. 17 July 2002. Archived from the original on 18 February 2008. Retrieved 4 February 2008.
- "Official Linux Bluetooth protocol stack". BlueZ. Retrieved 4 September 2010.
- "Bluedroid stack in android". Jacob su. Retrieved 19 June 2019.
- "Affix Bluetooth Protocol Stack for Linux". Affix. Retrieved 19 June 2019.
- Maksim Yevmenkin (2002). "ng_bluetooth.4 — placeholder for global Bluetooth variables". BSD Cross Reference. FreeBSD. Lay summary.
- Iain Hibbert; Itronix Inc (2006). "bluetooth.4 — Bluetooth Protocol Family". BSD Cross Reference. NetBSD. Lay summary.
- Ted Unangst (11 July 2014). "CVS: cvs.openbsd.org: src". source-changes@cvs (Mailing list). OpenBSD.
bluetooth support doesn't work and isn't going anywhere.
- tbert, ed. (29 July 2014). "g2k14: Ted Unangst on the Art of the Tedu". OpenBSD Journal.
Of these, you may possibly miss bluetooth support. Unfortunately, the current code doesn't work and isn't structured properly to encourage much future development.
- Hasso Tepper, ed. (2008). "bluetooth.4 — Bluetooth Protocol Family". BSD Cross Reference. DragonFly BSD. Lay summary.
- "sys/netgraph7/bluetooth/common/ng_bluetooth.c". BSD Cross Reference. DragonFly BSD.
- Sascha Wildner (15 November 2014). "kernel/netgraph7: Port the kernel part of the netgraph7 bluetooth stack". DragonFly BSD.
- "Our History". Bluetooth.com. Retrieved 24 August 2018.
- "English Introduction to Membership". Bluetooth.org. Retrieved 13 May 2014.
- "IEEE Std 802.15.1–2002 – IEEE Standard for Information technology – Telecommunications and information exchange between systems – Local and metropolitan area networks – Specific requirements Part 15.1: Wireless Medium Access Control (MAC) and Physical Layer (PHY) Specifications for Wireless Personal Area Networks (WPANs)". Ieeexplore.ieee.org. doi:10.1109/IEEESTD.2002.93621. Retrieved 4 September 2010.
- Guy Kewney (16 November 2004). "High speed Bluetooth comes a step closer: enhanced data rate approved". Newswireless.net. Retrieved 4 February 2008.
- "IEEE Std 802.15.1–2005 – IEEE Standard for Information technology – Telecommunications and information exchange between systems – Local and metropolitan area networks – Specific requirements Part 15.1: Wireless Medium Access Control (MAC) and Physical Layer (PHY) Specifications for Wireless Personal Area Networks (W Pans)". Ieeexplore.ieee.org. doi:10.1109/IEEESTD.2005.96290. Retrieved 4 September 2010.
- "Specification Documents". Bluetooth SIG. Retrieved 3 May 2012.
- "HTC TyTN Specification" (PDF). HTC. Archived from the original (PDF) on 12 October 2006. Retrieved 4 February 2008.
- "Simple Pairing Whitepaper" (PDF). Version V10r00. Bluetooth SIG. 3 August 2006. Archived from the original (PDF) on 18 October 2006. Retrieved 1 February 2007.
- "Bluetooth Core Version 3.0 + HS specification".
- "Bluetooth Core Specification Addendum (CSA) 1".
- David Meyer (22 April 2009). "Bluetooth 3.0 released without ultrawideband". zdnet.co.uk. Retrieved 22 April 2009.
- "Wimedia.org". Wimedia.org. 4 January 2010. Archived from the original on 26 April 2002. Retrieved 4 September 2010.
- "Wimedia.org". Archived from the original on 23 March 2009. Retrieved 4 September 2010.
- "bluetooth.com". Retrieved 29 January 2015.
- "USB.org". USB.org. 16 March 2009. Archived from the original on 10 June 2011. Retrieved 4 September 2010.
- "Incisor.tv". Incisor.tv. 16 March 2009. Retrieved 4 September 2010.
- "Bluetooth group drops ultrawideband, eyes 60 GHz". EETimes. Retrieved 4 June 2015.
- "Report: Ultrawideband dies by 2013". EETimes. Retrieved 4 June 2015.
- "Simon Stenhouse - Leech Attempt" (PDF). incisor.tv. Retrieved 4 June 2015.
- "Wibree forum merges with Bluetooth SIG" (PDF) (Press release). Nokia. 12 June 2007. Archived from the original (PDF) on 29 December 2014. Retrieved 4 February 2008.
- "Bluetooth.com". Bluetooth.com. Retrieved 4 September 2010.
- "Bluetooth SIG unveils Smart Marks, explains v4.0 compatibility with unnecessary complexity". Engadget.
- "Dialog Semiconductor".
- "BlueNRG Bluetooth® low energy wireless network processor - STMicroelectronics". st.com. Retrieved 4 June 2015.
- ":::笙科電子-Amiccom:::". Archived from the original on 25 August 2013.
- "CSR.com". CSR. Archived from the original on 28 June 2012. Retrieved 7 April 2011.
- "Nordicsemi.com". Nordic Semiconductor. Archived from the original on 2 April 2011. Retrieved 7 April 2011.
- "TI.com". Texas Instruments. Retrieved 7 April 2011.
- "iFixit MacBook Air 13" Mid 2011 Teardown". iFixit.com. Retrieved 27 July 2011.
- "Broadcom.com – BCM20702 – Single-Chip Bluetooth® 4.0 HCI Solution with Bluetooth Low Energy (BLE) Support". Broadcom. Retrieved 27 July 2011.
- "Press Releases Detail | Bluetooth Technology Website". Bluetooth.com. 4 December 2013. Retrieved 13 May 2014.
- "Adopted Specification; Bluetooth Technology Website". Bluetooth.com. 4 December 2013. Retrieved 14 May 2014.
- "DailyTech". Archived from the original on 7 December 2014.
- "HomePod - Technical Specifications". Apple. Retrieved 29 January 2018.
- cnxsoft (10 June 2016). "Bluetooth 5 Promises Four times the Range, Twice the Speed of Bluetooth 4.0 LE Transmissions".
- "Bluetooth 5 standard brings range, speed and capacity boost for IoT".
- "Bluetooth® 5 Quadruples Range, Doubles Speed, Increases Data Broadcasting Capacity by 800% - Bluetooth Technology Website". www.bluetooth.com. Archived from the original on 9 December 2018. Retrieved 12 December 2018.
- ""Bluetooth 5" spec coming next week with 4x more range and 2x better speed [Updated]".
- "Bluetooth 5: everything you need to know".
- "Bluetooth Core Specification v5.0" (PDF download). www.bluetooth.org.
- Stallings, William. (2005). Wireless communications & networks.'=' Upper Saddle River, NJ: Pearson Prentice Hall.
- Juha T. Vainio (25 May 2000). "Bluetooth Security" (PDF). Helsinki University of Technology. Retrieved 1 January 2009.
- Andreas Becker (16 August 2007). "Bluetooth Security & Hacks" (PDF). Ruhr-Universität Bochum. Retrieved 10 October 2007.
- Scarfone, K. & Padgette, J. (September 2008). "Guide to Bluetooth Security" (PDF). National Institute of Standards and Technology. Retrieved 3 July 2013.
- John Fuller. "What is bluejacking?". howstuffworks. Retrieved 26 May 2015.
- Kaviarasu, S., & Muthupandian, P. (2016). Bluejacking Technology: A Review. International Journal of Trend in Research and Development, 3(6), 1. Retrieved October, 2018, from https://www.researchgate.net/publication/314233155_Bluejacking_Technology_A_Review
- "Security Weaknesses in Bluetooth". RSA Security Conf. – Cryptographer’s Track. CiteSeerX 10.1.1.23.7357.
- "Bluetooth". The Bunker. Archived from the original on 26 January 2007. Retrieved 1 February 2007.
- "BlueBug". Trifinite.org. Retrieved 1 February 2007.
- John Oates (15 June 2004). "Virus attacks mobiles via Bluetooth". The Register. Retrieved 1 February 2007.
- "Long Distance Snarf". Trifinite.org. Retrieved 1 February 2007.
- "Dispelling Common Bluetooth Misconceptions". SANS. Retrieved 9 July 2014.
- "F-Secure Malware Information Pages: Lasco.A". F-Secure.com. Archived from the original on 17 May 2008. Retrieved 5 May 2008.
- Ford-Long Wong; Frank Stajano; Jolyon Clulow (April 2005). "Repairing the Bluetooth pairing protocol" (PDF). University of Cambridge Computer Laboratory. Archived from the original (PDF) on 16 June 2007. Retrieved 1 February 2007.
- "Archived copy". Archived from the original on 9 November 2007. Retrieved 2007-11-06.CS1 maint: Archived copy as title (link)
- "Avishai Wool – אבישי וול". tau.ac.il. Retrieved 4 June 2015.
- Yaniv Shaked; Avishai Wool (2 May 2005). "Cracking the Bluetooth PIN". School of Electrical Engineering Systems, Tel Aviv University. Retrieved 1 February 2007.
- "Phone pirates in seek and steal mission". Cambridge Evening News. Archived from the original on 17 July 2007. Retrieved 4 February 2008.
- "Going Around with Bluetooth in Full Safety" (PDF). F-Secure. May 2006. Archived from the original (PDF) on 10 June 2006. Retrieved 4 February 2008.
- Finistere & Zoller. "All your Bluetooth is belong to us" (PDF). archive.hack.lu.
- "BlueBorne Information from the Research Team – Armis Labs". armis. Retrieved 20 September 2017.
- D. Chomienne; M. Eftimakis (20 October 2010). "Bluetooth Tutorial" (PDF). Retrieved 11 December 2009.
- M. Hietanen; T. Alanko (October 2005). "Occupational Exposure Related to Radiofrequency Fields from Wireless Communication Systems" (PDF). XXVIIIth General Assembly of URSI – Proceedings. Union Radio-Scientifique Internationale. Archived from the original (PDF) on 6 October 2006. Retrieved 19 April 2007.
- "Bluetooth Innovation World Cup". Bluetooth.com. Retrieved 4 September 2010.
- "Bluetooth SIG announces winners of Imagine Blue Awards at Bluetooth World". Bluetooth.com. Retrieved 29 March 2017.
- "Bluetooth Breakthrough Awards". bluetooth.org. Archived from the original on 15 July 2015. Retrieved 4 June 2015.
|Wikimedia Commons has media related to Bluetooth.|