When you think of connected devices, you immediately think of some examples. Whether it’s cars, door sensors, or medical devices, they connect and process data in different ways.
Some iterations are smarter than others. Cameras can connect to Wi-Fi access points and send data directly to the cloud. Door sensors are simpler. Both technologies require a physical intermediary device connected to the network to process the data and send it.
They are called IoT gateways, which play a crucial role in IoT deployments, collecting and aggregating sensor data from various devices. IoT gateway devices bridge the communication gap between IoT devices, sensors, systems, and the cloud. By systematically connecting the field and the cloud, IoT gateway devices provide local processing and storage solutions, as well as the ability to autonomously control field devices based on sensor data input.
From there, they convert between sensor protocols and process data from these sensors and devices before sending it out for further processing. With simpler devices and sensors, they typically connect to IoT gateways using short-range wireless transmission modes (e.g., Bluetooth LE, Zigbee, Z-Wave) or remote modes like LTE, LTE-M, or even Wi-Fi.
Once connected, IoT gateways provide several key features, including:
-
Bridging communications and facilitating machine-to-machine (or M2M) communication.
-
Offline support services, so a WAN connection is not always required.
-
Data extraction, cleaning, filtering, localization, and even early analysis before sending it to the cloud or remote data centers.
-
Providing an additional layer of security as a buffer between the WAN and devices.
-
Real-time configuration, control, management, and change management tracking.
However, IoT gateways do add an extra component to the network, along with another potential attack vector that could be compromised. This means you have an additional device on the network that must be updated, managed, and secured. That said, what happens when we remove this IoT gateway? Will future edge and distributed computing solutions be able to handle the billions of IoT and connected devices coming online in the next few years?
To achieve a gateway-less IoT deployment, some changes must be made.
The New Realm of IoT Devices
Even today, IoT gateways still play a critical role in helping sensors and devices connect to an intermediary source that collects data and sends it out for further processing and analysis. However, edge computing is specifically designed to overcome the challenges of IoT connectivity.
Edge computing architectures help with latency. Combined with 5G technology (where latency is typically less than 1 millisecond and speeds exceed 100 Mbps), you have a powerful platform where edge devices can now connect and process all data.
Is the Edge the New IoT Gateway?
The real answer is not black and white; it depends on the situation. In the next five years or so, edge deployments will become a key component of IoT integration and collaboration with connected devices. In fact, assuming the edge network is close enough and meets your requirements, you will be able to connect simple devices and sensors directly to the edge ecosystem.
Additionally, you will be able to process data faster at the edge and gain deeper insights into the information being collected. You will be able to integrate with other analytics or insight services that already belong to that edge ecosystem. By leveraging a powerful edge and 5G platform, you will be able to analyze data faster as it will connect to a broader, faster network.
When you compare this with the list above, you will quickly notice that edge and 5G can act as new IoT gateways, but positioned at the edge. These systems are designed to:
· Support connected devices and M2M communication
· Enable advanced data extraction and processing
· Ensure the security of data and physical infrastructure
· Provide real-time access and control over devices
However, despite the powerful capabilities of the edge ecosystem, there are still some challenges in functionality. Specifically, in certain situations, IoT gateways may be less reliable in edge architectures:
· If the connection to the edge ecosystem is lost, data, performance, and even management functions may be lost until the connection is restored.
· You will lose offline support functionalities that allow you to continue to process and use local data.
· You may lose some security protections as connected devices must go to the edge for connectivity. However, this is debatable as a well-designed edge ecosystem can be very secure.
· Depending on your organization, you may encounter compliance issues surrounding data. Certain types of data points may be prohibited from being sent outside the enterprise.
Ensure you plan ahead and truly understand the types of connected devices you have and how they interact with the respective data.
The Future of IoT Design
So, will the edge become the future IoT gateway? In many cases, the answer is yes, but it is not the end of IoT gateways. Certainly, in some cases, a local IoT gateway may be required, especially in latency-sensitive situations. However, data security and integrity requirements may further necessitate the use of localized approaches to handle IoT data.
Edge maturity will also take a few years. If you are going to deploy IoT solutions, ensure you cover the basics. You need to understand latency and connectivity requirements, as well as how to manage data and device communication. That said, understand the robust capabilities of the edge ecosystem in the near and distant future. Don’t shy away from testing the edge opportunities, as it can be a driver for your business.
This article was translated by Qianjia.com.