This document discusses FIWARE's IoT proposal and community. It provides an overview of FIWARE's target IoT users and developers, including IoT consumers and providers. It describes the most common IoT scenarios in FIWARE involving the Orion Context Broker and IDAS/SBC components. It also outlines several options for connecting devices to FIWARE Lab, such as using the IDAS/SBC with UltraLight 2.0, MQTT, or CoAP/OMA-LWM2M protocols. Finally, it mentions some success stories around smart cities, smart spaces, and emerging trends like iBeacons.

1. FIWARE IoT Proposal & Community
Carlos Ralli Ucendo, Telefonica
IoT Chapter Architect, FIWARE
@carlosralli

2. FIWARE IoT Target Users/Developers
Context
Broker
Desktop/Mobile/Tablet
User Interface
3D Advanced Interfaces
UI Prototyping / Dashboards
App Logic
@FIWARE-Cloud
OAuth2.0
SANTANDER
SMARTSPACES
SEVILLA
1) IoT Consumers. Normally not just IoT.
• A single point, API & Protocol for IoT, OpenData, etc.
• Context: Data Entities + Data Entities events.
• A Public & Secured Ecosystem at FIWARE Lab
2) IoT Providers. Pretty Heterogeneous solutions/skills.
• An incremental approach. Public/Private instances.
• KISS philosophy for most (web)developers.
• Advanced IoT architecture, e.g. for IoT Advanced Devel.
MultiMedia Events
Complex
Event
Processing

3. IoT Consumers (IoT): Northbound Single Point (API/Protocol)
Entities
Developers need to know/discover the Ecosystem conventions. Examples:
Developers may:
•Query an Entity (whole set or specific attributes) or Subscribe to changes of atttibutes of Entities.
•Discover all Entities (entity_IDs) or all Entities with a specific “type”.
•Discover all Attributes of an specific Entity (entity_ID).
Full List of FIWARE Lab (Global Context Broker) conventions (section 3.5):
https://forge.fi-ware.org/plugins/mediawiki/wiki/fiware/index.php/Publish/Subscribe_Broker_-_Orion_Context_Broker_-_User_and_Programmers_Guide
3
My
FIWARE-App
Context
Broker
OAuth2.0
OMA NGSI10 - QueryContext
OMA NGSI10 - SubscribeContext
(type, entity_ID, attributes)

4. IoT Providers: Connect any “Thing”/System to FIWARE Lab
NGSI9/10
SML, UL2.0, MQTT, ETSIM2M, CoAP/OMA-LW
2.3 Advanced Scenarios
4
Context
Broker
OAuth2.0
2.1 OMA NGSI Agent
2.2 IoT BE (IDAS/SBC)
Your IoT IoT
Backend
Gateway GEs Backend GEs
NGSI
Propietary
Zigbee
Zwave
CoAP/MTRunner
ETSIM2M
CoAP/LWM2M

5. FIWARE IoT: Most Common Scenarios (2.1 & 2.2)
Context
Broker
5
User
Interface
App Logic
FI-WARE Cloud
Dashboards
UI Prototyping
OAuth2.0
SANTANDER
SEVILLA
IDAS Portal/
ADMIN API
IDAS
SMARTSPACES SBC
Commands
Commands
(Future Delivery)
Commands
2.1
2.2
2.2
IDAS
SBC

6. FIWARE IoT: Advanced Scenario (2.3). Visit our demo at FIWARE booth

http://wiki.fi-ware.org/Internet_of_Things_(IoT)_Services_Enablement_Architecture
6

7. Success Stories: Kick off @ CPE’13
7
1st Prize………….SmartAds
Complete context-sensitive Ads solution developed
in just 4 days & nights.
Massive, > 6K developers
Mainly young entrepreneurs
Neelie Kroes FIWARE Lab Launch
Hackathon + Challenges Announcements
Talent
Day&Night
Involving developers, debugging, improving training sessions

8. Success Stories: Smartcities & SMEs involvement
Smartcity resources exploitation, involve local market & public policies makers
1st Prize………….MagicBox…………………………………………….….…..…TVs displaying Smartcities & Smartspaces.
2nd Prize………….FI-BOT……………………………………………………..….…Robotics exploiting opendata & sensors.
3rd Prize.…………OpenAlerts……..…..............................................Interfaces for citizens (mobile If-Then App).
4th Prize………….Traffic Heatmap…..............................................Traffic routing based on city real-time Info.
8
Winning Teams
33 succeeded building a product-like working App (of 77 registered developers)
Several participants own a Start-up & keep on using FIWARE

9. Success Stories: Emerging Trends fast adoption
9
iBeacons in FI-WARE by Context Team.
•3rd prize within SmartBusiness FIWARE challenge.
(Jan 2014 @ CPBR7 Sao Paulo)

10. Our OpenData/IoT Resources Ecosystem is growing fast
10
SANTANDER
SEVILLA
MALAGA
TRENTO

11. Connect your IoT to FIWARE Lab. Option 1. IDAS/SBC Ultralight2.0
Step 1 – Create Model API-Key (devices auth)
Step 2 – Create Asset (device)
Step 3 – Send Measurements
Step 4 – Send Commands
SBC Testing details:
•IPv4: 130.206.80.47
•IPv6: 2001:720:1514:80::47
•UL2.0 Port: 8002 (only IPv4)
•REST API Port: 5371 (IPv4/IPv6)
•REST API URI:
<SBC_HOST>/m2m/v2/services/OpenIoT

12. Connect your IoT to FIWARE Lab. Option 1. IDAS/SBC Ultralight2.0
Step 1 – Create Model
(SML phenomenons)

13. Connect your IoT to FIWARE Lab. Option 1. IDAS/SBC Ultralight2.0
Step 2 – Create Asset
(logical device)

14. Connect your IoT to FIWARE Lab. Option 1. IDAS/SBC Ultralight2.0
Step 3 – Send Measurements
(Mapping to UL2.0)

15. Connect your IoT to FIWARE Lab. Option 1. IDAS/SBC Ultralight2.0
Step 4 – Sending Commands to Devices

16. Connect your IoT to FIWARE Lab. Option 1. IDAS/SBC Ultralight2.0
Step 4.1 – Register Command URL (from REST API or Devices itself)
Step 4.2 – Send Commands via IDAS/SBC REST API

17. Connect your IoT to FIWARE Lab. More Southbound Options
Option 2. IDAS/SBC MQTT3.1
•SW Ready, manuals coming up soon.
•Devices publish measures as MQTT clients.
•Devices subscribe for commands at SBC (MQTT broker).
Message formatting aligned to UL2.0
•Topic: <api-key>/</device-id>/<alias> or <api-key>/</device-id>/multi
•Payload: <measure_value> or <alias1>|<value1>#<alias2>|<value2>..
Receiving Commands
•Collect pending Commands: <api-key>/<device_id>/cmdget
•Receive Commands: <api-key>/<device_id>/cmd/+
Commands received:
•Topic: <api-key>/<device_id>/cmd/<new_topic_level>
•Payload: cmdid|<cmid>#<param1>|<value1>…
SBC

18. Connect your IoT to FIWARE Lab. More Southbound Options
Option 3. IDAS/SBC CoAP/OMA-LWM2M.
•Planned for early 2015.
Extra tools. IDAS/SBC + RaspberryPI GW
•https://github.com/telefonicaid/fiware-figway/
•Currently SML & NGSI protocols.
•Planned UL2.0 for early 2015.

19. TThhaannkkss!!