Presentation by Andreas Neubacher at IEC SEG8 meeting on 20.06.2018

1. © 2017 oneM2M
How oneM2M fits into the IoT Landscape -
enabling cross vertical domain interoperability
Andreas Neubacher, 20.06.2018
Presentation @ IEC SEG8 meeting
1

2. © 2017 oneM2M
Agenda
2
oneM2M Interworking with other domains
or proximal technologies
3
The Standards Landscape and Categorization of Standards1
How oneM2M fit’s into the IoT picture2
oneM2M technology in Action4
6/19/2018

3. © 2017 oneM2M
The Standards Landscape and
categorization of Standards
6/19/2018 3

4. © 2017 oneM2M
CoAP
RTPSWebSocket
HTTP
OS-IoTIoTDM
 Which groups actually specify technology, which are just doing marketing & promotion?
 Which technologies are used / will be used for M2M, IoT industrial IoT?
 Which technologies are overlapping or complementing each other?
Jungle of Consortia, Standards& OS-
Projects
6/19/2018 4

5. © 2017 oneM2M
Over 200 member organizations
in oneM2M
oneM2M: A Global Partnership Project
A standard to create ecosystem, similar to 3GPP specifying 2G, 3G, LTE
The 8 regional Standards Developent
organizations SDO‘s, are transposing
oneM2M technical specifications into
normative Standards. Those standards
are then references by regional legal
and regulatory bodies
56/19/2018

6. © 2017 oneM2M
200+ Members in oneM2M
66/19/2018
Some of the 200+ active members of oneM2M

7. © 2017 oneM2M
 Highly isolated and resilient local networks
 Multiple Firewalls, very often no direct
connection to internet
 A lot of protocols specific to industry automation
 Optimized for real time control
 Heterogeneous
 Vendor specific
Factory domain Carrier Domain
INDUSTRY AUTOMATION AND ICT*
complementary areas will merge and blur
7
 Global standards
 IP-based communication
 Cloud-based production of network-related or
service-related functions
 “Softwarization” of networks
 Network Function
Virtualization (NFV)
 Software Defined
Networks (SDN)
*) ICT = Information and Communication Technology
I 4.0
Different families of standards are relevant; different communities need to harmonize their solutions
Industrie 4.0. standards should be global; fragmented and regional standards need to be consolidated
Main challenge: Domain specific innovation in the light of commonly understood requirements
6/19/2018

8. © 2017 oneM2M
Observation 1: mix proximal & distal networks
8
Source: „How oneM2M fits into the landscape of IoT technologies” Industry Day Bangalore, September 20th 2017 Dr. Josef J. Blanz
6/19/2018

9. © 2017 oneM2M 9
C
Horozontal relevant Standards
Vertical relevant Standards
Cloud
productsInfrastructure / Data Center
Home Domain Autmotive Domain Industrial Domain
Observation 2: proximal & distal standards
6/19/2018

10. © 2017 oneM2M
Observation 3: different standards for
different applications / Layers
• Plain Connectivity Layer standards (connectivity only, i.e. IP@ / IP data transport)
• Example:
• WLAN IEEE 802.11, PAN IEEE 802.15., LAN IEEE 802.3, Cellular technologies 2G, 3G, LTE
• Characteristics:
• Bandwitdh, Latency, Pathloss/Range, QoS support
• Service:
• IP@, connectivity, may be security features, Authentication and Authorization, global availability (roaming)
• Hybrid connectivity standards (offering data transport plus other services)
• Example:
• Zigbee, Bluetooth (connectivity based on IEEE802.15.x), OCF (connectivity base on IEEE 802.11), Z-Wave etc.
• Characteristics:
• Specific services enabling Applications on top of the Technology, mainly in context of the connectivity/range
• Services:
• Different services e.g. like Bluetooth Profiles “OPP (Object Push-), HFP (Hands Free-) Profile, or specific data models for Home Domain
and mesh functionality as built in Z-Wave
6/19/2018 10

11. © 2017 oneM2M
• Data/Service Layer standards (data interoperability)
• Example:
• oneM2M, OPC-UA
• Characteristics:
• Services, independent of underlying connectivity technology
• Service:
• E.g. security features, data models, discovery functions, device management, registration services,
subscriptions and notifications etc…
6/19/2018 11
Observation 3: different standards for
different applications / Layers

12. © 2017 oneM2M
P-
IoT Applications
Service Layer
aka Service Platform
Middleware
Enablement Platform
HTTP WebSocketCoAP RTPS
DTLS /
UDP
TLS /
TCP
Protocols
IP
IEEE
802.1TSN
Wired
Access
I
IndustrialIoT
Physical
Link
Network
Transport
Presentation
Application
Session
Technologies and standards in the
communication Stack for IoT
Source: „How oneM2M fits into the landscape of IoT technologies” Industry Day Bangalore, September 20th 2017 Dr. Josef J. Blanz
6/19/2018 12

