Description of a Smart City Platform, what is the offering of FIWARE in terms of the Smart City Platform with general concepts about the standards used and a complete architecture of services. The relationship of Smart Cities and Cloud for deployment of solutions, with the specific case of the FIWARE Lab. This is our OpenStack environment free for use for the FIWARE Ecosystem to deploy Infrastructure as a Service (IaaS) to test the "Powered by FIWARE" solutions.

1. Building the Smart City Platform on
FIWARE Lab
Fernando López
FIWARE Cloud & Platform Senior Expert
fernando.lopez@fiware.org
@flopezaguilar
https://www.slideshare.net/flopezaguilar
https://github.com/flopezag

2. About me
▪ More than 35 years of programming experience (more than 12 programming languages)
▪ More than 10 years working with OpenStack and AWS
▪ Web Development, Message Queues, Functional Programming, Big Data and Data
Engineering
▪ Developer, Team Leader, QA Manager, Project & Product Manager
▪ DevOps(Secs) activities with more than 6 years
▪ Now Cloud and IoT Platform Senior Expert in FF
▪ Principal Cloud Architect in FIWARE Lab
▪ Evangelist of FIWARE Technology and TSC Member of FIWARE Technology
▪ Love Coding, CI & CD and AI/ML
2

3. What is a Smart City
A set of Policies & Strategies that leverage Data & Technologies from different sources
to Deliver New Businesses that:
3
CITIES
CITIZENS
BUSINESS
Drive efficiency, sustainability & improved
decision making
Create an ecosystem of transparent,
competitive and efficient environment
Improve the inclusiveness and quality of
life and develop of new citizens services
1
2
3

4. Smart Cities: where we are
Yes!
You may be already an
Efficient and Open City ….
… but there is still a
journey you have to
travel to be where
you HAVE TO BE
4
• Vertical solutions (some
being IoT-enabled) bringing
efficiency but in silos
• Historic and static data
published as open data
Efficient & Open

5. FIWARE: Supporting cities in their transformation journey
1 2 3 4
0
Enabling the
Data Economy
• City as a platform including
also 3rd party data enabling
innovative business models
• Open and commercial data
enabling multi-side markets
Supporting
Open Innovation
• Right-time context info
published as open data to
third parties
• Authorization and access
control (API management)
• Common Info Models
• Full interoperability between
cities and within the city
• Enabling portability of
solutions across cities
Collaborating towards
a sustainable market
• Breaking information silos
through shared context data
space with standard API
• Enabling Overall City-level
Governance Solutions
Exploiting Data
across verticals
CRMSocial
network
s
Waste
Mgmt.
Smart
Parking
Air
Quality
Context Management Layer
City-level governance system

6. Exploiting data across verticals
 Need to build an holistic data representation and the
history of the city (context) for breaking the silos:
• Vertical smart solutions
• Information systems
• IoT infrastructures
 A data-driven ”system of systems” architecture:
• Interoperability of systems within the city
• City-level smart decision support systems on top
 Key properties:
• Replaceability (systems can be replaced)
• Extensibility (new systems can be added easily)
• Loose coupling (systems can evolve independently)
• Low intrusiveness (systems do not need to change)
6
CRMSocial
networks
Waste
Mgmt.
Smart
Parking
Air
Quality
Context Management Layer
City-level governance system

7. Implementing Smart Solutions requires gathering and
managing context information at large scale
# Smart Cities
Bus
• Location
• No. passengers
• Driver
• License plate
Citizen
• Birthday
• Preferences
• Location
• TODO list
Shop
• Location
• Business name
• Franchise
• offerings
Incident / claim
• Date
• Location
• Type
• Issuer
• Description

8. FIWARE: Driving the standard for Context Information Management
 The FIWARE Context Broker technology implements the FIWARE NGSI API: a simple yet
