What is an IoT network?
An IoT network is a collection of various devices that communicate and interact with one another through diverse communication protocols without the need of human intervention. These networks are characterized by their ability to connect multiple devices, often from disparate domains, to collect, transmit, and analyze data.
The architecture of an IoT network can vary significantly based on the types of communication channels used and the specific requirements of the application.
Why IoT networks matter?
IoT networks serve as the backbone of the Internet of Things projects, enabling seamless communication and data exchange between a vast array of devices. They facilitate the aggregation of data from diverse sources, such as sensors, actuators, and other connected devices, into a centralized system where it can be analyzed and acted upon.
This interconnected framework allows for the creation of sophisticated applications and services, from smart homes and industrial automation to intelligent transportation systems. By providing the necessary infrastructure for devices to communicate efficiently, IoT networks ensure that data flows smoothly and that actionable insights can be derived in real-time.
The robustness and scalability of these networks are critical for supporting the growing number of connected devices and the increasing volume of data they generate.
Types of IoT networks
Different communication channels can lead to diverse installations and network configurations. Additionally, it is possible to combine several of these channels within the same setup. This section outlines various networks commonly found in IoT projects. The following list is not exhaustive but covers the most prevalent patterns.
Autonomous devices
In this model, devices connect directly to the cloud without intermediary systems. Each device is responsible for sending its own data. This setup is valued for its simplicity, as it avoids the need for additional hardware or software layers. However, it necessitates embedding additional logic within the devices and may require individual subscriptions, resulting in recurring costs.
This model is frequently used in the following scenarios:
-
Isolated devices: When a device is isolated, adding a gateway for each device is impractical. It’s more efficient to consolidate connectivity. For example, a weather station in a remote location that needs to send data independently.
-
Mobile devices: For devices whose locations are unpredictable or change frequently, it’s impractical to guarantee their connection to a specific gateway or network. An example is the tracking of heavy-duty trucks.
-
WiFi-connected devices: This scenario is somewhat unique because the device must be near a router that merely provides WiFi access, not directly related to the IoT solution. The device communicates directly with the cloud. WiFi simplifies direct cloud connections without additional subscription costs and offers strong connectivity. Devices often also use a secondary connection, such as BLE, for configuring the WiFi access point.
IoT gateway
In this configuration, a central IoT gateway manages connectivity to the cloud. It can utilize various channels such as WiFi, Ethernet, 5G, LTE-M, etc. Devices use an M2M (Machine to Machine) communication channel to connect to the gateway, examples include LoRaWAN, ZigBee, or WiFi.
Advantages of this setup include:
Cost reduction: Only the gateway requires a subscription if a network with such fees is used.
Offloading intelligence to the IoT gateway: Devices can simply transmit raw data without needing to handle internet connectivity issues or data reformatting. This reduces the hardware requirements for the devices. Furthermore, the IoT gateway can incorporate data filtering functionalities, such as eliminating duplicates, which lowers cloud processing costs.
Enhanced security: With a single point of contact to the cloud, the attack surface is minimized.
This setup can be implemented in either a star network, where all devices connect directly to the gateway, or a mesh network, as long as the gateway can receive data from the devices.
Disconnected network or device
In some scenarios, connectivity to the cloud is either not possible due to coverage issues or intentionally avoided for security reasons. For instance, a lack of network coverage may necessitate a technician connecting to the equipment via Bluetooth, WiFi, or another short-range technology.
Sometimes, disconnection from the cloud is a deliberate choice for security purposes. For example, a company might isolate its physical security systems on a dedicated network separate from the internet to minimize potential vulnerabilities.
In these cases, local connectivity is essential for configuring the equipment. If data needs to be sent to the cloud, the technician’s smartphone, tablet, or laptop can act as a gateway. After retrieving the data locally, the technician can upload it to the cloud when internet access is available. To accommodate this scenario, a cloud solution must allow a human user to act on behalf of a device, referred to as “on-behalf mode.”
