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 © 2015 oneM2M
1
Connected Pancakes – 1/3 “Thing”
“Thing”
Communication Unit
Communication Unit
Data Processing & Communication Application
Data Processing & Communication Application
Network
© 2015 oneM2M
Connected Pancakes – 2/3 “Thing”
“Thing”
Communication Unit
Communication Unit
Data Processing Part
Data Processing Part
Data Communication Part
Data Communication Part
Network
© 2015 oneM2M
Connected Pancakes – 3/3 “Thing”
“Thing”
Communication Unit
Communication Unit
Data Processing Part
Data Processing Part
Common Services Part
Common Services Part
Data Communication Part
Data Communication Part
Network
© 2015 oneM2M
oneM2M Pancakes “Thing”
“Thing”
Communication Unit
Communication Unit
Data Processing Part
Data Processing Part
Common Services Part
oneM2M
Data Communication Part
Common Services Part Data Communication Part
Network
© 2015 oneM2M
oneM2M Architecture 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 Service Layer
Mca
CSE
CSE
Mcn Network Layer
NSE
Mcc Underlying Network
Device (“Application Service Node”) © 2015 oneM2M
Mcn
NSE IoT Cloud Platform (“Infrastructure Node”)
oneM2M Functions Registration
Discovery
Security
Group Management
Data Management & Repository
Subscription & Notification
Device Management
Application & Service Management
Communication Management
Network Service Exposure
Location
Service Charging & 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
© 2015 oneM2M
oneM2M partnership 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
© 2015 oneM2M
9
oneM2M organization 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
WG1 – REQ
WG2 – ARC
Methods of Work Group
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)
© 2015 oneM2M
10
Purpose, Work & Deliverables 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 © 2015 oneM2M
11
oneM2M implementations Open source implementations
IotDM
Commercial implementations available and demos
COME AND SEE THE DEMOS © 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 © 2015 oneM2M
Interoperable standard Guidelines active collaborations
MQTT
uses interworks with
uses interworks with
OMADM LWM2M
interworks with
uses
HTTP CoAP TLS DTLS
Protocols
Full platforms © 2015 oneM2M
Interoperable standard Example implementation by KETI AllJoyn
Google Nest
oneM2M Interworking Proxy (for AllJoyn)
Powertech Smart Plug
oneM2M Interworking Proxy (for Nest)
onePass App
Pebble
oneM2M Service Entity AllJoyn (MN-CSE)
Dawon DNS Smart Plug
oneM2M Service Entity Nest (IN-CSE)
Open API
oneM2M oneM2M Hue Service Entity (IN-CSE)
oneM2M Service Entity (IN-CSE)
Jawbone Open API
Open API
OIC
onePass App
oneM2M Interworking Proxy (for Jawbone)
Jawbone U24
oneM2M Interworking Proxy (for Hue)
Philips Hue © 2015 oneM2M
onePass App
ConnecThing App
oneM2M Work Programme Release 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) • • • • • • • • • • • • • •
© 2015 oneM2M
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 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??? © 2015 oneM2M
17
Work Process Energy
Enterprise
Healthcare
Public Services
Residential
Other
Transportation
Industry
REQUIREMENTS TS‐0002
TECHNICAL REPORTS
TECHNICAL SPECS © 2015 oneM2M
18
Rel. 1 Technical Reports Architecture Analysis 1
Protocol Analysis
Use Cases
Architecture Analysis 2
TR‐0002
TR‐0001
TR‐0003
(WI‐0002)
(WI‐0001)
(WI‐0002)
Study of Mgt Capab. Enablnt
Abstraction & Semantics
Security Analysis
TR‐0009
TR‐0006
TR‐0007
TR‐0008
(WI‐0008)
(WI‐0004)
(WI‐0005)
(WI‐0007)
Roles & Focus Areas
Use Cases v2
E2E Security & 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) © 2015 oneM2M
19
Rel. 1 Technical Specifications Requirements
Functional Architecture
Definitions & Acronyms
Service Layer Core Protocols
TS‐0002
TS‐0001
TS‐0011
TS‐0004
(WI‐0001)
(WI‐0002)
(WI‐0003)
(WI‐0009)
HTTP Protocol Binding
CoAP Protocol Binding
Management Enablnt ‐ OMA
Management Enablnt ‐ BBF
TS‐0009
TS‐0008
TS‐0005
TS‐0006
(WI‐0013)
(WI‐0012)
(WI‐0010)
(WI‐0010)
MQTT Protocol Binding
Security 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 Industrial domain enablement (at least 1 normative feature)
Home domain enablement (at least 1 normative feature) • Home appliance information models
• Time series, etc. • In conjunction with the TR
Semantic interoperability • base ontology • semantic discovery • semantic descriptions
Advanced protocol binding • WebSocket (?) • Efficient content representations (?)
oneM2M beyond initial release
APP identifiers and registry services
oneM2M interworking framework
Security • Enhancement for authorization • privacy support • e2e security (?) © 2015 oneM2M
• Generic interworking • AllJoyn/AllSeen and/or • OIC and/or • OMA LightWeight M2M (OMA LWM2M) •3GPP Rel.13 Interworking 21
Still hungry?
© 2015 oneM2M
22