GSMA's SGP.32 eSIM Standard Shifts IoT Device Control from Servers to Endpoints

Enterprise IoT Deployments Gain Autonomous Carrier Switching

GSMA's SGP.32 eSIM standard introduces device-initiated profile downloads for IoT hardware, replacing the server-orchestrated SGP.02 architecture that required backend provisioning for every carrier change. Under SGP.32, endpoints evaluate coverage quality or compliance policies and switch operators without centralized intervention. This shifts operational control from IT departments and connectivity providers to the edge device itself.

For enterprises managing fleets across fragmented coverage areas — logistics tracking in rural corridors, remote industrial sensors, or global asset monitoring — the change reduces dependency on vendor provisioning systems. Devices can prioritize the strongest available signal rather than waiting for manual reconfiguration. The standard also lowers barriers for consumer-mobile carriers to enter IoT connectivity, intensifying competition against established providers whose SGP.02 platforms required significant integration overhead.

Wireless Logic anticipates SGP.32 will pressure mature providers to differentiate through compliance frameworks and scalability rather than proprietary provisioning lock-in. Enterprises should evaluate whether current IoT connectivity contracts include SGP.32 roadmaps and what migration timelines look like for existing device inventories.

AT&T's Network Intelligence Standard Competes on Granular KPIs

AT&T's IoT Network Intelligence Standard, introduced at CES 2026, exposes real-time 4G and 5G metrics — signal strength, throughput, latency, and location-based analytics — through a dashboard interface. The standard targets enterprises needing per-device visibility into connectivity performance, competing with general network monitoring tools that aggregate data without IoT-specific granularity.

The offering addresses a common blind spot: enterprises deploying sensors or telemetry devices often lack direct insight into why individual endpoints drop offline or experience degraded performance. AT&T's approach surfaces whether a failure stems from weak signal, network congestion, or device malfunction. However, the company has not disclosed pricing models, customer adoption figures, or comparative benchmarks against competitors like Verizon's ThingSpace or AWS IoT Device Defender.

Enterprises evaluating connectivity providers should ask for access to similar KPI dashboards during procurement. The absence of published pricing suggests AT&T may bundle the service with existing IoT connectivity contracts rather than offering it standalone, which could complicate cost comparisons.

LoRaWAN Maintains Industrial Niche Amid NIS2 Compliance Pressure

LoRaWAN remains positioned for industrial IoT deployments requiring 50 kbps data rates over 2-10 km ranges with building penetration, particularly where cellular alternatives like NB-IoT face cost or coverage constraints. The protocol's relevance strengthens as enterprises implement network segmentation requirements under the EU's NIS2 directive, which mandates isolation of critical infrastructure systems by late 2026.

LoRaWAN's star topology naturally segments IoT traffic from enterprise networks, reducing the attack surface compared to cellular-connected devices that route through carrier infrastructure before reaching corporate systems. However, the protocol has not gained measurable market share against cellular standards, and no new adoption data from major industrial operators has emerged.

Enterprises subject to NIS2 should evaluate whether LoRaWAN's inherent segmentation reduces compliance costs compared to retrofitting cellular IoT deployments with additional firewalls or VLANs. The calculation depends on device density, existing gateway infrastructure, and whether applications tolerate LoRaWAN's higher latency compared to 5G.

What to Watch

GSMA has not published SGP.32 certification timelines for chipset manufacturers or module vendors. Enterprises planning IoT deployments in 2026 should confirm whether shortlisted hardware supports the standard or requires firmware updates. Devices locked to SGP.02 will depend on vendor provisioning systems for the next 5-10 years, limiting carrier optionality.

For AT&T's Network Intelligence Standard, pricing disclosure will determine whether the service becomes table stakes or remains a premium add-on. Competitors will likely match KPI visibility if adoption accelerates, but first-mover advantage may lock in early customers through dashboard integrations with existing IoT platforms.

LoRaWAN adoption hinges on whether NIS2 enforcement drives enterprises toward protocols with lower integration complexity for segmentation. If regulators accept virtualized network isolation for cellular IoT, LoRaWAN's compliance advantage narrows. Track whether major industrial OEMs standardize on LoRaWAN gateways or continue dual-tracking with NB-IoT.