Project: /_project.yaml Book: /_book.yaml
This page summarizes the required modem features for supporting an eSIM chip or removable eSIM 4FF card.
These are the modem requirements for general eSIM support. The LPA needs the modem to support all of these requirements to function properly.
When there is no operational or test profile enabled on eSIM, the default boot profile is enabled. The modem shall recognize the eSIM with the default boot profile enabled as a valid SIM. The modem shall report card as valid to upper layers and shall not turn off the SIM power.
When opening a logical channel to ISD-R, the modem shall send correct terminal capabilities to the eSIM. The terminal capability must encode support for eUICC capabilities: “Local Profile Management” and “Profile Download” per ETSI TS 102 221.
The modem shall support the setSimPower API.
The modem shall support the getSimSlotsStatus{: .external} API, which indicates whether a slot contains an eSIM.
The modem shall provide the ATR and slot ID of the card status as specified in the getIccCardStatus API. This API was first introduced in v1.0 and, in v1.2, CardStatus{: .external} was changed to include ATR{: .external}.
As the eSIM OS OTA is not standardized, this depends on the vendor providing eSIM OS. The modem shall support all requirements for eSIM OS OTA, for example switching to passthrough mode and keeping the eSIM powered on during the OTA procedure.
These are general modem logging requirements to properly debug eSIM issues.
Logging shall capture all the OTA packets for Cellular RATs (4G, 3G, 2G) and IMS (SIP, RTP, RTCP, XCAP). ESP protected SIP packets shall be logged without ESP. OTA parser shall be compliant to 3GPP specs.
Logging shall support capture IP packets on all network interfaces.
Logging shall support capturing debug logs and protocol layer information including protocol layer states, radio power measurements, network cell information, packet TX/RX statistics, inter-layer messaging, inter-processor communication, SIM functionality & APDU logging, and RIL logging.
Device software shall support an on-device modem log capturing mechanism.
Device software shall support different modem logging configurations (level, modules). These configurations shall be supported for both on-device logging and PC-tool-based logging.
Bug reports shall contain modem logs, vendor RIL logs, panic signature logs, and Android logs.