Device type green: supported red: not supported	Most personal consumer devices	Some personal consumer devices - mainly watches	M2M devices	IoT devices	(Consumer) devices with pre-loaded eSIM profile
	All smartphone, pads, laptops, some, watches, etc.	Apple Watch, case-by-case also some other watches (not all)	Automotive TCUs, metering devices, etc.	Same as M2M devices	Some routers, (some) dog trackers, etc.
Remote SIM Provisioning according to which GSMA specification?	GSMA SGP.22	GSMA SGP.22	GSMA SGP.02	GSMASGP.32	N/A
Reason for not supporting		Business rules, implemented by OEM in device, prevent to load test profiles and/or profile download proceedure requires additional infrastructure elements which go beyond what the GSMA eSIM specs define. Fo a particular device/watch, these arguments may apply in one market while this is not the case in other markets.	Device has an exclusive 1:1 relationship with a given RSP backend service. No other RSP service can interfere.		No Remote SIM Provisioning supported or disabled
Remarks		COMPRION cannot provide guidance which watches can or cannot be served as this is to fragmented and potentially subject to changes.	Solutions for this type of devices will more and more use the GSMA SGP.32 spec for IoT devices and not the former for M2M devices any more due to weaknesses in the old M2M spec. However, this will evolve gradually as COTS products according to the GSMA.32 IoT spec will only become available in 2025

 What are the indicators that a device is in the "consumer device" category?

• It is a smartphone, a watch, a pad or a laptop.
• Its data sheet points to the GSMA SGP.22 specification for Remote SIM Provisioning.
• Its data sheet talks about a "consumer eSIM or eUICC".
• It allows to scan a QR code with a camera to load the eSIM profile.

What are the indicators that a device is in the "M2M device" category?

• It does not allow to scan a QR code or to enter an activation code text string to download an eSIM profile.
• Its data sheet points to the GSMA SGP.02 specification for Remote SIM Provisioning.
• It is a small scale and/or embedded device.
• It serves typical M2M use cases (metering, remote control of devices, ...).
• The device was launched 2024 or earlier (but also some later devices will be in this category).

What are the indicators that a device is in the "IoT" device category?

• It is a device which was launched 2025 or later.
• its data sheet points to the GSMA SGP.32 specification for Remote SIM Provisioning.
• it is a small scale and/or embedded device (same as M2M).
• it serves typical M2M use cases (metering, remote control of devices, ...) (same as M2M).

 

Besides beeing in one of the device categories, which can be supported, your device must not have special test certificates in its eSIM according to GSMA SGP.26. It is very unlikely that you have such a device if you did not explicitely sourced it with this feature (such devices cannot be purchased on the open market).

What Profiles are available?

Out-of-the-box, we provide profile packages with profiles according to the following types:

• GSMA TS.48 Version 4.0 (currently our default) or V5.0 – all different flavors: SAIP 2.1 / 2.3 with or without BERTLV
• Rohde&Schwarz GSMA Test Profile, T-Mobile US Profile DISH US Profile (availability requires approval from Rohde & Schwarz)
• Anritsu RTD LTE Profile and RTD 5G Profile as well as T-Mobile US Profile (availability requires approval from Anritsu)
• COMPRION LTE Test Profile

 

Which of the multiple GSMA TS.48 test profile types should I use?

The profiles differ in the SAIP version (v2.1 versus v2.3) and whether they use BERTLV. If you do not know what the eUICC in your mobile device supports, we recommend using the simplest profile to prevent interoperability issues, i.e. SAIP v2.1 and NoBERTLV.

 

For the GSMA TS.48 V4.0 / V 5.0 test profiles: What is the difference between the "SAIP2.1A_NoBERTLV" and the "SAIP2.1B_NoBERTLV" profiles?

There was an inconsistency in the Simalliance Technical Specification v2.1, which lead to different implementations. Version A and B were developed to have a correctly working profile for both implementation.

Details: The way how the PIN context of a Local PIN is established is interpreted differently. PE TELECOM contains sub DF-s. In order to set the context of the Local PIN to DF TELECOM some cards required to set the current context to DF TELECOM before PE Local PIN. The Version B profile contains an additional Generic File Management Profile Element (identification='0') which sets the current context to DF TELECOM.

 

 

For the GSMA TS.48 test profiles: What is the difference between the version 4.0 and 5.0?

