The eSIM in the Remote SIM provisioning SGP.32 framework is capable to inform the managing eIM about the special events that happened that caused the eSIM state change (e..g a new profile was enabled due to connectivity fallback). It shall be possible to propagate this information to the application using the API as asynchronous notification. The managing application might then take appropriate actions (e.g. download a new profile that is relevant for the country where the device is currently located).
These events are part of the SGP.32 standard and therefore can be reasonably expected that these will be supported by multiple implementations. It shall however by still possible to handle the case that all or some of the events are not supported. It should be possible to "subscribe" to all, or subset of the events on a set of target eSIMs.
It should be considered to be able to list what events are supported by the API endpoint and set of target eSIMs. It could be considered to include also support of proprietary events that are implementation specific.
The API should include:
- Subscribe and unsubscribe to events
- List events
- Event notification delivery
The following events are possible according to the SGP.32:
otherEim(0), -- for change(s) requested by another registered eIM
fallback(1), -- for change(s) following fallback requested by IPA
emergencyProfile(2), -- for change(s) following Emergency Profile swap requested by IPA
local(3), -- for change(s) applied locally (RFU, not supported in this version)
reset(4), -- for change(s) following an euicc reset
immediateEnableProfile(5), -- for change(s) following immediate Profile enabling requested by IPA
deviceChange(6), -- for change(s) detected by IPAe following a IoT Device change (removable eSIMs)
undefined(127) -- unknown cause
Additionally it is supported to inform about the current PLMN (Country and network code) and its change:
rPLMN [2] OCTET STRING (SIZE(3)) OPTIONAL -- MCC and MNC of the last registered PLMN, coded as defined in 3GPP TS 24.008 [22]
The eSIM in the Remote SIM provisioning SGP.32 framework is capable to inform the managing eIM about the special events that happened that caused the eSIM state change (e..g a new profile was enabled due to connectivity fallback). It shall be possible to propagate this information to the application using the API as asynchronous notification. The managing application might then take appropriate actions (e.g. download a new profile that is relevant for the country where the device is currently located).
These events are part of the SGP.32 standard and therefore can be reasonably expected that these will be supported by multiple implementations. It shall however by still possible to handle the case that all or some of the events are not supported. It should be possible to "subscribe" to all, or subset of the events on a set of target eSIMs.
It should be considered to be able to list what events are supported by the API endpoint and set of target eSIMs. It could be considered to include also support of proprietary events that are implementation specific.
The API should include:
The following events are possible according to the SGP.32:
Additionally it is supported to inform about the current PLMN (Country and network code) and its change:
rPLMN [2] OCTET STRING (SIZE(3)) OPTIONAL -- MCC and MNC of the last registered PLMN, coded as defined in 3GPP TS 24.008 [22]