SGP.32 and the Future of Connected Device Manufacturing

Even the most casual observer can tell that the telco industry is going through a massive shift, fundamentally changing how network operators, OEMs, and enterprises handle their remote deployments.

For a long time, any smart-device launch would have to contend with a fragmented connectivity model, meaning that building the physical hardware and sorting out network access were two completely different headaches. Then, for a while, GSMA standards progressed to a point where it was just a single headache. By today, those same standards have completely reframed the approach, both overcoming the hardware/software divide and turning pitfalls into advantages.

To appreciate how far the model has come, it’s handy to focus on the journey of a single device. For today, let’s say it’s a humble industrial temperature sensor, a robust, specialized battery-powered little tracker keeping an eye on cold-chain logistics across international borders.

In the past, this sensor's global lifecycle would create numerous logistical issues. Getting it market-ready meant juggling regional hardware variants, fighting through complex customs rules, and then trying to budget for field engineers to do intermittent physical SIM card swaps.

While there are still a lot of hard-working legacy fleets propping up whole markets, thankfully the day of the plastic SIM is fading fast. This truly came into effect with the GSMA SGP.32 spec. Built specifically for the needs of low-power, autonomous devices, this framework gives us a unified architecture that neatly bridges the gap between hardware assembly and network orchestration.

We’re going to follow our little temperature sensor as it journeys from a factory floor in Asia to a busy shipping port in South America, and through years of non-stop operation, to see just how massive the business impact of SGP.32 has been.

Connectivity is now part of the hardware

For decades, the golden rule in smart-device manufacturing was that cellular connections are addressed at the last second. OEMs would simply build the device and leave an empty slot on the circuit board. Only when they finally knew exactly where the device was going would someone manually slot in a localized, plastic SIM card on the warehouse floor. If a bulk order of sensors was split between clients in Europe and North America, assembly lines had to split, inventory was divided, and region-specific SIMs were carefully inserted. The danger here was that with just a tiny little SIM mislabeling issue, you could have thousands of devices heading for a destination where they’d arrive, boot up, and then sit there like a brick.

The industry first attempted to fix this with older remote provisioning standards, but they were pretty clunky for autonomous assets. The legacy M2M standard SGP.02 leaned heavily on SMS protocols to push network updates. That was already a non-starter for modern, low-power assets using NB-IoT or LTE-M networks, which frequently drop into deep sleep modes to save battery and would consider the power drain of processing SMS messages a wild extravagance. On the other hand, the consumer standard SGP.22 required a human to press a button or scan a QR code — which is useless for our temperature sensor, nestled deep inside a perishable goods shipping container.

SGP.32 completely reframed the model, having been specifically designed for the Internet of Things. With it, manufacturers don't have to treat network access like an aftermarket add-on. Instead, connectivity is welded right into the hardware from day one. OEMs can embed a unified single eUICC directly on to the circuit board, which is initialized with the operator's profile ether during manufacturing, or simply in the field by remote installation of a QR-code, which is a leap forward for IoT OEM connectivity.

That means our heroic temperature sensor now rolls off the line in Shenzhen fully equipped and ready to connect anywhere in the world. By shifting the point of control on connectivity from SIM vendors and MNOs to OEMs, SGP.32 ditches the need for physical hardware tweaks, moving the whole connectivity model from physical logistics to digital orchestration.

Connectivity as a component

To appreciate what an upgrade this is, it’s useful to remember how much of a drain legacy SIM logistics were on supply chain budgets. Making multiple hardware variants for different operators, frequency bands, or local rules forced manufacturers to hold complex, expensive inventory. Keeping up with regional demands and predicting their shifts meant tying up capital in specialized hardware that was tough to repurpose if the market changed.

With SGP.32, the SIM card is no longer a localized token. From a hardware design point of view, it’s simply just another electronic component, soldered onto our temperature sensor’s board right next to its microprocessor and antenna. Instead of juggling dozens of regional versions, manufacturers can now build it as a single global SKU with or without embedded bootstrap connectivity. Every device on the line next to it is identical, all equally unbothered by wherever they might end up.

For the business building our favorite temperature sensor, this unified approach cuts down on the total cost of ownership. The factory can machine hundreds of thousands of sensors, each with an embedded chip running a universally recognized identity called the eUICC Identifier (EID). When a logistics client drops an order for ten thousand sensors for a new multi-continent shipping route, the warehouse simply boxes and ships the right size stack from inventory. No sealed casings to crack open or SIMs to swap, wrangle local operator contracts during manufacturing, or sweat over customs delays caused by mismatched hardware. Network profiles are handled digitally, when and where they're needed, keeping the supply chain agile and moving.

The greater flexibility SGP.32 unlocks

Having left the Shenzhen factory and slept through a trip around the world to Brazil, the second our intrepid temperature sensor is powered up in Porto de Santos, the new GSMA spec kicks in. The IoT-specialist GSMA standard enables secure, remote profile orchestration even for constrained IoT devices, allowing connectivity to adapt as commercial agreements, regulations, and deployment locations change over time.

This flexibility comes from ditching the cumbersome, SMS-dependent methods of previous device generations. The engines of this new standard are two components specifically built to optimize Remote SIM Provisioning (RSP) for battery-dependent hardware: the eSIM IoT Manager (eIM) and the IoT Profile Assistant (IPA). The IPA is essentially the smart control layer that replaced all the human input needed by the consumer app, operating without any external help. Depending on how the hardware is designed, this assistant can live in the device's software (IPAd) or directly on the eUICC chip (IPAe), meaning that it’ll integrate easily even with older hardware.

