Backend Device Management - IDAS

Chapter:
Internet of Things Services Enablement
Version:
7.1.3
Updated:
2018-05-16
Contact Person:
Jose Gato Luis
jose.gato at atos dot net
Feedback:

IDAS

criteria value label
The overall label is the average of all individual labels assessed by Sep 2016
Documentation completeness Poor B
Documentation soundness Poor B
APIs Failure Rate 0,17 tests failed/executed A+
Detected defects by Priority 1,77 average bugs priority A+
Time to respond issues > 15 days D
Time to fix issues > 20 days D
Scalability 1,03 response time/thread number A+++
Performance 140 updates/sec B
Stability Memory/CPU are very slightly increasing but no leak A++

What you get

The IDAS component is an implementation of the Backend Device Management GE, according to the FIWARE reference architecture. You are here because you need to connect objects to gather data or interact with them, typical IoT use case scenario . If so, you need to use one of the existing IoT Agents that are part of IDAS.

Current list of supported IoT Agents (implemented with node.js):
  • IoTAgent-JSON 1.6.2 (HTTP/MQTT transport)
  • This IoT Agent is designed to be a bridge between an HTTP/MQTT+JSON based protocol and the FIWARE NGSI standard used in FIWARE, like the Orion Context Broker
  • IoTAgent-LWM2M 0.4.0 (CoaP transport).
  • This IoT Agent is designed to be a bridge between an Lightweight M2M protocol and the FIWARE NGSI standard used in FIWARE, like the Orion Context Broker
  • IoTAgent-UL 1.5.2 (HTTP/MQTT transport)
  • This IoT Agent is designed to be a bridge between an UltraLight2.0 protocol and the FIWARE NGSI standard used in FIWARE, like the Orion Context Broker Others:
  • IoTAgent-node-lib 2.5.1
  • This repository does not belong to an executable agent, but a library to create new agents. This core library allows to develop new agents for specific southbound protocols/standards/messages.

Please, visit the downloads section for other versions of agents like the ones (beta) supporting NGSIv2. This is the official list of agent’s repositories, but other agents would be available. Please refer to each repository for extra information about documentation, installation, user’s guide, etc.

Why to get it

You need this component if you plan to connect IoT devices/gateways to FIWARE-based ecosystems. IoT Agents translate IoT-specific protocols into the NGSI context information protocol, that is the FIWARE standard data exchange model. You do not need this component if your devices or gateways natively support the NGSI API.

By using an IoT Agent , your devices will be represented in a FIWARE platform as NGSI entities in a ContextBroker. This means that you can query or subscribe to changes of device parameters status by querying or subscribing to the corresponding NGSI entity attributes at the ContextBroker.

Additionally, you may trigger commands to your actuation devices just by updating specific command-related attributes in their NGSI entities representation at the Contaxt Broker. This way, all developers interactions with devices are handled at a ContextBroker, providing an homogeneous API and interface as for all other non-IoT data in a FIWARE ecosystem.

Open specification reference


IDAS component has been designed according the BE Device Management Open Specification .
Feedback: 
Label: 
A
Efficency Description: 

IDAS

criteria value label
The overall label is the average of all individual labels assessed by Sep 2016
Documentation completeness Poor B
Documentation soundness Poor B
APIs Failure Rate 0,17 tests failed/executed A+
Detected defects by Priority 1,77 average bugs priority A+
Time to respond issues > 15 days D
Time to fix issues > 20 days D
Scalability 1,03 response time/thread number A+++
Performance 140 updates/sec B
Stability Memory/CPU are very slightly increasing but no leak A++