Hybrid & multi-cloud infrastructure

Lightweight M2M (LWM2M)

Definition of Lightweight M2M (LWM2M)

OMA LightweightM2M (LwM2M) is a protocol standard that allows IoT devices to securely connect to one or more LwM2M servers. IoT devices and servers exchange application data such as temperature, perform software & firmware updates, monitor connectivity, etc. LwM2M is an application layer protocol and defines payload format and a related metadata file format.

In the LwM2M specification, an IoT device exposes a number of objects. These objects can be accessed by the server using create, read, update, delete, execute and discover operations. Additionally the IoT device can send “notifications” to the server, assuming the server registered itself with an “observe” operation.

The LwM2M payload can be formatted as TLV, JSON, opaque or Plain Text format. LwM2M Version 1.1 added additional formats CoRE Link, CBOR, SenML JSON, and SenML CBOR. A LwM2M server must support all formats. A LwM2M client must support a standard-defined subset.

An object, its internal resource structure and associated metadata (identifiers, names, cardinality, access) are defined in an XML file. This XML file follows an LwM2M defined XML schema.

The LwM2M specification comes with predefined objects which cover mainly device management. Objects from other standard organizations like IPSO or from companies are available at the OMA LwM2M Registry. Refer to the following diagram for an illustration of the retrieval of the Device Object resource values. The used identifiers are defined in the LwM2M Device Object.

LWM2M Overview

LwM2M runs on top of the CoAP protocol, a lightweight HTTP alternative. CoAP itself typically runs on DTLS/UDP. Additional protocols have been introduced in LwM2M 1.1. Transport Bindings, including TLS/TCP and usage over mobile network protocols like narrow band IoT (see also Technology Radar on NIDD&SCEF).

LwM2M protocol stack

Optionally, OSCORE can be used to encrypt the CoAP message payload, see [8] for details.



LwM2M provides full plug-and-play capabilities and thus helps the dream of IoT come true: connect a LwM2M device to your IoT Platform and retrieve business data from it or manage the device’s software, hardware and configuration. LwM2M makes this possible because it is a full-stack standard, defining a standard payload format, standard metadata, and a central registry for metadata files. Additionally, an IoT platform can use runtime discovery to learn about the supported objects when a new device is connected. LwM2M does include domain models for device management, for example, and thus no additional software development in that area is needed when using supporting IoT platforms. For specific use cases (e.g. smart cities), more standard objects are needed to reach the same plug-and-play user experience.

The LwM2M specification has been optimized for mobile networks, which means it works also if only low bandwidth is available. This applies for e.g. narrow-band IoT and LoRaWAN. This is enabled by compact message payloads and avoidance of metadata transmission.

LwM2M comes with rich out-of-the-box functionality, including protocol functionality like CRUD operations. In protocols like MQTT, this needs to be designed in a bespoke approach.


Historically, the usage of UDP made it more difficult to scale LwM2M to a large implementation with millions of devices, however in the last years many environments (including hyperscaler and Kubernetes) have added UDP support. For example, two out of the four AWS loadbalancers support UDP.

While the LwM2M standard supports TCP since release 1.1, support of TCP in LwM2M devices is just emerging. Therefore, TCP is currently no full alternative for UDP-based LwM2M.

The LwM2M feature-rich protocol causes a complex implementation for simple sensor use cases: If a sensor just wants to send measurements to a server, LwM2M v1.0 causes more complexity than using the MQTT protocol. This applies to both the protocol complexity and the device implementation complexity. This can be mitigated using LwM2M client libraries. Also LwM2M v1.1 has introduced a new “Send” operation to make this use cases simpler on protocol level.


Markets using LwM2M

The LwM2M specification is used especially in the telecommunication market, which is not surprising as the standard was driven by many telecommunication players participating in the OMA. Additionally LwM2M also gains traction in the modem space, with vendors like u*blox Telit and Sierra Wirelss to include LwM2M clients in their modems. Note that traction in the telecommunication space is weakened by existing, well-established device management standards like TR-069.

Compared to MQTT, usage of LwM2M is less by at least one dimension:

  • Google Trends: 70 vs. 2 (Search)
  • Stackoverflow: 5000 vs. 25 (MQTT vs. LwM2M)
  • GitHub projects: 36.000 vs. 300 ( MQTT vs. LwM2M)

LwM2M Software

Server applications with end-user LwM2M support include:

Server developer libraries available include:

Client developer libraries available include:

See also OMA LwM2M Github pages for additional tooling.


Most IoT platforms do not support LwM2M as a first-class protocol (one exception being Software AG's Cumulocity IoT). Instead nearly all IoT platforms support MQTT. This makes it unrealistic that LwM2M would become the dominant IoT protocol in the future.

As LwM2M provides many unique features, it will be an important challenger in the area of IoT protocols.

Adoption of the LwM2M specification might increase with the newly released MQTT binding in LwM2M 1.2.