|
The motivation of LightweightM2M is to develop a fast deployable client-server specification to provide machine to machine service. LightweightM2M is principally a device management protocol, but it should be designed to be able to extend to meet the requirements of applications. LightweightM2M is not restricted to device management, it should be able transfer service / application data. LightweightM2M implements the interface between M2M device and M2M Server. It provides a choice for the M2M Service Provider to deploy a M2M system to provide service to the M2M user. The following files are included in the release package: - Enabler Release Definition
Lists all the component files in the release. - Requirements Document
The Requirements Document contains use cases and requirements for the OMA DM Lightweight M2M enabler. It describes a set of functional requirements for M2M service enablement between the LWM2M Server and the LWM2M Client and the device management from the LWM2M Server to the LWM2M Clients. - Architecture Document
The Architecture Document contains an architecture diagram, protocol endpoints description, interfaces definition and detailed descriptions for OMA DM Lightweight M2M enabler. The architecture diagram shows the client and server components in this enabler as well as the interfaces between these two components. Furthermore, it gives a short description for the functions of these interfaces. - Technical Specification
This document specifies version 1.0 of the Lightweight Machine-to-Machine (LWM2M) protocol that includes a simple resource model, operations for creation, update, deletion, and retrieval of resources, asynchronous notifications of resource changes, support for several serialization formats, UDP and SMS transport support, communication security based on the DTLS and support for use of multiple LWM2M Servers. - Access Control
The Access Control Object supports the need to determine which operation on a given Object Instance is authorized for which LWM2M Server. - Connectivity Monitoring
The Connectivity Monitoring Object enables the monitoring of parameters related to network connectivity. - Connectivity Statistics
The Connectivity Statistics Object Objects enables clients to collect statistical information and enables the LWM2M Server to retrieve this information, set the collection duration and reset the statistical parameters. - Device
The Device Object provides a range of device related information which can be queried by the LWM2M Server, and a device reboot and factory reset function. - Firmware Update
The Firmware Update Object enables management of firmware which is to be updated. This Object includes installing firmware package, updating firmware and performing actions after updating firmware. - Location
The Location Object provides information on device related information including latitude, longitude, altitude and velocity. - Security
The Security Object provides the keying material of a LWM2M Client appropriate to access a specified LWM2M Server. - Server
The Server Objects provide data related to a LWM2M Server.
There are the following Enabler Test Specifications and Validation Plans - Enabler Test Specification
This document describes in detail available test cases for LightweightM2M as specified in OMA-TS-LightweightM2M-V1_0. The test cases are split in two categories, conformance and interoperability test cases. The conformance test cases are aimed to verify the adherence to normative requirements described in the technical specifications. The interoperability test cases are aimed to verify that implementations of the specifications work satisfactory. - Enabler Validation Plan
This document details the Validation plan for the Lightweight M2M V1.0 Enabler Release. The successful accomplishment of the validation activities will be required for the Enabler to be considered for Approved status. The validation plan for the Lightweight M2M V1.0 Enabler Release specifications is based on testing expectations in the Enabler Test Requirements (ETR). While the specific test activities to be performed are described in the Enabler Test Specification (ETS) the test environment is described in this plan. This test environment details infrastructure, operational and participation requirements identified for the needed testing activities.
Documents for download
|
