Jump to content

Talk:EUICC

Page contents not supported in other languages.
From Wikipedia, the free encyclopedia

References

[edit]

Here are some sources I am working with while I get to the bottom of eUICC and EID:

Authoritative

[edit]

Second-hand manufacturer implementation

[edit]

Third-party non-authoritative and possibly misleading

[edit]

Stephen Charles Thompson (talk) 17:27, 16 September 2022 (UTC)[reply]

References

  1. ^ "SGP.29 v1.0 EID Definition and Assignment Process". eSIM. GSM Association. 31 Jul 2020.

EID and eSIM authorities?

[edit]

Is there any other governing body that defines eSIM and "EID" besides the GSM Association? Is GMSA standard for eUICC the only applicable standard for eSIM? Do cellular network providers / operators have their own standards defining implementation / use of eSIM? Stephen Charles Thompson (talk) 17:32, 16 September 2022 (UTC)[reply]

Propose merge

[edit]

It may be appropriate to merging this content into the article eSIM. I see this article as stub quality due to short length. It was created to drill into GSM Association standards for eSIM. I am now looking into other standards for eSIM, if there are any. It may be that GSMA owns the term outright, unsure at this point. Stephen Charles Thompson (talk) 18:25, 16 September 2022 (UTC)[reply]

It's a really messy area. eUICC is software, and eSIM is hardware, as I understand it. It is possible to install UICC on an embedded SIM, for example.
Unfortunately, people tend to use "eSIM" as a synonym for the "eUICC" architecture, which offers remote provisioning of multiple profiles.
I would personally want to keep the two terms separate. It makes more sense to me as eUICC is used on iSIM for example, which is not an eSIM. Bringing "eSIM" and "eUICC" closer together is problematic, as the two are moving further apart as new form factors become available. Mikeindenmark (talk) 20:06, 19 March 2023 (UTC)[reply]
Closing, given the uncontested objection and no support, with stale discussion. Klbrain (talk) 09:45, 1 May 2023 (UTC)[reply]