Introduction to FIWARE Open Ecosystem
Download as PPTX, PDF13 likes4,903 views
The document introduces the FIWARE open ecosystem, which provides an advanced open standard platform aimed at fostering innovation and avoiding vendor lock-in through a federation of infrastructures, generic enablers, and cloud-based services. It highlights the benefits of an open and sustainable ecosystem for developers, entrepreneurs, and technology providers, facilitating easier connections and efficient data management in areas like smart cities. The overarching goal is to stimulate local economy growth and job creation by enabling diverse applications and leveraging real-time data across multiple domains.
![Why FIWARE
Driver What is needed? What does FIWARE bring?
Technology Open, driven by implementation, specs (open
source reference implemenation)
Sustainable investment over time
Open specifications backed by open source
reference implementations (see [1], [2])
100+ M€ of investment (2011-2016)
Experimental
environment
Ability to experiment with real data coming from
cities (not just open historic datasets but real-time
dat).
Free Cloud capacity enabling entrepreneurs to test
and host a permanent showcase of their
applications.
15 cities (7 in Spain) already working on setting
up a connection to FIWARE Lab [3]
3000+ cores, 16Tb RAM and 750+ Tb HD will be
the free computing capacity provided by the
FIWARE Lab Cloud across 16 nodes distributed in
Europe
Incentives for
creating the
ecosystem
Engagement of technology providers,
entrepreneurs, data providers, customers
Funding for first entrepreneurs joining the
ecosystem.
Invesment in promotion and dissemination activities
52 partners, 13 countries (just FIWARE)
100 M€ devoted to fund entrepreneurs in 2014-
2016. Additional opportunities in Horizon 2020.
6,2+ M€ devoted to dissemination
Global footprint Helping entrepreneurs and technology providers to
create opportunities not just in Europe but other
regions (Latam, Asia and, why not, USA)
FIWARE Lab nodes in Mexico and Brazil.
Conversations between EC and public authorities
in Mexico and Brazil to explore collaboration
opportunities
[1] – http://wiki.fi-ware.org/Summary_of_FIWARE_Open_Specifications
[2] – http://catalogue.fi-ware.org
55
[3] – http://lab.fi-ware.org](https://image.slidesharecdn.com/introductiontofi-wareopenecosystemv2-140917043753-phpapp02/85/Introduction-to-FIWARE-Open-Ecosystem-55-320.jpg)
Introduction to FIWARE Open Ecosystem
- 1. Introduction to FIWARE Open Ecosystem Fernando López, Fermín Galán, Sergio García Telefonica I+D. fernando.lopezaguilar@telefonica.com, @flopezaguilar (twitter) fermin.galanmarquez@telefonica.com, @fermingalan (twitter) sergio.garciagomez@telefonica.com http://tinyurl.com/fiware-open-ecosystem
- 2. The Internet will again transform the daily life of individuals and businesses The Next Computer 2
- 3. Ecosystem and platform: two tied concepts Open Standard Platform ecosystem open sustainable global 3
- 4. FIWARE = advanced OpenStack-based Cloud + rich library of Generic Enablers Driven by implementation Sustainability ensured 4
- 5. Why an open standard platform is required 5 • Avoid vendor lock-in: – Standard Southbound APIs for sensor providers. – Standard Northbound APIs offered to applications. – Portability among platform providers. – Interoperability of solutions enabled by the platform. • Larger community of developers – True innovation. – Better prices. • Not any standard is enough – Modularity. – Allow different business models. – Integration with standard open data platform. – Non-intrusive.
- 6. 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. 6
- 7. 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. 7 Web UI •Advanced networking capabilities (SDN) and Middleware • Interface to robots I2ND •Security Monitoring •Built-in Identity/Access/Privacy Management Security
- 8. FIWARE Lab: going beyond technology, the “meeting point” where innovation takes place Entrepreneurs, Developers • Develop once for a large market • Easily meet potential customers • Marketing, promotion • Ability to test with real data and end users • Simple yet powerful APIs that accelerate product development App Customers and Data providers • Connect to entrepreneurs • Put their data at work • Bring new innovative services to end users • Be more efficient • Social Reputation FIWARE Technology Providers • “Competitive” approach • Connect to entrepreneurs: jointly exploit the opportunities 4,2 M€ promotion campaign • Campus Party events • Startup Weekend events • Chambers of Commerce • 870 K€ in prizes 100 M€ of funding devoted to entrepreneurs in phase 3 of the FIWARE program 8
- 10. Take the most of infrastructures while keeping costs lower and under control 10
- 15. Management of Blueprints 15
- 16. Gathering, publishing, processing and analyzing private and open data at large scale 16
- 17. Context Management in FIWARE • A simple yet powerful standard API should be defined that helps programmers to manage Context information. • Context information refers to the values of attributes characterizing entities relevant to applications 17 API Bus • Location • No. passengers • Driver • Licence plate Person • Name-Surname • Birthday • Preferences • Location • ToDo list Shop • Location • Business name • Franchise • offerings My Application
- 18. Context Management in FIWARE • Context information may come from many sources using different interfaces and protocols … but programmers should just care about entities and their attributes … What’s the current temperature in place “X”? Place = “X”, temperature = 30º 18 API A sensor in a pedestrian street The Public Bus Transport Management system It’s too hot! A person from his smartphone
- 19. Context Management in FIWARE • Programmers may want to get notified when an update on context information takes place … Bus = “X”, last_stop = “A”, arrived= “Yes” push 19 Notify me when bus “X” arrives at the bus stop “A” API
- 20. Context Management in FIWARE • Acting on certain devices should be as easy as to change the value of attributes linked to certain entities Street Lamp lamp1.status “on” Street lamp = “lamp1”, status= “on” 20 API
- 21. Basic Context Broker operations (1) • Context Producers publish data/context elements by invoking the updateContext operation on a Context Broker. • Context Consumers can retrieve data/context elements by invoking the queryContext operation on a Context Broker Context Consumer queryContext updateContext Context Producer Context Broker 21
- 22. Basic entities and operations (2) • Context Consumers can be subscribed to reception of context information complying with certain conditions, using the subscribeContext operation a ContextBroker exports. Such subscriptions may have a duration. • The Context Broker notifies updates on context information to subscribed Context Consumers by invoking the notifyContext operation they export Application subscription_id = subscribeContext (consumer, expr, duration) notifyContext (subscription_id, data/context) Context Broker Context Consumer 22
- 23. Basic entities and operations (3) • Context Providers can be registered to the Context Broker linked to certain context information. • A Context Broker will invoke the queryContext operation exported by Context Providers whenever they are queried for context information or have to notify updates in context information 23 Application registerContext (producer URI, registration data, duration, registration_id) queryContext Context Provider Context Broker Context Consumer queryContext
- 24. Integration with existing systems • Context adapters will be developed to interface with existing systems (e.g., municipal services management systems in a smart city) acting as Context Providers, Context Producers, or both • Some attributes from a given entity may be linked to a Context Provider while other attributes may be linked to Context Producers System A System B 24 queryContext (e1, attr1, attr2) queryContext (e1, attr1) Context Provider updateContext (e1, attr2) Context Consumer Application Context Broker
- 25. Easing connection to the physical world 25
- 26. Integration with sensor networks • The backend IoT Device Management GE enables creation and configuration of NGSI IoT Agents that connect to sensor networks • Each NGSI IoT Agent can behave as Context Consumers or Context Providers, or both OMA NGSI API (northbound interface) FIWARE Context Broker 26 IoT Agent-1 IoT Agent-2 IoT Agent-n IoT Agent Manager create/monitor FIWARE Backend IoT Device Management (southbound interfaces) ETSI M2M MQTT IETF CoAP
- 27. FIWARE IoT-M2M & Context/Management altogether 27 NGSI IoT Agents IoT Backend Device Management Backen d Applications CEP Sensor2Things FIWARE NGSI-9/10 IoT-enabled Context Management Backend BigData Analysis ContextBroker Other sources Gateway/Device Platform GEs Gateway/Device Platform GEs Gateway/Device Platform GEs Gateway/Device Platform GEs Native NGSI IoT Agent Native NGSI IoT Agent
- 28. Context Processing and Analysis Programming of rules NGSI-9/10 Complex Event Processing 28 (CEP) Simple Processing (aggregation, averages, …) Sensor2Things BigData Analysis (COSMOS) Context Broker Context Management Processing and Analysis NGSI-9/10 Context Source s Applications
- 29. CEP Technology – expanding the ECA paradigm • From Event-Condition-Action to Pattern-Condition-Action • In certain scenarios, single events are insignificant, a CEP engine can detect combinations of events which are meaningful, called situations, and generate derived events. CEP Authoring Tool CEP Engine Definitions Detected Situations Event Sources Build Time Run Time Input Events Event Processing Rules / Patterns Output Events (Detected Situations)
- 30. Cosmos / Big Data overview • Cosmos + Infinity – Ephemeral private Hadoop computing clusters management – Security enhanced HDFS-based permanent storage Infinity Server Infinity API Hadoop Namenode Datanode HDFS HDFS … Datanode New data Cosmos Master Node Cosmos API Infrastructure Hadoop HDFS Software Hadoop HDFS Cluster Node … Cluster Node App
- 31. The Stream Oriented Generic Enabler Infrastructure-based streaming architecture Media infrastructure Record Process Augment Analyze Mix Media source Media sink • Most important protocols and codecs (WebRTC, H.264) • Real Time communications (B2B UA, MCU router and mixer) • VoD: Media recording & Media playing • Seamless Computer Vision algorithms: detection, tracking... • 2D Agumented reality: 2D overlays, alpha blending,...
- 32. (Open) Data Platform • Search & Discover Data: – keywords, browse by facets, previews & visualization – REST/Json APIs to access data and metadata • Data Management for publishers – Easy store & update of metadata. – Worflows & authorization – Support of private datasets acquisition from FIWARE Store & Data Portal.
- 33. Offering rich web-based user interfaces 33
- 34. Data/Applications Visualization and Delivery 34
- 35. Reaching target users, monetize 35
- 36. Ensuring Privacy, Security and Trust 36
- 37. Access from everywhere, taking the most of the network and capabilities of devices 37
- 41. FIWARE Instances • Future Internet Applications run on top of “FIWARE Instances” that are built by “FIWARE Instance Providers” upon: – selection of FIWARE GEis (products) from the FIWARE Catalogue. – assembly of selected FIWARE GEis with proprietary added-value products. FIWARE Catalogue FIWARE GE implementations FIWARE Instance 41 Future Internet App assemble… proprietary product
- 43. Domain-specific platforms = FIWARE + specific enablers FIWARE GEs SMART City Apps SMART Factory Apps SMART Agrifood Apps Domain specific enablers 43
- 44. Envisioned target Smart City platform IoT Broker & Config (from sensors to things) actuators Open Data 44 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
- 45. FIWARE Ops: paving the way for FIWARE providers Deployment Deployment of basic Cloud Hosting GEs and Monitoring Adapters in a FIWARE node Federation Management Federate a new FIWARE node within a given FIWARE instance (e.g., the FIWARE Lab) Connectivity Management Manage connectivity of services across FIWARE nodes of a FIWARE instance Service Offert Management Registration and deployment of additional Generic Enablers, Specific Enablers and complementary Future Internet Facilities 45
- 46. Thanks! Join us! www.lab.fiware.org
- 47. BACKUP SLIDES
- 48. Internet: a transformation engine Navigation, Calling a taxi (Uber), Recruiting (Linkedin)… 48
- 49. The FIWARE Program (formerly known as Future Internet PPP) • Goal: capture opportunities derived from the new wave of digitalization of life and businesses • Strategy: Build a ecosystem that will work as catalyst for capturing the opportunities. Lead standards for Smart Cities and APIs for IoT (Internet of Things) • Pillars: – FI-WARE : a generic, open standard platform which serve the needs of developers in multiple domains – FIWARE Lab : a meeting point where innovation takes place, an opportunities can be incubated – : a program that funds developers and entrepreneurs, and ignites roll-out of the ecosystem – FIWARE Ops : the suite of tools easing deployment and operation of FI-WARE instance nodes • Global footprint: open to regions sharing the ambition tourism eHealth Transport, Mobility and Logistics e-government Smart Energy Grid … 49
- 50. How can the new opportunities be captured and ultimately translated into local economy growth and creation of jobs? Entrepreneurs, Developers • Develop once for a large market • Easily meet potential customers • Marketing, promotion • Ability to test with real data and end users • Simple yet powerful APIs that accelerate product development App Sponsors and Data providers • Connect to entrepreneurs • Put their data at work • Bring new innovative services to end users • Be more efficient • Social Reputation Technology Providers • Ability to “coopete” • Connect to entrepreneurs: jointly exploit the opportunities 50
- 51. How can the new opportunities be captured and ultimately translated into local economy growth and creation of jobs? Entrepreneurs, Developers • Develop once for a large market • Easily meet potential customers • Marketing, promotion • Ability to test with real data and end users • Simple yet powerful APIs that accelerate product development App Sponsors and Data providers • Connect to entrepreneurs • Put their data at work • Bring new innovative services to end users • Be more efficient • Social Reputation ecosystem Technology Providers • Ability to “coopete” • Connect to entrepreneurs: jointly exploit the opportunities 51
- 52. How can the new opportunities be captured and ultimately translated into local economy growth and creation of jobs? Entrepreneurs, Developers • Develop once for a large market • Easily meet potential customers • Marketing, promotion • Ability to test with real data and end users • Simple yet powerful APIs that accelerate product development App Sponsors and Data providers • Connect to entrepreneurs • Put their data at work • Bring new innovative services to end users • Be more efficient • Social Reputation ecosystem open sustainable global Technology Providers • Ability to “coopete” • Connect to entrepreneurs: jointly exploit the opportunities 52
- 53. Building the FIWARE ecosystem: the vision creation of dedicated GE instances Use of Global shared GE instance FIWARE Catalogue FIWARE provider A Applications FIWARE provider B Applications 53
- 54. How the ecosystem is actually emerging: the case of Smart Cities • Some cities already connecting to FIWARE Lab: – Italy: Trento, Torino, Veneto – Spain: Valencia, Sevilla, Málaga, Santander, Logroño, Vigo, Lleida, Sabadell, … – Finland: Helsinki, Espoo – Netherlands: Amsterdam – Portugal: Lisbon – Discussion with cities in other countries ongoing • FIWARE Challenge on Smart Cities: – Launched end of October – 300+ teams (individuals, startups, SMEs – few researchers) applied to the challenge (ES, EN) – 20 final teams run the final in CPBR 14 – quite amazing results! 54
- 55. Why FIWARE Driver What is needed? What does FIWARE bring? Technology Open, driven by implementation, specs (open source reference implemenation) Sustainable investment over time Open specifications backed by open source reference implementations (see [1], [2]) 100+ M€ of investment (2011-2016) Experimental environment Ability to experiment with real data coming from cities (not just open historic datasets but real-time dat). Free Cloud capacity enabling entrepreneurs to test and host a permanent showcase of their applications. 15 cities (7 in Spain) already working on setting up a connection to FIWARE Lab [3] 3000+ cores, 16Tb RAM and 750+ Tb HD will be the free computing capacity provided by the FIWARE Lab Cloud across 16 nodes distributed in Europe Incentives for creating the ecosystem Engagement of technology providers, entrepreneurs, data providers, customers Funding for first entrepreneurs joining the ecosystem. Invesment in promotion and dissemination activities 52 partners, 13 countries (just FIWARE) 100 M€ devoted to fund entrepreneurs in 2014- 2016. Additional opportunities in Horizon 2020. 6,2+ M€ devoted to dissemination Global footprint Helping entrepreneurs and technology providers to create opportunities not just in Europe but other regions (Latam, Asia and, why not, USA) FIWARE Lab nodes in Mexico and Brazil. Conversations between EC and public authorities in Mexico and Brazil to explore collaboration opportunities [1] – http://wiki.fi-ware.org/Summary_of_FIWARE_Open_Specifications [2] – http://catalogue.fi-ware.org 55 [3] – http://lab.fi-ware.org
- 56. Extending the FIWARE Lab offering for service providers and developers • ff • Availability of 5 nodes (end of March 2014) with 500+ cores, 1TB+ Ram, 100TB+ HD • Additional 12 nodes (April / September 2014) up to 3000+ cores, 16TB+ Ram, 750TB+ HD • Level 1 and Level 2 support for the nodes • Showcases for developers, infrastructures, smart businesses 56
Editor's Notes
- #30: Rules – event Patterns