More Related Content Similar to OMA Lightweight M2M Tutorial (20) 2. 2
Tutorial Overview
• Why Lightweight Device Management
• OMA Lightweight M2M Standard
• Benefits
• Architecture
• Features
• Object Model
• Security
• Interfaces
©Sensinode 2013
3. 3
• Traditional Device Management is widely used in Mobile Devices
Used by Operators and Enterprises for managing mobile devices
Some M2M use today with Cellular devices, mostly proprietary
OMA DM the only standard, however fragmented by handset vendors
using proprietary mechanisms
• Lightweight Device Management provides the ideal M2M solution
OMA LWM2M standard suitable for the whole M2M market
Only fragmented, proprietary solutions on the market today
Applicable to both Cellular devices and WSN devices
Much larger accessible market, often 500x more devices
Extensible Object Model open to the whole M2M industry
Enables both Management and Application data with the same solution
Why Lightweight Device Management?
©Sensinode 2013
4. 4
• Open Mobile Alliance is well known for Device Management (DM)
• OMA Lightweight M2M (LWM2M) is a new standard from the alliance
Focused on constrained Cellular and other M2M devices
Sensinode is a member of OMA and is dedicated to LWM2M
• The standard defines
Efficient Device-Server interface based on open IETF standards
CoAP and DTLS bound to UDP or SMS
Extensible Object and Resource model for application semantics
Public registry of Objects from OMA, other SDOs or enterprises
• Timeline
Requirements & architecture was completed 3Q/2012
Technical specification was stable 2Q/2013
Standard to be published July 2013
OMA Lightweight M2M
©Sensinode 2013
5. 5
• Simple, efficient protocol, interfaces and payload formats
• Banking class security based on DTLS
With Pre-shared and Public Key modes, Provisioning and Bootstrapping
• Powerful Object and Resource model
Global registry and public lookup of all Objects
Provides application semantics that are easy to use and re-use
Standard device management Objects already defined by OMA
• Applicable to Cellular, 6LoWPAN, WiFi and ZigBee IP or any other IP
based constrained devices or networks
• Ideal time-to-market for the standard
LWM2M is commercially deployable in 2013
Can be combined with existing DM offerings
Will be supported in OneM2M and can be integrated with ETSI M2M
Benefits of OMA Lightweight M2M
©Sensinode 2013
7. 7
• Based on efficient, secure IETF standards
CoAP and DTLS with UDP and SMS bindings
• Interfaces
Bootstrapping – Pre-provisioned or Client/Server Initiated
Registration – Register the Client and its Objects
Management & Service – Server access to Object or Resource
Information Reporting – Notifications with new Resource values
• Object Model
Object defines Resources, each can have Instances
OMA, other SDOs or enterprises can define & register Objects
• Efficient Payloads
Plain text for individual resources
Binary TLV or JSON for resource batches (Object or Resource arrays)
Features
©Sensinode 2013
8. 8
• A Client has one or more Object Instances
• An Object is a collection of Resources
• A Resource is an atomic piece of information
that can be
Read, Written or Executed
• Resources can have multiple instances
• Objects and Resources are identified by a 16-
bit Integer, Instances by an 8-bit Integer
• Objects/Resources are accessed with simple
URIs:
/{Object ID}/{Object Instance}/{Resource ID}
e.g.
/3/0/1 (Device Object, Manufacturer Resource)
Object Model
©Sensinode 2013
9. 9
• The LWM2M Technical Specification defines six normative Objects
Standard Device Management Objects
©Sensinode 2013
Object Name ID Multiple Instances? Description
LWM2M Server 1 Yes This LWM2M objects provides the data related
to a LWM2M server, the initial access rights,
and security related data.
Access Control 2 Yes Access Control Object is used to check
whether the LWM2M Server has access right
for performing an operation.
Device 3 No This LWM2M Object provides a range of
device related information which can be
queried by the LWM2M Server, and a device
reboot and factory reset function.
Connectivity Monitoring 4 No This LWM2M objects enables monitoring of
parameters related to network connectivity.
Firmware 5 No This Object includes installing firmware
package, updating firmware, and performing
actions after updating firmware.
Location 6 No The GPS location of the device.
10. 10
• Example of the LWM2M Location Object, which has 6 Resources
Object Example
©Sensinode 2013
11. 11
• Defining a new Object is straightforward
• Object IDs are registered with the OMA Naming Authority (OMNA)
• Who can register an Object?
OMA working groups
3rd
party organizations
Enterprises
• How to register an Object?
Write a specification filling out the Object template tables:
Object Name, Description and if it can have Multiple Instances
The list of resources the Object defines
Resource Name, ID, Operations, Multiple Instances?,
Mandatory?, Data Type, Range, Units and Description
Fill out the Lightweight Object form on-line (starting 3Q/2013)
Defining new Objects
©Sensinode 2013
12. 12
• Lightweight M2M defines a strong, holistic security solution
• DTLS v1.2 security for all CoAP communication
• Three DTLS security modes are defined
Pre-Shared Key, Raw Public Key and Certificate mode
• Interoperable TLS Cipher suites for each mode are defined
• Per Server and Object Instance access control using Objects
• Bootstrapping for complete provisioning and key management
Pre-configured Bootstrapping (from e.g. Flash)
Smart Card Bootstrapping (from e.g. a SIM card)
Use of a Bootstrap Server for initial setup or re-configuration and keying
Client-initiated Bootstrapping
Server-initiated Bootstrapping
Security
©Sensinode 2013
13. 13
• Bootstrap Interface
Configure Servers & Keying
Pre-Configuration, Smart Card, Client
and Server Initiated Bootstrap
• Registration Interface
RFC6690 based Resource Directory
• Management Interface
Access to Object Instances and
Resources
• Reporting Interface
Subscription to Object Instances and
Resources
Asynchronous notification
Interfaces
©Sensinode 2013
