UNIT 4: Internet of Things – Comprehensive Notes
I. IoT Fundamentals and Architectural Frameworks
IoT Definition & Ecosystem
-
IoT: A network of physical objects ("things") embedded with sensors, software, and connectivity to exchange data with other devices/systems over the Internet.
-
Core Components:
-
Things: Sensors/actuators with unique identifiers.
-
Communication: Networks (WPAN, WAN, etc.).
-
Data Processing: Cloud/edge analytics.
-
Applications: User-facing services.
-
-
Ecosystem: Interconnected entities (device manufacturers, network providers, platform developers, application developers, users).
[!TIP] Exam often asks: "Role of Things and Internet in IoT." Emphasize: Things sense/act; Internet enables global connectivity & data exchange.
Logical vs Physical Design
| Logical Design | Physical Design |
|---|---|
| Abstract view: functional modules (e.g., application, network, perception layers). | Concrete implementation: hardware (sensors, gateways), protocols, physical connectivity. |
| Focus: data flow, services, APIs. | Focus: device specs, power, form factor, interfaces. |
Reference Architectures
-
IoT-A (Architecture): ISO/IEC 30141 standard. Key aspects:
-
Information Models: Semantic descriptions (e.g., using OCF, oneM2M).
-
Functional Entities: Device, gateway, network, application, management.
-
-
Service-Oriented Architecture (SOA):
-
Services as reusable, loosely-coupled components.
-
Challenges: Resource constraints, real-time needs, heterogeneity.
-
-
IoT Planes & Enablers:
-
Planes: Management, security, data, communication.
-
Enablers: Sensors, actuators, connectivity, analytics, cloud.
-
Interdependencies: E.g., security enabler impacts all planes.
-
IoT System Levels (vs M2M)
| Level 3 (Device-Centric) | Level 4 (Cloud-Centric) |
|---|---|
| Single device or local network. | Global cloud integration, big data analytics. |
| Example: Smart thermostat controlling HVAC. | Example: Smart city platform aggregating traffic, weather, energy data. |
M2M vs IoT
| Aspect | M2M | IoT |
|---|---|---|
| Connectivity | Point-to-point, proprietary networks. | IP-based, Internet-scale. |
| Data | Limited, siloed, for automation. | Massive, aggregated, for analytics. |
| Architecture | Standalone, closed systems. | Service-oriented, cloud-integrated. |
| Scalability | Low (point-to-point). | High (IP-based, cloud). |
| Analytics | Minimal, local. | Advanced (AI/ML in cloud). |
Reasons for Shift from M2M to IoT: IP ubiquity, cloud economics, big data value, open standards, scalability.
IoT Gateway Functionality
-
Roles:
-
Protocol Translation: E.g., ZigBee/Z-Wave ↔ Wi-Fi/Ethernet.
-
Data Filtering & Aggregation: Reduce cloud traffic.
-
Edge Processing: Local analytics, rule engines.
-
Security: Firewall, encryption termination.
-
Device Management: Onboarding, firmware updates.
-
II. Hardware Building Blocks and Device Fundamentals
Sensors
-
Types:
-
By Physical Quantity: Temperature, pressure, humidity, motion (PIR), image (camera), gas (MQ-series).
-
By Output: Analog (voltage), digital (I2C/SPI).
-
-
Selection Criteria:
- Accuracy, range, resolution, power consumption, cost, size, interface.
-
Common IoT Sensors: DHT11/DHT22 (temp/humidity), PIR (motion), MQ-2 (gas), Ultrasonic (distance), BMP180 (pressure).
-
Quantization Error:
- Error due to digitizing analog signal.
$$Q_e = \frac{V_{fs}}{2^n}$$
where $$\displaystyle V_{fs} $$ = full-scale voltage range, $n$ = bits of ADC.
\boxed{Q_e = \frac{V_{fs}}{2^n}}
Actuators
-
Role: Convert electrical signals to physical action (e.g., motor, relay, heater).
-
Types:
-
Mechanical: Motors, solenoids.
-
Soft: Pneumatic muscles, elastomers.
-
Shape Memory Polymer (SMP): Deform with temperature/light.
-
Pneumatic: Air pressure-driven.
-
-
Four Selection Characteristics:
-
Force/Torque Output.
-
Speed/Response Time.
-
Power Consumption.
-
Durability & Environment (IP rating, temperature range).
-
Microcontrollers & SBCs
-
Basic Microcontrollers (e.g., Arduino Uno - ATmega328P, ESP32):
- Low cost, low power, real-time operation, limited OS.
-
Raspberry Pi (SBC):
-
Architecture: SoC (Broadcom), runs Linux ( Raspbian).
-
vs Desktop: Lower power, ARM CPU, GPIO pins, no BIOS, embedded-focused.
-
-
Interfacing:
-
SPI: Full-duplex, synchronous (SCLK, MOSI, MISO, CS). Fast, short-range.
-
I2C: Multi-master, 2-wire (SDA, SCL). Addressable devices.
-
GPIO: General-purpose input/output pins (digital/analog).
-
Identification & Short-Range Communication
-
RFID:
-
Principle: Electromagnetic coupling (inductive) or backscatter (UHF) for tag-reader communication.
-
Features: Passive (no battery), active (battery), read/write, range (cm to m).
-
Terminology: Tag (RFID chip+antenna), Reader, Middleware, EPC.
-
IoT Integration: Asset tracking, inventory, access control.
-
-
NFC:
-
Definition: Short-range (≤10 cm) wireless tech based on RFID standards (ISO 14443, 18092).
-
Applications: Contactless payment, device pairing, data exchange (Android Beam).
-
Challenges & Requirements of IoT Devices
-
Challenges: Power limitation, constrained resources (CPU/RAM), security vulnerabilities, interoperability, scalability.
-
Requirements: Low energy consumption, small form factor, robust connectivity, security by design, cost-effectiveness.
III. Communication Protocols and Network Technologies
WPAN Standards
-
IEEE 802.15.4:
-
Defines PHY/MAC for low-rate WPANs (250 kbps max).
-
Relevance to IoT: Basis for ZigBee, 6LoWPAN. Low power, low data rate, star/mesh topologies.
-
-
6LoWPAN:
-
Functionality: Adaptation layer enabling IPv6 over 802.15.4 (packet fragmentation/header compression).
-
Comparison:
-
IPv4: 32-bit, limited addresses, not designed for IoT.
-
IPv6: 128-bit, vast address space, built-in security (IPsec), but header too large for 802.15.4 MTU. 6LoWPAN compresses headers.
-
-
-
ZigBee:
-
Architecture:
-
Coordinator: Forms network, stores info.
-
Router: Extends network, routes data.
-
End Device: Sleeps, communicates only with parent.
-
-
Types: ZigBee PRO (mesh, scalable), ZigBee IP (IPv6), ZigBee RF4CE (remote control).
-
Features: Low power, mesh networking, 250 kbps, 128-bit AES.
-
Wireless Sensor Networks (WSN)
-
Definition: Network of spatially distributed sensors cooperatively monitoring physical/environmental conditions.
-
Characteristics: Self-organizing, multi-hop, dense deployment, energy-constrained.
-
Applications: Environmental monitoring, agriculture, military.
-
Relation to IoT: WSN is a subset of IoT focusing on sensing; IoT adds Internet connectivity, cloud, applications.
Application Layer Protocols
| Protocol | Model | Key Features | IoT Role |
|---|---|---|---|
| MQTT | Publish-Subscribe | Broker-centric, QoS 0/1/2, lightweight (header ~2 bytes). | Ideal for constrained networks, remote monitoring. |
| CoAP | RESTful (Request-Response) | UDP-based, confirmable/non-confirmable, GET/PUT/POST/DELETE, observe pattern. | Constrained devices, web-like interaction, proxy to HTTP. |
| AMQP | Publish-Subscribe/Queue | Standardized, reliable, transactional, complex (frame types: transfer, disposition, flow). | Enterprise IoT, financial, guaranteed delivery. |
| XMPP | Publish-Subscribe/IM | XML-based, presence, extensible. | Real-time IoT services, chat-bot integration. |
| SMQTT | Publish-Subscribe | Secure MQTT: Uses RSA/AES for message encryption, key management. | Secure messaging in untrusted environments. |
| WebSockets | Full-duplex | Persistent TCP connection, real-time bidirectional. | Web-based IoT dashboards, live updates. |
[!TIP] MQTT vs AMQP: MQTT is simpler, lightweight; AMQP is richer, enterprise-grade. MQTT can use WebSockets as transport (over TCP).
CoAP in Constrained Networks
-
Uses UDP (no connection overhead), small headers (4 bytes base).
-
Confirmable (CON): Acknowledged, retransmitted.
-
Non-Confirmable (NON): Fire-and-forget.
-
Block-wise Transfer: For large payloads (fragmentation).
-
Observe: Server pushes updates to client (like MQTT subscribe).
-
Justification: Low overhead, RESTful semantics, works with proxies to HTTP.
Network Topologies & Types
-
Physical Topologies: Star (hub/AP), Mesh (multi-hop), Tree (hierarchical), Bus (legacy).
-
Connection Types: WPAN (Bluetooth, ZigBee), WLAN (Wi-Fi), LPWAN (LoRaWAN, NB-IoT), Cellular (4G/5G).
Challenges in IoT LAN Development
- Interference (2.4 GHz crowded), security (open Wi-Fi), device heterogeneity, power management, scalability.
IV. Cloud Computing, Data Analytics, and IoT Platforms
Cloud Integration in IoT
-
Role: Scalable storage, compute, analytics, device management, APIs.
-
Cloud Communication APIs: RESTful APIs (HTTPS), MQTT over WebSockets, CoAP-to-HTTP proxies.
-
Service Models:
-
IaaS: Virtual machines, storage (AWS EC2, Azure VMs).
-
PaaS: Development platforms (AWS IoT Core, Azure IoT Hub).
-
SaaS: Applications (Salesforce IoT, SAP IoT).
-
-
Challenges: Latency, bandwidth cost, data privacy, vendor lock-in, security.
Data Analytics in IoT
-
Role: Extract insights from sensor data (predictive maintenance, anomaly detection, optimization).
-
Analytics Approaches:
-
M2M: Mostly descriptive (what happened), batch processing.
-
IoT: Predictive/prescriptive (what will happen, what to do), real-time streaming (Spark, Flink), edge analytics.
-
IoT Platforms
-
Common Platforms: AWS IoT, Azure IoT, Google Cloud IoT, IBM Watson IoT, ThingWorx.
-
Features/Components:
- Device SDKs, connectivity (MQTT/CoAP brokers), device registry, rules engine, data storage, dashboards, security (TLS, auth).
V. Security and Privacy in IoT Systems
Need for Security
- Devices are physically accessible, often poorly secured, attack surface large. Compromise can lead to physical harm (medical devices), privacy breaches, DDoS (Mirai).
Security Models/Frameworks
-
Layered Security: Device, network, cloud, application.
-
IoT Security Framework (e.g., NIST, OWASP IoT):
- Identify, Protect, Detect, Respond, Recover.
-
Authentication/Authorization: Mutual TLS, OAuth 2.0, certificates.
-
Data Security: Encryption (AES), secure key storage (HSM/TPM).
Vulnerabilities & Attack Vectors
| Layer | Vulnerabilities | Example Attacks |
|---|---|---|
| Device | Hardcoded passwords, unpatched firmware, insecure interfaces. | Botnet recruitment (Mirai). |
| Network | Open ports, weak encryption, replay attacks. | Sniffing, man-in-the-middle. |
| Application/Service | Insecure APIs, injection, broken auth. | Data theft, service disruption. |
Secure Messaging & Protocols
-
SMQTT: RSA for key exchange, AES for message encryption. Secure publish-subscribe.
-
Best Practices:
-
Use TLS/DTLS for transport.
-
Regular firmware updates.
-
Network segmentation.
-
Principle of least privilege.
-
VI. Applications and Case Studies
Smart Home Automation (Design with Raspberry Pi)
-
Components Sketch:
[Sensors: DHT11, PIR, Light Sensor] → [Raspberry Pi (GPIO/I2C/SPI)] → [Cloud/AWS IoT] ← [User App] ↑ [Actuators: Relay (lights/fan), Servo (door lock)] -
Applications: Lighting control, HVAC, security (alarms, cameras), energy monitoring.
-
Raspberry Pi Role: Central hub/gateway: runs Node-RED/Python, interfaces sensors via GPIO, connects to cloud via MQTT/HTTP.
Other IoT Domains
-
Industrial IoT (IIoT): Predictive maintenance, asset tracking (ZigBee/6LoWPAN).
-
Smart Cities: Traffic management, smart lighting (LPWAN).
-
Healthcare: Wearables (BLE), remote patient monitoring.
-
Agriculture: Soil moisture sensors (LoRaWAN), automated irrigation.
Case Study: Smart Home
-
Implementation: Raspberry Pi as gateway; ZigBee sensors; AWS IoT Core for rules/analytics; mobile app for control.
-
Challenges: Interoperability (ZigBee/Z-Wave/Wi-Fi), security (camera feeds), user privacy.
VII. Advanced and Emerging Topics
Software Defined Networking (SDN) in IoT
-
Definition: Separates control plane (centralized controller) from data plane (switches).
-
IoT Relevance: Dynamic network management, traffic optimization, security policy enforcement.
-
Maturity Assessment: Emerging for IoT. Challenges: scalability of controllers, overhead in constrained networks, standardization.
Future Trends
-
Edge Computing: Process data near source (reduce latency, bandwidth).
-
AI Integration: On-device ML (TinyML), predictive analytics.
-
5G & Beyond: URLLC, massive IoT (mMTC), network slicing.
-
Blockchain: Decentralized trust, secure device identity.
High-Yield Exam Formulas & Definitions
-
Quantization Error: $$\displaystyle \boxed{Q_e = \frac{V_{fs}}{2^n}} $$
-
6LoWPAN: IPv6 adaptation layer for 802.15.4.
-
MQTT: Publish-Subscribe, broker, QoS levels.
-
CoAP: RESTful, UDP, confirmable/non-confirmable.
-
ZigBee Roles: Coordinator, Router, End Device.
-
IoT Levels: Level 3 (device), Level 4 (cloud).
-
SMQTT: Secure MQTT (RSA+AES).
-
SDN: Control/data plane separation.