Introduction to IOT (AL-803 (A)) - Unit 2 Short Notes

UNIT 2: IoT Technologies and Systems

1. IoT System Design and Architecture

Purpose of Logical Design:

To define the functional components, data flows, and interactions within an IoT system without specifying physical hardware or implementation details. It focuses on what the system does, not how it's built.

Key Components in Logical Design:

1. Devices/Things: Physical objects with sensors/actuators.

2. Connectivity: Communication protocols and networks.

3. Data Processing: Logic for filtering, aggregating, and analyzing data.

4. Services/Applications: User interfaces and business logic.

Components of an IoT Ecosystem:

[!TIP] Exam Focus: Be prepared to draw a simple block diagram of the IoT ecosystem showing data flow from Devices → Gateway → Cloud → Application.

2. Sensing and Actuation Technologies

Sensor Fundamentals

Challenges of Sensor Nodes:

• Power Consumption: Often battery-powered; must be ultra-low-power.

• Size & Cost: Must be small, cheap, and disposable for mass deployment.

• Accuracy & Precision: Affected by environmental drift, noise.

• Environmental Factors: Susceptibility to humidity, temperature, interference.

Types of Sensors:

Common Sensor Types: Temperature, Humidity, Pressure, Proximity, Motion (PIR), Gas, Image (Camera), Sound.

Actuator Fundamentals

Comparison: Electrical vs. Mechanical Actuators

[!TIP] Common Pitfall: Don't confuse "mechanical actuator" with "electromechanical relay." A relay is an electromechanical device (uses electromagnet to move a mechanical switch). In IoT context, "mechanical" often refers to purely physical actuators (spring-loaded, hydraulic).

3. Enabling Technologies for IoT

Machine-to-Machine (M2M) Communication:

• Definition: Direct communication between machines/ devices without human intervention, typically over wired or cellular networks.

• Architecture: Point-to-point or via a central hub. Often uses proprietary protocols. It is a precursor and subset of broader IoT.

Wireless Sensor Networks (WSN):

• Role: Foundational technology. Provides the infrastructure for large-scale, ad-hoc, multi-hop wireless networking of low-power sensor nodes. Enables data collection from physically distributed points, a core IoT function.

Radio Frequency Identification (RFID):

• Basic Principle:

  1. Tag: Contains a microchip (ID/data) & antenna. Passive tags harvest energy from reader's EM field.

  2. Reader: Emits EM field, receives signal from tag, decodes data.

  3. Backend System: Processes the read data.

• How it Enables IoT: Provides automatic wireless identification and data capture of physical objects without line-of-sight, enabling tracking, inventory, and context-awareness.

[!TIP] Exam Diagram: Be ready to sketch RFID working: Reader EM field → Tag energizes & modulates backscatter → Reader receives → Data to backend.

4. IoT Communication Protocols and Standards

Short-Range Wireless: NFC vs. Bluetooth vs. Wi-Fi

IoT-Specific Messaging & Transport Protocols:

1. MQTT (Message Queuing Telemetry Transport)

• Architecture Components:

  • Publisher: Sends messages to a Topic.

  • Subscriber: Receives messages from a Topic.

  • Broker: Central server that filters and routes messages based on topic subscriptions.

  • Topic: Hierarchical string (e.g., home/livingroom/temp) used for message classification.

• Key: Lightweight, publish/subscribe model, ideal for constrained networks.

2. CoAP (Constrained Application Protocol)

• Role of ACK & RST:

  • ACK (Acknowledgement): Confirms successful receipt of a confirmable (CON) message. Enables reliable transmission.

  • RST (Reset): Sent when a message is received but cannot be processed (e.g., unknown URI, malformed). Signals a fatal error, aborting the transaction. Crucial for error handling and resource management.

3. AMQP (Advanced Message Queuing Protocol)

• Main Frame Types:

  • Method Frame: Carries commands (e.g., basic.publish, queue.declare). Defines the action.

  • Header Frame: Carries attributes (metadata) for a message class (e.g., content-type, priority).

  • Body Frame: Carries the actual application data (message payload). Can be split across multiple frames.

  • Heartbeat Frame: Maintains connection liveness.

[!TIP] Protocol Comparison: MQTT (Pub/Sub, broker-centric) vs. CoAP (Req/Res, RESTful, for constrained nodes). MQTT for many-to-many; CoAP for one-to-one request/response.

5. IoT Platforms and Development Boards

Raspberry Pi as IoT Platform:

• Connectivity Options:

  • GPIO Pins: Direct digital/analog interfacing with sensors/actuators (via ADC/DAC modules for analog).

  • USB Ports: Connect external modems (4G/LTE), Wi-Fi/Bluetooth dongles, storage.

  • Ethernet Port: Wired network connection.

  • Built-in Wi-Fi & Bluetooth: Standard wireless connectivity.

  • CSI & DSI Ports: Connect official Raspberry Pi camera and display.

6. IoT Applications and Use Cases

Smart Home Automation System (IoT Context):

• Architecture: Distributed, layered.

• Key Components:

  1. Sensors/Actuators: Smart bulbs, thermostats, door locks, motion sensors.

  2. Hub/Gateway: Local controller (e.g., smart speaker, dedicated hub) that aggregates device traffic and connects to cloud.

  3. Cloud Platform: Manages devices, stores data, runs automation rules.

  4. Mobile/Web Application: User interface for control, monitoring, and scene setup.

• Implementation: Devices use protocols like Zigbee, Z-Wave, or Wi-Fi to talk to the hub. Hub uses MQTT/HTTP to communicate with cloud. User interacts via app.

[!DIAGRAM: CANVAS] Smart Home Architecture: Draw a diagram with four layers: (1) Physical Layer (sensors/actuators) → (2) Gateway/Hub Layer → (3) Cloud Layer → (4) Application Layer (user phone). Show data flowing up and commands flowing down.

7. Cross-cutting Issues: Challenges and Security

General Challenges in IoT Deployments:

Security in IoT Systems: Common Attacks & Vulnerabilities:

[!TIP] Exam Link: Connect security attacks to the challenges. E.g., DoS attacks exploit scalability issues; eavesdropping exploits privacy weaknesses.