The Trusted Connectivity Alliance (TCA) defines the format used to package eSIM profiles. The GSMA’s SGP.32 specification defines how those profiles are remotely provisioned and managed on IoT devices. A common package format means compatible eUICCs can interpret profiles from different operators and suppliers, which is a big part of why SGP.32 works at all. It doesn’t guarantee that every profile will install and run on every chip, though. That still depends on which profile features the eUICC supports, whether the operator will supply a profile for your device, and how your eIM, IPA and SM-DP+ are set up. So before you roll out a fleet, get your supplier to show you the operator profiles you want being downloaded, enabled and used on the actual equipment you’re buying. This piece explains who writes which part of the eSIM rules, where TCA fits, and what to ask.
Trusted Connectivity Alliance at a glance
- What it is: a global, non-profit industry association for SIM, eSIM and secure element technology. It grew out of the SIMalliance in 2020 and opened its membership beyond traditional SIM makers.
- Its most important document: the eUICC Profile Package: Interoperable Format Technical Specification, first published in 2015. Version 3.4 was released in March 2025, and TCA’s specification library now lists technical specification v3.4.1 (May 2025) and test specification v3.4 (February 2026).
- Why SGP.32 needs it: it standardises the format of the profile operators load onto an eUICC, so compatible eUICCs from different vendors can interpret the same profile.
- Who is in it: 14 members listed on its members page in November 2026, including Thales, Giesecke+Devrient, IDEMIA, Kigen, NXP, STMicroelectronics and Valid.
- How big: TCA says its members represent around 85% of the global eSIM hardware market. It estimated 605 million eSIMs shipped worldwide in 2025, up 18%. That figure covers all eSIM hardware, phones included, not just IoT. For SGP.32 specifically, TCA points to a strong rise in the number of subscription management platforms supporting SGP.32 profile downloads.
Who writes the eSIM rules? The layers and their authors
Here is the thing that confuses people. There is no single “eSIM standard”. There is a stack of specifications from different bodies, and SGP.32 sits on top of all of them. I find it easiest to picture as layers, from the radio network at the bottom to the paperwork that proves a product complies at the top.
| Body | What it writes | Where you meet it in SGP.32 |
|---|---|---|
| GSMA | The remote SIM provisioning architecture and technical specs: SGP.21/22 (consumer), SGP.31/32 (IoT), SGP.41 (in-factory) | The eIM, the IPA, the SM-DP+, and how profiles are downloaded, enabled and deleted |
| Trusted Connectivity Alliance | The interoperable eUICC profile package format and its test specification | The structure of the operator profiles your eUICC receives |
| ETSI TC SET | The UICC platform the SIM runs on; called TC SCP until January 2022 | The card’s commands, files and interfaces, underneath everything else |
| GlobalPlatform | Secure element card specifications, secure channel protocols and remote application management | How applications and files on the eUICC are managed remotely, and parts of eUICC testing |
| 3GPP | The network side, including the USIM application and network authentication | What happens once a profile is enabled and the device attaches |
| GSMA compliance | The SGP.24 compliance process and SGP.33 test specifications | Functional compliance evidence for the eUICC, eIM and other components |
| GSMA SAS | Security Accreditation Scheme for production sites (SAS-UP) and subscription management sites (SAS-SM) | Whether the factory that made your eUICC and the site running your SM-DP+ are accredited |
Sources: GSMA eSIM specification status pages and SGP.24; TCA; ETSI; GlobalPlatform. Simplified for buyers.
If you want the architecture side first, our SGP.32 architecture guide covers the eIM, IPA and eUICC, and SGP.31 vs SGP.32 explains the split between the GSMA’s architecture and technical documents.
What the Trusted Connectivity Alliance does for SGP.32
Think of an operator profile as a parcel. The GSMA’s specs describe the delivery service: who is allowed to send it, how it is addressed to one specific chip, how it is signed and who confirms it arrived. TCA’s spec describes what is inside the box and how it is packed, so a compatible chip at the other end knows how to unpack it.
The analogy has a limit worth stating. A standard box doesn’t mean every recipient can use every item inside it. If a profile relies on features the eUICC doesn’t support, or the operator won’t issue a profile for your device type, or the eIM and SM-DP+ aren’t set up to work together, the parcel still won’t arrive usable. The common format removes one big source of incompatibility. It doesn’t remove all of them.
That still matters a great deal. Before a common format, operators had to deal with each SIM vendor’s way of doing things. Now they build to one interoperable format that compatible eUICCs understand. You can see how deeply it is wired in from the GSMA’s own documents:
- The GSMA’s SGP.24 compliance process (v2.7, July 2026) lists TCA’s profile package technical and test specifications as references.
- SGP.41, the in-factory provisioning architecture, requires TCA profile package v3.1 or higher.
- The GSMA’s eSIM test specifications reference TCA’s profile package test specification as an external test to be run on the eUICC.
Version 3.4 of the profile package spec brought two changes that matter for IoT. It aligned with 3GPP Release 18, including support for 5G network slicing authentication. And it added support for GlobalPlatform’s Secure Channel Protocol Amendment M, which GlobalPlatform describes as enabling remote application and file management on secure elements in constrained IoT devices and low-power networks, such as NB-IoT devices without SMS. That is about managing applications and files on the chip. It is separate from SGP.32’s own profile download, enable and delete operations.
Why an alliance, and not just the GSMA?
The GSMA is, at heart, the operators’ association. The people who actually build SIMs and secure elements needed their own place to agree technical detail without handing every decision to their biggest customers. That was the SIMalliance. In 2020 it became the Trusted Connectivity Alliance and opened its doors to chip makers, IP vendors and others across the SIM supply chain, because by then the SIM was turning into an eSIM, an iSIM and a secure element inside the processor.
In practice the two work together. TCA’s board chair, Guido Abate of STMicroelectronics, also chairs one of the GSMA’s eSIM working groups, and the two bodies have run a joint webinar on SGP.32. That overlap is normal in this industry. The same few dozen engineers sit in most of these rooms. I’ve written more about why industries form these clubs in the first place, from the 450 MHz Alliance to O-RAN, in why telecoms alliances exist on IoTPortal.
TCA does more than the profile spec. It publishes annual eSIM market figures from member shipments, a guide for Java Card applet developers on eSIM interoperability, and in May 2026 it published the first common lifecycle assessment methods for measuring the environmental impact of SIM and eSIM products.
The buyer acceptance test that matters most
Here is the test I’d put in front of any supplier before signing. Picture a remote pumping station: a router with an eUICC, a bootstrap profile, and a second operator’s profile you expect to switch to one day. Ask the supplier to prove it, on the exact hardware and firmware proposed for your rollout:
- Download and enable a second operator profile using the eIM, IPA and SM-DP+ your fleet will actually use, not a lab setup.
- Confirm the device reconnects on the new profile and your application traffic resumes: telemetry flowing, remote access working, firewall rules and APN settings correct.
- Show a controlled failure. Switch to a profile that can’t connect, and demonstrate how the device recovers, whether through fallback, rollback or the eIM, without anyone driving to site.
If a supplier can do all three on your kit, the standards have done their job. If they can only show you a slide or a membership logo, you haven’t tested anything yet. Our pieces on bootstrap issues and modem compatibility explain where this usually goes wrong.
What to ask your supplier
On top of the acceptance test, and our checklist for eSIM providers, I’d ask for these by name:
- The exact eUICC model and the SGP.32 version it has functional compliance evidence for.
- The TCA profile package versions it supports, and evidence it has passed the TCA profile package test specification.
- The eUICC production site’s SAS-UP accreditation, including its scope.
- The SM-DP+ site’s SAS-SM accreditation, including its scope.
- The eIM’s applicable security and compliance evidence.
- Which operator profiles are actually available for your device type and countries today, named and in writing.
Functional compliance and site security accreditation are different things, so ask for both separately. A compliant chip made in an unaccredited site, or an accredited site running an untested platform, isn’t the full picture.
The Trusted Connectivity Alliance members, and where they sit
These are the 14 members TCA lists in November 2026. I’ve grouped them by the job they do in the eSIM supply chain, because that tells you more than the logo. Where we have already covered a member’s SGP.32 story, I’ve linked it.
| Member | Role in the eSIM chain | SGP.32 relevance |
|---|---|---|
| Thales | SIM, eSIM and eUICC maker, subscription management | eUICCs and eIM services; see Thales, Singtel and Bridge Alliance |
| Giesecke+Devrient | SIM, eSIM and eUICC maker, subscription management | eUICCs and remote management platforms |
| IDEMIA | SIM, eSIM and eUICC maker, subscription management | Part of the Tele2 IoT and Cisco SGP.32 service launched in March 2026 |
| Valid | SIM and eSIM maker | eUICCs and provisioning services |
| Eastcompeace | SIM and smart card maker | eUICC supply |
| Kigen | eUICC operating system and eIM provider | The OS inside many IoT eUICCs; see Kigen and SGP.32 |
| NXP Semiconductors | Secure element and eSIM silicon | The chip under the eUICC OS |
| STMicroelectronics | Secure element and eSIM silicon | The chip under the eUICC OS |
| Redtea Mobile | eSIM platforms and connectivity services | Runs a GSMA-certified SM-DP+ and sells SGP.32 eSIM solutions |
| COMPRION | SIM and eSIM test tools | Testing eUICCs and devices against the specs |
| Linxens | Smart card modules and components | Physical SIM and eSIM packaging |
| Card Centric | Listed member | Profile to follow |
| Monty Mobile | Listed member | Profile to follow |
| Trasna | Listed member | Profile to follow |
Source: TCA members page, November 2026. Grouping and SGP.32 notes are sgp32.co.uk analysis.
Two things stand out. First, the silicon and the chip OS are separate members. That split is exactly where one of the four locks in our UK SGP.32 landscape sits: the eUICC OS is fixed at manufacture, whoever made the silicon. Second, most of the members who run eIMs are also eUICC makers. That’s worth knowing when a chip vendor offers to manage your fleet as well.
What it means for lock-in
A common profile format takes a lot of friction out of moving between operators. That’s precisely why, as I argued in SGP.32 didn’t end operator lock-in, it moved it, the lock now tends to sit elsewhere: in the eIM, the bootstrap profile and the eUICC OS. Standards bodies narrowed one door, and the commercial world built new ones next to it. The acceptance test above is how you find out which doors are open on your fleet.
If you’re new to all this, start with what SGP.32 is, then the SGP.32 glossary for the acronyms. For the chip itself, our sister site euicc.co.uk goes deeper, and IoTPortal has a plain-English guide to what an eUICC is.
My take
Every standard has a layer nobody writes press releases about, and in eSIM it’s the profile package. It’s a file format with no logo, no launch event and no keynote. It’s also a large part of the reason an operator in Norway and a chip made in France can meet on a router in a remote pumping station at all.
But a shared format is a starting point, not a guarantee. The real proof is a profile switch working on your hardware, with your platform, in front of you. I’ll be profiling the TCA members with a real SGP.32 story over the coming weeks, starting with the eUICC makers.
Quick answers
What is the Trusted Connectivity Alliance?
The Trusted Connectivity Alliance (TCA) is a global, non-profit industry association for SIM, eSIM and secure element technology. It evolved from the SIMalliance in 2020 and its members include Thales, Giesecke+Devrient, IDEMIA, Kigen, NXP, STMicroelectronics and Valid.
What does TCA have to do with SGP.32?
TCA writes the eUICC Profile Package: Interoperable Format specification, which defines how operator profiles are packaged. Compatible eUICCs can interpret profiles in this format from different operators. Whether a specific profile installs and works also depends on supported profile features, operator availability and the eIM, IPA and SM-DP+ setup.
Does a common profile format mean any operator profile works on any eUICC?
No. It removes a major source of incompatibility, but installation also depends on the eUICC supporting the profile’s features, the operator issuing a profile for your device, and the provisioning platforms working together. Ask suppliers to demonstrate the profiles you need on your actual hardware.
Is TCA the same as the GSMA?
No. The GSMA writes the remote SIM provisioning specifications, including SGP.31 and SGP.32. TCA writes the profile package format and its test specification, which the GSMA’s compliance process references. The two bodies work closely together.
What is the latest version of the TCA profile package specification?
TCA’s specification library lists the eUICC Profile Package: Interoperable Format Technical Specification at v3.4.1 (May 2025) and the matching test specification at v3.4 (February 2026). Version 3.4 of the technical specification was first released in March 2025.
Who are the members of the Trusted Connectivity Alliance?
In November 2026 TCA lists 14 members: Card Centric, COMPRION, Eastcompeace, Giesecke+Devrient, IDEMIA, Kigen, Linxens, Monty Mobile, NXP Semiconductors, Redtea Mobile, STMicroelectronics, Thales, Trasna and Valid.
Which standards bodies are behind eSIM?
The main ones are 3GPP for the network and USIM application, ETSI TC SET for the UICC platform, GlobalPlatform for secure element management, the Trusted Connectivity Alliance for the profile package format, and the GSMA for remote provisioning, compliance and security accreditation.
Sources: Trusted Connectivity Alliance (about, members and specification library pages; eSIM market data, March 2026; lifecycle assessment release, May 2026); TCA profile package v3.4 release coverage (March 2025); GlobalPlatform, remote management for constrained IoT devices and networks (May 2024); GSMA eSIM specification status pages, SGP.24 v2.7 (July 2026) and SGP.41 v1.0; ETSI TC SET committee page. Diagram by sgp32.co.uk.