oneM2M Overview

Roland Hechwartner, oneM2M TP Chair

oneM2M Industry Day
IIIT, Hyderabad 25 September 2019

1
 Agenda – oneM2M @ Industry
Day
• oneM2M Overview – this presentation
Followed by…
• Do No Harm to the Network using oneM2M - oneM2M – 3GPP Interworking
• oneM2M Certification
• Data Semantics
• oneM2M Smart Device Template - in a typical vertical industry
• oneM2M in Smart Cities – Korean Smart City Initiative
• C-DOT & oneM2M activities
• Global oneM2M implementations - oneTransport/Bordeaux/KEPCO

© 2019 oneM2M 2
oneM2M Partnership Project

founded1 July, 24th 2012

Almost 200 member organizations in oneM2M
TP#1: Sep 24th-29th 2012
[1] Partnership Agreement V 2.0 (Approved March 2013)

Join forces
=> reduce fragmentation
Partner transpositions
Þ De jure Standard
Þ “collaborate on standard”
Þ focus on interoperability
Þ “compete in implementation”

=> Reuse e.g.

HGI

Release 2 transposition
www.oneM2M.org ITU-T SG20 Y.4500.x
All documents and specifications are publically available

© 2019 oneM2M 3
 oneM2M Structure
http://onem2m.org/about-onem2m/organisation-and-structure

Finance
Partners

Steering Industry Liaison

Committee Legal
Marketing
Methods/Procedures

Work Programme
Technical
Coordination Group
Plenary
Members / Partners

Methods of Work

Requirements System Design Testing and

and Domain and Security Developers
Models Ecosystem

© 2019 oneM2M 4
 oneM2M Work Process
Energy Enterprise Healthcare Public Services

Interoperability
Test Events
Residential Other Transportation Industry

REQUIREMENTS Certification Program

TS-0002

TECHNICAL REPORTS TECHNICAL SPECS

TECHNICAL REPORTS
TECHNICAL REPORTS TECHNICAL SPECS
TECHNICAL SPECS

© 2019 oneM2M 5
 oneM2M Breaks Down the Silos

Horizontal
Smart Smart Smart
Emergency
Information Flow
Transportation Infrastructure
Services Smart Smart Smart
Emergency Transportatio Infrastructure …
Services n

Information Flow
Information Flow

Information Flow

Vertical
Vertical

Vertical

… Service Layer

© 2019 oneM2M 6
 oneM2M
is an End-to-End IoT Technology

App
Flexible Deployment Options
Non-
App App App oneM2M App
Service Layer • IoT Cloud / Enterprise

• IoT Gateway

• IoT Edge Device

Service Layer
Service Layer • IoT User Devices
Communication Network(s)

© 2019 oneM2M 7
 oneM2M Architecture

Application
Layer AE AE AE
Developer API

Service
Layer CSE CSE CSE CSE
Network Interface

Network Underlying Underlying

Layer NSE Network NSE NSE Network NSE
Other
Application Service Node Middle Node Infrastructure Node Backend

Device, Sensor, Actuator Edge Device or Gateway Backend or Cloud

Application Entity (AE) Provides application logic for the end-to-end M2M solutions
Common Services Entity (CSE) Provides the set of "service functions" that are common to the M2M environments
Network Services Entity (NSE) Provides services to the CSEs besides the pure data transport
Node Logical equivalent of a physical (or possibly virtualized, especially on the server side) device

© 2019
© 2017 oneM2M
oneM2M
8
 oneM2M is Resource Oriented
Based on REST architecture style (representational state transfer)
• Access using an URI http://www.example.com/wiki/rest
• Representation format: XML, JSON, BSON, …
• Dependencies, hierarchy is represented by link in resource representation

Basic Resources
• Common Service Entity (CSE)
• Container (CNT)
• Application Entity (AE)
• Container (CNT)
• Content Instance (CIN)
• ….

onem2m.org, TS-0001 Functional Architecture Based on slides provided by Thierry Monteil at the CDOT foundation Day 2019

© 2019
© 2017 oneM2M
oneM2M
9
oneM2M functions provided to
applications
Service Layer
Common Service Layer
Group Communication
Registration Discovery Security
Management Management

