1. ONEM2M RELEASE 2: SETTING THE STANDARD FOR IOT INTEROPERABILITY
Dr. Omar Elloumi, Nokia; Dr. Josef Blanz, Qualcomm; Nicolas Damour, Sierra Wireless;
Dale Seed, Interdigital
Moderator: Ultan Mulligan, ETSI & oneM2M Marcom vice-chair
IoT Grand Slam, 1 December 2016

2. Panelists Dr. Omar Elloumi, Nokia. oneM2M TP Chair
Dr. Josef Blanz, Qualcomm. oneM2M TP vice-Chair
Nicolas Damour, Sierra Wireless, oneM2M ARC WG Chair
Dale Seed, Interdigital, oneM2M contributor
Moderator: Ultan Mulligan, ETSI, oneM2M Marcom vice-Chair

3. oneM2M Partnership Project
Over 200 member organizations in oneM2M
All documents are publically available

4. What is oneM2M? Application Layer Service Layer Network Layer
It is a software/middleware layer
It sits between applications and underlying communication networking HW/SW
It typically rides on top of IP protocol stack
It provides functions that applications across different industry segments commonly need
It exposes common set of functions to applications via developer friendly APIs
It is integrated into devices/gateways/servers and allows distributed intelligence
It hides complexity of NW usage from apps
It controls when communication happens
It stores and shares data
It supports access control
It notifies applications about events
Application Layer
Service Layer
Network Layer

5. Communication Network(s)
What is oneM2M? …
HVAC Apps
Home Apps
Asset Apps
eHealth Apps
Simple APIs via Standardized Reference Points
Service Layer
Data Processing Resources & Protocols & Communication HW
Communication Network(s)
Horizontal layer of functions commonly needed across different industry verticals

6. Break the silos and simplify the environment
Pipe#1
1 Application, 1 Network 1 (or few) types of Device
Pipe#2
1 Application, 1 Network 1 (or few) types of Device
Pipe#N
1 Application, 1 Network 1 (or few) types of Device
Horizontal (based on common Layer)
Applications share common infrastructure, environments and network elements
Business
Application # 1 i N
Transport Network 1
Transport Network 2
Local NW
Device
Common Application Infrastructure
Gateway IP
Business Application
Business Application
Business Application
Transport Network (mobile, fixed, Powerline ..)
Transport Network (mobile, fixed, Powerline ..)
Transport Network (mobile, fixed, Powerline ..)
Local NW
Gateway
Local NW
Gateway
Local NW
Gateway
Device
Device
Device 6 6

7. Motivation for oneM2M Vertical Silos Interconnected Silos
Intra-Vertical or Intra-Use Case
Lower cost
CAPEX & OPEX impact as explained, easier to maintain, focus only on Apps
Larger eco system: More choices
Transition from one SP to another SP using same standard
Chose from different SW/HW vendors that offer standard compliant products
Select products that match with individual requirements, minimize cost for customization
Inter-Vertical or Inter-Use Case
All of the motivators above, plus:
Sharing Data Across Verticals brings about New Business Opportunities
Shared access to sensors/actors/events/data allows for new business models / added value

8. oneM2M Release 2 Home domain enablement Industrial domain enablement
Home appliance information models
Industrial domain enablement
Time series data
oneM2M
Beyond
initial release
oneM2M Application Identification Registry established
Semantic interoperability
Base ontology
Semantic discovery
Semantic descriptions
oneM2M interworking framework
Generic interworking
AllJoyn/AllSeen
OIC
OMA LWM2M
3GPP Rel.13 Interworking
Advanced protocol binding
WebSockets
Security
Dynamic Authorization
End-to-End Security
Privacy support

9. Strong implementation base
Industry-driven Open source implementations
Examples of Commercial implementations /demos
2 successful interop events held in 2015/2016
With 30 participating organizations and 75 engineers
IotDM

10. Ongoing collaborations
Guidelines & Ref. Arch.
collaborations
MQTT
Now OCF
uses
interworks with
OMADM LWM2M
Uses/interworks
HTTP CoAP TLS DTLS
interworks with
uses
Protocols
Platforms

11. oneM2M Release 2 Specifications
TS 0001: Functional Architecture
TS 0002: Requirements
TS 0003: Security Solutions
TS 0004: Service Layer Core Protocol
TS 0005: Management Enablement (OMA)
TS 0006: Management Enablement (BBF)
TS 0007: Service Components
TS 0009: HTTP Protocol Binding
TS 0010: MQTT Protocol Binding
TS 0011: Common Terminology
TS 0012: oneM2M Base Ontology
TS 0014: LWM2M Interworking
TS 0015: Testing Framework
TS 0020: WebSocket Protocol Binding
TS 0021: oneM2M and AllJoyn Interworking
TS 0023: Home Appliances Information Model and Mapping
TS 0024: OIC Interworking
TR 0001: Use Cases Collection
TR 0007: Study of Abstraction and Semantic Enablements
TR 0008: Security
TR 0012: oneM2M End-to-End security and Group Authentication
TR 0016: Study of Authorization Architecture for Supporting Heterogeneous Access Control Policies
TR 0017: Home Domain Abstract Information Model
TR 0018: Industrial Domain Enablement
TR 0022: Continuation and Integration of HGI Smart Home Activities
TR 0024: 3GPP Release 13 Interworking

12. Check out recorded oneM2M webinars
“oneM2M:How standardization enables the next internet evolution”
“Taking a look inside oneM2M”
“Facing the Challenges of M2M Security and Privacy”
“On Management, Abstraction & Semantics”
“oneM2M Release 1 Primer: What’s in there, and why is it important?”
“Personal Connected Healthcare: how oneM2M can help develop the market”
“Accelerating the Internet of Things: The oneM2M App-ID Registry”
“Enhancing oneM2M platform with semantics, why does it matter?”
“Use of the oneM2M standard in the oneTransport field”
“Future proof IoT based smart cities using oneM2M”
“oneM2M Release 2 Overview”

13. Where to find info? https://www.youtube.com/c/onem2morg
Web Site
Join oneM2M
YouTube Channel
Webinars
Published Specifications