Why BLE advertising and scanning in IOT Protocols? - Purpose & Use Cases

The Big Idea

What if your devices could find each other effortlessly without you lifting a finger?

The Scenario

Imagine you want to find your friends in a crowded park by shouting their names repeatedly and hoping they hear you.

Or you try to listen carefully to every shout around you to find if someone is calling your name.

The Problem

Shouting names manually is tiring and slow, and you might miss your friends if you are not paying attention.

Listening to all shouts at once is confusing and easy to miss important calls.

This manual way wastes energy and causes delays.

The Solution

BLE advertising and scanning automate this process by letting devices broadcast small messages (advertising) and others listen for these messages (scanning) efficiently.

This way, devices find each other quickly without shouting or constant listening, saving energy and time.

Before vs After

✗ Before

Manually shout name repeatedly
Manually listen for shouts

✓ After

Device broadcasts BLE advertisement packets
Device scans and filters for specific BLE advertisements

What It Enables

Devices can discover and connect to each other quickly and efficiently without wasting battery or missing important signals.

Real Life Example

Your fitness tracker automatically finds your smartphone nearby by scanning for its BLE advertisements, so it can sync your health data seamlessly.

Key Takeaways

Manual searching for devices is slow and unreliable.

BLE advertising and scanning automate discovery with low energy use.

This enables fast, reliable connections between devices in everyday life.

Practice

1. What is the main purpose of BLE advertising in Bluetooth Low Energy communication?

easy

A. To broadcast small packets of data repeatedly to nearby devices

B. To establish a full connection between devices

C. To encrypt data between devices

D. To scan for other devices' signals

Solution

1. Step 1: Understand BLE advertising role

   BLE advertising sends small data packets repeatedly to announce presence.

2. Step 2: Differentiate from scanning and connection

   Advertising is broadcasting, not scanning or connecting.

3. Final Answer:

   To broadcast small packets of data repeatedly to nearby devices -> Option A

4. Quick Check:

   Advertising = broadcast small data [OK]

Hint: Advertising means sending out info repeatedly [OK]

Common Mistakes:

• Confusing advertising with scanning
• Thinking advertising establishes connections
• Assuming advertising encrypts data

2. Which of the following is the correct command to start BLE scanning using the Linux tool bluetoothctl?

easy

A. ble scan start

B. start scan

C. scan start

D. scan on

Solution

1. Step 1: Recall bluetoothctl scan command

   The correct command to start scanning is exactly scan on.

2. Step 2: Check other options for syntax

   Other options are incorrect commands or invalid syntax in bluetoothctl.

3. Final Answer:

   scan on -> Option D

4. Quick Check:

   bluetoothctl scan on = start scanning [OK]

Hint: Use exact command 'scan on' in bluetoothctl [OK]

Common Mistakes:

• Using 'start scan' instead of 'scan on'
• Typing commands not supported by bluetoothctl
• Confusing scan commands with advertising commands

3. Given this Python snippet using a BLE library to scan devices:

devices = scanner.scan(5.0)
for dev in devices:
    print(dev.addr)

What will this code output?

medium

A. Empty list because scan time is too short

B. List of device addresses found during 5 seconds scan

C. Error because scan() needs no arguments

D. List of device names found during 5 seconds scan

Solution

1. Step 1: Understand scan() usage with timeout

   The scan method scans for devices for given seconds and returns device objects.

2. Step 2: Identify printed attribute

   Printing dev.addr outputs device MAC addresses found.

3. Final Answer:

   List of device addresses found during 5 seconds scan -> Option B

4. Quick Check:

   scan(5.0) returns devices; dev.addr prints addresses [OK]

Hint: scan(timeout) returns devices; print dev.addr for addresses [OK]

Common Mistakes:

• Thinking scan() takes no arguments
• Confusing device address with device name
• Assuming scan always returns empty list

4. You wrote this code to scan BLE devices but get no output:

scanner = Scanner()
devices = scanner.scan()
for dev in devices:
    print(dev.addr)

What is the likely problem?

medium

A. print(dev.addr) is incorrect attribute

B. Scanner() class does not exist

C. Missing scan timeout argument causes no devices found

D. scan() method should be called with 'start' keyword

Solution

1. Step 1: Check scan() method requirements

   scan() requires a timeout argument to specify scan duration.

2. Step 2: Understand effect of missing timeout

   Without timeout, scan may return immediately with no devices.

3. Final Answer:

   Missing scan timeout argument causes no devices found -> Option C

4. Quick Check:

   scan() needs timeout to find devices [OK]

Hint: Always provide scan timeout to get results [OK]

Common Mistakes:

• Omitting scan timeout argument
• Assuming dev.addr is invalid
• Thinking scan() uses 'start' keyword

5. You want to filter BLE scan results to only show devices advertising a specific service UUID. Which approach correctly applies this filter in Python?

hard

A. Use a list comprehension: [dev for dev in devices if '1234' in dev.getScanData()]

B. Check if '1234' in dev.addr for each device

C. Filter devices by comparing dev.name to '1234'

D. Use devices.filter('1234') method directly

Solution

1. Step 1: Understand filtering by service UUID

   Service UUIDs appear in scan data, not in address or name.

2. Step 2: Use list comprehension with getScanData()

   getScanData() returns advertised data; check if UUID '1234' is present.

3. Final Answer:

   Use a list comprehension: [dev for dev in devices if '1234' in dev.getScanData()] -> Option A

4. Quick Check:

   Filter by UUID in scan data using list comprehension [OK]

Hint: Filter devices by checking UUID in scan data list [OK]

Common Mistakes:

• Checking UUID in device address
• Filtering by device name instead of UUID
• Using non-existent filter() method on devices