Fiware IoT_intro&scenarios
•Transferir como PPT, PDF•
1 gostou•2,628 visualizações
FIWARE IoT introduction and typical scenarios
Recomendados
Mais conteúdo relacionado
Mais procurados
Mais procurados (20)
Destaque
Destaque (11)
Semelhante a Fiware IoT_intro&scenarios
Semelhante a Fiware IoT_intro&scenarios (20)
Mais de FIWARE
Mais de FIWARE (20)
Último
Último (20)
Fiware IoT_intro&scenarios
- 1. FIWARE IoT:Beginner’s Intro Carlos Ralli Ucendo, @carlosralli . Telefonica I+D IoT Chapter Architect, FIWARE
- 2. FIWARE (IoT) Target: Developers Context Broker App Logic @FIWARE-Cloud Desktop/Mobile/Tablet User Interface Web 3D GE / Advanced UI Wirecloud GE / Dashboards OAuth2.0 SANTANDER SMARTSPACES SEVILLA 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. 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 MultiMedia Events Complex Event Processing IoT Geis Smartcities OpenData BigData Analytics
- 3. IoT Consumers: ContextBroker (Observations+Commands) 3 Developers need to know/discover the Ecosystem conventions. Examples: Developers may: •Query an Entity (whole set or specific attributes) or Subscribe to changes of attributes of Entities. •Discover all Entities (entity_IDs) or all Entities with a specific “type”. •Trigger commands to devices by updating command related attributes of NGSI entities. 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 My FIWARE-App Context Broker OAuth2.0 OMA NGSI10 - QueryContext OMA NGSI10 - SubscribeContext (type, entity_ID, attributes) Entities
- 5. IoT – Typical Scenario I (fully tested, most used so far) • Simplest scenario. • Extensively tested with developers. Most Feedback Implemented. • New features are required (Edge management, more Agents)
- 6. IoT – Typical Scenario II (under testing, native NGSI) • Added-value scenario. Still to be introduced in Hackathons (exercises, challenges, etc.) • Will work with non NGSI devices once it becomes Scenario III = I + II
- 8. FIWARE Community: Kick off @ CPE’13 8 1st Prize………….SmartAds Complete context-sensitive Ads solution developed in just 4 days & nights. Neelie Kroes FIWARE Lab Launch Hackathon + Challenges Announcements Massive, > 6K developers Mainly young entrepreneurs Talent Day&Night Involving developers, debugging, improving training sessions
- 9. FIWARE Community: Smartcities IoT Data & SMEs involvement 9 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. Winning Teams 33 succeeded building a product-like working App (of 77 registered developers) Several participants own a Start-up & keep on using FIWARE
- 10. FIWARE Community: Emerging IoT Trends fast adoption 10 iBeacons in FI-WARE by Context Team. •3rd prize within SmartBusiness FIWARE challenge. (Jan 2014 @ CPBR7 Sao Paulo)