Data Registration Application &

Subscription & Device Network Service
Management & Service
Notification Management Exposure
Repository Management

Service Charging Transaction

Location Semantics
& Accounting Management

© 2019
© 2017 oneM2M
oneM2M 10
 oneM2M Security Framework
Service Layer Dynamic
Authorization
Authorization • oneM2M complements existing proven
Secure Privacy
Policy
security technologies to address IoT
Communicatio
n Manager security challenges
Enrollment & End-to-End
Provisioning Security
• oneM2M provides a common set of
security capabilities to secure IoT
devices and applications and prevent/
Registration
Group
Communicatio mitigate attacks
Registration Discovery Security n
Management
Management

Data Application & Network • oneM2M exposes an abstracted set of

Subscription Device
Management
& Notification Management
Service Service security related APIs to help simplify
& Repository Management Exposure
security for IoT devices and applications
Service
Transaction
Location Charging & Semantics
Management
Accounting

© 2019 oneM2M Source: Dale Seed, oneM2M Overview 2019 11

 oneM2M Device Management
Framework
Service Layer • oneM2M provides a common set of
Device
Device
Topology Device management capabilities to manage IoT
Configuration
Management Firmware
Upgrade
devices, applications and the service
Device Software Software layer
Diagnostics Management Configuration
• Device Management
• Device Configuration (e.g. enable/ disable
capabilities, provisioning)
• Device Diagnostics and Monitoring (e.g.
Registration
Group Communication
memory, battery, event logs, reboot)
Registration Discovery Security
Management Management • Device Firmware Management
• Device Topology Management (e.g. Area
Data Application & Network
Network topology & characteristics)
Subscription Device
Management Service Service
& Repository
& Notification Management
Management Exposure
• Application & Service Layer
Management
Service • Policy Configuration
Transaction
Location Charging & Semantics • Software Management (e.g. download/ install/
Management
Accounting
activation)

© 2019 oneM2M
Source: Dale Seed, oneM2M Overview 2019 12
oneM2M Interworking Framework

Discovery, Security, Data Management,

etc.

© 2019 oneM2M
Source: oneM2M MAS Webinar 13
 oneM2M Interworking towards
Domain-specific Technologies
Gateway (oneM2M Middle Node)

oneM2M AE
oneM2M defined oneM2M Data Containers Application
E.g. OCF, IPE AE + Abstract
Application Application
OMA LwM2M Information Model oneM2M AE
oneM2M Application
oneM2M CSE Infrastructure -
CSE
oneM2M AE
Application

Gateway (oneM2M Middle Node)

Backend

KNX, Zigbee, KNX, Zigbee, oneM2M oneM2M

ETSI ITS etc App IPE AE
ETSI ITS Application Application Application

etc Network
oneM2M CSE IPE … Interworking Proxy Entity
oneM2M Release 2 & 3:
• Generic IPE (Ontology-based Interworking)
Based on a slide provided by: Dr. Josef J. Blanz . ndustry Day Bangalore, September 20th 2017
• IoT proximal Interworking TS-0033
© 2019
© 2017 oneM2M
oneM2M 14
 oneM2M Specifications & Release 4
Current Specifications
• Requirements
• Functional Architecture
• Security
• Service Layer Protocols
• Protocol Bindings
e.g. HTTP, CoAP, MQTT, WebSockets
• Base Ontology & Semantics
• Remote Management Enablement
e.g. for OMA, BBF
• Vertical Domain Support
e.g. Smart Home
• Interworking Support
e.g. LwM2M, OCF, 3GPP, OSGi
• Tests & Certifications
Release 4 - More Smart City & Vertical Domain Support
• Smart City, e.g. Ontologies for Smart City Services
• Public Warning Service Enabling
• Vehicular Domain Enabling, incl. 3GPP V2X interworking
• Industrial Domain Enabling, e.g. OPC-UA model mapping
• Railway Domain Enabling
• Interworking e.g. ZigBee, Modbus
• …
Release 4 - Feature Enhancement & Optimization
• SDT4.0 & Data Model extension, e.g. City, Railway
• Semantic Enhancement, e.g. reasoning, ontology mapping
• Security Enhancement, e.g. user/data privacy
• Edge & Fog Computing support, e.g. service provisioning, service pooling
• System Optimizations, e.g. lightweight services, platform discovery, rule
engine, users, …
• 3GPP Interworking, e.g. session QoS, V2X, charging..
• Testing & Developer Guides
© 2019
© 2017 oneM2M
oneM2M 15
oneM2M Timeline

