Both sides previous revisionPrevious revisionNext revision | Previous revision |
en:iot-reloaded:iot_reference_architecture [2024/12/03 12:27] – [Network Layer: The Communication Backbone] ktokarz | en:iot-reloaded:iot_reference_architecture [2025/01/04 14:42] (current) – [Application Layer] pczekalski |
---|
====== IoT Reference Architectures ====== | ====== IoT Reference Architectures ====== |
| |
This chapter focuses on the architectural design of IoT networks and systems. It leverages the well-known four-layered IoT reference architecture shown in figure 1 to discuss the methodologies and tools for the design of IoT networks and systems. | This chapter focuses on the architectural design of IoT networks and systems. It leverages the well-known four-layered IoT reference architecture shown in figure {{ref>iot_4layered_architecture}} to discuss the methodologies and tools for the design of IoT networks and systems. |
An IoT reference architecture acts as a strategic blueprint detailing the key components and their interactions within an IoT ecosystem. It offers a robust framework to guide the design, development, and deployment of effective IoT solutions, ensuring a cohesive and scalable system architecture. The IoT reference architecture outlines the foundational layers and components required for the seamless operation of IoT systems. Each layer plays a critical role in ensuring the efficient collection, transmission, processing, and utilization of data in an IoT ecosystem. | An IoT reference architecture is a strategic blueprint detailing the key components and their interactions within an IoT ecosystem. It offers a robust framework for designing, developing, and deploying effective IoT solutions, ensuring a cohesive and scalable system architecture. The IoT reference architecture outlines the foundational layers and components required for the seamless operation of IoT systems. Each layer is critical in ensuring efficient data collection, transmission, processing, and utilisation in an IoT ecosystem. |
| |
<figure iot_4layered_architecture> | <figure iot_4layered_architecture> |
{{:en:iot-reloaded:iot_architecture_4_layers.png?300|}} | {{:en:iot-reloaded:iot_architecture_4_layers.png?300|4 Layered IoT Architecture Model}} |
<caption>4 layered IoT architecture model</caption> | <caption>4 Layered IoT Architecture Model</caption> |
</figure> | </figure> |
| |
| |
| |
The perception layer forms the foundation of the IoT ecosystem by interacting directly with the physical world. It consists of various IoT-enabled devices, sensors, and actuators that gather data or influence the environment. | The perception layer forms the foundation of the IoT ecosystem by interacting directly with the physical world. It comprises various IoT-enabled devices, sensors, and actuators that gather data or influence the environment. Recent advances in hardware and low-power computing also bring data processing capabilities to this layer, including simple AI tasks. |
| |
**Components** | **Components** |
* Interfaces with actuators to enact physical changes or respond to user commands. | * Interfaces with actuators to enact physical changes or respond to user commands. |
| |
This layer serves as the "eyes and hands" of the IoT system, enabling it to sense and influence its surroundings. | This layer serves as the IoT system's "eyes and hands," enabling it to sense and influence its surroundings. |
| |
===== Transport Layer: The Communication Backbone ===== | ===== Transport Layer: The Communication Backbone ===== |
| |
| |
The transport layer, sometimes referenced as the network layer, facilitates connectivity between IoT devices and the broader system, ensuring that data captured at the perception layer is reliably transmitted to data processing units. This layer also supports device-to-device and device-to-cloud communication. | The transport layer, called the network layer, facilitates connectivity between IoT devices and the broader system. It ensures that data captured at the perception layer is reliably transmitted to data processing units. This layer provides various communication models, including device-to-device and device-to-cloud communication. |
| |
**Components** | **Components** |
| |
- Communication Protocols: Include MQTT, CoAP, HTTP, and WebSocket, tailored to support lightweight and efficient IoT communication. | - Communication Protocols: These include MQTT, CoAP, HTTP, and WebSocket, tailored to support lightweight and efficient IoT communication. |
- Networking Infrastructure: Gateways, routers, modems, and switches that route and manage traffic between devices and systems. | - Networking Infrastructure: Gateways, routers, modems, and switches that route and manage traffic between devices and systems. |
- Connectivity Technologies: | - Connectivity Technologies: |
* Long-range: Cellular (4G/5G), LoRaWAN, Sigfox. | * Long-range: Cellular (4G/5G), LoRaWAN, Sigfox. |
* Satellite for remote or global coverage. | * Satellite for remote or global coverage. |
| |
**Functionality** | **Functionality** |
* Ensures secure and seamless data transmission. | * Ensures secure and seamless data transmission. |
* Handles device discovery, authentication, and network management. | * Handles device discovery, authentication, and network management. |
* Bridges the gap between localized IoT systems and centralized data platforms like cloud servers. | * Bridges the gap between localised IoT systems and centralised data platforms like cloud servers. |
| |
This layer is the "nervous system" of the IoT architecture, enabling the flow of information across the ecosystem. | This layer is the "nervous system" of the IoT architecture, enabling the flow of information across the ecosystem. |
| |
| |
The data processing layer is responsible for aggregating, filtering, analyzing, and deriving actionable insights from the data collected by IoT devices. This layer can operate at the edge (closer to the devices) or in the cloud, depending on the application’s requirements. | The data processing layer is responsible for aggregating, filtering, analysing, and deriving actionable insights from the data collected by IoT devices. Depending on the application's requirements, this layer can operate at the edge (closer to the devices) in the fog or the cloud. |
| |
**Components** | **Components** |
| |
- Edge Computing Devices: Localized processing units that enable near-real-time data analysis, reducing latency and bandwidth usage. | - Edge Computing Devices: Localised processing units that enable near-real-time data analysis, reducing latency and bandwidth usage. |
- Cloud Platforms: Centralized systems for large-scale data storage, advanced analytics, and machine learning model training. | - Fog Computing Devices: Components located between the Edge and Cloud, fog computing devices provide distributed computing services that allow advanced data operations on a limited scale and ensure a more flexible approach to IoT data security and processing. They also optimise data transmission through aggregation and preprocessing for the Cloud Platforms. |
| - Cloud Platforms: centralised systems for large-scale data storage, advanced analytics, and extensive AI tasks such as machine learning model training. |
- Data Pipelines: Tools for data ingestion, transformation, and integration with enterprise systems. Examples include Apache Kafka and AWS IoT Core. | - Data Pipelines: Tools for data ingestion, transformation, and integration with enterprise systems. Examples include Apache Kafka and AWS IoT Core. |
- AI and Analytics Engines: Algorithms and tools for predictive analytics, anomaly detection, and decision-making. | - AI and Analytics Engines: Algorithms and tools for predictive analytics, anomaly detection, and decision-making. |
**Functionality** | **Functionality** |
| |
* Cleanses and normalizes raw data for processing. | * Cleanses and normalises raw data for processing. |
* Performs analytics to extract patterns, trends, and actionable insights. | * Performs analytics to extract patterns, trends, and actionable insights. |
* Supports automated decision-making and triggers responses in real time. | * Supports automated decision-making and triggers responses in real time. |
===== Application Layer ===== | ===== Application Layer ===== |
| |
The User Interaction and Value Creation Layer | The Application Layer is also known as the User Interaction and Value Creation Layer. |
The application layer is where processed data is transformed into end-user functionalities and value-driven solutions. It consists of software applications, services, and user interfaces that allow users to interact with and benefit from the IoT system. | The Application Layer transforms processed data into end-user functionalities and value-driven solutions. It consists of software applications, services, and user interfaces that allow users to interact with and benefit from the IoT system. |
| |
**Components** | **Components** |
| |
- Applications: Solutions tailored to specific use cases, such as smart home automation, industrial IoT monitoring, and healthcare diagnostics. | - Applications: Solutions tailored to specific use cases, such as smart home automation, industrial IoT monitoring, and healthcare diagnostics. |
- Visualization Tools: Dashboards and reporting tools that present data insights in an intuitive manner. | - Visualisations Tools: Dashboards and reporting tools that intuitively present data insights. |
- APIs and Integration Services: Enable connectivity with third-party applications and systems. | - APIs and Integration Services: Enable connectivity with third-party applications and systems. |
| |
| |
**Key Insights and Integration of Layers** | **Key Insights and Integration of Layers** |
- Seamless Integration: The layers are interdependent and must work harmoniously. For instance, data collected by the perception layer is meaningless without the processing layer’s intelligence or the application layer’s usability. | - Seamless Integration: The layers are interdependent and must work harmoniously. For instance, data collected by the perception layer is meaningless without the processing layer's intelligence or the application layer's usability. |
- Scalability and Flexibility: IoT systems must be designed to scale with increasing devices, data volumes, and user demands. Each layer should support modular expansion. | - Scalability and Flexibility: IoT systems must be designed to scale with increasing devices, data volumes, and user demands. Each layer should support modular expansion. |
- Security Across Layers: Robust security measures, such as encryption, authentication, and intrusion detection, must be integrated at every layer to protect data and devices from threats. | - Security Across Layers: Robust security measures, such as encryption, authentication, and intrusion detection, must be integrated at every layer to protect data and devices from threats. |
| |
By leveraging a well-structured IoT reference architecture, organizations can build resilient and efficient IoT ecosystems tailored to their specific needs. This layered approach ensures that every component, from sensors to user applications, contributes to a cohesive and value-driven system. The discussion on IoT architectures presented in the remaining parts of this chapter is based on the IoT reference architecture presented above. | Organisations can build resilient and efficient IoT ecosystems tailored to their specific needs by leveraging a well-structured IoT reference architecture. This layered approach ensures that every component, from sensors to user applications, contributes to a cohesive and value-driven system. The discussion on IoT architectures presented in the remaining parts of this chapter is based on the IoT reference architecture presented above. |