Identity Management
IoT Device identification is fundamental in the platform in order to know at each particular timestamp who is the owner of the specific set of measurements
Once the IoT template is ready, it is possible to define the specific identifier that will uniquely identify the device at the time it is deployed. This identifier can be an IMEI, a MAC address, etc. The criteria to define this identifying string depends on the particular IoT System Integrator that assembles the device. Please, note that even if IMEIs, for example, are universally unique, there might be some unexpected overlap among vendors if two different IMEIs for different devices collided. In our data model we consider that all identifiers for devices assembled by the same IoT System Integrator must be compulsorily unique.
Keep in mind that identities can only be issued by IoT System Integrators or IoT SaaS platform (second level in role hierarchy). The necessary fields to issue one specific identity ([POST] /identities) are:
primary_identifier: corresponds to the string that contains the unique identifier of the physical device you are deploying. For example, you might decide to use an IMEI to uniquely identify your device in the physical network.
id_sensor: defines the unique identification number corresponding to the IoT device whose identity you are assigning. NOTE: to know the id_sensor of your device in database, you can visit https://docs.airtrace.io/iot-system-integrators/identity-handling for more information.
Once identities are created, they are left pending for their corresponding association in next stage (Section 2.1.3), at project creation and deployment.
Last updated