Movatterモバイル変換

Introduction to FIWARE IoTFernando López AguilarFIWARE Cloud and Platform Senior Expertfernando.lopez@fiware.org@flopezaguilar(Reference Orion Context Broker version: 0.24.0)

2Open data publicationOnce context information is gathered, a lot of usefulcomplementary FIWARE enablers can be usedContext BrokerAdvanced Web-based UI (AR,3D)Data/Apps visualizationBig Data AnalysisComplex EventProcessingMultimedia processing

5FIWARE Catalogue (http://catalogue.fiware.org)5

6FIWARE Academy (http://edu.fiware.org)

FIWARE IoT: Interoperability at Context Data LevelSatisfying Developers view Common language for all Data Sources (IoT and non-IoT). Single REST API. Query, Subscribe, Trigger Actions. Open Source solutions published in GitHub, Read-the-docs, etc.Street Devices• Location• Observations• CommandsContext BrokerNGSI APIBoiler• Manufacturer• Last revision• Product id• Temperature• ActionsUsers• Name-Surname• Birthday• Location• ToDo listCity• OpenData• Users InputPublic Bus T.System• Location• Arrival timeAPPs / Services / Data Scientist

Tenemos un planWe have a plan :

13Smart* FIWARE most-used IoT Stack

IoT Agents Device Protocol to NGSI Bridge:• One entity per device.• Constrained set of interactions. Design principles:• Modular approach.• Deployment flexibility.• Simplify the creation of Custom IoT Agents. Provisioning of devices and groups of devices. IoT Manager. Additional services (e.g.: security, device registration, stats).14

Integration with sensor networks Smart solutions need to deal with the wide variety of IoT protocols today Rather than trying to solve the battle of standards at IoT level, it brings astandard where no standard exists today: context information management15Context BrokerIoTAgent-1IoTAgent-2IoTAgent-nIoT AgentManagercreate/monitorIoT FrameworkStandard API (northbound interface)(southbound interfaces)MQTTETSI M2M IETF CoAP

What FIWARE provides?1. Two out-of-the-box agents• IOTA-JSON (JSON payloads)• IOTA-UL (ultralight text-based data payloads)• Both support HTTP and MQTT transports2. A Node.js based SDK to program new IOTAs (iotagent-node-liblibrary)• Provides the common functionality for the northbound interface(provisioning, NGSI-based interaction with Orion Context Broker, etc.).• Protocol (transport and payload) is the part that has to be done by theIOTA developer using the library• IOTA-JSON and IOTA-UL has been implemented using this library3. The IoTManager component.16

Transport & Payload Device protocol = transport protocol + payload format Transports protocols• HTTP• MQTT• Others Payload format• UL (ultralight)• JSON• Others Transport and payload format are orthogonal, e.g.• HTTP transport using JSON payload• MQTT transport using JSON payload• HTTP transport using UL payload• MQTT transport using UL payload• Etc.17PhysicalLinkTCPMQTTPhysicalLinkTCPHTTP

Payload formats examples JSON Ultralight (UL)18{"h": "45%","t": "23","l": "1570"}h|45%|t|23|l|1570

Ultralight 2.0 (Measures) Simple HTTP-based protocol Measure reporting:• Key/Value pairs separated by | and #• POST request with plain/text content to the IoTA path:POST http://{{host}}:{{iota_ul-port}}/iot/d?k=&i={{device-id}}&t=2016-03-01T10:00:00Z Payload example:t|34#h|87#l|1900 Required query params• k: Service API Key• i: Device ID Optional query params• t: timestamp of the measure19

Interaction models: Active Attributes20IOT AgentDBDeviceProtocolNGSIEntityinformationInteractionbegins

Interaction models: Commands21IOT AgentDeviceProtocolNGSICommandExecutionInteractionbeginsResultInformationRequires the IOT Agent to beregistered as a ContextProvider

Attribute types Active attributes• Actively updated to CB Lazy attributes• Kept at the device, obtained using the CPr-forwardingmechanism Static attributes• As active attributes, but with a “fixed” value Commands• For actuation capabilities• Managed in a similar way to lazy attributes, but involving also aninfo and a status CB attributes22

Configuration API: Group provision Create service• /iot/services Not exactly REST (check doc)• POST• GET• DELETE• PUT Static attributes Mandatory• Resource• Api key• Entity Type23{"services": [{"apikey": "4jggokgpepnvsb2uv4s40d59ov","cbroker": "http://0.0.0.0:1026","entity_type": "thing","resource": "/iot/d"}]}

Configuration API: Device provision Create device• /iot/devices Not exactly REST (check doc):• POST• GET• DELETE• PUT Mandatory• Device_id• Entity_type• protocol Commands• endpoint24{"devices": [{"device_id": "my_device_01","entity_name": "my_entity_01","entity_type": "thing","protocol": "PDI-IoTA-UltraLight","timezone": "Europe/Madrid","attributes": [{"object_id": "t","name": "temperature","type": "int"},{"object_id": "l","name": "luminosity","type": "number"}]}]}

Sending Measurements: Ultralight 2.0 HTTP25Simple HTTP ProtocolAPI key (k)Device Id (i)Key Pair valuesPush and Pull commandsPOST /iot/d?k= k=4jggokgpepnvsb2uv4s40d59ov&i=my_device_01 HTTP/1.1Host: localhost:7896Content-Type: text/plainCache-Control: no-cachet|37#l|1200HTTP/1.1 200 OKContent-Length: 88Content-Type: text/htmlConnection: Closedmy_device_01@t|2| my_device_01@l|200

Orion Context Broker in a nutshell26

Context Broker operations: create & pull data Context Producer, publish data/context elements by invoking theupdate operation on a Context Broker. Context Consumer, can retrieve data/context elements by invokingthe query operations on a Context Broker.27

STH-COMET: Why?28 The Context Broker only storesthe latest attribute values:• Event-driven action-orientedparadigm The Short Time Historic addsmemory into the equation:• Continuous improvementparadigm

STH-COMET: What?29 Time series database:• Optimized to deal with valuesindexed in time• Raw data vs. Aggregated data• Basic aggregation concepts:□ Range□ Resolution□ Origin□ Offset

STH – Comet : How(birds-eye functioning: minimal)30updatequery (raw & aggregated)ClientOrionContextBroker

Help project content31Context BrokerIoT AgentUltralight 2.0STH - COMETMongoDB789640411026 8666Virtual Machine Instance Ansible and docker-compose file to deploy a Virtual Machine withOrion, IoT Agent Ultralight and Comet.https://github.com/flopezag/fiware-iot-hackathon Instruction to send data from sensor and recover them from Orion orComet (data aggregation)

Further reading IoT Agent-Ultralight• Base doc: https://github.com/fiware/iotagent-ul Orion Context Broker• Base doc: https://github.com/fiware/orion• ReadTheDocs: https://fiware-orion.readthedocs.io STH-Comet• Github repository: https://github.com/fiware/fiware-sth-comet• ReadTheDocs: https://fiware-sth-comet.readthedocs.io/en/latest32

Question & Answerfiware-tech-help@lists.fiware.orgfiware-lab-help@lists.fiware.org33

Thank you!http://fiware.orgFollow @FIWARE on Twitter34

Thank you!http://fiware.orgFollow @FIWARE on Twitter

Active attributes37…"attributes": [{ "object_id": "t", "name": "temperature", "type": "float" },{ "object_id": "h", "name": "humidity", "type": "float" }],…

Lazy attributes Q: Why all this complication? Why don’t use only active attributes?38…"lazy":[{ "object_id": "l", "name": "luminosity", "type": "percentage" }],…

Static attributes Similar to active attributes but…• They don’t correspond to actual measures sent by the physical device• They have a fixed value• They are attached to every IOTA-to-CB update operation Q: Why using static attributes?39…"static_attributes": [{ "name": "serialID", "type": "02598347", "value": "02598347" }]…

Commands Three supporting attributes at CB (per command)• <cmd> (write), the one used by the application (through update contextat CB) in order to execute command• <cmd>_status (read only), the one in which IOTA published status□ UNKNOWN: transient status, just after device provisioning and before anyexecution is done□ PENDING: command execution is in progress□ ERROR: command execution finished in error status□ FINISHED: command execution finished in ok status• <cmd>_info (read only): upon completion, the result of the commandexecution (if any) is published by IOTA in this attribute Example:• turn• turn_info• turn_status40…"commands": [{ "object_id": "u", "name": "turn", "type": "string" }],…

Commands41…"commands": [{ "object_id": "u", "name": "turn", "type": "string" }],…turn_statusturn_statusturn_info

Movatterモバイル変換

Change Language

Introduction to FIWARE IoT

Embed presentation

Recommended

More Related Content

What's hot

Similar to Introduction to FIWARE IoT

More from Fernando Lopez Aguilar

Recently uploaded

Introduction to FIWARE IoT

Editor's Notes