Why SGP.32 Matters for OEMs
Designing cellular IoT products for greater connectivity flexibility across the device lifecycle
Cellular connectivity decisions can outlast the design phase
For an original equipment manufacturer (OEM), selecting a cellular module is only one part of the connectivity decision. The larger challenge is maintaining flexibility after products move from prototype to production and into the field.
Coverage requirements can change. A customer may expand into a new market. Commercial relationships may evolve. A connectivity strategy that works during development can become a limitation later if changing a carrier profile requires a physical SIM swap, a site visit, or a redesign.
This is why SGP.32 matters. Developed by the GSMA for IoT, the specification provides a dedicated remote SIM provisioning model for devices that may have limited bandwidth, limited power, little or no user interface, and minimal local user interaction.
What is SGP.32?
SGP.32 is the GSMA eSIM IoT Technical Specification. It adapts remote SIM provisioning to IoT use cases and introduces two important architectural components:
- eSIM IoT Manager (eIM): The remote management component used to support eSIM profile operations.
- IoT Profile Assistant (IPA): The component on the device or eUICC that supports communication and carries out profile-related operations.
For OEMs, the significance is not simply that an eSIM is embedded in the product. The greater value comes from planning how approved connectivity profiles can be added, removed, or changed remotely as deployment requirements evolve.
OEM DESIGN QUESTION
What happens if the original connectivity choice no longer fits?
Ask this before the product architecture is locked, not after devices are deployed. Consider the ownership of profile management, supported providers, geographic requirements, fallback behavior, and the operational process for connectivity changes.
Four reasons OEMs should pay attention
1. Greater flexibility beyond initial deployment
SGP.32 creates a standardized path for remote eSIM profile management. This can give OEMs more options when approved connectivity requirements change over the product lifecycle.
2. A more adaptable approach to multi-market products
OEMs building for multiple regions often face different carrier and profile requirements. Remote profile orchestration can support a more flexible deployment strategy, although actual availability remains dependent on approved profiles, providers, coverage, and commercial terms.
3. Less dependence on physical SIM replacement
A remote provisioning model can reduce the need to treat every connectivity change as a physical intervention. This is particularly relevant for distributed devices or equipment installed in locations that are difficult or costly to access.
4. Connectivity becomes part of lifecycle planning
SGP.32 encourages OEMs to think beyond first activation. Product teams can consider how connectivity will be monitored, managed, and adapted alongside firmware, device operations, and customer requirements.
EXPLORE GENEVA
Evaluate SGP.32 orchestration as part of a complete embedded experience.
Plan for SGP.32 before the hardware is finalized
Treating eSIM as a late-stage component decision can leave important operational questions unresolved. OEM product and engineering teams should evaluate the connectivity model alongside the hardware and software architecture.
| Planning area | Question for the OEM team | Deployment footprint | Which countries, networks, and customer environments must the product support? |
|---|---|
| Profile ownership | Who controls profile selection, activation, switching, and support? |
| Device architecture | Will the IPA be device-based or eUICC-based, and what does that mean for integration and certification? |
| Fallback and recovery | What should happen when the preferred network or profile is unavailable? |
| Lifecycle operations | How will connectivity changes be coordinated with device management, firmware updates, and customer support? |
| Commercial model | Which profile providers, data plans, terms, and support boundaries apply? |
Connectivity should not become a fixed constraint after deployment.
SGP.32 gives OEMs a standardized framework for remotely managing approved eSIM profiles in IoT devices, helping product teams plan for changing connectivity needs without relying on physical SIM replacement.
From connectivity choice to connectivity strategy
The value of SGP.32 is not limited to replacing a removable SIM with an embedded one. It gives OEMs a framework for considering connectivity as a remotely manageable element of the product lifecycle.
That changes the design conversation. Instead of asking only, “Which carrier and module should we select today?”, OEM teams can also ask, “How will this product adapt when coverage, markets, customer requirements, or commercial priorities change?”
For manufacturers building long-life connected products, that flexibility can be an important part of creating a more resilient product strategy.
NEXT STEP
Put the connectivity strategy into practice.
