Eric Yang covers everything you need to know about developing IoT endpoints, using mbed Client.

1. ©ARM 2016
Developing IoT endpoints
with mbed Client
Eric Yang / Staff Engineer / ARM
ARM mbed Connect / Shenzhen, China
December 5, 2016

2. ©ARM 20162
Agenda
 ARM mbed Client introduction
 Connecting endpoints with mbed Client
 Managing endpoints with mbed Client
 Maintaining energy efficiency
 End-to-end security with mbed Client
 Porting mbed Client to endpoints
 Summary

3. ©ARM 20163
mbed Client introduction

4. ©ARM 20164
mbed Client & mbed Connector
 mbed Client is an implementation of the LWM2M client, and the mbed
Connector implements the LWM2M server
 mbed Client communicates with mbed Connector via CoAP messages
 mbed Connector interacts with Web services and apps using a REST API

5. ©ARM 20165
mbed Client scope
 mbed Client is a portable embedded software library that links IoT
devices with mbed Device Connector, providing the infrastructure to
connect endpoints with cloud apps
 mbed Client is provided free for IoT device manufacturers
 A complete set of libraries
 High level C++ API
 Porting guidelines and examples
 Apache 2.0 license

6. ©ARM 20166
Connecting endpoints
with mbed Client

7. ©ARM 20167
mbed Device Connector: Making IoT scale
 mbed Device Connector eases development, management and scaling
of IoT
 Available at connector.mbed.com – easy transition to commercial service
providers
Build IoT Device Connect your devices
Build application
with example code

8. ©ARM 20168
Bootstrapping IoT devices
 Factory bootstrap according to OMA LWM2M standard
 Create the keys in the webpage
 Copy-and-paste them into the relevant file
 Bootstrapping of devices enables to configure a secure channel between
device and mbed Device Connector

9. ©ARM 20169
LWM2M data traffic
 Turn any device into an
endpoint to use with mbed
Device Connector
 Device initiated
 IoT devices provide sensor
readings and configuration
information, to a cloud-based
platform
 Service initiated
 Actuators receive instructions
from users routed via the cloud
infrastructure

10. ©ARM 201610
Managing endpoints
with mbed Client

11. ©ARM 201611
mbed Client interfaces for device
management
 mbed Client allows full control and monitor of endpoint and applications
 Registration and deregistration
 Register the Client and its Objects
 Device management and service enablement
 Server access to Object or Resource
 Information reporting
 Observe and get notifications of new Resource values

12. ©ARM 201612
Object and Resource model
 Object & Resources can each can have
Instances
 An Object is a collection of Resources
 A Resource is an atomic piece of
information that can be read, written or
executed
 Access control list (ACL) control access
to objects accessed by LWM2M Servers
©Sensinode 2013

13. ©ARM 201614
Maintaining energy efficiency

14. ©ARM 201615
IoT energy constraints
 Power consumption is one of the key constraints for the IoT devices
 Use battery or energy harvesting source for power which further
constraints hardware, software and the communication protocol usage
 Important to keep the device in sleep mode when not sensing or
communicating data

15. ©ARM 201617
From Web Applications to IoT Nodes
Web application
1000s of bytes
HTTP
IP
TLS / TCP
DTLS / UDP
Binary web object
CoAP
IP
100s bytes
10s of bytes
IoT backhaul
IoT node network
Proxy Router
Web object
DTLS / UDP
Binary web object
CoAP
6LoWPAN

16. ©ARM 201619
Sleeping nodes & energy efficiency
 Easy to interact with devices that are always connected
 To save energy client registers to server in Queue Mode and goes offline
 Server queues operations when client is asleep
 Client uses the registration update message to inform server that it is
awake and ready to receive messages
 Server conveys queued messages to client within a given time window

17. ©ARM 201620
End-to-end security
with mbed Client

18. ©ARM 201621
mbed Client security
 LWM2M defines a strong security solution for authentication of the end
points and data channel protection
 DTLS v1.2 security for all CoAP communication
 mbed Client uses X.509 certificates to authenticate DTLS keys
 Per Server and Object instance access control using ACL objects
 Bootstrapping for complete provisioning and key management

19. ©ARM 201622
mbed TLS for mbed Client
 mbed TLS makes it easy for developers to include cryptographic and
TLS/DTLS capabilities in their embedded products, with a minimal code
footprint
 mbed Client provides an API to set up entropy and RNG functions for the
underlying TLS to enhance robustness and security
 Full API documentation available
 Open Source under Apache 2.0 license at https://tls.mbed.org/
 Suitable for use on Cortex-M and Cortex-A targets

20. ©ARM 201623
Porting mbed Client
to endpoints

21. ©ARM 201624
mbed Client scalability objectives
 Enable management of all connected devices within a single
management system
 Support mbed Client porting across a wide spectrum of hardware
platforms and embedded operating systems of a very fragmented IoT
market
 Enable smooth and swift porting of mbed Client capabilities for ARM
partners

22. ©ARM 201625
Platform Abstraction Layer
mbed Client
mbed OS RTOS

23. ©ARM 201626
Platform Abstraction Layer
New release
mbed OS RTOS

24. ©ARM 201627
Platform Abstraction Layer
 Contain porting effort within
a single layer of platform
dependent interfaces, which
can be implemented by
partners
Platform
Abstraction
Layer
mbed OS RTOS

25. ©ARM 201628
mbed Client library
 PAL interfaces include:
 Threads
 Synchronization objects
 Kernel ticks, timers
 Memory-pool
 Message-queue
 IP networking
Application and service integration
Custom Embedded Platform
(Metal/RTOS/Linux, Networking)
mbed Services Client Librarymbed Client C++ API
Device Connector support
LWM2M
mbed TLS
PAL implementation
Custom Embedded Platform
(Metal/RTOS/Linux, Networking)
PAL implementation
Custom embedded platform
(mbed OS / RTOS / Linux)
PAL implementation
Platform Abstraction Layer
CoAP

26. ©ARM 201629
Summary

27. ©ARM 201630
mbed Client
Connect
Addressing the complexity of
reliably connecting high
volumes of diverse devices
across different networks
Management
Enabling scalability
through interoperability
across the supply chain
Productivity
Portable to any device
allowing management of all
connected devices on a
single system and fast time
to market
Efficiency
Optimized for constrained
environments and sleepy
nodes
Security
Trust through end-to-end
security, by providing
confidentiality, integrity and
authentication

28. ©ARM 201631
Useful links
 mbed Client libraries, example code, and documentation
 https://docs.mbed.com/docs/mbed-client-guide/en/latest/
 mbed Client source code
 https://github.com/ARMmbed/mbed-client/tree/master/source
 mbed Client example:
 https://github.com/ARMmbed/mbed-client-quickstart
 ARM mbed developer site:
 https://developer.mbed.org/
 OMA LWM2M object & resource registry
 http://technical.openmobilealliance.org/Technical/technical-
information/omna/lightweight-m2m-lwm2m-object-registry

29. Thank You!