Rule engine for IoT data routing in IOT Protocols - Step-by-Step Execution

Process Flow - Rule engine for IoT data routing

Receive IoT Data

↓

Evaluate Rules

↓

Match Rule?

No→Discard or Store

Yes↓

Route Data to Target

↓

Log or Notify

Data from IoT devices is received, checked against routing rules, and then sent to the correct destination if a rule matches.

Execution Sample

IOT Protocols

data = {'temp': 30, 'humidity': 70}
rules = [{'condition': lambda d: d['temp'] > 25, 'target': 'cooling_system'}]
route = None
for rule in rules:
  if rule['condition'](data):
    route = rule['target']

This code checks if temperature is above 25 and routes data to the cooling system if true.

Process Table

Step	Action	Data State	Rule Condition Result	Routing Decision
1	Receive data	{'temp': 30, 'humidity': 70}	N/A	N/A
2	Evaluate rule condition	{'temp': 30, 'humidity': 70}	True (30 > 25)	Route to cooling_system
3	Route data	{'temp': 30, 'humidity': 70}	True	Data sent to cooling_system
4	End	{'temp': 30, 'humidity': 70}	N/A	Routing complete

💡 All rules evaluated; data routed based on matching condition.

Status Tracker

Variable	Start	After Step 1	After Step 2	After Step 3	Final
data	{}	{'temp': 30, 'humidity': 70}	{'temp': 30, 'humidity': 70}	{'temp': 30, 'humidity': 70}	{'temp': 30, 'humidity': 70}
rule	N/A	N/A	{'condition': lambda, 'target': 'cooling_system'}	{'condition': lambda, 'target': 'cooling_system'}	{'condition': lambda, 'target': 'cooling_system'}
route	None	None	cooling_system	cooling_system	cooling_system

Key Moments - 2 Insights

Why does the routing decision happen only after the rule condition is True?

Because the engine checks each rule's condition against the data; only when the condition is True (see Step 2 in execution_table) does it decide where to send the data.

What happens if no rule matches the data?

If no rule condition is True, the data is either discarded or stored for later (not shown in this example), as indicated by the 'No' branch in the concept_flow.

Visual Quiz - 3 Questions

Look at the execution_table at Step 2, what is the result of the rule condition?

A Error evaluating condition

B False (30 < 25)

C True (30 > 25)

D Condition not checked

💡 Hint

Check the 'Rule Condition Result' column at Step 2 in the execution_table.

At which step is the data routed to the target?

A Step 1

B Step 3

C Step 2

D Step 4

💡 Hint

Look at the 'Routing Decision' column to find when data is sent.

If the temperature was 20 instead of 30, what would happen in Step 2?

A Rule condition would be False

B Rule condition would be True

C Data would be routed to cooling_system anyway

D Execution would stop with error

💡 Hint

Refer to the condition 'temp > 25' and how it evaluates with 20 in the execution_table.

Concept Snapshot

Rule engine receives IoT data
Checks each rule's condition
If condition True, routes data to target
If no match, data discarded or stored
Simple if-then routing logic
Easy to add more rules for complex routing

Full Transcript

The rule engine for IoT data routing works by first receiving data from devices. It then evaluates each rule's condition against this data. If a condition is true, the engine routes the data to the specified target. If no rules match, the data can be discarded or stored. This process repeats for every incoming data point, enabling flexible and automated routing based on simple conditions.