powerful public, royalty-free standard API for Context Information Management.
 Simple: A RESTful API using JSON which any web programmer learns how to use in one day.
 Yet powerful: FIWARE NGSI supports geo-queries, notifications, soon Linked Data (JSON-LD).
Application/Service
Bus
• Location
• No. passengers
• Driver
• Licence plate
Citizen
• Name-Surname
• Birthday
• Preferences
• Location
• ToDo list
Shop
• Location
• Business name
• Franchise
• offerings
Context Broker
FIWARE NGSI API

9. FIWARE: Driving relevant standards at every step
9
1 2 3 4
0
Enabling the
Data Economy
• City as a platform including
also 3rd party data enabling
innovative business models
• Open and commercial data
enabling multi-side markets
Supporting
Open Innovation
• Right-time context info
published as open data to
third parties
• Authorization and access
control (API management)
• Common Info Models
• Full interoperability between
cities and within the city
• Enabling portability of
solutions across cities
Collaborating towards
a sustainable market
• Breaking information silos
through shared context data
space with standard API
• Enabling Overall City-level
Governance Solutions
Exploiting Data
across verticals
ETSI NGSI-LD Open API for context
information management (based on
FIWARE NGSIv2 API).
FIWARE provides an Open Source
reference implementation of this
standard.
The FIWARE Context Broker
Technology is a CEF Building Block.
Recommended to Public Administrations
across member states of the EU.

10. FIWARE: Driving relevant standards at every step
10
1 2 3 4
0
Enabling the
Data Economy
• City as a platform including
also 3rd party data enabling
innovative business models
• Open and commercial data
enabling multi-side markets
Supporting
Open Innovation
• Right-time context info
published as open data to
third parties
• Authorization and access
control (API management)
• Common Info Models
• Full interoperability between
cities and within the city
• Enabling portability of
solutions across cities
Collaborating towards
a sustainable market
• Breaking information silos
through shared context data
space with standard API
• Enabling Overall City-level
Governance Solutions
Exploiting Data
across verticals
TMForum + FIWARE Foundation support cities
through the definition of a common Reference
Architecture and smart data models.
Leverages on initial FIWARE Data Models
widely used by cities already using FIWARE.
New Data Models will be defined involving cities
following a driven-by-implementation approach.

11. “Powered by FIWARE” Smart City: Reference Architecture (take 1)
KeyrockIdM&WilmaAccessControl
APIManagement
IoT platformsKurento RT
media stream
processing
IDAS NGSI Agent Framework
System
Adapter …IoT
Agent
FIWARE Context Broker
Bus
• location
• route
• next stop
• time next stop
Street
• location
• traffic
• pollution
Parking space
• location
• no. slots
Shared car
• location
• status
Citizen claim
• location
• citizen id
• description
Waste Bin
• location
• capacity
Other information sources
…Social
netwoks
CRM
Deployed IoT networks,
machines, cameras, robots
High-level
Context
Updates
Processing Engines
(Flink, Spark, Tensorflow, Hadoop, …)
Smart City Governance System
Operation
Dashboards
Advanced
Data Maps
AI
Algorithms
Big Data
Algorithms
Complex Event
Processing
Cygnus / Draco / Cosmos / STH
Comet / QuantumLeap
History Data
Stream
Vertical solutions
Waste
Mgmt..
Smart
Parking
Air
Quality …Traffic
control
GIS
Wirecloud
Mashup
Apache
Superset
System
Adapter
System
Adapter
System
Adapter