13. © 2017 oneM2M
Interoperability of Data, Example:
„I4.0 Verwaltungsschale“ / Asset Administration Shell (AAS)
6/19/2018 13
*) Source: I4.0, DISKUSSIONSPAPIER, I4.0-Sprache, „Vokabular, Nachrichtenstruktur und semantische Interaktionsprotokolle der I4.0-Sprache“
https://www.plattform-i40.de/I40/Redaktion/DE/Downloads/Publikation/hm-2018-sprache.pdf?__blob=publicationFile&v=5
*)

14. © 2017 oneM2M
Take Aways
6/19/2018 14
1. Technology categorization based on “Distance”
i. proximal networks are providing connectivity within the shop floor, within a “enterprise”-,
building, or a plant
• proximal networks are usually operated by the plant or the enterprises itself
• proximal networks are usually decoupled/protected from wide area networks by firewalls etc..
• Required (high) latencies, may be possibly only delivered within the proximal networks over
local distances
• proximal networks are able to provide the components attached to proximal networks may
have different live cycles compared to distal networks
ii. distal networks are providing connectivity between manufacturing sites and between (e.g.
Logistic) partners in the value chain over (global) wide area networks
• distal networks are usually operated by various partners (global connectivity)
• distal networks usually require, Authentication, Authorization and Accounting to gain access to
the network at all
• distal networks are constrained in latency by physics, i.e. speed of light. (~1ms delay
corresponds to ~300km in vacuum/air)

15. © 2017 oneM2M
Take Aways
6/19/2018 15
2. Technology categorization based the protocol Layer support
i. Plain Connectivity Layer standards (connectivity only, i.e. IP@ / IP data transport)
ii. Hybrid connectivity standards (offering data transport plus other services)
iii. Data/Service Layer standards (data interoperability)
3. Interoperability of Data, are key enabler for cross vertical domain interoperability and uses cases
i. Data need to be able to be interpreted by various instances/stakeholders
ii. Data model’s need to be defined
iii. Interworking, towards legacy or vertical technologies with their own Data model’s possible

16. © 2017 oneM2M
How oneM2M fit’s into the IoT
picture
6/19/2018 16

17. © 2017 oneM2M
IP Communication
Connectivity Layer
17
Main Components of an IoT Solution
Device / Cloud Infrastructure
IoT Application
Common Service
Layer “IoT OS”
Cloud
products„many“ IoT Devices
IoT Infrastructure
(Service Platform)
6/19/2018

18. © 2017 oneM2M
Connectivity Layer
Individual Standards
in IoT Communication
18
IoT Application
IoT Device IoT Infrastructure
(Service Platform)
Common Service
Layer “IoT OS”
Cloud
products
6/19/2018

19. © 2017 oneM2M
Connectivity
 Applications access the Connectivity
Layer and built-in sensors, via API’s
provided by the Operating System
 Operating System collects connectivity
requests from applications, buffers
messages, optimizes & controls device’s
network use
 Connectivity Layer provides the device
access to the Internet via the 3GPP
mobile network WiFi etc..
Learn form the Success of smart Phones
offer a framework for developers!
19
Operating System
Applications
*) API: Application Programmers Interface
API
Take Away:
Apply the concept of an Operating System “OS” to IoT Devices
Governance:
6/19/2018

20. © 2017 oneM2M
Common IoT Key problems solved by
oneM2M
20
• oneM2M stores data in case of lack of connectivity
• oneM2M can controls the devices usage of connectivity (When, how often
communication happens)
Connectivity
• oneM2M provides globally standardized interfaces for the Application
developers (device and cloud)
• oneM2M enables Application portability
Application
area
• oneM2M provides services towards the Application (Application –Registration & -Discovery,
Subscription & Notifications Services, Secure Communication, Device Management etc…
• oneM2M enables Device portability (a Device can be connected to any
Infrastructure solution)
Data
Interoperability
6/19/2018

21. © 2017 oneM2M
Interfaces in scope of developers
21*) API REST Communication
IoT Application
Common Service
Layer / IoT OS
IP Communication
Mca Communication *
Connectivity Layer
Mca Communication *
Mcc Communication
Cloud
productsIoT Device
IoT Infrastructure
(Service Platform)
6/19/2018

22. © 2017 oneM2M
Connectivity Layer
Functions provided by an Common
Service layer
22
IoT Application
Common Service
Layer “IoT OS”
IP Communication
Functions Provided
by the oneM2M
Common Service Layer
Legend:
Registration
Group
Management
SecurityDiscovery
Data
Management
& Repository
Application &
Service
Management
Device
Management
Subscription
& Notification
Communicati
on
Management
Service
Charging &
Accounting
Location
Network
Service
Exposure
Standardized Functions, exposed to applications
IoT Device
IoT Infrastructure
(Service Platform)
6/19/2018

