“The Internet of Things (IoT) is a system of interrelated computing devices, mechanical and digital machines, objects, animals or people that are provided with unique identifiers and the ability to transfer data over a network without requiring human-to-human or human-to-computer interaction.”
— “What is the Internet of Things” on IoT Agenda.
Still kind of confused?
I don’t blame you. Although a quick Google search will turn up lots of articles and posts explaining what the Internet of Things is and its many potential benefits, it isn’t made clear how an IoT system actually works.
As the Director of Business Development at Leverege, I often find myself clarifying for those who are non-technical. So, as a non-technical person myself (at Brown I was a Philosophy major), here is a simple explanation of what goes on in an IoT system:
An IoT system, explained.
A complete IoT system integrates four distinct components: sensors/devices, connectivity, data processing, and a user interface. Below I will briefly explain each component and what it does.
First, sensors or devices collect data from their environment. This could be as simple as a temperature reading or as complex as a full video feed.
I use “sensors/devices,” because multiple sensors can be bundled together or sensors can be part of a device that does more than just sense things. For example, your phone is a device that has multiple sensors (camera, accelerometer, GPS, etc), but your phone is not just a sensor.
However, whether it’s a standalone sensor or a full device, in this first step data is being collected from the environment by something.
Next, that data is sent to the cloud (what’s the cloud?), but it needs a way to get there!
The sensors/devices can be connected to the cloud through a variety of methods including: cellular, satellite, WiFi, Bluetooth, low-power wide-area networks (LPWAN), or connecting directly to the internet via ethernet.
Each option has tradeoffs between power consumption, range and bandwidth (here’s a simple explanation). Choosing which connectivity option is best comes down to the specific IoT application, but they all accomplish the same task: getting data to the cloud.
3) Data Processing
Once the data gets to the cloud, software performs some kind of processing on it.
This could be very simple, such as checking that the temperature reading is within an acceptable range. Or it could also be very complex, such as using computer vision on video to identify objects (such as intruders in your house).
But what happens when the temperature is too high or if there is an intruder in your house? That’s where the user comes in.
4) User Interface
Next, the information is made useful to the end-user in some way. This could be via an alert to the user (email, text, notification, etc). For example, a text alert when the temperature is too high in the company’s cold storage.
Also, a user might have an interface that allows them to proactively check in on the system. For example, a user might want to check the video feeds in their house via a phone app or a web browser.
However, it’s not always a one-way street. Depending on the IoT application, the user may also be able to perform an action and affect the system. For example, the user might remotely adjust the temperature in the cold storage via an app on their phone.
And some actions are performed automatically. Rather than waiting for you to adjust the temperature, the system could do it automatically via predefined rules. And rather than just call you to alert you of an intruder, the IoT system could also automatically notify relevant authorities.
An IoT system consists of sensors/devices which “talk” to the cloud through some kind of connectivity. Once the data gets to the cloud, software processes it and then might decide to perform an action, such as sending an alert or automatically adjusting the sensors/devices without the need for the user.
But if the user input is needed or if the user simply wants to check in on the system, a user interface allows them to do so. Any adjustments or actions that the user makes are then sent in the opposite direction through the system: from the user interface, to the cloud, and back to the sensors/devices to make some kind of change.
Disclaimer: This is a curated post. The statements, opinions and data contained in this column are solely those of the individual authors and contributors and not that of iamwire or the editor(s). The article was published by the author here.