GATT profile architecture in IOT Protocols - Step-by-Step Execution

Process Flow - GATT profile architecture

Start: Device connects

↓

Discover GATT Profile

↓

Find Services

↓

Find Characteristics

↓

Read/Write/Notify Characteristics

↓

End Communication

This flow shows how a device connects, discovers the GATT profile, finds services and characteristics, then reads or writes data.

Execution Sample

IOT Protocols

Connect to device
Discover GATT profile
Find Heart Rate Service
Read Heart Rate Measurement characteristic
Receive notification

This sequence shows a device connecting and interacting with a Heart Rate service using GATT profile.

Process Table

Step	Action	GATT Component	Result
1	Connect to device	N/A	Connection established
2	Discover GATT profile	Profile	Profile found with services
3	Find Heart Rate Service	Service	Service UUID 0x180D found
4	Find Heart Rate Measurement characteristic	Characteristic	Characteristic UUID 0x2A37 found
5	Read Heart Rate Measurement	Characteristic Value	Value read: 72 bpm
6	Enable notifications	Characteristic	Notifications enabled
7	Receive notification	Characteristic Value	Notification received: 75 bpm
8	End communication	N/A	Disconnected

💡 Communication ends after disconnection

Status Tracker

Variable	Start	After Step 2	After Step 3	After Step 4	After Step 5	After Step 7	Final
Connection Status	Disconnected	Connected	Connected	Connected	Connected	Connected	Disconnected
Profile Discovered	No	Yes	Yes	Yes	Yes	Yes	No
Service Found	No	No	Yes	Yes	Yes	Yes	No
Characteristic Found	No	No	No	Yes	Yes	Yes	No
Characteristic Value	N/A	N/A	N/A	N/A	72 bpm	75 bpm	N/A
Notifications Enabled	No	No	No	No	No	Yes	No

Key Moments - 3 Insights

Why do we need to discover the GATT profile before reading data?

Discovering the GATT profile (Step 2) tells us what services and characteristics the device offers, so we know what data we can read or write.

What is the difference between a service and a characteristic?

A service (Step 3) groups related data, while a characteristic (Step 4) is a single data point you can read or write, like the heart rate measurement.

Why enable notifications after reading a characteristic?

Reading gives one value (Step 5), but enabling notifications (Step 6) lets the device send updates automatically (Step 7) without asking each time.

Visual Quiz - 3 Questions

Look at the execution table, what is the characteristic value read at Step 5?

A 72 bpm

B 75 bpm

C 0x180D

D Disconnected

💡 Hint

Check the 'Characteristic Value' column at Step 5 in the execution table.

At which step does the device enable notifications for updates?

A Step 4

B Step 7

C Step 6

D Step 8

💡 Hint

Look for the action 'Enable notifications' in the execution table.

If the device never discovers the GATT profile, what happens to the connection status?

A Changes to Connected

B Remains Disconnected

C Changes to Notifications Enabled

D Changes to Service Found

💡 Hint

Check variable 'Connection Status' after Step 2 in variable tracker.

Concept Snapshot

GATT profile architecture:
- Device connects and discovers GATT profile
- Profile contains services (group data)
- Services contain characteristics (data points)
- Read/write or enable notifications on characteristics
- Notifications send updates automatically
- Communication ends on disconnect

Full Transcript

The GATT profile architecture starts when a device connects to another device. It discovers the GATT profile to learn what services and characteristics are available. Services group related data, and characteristics are individual data points you can read or write. For example, the Heart Rate service has a characteristic for heart rate measurement. The device reads this characteristic to get a value like 72 bpm. It can also enable notifications to receive updates automatically, such as when the heart rate changes. Finally, the communication ends when the device disconnects.

Practice

1. What is the main purpose of the GATT profile architecture in Bluetooth Low Energy (BLE)?

easy

A. To encrypt data during Bluetooth transmission

B. To increase the Bluetooth signal strength between devices

C. To manage device battery usage during Bluetooth communication

D. To organize data into profiles, services, characteristics, and descriptors for clear communication

Solution

1. Step 1: Understand GATT architecture purpose

   The GATT profile architecture structures data into profiles, services, characteristics, and descriptors to organize communication.

2. Step 2: Compare with other options

   Options A, B, and D describe other Bluetooth features but not the main purpose of GATT architecture.

3. Final Answer:

   To organize data into profiles, services, characteristics, and descriptors for clear communication -> Option D