TP42
Industry Hyderabad
Day 5 Sep 25

© 2019 oneM2M 16
 oneM2M Adoption

oneM2M has
global adoption

oneM2M Open Source

Project
oneM2M Product Offerings

oneM2M Trial Deployment

oneM2M Commercial
Deployment
© 2019 oneM2M
Source: Dale Seed, oneM2M Overview 2019 17
 oneM2M Implementation and
Deployment Base
A vibrant and
healthy
Industry-driven Open source implementations
ecosystem of
oneM2M OS-IoT
implementations IotDM
exists! Examples of Commercial implementations, Prototypes, Trials

nts
to m e
k y
Lin eplo
ofd
t
Lis

to duc ts Certification Test Houses and Test Tool Vendors

k o
Lin Pr
if ied
ert
C Regular Interop Events (6 Held from 2015-2018)
© 2019 oneM2M
Based on slides by: Dale Seed, oneM2M Overview 2019 18
 Takeaways
oneM2M - Common Service Layer
oneM2M
• Open global de-jure Standard
• Specifies a common set of horizontal IoT services
• Interworks with existing IoT technologies
• Value proposition
• Simplifies the life for IoT stakeholders
• Minimize development, deployment and maintenance
costs
• Interoperability testing and certification program
• Mature and commercially deployed technology
• Vendor independent => Essential building block for an
IoT ecosystem
© 2019 oneM2M 19
Thank you!

© 2019 oneM2M 20
Backup
• Publicly Accessible Links
• oneM2M Releases and Specifications

© 2019 oneM2M 21
oneM2M Feature Summary by Release

© 2019 oneM2M 22
Publicly Accessible Links

• Web Site • Webinars

• http://www.oneM2M.org
• Developer Guides
• http://www.onem2m.org/developer-guides
• Technical Questions
• http://www.onem2m.org/technical/technical-questions
• Published Specifications
• http://www.onem2m.org/technical/published-documents
• Documents developed in oneM2M
• http://www.onem2m.org/technical/latest-drafts
• http://www.onem2m.org/technical/webinars
• YouTube Channel
• https://www.youtube.com/c/onem2morg
• Events
• http://www.onem2m.org/news-events/events
• Certified Products
• http://www.onem2mcert.com/sub/sub04_01.php

© 2019 oneM2M 23
Publicly Accessible Links

Developer Guides
are now accessible via the public link:
http://www.onem2m.org/developer-guides

© 2019 oneM2M 24
oneM2M Releases and Specifications
 TS 0001: Functional Architecture
 TS 0002: Requirements
 TS 0003: Security Solutions
Se

Release 1
 TS 0004: Service Layer Core Protocol
 TS 0005: Management Enablement (OMA) on e a
 TS 0006: Management Enablement (BBF) htt e
p:/ M
ll p
 TS 0007: Service Components /w 2
ww M
ub
 TS 0009: HTTP Protocol Binding .on a
lis
em nd he
 TS 0010: MQTT Protocol Binding
dd
.or its
2m
Release 2

 TS 0011: Common Terminology

g/t P oc
 TS 0012: oneM2M Base Ontology ec a
hn rt
um
 TS 0014: LWM2M Interworking ica ne en
 TS 0015: Testing Framework l/p
ub r T ts b
lis yp
y
Release 2A

 TS 0020: WebSocket Protocol Binding

d- e
he
 TS 0021: oneM2M and AllJoyn Interworking do 1
m :
 TS 0023: Home Appliances Information Model and Mapping cu
 TS 0024: OIC Interworking
en
ts
 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 For details see also
 TR 0024: 3GPP Release 13 Interworking
 TS-0032 – MAF and MEF Interface Specification
