Standards to enable an IoT Eco System Andreas Neubacher, Deutsche Telekom Technology Architecture & Innovation | Standardization & IPR Management

14.06.2016

Definition & what’s actually the language of things? 1

Scalability challenges Ahead

2

OneM2M in a nutshell 3

OneM2M organization 4

OneM2M more elaborated 5

2

3

IoT The Internet of Things (IoT) refers to the use of:

intelligently connected devices and systems

to leverage data gathered

by embedded sensors and actuators in machines and other physical objects.

Definitions* use in context of the following slides

* Source: GSMA Connected Living; Understanding Internet of Things (IoT)

A definition about Connected things

4

What’s actually the language of things …….

Imagine someone is calling you on your phone and is talking to you in Suaheli? Even though you are using a standardized network/transport technology for voice, like GSM, 3 or VoLTE, you are probably not

able to communicate or get any meaningful result out of this call?

Does a Audi understand if a BMW sends 40°C? Today if a parking-sensor, a meter, a fridge, a toaster, a car etc. talks to a “cloud” they are only able to understand each

other, until engineers have “educated” them the same language on both sides (Thing/Machine/Device and the cloud).

… considerable implementation effort is spent for each IoT customer, to convert data generated by Things/Machines into information being useful for an IoT-cloud service on the other side. => until you don’t know what temperature is 40°C it’s not of any information/value

oneM2M standard is providing a “common language” to enable a common technology across verticals, (home, health care, automotive, industry…) to create economy of scale and to enable a developer community to work on IoT- Applications ….. it even happens today at…

Today . . .

Tomorrow. . .

40°C what? Coolant-, Outside- or even the temperature of the Driver?

Definition & what’s actually the language of things? 1

Scalability challenges Ahead

2

OneM2M in a nutshell 3

OneM2M organization 4

OneM2M more elaborated 5

5

To make M2M and IoT easy for you:

DTAG Cloud of Things and Gateway

Easy and Fast Implementation

Full Service by DTAG

Security „Made in GerMany“

One Solution multiple possibilities

Your benefit: M2M and Iot without High

investment, with the background and

support of a strong partner

DTAG Cloud Of Things solution Processing of decentral sensor Data

A B

Cloud of Things

Andreas Neubacher Technology Architecture & Innovation | Standardization & IPR Management 6

YoUr Device is Close For enhanced Services and better Products

Compatible Gateways connected to your

Machine*

Sensor data are conveyed secure

(cyphered) and reliable

Celular netwokrs are used to transmit your data

to our cloud. Worldwide available connectivity

Connectivity Gateway Secure hosted solution

Intefaces of your machine are able to be easyly integrated and connected with the Industrie 4.0 box.

Cloud der Dinge

Decentralized Machine's & Things

Information can be post processed

automatically via API’s

Customer system

*Easy integration, in case of certified hardware und compatible protocols

Andreas Neubacher Technology Architecture & Innovation | Standardization & IPR Management 7

Cloud der Dinge

Senors and Machines generate Data.

E.g. Temperature 40°C

Gateway provides local-

connecitivity to sensors and wide area

connectivity to the cloud

Data can be analysed, processed, stored and exposed to customer

systems

Transparent data transport (connectivity) via various technologies based on wires, fibre or even wireless

Data or even information can be

integrated systems via defined APIs

40°C

40°C

40°C DrugTemperatur

SteamTemperatur

NeedleTemperatur

40°C DT

40°C ST

40°C NT

Gateway Providing

connectivity The cloud need to be educated the names and

linked

What Temperature is

40°C ? Customer need to be educated how to use the

API’s

Customer specific Implementation effort

Challenges => From Data to information meaning of data / implementation effort

Machines & things

Customer system

8

The WEB presentation need to be implemented for

the customer

Hosted Solution

9

IoT Projects are often dedicated implementation projects per customer

Data, like temperature, Voltage, Power, States like ON/OFF etc. measurements are common for many IoT projects

Converting the Data into “information”, i.e. which temperature, is being measured, creates implementation efforts

Communication always takes place at least between two communication partners, Device/Thing and Server/Cloud

=> thus implementation efforts always are on at least two entities for any new service/customer

Challenges

Summary

Making Things talk to each other, by a common standardized Service layer, allows focusing on the real differentiator => implementation of clever IoT services in the cloud

Definition & what’s actually the language of things? 1

Scalability challenges Ahead

2

OneM2M in a nutshell 3

OneM2M organization 4

OneM2M more elaborated 5

10

Operator Domain

Customer Domain

Cloud der Dinge

oneM2M approach / oneM2M Architecture

Gateway Providing

connectivity

Hosted Solution

Customer system

Machines & things

AE

AE

AE CSE

AE AE Application Entity

CSE CSE Common Service Entity

NSE NSE Network Service Entity

IN-CSE

NSE NSE

AE

Field Domain Infrastructure Domain

Mca Interface

Mcn

Mcc Mca

Mcn

Customer Domain

oneM2M defined Interface

Operator Domain

Service Layer

Connectivity Layer

AE CSE NSE Please mind: AE, CSE, NSE are logical elements and can be combined even within one Device

11

AE

oneM2M functions and interactions

An open Mca interface between the AE and CSE enables software developers based public available specifications to develop Software for AE (Application Entities).