When our world-travelling sensor, previously of Shenzhen and now of Porto de Santos, is connected and now considers that it has something to report, the IPA sets up an encrypted connection to the centralized eIM server. A powerful feature of SGP.32 is its support for lightweight protocols like Constrained Application Protocol over User Datagram Protocol – which is shortened to ‘CoAP over UDP’.

By chatting over UDP instead of power-hungry and data-heavy TCP/IP or SMS, the sensor uses far less battery and memory, adding years to its lifespan in the field. This frugal design means that as our device continues to travel the globe, diligently monitoring temperatures wherever it goes, the main orchestration platform will keep pushing essential commands and updates, like new profiles or security tweaks, without draining the power cell. The result is that its parent enterprises maintain dynamic control over their sensor, no matter how far afield they are.

Better manufacturing, simpler operations

Once our temperature sensor left the factory of its birth and ventured out into the global supply chain, operational resilience and adaptability became its most essential feature.

When our sensor landed in Brazil, got unpacked, slapped onto a refrigerated container, and powered on, it was expected to hit the ground running. Local port workers don't have the time, training, or inclination to mess with manual configs or hunt around in the packaging for a QR code to scan. Instead, the sensor boots up using its pre-loaded bootstrap profile. This bootstrap is a rugged, globally roaming profile that acts as a temporary bridge to the internet.

This initial connection is hyper-efficient and comes with just enough connectivity to get things going. The sensor uses the bootstrap to say hello to the local network and share its location with the eIM platform. The backend systems see the sensor is now in South America and instantly orchestrate the download of a locally optimized Brazilian operator profile. The moment this operational profile is safely downloaded, the device automatically turns off the roaming bootstrap and switches to the local network. As far as connectivity is concerned, our device is now as Brazilian as if it were born there. Olá!

Thanks to this automated sequence, ops teams are entirely free from the tangle of manual onboarding. They can watch thousands of sensors come online globally from a ‘single pane of glass’ dashboard, confident that every asset will start speaking the local language and adapt to its new home. It brings previously undreamed-of predictability to IoT deployments and connectivity management, turning what used to be stressful, high-risk global rollouts into standard, everyday software operations.

A better model for OEMs and enterprises

Over the sensor's five-to-ten-year lifespan, the strategic value of this flexible architecture becomes a huge competitive advantage. Long-term IoT deployments will inevitably hit bumps in the road as infrastructure ages, carrier contracts (or whole carriers) expire, and data legislation shifts.

A previously longstanding issue for global fleets was permanent roaming restrictions. Many regions have rules that foreign SIMs roaming on local networks for too long, usually 90+ days, are kicked off permanently. Until recently, that would have turned our travelling temperature sensor into a decorative rock, along with the rest of the fleet. SGP.32 made this dire regulatory risk a thing of the past. Since the hardware and network provisioning are separate, an enterprise can (and should) digitally swap that roaming profile for a fully compliant local one long before any deadlines hit.

OEMs gain a simpler production process and a globally deployable product, while enterprises retain the flexibility to select, change, and optimize connectivity long after devices leave the factory. If a primary profile goes completely offline, SGP.32 is also a safety net as the sensor can revert back to its trusty bootstrap profile, reconnect, and ask for new instructions.

Another of the issues this framework fixed was the vendor lock-in inherent to plastic SIM cards. Instead, enterprises can manage global fleets without jumping between five different vendor dashboards, and can negotiate better rates knowing they can easily and cheaply switch carriers over the air, and execute complete IoT profile management strategies that treat connectivity like fluid software, not a stubborn piece of hardware.

Orchestrate IoT connectivity with the 1GLOBAL eIM

Administering all these sophisticated GSMA features requires a rock-solid, enterprise-grade control center. While heroically hard-working, our sensor is only as smart as the platform coordinating its capabilities. Fully compliant with the GSMA SGP.32 standard, 1GLOBAL's unique platform is built to give you granular zero-touch control over massive fleets, all the way down to individual sensors, ensuring your operations are as efficient as possible.

Through 1GLOBAL’s centralized profile management, remote provisioning, bootstrap connectivity, and robust lifecycle control, OEMs and enterprises can deploy globally while maintaining complete control over connectivity from manufacture to retirement. The 1GLOBAL eSIM IoT Manager (eIM) acts as your comprehensive command center, talking effortlessly with the device-side IoT Profile Assistant (IPA). When our temperature sensor wakes up in the next country after Brazil, the platform will securely handle the transaction, using cryptographic authentication between the eUICC and the server to keep your data and settings locked down.

For the logistics admins, the workflows are intuitive. 1GLOBAL’s platform offers a clean central portal for everyday oversight, plus robust APIs for heavy-duty automation. Fleet managers can import, activate, and delete operator profiles in under two minutes. This kind of agility means reacting to network outages or new regs in real-time, all without ever sending a technician into the field.

1GLOBAL guarantees you true operator independence, with the bootstrap profile serving as a reliable foundation, while local profiles are constantly optimized for the best network performance and cost. It’s a next-gen solution that ensures the future of IoT eSIM management stays flexible and resilient, finally freeing businesses from the old logistical headaches that used to hold global device manufacturing back.

Contact the 1GLOBAL IoT team today to learn more.