Interface to the internet of Things
Connecting IoT devices or “things” involves the need to overcome a common set of problems arising in the different layers of the communication model. Using sensor data or acting upon them requires interaction with a heterogeneous environment of devices running different protocols (due to the lack of globally accepted standards), dispersed and accessible through multiple wireless technologies.
To learn more about the Interface to the internet of Things, check out the documentation
What are IoT Agents?
The IoT Agent (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.
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.
FIWARE-Ready IoT devices are able demonstrate the ability of the IoT solutions to seamless interoperate with FIWARE platforms. Any IoT device which is able to connect to the context broker (either directly or via an IoT Agent) is able to undergo a certification and testing process and can be added to the FIWARE marketplace and labelled as a FIWARE-Ready IoT Device.
Why Use IoT Agents?
By using an IoT Agent , your devices will be represented in a FIWARE platform as NGSI entities in a Context Broker. 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 will be able trigger commands to your actuation devices by updating specific command-related attributes in the associated NGSI entities representation at the Context Broker. This way, all hardware interactions with IoT devices can be handled by the Context Broker, using a homogeneous NGSI interface.
IoT Agent Framework Library
Library for developing your own IoT Agent.
The IoT Agent Framework Library project is part of FIWARE and but is not rated as a standalone component. It is used in the following IoT Agents:
IoT Agent for JSON
IoT Agent for Ultralight
IoT Agent for LoRaWaN
IoT Agent for the LoRaWAN protocol (with CayenneLpp and CBOR data models)
IoT Agent for LightWeight Machine2Machine
IoT Agent accepting COAP requests.
IoT Agent for OPC UA
IoT Agent accepting data from OPC UA devices.
🌱 IoT Agent for Sigfox (Incubated)
IoT Agent for the Sigfox protocol.
🆕 IoT Agent for ADAPT/ISOXML (Incubated)
IoT Agent for the ISOXML/ADAPT protocol.
What is Kurento?
Why use Kurento?
🌱 OpenVidu (Incubated)
What is OpenVidu?
The Openvidu Generic Enabler simplifies real-time processing of media streams managed or provided by Kurento, providing a simple HTTP REST API that manages the streams and provides an extra security layer simplifying the transformation of video cameras into sensors as well as the incorporation of advanced application functions (integrated audiovisual communications, augmented reality, flexible media playing and recording, etc
Why Use OpenVidu?
Openvidu is a simple (easy to deploy/ easy to use) way to have advanced media streams processing and communications. It is opensource, compatible with multiple frontend and backend technologies. It provides support for many media transmission protocols. It hides the specifics and allows you to focus in your use case and business logic.
🌱 Open MTC (Incubated)
A reference implementation of the oneM2M standard, for conducting applied research and developing innovative M2M and IoT applications. It offers an NGSI interface for connection to the Orion Context Broker