onem2m: bridging iotconnectivity islands...2016/03/22 · onem2m: bridging iotconnectivity islands...
TRANSCRIPT
oneM2M:
Bridging IoT connectivity IslandsInternet of Things in the Smart Home, 21 March 2016
Enrico Scarrone
TIM/Global Advisory
Standard Coordination
oneM2M SC Vice Chair
ETSI TC SmartM2M Chair
Dr. Mahdi Ben Alaya
Founder & CEO - Sensinov
oneM2M TST WG Vice Chair
Omar Elloumi
Nokia
oneM2M TP Chair
ETSI TC SmartM2M Vice Chair
IoT Value chain
There are several analysis with slightly different
numbers……
All showing that TODAY the integration activities are
the greater part of the business
2
61%
18%
13%
8%
Deploy an IoT service today
is a complex exercise
Device
Communication
Network
Data
Platform
Management
Application
System
Business model
Process
3
And is not a
mature business….
So solutions,
approaches and
expertize are not
consolidated
IOT!!!
Integration
Interworking
Legacy
Regulation
Opportunities and problems .
• Diversity is the richness that allows evolution and
innovation: combination of services is the biggest
opportunity for the future
• But fragmentation of solutions and technologies is
the enemy that is delaying and blocking the
developments
• Simplify the environment, removing the
unnecessary duplicated solutions (economy of
scale), preserve the necessary/opportune solution
specialization by interwoking
4
Integrate Via open platforms
Source: CRYSTAL project/Philips
Platform based integration
Based on open standards
Home Energy HealthAutomotive
Communication Devices & Hardware
Communication Technologies &
Protocols
Common Service Layer
Communication Networks
Automotive
Applications
Home
Applications
Energy
Applicationse-Health
Applications
The role of Standardization
Support the developers community accelerating the
development of IoT
Transfer the competition from integration and platforms to
services unlocking the market
Reduce the cost of due to creation and management of silos
Enable Inter-technology and inter-domain data sharing
generating new services and new business opportunity
Reduce the costs, enlarge the market,
enable real competition on services
6
Over 200 member organizations in oneM2M
oneM2M Partnership Project
www.oneM2M.org
All document are publically available
Scope & Objectives
• To develop: Global M2M/IoT specifications -
using common use cases and architecture principles across multiple
M2M/IoT applications to connect devices and application servers
worldwide with an access independent view of end-to-end services
• To define: Service Layer platform supporting a service architecture
including:
- Protocols/APIs/standard objects (open interfaces & protocols)
- Interoperability, test and conformance specifications
- Service Layer interfaces/APIs for:
– Applications and service semantics/ontologies
– Communication and data sharing
– Security and privacy aspects
– Authentication, encryption, integrity verification
8
oneM2M simplified Architecture
AE AE AE
CSE CSE CSE
M2M Applications
M2M Service layer
Underlying Transport
Mca Mca Mca
Mcc Mcc
Mcn McnMcn Mcn
NSE NSENetwork Service Entity
Device Gateway(s) Servers
9
IoT cross-domain interoperability
Invert the pipe
• Highly fragmented market with small vendor-specific applications.
• Reinventing the wheel: Same services developed again and again.
• Each silo contains its own technologies without interop.
• End-to-end platform: common service capabilities layer.
• Interoperability at the level of communications and data.
• Seamless interaction between heterogeneous applications and devices.
OneM2M as Interworking framework:
Simplification does not means one solution!
Legacy technologies will continue to exist and needs to be
integrated
Specific technologies will be required in several sectors, for
technical and commercial reasons
In case of interworking, the real problem are not the
communication protocols, but the information semantics
and ontologies
oneM2M solution acts as interworking framework by means
of a significant separation between communication and
semantics aspects
oneM2MOther protocol/API oneM2M protocol/APIOther IoT
App
oneM2M
native App
oneM2M status highlights�Release 1 has been released in January 2015
� It is significantly based on Release 2 of ETSI M2M Specification developed
between 2009-2012. OneM2M standard is stable.
� It includes interworking communication support, but limited semantic support
�Launch event took place on December 2014 in ETSI with more than 10
multivendor demos
�There are several Open Source projects (e.g. in Ocean and Eclipse, etc…)
�First commercial service launched in May 2015 in Korea
� Interoperability test events was successfully run in September 2015
�ETSI WS - Featuring oneM2M in December 9-10-11 2015 has shown a significant
participation with more than 250 person registered.
�10 demos involving 32 companies, covering a cross section of the application
domains:
�Smart Metering, Home automation, Energy Efficiency, Smart living,
eHealth,Smart City & Intelligent Transport System
�The 2nd interoperability event will also be organized by ETSI & TTA .It will be held
in the TTA premises in Seongnam-city, Korea, from 10-13 May 2016
oneM2M Demos - Who Took Part
Planning for Release 2 – Planned Features
Industrial domainenablement
• Time series, etc.
• In conjunction with
the TR
oneM2MBeyond
initial release
Semanticinteroperability
• base ontology
• semantic discovery
• semantic
descriptions
Security• Enhancement for
authorization
• privacy support
• e2e security
Home domain enablement• Home appliance
information models
oneM2M Application Identification Registry established
Advanced protocol binding•WebSocket
oneM2M interworking framework
• Generic interworking
• AllJoyn/AllSeen
• OIC
• OMA LightWeight M2M
•3GPP Rel.13 interworking
14
Planning for Release 2 - Timeline
R2 normative work
Jul Aug Sep Oct Nov Dec Jan Feb Mar Apr May Jun Jul Aug Sep
Stage 1
R3 non-normative
work
R3 normative work
Stage1 Freeze
R2 normative work
Stage 2
R3 non normative
work
R3 normative work
R2 normative work
Stage 3
R3 normative work
Stage3 Freeze
2015 2016
TP24
R3 start norm work
Oct Nov
TP25
Stage2 Freeze
TP18 TP19 TP20 TP21 TP22 TP23
R2 approval
R2 ratification
TP26
ARC 19.4
Release 2
Release 3
Color Code
Semantic in oneM2M
16
01010101101
0101 01010101
Release 1
Semantic interoperability
Release 2
• oneM2M offered initial semantic enhancement in Release 1
and aims to provide full semantic support in the next releases.
Bin
ary
Text
Ke
yw
ord
s
De
scri
pti
on
Cla
ssif
ica
tio
n
On
tolo
gy
LAN
Business
Applications
Data
Analytics
Dashboards
LAN
WAN
LAN
Middle Node 1 Middle Node 2
Infrastructure Node
Interworking with non oneM2M Technologies
• The Interworking Proxy Entity (IPE) abstracts and maps the
non-oneM2M data model to the oneM2M resources.
• Bidrectional communication between the oneM2M system
and a specific technology (Monitor and Control).
• Seamless interaction between applications and devices using
the oneM2M Restful API.
18
Zigbee Zwave
Modbus
Canbus
Enocean
LWM2M
OIC
AllJoin
Others
KNX
LORA
Interworking
Proxy Entity
CSE
Non oneM2M entities oneM2M entities
oneM2M resources
interworking with semantic
CSE
Resource Repository
Interworking
Proxy Entity
Non oneM2M devices in Area Network Proxied devices in oneM2M system
oneM2M
Base
Ontology
Vertical
Domain
Ontology
19
• Non oneM2M Technologies are described using the oneM2M
base ontology + domain specific extensions.
• The Interworking Proxy Entity translates the ontology instance to
resources on the CSE based on pre-defined instantiation rules.
Evolution of semantic in oneM2M
<container>
<semanticDescriptor>
<AE>
label
ontologyRef
appName
<…>
…
0..1
0..n
0..1
0..n
0..n
..
..
Att
rib
tue
sC
hil
d R
eso
urc
es
Release-1: A set of labels (keywords) can
be defined for each resoruce. E.g.
« temperature », « luminosity »
Release-1: Each resource can be linked to
an ontology reference (description). E.g.
« http://ontology.tno.nl/saref#Device »
Release-2: A complete semantic
description can be added to a resource
(Ontology). E.g.<RDF>…</RDF>
Release-1: Resource Names (Text) can be
defined by the client and so have some
meaning. E.g. « Temperature-AE »
App-ID1
20
WANLAN Interworking
Proxy Entity
(IPE)
Gateway
End-Device-1
Measurement-1Measurement-1
DataData
Measurement-2Measurement-2
DescriptionDescription
DescriptorDescriptor
Measurement-3Measurement-3
Infrastructure
NodeMiddle Node
CSE
Application Entity
Container
Content Instance
Resource Type
oneM2M base ontology model
Service
Functionality
Operation
Input Output
Target Controlling
Measuring
Value
Aspect
Thing
isExposedBy
consistsOf
concerns
hasMethod hasTarget
hasInputMethod
hasOutput
isPartOf
AreaNetwork
Device
hasThingProperty
hasService
hasFunctionality
hasOperation refersTo
subclassOf
subclassOf
subclassOf
22
oneM2M base ontology instance
Service
#TempServ
Service
#TempServ
Measuring
#TempFunction
Measuring
#TempFunctionOperation
#RetrieveTempOp
Operation
#RetrieveTempOp
Output
#Temp
Output
#Temp
Target
#/MN-CSE/AE-123/CNT-TEMP
Target
#/MN-CSE/AE-123/CNT-TEMP
Value
#17
Value
#17
Aspect
#Temperature
Aspect
#Temperature
isExposedBy
concerns
hasMethod hasTarget
Method
#Retreive
Method
#Retreive
hasOutput
isPartOf
AreaNetwork
#WIFI-1
AreaNetwork
#WIFI-1
Device
#1234AB
Device
#1234ABhasThingProperty
hasService
hasFunctionality
hasOperation refersTo
describes
23
Mapping to vertical ontologies
onem2m:Service
Onem2m:FunctionalityOnem2m:Functionality
isExposedBy
onem2m:Device
hasService
hasFunctionality
saref:Servicesaref:Service
saref:Fonctionsaref:Fonction
represents
saref:Devicesaref:Device
offredByrepresents
Verical
domain
Saref
Ontology
Service
Layer
oneM2M
base
ontology
saref:TemperatureSensor
subClass
subClass
subClass
subClass
Aspect
refersTo
PropertyProperty
subClass
hasProperty
saref:Temperature
subClass
24
Thank you!!!!!!!
For contacts and questions:
www.oneM2M.org