Connecting FIWARE-ready HOP Ubiquitous ... - FIWARE Catalogue

1 downloads 141 Views 639KB Size Report
SIGFox Cloud: https://github.com/telefonicaid/sigfox-iotagent. Additionally, any new ... such as "Server", "Security", "
Connecting FIWARE-ready HOP Ubiquitous devices to FIWARE IoT platforms (Orion Context Broker) 1. What is FIWARE IoT FIWARE is an open software ecosystem provided by the FIWARE Community (htttp://www.fiware.org). FIWARE exposes to developers Data Context elements or entities (JSON objects) with attributes and metadata with a uniform REST API (NGSI9/10). NGSI is now being adopted by more than 90 Smart Cities worldwide as part of the Open and Agile Smart Cities (OASC). Orion Context Broker is available at: http://bit.ly/github-ContextBroker FIWARE IoT is an Open Source software stack aiming to bring Data-level interoperability to the complex salad of standards and protocols in the world of IoT today. FIWARE IoT is able to expose, by means of the Orion Context Broker component, all IoT devices information and commands using the Data Context API (NGSI).

Figure 1. Orion Context Broker ecosystem.

Any IoT standard or proprietary protocol can be connected to FIWARE via the IoTAgent components. Currently FIWARE IoT is providing IoT-Agents for:  Ultralight2.0/HTTP: http://bit.ly/fiware_iot-ul20  MQTT/TCP: http://bit.ly/fiware_iot-ul20  LWM2M/CoAP: http://bit.ly/fiware_iot-lwm2m-coap  SIGFox Cloud: https://github.com/telefonicaid/sigfox-iotagent Additionally, any new standard or proprietary protocol might be implemented using this node.js IoT-Agent library:  https://github.com/telefonicaid/iotagent-node-lib or this C++ library:  https://github.com/telefonicaid/fiware-IoTAgent-Cplusplus

2. How to use HOP devices with FIWARE HOP Ubiquitous offers several solutions both outdoor and indoor sensorization and actuation but all of them, from simple beacon to Smart POIs for Smart Cities. All of them are integrated in the Internet of Things world via LwM2M protocol.

Figure 2. Temperature/Humidity sensor, Flood sensor and Smart POI (Beacon)

OMA LwM2M protocol allows connecting to any backend supporting OMA LwM2M, thereby devices can be not only managed from our own platform (Homard platform), else it can be also managed by third party platforms such as FIWARE. HOP Ubiquitous, as part of the solution offers also the IoT platform to manage the integration with third party platforms, Figure 2 presents an screenshot from the platform. Homard offers the possibility to manage the devices and other tasks such as firmware upgrade over the air, remote configuration, statistics provisioning, information reporting, etc.

Figure 3. Homard frontend screenshots

3 Configuring HOP devices with LightweightM2M IoT-Agent 3.1 Intro & Requirements LwM2M is a device management protocol created by the Open Mobile alliance which allows the remote manipulation of constrained devices in the Internet of Things. This complete protocol defines the procedures for provisioning, commissioning and management of a device through the definition of the resources exposed by the device. The functionality of LwM2M protocol is carried out through a set of basic objects such as "Server", "Security", "Device", "Statistics", ... but there are also more specific objects defined by the IPSO Alliance which aims to cover the need common definitions for sensors such as temperature/humidity/presence / etc. or actuators such as power/light/load control, buzzers, etc. CoAP (Constrained Application Protocol) defines the message header, request/response codes, message options and retransmission mechanisms, this protocol together with UDP is used by LwM2M as a transport mechanism. There are a large variety of topologies on the IoT but they have three common parts; devices, routers and backends. In some scenarios, routers are transparent for the end-devices such as cellular technologies, examples are: GSM, SigFox, NarrowBand IoT or Wi-Fi Hallow, since they are already deployed by Telco’s. Others, such as Wi-Fi, Bluetooth, 6LoWPAN and Z-Wave are provided individually with the devices. In HOP Ubiquitous our technology is mainly based on GSM and Bluetooth 4.0. The IoT stack is presented in the Figure 4. Devices support IPv4/IPv6 connectivity and OMA LwM2M in conjunction with IPSO Objects.

Figure 4. IoT Stack from HOP Ubiquitous devices

3.2 Configuring HOP devices to send data to FIWARE IoT The device configuration will be carried out through a simple interface on the Homard frontend where to specify the IoTAgent IP address. As future feature, the interface could display a drop-down menu to select the desired deployment where to integrate the devices, which basically are IoTAgent instances pointing to different Orion Context Broker projects/smart cities. After configure the IoTAgent instance, the Homard frontend will carry out the next steps:  Service provisioning on the specified IoTAgent, if the service was not previously created in the instance. This procedure is carried out through an HTTP request addressed to the administration port of the LwM2M

IoTAgent. Next block shows an example of this kind of petition, where a service to group Smart Meet Room devices is created. curl localhost:4041/iot/services -s -S --header 'Content-Type: application/json' \ --header 'Accept: application/json' --header 'fiware-service: HOPSmartMeetRoom' --header 'fiware-servicepath: /hopsmr' \ -d @- | python -mjson.tool)