Combining LwM2M and OneM2M

Transcription

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

2 Sierra Wireless Overview Founded in ,100 employees worldwide 2015 revenue: $608 million #1 IoT module supplier (1) Beijing Shanghai Shenzhen Bangalore Hong Kong Tokyo Seoul Taipei San Diego St Petersburg London Paris Toulouse Karlskrona Munich Nice 20+ years of innovation Belo Horizonte Melbourne Johannesburg R&D, Marketing, Operations Manufacturing Commercial offices IoT Hardware IoT Connectivity IoT Platform Embedded Solutions Connected Machines Gateways Solutions Enterprise Services (1) 35% Global M2M module market share (source: ABI Research June 2015) 2

3 Sierra Wireless and LightweightM2M OMA DM Wakaama 3

4 LightweightM2M Summary LightweightM2M is originally a Device Management technology Extended to support generic data exchange Device Manager 4

5 LightweightM2M Summary LightweightM2M is originally a Device Management technology Extended to support generic data exchange LwM2M Client Device LwM2M Server Manager 5

6 LightweightM2M Summary LightweightM2M is originally a Device Management technology Extended to support generic data exchange LwM2M Client Device LwM2M Server Manager 6

7 OneM2M Summary OneM2M is a full, but complex service layer technology 7

8 OneM2M Summary OneM2M is a full, but complex service layer technology 8

9 OneM2M Summary OneM2M is a full, but complex service layer technology IoT Device Application IoT Server Application 9

10 OneM2M Summary OneM2M is a full, but complex service layer technology IoT Device Application IoT Server Application Underlying Network 10

11 OneM2M Summary OneM2M is a full, but complex service layer technology IoT Device Application IoT Server Application Underlying Network 11

12 OneM2M Summary OneM2M is a full, but complex service layer technology IoT Device Application IoT Server Application Underlying Network 12

13 OneM2M Summary OneM2M is a full, but complex service layer technology IoT Device Application IoT Server Application Underlying Network 13

14 Developer s Perspective What do you develop? 1. Enabling Technology Protocol stack (client / server) Object/Data Manager 2. End Applications Server Applications Device Applications 14

15 Combining LwM2M and OneM2M 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 15

16 Combining LwM2M and OneM2M 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 16

17 Reuse LightweightM2M and CoAP 17

18 Reuse LightweightM2M and CoAP LwM2M Client LwM2M over CoAP LwM2M Server 18

19 Reuse LightweightM2M and CoAP LwM2M Client onem2m over CoAP LwM2M over CoAP LwM2M Server 19

20 Use the OneM2M Interworking capabilities 20

21 Use the OneM2M Interworking capabilities onem2m CSE onem2m Mcc onem2m CSE 21

22 Use the OneM2M Interworking capabilities onem2m CSE Mcc onem2m CSE 22

23 Use the OneM2M Interworking capabilities LwM2M Server onem2m IPE - AE onem2m CSE Mcc onem2m CSE 23

24 Use the OneM2M Interworking capabilities LwM2M Server onem2m IPE - AE onem2m CSE Mcc onem2m CSE 24

25 Use OneM2M Mca as northbound interfaces 25

26 Use OneM2M Mca as northbound interfaces LwM2M Client LwM2M Server 26

27 Use OneM2M Mca as northbound interfaces Mca Mca LwM2M Client LwM2M Server 27

28 Use OneM2M Mca as northbound interfaces IoT Device Application Mca IoT Server Application Mca LwM2M Client LwM2M Server 28

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 29

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) Reference to actual object definition: Example: OBIS ID = for Active Power, in Watts 30

31 Bring in advanced security In LwM2M, security is provided by: Transport layer security (DTLS) Access control on objects determined per LwM2M Server 31

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, ) 32

33 Thank You Nicolas Damour Sierra Wireless - Senior Manager, Business and Innovation OneM2M Chairman of the WG2-Architecture OMA Member of the Board of Directors 33