Skip to content


Switch branches/tags

Name already in use

A tag already exists with the provided branch name. Many Git commands accept both tag and branch names, so creating this branch may cause unexpected behavior. Are you sure you want to create this branch?

Latest commit

[ADMIN] update object 4 as approved by DMSE on Dec 09 and ratified by the BoD…

Git stats


Failed to load latest commit information.
Latest commit message
Commit time

LwM2M Registry

This public repository is dedicated to store and register new LwM2M Objects and Reusable Resources.

Registration Process

Companies that would like to register a new Object or Reusable Resource should follow these steps:

  1. Create an Issue
  2. The Maintainer will create a new branch based on the Issue
  3. Create a new Object or revise an existing one
  4. Create a Pull Request

The steps are described below. Please contact in case you encounter any problem during the submission

1. Create an Issue

  • The Submitter needs to create an Issue before registering your Objects or Reusable Resources
  • In the Issue, you must indicate what you would like to do:
    1. Create Version 1.0 of a new Object
    2. Create a new Version X.Y of an existing Object
    3. Create one or more Reusable Resources

2. New branch

  • Based on the information provided in the Issue, the Maintainer will:
    • Create a new topic or `feature branch for the submitter to apply their changes
      • Branch Name: ObjID_companyName
    • Reserve one or more Object IDs or/and Reusable Resource IDs based on the Issue

3. Create a new Object

  • For each Object to register, the Submitter requires to create a new Object file using the LwM2M Editor, Guidelines& Best Practice
  • This Object file will be used in step 4 when creating the Pull Request

Note: OMA provides an Editor tool called OMA LwM2M Editor / Validator. The editor facilitates the creation of a valid OMA LwM2M Object.

4. Create a Pull Request

  • The Submitter needs to create a Pull Request against the designated branch
  • These are the steps to follow: 4.1 Update the DDF.xml file 4.2 Create a new Object or update an existing Object file 4.3 Add the Object file to the version_history folder 4.4 Update the Common.xml file (if you are registering Reusable Resource(s))

The following section describes these steps in detail.

4.1 Update the DDF.xml file

  • If the submission contains a new Object, the DDF.xml file must be updated
  • The DDF.xml file contains all the Objects in the Registry. Therefore, each time a new Object is added, the DDF.xml file must be updated with a new Object placeholder.

Example of a placeholder in the DDF.xml file for e.g., Object ID = 0, version 1.0

        <!-- Integer, this number is allocated by the Maintainer -->
        <!-- ObjecID also called ObjID-->
        <!-- URN of the object 
             for other versions than v1.0 the URN must include the version, e.g., for v1.1 the URN is urn:oma:lwm2m:oma:0:1.1 -->
        <Name>LWM2M Security</Name>
        <!-- Name of the object -->
        <Description>Object description</Description>
        <!-- Description of the Object -->
        <Owner>Test WG</Owner>
        <!-- Name of the organization that has registered the object -->
        <!-- Type of Object: 
             0 = defined by OMA, 
             1 = defined by external Standards Development Organizations, 
             2 = private or individual -->
        <!-- Version of the object -->
        <!-- URL to the xml file describing the Object 
             latest version the filename is stored in the root as ObjID.xml
             Previous versions of the file are stored in the version_history folder as ObjID-X_Y.xml, where X.Y is the Object Version.-->
        <!-- VOID- Link that opens the Object in the Vorto environment -->
        <!-- 0 => if link to object should not be visible, 
             1 => if object should be visible (default) -->
        <!-- URL to the TS of the object, not visible, not used -->
        <!-- 0 => if link to TS should not be visible, 
             1 => if link to TS should be visible (default) -->

4.2 Update or create a new ObjID.xml file

  • In this step, if you are creating the first version of an Object, version 1.0, then you must add a fully qualified ObjID.xml file to the allocated branch, or
  • If you are revising an existing Object, e.g. version 1.1 of Object ID 0.xml, you can modify the current Object directly in the root of the allocated branch. But later, you will have to add the new revision of the Object to the history_folder; see next step.

4.3 Add a new ObjID-X_Y.xml file to the version_history folder

  • Each Object version must have a file in the version_history folder
  • The name of the file, e.g., for Object ID 0, Version 1.1, is 0-1_1.xml
    • The content of the 0-1_1.xml file is the same as the content of the file 0.xml for version 1.1
      • IPSO hosts in the version_history folder a file for each Object in the Registry; the file name indicates the ObjID and the version of the Object

4.4 Update the Common.xml file (if adding new Reusable Resources)

  • If the request is to add one or more Reusable Resources, then for each Reusable Resource a placeholder must be added to the Common.xml file.

Example of Reusable Resource placeholder

    <Item ID="4000">
      <!-- Resource ID of the reusable resource 
           The Maintainer allocates reusable Resource IDs; this is one of the reasons to raise an Issue in the first place -->
      <!-- Name of the reusable resource -->
      <!-- Allowed Operation on the reusable resource-->
      <!-- Type of the reusable resource -->
      <!-- Range/Enumeration of the reusable resource
           A range is expressed with (..),e.g., from 0 to 10, it is expressed as; `(0..10)`
      <!-- Unit of the reusable resource 
           Please note the units expressed in this element MUST comply with the units defined in the SenML Registry -->
      <!-- Name of the organization that has registered the object -->
      <Description><![CDATA[Reusable Resource Description]]></Description>
      <!-- Description of the reusable resource -->
      <!-- Link to the technical specification (word, pdf etc.) -->
      <!--    0 => if link to TS should not be visible, 1 => if link to TS should be visible (default) -->

5. Auto-validation

  • As soon as the Pull Request is created against the designated branch, the LwM2M Validator will evaluate the content of the Pull Request
  • At the end of the validation, the LwM2M Validator will insert a label in the Pull Request indicating the result of the validation: Failed Validation or Passed Validation
  • If the validation has failed, then the LwM2M Validator will insert a table with the list of errors identified during the validation
    • The Error Codes, indicate who should resolve the problem, the Submitter or the Maintainer
  • If the validation has passed, then a green label will be displayed, and the IPSO group will be able to review your submission