Combining LwM2M and oneM2M

33
1 Sierra Wireless is building the Internet of Things. Combining LwM2M and OneM2M A Developer’s Perspective OMA IoT Developer Seminar, Singapore, 26 th October 2016

Transcript of Combining LwM2M and oneM2M

Page 1: Combining LwM2M and oneM2M

1

Sierra Wireless is building

the Internet of Things.

Combining LwM2M and OneM2MA Developer’s Perspective

OMA IoT Developer Seminar, Singapore, 26th October 2016

Page 2: Combining LwM2M and oneM2M

2

Sierra Wireless Overview

(1) 35% Global M2M module market share (source: ABI Research – June 2015)

IoT Hardware IoT PlatformIoT Connectivity

ConnectedMachines Enterprise

Services

Embedded Solutions

Gateways Solutions

ParisToulouse

San DiegoShenzhen

Hong

Kong

London

Munich

R&D, Marketing, Operations Manufacturing Commercial offices

Belo Horizonte

Johannesburg

Bangalore

BeijingTokyo

Taipei

Melbourne

Shanghai

KarlskronaSeoul

NiceSt

Petersburg

1,100 employees worldwide

Founded in 1993

2015 revenue: $608 million

#1 IoT module supplier (1)

20+ years of innovation

Page 3: Combining LwM2M and oneM2M

3

Sierra Wireless and LightweightM2M

Wakaama

OMA DM

Page 4: Combining LwM2M and oneM2M

4

LightweightM2M is originally a Device Management technology

Extended to support generic data exchange

LightweightM2M – Summary

Device Manager

Page 5: Combining LwM2M and oneM2M

5

LightweightM2M is originally a Device Management technology

Extended to support generic data exchange

LightweightM2M – Summary

Device Manager

LwM2M Client LwM2M Server

Page 6: Combining LwM2M and oneM2M

6

LightweightM2M is originally a Device Management technology

Extended to support generic data exchange

LightweightM2M – Summary

Device Manager

LwM2M Client LwM2M Server

Page 7: Combining LwM2M and oneM2M

7

OneM2M is a full, but complex service layer technology

OneM2M – Summary

Page 8: Combining LwM2M and oneM2M

8

OneM2M is a full, but complex service layer technology

oneM2M Common

Services Entity

OneM2M – Summary

oneM2M Common

Services Entity

oneM2M Common

Services Entity

Page 9: Combining LwM2M and oneM2M

9

OneM2M is a full, but complex service layer technology

oneM2M Common

Services Entity

OneM2M – Summary

oneM2M Common

Services Entity

oneM2M Common

Services Entity

IoT Server

Application

IoT Device

Application

Page 10: Combining LwM2M and oneM2M

10

OneM2M is a full, but complex service layer technology

oneM2M Common

Services Entity

OneM2M – Summary

oneM2M Common

Services Entity

oneM2M Common

Services Entity

IoT Server

Application

IoT Device

Application

Underlying Network

Page 11: Combining LwM2M and oneM2M

11

OneM2M is a full, but complex service layer technology

oneM2M Common

Services Entity

OneM2M – Summary

oneM2M Common

Services Entity

oneM2M Common

Services Entity

IoT Server

Application

IoT Device

Application

Underlying Network

Page 12: Combining LwM2M and oneM2M

12

OneM2M is a full, but complex service layer technology

oneM2M Common

Services Entity

OneM2M – Summary

oneM2M Common

Services Entity

oneM2M Common

Services Entity

IoT Server

Application

IoT Device

Application

Underlying Network

Page 13: Combining LwM2M and oneM2M

13

OneM2M is a full, but complex service layer technology

oneM2M Common

Services Entity

OneM2M – Summary

oneM2M Common

Services Entity

oneM2M Common

Services Entity

IoT Server

Application

IoT Device

Application

Underlying Network

Page 14: Combining LwM2M and oneM2M

14

Developer’s Perspective

1. Enabling Technology

Protocol stack (client / server)

Object/Data Manager

2. End Applications

Server Applications

Device Applications

What do you develop?

Page 15: Combining LwM2M and oneM2M

15

LightweightM2M is a good first step for IoT standards

• Enough for most applications

• Data consumer is the same as the data producer (80% of cases)

• No northbound interfaces, ok for integrated devices

Combining LwM2M and OneM2M

Page 16: Combining LwM2M and oneM2M

16

LightweightM2M is a good first step for IoT standards

• Enough for most applications

• Data consumer is the same as the data producer (80% of cases)

