Why a newsletter dedicated for IoT Connectivity??

IoT devices are no longer confined to a single network, country, continent. Fleets of vehicles, industrial sensors, payment terminals, health devices, and asset trackers now cross borders, roam between operators, and increasingly talk to satellites as naturally as they talk to terrestrial networks.

Behind this apparent simplicity sits a messy reality of roaming agreements, GRX/IPX interconnects, GTP tunnels across half the planet, policy engines trying to enforce SLAs on networks they do not fully control, and regulators who are far more skeptical about “permanent roaming” (like in India, China, Brazil to name a few) and data leaving their borders than they were a few years ago.

This newsletter exists to unpack that complexity in a way that is both deeply technical and ruthlessly practical. Every Tuesday, it will zoom into one specific building block of global IoT connectivity and explain how it really works in production, not just in vendor slide-decks. :)

What does “Global IoT Connectivity” Really Means

“Global IoT connectivity” is often marketed as a global SIM that just works everywhere. In practice, it is a layered system encompassing:

• Access: 2G/3G sunset issues, LTE-M, NB-IoT, 4G, and 5G (NSA and SA) across hundreds of MNOs.

• Core networks: Mobile core (EPC/5GC), roaming anchors, GGSN/PGW/UPF placement, and slicing where it actually exists rather than in brochures.

• Interconnect: GRX/IPX clouds, roaming hubs, signaling and user-plane paths that define latency, reliability, and failure modes.

• Control and policy: PCRF/PCF, HSS/UDM/AUSF, and how authentication, QoS, and charging are enforced when devices roam permanently.

The operational magic of this lies in how these layers are composed to deliver predictable behavior for fleets running across various countries and networks.

Each week, the focus will be on one concrete component or pattern used to make “global IoT connectivity” actually work. Over the coming editions of this newsletter, I will try to cover topics that include:

• IMSI sponsorship

• GTP proxies

• GRX/IPX

• eSIM and multi-IMSI orchestration

• Private LTE/5G and hybrid connectivity

• NTN and satellite IoT integration

• APIs and exposure (GSMA Open Gateway, etc.)

This is not a marketing newsletter. Each edition will dive into details such as:

• Call flows and packet traces where sessions are anchored, how tunnels are set up, and where they break-out.

• Configuration examples and patterns of how core network elements are typically configured and what makes it work.

• Failure modes and debugging stories about what goes wrong and how those issues are traced and mitigated, referencing interviews from industry experts and from my own experience.

The content is written for people building or operating connectivity, not just consuming it.

This newsletter is targeted for

• IoT product leaders and architects working on connected products that must function across many countries and network conditions.

• Core-network and roaming engineers who care about GTP tunnels, routing, QoS, and security.

• MVNO/MVNE and connectivity providers designing global propositions, from industrial IoT.

• Hardware OEMs and module vendors who need to understand how their devices behave once they leave the lab and attach to networks worldwide.

Readers do not need to be 3GPP spec experts, but they should appreciate a diagram, a call flow, and a frank discussion of trade-offs.

The timing of this series is intentional. Over 2025-2026, several trends are colliding:

• Legacy networks continue to be switched off while LTE-M and NB-IoT coverage remains patchy, forcing careful access-technology decisions.

• 5G standalone deployments are moving from trials to production, especially for private and industrial use cases.

• eSIM is becoming the default for many IoT form factors, bringing both flexibility and operational complexity.

• Satellite and NTN providers are racing to integrate with terrestrial ecosystems.

• Regulators are scrutinizing permanent roaming, data localization, and lawful intercept more aggressively, which directly impacts how “global” a global IoT offer can be.

To get the most from this series:

• Subscribe or Follow: Turn on notifications for the author and the newsletter so each Tuesday’s issue lands in the feed.

• Comment with challenges and questions: Share roaming problems, tricky deployments, or topics that merit a deep dive. These will strongly influence the next editions of this newsletter.

• Share with colleagues: Pass issues to teammates in product, core, or operations, working on elements of Global IoT Connectivity, so discussions start from a shared, technically grounded perspective.

Looking forward to your support.

Originally written for "Inside Global IoT Connectivity" Newsletter in Linkedin on 17th February 2026. Link to original article here: https://www.linkedin.com/pulse/why-newsletter-dedicated-iot-connectivity-kartikeswar-koppula-dufqf/?trackingId=6dS61eLyRrG6PKBerwEAwA%3D%3D