Presentation by Daniel Calvo R&D Engineer – Energy Sector, Atos FIWARE Global Summit 27-28 November 2018 Malaga, Spain

1. Connecting sensors to FIWARE with IDAS
Overview
Daniel Calvo
IoE Lab. ATOS Research & Innovation
daniel.calvo@atos.net
@danicalvoalonso

2. 1
Connecting
to IoT
IDAS framework IoT Agents New & deprecated
features

3. Connecting to IoT
2

4. What is the IoT?
3
“Internet is connected to the physical world via ubiquitous
sensors”
“Sensor technology enable computers to observe, identify
and understand the world without the limitations of human-
entered data”
Kevin Ashton
Coiner of the term IoT in 1999

5. What is the IoT?
4
https://atos.net/content/mini-sites/journey-2020/index.html

6. What is the IoT?
5
https://www.ericsson.com
2014 2015 2016 2017 2018 2019 2020 2021
Connected devices (billions)
0
25
20
15
10
5
30
Cellular IoT
Non-cellular IoT
PC/laptop/tablet
Mobile phones
Fixed phones

7. What elements are part of the IoT?
6
Users
Applications
IoT Platforms
Communication
Devices

8. IoT Interoperability ? Still a $1,000,000 question
9

9. FIWARE Smart*: Local Ecosystem growth engine
10
Devices NDevices 1 Devices 2
Smart City / Authorities / Citizens
Communication NCommunication 1 Communication 2
New system M
Context Data Ecosystem
IoT Agent 1 IoT Agent 2 IoT Agent N IoT Agent M

10. FIWARE Smart*: Local Ecosystem growth engine
§ Higher efficiency
• Shared networks
• Cloud
§ Boost overall business
• Cross vertical ideas and services
• New players
• Data scientists
• Developers
• Ease the integration of new protocols
and devices
11

11. FIWARE IoT Stack
IoT Devices
Comm
South API
IoT Agents
North API
Context broker
12

12. IDAS Framework
13

13. IoT Communication Protocols
14
Range
Speed
< 3m < 5km < 100km
bps
Kbps
Mbps

14. IoT Devices: constrained nodes
15
ARM Cortex-M3 32 MHz
~MB Flash, ~KB RAM
ZigBee, GRPS, IEEE 802.15.4
Low power consumption
mode
Contiki OS, FreeRTOS, RIOT

15. IoT Agents: Connecting IoT Protocols to FIWARE
16
APPLICATION
TRANSPORT
SIMPLIFIED OSI
NETWORK
LINK
PHYSICAL
CoAP
802.15.4
UDP
IoT Device
IPv6, RPL
6LoWPAN
App protocol
IoT Agent
TCP
CONTEXT BROKER
IPv4
HTTP
NGSI /REST
1000s of bytes
10/100s of bytes

16. IoT Agents: Connecting IoT Protocols to FIWARE
17
APPLICATION
TRANSPORT
SIMPLIFIED OSI
NETWORK
LINK
PHYSICAL
CoAP
802.15.4
UDP
IoT Device
IPv6, RPL
6LoWPAN
App protocol
IoT Agent
802.15.4
UDP
IPv6, RPL
6LoWPAN
IPv4
TCP
CoAP
App protocol
HTTP
NGSI/REST
TCP
CONTEXT BROKER
IPv4
HTTP
NGSI /REST
1000s of bytes
10/100s of bytes

17. IoT Agents’ features
18
IoT Agent
IoT Agent Lib
Agent Ad-hoc
Context broker
IoT Device
External system

18. IoT Agents’ features
19
IoT Agent
IoT Agent Lib
Agent Ad-hoc
Context broker
IoT Device
External system
1. IoT Agent Registers the device
1.

19. IoT Agents’ features
20
IoT Agent
IoT Agent Lib
Agent Ad-hoc
Context broker
IoT Device
External system
1. IoT Agent Registers the device
2. Device sends information updates
1.
2.

20. IoT Agents’ features
21
IoT Agent
IoT Agent Lib
Agent Ad-hoc
Context broker
IoT Device
External system
1. IoT Agent Registers the device
2. Device sends information updates
3. Agent sends NGSI request
1.
2.
3.

