Topics and topic hierarchy in IOT Protocols - Full Explanation

Introduction

Imagine you want to send messages to different groups of people based on their interests. Without a clear way to organize these groups, messages would get lost or sent to the wrong people. Topics and topic hierarchy solve this by organizing messages so they reach the right receivers efficiently.

Explanation

What is a Topic

A topic is like a label or a category name that messages are sent to or received from. It helps organize messages by subject so devices or applications can subscribe only to the topics they care about. Topics are simple text strings that describe the message content area.

A topic is a named channel that organizes messages by subject.

Topic Hierarchy Structure

Topics can be arranged in a hierarchy using slashes to separate levels, like folders in a file system. This allows grouping related topics under a common parent topic. For example, 'home/kitchen/temperature' and 'home/livingroom/temperature' share the 'home' parent topic.

Topic hierarchy organizes topics in levels separated by slashes for better grouping.

Wildcards in Topic Subscription

Wildcards let subscribers listen to multiple topics at once without listing each one. The single-level wildcard '+' matches one level in the hierarchy, while the multi-level wildcard '#' matches all remaining levels. This makes it easy to subscribe broadly or narrowly.

Wildcards allow flexible subscription to multiple topics in a hierarchy.

Benefits of Topic Hierarchy

Using a topic hierarchy helps keep messages organized and reduces unnecessary data traffic. Devices only receive messages relevant to their subscribed topics, improving efficiency and clarity in communication. It also simplifies managing large numbers of topics.

Topic hierarchy improves message organization and communication efficiency.

Real World Analogy

Think of a large library where books are organized by sections, shelves, and categories. If you want a book about cooking, you go to the 'Cooking' section, then to a specific shelf like 'Baking'. This way, you find books quickly without searching the entire library.

What is a Topic → A book section label like 'Cooking' that groups related books

Topic Hierarchy Structure → Shelves and subcategories within the library section, like 'Baking' under 'Cooking'

Wildcards in Topic Subscription → Choosing to browse all shelves in 'Cooking' or just one specific shelf

Benefits of Topic Hierarchy → Finding books faster and avoiding looking through unrelated sections

Diagram

Diagram

┌─────────┐
│  home   │
├─────────┤
│ kitchen │
│  │      │
│  ├─temperature
│  └─humidity
├─────────┤
│livingroom│
│  ├─temperature
│  └─humidity
└─────────┘

This diagram shows a topic hierarchy with 'home' as the root, branching into 'kitchen' and 'livingroom', each having 'temperature' and 'humidity' topics.

Key Facts

Topic → A named string that categorizes messages for sending and receiving.

Topic Hierarchy → A structure of topics separated by slashes to organize messages in levels.

Single-level Wildcard (+) → A symbol that matches exactly one level in a topic hierarchy.

Multi-level Wildcard (#) → A symbol that matches any number of levels in a topic hierarchy.

Subscription → The act of registering to receive messages from specific topics.

Common Confusions

Believing topics are like message contents rather than labels.

Believing topics are like message contents rather than labels. Topics are labels or addresses for messages, not the message content itself.

Thinking wildcards can be used anywhere in the topic string.

Thinking wildcards can be used anywhere in the topic string. Wildcards must follow specific rules: '+' replaces one level, '#' must be last and replaces all remaining levels.

Assuming topic hierarchy is mandatory for all messaging.

Assuming topic hierarchy is mandatory for all messaging. Topic hierarchy is a helpful convention but not always required; simple flat topics can also be used.

Summary

Topics are named labels that organize messages by subject for sending and receiving.

Topic hierarchy uses slashes to create levels, grouping related topics like folders.

Wildcards '+' and '#' let subscribers listen to multiple topics flexibly within the hierarchy.

Practice

1. What is the main purpose of topics in IoT protocols like MQTT?

easy

A. To encrypt messages for security

B. To store device firmware

C. To organize messages in a clear, folder-like structure

D. To control device power settings

Solution

1. Step 1: Understand the role of topics

   Topics act like folders to organize messages so devices know where to send or receive data.

2. Step 2: Compare options with topic function

   Only organizing messages matches the purpose of topics; encryption and firmware storage are unrelated.

3. Final Answer:

   To organize messages in a clear, folder-like structure -> Option C

4. Quick Check:

   Topics organize messages = B [OK]

Hint: Topics are like folders for messages [OK]

Common Mistakes:

• Confusing topics with security features
• Thinking topics store device data
• Mixing topics with device settings

2. Which of the following is the correct way to write a topic with three levels?

easy

A. home-kitchen-temperature

B. home.kitchen.temperature

C. home\kitchen\temperature

D. home/kitchen/temperature

Solution

1. Step 1: Recall topic level separator

   Topics use slashes (/) to separate levels, like folders in a path.

2. Step 2: Check each option's separator

   Only home/kitchen/temperature uses slashes correctly; others use dots, backslashes, or dashes which are incorrect.

3. Final Answer:

   home/kitchen/temperature -> Option D

4. Quick Check:

   Topic levels separated by '/' = A [OK]

Hint: Use slashes (/) to separate topic levels [OK]

Common Mistakes:

• Using dots instead of slashes
• Using backslashes which are invalid
• Using dashes instead of separators

3. Given the topic building1/floor2/room3/sensor, which part represents the third level?

medium

A. room3

B. floor2

C. building1

D. sensor

Solution

1. Step 1: Split the topic by slashes

   Splitting 'building1/floor2/room3/sensor' by '/' gives ['building1', 'floor2', 'room3', 'sensor'].

2. Step 2: Identify the third element

   The third element (index 2) is 'room3'.

3. Final Answer:

   room3 -> Option A

4. Quick Check:

   Third level = room3 = C [OK]

Hint: Count levels separated by '/' to find position [OK]

Common Mistakes:

• Counting from zero incorrectly
• Choosing first or second level by mistake
• Confusing last level with third

4. Identify the error in this topic string: home//livingroom/temperature

medium

A. Double slash creates an empty level

B. Missing slash between 'home' and 'livingroom'

C. Topic levels must use dots, not slashes

D. Topic cannot contain the word 'temperature'

Solution

1. Step 1: Analyze the topic string

   The string 'home//livingroom/temperature' has two slashes together, meaning an empty level between them.

2. Step 2: Understand topic level rules

   Empty levels are invalid because each level should have a name; double slashes cause this error.

3. Final Answer:

   Double slash creates an empty level -> Option A

4. Quick Check:

   Double slash = empty level error = A [OK]

Hint: Avoid double slashes to prevent empty topic levels [OK]

Common Mistakes:

• Ignoring empty levels caused by double slashes
• Thinking dots are required separators
• Believing certain words are forbidden in topics

5. You want to subscribe to all sensors in any room on floor 1 of building 2 using MQTT topics. Which subscription topic should you use?

hard

A. building2/floor1/*/sensor

B. building2/floor1/+/sensor

C. building2/floor1/room1/sensor

D. building2/floor1/#/sensor

Solution

1. Step 1: Understand MQTT wildcards

   The '+' wildcard matches exactly one level, while '#' matches all remaining levels.

2. Step 2: Analyze the subscription needs

   We want any room on floor1, so '+' replaces the room level. '#' would match too many levels, and '*' is invalid in MQTT.

3. Final Answer:

   building2/floor1/+/sensor -> Option B

4. Quick Check:

   '+' wildcard for one level = D [OK]

Hint: Use '+' for single-level wildcard in MQTT topics [OK]

Common Mistakes:

• Using '#' when only one level is needed
• Using '*' which is not a valid MQTT wildcard
• Specifying exact room instead of wildcard