IoT Architecture and Frameworks Lecture Notes

Learning Objectives

By the end of this lesson, you will be able to:

• Explain the IoT architecture and frameworks.
• Describe IoT interoperability as design considerations.
• Discuss industry-aligned use cases.

IoT Device Architecture

Four Layers of Device Architecture

1. Base Layer (IoT Devices)

   • Components include sensors with sensing, computing, and connection capabilities.

2. IoT Gateway / Aggregation Layer

   • Aggregates data from various sensors.
   • Forms the definition engine, setting rules for data aggregation.

3. Processing Engine / Event Processing Layer

   • Processes data obtained from the sensor layer using algorithms.
   • Displays data on a dashboard.

4. Application Layer / API Management Layer

   • Acts as an interface between third-party applications and infrastructure.
   • Supported by device managers and identity/access managers for security.

IoT Reference Architecture

Layers in IoT Reference Architecture

• Device Layer: Main component with interconnected devices (e.g., Bluetooth, Zigbee).
• Communication Layer: Utilizes REST protocols and application-level protocols; tightly coupled with the device layer.
• Bus Layer (Aggregation Layer):
  • Acts as a message broker, forming a bridge between data and communication layers.
  • Supports HTTP servers and MQTT brokers.
• Event Processing and Analytics Layer: Drives data transformation and stores data in databases.
• Client Layer: Creates a web-based engine for external API interaction and analytics dashboard.

IoT Frameworks

• ISO 30141: Common vocabulary, reusable designs, and best practices for developers.
• Secure application standards to maximize organizational benefits and reduce risks.

IoT Standardization and Design Considerations

Key Standards

• M2M (Machine to Machine): Connects devices via hardware/software.
• Contiki: Open-source OS for low-cost, low-power IoT microcontrollers.
• Light OS: Unix-like operating system for wireless sensor networks.
• Random Phase Multiple Access: Proprietary standard for connecting IoT objects.
• Sigfox: Proprietary low-power, low-throughput technology.

IoT Interoperability Challenges

• Coexistence of diverse systems and equipment.
• Varied data formats and models, leading to complex interrelationships.
• Difficulty in forming global agreements due to multivision systems.
• Low-power devices on lossy networks with limited recharge capabilities.

IoT Design Considerations

Factors to Consider

• Wireless capability, functionality, interoperability, secure storage, immediate boot capacity.
• Device categorization, bandwidth, cryptographic control, and power management.
• Establish a dispute resolution mechanism for long-term failures.

Stages of IoT Integration

1. Network Things: Wireless sensors and actuators.
2. Sensor Data Aggregation: Systems for analog to digital data conversion.
3. Edge IT Systems: Pre-processing data before cloud storage.
4. Data Management and Analysis: Performed in cloud or traditional data centers.

Key Architecture Areas of IoT

1. Client-side IoT Device Layer
2. Server-side IoT Gateway Layer
3. IoT Platform Layer: Pathway connecting clients and operators.

Centralized vs. Decentralized IoT Architectures

• Centralized Architecture: Hub managed from one point; associated with cloud architectures.
• Decentralized Architecture: Autonomous communication without a central hub; supports peer-to-peer messaging.

Industry-Aligned Use Cases

Smart Farming

• Requires robust data processing, durable hardware, and mobile access.
• Integrates sensors for monitoring climatic conditions and optimizing crop yield.

Diabetes Management

• Utilizes IoT to remotely transmit blood glucose data via a smartphone with embedded SIM.
• Ensures real-time monitoring and high accuracy.

Key Takeaways

• Understand IoT reference architectures and frameworks.
• Describe interoperability and design considerations in IoT.
• Discuss relevant industry use cases.