21. IoT Agents’ features
22
IoT Agent
IoT Agent Lib
Agent Ad-hoc
Context broker
IoT Device
External system
1. IoT Agent Registers the device
2. Device sends information updates
3. Agent sends NGSI request
4. External system modifies CB data
1.
2.
3.
4.

22. IoT Agents’ features
23
IoT Agent
IoT Agent Lib
Agent Ad-hoc
Context broker
IoT Device
External system
1. IoT Agent Registers the device
2. Device sends information updates
3. Agent sends NGSI request
4. External system modifies CB data
5. Context broker updates device value
1.
2.
3.
4.
5.

23. IoT Agents’ features
24
IoT Agent
IoT Agent Lib
Agent Ad-hoc
Context broker
IoT Device
External system
1. IoT Agent Registers the device
2. Device sends information updates
3. Agent sends NGSI request
4. External system modifies CB data
5. Context broker updates device value
6. Device receives command
1.
2.
3.
4.
5.
6.

24. IoT Agents’ features
25
IoT Agent
IoT Agent Lib
Agent Ad-hoc
Context broker
IoT Device
External system
1. IoT Agent Registers the device
2. Device sends information updates
3. Agent sends NGSI request
4. External system modifies CB data
5. Context broker updates device value
6. Device receives command
1.
2.
3.
4.
5.
6.
NGSI
IoT
Comm

25. IoT Agents: device to NGSI mapping
§ Each IoT Device is mapped to a CB Entity
§ Each IoT resource is mapped to CB attribute
26
• devID0001
• remoteType
Entity
• temperature
• float
• 25.4
Attribute
• heartRate
• integer
• 80
Attribute

26. IoT Agents: active attributes
27
http://www.smartdubai.ae

27. IoT Agents: active attributes
28
IoT Agent
IoT Agent Lib
Agent Ad-hoc
Context broker
IoT Device
External system
1.
2.
3.
NGSI
IoT
Comm
1. Device sends information updates
2. Agent sends NGSI request
3. External system is notified or queries CB
data
§ Device may sleep to reduce energy
consumption

28. IoT Agents: lazy attributes
29

29. IoT Agents: lazy attributes
30
IoT Agent
IoT Agent Lib
Agent Ad-hoc
Context broker
IoT Device
External system
1. External system queries CB
2. CB queries IoT Agent as Context
provider
3. IoT Agent queries device
§ Device may be listening to queries
3.
1.
4.
NGSI
IoT
Comm
2. 5.

30. IoT Agents: commands
31
https://atmelcorporation.files.wordpress.com

31. IoT Agents: commands
32
IoT Agent
IoT Agent Lib
Agent Ad-hoc
Context broker
IoT Device
External system
1. External system sets attribute in CB
2. CB updates context in IoT Agent as
Context provider
3. IoT Agent answers with PENDING
4. IoT Agent sends command to device
5. Device answers with command result
6. IoT Agent updates context in CB
4.
1.
5.
NGSI
IoT
Comm
2. 3. 6.

32. IoT Agents
35

33. Main IoT Agents available: Ultralight 2.0
36
APPLICATION
TRANSPORT
SIMPLIFIED OSI
NETWORK
LINK
PHYSICAL
MQTT / HTTP /
AMQP
TCP
IoT Device
ULTRALIGHT
IoT Agent
TCP
IPv4
TCP
MQTT / HTTP /
AMQP
ULTRALIGHT
HTTP
NGSI/REST
TCP
CONTEXT BROKER
IPv4
HTTP
NGSI /REST

34. Main IoT Agents available: Ultralight 2.0
§ Measure payload syntax
• temperature | 15 | position | up
§ Does not support lazy attributes
§ https://github.com/telefonicaid/iotagent-ul
§ Un-appropriate for:
• Really constrained devices
• Low-Power and Lossy Networks (LLNs),
§ Data model based on shorter text messages
37

35. Main IoT Agents available: JSON
38
APPLICATION
TRANSPORT
SIMPLIFIED OSI
NETWORK
LINK
PHYSICAL
MQTT / HTTP /
AMQP
TCP
IoT Device
JSON
IoT Agent
TCP
IPv4
TCP
MQTT / HTTP /
AMQP
JSON
HTTP
NGSI/REST
TCP
CONTEXT BROKER
IPv4
HTTP
NGSI /REST