The V5.0 profiles differ in the following aspects compared to the V4.0 profiles:

TS48 V5.0 eSIM_GTP_SAIP2.1A_NoBERTLV.der	Alignment with 3GPP 31.102 v16.9.0 and 31.103 v16.1.0: - Minor typos correction (as bad calculation of size or format change) - EF ARR on ADF USIM: add Access Condition for EF SUCI CALC Info USIM to be record 15 (correction) - Change record size and file size of EF MSISDN - DF SAIP and EF (SUCI_Calc_info_USIM) under DF SAIP is removed
TS48 V5.0 eSIM_GTP_SAIP2.1A_NoBERTLV.der	Alignment with 3GPP 31.102 v16.9.0 and 31.103 v16.1.0: - Minor typos correction (as bad calculation of size or format change) - EF ARR on ADF USIM: add Access Condition for EF SUCI CALC Info USIM to be record 15 (correction) - Change record size and file size of EF MSISDN
TS48 V5.0 eSIM_GTP_SAIP2.3_BERTLV_SUCI.der	Alignment with 3GPP 31.102 v16.9.0 and 31.103 v16.1.0: - Minor typos correction (as bad calculation of size or format change) - Change UST to enable SUCI Calculation by USIM, URSP by USIM, 5G Security Parameters extended and MuD and MiD configuration data - Add EFMuDMiDConfigData in ADF USIM and ADF ISIM - Change IST to enable MuD and MiD configuration data - EF ARR on ADF USIM: add Access Condition for EF SUCI CALC Info USIM to be record 15 (correction) - Change record size and file size of EF MSISDN
TS48 V5.0 eSIM_GTP_SAIP2.3_NoBERTLV.der	Alignment with 3GPP 31.102 v16.9.0 and 31.103 v16.1.0: - Minor typos correction (as bad calculation of size or format change) - EF ARR on ADF USIM: add Access Condition for EF SUCI CALC Info USIM to be record 15 (correction) - Change UST to enable SUCI Calculation by USIM and 5G Security Parameters extended  - Change record size and file size of EF MSISDN

 

 

What if I have purchased a profile package for a specific profile type but then need another profile type

You need to purchase another package with the other profile type.

 

What settings do the profiles have?

• For the GSMA TS.48 eSIM test profiles you can check all details on GSMA’s Github: https://github.com/GSMATerminals/Generic-eUICC-Test-Profile-for-Device-Testing-Public.
• Applicable to mobile communication tests for NR-5GC / LTE-EPC / UTRAN / GERAN technology, for interworking with CDMA (1xRTT/HRPD) and for IMS according to the 3GPP conformance test specifications TS 38.523, TS 36.523, TS 34.123, TS 34.229 and TS 51.010.
• R&S GSMA eSIM Test Profile: This is equivalent to the R&S test SIM card. For details, please contact R&S.
• Anritsu LTE and 5G eSIM Test Profile: These are equivalent to the respective Anritsu LTE and 5G test SIM cards. For details, please contact Anritsu.
• COMPRION LTE Test Profile: Profile with XOR algorithm, covering USIM and ISIM. Addresses test cases as specified in 3GPP TS31.121, TS34.123-1, TS34.229-1, TS36.523-1. In case you need more information, please get in touch.
• MNO-specific test profiles (T-Mobile US, DISH US): in case you need further information, please just contact COMPRION

For the most relevant default parameters, please see the tables below:

General purpose eSIM Test Profiles
	Anritsu RTD LTE	Anritsu RTD 5G	R&S GSMA Test Profile	GSMA TS.48	Comprion 001
Supported GSMA network generation	up to 4G / LTE	up to 5G	up to 5G	up to 5G	up to 4G
SAIP version	2.1	2.1	2.1	2.1 or 2.3 - depending on chosen version	2.1
contains BERTLV	no	no	no	yes or no - depending on chosen version	no
MCC/MNC	001/01
IMSI	001010123456789		001010123456063	001010123456789
USIM	yes
ISIM	yes
CSIM	no	no	yes	yes	no
Authentication algorithm (USIM and ISIM)	Milenage	Milenage	XOR	XOR	XOR
Key (USIM and ISIM)	'000102030405060708090A0B0C0D0E0F'H
Opc (USIM and ISIM)	'C6A13B37878F5B826F4F8162A1C8D879'H		'00000000000000000000000000000000'H
GBA (USIM)	no
GBA (ISIM)	no		yes
EAP	no		yes	no	no
SUCI calculation	no	yes (by device)	yes (by USIM)	yes (by USIM or by device - depending on choosen version)	no

 

