Standardized Service Layering for Iot in Onem2m

Standardized Service Layering for IoT in oneM2M

ETSI M2M Workshop, Sophia‐Antipolis, Dec. 2015 Nicolas Damour, [email protected] Senior Manager for Business & Innovation at Sierra Wireless Chairman of the Architecture Working Group at oneM2M

“Thing” “Thing”

Communication Communication Unit Unit

Data Processing Data Processing & Communication & Communication Application Application

Network

“Thing” “Thing”

Communication Communication Unit Unit Data Processing Data Processing Part Part

Data Communication Data Communication Part Part

Network

“Thing” “Thing”

Communication Communication Unit Unit Data Processing Data Processing Part Part Common Services Common Services Part Part Data Communication Data Communication Part Part

Network

“Thing” “Thing”

Communication Communication Unit Unit Data Processing Data Processing Part Part Common Services Common Services oneM2M Part Part Data Communication Data Communication Part Part

Network

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

Application Layer AE AE Mca Mca

Service Layer CSE CSE Mcn Mcc Mcn

Network Underlying Layer NSE Network NSE

Group Registration Discovery Security Management

Data Application & Subscription & Device Management & Service Notification Management Repository Management

Communication Network Service Service Charging Location Management Exposure & Accounting

© 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

Partnership project between 14 partners created in 2012 to specify and promote a standard for an IoT/M2M Common Service Layer

Over 200 active member organizations

SC ‐ STEERING COMMITTEE Chairman: Fran O’Brien, Cisco Vice‐chairs: E. Scarrone, Telecom Italia ‐ P. Jain, Intel ‐ T. Li, Huawei

Finance Committee Marketing & Communication Committee Legal Committee Methods & Processes Committee

TP ‐ TECHNICAL PLENARY Chairman: Omar Elloumi, Alcatel‐Lucent Vice‐chairs: R. Hechwartner, Deutsche Telekom; N. Yamasaki, KDDI; K. Young Kim, LG Electronics

Work Programme Management Group Coordination Team Methods of Work Group

WG1 –REQ WG2 –ARC WG3 –PRO WG4 –SEC WG5 –MAS WG6 –TST Requirements Architecture Protocols Security Mgt Abst. & Sem. Test S. Kiewel (iconectiv) N. Damour (Sierra W.) P. Niblett (IBM) F. Ennesser (Gemalto) Y. Zhang (Huawei) J. Song (KETI)

Purpose To specify and promote a Standard for an M2M/IoT Common Service Layer Work Six physical 1‐week meetings per year with ~100 attendees 200+ documents produced and discussed at each meeting 3800 docs in 2013 4400 docs in 2014 Deliverables Technical Reports (TRs) and Technical Specifications (TSs) Release 1 published in January 2015 –10 TSs + 5 TRs Release 2 planned for mid‐2016

Open source implementations

IotDM

Commercial implementations available and demos COME AND SEE THE DEMOS

• 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

Guidelines

active collaborations

MQTT uses interworks with

uses interworks with OMADM LWM2M

interworks with uses

HTTP CoAP TLS DTLS

Example implementation by KETI AllJoyn Google Nest

oneM2M oneM2M Interworking Interworking onePass Proxy Proxy App (for AllJoyn) (for Nest) Powertech Smart Plug Pebble

Open oneM2M oneM2M API Service Entity Service Entity AllJoyn(MN-CSE) (IN-CSE)Nest Dawon DNS Smart Plug

oneM2M

oneM2M oneM2M Jawbone Hue Service Entity Service Entity Open (IN-CSE) (IN-CSE) Open API API

OIC onePass oneM2M oneM2M onePass App Interworking Interworking App Proxy Proxy (for Jawbone) (for Hue)

Jawbone U24 Philips Hue ConnecThing App

© 2015 oneM2M oneM2M Work Programme Release 1 (publ. Jan. 2015) Release 2 (target ~mid. 2016) • WI‐01 ‐ Requirements • WI‐15 ‐ Use Cases v2 • WI‐02 ‐ Architecture • WI‐16 ‐ E2E Security & Groups • WI‐03 ‐ Vocabulary • WI‐17 ‐ Home Domain Enablement • WI‐04 ‐ Study of Managt Capability • WI‐18 ‐ oneM2M & AllJoyn IWK • WI‐05 ‐ Abstraction & Semantics • WI‐19 ‐ Dynamic Authorization • WI‐06 ‐ Device/GW Classification • … • WI‐07 ‐ Security • WI‐24 ‐ LWM2M Interworking • WI‐08 ‐ Protocol Analysis • WI‐25 ‐ Area Ntwks Gen. Interwrkg • WI‐09 ‐ Protocols • WI‐26 ‐ Efficient Communications • WI‐10 ‐ Management Enablement • WI‐27 ‐ Testing Framework • WI‐11 ‐ Service Components Arch. • WI‐28 ‐ Industrial Domain Enablnt • WI‐12 ‐ RESTful COAP Protocol • … • WI‐13 ‐ RESTful HTTP Protocol • WI‐43 ‐ Contin. of HGI Smart Home • WI‐14 ‐ MQTT Protocol • WI‐44 ‐ oneM2M & OIC IWK © 2015 oneM2M 16 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???

Energy Enterprise Healthcare Public Services

Residential Other Transportation Industry

REQUIREMENTS TS‐0002

TECHNICAL REPORTS TECHNICAL SPECS

Architecture Use Architecture Analysis 1 Cases Analysis 2 TR‐0002 TR‐0001 TR‐0003 (WI‐0002) (WI‐0001) (WI‐0002)

Protocol Study of Mgt Abstraction & Security Analysis Capab. Enablnt Semantics Analysis TR‐0009 TR‐0006 TR‐0007 TR‐0008 (WI‐0008) (WI‐0004) (WI‐0005) (WI‐0007)

Roles & Use E2E Security & Focus Areas Cases v2 Group Authent. TR‐0005 TR‐0011 TR‐0012 (WI‐0003) (WI‐0014) (WI‐0011)

(Now 82 Tech. Reports under way for Rel. 2 as of Sept. 2015)

Requirements Functional Definitions Service Layer Architecture & Acronyms Core Protocols TS‐0002 TS‐0001 TS‐0011 TS‐0004 (WI‐0001) (WI‐0002) (WI‐0003) (WI‐0009)

HTTP Protocol CoAP Protocol Management Management Binding Binding Enablnt ‐ OMA Enablnt ‐ BBF TS‐0009 TS‐0008 TS‐0005 TS‐0006 (WI‐0013) (WI‐0012) (WI‐0010) (WI‐0010)

MQTT Protocol Security Binding Solutions TS‐0010 TS‐0003 (WI‐0014) (WI‐0007)

(Now 32 Tech. Specifications under way for Rel. 2 as of Sept. 2015)

© 2015 oneM2M 20 oneM2M Release 2 features Home domain Industrial domain enablement (at least 1 enablement (at least 1 normative feature) normative feature) • Home appliance • Time series, etc. information models • In conjunction with the TR APP identifiers and registry services oneM2M Semantic interoperability beyond • base ontology initial release • semantic discovery • semantic descriptions oneM2M interworking framework • Generic interworking • AllJoyn/AllSeen and/or Advanced protocol binding Security • OIC and/or • WebSocket (?) • Enhancement for • OMA LightWeight • Efficient content authorization M2M (OMA LWM2M) representations (?) • privacy support •3GPP Rel.13 • e2e security (?) Interworking © 2015 oneM2M 21 Still hungry?