Accelerate SIM retry after LTE_LC_NW_REG_UICC_FAIL

Toolchain v2.70, SDK v2.7.0, VS Code, Windows

The design has an eSIM and a regular SIM, with a switch driven by a GPIO line. We default to the regular SIM, but if the library gives us an LTE_LC_NW_REG_UICC_FAIL we switch over to the eSIM. The idea is that we'll run off the eSIM unless a regular SIM is present, in which case that will override. The issue is that it takes ~30 seconds from the failure notification for the library to retry and thus detect the eSIM. Is there any way to accelerate this process and get the library to immediately detect the newly-selected eSIM? I thought of terminating and re-initializing the library, but that seemed a bit drastic...

Parents
  • Modem team;

    SIM stack in modem firmware has 30 second timer for reconnecting UICC. It is very much possible that delay for detecting eSIM is caused by this.

    When receiving LTE_LC_NW_REG_UICC_FAIL and after switching eSIM the customer might speed the process by deactivating and re-activating modem.

    The procedure would be:

    1. receive LTE_LC_NW_REG_UICC_FAIL

    2. Switch eSIM

    3. CFUN=4 for modem deactivation

    4. CFUN=1 for mode activation

Reply
  • Modem team;

    SIM stack in modem firmware has 30 second timer for reconnecting UICC. It is very much possible that delay for detecting eSIM is caused by this.

    When receiving LTE_LC_NW_REG_UICC_FAIL and after switching eSIM the customer might speed the process by deactivating and re-activating modem.

    The procedure would be:

    1. receive LTE_LC_NW_REG_UICC_FAIL

    2. Switch eSIM

    3. CFUN=4 for modem deactivation

    4. CFUN=1 for mode activation

Children