SlideShare a Scribd company logo
Introduction to FIWARE Cloud & Context Broker 
Fermín Galán, Telefonica I+D. 
fermin.galanmarquez@telefonica.com, @fermingalan (twitter) 
http://tinyurl.com/fiware-open-ecosystem
FIWARE = advanced OpenStack-based Cloud + 
rich library of Generic Enablers 
Driven by 
implementation 
Sustainability 
ensured 
2
FIWARE Generic Enablers (GEs) 
 A FIWARE Generic Enabler (GE): 
 Set of general-purpose platform functions available through APIs. 
 Building with other GEs a FIWARE Reference Architecture. 
 FIWARE GE Specifications are open (public and royalty-free). 
 FIWARE GE implementation (FIWARE GEi): 
 Platform product that implements a given GE Open Spec. 
 There might be multiple compliant GEis of each GE Open Spec. 
 At least one open source reference implementation of 
FIWARE GEs (FIWARE GEris): 
 Well-known open source license. 
 Publicly available Technical Roadmap updated in every release. 
 Available FIWARE GEis, GEris and incubated enablers 
published on the FIWARE Catalogue. 
3
FIWARE major differential features 
• Federation of infrastructures (private/public regions) 
• Automated GE deployment Cloud 
• Complete Context Management Platform 
• Integration of Data and Media Content Data 
•Easy plug&play of devices using multiple protocols 
•Automated Measurements/Action Context updates IoT 
• Visualization of data (operation dashboards) 
•Publication of data sets/services Apps 
•Easy support of UIs with advanced web-based 3D and AR 
capabilities 
•Visual representation of context information. 
4 
Web UI 
•Advanced networking capabilities (SDN) and Middleware 
• Interface to robots I2ND 
•Security Monitoring 
•Built-in Identity/Access/Privacy Management Security
FIWARE Lab (http://lab.fiware.org) 
5
Take the most of infrastructures while keeping 
costs lower and under control 
6
VM provisioning 
7
Gathering, publishing, processing and 
analyzing private and open data at large scale 
8
Context management 
• Context Management in FI-WARE is about management of Context data 
(aka Context Information) 
• Context Information is always relevant to “entities”, although entities can 
be anything (applications, users, things, …) 
• Orion Context Broker intermediates between context producers and 
context consumers 
Orion Context 
Broker Applications 
9
The NGSI information model 
Meta-data 
• Name 
• Type 
• Value 
Context Element attributes 
• Name 
• Type 
• Value 
Context Element 
• EntityId 
• EntityType 
“has” “has” 
1 n 1 n 
Orion metadata: ID, location 
Custom metadata 
Electrical Regulator 
Node Lamps 
Vans 
Issues location TimeInstant 
Technicians 
severity batteryCharge 
illuminance 
presence 
electricPotential 
10
Orion Context Broker in a nutshell 
Orion Context Broker 
Context 
Producers 
Context 
Consumers 
subscriptions 
update 
query 
notify 
notify 
update 
update 
DB 
1026 
1026 
11
NGSI API 
Context Availability 
Management (NGSI9) 
• Register context sources 
(registerContext) 
• Search for context sources 
(discoverContextAvailability) 
• Subscribe to context sources 
availability notifications 
(subscribeContextAvailability, 
updateContextAvailabilitySubcrip 
tion & 
unsubscribeContextAvailability) 
• REST API (XML & JSON rendering) 
• Additional “convenience” operations to ease some 
operations 
Context Management (NGSI10) 
• Update context information 
(updateContext) 
• Query context information 
(queryContext) 
• Subscribe to context information 
notifications (subscribeContext, 
updateContextSubcription & 
unsubscribeContext) 
12
Context Broker Resources for developers 
• Quick Start Guide 
– http://tinyurl.com/orion-quickstart 
• Single entry point: the FI-WARE Catalogue 
– http://catalogue.fi-ware.org/ 
– “Enablers” tab 
– “Data/Context management chapter” 
– Search for “Publish/Subscribe Context Broker - Orion 
Context Broker” 
• Direct URL: http://catalogue.fi-ware. 
org/enablers/publishsubscribe-context-broker-orion-context- 
broker 
• The core manuals are linked from “Documentation” tab 
13
Envisioned target Smart City platform 
IoT Broker & Config 
(from sensors to things) 
actuators Open Data 
14 
CEP 
Inventory 
• Smart city platform as 
a Data/Knowledge Hub 
• Non-intrusive, open to 
third parties 
CKAN 
Big Data 
Context Broker 
Accounting & Payment & Billing 
IDM & Auth 
Short-term 
historic 
data 
BigData 
Processing 
Data 
Quering/Action, 
Publish/Subscr 
Open Data 
publishing 
Real-time 
processing 
BI 
ETL 
RULES 
DEFINITION 
TOOL 
OPERATIONAL 
DASHBOARD 
KPI GOVERNANCE OPEN DATA PORTALS 
Service 
orchestrator 
Context 
Adapters 
Management 
IoT Backend 
DeviceManagement 
measures / 
commands 
IoT/Senso 
r 
Real Time 
Media 
Stream 
Processing 
Media 
streams 
City Services 
GIS 
Specific Enablers 
Generic Enablers
FIWARE Catalogue (http://catalogue.fiware.org) 
15
FIWARE University (http://edu.fi-ware.org) 
16
Thanks! 
Join us! 
www.lab.fiware.org

More Related Content

Introduction to FIWARE Cloud & Context Broker

  • 1. Introduction to FIWARE Cloud & Context Broker Fermín Galán, Telefonica I+D. fermin.galanmarquez@telefonica.com, @fermingalan (twitter) http://tinyurl.com/fiware-open-ecosystem
  • 2. FIWARE = advanced OpenStack-based Cloud + rich library of Generic Enablers Driven by implementation Sustainability ensured 2
  • 3. FIWARE Generic Enablers (GEs)  A FIWARE Generic Enabler (GE):  Set of general-purpose platform functions available through APIs.  Building with other GEs a FIWARE Reference Architecture.  FIWARE GE Specifications are open (public and royalty-free).  FIWARE GE implementation (FIWARE GEi):  Platform product that implements a given GE Open Spec.  There might be multiple compliant GEis of each GE Open Spec.  At least one open source reference implementation of FIWARE GEs (FIWARE GEris):  Well-known open source license.  Publicly available Technical Roadmap updated in every release.  Available FIWARE GEis, GEris and incubated enablers published on the FIWARE Catalogue. 3
  • 4. FIWARE major differential features • Federation of infrastructures (private/public regions) • Automated GE deployment Cloud • Complete Context Management Platform • Integration of Data and Media Content Data •Easy plug&play of devices using multiple protocols •Automated Measurements/Action Context updates IoT • Visualization of data (operation dashboards) •Publication of data sets/services Apps •Easy support of UIs with advanced web-based 3D and AR capabilities •Visual representation of context information. 4 Web UI •Advanced networking capabilities (SDN) and Middleware • Interface to robots I2ND •Security Monitoring •Built-in Identity/Access/Privacy Management Security
  • 6. Take the most of infrastructures while keeping costs lower and under control 6
  • 8. Gathering, publishing, processing and analyzing private and open data at large scale 8
  • 9. Context management • Context Management in FI-WARE is about management of Context data (aka Context Information) • Context Information is always relevant to “entities”, although entities can be anything (applications, users, things, …) • Orion Context Broker intermediates between context producers and context consumers Orion Context Broker Applications 9
  • 10. The NGSI information model Meta-data • Name • Type • Value Context Element attributes • Name • Type • Value Context Element • EntityId • EntityType “has” “has” 1 n 1 n Orion metadata: ID, location Custom metadata Electrical Regulator Node Lamps Vans Issues location TimeInstant Technicians severity batteryCharge illuminance presence electricPotential 10
  • 11. Orion Context Broker in a nutshell Orion Context Broker Context Producers Context Consumers subscriptions update query notify notify update update DB 1026 1026 11
  • 12. NGSI API Context Availability Management (NGSI9) • Register context sources (registerContext) • Search for context sources (discoverContextAvailability) • Subscribe to context sources availability notifications (subscribeContextAvailability, updateContextAvailabilitySubcrip tion & unsubscribeContextAvailability) • REST API (XML & JSON rendering) • Additional “convenience” operations to ease some operations Context Management (NGSI10) • Update context information (updateContext) • Query context information (queryContext) • Subscribe to context information notifications (subscribeContext, updateContextSubcription & unsubscribeContext) 12
  • 13. Context Broker Resources for developers • Quick Start Guide – http://tinyurl.com/orion-quickstart • Single entry point: the FI-WARE Catalogue – http://catalogue.fi-ware.org/ – “Enablers” tab – “Data/Context management chapter” – Search for “Publish/Subscribe Context Broker - Orion Context Broker” • Direct URL: http://catalogue.fi-ware. org/enablers/publishsubscribe-context-broker-orion-context- broker • The core manuals are linked from “Documentation” tab 13
  • 14. Envisioned target Smart City platform IoT Broker & Config (from sensors to things) actuators Open Data 14 CEP Inventory • Smart city platform as a Data/Knowledge Hub • Non-intrusive, open to third parties CKAN Big Data Context Broker Accounting & Payment & Billing IDM & Auth Short-term historic data BigData Processing Data Quering/Action, Publish/Subscr Open Data publishing Real-time processing BI ETL RULES DEFINITION TOOL OPERATIONAL DASHBOARD KPI GOVERNANCE OPEN DATA PORTALS Service orchestrator Context Adapters Management IoT Backend DeviceManagement measures / commands IoT/Senso r Real Time Media Stream Processing Media streams City Services GIS Specific Enablers Generic Enablers
  • 17. Thanks! Join us! www.lab.fiware.org

Editor's Notes

  1. Orion Context Broker is an implementation of a context information broker with persistent storage It implements OMA NGSI9/10 specification NGSI9 is about context information availability (i.e. sources of context information) management NGSI10 is about context information itself