23. © 2017 oneM2M
Possibilities to attach devices
via oneM2M Technology to an Infrastructure
23
• Infrastructure Node (IN): contains one
Common Services Entity and contains zero or
more Application Entities
• Middle Node (MN): contains one
Common Services Entity and contains zero
or more Application Entities. NOTE: There may
be zero or more Middle Nodes in the Field
Domain of the oneM2M System.
Application Dedicated Node: contains at
least one Application Entity and does not
contain a Common Services Entity
NOTE: There may be zero or more
ADNs in the Field Domain of the
oneM2M System.
EXAMPLE: Physical
mapping: an Application Dedicated
Node could reside in a constrained
M2M Device.
Application
Dedicated
Node
Application
Dedicated
Node
Application
Dedicated
Node
Middle NodeMiddle Node
Middle Node
Infrastructure Node
AE AE
AE
AE AE
IN-CSE
CSE
CSE
AE
CSE
AE
Source*): oneM2M-TS-0001-V3.11.0 Functional Architecture
Application
Dedicated
Node
AE
6/19/2018

24. © 2017 oneM2M
oneM2MInterworking with
other domains / proximal
technologies
6/19/2018 24

25. © 2017 oneM2M
oneM2M Interworking towards domains
25
Gateway (oneM2M MN)
6/19/2018
E.g. OPC- UA
Technology
based
oneM2M IN-
CSE
oneM2M AE
oneM2M AE
oneM2M AE
oneM2M CSE
oneM2M
AE
Gateway (oneM2M MN)
Based on a slide provided by: Dr. Josef J. Blanz „How oneM2M fits into the landscape of IoT technologies” Industry Day Bangalore, September 20th 2017
Industrial
Domain
enablement IPE
KNX, Zigbee
or XYZ
Network
KNX / Zigbee /
XYZ App
oneM2M
CSE
oneM2M AE

26. © 2017 oneM2M
Interworking towards non oneM2M
domains
• Interworking towards other technologies/domains is based Interworking Proxy Application Entities
(IPE’s).
• IPE’S are specialized Applications that facilitate interworking between non oneM2M Nodes and
the oneM2M System. An IPE maps data of the non oneM2M Nodes into oneM2M resources
• Towards major market relevant technologies/verticals, oneM2M defines/standardizes interworking,
e.g. covered in oneM2M documents:
• TR-0018 Industrial Domain Enablement
• TR-0049 Industrial Domain Information Model Mapping & Semantics Support
• TS-0023 Home Appliances Information Model and Mapping
• For generic interworking and guidance can be found in:
• TS-0030 Ontology based Interworking
6/19/2018 26

27. © 2017 oneM2M
Take Aways
6/19/2018 27
1. oneM2M is a standard to provide multivendor interoperability and solves common problems in
the IoT area
2. oneM2M does an abstraction of the underlying connectivity layer technologies, towards the
Application on the Device and at the Infrastructure Domain (towards the actual Cloud solution)
3. oneM2M uses already existing Technologies (Protocols, Serializations etc.) and describes how
they are going to be used between the oneM2M entities
4. oneM2M provides globally specified Developer friendly API’s for Application developers
=> Mca reference points
5. oneM2M provides an multivendor interoperable open interface between the Device and
Infrastructure Domain => Mcc reference point

28. © 2017 oneM2M
Take Aways
6/19/2018 28
6. oneM2M common Service Layer provides Services towards the Applications
(@ the Device and @ the Infrastructure)
• oneM2M registers (possibly Authenticate) Applications
• oneM2M discovery services for Applications
• oneM2M provides e2e security and access control policies between Applications per design
• oneM2M stores data in case of lack of connectivity
• oneM2M provides carrier grade Device Management functionality based on LWM2M, OMA DM or
TR69 specifications
• oneM2M controls the communication layer, how, when, and the frequency connectivity is used.
(protects the connectivity network and contributes to power efficiency)
• …..
7. oneM2M provides a flexible Architecture, to be accommodated at various different device
platforms
8. oneM2M covers Data Models, Semantic and provides Interworking to other Technolgies

29. © 2017 oneM2M
Next Step:
oneM2M technology in Action
6/19/2018 29

30. © 2017 oneM2M
Dipl.-Ing. Andreas Neubacher
Technology & Innovation | Standardization & IPR Management
Rennweg 97-99, 1030 Wien
Tel: +43 1 79 585 7204
Tel: +43 1 79 585 9 7204
Mobil: +43 676 604 79 54
E-Mail: andreas.neubacher@t-mobile.at
www.t-mobile.at
Questions?
6/19/2018 30