Conceptual outcomes of the CPaaS.io Project as presented at the final review meeting in February 2019.

1. City Platform as a Service – Integrated and Open
Conceptual Outcomes
Antonio Skarmeta, Juan A. Martinez (OdinS)
Final Project Review, Web Conference
February 21st, 2019

2. Overview
1. Functional Architecture
2. Federation Mechanism
3. Personal Data Store
4. Data Quality Ontology
February 2019 © CPaaS.io Project Consortium 2

3. FUNCTIONAL ARCHITECTURE
Outcome #1
February 2019 © CPaaS.io Project Consortium 3

4. Architecture layers
February 2019 © CPaaS.io Project Consortium 4

5. Functional Architecture
Horizontal Layers
• IoT Data & Ingestion Layer: Context information acquired by our platform. It follows the NGSI
interface.
• IoT Broker and IDAS module incorporate the information to our platform.
• Virtual Entity Layer: Generation of aggregated information for required virtual information used by
services, and application.
• Thanks to NGSI and Context Broker
• Semantic Data & Integration Layer: Richer information representation and relations among the
stored information
• Knowledge Layer: Machine Learning (ML) component.
• Contains the aggregated and processed information useful for Smart City upper-layer services and
applications.
Traversal Layers
• Platform Management Federation and Operation Pillar: Make easier a deployment of the platform.
• FogFlow, which allows for a dynamic deployment in both edge and cloud layers.
• Security & Privacy Pilar: Enablers that guarantee a secure & private exchange of information.
February 2019 © CPaaS.io Project Consortium 5

6. Final u2-based (left) and FIWARE-based (right)
Instantiation views
February 2019 © CPaaS.io Project Consortium 6

7. Platform Integration
Achievements – last 6 months
• D3.7 released
• Updated functional architecture
• Updated Instantiation views (FIWARE & u2-based)
• Update and alignment of Deployment and Operation views (+ new
SmartParking scenario)
• New components (PDS, front-end to PDS (as part of android app))
• Volere template completed with final cross-check
• 79 Functional and non-functional requirements
• Fully covered 52, partially covered 14, dropped 13
February 2019 © CPaaS.io Project Consortium 7

8. Platform Integration
Project Achievements
• EU-side:
▪ Security components integration
▪ FogFlow integration
▪ Complete flow from sensors to analytical/historical data, plus semantic
knowledge
▪ Platform federation
• Japanese-side:
▪ Revising Semantic Integration Layer and OPaaS.io Component
▪ Extending area of supported IoT/Smart Cities applications
▪ ucR-Light for EU-Japan platform integration
February 2019 © CPaaS.io Project Consortium 8

9. Summary
• CPaaS.io followed the IoT ARM methodology
• Requirement collection and analysis phase leading to initial logical architecture
• Elaboration of a Functional view paving the way to two concrete instantiations of
the platform (and of the logical FCs) using different technologies: u2 for Japan,
FIWARE for Europe
• Elaboration of strategies for e.g. interoperability and federation
• Detailed description of both Instantiation Views
• Detailed description of Deployment and Operation views for each scenario
(architecture, UML use-cases)
• Incremental work on Volere template with final cross-check (actual coverage of
reqs)
• Incremental implementation of European platform using Agile
methodology with weakly update and monthly reviews
February 2019 © CPaaS.io Project Consortium 9

10. Platform Integration
February 2019 © CPaaS.io Project Consortium 10

11. Platform Integration
u2-based: main achievements
1. Revising Semantic Integration Layer Components and OPaaS.io Component
• Semantic Integration Layer
• IoT Devices are accessed using ucode resolution function and ucR-based contents management APIs
• OPaaS.io Component
• Open ID Connect based REST APIs (➔ WP5)
2. Extending area of supported IoT/Smart Cities applications
• New applications
• IoT Fishing Industry, Forestry, Data-driven agriculture, New Emergency Medical Services, etc.
• Multi-hop LoRa nodes is added to IoT Sercvices Layer
• for Finshing industry, forestry, and aggriculture
• Light-weight simple API is used
• ucR-Light as follows
3. ucR-Light for EU-Japan platform integration
• IoT Device Integration: ucR + RESTful –based new simpler and lighter protocols for platform integration
• Authorization Integration: Integration based on Open ID Connect protocol which both architrectures are
supporting (➔ WP5)
February 2019 © CPaaS.io Project Consortium 11