CSE‘s provide generic services to AE‘s, in common for IoT/M2M applications, (device discovery, Authorization, registration, security functions etc)

CSE‘s do control NSE‘s. I.e. CSE‘s control how IoT applications use the connectivity (how often and when data are sent over a certain access => Connecitivity and Data Management Handling „CMDH“ functionality)

CSE in the Infrastructure domain (IN-CSEs) provide functions via the Mca interface to cloud- or customer-applications (AE’s). E.g. a cloud application may access Data collected by the CSE via Mca Interface (Data Management & Repository function). I.e. a cloud based module for predictive maintenance can access data via this function, while other data are just being able to be accessible for accounting purposes (think of maintainance of pipes and accounting of water in smart cities)

12

Opportunities due to oneM2M

Open globally available public specifications for the Mca interface enables independent software developers to develop Software for AE’s (think of APP stores for IoT)

for Devices

Cloud solutions

Implementation effort is being reduced by a common Service layer following, one unique language among devices, supported via multiple protocols (http, CoAP, MQTT).

Possibility of standardized software modules due to open Mca Interface, executed in the Cloud environment

Customer systems can be adopted by the customer itself or by independent software developers via public available Mca specifications

13

Example implementations of oneM2M

14

http://www.toyota-itc.com/news/img/20150525_release_rev4.pdf

http://h41111.www4.hp.com/solutions/iot/index.html

Definition & what’s actually the language of things? 1

Scalability challenges Ahead

2

OneM2M in a nutshell 3

OneM2M organization 4

OneM2M more elaborated 5

15

Over 200 member organizations in oneM2M

oneM2M a global partnership project

The 8 regional Standards Developent organizations SDO‘s, are converting oneM2M technical specifications into normative Standards. Those standards are then references by regional legal and regulatory bodies (European Commission etc.)

16

200+ members organizations Some of the 200+ active members of oneM2M

17

Definition & what’s actually the language of things? 1

Scalability challenges Ahead

2

OneM2M in a nutshell 3

OneM2M organization 4

OneM2M more elaborated 5

18

© 2015 oneM2M 19

Underlying Network

Underlying Network

CSE

AE

NSE

CSE

AE

NSE

CSE

AE

NSE NSE

Device Gateway Server

Application Layer

Service Layer

Network Layer

Mca

Mcn

Mca Mca

Mcn Mcn Mcn Mcc Mcc

Entities AE (Application Entity), CSE (Common Services Entity) and NSE (Network Services Entity)

Reference Point One or more interfaces - Mca, Mcn, Mcc and Mcc’

Technical View

CSE

Mcc’

Other Server

EXAMPLE REQUEST GET http://provider.net/home/temperature/la HTTP/1.1 Host: provider.net X-Orig: /CSE-1234/WeatherApp42 X-M2M-RI: 56398096 Accept: application/vnd.onem2m-res+json

EXAMPLE RESPONSE HTTP/1.1 200 OK X-M2M-RI: 56398096 Content-Type: application/vnd.onem2m-res+json Content-Length: 94 {"ri":"28375964","cnf":"application/json:0", "con":"{'timestamp':1413405177000,'value':25.32}"}

© 2015 oneM2M

Possible Topologies

Application Service

Node

Application Dedicated

Node

Application Dedicated Node

Application Dedicated Node

Middle Node Middle Node

Middle Node

Infrastructure Node

AE AE

AE

AE AE

IN-CSE

CSE

CSE

AE

CSE

AE AE

20

© 2015 oneM2M 21

Interoperable standard

Source: https://docbox.etsi.org/Workshop/2015/201512_M2MWORKSHOP/S01_SETTINGTHESCENE/SIERRAWIRELESS_DAMOUR.pdf

© 2015 oneM2M 22

Interoperable standard

Source: https://docbox.etsi.org/Workshop/2015/201512_M2MWORKSHOP/S01_SETTINGTHESCENE/SIERRAWIRELESS_DAMOUR.pdf

© 2015 oneM2M 23

Registration Group

Management Security Discovery

Data Management &

Repository

Application & Service

Management

Device Management

Subscription & Notification

Communication Management

Service Charging & Accounting

Location Network Service

Exposure

Common Service Functions Functions provided by cSe’S

© 2015 oneM2M 24

Security Solutions

TS-0003 (WI-0007)

MQTT Protocol Binding

TS-0010 (WI-0014)

Functional Architecture

TS-0001 (WI-0002)

Requirements

TS-0002 (WI-0001)

Service Layer Core Protocols

TS-0004 (WI-0009)

Definitions & Acronyms

TS-0011 (WI-0003)

Management Enablnt - BBF

TS-0006 (WI-0010)

Management Enablnt - OMA

TS-0005 (WI-0010)

CoAP Protocol Binding

TS-0008 (WI-0012)

HTTP Protocol Binding

TS-0009 (WI-0013)

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

Rel. 1 Technical Specifications

Take Away

25

Open, globally available, public, specifications, based on oneM2M, enable independent software developers to develop Software for AE’s (think of APP stores for IoT)

for Devices

Cloud solutions

Implementation effort is being reduced by a common oneM2M Service layer following, one unique language among devices

The freedom for customers selecting the device manufacturer of choice, creates an open market and the economy of scales, IoT business finally needs to cope with billions of devices

Summary

Andreas Neubacher Technology Architecture & 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