Backend Device Management - IDAS

Chapter:
Internet of Things Services Enablement
Version:
Updated:
2016-10-21
Contact Person:
Carlos Ralli Ucendo
carlos.ralliucendo at telefonica dot com
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.
Its main usage is the Typical IoT use-case Scenario I: Common Simple Scenario of the overall FIWARE IoT architecture.

As of May 2016, IDAS has been totally refactored according to the feedback provided by FIWARE Developer community.
Concretely, the new IDAS (Release 5 onwards) provides:
  • All IoT Agents are now coded with node.js and therefore the installation, configuration and new development processes have been simplified and optimized.
  • The IoT Agents are not classified anymore by the transport technology (e.g: HTTP, MQTT, CoAP) but they are distributed in different GIT repositories based on the top level (device semantics) protocol and offering different trasnport possibilities. This means that thre is an Ultralight2.0 IoT Agent with different trasnport options (currently HTTP or MQTT) that may be increased in the future (e.g. supporting CoAP in the forthcomming Sprints). You will select and use only those IoT Agents supporting the IoT semantics and trasnport protocol your devices/gateways actually use.
  • The IoT Agent Manager component delivered at Release 4 is still not available with node.js and thefore it will be announced in the forthcoming sprints. This component addresses monitoring and management of IoT Agent instances. You only need this component for complex scenarios with multiple IoT Agent instances.
  • The Northbound API of IDAS (i.e. all IoT Agents plus the IoT Manager) is the OMA NGSI protocol, as long as IoT Agents are normally expected to be connected to an NGSI Broker, such as the Orion ContextBroker
  • A Library for IoT Agents in node.js is provided for those IoT integrators willing to implement a new IoT specific standard/propietary protocol themselves.
  • A Reference client tool called FIGWAY to connect physical devices or experiment with virtual devices for simulation exercises using UL2.0/HTTP protocol. UL2.0 is an open and light protocol specification for devices.
  • An IoT Edge Manager component is being implement in Release 5 onwards. Initially it stores and handles the communications and/or IoT-gateways topology and details as NGSI entities. This testing implementation is being developed as part of FIGWAY tool. In the future it may address more functions beyond storage/description related to IoT networks, IoT Gateways and IoT end-nodes operations.


Why to get it

You need this component if you plan to connect IoT devices/gateways to FIWARE-based ecosystems. IDAS 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 this component (in reality just the IoT Agents related to your devices IoT protocols), 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. Please check also the following specifications:
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++