MNO-specific eSIM Test Profiles
	Anritsu T-Mobile US Profile	R&S T-Mobile US Profile	R&S DISH profile
Supported GSMA network generation	up to 4G / LTE	up to 5G	up to 5G
SAIP version	2.3	2.1	2.1
contains BERTLV	no
MCC/MNC	310/310	310/260	313/340
IMSI	310310012345678	310260012345606	31334090002647
USIM	yes
ISIM	yes
CSIM	no	yes	yes
Authentication algorithm (USIM and ISIM)	XOR
Key (USIM and ISIM)	'00112233445566778899AABBCCDDEEFF'H	'000102030405060708090A0B0C0D0E0F'H
Opc (USIM and ISIM)	'00000000000000000000000000000000'H
GBA (USIM)	no
GBA (ISIM)	yes		no
EAP	no	yes	no
SUCI calculation	no	yes (by USIM)

 

 

I need a profile with settings which differ from the settings of out-of-the-box available profiles. What options do exist?

Test profiles which belong to an existing profile package reside on the Remote SIM Provisioning Server (SM-DP+) and cannot be changed on this server anymore. But there are two options:

• You modify the profile yourself after it has been downloaded to the device. There are two options for this:
  • Via AT+CSIM commands managed by a tool like the COMPRION iSIMConnect (https://www.comprion.com/products-solutions/products-solutions-a-z/isimconnect/). But be aware: not all devices support this or have this enabled.
  • Via Remote File/Application Management. This requires connecting to the device via a Network Simulator and an OTA Server like COMPRION’s eUICC Profile Manager – Explorer(https://www.comprion.com/products-solutions/products-solutions-a-z/euicc-profile-manager/).
• COMPRION provisions a dedicated profile package for you with an eSIM test profile template according to your requirements. For some requirements this is not too difficult (e.g. changing MCC/MNC), for others it might be more complex. Please contact COMPRION with your specific requirements before ordering if you want to discuss this option.

Does the mobile device need to be connected to the Internet for an eSIM test profile download?

Yes, this is essential as the profile is downloaded from a cloud-based Remote SIM Provisioning service.

 

Do the profiles of my profile package, which I can download via the provided QR code, differ from download to download?

With one exception they are all identical. Each profile needs to have a unique ICCID. But this should not be relevant for you.

 

Can I use an activation code instead of a QR code?

Yes, besides the QR code, we’ll also provide the Activation Code.

Please note that some device manufacturers use different terminologies. The Activation Code is the combination of the URL of the RSP server and the MatchingID – the identifier of the profile. Some device manufacturers split this and ask for both elements separately but still call the second part “Activation Code” even though it is the MatchingID. Then you need split the Activation code.

Example: Activation code = 1$rsp.truphone.com$JJ-29YBA0-RJQ4MY

• RSP Server URL is: rsp.truphone.com
• MatchingID is: JJ-29YBA0-RJQ4MY

 

How do I download an eSIM test profile to a device?

Different devices require different activities:

• Consumer devices: The eSIM profile download is initiated in the user interface of the device. For details, please check the OEM’s documentation of the device.
• Consumer smartwatches: typically, the profile download is managed via a complementary smartphone. For details, please check the OEM’s documentation of the device.
• IoT devices: There are two options:
  • The profile download can be triggered via the “eIM” service if the device is associated with such a service.
  • It may be possible to trigger the profile download also on the device. If this is possible the detailed methodology will strongly depend on the device. For details, please check the OEM’s documentation of the device.

 

I cannot load the profile to a device. What is wrong?

There are multiple possible reasons. Most frequent reasons are:

• Device type is not supported. See above.
• Device has a test eUICC, i.e. an eUICC with certificates according to GSMA SGP.26. If you have purchased the device through “normal” channels, this will not be the problem.
• Mobile device has a carrier SIM lock. The device will only accept eSIM profiles with certain carrier-specific configurations, but not normal test profiles. In this case, COMPRION might be able to help you to work around this problem. Please contact COMPRION to discuss.
• Device has certain OEM/MNO business rules configured which prevent normal eSIM test profiles. This is often the case for smartwatches. Not for all, but in particular it holds true for Apple Watch.
• Mobile device need a special Remote SIM Provisioning mechanism for the profile download. This is often the case for smartwatches. Not for all, but in particular it holds true for Apple Watch.
• eUICC of the device is not interoperable with eSIM profile. Although standardized, this happens from time to time. An indication that this is the problem is that the profile can be downloaded, but not installed / activated. Instead, the eSIM returns an error to the eSIM Test Profile Service backed (SM-DP+)

 

What to do if a device has a carrier SIM lock?

COMPRION might be able to provide a customized eSIM test profile which shows the required carrier-specific settings. Please contact COMPRION to discuss.

What is eSIM “activation”?

This term is not part of the GSMA eSIM specification. It is used by different devices in different ways. Most often, it refers to the phase after the profile has been downloaded, installed and enabled. Then the phone starts to try connecting to a mobile network which fits the configuration of the eSIM profile. Depending on the device, it may give up after some 10 seconds or only much later (some devices try for 12 or 24 hours). You may not be able to terminate or interrupt this process. E.g. disabling and deletion of the profile might only be possible when the device has finished the activation procedure.

 

The eSIM test profile is downloaded, installed and enabled on the device, but the device does not connect to my network simulator. Why?

Most likely, the configuration of the network simulator does not match with the configuration of the eSIM profile. Please compare the profile settings with the settings of your network simulator. Please check in particular: MCC/MNC, IMSI, Authentication Algorithm.

 

The eSIM test profile is downloaded, installed and enabled on the device and the device is connected to a Network Simulator, but the device does not show the expected behavior. Why?

There are multiple potential reasons dor this:

• The eSIM test profile does not configure what you intent to test. Please check the eSIM profile documentation to check if this is the case
• The Network Simuator is not configured accordingly
• The device has been customized by a MNO (can be if you purchased the device not on the open market but via a MNO channel). In this case, the behavior of such devices in a network may depend on MNO-specific configurations in the eSIM profile, which a MNO-own profile may contain but not a generic test profile. In particular if you have seen a different behavior of this device with a MNO operational profile in the live network of this MNO compared to what you see with a test profile and a network simulator - then this might be the reason.

 

How can I delete an eSIM test profile on a mobile device?

For consumer devices, this can only be done by the user on the device itself. Please check the OEM’s documentation of the device for this. The GSMA specification for eSIM prevents mechanisms from deleting a profile from remote.

Please note: There is a difference between “disabling” a profile and “deleting” a profile.

Typically, the process to delete a profile needs internet connectivity of the device (WLAN), as the GSMA eSIM specification requires the device to send a notification of the deletion back to the Remote SIM Provisioning service. If this message cannot be sent due to lack of internet connectivity, the deletion process may not be finished. If the device becomes connected later on, the device will automatically try to send the message later. But this may not happen immediately. It may take hours before the device does this.

 

Do I have to delete a test profile on the device after testing?

If you are using the COMPRION eSIM Test Profile Service Packages, you do not need to do this. But you may want to do this to clean up the device.

I lost the QR code of my profile package. How can I get it again?

Please contact COMPRION.

 

How do I get to know how many downloads are left from the package of downloads which I purchased?

COMPRION provides a dedicated website where you can access this data. You will get the link to this website after you purchased a profile package in an email together with all other required information.

 

What happens to the profile package after the 12 months validity period?

Profiles which have already been downloaded to a device stay functional, also after the 12 months period. But profiles which have not been downloaded at the end of the 12 months perid become invalid.

 

The QR code of my profile package became disclosed to people who should not use my profile package. How to mitigate?

Unfortunately, there is no way to mitigate.

 

Where can I get more technical information about eSIM, eSIM profiles and Remote SIM Provisioning?

• Regarding eSIM profiles, please check out the technical specification and other documents from ETSI and the Trusted Connectivity Alliance.
• Regarding the eSIM and Remote SIM Provisioning: Please check out the technical specifications and other documents from the GSMA.
• COMPRION has held webinars related to the topic which you may find helpful. Please have a look here: https://www.comprion.com/company/events/webinars/

I have a product question or a problem that I cannot find an answer to here.

Please contact COMPRION via eTPS-ops(at)comprion.com