We have an ST4SIM-200M which is an M2M chip.
Now I am 99% sure I won’t be able to deploy any consumer profile onto this chip since it follows the push model and probably needs a different kind of profile which is also proactively provisioned by the manufacturer (though I’d be happy if this isn’t true), but I found out I cannot even retrieve its EID let alone EuicInfo2, profile list or anything. It can open a logical channel and select same ISD-R that consumer chips use, however the 6985 status code is returned for 81E2910006BF3E035C015A.
So does anyone know anything about specs of those chips and their APDU commands in particular? Thanks.
P.S. I tried to ask this on manufacturer’s forum but they didn’t allow such question.
You can be 100% sure. SGP.02 M2M eSIM provisioning has nothing in common with SGP.22 Consumer eSIM provisioning. They use different protocols, different cryptographic certificates and a different root-of-trust.
Yes. that is expected. they have nothing to do with each other. Even pySim should state clearly that the related commands are for Consumer and IoT eUICC only, and not for M2M. If it’s missing somewhere, please let us know so we can update it accordingly.
Check GSMA SGP.02 for all the related information. There’s not really much you can do as a local user of such a product. I guess you can read the EID (using a different command) but that’s about it. Everything else is controlled remotely via encrypted OTA communication by the issuer of the eUICC.
That’s the entire point: Consumer eUICC is for a local user (consumer) being in control. M2M eUICC is for a centralized remote management backend being in control.
1 Like
Hi @laforge and thanks for your reply.
I used at+csim command to communicate with the chip because it is integrated into a LTE module.
Do consumer and IoT chips use same protocols and commands, if I got my hands on an IoT chip would it be possible to deploy a consumer profile using consumer LPA software like lpac? As an active eUICC researcher and developer, have you had any experience with them?
Well, that was what I expected more or less, especially after some try and fail and reading about them online.
FYI, that doesn’t mean you cannot use pySim. See pySim/transport/modem_atcmd.py
We do have SGP.32 IoT eUICC samples at sysmocom for R&D, but given that at this point no single product has received GSMA accreditation there is no vendor that can issue you an SGP.32 IoT eUICC with GSMA production certificates, i.e. you cannot install production profiles from normal operators.
But yes, you can just talk to them from lpac or pySim-shell.
If all IoT eSIM SGP.32 modules are in test/sample state, does this mean the chips advertised as eSIM for IoT are in fact consumer solutions?
As I stated, there is to this point not a single GSMA-accredited eUICC for SGP.32 (IoT eSIM RSP).
I cannot really comment on what some companies out there advertise…