CES2026
December 4, 2025
Lessons Learned While Going Through the SGP.32 eSIM Journey
TL;DR:
The SGP.32 eSIM standard represents one of the biggest advancements in IoT connectivity. It provides the ability to remotely update network profiles, comply with roaming rules, and run global fleets without touching the physical device. Simplex Wireless is one of the few companies operating as a truly independent EIM provider, meaning we are not tied to a specific mobile network operator or SIM manufacturer. This independence provides unmatched flexibility for IoT deployments, but it also introduces technical complexity when supporting the entire SGP.32 ecosystem. Over the past years of building a complete, in house EIM platform, Simplex Wireless has learned what works, what matters, and what every IoT provider should consider on their own SGP.32 journey.
Quick Navigation
Lesson 1: Independence Brings Flexibility and Complexity
Lesson 2: Building a Complete In House EIM Was Essential
Lesson 3: Carrier Grade Experience Shapes the Platform
Lesson 4: Supporting All IPA Variants Is Not Optional
Lesson 5: Architecture Must Be Multi Tenant, Redundant and Future Ready
Lesson 6: Operational Strength Matters as Much as Technology
Lesson 7: Rollback, Fallback and Bootstrap Profiles Are Mandatory
How Simplex Wireless Helps You Navigate SGP.32
Why SGP.32 Matters for IoT
SGP.32 is the first eSIM standard created specifically for IoT. Earlier versions addressed either machine to machine applications or consumer devices with user interfaces. SGP.32 combines remote management with automation and does so in a way that works for devices without screens, keyboards or human involvement.
For companies deploying thousands of devices, SGP.32 offers the practical ability to change subscriptions over the air, avoid truck rolls, meet regulatory requirements in countries that restrict permanent roaming, scale globally without redesigning hardware and introduce secure management policies that function for long term installations. This is why companies increasingly seek options that support SGP.32 out of the box, including the Simplex Wireless xoSIM which is built specifically for the modern IoT landscape. More information on xoSIM is available at the Simplex website at www.simplexwireless.com/xosim
Lesson 1: Independence Brings Flexibility and Complexity
Many eSIM providers are tied to a specific mobile network operator (MNO) or to a particular SIM card manufacturer (EUM). This limits the customer because the ecosystem becomes locked into a specific subscription source. Simplex Wireless operates differently. We intentionally chose to be independent of any particular carrier or EUM. This ensures that customers can use Simplex connectivity, use their own connectivity or even combine both approaches.
The benefit is significant. Customers retain choice. They can change strategies without replacing hardware. They are not bound to a single pricing model. They can keep existing operator contracts if they prefer. However, this flexibility comes at the cost of additional complexity for the platform provider. Supporting the entire SGP.32 ecosystem requires accommodating a wide range of IPA designs, modem behaviors, device architectures and provisioning flows. This was one of the first and most meaningful lessons learned.
Lesson 2: Building a Complete In-House EIM Was Essential
Simplex Wireless made a deliberate decision to build the EIM platform entirely in house. This choice ensures full control over feature development, upgrades, performance tuning and long term support. Many companies license the entire platform from external vendors which limits customization and slows innovation. For IoT projects with long life cycles, the ability to react quickly to new requirements is essential.
Because our EIM is built internally at our engineering center in Atlanta, we can introduce new capabilities without waiting for vendor roadmaps, maintain strict quality control and ensure deep knowledge of every system component. The platform is hosted in a private cloud environment with controlled, whitelist access for security. The independence of the infrastructure, combined with internal engineering ownership, provides customers with long term stability. More information about the Simplex EIM platform is available at www.simplexwireless.com/esim-iot-manager-platform.
Lesson 3: Carrier Grade Experience Shapes the Platform
Building a functional eSIM platform is not the same as building a carrier grade system. SGP.32 requires extremely high reliability. When devices rely on profile updates to restore connectivity, the underlying platform must remain available under all conditions.
The Simplex Wireless R and D team has spent more than two decades building and supporting mission critical systems for Tier 1 carriers. These systems include roaming steering platforms that process tens of thousands of transactions per second, device detection and analytics engines, entitlement systems and large scale messaging environments. This background influenced how the EIM was designed. Redundancy, failover, low latency paths and operational maturity were built into the system from the beginning. This experience was essential when implementing SGP.32 because the specification demands predictable, fault tolerant communication between the EIM, the eUICC and the IPA.
Lesson 4: Supporting All IPA Variants Is Not Optional
The SGP.32 standard allows several implementation variations for the IoT Profile Assistant, also known as the IPA. Devices may use IPAe, which runs inside the eUICC, or IPAd, which runs inside the modem or device firmware. Both must be supported. In addition, SGP.32 allows for multiple messaging formats, including normal and compressed profiles. It supports different communication bindings, including JSON and ASN.1. It also allows two provisioning models, direct download and indirect download.
To provide a truly flexible and independent solution, Simplex Wireless learned that every variant must be supported. Customers deploy a wide variety of hardware from numerous manufacturers. Modems behave differently. Some devices require indirect EIM communication while others communicate directly. Each permutation must function reliably. Implementing these capabilities was complex, but it ensures that customers can adopt SGP.32 without changing their hardware.
Lesson 5: Architecture Must Be Multi Tenant, Redundant and Future Ready
SGP.32 adoption is growing rapidly. Any platform supporting it must be designed for scale and long-term growth. Early in the design process, Simplex Wireless created a multi-tenant environment that allows customers to manage sub customers. This is important for OEMs, resellers and organizations with internal departments that operate autonomously. Each tenant receives isolated configuration, policy controls and access rights.
Redundancy was equally important. The platform is designed to remain operational even when individual components fail. Continuous monitoring, automated failover and distributed processing ensure that profile management can proceed even during maintenance or outages. Future readiness was also considered. The platform is structured so additional bindings, new device behaviors and new standard revisions can be incorporated without major redesign.
Lesson 6: Operational Strength Matters as Much as Technology
A reliable SGP.32 implementation requires more than software. It requires disciplined operations. Simplex Wireless provides ongoing, around the clock support to ensure customers receive timely assistance. Service level agreements, formal ticketing processes and quarterly business reviews help customers plan, evaluate performance and resolve complex challenges.
Because the EIM is hosted in a secured private cloud with controlled access, issues can be diagnosed without dependency on external hosting vendors. Internal engineering teams can observe real time system behavior, deploy updates rapidly and resolve issues quickly. This operational maturity has been one of the most important lessons learned. Customers need not only technology but also a dependable partner who supports them throughout the entire product lifecycle.
Lesson 7: Rollback, Fallback and Bootstrap Profiles Are Mandatory
The promise of eSIM is that devices can be updated remotely. However, if a profile installation fails or a device becomes unreachable, significant operational problems follow. During the development of the Simplex Wireless EIM, three features emerged as absolutely essential.
The first is rollback. If a device activates a new profile and loses connectivity, it must have the ability to revert to the previous profile so that it does not become permanently unreachable. The second is fallback, which ensures that temporary interruptions during downloads do not corrupt the profile. The third is the presence of a bootstrap profile. This minimal profile allows the device to maintain basic connectivity long enough to receive instructions from the EIM. These three concepts significantly reduce the risk of stranded devices and prevent costly field service visits.
How Simplex Wireless Helps You Navigate SGP.32
Companies evaluating SGP.32 face a range of questions about hardware compatibility, connectivity strategy, provisioning models and long term maintenance. Simplex Wireless provides guidance throughout this process. Because we are independent of mobile operators and SIM manufacturers, our customers retain full flexibility. They may use Simplex connectivity, use their own existing carriers or combine both approaches through the xoSIM Open SIM concept.
The Simplex EIM platform supports every major SGP.32 variant, including IPAe, IPAd, direct and indirect downloads and both JSON and ASN.1 bindings. The platform is engineered for scale, integrated with robust operations and developed entirely in house by a team that has built carrier grade systems for more than 20 years. More information about global connectivity options can be found at www.simplexwireless.com/global-iot-sim-card.
Takeaway
The journey to SGP.32 is not a simple one. It introduces new architectural possibilities, but also new technical challenges. Companies who adopt SGP.32 can achieve lower operational costs, better global compliance, more flexible deployments and dramatically improved long term scalability. The lessons Simplex Wireless learned while developing an independent, fully in house EIM illustrate the importance of deep technical expertise, real carrier grade experience and ongoing operational excellence.
Most importantly, SGP.32 should expand your options, not limit them. With an independent partner like Simplex Wireless, customers retain full control over their connectivity strategy and can design solutions that evolve as their business grows.
To begin your own SGP.32 journey, visit www.simplexwireless.com or contact our team directly at www.simplexwireless.com/contact.
This article was curated by Jan Lattunen, CCO Simplex Wireless
About the Author: Jan Lattunen manages Sales and Marketing for Simplex Wireless. Jan has 20 years’ experience in working with SIM card technology and was involved in launching the eSIM in North America with major carriers and OEMs. His expertise in telecommunications is around SIM cards. On a personal note, Jan is a family man and avid cyclist with advocacy for safety in the roads. You can connect with Jan on https://linkedin.com/in/JanLattunen