• No northbound interfaces, ok for integrated devices

OneM2M is a natural extension of LightweightM2M

1. Reuse LightweightM2M and CoAP as device-to-cloud enablers

2. Use the OneM2M Interworking capabilities to integrate LightweightM2M

3. Use OneM2M Mca as the application - northbound interfaces

4. Bring in full data semantics and advanced security

Combining LwM2M and OneM2M

Page 17: Combining LwM2M and oneM2M

17

Reuse LightweightM2M and CoAP

Page 18: Combining LwM2M and oneM2M

18

Reuse LightweightM2M and CoAP

LwM2M over CoAP

LwM2M Client LwM2M Server

Page 19: Combining LwM2M and oneM2M

19

Reuse LightweightM2M and CoAP

LwM2M over CoAP

oneM2M Common

Services Entity

oneM2M Common

Services EntityoneM2M over CoAP

LwM2M Client LwM2M Server

Page 20: Combining LwM2M and oneM2M

20

Use the OneM2M Interworking capabilities

Page 21: Combining LwM2M and oneM2M

21

Use the OneM2M Interworking capabilities

oneM2M CSE oneM2M CSEoneM2M Mcc

Page 22: Combining LwM2M and oneM2M

22

Use the OneM2M Interworking capabilities

oneM2M CSE oneM2M CSEMcc

Page 23: Combining LwM2M and oneM2M

23

Use the OneM2M Interworking capabilities

oneM2M CSEMcc

LwM2M Server

oneM2M IPE - AE

oneM2M CSE

Page 24: Combining LwM2M and oneM2M

24

Use the OneM2M Interworking capabilities

oneM2M CSEMcc

LwM2M Server

oneM2M IPE - AE

oneM2M CSE

Page 25: Combining LwM2M and oneM2M

25

Use OneM2M Mca as northbound interfaces

Page 26: Combining LwM2M and oneM2M

26

Use OneM2M Mca as northbound interfaces

LwM2M Client LwM2M Server

Page 27: Combining LwM2M and oneM2M

27

Use OneM2M Mca as northbound interfaces

LwM2M Client LwM2M Server

oneM2M Common

Services Entity

oneM2M Common

Services Entity

Mca Mca

Page 28: Combining LwM2M and oneM2M

28

Use OneM2M Mca as northbound interfaces

LwM2M Client LwM2M Server

oneM2M Common

Services Entity

oneM2M Common

Services Entity

IoT Server

Application

IoT Device

Application

Mca Mca

Page 29: Combining LwM2M and oneM2M

29

Bring in full data semantics

In LwM2M, data semantics is shared out-of-band through object defs.

Example: Odins single phase power meter (urn:oma:lwm2m:x:10243)

« Active Power » is the resource /10243/0/6/0, expressed in kWatts

But there is also the IPSO Object power (urn:oma:lwm2m:ext:3305)

« Active Power » there is /3305/0/5800/0, expressed in Watts

Page 30: Combining LwM2M and oneM2M

30

Bring in full data semantics

In LwM2M, data semantics is shared out-of-band through object defs.

Example: Odins single phase power meter (urn:oma:lwm2m:x:10243)

« Active Power » is the resource /10243/0/6/0, expressed in kWatts

But there is also the IPSO Object power (urn:oma:lwm2m:ext:3305)

« Active Power » there is /3305/0/5800/0, expressed in Watts

In oneM2M, each data can be « tagged » using a semantic descriptor:

• Reference to external ontology (ex: DLMS/COSEM model)

http://www.dlms.com/COSEMpdu/

• Reference to actual object definition:

Example: OBIS ID = 1.1.1.7.0.255 for Active Power, in Watts

Page 31: Combining LwM2M and oneM2M

31

Bring in advanced security

In LwM2M, security is provided by:

• Transport layer security (DTLS)

• Access control on objects determined per LwM2M Server

Page 32: Combining LwM2M and oneM2M

32

Bring in advanced security

In LwM2M, security is provided by:

• Transport layer security (DTLS)

• Access control on objects determined per LwM2M Server

In OneM2M, advanced security is available:

• Transport layer security (TLS/DTLS)

• Finer access control determined per application/entity, also using roles

• Distributed authentication and authorization model

• Application-level end-to-end encryption is supported

• More to come in release 3 (privacy profiles, …)

Page 33: Combining LwM2M and oneM2M

33

Thank You

Nicolas Damour – [email protected] Wireless - Senior Manager, Business and Innovation

OneM2M – Chairman of the WG2-Architecture

OMA – Member of the Board of Directors