12. FIWARE: Driving relevant standards at every step
1 2 3 4
0
Enabling the
Data Economy
• City as a platform including
also 3rd party data enabling
innovative business models
• Open and commercial data
enabling multi-side markets
Supporting
Open Innovation
• Right-time context info
published as open data to
third parties
• Authorization and access
control (API management)
• Common Info Models
• Full interoperability between
cities and within the city
• Enabling portability of
solutions across cities
Collaborating towards
a sustainable market
• Breaking information silos
through shared context data
space with standard API
• Enabling Overall City-level
Governance Solutions
Exploiting Data
across verticals
• Breaking information silos
through shared context data
space with standard API
• Enabling Overall City-level
Governance Solutions
Exploiting Data
across verticals
• Common Info Models
• Full interoperability between
cities and within the city
• Enabling portability of
solutions across cities
Collaborating towards
a sustainable market
FIWARE DCAT-AP extension for right-time
datasets
CKAN Extensions for other platforms
(OpenDataSoft, Socrata, …): right-time datasets,
end-user dashboards, developer feedback, …
Authorization and Access Control using open
standards OAuth2 and XACML 3.0.

13. Enabling the Data Economy
13
 The City is not able to capture all data
describing what is going on (context)
• Banks
• Retailers
• Telecom Operators
• …
 How to bring the incentives for potential
context data providers?
 The City may become an enabler of the Data
Economy
• Ability to monetize provided data
• Support to multi-side markets
• Warrantying sovereignty of data
Smart
Facto
ry
Smart
Bank
Smart
Retail
Smart
Home
Smart
City
standard Context Information Management layer
Smart
Services

14. FIWARE: Driving relevant standards at every step
1 2 3 4
0
Enabling the
Data Economy
• City as a platform including
also 3rd party data enabling
innovative business models
• Open and commercial data
enabling multi-side markets
Supporting
Open Innovation
• Right-time context info
published as open data to
third parties
• Authorization and access
control (API management)
• Common Info Models
• Full interoperability between
cities and within the city
• Enabling portability of
solutions across cities
Collaborating towards
a sustainable market
• Breaking information silos
through shared context data
space with standard API
• Enabling Overall City-level
Governance Solutions
Exploiting Data
across verticals
• Breaking information silos
through shared context data
space with standard API
• Enabling Overall City-level
Governance Solutions
Exploiting Data
across verticals
• Common Info Models
• Full interoperability between
cities and within the city
• Enabling portability of
solutions across cities
Collaborating towards
a sustainable market
FIWARE provides the Data Economy Framework
open source based on TMForum (open source
reference implementation of marketplace
functions).
Enables the Data Economy through the datasets
monetization and the evolution of open data
publication platforms into data marketplaces.
Collaboration with IOTA to support trustworthy
accountability and management of contracts.
Data Economy
Framework

15. “Powered by FIWARE” Smart City: Reference Architecture (take 1)
KeyrockIdM&WilmaAccessControl
APIManagement
IoT platformsKurento RT
media stream
processing
IDAS NGSI Agent Framework
System
Adapter …IoT
Agent
FIWARE Context Broker
Bus
• location
• route
• next stop
• time next stop
Street
• location
• traffic
• pollution
Parking space
• location
• no. slots
Shared car
• location
• status
Citizen claim
• location
• citizen id
• description
Waste Bin
• location
• capacity
Other information sources
…Social
netwoks
CRM
Deployed IoT networks,
machines, cameras, robots
High-level
Context
Updates
Processing Engines
(Flink, Spark, Tensorflow, Hadoop, …)
Smart City Governance System
Operation
Dashboards
Advanced
Data Maps
AI
Algorithms
Big Data
Algorithms
Complex Event
Processing
Cygnus / Draco / Cosmos / STH
Comet / QuantumLeap
History Data
Stream
Vertical solutions
Waste
Mgmt..
Smart
Parking
Air
Quality …Traffic
control
GIS
Wirecloud
Mashup
Apache
Superset
System
Adapter
System
Adapter
System
Adapter
Extended Data Publication Platform
(e.g., CKAN)
Open Data Portal
(supporting
right-time datasets)