12. Revised Functions of Semantic Integration
Layer Components
Identification Resolution Functions
▪ Resolve ucode: Acquiring information about a certain ucode;
▪ Define ucode-associated information: Defining relationship between a certain ucode and information
▪ Update ucode-associated information: Updating information about a certain ucode;
▪ Delete ucode-associated information: Deleting information about a certain ucode;
Contents Management Functions
▪ Search data: searching ucR triple data from a certain ucode
▪ Resister data: registering ucR triple data associate with a certain ucode
▪ Get data from ucode: getting ucR triple data from a certain ucode
▪ Get data from property parameters: getting ucR triple data by property-based query
▪ Update data from ucode: updating ucR triple data from a certain ucode
▪ Update data from property parameters: updating ucR triple data by property-based query
▪ Delete data: deleting ucR triple data from a certain ucode
▪ Delete data property: deleting ucR triple data by property-based query
February 2019 © CPaaS.io Project Consortium 12

13. Extending area of supported IoT/Smart Cities
applications
February 2019 © CPaaS.io Project Consortium 13
“See See”: Sea state monitoring system
for fishery industry
“Ring Ring”: Safety Monitoring System
for Forestry Workers

14. Platform Integration
u2-based: Instantiation View
February 2019 © CPaaS.io Project Consortium 14
Light-
Weight
Device
Manager

15. Platform Integration
February 2019 © CPaaS.io Project Consortium 15

16. Platform Integration
FIWARE-based: main achievements
February 2019 © CPaaS.io Project Consortium 16
• FogFlow integrated, deployed and presented in three use
cases
• Security layer integration to IoT Broker
• NGSI to RDF Mapper
▪ Adapter from NGSI to Semantic Data repository
• Personal Data Storage integration between EU-JP
• Full data flow working from sensor level to historical and
semantical level

17. System Architecture
FIWARE-based: Instantiation view
February 2019 © CPaaS.io Project Consortium 17
• Mapping of concrete Functional
Components onto an Instantiation
View
• Components and relationships from
FIWARE IoT Services and
new/additional modules
• Security layer integration represented
in the Security & Privacy pillar
• New/enhanced components
▪ LoRaWAN to NGSI bridge
▪ NGSI to RDF mapper
▪ FIWARE STH Comet
o Open-source contribution
(metadata support)

18. FEDERATION MECHANISM
Outcome #2
February 2019 © CPaaS.io Project Consortium 18

19. MyEvents - Sapporo Snow Festival 2018
Deployment
February 2019 © CPaaS.io Project Consortium 19
8 MS Band
25 GB of Data
collected
12 Zephyr
12 Smart
phones
3 GoPros

20. MyEvents -Activities at Sapporo Snow Festival
February 2019 © CPaaS.io Project Consortium 20
Tube Rider
Football
Snow Mini
Golf
Snow
Rafting
Snow Ball
Throwing

