GATT profile architecture in IOT Protocols - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Understanding GATT Profile Roles

In the GATT profile architecture, which device role is responsible for initiating requests and controlling the data exchange?

A Client

B Peripheral

C Server

D Broadcaster

💡 Hint

Think about which device asks for data in a conversation.

The Client initiates requests and controls data exchange by querying the Server. The Server responds to these requests.

💻 Command Output

intermediate

GATT Service Discovery Output

What is the expected output when a GATT client successfully discovers a primary service with UUID 0x180D (Heart Rate) on a server?

IOT Protocols

gatt-client> discover-primary-services 0x180D
Service found: UUID=0x180D, Start Handle=0x0001, End Handle=0x0005

A Syntax error: unknown command

B Error: Service 0x180D not found

C Service found: UUID=0x180A, Start Handle=0x0001, End Handle=0x0005

D Service found: UUID=0x180D, Start Handle=0x0001, End Handle=0x0005

💡 Hint

Look for the exact UUID 0x180D in the output.

The output confirms discovery of the Heart Rate service with UUID 0x180D and its handle range.

❓ Configuration

advanced

Configuring a GATT Server Characteristic

Which configuration snippet correctly defines a GATT characteristic with UUID 0x2A37 (Heart Rate Measurement) that supports notifications?

A

[Characteristic]
UUID=0x2A37
Properties=Notify
Value=0x00

B

[Characteristic]
UUID=0x2A37
Properties=Read
Value=0x00

C

[Characteristic]
UUID=0x2A37
Properties=Write
Value=0x00

D

[Characteristic]
UUID=0x2A37
Properties=Indicate
Value=0x00

💡 Hint

Notifications allow the server to send updates without client requests.

The characteristic must have the Notify property to support notifications. Other properties do not enable notifications.

❓ Troubleshoot

advanced

Troubleshooting GATT Connection Failure

A GATT client fails to connect to a server device. Which of the following is the most likely cause?

A The server device is advertising with a different UUID than the client expects

B The client device has no Bluetooth adapter installed

C The server device is within range and advertising correctly

D The client device has a fully charged battery

💡 Hint

Think about hardware requirements for Bluetooth communication.

If the client device lacks a Bluetooth adapter, it cannot connect to any server device.

🔀 Workflow

expert

Correct Sequence for GATT Data Exchange

What is the correct order of steps for a GATT client to read a characteristic value from a server?

A 2,1,4,3

B 4,2,1,3

C 4,1,2,3

D 1,4,2,3

💡 Hint

Remember that connection must happen before discovery.

The client must first connect, then discover services, then characteristics, and finally read the value.

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