16. Driving de-facto standards: Smart Cities
16
Involving 130+ cities in 25+
countries.
All of them agree to foster
adoption of common
principles:
• Common API: NGSI-LD
• Compatible Open Data
Publication platforms
• Collaboration in definition
of data models
TM Forum supports FIWARE
NGSIv2 for real-time access to
context information in cities
TM Forum and FIWARE collaborate
towards development of data
marketplace platform components
TM Forum and FIWARE launched
the Front-runner Smart Cities
initiative towards definition of
common information models in
collaboration with cities
Identified as one of the most
relevant Smart Cities
Platform initiatives with a
global footprint within the
IES-City (IoT-Enabled Smart
City) Framework

17. 17
Why Cloud + Smart Cities

18. 18
IoT = ICT + OT
f(Cloud, ICT) = ICT(enhances)
Revolutionary Impact = ICT + OT + AI

19. 19
Cloud provides flexibility and agility to leverage
Data & Technologies in a very efficient way

20. 20
Smart City solution should be deployed on different
Cloud providers

21. Why OpenStack?
 FIWARE Foundation, through FIWARE Community, provide Cloud Native
Infrastructure using OpenStack for testing “Powered by FIWARE” solutions.
 It is open and free for use following the Terms & Conditions of the FIWARE Lab.
 Facilitate the DevOps operation in the early stages of developing new Business
solutions.
 OpenStack is Open Source.
21

22. Working with FIWARE Lab…
https://cloud.lab.fiware.org
22

23. Quick glance to components
23

24. Login: https://cloud.lab.fiware.org
24

25. Overview
25

26. The first virtual machine: requirements
26

27. Create a Security Group
 A Security Group should be
created using a name and a
description.
 Clicking in button “create security
group” inside the menu option
“Access & Security”.
27

28. Manage rules
28
 Clicking on “Manage Rules” we add new rules to a Security Group.
• Rules define what ports and protocols are opened for any VM on which we apply our Security Group.
• Important: If there is no rule defined, there is no connectivity (no networking)
 Please, pay attention to security!!!:
• Unnecessary Ports or IP sources should not be opened to access our applications.

29. Manage rules (II)
29
 Typical examples of opened ports:
• Port 22 → SSH
• Port 80, 443 → HTTP, HTTPS
• Port 1026 → Orion Context Broker
• Port 5050 → Cygnus
 Egress – Outgoing traffic
 Ingress – Incoming traffic
 Can be updated afterward

30. Key pairs
30

31. Key pair (II)
31
 The Keypair requires a name.
 The private part of the Keypair will be downloaded as a .pem file.
 The private Key is not stored in the cloud.
 We cannot access the VMs without this file.

32. Allocate a floating IP to the project
32
 A Floating IP is needed in the project so we can access our VMs from the Internet
Access & Security → Floating IPs → Allocate IP to Project
 The Floating IP association will be done later, once we have our VMs created.

33. Allocate a floating IP to the project (II)
33

34. Launch our first virtual machine (OrionLD CB) from
Images
34

35. Launch our first virtual machine (OrionLD CB) from
images
35
 Launch Instance: Details
 Instance Name (mandatory)
 Flavor value (mandatory)
• Tiny – Is too small flavor
• Small – It is too small flavor too.
• Medium – Will be Ok to run the OrionLD CB
• Large – Will be a powerful Flavor.
 DO NOT press Launch yet…!!! Go to
Networking

36. Launch our first virtual machine (OrionLD CB) from images
(networks)
36
 Launch Instance: Networks
 Choose here the network named:
• node-int-net-01 (FIWARE Convention)
 DO NOT press Launch yet …!!! Go to
Security Groups

37. Launch our first virtual machine (Orion CB) from images
(access & security)
37
 Launch Instance: Access & Security
 Choose the security group previously
created
 Choose the key pair previously created
 DO Press Launch…

38. The instance…
38

39. Associate floating IP to a virtual machine
39

40. Thank you!
www.fiware.org
Follow @FIWARE on Twitter
Fernando López
FIWARE Cloud & Platform Senior Expert
fernando.lopez@fiware.org
@flopezaguilar
https://www.slideshare.net/flopezaguilar
https://github.com/flopezag