IoT - synchronize the layers
How the next generation of IoT infrastructure moves from simply providing connectivity to making heterogeneous local devices intelligible to one another.
If we are talking about the complete connected-device architecture and reducing deployment complexity then antenna/RF expertise, router capability, and the mission-critical communications position of Antennas must be coherent.
So, the next IoT opportunity may be between the devices - Connectivity has solved one problem. Interoperability may be the next.
For much of the development of the Internet of Things, the central challenge was relatively straightforward: How do we connect the device?
That question created an extraordinary period of innovation in antennas, cellular communications, Wi-Fi, Bluetooth, LPWAN, GNSS, routers, gateways and cloud platforms.
It isn't finished.
5G, private networks, satellite connectivity and increasingly sophisticated RF systems are extending reliable communications into places where connecting equipment was previously difficult or uneconomic.
But as connectivity improves, another problem becomes increasingly visible.
We have become very good at connecting devices to networks.
We are considerably less good at enabling different devices, using different technologies, from different generations, to communicate simply with each other.
That could represent one of the next significant opportunities in IoT.
The installed world isn't starting again
The future of IoT will not be built exclusively from new equipment.
Factories, commercial buildings, energy systems, utilities, transport infrastructure and homes already contain enormous numbers of installed devices.
Meters.
Sensors.
Pumps.
Boilers.
Heat pumps.
Compressors.
Solar inverters.
Battery systems.
HVAC controllers.
Industrial instruments.
Building-management systems.
Some are connected.
Some are analogue.
Some use established industrial protocols.
Some communicate wirelessly.
Some are effectively isolated.
Most will not be replaced simply because a newer communications technology has appeared.
That means the IoT industry faces an interesting architectural challenge.
How do we bring the installed physical world into the connected world without rebuilding it?
From connectivity to translation
Consider a relatively ordinary plant room.
One device might communicate over Modbus.
Another may have a simple analogue output.
A newer sensor might use Bluetooth Low Energy.
An environmental sensor could use LoRa.
The building-management system might operate over BACnet.
A new energy-management system may ultimately want the information over Ethernet, Wi-Fi or another IP-based interface.
None of these technologies is necessarily wrong.
They simply come from different generations and different applications.
The problem therefore becomes less about choosing the winning protocol and more about creating an intelligent translation layer between them.
Conceptually: Physical Device → Local Intelligence → Protocol Translation → Network
That middle layer could become increasingly important.
Perhaps not everything needs to reach the cloud
There is another assumption worth reconsidering.
For much of IoT, information has followed a familiar route:
Sensor → Gateway → Internet → Cloud → Application → User
There are excellent reasons for that architecture.
Cloud infrastructure enables remote management, historical analysis, fleet monitoring, enterprise integration and increasingly powerful AI.
But it doesn't necessarily follow that every measurement needs to make that entire journey.
Sometimes somebody standing beside the equipment simply needs to know:
What is happening here, now?
A local interface can answer that question without requiring a round trip through remote infrastructure.
The more interesting architecture may therefore become:
Device → Local Intelligence → Local Information with: → Network / Cloud / Enterprise
available where it adds value.
This isn't an argument against cloud connectivity.
It is an argument for choice.
The edge is becoming more capable
That choice is becoming possible because intelligence at the edge is improving rapidly.
Processors are becoming smaller, less expensive and more energy-efficient.
A device no longer has to transmit every measurement before something useful can happen.
It can potentially identify a change, compare values, recognize an exception, trigger an alarm or translate information locally before deciding what needs to leave the site.
That changes the economics of IoT.
Instead of thinking only about connecting sensors, we can begin thinking about distributed local intelligence.
A sensor measures something.
A local device understands it.
A communications layer transports what is useful.
And a wider network connects it when required.
Each layer does the job it is best suited to perform.
The antenna is becoming part of a larger system
This evolution is particularly interesting from an RF perspective.
Modern IoT equipment increasingly needs combinations of cellular, GNSS, Wi-Fi, Bluetooth, LPWAN and other technologies rather than a single radio connection.
The physical constraints are considerable.
Antennas, enclosures, power consumption, processors, radio modules, environmental protection and installation method all interact.
And the further wireless technology moves into industrial infrastructure, energy systems, transport and buildings, the more important real-world installation becomes.
A technically sophisticated device that is difficult or expensive to install is not necessarily a good IoT product.
The engineering objective increasingly becomes:
Make sophisticated connectivity simple at the point of deployment.
That creates an interesting convergence between RF engineering, ruggedized enclosures, embedded electronics and local software.
Could the gateway itself evolve?
The conventional gateway principally connects devices to networks.
The next generation could do considerably more.
Imagine a compact device capable of accepting information from multiple wired and wireless sources, interpreting it locally, presenting essential information locally and translating selected data into whatever communications environment surrounds it.
Such a device would not necessarily replace existing gateways, controllers or cloud platforms.
It could sit between generations of technology.
Old equipment on one side.
Modern communications on the other.
That distinction matters because the installed equipment base is vastly larger than the annual market for completely new equipment.
There may therefore be considerable value in technology that makes existing infrastructure more useful.
And there is another possibility: local networks
Take the concept one stage further.
If individual edge devices can sense, interpret and communicate locally, they need not necessarily operate as isolated endpoints.
A building, industrial site, energy installation or piece of infrastructure could gradually become a collection of intelligent local nodes.
Some might have Internet connectivity.
Some might not.
Some might communicate only short distances.
Others might provide a bridge into cellular, private 5G, Wi-Fi, LoRaWAN or satellite networks.
The resulting architecture becomes less like the traditional:
device → gateway → cloud
and more like:
device ↔ device ↔ local network ↔ wider network
The distinction may sound subtle.
Commercially, this is significant.
Resilience becomes a feature
Local capability also introduces something increasingly valuable:
graceful degradation.
If the Internet connection disappears, what happens?
If the answer is everything stops, the system has a fundamental dependency.
But if measurement continues, local communication continues, alarms continue and essential information remains available, loss of the external connection becomes an inconvenience rather than a system failure.
For industrial, infrastructure, energy and mission-critical applications, that distinction matters.
The strongest future architecture may therefore not be purely local or purely cloud-based.
It may be:
Local when it must be. Connected when it can be. Cloud-enabled when it adds value.
A different definition of connectivity
This suggests that the IoT industry's definition of connectivity may itself be expanding.
Yesterday, connectivity meant: Can the device reach the network?
Tomorrow it may increasingly mean: Can this device communicate with whatever surrounds it?
That requires antennas and RF engineering.
But it will also require protocol translation, edge processing, local display, security, ruggedized packaging and simple deployment.
The companies capable of bringing several of those disciplines together could occupy an interesting position in the next stage of IoT.
Because there are already billions of devices in the physical world.
The opportunity isn't simply to connect another billion.
It is to make the devices already around us understandable, interoperable and useful to each other.
At Tigertek, that is an area we believe deserves considerably more attention.
The next great IoT network may not begin in the cloud.
It may begin locally — between the devices - 'synchronising' so to speak !
