[[["易于理解","easyToUnderstand","thumb-up"],["解决了我的问题","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["没有我需要的信息","missingTheInformationINeed","thumb-down"],["太复杂/步骤太多","tooComplicatedTooManySteps","thumb-down"],["内容需要更新","outOfDate","thumb-down"],["翻译问题","translationIssue","thumb-down"],["示例/代码问题","samplesCodeIssue","thumb-down"],["其他","otherDown","thumb-down"]],["最后更新时间 (UTC):2025-03-26。"],[],[],null,["# Modem requirements for eSIM support\n\nThis page summarizes the required modem features for supporting an eSIM chip or\nremovable eSIM 4FF card.\n\nGeneral requirements\n--------------------\n\nThese are the modem requirements for general eSIM support. The Local Profile\nAssistant (LPA) needs the modem to support all of these requirements to function\nproperly.\n\n### Handle the default boot profile correctly\n\nWhen there is no operational or test profile enabled on eSIM, the default boot\nprofile is enabled. The modem recognizes the eSIM with the default boot\nprofile enabled as a valid SIM, reports the card as valid to upper layers,\nand doesn't turn off the SIM power.\n\n### Send terminal capabilities correctly\n\nOn power-up, the modem sends correct terminal capabilities to the eSIM. The\nterminal capability encodes support for eUICC capabilities *Local Profile\nManagement* and *Profile Download*.\n\nSee\n[ETSI TS 102 221 Section 11.1.19.2.4](https://www.etsi.org/deliver/etsi_ts/102200_102299/102221/15.00.00_60/ts_102221v150000p.pdf):\n\"Additional Terminal capability indications related to eUICC\". Bytes \\[1-3\\] shall\nbe: '83 (Tag) '01' (Length) '07' (eUICC capabilities).\n\n### (Optional) Support eSIM OS OTA updates\n\n| **Note:** As eSIM OS over-the-air (OTA) updates aren't standardized, this depends on the vendor providing the eSIM OS.\n\nThe modem supports all requirements for eSIM OS OTA updates, for example,\nswitching to passthrough mode and keeping the eSIM powered on during the OTA\nupdate procedure.\n\nHAL requirements\n----------------\n\nThese are API implementations that are required for general eSIM support.\n\nFor devices supporting MEPs, see the\n[HAL requirements for MEP](/docs/core/connect/esim-mep#hal-requirements).\n\n### Implement setSimPower in Radio HAL v1.1\n\nThe modem supports the\n[`setSimPower`](https://android.googlesource.com/platform/hardware/interfaces/+/android16-release/radio/1.1/IRadio.hal#72)\nmethod.\n\n### Implement getSimSlotsStatus in IRadioConfig HAL v1.2\n\n| **Note:** Support for IRadioConfig HAL v1.2 is required for devices launching with Android 10 and is recommended for all other Android versions.\n\nThe modem supports the\n[`getSimSlotsStatus`](https://android.googlesource.com/platform/hardware/interfaces/+/android16-release/radio/config/1.0/IRadioConfig.hal#51)\nmethod, which indicates whether a slot contains an eSIM.\n\nThis method was introduced in v1.0. In v1.2,\n[`SimSlotStatus`](https://android.googlesource.com/platform/hardware/interfaces/+/android16-release/radio/config/1.2/types.hal#22)\nincludes\n[EID](https://android.googlesource.com/platform/hardware/interfaces/+/android16-release/radio/config/1.2/types.hal#31).\n\n### Implement getIccCardStatus in IRadio HAL v1.4\n\n| **Note:** Support for IRadio HAL v1.4 is required for devices launching with Android 10 and is recommended for all other Android versions.\n\nThe modem provides the answer to reset (ATR) and slot ID of the card status\nin the\n[`getIccCardStatusResponse`](https://android.googlesource.com/platform/hardware/interfaces/+/android16-release/radio/1.0/IRadioResponse.hal#38)\nmethod. This method was introduced in v1.0 and, in v1.2,\n[`CardStatus`](https://android.googlesource.com/platform/hardware/interfaces/+/android16-release/radio/1.2/types.hal#343)\nwas changed to include\n[ATR](https://android.googlesource.com/platform/hardware/interfaces/+/android16-release/radio/1.2/types.hal#353).\nIn v1.4,\n[`CardStatus`](https://android.googlesource.com/platform/hardware/interfaces/+/android16-release/radio/1.4/types.hal#1669)\nincludes\n[EID](https://android.googlesource.com/platform/hardware/interfaces/+/android16-release/radio/1.4/types.hal?#1678).\n\n### Set CardState:RESTRICTED on SIM lock (subsidy lock)\n\nIf the eSIM is SIM locked (subsidy locked), the modem sets the card state as\n[`CardState:RESTRICTED`](https://android.googlesource.com/platform/hardware/interfaces/+/android16-release/radio/1.0/types.hal#168)\nin the\n[`getIccCardStatusResponse`](https://android.googlesource.com/platform/hardware/interfaces/+/android16-release/radio/1.0/IRadioResponse.hal#38)\nmethod.\n\n### (Optional) Implement setSimSlotsMapping in IRadioConfig HAL v1.0\n\n| **Note:** Only required in device configurations that require slot switching, for example, where the device has one eSIM slot and one physical/removable SIM (pSIM) slot, and only one can be active at the same time.\n\nThe modem supports the\n[`setSimSlotsMapping`](https://android.googlesource.com/platform/hardware/interfaces/+/android16-release/radio/config/1.0/IRadioConfig.hal#81)\nmethod,\nwhich sets the mapping from physical slots to logical slots. The LPA uses this\nmethod to select the active SIM slot.\n\nLogging requirements\n--------------------\n\nThese are general modem logging requirements for debugging eSIM issues.\n\n### Log capture\n\nLogging captures interprocessor communication, SIM functionality, radio\ninterface layer (RIL) logging, and application protocol data unit (APDU)\nlogging.\n\n### On-device logging\n\nDevice software supports an on-device modem log capturing mechanism.\n\n### Log config support\n\nDevice software supports different modem logging configurations (level,\nmodules). These configurations must be supported for both on-device logging and\nPC-tool-based logging.\n\n### Android bug report\n\nBug reports contains modem logs, vendor RIL logs, panic signature logs, and\nAndroid logs."]]