SGP.32 and the Future of eSIM: iSIM, Edge Computing and Beyond

The Direction of Travel

SGP.32 solves the immediate problem: remote SIM management for IoT devices at scale. But the forces that drove its creation – miniaturisation, the edge computing shift, software-defined networks and the sheer scale of IoT deployment – are continuing to evolve.

iSIM – Connectivity at the Chip Level

The logical endpoint of the eSIM journey is iSIM – Integrated SIM. Where an eUICC is a separate secure element chip added to the PCB alongside the cellular modem, an iSIM integrates SIM functionality directly into the application processor or cellular SoC.

iSIM delivers further miniaturisation, lower BOM cost and reduced PCB complexity. For ultra-compact IoT devices – wearables, smart labels, environmental sensors – eliminating the eUICC as a separate component is significant. iSIM operates under the same GSMA eSIM specifications as eUICC – SGP.32 is as relevant to iSIM deployments as to traditional eUICC ones.

5G RedCap and SGP.32

5G RedCap (Reduced Capability, 3GPP Release 17) is designed for IoT devices needing 5G features without full 5G bandwidth requirements. RedCap devices are natural SGP.32 candidates – typically headless devices deployed at scale. As RedCap module prices fall from the current $30-50 range toward $15-25 by 2026-2027, RedCap plus SGP.32 becomes an attractive combination for mid-tier industrial IoT.

Ambient IoT and Zero-Power Provisioning

3GPP Release 19 introduces Ambient IoT – backscatter and energy harvesting devices with essentially zero active power consumption. These devices are beyond the reach of even NB-IoT in terms of power budget. For true ambient IoT devices, provisioning models will need to evolve further – potentially near-field provisioning at deployment time or reader infrastructure handling connectivity on behalf of passive devices.

Edge Computing and the eIM at the Edge

As edge computing matures, eIM functionality will increasingly move closer to the devices it manages. An on-premise eIM running at a factory edge node can manage the eSIM profiles of thousands of factory floor sensors with lower latency, greater data sovereignty and independence from WAN connectivity.

This is where the intersection of private 5G, edge computing and SGP.32 creates genuinely new capabilities. A private 5G network with its own on-premise eIM can manage device profiles within the network boundary, switching devices between private and public cellular based on policy.

Software-Defined Connectivity

The longer-term trajectory of eSIM is connectivity as software. The vision – which Wireless Logic and others are articulating as programmable connectivity – is that enterprises define connectivity policy in software and the eIM/SM-DP+ infrastructure executes it automatically. A device crossing a border automatically acquires a local profile. A device reporting poor signal automatically switches to a better-performing operator. A device at end of life automatically has its profiles revoked.

SGP.32 is the enabling standard for this vision. The eIM architecture is the right foundation for software-defined connectivity at scale.

For the hardware ecosystem today, see the eSIM Hardware Guide.