showcase c...onem2m showcase configuration : smartcity data flow 9 resource tree viewer &...
TRANSCRIPT
Korea
KETI&
SKT & nTels
USA
CONVIDAWireless
Japan(Germany)
NEC Laboratories
Europe
Germany
FraunhoferFOKUS
Showcase C:
Smart City Services and Multiple Service
Layer Platforms Interworking
KETI – Convida Wireless – NEC – Fraunhofer – SKT – nTels
Presenter: Prof. Song JaeSeung, KETI & Sejong University, ([email protected])
Towards the Internet of Things
Federated
IoT
Infrastru
cture
Application Application
WSN Platform WSN Platform
WSN (Sink) WSN (GW)
Sink GW
Service Domain A Service Domain B
Application Application
IoT Platform
Fully addressable Thing
Service Domain A Service Domain B
Application Application Application
IoTPlatform
IoTPlatform
IoTPlatform
Fully addressable Thing
Service Domain A Service Domain B Service Domain A Service Domain B Domain A Domain B Domain C
Domain A Domain B Domain C
IoTness
Reference: Pedro Malo, Univ. Nova de Lisboa, IoT Week 2013
Vertical Horizontal Federated
2
Why is interoperability important in IoT?
Federated service infrastructures
Cross platform services
Platform independent services
Platform independent devices
Service Platform
A
Service Platform
B
Service Platform
C
Mobility Mobility
Service A Service B Service C
Device A Device B Device C
3
How can we enable interoperability using oneM2M?Io
TP
latf
orm
IoT
Serv
ice
IoT
Dev
ices
Service Domain A Service Domain B
Internet
4
1
2
5 Data interoperability
Platform to Platform
interoperability
Device to Platform
interoperability
Device to Device
interoperability
3 Service interoperability
4
IoT platformIoT platform
IoT GatewayIoT GatewayIoT Gateway
IoT platform
Interne
t
Interne
t
Interne
t
Interne
t
Interne
t
Interne
t
Interne
t Interne
t
IoT Device IoT Device IoT DeviceIoT DeviceIoT DeviceIoT Device
How can we enable interoperability using oneM2M?
IN-AE IN-AE(Service)
IN-AE
IN-CSE IN-CSE(Server)
IN-CSE
MN-CSE MN-CSE(Gateway)
MN-CSE
ADN ADN(End device)
ADN
InfrastructureDomain
Field Domain
Mca
Mcc’
Service Provider A Service Provider B Service Provider C
Mcc
Mca
Mcc’
Mca
Mcc
Mca
Mca
Mcc
Mca
1
23
• MN-CSE of Service Provider A can communicate with IN-CSE of Service Provider B via Mcc
• IN-AE of Service Provider A communicate with IN-CSE of Service Provider B via Mca/Mcc’/Mcc
• IN-AE of Service Provider C can communicate with IN-CSE of Service Provider B via Mca
1
2
3
Mcc
Mca
5
A collaboration between KETI, Convida, NEC, Fraunhofer, SKT and nTels (KINF)
KETI InterDigital/Convida Fraunhofer
NEC Laboratories Europe
3 IoT platforms
Smart city services
6
IN-CSE
IN-CSE
IN-CSE
SmartCity Application(AE)
Purpose and features of showcase C
Purpose of showcase Co Manufacturer independent connectivityo Discovery of various deviceso Interworking with smart city serviceso Interoperability between multiple oneM2M
platformso Information retrieval
Featureso AE registrationso CSE – CSE registrationso Container & ContentInstances
- CRUD operationso Subscription & Notificationo Multi-hop regargeting (PointOfAccess)
7
oneM2M Showcase Configuration (Interface)
8
Resource Tree Viewer & Protocol Analyser
IN-CSE
SmartCity Application(AE)
ADN-AESensor
y
x z
IN-CSE
AND-AESensor
ASN-CSESensor
ASN-CSEActuator
AE
AND-AE
SmartCitySensors
IN-CSE
Mcc’
Mcc’
Mcc’Mca
MccMcc
Mca
Mca
Mca
Dron LED-treeIllumination
SensorTemperature & HumiditySensor
IlluminationSensor
SmartCube
IlluminationSensor
Temp. & HumiditySensor
CONVIDA WirelessKETIFraunhofer FOKUSNEC
oneM2M Showcase Configuration : SmartCity Data Flow
9
Resource Tree Viewer & Protocol Analyser
IN-CSE
SmartCity Application(AE)
ADN-AESensor
y
x z
IN-CSE
AND-AESensor
ASN-CSESensor
ASN-CSEActuator
AE
AND-AE
SmartCitySensors
IN-CSE
Mcc’
Mcc’
Mcc’Mca
MccMcc
Dron LED-treeIllumination
SensorTemperature & HumiditySensor
IlluminationSensor
SmartCube
IlluminationSensor
Temp. & HumiditySensor
CONVIDA WirelessKETIFraunhofer FOKUSNEC
Mca
Mca
Mca
oneM2M Showcase Configuration : Actuator Call Flow
10
Resource Tree Viewer & Protocol Analyser
IN-CSE
SmartCity Application(AE)
ADN-AESensor
y
x z
IN-CSE
AND-AESensor
ASN-CSESensor
ASN-CSEActuator
AE
AND-AE
SmartCitySensors
IN-CSE
Mcc’
Mcc’
Mcc’
MccMcc
Dron LED-treeIllumination
SensorTemperature & HumiditySensor
IlluminationSensor
SmartCube
IlluminationSensor
Temp. & HumiditySensor
CONVIDA WirelessKETIFraunhofer FOKUSNEC
Mca
Mca
Mca
Mca
oneM2M Showcase Configuration : Data & Call Flow
11
Resource Tree Viewer & Protocol Analyser
IN-CSE
SmartCity Application(AE)
ADN-AESensor
y
x z
IN-CSE
AND-AESensor
ASN-CSESensor
ASN-CSEActuator
AE
AND-AE
SmartCitySensors
IN-CSE
Mcc’
Mcc’
Mcc’
MccMcc
Dron LED-treeIllumination
SensorTemperature & HumiditySensor
IlluminationSensor
SmartCube
IlluminationSensor
Temp. & HumiditySensor
CONVIDA WirelessKETIFraunhofer FOKUSNEC
Mca
Mca
Mca
Mca
oneM2M Showcase Configuration (Protocols)
12
Resource Tree Viewer & Protocol Analyser
IN-CSE
SmartCity Application(AE)
ADN-AESensor
y
x z
IN-CSE
AND-AESensor
ASN-CSESensor
ASN-CSEActuator
AE
AND-AE
SmartCitySensors
IN-CSE
Mcc’
Mcc’
Mcc’Mca
MccMcc
Mca
Mca
Mca
Dron LED-treeIllumination
SensorTemperature & HumiditySensor
IlluminationSensor
SmartCube
IlluminationSensor
Temp. & HumiditySensor
CONVIDA WirelessKETIFraunhofer FOKUSNEC
HTTP
HTTP
HTTP
HTTP
(CoAP)
HTTP
(CoAP, MQTT)
HTTP
(MQTT)
HTTP
(CoAP)
HTTP
(CoAP)
HTTP
(CoAP)
HTTP
Register AE
13
INCCSECNVDs01
ci1
ci2
ci3
ci4
ci5
ci6
ae07
ae08
c0
ae11
ae13
c1
KETI AE registers to Convida IN-CSE
ae07
resourceType = AE
parentID = /INCSECNVD
creationTime = 2014-12-04T18:12:57
expirationTime = 2014-12-04T18:14:37
lastModifiedTime = 2014-12-04T18:12:57
labels =
appName =
App-ID = ae07
AE-ID = /INCSECNVD/ae07
pointOfAccess =
ontologyRef =
nodeLink =
Create Containers and ContentInstances
14
INCCSECNVDs01
ci1
ci2
ci3
ci4
ci5
ci6
ae07
ae08
c0
ae11
ae13
c1
KETI AE creates containers and contentInstances on
Convida IN-CSE
ci1
resourceType = contentInstance
resourceID = /INCSECNVD/ae07/c01/ci1
parentID = /INCSECNVD/ae07/c01
creationTime = 2014-12-04T18:13:03
expirationTime = 2014-12-04T18:14:43
lastModifiedTime = 2014-12-04T18:13:03
stateTag = 1
labels =
creator =
announceTo =
announceAttribute = parentID
typeOfContent = text
contentSize = 1
ontologyRef =
content = 5
encoding =
Message Flow for SmartCity
15
The IoT Broker and NGSI-Binding were developed in the EU FP7 FI-WARE and FI-CORE Collaborative Projects
Sensor Data from City of Santander in OMA NGSI Context Format
Local Sensor Data inNGSI Context Format
Local Sensor Data inNGSI Context Format
Local Sensor Data inNGSI Context Format
Mca
Mcc
Mca
Mcc‘ Mcc‘
Mca
Cloud City Operation Center
… enables the city of Santander in Spain to improve the servicesit delivers to local residents by
automating the management of its public infrastructure while
reducing costs.(NEC Corporation, May 2014)IoT Broker
Data Format and Binding
16
Mca
Mcc
Mca
Mcc‘ Mcc‘
Mca
SmartCity AE
Resource Structure
Temperature & Light Container
Traffic Container
ParkingContainer
IrrigationContainer
Temperature & Light Instance 1
...
Temperature & Light Instance 2
{entityId: {
id: urn:x-iot:smartsantander:1:29,type: light,isPattern: false
}attributes: [
{name: light,contextValue: 3.65,type: light
},{
name: temperature,contextValue: 9.55,type: temperature
},<....>
]}
NGSI Data
Smart City Services Demo
17
Show the level of the CO2 emissions indifferent parts of the Santander city –from green, which is low to red, whichis high.
Show various devices (sensors andactuators) from one of oneM2Mplatforms.
Achievements and Lessons Learned
18
Feasibility of IoT services at global scale
Korea – Japan – Europe (Germany & Spain) – USA 1
Interworking between different oneM2M compliant platforms
Three oneM2M IoT platforms : KETI – SDP – openMTC2
Inclusion of various existing smart services
NEC Smart City Services + Genuine IoT Services3
Good open API libraries
Help developers to develop an IoT applications
An important ingredient for the IoT ecosystems4
Summary
19
Connected things (sensors and actuators) based on oneM2M specifications can facilitate smart services
Opening of things and standardized platforms capabilities allow creating converged services across industries
The IoT and oneM2M will bring us beyond connectivity
This showcase (SmartCity Services and Platforms Interworking) shows feasibilities of : o IoT services at global scaleo interworking between different oneM2M compliant platformso inclusion of many existing smart serviceso A need for good open API libraries
Smart services needs STANDARDIZED smart platforms
oneM2M Showcase
Annex 1 – KETI Mobius Open IoT Platform
21
IoT Device Platform (&CUBE) Open IoT Platform (Mobius)
Core
ThingManager
SecurityManager
ResourceManager
ApplicationManager
DeviceManager
InteractionManager
TAL MicroServer
Device Application
Annex 2 – Convida Wireless SDP
22
Annex 3 – Fraunhofer FOKUS OpenMTC
23
Comprehensive M2M/IoT platform
Enable the academia and industry to
Develop and validate domain-specific
M2M/IoT applications and services
Integrate various machine devices with
operator networks
Comprehensive M2M/IoT deployment
Over managed or unmanaged core
Intermediary layer
Between multiple managed domains
Service platforms, the operator network,
and devices
Aligned with ETSI and oneM2M spec
Extensible to specific research needs
Configurable & high performance
More Information: www.openMTC.org
Telco PaaS Front-end: OpenXSP
Smart City converged human-to-human
and M2M Services
OpenMTC
Annex 3 – Fraunhofer FOKUS OpenMTC Architecture
Managed Network
Unmanaged
networks
HTTP/CoAP/WebSocket
Diameter
Interworking Proxy
BluetoothZigBeeWiFiFS20IEC
Applic
ation
Enable
ment
Applic
ation
OpenM
TC F
ronte
nd
HSSANDSF
Application Enablement
Core FeaturesO
penM
TC B
ack
end
Device API Data API Network API
ApplicationsSmart grid app
ITS appeHealth app
Environment app
Connectivity Management
Transport Protocols
Core Features
RXMld/Mcc
Mcc‘
Mla/Mca
Mla/
Mca
Other M2M
Platform
Network Exposure
ConnectivityManagement
Network ExposureTransport Protocols
Local
networkLocal
networkLocal
network
Factory
PCRF
Access and Core – OpenEPC
Annex 4 – NEC Smart City Services
25
• The left side shows the noise level (black bars) and temperature level (green bars) averaged for six districts of the city of Santander.
• The right side shows the light levels for different sections of the city, where green indicates a low light level (at night), whereas brown indicates a high light level.