OMA LwM2M Workshop - Friedhelm Rodermund, OMA LwM2M in the IoT Space

37
Friedhelm Rodermund [email protected] Vodafone Group R&D OMA LwM2M in the IoT space LwM2M workshop 28th Jan 2015 Düsseldorf, Germany

Transcript of OMA LwM2M Workshop - Friedhelm Rodermund, OMA LwM2M in the IoT Space

Friedhelm Rodermund

[email protected]

Vodafone Group R&D

OMA LwM2M

in the IoT space

LwM2M workshop 28th Jan 2015

Düsseldorf, Germany

Vodafone footprint

LwM2M

LwM2M

IoT needs ...

Horizontal standard which is easily extendable

Single protocol for device and application mgmt.

Highly efficient protocol -> reduced traffic, power

consumption

Small CPU/memory footprint-> lower device costs

State-of-the-art security

Developer friendly solution

OMA Lightweight M2MThe new standard for the Internet of Things

Horizontal standard which is easily extendable

Single protocol for device and application mgmt.

Highly efficient protocol -> reduced traffic, power

consumption

Small CPU/memory footprint-> lower device costs

State-of-the-art security

Developer friendly solution

CoAP

• Constrained Application Protocol (IETF RFC7252)

• web model for IoT

• HTTP like verbs: GET, PUT, POST and DELETE CoAP

methods)

• Confirmable and non-confirmable message

• M2M functions such as subscribe model

• DTLS security

HTTP vs. CoAP

HTTP - ASCII- 55Bytes Header CoAP - Binary- 4Bytes headerHTTP/TCP flow CoAP/ UDP flow

LwM2M Architecture

LwM2M – Logical Interfaces

Bootstrapping

Registration

Management & Service Enablement

Information Reporting

LwM2M Object Model - overview

• Functionality is grouped into Objects

(examples: Firmware Object, Connectivity Mgmt.

Object, Location Object, Sensor Object)

• LWM2M client has one or more Objects

• Objects/Resources are accessed with GET,

PUT, POST, DELETE commands via simple

URIs: /{Object ID}/{Object Instance ID}/{Resource

ID}

e.g. POST /3/0/4 causes a device reboot

e.g. GET /6 retrieves the device location

• Anybody can create new objects (and registered

with OMNA) to support new use cases!

LWM2M Server

e.g. GET /1/0/1“registration

lifetime 3600s”

OMA LwM2M – Functional Overview

LWM2M

Boot-strap-ping

Device Conf

Firmware

Update

Diagnostics

Conn. Mgmt

.

RemoteControl

Data

Reporting

Lock & Wipe

OMA LwM2M - Security

Security for the LWM2M relies on the Datagram Transport Layer Security (DTLS) [RFC6347]

LwM2M 1.0 objects

Object Object ID

LWM2M Security 0

LWM2M Server 1

Access 2

Device 3

Connectivity Monitoring 4

Firmware 5

Location 6

Connectivity Statistics 7

LwM2M objects NEW (OMA Budapest, Jan 2015)

Object Object ID

Lock&Wipe 8

Software Management 9

Cellular Network Connectivity 10

APN Connection Profile 11

WLAN Connectivity 12

Bearer Selection 13

Capability Management

IP Smart Object alliance LwM2M objects

Object Object ID * Multiple Instances?

IPSO Digital Input 200 Yes

IPSO Digital Output 201 Yes

IPSO Analogue Input 202 Yes

IPSO Analogue Output 203 Yes

IPSO Generic Sensor 300 Yes

IPSO Luminosity Sensor 301 Yes

IPSO Presence Sensor 302 Yes

IPSO Temperature Sensor 303 Yes

IPSO Humidity Sensor 304 Yes

IPSO Power Measurement 305 Yes

IPSO Actuator 306 Yes

IPSO Set Point 308 Yes

IPSO French TIC Info 309 Yes

IPSO Load Control 310 Yes

IPSO Light Control 311 Yes

IPSO Power Control 312 Yes

IPSO Accelerometer 313 Yes

• MAI = OMA DM / LWM2M server

northbound interface towards

application

• joint collaboration with oneM2M and

BBF to «Define a framework and

requirements for the interaction

between the M2M Service Layer and

the Device Management Layer»

• Requirement work completed

LwM2M – Mobile Application Interface (MAI)

• LwM2M gateway work is just starting in OMA

• Gateway functionality very useful in many M2M scenarios

• Dedicated gateway object possibly plus protocol enhancements

LwM2M Gateway

LwM2M next release -> 1.1

• Kick off at next OMA meeting in June 2015 (Miami) ?

• TCP support ?

• Security alignments with new IETF work ?

• SMS security enhancements ?

• Peer – to peer support between clients ?

• Gateway support ?

• Object versioning ?

• your input is welcome!

Growing ecosystem !

• Further evolution of LWM2M standard in OMA (new objects, LWM2M 1.1)

• IPSO Alliance defining LwM2M objects for smart city/building applications

• Eclipse Foundation running LwM2M open source projects (Wakaama, Leshan)

• OMA developing a test suite for testing and certification

• OMA LwM2M Test Fest event

• Jointly with ETSI and IPSO Alliance in Nov 2013 in Las Vegas

• Jointly with ETSI March 2014 in London

• 26-29 Jan 2015 in Dusseldorf, GERMANY

• OMA developing portal and SDKs for supporting the LwM2M developer’s community

LwM2M – useful linksOMA-LwM2M : OMA-TS-LightweightM2M-V1_0, December 2013 (since Jan 2014 : 1153 downloads)

OMNA Lightweight M2M (LwM2M) Object & Resource Registry

[RFC 7252] : Constrained Application Protocol (CoAP) Shelby, Z., Hartke, K., Bormann, C., and B.

Frank,June 2014

[RFC6347] , “Datagram Transport Layer Security Version 1.2”, Rescorla, E. and N. Modadugu,January

2012.

OMA–Lightweight M2M White paper : G. Klas, F. Rodermund, Vodafone; Z. Shelby,ARM; S. Akhour, J.

Höller, Ericsson; 2014 (572 downloads)

IPSO Alliance

Eclipse Foundation

oneM2M TS-0005-Management_Enablement (OMA)-V-2014-08

OMA-M2Mi : OMA Management Interface for M2M V1.0

Thanks!

Vodafone Innovation Days Oct 2013