text:
Bluetooth
From Wikipedia, the free encyclopedia
This is the current revision of this page, as edited by 2605:a601:4100:3300:2306:3e9b:ee82:c306 (talk) at 21:18, 28 August 2017. The present address (URL) is a permanent link to this version.
Revision as of 21:18, 28 August 2017 by 2605:a601:4100:3300:2306:3e9b:ee82:c306 (talk)
(diff) ← Previous revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search
This article is about a wireless technology standard. For the medieval king of Denmark, see Harald Bluetooth.
Bluetooth
Developed by
Bluetooth Special Interest Group
Industry
Mobile personal area networks
Compatible hardware
Mobile phones, personal computers, gaming consoles[1]
Physical range
Typically less than 10 m (33 ft), up to 100 m (330 ft); Bluetooth 5.0: 40–400 m (100–1,000 ft) [2][3]
Bluetooth is a wireless technology standard for exchanging data over short distances (using short-wavelength UHF radio waves in the ISM band from 2.4 to 2.485 GHz[4]) from fixed and mobile devices, and building personal area networks (PANs). Invented by telecom vendor Ericsson in 1994,[5] it was originally conceived as a wireless alternative to RS-232 data cables.
Bluetooth is managed by the Bluetooth Special Interest Group (SIG), which has more than 30,000 member companies in the areas of telecommunication, computing, networking, and consumer electronics.[6] The IEEE standardized Bluetooth as IEEE 802.15.1, but no longer maintains the standard. The Bluetooth SIG oversees development of the specification, manages the qualification program, and protects the trademarks.[7] A manufacturer must meet Bluetooth SIG standards to market it as a Bluetooth device.[8] A network of patents apply to the technology, which are licensed to individual qualifying devices.
Contents
[hide]
1 Origin
2 Name and logo
2.1 Etymology of the name
2.2 Logo
3 Implementation
3.1 Communication and connection
4 Uses
4.1 Bluetooth profiles
4.2 List of applications
4.3 Bluetooth vs. Wi-Fi (IEEE 802.11)
4.4 Bluetooth vs. ANT+
4.5 Devices
5 Computer requirements
5.1 Operating system implementation
6 Specifications and features
6.1 Bluetooth 1.0 and 1.0B
6.2 Bluetooth 1.1
6.3 Bluetooth 1.2
6.4 Bluetooth 2.0 + EDR
6.5 Bluetooth 2.1 + EDR
6.6 Bluetooth 3.0 + HS
6.6.1 Ultra-wideband
6.7 Bluetooth 4.0 + LE
6.8 Bluetooth 4.1
6.9 Bluetooth 4.2
6.10 Bluetooth 5
7 Technical information
7.1 Bluetooth protocol stack
7.1.1 LMP
7.1.2 L2CAP
7.1.3 SDP
7.1.4 RFCOMM
7.1.5 BNEP
7.1.6 AVCTP
7.1.7 AVDTP
7.1.8 TCS
7.1.9 Adopted protocols
7.2 Baseband error correction
7.3 Setting up connections
7.4 Pairing and bonding
7.4.1 Motivation
7.4.2 Implementation
7.4.3 Pairing mechanisms
7.4.4 Security concerns
8 Security
8.1 Overview
8.2 Bluejacking
8.3 History of security concerns
8.3.1 2001–2004
8.3.2 2005
8.3.3 2006
8.3.4 2007
8.4 Mitigation
9 Health concerns
10 Bluetooth award programs
11 See also
12 References
13 External links
Origin[edit]
The development of the "short-link" radio technology, later named Bluetooth, was initiated in 1989 by Nils Rydbeck, CTO at Ericsson Mobile in Lund, Sweden, and by Johan Ullman. The purpose was to develop wireless headsets, according to two inventions by Johan Ullman, SE 8902098-6, issued 1989-06-12 and SE 9202239, issued 1992-07-24 . Nils Rydbeck tasked Tord Wingren with specifying and Jaap Haartsen and Sven Mattisson with developing. Both were working for Ericsson in Lund.[9] The specification is based on frequency-hopping spread spectrum technology.
Name and logo[edit]
Etymology of the name[edit]
The name "Bluetooth" is an Anglicised version of the Scandinavian Blåtand/Blåtann (Old Norse blátǫnn), the epithet of the tenth-century king Harald Bluetooth who united dissonant Danish tribes into a single kingdom and, according to legend, introduced Christianity as well. The idea of this name was proposed in 1997 by Jim Kardach of Intel who developed a system that would allow mobile phones to communicate with computers.[10] At the time of this proposal he was reading Frans G. Bengtsson's historical novel The Long Ships about Vikings and King Harald Bluetooth.[11][12] The implication is that Bluetooth does the same with communications protocols, uniting them into one universal standard.[13]
Logo[edit]
The Bluetooth logo is a bind rune merging the Younger Futhark runes (Hagall) (ᚼ) and (Bjarkan) (ᛒ), Harald's initials.[14] [15]
Implementation[edit]
Bluetooth operates at frequencies between 2402 and 2480 MHz, or 2400 and 2483.5 MHz including guard bands 2 MHz wide at the bottom end and 3.5 MHz wide at the top.[16] This is in the globally unlicensed (but not unregulated) industrial, scientific and medical (ISM) 2.4 GHz short-range radio frequency band. Bluetooth uses a radio technology called frequency-hopping spread spectrum. Bluetooth divides transmitted data into packets, and transmits each packet on one of 79 designated Bluetooth channels. Each channel has a bandwidth of 1 MHz. It usually performs 800 hops per second, with Adaptive Frequency-Hopping (AFH) enabled.[16] Bluetooth low energy uses 2 MHz spacing, which accommodates 40 channels.[citation needed]
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 8DPSK modulation may also be used between compatible devices. Devices functioning with GFSK are said to be operating in basic rate (BR) mode where an instantaneous bit rate of 1 Mbit/s is possible. The term Enhanced Data Rate (EDR) is used to describe π/4-DPSK and 8DPSK schemes, each giving 2 and 3 Mbit/s respectively. The combination of these (BR and EDR) modes in Bluetooth radio technology is classified as a "BR/EDR radio".
Bluetooth is a packet-based protocol with a master/slave architecture. One master may communicate with up to seven slaves in a piconet. All devices share the master's clock. Packet exchange is based on the basic clock, defined by the master, which ticks at 312.5 µs intervals. Two clock ticks make up a slot of 625 µs, and two slots make up a slot pair of 1250 µs. In the simple case of single-slot packets the master transmits in even slots and receives in odd slots. The slave, conversely, receives in even slots and transmits in odd slots. Packets may be 1, 3 or 5 slots long, but in all cases the master's transmission begins in even slots and the slave's in odd slots.
The above is valid for "classic" BT. Bluetooth Low Energy, introduced in the 4.0 specification, uses the same spectrum but somewhat differently; see Bluetooth low energy#Radio interface.
Communication and connection[edit]
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 initiator of the connection—but may subsequently operate as slave).
The Bluetooth Core Specification provides for the connection of two or more piconets to form a scatternet, in which certain devices simultaneously play the master role in one piconet and the slave role in another.
At any given time, data can be transferred between the master and one other device (except for the little-used broadcast mode. The master chooses which slave device to address; typically, it switches rapidly from one device to another in a round-robin fashion. Since it is the master that chooses which slave to address, whereas a slave is (in theory) supposed to listen in each receive slot, being a master is a lighter burden than being a slave. Being a master of seven slaves is possible; being a slave of more than one master is possible. The specification is vague as to required behavior in scatternets.[citation needed]
Uses[edit]
Class
Max. permitted power
Typ. range[3]
(m)
(mW)
(dBm)
1
100 20 ~100
2
2.5 4 ~10
3
1 0 ~1
4
0.5 -3 ~0.5
Bluetooth is a standard wire-replacement communications protocol primarily designed for low-power consumption, with a short range based on low-cost transceiver microchips in each device.[17] Because the devices use a radio (broadcast) communications system, they do not have to be in visual line of sight of each other; however, a quasi optical wireless path must be viable.[6] Range is power-class-dependent, but effective ranges vary in practice. See the table on the right.
Officially Class 3 radios have a range of up to 1 metre (3 ft), Class 2, most commonly found in mobile devices, 10 metres (33 ft), and Class 1, primarily for industrial use cases,100 metres (300 ft).[3] Bluetooth Marketing qualifies that Class 1 range is in most cases 20–30 metres (66–98 ft), and Class 2 range 5–10 metres (16–33 ft).[2]
Bluetooth version
Maximum speed[citation needed]
Maximum range[citation needed]
3.0 25 Mbit/s[18] 10 meters (33 ft)
4.0 25 Mbit/s[19] 60 meters (200 ft)[20]
5 50 Mbit/s 240 meters (800 ft)
The effective range varies due to propagation conditions, material coverage, production sample variations, antenna configurations and battery conditions. Most Bluetooth applications are for indoor conditions, where attenuation of walls and signal fading due to signal reflections make the range far lower than specified line-of-sight ranges of the Bluetooth products. Most Bluetooth applications are battery powered Class 2 devices, with little difference in range whether the other end of the link is a Class 1 or Class 2 device as the lower powered device tends to set the range limit. In some cases the effective range of the data link can be extended when a Class 2 device is connecting to a Class 1 transceiver with both higher sensitivity and transmission power than a typical Class 2 device.[21] Mostly, however, the Class 1 devices have a similar sensitivity to Class 2 devices. Connecting two Class 1 devices with both high sensitivity and high power can allow ranges far in excess of the typical 100m, depending on the throughput required by the application. Some such devices allow open field ranges of up to 1 km and beyond between two similar devices without exceeding legal emission limits.[22][23][24]
The Bluetooth Core Specification mandates a range of not less than 10 metres (33 ft), but there is no upper limit on actual range. Manufacturers' implementations can be tuned to provide the range needed for each case.[3]
Bluetooth profiles[edit]
Main article: List of Bluetooth profiles
To use Bluetooth wireless technology, a device must be able to interpret certain Bluetooth profiles, which are definitions of possible applications and specify general behaviors that Bluetooth-enabled devices use to communicate with other Bluetooth devices. These profiles include settings to parameterize and to control the communication from the start. Adherence to profiles saves the time for transmitting the parameters anew before the bi-directional link becomes effective. There are a wide range of Bluetooth profiles that describe many different types of applications or use cases for devices.[25][26]
List of applications[edit]
A typical Bluetooth mobile phone headset.
Wireless control of and communication between a mobile phone and a handsfree headset. This was one of the earliest applications to become popular.[27]
Wireless control of and communication between a mobile phone and a Bluetooth compatible car stereo system.
Wireless control of and communication with iOS and Android device phones, tablets and portable wireless speakers.[28]
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.[29]
Wireless networking between PCs in a confined space and where little bandwidth is required.[30]
Wireless communication with PC input and output devices, the most common being the mouse, keyboard and printer.
Transfer of files, contact details, calendar appointments, and reminders between devices with OBEX.
Replacement of previous wired RS-232 serial communications in test equipment, GPS receivers, medical equipment, bar code scanners, and traffic control devices.
For controls where infrared was often used.
For low bandwidth applications where higher USB bandwidth is not required and cable-free connection desired.
Sending small advertisements from Bluetooth-enabled advertising hoardings to other, discoverable, Bluetooth devices.[31]
Wireless bridge between two Industrial Ethernet (e.g., PROFINET) networks.
Seventh and eighth generation game consoles such as Nintendo's Wii,[32] and Sony's PlayStation 3 use Bluetooth for their respective wireless controllers.
Dial-up internet access on personal computers or PDAs using a data-capable mobile phone as a wireless modem.
Short-range transmission of health sensor data from medical devices to mobile phone, set-top box or dedicated telehealth devices.[33][34]
Allowing a DECT phone to ring and answer calls on behalf of a nearby mobile phone.
Real-time location systems (RTLS) are used to track and identify the location of objects in real time using "Nodes" or "tags" attached to, or embedded in, the objects tracked, and "Readers" that receive and process the wireless signals from these tags to determine their locations.[35]
Personal security application on mobile phones for prevention of theft or loss of items. The protected item has a Bluetooth marker (e.g., a tag) that is in constant communication with the phone. If the connection is broken (the marker is out of range of the phone) then an alarm is raised. This can also be used as a man overboard alarm. A product using this technology has been available since 2009.[36]
Calgary, Alberta, Canada's Roads Traffic division uses data collected from travelers' Bluetooth devices to predict travel times and road congestion for motorists.[37]
Wireless transmission of audio (a more reliable alternative to FM transmitters)
Bluetooth vs. Wi-Fi (IEEE 802.11)[edit]
Bluetooth and Wi-Fi (the brand name for products using IEEE 802.11 standards) have some similar applications: setting up networks, printing, or transferring files. Wi-Fi is intended as a replacement for high-speed cabling for general local area network access in work areas or home. This category of applications is sometimes called wireless local area networks (WLAN). Bluetooth was intended for portable equipment and its applications. The category of applications is outlined as the wireless personal area network (WPAN). Bluetooth is a replacement for cabling in a variety of personally carried applications in any setting, and also works for fixed location applications such as smart energy functionality in the home (thermostats, etc.).
Wi-Fi and Bluetooth are to some extent complementary in their applications and usage. Wi-Fi is usually access point-centered, with an asymmetrical client-server connection with all traffic routed through the access point, while Bluetooth is usually symmetrical, between two Bluetooth devices. Bluetooth serves well in simple applications where two devices need to connect with minimal configuration like a button press, as in headsets and remote controls, while Wi-Fi suits better in applications where some degree of client configuration is possible and high speeds are required, especially for network access through an access node. However, Bluetooth access points do exist, and ad-hoc connections are possible with Wi-Fi though not as simply as with Bluetooth. Wi-Fi Direct was recently developed to add a more Bluetooth-like ad-hoc functionality to Wi-Fi.[citation needed]
Bluetooth vs. ANT+[edit]
Bluetooth Smart and ANT+ are similar wireless technologies that allow information to pass between electronic devices.
Bluetooth devices will talk to other electronics connected to the Bluetooth network – and the same goes for ANT+ devices.
Of course there are advantages and disadvantages of each protocol that must be considered when choosing.
Devices[edit]
A Bluetooth USB dongle with a 100 m range.
Bluetooth exists in many products, such as telephones, speakers, tablets, media players, robotics systems, handheld, laptops and console gaming equipment, and some high definition headsets, modems, and watches.[38] The technology 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.[39] Bluetooth devices can advertise all of the services they provide.[40] This makes using services easier, because more of the security, network address and permission configuration can be automated than with many other network types.[39]
Computer requirements[edit]
A typical Bluetooth USB dongle.
An internal notebook Bluetooth card (14×36×4 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 computers and most recent laptops come with a built-in Bluetooth radio, others require an external adapter, typically in the form of a small USB "dongle."
Unlike its predecessor, IrDA, which requires a separate adapter for each device, Bluetooth lets multiple devices communicate with a computer over a single adapter.[41]
Operating system implementation[edit]
For more details on this topic, see 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.[42] Previous versions required users to install their Bluetooth adapter's own drivers, which were not directly supported by Microsoft.[43] 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.[42] Windows 7 works with Bluetooth v2.1+EDR and Extended Inquiry Response (EIR).[42]
The Windows XP and Windows Vista/Windows 7 Bluetooth stacks support the following Bluetooth profiles natively: PAN, SPP, DUN, HID, HCRP. The Windows XP stack can be replaced by a third party stack that supports more profiles or newer Bluetooth versions. The Windows Vista/Windows 7 Bluetooth stack supports vendor-supplied additional profiles without requiring that the Microsoft stack be replaced.[42]
Apple products have worked with Bluetooth since Mac OS X v10.2, which was released in 2002.[44]
Linux has two popular Bluetooth stacks, BlueZ and Affix. The BlueZ stack is included with most Linux kernels and was originally developed by Qualcomm.[45] The Affix stack was developed by Nokia.
FreeBSD features Bluetooth since its v5.0 release.
NetBSD features Bluetooth since its v4.0 release. Its Bluetooth stack was ported to OpenBSD as well, however OpenBSD later removed it for security reasons.
Specifications and features[edit]
The specifications were formalized by the Bluetooth Special Interest Group (SIG). The SIG was formally announced on 20 May 1998. Today it has a membership of over 30,000 companies worldwide.[46] It was established by Ericsson, IBM, Intel, Toshiba and Nokia, and later joined by many other companies.
All versions of the Bluetooth standards support downward compatibility.[1] That lets the latest standard cover all older versions.
The Bluetooth Core Specification Working Group (CSWG) produces mainly 4 kinds of specifications:
The Bluetooth Core Specification, release cycle is typically a few years in between
Core Specification Addendum (CSA), release cycle can be as tight as a few times per year
Core Specification Supplements (CSS), can be released very quickly
Errata (Available with a user account: Errata login)
Bluetooth 1.0 and 1.0B[edit]
Versions 1.0 and 1.0B[citation needed] had many problems, and manufacturers had difficulty making their products interoperable. Versions 1.0 and 1.0B also included mandatory Bluetooth hardware device address (BD_ADDR) transmission in the Connecting process (rendering anonymity impossible at the protocol level), which was a major setback for certain services planned for use in Bluetooth environments.
Bluetooth 1.1[edit]
Ratified as IEEE Standard 802.15.1–2002[47]
Many errors found in the v1.0B specifications were fixed.
Added possibility of non-encrypted channels.
Received Signal Strength Indicator (RSSI).
Bluetooth 1.2[edit]
Major enhancements include:
Faster Connection and Discovery
Adaptive frequency-hopping spread spectrum (AFH), which improves resistance to radio frequency interference by avoiding the use of crowded frequencies in the hopping sequence.
Higher transmission speeds in practice than in v1.1, up to 721 kbit/s.[48]
Extended Synchronous Connections (eSCO), which improve voice quality of audio links by allowing retransmissions of corrupted packets, and may optionally increase audio latency to provide better concurrent data transfer.
Host Controller Interface (HCI) operation with three-wire UART.
Ratified as IEEE Standard 802.15.1–2005[49]
Introduced Flow Control and Retransmission Modes for L2CAP.
Bluetooth 2.0 + EDR[edit]
This version of the Bluetooth Core Specification was released in 2004. The main difference is the introduction of an Enhanced Data Rate (EDR) for faster data transfer. The bit rate of EDR is 3 Mbit/s, although the maximum data transfer rate (allowing for inter-packet time and acknowledgements) is 2.1 Mbit/s.[48] EDR uses a combination of GFSK and Phase Shift Keying modulation (PSK) with two variants, π/4-DQPSK and 8DPSK.[50] 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.[51]
Bluetooth 2.1 + EDR[edit]
Bluetooth Core Specification Version 2.1 + EDR was adopted by the Bluetooth SIG on 26 July 2007.[50]
The headline feature of v2.1 is secure simple pairing (SSP): this improves the pairing experience for Bluetooth devices, while increasing the use and strength of security. See the section on Pairing below for more details.[52]
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[edit]
Version 3.0 + HS of the Bluetooth Core Specification[50] was adopted by the Bluetooth SIG on 21 April 2009. Bluetooth v3.0 + HS provides theoretical data transfer speeds of up to 24 Mbit/s, though not over the Bluetooth link itself. Instead, the Bluetooth link is used for negotiation and establishment, and the high data rate traffic is carried over a colocated 802.11 link.
The main new feature is AMP (Alternative MAC/PHY), the addition of 802.11 as a high speed transport. The High-Speed part of the specification is not mandatory, and hence only devices that display the "+HS" logo actually support Bluetooth over 802.11 high-speed data transfer. A Bluetooth v3.0 device without the "+HS" suffix is only required to support features introduced in Core Specification Version 3.0[53] or earlier Core Specification Addendum 1.[54]
L2CAP Enhanced modes
Enhanced Retransmission Mode (ERTM) implements reliable L2CAP channel, while Streaming Mode (SM) implements unreliable channel with no retransmission or flow control. Introduced in Core Specification Addendum 1.
Alternative MAC/PHY
Enables the use of alternative MAC and PHYs for transporting Bluetooth profile data. The Bluetooth radio is still used for device discovery, initial connection and profile configuration. However, when large quantities of data must be sent, the high speed alternative MAC PHY 802.11 (typically associated with Wi-Fi) transports the data. This means that Bluetooth uses proven low power connection models when the system is idle, and the faster radio when it must send large quantities of data. AMP links require enhanced L2CAP modes.
Unicast Connectionless Data
Permits sending service data without establishing an explicit L2CAP channel. It is intended for use by applications that require low latency between user action and reconnection/transmission of data. This is only appropriate for small amounts of data.
Enhanced Power Control
Updates the power control feature to remove the open loop power control, and also to clarify ambiguities in power control introduced by the new modulation schemes added for EDR. Enhanced power control removes the ambiguities by specifying the behaviour that is expected. The feature also adds closed loop power control, meaning RSSI filtering can start as the response is received. Additionally, a "go straight to maximum power" request has been introduced. This is expected to deal with the headset link loss issue typically observed when a user puts their phone into a pocket on the opposite side to the headset.
Ultra-wideband[edit]
The high speed (AMP) feature of Bluetooth v3.0 was originally intended for UWB, but the WiMedia Alliance, the body responsible for the flavor of UWB intended for Bluetooth, announced in March 2009 that it was disbanding, and ultimately UWB was omitted from the Core v3.0 specification.[55]
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.[56][57][58][59][60][61]
In October 2009 the Bluetooth Special Interest Group suspended development of UWB as part of the alternative MAC/PHY, Bluetooth v3.0 + HS solution. A small, but significant, number of former WiMedia members had not and would not sign up to the necessary agreements for the IP transfer. The Bluetooth SIG is now in the process of evaluating other options for its longer term roadmap.[62][63][64]
Bluetooth 4.0 + LE[edit]
See also: Bluetooth low energy
The Bluetooth SIG completed the Bluetooth Core Specification version 4.0 (called Bluetooth Smart) and has been adopted as of 30 June 2010. It includes Classic Bluetooth, Bluetooth high speed and Bluetooth low energy protocols. Bluetooth high speed is based on Wi-Fi, and Classic Bluetooth consists of legacy Bluetooth protocols.
Bluetooth low energy, previously known as Wibree,[65] 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 running off a coin cell. Chip designs allow for two types of implementation, dual-mode, single-mode and enhanced past versions.[66] 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.[67]
In a single-mode implementation, only the low energy protocol stack is implemented. STMicroelectronics,[68] AMICCOM,[69] CSR,[70] Nordic Semiconductor[71] and Texas Instruments[72] have released single mode Bluetooth low energy solutions.
In a dual-mode implementation, Bluetooth Smart functionality is integrated into an existing Classic Bluetooth controller. As of March 2011[update], the following semiconductor companies have announced the availability of chips meeting the standard: Qualcomm-Atheros, CSR, Broadcom[73][74] and Texas Instruments. The compliant architecture shares all of Classic Bluetooth’s existing radio and functionality resulting in a negligible cost increase compared to Classic Bluetooth.
Cost-reduced single-mode chips, which enable highly integrated and compact devices, feature a lightweight Link Layer providing ultra-low power idle mode operation, simple device discovery, and reliable point-to-multipoint data transfer with advanced power-save and secure encrypted connections at the lowest possible cost.
General improvements in version 4.0 include the changes necessary to facilitate BLE modes, as well the Generic Attribute Profile (GATT) and Security Manager (SM) services with AES Encryption.
Core Specification Addendum 2 was unveiled in December 2011; it contains improvements to the audio Host Controller Interface and to the High Speed (802.11) Protocol Adaptation Layer.
Core Specification Addendum 3 revision 2 has an adoption date of 24 July 2012.
Core Specification Addendum 4 has an adoption date of 12 February 2013.
Bluetooth 4.1[edit]
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.[75]
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[76]
Notice that some features were already available in a Core Specification Addendum (CSA) before the release of v4.1.
Bluetooth 4.2[edit]
Released on December 2, 2014, it Introduces features for the Internet of Things.
The major areas of improvement are:
Low Energy Secure Connection with Data Packet Length Extension
Link Layer Privacy with Extended Scanner Filter Policies
Internet Protocol Support Profile (IPSP) version 6 ready for Bluetooth Smart things to support connected home
Older Bluetooth hardware may receive 4.2 features such as Data Packet Length Extension and improved privacy via firmware updates.[77][78]
Bluetooth 5[edit]
The Bluetooth SIG officially unveiled Bluetooth 5 during a media event in London on 16 June 2016. Its new features are mainly focused on emerging Internet of Things technology. The Samsung Galaxy S8 launched with Bluetooth 5 support in April 2017. Marketing drops the point number; so that it is just "Bluetooth 5" (not 5.0 or LE like Bluetooth 4.0). The change is for the sake of "Simplifying our marketing, communicating user benefits more effectively and making it easier to signal significant technology updates to the market."[79]
Bluetooth 5 provides double the speed (50 Mbit/s), fourfold the range, and eightfold the data broadcasting capacity of transmissions compared to Bluetooth 4.x low energy. The increase in transmissions could be important for Internet of Things devices, where many nodes connect throughout a whole house. Bluetooth 5 adds functionality for connectionless services such as location-relevant navigation[80] of low-energy Bluetooth connections.[81][82][83]
The major areas of improvement are:
Slot Availability Mask (SAM)
2 Mbit/s PHY for LE
LE Long Range
High Duty Cycle Non-Connectable Advertising
LE Advertising Extensions
LE Channel Selection Algorithm #2
Features Added in CSA5 - Integrated in v5.0:
Higher Output Power
The following features were removed in this version of the specification:
Park State[84]
Technical information[edit]
Bluetooth protocol stack[edit]
Main articles: Bluetooth stack and Bluetooth protocols
Bluetooth Protocol Stack
Bluetooth is defined as a layer protocol architecture consisting of core protocols, cable replacement protocols, telephony control protocols, and adopted protocols.[85] Mandatory protocols for all Bluetooth stacks are LMP, L2CAP and SDP. In addition, devices that communicate with Bluetooth almost universally can use these protocols: HCI and RFCOMM.[citation needed]
LMP[edit]
The Link Management Protocol (LMP) is used for set-up and control of the radio link between two devices. Implemented on the controller.
L2CAP[edit]
The Logical Link Control and Adaptation Protocol (L2CAP) is used to multiplex multiple logical connections between two devices using different higher level protocols. Provides segmentation and reassembly of on-air packets.
In Basic mode, L2CAP provides packets with a payload configurable up to 64 kB, with 672 bytes as the default MTU, and 48 bytes as the minimum mandatory supported MTU.
In Retransmission and Flow Control modes, L2CAP can be configured either for isochronous data or reliable data per channel by performing retransmissions and CRC checks.
Bluetooth Core Specification Addendum 1 adds two additional L2CAP modes to the core specification. These modes effectively deprecate original Retransmission and Flow Control modes:
Enhanced Retransmission Mode (ERTM): This mode is an improved version of the original retransmission mode. This mode provides a reliable L2CAP channel.
Streaming Mode (SM): This is a very simple mode, with no retransmission or flow control. This mode provides an unreliable L2CAP channel.
Reliability in any of these modes is optionally and/or additionally guaranteed by the lower layer Bluetooth BDR/EDR air interface by configuring the number of retransmissions and flush timeout (time after which the radio flushes packets). In-order sequencing is guaranteed by the lower layer.
Only L2CAP channels configured in ERTM or SM may be operated over AMP logical links.
SDP[edit]
The Service Discovery Protocol (SDP) allows a device to discover services offered by other devices, and their associated parameters. For example, when you use a mobile phone with a Bluetooth headset, the phone uses SDP to determine which Bluetooth profiles the headset can use (Headset Profile, Hands Free Profile, Advanced Audio Distribution Profile (A2DP) etc.) and the protocol multiplexer settings needed for the phone to connect to the headset using each of them. Each service is identified by a Universally Unique Identifier (UUID), with official services (Bluetooth profiles) assigned a short form UUID (16 bits rather than the full 128).
RFCOMM[edit]
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.
BNEP[edit]
The Bluetooth Network Encapsulation Protocol (BNEP) is used for transferring another protocol stack's data via an L2CAP channel. Its main purpose is the transmission of IP packets in the Personal Area Networking Profile. BNEP performs a similar function to SNAP in Wireless LAN.
AVCTP[edit]
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.
AVDTP[edit]
The Audio/Video Distribution Transport Protocol (AVDTP) is used by the advanced audio distribution profile to stream music to stereo headsets over an L2CAP channel intended for video distribution profile in the Bluetooth transmission.
TCS[edit]
The Telephony Control Protocol – Binary (TCS BIN) is the bit-oriented protocol that defines the call control signaling for the establishment of voice and data calls between Bluetooth devices. Additionally, "TCS BIN defines mobility management procedures for handling groups of Bluetooth TCS devices."
TCS-BIN is only used by the cordless telephony profile, which failed to attract implementers. As such it is only of historical interest.
Adopted protocols[edit]
Adopted protocols are defined by other standards-making organizations and incorporated into Bluetooth’s protocol stack, allowing Bluetooth to code protocols only when necessary. The adopted protocols include:
Point-to-Point Protocol (PPP)
Internet standard protocol for transporting IP datagrams over a point-to-point link.
TCP/IP/UDP
Foundation Protocols for TCP/IP protocol suite
Object Exchange Protocol (OBEX)
Session-layer protocol for the exchange of objects, providing a model for object and operation representation
Wireless Application Environment/Wireless Application Protocol (WAE/WAP)
WAE specifies an application framework for wireless devices and WAP is an open standard to provide mobile users access to telephony and information services.[85]
Baseband error correction[edit]
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[edit]
Any Bluetooth device in discoverable mode transmits the following information on demand:
Device name
Device class
List of services
Technical information (for example: device features, manufacturer, Bluetooth specification used, clock offset)
Any device may perform an inquiry to find other devices to connect to, and any device can be configured to respond to such inquiries. However, if the device trying to connect knows the address of the device, it always responds to direct connection requests and transmits the information shown in the list above if requested. Use of a device's services may require pairing or acceptance by its owner, but the connection itself can be initiated by any device and held until it goes out of range. Some devices can be connected to only one device at a time, and connecting to them prevents them from connecting to other devices and appearing in inquiries until they disconnect from the other device.
Every device has a unique 48-bit address. However, these addresses are generally not shown in inquiries. Instead, friendly Bluetooth names are used, which can be set by the user. This name appears when another user scans for devices and in lists of paired devices.
Most cellular phones have the Bluetooth name set to the manufacturer and model of the phone by default. Most cellular phones and laptops show only the Bluetooth names and special programs are required to get additional information about remote devices. This can be confusing as, for example, there could be several cellular phones in range named T610 (see Bluejacking).
Pairing and bonding[edit]
Motivation[edit]
Many services offered over Bluetooth can expose private data or let a connecting party control the Bluetooth device. Security reasons make it necessary to recognize specific devices, and thus enable control over which devices can connect to a given Bluetooth device. At the same time, it is useful for Bluetooth devices to be able to establish a connection without user intervention (for example, as soon as in range).
To resolve this conflict, Bluetooth uses a process called bonding, and a bond is generated through a process called pairing. The pairing process is triggered either by a specific request from a user to generate a bond (for example, the user explicitly requests to "Add a Bluetooth device"), or it is triggered automatically when connecting to a service where (for the first time) the identity of a device is required for security purposes. These two cases are referred to as dedicated bonding and general bonding respectively.
Pairing often involves some level of user interaction. This user interaction confirms the identity of the devices. When pairing successfully completes, a bond forms between the two devices, enabling those two devices to connect to each other in the future without repeating the pairing process to confirm device identities. When desired, the user can remove the bonding relationship.
Implementation[edit]
During pairing, the two devices establish a relationship by creating a shared secret known as a link key. If both devices store the same link key, they are said to be paired or bonded. A device that wants to communicate only with a bonded device can cryptographically authenticate the identity of the other device, ensuring it is the same device it previously paired with. Once a link key is generated, an authenticated Asynchronous Connection-Less (ACL) link between the devices may be encrypted to protect exchanged data against eavesdropping. Users can delete link keys from either device, which removes the bond between the devices—so it is possible for one device to have a stored link key for a device it is no longer paired with.
Bluetooth services generally require either encryption or authentication and as such require pairing before they let a remote device connect. Some services, such as the Object Push Profile, elect not to explicitly require authentication or encryption so that pairing does not interfere with the user experience associated with the service use-cases.
Pairing mechanisms[edit]
Pairing mechanisms changed significantly with the introduction of Secure Simple Pairing in Bluetooth v2.1. The following summarizes the pairing mechanisms:
Legacy pairing: This is the only method available in Bluetooth v2.0 and before. Each device must enter a PIN code; pairing is only successful if both devices enter the same PIN code. Any 16-byte UTF-8 string may be used as a PIN code; however, not all devices may be capable of entering all possible PIN codes.
Limited input devices: The obvious example of this class of device is a Bluetooth Hands-free headset, which generally have few inputs. These devices usually have a fixed PIN, for example "0000" or "1234", that are hard-coded into the device.
Numeric input devices: Mobile phones are classic examples of these devices. They allow a user to enter a numeric value up to 16 digits in length.
Alpha-numeric input devices: PCs and smartphones are examples of these devices. They allow a user to enter full UTF-8 text as a PIN code. If pairing with a less capable device the user must be aware of the input limitations on the other device; there is no mechanism available for a capable device to determine how it should limit the available input a user may use.
Secure Simple Pairing (SSP): This is required by Bluetooth v2.1, although a Bluetooth v2.1 device may only use legacy pairing to interoperate with a v2.0 or earlier device. Secure Simple Pairing uses a form of public key cryptography, and some types can help protect against man in the middle, or MITM attacks. SSP has the following authentication mechanisms:
Just works: As the name implies, this method just works, with no user interaction. However, a device may prompt the user to confirm the pairing process. This method is typically used by headsets with very limited IO capabilities, and is more secure than the fixed PIN mechanism this limited set of devices uses for legacy pairing. This method provides no man-in-the-middle (MITM) protection.
Numeric comparison: If both devices have a display, and at least one can accept a binary yes/no user input, they may use Numeric Comparison. This method displays a 6-digit numeric code on each device. The user should compare the numbers to ensure they are identical. If the comparison succeeds, the user(s) should confirm pairing on the device(s) that can accept an input. This method provides MITM protection, assuming the user confirms on both devices and actually performs the comparison properly.
Passkey Entry: This method may be used between a device with a display and a device with numeric keypad entry (such as a keyboard), or two devices with numeric keypad entry. In the first case, the display presents a 6-digit numeric code to the user, who then enters the code on the keypad. In the second case, the user of each device enters the same 6-digit number. Both of these cases provide MITM protection.
Out of band (OOB): This method uses an external means of communication, such as Near Field Communication (NFC) to exchange some information used in the pairing process. Pairing is completed using the Bluetooth radio, but requires information from the OOB mechanism. This provides only the level of MITM protection that is present in the OOB mechanism.
SSP is considered simple for the following reasons:
In most cases, it does not require a user to generate a passkey.
For use cases not requiring MITM protection, user interaction can be eliminated.
For numeric comparison, MITM protection can be achieved with a simple equality comparison by the user.
Using OOB with NFC enables pairing when devices simply get close, rather than requiring a lengthy discovery process.
Security concerns[edit]
Prior to Bluetooth v2.1, encryption is not required and can be turned off at any time. Moreover, the encryption key is only good for approximately 23.5 hours; using a single encryption key longer than this time allows simple XOR attacks to retrieve the encryption key.
Turning off encryption is required for several normal operations, so it is problematic to detect if encryption is disabled for a valid reason or for a security attack.
Bluetooth v2.1 addresses this in the following ways:
Encryption is required for all non-SDP (Service Discovery Protocol) connections
A new Encryption Pause and Resume feature is used for all normal operations that require that encryption be disabled. This enables easy identification of normal operation from security attacks.
The encryption key must be refreshed before it expires.
Link keys may be stored on the device file system, not on the Bluetooth chip itself. Many Bluetooth chip manufacturers let link keys be stored on the device—however, if the device is removable, this means that the link key moves with the device.
Security[edit]
Overview[edit]
See also: Mobile security § Attacks based on communication networks
Bluetooth implements confidentiality, authentication and key derivation with custom algorithms based on the SAFER+ block cipher. Bluetooth key generation is generally based on a Bluetooth PIN, which must be entered into both devices. This procedure might be modified if one of the devices has a fixed PIN (e.g., for headsets or similar devices with a restricted user interface). During pairing, an initialization key or master key is generated, using the E22 algorithm.[86] The E0 stream cipher is used for encrypting packets, granting confidentiality, and is based on a shared cryptographic secret, namely a previously generated link key or master key. Those keys, used for subsequent encryption of data sent via the air interface, rely on the Bluetooth PIN, which has been entered into one or both devices.
An overview of Bluetooth vulnerabilities exploits was published in 2007 by Andreas Becker.[87]
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.[88]
Bluetooth v2.1 – finalized in 2007 with consumer devices first appearing in 2009 – makes significant changes to Bluetooth's security, including pairing. See the pairing mechanisms section for more about these changes.
Bluejacking[edit]
Main article: 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!"[89] Bluejacking does not involve the removal or alteration of any data from the device.[citation needed] Bluejacking can also involve taking control of a mobile device wirelessly and phoning a premium rate line, owned by the bluejacker. Security advances have alleviated this issue.
History of security concerns[edit]
2001–2004[edit]
In 2001, Jakobsson and Wetzel from Bell Laboratories discovered flaws in the Bluetooth pairing protocol and also pointed to vulnerabilities in the encryption scheme.[90] 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.[91] In a subsequent experiment, Martin Herfurt from the trifinite.group was able to do a field-trial at the CeBIT fairgrounds, showing the importance of the problem to the world. A new attack called BlueBug was used for this experiment.[92] In 2004 the first purported virus using Bluetooth to spread itself among mobile phones appeared on the Symbian OS.[93] The virus was first described by Kaspersky Lab and requires users to confirm the installation of unknown software before it can propagate. The virus was written as a proof-of-concept by a group of virus writers known as "29A" and sent to anti-virus groups. Thus, it should be regarded as a potential (but not real) security threat to Bluetooth technology or Symbian OS since the virus has never spread outside of this system. In August 2004, a world-record-setting experiment (see also Bluetooth sniping) showed that the range of Class 2 Bluetooth radios could be extended to 1.78 km (1.11 mi) with directional antennas and signal amplifiers.[94] 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.[95]
2005[edit]
In January 2005, a mobile malware worm known as Lasco surfaced. The worm began targeting mobile phones using Symbian OS (Series 60 platform) using Bluetooth enabled devices to replicate itself and spread to other devices. The worm is self-installing and begins once the mobile user approves the transfer of the file (velasco.sis) from another device. Once installed, the worm begins looking for other Bluetooth enabled devices to infect. Additionally, the worm infects other .SIS files on the device, allowing replication to another device through use of removable media (Secure Digital, Compact Flash, etc.). The worm can render the mobile device unstable.[96]
In April 2005, Cambridge University security researchers published results of their actual implementation of passive attacks against the PIN-based pairing between commercial Bluetooth devices. They confirmed that attacks are practicably fast, and the Bluetooth symmetric key establishment method is vulnerable. To rectify this vulnerability, they designed an implementation that showed that stronger, asymmetric key establishment is feasible for certain classes of devices, such as mobile phones.[97]
In June 2005, Yaniv Shaked[98] and Avishai Wool[99] 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.[100]
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.[101]
2006[edit]
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.[102]
2007[edit]
In October 2007, at the Luxemburgish Hack.lu Security Conference, Kevin Finistere and Thierry Zoller demonstrated and released a remote root shell via Bluetooth on Mac OS X v10.3.9 and v10.4. They also demonstrated the first Bluetooth PIN and Linkkeys cracker, which is based on the research of Wool and Shaked.[citation needed]
Mitigation[edit]
Options to mitigate against Bluetooth security attacks include:[103]
Enable Bluetooth only when required
Enable Bluetooth discovery only when necessary, and disable discovery when finished
Do not enter link keys or PINs when unexpectedly prompted to do so
Remove paired devices when not in use
Regularly update firmware on Bluetooth-enabled devices
Health concerns[edit]
Main article: Wireless electronic devices and health
Bluetooth uses the microwave radio frequency spectrum in the 2.402 GHz to 2.480 GHz range,[104] which is non-ionizing radiation, of similar bandwidth to the one used by wireless and mobile phones. No specific demonstration of harm has been demonstrated up to date, even if wireless transmission has been included by IARC[disambiguation needed] in the possible carcinogen list. Maximum power output from a Bluetooth radio is 100 mW for class 1, 2.5 mW for class 2, and 1 mW for class 3 devices. Even the maximum power output of class 1 is a lower level than the lowest powered mobile phones.[105] UMTS and W-CDMA output 250 mW, GSM1800/1900 outputs 1000 mW, and GSM850/900 outputs 2000 mW.
Bluetooth award programs[edit]
The Bluetooth Innovation World Cup, a marketing initiative of the Bluetooth Special Interest Group (SIG), was an international competition that encouraged the development of innovations for applications leveraging Bluetooth technology in sports, fitness and health care products. The aim of the competition was to stimulate new markets.[106]
The Bluetooth Innovation World Cup morphed into the Bluetooth Breakthrough Awards in 2013. The Breakthrough Awards[107] Bluetooth program highlights the most innovative products and applications available today, prototypes coming soon, and student-led projects in the making.
See also[edit]
Bluesniping
BlueSoleil – proprietary driver
Bluetooth low energy beacons (iBeacon and Eddystone)
Continua Health Alliance
DASH7
Headset (audio)
Hotspot (Wi-Fi)
Java APIs for Bluetooth
Li-Fi
MyriaNed
Near field communication
RuBee – secure wireless protocol alternative
Tethering
ZigBee – low-power lightweight wireless protocol in the ISM band
References[edit]
Jump up ^ DualShock#DualShock 4, Wikipedia
^ Jump up to: a b bluAir. "Bluetooth Range: 100m, 1km, or 10km?". bluair.pl. Retrieved 4 June 2015.
^ Jump up to: a b c d "Basics | Bluetooth Technology Website". Bluetooth.com. 23 May 2010.
Jump up ^ "basic rate/enhanced data rate (br/edr)". Bluetooth.com. Retrieved 3 June 2016.
Jump up ^ "Bluetooth traveler". hoovers.com. Archived from the original on 11 January 2011. Retrieved 9 April 2010.
^ Jump up to: a b Newton, Harold. (2007). Newton’s telecom dictionary. New York: Flatiron Publishing.
Jump up ^ "Bluetooth.org". Bluetooth.org. Retrieved 3 May 2011.
Jump up ^ "Brand Enforcement Program". Bluetooth.org. Retrieved 2 November 2013.
Jump up ^ "The Bluetooth Blues". Information Age. 24 May 2001. Archived from the original on 22 December 2007. Retrieved 1 February 2008.
Jump up ^ "'So, that's why it's called Bluetooth!' and other surprising tech name origins". PCWorld. Retrieved 2017-08-16.
Jump up ^ Kardach, Jim (5 March 2008). "Tech History: How Bluetooth got its name". Retrieved 11 June 2013.
Jump up ^ Mark Forsyth. The etymologicon. // Icon Books Ltd. London N79DP, 2011. p. 139.
Jump up ^ "Milestones in the Bluetooth advance". Ericsson Technology Licensing. 22 March 2004. Archived from the original on 20 June 2004.
Jump up ^ "Bluetooth on Twitter".
Jump up ^ "Bluetooth Experience Icons" (PDF). Bluetooth Special Interest Group. Retrieved 2016-10-21. Bluetooth Experience Icons borrow two of these three features: the blue color and the rune-inspired symbol.
^ Jump up to: a b "Bluetooth Radio Interface, Modulation & Channels". Radio-Electronics.com.
Jump up ^ "How Bluetooth Technology Works". Bluetooth SIG. Archived from the original on 17 January 2008. Retrieved 1 February 2008.
Jump up ^ "Wi-Fi Direct vs. Bluetooth 4.0: A Battle for Supremacy". PCWorld. Retrieved 2017-07-22.
Jump up ^ "Wi-Fi Direct vs. Bluetooth 4.0: A Battle for Supremacy". PCWorld. Retrieved 2017-07-22.
Jump up ^ "Wi-Fi Direct vs. Bluetooth 4.0: A Battle for Supremacy". PCWorld. Retrieved 2017-07-22.
Jump up ^ "Class 1 Bluetooth Dongle Test". Amperordirect.com. Retrieved 4 September 2010.
Jump up ^ "WT41 Long Range Bluetooth Module".
Jump up ^ "BluBear Industrial Long Range Bluetooth 2.1 Module with EDR". Archived from the original on 17 July 2013.
Jump up ^ "OEM Bluetooth Serial Port Module OBS433".
Jump up ^ "Profiles Overview". Bluetooth.com. Retrieved 3 June 2013.
Jump up ^ Ian, Paul. "Wi-Fi Direct vs. Bluetooth 4.0: A Battle for Supremacy". PC World. Retrieved 27 December 2013.
Jump up ^ "History of the Bluetooth Special Interest Group". Bluetooth.com.
Jump up ^ "Portable Wireless Bluetooth Compatible Speakers". Trusound Audio.
Jump up ^ "Bluetooth Revisited". www.techpayout.com. Retrieved 10 May 2016.
Jump up ^ "Bluetooth Technology". mobileinfo.com.
Jump up ^ John Fuller. "How Bluetooth Surveillance Works". howstuffworks. Retrieved 26 May 2015.
Jump up ^ "Wii Controller". Bluetooth SIG. Archived from the original on 20 February 2008. Retrieved 1 February 2008.
Jump up ^ "Telemedicine.jp". Telemedicine.jp. Retrieved 4 September 2010.
Jump up ^ "Tai nghe bluetooth nokia". tainghebluetooth.com.
Jump up ^ "Real Time Location Systems" (PDF). clarinox. Retrieved 4 August 2010.
Jump up ^ "Tenbu's nio Is Kind of Like a Car Alarm for Your Cellphone". OhGizmo!. Retrieved 4 June 2015.
Jump up ^ "Wireless waves used to track travel times". CTV Calgary News. 26 November 2012. Retrieved 11 July 2013.
Jump up ^ "Watch". Bluetooth.com. Retrieved 4 September 2010.
^ Jump up to: a b "How Bluetooth Works". How Stuff Works. 30 June 2010.
Jump up ^ "Specification Documents" (PDF). Bluetooth.com. 30 June 2010. [dead link]
Jump up ^ "Bluetooth for Programmers" (PDF). MIT Computer Science And Artificial Intelligence Laboratory.
^ Jump up to: a b c d "Bluetooth Wireless Technology FAQ – 2010". Retrieved 4 September 2010.
Jump up ^ "Network Protection Technologie". Changes to Functionality in Microsoft Windows XP Service Pack 2. Microsoft Technet. Retrieved 1 February 2008.
Jump up ^ "Apple Introduces "Jaguar," the Next Major Release of Mac OS X" (Press release). Apple. 17 July 2002. Retrieved 4 February 2008.
Jump up ^ "Official Linux Bluetooth protocol stack". BlueZ. Retrieved 4 September 2010.
Jump up ^ "English Introduction to Membership". Bluetooth.org. Retrieved 2014-05-13.
Jump up ^ "IEEE Std 802.15.1–2002 – IEEE Standard for Information technology – Telecommunications and information exchange between systems – Local and metropolitan area networks – Specific requirements Part 15.1: Wireless Medium Access Control (MAC) and Physical Layer (PHY) Specifications for Wireless Personal Area Networks (WPANs)". Ieeexplore.ieee.org. doi:10.1109/IEEESTD.2002.93621. Retrieved 4 September 2010.
^ Jump up to: a b Guy Kewney (16 November 2004). "High speed Bluetooth comes a step closer: enhanced data rate approved". Newswireless.net. Retrieved 4 February 2008.
Jump up ^ "IEEE Std 802.15.1–2005 – IEEE Standard for Information technology – Telecommunications and information exchange between systems – Local and metropolitan area networks – Specific requirements Part 15.1: Wireless Medium Access Control (MAC) and Physical Layer (PHY) Specifications for Wireless Personal Area Networks (W Pans)". Ieeexplore.ieee.org. doi:10.1109/IEEESTD.2005.96290. Retrieved 4 September 2010.
^ Jump up to: a b c "Specification Documents". Bluetooth SIG. Retrieved 3 May 2012.
Jump up ^ "HTC TyTN Specification" (PDF). HTC. Archived from the original (PDF) on 12 October 2006. Retrieved 4 February 2008.
Jump up ^ "Simple Pairing Whitepaper" (PDF). Version V10r00. Bluetooth SIG. 3 August 2006. Archived from the original (PDF) on 18 October 2006. Retrieved 1 February 2007.
Jump up ^ "Bluetooth Core Version 3.0 + HS specification".
Jump up ^ "Bluetooth Core Specification Addendum (CSA) 1".
Jump up ^ David Meyer (22 April 2009). "Bluetooth 3.0 released without ultrawideband". zdnet.co.uk. Retrieved 22 April 2009.
Jump up ^ "Wimedia.org". Wimedia.org. 4 January 2010. Archived from the original on 26 April 2002. Retrieved 4 September 2010.
Jump up ^ "Wimedia.org". Wimedia.org. Retrieved 4 September 2010. [dead link]
Jump up ^ "Wimedia.org". Archived from the original on 23 March 2009. Retrieved 4 September 2010.
Jump up ^ "bluetooth.com". Retrieved 29 January 2015.
Jump up ^ "USB.org". USB.org. 16 March 2009. Retrieved 4 September 2010.
Jump up ^ "Incisor.tv". Incisor.tv. 16 March 2009. Retrieved 4 September 2010.
Jump up ^ "Bluetooth group drops ultrawideband, eyes 60 GHz". EETimes. Retrieved 4 June 2015.
Jump up ^ "Report: Ultrawideband dies by 2013". EETimes. Retrieved 4 June 2015.
Jump up ^ "Simon Stenhouse - Leech Attempt" (PDF). incisor.tv. Retrieved 4 June 2015.
Jump up ^ "Wibree forum merges with Bluetooth SIG" (PDF) (Press release). Nokia. 12 June 2007. Retrieved 4 February 2008.
Jump up ^ "Bluetooth.com". Bluetooth.com. Retrieved 4 September 2010.
Jump up ^ "Bluetooth SIG unveils Smart Marks, explains v4.0 compatibility with unnecessary complexity". Engadget.
Jump up ^ "BlueNRG Bluetooth® low energy wireless network processor - STMicroelectronics". st.com. Retrieved 4 June 2015.
Jump up ^ ":::笙科電子-Amiccom:::". Archived from the original on 25 August 2013.
Jump up ^ "CSR.com". CSR. Retrieved 7 April 2011.
Jump up ^ "Nordicsemi.com". Nordic Semiconductor. Retrieved 7 April 2011.
Jump up ^ "TI.com". Texas Instruments. Retrieved 7 April 2011.
Jump up ^ "iFixit MacBook Air 13" Mid 2011 Teardown". iFixit.com. Retrieved 27 July 2011.
Jump up ^ "Broadcom.com – BCM20702 – Single-Chip Bluetooth® 4.0 HCI Solution with Bluetooth Low Energy (BLE) Support". Broadcom. Retrieved 27 July 2011.
Jump up ^ "Press Releases Detail | Bluetooth Technology Website". Bluetooth.com. 2013-12-04. Retrieved 2014-05-13.
Jump up ^ "Adopted Specification; Bluetooth Technology Website". Bluetooth.com. 2013-12-04. Retrieved 2014-05-14.
Jump up ^ "Redmondpie".
Jump up ^ "DailyTech".
Jump up ^ Bluetooth 5 promises four times the speed and twice the range of Bluetooth 4.0 LE transmissions
Jump up ^ "Bluetooth 5 standard brings range, speed and capacity boost for IoT".
Jump up ^ Bluetooth® 5 Quadruples Range, Doubles Speed, Increases Data Broadcasting Capacity by 800% | Bluetooth Technology Website
Jump up ^ ""Bluetooth 5" spec coming next week with 4x more range and 2x better speed [Updated]".
Jump up ^ "Bluetooth 5: everything you need to know".
Jump up ^ "Bluetooth Core Specification v5.0" (PDF download). www.bluetooth.org.
^ Jump up to: a b Stallings, William. (2005). Wireless communications & networks.'=' Upper Saddle River, NJ: Pearson Prentice Hall.
Jump up ^ Juha T. Vainio (25 May 2000). "Bluetooth Security" (PDF). Helsinki University of Technology. Retrieved 1 January 2009.
Jump up ^ Andreas Becker (16 August 2007). "Bluetooth Security & Hacks" (PDF). Ruhr-Universität Bochum. Retrieved 10 October 2007.
Jump up ^ Scarfone, K. & Padgette, J. (September 2008). "Guide to Bluetooth Security" (PDF). National Institute of Standards and Technology. Retrieved 3 July 2013.
Jump up ^ John Fuller. "What is bluejacking?". howstuffworks. Retrieved 26 May 2015.
Jump up ^ "Security Weaknesses in Bluetooth". RSA Security Conf. – Cryptographer’s Track. CiteSeerX 10.1.1.23.7357  . Missing or empty |url= (help); |access-date= requires |url= (help)
Jump up ^ "Bluetooth". The Bunker. Archived from the original on 26 January 2007. Retrieved 1 February 2007.
Jump up ^ "BlueBug". Trifinite.org. Retrieved 1 February 2007.
Jump up ^ John Oates (15 June 2004). "Virus attacks mobiles via Bluetooth". The Register. Retrieved 1 February 2007.
Jump up ^ "Long Distance Snarf". Trifinite.org. Retrieved 1 February 2007.
Jump up ^ "Dispelling Common Bluetooth Misconceptions". SANS. Retrieved 9 July 2014.
Jump up ^ "F-Secure Malware Information Pages: Lasco.A". F-Secure.com. Retrieved 5 May 2008.
Jump up ^ Ford-Long Wong; Frank Stajano; Jolyon Clulow (April 2005). "Repairing the Bluetooth pairing protocol" (PDF). University of Cambridge Computer Laboratory. Archived from the original (PDF) on 16 June 2007. Retrieved 1 February 2007.
Jump up ^ "Archived copy". Archived from the original on 9 November 2007. Retrieved 2007-11-06.
Jump up ^ "Avishai Wool - אבישי וול". tau.ac.il. Retrieved 4 June 2015.
Jump up ^ Yaniv Shaked; Avishai Wool (2 May 2005). "Cracking the Bluetooth PIN". School of Electrical Engineering Systems, Tel Aviv University. Retrieved 1 February 2007.
Jump up ^ "Phone pirates in seek and steal mission". Cambridge Evening News. Archived from the original on 17 July 2007. Retrieved 4 February 2008.
Jump up ^ "Going Around with Bluetooth in Full Safety" (PDF). F-Secure. May 2006. Archived from the original (PDF) on 2006-06-10. Retrieved 4 February 2008.
Jump up ^ Elaina Chai; Ben Deardorff & Cathy Wu. "Hacking Bluetooth" (PDF). Retrieved 26 April 2015.
Jump up ^ D. Chomienne; M. Eftimakis (20 October 2010). "Bluetooth Tutorial" (PDF). Retrieved 11 December 2009.
Jump up ^ M. Hietanen; T. Alanko (October 2005). "Occupational Exposure Related to Radiofrequency Fields from Wireless Communication Systems" (PDF). XXVIIIth General Assembly of URSI – Proceedings. Union Radio-Scientifique Internationale. Archived from the original (PDF) on 6 October 2006. Retrieved 19 April 2007.
Jump up ^ "Bluetooth Innovation World Cup". Bluetooth.com. Retrieved 4 September 2010.
Jump up ^ "Bluetooth Breakthrough Awards". bluetooth.org. Retrieved 4 June 2015.
External links[edit]
Wikimedia Commons has media related to Bluetooth.
Official website
Specifications at Bluetooth SIG
[show]
v
t
e
Internet access
Wired
Cable
Dial-up
DOCSIS
DSL
Ethernet
FTTx
G.hn
HD-PLC
HomePlug
HomePNA
IEEE 1901
ISDN
MoCA
PON
Power-line
Broadband
Wireless
Bluetooth
DECT
EVDO
GPRS
HSPA
iBurst
Li-Fi
LTE
MMDS
Muni Wi-Fi
Satellite
UMTS-TDD
Wi-Fi
WiMAX
WiBro
Wireless USB
[show]
v
t
e
Spread spectrum in digital communications
Main articles
Spread spectrum
Code-division multiple access (CDMA)
History
Hedy Lamarr
Commercial use
More...
Spread spectrum methods
Direct-sequence spread spectrum (DSSS)
Frequency-hopping spread spectrum (FHSS)
Chirp spread spectrum (CSS)
Time-hopping spread spectrum (THSS)
CDMA schemes
W-CDMA
TD-CDMA
TD-SCDMA
DS-CDMA
FH-CDMA
MC-CDMA
Major implementations
Space Network (NASA)
GPS
Galileo
GLONASS
Bluetooth
Cordless phones: DECT
Cellular
EV-DO Mobile
IS-95 (aka cdmaOne)
CDMA2000 (aka IS-2000)
Also
Qualcomm
Verizon
Major concepts
PN (pseudorandom noise) code
Chip
Near–far problem
Power spectral density (PSD)
Process gain
Rake receiver
Low probability of intercept
See also
Digital communication
Modulation
Statistical multiplexing
Waveform
[show]
v
t
e
IEEE standards
Current
488
730
754
Revision
854
828
829
896
1003
1014
1016
1076
1149.1
1154
1164
1275
1278
1284
1355
1394
1451
1497
1516
1541
1547
1584
1588
1596
1603
1613
1666
1667
1675
1685
1800
1801
1815
1850
1900
1901
1902
1904
1905
2030
11073
12207
14764
16085
16326
29148
42010
802 series
802.1
D
p
Q
Qat
Qay
w
X
ab
ad
AE
ag
ah
ak
aq
ax
az
802.11
a
b
c
d
e
f
g
h
i
j
k
n
p
r
s
u
v
w
y
ac
ad
af
ah
ai
ax
ay
.2
.3
.4
.5
.6
.7
.8
.9
.10
.12
.14
.15
.1
.4
.4a
.16
d · e
.17
.18
.20
.21
.22
Proposed
P1363
P1619
P1699
P1823
P1906.1
Superseded
754-1985
830
1219
1233
1362
1364
1471
See also
IEEE Standards Association
Category:IEEE standards
[show]
v
t
e
Telecommunications
History
Beacon
Broadcasting
Cable protection system
Cable TV
Communications satellite
Computer network
Drums
Electrical telegraph
Fax
Heliographs
Hydraulic telegraph
Internet
Mass media
Mobile phone
Optical telecommunication
Optical telegraphy
Pager
Photophone
Prepaid mobile phone
Radio
Radiotelephone
Satellite communications
Semaphore
Smartphone
Smoke signals
Telecommunications history
Telautograph
Telegraphy
Teleprinter (teletype)
Telephone
The Telephone Cases
Television
Timeline of communication technology
Undersea telegraph line
Videoconferencing
Videophone
Videotelephony
Whistled language
Pioneers
Edwin Howard Armstrong
John Logie Baird
Paul Baran
Alexander Graham Bell
Tim Berners-Lee
Jagadish Chandra Bose
Vint Cerf
Claude Chappe
Donald Davies
Lee de Forest
Philo Farnsworth
Reginald Fessenden
Elisha Gray
Erna Schneider Hoover
Charles K. Kao
Hedy Lamarr
Innocenzo Manzetti
Guglielmo Marconi
Antonio Meucci
Radia Perlman
Alexander Stepanovich Popov
Johann Philipp Reis
Nikola Tesla
Camille Tissot
Alfred Vail
Charles Wheatstone
Vladimir K. Zworykin
Transmission
media
Characteristic impedance
Coaxial cable
Electromagnetic radiation
Electrical cable
Free-space optical communication
Heaviside condition
Loading coil
Molecular communication
Optical fiber
Telegrapher's equations
Network topology
and switching
Links
Nodes
Terminal node
Network switching (circuit
packet)
Telephone exchange
Multiplexing
Space-division
Frequency-division
Time-division
Polarization-division
Orbital angular-momentum
Code-division
Networks
ARPANET
BITNET
Cellular network
Computer
CYCLADES
Ethernet
FidoNet
Internet
ISDN
LAN
Mobile
NGN
NPL network
Public Switched Telephone
Radio
Telecommunications equipment
Television
Telex
WAN
Wireless
World Wide Web
Category
Portal
Authority control
GND: 4638953-2
Retrieved from "https://en.wikipedia.org/w/index.php?title=Bluetooth&oldid=797730862"
Categories:
Channel access methods
Bluetooth
Mobile computers
Networking standards
Wireless
Telecommunications-related introductions in 1994
Swedish inventions
Hidden categories:
All articles with dead external links
Articles with dead external links from February 2017
Pages using web citations with no URL
Pages using citations with accessdate and no URL
Use dmy dates from July 2016
All articles with unsourced statements
Articles with unsourced statements from August 2017
Articles with unsourced statements from April 2012
Articles with unsourced statements from December 2016
Articles with unsourced statements from May 2015
Articles with unsourced statements from September 2015
Articles containing potentially dated statements from March 2011
All articles containing potentially dated statements
Articles with unsourced statements from December 2013
All articles with links needing disambiguation
Articles with links needing disambiguation from June 2017
Wikipedia articles with GND identifiers
Navigation menu
Personal tools
Not logged in
Talk
Contributions
Create account
Log in
Namespaces
Article
Talk
Variants
Views
Read
Edit
View history
More
Search
Navigation
Main page
Contents
Featured content
Current events
Random article
Donate to Wikipedia
Wikipedia store
Interaction
Help
About Wikipedia
Community portal
Recent changes
Contact page
Tools
What links here
Related changes
Upload file
Special pages
Permanent link
Page information
Wikidata item
Cite this page
Print/export
Create a book
Download as PDF
Printable version
In other projects
Wikimedia Commons
Languages
العربية
Azərbaycanca
বাংলা
Bân-lâm-gú
Беларуская
Беларуская (тарашкевіца)
Български
Bosanski
Català
Čeština
Cymraeg
Dansk
Deutsch
Eesti
Ελληνικά
Español
Esperanto
Euskara
فارسی
Français
Galego
한국어
Հայերեն
हिन्दी
Hrvatski
Bahasa Indonesia
Íslenska
Italiano
עברית
ಕನ್ನಡ
Kapampangan
ქართული
Қазақша
Кыргызча
Latviešu
Lëtzebuergesch
Lietuvių
Lumbaart
Magyar
മലയാളം
मराठी
მარგალური
مصرى
Bahasa Melayu
မြန်မာဘာသာ
Nederlands
नेपाली
日本語
Napulitano
Norsk
Norsk nynorsk
ਪੰਜਾਬੀ
پنجابی
Polski
Português
Română
Русский
Саха тыла
Scots
Seeltersk
Shqip
සිංහල
Simple English
Slovenčina
Slovenščina
Soomaaliga
کوردی
Српски / srpski
Srpskohrvatski / српскохрватски
Suomi
Svenska
Tagalog
தமிழ்
తెలుగు
ไทย
Türkçe
Українська
اردو
Tiếng Việt
ייִדיש
粵語
中文
Edit links
This page was last edited on 28 August 2017, at 21:18.
Text is available under the Creative Commons Attribution-ShareAlike License; additional terms may apply. By using this site, you agree to the Terms of Use and Privacy Policy. Wikipedia® is a registered trademark of the Wikimedia Foundation, Inc., a non-profit organization.
Privacy policy
About Wikipedia
Disclaimers
Contact Wikipedia
Developers
Cookie statement
Mobile view
Enable previews

values: mw-page-base noprint

values: mw-head-base noprint

attrs: id class style

values: firstHeading firstHeading en

values: siteSub noprint

value: bdi

value: td

value: tr

value: tbody

value: table

attrs: id class role

values:
revision-info-current
plainlinks fmbox fmbox-system
presentation

attrs: id style

attrs: alt src width height srcset data-file-width data-file-height

values:
/wiki/Gaming_console
mw-redirect
Gaming console

values:
/wiki/Radio_waves
mw-redirect
Radio waves

values: Institute of Electrical and Electronics Engineers

values:
/wiki/Runic_alphabet
mw-redirect
Runic alphabet

values: Adaptive frequency-hopping spread spectrum

values:
/wiki/Bluetooth_low_energy
mw-redirect
Bluetooth low energy

values: This claim needs references to reliable sources. (August 2017)

values:
noprint Inline-Template Template-Fact
white-space:nowrap;

values:
/wiki/Gaussian_frequency-shift_keying
mw-redirect
Gaussian frequency-shift keying

values: Edit section: Communication and connection

values: This claim needs references to reliable sources. (April 2012)

values: This claim needs references to reliable sources. (December 2016)

values:
/wiki/Wireless_speakers
mw-redirect
Wireless speakers

values:
/wiki/Bluetooth_headset
mw-redirect
Bluetooth headset

values:
/wiki/Computer_printer
mw-redirect
Computer printer

values: History of video game consoles (seventh generation)

values: History of video game consoles (eighth generation)

values:
/wiki/Game_consoles
mw-redirect
Game consoles

values:
/wiki/Calgary,_Alberta,_Canada
mw-redirect
Calgary, Alberta, Canada

values: Edit section: Bluetooth vs. Wi-Fi (IEEE 802.11)

values:
/wiki/Wireless_local_area_network
mw-redirect
Wireless local area network

values: This claim needs references to reliable sources. (May 2015)

values:
/wiki/Bluetooth_Smart
mw-redirect
Bluetooth Smart

values: Edit section: Operating system implementation

values:
/wiki/Windows_XP_Service_Pack_2
mw-redirect
Windows XP Service Pack 2

values:
/wiki/Mac_OS_X_v10.2
mw-redirect
Mac OS X v10.2

values: Edit section: Specifications and features

values: This claim needs references to reliable sources. (September 2015)

values:
/wiki/Radio_frequency_interference
mw-redirect
Radio frequency interference

values:
/wiki/Phase_shift_keying
mw-redirect
Phase shift keying

values:
/wiki/Media_Access_Control
mw-redirect
Media Access Control

values:
plainlinks noprint asof-tag update
display:none;

values:
/wiki/Internet_of_Things
mw-redirect
Internet of Things

values:
/wiki/Data_packet
mw-redirect
Data packet

values:
/wiki/Bluetooth_protocols
mw-redirect
Bluetooth protocols

values:
/wiki/Bluetooth_profile
mw-redirect
Bluetooth profile

values:
/wiki/Universally_Unique_Identifier
mw-redirect
Universally Unique Identifier

values:
/wiki/IP_datagram
mw-redirect
IP datagram

values:
/wiki/Error_correction
mw-redirect
Error correction

values:
/wiki/Public_key_cryptography
mw-redirect
Public key cryptography

values:
/wiki/Near_Field_Communication
mw-redirect
Near Field Communication

values: National Institute of Standards and Technology

values: This claim needs references to reliable sources. (December 2013)

values: Edit section: History of security concerns

values:
/wiki/Bell_Laboratories
mw-redirect
Bell Laboratories

values:
/wiki/Bluetooth_sniping
mw-redirect
Bluetooth sniping

values:
/wiki/Compact_Flash
mw-redirect
Compact Flash

values:
/wiki/Cambridge_University
mw-redirect
Cambridge University

values: International Agency for Research on Cancer

values:
/wiki/Bluetooth_low_energy_beacons
mw-redirect
Bluetooth low energy beacons

values: div-col columns column-count column-count-2

values: -moz-column-count: 2; -webkit-column-count: 2; column-count: 2;

values:
nofollow
external text
http://www.bluair.pl/bluetooth-range

values:
nofollow
http://www.telemedicine.jp/
external text

values:
nofollow
http://www.bluez.org/
external text

values:
nofollow
external text
//doi.org/10.1109%2FIEEESTD.2002.93621

values:
nofollow
external text
//doi.org/10.1109%2FIEEESTD.2005.96290

values:
nofollow
http://www.wimedia.org/
external text

values:
nofollow
http://www.amiccom.com.tw/
external text

values:
nofollow
external text
http://www.iki.fi/jiitv/bluesec.pdf

attrs: alt src title width height srcset data-file-width data-file-height

values:
nofollow
external text
http://www.eng.tau.ac.il/~shakedy

values:
nofollow
http://www.eng.tau.ac.il/~yash/
external text

values:
nofollow
http://floatingbluetoothspeakerpro.com/
external text

values: -moz-column-width: 30em; -webkit-column-width: 30em; column-width: 30em; list-style-type: decimal;

values:
nofollow
http://www.bluetooth.org/
external text

values: Digital Enhanced Cordless Telecommunications

values: Multichannel Multipoint Distribution Service

values: nowraplinks collapsible autocollapse navbox-inner

values:
/wiki/Spread_Spectrum#History
mw-redirect
Spread Spectrum

values:
/wiki/Direct-sequence_CDMA
mw-redirect
Direct-sequence CDMA

values: Multi-carrier code-division multiple access

values:
/wiki/Low_probability_of_intercept
mw-redirect
Low probability of intercept

values: nowraplinks hlist collapsible autocollapse navbox-inner

values:
/wiki/IEEE_floating_point
mw-redirect
IEEE floating point

values: Service Interoperability in Ethernet Passive Optical Networks

values: Provider Backbone Bridge Traffic Engineering

values: Universal Power Adapter for Mobile Devices

values:
/wiki/File:Telecom-icon.svg
image
Telecommunications symbol

values: navigation navbox Telecommunications padding:3px

values:
nofollow
external text
http://d-nb.info/gnd/4638953-2

values: Category:Telecommunications-related introductions in 1994

values: Category:All articles with dead external links

values: Category:Articles with dead external links from February 2017

values: Category:Pages using web citations with no URL

values: Category:Pages using citations with accessdate and no URL

values: Category:All articles with unsourced statements

values: Category:Articles with unsourced statements from August 2017

values: Category:Articles with unsourced statements from April 2012

values: Category:Articles with unsourced statements from December 2016

values: Category:Articles with unsourced statements from May 2015

values: Category:Articles with unsourced statements from September 2015

values: Category:Articles containing potentially dated statements from March 2011

values: Category:All articles containing potentially dated statements

values: Category:Articles with unsourced statements from December 2013

values: Category:All articles with links needing disambiguation

values: Category:Articles with links needing disambiguation from June 2017

values: Category:Wikipedia articles with GND identifiers

values: Discussion about edits from this IP address [ctrl-alt-n]

values: A list of edits made from this IP address [ctrl-alt-y]

values: You are encouraged to create an account and log in; however, it is not mandatory

values: You're encouraged to log in; however, it's not mandatory. [ctrl-alt-o]

values:
/wiki/Bluetooth
View the content page [ctrl-alt-c]
c

values: Discussion about the content page [ctrl-alt-t]

values: p-namespaces navigation vectorTabs p-namespaces-label

values:
p-variants
navigation
vectorMenu emptyPortlet
p-variants-label

values: Past revisions of this page [ctrl-alt-h]

values: p-views navigation vectorTabs p-views-label

values:
p-cactions
navigation
vectorMenu emptyPortlet
p-cactions-label

values:
mw-wiki-logo
/wiki/Main_Page
Visit the main page

values:
/wiki/Main_Page
Visit the main page [ctrl-alt-z]
z

values: Featured content – the best of Wikipedia

values:
uls-settings-trigger
Language settings
0
button
true

values: بلوتوث – Arabic

values:
https://az.wikipedia.org/wiki/Bluetooth
Bluetooth – Azerbaijani
az
az
interlanguage-link-target

values: ব্লুটুথ – Bangla

values:
https://be.wikipedia.org/wiki/Bluetooth
Bluetooth – Belarusian
be
be
interlanguage-link-target

values: Bluetooth – Belarusian (Taraškievica orthography)

values:
https://bg.wikipedia.org/wiki/Bluetooth
Bluetooth – Bulgarian
bg
bg
interlanguage-link-target

values:
https://bs.wikipedia.org/wiki/Bluetooth
Bluetooth – Bosnian
bs
bs
interlanguage-link-target

values:
https://ca.wikipedia.org/wiki/Bluetooth
Bluetooth – Catalan
ca
ca
interlanguage-link-target

values:
https://cs.wikipedia.org/wiki/Bluetooth
Bluetooth – Czech
cs
cs
interlanguage-link-target

values:
https://cy.wikipedia.org/wiki/Bluetooth
Bluetooth – Welsh
cy
cy
interlanguage-link-target

values:
https://da.wikipedia.org/wiki/Bluetooth
Bluetooth – Danish
da
da
interlanguage-link-target

values:
https://de.wikipedia.org/wiki/Bluetooth
Bluetooth – German
de
de
interlanguage-link-target

values:
https://et.wikipedia.org/wiki/Bluetooth
Bluetooth – Estonian
et
et
interlanguage-link-target

values:
https://el.wikipedia.org/wiki/Bluetooth
Bluetooth – Greek
el
el
interlanguage-link-target

values:
https://es.wikipedia.org/wiki/Bluetooth
Bluetooth – Spanish
es
es
interlanguage-link-target

values:
https://eo.wikipedia.org/wiki/Bludento
Bludento – Esperanto
eo
eo
interlanguage-link-target

values:
https://eu.wikipedia.org/wiki/Bluetooth
Bluetooth – Basque
eu
eu
interlanguage-link-target

values: بلوتوث – Persian

values:
https://fr.wikipedia.org/wiki/Bluetooth
Bluetooth – French
fr
fr
interlanguage-link-target

values:
https://gl.wikipedia.org/wiki/Bluetooth
Bluetooth – Galician
gl
gl
interlanguage-link-target

values:
https://hy.wikipedia.org/wiki/Bluetooth
Bluetooth – Armenian
hy
hy
interlanguage-link-target

values: ब्लूटूथ – Hindi

values:
https://hr.wikipedia.org/wiki/Bluetooth
Bluetooth – Croatian
hr
hr
interlanguage-link-target

values:
https://id.wikipedia.org/wiki/Bluetooth
Bluetooth – Indonesian
id
id
interlanguage-link-target

values:
https://is.wikipedia.org/wiki/Bluetooth
Bluetooth – Icelandic
is
is
interlanguage-link-target

values:
https://it.wikipedia.org/wiki/Bluetooth
Bluetooth – Italian
it
it
interlanguage-link-target

values: בלוטות' – Hebrew

values: ಬ್ಲ್ಯೂಟೂತ್ – Kannada

values:
https://ka.wikipedia.org/wiki/Bluetooth
Bluetooth – Georgian
ka
ka
interlanguage-link-target

values:
https://kk.wikipedia.org/wiki/Bluetooth
Bluetooth – Kazakh
kk
kk
interlanguage-link-target

values:
https://ky.wikipedia.org/wiki/Bluetooth
Bluetooth – Kyrgyz
ky
ky
interlanguage-link-target

values:
https://lv.wikipedia.org/wiki/Bluetooth
Bluetooth – Latvian
lv
lv
interlanguage-link-target

values:
https://lb.wikipedia.org/wiki/Bluetooth
Bluetooth – Luxembourgish
lb
lb
interlanguage-link-target

values:
https://lt.wikipedia.org/wiki/Bluetooth
Bluetooth – Lithuanian
lt
lt
interlanguage-link-target

values:
https://hu.wikipedia.org/wiki/Bluetooth
Bluetooth – Hungarian
hu
hu
interlanguage-link-target

values: ബ്ലൂടൂത്ത് – Malayalam

values: ब्लूटूथ – Marathi

values:
https://ms.wikipedia.org/wiki/Bluetooth
Bluetooth – Malay
ms
ms
interlanguage-link-target

values: ဘလူးထူးသ် – Burmese

values:
https://nl.wikipedia.org/wiki/Bluetooth
Bluetooth – Dutch
nl
nl
interlanguage-link-target

values: ब्लुटुथ – Nepali

values:
https://ja.wikipedia.org/wiki/Bluetooth
Bluetooth – Japanese
ja
ja
interlanguage-link-target

values: ਬਲੂਟੁੱਥ – Punjabi

values:
https://pl.wikipedia.org/wiki/Bluetooth
Bluetooth – Polish
pl
pl
interlanguage-link-target

values:
https://pt.wikipedia.org/wiki/Bluetooth
Bluetooth – Portuguese
pt
pt
interlanguage-link-target

values:
https://ro.wikipedia.org/wiki/Bluetooth
Bluetooth – Romanian
ro
ro
interlanguage-link-target

values:
https://ru.wikipedia.org/wiki/Bluetooth
Bluetooth – Russian
ru
ru
interlanguage-link-target

values:
https://sq.wikipedia.org/wiki/Bluetooth
Bluetooth – Albanian
sq
sq
interlanguage-link-target

values: බ්ලූටූත් – Sinhala

values:
https://sk.wikipedia.org/wiki/Bluetooth
Bluetooth – Slovak
sk
sk
interlanguage-link-target

values:
https://sl.wikipedia.org/wiki/Bluetooth
Bluetooth – Slovenian
sl
sl
interlanguage-link-target

values:
https://so.wikipedia.org/wiki/Bluetooth
Bluetooth – Somali
so
so
interlanguage-link-target

values: Блутут – Serbian

values:
https://sh.wikipedia.org/wiki/Bluetooth
Bluetooth – Serbo-Croatian
sh
sh
interlanguage-link-target

values:
https://fi.wikipedia.org/wiki/Bluetooth
Bluetooth – Finnish
fi
fi
interlanguage-link-target

values:
https://sv.wikipedia.org/wiki/Bluetooth
Bluetooth – Swedish
sv
sv
interlanguage-link-target

values:
https://tl.wikipedia.org/wiki/Bluetooth
Bluetooth – Tagalog
tl
tl
interlanguage-link-target

values: புளூடூத் – Tamil

values: బ్లూటూత్ – Telugu

values: บลูทูธ – Thai

values:
https://tr.wikipedia.org/wiki/Bluetooth
Bluetooth – Turkish
tr
tr
interlanguage-link-target

values:
https://uk.wikipedia.org/wiki/Bluetooth
Bluetooth – Ukrainian
uk
uk
interlanguage-link-target

values: بلوٹوتھ – Urdu

values:
https://vi.wikipedia.org/wiki/Bluetooth
Bluetooth – Vietnamese
vi
vi
interlanguage-link-target

values: בלו טוט – Yiddish

values: /static/images/wikimedia-button-1.5x.png 1.5x, /static/images/wikimedia-button-2x.png 2x

values: /static/images/poweredby_mediawiki_132x47.png 1.5x, /static/images/poweredby_mediawiki_176x62.png 2x

values:
suggestions
display: none; font-size: 13px;

values: mediawiki ltr sitedir-ltr mw-hide-empty-elt ns-0 ns-subject page-Bluetooth rootpage-Bluetooth skin-vector action-view