Standards to enable an IoT Eco System

Transcription

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

2 1 Definition & what s actually the language of things? 2 Scalability challenges Ahead 3 OneM2M in a nutshell 4 OneM2M organization 5 OneM2M more elaborated 2

3 A definition about Connected things Definitions* use in context of the following slides 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. * Source: GSMA Connected Living; Understanding Internet of Things (IoT) 3

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? 40 C what? Coolant-, Outside- or even the temperature of the Driver? 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). Today... 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 Tomorrow... 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 4

5 1 Definition & what s actually the language of things? 2 Scalability challenges Ahead 3 OneM2M in a nutshell 4 OneM2M organization 5 OneM2M more elaborated 5

6 DTAG Cloud Of Things solution Processing of decentral sensor Data A Cloud of Things B 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 Andreas Neubacher Technology Architecture & Innovation Standardization & IPR Management 6

7 YoUr Device is Close For enhanced Services and better Products Decentralized Machine's & Things Connectivity Gateway Secure hosted solution Customer system Cloud der Dinge 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 Information can be post processed automatically via API s Intefaces of your machine are able to be easyly integrated and connected with the Industrie 4.0 box. *Easy integration, in case of certified hardware und compatible protocols Andreas Neubacher Technology Architecture & Innovation Standardization & IPR Management 7

8 Challenges => From Data to information meaning of data / implementation effort Machines & things 40 C 40 C SteamTemperatur NeedleTemperatur Gateway Providing connectivity 40 C DT 40 C ST Hosted Solution What The cloud need The WEB Temperature is to be educated presentation need to 40 C? the names and be implemented for Customer need the customer linked to be educated 40 C DrugTemperatur how to use the API s 40 C NT Cloud der Dinge Customer system Senors and Machines generate Data. E.g. Temperature 40 C Gateway provides localconnecitivity to sensors and wide area connectivity to the cloud Data can be analysed, processed, stored and exposed to customer systems Data or even information can be integrated systems via defined APIs Transparent data transport (connectivity) via various technologies based on wires, fibre or even wireless Customer specific Implementation effort 8

9 Challenges Summary 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 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 9

10 1 Definition & what s actually the language of things? 2 Scalability challenges Ahead 3 OneM2M in a nutshell 4 OneM2M organization 5 OneM2M more elaborated 10

11 onem2m approach / onem2m Architecture Field Domain Customer Domain Operator Domain Hosted Solution Infrastructure Domain Customer Domain Customer system Machines & things Mca Interface CSE Mcn Mcc Service Layer Cloud der Dinge Mca IN-CSE Operator Mcn Domain NSE NSE CSE NSE Please mind:, CSE, NSE are logical elements and can be combined even within one Device Gateway Providing connectivity Connectivity Layer CSE NSE Application Entity CSE Common Service Entity NSE Network Service Entity onem2m defined Interface 11

12 onem2m functions and interactions An open Mca interface between the and CSE enables software developers based public available specifications to develop Software for (Application Entities). CSE s provide generic services to 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 ( 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

13 Opportunities due to onem2m Open globally available public specifications for the Mca interface enables independent software developers to develop Software for 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

14 Example implementations of onem2m

15 1 Definition & what s actually the language of things? 2 Scalability challenges Ahead 3 OneM2M in a nutshell 4 OneM2M organization 5 OneM2M more elaborated 15

16 onem2m a global partnership project Over 200 member organizations in onem2m 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

17 200+ members organizations Some of the 200+ active members of onem2m 17

18 1 Definition & what s actually the language of things? 2 Scalability challenges Ahead 3 OneM2M in a nutshell 4 OneM2M organization 5 OneM2M more elaborated 18

19 Technical View Application Layer Mca Mca Mca Service Layer CSE CSE CSE CSE Mcn Mcc Mcn Mcn Mcc Mcn Mcc Network Layer NSE Underlying Network NSE NSE Underlying Network NSE Device Gateway Server Other Server Entities Reference Point (Application Entity), CSE (Common Services Entity) and NSE (Network Services Entity) One or more interfaces - Mca, Mcn, Mcc and Mcc EXAMPLE REQUEST GET HTTP/1.1 Host: provider.net X-Orig: /CSE-1234/WeatherApp42 X-M2M-RI: Accept: application/vnd.onem2m-res+json EXAMPLE RESPONSE HTTP/ OK X-M2M-RI: Content-Type: application/vnd.onem2m-res+json Content-Length: 94 {"ri":" ","cnf":"application/json:0", "con":"{'timestamp': ,'value':25.32}"} 2015 onem2m 19

20 Possible Topologies Infrastructure Node IN-CSE Middle Node CSE CSE Middle Node Application Dedicated Node Application Dedicated Node Middle Node CSE 2015 onem2m Application Dedicated Node Application Service Node 20

21 Interoperable standard 2015 onem2m 21 Source:

22 Interoperable standard 2015 onem2m 22 Source:

23 Common Service Functions Functions provided by cse S 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 23

24 Rel. 1 Technical Specifications Requirements TS-0002 (WI-0001) Functional Architecture TS-0001 (WI-0002) Definitions & Acronyms TS-0011 (WI-0003) Service Layer Core Protocols TS-0004 (WI-0009) HTTP Protocol Binding TS-0009 (WI-0013) CoAP Protocol Binding TS-0008 (WI-0012) Management Enabl nt - OMA TS-0005 (WI-0010) Management Enabl nt - BBF TS-0006 (WI-0010) MQTT Protocol Binding TS-0010 (WI-0014) Security Solutions TS-0003 (WI-0007) (Now 32 Tech. Specifications under way for Rel. 2 as of Sept. 2015) 2015 onem2m 24

25 Take Away Summary Open, globally available, public, specifications, based on onem2m, enable independent software developers to develop Software for 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 25

26 Andreas Neubacher Technology Architecture & Innovation Standardization & IPR Management Rennweg 97-99, 1030 Wien Tel: Tel: Mobil: andreas.neubacher@t-mobile.at