4. Quick Check:

   GATT architecture = Organize data clearly [OK]

Hint: Remember GATT structures data for clear device communication [OK]

Common Mistakes:

• Confusing GATT with Bluetooth signal or encryption features
• Thinking GATT manages battery usage
• Mixing GATT with lower-level radio functions

2. Which of the following correctly represents the hierarchy in GATT profile architecture from highest to lowest level?

easy

A. Service > Profile > Characteristic > Descriptor

B. Characteristic > Service > Profile > Descriptor

C. Profile > Service > Characteristic > Descriptor

D. Descriptor > Characteristic > Service > Profile

Solution

1. Step 1: Recall GATT hierarchy order

   The correct order is Profile at the top, then Service, followed by Characteristic, and Descriptor at the bottom.

2. Step 2: Match options with hierarchy

   Profile > Service > Characteristic > Descriptor matches this order exactly; others have incorrect sequences.

3. Final Answer:

   Profile > Service > Characteristic > Descriptor -> Option C

4. Quick Check:

   Hierarchy order = Profile > Service > Characteristic > Descriptor [OK]

Hint: Profile contains services, services contain characteristics, characteristics have descriptors [OK]

Common Mistakes:

• Mixing up the order of profile and service
• Confusing characteristics with descriptors
• Reversing the hierarchy levels

3. Given a BLE device with a GATT profile containing a Heart Rate Service (UUID 0x180D) and a Heart Rate Measurement characteristic (UUID 0x2A37), what will the device send when the heart rate changes?

medium

A. A profile change event to the connected device

B. A notification containing the new heart rate value from the Heart Rate Measurement characteristic

C. A descriptor update with the heart rate value

D. A new service registration with updated UUID

Solution

1. Step 1: Identify characteristic role

   The Heart Rate Measurement characteristic sends updated heart rate data via notifications.

2. Step 2: Understand BLE data flow

   Services and profiles define structure but do not send data directly; descriptors provide metadata, not values.

3. Final Answer:

   A notification containing the new heart rate value from the Heart Rate Measurement characteristic -> Option B

4. Quick Check:

   Characteristic sends data notifications [OK]

Hint: Characteristics send data updates via notifications [OK]

Common Mistakes:

• Confusing descriptors with data carriers
• Thinking services send data directly
• Assuming profile changes on data update

4. A developer tries to add a characteristic directly under a profile without defining a service first. What is the likely issue?

medium

A. The characteristic will not be recognized because characteristics must belong to a service

B. The profile will automatically create a default service for the characteristic

C. The characteristic will work but descriptors will fail

D. The BLE device will crash due to invalid hierarchy

Solution

1. Step 1: Understand GATT hierarchy rules

   Characteristics must be part of a service; profiles contain services, not characteristics directly.

2. Step 2: Analyze consequences of skipping service

   Without a service, the characteristic is invalid and won't be recognized by BLE clients.

3. Final Answer:

   The characteristic will not be recognized because characteristics must belong to a service -> Option A

4. Quick Check:

   Characteristic requires service parent [OK]

Hint: Characteristics must be inside services, never directly under profiles [OK]

Common Mistakes:

• Assuming profiles can contain characteristics directly
• Expecting automatic service creation
• Believing device crashes on hierarchy errors

5. You want to design a BLE device that measures temperature and humidity. Which GATT profile architecture setup is best to organize these measurements for easy client access?

hard

A. Create one profile with two services: Temperature Service and Humidity Service, each with their own measurement characteristic

B. Create one profile with one service containing both temperature and humidity characteristics

C. Create two profiles: one for temperature and one for humidity, each with one service and characteristic

D. Create one service with one characteristic that alternates between temperature and humidity values

Solution

1. Step 1: Consider GATT design best practices

   Grouping related measurements under separate services for temperature and humidity allows clear separation and easier client handling.

2. Step 2: Evaluate options for clarity and efficiency

   Creating one profile with two services, each with their own characteristic, is a common and clear design pattern for distinct sensor types.

3. Final Answer:

   Create one profile with two services: Temperature Service and Humidity Service, each with their own measurement characteristic -> Option A

4. Quick Check:

   Separate services for distinct sensor types [OK]

Hint: Use separate services for distinct sensor measurements [OK]

Common Mistakes:

• Creating multiple profiles unnecessarily
• Using one characteristic for multiple data types
• Grouping unrelated data into one service