IoT Fleet Management

[FabrizioMoggio]

A fleet of IoT devices needs to be managed in this API

[varanto]

We can add a fleet id attribute on top of the current explicit device list. The meaning of this fleet id (i.e., how to actually retrieve the related list of devices) depends on what is supported in the Operator network. For example, as discussed here, one option could be to use the devices identified and managed via the DedicatedNetwork API.

[FabrizioMoggio]

@rkandoi the idea is to create a new Issue to add a "fleet Id" as optional input to the IoT API. With this new parameter, if the Operator provides an API that does fleet management, the developer can leverage on that API to create a fleet, get back a "fleet Id" and use it in the IoT API. If you agree on this, I will proceed creating a new Issue.

[FabrizioMoggio]

When we first presented the IoT API in CAMARA there was a discussion on some overlapping with the Dedicated Networks API (https://github.com/camaraproject/DedicatedNetworks/). It was decided to see how DN would have evolved especially in terms of fleet management. In my understanding currently there is no proper fleet management in DN. A device management flow is indeed implemented.

How, in my understanding, DN works for device management:
According to the general documentation, the workflow is:

Create a dedicated network

• For each device , create an Access resource linking that device to the network
• Only devices with created Access resources can use the network's resources
• You can delete Access resources to revoke fleet device permissions

This is similar to how the IoT API works, managing just one device for each call. To improve this without changing the scope of the IoT, I suggest to proceed as suggested here: #30 (comment), adding just a "fleet-id". This optional parameter can be returned by a new CAMARA API specifically designed to manage SIM fleets. It can even be a parameter returned by an Operator specific API (not a CAMARA one).