IoT Broker

Chapter:
Internet of Things Services Enablement
Version:
5.4.3
Updated:
2016-10-21
Contact Person:
Stefan Gessler, Flavio Cirillo
iotplatform at neclab dot eu
Feedback:

Iot Broker

criteria value label
The overall label is the average of all individual labels assessed by Sep 2016
Documentation completeness Good A+
Documentation soundness Good A+
APIs Failure Rate 0,07 tests failed/executed A++
Detected defects by Priority 2 average bugs priority A
Time to respond issues 5,6 days A+
Time to fix issues 16,4 days C
Scalability 1,15 response time/thread number A++
Performance 388,95 updates/sec B
Stability Memory/CPU are progressively increasing but no leak A

What you get

The IoT Broker Generic Enabler is specified as a lightweight and scalable middleware component that separates IoT applications from the underlying device installations. The IoT Broker implementation available through the FIWARE Catalogue is the reference implementation of this Generic Enabler by NEC. This implementation satisfies all properties described in the specification of the Generic Enabler. The IoT Broker has unique properties that you will not find in other IoT Platforms:
  • While the IoT Broker GE decouples applications from underlying IoT device installations, it achieves this going far beyond the common publish/subscribe paradigm. Instead, the IoT Broker actively communicates simultaneously with large quantities IoT gateways and devices in order to obtain exactly the information that is required by the running IoT applications. As a result, information only is generated and exchanged when needed. This is in contrast to the state-of-the-art middleware components where any piece of information - whether needed or not - is just ''dumped'' inside a central repository.
  • The IoT Broker has the ability to automatically translate information to the right abstraction level and therefore closes the gap between information-centric applications and device-centric IoT installations. For example, a simple device can typically only deliver values without being aware of the meaning of these values in the application's context. On the other hand, IoT applications have to written without consideration of the device installations in order to be applicable in more than one specific environment. This gap is closed by the IoT Broker by the use of so-called associations between device-level and thing-level information.
The IoT Broker Generic Enabler is based on the simple and powerful information model standardized in OMA Next Generation Service Interface Context Enabler (NGSI 9 / NGSI 10). This API has emerged in FIWARE as an important open standard of information exchange, implemented by a considerable number of FIWARE GEs. In NGSI 9/10, all objects of the real world, being it sensor/actuator devices or arbitrary objects (like tables, rooms, cars, ...) are represented as so-called Context Entities, while information about these objects is expressed in the form of attributes. For more information about the OMA NGSI 9/10 information model and the related interfaces, please refer to the Open API Specification.

Why to get it

The main features of this Enabler are
  • Offering a single point of contact to the user, hiding the complexity of the multi-provider nature of the Internet of Things.
  • Collecting and aggregating information about thousands of real-world objects on behalf of the user.
  • Provide means to assemble lower-level device information (device-centric access) into higher-level Thing information (information-centric access).
The IoT Broker GE is a component for retrieving and aggregating information from the Internet of Things.
Label: 
A
Efficency Description: 

Iot Broker

criteria value label
The overall label is the average of all individual labels assessed by Sep 2016
Documentation completeness Good A+
Documentation soundness Good A+
APIs Failure Rate 0,07 tests failed/executed A++
Detected defects by Priority 2 average bugs priority A
Time to respond issues 5,6 days A+
Time to fix issues 16,4 days C
Scalability 1,15 response time/thread number A++
Performance 388,95 updates/sec B
Stability Memory/CPU are progressively increasing but no leak A