Why SGP.32 and why SGP.22?

I understand the technical (I think I do, I’m starting to wonder tho), but what’s the reason to design a mobile device with one or the other? I hear SGP.32 is better for 5G and SGP.22 is better for 3G and 4G but is that true? My watch is 5G and it still uses SGP.22.

And every MNO has a EIM…so how is this managed? Do you just add like 10 EIMS to your UICC? Or do you stand up own EIM for your own needs? Is there a open source EIM?

Hello @mayhayze,

The purpose of SGP.32 is to allow remote administration of profile. As opposed to SGP.22, which local administration:

  • SGP.22: the end user (basically a person) manage the profile locally on the device, using the LPA.
  • SGP.32: the device issuer (or service provider, basically a business) administer all the device it issues using the EIM (via web UI, or business logic and an API),

They can both offer 3G, 4G or 5G, there is no real constraint at this level, as far as I know.

Hope this helps,
Greg

3 Likes

Ok, but SGP.22 also does Remote Profile Management through the DS and ES. For example, my watch jumped on my phone plan and I never touched it. Also some of these cell routers use SGP.22. Honestly you touched on what’s confusing me.

RpmPackage ::= SEQUENCE OF RpmCommand -- #SupportedForRpmV3.0.0#
 RpmCommand ::= SEQUENCE {
  continueOnFailure [0] NULL OPTIONAL,
  rpmCommandDetails CHOICE {
   enable [1] SEQUENCE {iccid [APPLICATION 26] Iccid},
   disable [2] SEQUENCE {iccid [APPLICATION 26] Iccid},
   delete [3] SEQUENCE {iccid [APPLICATION 26] Iccid},
   listProfileInfo [4] ListProfileInfo,
   updateMetadata [5] SEQUENCE {
    iccid [APPLICATION 26] Iccid,
    updateMetadataRequest UpdateMetadataRequest
   },
   contactPcmp [6] SEQUENCE {
   iccid [APPLICATION 26] Iccid,
   dpiRpm UTF8String OPTIONAL
  }
 }
}

@mayahayze, I think you are referring to recent features introduced to SGP.22 v3.x while most deployments today use SGP.22 v2.x - so the comparison usually is between SGP.22 v2.x and SGP.32 v1.2

Also, RPM of SGP.22 (as opposed to SGP.32) does not cover downloading of new profiles.

1 Like

Well true, but the SMDS has Event Records. I guess the SGP.32 EIM is equivalent to the SGP.22 DP+ and the DS put together??

But I see what you mean, the interesting stuff is in SGP.32 3.x, I guess the SGP.22 team has there own ideas about IoT. Who is using SGP.32 v3??

Please make sure to read up on the specifications and/or the recorded talks I’ve given also specifically on how SGP.32 differs from SGP.22.

The eIM is not a replacement of the SM-DP+. The eIM is the centralized “upper half” of the LPA. You basically take the SGP.22 LPA, and split it into a local IPA and a remote/centralzied eIM. The eIM is under control of (and operated by or under authoriy of) the “device fleet owner” and not under control of the SM-DP+ which is under control/authority of the MNO of a specific profile.

1 Like

Fair, but I didn’t say it was a replacement. I said it the IM is equivalent to the DS and DP+, I see you point but …|

Reading these specs and listening to your talk, I also think about 3 things. First, SGP.32 has no way for the device CPU to enable profiles or support 5G dual sim dual standby, so no fancy logic to pick the best signal or whatever … second, neither SGP.22 or SGP.32 really has orchestration. SGP.32 maybe makes orchestration a simpler task, but maybe not actually because every carrier has their own EIM planned and if there are hundreds of EIMs everywheres we’re better off with LPAs keeping their own top half … third, both specs are WAY WAY WAY too complicated (probly cause they built everything on top of smart cards, but WHAT a nightmare)

Also, are the different SIM companies cross testing there EUICCs and EIMs? I kinda think maybe not. At least, it’s not talked about like SGP.22 EUICCS beting cross compatible with SMDP+ servers. That means device companies have to write their own IPA or get stuck with the forever kind of tech debt.