SlideShare a Scribd company logo
Connecting to the IoT
Carlos Ralli Ucendo
IoT Architect
@carlosralli
Connecting IoT Devices
to FIWARE
#SmartCities
#SmartAgrifood
#SmartIndustry
FIWARE: Tecnology for Smart*
#SmartRegions
NGSI CONTEXT INFORMATION
IoT Interoperability ? Still a $1,000,000 question
FIWARE IoT: Interoperability at Context Data Level
Satisfying Developers view
 Common language for all Data Sources (IoT and non-IoT).
 Single REST API. Query, Subscribe, Trigger Actions.
 Opensource solutions published in GitHub, Read-the-docs, etc
Context Broker
NGSI API
Boiler
• Manufacturer
• Last revision
• Product id
• Temperature
• Actions
Users
• Name-Surname
• Birthday
• Location
• ToDo list
City
• OpenData
• Users Input
Street Devices
• Location
• Observations
• Commands
Public Bus T.System
• Location
• Arrival time
APPs / Services / Data Scientist
Higher Efficiency
• Automatization
Higher IT Business
• Common suppliers
Previously: Sylos or Verticals Smartcity/Smart*
Higher Efficiency
Boost Overall Business
• Cros-vertical ideas
and services
• New Players
• Data Scientists
• Developers
• Share Networks, Cloud
FIWARE Smart*: Local Ecosystem growth engine
Smart* FIWARE most-used IoT Stack
Talking to IoT – Choosing an IoT-Agent
Use IoT Agents node.js
library to develop your
own IoT Agent.
Can I program my
devices/gateways to
support a given IoT
protocol?
Is your IoT network
lossy & unstable or
your devices too
constrained to
support HTTP/TCP?
Use LWM2M IoT Agent. UDP
is recommended for
constrained networks and
CoAP is REST for constrained
devices
Are your coding
Preferences/ libraries/
language handling better
JSON objects rather than
shorter text messages?
Use Ultralight2.0 IoT
Agent. Messages are
simple and light as
“t|25”
No
Yes
Use JSON IoT Agent.
Choose MQTT if RT
bidirectionality is a
must.
Yes
No
No
Ongoing Work
 Evolution of IoT Agents
• Include new functionalities such as data Transformations.
• New protocols.
• Consider IoT management.
 From Cloud-Centralized to Distributed models
• IoT Agents, NGSI Brokers and CEP at the IoT Gateway Level.
 (Context) Data Models
• Smartcities: OASC Alliance
• SmartAgrifood: IoF Project
 Federation and other implemantations of NGSI Brokers
• IoT Broker
 Market Dynamization
• FIWARE IoT Ready Program.
Thanks!Thanks!

More Related Content

Connecting to the IoT

  • 2. Carlos Ralli Ucendo IoT Architect @carlosralli Connecting IoT Devices to FIWARE
  • 3. #SmartCities #SmartAgrifood #SmartIndustry FIWARE: Tecnology for Smart* #SmartRegions NGSI CONTEXT INFORMATION
  • 4. IoT Interoperability ? Still a $1,000,000 question
  • 5. FIWARE IoT: Interoperability at Context Data Level Satisfying Developers view  Common language for all Data Sources (IoT and non-IoT).  Single REST API. Query, Subscribe, Trigger Actions.  Opensource solutions published in GitHub, Read-the-docs, etc Context Broker NGSI API Boiler • Manufacturer • Last revision • Product id • Temperature • Actions Users • Name-Surname • Birthday • Location • ToDo list City • OpenData • Users Input Street Devices • Location • Observations • Commands Public Bus T.System • Location • Arrival time APPs / Services / Data Scientist
  • 6. Higher Efficiency • Automatization Higher IT Business • Common suppliers Previously: Sylos or Verticals Smartcity/Smart*
  • 7. Higher Efficiency Boost Overall Business • Cros-vertical ideas and services • New Players • Data Scientists • Developers • Share Networks, Cloud FIWARE Smart*: Local Ecosystem growth engine
  • 9. Talking to IoT – Choosing an IoT-Agent Use IoT Agents node.js library to develop your own IoT Agent. Can I program my devices/gateways to support a given IoT protocol? Is your IoT network lossy & unstable or your devices too constrained to support HTTP/TCP? Use LWM2M IoT Agent. UDP is recommended for constrained networks and CoAP is REST for constrained devices Are your coding Preferences/ libraries/ language handling better JSON objects rather than shorter text messages? Use Ultralight2.0 IoT Agent. Messages are simple and light as “t|25” No Yes Use JSON IoT Agent. Choose MQTT if RT bidirectionality is a must. Yes No No
  • 10. Ongoing Work  Evolution of IoT Agents • Include new functionalities such as data Transformations. • New protocols. • Consider IoT management.  From Cloud-Centralized to Distributed models • IoT Agents, NGSI Brokers and CEP at the IoT Gateway Level.  (Context) Data Models • Smartcities: OASC Alliance • SmartAgrifood: IoF Project  Federation and other implemantations of NGSI Brokers • IoT Broker  Market Dynamization • FIWARE IoT Ready Program.