Home Developers White label

Platform

SIM managementEvery subscriber, one consoleInsight toolsUsage, sessions and alertsConnectorsStream events to your cloudOpenVPN and IPsecPrivate tunnels to your networkSecurityPrivate APN and zero trustPrivate 5G and FWAYour own secure network

SIMs and network

ConnectivityOne network, every borderGlobal IoT SIMOne SIM for every marketIoT eSIMEmbedded and solder-downSGP.32 eSIM IoTRemote provisioning for fleetsVoiceReal, regulated phone numbers

Industries

IoTEvery device, one global SIMBusinessA subscriber for every employeeTravelBranded travel eSIM stores

Company

About SimsonicWhat we are and who it is forContactSales and support, one doorDevelopersGuides and the APIAPI docsEndpoints and examplesKnowledge baseHow it works, in detailGlossaryeSIM and IoT terms explainedBlogNotes from the networkManagement consoleSign in to Simsonic
Shop eSIMs & data plansOrder onlineShop now
PortalYour shopGet started
← All posts

SGP.32 explained: eSIM remote provisioning built for IoT

SGP.32 is the GSMA standard for eSIM in IoT devices that have no screen and no user. Here is what it changes, how the eIM works and why it matters for long-life fleets.

eSIM lets a device change mobile operator without a physical SIM swap. For phones, that is handled by the person holding the phone, who scans a QR code. IoT devices have no person and often no screen. SGP.32 is the GSMA standard that makes eSIM work for them.

Why IoT needed a new standard

Earlier machine-to-machine eSIM specifications worked, but they were built around tight integrations between operators and the platforms that managed profiles. Switching provider could be slow and complicated, which undermined the main promise of eSIM: freedom to change network after deployment.

SGP.32 is designed to make that switch practical at fleet scale.

How SGP.32 works

SGP.32 introduces two key pieces:

  • The eIM (eSIM IoT remote manager). A management service that tells devices which profiles to download, enable or delete. It can act on a whole fleet at once.
  • The IPA (IoT profile assistant). A small component in the device or the SIM that carries out those instructions locally.

Together they let a business manage eSIM profiles across thousands of headless devices remotely, with no user and no screen.

What it changes for you

  • Carrier choice after deployment. You can move devices to a different operator profile over the air.
  • Longer device life. A meter or charger built to last 15 years can outlive any single connectivity contract.
  • Simpler manufacturing. One hardware build can be shipped worldwide and given the right profile in each market.
  • Fleet-level control. Profile changes are driven centrally rather than device by device.

Who should care now

If you are designing hardware today that will be in the field for many years, such as smart meters, EV chargers, industrial sensors or vehicles, SGP.32 support is worth specifying now. Retrofitting connectivity choices later is far harder.

SGP.32 at Simsonic

Simsonic SGP.32 eSIM for IoT supports eIM-driven fleet provisioning and over-the-air carrier switching, managed from the same console as the rest of your estate. For a deeper look at the standard, read SGP.32: eSIM remote provisioning built for IoT, or see the industrial MFF2 IoT eSIM for hardware built to last.

More from the blogTalk to the team