Services and characteristics in IOT Protocols - Step-by-Step Execution

Process Flow - Services and characteristics

Device starts advertising

↓

Central device scans and connects

↓

Discover services

↓

For each service

↓

Discover characteristics

↓

Read/Write/Notify characteristics

↓

Use data or control device

↓

Disconnect or continue communication

This flow shows how a central device connects to a peripheral, discovers its services and characteristics, then reads or writes data.

Execution Sample

IOT Protocols

1. Scan for devices
2. Connect to device
3. Discover services
4. Discover characteristics
5. Read characteristic value

Steps to connect to a BLE device and read a characteristic value.

Process Table

Step	Action	Result	Notes
1	Scan for devices	Found device with name 'Sensor1'	Device advertising with services
2	Connect to 'Sensor1'	Connection established	Ready to discover services
3	Discover services	Found service UUID 0x180F (Battery Service)	Service provides battery info
4	Discover characteristics of 0x180F	Found characteristic UUID 0x2A19 (Battery Level)	Characteristic holds battery percentage
5	Read characteristic 0x2A19	Value = 85	Battery level is 85%
6	Disconnect	Connection closed	End of session

💡 Disconnected after reading characteristic value

Status Tracker

Variable	Start	After Step 1	After Step 2	After Step 3	After Step 4	After Step 5	Final
device_found	null	'Sensor1'	'Sensor1'	'Sensor1'	'Sensor1'	'Sensor1'	null
connection_status	disconnected	disconnected	connected	connected	connected	connected	disconnected
services	empty	empty	empty	[0x180F]	[0x180F]	[0x180F]	[0x180F]
characteristics	empty	empty	empty	empty	[0x2A19]	[0x2A19]	[0x2A19]
characteristic_value	null	null	null	null	null	85	85

Key Moments - 3 Insights

Why do we need to discover services before characteristics?

Services group related characteristics. Discovering services first tells us what groups exist, so we know where to look for characteristics (see steps 3 and 4 in execution_table).

What does the characteristic value represent?

The characteristic value holds the actual data, like battery level 85% in step 5. Characteristics are like data points inside services.

Why disconnect after reading a characteristic?

After getting needed data, disconnecting frees resources and saves power, shown in step 6.

Visual Quiz - 3 Questions

Look at the execution table, what is the connection status after step 2?

A disconnected

B connected

C connecting

D unknown

💡 Hint

Check the 'connection_status' variable after step 2 in variable_tracker.

At which step is the battery level value read?

A Step 3

B Step 4

C Step 5

D Step 6

💡 Hint

Look at the 'Read characteristic' action in execution_table.

If the device did not advertise any services, what would happen at step 3?

A Services list would be empty

B Connection would fail

C Characteristics would be discovered anyway

D Device would disconnect immediately

💡 Hint

Refer to step 3 and the 'services' variable in variable_tracker.

Concept Snapshot

Services group related data points called characteristics.
Central device connects to peripheral, discovers services, then characteristics.
Characteristics hold actual data to read or write.
Discover services first, then characteristics.
Read/write characteristic values to interact with device.
Disconnect when done to save power.

Full Transcript

This visual execution shows how a central device connects to a Bluetooth Low Energy peripheral device. First, the central scans and finds a device named 'Sensor1'. Then it connects to it. After connection, it discovers the services the device offers, such as the Battery Service with UUID 0x180F. Next, it discovers characteristics inside that service, like the Battery Level characteristic with UUID 0x2A19. The central reads the battery level value, which is 85%. Finally, the connection is closed to save resources. Variables like connection status, services, characteristics, and characteristic values change step by step as shown. Key points include discovering services before characteristics, characteristics holding data, and disconnecting after use. The quiz questions help reinforce understanding of these steps.

Practice

1. What is the main role of a service in IoT protocols?

easy

A. To encrypt communication between devices

B. To store individual data values

C. To define the device's network address

D. To group related data and functions on a device

Solution

1. Step 1: Understand the concept of a service

   A service groups related data and functions on a device to organize them logically.

2. Step 2: Differentiate service from characteristics

   Characteristics are individual data pieces inside a service, not the grouping itself.

3. Final Answer:

   To group related data and functions on a device -> Option D

4. Quick Check:

   Service = Grouping data [OK]

Hint: Services group data; characteristics hold data values [OK]

Common Mistakes:

• Confusing services with characteristics
• Thinking services store single data values
• Mixing service role with network functions

