On Remote SIM Provisioning proposed Objects (504, 505) about lwm2m-registry HOT 4 CLOSED

We believe we have met the Ericsson desires by defining Object 504 to address the use case where the LwM2M client connects directly to the SM-DP+ server and the use case where the LwM2M server is an intermediary between the LwM2M client and the SM-DP+ server. Per the Qualcomm desire, the use case where the LwM2M server is the repository of the SIM Update Package and is used to download that package to the LwM2M client where the update SIM process is locally executed is addressed in Object 505.

There are enough differences in the similar resources such that they should evolve independently (usage, enumerated values, states, etc.) which is why separate objects are preferred.

In terms of reusable resources, there are some resources we could declare as reusable resources, but we did not see enough future use to merit the extra effort and we did follow the original DMSE style rather than the IPSO style . If you think there is enough value to separate certain resources into reusable resources, please let us know which ones and we will make that effort.

from lwm2m-registry.

Thanks Alan. So the Qualcomm proposal is to modify Object 504 to remove support for nuSIM and focus only on GSMA Remote SIM Provisioning and the nuSIM provisioning would be handled by Object 505? We are fine with this approach but the naming of the objects must reflect this, which the current namings don’t. The users are fully aware whether they use GSMA eSIM or nuSIM. Hence, our proposal is to call Object 504 ”GSMA Remote SIM Provisioning” and Object 505 ”nuSIM Provisioning”.

from lwm2m-registry.

Based on Object 504 and 505 in #606 and #604 this issue can be closed.

from lwm2m-registry.

Closed per 5/11/2021

from lwm2m-registry.