View source for Bluetooth

{{Short description|Short-range wireless technology standard}}
{{for-multi|the 10th-century king|Harald Bluetooth|the fungus|Hydnellum caeruleum}} 
{{protection padlock|small=yes}}
{{Use dmy dates|date=April 2024}}
{{Infobox protocol
| name        = Bluetooth
| image       = Bluetooth logo (2016).svg
| image_upright = 1.15
| developer   = [[Bluetooth Special Interest Group]]
| industry    = [[Personal area network]]s 
| introdate   = {{start date and age|p=y|df=yes|1998|5|7}}
| hardware    = {{plainlist|
* [[Personal computer]]s
* [[Smartphone]]s
* [[Video game console|Gaming console]]s
* [[Audio equipment|Audio devices]]
* [[Embedded system|Embedded devices]]
* [[Key finder]]s
}}
| range       = Typically less than {{convert|10|m|sigfig=2|abbr=on}}, up to {{convert|100|m|sigfig=2|abbr=on}}.<br/>Bluetooth 5.0: {{convert|40–400|m|sigfig=1|abbr=on}}<ref name=BTrange>{{cite web|url=http://www.bluair.pl/bluetooth-range|title=Bluetooth Range: 100m, 1&nbsp;km, or 10&nbsp;km?|work=bluair.pl|access-date=4 June 2015|archive-date= 13 June 2015|archive-url=https://web.archive.org/web/20150613072937/http://www.bluair.pl/bluetooth-range|url-status=dead}}</ref><ref name="bluetooth1"/>
| website     = {{URL|https://www.bluetooth.com/|bluetooth.com}}
}}
[[Image:Plantronics Voyager Legend.JPG|thumb|A Bluetooth [[earbud]], an earphone and microphone that communicates with a cellphone using the Bluetooth protocol]]

'''Bluetooth''' is a short-range [[wireless]] technology standard that is used for exchanging data between fixed and mobile devices over short distances and building [[personal area network]]s (PANs). In the most widely used mode, transmission power is limited to 2.5 [[milliwatt]]s, giving it a very short range of up to {{convert|10|m|ft}}. It employs [[Ultra high frequency|UHF]] [[radio wave]]s in the [[ISM band]]s, from 2.402{{nbsp}}[[GHz]] to 2.48{{nbsp}}GHz.<ref name="Muller">{{cite book
 |last1        = Muller
 |first1       = Nathan J.
 |title        = Networking A to Z
 |publisher    = McGraw-Hill Professional
 |date         = 2002
 |pages        = 45–47
 |url          = https://books.google.com/books?id=0qv4KbasX7wC&q=bluetooth&pg=PA45
 |isbn         = 9780071429139
 |access-date  = 14 June 2021
|archive-date = 24 June 2021
|archive-url  = https://web.archive.org/web/20210624205933/https://books.google.com/books?id=0qv4KbasX7wC&q=bluetooth&pg=PA45
 |url-status   = live
}}</ref> It is mainly used as an alternative to wired connections to exchange files between nearby portable devices and connect [[cell phone]]s and music players with [[wireless headphone]]s, [[wireless speakers]], [[HIFI]] systems, [[car audio]] and wireless transmission between [[TVs]] and [[soundbars]].

Bluetooth is managed by the [[Bluetooth Special Interest Group]] (SIG), which has more than 35,000 member companies in the areas of telecommunication, computing, networking, and consumer electronics. The [[Institute of Electrical and Electronics Engineers|IEEE]] standardized Bluetooth as '''IEEE 802.15.1''' but no longer maintains the standard. The Bluetooth SIG oversees the development of the specification, manages the qualification program, and protects the trademarks.<ref>{{cite web |url=https://www.bluetooth.com/about-us/ |title=About us – Bluetooth Technology Website |publisher=Bluetooth.com |access-date=8 May 2019 |archive-date=26 April 2019 |archive-url=https://web.archive.org/web/20190426192848/https://www.bluetooth.com/about-us/ |url-status=live }}</ref> A manufacturer must meet [[Bluetooth Special Interest Group#Qualification|Bluetooth SIG standards]] to market it as a Bluetooth device.<ref>{{cite web |url=https://www.bluetooth.com/develop-with-bluetooth/marketing-branding/brand-enforcement-program/ |title=Brand Enforcement Program |publisher=Bluetooth.com |access-date=8 May 2019 |archive-date=20 February 2018 |archive-url=https://web.archive.org/web/20180220182035/https://www.bluetooth.com/develop-with-bluetooth/marketing-branding/brand-enforcement-program |url-status=live }}</ref> A network of [[patent]]s applies to the technology, which is licensed to individual qualifying devices. {{As of|2021}}, 4.7 billion Bluetooth [[integrated circuit]] chips are shipped annually.<ref>{{cite web |author=Federica Laricchia |url=https://www.statista.com/statistics/1220933/global-bluetooth-device-shipment-forecast/ |title=Global Bluetooth device shipments 2022 |publisher=Statista |date=31 March 2022 |accessdate=7 August 2022}}</ref> Bluetooth was first demonstrated in space in 2024, an early test envisioned to enhance [[Internet of things|IoT]] capabilities.<ref>{{Cite web |last=Paleja |first=Ameya |date=2024-05-03 |title=US achieves 1st-ever space Bluetooth link using satellites |url=https://interestingengineering.com/innovation/bluetooth-connection-space-hubble-network |access-date=2024-05-06 |website=Interesting Engineering}}</ref>

{{TOC limit|4}}

==Etymology==
The name "Bluetooth" was proposed in 1997 by Jim Kardach of [[Intel]], one of the founders of the Bluetooth SIG. The name was inspired by a conversation with Sven Mattisson who related Scandinavian history through tales from [[Frans G. Bengtsson]]'s ''[[The Long Ships]]'', a historical novel about Vikings and the 10th-century Danish king [[Harald Bluetooth]]. Upon discovering a picture of the [[Jelling stones#Runestone of Harald Bluetooth|runestone of Harald Bluetooth]]<ref>{{cite web|url=http://jelling.natmus.dk/en/about-jelling/the-rune-stones/harald-bluetooths-rune-stone|title=Harald Bluetooth's rune stone|publisher=National Museum of Denmark|access-date=22 October 2021|archive-date=26 October 2021|archive-url=https://web.archive.org/web/20211026032119/http://jelling.natmus.dk/en/about-jelling/the-rune-stones/harald-bluetooths-rune-stone/|url-status=live}}</ref> in the book ''A History of the Vikings'' by [[Gwyn Jones (author)|Gwyn Jones]], Kardach proposed Bluetooth as the codename for the short-range wireless program which is now called Bluetooth.<ref name="EETimes">{{cite news|work=eetimes|url=https://www.eetimes.com/tech-history-how-bluetooth-got-its-name|title=Tech History: How Bluetooth got its name|first=Jim|last=Kardach|date=5 March 2008|access-date=11 June 2013|archive-date=5 December 2019|archive-url=https://web.archive.org/web/20191205132704/https://www.eetimes.com/tech-history-how-bluetooth-got-its-name/|url-status=live}}</ref><ref>{{cite book|author=Forsyth, Mark|title= The Etymologicon|url=https://archive.org/details/etymologiconcirc00fors_748|url-access=limited|publisher= Icon Books Ltd.|location= London |date= 2011|page= [https://archive.org/details/etymologiconcirc00fors_748/page/n138 139]|isbn= 9781848313071}}</ref><ref>{{cite web|url=https://www.kardach.com/bluetooth/naming-bluetooth|title=The Naming of a Technology|publisher=kardach.com|author=Kardach, Jim|access-date=22 October 2021|archive-date=22 October 2021|archive-url=https://web.archive.org/web/20211022195739/https://www.kardach.com/bluetooth/naming-bluetooth|url-status=live}}</ref>

According to Bluetooth's official website,
{{Blockquote
|text=Bluetooth was only intended as a placeholder until marketing could come up with something really cool.
Later, when it came time to select a serious name, Bluetooth was to be replaced with either RadioWire or PAN (Personal Area Networking). PAN was the front runner, but an exhaustive search discovered it already had tens of thousands of hits throughout the internet.
A full trademark search on RadioWire couldn't be completed in time for launch, making Bluetooth the only choice. The name caught on fast and before it could be changed, it spread throughout the industry, becoming synonymous with short-range wireless technology.<ref>{{cite web|title=Origin of the Name|url=https://www.bluetooth.com/about-us/bluetooth-origin/|access-date=2021-11-10|website=Bluetooth Technology Website|archive-date=28 December 2020|archive-url=https://web.archive.org/web/20201228185749/https://www.bluetooth.com/about-us/bluetooth-origin/|url-status=live}}</ref> }}

Bluetooth is the [[Anglicised]] version of the Scandinavian ''Blåtand''/''Blåtann'' (or in [[Old Norse]] ''blátǫnn''). It was the [[epithet]] of King Harald Bluetooth, who united the disparate 
Danish tribes into a single kingdom; Kardach chose the name to imply that Bluetooth similarly unites communication protocols.<ref>{{cite web|url=http://www.ericsson.com/bluetooth/companyove/history-bl/|title=Milestones in the Bluetooth advance|publisher=Ericsson Technology Licensing|date=22 March 2004|archive-url=https://web.archive.org/web/20040620150507/http://www.ericsson.com/bluetooth/companyove/history-bl/|archive-date=20 June 2004}}</ref>
===Logo===
[[File:Bluetooth.svg|thumb|upright 0.25|The logo]] 
The Bluetooth logo is a [[bind rune]] merging the [[Younger Futhark]] [[runes]] [[File:Runic letter ior.svg|8px]]&nbsp;(ᚼ, [[Haglaz|Hagall]]) and [[File:Runic letter berkanan.svg|8px]]&nbsp;(ᛒ, [[Berkanan|Bjarkan]]), Harald's initials.<ref>{{cite web|url=https://twitter.com/BluetoothSIG/status/704694301201043456|title=Bluetooth on Twitter|access-date=2 March 2016|archive-date=30 December 2018|archive-url=https://web.archive.org/web/20181230095911/https://twitter.com/BluetoothSIG/status/704694301201043456|url-status=live}}</ref><ref>{{cite web|url=https://www.bluetooth.org/DocMan/handlers/DownloadDoc.ashx?doc_id=46091|title=Bluetooth Experience Icons|publisher=Bluetooth Special Interest Group|quote=Bluetooth Experience Icons borrow two of these three features: the blue color and the rune-inspired symbol.|access-date=21 October 2016|archive-date=23 December 2018|archive-url=https://web.archive.org/web/20181223163534/https://www.bluetooth.org/DocMan/handlers/DownloadDoc.ashx?doc_id=46091|url-status=live}}</ref>

== History ==
{{More citations needed|section|date=February 2024}}
[[File:Ericsson Bluetooth module.jpg|thumb|Ericsson Bluetooth module PBA&nbsp;313 01/2S R2A, manufactured in week&nbsp;22 of 2001]]
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. The purpose was to develop wireless headsets, according to two inventions by [[Johan Ullman]], {{cite patent |country=SE |number=8902098-6 |gdate=1989-06-12}} and {{cite patent |country=SE |number=9202239 |gdate=1992-07-24}}. Nils Rydbeck tasked [[Tord Wingren]] with specifying and Dutchman [[Jaap Haartsen]] and Sven Mattisson with developing.<ref>{{cite web |title=Who Invented Bluetooth? |last=Nguyen |first=Tuan C. |website=ThoughtCo|url=https://www.thoughtco.com/who-invented-bluetooth-4038864 |access-date=11 October 2019 |archive-date=11 October 2019 |archive-url=https://web.archive.org/web/20191011191850/https://www.thoughtco.com/who-invented-bluetooth-4038864 |url-status=live}}</ref> Both were working for Ericsson in Lund.<ref>{{cite news |date=24 May 2001 |title=The Bluetooth |website=Information Age |url=http://www.information-age.com/article/2001/may/the_bluetooth_blues |archive-url=https://web.archive.org/web/20071222231740/http://www.information-age.com/article/2001/may/the_bluetooth_blues |archive-date=22 December 2007 |access-date=1 February 2008}}</ref> Principal design and development began in 1994 and by 1997 the team had a workable solution.<ref name="documents.epo 2012-03-30">{{cite web |title=Presenting the (economic) value of patents nominated for the European Inventor Award 2012 |date=30 March 2012 |publisher=Technopolis Group |url=http://documents.epo.org/projects/babylon/eponet.nsf/0/39F611EACF119B21C12579F30036D7E4/$File/haartsen_en.pdf |access-date=28 September 2021 |archive-date=3 July 2021 |archive-url=https://web.archive.org/web/20210703142518/http://documents.epo.org/projects/babylon/eponet.nsf/0/39F611EACF119B21C12579F30036D7E4/$File/haartsen_en.pdf |url-status=live}}</ref> From 1997 Örjan Johansson became the project leader and propelled the technology and standardization.<ref>{{cite web |title=Grattis Bluetooth, 10 år |website=etn.se |url=http://etn.se/index.php/nyheter/45972-grattis-bluetooth-10-ar |access-date=29 October 2019 |archive-date=29 October 2019 |archive-url=https://web.archive.org/web/20191029131527/http://etn.se/index.php/nyheter/45972-grattis-bluetooth-10-ar |url-status=live}}</ref><ref>{{cite web |title=Sveriges 20 främsta innovationer de senaste 35 åren |website=Veckans affärer |url=http://www.va.se/nyheter/2015/06/24/sveriges-20-framsta-innovationer-de-senaste-35-aren/ |access-date=29 October 2019|archive-date=29 October 2019|archive-url=https://web.archive.org/web/20191029174607/https://www.va.se/nyheter/2015/06/24/sveriges-20-framsta-innovationer-de-senaste-35-aren/ |url-status=live}}</ref><ref>{{cite web |url=https://stik.se/122nobelkandidater_sv.pdf |title=122 Nobel prize candidates |access-date=29 October 2019 |archive-date=29 October 2019 |archive-url=https://web.archive.org/web/20191029174558/https://stik.se/122nobelkandidater_sv.pdf |url-status=live}}</ref><ref>{{cite web |url=https://innovatorsradet.se/innovationer.htm |title=De största innovationerna i modern tid |website=innovatorsradet.se |access-date=29 October 2019 |archive-url=https://web.archive.org/web/20190517151629/https://innovatorsradet.se/innovationer.htm |archive-date=17 May 2019 |url-status=dead}}</ref>

In 1997, Adalio Sanchez, then head of [[IBM]] [[ThinkPad]] product R&D, approached Nils Rydbeck about collaborating on integrating a [[mobile phone]] into a ThinkPad notebook. The two assigned engineers from [[Ericsson]] and [[IBM]] studied the idea. The conclusion was that power consumption on cellphone technology at that time was too high to allow viable integration into a notebook and still achieve adequate battery life. Instead, the two companies agreed to integrate Ericsson's short-link technology on both a ThinkPad notebook and an Ericsson phone to accomplish the goal.

Since neither IBM ThinkPad notebooks nor Ericsson phones were the market share leaders in their respective markets at that time, Adalio Sanchez and Nils Rydbeck agreed to make the short-link technology an open industry standard to permit each player maximum market access. Ericsson contributed the short-link radio technology, and IBM contributed patents around the logical layer. Adalio Sanchez of IBM then recruited Stephen Nachtsheim of Intel to join and then Intel also recruited [[Toshiba]] and [[Nokia]]. In May&nbsp;1998, the Bluetooth SIG was launched with IBM and Ericsson as the founding signatories and a total of five members: Ericsson, Intel, Nokia, Toshiba, and IBM.

The first Bluetooth device was revealed in 1999. It was a hands-free mobile headset that earned the "Best of show Technology Award" at [[COMDEX]]. The first Bluetooth mobile phone was the unreleased prototype Ericsson&nbsp;T36, though it was the revised Ericsson model [[Ericsson T39|T39]] that actually made it to store shelves in June 2001. However Ericsson released the R520m in Quarter 1 of 2001,<ref>{{cite web |url=https://www.mobilephonemuseum.com/phone-detail/r520m |title=Mobile Phone Museum |website=mobilephonemuseum.com}}</ref> making the R520m the first ever commercially available Bluetooth phone. In parallel, IBM introduced the IBM ThinkPad&nbsp;A30 in October&nbsp;2001 which was the first notebook with integrated Bluetooth.

Bluetooth's early incorporation into consumer electronics products continued at Vosi Technologies in Costa Mesa, California, initially overseen by founding members Bejan Amini and Tom Davidson. Vosi Technologies had been created by real estate developer Ivano Stegmenga, with United States Patent 608507, for communication between a cellular phone and a vehicle's audio system. At the time, Sony/Ericsson had only a minor market share in the cellular phone market, which was dominated in the US by Nokia and Motorola. Due to ongoing negotiations for an intended licensing agreement with Motorola beginning in the late 1990s, Vosi could not publicly disclose the intention, integration, and initial development of other enabled devices which were to be the first "[[Home automation|Smart Home]]" internet connected devices.

Vosi needed a means for the system to communicate without a wired connection from the vehicle to the other devices in the network. Bluetooth was chosen, since [[Wi-Fi]] was not yet readily available or supported in the public market. Vosi had begun to develop the Vosi Cello integrated vehicular system and some other internet connected devices, one of which was intended to be a table-top device named the Vosi Symphony, networked with Bluetooth. Through the negotiations with [[Motorola]], Vosi introduced and disclosed its intent to integrate Bluetooth in its devices. In the early 2000s a legal battle<ref>{{cite web |title=Motorola Inc. v. Vosi Technologies Inc. |department=Cases |website=casetext.com |url=https://casetext.com/case/motorola-inc-v-vosi-technologies-inc|archive-url=https://web.archive.org/web/20210414113718/https://casetext.com/case/motorola-inc-v-vosi-technologies-inc|url-status=dead|archive-date=14 April 2021}}</ref> ensued between Vosi and Motorola, which indefinitely suspended release of the devices. Later, Motorola implemented it in their devices, which initiated the significant propagation of Bluetooth in the public market due to its large market share at the time.

In 2012, Jaap Haartsen was nominated by the [[European Patent Office]] for the [[European Inventor Award]].<ref name="documents.epo 2012-03-30"/>

== Implementation ==
Bluetooth operates at frequencies between 2.402 and 2.480{{nbsp}}GHz, or 2.400 and 2.4835{{nbsp}}GHz, including [[guard band]]s 2{{nbsp}}MHz wide at the bottom end and 3.5{{nbsp}}MHz wide at the top.<ref name="Radio-Electronics.com">{{cite web |url=http://www.radio-electronics.com/info/wireless/bluetooth/radio-interface-modulation.php |title=Bluetooth Radio Interface, Modulation & Channels |publisher=Radio-Electronics.com |access-date=24 March 2012 |archive-date=2 January 2012 |archive-url=https://web.archive.org/web/20120102064023/http://www.radio-electronics.com/info/wireless/bluetooth/radio-interface-modulation.php |url-status=live }}</ref> This is in the globally unlicensed (but not unregulated) industrial, scientific and medical ([[ISM band|ISM]]) 2.4{{nbsp}}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{{nbsp}}MHz. It usually performs 1600{{nbsp}}hops per second, with [[adaptive frequency-hopping spread spectrum|adaptive frequency-hopping]] (AFH) enabled.<ref name="Radio-Electronics.com"/> [[Bluetooth Low Energy]] uses 2{{nbsp}}MHz spacing, which accommodates 40 channels.<ref>{{cite web|url=https://www.bluetooth.org/DocMan/handlers/DownloadDoc.ashx?doc_id=421043|title=Bluetooth Specification Version 5.0|website=Bluetooth Special Interest Group|access-date=8 December 2016|archive-date=23 December 2018|archive-url=https://web.archive.org/web/20181223163509/https://www.bluetooth.org/DocMan/handlers/DownloadDoc.ashx?doc_id=421043|url-status=live}}</ref>

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{{nbsp}}[[Mbit/s]] is possible. The term ''Enhanced Data Rate'' (''EDR'') is used to describe π/4-DPSK (EDR2) and 8-DPSK (EDR3) schemes, transferring 2 and 3{{nbsp}}Mbit/s respectively.

In 2019, Apple published an extension called HDR which supports data rates of 4 (HDR4) and 8 (HDR8)&nbsp;Mbit/s using π/4-[[DQPSK]] modulation on 4&nbsp;MHz channels with forward error correction (FEC).<ref>{{cite web|url=http://www.freepatentsonline.com/y2019/0104424.html |title=Ultra-Low Latency Audio Over Bluetooth – Apple Inc |publisher=Freepatentsonline.com |accessdate=21 July 2022}}</ref>

Bluetooth is a [[packet switching|packet-based protocol]] with a [[master/slave (technology)|master/slave architecture]]. One master may communicate with up to seven slaves in a [[piconet]]. All devices within a given piconet use the clock provided by the master as the base for packet exchange. The master clock ticks with a period of 312.5{{nbsp}}[[μs]], two clock ticks then make up a slot of 625{{nbsp}}μs, and two slots make up a slot pair of 1250{{nbsp}}μ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,<ref>{{Cite journal|last1=Gomez|first1=Carles|last2=Oller|first2=Joaquim|last3=Paradells|first3=Josep|date=29 August 2012|title=Overview and Evaluation of Bluetooth Low Energy: An Emerging Low-Power Wireless Technology|journal=Sensors|volume=12|issue=9|pages=11734–11753|doi=10.3390/s120911734|issn=1424-8220|pmc=3478807|bibcode=2012Senso..1211734G|doi-access=free}}</ref> which [[Bluetooth Low Energy#Radio interface|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/leader 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 scheduling|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.<ref>{{Cite journal |last3=Patil |last2=Koul |last1=Kurawar |first3=Viki Tukaram |first2=Ayushi |first1=Arwa |date=August 2014 |title=Survey of Bluetooth and Applications |journal=International Journal of Advanced Research in Computer Engineering & Technology |volume=3 |pages=2832–2837 |issn=2278-1323}}</ref>

== Uses ==
Bluetooth is a standard wire-replacement communications protocol primarily designed for low power consumption, with a short range based on low-cost [[transceiver]] [[integrated circuit|microchips]] in each device.<ref>{{cite web|url=http://www.bluetooth.com/Bluetooth/Technology/Works/|title=How Bluetooth Technology Works|publisher=Bluetooth SIG|access-date=1 February 2008|archive-url = https://web.archive.org/web/20080117000828/http://bluetooth.com/Bluetooth/Technology/Works/ <!-- Bot retrieved archive --> |archive-date = 17 January 2008}}</ref> 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|quasi optical]]'' wireless path must be viable.<ref name="autogenerated1">{{cite book|last=Newton|first=Harold|year=2007|title=Newton's telecom dictionary|location=New York|publisher=Flatiron Publishing|isbn=9780979387364}}</ref>

=== Bluetooth classes and power use ===
{| class="wikitable floatright" style="text-align:right;"
|+ Bluetooth device power by class
|-
! rowspan=2 | Class
! colspan=2 | Maximum permitted power
|-
! mW
! [[dBm]]
|-
! 1
| 10–100 || +10–+20
|-
! 1.5*
| 2.5–10 || +4–+10
|-
! 2
| 1–2.5 || 0–+4
|-
! 3
| 0.01–1 || &minus;20–0
|-
| colspan="4" style="text-align:left;"| * Class{{nbsp}}1.5 included in Class{{nbsp}}1 for BR/EDR
|-
| colspan="4" style="text-align:left;"| Source: Bluetooth Core Specification revision{{nbsp}}5.3,<br>Volume{{nbsp}}6, Part{{nbsp}}A, §{{nbsp}}3, and<br>Volume{{nbsp}}2, Part{{nbsp}}A, §{{nbsp}}3, [https://www.bluetooth.com/specifications/specs/core-specification-5-3/ Bluetooth SIG]
|}
Historically, the Bluetooth range was defined by the radio class, with a lower class (and higher output power) having larger range.<ref name="bluetooth1">{{cite web |url=http://www.bluetooth.com/Pages/Basics.aspx |title=Basics {{pipe}} Bluetooth Technology Website |publisher=Bluetooth.com |date=23 May 2010 |access-date=16 October 2012 |archive-date=28 October 2012 |archive-url=https://web.archive.org/web/20121028194747/http://www.bluetooth.com/Pages/basics.aspx |url-status=dead }}</ref> The actual range of a given link depends on several qualities of both communicating devices and the [[Path loss|air and obstacles in between]]. The primary attributes affecting range are the data rate, protocol (Bluetooth Classic or Bluetooth Low Energy), transmission power, and receiver sensitivity, and the relative orientations and gains of both antennas.<ref>{{cite web|url=https://www.bluetooth.com/learn-about-bluetooth/key-attributes/range/|title=Understanding Bluetooth Range|date=April 2022 |publisher=Bluetooth SIG|access-date=29 June 2022}}</ref>

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&nbsp;2 devices, with little difference in range whether the other end of the link is a Class&nbsp;1 or Class&nbsp;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&nbsp;2 device is connecting to a Class&nbsp;1 transceiver with both higher sensitivity and transmission power than a typical Class&nbsp;2 device.<ref>{{cite web |url=https://inventionduniya.in/what-is-bluetooth-and-how-to-use-bluetooth/ |archive-url=https://web.archive.org/web/20211010085437/https://inventionduniya.in/what-is-bluetooth-and-how-to-use-bluetooth/ |url-status=dead |archive-date=10 October 2021 |title=Class 1 Bluetooth Dongle Test |publisher=Amperordirect.com |access-date=4 September 2010 }}</ref> In general, however, Class&nbsp;1 devices have sensitivities similar to those of Class&nbsp;2 devices. Connecting two Class&nbsp;1 devices with both high sensitivity and high power can allow ranges far in excess of the typical 100&nbsp;m, depending on the throughput required by the application. Some such devices allow open field ranges of up to 1&nbsp;km and beyond between two similar devices without exceeding legal emission limits.<ref name="WT41">{{cite web |url=http://www.bluegiga.com/WT41_Long_Range_Bluetooth_Module |title=WT41 Long Range Bluetooth Module |access-date=28 August 2013 |archive-date=3 July 2013 |archive-url=https://web.archive.org/web/20130703045646/http://www.bluegiga.com/WT41_Long_Range_Bluetooth_Module |url-status=live }}</ref><ref name="BluBear">{{cite web |url=http://www.lesswire.com/en/products/embedded-wireless-modules/bluetooth/bluebear/overview/ |archive-url=https://web.archive.org/web/20130717051641/http://www.lesswire.com/en/products/embedded-wireless-modules/bluetooth/bluebear/overview/ |url-status=dead |archive-date=17 July 2013 |title=BluBear Industrial Long Range Bluetooth 2.1 Module with EDR  }}</ref><ref name="OBS433">{{cite web |url=http://www.connectblue.com/products/classic-bluetooth-products/classic-bluetooth-modules/bluetooth-serial-port-module-obs433/ |title=OEM Bluetooth Serial Port Module OBS433 |access-date=28 August 2013 |archive-date=16 July 2013 |archive-url=https://web.archive.org/web/20130716065225/http://www.connectblue.com/products/classic-bluetooth-products/classic-bluetooth-modules/bluetooth-serial-port-module-obs433/ |url-status=live }}</ref>

=== Bluetooth profile ===
{{Main|List of Bluetooth profiles}}

To use Bluetooth wireless technology, a device must be able to interpret certain Bluetooth profiles. 
For example,

* The [[List of Bluetooth profiles#Headset Profile (HSP)|Headset Profile (HSP)]] connects headphones and earbuds to a cell phone or laptop.
* The [[List of Bluetooth profiles#Health Device Profile (HDP)|Health Device Profile (HDP)]] can connect a cell phone to a digital thermometer or heart rate detector.
* The [[List of Bluetooth profiles#Video Distribution Profile (VDP)|Video Distribution Profile (VDP)]] sends a video stream from a video camera to a TV screen or a recording device.

Profiles 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.<ref>{{cite web|url=https://www.bluetooth.com/specifications/profiles-overview/|title=Traditional Profile Specifications|publisher=Bluetooth.com|access-date=28 October 2019|archive-date=11 March 2020|archive-url=https://web.archive.org/web/20200311022237/https://www.bluetooth.com/specifications/profiles-overview/|url-status=live}}</ref>

=== List of applications ===
[[File:Bluetooth headset.jpg|thumb|250px|right|A typical Bluetooth mobile phone [[headset (audio)|headset]] from the early 2000s]]
[[File:JBL GO2 Bluetooth speaker 00 10 27 681000.jpeg|thumb|A handheld, waterproof JBL [[Bluetooth speaker]] with a rechargeable battery, made in the late 2010s]]
* Wireless control and communication between a mobile phone and a [[handsfree]] [[headset (audio)|headset]]. This was one of the earliest applications to become popular.<ref>{{cite web|url=http://www.bluetooth.com/Pages/History-of-Bluetooth.aspx|title=History of the Bluetooth Special Interest Group|publisher=Bluetooth.com|access-date=15 May 2015|archive-date=1 July 2015|archive-url=https://web.archive.org/web/20150701073626/http://www.bluetooth.com/Pages/History-of-Bluetooth.aspx|url-status=live}}</ref>
* Wireless control of audio and communication functions between a mobile phone and a Bluetooth compatible car stereo system (and sometimes [[SIM Access Profile|between the SIM card and the car phone]]<ref>{{Cite book|last=Sauter|first=Martin|url=https://books.google.com/books?id=aEewDwAAQBAJ&pg=PA491|title=From GSM to LTE-Advanced Pro and 5G: An Introduction to Mobile Networks and Mobile Broadband|date=2 August 2017|publisher=John Wiley & Sons|isbn=978-1-119-34690-6|page=491|access-date=13 September 2020|archive-date=14 April 2021|archive-url=https://web.archive.org/web/20210414135830/https://books.google.com/books?id=aEewDwAAQBAJ&pg=PA491|url-status=live}}</ref><ref>{{Cite book|last=Penttinen|first=Jyrki T. J.|url=https://books.google.com/books?id=HRQmBgAAQBAJ&pg=PA129|title=The Telecommunications Handbook: Engineering Guidelines for Fixed, Mobile and Satellite Systems|date=16 March 2015|publisher=John Wiley & Sons|isbn=978-1-119-94488-1|page=129|access-date=13 September 2020|archive-date=25 January 2021|archive-url=https://web.archive.org/web/20210125202158/https://books.google.com/books?id=HRQmBgAAQBAJ&pg=PA129|url-status=live}}</ref>).
*Wireless communication between a smartphone and a [[smart lock]] for unlocking doors.
* Wireless control of and communication with iOS and Android device phones, tablets and portable [[wireless speaker]]s.<ref>{{cite web|url=https://www.trusoundaudio.com/collections/all|title=Portable Wireless Bluetooth Compatible Speakers|publisher=Trusound Audio|access-date=7 April 2016|archive-url=https://web.archive.org/web/20160418105028/https://www.trusoundaudio.com/collections/all|archive-date=18 April 2016|url-status=dead}}</ref>
* 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.<ref>{{cite web|title=Bluetooth Revisited|url=https://techpayout.com/blog/bluetooth-revisited/|website=techpayout.com|access-date=10 May 2016|date=27 March 2014|archive-date=3 June 2016|archive-url=https://web.archive.org/web/20160603110522/https://techpayout.com/blog/bluetooth-revisited/|url-status=dead}}</ref>
* Wireless networking between PCs in a confined space and where little bandwidth is required.<ref>{{cite web
|url=http://www.mobileinfo.com/Bluetooth/applic.htm
|title=Bluetooth Technology
|publisher=mobileinfo.com
|access-date=11 May 2015
|archive-date=23 December 2018
|archive-url=https://web.archive.org/web/20181223163529/http://www.mobileinfo.com/Bluetooth/applic.htm
|url-status=live
}}</ref>
* Wireless communication with PC input and output devices, the most common being the [[computer mouse|mouse]], [[keyboard technology|keyboard]] and [[computer printer|printer]].
* Transfer of files, contact details, calendar appointments, and reminders between devices with OBEX{{efn|Many operating systems delete incomplete files if the file transfer has failed.}} and sharing directories [[FTP server|via FTP]].<ref>{{cite web |url=https://www.youtube.com/watch?v=3BdT1DGyGT4| archive-url=https://ghostarchive.org/varchive/youtube/20211123/3BdT1DGyGT4| archive-date=23 November 2021 | url-status=live|title=Samsung Omnia II: How to Transfer Files with Bluetooth FTP| via=[[YouTube]]|date=11 December 2009}}{{cbignore}}</ref>
* Triggering the camera shutter of a [[smartphone]] using a Bluetooth controlled [[selfie stick]].<ref>{{Cite web |last=Mattei |first=Giovanni |title=Selfie stick: i migliori modelli per foto e video eccellenti |url=https://www.telefonino.net/guide/selfie-stick/ |access-date=31 October 2022 |website=telefonino.net |language=it}}</ref>
* Replacement of previous wired [[RS-232]] serial communications in test equipment, [[Global Positioning System|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.<ref>{{cite news|url=http://electronics.howstuffworks.com/bluetooth-surveillance1.htm|title=How Bluetooth Surveillance Works|author=John Fuller|date=28 July 2008|newspaper=howstuffworks|access-date=26 May 2015|archive-date=26 May 2015|archive-url=https://web.archive.org/web/20150526093443/http://electronics.howstuffworks.com/bluetooth-surveillance1.htm|url-status=live}}</ref>
* Wireless bridge between two Industrial Ethernet (e.g., [[PROFINET]]) networks.
* Game consoles have been using Bluetooth as a wireless communications protocol for peripherals since the [[History of video game consoles (seventh generation)|seventh generation]], including [[Nintendo]]'s [[Wii]]<ref>{{cite web|url=http://bluetooth.com/Bluetooth/Products/Products/Product_Details.htm?ProductID=2951|title=Wii Controller|publisher=Bluetooth SIG|access-date=1 February 2008|archive-url = https://web.archive.org/web/20080220080315/http://bluetooth.com/Bluetooth/Products/Products/Product_Details.htm?ProductID=2951 |archive-date = 20 February 2008}}</ref> and [[Sony]]'s [[PlayStation 3]] which use Bluetooth for their respective 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.<ref>{{cite web |url=http://www.telemedicine.jp/ |title=Telemedicine.jp |publisher=Telemedicine.jp |access-date=4 September 2010 |archive-date=23 December 2018 |archive-url=https://web.archive.org/web/20181223163413/http://www.telemedicine.jp/ |url-status=live }}</ref><ref>{{cite web|url=http://tainghebluetooth.com/tai-nghe-bluetooth-nokia|title=Tai nghe bluetooth nokia|publisher=tainghebluetooth.com|access-date=6 September 2016|archive-date=21 September 2016|archive-url=https://web.archive.org/web/20160921022818/http://tainghebluetooth.com/tai-nghe-bluetooth-nokia/|url-status=live}}</ref>
* Allowing a [[DECT]] phone to ring and answer calls on behalf of a nearby mobile phone.
*[[Real-time locating system|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.<ref>{{cite web|url=http://www.clarinox.com/docs/whitepapers/RealTime_main.pdf|title=Real Time Location Systems|publisher=clarinox|access-date=4 August 2010|archive-date=28 December 2019|archive-url=https://web.archive.org/web/20191228211943/https://www.clarinox.com/docs/whitepapers/RealTime_main.pdf|url-status=live}}</ref>
* 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.
* [[Calgary]], [[Alberta]], Canada's Roads Traffic division uses data collected from travelers' Bluetooth devices to predict travel times and road congestion for motorists.<ref>{{cite web |url=https://www.ctvnews.ca/calgary/article/wireless-waves-used-to-track-travel-times/ |title=Wireless waves used to track travel times |publisher=CTV Calgary News |date=26 November 2012 |access-date=11 July 2013 |archive-date=1 July 2013 |archive-url=https://web.archive.org/web/20130701092731/http://calgary.ctvnews.ca/wireless-waves-used-to-track-travel-times-1.1054731 |url-status=live }}</ref>
* Wireless transmission of audio (a more reliable alternative to [[FM transmitter (personal device)|FM transmitters]])
* Live video streaming to the visual cortical implant device by Nabeel Fattah in Newcastle university 2017.<ref>{{cite book|chapter-url=https://www.researchgate.net/publication/284639806|doi=10.1109/EMBC.2015.7320250 |chapter=Wireless data and power transfer of an optogenetic implantable visual cortex stimulator |title=2015 37th Annual International Conference of the IEEE Engineering in Medicine and Biology Society (EMBC) |date=2015 |last1=Fattah |first1=Nabeel |last2=Laha |first2=Soumyasanta |last3=Sokolov |first3=Danil |last4=Chester |first4=Graeme |last5=Degenaar |first5=Patrick |volume=2015 |pages=8006–8009 |pmid=26738150 |isbn=978-1-4244-9271-8 |s2cid=4575272 }}</ref>
* Connection of [[motion controller]]s to a PC when using VR headsets
* Wireless connection between [[TVs]] and [[soundbars]].

=== Devices ===
[[File:TP-Link Archer T2UB Nano dongle plugged in to a computer.jpg|thumb|250x250px|A modern Bluetooth [[USB]] dongle]]
Bluetooth exists in numerous products such as telephones, [[Wireless speaker|speakers]], tablets, media players, robotics systems, laptops, and game console equipment as well as some high definition [[Headset (audio)|headsets]], [[modem]]s, [[hearing aid]]s<ref name="Bluetooth Hearing Aids">{{cite web |title=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 |last=Mroz |first=Mandy |date=21 May 2018 |url=https://www.healthyhearing.com/help/hearing-aids/bluetooth |website=Healthy Hearing |access-date=15 July 2018 |archive-date=25 May 2019 |archive-url=https://web.archive.org/web/20190525124635/https://www.healthyhearing.com/help/hearing-aids/bluetooth |url-status=live }}</ref> and even watches.<ref>{{cite web |url=http://www.bluetooth.com/English/Products/Pages/Watch.aspx |title=Watch |publisher=Bluetooth.com |access-date=4 September 2010 |archive-url=https://web.archive.org/web/20100918122452/http://www.bluetooth.com/English/Products/pages/watch.aspx |archive-date=18 September 2010 |url-status=dead }}</ref> 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.<ref name="Devices">{{cite web |url=http://www.howstuffworks.com/bluetooth.htm |title=How Bluetooth Works |publisher=How Stuff Works |date=30 June 2010 |access-date=12 April 2012 |archive-date=4 April 2012 |archive-url=https://web.archive.org/web/20120404182314/http://www.howstuffworks.com/bluetooth.htm |url-status=live }}</ref> Bluetooth devices can advertise all of the services they provide.<ref>{{cite web |url=https://www.bluetooth.com/specifications |title=Specification Documents |publisher=Bluetooth.com |date=30 June 2010 |access-date=12 September 2017 |archive-date=12 September 2017 |archive-url=https://web.archive.org/web/20170912191437/https://www.bluetooth.com/specifications |url-status=live }}</ref> This makes using services easier, because more of the security, [[network address]] and permission configuration can be automated than with many other network types.<ref name="Devices" />

== Computer requirements ==
[[File:BluetoothUSB.jpg|thumb|250px|right|An early Bluetooth [[USB]] dongle]]
[[File:DELL TrueMobile 350 Bluetooth card.jpg|thumb|250px|right|An early internal notebook Bluetooth card (14×36×4{{nbsp}}mm)]]

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 computer]]s 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]]".

Unlike its predecessor, [[Infrared Data Association|IrDA]], which requires a separate adapter for each device, Bluetooth lets multiple devices communicate with a computer over a single adapter.<!-- please clarify – all versions? or only some? --><ref>{{cite web|url=http://people.csail.mit.edu/rudolph/Teaching/Articles/PartOfBTBook.pdf|title=Bluetooth for Programmers|publisher=MIT Computer Science And Artificial Intelligence Laboratory|access-date=11 May 2015|archive-date=23 December 2018|archive-url=https://web.archive.org/web/20181223163532/http://people.csail.mit.edu/rudolph/Teaching/Articles/PartOfBTBook.pdf|url-status=live}}</ref>

=== Operating system implementation ===
{{further|Bluetooth stack}}

For [[Microsoft]] platforms, [[Windows XP Service Pack 2]] and SP3 releases work natively with Bluetooth v1.1, v2.0 and v2.0+EDR.<ref name="WinBT 2010 FAQ">{{cite web |url=http://download.microsoft.com/download/9/c/5/9c5b2167-8017-4bae-9fde-d599bac8184a/Bth_FAQ.docx |title=Bluetooth Wireless Technology FAQ{{nbsp}}– 2010 |access-date=4 September 2010 |archive-date=23 December 2018 |archive-url=https://web.archive.org/web/20181223163558/http://download.microsoft.com/download/9/c/5/9c5b2167-8017-4bae-9fde-d599bac8184a/Bth_FAQ.docx |url-status=live }}</ref> Previous versions required users to install their Bluetooth adapter's own drivers, which were not directly supported by Microsoft.<ref>{{cite web|publisher=Microsoft Technet|website=Changes to Functionality in Microsoft Windows XP Service Pack 2|title=Network Protection Technologie|url=http://www.microsoft.com/technet/prodtechnol/winxppro/maintain/sp2netwk.mspx|access-date=1 February 2008|archive-url=https://web.archive.org/web/20080101194700/http://www.microsoft.com/technet/prodtechnol/winxppro/maintain/sp2netwk.mspx|archive-date=1 January 2008|url-status=dead}}</ref> 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.<ref name="WinBT 2010 FAQ" /> Windows 7 works with Bluetooth v2.1+EDR and Extended Inquiry Response (EIR).<ref name="WinBT 2010 FAQ" />
The Windows XP and Windows Vista/Windows 7 Bluetooth stacks support the following Bluetooth profiles natively: PAN, SPP, [[Dial-up Internet access|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.<ref name="WinBT 2010 FAQ" /> Windows 8 and later support Bluetooth Low Energy (BLE). 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.

[[Apple Inc.|Apple]] products have worked with Bluetooth since [[Mac OS X v10.2|Mac OS{{nbsp}}X&nbsp;v10.2]], which was released in 2002.<ref>{{cite press release|url=https://www.apple.com/pr/library/2002/jul/17jaguar.html|title=Apple Introduces "Jaguar," the Next Major Release of Mac OS X|publisher=Apple|date=17 July 2002|access-date=4 February 2008|archive-url=https://web.archive.org/web/20080218140207/http://www.apple.com/pr/library/2002/jul/17jaguar.html|archive-date=18 February 2008|url-status=dead}}</ref>

[[Linux]] has two popular [[Bluetooth stack#Linux|Bluetooth stack]]s, BlueZ and Fluoride. The BlueZ stack is included with most Linux kernels and was originally developed by [[Qualcomm]].<ref>{{cite web |url=http://www.bluez.org/ |title=Official Linux Bluetooth protocol stack |publisher=BlueZ |access-date=4 September 2010 |archive-date=22 May 2019 |archive-url=https://web.archive.org/web/20190522085659/http://www.bluez.org/ |url-status=live }}</ref> Fluoride, earlier known as Bluedroid is included in Android OS and was originally developed by [[Broadcom]].<ref>{{cite web |url=https://medium.com/@zpcat/bluedroid-stack-in-android-564c58b451f4 |title=Bluedroid stack in android |date=10 May 2016 |publisher=Jacob su |access-date=19 June 2019 |archive-date=19 June 2019 |archive-url=https://web.archive.org/web/20190619145347/https://medium.com/@zpcat/bluedroid-stack-in-android-564c58b451f4 |url-status=live }}</ref>
There is also Affix stack, developed by [[Nokia]]. It was once popular, but has not been updated since 2005.<ref>{{cite web |url=https://affix.sourceforge.net/ |title=Affix Bluetooth Protocol Stack for Linux |publisher=Affix |access-date=19 June 2019 |archive-date=5 November 2018 |archive-url=https://web.archive.org/web/20181105100905/http://affix.sourceforge.net/ |url-status=live }}</ref>

[[FreeBSD]] has included Bluetooth since its v5.0 release, implemented through [[netgraph]].<ref name=f>{{cite web |author= Maksim Yevmenkin |date= 2002 |url= http://bxr.su/f/share/man/man4/ng_bluetooth.4 |title= ng_bluetooth.4 – placeholder for global Bluetooth variables |website= BSD Cross Reference |publisher= [[FreeBSD]]  |access-date= 10 April 2019 |archive-date= 12 February 2022 |archive-url= https://web.archive.org/web/20220212025010/http://bxr.su/FreeBSD/share/man/man4/ng_bluetooth.4 |url-status= live}}</ref><ref>{{cite book |entry=ng_bluetooth |title=BSD Kernel Interfaces Manual |entry-url=https://www.freebsd.org/cgi/man.cgi?query=ng_bluetooth&sektion=4 |publisher=FreeBSD}}</ref>

[[NetBSD]] has included Bluetooth since its v4.0 release.<ref name=n>{{cite web |author1= Iain Hibbert |author2= Itronix Inc |date= 2006 |url= http://bxr.su/n/share/man/man4/bluetooth.4 |title= bluetooth.4 – Bluetooth Protocol Family |website= BSD Cross Reference |publisher= [[NetBSD]] |access-date= 10 April 2019 |archive-date= 12 February 2022 |archive-url= https://web.archive.org/web/20220212024954/http://bxr.su/NetBSD/share/man/man4/bluetooth.4 |url-status= live }}</ref><ref>{{cite book |entry=bluetooth(4) |title=NetBSD Manual Pages |entry-url= http://mdoc.su/n/bluetooth.4 |archive-url=https://web.archive.org/web/20210313080003/http://man.netbsd.org/bluetooth.4 |archive-date=13 March 2021 |publisher=NetBSD}}</ref> Its Bluetooth stack was ported to [[OpenBSD]] as well, however OpenBSD later removed it as unmaintained.<ref>{{cite mailing list |author= Ted Unangst |date= 11 July 2014 |url= https://marc.info/?l=openbsd-cvs&m=140511572108715&w=2 |title= CVS: cvs.openbsd.org: src |mailing-list= source-changes@cvs |publisher= [[OpenBSD]] |quote= "bluetooth support doesn't work and isn't going anywhere." |access-date= 10 April 2019 |archive-date= 19 January 2019 |archive-url= https://web.archive.org/web/20190119041354/https://marc.info/?l=openbsd-cvs&m=140511572108715&w=2 |url-status= live }}</ref><ref>{{cite web |editor= tbert |date= 29 July 2014 |url= https://undeadly.org/cgi?action=article&sid=20140729070721 |title= g2k14: Ted Unangst on the Art of the Tedu |website= [[OpenBSD Journal]] |quote= "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." |access-date= 10 April 2019 |archive-date= 24 March 2019 |archive-url= https://web.archive.org/web/20190324221310/http://undeadly.org/cgi?action=article&sid=20140729070721 |url-status= live }}</ref>

[[DragonFly BSD]] has had NetBSD's Bluetooth implementation since 1.11 (2008).<ref name=d>{{cite web |editor= Hasso Tepper |date= 2008 |url= http://bxr.su/d/share/man/man4/bluetooth.4 |title= bluetooth.4 – Bluetooth Protocol Family |website= BSD Cross Reference |publisher= [[DragonFly BSD]] |access-date= 10 April 2019 |archive-date= 12 February 2022 |archive-url= https://web.archive.org/web/20220212025009/http://bxr.su/DragonFly/share/man/man4/bluetooth.4 |url-status= live }}</ref><ref>{{cite book |entry=bluetooth |title=DragonFly On-Line Manual Pages |entry-url=https://www.dragonflybsd.org/cgi/web-man?command=bluetooth&section=4 |publisher=DragonFly}}</ref> A [[netgraph]]-based implementation from [[FreeBSD]] has also been available in the tree, possibly disabled until 2014-11-15, and may require more work.<ref name=d_ng>{{cite web |url= http://bxr.su/d/sys/netgraph7/bluetooth/common/ng_bluetooth.c |title= sys/netgraph7/bluetooth/common/ng_bluetooth.c |website= BSD Cross Reference |publisher= [[DragonFly BSD]] |access-date= 10 April 2019 |archive-date= 12 February 2022 |archive-url= https://web.archive.org/web/20220212024952/http://bxr.su/DragonFly/sys/netgraph7/bluetooth/common/ng_bluetooth.c |url-status= live }}</ref><ref>{{cite web |author= Sascha Wildner |date= 15 November 2014 |url= https://github.com/DragonFlyBSD/DragonFlyBSD/commit/e85b99abf6da4a83a7dc495b0ef37ce19864149f |title= kernel/netgraph7: Port the kernel part of the netgraph7 bluetooth stack |publisher= [[DragonFly BSD]] |access-date= 10 April 2019 |archive-date= 30 April 2019 |archive-url= https://web.archive.org/web/20190430044658/https://github.com/DragonFlyBSD/DragonFlyBSD/commit/e85b99abf6da4a83a7dc495b0ef37ce19864149f |url-status= live }}</ref>

== Specifications and features ==
{{mw-datatable}}
{| class="wikitable mw-datatable floatright" style="text-align:center;"
|+Bluetooth versions
! colspan="2" |Version
! rowspan="2" |Adoption year
! colspan="2" |Maximum rate
! rowspan="2" |Max range
! rowspan="2" |Radio frequency
|-
!Major
!Minor
!Classic
!Low Energy
|-
! rowspan="3" |1
!1.0
|1999
| rowspan="2" |732.2 kbit/s
| rowspan="6" {{N/A}}
| rowspan="6" |10 m
| rowspan="16" |2.4&nbsp;GHz
|-
!1.1
|2001
|-
!1.2
|2003
|1 Mbit/s
|-
! rowspan="2" |2
!2.0
|2004
| rowspan="2" |2.1 Mbit/s
|-
!2.1
|2007
|-
!3
!3.0
|2009
|2.4 Mbit/s
|-
! rowspan="3" |4
!4.0
|2009
| rowspan="3" |3 Mbit/s
| rowspan="3" |1 Mbit/s
| rowspan="3" |60 m
|-
!4.1
|2013
|-
!4.2
|2014
|-
! rowspan="5" |5
!5.0
|2016
|rowspan="5" |50 Mbit/s
|rowspan="5" | 2 Mbit/s
|rowspan="5" |240 m
|-
!5.1
|2019
|-
!5.2
|2020
|-
!5.3
|2021
|-
!5.4
|2023
|-
! rowspan="2" | 6
!6.0
|2024
|{{dunno}}
|3 Mbit/s
|300 m
|-
!6.1
|2025
|{{dunno}}
|{{dunno}}
|{{dunno}}
|}
The specifications were formalized by the [[Bluetooth Special Interest Group]] (SIG) and formally announced on 20 May 1998.<ref>{{cite web|url=https://www.bluetooth.com/about-us/our-history|title=Our History|publisher=Bluetooth.com|access-date=24 August 2018|archive-url=https://web.archive.org/web/20180525083558/https://www.bluetooth.com/about-us/our-history|archive-date=25 May 2018|url-status=dead}}</ref> In 2014 it had a membership of over 30,000 companies worldwide.<ref>{{cite web |url=https://www.bluetooth.org/en-us/members/introduction-to-membership |title=English Introduction to Membership |website=Bluetooth.org |access-date=13 May 2014 |archive-url=https://web.archive.org/web/20140626122249/https://www.bluetooth.org/en-us/members/introduction-to-membership |archive-date=26 June 2014 |url-status=dead }}</ref> It was established by [[Ericsson]], [[IBM]], [[Intel]], [[Nokia]] and [[Toshiba]], and later joined by many other companies.

All versions of the Bluetooth standards are [[Backward compatibility|backward-compatible]] with all earlier versions.<ref>{{cite web |url=https://www.kohls.com/media/digital/ecom/pdfs/pdf/Bluetooth_Compatibility_Guide_May_2015.pdf |title=Compatibility guide |date=2016 |access-date=18 December 2019 |archive-date=28 December 2019 |archive-url=https://web.archive.org/web/20191228212138/https://www.kohls.com/media/digital/ecom/pdfs/pdf/Bluetooth_Compatibility_Guide_May_2015.pdf |url-status=live }}</ref>

The Bluetooth Core Specification Working Group (CSWG) produces mainly four kinds of specifications:
* The Bluetooth Core Specification{{dash}}typically released every few years
* Core Specification Addendum (CSA)
* Core Specification Supplements (CSS){{dash}}can be released more frequently than Addenda
* Errata{{dash}}published privately to Bluetooth SIG members

=== Bluetooth 1.0 and 1.0B ===

* Products were not interoperable.
* Anonymity was not possible, preventing certain services from using Bluetooth environments.<ref>{{cite web|date=2007|title=BlueTooth|url=http://blue-tooth.50webs.com/bluetooth1_and_1.0b.html|access-date=25 October 2021|website=BlueTooth|archive-date=14 February 2020|archive-url=https://web.archive.org/web/20200214234923/http://blue-tooth.50webs.com/bluetooth1_and_1.0b.html|url-status=live}}</ref>

=== Bluetooth 1.1 ===
* Ratified as [[IEEE 802.15#IEEE 802.15.1: WPAN / Bluetooth|IEEE Standard 802.15.1–2002]]<ref>{{Cite book|doi=10.1109/IEEESTD.2002.93621 |isbn=978-0-7381-3335-5 |year=2002 |title=IEEE Standard for Telecommunications and Information Exchange Between Systems – LAN/MAN – Specific Requirements – Part 15: Wireless Medium Access Control (MAC) and Physical Layer (PHY) Specifications for Wireless Personal Area Networks (WPANs) }}</ref>
* Many errors found in the v1.0B specifications were fixed.
* Added possibility of non-encrypted channels.
* [[Received signal strength indicator]] (RSSI)

=== Bluetooth 1.2 ===
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&nbsp;kbit/s<ref name="Guy Kewney">{{cite web
|url=http://www.newswireless.net/index.cfm/article/629
|title= High speed Bluetooth comes a step closer: enhanced data rate approved
|author=Guy Kewney
|date=16 November 2004
|publisher=Newswireless.net
|access-date=4 February 2008
|archive-url=https://web.archive.org/web/20180115173504/http://www.newswireless.net/index.cfm/article/629
|archive-date=15 January 2018
}}</ref>
* 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
* [[Bluetooth protocols#Host/controller interface (HCI)|Host Controller Interface]] (HCI) operation with three-wire [[Universal asynchronous receiver-transmitter|UART]]
* Ratified as [[IEEE 802.15#IEEE 802.15.1: WPAN / Bluetooth|IEEE Standard 802.15.1–2005]]<ref>{{Cite book |doi=10.1109/IEEESTD.2005.96290 |isbn=978-0-7381-4708-6 |title=IEEE Standard for Information technology-- Local and metropolitan area networks-- Specific requirements-- Part 15.1a: Wireless Medium Access Control (MAC) and Physical Layer (PHY) specifications for Wireless Personal Area Networks (WPAN)}}</ref>
* Introduced flow control and retransmission modes for {{abbr|L2CAP|Logical link control and adaptation protocol}}

=== Bluetooth 2.0 + EDR ===
This version of the Bluetooth Core Specification was released before 2005. The main difference is the introduction of an Enhanced Data Rate (EDR) for faster [[Bit rate|data transfer]]. The data rate of EDR is 3{{nbsp}}Mbit/s, although the maximum data transfer rate (allowing for inter-packet time and acknowledgements) is 2.1{{nbsp}}Mbit/s.<ref name="Guy Kewney" /> EDR uses a combination of [[Gaussian frequency-shift keying|GFSK]] and [[phase-shift keying]] modulation (PSK) with two variants, π/4-[[DQPSK]] and 8-[[Differential phase-shift keying|DPSK]].<ref name="bluetooth_specs">{{cite web
|url=http://www.bluetooth.org/docman/handlers/DownloadDoc.ashx?doc_id=40560&ei=25GiT8L3CuTa0QGnmqDVDA&usg=AFQjCNGXY5pm4Tkju1KGs4dYRJLtd03FEg
|title=Specification Documents
|publisher=Bluetooth SIG
|access-date=3 May 2012
|archive-date=23 December 2018
|archive-url=https://web.archive.org/web/20181223163507/https://www.bluetooth.org/docman/handlers/DownloadDoc.ashx?doc_id=40560&ei=25GiT8L3CuTa0QGnmqDVDA&usg=AFQjCNGXY5pm4Tkju1KGs4dYRJLtd03FEg
|url-status=live
}}</ref> 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.<ref>{{cite web
|url=http://www.europe.htc.com/z/pdf/products/1766_TyTN_LFLT_OUT.PDF
|archive-url=https://web.archive.org/web/20061012113727/http://www.europe.htc.com/z/pdf/products/1766_TyTN_LFLT_OUT.PDF
|url-status=dead
|archive-date=12 October 2006
|title=HTC TyTN Specification
|publisher=HTC
|access-date=4 February 2008
}}</ref>

=== Bluetooth 2.1 + EDR ===
Bluetooth Core Specification version 2.1 + EDR was adopted by the Bluetooth SIG on 26 July 2007.<ref name="bluetooth_specs" />

The headline feature of v2.1 is [[#Pairing|secure simple pairing]] (SSP): this improves the pairing experience for Bluetooth devices, while increasing the use and strength of security.<ref>{{cite web
|date=3 August 2006
|title=Simple Pairing Whitepaper
|version=Version V10r00
|publisher=Bluetooth SIG |url=http://bluetooth.com/NR/rdonlyres/0A0B3F36-D15F-4470-85A6-F2CCFA26F70F/0/SimplePairing_WP_V10r00.pdf
|access-date=1 February 2007
|archive-url = https://web.archive.org/web/20061018032605/http://www.bluetooth.com/NR/rdonlyres/0A0B3F36-D15F-4470-85A6-F2CCFA26F70F/0/SimplePairing_WP_V10r00.pdf
|archive-date = 18 October 2006
}}</ref>

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<ref name="bluetooth_specs" /> was adopted by the Bluetooth SIG on 21 April 2009. Bluetooth v3.0 + HS provides theoretical data transfer speeds of up to 24&nbsp;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 [[IEEE 802.11|802.11]] link.

The main new feature is {{abbr|AMP|Alternative MAC/PHY}} (Alternative MAC/PHY), the addition of [[IEEE 802.11|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<ref>{{cite web|url=https://www.bluetooth.org/docman/handlers/DownloadDoc.ashx?doc_id=40560|title=Bluetooth Core Version 3.0 + HS specification|access-date=8 May 2011|archive-date=23 December 2018|archive-url=https://web.archive.org/web/20181223163602/https://www.bluetooth.org/docman/handlers/DownloadDoc.ashx?doc_id=40560|url-status=live}}</ref> or earlier Core Specification Addendum 1.<ref>{{cite web|url= https://www.bluetooth.org/DocMan/handlers/DownloadDoc.ashx?doc_id=174214|title= Bluetooth Core Specification Addendum (CSA) 1|access-date= 11 April 2018|archive-date= 23 December 2018|archive-url= https://web.archive.org/web/20181223163555/https://www.bluetooth.org/DocMan/handlers/DownloadDoc.ashx?doc_id=174214|url-status= live}}</ref>

; [[#Logical Link Control and Adaptation Protocol|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 [[Medium access control|MAC]] and [[PHY]]s 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 behavior 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.

==== Ultra-wideband ====
The high-speed (AMP) feature of Bluetooth v3.0 was originally intended for [[Ultra-wideband|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.<ref>{{cite web
|url=http://news.zdnet.co.uk/communications/0,1000000085,39643174,00.htm
|title=Bluetooth 3.0 released without ultrawideband
|author=David Meyer
|date=22 April 2009
|publisher=zdnet.co.uk
|access-date=22 April 2009
|archive-date=19 September 2011
|archive-url=https://web.archive.org/web/20110919213421/http://www.zdnet.co.uk/news/networking/2009/04/22/bluetooth-30-released-without-ultrawideband-39643174/
|url-status=dead
}}</ref>

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.<ref>{{cite web |url=http://www.wimedia.org/ |title=Wimedia.org |publisher=Wimedia.org |date=4 January 2010 |access-date=4 September 2010 |url-status=dead |archive-url=https://web.archive.org/web/20020426095418/http://www.wimedia.org/ |archive-date=26 April 2002 }}</ref><ref>{{cite web |url=http://www.wimedia.org/imwp/download.asp?ContentID=15506 |title=Wimedia.org |access-date=4 September 2010 |url-status=dead |archive-url=https://web.archive.org/web/20090323120814/http://www.wimedia.org/imwp/download.asp?ContentID=15506 |archive-date=23 March 2009 }}</ref><ref>{{cite web |url=http://www.bluetooth.com/Pages/Press-Releases-Detail.aspx?ItemID=4 |title=bluetooth.com |access-date=29 January 2015 |archive-date=8 February 2015 |archive-url=https://web.archive.org/web/20150208013350/http://www.bluetooth.com/Pages/Press-Releases-Detail.aspx?ItemID=4 |url-status=live }}</ref><ref>{{cite web |url=http://www.usb.org/press/WiMedia_Tech_Transfer/ |title=USB.org |publisher=USB.org |date=16 March 2009 |access-date=4 September 2010 |archive-url=https://web.archive.org/web/20110610211240/http://www.usb.org/press/WiMedia_Tech_Transfer/ |archive-date=10 June 2011 |url-status=dead }}</ref><ref>{{cite web |url=http://www.incisor.tv/2009/03/what-to-make-of-bluetooth-sig-wimedia.html |title=Incisor.tv |publisher=Incisor.tv |date=16 March 2009 |access-date=4 September 2010 |archive-url=https://web.archive.org/web/20180916054407/http://www.incisor.tv/2009/03/what-to-make-of-bluetooth-sig-wimedia.html |archive-date=16 September 2018 |url-status=dead }}</ref>

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 Alliance|WiMedia]] members had not and would not sign up to the necessary agreements for the [[intellectual property|IP]] transfer. As of 2009, the Bluetooth SIG was in the process of evaluating other options for its longer-term roadmap.<ref>{{cite web|url=https://www.eetimes.com/bluetooth-group-drops-ultrawideband-eyes-60-ghz/|title=Bluetooth group drops ultrawideband, eyes 60 GHz|website=EETimes|date=29 October 2009|access-date=17 June 2021|archive-date=12 June 2021|archive-url=https://web.archive.org/web/20210612021636/https://www.eetimes.com/bluetooth-group-drops-ultrawideband-eyes-60-ghz/|url-status=live}}</ref><ref>{{cite web |url=https://www.eetimes.com/report-ultrawideband-dies-by-2013/ |title=Report: Ultrawideband dies by 2013 |website=EETimes |date=4 May 2009 |access-date=17 June 2021 |archive-date=12 June 2021 |archive-url=https://web.archive.org/web/20210612021648/https://www.eetimes.com/report-ultrawideband-dies-by-2013/ |url-status=live }}</ref><ref>{{cite web|url=http://www.incisor.tv/download.php?file=140november2009.pdf|title=Simon Stenhouse – Leech Attempt|website=incisor.tv |date=November 2009 |access-date=4 June 2015|archive-url=https://web.archive.org/web/20150924034305/http://www.incisor.tv/download.php?file=140november2009.pdf|archive-date=24 September 2015|url-status=dead}}</ref>

=== {{Anchor|v4.0}}Bluetooth 4.0 ===
{{main|Bluetooth Low Energy}}

The Bluetooth SIG completed the Bluetooth Core Specification version 4.0 (called Bluetooth Smart) and has been adopted {{as of|2010|June|30|lc=y}}. 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,<ref>{{cite press release |url=http://www.wibree.com/press/Wibree_pressrelease_final_1206.pdf |title=Wibree forum merges with Bluetooth SIG |date=12 June 2007 |publisher=Nokia |access-date=4 February 2008 |archive-url=https://web.archive.org/web/20141229073516/http://www.wibree.com/press/Wibree_pressrelease_final_1206.pdf |archive-date=29 December 2014 |url-status=dead }}</ref> 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 [[Button cell|coin cell]]. Chip designs allow for two types of implementation, dual-mode, single-mode and enhanced past versions.<ref>{{cite web |url=http://www.bluetooth.com/Bluetooth/Press/SIG/SIG_INTRODUCES_BLUETOOTH_LOW_ENERGY_WIRELESS_TECHNOLOGY_THE_NEXT_GENERATION_OF_BLUETOOTH_WIRELESS_TE.htm |title=Bluetooth.com |publisher=Bluetooth.com |access-date=4 September 2010 |archive-url=https://web.archive.org/web/20091221175650/http://www.bluetooth.com/Bluetooth/Press/SIG/SIG_INTRODUCES_BLUETOOTH_LOW_ENERGY_WIRELESS_TECHNOLOGY_THE_NEXT_GENERATION_OF_BLUETOOTH_WIRELESS_TE.htm |archive-date=21 December 2009 |url-status=dead }}</ref> 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.<ref>{{cite web |url=https://www.engadget.com/2011/10/25/bluetooth-sig-unveils-smart-marks-explains-v4-0-compatibility-w/ |title=Bluetooth SIG unveils Smart Marks, explains v4.0 compatibility with unnecessary complexity |date=25 October 2011 |publisher=Engadget |access-date=24 August 2017 |archive-date=30 December 2018 |archive-url=https://web.archive.org/web/20181230095852/https://www.engadget.com/2011/10/25/bluetooth-sig-unveils-smart-marks-explains-v4-0-compatibility-w/ |url-status=live }}</ref>

Compared to ''Classic Bluetooth'', Bluetooth Low Energy is intended to provide considerably reduced power consumption and cost while maintaining a [[#Radio interface|similar communication range]]. In terms of lengthening the battery life of Bluetooth devices, {{abbr|BLE|Bluetooth Low Energy}} represents a significant progression.

* In a single-mode implementation, only the low energy protocol stack is implemented. [[Dialog Semiconductor]],<ref>{{cite web|url=https://www.dialog-semiconductor.com/bluetooth-low-energy|title=Dialog Semiconductor|access-date=1 February 2018|archive-date=23 December 2018|archive-url=https://web.archive.org/web/20181223163430/https://www.dialog-semiconductor.com/bluetooth-low-energy|url-status=live}}</ref> [[STMicroelectronics]],<ref>{{cite web|url=https://www.st.com/en/wireless-connectivity/bluenrg-1.html|title=BlueNRG-1 – Programmable Bluetooth LE 5.2 Wireless SoC |publisher=[[STMicroelectronics]] |access-date=24 March 2022 }}</ref> AMICCOM,<ref>{{cite web|url=http://www.amiccom.com.tw/ |title=笙科電子-Amiccom |url-status=dead |archive-url=https://web.archive.org/web/20130825161057/http://www.amiccom.com.tw/ |archive-date=25 August 2013 }}</ref> [[CSR plc|CSR]],<ref>{{cite web |url=http://www.csr.com/products/45/csr-energy |archive-url=https://archive.today/20120628214525/http://www.csr.com/products/45/csr-energy |url-status=dead |archive-date=28 June 2012 |title=CSR.com |publisher=CSR |access-date=7 April 2011 }}</ref> [[Nordic Semiconductor]]<ref>{{cite web |url=http://www.nordicsemi.com/eng/Products/Bluetooth-R-low-energy/nRF8001 |title=Nordicsemi.com |publisher=Nordic Semiconductor |access-date=7 April 2011 |archive-url=https://web.archive.org/web/20110402173736/http://www.nordicsemi.com/eng/Products/Bluetooth-R-low-energy/nRF8001 |archive-date=2 April 2011 |url-status=dead }}</ref> and [[Texas Instruments]]<ref>{{cite web |url=http://focus.ti.com/docs/prod/folders/print/cc2540.html |title=TI.com |publisher=Texas Instruments |access-date=7 April 2011 |archive-date=21 July 2011 |archive-url=https://web.archive.org/web/20110721114918/http://focus.ti.com/docs/prod/folders/print/cc2540.html |url-status=live }}</ref> 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|2011|03}}, the following semiconductor companies have announced the availability of chips meeting the standard: [[Qualcomm Atheros]], [[CSR plc|CSR]], [[Broadcom]]<ref>{{cite web |url=http://www.ifixit.com/Teardown/MacBook-Air-13-Inch-Mid-2011-Teardown/6130/1 |title=iFixit MacBook Air 13" Mid 2011 Teardown |date=21 July 2011 |publisher=iFixit.com |access-date=27 July 2011 |archive-date=24 July 2011 |archive-url=https://web.archive.org/web/20110724072433/http://www.ifixit.com/Teardown/MacBook-Air-13-Inch-Mid-2011-Teardown/6130/1 |url-status=live }}</ref><ref>{{cite web |url=http://www.broadcom.com/products/Bluetooth/Bluetooth-RF-Silicon-and-Software-Solutions/BCM20702 |title=Broadcom.com&nbsp;– BCM20702&nbsp;– Single-Chip Bluetooth 4.0 HCI Solution with Bluetooth Low Energy (BLE) Support |publisher=Broadcom |access-date=27 July 2011 |archive-url=https://web.archive.org/web/20110811125845/http://www.broadcom.com/products/Bluetooth/Bluetooth-RF-Silicon-and-Software-Solutions/BCM20702 |archive-date=11 August 2011 |url-status=dead }}</ref> 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 [[Advanced Encryption Standard|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.

=== {{Anchor|v4.1}}Bluetooth 4.1 ===
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.<ref>{{cite web |url=http://www.bluetooth.com/Pages/Press-Releases-Detail.aspx?ItemID=197 |title=Press Releases Detail {{pipe}} Bluetooth Technology Website |publisher=Bluetooth.com |date=4 December 2013 |access-date=13 May 2014 |archive-date=23 June 2014 |archive-url=https://web.archive.org/web/20140623092659/http://www.bluetooth.com/pages/press-releases-detail.aspx?itemid=197 |url-status=dead }}</ref>

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<ref>{{cite web |url=https://www.bluetooth.org/en-us/specification/adopted-specifications |title=Adopted Specification; Bluetooth Technology Website |publisher=Bluetooth.com |date=4 December 2013 |access-date=14 May 2014 |archive-date=3 October 2015 |archive-url=https://web.archive.org/web/20151003173654/https://www.bluetooth.org/en-us/specification/adopted-specifications |url-status=dead }}</ref>
Some features were already available in a Core Specification Addendum (CSA) before the release of v4.1.

=== {{Anchor|v4.2}}Bluetooth 4.2 ===
Released on 2 December 2014,<ref>{{Cite web |date=2 December 2014 |title=Specification of the Bluetooth System |url=https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=441541 |access-date=23 February 2023 |publisher=[[Bluetooth Special Interest Group]] |format=PDF}}</ref> it introduces features for the [[Internet of things]].

The major areas of improvement are:
* Bluetooth Low Energy Secure Connection with Data Packet Length Extension to improve the [[cryptographic protocol]]
* Link Layer Privacy with Extended Scanner Filter Policies to improve [[data security]]
* Internet Protocol Support Profile (IPSP) [[IPv6|version 6]] ready for Bluetooth [[smart devices]] to support the Internet of things and [[home automation]]
Older Bluetooth hardware may receive 4.2 features such as Data Packet Length Extension and improved privacy via firmware updates.<ref name=":0">{{cite web|url=http://www.redmondpie.com/bluetooth-4.2-announced-heres-what-is-new/ |title=Bluetooth 4.2 Announced: Here's What Is New |publisher=Redmond Pie |last=Rehman |first=Zayed |date=4 December 2014 |access-date=13 December 2024 |archive-date=13 December 2014 |archive-url=https://web.archive.org/web/20141213015652/http://www.redmondpie.com/bluetooth-4.2-announced-heres-what-is-new/ |url-status=live}}</ref><ref name=":1">{{cite web |url=http://www.dailytech.com/Bluetooth+42+Promises+Faster+Connections+Better+Security+to+Stop+Snooping/article36960.htm |title=Bluetooth 4.2 Promises Faster Connections, Better Security to Stop Snooping |publisher=[[DailyTech]] |last=Hatamoto |first=Michael |date=4 December 2014 |archive-url=https://web.archive.org/web/20141207093853/http://www.dailytech.com/Bluetooth+42+Promises+Faster+Connections+Better+Security+to+Stop+Snooping/article36960.htm |archive-date=7 December 2014 |url-status=dead}}</ref>

=== {{Anchor|v5}}Bluetooth 5 ===
The Bluetooth SIG released Bluetooth 5 on 6 December 2016.<ref>{{Cite web |last=Woolley |first=Martin |date=26 October 2017 |title=Bluetooth Core Specification Version 5.0 Feature Enhancements |url=https://www.bluetooth.com/wp-content/uploads/2019/03/Bluetooth_5-FINAL.pdf |access-date=23 February 2023 |website=bluetooth.com |edition=1.1.0}}</ref> Its new features are mainly focused on new [[Internet of Things]] technology. Sony was the first to announce Bluetooth 5.0 support with its [[Xperia XZ Premium]] in Feb 2017 during the Mobile World Congress 2017.<ref>{{cite web|url=https://www.ibtimes.co.in/mwc-2017-sony-launches-new-5g-ready-xperia-xz-series-top-notch-camera-717581|title=MWC 2017: Sony launches new 5G-ready Xperia XZ series with top-notch camera|website=IBT|date=27 February 2017|access-date=3 October 2019|archive-date=3 October 2019|archive-url=https://web.archive.org/web/20191003065556/https://www.ibtimes.co.in/mwc-2017-sony-launches-new-5g-ready-xperia-xz-series-top-notch-camera-717581|url-status=live}}</ref> 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 Inc.|Apple]] also integrated Bluetooth 5 in its new [[HomePod]] offering released on 9 February 2018.<ref>{{cite web|url=https://www.apple.com/homepod/specs/|title=HomePod – Technical Specifications|website=Apple|access-date=29 January 2018|archive-date=13 May 2019|archive-url=https://web.archive.org/web/20190513062322/https://www.apple.com/homepod/specs/|url-status=live}}</ref> Marketing drops the point number; so that it is just "Bluetooth 5" (unlike Bluetooth 4.0);<ref>{{cite web|url=https://www.cnx-software.com/2016/06/10/bluetooth-5-promises-four-times-the-speed-twice-the-range-of-bluetooth-4-0-le-transmissions/|title=Bluetooth 5 Promises Four times the Range, Twice the Speed of Bluetooth 4.0 LE Transmissions|last=cnxsoft|date=10 June 2016|access-date=12 December 2018|archive-date=12 May 2019|archive-url=https://web.archive.org/web/20190512044135/https://www.cnx-software.com/2016/06/10/bluetooth-5-promises-four-times-the-speed-twice-the-range-of-bluetooth-4-0-le-transmissions/|url-status=live}}</ref> 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 [[Bluetooth Low Energy|BLE]], options that can double the data rate (2{{nbsp}}Mbit/s burst) at the expense of range, or provide up to four times the range at the expense of data rate. The increase in transmissions could be important for Internet of Things devices, where many nodes connect throughout a whole house. Bluetooth 5 increases capacity of connectionless services such as location-relevant navigation<ref>{{cite web|url=http://www.computerweekly.com/news/450298598/Bluetooth-5-standard-brings-range-speed-and-capacity-boost-for-IoT|title=Bluetooth 5 standard brings range, speed and capacity boost for IoT|access-date=18 June 2016|archive-date=18 June 2016|archive-url=https://web.archive.org/web/20160618143744/http://www.computerweekly.com/news/450298598/Bluetooth-5-standard-brings-range-speed-and-capacity-boost-for-IoT|url-status=live}}</ref> of low-energy Bluetooth connections.<ref>{{cite web|url=https://www.bluetooth.com/news/pressreleases/2016/06/16/-bluetooth-5-quadruples-rangedoubles-speedincreases-data-broadcasting-capacity-by-800|title=Bluetooth 5 Quadruples Range, Doubles Speed, Increases Data Broadcasting Capacity by 800% – Bluetooth Technology Website|website=bluetooth.com|access-date=12 December 2018|archive-url=https://web.archive.org/web/20181209055417/https://www.bluetooth.com/news/pressreleases/2016/06/16/-bluetooth-5-quadruples-rangedoubles-speedincreases-data-broadcasting-capacity-by-800|archive-date=9 December 2018|url-status=dead}}</ref><ref>{{cite web|url=https://arstechnica.com/gadgets/2016/06/bluetooth-5-spec-coming-next-week-with-2x-more-range-and-4x-better-speed/|title="Bluetooth 5" spec coming next week with 4x more range and 2x better speed [Updated]|date=10 June 2016|access-date=14 June 2017|archive-date=10 June 2019|archive-url=https://web.archive.org/web/20190610041359/https://arstechnica.com/gadgets/2016/06/bluetooth-5-spec-coming-next-week-with-2x-more-range-and-4x-better-speed/|url-status=live}}</ref><ref>{{cite web|url=http://www.techradar.com/news/networking/bluetooth-5-everything-you-need-to-know-1323060|title=Bluetooth 5: everything you need to know|date=10 June 2016|access-date=11 June 2016|archive-date=5 May 2021|archive-url=https://web.archive.org/web/20210505011821/https://www.techradar.com/news/networking/bluetooth-5-everything-you-need-to-know-1323060|url-status=live}}</ref>

The major areas of improvement are:
* Slot Availability Mask (SAM)
* 2&nbsp;Mbit/s PHY for {{abbr|LE|Low Energy}}
* 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<ref>{{cite web|url=https://www.bluetooth.org/DocMan/handlers/DownloadDoc.ashx?doc_id=421043|title=Bluetooth Core Specification v5.0|website=bluetooth.org|format=PDF download|access-date=8 December 2016|archive-date=23 December 2018|archive-url=https://web.archive.org/web/20181223163509/https://www.bluetooth.org/DocMan/handlers/DownloadDoc.ashx?doc_id=421043|url-status=live}}</ref>

=== {{Anchor|v5}}Bluetooth 5.1 ===
The Bluetooth SIG presented Bluetooth 5.1 on 21 January 2019.<ref>{{Cite web |last=Woolley |first=Martin |date=28 January 2019 |title=Bluetooth Core Specification v5.1 |url=https://www.bluetooth.com/wp-content/uploads/Files/Specification/1901_Feature_Overview_Brief_FINAL.pdf |access-date=23 February 2023 |website=bluetooth.com |edition=1.0.1 |archive-date=23 February 2023 |archive-url=https://web.archive.org/web/20230223194148/https://www.bluetooth.com/wp-content/uploads/Files/Specification/1901_Feature_Overview_Brief_FINAL.pdf |url-status=dead }}</ref>

The major areas of improvement are:
* [[Angle of arrival]] (AoA) and Angle of Departure (AoD) which are used for locating 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 {{abbr|QoS|Quality of service}} and Flow Specification
** Block 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:
* Models
* [[Bluetooth mesh#Mesh models|Mesh-based model]] hierarchy

The following features were removed in this version of the specification:
* Unit keys

=== Bluetooth 5.2 ===
On 31 December 2019, the Bluetooth SIG published the Bluetooth Core Specification version 5.2. The new specification adds new features:<ref>{{cite web |last=Woolley |first=Martin |date=9 December 2020 |title=Bluetooth Core Specification Version 5.2 Feature Overview |url=https://www.bluetooth.com/wp-content/uploads/2020/01/Bluetooth_5.2_Feature_Overview.pdf |url-status=live |archive-url=https://web.archive.org/web/20200108105207/https://www.bluetooth.com/wp-content/uploads/2020/01/Bluetooth_5.2_Feature_Overview.pdf |archive-date=8 January 2020 |access-date=8 January 2020 |website=bluetooth.com}}</ref>

* Enhanced Attribute Protocol (EATT), an improved version of the Attribute Protocol (ATT)
* LE Power Control
* LE Isochronous Channels
* [[Bluetooth Low Energy#Audio|LE Audio]] that is built on top of the new 5.2 features. BT LE Audio was announced in January 2020 at [[Consumer Electronics Show|CES]] by the [[Bluetooth Special Interest Group|Bluetooth SIG]]. Compared to regular Bluetooth Audio, Bluetooth Low Energy Audio makes lower battery consumption possible and creates a standardized way of transmitting audio over BT LE. Bluetooth LE Audio also allows one-to-many and many-to-one transmission, allowing multiple receivers from one source or one receiver for multiple sources, known as Auracast.<ref>{{Cite news|url=https://www.wired.com/story/bluetooth-le-audio/|title=The New Version of Bluetooth Is Here to Fix Your Headphones|magazine=Wired|access-date=3 February 2020|issn=1059-1028|archive-date=26 April 2020|archive-url=https://web.archive.org/web/20200426154948/https://www.wired.com/story/bluetooth-le-audio/|url-status=live}}</ref><ref>{{cite web|url=https://www.macrumors.com/2020/01/06/bluetooth-sig-debuts-le-audio/|title=Bluetooth SIG Announces 'LE Audio' With Audio Sharing, Lower Data Consumption, Hearing Aid Support and More|last=Clover|first=Juli|website=macrumors.com|date=6 January 2020|access-date=3 February 2020|archive-date=20 February 2020|archive-url=https://web.archive.org/web/20200220134827/https://www.macrumors.com/2020/01/06/bluetooth-sig-debuts-le-audio/|url-status=live}}</ref> It uses a new [[LC3 (codec)|LC3 codec]]. BLE Audio will also add support for hearing aids.<ref>{{cite web|url=https://source.android.com/devices/bluetooth/asha|title=Hearing Aid Audio Support Using Bluetooth LE|website=Android Open Source Project|access-date=3 February 2020|archive-date=20 February 2020|archive-url=https://web.archive.org/web/20200220152923/https://source.android.com/devices/bluetooth/asha|url-status=live}}</ref> On 12 July 2022, the Bluetooth SIG announced the completion of Bluetooth LE Audio. The standard has a lower minimum latency claim of 20–30 ms vs Bluetooth Classic audio of 100–200 ms.<ref>{{cite web |author=Scharon Harding |url=https://arstechnica.com/gadgets/2022/07/whats-bluetooth-le-audio-explaining-the-latest-wireless-tech-standard/ |title=What's Bluetooth LE Audio? Explaining the spec and what it means for wireless sound |publisher=Ars Technica |date=12 July 2022 |access-date=21 July 2022}}</ref> At [[IFA Berlin|IFA]] in August 2023 Samsung announced support for Auracast through a software update for their [[Samsung Galaxy Buds series|Galaxy Buds2 Pro]] and two of their TVs.<ref>{{Cite web |author1=Carrie Marshall |date=2023-08-30 |title=Samsung leaps ahead of Apple and adds game-changing Auracast Bluetooth to its 4K TVs and earbuds |url=https://www.techradar.com/televisions/your-samsung-earbuds-and-4k-tv-are-getting-a-huge-bluetooth-upgrade |access-date=2023-10-09 |website=TechRadar}}</ref> In October users started getting updates for the earbuds.<ref>{{Cite web |last1=SamMobile |last2=Shaik |first2=Asif Iqbal |date=2023-10-06 |title=Galaxy Buds 2 Pro get Bluetooth Auracast support with new update |url=https://www.sammobile.com/news/galaxy-buds-2-pro-bluetooth-auracast-new-update/ |access-date=2023-10-09 |website=SamMobile}}</ref>

=== Bluetooth 5.3 ===
The Bluetooth SIG published the Bluetooth Core Specification version 5.3 on 13 July 2021. The feature enhancements of Bluetooth 5.3 are:<ref>{{cite web |last=Woolley |first=Martin |date=24 June 2021 |title=Bluetooth Core Specification Version 5.3 Feature Enhancements |url=https://www.bluetooth.com/wp-content/uploads/2021/01/Bluetooth_5.3_Feature_Enhancements_Update.pdf |url-status=live |archive-url=https://web.archive.org/web/20210730064958/https://www.bluetooth.com/wp-content/uploads/2021/01/Bluetooth_5.3_Feature_Enhancements_Update.pdf |archive-date=30 July 2021 |access-date=17 September 2021 |website=bluetooth.com}}</ref>

* Connection Subrating
* Periodic Advertisement Interval
* Channel Classification Enhancement
* Encryption key size control enhancements

The following features were removed in this version of the specification:
* Alternate MAC and PHY (AMP) Extension

=== Bluetooth 5.4 ===
The Bluetooth SIG released the Bluetooth Core Specification version 5.4 on 7 February 2023. This new version adds the following features:<ref>{{Cite web |last=Woolley |first=Martin |date=7 February 2023 |title=Bluetooth Core Specification Version 5.4 |url=https://www.bluetooth.com/wp-content/uploads/2023/02/2301_5.4_Tech_Overview_FINAL.pdf |url-status=live |archive-url=https://web.archive.org/web/20230209191214/https://www.bluetooth.com/wp-content/uploads/2023/02/2301_5.4_Tech_Overview_FINAL.pdf |archive-date=9 February 2023 |access-date=23 February 2023 |website=bluetooth.com}}</ref>

* Periodic Advertising with Responses (PAwR)
* Encrypted Advertising Data
* LE {{abbr|GATT|Generic Attribute Profile}} Security Levels Characteristic
* Advertising Coding Selection

=== Bluetooth 6.0 ===
The Bluetooth SIG released the Bluetooth Core Specification version 6.0 on 27 August 2024.<ref>{{Cite web |date=2024-08-30 |title=Core Specification |url=https://www.bluetooth.com/specifications/specs/core-specification-6-0/ |access-date=2024-09-05 |website=Bluetooth® Technology Website |language=en-US}}</ref> This version adds the following features:<ref>{{Cite web |date=2024-09-03 |title=Now Available: New Version of the Bluetooth Core Specification |url=https://www.bluetooth.com/blog/now-available-new-version-of-the-bluetooth-core-specification/ |access-date=2024-09-05 |website=Bluetooth® Technology Website |language=en-US}}</ref>

* Bluetooth Channel Sounding
* Decision-based advertising filtering
* Monitoring advertisers
* {{abbr|ISOAL|Isochronous Adaptation Layer}} enhancement
* LL extended feature set
* Frame space update

=== Bluetooth 6.1 ===
The Bluetooth SIG released the Bluetooth Core Specification version 6.1 on 7 May 2025.<ref>{{cite web |title=Delivering on the bi-annual release schedule: Bluetooth® Core 6.1 is here |url=https://www.bluetooth.com/blog/delivering-on-the-bi-annual-release-schedule-bluetooth-core-6-1-is-here/ |website=Bluetooth® Technology Website |publisher=Bluetooth SIG, Inc. |access-date=13 May 2025 |date=7 May 2025}}</ref>

* Increased device privacy
* Improved power efficiency

== Technical information ==

=== Architecture ===

==== Software ====
Seeking to extend the compatibility of Bluetooth devices, the devices that adhere to the standard use an interface called HCI (Host Controller Interface) between the host and the controller.

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 (Logical Link Control and Adaptation Protocol). The L2CAP protocol is responsible for the segmentation and reassembly of the packets.

==== Hardware ====
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 (e.g. [[SBC (codec)]]) 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.

A Bluetooth device is a [[short-range device|short-range]] [[wireless]] device. Bluetooth devices are [[semiconductor device fabrication|fabricated]] on [[RF CMOS]] [[integrated circuit]] ([[RF circuit]]) chips.<ref name="Happich">{{cite news |last1=Happich |first1=Julien |date=24 February 2010 |title=Global shipments of short range wireless ICs to exceed 2 billion units in 2010 |work=[[EE Times]] |url=https://www.eetimes.com/document.asp?doc_id=1254987 |url-status=live |access-date=25 October 2019 |archive-url=https://web.archive.org/web/20220212025004/https://www.eetimes.com/global-shipments-of-short-range-wireless-ics-to-exceed-2-billion-units-in-2010/ |archive-date=12 February 2022}}</ref><ref>{{cite book |last1=Veendrick |first1=Harry J. M. |title=Nanometer CMOS ICs: From Basics to ASICs |date=2017 |publisher=Springer |isbn=9783319475974 |page=243 |url=https://books.google.com/books?id=Lv_EDgAAQBAJ&pg=PA243 |access-date=26 October 2019 |archive-date=5 May 2020 |archive-url=https://web.archive.org/web/20200505161843/https://books.google.com/books?id=Lv_EDgAAQBAJ&pg=PA243 |url-status=live }}</ref>

=== Bluetooth protocol stack ===
{{Main|List of Bluetooth protocols}}
[[File:Bluetooth protokoly.svg|thumb|250px|right|Bluetooth protocol stack]]

Bluetooth is defined as a layer protocol architecture consisting of core protocols, cable replacement protocols, telephony control protocols, and adopted protocols.<ref name="autogenerated2">{{cite book|last=Stallings|first=William|year=2005|title=Wireless communications & networks|location=Upper Saddle River, NJ|publisher=Pearson Prentice Hall|isbn=9788132231561}}</ref> Mandatory protocols for all Bluetooth stacks are LMP, L2CAP and SDP. In addition, devices that communicate with Bluetooth almost universally can use these protocols: [[Bluetooth protocols#Host Controller Interface (HCI)|HCI]] and RFCOMM.{{citation needed|date=November 2023}}

==== Link Manager ====
The Link Manager (LM) is the system that manages establishing 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 via the management protocol of the LMP link. To perform its function as a service provider, the LM uses the services included in the Link Controller (LC).
The Link Manager Protocol basically consists of several 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.
* Authentication.
* Negotiation of link mode and connection establishment.

==== Host Controller Interface ====
The Host Controller Interface provides a command interface between the controller and the host.

==== 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&nbsp;kB, with 672 bytes as the default [[Maximum transmission unit|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 profile]]s the headset can use (Headset Profile, Hands Free Profile (HFP), [[Advanced Audio Distribution 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 [[Subnetwork Access Protocol|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 [[List of Bluetooth protocols#Logical link control and adaptation protocol (L2CAP)|L2CAP]] channel intended for video distribution profile in the Bluetooth transmission.

==== Telephony Control Protocol ====
The ''Telephony Control Protocol{{nbsp}}– 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 ====
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 datagram]]s over a point-to-point link.
;[[TCP/IP]]/UDP: Foundation Protocols for TCP/IP protocol suite
;[[OBject EXchange|Object Exchange Protocol]] (OBEX): Session-layer protocol for the exchange of objects, providing a model for object and operation representation
;[[Wireless Application Protocol|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.<ref name="autogenerated2" />

=== 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 [[MAC address|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 [[Sony Ericsson T610|T610]] (see [[Bluejacking]]).

{{anchor|Pairing}}

=== Pairing and bonding ===

==== Motivation ====
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 completes, a bond forms between the two devices, enabling those two devices to connect in the future without repeating the pairing process to confirm device identities. When desired, the user can remove the bonding relationship.

==== Implementation ====
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 [[cryptography|cryptographically]] [[authentication|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-oriented logical transport|ACL]] link between the devices may be [[encryption|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 ====
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 [[Personal identification number|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 attack|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 minimal 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.

==== Security concerns ====
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 [[Stream cipher attack|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 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.

== Security ==

=== Overview ===
{{see also|Mobile security#Attacks based on communication networks}}

Bluetooth implements [[confidentiality]], [[authentication]] and [[key (cryptography)|key]] derivation with custom algorithms based on the [[Secure and Fast Encryption Routine|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.<ref>{{cite web
|author=Juha T. Vainio
|date=25 May 2000
|title=Bluetooth Security
|publisher=Helsinki University of Technology
|url=http://www.iki.fi/jiitv/bluesec.pdf
|access-date=1 January 2009
|archive-date=25 September 2020
|archive-url=https://web.archive.org/web/20200925110917/http://www.yuuhaw.com/bluesec.pdf
|url-status=live
}}</ref>
The [[E0 (cipher)|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.<ref>{{cite web
|author=Andreas Becker
|date=16 August 2007
|title=Bluetooth Security & Hacks
|publisher=Ruhr-Universität Bochum
|url=http://gsyc.es/~anto/ubicuos2/bluetooth_security_and_hacks.pdf
|access-date=10 October 2007
|archive-date=21 March 2016
|archive-url=https://web.archive.org/web/20160321205619/http://gsyc.es/~anto/ubicuos2/bluetooth_security_and_hacks.pdf
|url-status=dead
}}</ref>

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.<ref>{{cite web
|author1=Scarfone, K.
|author2=Padgette, J.
|name-list-style=amp
|date=September 2008
|title=Guide to Bluetooth Security
|publisher=National Institute of Standards and Technology
|url=http://csrc.nist.gov/publications/nistpubs/800-121-rev1/sp800-121_rev1.pdf
|access-date=3 July 2013
|archive-date=11 June 2017
|archive-url=https://web.archive.org/web/20170611040534/http://csrc.nist.gov/publications/nistpubs/800-121-rev1/sp800-121_rev1.pdf
|url-status=live
}}</ref>

Bluetooth v2.1&nbsp;– finalized in 2007 with consumer devices first appearing in 2009&nbsp;– makes significant changes to Bluetooth's security, including pairing. See the [[#Pairing mechanisms|pairing mechanisms]] section for more about these changes.

=== Bluejacking ===
{{main|Bluejacking}}
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!"<ref>{{cite web|url=http://electronics.howstuffworks.com/bluejacking.htm|title=What is bluejacking?|author=John Fuller|date=28 July 2008 |publisher=howstuffworks|access-date=26 May 2015|archive-date=20 May 2015|archive-url=https://web.archive.org/web/20150520035211/http://electronics.howstuffworks.com/bluejacking.htm|url-status=live}}</ref> Bluejacking does not involve the removal or alteration of any data from the device.<ref>{{Cite web |title=Bluesnarfing vs. Bluejacking: Top 4 Differences |url=https://www.spiceworks.com/it-security/endpoint-security/articles/bluesnarfing-vs-bluejacking/ |access-date=2024-03-06 |website=Spiceworks}}</ref>

Some form of [[Denial-of-service attack|DoS]] is also possible, even in modern devices, by sending unsolicited pairing requests in rapid succession; this becomes disruptive because most systems display a full screen notification for every connection request, interrupting every other activity, especially on less powerful devices.

=== History of security concerns ===

==== 2001–2004 ====
In 2001, Jakobsson and Wetzel from [[Bell Laboratories]] discovered flaws in the Bluetooth pairing protocol and also pointed to vulnerabilities in the encryption scheme.<ref>{{cite news
|title=Security Weaknesses in Bluetooth
|publisher= RSA Security Conf.&nbsp;– Cryptographer's Track
|citeseerx=10.1.1.23.7357
}}</ref> 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.<ref>{{cite web
|title=Bluetooth
|publisher=The Bunker
|url=http://www.thebunker.net/resources/bluetooth
|access-date=1 February 2007
|archive-url = https://web.archive.org/web/20070126012417/http://www.thebunker.net/resources/bluetooth |archive-date = 26 January 2007}}</ref> 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 [[Bluebugging|BlueBug]] was used for this experiment.<ref>{{cite web
|title=BlueBug
|publisher=Trifinite.org
|url=http://trifinite.org/trifinite_stuff_bluebug.html
|access-date=1 February 2007
|archive-date=23 December 2018
|archive-url=https://web.archive.org/web/20181223163514/https://trifinite.org/trifinite_stuff_bluebug.html
|url-status=live
}}</ref> In 2004 the first purported [[computer virus|virus]] using Bluetooth to spread itself among mobile phones appeared on the [[Symbian OS]].<ref>{{cite web
|author=John Oates
|date=15 June 2004
|title=Virus attacks mobiles via Bluetooth
|website=The Register
|url=https://www.theregister.co.uk/2004/06/15/symbian_virus/
|access-date=1 February 2007
|archive-date=23 December 2018
|archive-url=https://web.archive.org/web/20181223163603/https://www.theregister.co.uk/2004/06/15/symbian_virus/
|url-status=live
}}</ref>
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&nbsp;2 Bluetooth radios could be extended to {{convert|1.78|km|mi|abbr=on}} with directional antennas and signal amplifiers.<ref>{{cite web
|title=Long Distance Snarf
|publisher=Trifinite.org
|url=http://trifinite.org/trifinite_stuff_lds.html
|access-date=1 February 2007
|archive-date=23 December 2018
|archive-url=https://web.archive.org/web/20181223163536/https://trifinite.org/trifinite_stuff_lds.html
|url-status=live
}}</ref>
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.<ref>{{cite web
|title=Dispelling Common Bluetooth Misconceptions
|publisher=SANS
|url=http://www.sans.edu/research/security-laboratory/article/bluetooth
|access-date=9 July 2014
|archive-date=14 July 2014
|archive-url=https://web.archive.org/web/20140714150109/http://www.sans.edu/research/security-laboratory/article/bluetooth
|url-status=dead
}}</ref>

==== 2005 ====
In January 2005, a mobile [[malware]] worm known as Lasco surfaced. The worm began targeting mobile phones using [[Symbian OS]] ([[S60 (software platform)|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]]&nbsp;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.<ref>{{cite web
 |url          = http://www.f-secure.com/v-descs/lasco_a.shtml
 |title        = F-Secure Malware Information Pages: Lasco.A
 |publisher    = F-Secure.com
 |access-date   = 5 May 2008
|archive-url  = https://web.archive.org/web/20080517091014/http://www.f-secure.com/v-descs/lasco_a.shtml
 |archive-date = 17 May 2008
|url-status     = dead
}}</ref>

In April 2005, [[University of Cambridge]] security researchers published results of their actual implementation of passive attacks against the [[Personal identification number|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.<ref>{{cite web
|author1=Ford-Long Wong |author2=Frank Stajano |author3=Jolyon Clulow |date=April 2005
|title=Repairing the Bluetooth pairing protocol
|publisher=University of Cambridge Computer Laboratory
|url=http://www.cl.cam.ac.uk/~fw242/publications/2005-WongStaClu-bluetooth.pdf
|access-date=1 February 2007
|archive-url = https://web.archive.org/web/20070616082657/http://www.cl.cam.ac.uk/~fw242/publications/2005-WongStaClu-bluetooth.pdf <!-- Bot retrieved archive --> |archive-date = 16 June 2007}}</ref>

In June 2005, Yaniv Shaked<ref>{{cite web |url=http://www.eng.tau.ac.il/~shakedy |title=Yaniv Shaked's Homepage |access-date=6 November 2007 |url-status=dead |archive-url=https://web.archive.org/web/20071109192150/http://www.eng.tau.ac.il/~shakedy/ |archive-date=9 November 2007 }}</ref> and Avishai Wool<ref>{{cite web|url=http://www.eng.tau.ac.il/~yash/|title=Avishai Wool – אבישי וול|website=tau.ac.il|access-date=4 June 2015|archive-date=23 December 2018|archive-url=https://web.archive.org/web/20181223163419/http://www.eng.tau.ac.il/~yash/|url-status=live}}</ref> 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.<ref>{{cite web
|author1=Yaniv Shaked
|author2=Avishai Wool
|date=2 May 2005
|title=Cracking the Bluetooth PIN
|publisher=School of Electrical Engineering Systems, Tel Aviv University
|url=http://www.eng.tau.ac.il/~yash/shaked-wool-mobisys05/
|access-date=1 February 2007
|archive-date=23 December 2018
|archive-url=https://web.archive.org/web/20181223163532/http://www.eng.tau.ac.il/~yash/shaked-wool-mobisys05/
|url-status=live
}}</ref>

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.<ref>{{cite news
|title=Phone pirates in seek and steal mission
|newspaper=Cambridge Evening News
|url=http://www.cambridge-news.co.uk/news/region_wide/2005/08/17/06967453-8002-45f8-b520-66b9bed6f29f.lpf
|archive-url=https://web.archive.org/web/20070717035938/http://www.cambridge-news.co.uk/news/region_wide/2005/08/17/06967453-8002-45f8-b520-66b9bed6f29f.lpf
|archive-date=17 July 2007
|access-date=4 February 2008
}}</ref>

==== 2006 ====
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.<ref>{{cite web
|title=Going Around with Bluetooth in Full Safety
|url=http://www.securenetwork.it/bluebag_brochure.pdf
|archive-url=https://web.archive.org/web/20060610072813/http://www.securenetwork.it/bluebag_brochure.pdf
|url-status=dead
|archive-date=10 June 2006
|publisher=F-Secure
|date=May 2006
|access-date=4 February 2008
}}</ref>

In October 2006, at the Luxembourgish 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.<ref>{{cite web |last1=Finistere & Zoller |title=All your Bluetooth is belong to us |url=http://archive.hack.lu/2006/Zoller_hack_lu_2006.pdf |website=archive.hack.lu |access-date=20 September 2017 |archive-date=23 December 2018 |archive-url=https://web.archive.org/web/20181223163448/http://archive.hack.lu/2006/Zoller_hack_lu_2006.pdf |url-status=live }}</ref>

==== 2017 ====
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 (operating system)|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 12 September 2017.<ref>{{Cite news|url=https://www.armis.com/blueborne/#/technical|title=BlueBorne Information from the Research Team – Armis Labs|work=armis|access-date=20 September 2017|archive-date=21 September 2017|archive-url=https://web.archive.org/web/20170921075121/https://www.armis.com/blueborne/#/technical|url-status=live}}</ref>

==== 2018 ====
In July 2018, Lior Neumann and [[Eli Biham]], researchers at the Technion – Israel Institute of Technology identified a security vulnerability in the latest Bluetooth pairing procedures: Secure Simple Pairing and LE Secure Connections.<ref>{{cite web|url=https://www.forbes.com/sites/thomasbrewster/2018/07/24/bluetooth-hack-warning-for-iphone-android-and-windows|title=Update Your iPhones And Androids Now If You Don't Want Your Bluetooth Hacked|website=Forbes|date=24 July 2019|access-date=26 September 2019|archive-date=26 September 2019|archive-url=https://web.archive.org/web/20190926093726/https://www.forbes.com/sites/thomasbrewster/2018/07/24/bluetooth-hack-warning-for-iphone-android-and-windows|url-status=live}}</ref><ref>{{cite book|chapter-url=https://eprint.iacr.org/2019/1043|first1=Lior|last1=Neumann|first2=Eli|last2=Biham|chapter=Breaking the Bluetooth Pairing – the Fixed Coordinate Invalid Curve Attack |title=Selected Areas in Cryptography – SAC 2019|series=Lecture Notes in Computer Science|year=2020|volume=11959|pages=250–273|publisher=Technion – Israel Institute of Technology|doi=10.1007/978-3-030-38471-5_11|isbn=978-3-030-38470-8|s2cid=51757249|access-date=26 September 2019|archive-date=18 September 2019|archive-url=https://web.archive.org/web/20190918215324/https://eprint.iacr.org/2019/1043|url-status=live|issn=0302-9743}}</ref>

Also, in October 2018, Karim Lounis, a network security researcher at Queen's University, identified a security vulnerability, called CDV (Connection Dumping Vulnerability), on various Bluetooth devices that allows an attacker to tear down an existing Bluetooth connection and cause the deauthentication and disconnection of the involved devices. The researcher demonstrated the attack on various devices of different categories and from different manufacturers.<ref>{{cite book|chapter-url=https://link.springer.com/chapter/10.1007/978-3-030-12143-3_16|first1=Karim|last1=Lounis|first2=Mohammad|last2=Zulkernine|chapter=Connection Dumping Vulnerability Affecting Bluetooth Availability|title=13th International Conference on Risks and Security of Internet and Systems – CRiSIS 2018|series=Lecture Notes in Computer Science|year=2019|volume=11391|pages=188–204|publisher=Springer|doi=10.1007/978-3-030-12143-3_16|isbn=978-3-030-12142-6|s2cid=59248863|access-date=30 August 2021|archive-date=30 August 2021|archive-url=https://web.archive.org/web/20210830005951/https://link.springer.com/chapter/10.1007/978-3-030-12143-3_16|url-status=live}}</ref>

==== 2019 ====

In August 2019, security researchers at the [[Singapore University of Technology and Design]], Helmholtz Center for Information Security, and [[University of Oxford]] discovered a vulnerability, called KNOB (Key Negotiation of Bluetooth) in the key negotiation that would "brute force the negotiated encryption keys, decrypt the eavesdropped ciphertext, and inject valid encrypted messages (in real-time)".
<ref>{{cite web|url=https://www.forbes.com/sites/zakdoffman/2019/08/15/critical-new-bluetooth-security-issue-leaves-your-devices-and-data-open-to-attack|title=New Critical Bluetooth Security Issue Exposes Millions of Devices To Attack|website=Forbes|date=15 August 2019|access-date=20 August 2019|archive-date=20 August 2019|archive-url=https://web.archive.org/web/20190820200938/https://www.forbes.com/sites/zakdoffman/2019/08/15/critical-new-bluetooth-security-issue-leaves-your-devices-and-data-open-to-attack|url-status=live}}</ref>
<ref>{{cite book|url=https://www.usenix.org/system/files/sec19-antonioli.pdf|title=The KNOB is Broken: Exploiting Low Entropy in the Encryption Key Negotiation of Bluetooth BR/EDR|first1=Daniele|last1=Antonioli|first2=Nils Ole|last2=Tippenhauer|first3=Kasper B.|last3=Rasmussen|publisher=University of Oxford|location=Santa Clara|date=15 August 2019|isbn=9781939133069|access-date=14 June 2021|archive-date=16 April 2021|archive-url=https://web.archive.org/web/20210416163953/https://www.usenix.org/system/files/sec19-antonioli.pdf|url-status=live}}</ref> Google released an [[Android (operating system)|Android]] security patch on 5 August 2019, which removed this vulnerability.<ref>{{cite web|url=https://source.android.com/security/bulletin/2019-08-01.html|title=Android Security Bulletin—August 2019|access-date=5 June 2022}}</ref>

==== 2023 ====

In November 2023, researchers from [[Eurecom]] revealed a new class of attacks known as BLUFFS (Bluetooth Low Energy Forward and Future Secrecy Attacks). These 6 new attacks expand on and work in conjunction with the previously known KNOB and BIAS (Bluetooth Impersonation AttackS) attacks. While the previous KNOB and BIAS attacks allowed an attacker to decrypt and spoof Bluetooth packets within a session, BLUFFS extends this capability to all sessions generated by a device (including past, present, and future). All devices running Bluetooth versions 4.2 up to and including 5.4 are affected.<ref>{{cite web|url=https://www.bleepingcomputer.com/news/security/new-bluffs-attack-lets-attackers-hijack-bluetooth-connections/|title=New BLUFFS attack lets attackers hijack Bluetooth connections|access-date=1 December 2023}}</ref><ref>{{cite report|doi=10.1145/3576915.3623066|chapter=BLUFFS: Bluetooth Forward and Future Secrecy Attacks and Defenses |title=Proceedings of the 2023 ACM SIGSAC Conference on Computer and Communications Security |date=2023 |last1=Antonioli |first1=Daniele |pages=636–650 |isbn=979-8-4007-0050-7 }}</ref>

== Health concerns ==
{{Main|Wireless device radiation and health}}

Bluetooth uses the [[radio frequency]] spectrum in the 2.402{{nbsp}}GHz to 2.480{{nbsp}}GHz range,<ref name="D. Chomienne, M. Eftimakis">{{cite web
|url=http://floatingbluetoothspeakerpro.com/
|author1=D. Chomienne
|author2=M. Eftimakis
|title=Bluetooth Tutorial
|date=20 October 2010
|access-date=11 December 2009
|archive-url=https://web.archive.org/web/20161212135324/http://floatingbluetoothspeakerpro.com/
|archive-date=12 December 2016
|url-status=dead
}}</ref> which is [[non-ionizing radiation]], of similar bandwidth to that used by wireless and mobile phones. No specific harm has been demonstrated, even though wireless transmission has been included by [[International Agency for Research on Cancer|IARC]] in the possible [[carcinogen]] list. Maximum power output from a Bluetooth radio is 100{{nbsp}}[[Milliwatt#Multiples|mW]] for Class{{nbsp}}1, 2.5{{nbsp}}mW for Class{{nbsp}}2, and 1{{nbsp}}mW for Class{{nbsp}}3 devices. Even the maximum power output of Class{{nbsp}}1 is a lower level than the lowest-powered mobile phones.<ref>{{cite web
|url=http://www.ursi.org/Proceedings/ProcGA05/pdf/K03.7(01682).pdf
|author1=M. Hietanen
|author2=T. Alanko
|title=Occupational Exposure Related to Radiofrequency Fields from Wireless Communication Systems
|website=XXVIIIth General Assembly of URSI&nbsp;– Proceedings
|publisher=Union Radio-Scientifique Internationale
|date=October 2005
|access-date=19 April 2007
|archive-url=https://web.archive.org/web/20061006124651/http://www.ursi.org/Proceedings/ProcGA05/pdf/K03.7%2801682%29.pdf
|archive-date=6 October 2006
|url-status=dead
}}</ref> [[UMTS]] and [[W-CDMA]] output 250{{nbsp}}mW, [[GSM frequency bands|GSM1800/1900]] outputs 1000{{nbsp}}mW, and [[GSM frequency bands|GSM850/900]] outputs 2000{{nbsp}}mW.

== Award programs ==
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 competition aimed to stimulate new markets.<ref name="Getstarted">{{cite web |url=http://www.bluetooth.com/Bluetooth/Press/Bluetooth_World_Innovation_Cup.htm |title=Bluetooth Innovation World Cup |publisher=Bluetooth.com |access-date=4 September 2010 |archive-date=23 August 2009 |archive-url=https://web.archive.org/web/20090823092414/http://www.bluetooth.com/Bluetooth/Press/Bluetooth_World_Innovation_Cup.htm |url-status=live }}</ref>

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.<ref>{{cite web |url=https://www.bluetooth.com/news/pressreleases/2017/03/bluetooth-sig-announces-winners-of-imagine-blue-awards-at-bluetooth-world-2017 |title=Bluetooth SIG announces winners of Imagine Blue Awards at Bluetooth World |website=Bluetooth.com |access-date=29 March 2017 }}{{Dead link|date=July 2020 |bot=InternetArchiveBot |fix-attempted=yes }}</ref> The Bluetooth Breakthrough Awards program highlights the most innovative products and applications available today, prototypes coming soon, and student-led projects in the making.<ref>{{cite web|url=https://www.bluetooth.org/en-us/news-events/bluetooth-breakthrough-awards|title=Bluetooth Breakthrough Awards|website=bluetooth.org|access-date=4 June 2015|archive-url=https://web.archive.org/web/20150715025823/https://www.bluetooth.org/en-us/news-events/bluetooth-breakthrough-awards|archive-date=15 July 2015|url-status=dead}}</ref>

== See also ==
{{div col}}
* [[ANT (network)|ANT+]]
* [[Bluetooth stack]] – building blocks that make up the various implementations of the Bluetooth protocol
* [[List of Bluetooth profiles]] – features used within the Bluetooth stack
* [[Bluesniping]]
* [[BlueSoleil]]&nbsp;– proprietary Bluetooth driver
* [[Bluetooth Low Energy beacon]]s ([[Types of beacons#AltBeacon (Radius Networks)|AltBeacon]], [[iBeacon]], [[Eddystone (Google)|Eddystone]])
* [[Bluetooth mesh networking]]
* [[Continua Health Alliance]]
* [[DASH7]]
* [[Audio headset]]
* [[Wi-Fi hotspot]]
* [[Java APIs for Bluetooth]]
* [[Key finder]]
* [[Li-Fi]]
* [[List of Bluetooth protocols]]
* [[MyriaNed]]
* [[Near-field communication]]
* [[NearLink]]
* [[RuBee]]&nbsp;– secure wireless protocol alternative
* [[Tethering]]
* [[Thread (network protocol)]]
* [[IEEE 802.11ah|Wi-Fi HaLow]]
* [[Zigbee]]&nbsp;– low-power lightweight wireless protocol in the [[ISM band]] based on [[IEEE 802.15.4]]
{{div col end}}

== Notes ==
{{notelist}}

== References ==
{{reflist}}

== External links ==
{{commons category|Bluetooth}}
* {{Official website|https://www.bluetooth.com/}}
* [https://www.bluetooth.org/en-us/specification/adopted-specifications Specifications] at [[Bluetooth Special Interest Group|Bluetooth SIG]]

{{Internet access}}
{{cdma}}
{{IEEE standards}}
{{Telecommunications}}

{{Authority control}}

[[Category:Bluetooth]]
[[Category:Mobile computers]]
[[Category:Networking standards]]
[[Category:Wireless communication systems]]
[[Category:Telecommunications-related introductions in 1989]]
[[Category:Swedish inventions]]
[[Category:Dutch inventions]]
[[Category:Cultural depictions of Harald Bluetooth]]