21. My Events – CPaaS.io Integration
February 2019 © CPaaS.io Project Consortium 21
IoT Resource Layer
IoT Data &Ingestion Layer
Virtual Entity Layer
Semantic Data &Integration Layer
Knowledge Layer
SMART CITY Services Layer
Security &
Privacy Pillar
Platform
Management ,
Federation and
Operation
Pillar
FogFlow
KeyRock
NGSI to RDF
mapper
XACML
Capability
Manager
Deployment
Tool
LoRaWAN to NGSI
bridge
Existing components
New/enhanced
components
IoT Agent
SPARQL App
Developer
CP-ABE
Device
FIWARE App
Developer
PEP-Proxy
IoT Discovery
LoRa Device
SPARQL
Agent
KAT Toolkit
IoT Broker
Context Broker
IoT Knowledge
Server
Device API
SPARQL
NGSI10
NGSI9
KnowledgeServer API
NGSI10
NGSI9
NGSI10
SPARQL
NGSI10
NGSI10
NGSI9
NGSI10
Capability
API
IdM API
XACML
Encryption
API
STH Comet
NGSI10
FIWARE-based Platform Instance U2-based Platform Instance
IoTA to NGSI
Bridge
Utrecht
Sensor Data
CostFed

22. Smart Building
February 2019 © CPaaS.io Project Consortium 22

23. Smart Building– CPaaS.io Integration
February 2019 © CPaaS.io Project Consortium 23
IoT Resource Layer
IoT Data &Ingestion Layer
Virtual Entity Layer
Semantic Data &Integration Layer
Knowledge Layer
SMART CITY Services Layer
Security &
Privacy Pillar
Platform
Management ,
Federation and
Operation
Pillar
FogFlow
KeyRock
NGSI to RDF
mapper
XACML
Capability
Manager
Deployment
Tool
LoRaWAN to NGSI
bridge
Existing components
New/enhanced
components
IoT Agent
SPARQL App
Developer
CP-ABE
Device
FIWARE App
Developer
PEP-Proxy
IoT Discovery
LoRa Device
SPARQL
Agent
KAT Toolkit
IoT Broker
Context Broker
IoT Knowledge
Server
Device API
SPARQL
NGSI10
NGSI9
KnowledgeServer API
NGSI10
NGSI9
NGSI10
SPARQL
NGSI10
NGSI10
NGSI9
NGSI10
Capability
API
IdM API
XACML
Encryption
API
STH Comet
NGSI10
FIWARE-based Platform Instance U2-based Platform Instance
IoTA to NGSI
Bridge
Utrecht
Sensor Data
EU Connector
JP Connector

24. Secure Interoperabililty
February 2019 © CPaaS.io Project Consortium 24
FIWARE based
Platform (EU)
u2-based
Platform (JP)
- NGSI-based API updateContext & queryContext methods
- REST interfaces
- OpenID interoperability for authentication
- Access control mechanism for data Access in each side
EU
Connector
JP
Connector
RETRIEVE INFO FROM JP
RETRIEVE INFO FROM EU

25. ucR-Light for EU-Japan platform integration
(1st Prototype)
February 2019 © CPaaS.io Project Consortium 25
For the platform integration,
“ucR-Light” has been newly developed.
1. Retrieving data for each sensor
/api/<ucode>/sensorstate/
% curl http://133.11.240.193/api/00001C00000000000002000000063433/sensorstate/
• Retrieving temperature sensor data of ucode =
0x00001C00000000000002000000063433
2. Retrieving All sensor data
/api/ALL/sensorstate/
% curl http://133.11.240.193/api/ALL/sensorstate/
• Retrieving all sensor data in our intelligent building
Simple RDF-based JSON data format + simple
RESTful API which are easy to use even for other
platform users

26. Federation Mechanism
• Defined key aspects for real federation of smart city platforms.
• Allows for data sources to be used in a common way, via NGSI API
or through semantic SPARQL queries
• Increase the potential of the platforms and facilitating future
integration of subsystems, that follow the platform of platforms
model.
❖ Open strategy and by attending to events focused on customers
and/or smart city this software, or at least the need for having this
sort of solution can be motivated.
February 2019 © CPaaS.io Project Consortium 26

27. PERSONAL DATA STORE
Outcome #3
February 2019 © CPaaS.io Project Consortium 27

28. Personal Data Store
February 2019 © CPaaS.io Project Consortium 28

29. PDS Integration
February 2019 © CPaaS.io Project Consortium 29