2. Which of the following is the correct way to define a characteristic with read and write properties in a device configuration?

easy

A. characteristic: { uuid: '1234', properties: read; write }

B. characteristic: { uuid: '1234', properties: 'read, write' }

C. characteristic: { uuid: '1234', properties: ['read', 'write'] }

D. characteristic: { uuid: '1234', properties: read write }

Solution

1. Step 1: Check the syntax for properties list

   Properties should be an array of strings, e.g., ['read', 'write'].

2. Step 2: Identify correct syntax among options

   Only characteristic: { uuid: '1234', properties: ['read', 'write'] } uses an array with strings correctly; others use invalid formats.

3. Final Answer:

   characteristic: { uuid: '1234', properties: ['read', 'write'] } -> Option C

4. Quick Check:

   Properties as array of strings = characteristic: { uuid: '1234', properties: ['read', 'write'] } [OK]

Hint: Use array of strings for properties, not comma strings [OK]

Common Mistakes:

• Using comma-separated string instead of array
• Omitting quotes around property names
• Using invalid separators like semicolons

3. Given this code snippet for a device service:

service = {
  uuid: 'abcd',
  characteristics: [
    { uuid: '1234', properties: ['read'] },
    { uuid: '5678', properties: ['write'] }
  ]
}
console.log(service.characteristics[1].properties.includes('write'))

What will be the output?

medium

A. false

B. true

C. undefined

D. Error

Solution

1. Step 1: Access the second characteristic's properties

   service.characteristics[1] refers to the characteristic with uuid '5678'.

2. Step 2: Check if 'write' is included in properties

   Its properties array is ['write'], so includes('write') returns true.

3. Final Answer:

   true -> Option B

4. Quick Check:

   Includes 'write' = true [OK]

Hint: Check array index and use includes() to verify property [OK]

Common Mistakes:

• Confusing index 0 and 1 in array
• Assuming includes returns false for single-item arrays
• Expecting an error due to property access

4. You have this characteristic definition:

{ uuid: 'abcd', properties: ['read', 'notify'] }

But notifications are not working on your device. What is the most likely mistake?

medium

A. The 'notify' property is misspelled or unsupported

B. The characteristic is missing the 'write' property

C. The service UUID is incorrect

D. The characteristic UUID is too short

Solution

1. Step 1: Verify the 'notify' property spelling and support

   Notifications require the 'notify' property spelled exactly and supported by device.

2. Step 2: Check other options for relevance

   Missing 'write' does not affect notifications; UUID length or service UUID unrelated.

3. Final Answer:

   The 'notify' property is misspelled or unsupported -> Option A

4. Quick Check:

   Notification needs correct 'notify' property [OK]

Hint: Check spelling and support of 'notify' property first [OK]

Common Mistakes:

• Assuming 'write' is needed for notifications
• Blaming UUID length without evidence
• Ignoring property spelling errors

5. You want to create a service with two characteristics: one readable temperature and one writable threshold. Which configuration correctly represents this?

hard

A. service: { uuid: 'temp', characteristics: [ { uuid: 'temp1', properties: ['read'] }, { uuid: 'thresh1', properties: ['write'] } ] }

B. service: { uuid: 'temp', characteristics: [ { uuid: 'temp1', properties: 'read' }, { uuid: 'thresh1', properties: 'write' } ] }

C. service: { uuid: 'temp', characteristics: [ { uuid: 'temp1', properties: ['write'] }, { uuid: 'thresh1', properties: ['read'] } ] }

D. service: { uuid: 'temp', characteristics: [ { uuid: 'temp1', properties: ['read', 'write'] }, { uuid: 'thresh1', properties: [] } ] }

Solution

1. Step 1: Identify required properties for each characteristic

   Temperature characteristic must be readable only; threshold must be writable only.

2. Step 2: Check each option's properties array

   service: { uuid: 'temp', characteristics: [ { uuid: 'temp1', properties: ['read'] }, { uuid: 'thresh1', properties: ['write'] } ] } correctly assigns ['read'] to temperature and ['write'] to threshold.

3. Final Answer:

   service: { uuid: 'temp', characteristics: [ { uuid: 'temp1', properties: ['read'] }, { uuid: 'thresh1', properties: ['write'] } ] } -> Option A

4. Quick Check:

   Correct properties arrays for read and write [OK]

Hint: Match properties array exactly to read or write need [OK]

Common Mistakes:

• Using string instead of array for properties
• Swapping read and write properties
• Leaving properties empty when needed