CPaaS.io - u2-based Toolbox

City Platform as a Service – Integrated and Open
U2 Toolbox
Noboru Koshizuka (UoT)
Final Project Review, Web Conference
February 21, 2019

Project Outcomes
u2 Toolbox Implementation
February 2019 © CPaaS.io Project Consortium 2
FIWARE
Toolbox
u2
Toolbox
Tools Supporting
City Developers
Conceptual Outcomes
Functional
Architecture
Federation
Mechanism
Personal Data
Store
Data Quality
Ontology
Concrete Results in Cities
Concepts
Implementations
Deployments
FIWARE
Toolbox
u2
Toolbox

u2 Toolbox Overview
• What we have worked out in CPaaS.io
• 5 new components (green)
• 3 enhanced components (orange)
• Status
• Fully integrated with existing u2 architecture
• u2-based Platform instance for CPaaS.io
• Validated by 3 use cases
• (1) Sapporo Open Data, (2) Yokosuka
Emergency Medical Service, (3) Tokyo Public
Transportation
• Additional new 3 use cases
• (1) Kochi Fishery, (2) Kochi Forestry, (3) e-MDH

Components of u2 Toolbox

uID Architecture: Most widely used IoT , Open Data
and PDS open architecture in Japan.
5
IoT Cloud
Edge Nodes
(IoT Engine, T-Kerne)
Ubiquitous
Communicator
(UI node)
February 2019 © CPaaS.io Project Consortium

Open Platform for IoT-Aggregator
Open Device Platform
▪ Devices from different manufacturers/vendors can
communicate with each other using IoT-Aggregator
▪ Devices are managed using ubiquitous ID
infrastructure
Open Application Platform
▪ Applications developed by application vendors or
individuals can be distributed, as well as official
applications provided by manufacturers
▪ Can be considered an “application store” for IoT, like
those for smartphones
Virtual devices
▪ Virtual devices are enhancing real devices can be
created
▪ Can be used just like real devices, but with access
control and other additional functions provided in the
cloud
6February 2019 © CPaaS.io Project Consortium

ucR-Light: Simple APIs for Platform Federation
Overview
• Simple APIs based on the ucR-model for platform
federation
• Syntax = RESTful API + JSON
• Semantics = ucode + RDF = ucR
General API Specification of ucR-Light
1. Retrieving data for each sensor
/api/<ucode>/sensorstate/
% curl
http://133.11.240.193/api/00001C00000000000002000000
063433/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
NEW

ucR-Light: Temperature sensors
Definition of JSON format data
{
"ucode": <ucode>, # ID of the sensor
"name": <Sensor Name>, # Name the sensor
"type": "temperature", # Sensor type = "temperature"
"category": "temp_sensor", # Sensor category = "temp_sensor"
"value": <value>, # Value of the sensor (degree in celcius)
"timestamp": <time stamp> # time stamp
}
Example
{
"ucode": "00001C00000000000002000000063433",
"name": "TempRoomA301",
"type": "temperature",
"category": "temp_sensor",
"value": "29.650002",
"timestamp": "2018-08-07 18:24:34"
}

ucR-Light: Humidity Sensors
{
"type": "humidity", # Sensor type = "humidity"
"category": "humid_sensor", # Sensor category = "humid_sensor"
"value": <value>, # Value of the sensor (percent)
}
Example
{
"ucode": "00001C00000000000002000000063434",
"name": "HumidRoomA301",
"type": "humidity",
"category": "humid_sensor",
"value": "57.851543",
"timestamp": "2018-08-07 18:24:36"
}

ucR-Light: Human Detection Sensors
{
"type": "humanditect", # Sensor type = "humanditect"
"category": "detect_sensor", # Sensor category = "detect_sensor"
"value": <value>, # Value of the sensor ("0" = non-detect, "1" = detect)
}
Example
{
"ucode": "00001C00000000000002000000063492",
"name": "DetectElevatorHallB1",
"type": "humanditect",
"category": "detect_sensor",
"value": "0",
"timestamp": "2018-08-07 18:25:50"
}

ucR-Light App (1) : UTdashboard
NEW

ucR-Light App (2) : UTsignage
integrated signage system
on u2 architecture
NEW

OPaaS.io: Omotenashi Platform
Overview
▪ OPaaS.io: “Omotenashi “Cloud” is a general-
purpose Personal Data Store (PDS) that uses the
IoT technology.
Functions
▪ Authorization: Starting authentication, logging in
by IDM, and acquiring an access token.
▪ User Management: Searching users, creating
users, and updating users’ information.
▪ Access Authority Management: Searching
authorized services, searching authorized user
attributes, and updating authority.
Enhancement
▪ Functions and APIs are enhanced in this project
New Enhanced OPaaS.io is published at:
▪ https://contest.opaas.io/api-spec.html
“Omotenashi” cloud dashboard
(user interface of PDS)

u2 Open Data Catalog (1)
Overview
▪ u2 Open Data Catalog is a open data catalog component in u2
architecture.
▪ It can contain not only metadata (catalog data) of open data but
also data bodies.
▪ It can deal with not only static data but also real-time dynamic
data.
Function
▪ 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