36. Main IoT Agents available: JSON
§ Measure payload syntax
• {“temperature”: 40.2, “position”: “left”}
§ Does not support lazy attributes
§ https://github.com/telefonicaid/iotagent-json
§ Un-appropriate for:
• Really constrained devices
• Low-Power and Lossy Networks (LLNs),
§ Data model based on JSON standard objects
39

37. Main IoT Agents available: OMA Lightweight M2M
40
http://openmobilealliance.org

38. Main IoT Agents available: OMA Lightweight M2M
41
APPLICATION
TRANSPORT
SIMPLIFIED OSI
NETWORK
LINK
PHYSICAL
DTLS / CoAP
UDP
IoT Device
LWM2M
IoT Agent
UDP
IPv4
TCP
DTLS / CoAP
LWM2M
HTTP
NGSI/REST
TCP
CONTEXT BROKER
IPv4
HTTP
NGSI /REST

39. Main IoT Agents available: OMA Lightweight M2M
§ Object model
• Based on Object and Resource hierarchy (e.g.: /1/12/3)
• OMA Registry
§ https://github.com/telefonicaid/lightweightm2m-iotagent
§ Appropriate for:
• Really constrained devices
• Low-Power and Lossy Networks (LLNs),
42

40. Main IoT Agents available: OPC-UA
43

41. Main IoT Agents available: LoRaWAN
44

42. IoT Agents overview
JSON Ultralight OMA LWM2M LoRaWAN OPC UA
Data model JSON Ultralight OMA LWM2M CayenneLpp /
CBOR
OPC UA
Comm.
Protocols
HTTP / MQTT
/ AMQP
HTTP / MQTT
/ AMQP
LWM2M
(CoAP)
LoRaWAN OPC UA
Active atts Yes Yes Yes Yes Yes
Lazy atts No No Yes No Yes
Commands Yes Yes Yes No Yes
Node.js
support
4, 6, 8 & 10 4, 6, 8 & 10 6, 8 & 10 8 & 10 8
45

43. How to start… First, choose your flavour!!
48

44. § https://github.com/telefonicaid/iotagent-node-lib
§ https://github.com/telefonicaid/iotagent-json
§ https://github.com/telefonicaid/iotagent-ul
§ https://github.com/telefonicaid/lightweightm2m-iotagent
§ https://github.com/Atos-Research-and-Innovation/IoTagent-LoRaWAN
§ https://github.com/Engineering-Research-and-Development/iotagent-opcua
§ https://fiware-tutorials.readthedocs.io/en/latest/
How to start… Then, docs, requirements and tutorials
49

45. How to start… Finally, node/npm or docker?
50

46. New and deprecated features
51

47. A very active GE!!
52
§ Commits to iotagent-node-lib
§ More than 200 PRs during 2018
§ Active contributors from

48. New features released during 2018
53
§ Full support to NGSIv2
• Active attributes reporting, including all plugins
• Device provisioning (entity creation and context registration)
§ Improved configurability with environment variables
§ Updated documentation
§ Full support to Node.js v8 and v10
• Updated dependencies and docker images
• Deprecation timeline for Node.js v4 and v6
§ Improved security
• Support to HTTPS
• Integration with new version of FIWARE IDM KeyRock (to be released in December
2018)

49. Deprecation timeline
54
11/2018 01/2019 05/2019
Node.js 4 (Argon)
Node.js 6 (Boron)
Node.js 8 (Carbon)
Node.js 10 (Dubnium)
§ Node.js v12 will be added in October 2019

50. FIWARE Release 7.5
IoT Agent Version
iotagent-node-lib 2.8.0
iotagent-json 1.9.0
iotagent-ul 1.8.0
lightweightm2m-iotagent 1.0.0
iotagent-lorawan 1.1.0
iotagent-opc-ua 1.0.0
55

51. Thank you!
http://fiware.org
Follow @FIWARE on Twitter
Daniel Calvo
IoE Lab. ATOS Research &
Innovation
daniel.calvo@atos.net