📘IoT Architecture

🎯 Lesson Objective

By the end of this lesson, students will:

• Understand the layered architecture of IoT systems

• Learn how data flows from sensor to mobile app

• Understand hardware layer vs network layer vs cloud layer

• Differentiate between edge computing and cloud computing

• Learn how this architecture applies to projects in this course

This lesson builds the foundation for designing scalable IoT systems.

1️⃣ What Is IoT Architecture?

IoT architecture refers to the structured design of how IoT systems are built, organized, and interconnected.

Instead of thinking of IoT as “just sensors + WiFi,”
we divide it into structured layers.

This makes systems:

• Organized

• Scalable

• Secure

• Maintainable

2️⃣ Standard 4-Layer IoT Architecture

Most IoT systems follow a 4-layer model:

1️⃣ Perception Layer
2️⃣ Network Layer
3️⃣ Processing Layer
4️⃣ Application Layer

Let’s break each layer down technically.

🔹 3️⃣ Perception Layer (Device Layer)

Also called:

• Physical Layer

• Sensor Layer

What It Contains:

• Sensors

• Actuators

• Microcontroller (ESP32)

📌 Function

This layer interacts with the physical world.

It:

• Collects data

• Converts physical signals into electrical signals

• Performs initial processing

📌 Example in This Course

📌 Technical Flow

Sensor → Analog/Digital Signal → ESP32 reads value

Example:

Temperature = 29°C
ESP32 reads it via GPIO
Stores it in variable

This is perception layer operation.

🔹 4️⃣ Network Layer

Also called:

• Transport Layer

• Communication Layer

📌 Function

This layer transfers data from ESP32 to cloud or mobile device.

📌 Communication Methods

• WiFi (most common in this course)

• Bluetooth

• GSM

• LoRa

• Ethernet

In this course, we focus on:

✔ WiFi (Station Mode)
✔ WiFi (Access Point Mode)
✔ Bluetooth

📌 Example Data Flow

ESP32 → WiFi Router → Internet → Blynk Cloud

OR

ESP32 → Creates Hotspot → Phone Connects

📌 Technical Protocols Used

IoT communication often uses:

• HTTP

• MQTT

• WebSocket

• TCP/IP

In this course:

Blynk internally uses WebSocket/MQTT protocols.

Students don’t need to manually implement these — but understanding is important.

🔹 5️⃣ Processing Layer (Cloud Layer)

Also called:

• Middleware Layer

• Data Processing Layer

📌 Function

This layer:

• Stores data

• Processes data

• Applies logic

• Sends responses

📌 In Our Course

We use:

👉 Blynk IoT Cloud

Cloud handles:

• Datastream storage

• Dashboard communication

• Device authentication

• Remote commands

📌 Example

Temperature > 30°C
Cloud receives data
Dashboard shows red alert

Cloud is responsible for visualization and control.

🔹 6️⃣ Application Layer

Also called:

• User Interface Layer

📌 Function

This is where user interacts with system.

Examples:

• Mobile app

• Web dashboard

• Serial Monitor

• Laptop interface

📌 In This Course

User can:

• See temperature

• Turn AC ON/OFF

• Lock/unlock door

• Monitor gas levels

This is final output layer.

7️⃣ Data Flow Example (Complete Path)

Let’s take Smart AC Example:

Step 1 – DHT11 measures temperature
Step 2 – ESP32 reads temperature
Step 3 – ESP32 sends data via WiFi
Step 4 – Blynk Cloud receives data
Step 5 – Dashboard updates
Step 6 – User presses AC ON
Step 7 – Cloud sends command
Step 8 – ESP32 receives command
Step 9 – Relay activates AC

Full round-trip architecture.

8️⃣ Edge Computing vs Cloud Computing

🔹 Edge Computing

Processing happens on ESP32 itself.

Example:

If temperature > 30 → Turn AC ON

This logic is inside microcontroller.

Advantages:

• Faster response

• No internet required

• More reliable

🔹 Cloud Computing

Processing happens on server.

Example:

Cloud compares temperature
Cloud decides control

Advantages:

• Centralized control

• Data logging

• Advanced analytics

📌 In This Course

We mainly use:

✔ Edge-based control logic
✔ Cloud-based monitoring

Hybrid approach.

9️⃣ 3-Layer vs 4-Layer Architecture

Some models simplify IoT into:

1️⃣ Device Layer
2️⃣ Network Layer
3️⃣ Application Layer

But for engineering clarity, we use 4-layer model.

🔟 Security in IoT Architecture

Security must exist at:

• Device level (authentication)

• Network level (secure WiFi)

• Cloud level (auth tokens)

In this course:

Blynk uses:

• Auth Token

• Device ID

• Secure connection

Security is very important in real-world IoT.

1️⃣1️⃣ Scalability Concept

Good IoT architecture allows:

• Multiple devices

• Multiple rooms

• Multiple users

• Remote access

Example:

One ESP32 → One room
Multiple ESP32 → Entire building

Architecture must support expansion.

1️⃣2️⃣ IoT Architecture in This Course

Let’s map it clearly:

This pattern repeats in every project.

1️⃣3️⃣ Why Architecture Knowledge Is Important

Without architecture:

Students just copy code.

With architecture:

Students can design systems.

Architecture knowledge allows:

• Debugging

• Scaling

• Innovation

• Product development

📌 Lesson Summary

In this lesson, we learned:

• IoT layered architecture

• Device layer details

• Network layer communication

• Cloud processing layer

• Application layer

• Edge vs Cloud computing

• Security considerations

• Scalability concepts

You now understand the structure behind every IoT project.