u2 Open Data Catalog (2)
New component
▪ Blockchain-based new open data
catalog system.
▪ Sapporo city and Fukuoka city are
now trying to use the new system.
▪ Blockchain-based open data
catalog is useful when community-
based organizations are managing
open data storage such as NGOs
and civic tech organization.
API Server (read only)
Global Data
State Storage
(JSON DB)
Blockchain
Server
Validator Node
Private Blockchain
Network
Web Client
NEW

kokosil
Overview
▪ kokosil is a software package to provide
information for visitors and tourists in towns,
tourist spots, commercial facilities, museums, parks,
exhibition venues, etc.
▪ It has a management function to register
information on target areas, tourist facilities, stores,
etc. easily, information distribution function to
provide timely information on popular seasonal
spots, ongoing events, etc.,
▪ kokosil has been introduced in more than 50 areas
and facilities so far.
▪
Enhancement
▪ Kokosil and Omotenashi cloud are integrated for
high-quality personalized end-user services
▪ Tourism information is customized according to
the personal data in OPaaS.io: preference, physical
condition, language, ...

IoT Engine (μT-Kernel 2.0)
Overview
▪ IoT-Engine is a standard development platform,
standardized by TRON Forum, for Open IoT to
realize "Aggregate Computing".
▪ IoT-Engine standard specifies the connector on
the Micro Processor Unit (MPU) board, and the
RTOS used by the MPU, and requires the function
to connect to the cloud services on the Internet.
▪ The RTOS used on the IoT-Engine is µT-Kernel 2.0
which TRON Forum releases as open source.
Enhancement
▪ µT-Kernel 2.0 (IEEE Std 2050-2018) is a light-weight
real-time operating system with small footprint,
which is open source software and adequate for
the IoT edge node devices.
▪ Standard edge nodes of the u2-based architecture
uses µT-Kernel 2.0.

ucode BLE
Overview
▪ In-house positioning device with
BLE communication and ucode
technology
▪ Low-energy
New Component
▪ ucode BLE with location proof
function with location proof verifier
on cloud servers
New ucode
BLE Beacon
NEW

Use Cases of u2 Toolbox

Use Cases: Sapporo Open Data for Tourism
Public Transportation
Data
Sports Event
Data
Sports Facility
Data
Tourist Information
Data
Sapporo Open Data Center
for Tourism
Digital Signage
Smartphone
Services
Hackathon,
Ideathon Events
BLE Beacon
Signboard
with BLE tag
Kokosil: Location-
aware Information
Service for Tourists

Use Cases: Yokosuka for Emergency Medical Servicess
IoT Smart
Ambulances
IP Camera Data
GPS-based
Geo-location Data
IoT Emergency Medical
Service System
Smartphones
for Doctors
Emergency
Hospitals
IP Camera Data
Smartphones
for Doctors
Position of Ambulance
Images of Patients

Use Cases: Tokyo Public Transportation Open Data
Operation Data
of Railways
Facility Data
Operation Data
of Bus
Operation Data
of Airplanes
Public Transportation
Open Data Center
Application Developers
(ICT Service Vendors)
Application Developers
(ICT Service Vendors)
Digital Signage
Smartphone
Services
Smartphone
Services

New use cases
Fishery Use Cases “See See”: Sea state monitoring
system for fishery industry
Forestry Use Cases “Ring Ring”: Safety
Monitoring System for Forestry Workers
e-MCDH: Mother-Child-Doctor Handbook for
Emergency Medical Service using OPaaS.io
NEWNEW
NEW

Deployment of u2 Toolbox

Usage of u2 Toolbox
Orchestrating your own
smart city app/platform
out of the box
u2 Toolbox
Already validated with 3 use cases in CPaaS.io
(Sapporo Open Data for Tourism, Tokyo Public
Transportation Open Data, Yokosuka Emergency
Medical Services)
Additional 3 use cases in CPaaS.io
(Kochi IoT Fishery, Kochi IoT Forestry,
e-MCDH: Mother-Child-Doctor Handbook)

Conclusion
• 5 new components have been introduced to CPaaS.io platform
• 3 components have been enhanced.
• Pre-existing components have been integrated and validated
• New standard IEEE 2050-2018: IEEE Standard for a Real-Time Operating
System (RTOS) for Small-Scale Embedded Systems (μT-Kernel 2.0)
Outlook beyond the project
Edge node components of u2 toolbox such as IoT-Engine, μT-Kernel, and ucode BLE are
available from the market or open source software of TRON Forum (www.tron.org). Cloud-
side components are available as web service and/or API-services such as “Omotenashi”-
cloud, u2 Open Data Catalog, and kokosil. TRON forum and open data/IoT community of
smart cities such as Yokosuka, Sapporo, and Tokyo are strongly support our architecture and
building a ecosystem of u2 toolbox.

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.

CPaaS.io - u2-based Toolbox

Recommandé

Recommandé

Contenu connexe

Tendances

Tendances (20)

Similaire à CPaaS.io - u2-based Toolbox

Similaire à CPaaS.io - u2-based Toolbox (20)

Plus de Stephan Haller

Plus de Stephan Haller (20)

Dernier

Dernier (20)

CPaaS.io - u2-based Toolbox