Using FIWARE and Microsoft Azure for the
development of IoT solutions
02.12.2015.
Nebojša Stojanović
How we did it
IoT Overview• “Buzzword”• The term IoT was first used by
Kevin Ashton in 1999• Phases of Internet Evolution
I generate 200MB of information per year
I have 100.000 followers
I generate 100GB of information per year
Lots of generic components
Market needs IoT products
A Reference Architecture for IoT
Source: http://wso2.com/download/wso2_whitepaper_a-reference-architecture-for-the-internet-of-things.pdf
Ingestor (broker)
Collection Presentation & action
Event producers
Transformation
Long-term storage
Event Hubs
Storage adapters
Stream processingCloud gateways
(web APIs)
Field gateways
Applications
Legacy IOT (custom protocols)
Devices
IP-capable devices(Windows/Linux)
Low-power devices (RTOS)
Search and query
Data analytics (Excel)
Web/thick client dashboardsService
bus
Azure DBs
Azure storage
HDInsight
Stream Analytics
Devices to take action
Microsoft Azure IoT services
Source: blogs.msdn.com/b/petsablog/archive/2014/12/11/iot-for-mortals-part-i.aspx
FI-WARE Generic Enablers- IoT Services Enablement
Source: https://www.fiware.org/2015/03/27/build-your-own-iot-platform-with-fiware-enablers/
Our IoT solutions for creating smart environment
Our IoT solutions for creating smart environment
• End-to-end solution for the environment monitoring. • System components: measuring device, back-end
infrastructure and client applications (web and mobile).
ekoNET solution
IngestionCollection Presentation and action
Event producers
Transformation
Long-term storage
Event Hubs (Raw data)
Transformation Service (Event Processor Host)
EB800 device(HTTPS )
Access & device mgmt
Web/thick client dashboards
Web API
Azure DBs
Blob storage
Stream Analytics (Log Raw
Data)
ekoNET Azure hosted platform
RPi800 device(HTTPS )
Event Hubs (Transform
ed data)
Stream Analytics
(Log Transformed
Data)
Stream Analytics
(Save Transformed
Data)
Real-time data
Web Socket
ekoNET FIWARE set-up
Recommended