30. PDS Personal Data Storage
February 2019 © CPaaS.io Project Consortium 30
Federation
using Linked
Data
Authentication using IdM
Authorization DCapBac
Privacy CP-ABE
Open ID Connect
Open ID Connect
PDS PDS
User
✓
• Secured interoperability
• OpenID connect integrated
• Authorization by the user is required

31. PDS Integration Demo: Digital Signage Personalization
February 2019 © CPaaS.io Project Consortium 31
Regular information
of UTsignage
Putting ID card of
“Martinez@es”
Putting ID card of
“Cheng@ch”
Authorized by
”Omotenashi” PDS
in JP
(for the Auth,
PIN in the card is used)
Visitor’s information Translated in Chinese Automatically
Visitor’s information Translated in Spanish Automatically
Clicking a link
Clicking a link
Authorization request is
transferred to EU PDS,
and authorization is
done in username and
password

32. EU-Dashboard - Login to New Account &
Editing PD
February 2019 © CPaaS.io Project Consortium 32
Login w/ New Account Get Current PD Change “Affiliation”

33. PERSONAL DATA STORE
• Exposing an API for registering services and accessing the stored personal
information.
• Presents an intuitive GUI that allows the users to easily handle the way each
specific detail/attribute of their personal information is disclosed.
• Federation of PDSs is also an added value for this software component
❖ Open strategy and by attending to events focused on customers and/or smart
city this software, or at least the need for having this sort of solution can be
motivated.
❖ Adoption of open and standard protocols assures that interested parties could
use and deploy it, or even evolve it to a richer solution.
❖ Of interest at different levels (local, regional or national), since it paves the way
for new solutions where the users make the decision about how their personal
information is managed.
February 2019 © CPaaS.io Project Consortium 33

34. DATA QUALITY ONTOLOGY
Outcome #4
February 2019 © CPaaS.io Project Consortium 34

35. February 2019 © CPaaS.io Project Consortium 35
MeasurementInfo Measurement
VirtualEntity
Owl:Thing MeasurementType MeasurementMeta
data
EmpiricalMeasure
ment
PowerSupplyInfo
PowerSupply
Device
QualityMetadata
Sensor
DataSource
VirtualSensor
PhysicalSensorClock
ClockSynchronisa
tion

36. SEDAQ
• Ontology representing quality of data
• Important when re-using information from other systems
• Based on:
• Basic W3C standards used for ontology modelling: RDF, RDFS, OWL.
• Existing vocabularies related to M2M: SSN, DCAT, OneM2M, PROV-O
❖ ETSI ISG CIM specification group also interested in data
quality aspect.
February 2019 © CPaaS.io Project Consortium 36

37. Gracias Mulțumesc 謝謝 Paldies Eskerrik asko Dziękuję Mahalo ‫תודה‬ Go raibh maith agat спасибо Grazzi आभारी
Xin cảm ơn 감사합니다 நன்றி Köszönöm ‫مرسي‬ Ndiyabulela Grazia Tak Благодаря Aitäh Terima kasih Děkuji
Asante Diolch ‫شكرا‬ Takk Ďakujem Gràcies Kiitos Obrigado Teşekkür ederim Ngiyabonga Þakka þér Grazas
Tapadh leibh ขอบคุณ Faleminderit Ačiū Danke Merci Grazie Hvala Ευχαριστώ Dankon Tack Dank je Grazcha
…
Thank You
ありがとう
This document has been produced in the context of the CPaaS.io project which is jointly funded by the European
Commission (grant agreement n° 723076) and NICT from Japan (management number 18302). All information provided
in this document is provided "as is" and no guarantee or warranty is given that the information is fit for any particular
purpose. The user thereof uses the information at its sole risk and liability. For the avoidance of all doubts, the European
Commission and NICT have no liability in respect of this document, which is merely representing the view of the project
consortium. This document is subject to change without notice.
February 2019 © CPaaS.io Project Consortium 37