iot large-scale pilot for smart cities & communities · basic data marketplace enablers (d2.4)...

IoT Large-Scale Pilot forSmart Cities & Communities

Deliver a marketfor IoT-enabledurban services for Europe and beyond

2

Mission: To create a global smart city marketbased on the needs of cities and communities—Demand-side—Global network of national networks—117 cities24 countriesEurope, Latin America, Asia-Pacific—Council of Cities Coordinator: GhentBoD representative: Carouge (Geneva)

A robust model for standards-basedinnovation and procurement ofIoT-enabled services across domains

5

Why standards?Supply-side• Reusability, replicability, scalability Scale, agile development/deployment

Demand-side• Replaceability, portability, comparability Choice, efficiency, value-for-money, independence

Both• Interoperability Reduced risk, increased investments, innovation 6

Common Technical Ground1. OASC neutral branding (based on standards and consensus

specifications)2. OASC Minimal Interoperability Mechanisms (MIMs)

• Context Information Management• Common data models• Ecosystem Transaction Management (marketplaces)

3. SynchroniCity reference implementation (standards-based)4. SynchroniCity cloud hosting (option)

7

Project Objectives1. Establish technical foundations2. Establish marketplace enablers3. Create reference zones4. Pilot services that serve citizen needs5. Establish ecosystem6. Establish citizen-oriented methods7. Establish holistic quantification of value8. Provide insights into new busines models9. Transform city policy-making and planning 10

Fo

un

dat

ion

s2

01

7

Workplan

Staged, ambitious (36 mo)Including open call for SMEs

Init

ial

Ap

ps

Op

en c

all

20

18

New

Ap

ps

20

19

Tra

nsi

tio

n

1111

SynchroniCity Architecture Model• IoT Management: to interact with the devices that use different standards or

protocols making them compatible and available to the SynchroniCity platform.

• Context Information Management: to manage the context information comingfrom IoT devices and other public and private data sources.

• Data Storage Management: to provide functionalities related to the data storageand data quality interacting with heterogeneous sources.

• Marketplace: to implement a hub to enable digital data exchange for urban dataand IoT capabilities providing features in order to manage asset catalogues,orders, revenue management.

• Security: to provide crucial security properties such as confidentiality,authentication, authorization, integrity, non-repudiation, access control, etc.

• Monitoring and Platform management: to provide functionalities to manageplatform configuration and to monitor activities of the platform services.

Baseline: SynchroniCity Cities/Reference Zones, OASC, FIWARE, EIP-SCC, NIST IES-CF.

Related standards: ITU-T SG20*/FG-DPM* (*drafts), ISO TC268.

Spec. doc.: Reference Architecture for IoT Enabled Smart Cities (D2.10)http://synchronicity-iot/docs

14

Interoperability Points• Interoperability Points represent the main

interfaces that allow a city (or any Reference Zone, RZ) and applications to interact with SynchroniCity platform

• Interoperability points are independent from the specific software components that realize them and can be implemented by cities in different steps to reach different levels of compliance

• The architecture has been designed following the OASC principles and the definitions of Minimal Interoperability Mechanisms (MIMs). MIMs, are the actual specifications of the interfaces at the Interoperability Points: they are standard API and guidelines that have to be implemented by a city in order to be compliant with the SynchroniCity framework15

Interoperability MechanismsInteroperability

PointDescription Specification document

(synchronicity-iot.eu/docs)Related Standards

[and Baselines]

Context Information Management API

This API allow to access to real-time context information from the different cities.

Reference Architecture for IoT EnabledSmart Cities (D2.10)

ETSI NGSI-LD prelim API, OMA NGSI, ITU-T SG20*/FG-DPM*

Shared data models

Guidelines and catalogue of common data models in different verticals to enable interoperability for applications and systems among different cities

Guidelines for the definition of OASC Shared Data Models (D2.2)

Catalogue of OASC Shared Data Models for Smart City domains (D2.3)

[FIWARE, GSMA, schema.org, Saref , SynchroniCity RZ + partner data models]

Ecosystem Transaction Management(“Marketplace”)

It exposes functionalities such as catalogue management, ordering management, revenue management, SLA, license management etc.Complemented by marketplaces for hardware and services.

Basic Data Marketplace Enablers(D2.4)

Guidelines for the integration of IoT devices in OASC compliantplatforms (D2.6)

[TM Forum API]

Security APIAPI to register and authenticate user and applications in order to access to the SynchroniCity-enabled services.

Reference Architecture for IoT EnabledSmart Cities (D2.10)

OAuth2

Data Storage APIThis API allows to access to historical data and open data of the reference zones.

Reference Architecture for IoT EnabledSmart Cities (D2.10)

ETSI NGSI-LD,DCAT-AP [CKAN]

Getting citiesready

How cities use the SynchroniCity Framework for standards-based

innovation and procurement

1. Identify assets

• First, a city needs to identify the assets that can and should be integrated with the SynchroniCity framework. These can include, e.g., data, (atomic) services and IoT devices

2. Implement access API

• Second, the access API can be implemented progressively, in different steps, depending on the technical infrastructure of the city. Security and Context Information Management API are the basic ones.

3. Align data models

• Third, OASC curates a set of standard data models for different sectors/application domains, and supports a city in the adaptation of their own data models to the SynchroniCity ones with guidelines and dedicated tools

4. Set yourterms

• Finally, SynchroniCity offers a fundamental asset access and management framework, partly to ensure proper handling of ownership, terms and licenses, which is an essential element, partly because SynchroniCity has the aim to foster a market for IoT-Enabled urban services, including data and products. Towards these two objectives, SynchroniCity provides marketplaces in which digital assets can be offered to public and private stakeholders, with or without monetisation. 18

SynchroniCity Ecosystem Transaction Management

IoT Edge

Smart City Services

IoT Data MarketplaceOpen data trading platform

- to deliver a Digital Single Market for IoT-enabled smart cities in Europe and beyond.

- to open innovation ecosystem around the proposed digital single smart city marketplace.

IoT Data Providing a natural incentive to share data through monetization,Data management with common APIs,FIWARE + TMForum Business APIs

IoT Product MarketplaceMulti-service e-commerce platform

IoT Devices& Solutions Helping SMSes in IoT market,

Connecting stakeholders together,User-created market ensuring sustainability,E-commerce platform

• IoT infrastructure owners• IoT manufactures and vendors• IoT service providers

• Enlarge IoT Business ecosystem• Foster new markets and innovation

• Vendors create their own pages and upload their products.• Reference City use cases with IoT products to be used.

SynchroniCity IoT Product Marketplace

• Initial version was presented in IoT Week 2018 Bilbao, receiving interests from participants.• Multi-user account management: special features for vendors and city authorities.

To Do:• Refinement with ToC, Privacy policy, etc.• We need more products! Best way could be to open

to vendors for adding their own products providing OASC compliance requirements

Value proposition (1)Demand-side: • Choice, flexibility, efficiency, value-for-money,

independence, economic development Supply-side: • Scale, agile development/deploymentAll: • Reduced risk, increased investments, innovation

27

Value proposition (2)• A path from R&I to implementation (+ link

AI, 5G, edge)• Standards-based innovation and

procurement across domains• A common technical ground based on

minimal interoperability and city needs• Emerging standards• Market validation• Privacy, trust, security, GDPR compliance

28

Approach comparison• Minimal vs. complete• Architecture framework model vs. reference

architecture• Market enablers vs. challenge-driven

(context is king)• Validated by implementation vs. by

committee• Global vs. national/regional• Transparent inspection vs. black box 30