Forum Discussion
eSIM setup during device enrolment
As already mentioned in this thread, this is something that the OEM needs to implement by the looks of things. If I take an example for Zebra devices where they have StageNow which is configuration that are scannable. I have not tried it myself with eSIM but they seem to have a partial solution for it https://supportcommunity.zebra.com/s/article/000021043?language=en_US
I know you are looking for something in regards to Samsung but maybe this can help you in the discussion with them.
Thanks Timmy, that is really useful. I am speaking to Samsung about doing something similar with KME Direct but also think Google should integrate it into the OoBE
- Moombas4 months agoLevel 4.1: Jelly Bean
But just FYI, see here: https://www.androidenterprise.community/t5/reports-assets/android-15-screenshots-and-slide-deck-assets/ba-p/8694
There's eSIM management stated for Android 15 but i guess still only after enrollment and not sure about the details.
- jasonbayton4 months agoLevel 4.0: Ice Cream Sandwich
Yep it's policy driven. What we'd need is a DPC.extras payload akin to system apps, locale, etc to allow the sending of a subscription ID
- Moombas4 months agoLevel 4.1: Jelly Bean
I mean best would be DPC and then having a tool in background which knows of the relevant information (which the eSIM QR would provide) and with that generating dynamic QR codes or something similar.
And in addition (for ex. fully managed devices using ZTE) you would need to add something into the Zero-Touch portal, to add the relevant information per device (csv file import), so Zero-Touch provisioning possible as well. But i guess i start dreaming 😄
Related Content
- 11 months ago
- 5 months ago
- 10 months ago