API endpoints for considerations

[maheshc01]

IoTDevMgmt_Camara.pptx.pdf

Attached are the slides we went over the call which has more feedback on the set of APIs we want to start planning for.

Also below are initial thought on some of the API endpoint which follow the principles of RESTful design rather then the RPC style endpoints of /add, /delete etc
IoTDeviceManagement-CAMARA.pdf

[david-bohaty-thalesgroup]

Hello, I would have some relatively minor comments:

IoTDevMgmt_Camara.pptx.pdf:
Regarding "Journey 1: Bulk Device Onboarding & Service Activation" slide:
-for preloaded profiles Device EIDs do not need to be registered with SM-DP+ as the profile is preloaded and could have been loaded to the eSIM by some different means.

Regarding "Journey 3: Runtime Profile State"

• Step 2 disable operation shall not be included. It is likely this will lead to loss of connectivity. The enable operation (step 3) implies the disabling of any other previously enabled profile (ensured by eSIM)

IoTDeviceManagement-CAMARA.pdf
There shall be another API that is able to retrieve the activation code without activating the subscription. This would be for example to prepare prerequisites to support the "Journey 1" i.e. to preload profiles in advance, but only activate later. For example GET /subscriptions/info
Additionally there could be set of APIs to support "suspension" of the profile - i.e. if the profile is expected to be disabled for a long time then to suspend its operation in the MNO core network. For example:
POST /subscriptions/suspend
POST/subscription/reactivate