Bluetooth® technology is all around us:  electronic beacons guiding firefighters through buildings; wearable medical devices sending patient’s biological data to a physician’s tablets; manufacturing equipment monitoring in 400,000 square foot warehouses; and more.  Bluetooth technology is growing and is expected to have an install base of over 48 billion by 2021 (per ABI Internet of Everything Market Tracker).

So how does Bluetooth work?  Bluetooth low energy has 40 physical channels in the 2.4GHz ISM band, each separated by 2MHz.  Bluetooth defines two transmissions types: data and advertising transmissions.  As such, 3 of these 40 channels are dedicated to advertising and 37 to data. 

Whether it’s a beacon (transmitting location, weather, or other data) or a fitness watch making a long term connection with a host (tablet or phone), all peripheral devices, at least initially, begin in advertising mode.

Advertising allows devices to broadcast information defining their intentions.

So how does Bluetooth® advertise?

For ease of use, Bluetooth defines a single packet format for both advertising and data transmissions.  This packet consist of four components: preamble (1 octet), access address (4 octets), Protocol Data Unit – PDU (2-257 octets), and Cyclic Redundancy Check – CRC (3 octets); see Figure 1A.  

Link Layer Single Packet format and breakout of Advertising PDU

The PDU segment is important, as it defines whether this packet is an advertising or data packet.  For our discussion, we’ll focus on advertising PDUs (Figure 1B).

The Advertising PDU packet (Figure 2A) contains a 16 bit header and a variable size payload.

Advertising PDU header, specifically PDU type and Length.

The advertising header defines 6 segments.  We’ll focus on the Length and PDU Type fields/segments (Figure 2B).  The Length field is 6 bits and defines the size of the payload, i.e. how much stuff we can advertise (Figure 2A).  The Length may be between 6 – 37 octets and is defined by PDU Type

So great, we know we’re advertising, and have “x” number of octets for payload, but why are we advertising?  This is where the PDU Type comes in. In Bluetooth® low energy there are two reasons to advertise/broadcast:

  • To establish a bi-direction connection between devices (such as a smart watch to a phone). 
  • Or to broadcast information without ever connecting to another device, such as a beacon transmitting data in a museum telling you there is a 500 year old mummified body 5 feet behind you. 

So whether it’s the smart watch or a mummy vying for attention, we developers focus on 4 PDU Types (Figure 2B): 

    • Known as Advertising Indications (ADV_IND), where a peripheral device requests connection to any central device (i.e., not directed at a particular central device). 
    • Example:  A smart watch requesting connection to any central device.
    • Similar to ADV_IND, yet the connection request is directed at a specific central device. 
    • Example: A smart watch requesting connection to a specific central device.
    • Non connectable devices, advertising information to any listening device. 
    • Example:  Beacons in museums defining proximity to specific exhibits.
    • Similar to ADV_NONCONN_IND, with the option additional information via scan responses. 
    • Example:  A warehouse pallet beacon allowing a central device to request additional information about the pallet. 

So, when a long-term connection is desired, the PDU Type is set to either ADV_IND or ADV_DIRECT_IND, depending on whether the peripheral is advertising to any device or a specific device.  

And when broadcasting general data without establishing a long term connection, ADV_NONCONN_IND or ADV_SCAN_IND is the PDU Type of choice.  Typical beacons would use ADV_NONCONN_IND, and a peripheral allowing access to more information such as our warehouse pallet, ADV_SCAN_IND may be a better choice. 

Whether requesting a long term connection or broadcasting as an electronic beacon, it all starts with advertising. 

In our next post, we’ll discuss extended advertising features released in Bluetooth 5


Enhancing Bluetooth Location Services with Direction Finding

A new Bluetooth direction finding feature allows devices to determine the direction of a Bluetooth signal, thereby enabling the development of Bluetooth proximity solutions that can understand device direction as well as Bluetooth positioning systems that can achieve down to centimeter-level location accuracy.


Related Resources

Bluetooth® Core Specification Version 5.3 Feature Enhancements

Bluetooth® Core Specification version 5.3 includes several feature enhancements with the potential to improve…

Bluetooth 5.2新機能のポイントを10分で解説!(日本語字幕)

この動画では2020年1月に発表されたBluetoothバージョン5.2新機能の概要を中心に話します。Enhanced Attributeプロトコル(EATT)、LE Power Control (LEPC)、Isochronous (アイソクロナス)チャネルなど、これらの各機能について詳しく説明します。最後に、アイソクロナスチャネルを利用した「LE Audio」と呼ばれる次世代のBluetoothオーディオについて日本語翻訳付きで解説します。

Designing and Developing Bluetooth® Internet Gateways

Design and implement your own Bluetooth® Internet working prototype and see for yourself how BIGs allow applications to exchange data with Bluetooth devices from anywhere in the world.

An Introduction to Bluetooth Low Energy for Swift Developers

All smartphones support Bluetooth® Low Energy (LE) and it is used in all manner…

How Bluetooth Low Energy Works: 21 Interesting Facts

Whether you’re a beginner or an expert in Bluetooth Low Energy development, it’s always…

Bluetooth Security and Privacy Best Practices Guide

This guide is intended to help implementers better understand why certain available security and…

Advanced Bluetooth for Android Developers

Android developers can take this guided tour of the most recent features and interesting…

How to Deploy BlueZ on a Raspberry Pi Board as a Bluetooth Mesh Provisioner

This step-by-step study guide will teach you: How to rebuild the kernel on a…

Discussing Bluetooth Range

Watch Nordic address some of the most common myths concerning Bluetooth range, discuss the…

 Get Help