DS-MAY26-PG26+27_Layout 1 18/05/2026 11:34 Page 2


INTERNET OF THINGS (IoT)


FEATURE Modern hardware ‘alIve’


onboarding much more realistic, which is why they are becoming such a key foundation for industrial IoT design.


model than trying to retrofit security later. So if I had to summarise the challenge, I would


say IoT adoption is difficult because enterprises need to scale connectivity, security and visibility at the same time. Solutions like Cellular SASE matter because they help close that gap. They move security closer to the device, simplify operations, and give enterprises a unified way to protect IoT, OT and IT environments as they grow.


whAt is the gsMA sgp.31/.32 stAndArd And how does it iMpAct the iot ecosysteM? As an official GSMA member, we at Transatel believe that GSMA GP.31/.32 standards are important because they modernise how eSIM works for IoT. If I put it simply, earlier eSIM standards were built more around consumer devices or older machine-to-machine models, but IoT devices have very different needs. They are often constrained, deployed at scale, and expected to run for years with very little maintenance. What SGP.31 and SGP.32 do is move a lot


of the provisioning complexity away from the device and into the cloud. Instead of making the device handle a heavy remote provisioning stack, the IoT device only needs a lightweight assistant and an embedded eUICC. That matters a lot for industrial and connected devices because it reduces memory usage, software complexity, and integration effort on the hardware side. Another big change is that the provisioning


process is fully remote and does not require a user interface. That is a huge deal for IoT, because these are not phones or tablets where someone can tap through a setup flow. These are often sensors, trackers, controllers or gateways that need to come online automatically, sometimes in remote or hard to reach locations. The standards also use lightweight internet


protocols that fit constrained hardware much better, and they do not require SMS as part of the provisioning flow. From an ecosystem perspective, the real value is that SGP.31 and SGP.32 help reduce fragmentation. They make it easier for OEMs to build one device design and manage connectivity remotely across multiple operators and geographies. That means less SKU complexity, less physical SIM handling, fewer logistics headaches, and a better fit for long device lifecycles. So I would say SGP.31 and SGP.32 are


important because they shift eSIM from being a connectivity feature into being a scalable lifecycle management tool for IoT. They make global deployment, operator flexibility, and remote


www.designsolutionsmag.co.uk


how will Adopting the stAndArd chAnge how oeMs deploy connected devices? Adopting SGP.31 and SGP.32 changes the way OEMs deploy connected devices because it makes the whole process much more scalable and much less dependent on physical SIM logistics. Instead of designing around country-specific SIMs, manual onboarding, or operator-by-operator setups, OEMs can ship a single hardware design and manage connectivity remotely. That is a big shift, especially for devices that are deployed at scale and expected to work for many years. What really changes is that connectivity


becomes part of the deployment strategy from day one, not something added later as an operational workaround. With SGP.31 and SGP.32, devices can be provisioned and managed remotely through a much lighter architecture, which reduces complexity on the device itself and makes it easier to support global rollouts. For OEMs, that means fewer SKUs, fewer regional variants, and less friction when moving from pilot to production. It also improves flexibility over the device


lifecycle. If an OEM needs to switch operators, adapt to local regulations, or update connectivity strategy in the field, they can do that without redesigning the device or replacing hardware. That matters a lot in IoT, where devices are often installed in remote places and are not easy to touch again once they are deployed. The standard helps OEMs move from a


fragmented deployment model to a more unified one. It makes connected devices easier to manufacture, easier to activate, easier to manage, and easier to keep compliant over time. In my view, that is why SGP.31 and SGP.32 are such an important step for large-scale IoT deployment.


trAnsAtel provides bootstrAp connectivity. whAt is this? whAt does it do? And why is it needed for iot? In simple terms, Transatel’s Bootstrap connectivity is the initial connectivity profile that gets a device online the moment it comes out of manufacturing. It is preloaded into the device so the product can connect immediately, without waiting for manual setup, QR-code scanning, or a technician to intervene. What it does: Bootstrap connectivity gives


the device its first path to the network, so it can complete essential early-life tasks such as profile download, activation, diagnostics, and remote management. This bootstrap profile can also remain available as a backup, which helps support OTA firmware updates, security updates, diagnostics, and future profile changes over the device lifecycle. Why it matters for IoT: It is needed because


IoT devices are often deployed at scale, in remote locations, and with long lifecycles, so


you cannot rely on manual activation or field servicing. Bootstrap connectivity is a way to reduce SIM logistics, remove activation delays, support one global SKU, and make out-of-the- box deployment much simpler across 200+ countries and territories. Why it is useful for OEMs: For OEMs, the big


benefit is that bootstrap connectivity helps shift IoT from a fragmented shipping-and-setup process to a more automated, factory-to-field model. That means fewer regional variants, less operational overhead, and a more reliable way to onboard devices, especially when connectivity needs to be maintained over many years.


Are there Any other points you think oeMs need to know About bootstrAp connectivity or the ecosysteM At lArge? Yes, there are a few important things OEMs should keep in mind beyond the basic idea of bootstrap connectivity. First, bootstrap is not the same thing as the final operational profile. Its job is to get the device online securely and automatically, but OEMs still need a clear plan for how the device moves from first connection to its long-term connectivity setup. That transition matters because it affects onboarding, operator choice, cost, and lifecycle control. Second, OEMs should think about bootstrap


as part of the full device lifecycle, not just manufacturing. It helps with factory activation, remote provisioning, OTA updates, diagnostics, and later profile changes, so it becomes a long-term operational enabler rather than just an install step. That is especially important for devices that may stay in the field for 10-15 years. Third, the ecosystem matters a lot. Bootstrap


works best when it is aligned with the newer IoT eSIM standards, especially the move toward SGP.31/32-style architecture and factory provisioning models. In practice, that means OEMs should check interoperability, profile management flow, and whether the solution supports multi-operator flexibility rather than locking them into a single network path. Bootstrap can also help simplify hardware


strategy. If OEMs design around one global SKU and rely on bootstrap connectivity to handle first activation, they can reduce regional variants, SIM logistics, warehousing, and manual provisioning errors. That is a big advantage when deploying at scale. Finally, OEMs should not think about


connectivity in isolation from security and operations. Bootstrap gives them a cleaner starting point, but they still need secure provisioning, remote visibility, policy control, and a way to manage devices across countries and carriers. That is where the real value comes from, because the goal is not just to connect a device once, but to keep it secure, manageable, and adaptable throughout its life.


Transatel www.transatel.com


Join Transatel’s webinar on 11th June at 1pm: https://designsolutionsmag.co.uk/category/webinars MAY 2026 deSIgn SolUTIonS 27


Page 1  |  Page 2  |  Page 3  |  Page 4  |  Page 5  |  Page 6  |  Page 7  |  Page 8  |  Page 9  |  Page 10  |  Page 11  |  Page 12  |  Page 13  |  Page 14  |  Page 15  |  Page 16  |  Page 17  |  Page 18  |  Page 19  |  Page 20  |  Page 21  |  Page 22  |  Page 23  |  Page 24  |  Page 25  |  Page 26  |  Page 27  |  Page 28  |  Page 29  |  Page 30  |  Page 31  |  Page 32  |  Page 33  |  Page 34  |  Page 35  |  Page 36  |  Page 37  |  Page 38  |  Page 39  |  Page 40  |  Page 41  |  Page 42  |  Page 43  |  Page 44  |  Page 45  |  Page 46  |  Page 47  |  Page 48  |  Page 49  |  Page 50  |  Page 51  |  Page 52