From Device to Cloud (Without the Telecom Jargon)
For many people, IoT connectivity feels like a black box.
A device sends data.
Somehow it reaches the cloud.
Dashboards update.
Magic happens.
But when something goes wrong—or when you need to scale—that black box suddenly becomes a problem.
Understanding the IoT connectivity stack does not require deep telecom knowledge.
It just requires a clear, structured view of how the pieces fit together.
This blog explains the full IoT connectivity stack, step by step, in plain English.
Why the IoT Connectivity Stack Matters
IoT failures rarely happen in isolation.
They usually happen:
- between layers
- at integration points
- where responsibilities are unclear
If you don’t understand the stack, you don’t know:
- where problems originate
- who owns which layer
- what can (and cannot) be changed
Clarity here saves time, money, and frustration.
Layer 1: The Device (Where Everything Starts)
At the bottom of the stack is the IoT device.
This includes:
- sensors and actuators
- firmware
- power source
- communication module
Key realities:
- devices are constrained
- updates are infrequent
- physical access is limited
Design mistakes at this layer are extremely hard to fix later.
Layer 2: Connectivity Hardware (Modem + SIM)
This layer provides identity and access.
It consists of:
- a cellular modem
- a SIM or eSIM (eUICC)
The SIM:
- identifies the device
- authenticates it to the network
- defines access rights
This is where GSMA standards (SGP.02, SGP.32) come into play.
Once deployed, this layer is often locked in for years.
Layer 3: Mobile Network Access
Here, the device connects to:
- a local mobile network
- potentially via roaming
This layer determines:
- coverage
- latency
- reliability
- roaming behavior
Important insight:
The same device can behave very differently on different networks.
Network choice matters more than many teams expect.
Layer 4: Network Routing & Security
This layer defines how traffic flows.
Common models:
- public internet routing
- VPN-based routing
- private APN routing
This is where:
- isolation is enforced
- exposure is limited
- security posture is defined
Many IoT security incidents originate here—not in the cloud.
Layer 5: Connectivity Management Platform (CMP)
The CMP is the control layer.
It provides:
- SIM activation and deactivation
- usage monitoring
- lifecycle states
- alerts and automation
Without a CMP, IoT operations rely on manual processes.
At scale, that does not work.
Layer 6: Data Ingestion & Cloud Platforms
This layer receives and processes data.
It includes:
- IoT hubs
- message brokers
- cloud platforms
Here, data is:
- stored
- processed
- integrated into applications
This is the layer most people see—but it depends entirely on the layers below.
Layer 7: Applications & Business Logic
At the top of the stack:
- dashboards
- analytics
- automation
- integrations
This is where IoT delivers business value.
But it only works reliably if the lower layers are solid.
Where Things Usually Go Wrong
Most IoT issues happen when:
- layers are designed in isolation
- ownership is unclear
- assumptions are made about “someone else’s responsibility”
The stack works as a system—or not at all.
The Key Takeaway
IoT connectivity is not one thing.
It is a stack of interdependent layers.
Understanding this stack:
- improves decision-making
- speeds up troubleshooting
- reduces risk
- enables scale