OPEN AND AGILE SMART CITIESA technical introductionSergio Garcia GomezTelefonica I+D. FIWARE Data/Context Chapter and Smart Cities Architect

Open Data/Content approaches

2

Datasets

Existing Datasets (census,

geographical, tourism,...)

Historic Data (from sensors,

events...)

Real Time

Vertical Systems (mobility, events...)

Internet of Things (sensors, Smart

meters...)

Media

Video streams (traffic,

surveillance..)

Audio (microphones),

speaches...

ApplicationsNGSICKAN WEBRTC

OASC PRINCIPLESDriven by

Implementation (procurement, projects, labs, accelerators)

Common APIs

(NGSI)

Data Models(CitySD

K)

Open Data

Platform(CKAN)

OASC PRINCIPLESDriven by

Implementation (procurement, projects, labs, accelerators)

Common APIs

(NGSI)

Data Models(CitySD

K)

Open Data

Platform(CKAN)

Being “Smart” requires first being “Aware”

Implementing a Smart City requires gathering and managing context information describing the current and historic “state” of the city

Context information refers to the values of attributes characterizing entities relevant to city services, governance and third-party apps

Bus• Location• No. passengers• Driver• License plate

Citizen• Name-Surname• Birthday• Preferences• Location• ToDo list

Shop• Location• Business name• Franchise• offerings

Context Information

City Governance SystemCity Services Third-party Apps

NGSI: Context from different sources FIWARE: Restful binding of OMA NGSI 9 and NGSI 10 Context information may come from many sources:

Existing systems, Users, through mobile apps, Sensor networks Source of info related to a given entity 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”

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

FIWARE Context Broker

IoT Agent-1

IoT Agent-2

IoT Agent-n

IoT Agent Manager

create/monitor

FIWARE Backend IoTDevice Management

NGSI API (northbound interface)

(southbound interfaces)MQTTETSI M2M IETF CoAP

OASC PRINCIPLESDriven by

Implementation (procurement, projects, labs, accelerators)

Common APIs

(NGSI)

Data Models(CitySD

K)

Open Data

Platform(CKAN)

Open Data Platform

De facto standard platform for open data in Europe and beyond.

Search & Discover Data: Search by keywords Browse by facets Explore data with previews & visualization REST/JSON APIs to access data and metadata Data Management for publishers Easy store & update of metadata and data Plenty of extensions: harvesting, geographical information, data visualization….

9

Entering data (web,

files, CKAN API)Harvest data from external repositories (geospatial servers, HTML, CKANs...)

Manage the publicationprocess: visibility, organizations, workflows...

Publishing and Managing Data

10

Search and discovery

11

Search and querythrough an APISearch by text,

facets (tags, format,...) in the portal

Metadata

12

A CKAN portal provides a rich set of metadata for each dataset

Title, group,owner, dates, license...

NGSI resource visualization

NGSI resources visualization

OASC PRINCIPLESDriven by

Implementation (procurement, projects, labs, accelerators)

Common APIs

(NGSI)

Data Models(CitySD

K)

Open Data

Platform(CKAN)

From Metamodel to data model

NGSI Metamodel

NGSI data example

Entity• Entity Id• Entity Type

Attribute• Attribute

Name• Attribyte

Type• Attribute

Value

Metadata• Metadata

Name• Metadata

Type• Metadata

Value

1 n 1 n

Entity• urn:santander:

123• MeteoSensor

Attribute• temperature• float• 23.5

Metadata• Accuracy• float• 0.01

OASC Participation modelEntity• entityId• entityType:

serviceRequest

Attribute• status• string

Metadata• location• string• WSG84

Attribute• serviceCod

e• stringAttribute• position• coords

…

= CitySDK Participation + NGSI model

Some examples

OASC PRINCIPLESDriven by

Implementation (procurement, projects, labs, accelerators)

Common APIs

(NGSI)

Data Models(CitySD

K)

Open Data

Platform(CKAN)

Showcasing OASCo Cities involvement and commitment to unleash real time data.• Pilots, procurement, R&D actionsoStart-ups and development partners to

develop solutions in various verticals and distil the data models to be shared.

Porto Citibrain

Helsinki Open311 (issue reporting)Description: The main objective of the pilot was to prepare a working prototype software to a) integrate Helsinki Open311 issue reporting API to FIWARE platform and store Helsinki issue reports (based on Open311 standard) to NGSI c) display Helsinki issue reporting API data on Wirecloud environment. Partners: Forum Virium

Next technical steps at OASCo Tools to define NGSI-based data models and and models repositoryo Definition of data models. CitySDK first.

o DCAT AP to support harvesting / interoperability among open data portals. CKAN as reference implementation

o Management of access control to data resourceso Federation / harvesting of data portalso Publication of open data resources

o Technical guidelines

o Rolling plan for Standardization

Thanks!Sergio Garcia GomezTelefonica I+D. FIWARE Data/Context Chapter and Smart Cities Architect