Slides from the OMA and oneM2M IoT Seminar on January 21, 2016 Speaker 4: Friedhelm Rodermund, IoT Consultant, Vodafone Presentation Title: “LWM2M and LPWA” Friedhelm Rodermund is an IoT consultant working with Vodafone Group R&D where his current focus is on IoT standards development and strategy. He has more than twenty years of experience within the mobile industry in various areas such as technical project management, technology innovation and evolution, strategy development, development and introduction of new services, intellectual property, and standards development. He was actively involved in the development of key standards for mobile communications and service enablers across standards development organizations such as 3GPP, ETSI, GSMA, OMA and oneM2M.

1. Friedhelm Rodermund
rodermund@vodafone.de
Vodafone Group R&D
•
LPWA
and
LWM2M
21 Jan 2016
This presentation contains only public information

2. LWM2M 1.1 scope
1. Firewall Traversal Improvements
2. Security Enhancements
3. LPWA support
4. CoAP PubSub
5. Resource Directory
6. HTTP2/QUIC
7. Object Versioning

3. LPWA (Low Power Wide Area)
provides radio connectivity for IoT-devices
• low cost
• small hardware and software footprint
• low energy consumption
• low traffic

4. LWM2M (Lightweight M2M)
provides service layer functions for IoT-devices
• low cost
• small hardware and software footprint
• low energy consumption
• low traffic

5. LPWA devices need
remote device management and service enablement
 Configuration settings to allow the device to connect to application servers
 Updating firmware, software
 Diagnostics to detect health of device, or repair in case it fails
 Configuration settings to affect the behaviour of the device applications
 Managing data from the applications
Device mgmt.
Service enabl.

6. Which DM capabilities might be in scope?
Device Management (DM) and provisioning capabilities are highly relevant to LPWA e.g. NB-IoT
devices and their applications:
DM capability NB-IoT examples
Bootstrapping the device Setting connectivity parameters, e.g.
- type of data to send over NB-IoT (IP, non-IP, SMS)
- frequency band selection ?
Managing application behaviour
and device behaviour
Setting the communications pattern, e.g.
- frequency of data readings
- frequency of communicating with server (hourly, daily …)
Setting the Power Save Mode parameters
- how often will an idle device do an periodic update?

7. Which DM capabilities might be in scope?
DM capability NB-IoT examples
Firmware update Likely in scope:
- bug fix, security updates over active life of device
Likely out of scope:
- change in system technology (Rel-13 to 5G); high risk.
Occasional ‘large file’ should be supported by NB-IoT RAN.
Server needs to take into account device constraints (memory, storage).
Likely we try to minimise the use of this.
Software component update Capabilities to update a component of the device OS.
Diagnostics A toolkit of capabilities to manage an uncommunicative or faulty device, e.g.
- restart device
Some diagnostics might be part of standard reporting, e.g. battery level.
Lock and wipe Ability to remotely disable and protect data in the device.

8. LPWA devices require a subset of LWM2M functions
depending on device type and use case
LWM2M
Boot-
strap-
ping
Device
Conf
Firmw
are
Update
Diagno
stics
Conn.
Mgmt
.
Remote
Control
Data
Report
ing
Lock &
Wipe

9. Challenges
There are new constraints and challenges for an application layer solution
running over LPWA e.g. NB-IoT:
 Data rate - for battery constrained devices, we need to adapt to work using 200 bytes per day
 Security - where is it most effective to apply this?
- e.g. customer may encrypt their data at source
- e.g. transport layer security (DTLS) could be applied UE and Application server?
 varying characteristics - power: some will be constrained by battery; others will have mains
of NB-IoT device - mobility: some may highly physically mobile (tracking device); others static
- some may change their characteristics with time, e.g. a stolen television becomes mobile…
> might lead to configuration profiles for different device classes
 integration into NB-IoT - opportunity to integrate DM components e.g. at SCEF? or PDN–GW? Or ?
architecture

10. LWM2M meets the constraints of LPWA communications, however,
further optimizations might be possible for e.g. NB-IoT. This work is
part of LWM2M 1.1.
LWM2M optimizations and enhancements

11. LWM2M meets the constraints of LPWA communications, however,
further optimizations might be possible for e.g. NB-IoT. This work is
part of LWM2M 1.1.
1) LWM2M over non-IP transport needs to be defined
2) LWM2M security concept needs to be reviewed and adapted
looking at 3GPP SA3 and IETF work (e.g. DICE)
3) LWM2M device management functionality needs to be
enhanced (e.g. switching transport modes)
LWM2M optimizations and enhancements

12. NB-IoT and LMM2M
LWM2M can be the integrated
solution for NB-IoT devices for
- device management
- extraction of application data
from device
- initiating control commands
to the application

13. GSMA NB-IoT Forum
NB-IoT Forum has been created recently to influence standardisation and foster adoption end eco-
system for NB-IoT based products and services
NB-IoT Forum is planning the
NB-IoT Open Lab to support developer community
1/ Provide access to live NB-IoT service and network, software simulation tools&work spaces
2/ Provide APIs, SDK and other resources to facilitate rapid application
3/ Engage with developers from different industries for richer idea exchanges to empower innovation
4/ Hosted worldwide, e.g. by Ericsson, Huawei, Nokia. To start Q1-2016.

14.  LWM2M offers device and asset mgmt. for LPWA
 OMA started work on further LWM2M improvements
 GSMA NB-IoT supporting eco-system building
including developer support
Summary

15. Thanks!