Date post: | 31-May-2015 |
Category: |
Documents |
Upload: | juanjo-hierro |
View: | 1,464 times |
Download: | 2 times |
http://www.fiware.orghttp://lab.fiware.orgFollow @FIWARE on Twitter
FIWARE: the pillar of the Future InternetJuanjo HierroTelefonica I+D. FIWARE Coordinator and Chief [email protected], @JuanjoHierro (twitter)
The FIWARE Public-Private Partnership (PPP)
Goal: capture opportunities derived from the new wave of digitalization of life and businesses that is coming
Strategy: Build an ecosystem that will work as catalyst for capturing the opportunities, engaging data providers and entrepreneurs
Pillars:• FI-WARE : a generic, open standard platform which
serve the needs of developers in multiple domains
• FIWARE Lab : a meeting point where innovation happens and data providers plus entrepreneurs can be engaged
• FIWARE Ops : the suite of tools easing deployment and operation of FI-WARE instance nodes
• : a program that funds developers and entrepreneurs, and ignites roll-out of the ecosystem
• FIWARE mundus : reach a global footprint, opening to regions that share the same vision and ambition
eHealth
tourism
Transport, Mobility
and Logistics
e-government
Smart Energy
Grid
…
2
3
What does FIWARE provide as a platform?
4
Being “Smart” requires first being “Aware”
Implementing a Smart Application requires gathering and managing context information
Context information refers to the values of attributes characterizing entities relevant to the application
Boiler• Manufacturer• Last revision• Product id• temperature
Users• Name-Surname• Birthday• Preferences• Location• ToDo list
Flowerpot• Humidity• Watering plan
Context Information
Application
5
Being “Smart” requires first being “Aware”
Implementing a Smart Application requires gathering and managing context information
Context information refers to the values of attributes characterizing entities relevant to the application
Bus• Location• No. passengers• Driver• Licence plate
Citizen• Name-Surname• Birthday• Preferences• Location• ToDo list
Shop• Location• Business name• Franchise• offerings
Context Information
Application
6
Different sources of context need to be handle
Context information may come from many sources:• Existing systems
• Users, through mobile apps
• Sensor networks (Internet of Things)
Source of info for a given entity.attribute may vary over time
Place = “X”, temperature = 30º
What’s the current temperature in place
“X”? Standard API
A sensor in a pedestrian street
The Public Bus Transport
Management systemA person from his
smartphone
It’s too hot!
Notify me the changes of temperature in place
“X”
7
A non-intrusive approach is required
Capable to integrate with existing or future systems dealing with management of municipal services without impact in their architectures
Info about attributes of one entity may come from different systems, which work either as Context Producers or Context Providers
Applications rely on a single model adapting to systems of each city
Application/Service
Standard API
System A System B
attribute “location” attribute “driver”
Context Producer Context Provider
8
Connecting to the Internet of Things
Capturing data from, or Acting upon, IoT devices should be as easy as to read/change the value of attributes linked to context entities
Context Broker
Standard APIStandard API
GET <Oauth token>/V1/contextEntities/flowerpot-1/attributes/humidity
PUT <Oauth token>/V1/contextEntities/flowerpot-1/attributes/status “watering”
Setting up the value of attribute “status” to “watering” triggers execution of a function in the IoT device that waters the plant
Issuing a get operation on the “humidity” attribute enables the application to find out whether the plant has to be watered
9
Connecting to the Internet of Things
Capturing data from, or Acting upon, IoT devices should be as easy as to read/change the value of attributes linked to context entities
Context Broker
Standard APIStandard API
GET <Oauth token>/V1/contextEntities/lamp1/attributes/presenceSensor
PUT <Oauth token>/V1/contextEntities/lamp1/attributes/status“light on”
Setting up the value of attribute “status” to “light on” triggers execution of a function in the IoT device that switches the lamp on
Issuing a get operation on the “presenceSensor” attribute enables the application to get info about presence of people near the lamp
10
Context Management in FIWARE
The FIWARE Context Broker GE implements the OMA NGSI-9/10 API: a simple yet powerful standard API for managing Context information complying with the requirements of a smart city
The FIWARE NGSI API is Restful: any web/backend programmer gets quickly used to it
Application/Service
Context Broker
NGSI API
Boiler• Manufacturer• Last revision• Product id• temperature
Users• Name-Surname• Birthday• Preferences• Location• ToDo list
Flowerpot• Humidity• Watering plan
11
FIWARE NGSI: Basic interaction
Context Producers publish context information by invoking the updateContext operation on a Context Broker.
Context Consumers can retrieve context information by invoking the queryContext operation on a Context Broker
Bus = “X”, location = (x, y)updateContext
Context Broker
Context Producer
Context Consumer
queryContext
FIWARE NGSI: Subscription to notifications
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
12
Bus = “X”, next_stop = “A”, arrived = “Yes”
updateContext (context_info)
Context Broker
Context Producer
Context Consumer(consumer1)
notifyContext (id, context_info)
Id = subscribeContext (consumer1, condition, duration)
FIWARE NGSI: Context Providers
Context Providers can be registered to the Context Broker as “holders” of certain context information.
A Context Broker will invoke the queryContext or updateContext operations exported by Context Providers whenever they are queried for, or asked to update, context information they hold
13
Bus = “X”, location = (x, y)queryContext / updateContext
Context Broker
Context Provider(provider-x)
Context Consumer
queryContext / updateContext
registerContext (provider-x, registration_data, duration, id))
14
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
queryContext (e1, attr1, attr2)
Context Provider
queryContext (e1, attr1)
Context Consumer
updateContext (e1, attr2)
Application
Context Broker
System B (e.g.
Transport system)
System A (e.g. GIS, POIs)
15
Integration with sensor networks
The FIWARE 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
FIWARE Context Broker
IoT Agent-1
IoT Agent-2
IoT Agent-n
IoT Agent
Manager
create/monitor
FIWARE Backend IoT
Device Management
OMA NGSI API (northbound interface)
(southbound interfaces)
MQTTETSI M2M
IETF CoAP
16
Open data publication
Once context information is gathered, a lot of useful complementary FIWARE enablers can be used
Context Broker
Advanced Web-based UI (AR, 3D)
Data/Apps visualization
Big Data AnalysisComplex Event Processing
Multimedia processing
17
Context Processing and Analysis
Applications
Complex Event Processing
(CEP)
Context Management Processing and Analysis
BigData Analysis (Hadoop- based)
Context Broker
Programming of rules
NGSI-9/10
NGSI
Context
Sources
Simple Processing (aggregation, averages,
…)Sensor2Things
NGSI IoT Agents
FIWARE IoT & Context/Management altogether
IoT Backend Device Management
Backend
Applications
FIWARE NGSI-9/10
Simple processing
CEP
IoT-enabled Context
Management
Backend
BigData Analysis
ContextBroker
Other sources
Gateway/Device
Platform GEs
Gateway/Device
Platform GEsGateway/
Device Platform GEs
Gateway/Device
Platform GEs
Native NGSI IoT
Agent
Native NGSI IoT
Agent
18
19
Data analytics
Context Broker
NGSI
Context
Sources
Analysis
Query/Reporting
Data mining
Extract
TransformLoad
20
Open Data publication
Context Broker
NGSI
Context
Sources
BigData Analysis
21
FIWARE = advanced OpenStack-based Cloud capabilities + library of APIs that ease development of applications
Sustainability ensured
Driven by implementati
on
22
FIWARE major differential features
• Federation of infrastructures (private/public regions)
• Automated GE deploymentCloud
• Complete Context Management Platform
• Integration of Data and Media Content
Data/Media Context Mgmt
• Easy plug&play of devices using multiple protocols
• Automated Measurements/Action Context updates
IoT Services Enablement
• Visualization of data (operation dashboards)
• Publication of data sets/services
Data/Services Delivery
• Easy incorporation of advanced 3D and AR features
• Visual representation of context information
Advanced Web UI
• Security Monitoring• Built-in Identity/Access/Privacy Management
Security
• Advanced networking (SDN) and middleware
• Interface to robotsI2ND
23
Why FIWARE?
24
Building a successful ecosystem requires …
Creating a vibrant community of active contributors who commit a sustainable investment over time
24 partners from 9 different countries
7430+ PMs devoted to development activities in 5 years (5165 PMs in the first 3 years)
122/76 M€ of budget/funding (37/23 M€ in the next 2 years)
Each FIWARE component is considered strategic in the portfolio of contributing partner
25
Building a successful ecosystem requires …
Bringing incentives for entrepreneurs and developers
80 M€ in grants to startups/SMEs in the next 2 years (FIWARE Acceleration Programme)
3100+ startups/SMEs applied to 1st Open Call of the FIWARE Acceleration programme
20 M€ to support involvement of16 accelerators across Europe
Selected startup/SMEs working as evangelists
Free FIWARE Lab environment for experimentation
1300 startups/SMEs to be funded (~400 as result of 1st Open Call)
26
Building a successful ecosystem requires …
engaging domain stakeholders
25+ relevant domain stakeholders involved in Use Cases and FIWARE Accelerator programme
16+ cities have published their open data on FIWARE Lab
New stakeholders triggered by awareness have approached us (e.g., Ferrovial, Bosch, …)
31 cities launched the Open and Agile Smart Cities innitative where they commit to adopt FIWARE APIs (NGSI, CKAN)
95/66 M€ of budget/funding devoted to Use Cases in verticals
27
Building a successful ecosystem requires …
Creating a meeting point where demand connects to offering and innovation takes place
FIWARE Lab environment with 3000+ Cores, 16+ TB RAM, 750+ TB HD
1900 open datasets from cities published and growing fast!
17 nodes across Europe
1st node in LATAM deployed in Mexico. New nodes being setup: Brazil and Chile
28
Building a successful ecosystem requires …
Raising awareness (which means an investment in marketing) and creating a brand
6,5 M€ in marketing activities (4 M€ so far)
Lead by reputed on-line marketing partner (Ogilvy)
450K€ just in sponsorship of events during 2015-16
29
Building a successful ecosystem requires …
Scale and go global
21 Innovation Hubs in Europe
First FIWARE Lab nodes in Mexico and Brazil
1,4 M€ funding assigned to FIWARE mundus activities targeted to build links with Mexico, Brazil, Chile, Japan, Canada, Korea, BRIC countries …
30
FIWARE PPP: main figures
24
9countries
partners
122 = 85 + 37 M€FIWARE budget (phases 1-2 + phase 3)
99 = 76 + 23 M€FIWARE funding (phases 1-2 + phase 3)
80 + 20 M€for startups/SMEs
1300Startups/SMEs
21Innovation Hubs
6,5 M€marketing
450 K€sponsorshipsnext 2 years
16+Cities
95/66 M€budget/funding of Vertical Use Cases
18 = 17 + 1FIWARE Lab nodes
31
What does FIWARE bring to Smart Cities?
32
Smart Cities can be engines of growth
Cities are where daily life and businesses actually happen …
Smart Cities are not simply about more efficient municipality services but transforming Cities into ICT platforms enabling development of smart applications
This way, cities would transform into engines of economy growth and improvement in the well-being of citizens
33
Why standards are relevant for Smart Cities
The current lack of standards means an impediment for the development of Smart Cities• The target market for solution and services is not large
enough to attract investment
• Solutions and services become tailor made, therefore expensive.
• Cities get locked-in to solution/application providers
Pillars of the FIWARE programme support the creation of a sustainable ecosystem:• The FIWARE platform brings the necessary standards
• The FIWARE Lab becomes the meeting point where cities meet entrepreneurs and innovation takes place
• The FIWARE Acceleration programme helps to attract a first wave of developers (startups/SMEs)
• The FIWARE mundus programme helps to expand globally
• The FIWARE Ops suite of tools ease the task to deploy FIWARE instances
Target Smart City platform
Smart city platform as a Data/Knowledge Hub
Non-intrusive, open to third parties
CKAN
Big Data
Context Broker
Accou
ntin
g &
Paym
en
t &
Billin
g
IDM
& A
uth
Short-term
historic data
BigData Processin
g
Data Quering/Acti
on, Publish/Subs
cr
Open Data publishing
Real-time processing
BIETL
RULESDEFINITION
TOOL
OPERATIONAL
DASHBOARDKPI GOVERNANCE OPEN DATA PORTALS
Service orchestrat
or
Context Adapters
CEP
34
IoT Backend Device
Managementmeasures / commands
IoT Broker & Config Management
(from sensors to things)
IoT/Sensor
Open Data
actuators
Media stream
s
Real Time Media Stream
Processing
City Services
GIS
Inventory
Specific Enablers
Generic Enablers
35
How can standard Smart City data models easing common solutions be defined? The problem
Smart City apps can be ported from one Smart City to another once their platforms provide the same set of APIs, that’s why FIWARE brings a rather high value
Without standard data models, Smart City apps would need to come with adapters that transform data made available by the city so that it complies with the data model handled by the app but that has proven to be easy with OMA NGSI (overall if NGSI is at both ends)
Creation of standard Smart City data models would allow to avoid performing this kind of adaptation and make portability of Smart City apps across Smart City platforms a pretty straightforward task
How creation of these standard Smart City data models can be fostered?
36
How can standard Smart City data models easing common solutions be defined? The solution
A “design by committee” approach would not be the best approach:• Such kind of approach has proven to be wrong in many
other standardization efforts in the past
• Who grants that the defined model is suitable for what apps need and developers want to have?
We need a “driven by implementation” approach:• Identify real applications that solve a real problem and cities
would like to see running in their cities
• Check what data models they have been designed to work with and take them as input
• Carry out a “data curation” process where input data models converge into a single common model
You will end with a set of standard data models and soon a portfolio of killer Smart City apps working!
37
How can standard Smart City data models easing common solutions be defined? FIWARE
The FIWARE Accelerator program enables to identify killer Smart City apps developed by entrepreneurs• These applications can serve as basis for definition of a
standard set of Smart City data models and drive curation process
• Involvement in this process becomes also an incentive for the entrepreneurs to join the program (“I want to influence the standard so that my app can easily align with it”, “I want to provide one of the first example applications”)
• There are 80 M€ for entrepreneurs that can be put at work!
Cities would play a key role:• Their data models will be contrasted/analyzed against those
coming from the apps and other cities
• They would get involved in the data curation process
Liason with other initiatives that may contribute
38
Open and Agile Smart Cities initiative
Launch of the Open and Agile Smart at CeBIT:• Denmark: Copenhagen, Aarhus and Aalborg
• Finland: Helsinki, Espoo, Vantaa, Oulu, Tampere, Turku
• Spain: Valencia, Santander, Málaga, Sevilla
• Portugal: Porto, Lisbon, Fundão, Palmela, Penela and Águeda
• Belgium: Brussels, Ghent and Antwerp
• Italy: Milan, Palermo and Lecce
• Brazil: Olinda (Recife), Anapólis (Goiás), Porto Alegre (Rio Grande do Sul), Vitória (Espírito Santo), Colinas de Tocantins (Tocantins) and Taquaritinga (São Paulo)
Other countries and cities welcome to join !
Some of them already in the pipeline
(*) Ordered by country and date of incorporation
39
Open & Agile Smart Cities initiative principles
API: Adoption of a lightweight, open-licene standard API to gather, publish, query and subscribe-to in-time context information describing the state of the city. Specifically, the FIWARE NGSI API will serve as a first common API which the supporters will implement.
Data model: Adoption of a simple initial standard data model required for effective interoperability when exchanging context information. Specifically, CitySDK, which is available through the FIWARE NGSI API, functions as a basis
Open Data Platform: Adoption of a flexible, easily-distributable open data publication platform which any organisation can set up at a low cost if it is not already being used. Specifically, CKAN will serve as the initial standard platform for publication of datasets or NGSI API resources. CKAN is already integrated and extended as part of the FIWARE Reference Architecture
40
Open & Agile Smart Cities initiative principles
Approach: Adoption of a “driven by implementation” approach towards experimental consolidation of initial standard data models as well as specification of new standard data models. The goal is that communities and developers can (1) co-create their services based on basic but commonly-defined data models, (2) influence the definition of new models by implementing and experimenting, and (3) help “curate” existing data models. Specifically, this will mean engaging organisations and communities, leveraging relevant initiatives, e.g. startups/SMEs selected through the FIWARE Accelerator Programme (projects focused on Smart Cities), the OrganiCity Experimentation-as-a-Service facility and open calls, Code for Europe and/or other relevant programmes, including national networks, that may help to engage wider communities of stakeholders and developers. It will also mean leveraging the FIWARE Lab, OrganiCity facility etc. as joint, major hubs for experimentation with the proposed APIs, data models and platforms
41
The way ahead
FIWARE = Open APIs for Smart Cities
CitySDK = FIWARE APIs + Standard Data Models for Smart Cities
Open & Agile Smart Cities = cities building City SDK by following a driven by implementation approach
The FIWARE Public-Private Partnership (PPP)
Goal: capture opportunities derived from the new wave of digitalization of life and businesses that is coming
Strategy: Build an ecosystem that will work as catalyst for capturing the opportunities, engaging data providers and entrepreneurs
Pillars:• FI-WARE : a generic, open standard platform which
serve the needs of developers in multiple domains
• FIWARE Lab : a meeting point where innovation happens and data providers plus entrepreneurs can be engaged
• FIWARE Ops : the suite of tools easing deployment and operation of FI-WARE instance nodes
• : a program that funds developers and entrepreneurs, and ignites roll-out of the ecosystem
• FIWARE mundus : reach a global footprint, opening to regions that share the same vision and ambition
eHealth
tourism
Transport, Mobility
and Logistics
e-government
Smart Energy
Grid
…
42
http://fiware.org
http://lab.fiware.org
Follow @Fiware on Twitter !
Thanks!
43