Onem2m Industry Day Introduction

ONEM2M INTRODUCTION

INDUSTRY DAY SEPT 14TH 2018, SEOUL

Presenter: Omar Elloumi, oneM2M TP Chair, Nokia Bell-Labs and CTO group [email protected]

oneM2M www.oneM2M.org

• Why IoT needs interoperability? • Introduction to oneM2M • Zoom on oneM2M release 3 • Takeaway

Automotive Home Energy e-Health Applications Applications Applications Applications

Common Service Layer

Communication Devices & Hardware

Communication Technologies & Protocols

Communication Networks

Automotive Home Energy Health

Platform based integration open standards and open source are key

Source: CRYSTAL project/Philips

Consumer IoT Telemetry

Home energy mgmt Enterprise IoT Healthcare Smart Home Asset tracking Digital signage Connected Car Smart city Fleet management Building automation Autonomous driving Industrial IoT Supply chain Smart Utilities Smart manufacturing Automation

© 2018 oneM2M Why oneM2M? Why now? • M2M (and IoT) communications existed for so many years, e.g.: – SCADA systems – Satellite based truck tracking • So why oneM2M? – Specific standards exist for home automation, smart factory, energy management, etc. but much larger growth will come from a fully integrated Internet of Things – The IoT vision will not materialize if we do not solve interoperability issues, therefore drive down integration costs and ensure time to market • Why now? – Technology is ready for an outcome based economy for a large number of use cases, more than what one can think of © 2018 oneM2M 8 oneM2M Partnership Project

Over 200 member organizations in oneM2M

A software “framework”

Located between the M2M applications and communication HW/SW that provide connectivity

Provides functions that M2M applications across different industry segments commonly need (eg. data transport, security/encryption, remote software update...)

Like an “Android” for the Internet of Things But it sits both on the field devices/sensors and in servers And it is a standard – not controlled by a single private company

© 2018 oneM2M 10 oneM2M Architecture approach Pipe (vertical): Horizontal (based on common Layer) 1 Application, 1 NW, Applications share common service and network infrastructure 1 (or few) type of Device Multipoint communications Point to point communications

Application Application Application

Business ApplicationApplication Common Common Service Layer Service Layer

Things Communication Communication Communication representations Network (wireline, wireless, Network 1 Network 2 Powerline ..) (including IP semantics) Gateway S Gateway A Local NW AA S Local NW Device S A A Device A Device Device Device Things S Common Service Layer A Application

Discovery & Group Registration Security Announcement Management

Data Application & Subscription & Device Management & Service Notification Management Repository Management

Service Communication Network Service Location Charging & Management Exposure Accounting

Semantics Interworking

Industry-driven Open source implementations

OS-IoT IotDM Examples of Commercial implementations /demos

4 interop. events so far

SeungMyeong JEONG / Omar Elloumi

© 2018 oneM2M 14 Summary of Release 2/3 Features Industrial Domain Enablement Home Domain Enablement • • Time series data management Home Appliance Information Models & SDT • • Atomic Transactions Mapping to existing standards (OCF, ECHONET, GoTAPI...) • Action Triggering Smart City & Automotive Enablement • Optimized Group Operations • Service Continuity • Cross resource subscriptions Management • M2M Application & Field Domain Market Adoption Component Configuration • Developer Guides oneM2M Rel-2/3 • oneM2M Conformance Test Semantics Features • Feature Catalogues • Semantic Description/Annotation • Product Profiles • Semantic Querying • Semantic Mashups oneM2M as generic • oneM2M Base Ontology interworking framework Security • 3GPP SCEF • Dynamic Authorization • OMA LwM2M • End to End Security • DDS • Enrollment & Authentication APIs • OPC-UA • Distributed Authorization • Modbus • Decentralized Authentication • AllJoyn/OCF • Interoperable Privacy Profiles © 2018 oneM2M • OSGi 15 • Secure Environment Abstraction • W3C WoT Product profiles

• product profiles and feature catalogue – guidebook to my oneM2M product features – fills the gap btw. function specs. and test specs.

Functional which feature to Test Purposes Architecture be implemented? (TS-0018) (TS-0001) Core Protocol which feature Abstract Test (TS-0004) needs to be tested? Suite (TS-0019) prepare test cases summarized for products Features Product Profiles Catalogue referred (TS-0025) (TS-0031) guideline for glimpse of oneM2M product planning

• example scenarios and binding messages

Deliverable Title Examples of HTTP binding, TR-0025 Application developer guide XML/JSON serialization Temperature monitoring example using CoAP CoAP binding, TR-0034 binding , OMA DM, TR-0035 Developer guide of Device Management LwM2M, BBF TR-069 TR-0037 Smart Farm Example using MQTT Binding MQTT binding Developer guide - Implementing security Provisioning, Security TR-0038 example Association Establishment TR-0039 Developer guide - SDT based implementation SDT for home appliances Semantic annotation and TR-0045 Developer Guide: Implementing Semantics discovery TR-0048 Developer Guide of 3GPP Interworking (TBD)

• TTA is the 1st Certification Body & Test House – oneM2M Release 1 certification program launched on 9th Feb. 2017

certified products (Sep. 2017)

Product Webpage Vendor Product Type GWP http://www.irexnet.co.kr IREXNET End product(IN-CSE) AiSOP http://www.irexnet.co.kr IREXNET End product(IN-CSE) Insator™ https://www.samsungsds.com SAMSUNG SDS End product(IN-CSE)

HANDYPIA IoT Platform http://www.handysoft.co.kr/ HANDYSOFT, Inc. End product(IN-CSE)

IoT Healthcare Platform http://www.hconnect.co.kr/ HealthConnect Co., Ltd End product

