The four primary systems of IoT technology are sensing and perception, communication and connectivity, data processing and analytics, and the user interface. They explain how a connected device collects information, sends it, uses it, and presents it to people.
This four-part model is a useful way to understand the Internet of Things (IoT), rather than a universal architecture standard. Some descriptions combine these functions into fewer components; a single device or application can also perform more than one function.
Contents
Key Takeaways
- Sensing and Perception: Sensors measure physical conditions such as temperature, movement, or light.
- Communication and Connectivity: Networks carry device readings and, where supported, commands.
- Data Processing and Analytics: Software checks readings, stores them, and applies rules or analysis on a device, nearby gateway, or cloud service.
- User Interface: An app, website, or control panel shows information and lets authorized users change settings or request actions.
Sensing and Perception: The Foundation of IoT Systems
Sensing and perception connect an IoT system to the physical environment. A temperature sensor in a greenhouse, for example, converts a measurement into data that the system can use.
- Sensors: Measure conditions such as temperature, movement, humidity, or light. Their placement and calibration affect the accuracy of the reading.
- Devices: Include endpoints that collect, process, or use data. An actuator, such as a motor or valve, changes something in the physical environment when instructed.
- Data Accuracy: A reliable system needs suitable sensors and readings with the right units. A wrong measurement can produce a wrong alert or action.
Communication and Connectivity: How IoT Data Travels
Communication and connectivity move information between devices and software. A greenhouse sensor might send its temperature reading over Wi-Fi to a local controller or an internet-connected service. The chosen network depends on range, power use, data volume, and the installation.
- Communication Protocols: Define how devices exchange messages. MQTT and HTTP are examples used by internet-connected systems; support must match between the components.
- Gateways: Can connect local devices to another network, translate protocols, or route messages. Devices that connect directly to a service may not need a separate gateway.
- Network Options: Include Ethernet, Wi-Fi, Bluetooth, Zigbee, and cellular. Short-range wireless is one option, rather than a requirement for every IoT device.
- Mesh Networks: Allow supported devices to relay messages through other devices. A mesh can extend coverage, but it is optional and depends on the equipment and network design.
Device readings are often called telemetry. A command travels toward a device to request an action, such as switching on a greenhouse fan. The device can report its resulting state so the application knows whether that action took place. A monitoring-only sensor may send readings without accepting control commands.
Data Processing and Analytics: Making Sense of IoT Information
Data processing turns readings into information or actions. A greenhouse controller can compare the measured temperature with a threshold and switch a fan on. This simple rule does not need machine learning, a large dataset, or a cloud connection.
- On-Device Processing: A device’s processor can filter readings or run a control rule where the data is collected.
- Edge Processing: A nearby gateway or local computer can combine readings and respond without sending every decision to a remote service.
- Cloud Computing: Can provide remote storage and processing for many devices or locations. It is useful for shared dashboards and longer-term analysis, but is not necessary for every local action.
- Analytics: May be a simple threshold, a historical trend, or a more complex model. Big-data tools fit large or complex datasets; a small sensor installation may need much less.
A system can combine these approaches. The greenhouse controller might run the fan locally while sending selected readings to a cloud service for history and remote viewing. Whether local functions continue during an internet outage depends on the device and application design.
User Interface: Viewing Information and Controlling Devices
The user interface is where people view IoT information and interact with the system. It may be a phone app, a website dashboard, or a local control panel. In the greenhouse example, it shows the temperature, alerts, and fan status, and may let an authorized user change the temperature target.
- Measurements: Show readings with units and their update time, so an old value is not mistaken for a current one.
- Status and Alerts: Tell users whether a device is online and whether it has reported a problem.
- Controls: Let permitted users change settings or request actions. Show whether a command is pending, failed, or confirmed where the system supports that feedback.
Automated systems do not require a person to approve every action. A local rule can operate the fan while the interface gives the owner a way to monitor conditions and adjust the rule.
Security Across the Four Systems
Security applies across the device, network, processing software, and interface. Identify devices, authenticate users and devices, restrict access to permitted actions, protect stored and transmitted data, and maintain supported software updates. For example, someone allowed to read the greenhouse dashboard should not automatically be allowed to change its controls.