RF Wireless World

Browse articles, tutorials, tools, and vendors.

Bluetooth Routing: How Devices Know a Packet is for Them

By RF Wireless Expert Team

Introduction : Imagine standing in a crowded, noisy room where dozens of people are shouting in different languages. How do you know when someone is specifically talking to you? Bluetooth devices face this exact “cocktail party problem” every second. In the 2.4 GHz spectrum, your smartphone’s Bluetooth chip is targetted by Wi-Fi signals, microwave radiation and packets from other people’s Bluetooth headphones, smartwatches and cars.

To filter out the noise and figure out if a microscopic packet of data is actually meant for it, a Bluetooth device uses a highly efficient, two step verification process using The Access Code (verifying the network) and the LT_ADDR (verifying the specific device).

Let us explore how a device decides to accept or ignore a packet.

Step 1: The Access Code (“Are you in my network?”)

Before a Bluetooth device even looks at the data inside a packet, it looks at the very first sequence of bits transmitted over the air i.e. Access Code.

When Bluetooth devices pair and connect, they form a mini network called a piconet. One device acts as the Central (e.g. your smartphone) and the others act as Peripherals (e.g. your smartwatch and wireless earbuds).

  • The Sync Word: The Access Code is mathematically derived from the Central device’s unique Bluetooth MAC Address (specifically, the Lower Address Part or LAP). Because every Central has a different MAC address, every piconet has a unique Access Code.
  • The Hardware Filter: The receiving chip in your wireless earbuds has a hardware “correlator” that constantly scans the airwaves. It is hard coded to look only for the Access Code of the smartphone it is connected to.
  • The Result: If a packet flies by from a stranger’s phone, the Access Code won’t match. The earbud’s radio chip instantly ignores it at the hardware level and goes back to sleep.

Step 2: The LT_ADDR (“Is this specifically for me ?”)

Once the device confirms the packet belongs to its piconet (because the Access Code matched), it wakes up to read the Packet Header.

A single Central device can juggle active connections with up to seven Peripherals at the same time. To keep them straight, the Central assigns a temporary “name tag” to each Peripheral when they connect. This is called the Logical Transport Address (LT_ADDR).

  • The 3 Bit Rule: The LT_ADDR is a tiny 3-bit field located right at the beginning of the packet header.
  • Values 1 through 7: If your smartphone (the Central) wants to send a music packet to your right earbud, it puts the right earbud’s assigned LT_ADDR (let’s say, 001) in the header. The earbud reads the header, sees 001, and says, “This is for me!” and processes the audio payload.
  • Ignoring Others: If the smartwatch (which was assigned LT_ADDR 010) reads that same packet, it sees 001, realizes the packet is meant for the earbud, and immediately discards it to save battery.

Step 3: The Broadcast Exception (“Attention Everyone!”)

What if the Central wants to send a message to all connected Peripherals at the same time like a network configuration update ?

Bluetooth reserves a special LT_ADDR value of exactly zero (000) for broadcasts. If a Peripheral reads a packet header and sees an LT_ADDR of 000, it knows this is an Active Peripheral Broadcast (APB). Every active Peripheral in the piconet will accept and process this packet, knowing it is a public announcement rather than a private message.

Summary: The Reverse Direction (Peripheral to Central)

We know how a Peripheral identifies its packets, but how does the Central know which Peripheral is talking to it?

Bluetooth uses a strict turn taking system called Time Division Duplexing (TDD). A Peripheral is only allowed to transmit a packet in the exact time slot immediately following a packet addressed to it by the Central.

Because the Central dictates the schedule, if it sends a request to LT_ADDR 001 (the earbud) in Slot 1, it knows with absolute certainty that whatever packet arrives in Slot 2 is the reply from the earbud.

By combining unique network Access Codes, specific 3-bit device addresses, and strict time-slot scheduling, Bluetooth devices can flawlessly pick their data out of thin air, no matter how noisy the environment gets.

References & Further Reading

  1. Bluetooth SIG : Bluetooth Core Specification Version 6.3, May 5, 2026.
  2. Bluetooth SIG : Bluetooth Core Specification change history
  3. Bluetooth SIG : Bluetooth Technology Overview

Continue Learning Bluetooth Basic Concepts

Continue Learning Bluetooth Technology

Compare Bluetooth With Other Technologies

Explore Deep Insight Bluetooth Technology

Keep Reading

Related Posts