ThingPlug https://www.thingplug.net SK Telecom Software component N-MAS http://www.ntels.com nTels End product www.onem2mcert.com IoTMakers Middleware http://iotmakers.olleh.com KT Software component

IoTMakers http://iotmakers.olleh.com KT Software component e-IoT Energy Platform https://spin.kepco.co.kr KEPCO End product

e-IoT Energy Gateway https://spin.kepco.co.kr KEPCO End product

• Distributed authorization – enforcement, decision, retrieval and information points are distributed – c.f. Hosting CSE decides and enforces authorization with accessControlPolicyID based normal authorization scheme • Secure environment (SE) abstraction – stores secure data (e.g. certificate) using SE abstract API

Policy Access Request Access Access Enforcement Resource Requester Point (PEP)

Decision Decision Request Response

Policy Policy Request Policy Attribute Request Policy Retrieval Decision Information Point Point Point (PRP) Policy Response (PDP) Attribute Response (PIP)

< distributed authorization model >

• generic interworking framework – provides guides to map non-oneM2M devices and services into “existing” oneM2M resource types in homogeneous way • data mgmt., device mgmt., event/notification, location, group, etc. – intends not to invent new wheels for each technology – does not include underlying network interworking aspects

TS-0030

TS-0024 TR-0043 TR-0018 TR-0028

Modbus

OPC

ZigBee

OSGi OCF information Wave

to be -

model for UA extended in resources the following releases resource hierarchy per generic interworking framework device & service

• Interwork-able 3GPP network functions to oneM2M – Device Triggering Recall/Replace, UE Monitoring, Background Data Transfer, Informing Potential Network Issues, Network Parameter Configuration, Node Schedule Management

UE 3GPP Domain

MTC-IWF AE SMS-SC Mcn Tsp Mcn Mca IN-CSE API MME SCEF (SCS) ASN/MN-CSE SMS Mcn

Mcn NAS (S)Gi 3GPP SGSN / GGSN / Communication IP Mca S-GW P-GW (S)Gi Unit IN-AE (AS)

oneM2M entity

Optionally present oneM2M entity Direct connection option not currently supported

Global IoT Connections - Connectivity Type CAGR • Mobile IoT connections 30

– 2016 – 317 million 25 – 2025 – 1.3 billion – CAGR = 17% 20 • LPWA connections 15 16% Short Range / – 2016 – 64 million 10

– 2025 – 3.4 billon Billons Connected of Devices – CAGR = 55.5% 5 LPWA 65% 0 Cellular 21% 2016 2017 2018 2019 2020 2021 2022 2023 2024 2025 2026 Source: IoT VALUE CHAIN REVENUE: WORLDWIDE TRENDS AND FORECASTS 2016–2025 Source: Gartner Forecasting Database (2G/3G/4G)

Cellular LPWA Options Using Licensed Spectrum Non-Cellular LPWA Options Using Unlicensed Spectrum (examples/market leaders) Cat-NB1 Cat-M1 EC-GSM-IoT LoRa® SIGFOX™ Ingenu Also known as Also known as LTE-M or Extended Coverage (Formerly On-Ramp Narrowband Internet of enhanced Machine Type GSM-IoT Wireless) Things (NB-IoT) Communications (eMTC) Deployment LTE in-band or In-Band LTE In-band GSM Europe: 868MHz Europe: 868MHz 2.4GHz guard-band. US: 915MHz US: 915MHz Re-farmed GSM Asia: 433MHz channels Standalone deployments Bandwidth 180MHz 1.4MHz 200MHz Various settings: 200kHz 1MHz 500kHz/250kHz / 150kHz/125 kHz.

Peak Downlink 10s of kbps 300Kbps 10s of kbps 50kdps - 624kbps Rate Uplink 10s of kbps 375Kbps 10s of kbps 50kdps 100bps 156kbps Urban 2-5km 3-10km 1-3km Range Rural 15km 30-50km 5-10km

Common Attributes • Small payload = Low Data volumes • Infrequent transmission = Low number of messages • Long battery life required • Low cost • Non-complex devices • High volume of device

IoT Value Chain Module Smart object SIM, sensor, Connected car, smart Network operator Service enabler System integrator IoT vertical transponder meter platform, application service applications provider 10-15% 35-40% 15-20% 15-20% 5% 5% End customer (Indicative values)

Integration and certification IP creation, vertical integration, partnerships, B2B offerings

Application Enablement Platforms drive value creation

Cloud • Optimised for constrained devices and networks – Low power and battery operated devices • non IP based – Short application payloads directly encapsulated in MAC frames between devices Network and headends (aka Network server) server – Running HTTP and TLS (with several handshakes) is not an option LPWA network • Limited downstream traffic capabilities (NB-IoT, LTE-M, – Limited time periods where the devices can LoRa, Sigfox, sat4M2M, etc.) listen to incoming network messages Non IP traffic, constrained networks

LPWA devices

C C C C S S S S P P P P 2G/3G/ LPWA LPWA LPWA LPWA 2G/3G/ NB-IoT LPWA network network LTE network network network LTE

IoT platform

Network server

oneM2M API oneM2M API oneM2M API oneM2M API

C C C C S S S S P P P P 2G/3G/ LoRaWa LoRaWa LoRaWa LoRaWa 2G/3G/ NB-IoT n n LTE n n NB-IoT LTE

IoT platform

Network server

• IoT, here to stay • Interoperability will make IoT accessible for use cases where cost was prohibitive so far • Interoperability, within and cross domain, will increase value for IoT • Interoperability and Certification are key for IoT • Traditional approaches for integration may not scale • Semantic interoperability emerging as very promising technology for IoT interoperability