Skip to content
Permalink
Branch: master
Find file Copy path
Find file Copy path
1 contributor

Users who have contributed to this file

321 lines (242 sloc) 25.3 KB

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

License

:octocat: Git Repository 🐳 Docker Hub : None 📚 Documentation 🎓 Academy 🎯 Roadmap

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

License

:octocat: Git Repository 🐳 Docker Hub 📚 Documentation 🎓 Academy 🎯 Roadmap

IoT Agent for a JSON based protocol (with AMQP, HTTP and MQTT transports)

This IoT Agent is designed to be a bridge between JSON and the NGSI interface. It follows the standard interaction model defined in the IoT Agent Framework Library.

Quality Assurance

The IoT Agent for JSON project is part of FIWARE and has been rated as follows:

  • Version Tested:
  • Documentation:
  • Responsiveness:
  • FIWARE Testing:

IoT Agent for Ultralight

License

:octocat: Git Repository 🐳 Docker Hub 📚 Documentation 🎓 Academy 🎯 Roadmap

IoT Agent for the Ultralight 2.0 protocol (with AMQP, HTTP and MQTT transports)

This IoT Agent is designed to be a bridge between Ultralight and the NGSI interface. It follows the standard interaction model defined in the IoT Agent Framework Library.

Quality Assurance

The IoT Agent for the Ultralight project is part of FIWARE and has been rated as follows:

  • Version Tested:
  • Documentation:
  • Responsiveness:
  • FIWARE Testing:

IoT Agent for LoRaWaN

License

:octocat: Git Repository 🐳 Docker Hub 📚 Documentation 🎓 Academy 🎯 Roadmap

IoT Agent for the LoRaWAN protocol (with CayenneLpp and CBOR data models)

This IoT Agent is designed to be a bridge between the LoRaWAN protocol and the NGSI interface. It follows the standard interaction model defined in the IoT Agent Framework Library.

Quality Assurance

The IoT Agent for LoRaWAN project is part of FIWARE and has been rated as follows:

  • Version Tested:
  • Documentation:
  • Responsiveness:
  • FIWARE Testing:

IoT Agent for LightWeight Machine2Machine

License

:octocat: Git Repository 🐳 Docker Hub 📚 Documentation 🎓 Academy 🎯 Roadmap

IoT Agent accepting COAP requests.

This IoT Agent is designed to be a bridge between the OMA Lightweight M2M protocol and the NGSI interface. It follows the standard interaction model defined in the IoT Agent Framework Library.

Quality Assurance

The IoT Agent for LightWeight Machine2Machine project is part of FIWARE and has been rated as follows:

  • Version Tested:
  • Documentation:
  • Responsiveness:
  • FIWARE Testing:

🌱 IoT Agent for OPC UA (Incubated)

License

:octocat: Git Repository 🐳 Docker Hub 📚 Documentation 🎯 Roadmap

IoT Agent accepting data from OPC UA devices.

This IoT Agent is designed to be a bridge between the OPC Unified Architecture protocol and the NGSI interface. It follows the standard interaction model defined in the IoT Agent Framework Library.

Quality Assurance

The IoT Agent for OPC-UA project is part of FIWARE and has been rated as follows:

  • Version Tested:
  • Documentation:
  • Responsiveness:
  • FIWARE Testing:

🆕 IoT Agent for Sigfox (Incubated)

License

:octocat: Git Repository 🐳 Docker Hub 📚 Documentation 🎯 Roadmap

IoT Agent for the Sigfox protocol.

This IoT Agent is designed to be a bridge between the Sigfox protocol and the NGSI interface. It follows the standard interaction model defined in the IoT Agent Framework Library.

Quality Assurance

The IoT Agent for Sigfox project is a new component within FIWARE and will be rated in the current release


🌱 Open MTC (Incubated)

License

:octocat: Git Repository 🐳 Docker Hub 📚 Documentation 📄 Site 🎓 Academy

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

Quality Assurance

The Open MTC project is part of FIWARE and has been rated as follows:

  • Version Tested:
  • Documentation:
  • Responsiveness:
  • FIWARE Testing:
You can’t perform that action at this time.