Page 1
© 2015 oneM2M 1
Standardized Service Layering for IoT in oneM2M
ETSI M2M Workshop, Sophia‐Antipolis, Dec. 2015Nicolas Damour, [email protected]
Senior Manager for Business & Innovation at Sierra WirelessChairman of the Architecture Working Group at oneM2M
Page 2
© 2015 oneM2M
Connected Pancakes – 1/3“Thing”“Thing”
Communication Unit
Communication Unit
Data Processing& Communication
Application
Data Processing& Communication
Application
Network
Page 3
© 2015 oneM2M
Connected Pancakes – 2/3“Thing”“Thing”
Communication Unit
Communication Unit
Network
Data CommunicationPart
Data ProcessingPart
Data CommunicationPart
Data ProcessingPart
Page 4
© 2015 oneM2M
Connected Pancakes – 3/3“Thing”“Thing”
Communication Unit
Communication Unit
Network
Data CommunicationPart
Data ProcessingPart
Data CommunicationPart
Data ProcessingPart
Common ServicesPart
Common ServicesPart
Page 5
© 2015 oneM2M
“Thing”“Thing”
Communication Unit
Communication Unit
oneM2M
oneM2M Pancakes
Network
Data CommunicationPart
Data ProcessingPart
Data CommunicationPart
Data ProcessingPart
Common ServicesPart
Common ServicesPart
Page 6
© 2015 oneM2M
UnderlyingNetwork
CSE
AE
CSE
AE
NSENSE
Device(“Application Service Node”)
IoT Cloud Platform(“Infrastructure Node”)
ApplicationLayer
ServiceLayer
NetworkLayer
McaMca McaMca
McnMcnMcnMcn MccMcc
Node (Host) Logical equivalent of a physical (or possibly virtualized) device
Common Services Entity (Service Layer) Provides the set of "service functions" common to the M2M environments
Application Entity (Application) Provides application logic for the end‐to‐end M2M solutions
Reference Point (Interface) One or more interfaces ‐Mca, Mcn, Mcc and Mcc’ (between 2 service providers)
Network Services Entity (Modem) Provides connectivity services to the CSEs besides the pure data transport
oneM2M Architecture
Page 7
© 2015 oneM2M
Registration Group ManagementSecurityDiscovery
Data Management & Repository
Application & Service
Management
Device Management
Subscription & Notification
Communication Management
Service Charging & AccountingLocationNetwork Service
Exposure
oneM2M Functions
Page 8
© 2015 oneM2M
Importance of standards• Reduced deployment and operation costs
• Cost‐effective products thanks to focused R&D efforts• Easier application development• Easier integration between solution components• Ability to share and reuse infrastructure and field devices
• Sustainable investments• No vendor lock‐in• Ability to benefit from further evolutions of the standard as it grows
• Improved opportunities• Ability to share and reuse data across vertical applications• Ability to interconnect with other IoT/M2M systems• Fostering of new applications and new business models
Page 9
© 2015 oneM2M 9
Over 200 active member organizations
Partnership project between 14 partnerscreated in 2012 to specify and promote
a standard for an IoT/M2M Common Service Layer
oneM2M partnership
Page 10
© 2015 oneM2M 10
SC ‐ STEERING COMMITTEEChairman: Fran O’Brien, Cisco
Vice‐chairs: E. Scarrone, Telecom Italia ‐ P. Jain, Intel ‐ T. Li, Huawei
TP ‐ TECHNICAL PLENARYChairman: Omar Elloumi, Alcatel‐Lucent
Vice‐chairs: R. Hechwartner, Deutsche Telekom; N. Yamasaki, KDDI; K. Young Kim, LG Electronics
Marketing & Communication Committee
Methods & Processes Committee
Finance Committee
Legal Committee
Coordination TeamMethods of Work Group
Work Programme Management Group
WG1 – REQRequirementsS. Kiewel (iconectiv)
WG2 – ARCArchitecture
N. Damour (Sierra W.)
WG3 – PROProtocols
P. Niblett (IBM)
WG4 – SECSecurity
F. Ennesser (Gemalto)
WG5 – MASMgt Abst. & Sem.
Y. Zhang (Huawei)
WG6 – TSTTest
J. Song (KETI)
oneM2M organization
Page 11
© 2015 oneM2M 11
Purpose, Work & Deliverables
PurposeTo specify and promote a
Standard for an M2M/IoT Common Service Layer
WorkSix physical 1‐week meetings per year with ~100 attendees200+ documents produced and discussed at each meeting
3800 docs in 2013 4400 docs in 2014
DeliverablesTechnical Reports (TRs) and Technical Specifications (TSs)Release 1 published in January 2015 – 10 TSs + 5 TRs
Release 2 planned for mid‐2016
Page 12
© 2015 oneM2M
oneM2M implementations
Open source implementations
Commercial implementationsavailable and demos
COME AND SEE THE DEMOS
IotDM
Page 13
© 2015 oneM2M
Mature and active standard
• Work started in 2012, leveraging 3+ years of experience
• 3800 docs produced in 2013, 4400 docs in 2014…
• Release 1 published in Jan 2015
• 16 specifications published so far
• More than 40 specifications in the works
• Hundreds of documents produced every month
• Corrections to release 1 actively maintained
• Release 2 with new features planned for 2016
Page 14
© 2015 oneM2M
Interoperable standard
Guidelines
Protocols Full platforms
MQTT
OMADM LWM2M
HTTP CoAP TLS DTLS
uses
uses
usesinterworks with
interworks with
interworks with
active collaborations
Page 15
© 2015 oneM2M
Interoperable standard
ConnecThing App
AllJoyn Google Nest
Jawbone U24 Philips Hue
PowertechSmart Plug
oneM2MService Entity(MN-CSE)
Dawon DNSSmart Plug
oneM2M Interworking
Proxy (for AllJoyn)
oneM2MService Entity
(IN-CSE)
oneM2M Interworking
Proxy (for Nest)
oneM2MService Entity
(IN-CSE)
oneM2M Interworking
Proxy (for Hue)
oneM2MService Entity(IN-CSE)
oneM2M Interworking
Proxy (for Jawbone)
Pebble
NestAllJoyn
OIC
HueJawbone
oneM2M
onePassApp
OpenAPI
onePassApp
OpenAPI
onePassApp
OpenAPI
Example implementation by KETI
Page 16
© 2015 oneM2M 16
oneM2M Work ProgrammeRelease 1 (publ. Jan. 2015)• WI‐01 ‐ Requirements• WI‐02 ‐ Architecture• WI‐03 ‐ Vocabulary• WI‐04 ‐ Study of Managt Capability• WI‐05 ‐ Abstraction & Semantics• WI‐06 ‐ Device/GW Classification• WI‐07 ‐ Security• WI‐08 ‐ Protocol Analysis• WI‐09 ‐ Protocols• WI‐10 ‐Management Enablement• WI‐11 ‐ Service Components Arch.• WI‐12 ‐ RESTful COAP Protocol• WI‐13 ‐ RESTful HTTP Protocol• WI‐14 ‐MQTT Protocol
Release 2 (target ~mid. 2016)• WI‐15 ‐ Use Cases v2• WI‐16 ‐ E2E Security & Groups• WI‐17 ‐ Home Domain Enablement• WI‐18 ‐ oneM2M & AllJoyn IWK• WI‐19 ‐ Dynamic Authorization• …• WI‐24 ‐ LWM2M Interworking• WI‐25 ‐ Area Ntwks Gen. Interwrkg• WI‐26 ‐ Efficient Communications• WI‐27 ‐ Testing Framework• WI‐28 ‐ Industrial Domain Enablnt• …• WI‐43 ‐ Contin. of HGI Smart Home• WI‐44 ‐ oneM2M & OIC IWK
Page 17
© 2015 oneM2M 17
Collaborative Mindset
• Collaborative mindset within oneM2M• Partnership Project from the start• Strong focus on reusing existing technologies wherever possible• Strong consideration for user industries
• Collaborative mindset with external organizations• Personal Connected Health Alliance – Continua• Home Gateway Initiative• AllSeen Alliance• Open Interconnect Consortium• European Smart Metering Industry Group• IEEE P2413• ITU‐T SG20• W3C• Industrial Internet Consortium???
Page 18
© 2015 oneM2M 18
Work Process
Public ServicesEnterprise HealthcareEnergy
TransportationOtherResidential
REQUIREMENTSTS‐0002
TECHNICAL SPECSTECHNICAL REPORTS
Industry
Page 19
© 2015 oneM2M 19
ArchitectureAnalysis 1
TR‐0002(WI‐0002)
ArchitectureAnalysis 2
TR‐0003(WI‐0002)
UseCasesTR‐0001(WI‐0001)
ProtocolAnalysisTR‐0009(WI‐0008)
SecurityAnalysisTR‐0008(WI‐0007)
Abstraction & Semantics
TR‐0007(WI‐0005)
Study of MgtCapab. Enablnt
TR‐0006(WI‐0004)
E2E Security &Group Authent.
TR‐0012(WI‐0011)
UseCases v2TR‐0011(WI‐0014)
Roles &Focus Areas
TR‐0005(WI‐0003)
Rel. 1 Technical Reports
(Now 82 Tech. Reports under way for Rel. 2 as of Sept. 2015)
Page 20
© 2015 oneM2M 20
SecuritySolutions
TS‐0003(WI‐0007)
MQTT ProtocolBindingTS‐0010(WI‐0014)
FunctionalArchitecture
TS‐0001(WI‐0002)
Requirements
TS‐0002(WI‐0001)
Rel. 1 Technical Specifications
Service LayerCore Protocols
TS‐0004(WI‐0009)
Definitions& Acronyms
TS‐0011(WI‐0003)
ManagementEnablnt ‐ BBF
TS‐0006(WI‐0010)
ManagementEnablnt ‐ OMA
TS‐0005(WI‐0010)
CoAP ProtocolBindingTS‐0008(WI‐0012)
HTTP ProtocolBindingTS‐0009(WI‐0013)
(Now 32 Tech. Specifications under way for Rel. 2 as of Sept. 2015)
Page 21
© 2015 oneM2M 21
oneM2M Release 2 featuresIndustrial domainenablement (at least 1 normative feature)
• Time series, etc.• In conjunction with the TR
oneM2Mbeyond
initial release
Semantic interoperability• base ontology• semantic discovery• semantic descriptions
Security• Enhancement for authorization • privacy support• e2e security (?)
oneM2M interworking framework
• Generic interworking• AllJoyn/AllSeenand/or• OIC and/or• OMA LightWeightM2M (OMA LWM2M)•3GPP Rel.13 Interworking
Home domainenablement (at least 1 normative feature)
• Home applianceinformation models
APP identifiers and registry services
Advanced protocol binding•WebSocket (?)• Efficient content representations (?)
Page 22
© 2015 oneM2M 22
Still hungry?