IoT Seminar (Oct. 2016) Nicolas Damour - Sierra Wireless

227 views

Published on

OMA Seminar/Webinar, October 27, 2016, "How Developers Can Get the Most Out of IoT Standards and Tools" - Presentation #3 from Nicolas Damour, Senior Manager, Business and Innovation, Sierra Wireless

"Combining LightweightM2M and oneM2M for Developers"

Published in: Technology
0 Comments
2 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
227
On SlideShare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
28
Comments
0
Likes
2
Embeds 0
No embeds

No notes for slide

IoT Seminar (Oct. 2016) Nicolas Damour - Sierra Wireless

  1. 1. 1 Sierra Wireless is building the Internet of Things. Combining LwM2M and OneM2M A Developer’s Perspective OMA IoT Developer Seminar, Singapore, 26th October 2016
  2. 2. 2 Sierra Wireless Overview (1) 35% Global M2M module market share (source: ABI Research – June 2015) IoT Hardware IoT PlatformIoT Connectivity Connected Machines Enterprise Services Embedded Solutions Gateways Solutions Paris Toulouse San Diego Shenzhen Hong Kong London Munich R&D, Marketing, Operations Manufacturing Commercial offices Belo Horizonte Johannesburg Bangalore Beijing Tokyo Taipei Melbourne Shanghai Karlskrona Seoul Nice St Petersburg 1,100 employees worldwide Founded in 1993 2015 revenue: $608 million #1 IoT module supplier (1) 20+ years of innovation
  3. 3. 3 Sierra Wireless and LightweightM2M Wakaama OMA DM
  4. 4. 4 LightweightM2M is originally a Device Management technology Extended to support generic data exchange LightweightM2M – Summary Device Manager
  5. 5. 5 LightweightM2M is originally a Device Management technology Extended to support generic data exchange LightweightM2M – Summary Device Manager LwM2M Client LwM2M Server
  6. 6. 6 LightweightM2M is originally a Device Management technology Extended to support generic data exchange LightweightM2M – Summary Device Manager LwM2M Client LwM2M Server
  7. 7. 7 OneM2M is a full, but complex service layer technology OneM2M – Summary
  8. 8. 8 OneM2M is a full, but complex service layer technology oneM2M Common Services Entity OneM2M – Summary oneM2M Common Services Entity oneM2M Common Services Entity
  9. 9. 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
  10. 10. 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
  11. 11. 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
  12. 12. 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
  13. 13. 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
  14. 14. 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?
  15. 15. 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
  16. 16. 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
  17. 17. 17 Reuse LightweightM2M and CoAP
  18. 18. 18 Reuse LightweightM2M and CoAP LwM2M over CoAP LwM2M Client LwM2M Server
  19. 19. 19 Reuse LightweightM2M and CoAP LwM2M over CoAP oneM2M Common Services Entity oneM2M Common Services Entity oneM2M over CoAP LwM2M Client LwM2M Server
  20. 20. 20 Use the OneM2M Interworking capabilities
  21. 21. 21 Use the OneM2M Interworking capabilities oneM2M CSE oneM2M CSEoneM2M Mcc
  22. 22. 22 Use the OneM2M Interworking capabilities oneM2M CSE oneM2M CSEMcc
  23. 23. 23 Use the OneM2M Interworking capabilities oneM2M CSEMcc LwM2M Server oneM2M IPE - AE oneM2M CSE
  24. 24. 24 Use the OneM2M Interworking capabilities oneM2M CSEMcc LwM2M Server oneM2M IPE - AE oneM2M CSE
  25. 25. 25 Use OneM2M Mca as northbound interfaces
  26. 26. 26 Use OneM2M Mca as northbound interfaces LwM2M Client LwM2M Server
  27. 27. 27 Use OneM2M Mca as northbound interfaces LwM2M Client LwM2M Server oneM2M Common Services Entity oneM2M Common Services Entity Mca Mca
  28. 28. 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
  29. 29. 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
  30. 30. 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
  31. 31. 31 Bring in advanced security In LwM2M, security is provided by: • Transport layer security (DTLS) • Access control on objects determined per LwM2M Server
  32. 32. 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, …)
  33. 33. 33 Thank You Nicolas Damour – ndamour@sierrawireless.com Sierra Wireless - Senior Manager, Business and Innovation OneM2M – Chairman of the WG2-Architecture OMA – Member of the Board of Directors

×