: The official Linux Bluetooth stack used in most distributions and Raspberry Pi systems.
: This is the "lower layer" that handles the hardware-heavy, time-critical tasks. It includes the Physical Layer (PHY) , which manages the actual 2.4 GHz radio signals, and the Link Layer , which handles packet formatting, encryption, and data synchronization.
A complete Bluetooth system is typically divided into three primary components:
: Resides in the main operating system (e.g., Android, Linux) and handles higher-level protocols and connection tracking. bluetooth stack
The story of the "Bluetooth stack" is an epic of engineering that spans from Viking kings to modern-day cybersecurity battles. It is the invisible "brain" inside your devices that manages every wireless handshake. 1. The Name: Uniting a Divided World The term "Bluetooth" wasn’t born in a lab; it was inspired by King Harald "Bluetooth" Gormsson , a 10th-century monarch who united the warring tribes of Denmark and Norway. In the 1990s, when tech giants like Intel, Ericsson, and Nokia were building competing, incompatible wireless standards, engineers proposed the name as a placeholder. Just as the king united Scandinavia, this technology was meant to unite PC and cellular industries. 2. The Stack: A Layered Masterpiece A Bluetooth stack is a set of software protocols that act like a digital translator. It is structured in layers, similar to the OSI network model : The Bottom (Controller Layer): Handles the raw radio waves and physical timing. The Middle (Host Layer): Manages the logic, like how to pair a device or discover services (SDP). The Top (Application Layer): This is what you interact with, such as an audio profile (A2DP) for your headphones or a heart rate monitor profile. 3. The Great Migrations (BlueZ vs. Fluoride) The "stack" isn't a single thing; different operating systems use different implementations: Linux/ChromeOS: Traditionally used
This is the actual radio hardware that transmits and receives analog signals on the 2.4 GHz ISM band. It handles the modulation (turning digital bits into radio waves) and demodulation.
This layer manages the state of the connection. It controls advertising (broadcasting presence to other devices), scanning (looking for advertisers), and creating/maintaining connections. It handles the low-level timing and frequency hopping, which ensures Bluetooth is resistant to interference from Wi-Fi or microwaves. : The official Linux Bluetooth stack used in
The HCI is the boundary layer. It standardizes how the software (Host) talks to the hardware (Controller). In a smartphone, this might be a physical connection like UART or USB; in a standalone device, it is often internal logic. The HCI allows developers to write software without needing to know the specific details of the radio chip being used.
Crucial for modern Bluetooth Low Energy (BLE) devices, GATT defines how data is organized. It structures data into "Services" and "Characteristics." For example, a heart rate monitor has a "Heart Rate Service," and the actual heart rate number is a "Characteristic" within that service.
L2CAP acts as the traffic cop for the upper layers. It takes large data packets from the applications above and chops them into smaller packets that the lower layers can send. It also handles multiplexing, allowing multiple services (like audio and data transfer) to share a single Bluetooth connection simultaneously. A complete Bluetooth system is typically divided into
Kai frowned. “So one bad layer breaks the whole stack?”
The Bluetooth specification divides the stack into two primary components, often separated into different physical or logical chips: