deviceDiscovery IDD

generic_mqtt & generic_mqtts

Overview

This page describes the generic_mqtt and generic_mqtts service interface of deviceDiscovery, which enables both application and Core/Support systems to lookup, register and revoke devices on which the Local Cloud’s systems are running. Device representation is not necessary for the base functionalities of a Local Cloud but in certain use cases (e.g. enabling onboarding) is needed. It’s implemented using protocol, encoding as stated in the following tables:

generic_mqtt

Profile type	type	Version
Transfer protocol	MQTT	3.1 and 3.1.1
Data encryption	N/A	-
Encoding	JSON	RFC 8259
Compression	N/A	-

generic_mqtts

Profile type	type	Version
Transfer protocol	MQTT	3.1 and 3.1.1
Data encryption	TLS	-
Encoding	JSON	RFC 8259
Compression	N/A	-

Hereby the Interface Design Description (IDD) is provided to the deviceDiscovery – Service Description. For further details about how this service is meant to be used, please consult that document.

Interface Description

register

The service operation request requires an MQTTRequestTemplate JSON encoded message in which the authentication is a proper identity info and the payload is a DeviceRegistrationRequest.

Topic:  arrowhead/serviceregistry/device-discovery/register

{
   "traceId": "<trace-id>",
   "authentication": "<identity-info>",
   "responseTopic": "<response-topic>",
   "qosRequirement": "<0|1|2>",
   "payload": {
      "name": "THERMOMETER2",
      "metadata": {
         "scales": [
            "kelvin",
            "celsius"
         ],
         "maxTemperature": {
            "kelvin": 310,
            "celsius": 40
         },
         "minTemperature": {
            "kelvin": 260,
            "celsius": -10
         }
      },
      "addresses": [
         "81:ef:1a:44:7a:f5"
      ]
   }
}

The service operation responds with an MQTTResponseTemplate JSON encoded message in which the status code is 200 if called successfully and the device entity is already existing or 201 if the entity was newly created. The response template payload is a DeviceRegistrationResponse.

{
   "status": 201,
   "traceId": "<trace-id>",
   "receiver": "<receiver-system-identifier>",
   "payload": {
      "name": "THERMOMETER2",
      "metadata": {
         "scales": [
            "kelvin",
            "celsius"
         ],
         "maxTemperature": {
            "kelvin": 310,
            "celsius": 40
         },
         "minTemperature": {
            "kelvin": 260,
            "celsius": -10
         }
      },
      "addresses": [
         {
            "type": "MAC",
            "address": "81:ef:1a:44:7a:f5"
         }
      ],
      "createdAt": "2024-11-04T01:53:02Z",
      "updatedAt": "2024-11-04T01:53:02Z"
   }
}

The error codes are 400 if the request is malformed, 401 if the requester authentication was unsuccessful, 403 if the authenticated requester has no permission and 500 if an unexpected error happens. In these cases the response template payload is an ErrorResponse JSON.

{
   "status": 400,
   "traceId": "<trace-id>",
   "receiver": "<receiver-system-identifier>",
   "payload": {
      "errorMessage": "Device name is missing.",
      "errorCode": 400,
      "exceptionType": "INVALID_PARAMETER",
      "origin": "arrowhead/serviceregistry/device-discovery/register"
   }
}

lookup

The service operation request requires an MQTTRequestTemplate JSON encoded message in which the authentication is a proper identity info and the payload is a DeviceLookupRequest.

Topic:  arrowhead/serviceregistry/device-discovery/lookup

{
   "traceId": "<trace-id>",
   "authentication": "<identity-info>",
   "responseTopic": "<response-topic>",
   "qosRequirement": "<0|1|2>",
   "payload": {
      "deviceNames": [
         "THERMOMETER2"
      ],
      "addresses": [
         "81:ef:1a:44:7a:f5"
      ],
      "addressType": "MAC",
      "metadataRequirementList": [
         {
            "maxTemperature.celsius": {
               "op": "LESS_THAN",
               "value": 50
            }
         }
      ]
   }
}

The service operation responds with an MQTTResponseTemplate JSON encoded message in which the status code is 200 if called successfully. The response template payload is a DeviceLookupResponse.

{
   "status": 200,
   "traceId": "<trace-id>",
   "receiver": "<receiver-system-identifier>",
   "payload": {
      "entries": [
         {
            "name": "THERMOMETER2",
            "metadata": {
               "scales": [
                  "kelvin",
                  "celsius"
               ],
               "maxTemperature": {
                  "kelvin": 310,
                  "celsius": 40
               },
               "minTemperature": {
                  "kelvin": 260,
                  "celsius": -10
               }
            },
            "addresses": [
               {
                  "type": "MAC",
                  "address": "81:ef:1a:44:7a:f5"
               }
            ],
            "createdAt": "2024-11-04T01:53:02Z",
            "updatedAt": "2024-11-04T01:53:02Z"
         }
      ],
      "count": 1
   }
}

The error codes are, 400 if the request is malformed, 401 if the requester authentication was unsuccessful, 403 if the authenticated requester has no permission and 500 if an unexpected error happens. In these cases the response template payload is an ErrorResponse JSON.

{
   "status": 500,
   "traceId": "<trace-id>",
   "receiver": "<receiver-system-identifier>",
   "payload": {
      "errorMessage": "Database operation error.",
      "errorCode": 500,
      "exceptionType": "INTERNAL_SERVER_ERROR",
      "origin": "arrowhead/serviceregistry/device-discovery/lookup"
   }
}

revoke

The service operation request requires an MQTTRequestTemplate JSON encoded message in which the authentication is a proper identity info and the payload is the device name.

Topic:  arrowhead/serviceregistry/device-discovery/revoke

{
   "traceId": "<trace-id>",
   "authentication": "<identity-info>",
   "responseTopic": "<response-topic>",
   "qosRequirement": "<0|1|2>",
   "payload": "THERMOMETER2"
}

The service operation responds with an MQTTResponseTemplate JSON encoded message in which the status code is 200 if called successfully and an existing device entity was removed and 204 if no matching entity was found.

{
   "status": 200,
   "traceId": "<trace-id>",
   "receiver": "<receiver-system-identifier>"
}

The error codes are, 400 if the request is malformed, 401 if the requester authentication was unsuccessful, 403 if the authenticated requester has no permission, 423 if the entity is not removable and 500 if an unexpected error happens. In these cases the response template payload is an ErrorResponse JSON.

{
   "status": 500,
   "traceId": "<trace-id>",
   "receiver": "<receiver-system-identifier>",
   "payload": {
      "errorMessage": "Database operation error.",
      "errorCode": 500,
      "exceptionType": "INTERNAL_SERVER_ERROR",
      "origin": "arrowhead/serviceregistry/device-discovery/revoke"
   }
}