Features & Limitations

Features and limitations of the 1NCE LwM2M Service integration.

1NCE LwM2M Interfaces

At the base for the LwM2M protocol stack lie the client (e.g. IoT device) and the server infrastructure. The 1NCE LwM2M Services consists of four logical components for the communication and management of connected IoT devices. In the figure, an abstract model of the LwM2M infrastructure is shown. Four logical interfaces are defined between the LwM2M server and the client.

Bootstrap Server

The 1NCE Bootstrap Service for LwM2M serves as a fully automated management entity for keys, access control, and configuration required to enroll an IoT device with the 1NCE LwM2M Service. This component is based in the background on the SIM-as-an-Identity Service to automate the LwM2M bootstring with a 1NCE SIM card or other secure identifiers.

LwM2M Server

Once a connected IoT LwM2M device completed the bootstrapping process, a device can connect and register to the 1NCE LwM2M Server. This registration lets the LWM2M server know of the connected IoT device existence and its registered capability.

Device Management

If an IoT device is registered with the 1NCE LwM2M Server, the individual device can be managed and services controlled via the Device Management User Interface or using the Device Management API. In the background, the Rules Engine is used to automate these device management processes. These interaction interfaces allow 1NCE customers to perform device management and M2M service enablement by sending operations to the client IoT device and getting corresponding responses from the LwM2M Client towards the 1NCE LwM2M integration.

LwM2M Data Reporting

The 1NCE LwM2M Service enables registered devices to report information to the LwM2M server. This reported data is handled via the Data Broker. All messages are forwarded to the AWS IoT Core and stored in the Device Management and Data Historian. These services store the received information and provides data for the visualization via the Management User Interface and regular event updates via the Management API.


  • Using 1NCE SIM connectivity, LwM2M is not bound to any specific Radio Network Type (RAT) and will work with any available communication (2G, 3G, 4G, NB-IoT, CAT-M).

  • The 1NCE LwM2M Service uses the 1NCE Device Shadow Service to store the current and past device states. Further the 1NCE Historian Service stores the LwM2M messages received from any registered and connected device. The state and message information can be retrieved using the Management User Interface or the Management API.

  • The communication with the 1NCE LwM2M server is secured via DTLS using Pre-Shared Keys (PSK). The PSK is regenerated for each device registration.

  • All Open Mobile Alliance (OMA) publicly defined LwM2M objects are supported. To see the full list, please reference the OMA lwm2m-registry.

  • LwM2M Action API allows to manage LwM2M devices remotely.


  • LwM2M clients used with the 1NCE Service need to support v1.1 at least partially.

  • All LwM2M clients are required to do the bootstrapping process in order to access the 1NCE
    LwM2M server. A direct connection to the server is not possible.

  • A LwM2M client device has to call the bootstrap server in plain CoAP (no DTLS). The bootstrap server will instruct the device to connect to the LwM2M server using DTLS or plain CoAP.

  • If the LwM2M client device loses the connection to the LwM2M server (e.g. network reregistration, time-outs, device sleep, etc.), it needs to initiate the bootstrapping once process again.

  • LwM2M Action API is asynchronous. Customer will not receive direct feedback from the device.