By: Dr. Philipp Schulte

For more than a decade, the automotive industry has been transforming into a software-defined ecosystem, where vehicles evolve through software updates, digital services, and continuous performance improvements. The scale of that transformation is massive. As of last year, more than 400 million connected cars are on the road globally, with connectivity quickly becoming a baseline expectation for modern vehicles. At the center of this transformation is connectivity. And with the recent finalization of the GSMA’s SGP.32 specification, the industry has reached an important inflection point in how vehicles connect to mobile networks globally. 

The Growing Complexity of Automotive Connectivity 

Modern electric and software-defined vehicles rely on constant, secure connectivity to enable OTA updates, real-time diagnostics, ADAS enhancements, infotainment, telematics, and data-driven upgrades throughout the lifecycle. The complexity of these platforms is already immense. Today’s vehicles can contain more than 300 million lines of code and generate up to 25 gigabytes of data per hour from sensors, telematics systems, and in-vehicle applications³.  

As automakers expand globally, this creates a logistical challenge: mobile network operator (MNO) requirements vary by country and region. Historically, supporting multiple markets often meant different hardware configurations, different SIM profiles, and region-specific integrations.  

That adds cost, operational overhead, and long-term rigidity – particularly for vehicles expected to remain in service for 10 years or more. What once worked for regional launches and fixed architectures no longer scales in a global, long‑lived vehicle fleet. SGP.32 marks a shift from static connectivity choices to a framework where decisions can be managed, governed, and adapted over a decade or more of vehicle operation. 

What Makes SGP.32 Different? 

SGP.32 is the GSMA’s new eSIM specification designed specifically for IoT and automotive use cases. While earlier consumer-focused eSIM standards worked well for smartphones, vehicles present a fundamentally different set of requirements, including long lifecycles, multi-network flexibility, scalable remote management, and secure cross-border operation. 

SGP.32 introduces a streamlined remote eSIM provisioning architecture tailored for these needs. It enables secure, over-the-air management of operator profiles without requiring physical access to the vehicle. Unlike earlier approaches, the architecture is designed to operate natively in distributed, resource-constrained IoT environments, reducing dependency on complex backend integrations. 

Early adoption is already emerging across the industry. For example, electric vehicle manufacturer Rivian announced that its upcoming R2 vehicle will support the SGP.32 standard, demonstrating how automakers are beginning to integrate the specification into next-generation vehicle architectures.  

For automakers, this unlocks the ability to deploy a single global hardware SKU, add or change mobile network providers over time, expand into new regions without redesigning connectivity hardware, and retain full control over connectivity strategy throughout the vehicle lifecycle. 

Connectivity is no longer defined entirely at production, but it remains an active design variable long after vehicles are on the road. 

SGP.32 vs. Previous Standards: A Necessary Evolution 

To fully understand the significance of SGP.32, it is important to compare it with earlier specifications such as SGP.02, which was originally designed for M2M use cases. While SGP.02 enabled remote SIM provisioning, it relies on a more rigid, operator-centric architecture with limited flexibility for dynamic, large-scale IoT deployments. 

That rigidity was intentional and appropriate for an earlier phase of connected mobility, prioritizing stability over adaptability. As vehicles increasingly behave like software platforms, however, the balance shifts toward continuous optimization across networks and regions. As a result, SGP.32 is not just an incremental upgrade – it fundamentally improves how connectivity can be orchestrated, making it better suited for software-defined vehicles and global deployment strategies. 

The Strategic Importance of a Single-SKU Model 

One of the most significant implications of SGP.32 is the move toward a single-SKU hardware strategy.