[1] ADM-0008-Release 1 Control Document
 TR-0025 Application developer guide [2] ADM-0011-Release 2 Control Document
 TR-0034 CoAP binding and long polling for temp. monit. [3] ADM-0012-Release 2A Control Document
 TR-0035 Device management use case
 TR-0037 Smart farm example using MQTT binding
 TR-0039 Developer guide-SDT-based implementation
 TR-0045 Implementing semantics

© 2019 oneM2M
 oneM2M Release 3 Deliverables
ADM-0017 Release 3 Control Document

TS 0001 - Functional Architecture, V 3.13.2 TS-0016 – Secure Environment Abstraction V 3.0.2

TS 0002 - Requirements, V 3.1.2 TS-0020 – WebSocket Protocol Binding, V 3.0.1
TS 0003 - Security Solutions, V 3.10.2 TS-0022 – Field Device Configuration-V 3.0.1
TS 0004 - Service Layer Core Protocol, V 3.11.0 TS-0023 – Home Appliances Information Model and Mapping, V
3.7.3
TS 0005 – Management enablement (OMA), V 3.4.2
TS-0024 – OCF Interworking, V 3.2.2
TS 0006 – Management enablement (BBF), V 3.6.2
Technical TS-0026 – 3GPP Interworking V3.0.0
Specifications TS 0008 – CoAP Protocol Binding, V 3.3.1
TS-0030 – Ontology Based Interworking V 3.0.3
TS 0009 – HTTP Protocol Binding, V3.2.0
TS-0031 – Feature Catalogue V 3.0.0
TS 0010 – MQTT Protocol Binding, V 3.0.2
TS-0032 – MAF and MEF Interface Specification V 3.0.1
TS 0011 – Common Terminology, V 3.0.2
TS-0033 – Interworking Framework V 3.0.0
TS-0012 – Base Ontology, V 3.7.3
TS-0034 – Semantics Support V 3.0.0
TS-0014 – LWM2M Interworking, V 3.1.1
TS-0035 – OSGi Interworking V 3.0.0
TR-0001 Use Cases Collection, V 3.1.1
Technical TR-0026 Vehicular Domain Enablement, V 3.0.1
Reports TR-0033 Study on Enhanced Semantic Enablement V 3.0.0

© 2019 oneM2M
 31 active Work Items*
Release 4 candidates marked in blue
TP WIs
WI-0049 - Rel-1,2 & 3 Maintenance
WI-0079 - Rel-4 Small Technical Enhancements
RDM WG
WI-0015 - oneM2M Use Case Continuation
WI-0046 – Vehicular domain enablement
WI-0070 - Disaster Alert Service Enabler
WI-0075 – Ind. Dom. Inf. Model Mapg. & Sem. Spt.
WI-0081 - Smart Device Template 4.0
WI-0084 – SDT based Information Model and
Mapping for Vert. Ind.
WI-0092 - Railway Domain Enablement
WI-0094- Ontologies for Smart City Services (OSCS)
SDS WG TDE WG
WI-0053 - Enhancements on Semantic Support WI-0054 - Developers guide series
WI-0058 – Interworking with 3GPP networks WI-0060 - Interoperability testing Release 2
WI-0064 - Adaptation of oneM2M for Smart City WI-0078 - oneM2M API guide
WI-0069 – Heterogen. identificat. service in WI-0085 - Conformance Test Specifications
oneM2M syst. Release 3
WI-0071 - oneM2M and W3C Web of Things Iwk WI-0086 - Conformance Test Specifications
WI-0072 – Modbus interworking Release 4
WI-0076 - Lightweight oneM2M Services
WI-0077 - Attribute Based Access Control Policy
WI-0080 - Edge and Fog Computing
WI-0082 - 3GPP V2X Interworking
WI-0083 - oneM2M Service Subscribers and Users
WI-0088 - M2M/IoT Application and Component
Configuration
WI-0089 - Getting started with oneM2M
WI-0090 - oneM2M and Zigbee interworking
WI-0091 - oneM2M Services and Platforms
Discovery
WI-0093 - Action Triggering Enhancements
© 2019 oneM2M * status in ADM-0001-Work Program Management v42.0.0.27