0urn:oma:lwm2m:oma:0LWM2M SecurityThis LwM2M Object provides the keying material of a LwM2M Client appropriate to access a specified LwM2M Server. One Object Instance SHOULD address a LwM2M Bootstrap-Server.
These LwM2M Object Resources MUST only be changed by a LwM2M Bootstrap-Server or Bootstrap from Smartcard and MUST NOT be accessible by any other LwM2M Server.Test WG01.0version_history/0-1_0.xml1http://www.openmobilealliance.org/release/LightweightM2M/V1_0_2-20180209-A/OMA-TS-LightweightM2M-V1_0_2-20180209-A.pdf10urn:oma:lwm2m:oma:0:1.1LWM2M SecurityThis LwM2M Object provides the keying material of a LwM2M Client appropriate to access a specified LwM2M Server. One Object Instance SHOULD address a LwM2M Bootstrap-Server.
These LwM2M Object Resources MUST only be changed by a LwM2M Bootstrap-Server or Bootstrap from Smartcard and MUST NOT be accessible by any other LwM2M Server.OMA01.1version_history/0-1_1.xml1http://www.openmobilealliance.org/release/LightweightM2M/V1_1_1-20190617-A/OMA-TS-LightweightM2M_Core-V1_1_1-20190617-A.pdf10urn:oma:lwm2m:oma:0:1.2LWM2M SecurityThis LwM2M Object provides the keying material of a LwM2M Client appropriate to access a specified LwM2M Server. One Object Instance SHOULD address a LwM2M Bootstrap-Server.
These LwM2M Object Resources MUST only be changed by a LwM2M Bootstrap-Server or Bootstrap from Smartcard and MUST NOT be accessible by any other LwM2M Server.OMA01.20.xml1http://www.openmobilealliance.org/release/LightweightM2M/V1_2-20201110-A/OMA-TS-LightweightM2M_Core-V1_2-20201110-A.pdf11urn:oma:lwm2m:oma:1LwM2M ServerThis LwM2M Objects provides the data related to a LwM2M Server. A Bootstrap-Server has no such an Object Instance associated to it.OMA01.0version_history/1-1_0.xml1http://www.openmobilealliance.org/release/LightweightM2M/V1_0_2-20180209-A/OMA-TS-LightweightM2M-V1_0_2-20180209-A.pdf11urn:oma:lwm2m:oma:1:1.1LwM2M ServerThis LwM2M Objects provides the data related to a LwM2M Server. A Bootstrap-Server has no such an Object Instance associated to it.OMA01.1version_history/1-1_1.xml1http://www.openmobilealliance.org/release/LightweightM2M/V1_1_1-20190617-A/OMA-TS-LightweightM2M_Core-V1_1_1-20190617-A.pdf11urn:oma:lwm2m:oma:1:1.2LwM2M ServerThis LwM2M Objects provides the data related to a LwM2M Server. A Bootstrap-Server has no such an Object Instance associated to it.OMA01.21.xml1http://www.openmobilealliance.org/release/LightweightM2M/V1_2-20201110-A/OMA-TS-LightweightM2M_Core-V1_2-20201110-A.pdf12urn:oma:lwm2m:oma:2LwM2M Access ControlAccess Control Object is used to check whether the LwM2M Server has access right for performing an operation.OMA01.0version_history/2-1_0.xml1http://www.openmobilealliance.org/release/LightweightM2M/V1_1_1-20190617-A/OMA-TS-LightweightM2M_Core-V1_1_1-20190617-A.pdf12urn:oma:lwm2m:oma:2:1.1LwM2M Access ControlAccess Control Object is used to check whether the LwM2M Server has access right for performing an operation.OMA01.12.xml1http://www.openmobilealliance.org/release/LightweightM2M/V1_2-20201110-A/OMA-TS-LightweightM2M_Core-V1_2-20201110-A.pdf13urn:oma:lwm2m:oma:3DeviceThis 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.OMA01.0version_history/3-1_0.xml1http://www.openmobilealliance.org/release/LightweightM2M/V1_1-20180710-A/OMA-TS-LightweightM2M_Core-V1_1-20180710-A.pdf13urn:oma:lwm2m:oma:3:1.1DeviceThis 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.OMA01.1version_history/3-1_1.xml1http://www.openmobilealliance.org/release/LightweightM2M/V1_1_1-20190617-A/OMA-TS-LightweightM2M_Core-V1_1_1-20190617-A.pdf13urn:oma:lwm2m:oma:3:1.2DeviceThis 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.OMA01.23.xml1http://www.openmobilealliance.org/release/LightweightM2M/V1_2-20201110-A/OMA-TS-LightweightM2M_Core-V1_2-20201110-A.pdf14urn:oma:lwm2m:oma:4Connectivity MonitoringThis LwM2M Object enables monitoring of parameters related to network connectivity.
In this general connectivity Object, the Resources are limited to the most general cases common to most network bearers. It is recommended to read the description, which refers to relevant standard development organizations (e.g. 3GPP, IEEE).
The goal of the Connectivity Monitoring Object is to carry information reflecting the more up to date values of the current connection for monitoring purposes. Resources such as Link Quality, Radio Signal Strength, Cell ID are retrieved during connected mode at least for cellular networks.OMA01.0version_history/4-1_0.xml1http://www.openmobilealliance.org/release/LightweightM2M/V1_0_2-20180209-A/OMA-TS-LightweightM2M-V1_0_2-20180209-A.pdf14urn:oma:lwm2m:oma:4:1.1Connectivity MonitoringThis LwM2M Object enables monitoring of parameters related to network connectivity.
In this general connectivity Object, the Resources are limited to the most general cases common to most network bearers. It is recommended to read the description, which refers to relevant standard development organizations (e.g. 3GPP, IEEE).
The goal of the Connectivity Monitoring Object is to carry information reflecting the more up to date values of the current connection for monitoring purposes. Resources such as Link Quality, Radio Signal Strength, Cell ID are retrieved during connected mode at least for cellular networks.OMA01.1version_history/4-1_1.xml1http://www.openmobilealliance.org/release/LightweightM2M/V1_1-20180710-A/OMA-TS-LightweightM2M_Core-V1_1-20180710-A.pdf14urn:oma:lwm2m:oma:4:1.2Connectivity MonitoringThis LwM2M Object enables monitoring of parameters related to network connectivity.
In this general connectivity Object, the Resources are limited to the most general cases common to most network bearers. It is recommended to read the description, which refers to relevant standard development organizations (e.g. 3GPP, IEEE).
The goal of the Connectivity Monitoring Object is to carry information reflecting the more up to date values of the current connection for monitoring purposes. Resources such as Link Quality, Radio Signal Strength, Cell ID are retrieved during connected mode at least for cellular networks.OMA01.2version_history/4-1_2.xml1http://www.openmobilealliance.org/release/LightweightM2M/V1_1_1-20190617-A/OMA-TS-LightweightM2M_Core-V1_1_1-20190617-A.pdf14urn:oma:lwm2m:oma:4:1.3Connectivity MonitoringThis LwM2M Object enables monitoring of parameters related to network connectivity.
In this general connectivity Object, the Resources are limited to the most general cases common to most network bearers. It is recommended to read the description, which refers to relevant standard development organizations (e.g. 3GPP, IEEE).
The goal of the Connectivity Monitoring Object is to carry information reflecting the more up to date values of the current connection for monitoring purposes. Resources such as Link Quality, Radio Signal Strength, Cell ID are retrieved during connected mode at least for cellular networks.OMA01.34.xml1http://www.openmobilealliance.org/release/LightweightM2M/V1_2-20201110-A/OMA-TS-LightweightM2M_Core-V1_2-20201110-A.pdf15urn:oma:lwm2m:oma:5Firmware UpdateThis LwM2M Object enables management of firmware which is to be updated. This Object includes installing a firmware package, updating firmware, and performing actions after updating firmware. The firmware update MAY require to reboot the device; it will depend on a number of factors, such as the operating system architecture and the extent of the updated software.
The envisioned functionality is to allow a LwM2M Client to connect to any LwM2M Server to obtain a firmware image using the object and resource structure defined in this section experiencing communication security protection using TLS/DTLS. There are, however, other design decisions that need to be taken into account to allow a manufacturer of a device to securely install firmware on a device. Examples for such design decisions are how to manage the firmware update repository at the server side (which may include user interface considerations), the techniques to provide additional application layer security protection of the firmware image, how many versions of firmware images to store on the device, and how to execute the firmware update process considering the hardware specific details of a given IoT hardware product. These aspects are considered to be outside the scope of this version of the specification.
A LwM2M Server may also instruct a LwM2M Client to fetch a firmware image from a dedicated server (instead of pushing firmware images to the LwM2M Client). The Package URI resource is contained in the Firmware object and can be used for this purpose.
A LwM2M Client MUST support block-wise transfer [CoAP_Blockwise] if it implements the Firmware Update object.
A LwM2M Server MUST support block-wise transfer. Other protocols, such as HTTP/HTTPs, MAY also be used for downloading firmware updates (via the Package URI resource). For constrained devices it is, however, RECOMMENDED to use CoAP for firmware downloads to avoid the need for additional protocol implementations.OMA01.0version_history/5-1_0.xml1http://www.openmobilealliance.org/release/LightweightM2M/V1_1_1-20190617-A/OMA-TS-LightweightM2M_Core-V1_1_1-20190617-A.pdf15urn:oma:lwm2m:oma:5:1.1Firmware UpdateThis LwM2M Object enables management of firmware which is to be updated. This Object includes installing a firmware package, updating firmware, and performing actions after updating firmware. The firmware update MAY require to reboot the device; it will depend on a number of factors, such as the operating system architecture and the extent of the updated software.
The envisioned functionality is to allow a LwM2M Client to connect to any LwM2M Server to obtain a firmware image using the object and resource structure defined in this section experiencing communication security protection using TLS/DTLS. There are, however, other design decisions that need to be taken into account to allow a manufacturer of a device to securely install firmware on a device. Examples for such design decisions are how to manage the firmware update repository at the server side (which may include user interface considerations), the techniques to provide additional application layer security protection of the firmware image, how many versions of firmware images to store on the device, and how to execute the firmware update process considering the hardware specific details of a given IoT hardware product. These aspects are considered to be outside the scope of this version of the specification.
A LwM2M Server may also instruct a LwM2M Client to fetch a firmware image from a dedicated server (instead of pushing firmware images to the LwM2M Client). The Package URI resource is contained in the Firmware object and can be used for this purpose.
A LwM2M Client MUST support block-wise transfer [CoAP_Blockwise] if it implements the Firmware Update object.
A LwM2M Server MUST support block-wise transfer. Other protocols, such as HTTP/HTTPs, MAY also be used for downloading firmware updates (via the Package URI resource). For constrained devices it is, however, RECOMMENDED to use CoAP for firmware downloads to avoid the need for additional protocol implementations.OMA01.15.xml1http://www.openmobilealliance.org/release/LightweightM2M/V1_2-20201110-A/OMA-TS-LightweightM2M_Core-V1_2-20201110-A.pdf16urn:oma:lwm2m:oma:6LocationThis LwM2M Object provides a range of location telemetry related information which can be queried by the LwM2M Server.OMA01.06.xml1http://www.openmobilealliance.org/release/LightweightM2M/V1_1_1-20190617-A/OMA-TS-LightweightM2M_Core-V1_1_1-20190617-A.pdf17urn:oma:lwm2m:oma:7Connectivity StatisticsThis LwM2M Objects enables client to collect statistical information and enables the LwM2M Server to retrieve these information, set the collection duration and reset the statistical parameters.OMA01.07.xml1http://www.openmobilealliance.org/release/LightweightM2M/V1_1_1-20190617-A/OMA-TS-LightweightM2M_Core-V1_1_1-20190617-A.pdf18urn:oma:lwm2m:oma:8Lock and WipeThis LWM2M objects provides the resources needed to perform the lock and wipe operations.OMA01.08.xml1http://www.openmobilealliance.org/release/LWM2M_LOCKWIPE/V1_0_3-20210119-A/OMA-TS-LWM2M_LockWipe-V1_0_2-20210119-A.pdf19urn:oma:lwm2m:oma:9LWM2M Software ManagementThis LwM2M objects provides the resources needed to perform software management on the device. Each software component is managed via a dedicated Software Management Object instance.OMA01.09.xml1http://www.openmobilealliance.org/release/LWM2M_SWMGMT/V1_0_2-20210119-A/OMA-TS-LWM2M_SwMgmt-V1_0_2-20210119-A.pdf110urn:oma:lwm2m:oma:10LWM2M Cellular ConnectivityThis object specifies resources to enable a device to connect to a 3GPP or 3GPP2 bearer, including GPRS/EDGE, UMTS, LTE, NB-IoT, SMS. For cellular connectivity, this object focuses on Packet Switched (PS) connectivity and doesn't aim to provide comprehensive Circuit Switched (CS) connectivity management.OMA01.0version_history/10-1_0.xml1010urn:oma:lwm2m:oma:10:1.1LWM2M Cellular ConnectivityThis object specifies resources to enable a device to connect to a 3GPP or 3GPP2 bearer, including GPRS/EDGE, UMTS, LTE, NB-IoT, SMS. For cellular connectivity, this object focuses on Packet Switched (PS) connectivity and doesn't aim to provide comprehensive Circuit Switched (CS) connectivity management.OMA01.110.xml1011urn:oma:lwm2m:oma:11LWM2M APN Connection ProfileThis object specifies resources to enable a device to connect to an APN.OMA01.0version_history/11-1_0.xml1011urn:oma:lwm2m:oma:11:1.1LWM2M APN Connection ProfileThis object specifies resources to enable a device to connect to an APN.OMA01.111.xml1012urn:oma:lwm2m:oma:12WLAN connectivityThis object specifies resources to enable a device to connect to a WLAN bearer.OMA01.0version_history/12-1_0.xml1012urn:oma:lwm2m:oma:12:1.1WLAN connectivityThis object specifies resources to enable a device to connect to a WLAN bearer.OMA01.112.xml1013urn:oma:lwm2m:oma:13LWM2M Bearer SelectionThis object specifies resources to enable a device to choose a PLMN/network on which to attach/register and what type of bearer to then connect.
This object allows via remote bearer and network configuration to overwrite automatic network and bearer selection e.g. as supported by the UICC. An equivalent example for overwriting automatic selection is a user doing manual network and bearer selection on a smart phone.OMA01.0version_history/13-1_0.xml1013urn:oma:lwm2m:oma:13:1.1LWM2M Bearer SelectionThis object specifies resources to enable a device to choose a PLMN/network on which to attach/register and what type of bearer to then connect.
This object allows via remote bearer and network configuration to overwrite automatic network and bearer selection e.g. as supported by the UICC. An equivalent example for overwriting automatic selection is a user doing manual network and bearer selection on a smart phone.OMA01.113.xml1014urn:oma:lwm2m:oma:14LWM2M Software ComponentIf some Objects are not supported after software update, the LwM2M Client MUST delete all the Object Instances of the Objects that are not supported.OMA01.014.xml1http://www.openmobilealliance.org/release/LWM2M_SWMGMT/V1_0_2-20210119-A/OMA-TS-LWM2M_SwMgmt-V1_0_2-20210119-A.pdf115urn:oma:lwm2m:oma:15DevCapMgmtThis LWM2M Object is dedicated to manage the device capabilities of a device e.g. sensors, communication, etc.OMA01.0version_history/15-1_0.xml1http://www.openmobilealliance.org/release/LWM2M_DevCapMgmt/V1_0_3-20200616-A/OMA-TS-LWM2M_DevCapMgmt-V1_0_3-20200616-A.pdf115urn:oma:lwm2m:oma:15:2.0DevCapMgmtThis LWM2M Object is dedicated to manage the device capabilities of a device e.g. sensors, communication, etc.OMA02.015.xml1http://www.openmobilealliance.org/release/LWM2M_DevCapMgmt/V1_0_4-20201208-A/OMA-TS-LWM2M_DevCapMgmt-V1_0_4-20201208-A.pdf116urn:oma:lwm2m:oma:16PortfolioThe Portfolio Object allows to extend the data storage capability of other Object Instances in the LwM2M system, as well as the services which may be used to authenticate and to protect privacy of data contained in those extensions. In addition, a service of data encryption is also definedOMA01.016.xml1http://www.openmobilealliance.org/release/LWM2M_PortfolioObj/V1_0_1-20200616-A/OMA-TS-LWM2M_PortfolioObj-V1_0_1-20200616-A.pdf117urn:oma:lwm2m:oma:17Communications CharacteristicsThis object enables configuration of various generic communications parameters.OMA01.00018urn:oma:lwm2m:oma:18Non-Access Stratum (NAS) ConfigurationThis object provides Non-Access Stratum (NAS) configuration and is derived from 3GPP TS 24.368.OMA01.00019urn:oma:lwm2m:oma:19BinaryAppDataContainerThis LwM2M Objects provides the application service data related to a LwM2M Server, eg. Water meter data.
There are several methods to create instance to indicate the message direction based on the negotiation between Application and LwM2M. The Client and Server should negotiate the instance(s) used to exchange the data. For example:
- Using a single instance for both directions communication, from Client to Server and from Server to Client.
- Using an instance for communication from Client to Server and another one for communication from Server to Client
- Using several instancesOMA01.019.xml1http://www.openmobilealliance.org/release/LwM2M_APPDATA/V1_0_1-20190221-A/OMA-TS-LWM2M_BinaryAppDataContainer-V1_0_1-20190221-A.pdf120urn:oma:lwm2m:oma:20Event LogThe Event Log Object is a single Instance Object defined for logging data in a straightforward and generic way.
The Resources of that Object are based on the OMA LwM2M set of reusable Resources dedicated to logging event activity.OMA01.020.xml1http://www.openmobilealliance.org/release/LwM2M_EventLog/V1_0_1-20200616-A/OMA-TS-LWM2M_EventLog-V1_0_1-20200616-A.pdf121urn:oma:lwm2m:oma:21LWM2M OSCOREThis LwM2M Object provides the keying material and related information of a LwM2M Client appropriate to access a specified LwM2M Server using OSCORE. One Object Instance MAY address a LwM2M Bootstrap-Server. These LwM2M Object Resources MUST only be changed by a LwM2M Bootstrap-Server or Bootstrap from Smartcard and MUST NOT be accessible by any other LwM2M Server.
Instances of this Object are linked from Instances of Object 0 using the OSCORE Security Mode Resource of Object 0. Instances of this Object MUST NOT be linked from more than one Instance of Object 0.OMA01.0version_history/21-1_0.xml1http://www.openmobilealliance.org/release/LightweightM2M/V1_1_1-20190617-A/OMA-TS-LightweightM2M_Core-V1_1_1-20190617-A.pdf121urn:oma:lwm2m:oma:21:1.1LWM2M OSCOREThis LwM2M Object provides the keying material and related information of a LwM2M Client appropriate to access a specified LwM2M Server using OSCORE. One Object Instance MAY address a LwM2M Bootstrap-Server. These LwM2M Object Resources MUST only be changed by a LwM2M Bootstrap-Server or Bootstrap from Smartcard and MUST NOT be accessible by any other LwM2M Server.
Instances of this Object are linked from Instances of Object 0 using the OSCORE Security Mode Resource of Object 0. Instances of this Object MUST NOT be linked from more than one Instance of Object 0.OMA01.121.xml1http://www.openmobilealliance.org/release/LightweightM2M/V1_2-20201110-A/OMA-TS-LightweightM2M_Core-V1_2-20201110-A.pdf122urn:oma:lwm2m:oma:22Virtual Observe NotifyThe Virtual Observe Notify Object provides a main function to notify multiple resources to a LwM2M Server in one notification message whether the resources are in one object/object instance or across multiple objects. The Virtual Observe Notify Object also provides some functions to implement more efficient multi-resource report.OMA01.022.xml1http://www.openmobilealliance.org/release/LwM2M_VON/V1_0-20190711-A/OMA-TS-LWM2M_VirtualObserveNotify-V1_0-20190711-A.pdf123urn:oma:lwm2m:oma:23LwM2M COSEThis Object provides the keying material and related information for use with COSE.OMA01.023.xml1http://www.openmobilealliance.org/release/LightweightM2M/V1_2-20201110-A/OMA-TS-LightweightM2M_Core-V1_2-20201110-A.pdf124urn:oma:lwm2m:oma:24MQTT ServerThis object defines configuration parameters for an MQTT client to interact with a MQTT server.OMA01.024.xml1http://www.openmobilealliance.org/release/LightweightM2M/V1_2-20201110-A/OMA-TS-LightweightM2M_Core-V1_2-20201110-A.pdf125urn:oma:lwm2m:oma:25LwM2M GatewayThis object is used by a LwM2M Gateway to maintain the devices connected to the gateway.OMA01.0version_history/25-1_0.xml1http://www.openmobilealliance.org/release/LightweightM2M/V1_2-20201110-A/OMA-TS-LightweightM2M_Core-V1_2-20201110-A.pdf125urn:oma:lwm2m:oma:25:2.0LwM2M GatewayThis object is used by a LwM2M Gateway to maintain the IoT Devices connected to the LwM2M Gateway.OMA02.025.xml1http://www.openmobilealliance.org/release/LwM2M_Gateway/V1_1-20210518-A/OMA-TS-LWM2M_Gateway-V1_1-20210518-A.pdf126urn:oma:lwm2m:oma:26LwM2M Gateway RoutingThis object is used by a LwM2M Gateway to maintain the routing table.OMA01.026.xml1http://www.openmobilealliance.org/release/LightweightM2M/V1_2-20201110-A/OMA-TS-LightweightM2M_Core-V1_2-20201110-A.pdf127urn:oma:lwm2m:oma:275GNR ConnectivityThis is a device management object that should be used for 5G-NR capable devices.OMA01.027.xml1http://www.openmobilealliance.org/release/LightweightM2M/V1_2-20201110-A/OMA-TS-LightweightM2M_Core-V1_2-20201110-A.pdf128urn:oma:lwm2m:oma:28Device RF CapabilitiesThis is a device management object that should be used for capturing the RF capabilities of the device.OMA01.028.xml1http://www.openmobilealliance.org/release/LightweightM2M/V1_2-20201110-A/OMA-TS-LightweightM2M_Core-V1_2-20201110-A.pdf1500urn:oma:lwm2m:oma:500CoAP ConfigThis object is used to configure the CoAP transmission parameters (RFC7252) and other parameters that affect CoAP transmission.OMA01.0500.xml10501urn:oma:lwm2m:oma:501LTE-MTC Band ConfigThis object is used to configure the cellular band used by the device as well as to change the band. It is intended to be used on LTE bands, as in NB-IoT and LTE Cat M1 frequency bands.OMA01.0501.xml10502urn:oma:lwm2m:oma:502CO DetectorThis is an alarm that should be raised if the sensor detects a higher than threshold CO level.OMA01.0502.xml10503urn:oma:lwm2m:oma:503Fire AlarmThis is an alarm that should be raised if the sensor(s) detect fire, based on the values reported from Temperature, Humidity, Smoke (CO2).OMA01.0503.xml10504urn:oma:lwm2m:oma:504GSMA Remote SIM ProvisioningThis is a device management object that should be used for Remote SIM Provisioning according to GSMA standardsOMA01.0504.xml10505urn:oma:lwm2m:oma:505LwM2M nuSIM ProvisioningThis is a device management object that should be used for Remote SIM Provisioning from a LwM2M server.OMA01.0505.xml10506urn:oma:lwm2m:oma:506TBCTBCOMA01.0002048urn:oma:lwm2m:ext:2048CmdhPolicyThis Object provides links to a set of rules associated with a specific CSE that governs the behavior of that CSE regarding rejecting, buffering and sending request or response messages via the Mcc reference point.oneM2M11.02048.xml1http://www.onem2m.org/images/files/deliverables/TS-0005-Management_Enablement_(OMA)-V1_0_1.pdf12049urn:oma:lwm2m:ext:2049ActiveCmdhPolicyThis Object provides a link to the currently active set of CMDH policiesoneM2M11.02049.xml1http://www.onem2m.org/images/files/deliverables/TS-0005-Management_Enablement_(OMA)-V1_0_1.pdf12050urn:oma:lwm2m:ext:2050CmdhDefaultsDefines which CMDH related parameters will be used by default.oneM2M11.02050.xml1http://www.onem2m.org/images/files/deliverables/TS-0005-Management_Enablement_(OMA)-V1_0_1.pdf12051urn:oma:lwm2m:ext:2051CmdhDefEcValuesThis Object represents default set of values for the Event Category parameter of an incoming request or response message.oneM2M11.02051.xml1http://www.onem2m.org/images/files/deliverables/TS-0005-Management_Enablement_(OMA)-V1_0_1.pdf12052urn:oma:lwm2m:ext:2052CmdhEcDefParamValuesThis Object represents a specific set of default values for the CMDH related parameters Request Expiration Timestamp, Result Expiration Timestamp, Operational Execution Time, Result Persistence and Delivery Aggregation that are applicable for a given Event Category if these parameters are not specified in the message.oneM2M11.02052.xml1http://www.onem2m.org/images/files/deliverables/TS-0005-Management_Enablement_(OMA)-V1_0_1.pdf12053urn:oma:lwm2m:ext:2053CmdhLimitsThis Object represents limits for CMDH related parameter values.oneM2M11.02053.xml1http://www.onem2m.org/images/files/deliverables/TS-0005-Management_Enablement_(OMA)-V1_0_1.pdf12054urn:oma:lwm2m:ext:2054CmdhNetworkAccessRulesThis Object defines the usage of underlying networks for forwarding information to other CSEs during processing of CMDH-related requests in a CSE.oneM2M11.02054.xml1http://www.onem2m.org/images/files/deliverables/TS-0005-Management_Enablement_(OMA)-V1_0_1.pdf12055urn:oma:lwm2m:ext:2055CmdhNwAccessRuleThis Object defines limits in usage of specific underlying networks for forwarding information to other CSEs during processing of CMDH-related requests in a CSE.oneM2M11.02055.xml1http://www.onem2m.org/images/files/deliverables/TS-0005-Management_Enablement_(OMA)-V1_0_1.pdf12056urn:oma:lwm2m:ext:2056CmdhBufferThis Object defines limits in usage of buffers for temporarily storing information that needs to be forwarded to other CSEs during processing of CMDH-related requests in a CSE.oneM2M11.02056.xml1http://www.onem2m.org/images/files/deliverables/TS-0005-Management_Enablement_(OMA)-V1_0_1.pdf12057urn:oma:lwm2m:ext:2057CmdhBackOffParametersSetThis Object defines set of parameters which can be referenced by a specific Instance of the CmdhNwAccessRule Object (ID: 2055)oneM2M11.02057.xml1http://www.onem2m.org/images/files/deliverables/TS-0005-Management_Enablement_(OMA)-V1_0_1.pdf13200urn:oma:lwm2m:ext:3200Digital InputGeneric digital input for non-specific sensorsIPSO Alliance11.0version_history/3200-1_0.xml103200urn:oma:lwm2m:ext:3200:1.1Digital InputGeneric digital input for non-specific sensorsIPSO Alliance11.13200.xml103201urn:oma:lwm2m:ext:3201Digital Output>Generic digital output for non-specific actuatorsIPSO Alliance11.0version_history/3201-1_0.xml103201urn:oma:lwm2m:ext:3201:1.1Digital OutputGeneric digital output for non-specific actuatorsIPSO Alliance11.13201.xml103202urn:oma:lwm2m:ext:3202Analog InputGeneric analog input for non-specific sensorsIPSO Alliance11.0version_history/3202-1_0.xml103202urn:oma:lwm2m:ext:3202:1.1Analog InputGeneric analog input for non-specific sensorsIPSO Alliance11.13202.xml103203urn:oma:lwm2m:ext:3203Analog OutputThis IPSO object is a generic object that can be used with any kind of analog output interface.IPSO Alliance11.0version_history/3203-1_0.xml103203urn:oma:lwm2m:ext:3203:1.1Analog OutputThis IPSO object is a generic object that can be used with any kind of analog output interface.IPSO Alliance11.13203.xml103300urn:oma:lwm2m:ext:3300Generic SensorThis IPSO object allows the description of a generic sensor. It is based on the description of a value and a unit according to the SenML specification. Thus, any type of value defined within this specification can be reported using this object. This object may be used as a generic object if a dedicated one does not exist.IPSO Alliance11.0version_history/3300-1_0.xml103300urn:oma:lwm2m:ext:3300:1.1Generic SensorThis IPSO object allows the description of a generic sensor. It is based on the description of a value and a unit according to the SenML specification. Thus, any type of value defined within this specification can be reported using this object. This object may be used as a generic object if a dedicated one does not exist.IPSO Alliance11.13300.xml103301urn:oma:lwm2m:ext:3301IlluminanceIlluminance sensor, example units = lxIPSO Alliance11.0version_history/3301-1_0.xml103301urn:oma:lwm2m:ext:3301:1.1IlluminanceIlluminance sensor, example units = lxIPSO Alliance11.13301.xml103302urn:oma:lwm2m:ext:3302PresencePresence sensor with digital sensing, optional delay parametersIPSO Alliance11.0version_history/3302-1_0.xml103302urn:oma:lwm2m:ext:3302:1.1PresencePresence sensor with digital sensing, optional delay parametersIPSO Alliance11.13302.xml103303urn:oma:lwm2m:ext:3303TemperatureThis IPSO object should be used with a temperature sensor to report a temperature measurement. It also provides resources for minimum/maximum measured values and the minimum/maximum range that can be measured by the temperature sensor. An example measurement unit is degrees Celsius.IPSO Alliance11.0version_history/3303-1_0.xml103303urn:oma:lwm2m:ext:3303:1.1TemperatureThis IPSO object should be used with a temperature sensor to report a temperature measurement. It also provides resources for minimum/maximum measured values and the minimum/maximum range that can be measured by the temperature sensor. An example measurement unit is degrees Celsius.IPSO Alliance11.13303.xml103304urn:oma:lwm2m:ext:3304HumidityThis IPSO object should be used with a humidity sensor to report a humidity measurement. It also provides resources for minimum/maximum measured values and the minimum/maximum range that can be measured by the humidity sensor. An example measurement unit is relative humidity as a percentage.IPSO Alliance11.0version_history/3304-1_0.xml103304urn:oma:lwm2m:ext:3304:1.1HumidityThis IPSO object should be used with a humidity sensor to report a humidity measurement. It also provides resources for minimum/maximum measured values and the minimum/maximum range that can be measured by the humidity sensor. An example measurement unit is relative humidity as a percentage.IPSO Alliance11.13304.xml103305urn:oma:lwm2m:ext:3305Power MeasurementThis IPSO object should be used over a power measurement sensor to report a remote power measurement. It also provides resources for minimum/maximum measured values and the minimum/maximum range for both active and reactive power. It also provides resources for cumulative energy, calibration, and the power factor.IPSO Alliance11.0version_history/3305-1_0.xml103305urn:oma:lwm2m:ext:3305:1.1Power MeasurementThis IPSO object should be used over a power measurement sensor to report a remote power measurement. It also provides resources for minimum/maximum measured values and the minimum/maximum range for both active and reactive power. It also provides resources for cumulative energy, calibration, and the power factor.IPSO Alliance11.13305.xml103306urn:oma:lwm2m:ext:3306ActuationThis IPSO object is dedicated to remote actuation such as ON/OFF action or dimming. A multi-state output can also be described as a string. This is useful to send pilot wire orders for instance. It also provides a resource to reflect the time that the device has been switched on.IPSO Alliance11.0version_history/3306-1_0.xml103306urn:oma:lwm2m:ext:3306:1.1ActuationThis IPSO object is dedicated to remote actuation such as ON/OFF action or dimming. A multi-state output can also be described as a string. This is useful to send pilot wire orders for instance. It also provides a resource to reflect the time that the device has been switched on.IPSO Alliance11.13306.xml103308urn:oma:lwm2m:ext:3308Set PointThis IPSO object should be used to set a desired value to a controller, such as a thermostat. A special resource is added to set the colour of an object.IPSO Alliance11.0version_history/3308-1_0.xml103308urn:oma:lwm2m:ext:3308:1.1Set PointThis IPSO object should be used to set a desired value to a controller, such as a thermostat. A special resource is added to set the colour of an object.IPSO Alliance11.13308.xml103310urn:oma:lwm2m:ext:3310Load ControlThis Object is used for demand-response load control and other load control in automation application (not limited to power).IPSO Alliance11.0version_history/3310-1_0.xml103310urn:oma:lwm2m:ext:3310:1.1Load ControlThis Object is used for demand-response load control and other load control in automation application (not limited to power).IPSO Alliance11.13310.xml103311urn:oma:lwm2m:ext:3311Light ControlThis Object is used to control a light source, such as a LED or other light. It allows a light to be turned on or off and its dimmer setting to be control as a % between 0 and 100. An optional colour setting enables a string to be used to indicate the desired colour.IPSO Alliance11.03311.xml103312urn:oma:lwm2m:ext:3312Power ControlThis Object is used to control a power source, such as a Smart Plug. It allows a power relay to be turned on or off and its dimmer setting to be control as a % between 0 and 100.IPSO Alliance11.0version_history/3312-1_0.xml103312urn:oma:lwm2m:ext:3312:1.1Power ControlThis Object is used to control a power source, such as a Smart Plug. It allows a power relay to be turned on or off and its dimmer setting to be control as a % between 0 and 100.IPSO Alliance11.13312.xml103313urn:oma:lwm2m:ext:3313AccelerometerThis IPSO object can be used to represent a 1-3 axis accelerometer.IPSO Alliance11.0version_history/3313-1_0.xml103313urn:oma:lwm2m:ext:3313:1.1AccelerometerThis IPSO object can be used to represent a 1-3 axis accelerometer.IPSO Alliance11.13313.xml103314urn:oma:lwm2m:ext:3314MagnetometerThis IPSO object can be used to represent a 1-3 axis magnetometer with optional compass direction.IPSO Alliance11.0version_history/3314-1_0.xml103314urn:oma:lwm2m:ext:3314:1.1MagnetometerThis IPSO object can be used to represent a 1-3 axis magnetometer with optional compass direction.IPSO Alliance11.13314.xml103315urn:oma:lwm2m:ext:3315BarometerThis IPSO object should be used with an air pressure sensor to report a barometer measurement. It also provides resources for minimum/maximum measured values and the minimum/maximum range that can be measured by the barometer sensor. An example measurement unit is pascals.IPSO Alliance11.0version_history/3315-1_0.xml103315urn:oma:lwm2m:ext:3315:1.1BarometerThis IPSO object should be used with an air pressure sensor to report a barometer measurement. It also provides resources for minimum/maximum measured values and the minimum/maximum range that can be measured by the barometer sensor. An example measurement unit is pascals.IPSO Alliance11.13315.xml103316urn:oma:lwm2m:ext:3316VoltageThis IPSO object should be used with voltmeter sensor to report measured voltage between two points. It also provides resources for minimum and maximum measured values, as well as the minimum and maximum range that can be measured by the sensor. An example measurement unit is volts.IPSO Alliance11.0version_history/3316-1_0.xml103316urn:oma:lwm2m:ext:3316:1.1VoltageThis IPSO object should be used with voltmeter sensor to report measured voltage between two points. It also provides resources for minimum and maximum measured values, as well as the minimum and maximum range that can be measured by the sensor. An example measurement unit is volts.IPSO Alliance11.13316.xml103317urn:oma:lwm2m:ext:3317CurrentThis IPSO object should be used with an ammeter to report measured electric current in amperes. It also provides resources for minimum and maximum measured values, as well as the minimum and maximum range that can be measured by the sensor. An example measurement unit is ampere.IPSO Alliance11.0version_history/3317-1_0.xml103317urn:oma:lwm2m:ext:3317:1.1CurrentThis IPSO object should be used with an ammeter to report measured electric current in amperes. It also provides resources for minimum and maximum measured values, as well as the minimum and maximum range that can be measured by the sensor. An example measurement unit is ampere.IPSO Alliance11.13317.xml103318urn:oma:lwm2m:ext:3318FrequencyThis IPSO object should be used to report frequency measurements. It also provides resources for minimum and maximum measured values, as well as the minimum and maximum range that can be measured by the sensor. An example measurement unit is hertz.IPSO Alliance11.0version_history/3318-1_0.xml103318urn:oma:lwm2m:ext:3318:1.1FrequencyThis IPSO object should be used to report frequency measurements. It also provides resources for minimum and maximum measured values, as well as the minimum and maximum range that can be measured by the sensor. An example measurement unit is hertz.IPSO Alliance11.13318.xml103319urn:oma:lwm2m:ext:3319DepthThis IPSO object should be used to report depth measurements. It can, for example, be used to describe a generic rain gauge that measures the accumulated rainfall in millimetres (mm).IPSO Alliance11.0version_history/3319-1_0.xml103319urn:oma:lwm2m:ext:3319:1.1DepthThis IPSO object should be used to report depth measurements. It can, for example, be used to describe a generic rain gauge that measures the accumulated rainfall in millimetres (mm).IPSO Alliance11.13319.xml103320urn:oma:lwm2m:ext:3320PercentageThis IPSO object should can be used to report measurements relative to a 0-100% scale. For example it could be used to measure the level of a liquid in a vessel or container in units of %.IPSO Alliance11.0version_history/3320-1_0.xml103320urn:oma:lwm2m:ext:3320:1.1PercentageThis IPSO object should can be used to report measurements relative to a 0-100% scale. For example it could be used to measure the level of a liquid in a vessel or container in units of %.IPSO Alliance11.13320.xml103321urn:oma:lwm2m:ext:3321AltitudeThis IPSO object should be used with an altitude sensor to report altitude above sea level in meters. Note that Altitude can be calculated from the measured pressure given the local sea level pressure. It also provides resources for minimum and maximum measured values, as well as the minimum and maximum range that can be measured by the sensor. An example measurement unit is meters.IPSO Alliance11.0version_history/3321-1_0.xml103321urn:oma:lwm2m:ext:3321:1.1AltitudeThis IPSO object should be used with an altitude sensor to report altitude above sea level in meters. Note that Altitude can be calculated from the measured pressure given the local sea level pressure. It also provides resources for minimum and maximum measured values, as well as the minimum and maximum range that can be measured by the sensor. An example measurement unit is meters.IPSO Alliance11.13321.xml103322urn:oma:lwm2m:ext:3322LoadThis IPSO object should be used with a load sensor (as in a scale) to report the applied weight or force. It also provides resources for minimum and maximum measured values, as well as the minimum and maximum range that can be measured by the sensor. An example measurement unit is kilograms.IPSO Alliance11.0version_history/3322-1_0.xml103322urn:oma:lwm2m:ext:3322:1.1LoadThis IPSO object should be used with a load sensor (as in a scale) to report the applied weight or force. It also provides resources for minimum and maximum measured values, as well as the minimum and maximum range that can be measured by the sensor. An example measurement unit is kilograms.IPSO Alliance11.13322.xml103323urn:oma:lwm2m:ext:3323PressureThis IPSO object should be used to report pressure measurements. It also provides resources for minimum and maximum measured values, as well as the minimum and maximum range that can be measured by the sensor. An example measurement unit is pascals.IPSO Alliance11.0version_history/3323-1_0.xml103323urn:oma:lwm2m:ext:3323:1.1PressureThis IPSO object should be used to report pressure measurements. It also provides resources for minimum and maximum measured values, as well as the minimum and maximum range that can be measured by the sensor. An example measurement unit is pascals.IPSO Alliance11.13323.xml103324urn:oma:lwm2m:ext:3324LoudnessThis IPSO object should be used to report loudness or noise level measurements. It also provides resources for minimum and maximum measured values, as well as the minimum and maximum range that can be measured by the sensor. An example measurement unit is decibels.IPSO Alliance11.0version_history/3324-1_0.xml103324urn:oma:lwm2m:ext:3324:1.1LoudnessThis IPSO object should be used to report loudness or noise level measurements. It also provides resources for minimum and maximum measured values, as well as the minimum and maximum range that can be measured by the sensor. An example measurement unit is decibels.IPSO Alliance11.13324.xml103325urn:oma:lwm2m:ext:3325ConcentrationThis IPSO object should be used to the particle concentration measurement of a medium. It also provides resources for minimum and maximum measured values, as well as the minimum and maximum range that can be measured by the sensor. An example measurement unit is parts per million.IPSO Alliance11.0version_history/3325-1_0.xml103325urn:oma:lwm2m:ext:3325:1.1ConcentrationThis IPSO object should be used to the particle concentration measurement of a medium. It also provides resources for minimum and maximum measured values, as well as the minimum and maximum range that can be measured by the sensor. An example measurement unit is parts per million.IPSO Alliance11.13325.xml103326urn:oma:lwm2m:ext:3326AcidityThis IPSO object should be used to report an acidity measurement of a liquid. It also provides resources for minimum and maximum measured values, as well as the minimum and maximum range that can be measured by the sensor. An example measurement unit is pH.IPSO Alliance11.0version_history/3326-1_0.xml103326urn:oma:lwm2m:ext:3326:1.1AcidityThis IPSO object should be used to report an acidity measurement of a liquid. It also provides resources for minimum and maximum measured values, as well as the minimum and maximum range that can be measured by the sensor. An example measurement unit is pH.IPSO Alliance11.13326.xml103327urn:oma:lwm2m:ext:3327ConductivityThis IPSO object should be used to report a measurement of the electric conductivity of a medium or sample. It also provides resources for minimum and maximum measured values, as well as the minimum and maximum range that can be measured by the sensor. An example measurement unit is Siemens.IPSO Alliance11.0version_history/3327-1_0.xml103327urn:oma:lwm2m:ext:3327:1.1ConductivityThis IPSO object should be used to report a measurement of the electric conductivity of a medium or sample. It also provides resources for minimum and maximum measured values, as well as the minimum and maximum range that can be measured by the sensor. An example measurement unit is Siemens.IPSO Alliance11.13327.xml103328urn:oma:lwm2m:ext:3328PowerThis IPSO object should be used to report power measurements. It also provides resources for minimum and maximum measured values, as well as the minimum and maximum range that can be measured by the sensor.This IPSO object should be used to report power measurements. It also provides resources for minimum and maximum measured values, as well as the minimum and maximum range that can be measured by the sensor. An example measurement unit is Watts. This object may be used for either real power or apparent power measurements.IPSO Alliance11.0version_history/3328-1_0.xml103328urn:oma:lwm2m:ext:3328:1.1PowerThis IPSO object should be used to report power measurements. It also provides resources for minimum and maximum measured values, as well as the minimum and maximum range that can be measured by the sensor. An example measurement unit is Watts. This object may be used for either real power or apparent power measurements.IPSO Alliance11.13328.xml103329urn:oma:lwm2m:ext:3329Power FactorThis IPSO object should be used to report a measurement or calculation of the power factor of a reactive electrical load. Power Factor is normally the ratio of non-reactive power to total power. This object also provides resources for minimum and maximum measured values, as well as the minimum and maximum range that can be measured by the sensor.IPSO Alliance11.0version_history/3329-1_0.xml103329urn:oma:lwm2m:ext:3329:1.1Power FactorThis IPSO object should be used to report a measurement or calculation of the power factor of a reactive electrical load. Power Factor is normally the ratio of non-reactive power to total power. This object also provides resources for minimum and maximum measured values, as well as the minimum and maximum range that can be measured by the sensor.IPSO Alliance11.13329.xml103330urn:oma:lwm2m:ext:3330DistanceThis IPSO object should be used to report a distance measurement. It also provides resources for minimum and maximum measured values, as well as the minimum and maximum range that can be measured by the sensor. An example measurement unit is Meters.IPSO Alliance11.0version_history/3330-1_0.xml103330urn:oma:lwm2m:ext:3330:1.1DistanceThis IPSO object should be used to report a distance measurement. It also provides resources for minimum and maximum measured values, as well as the minimum and maximum range that can be measured by the sensor. An example measurement unit is Meters.IPSO Alliance11.13330.xml103331urn:oma:lwm2m:ext:3331EnergyThis IPSO object should be used to report energy consumption (Cumulative Power) of an electrical load. An example measurement unit is Watt Hours.IPSO Alliance11.0version_history/3331-1_0.xml103331urn:oma:lwm2m:ext:3331:1.1EnergyThis IPSO object should be used to report energy consumption (Cumulative Power) of an electrical load. An example measurement unit is Watt Hours.IPSO Alliance11.13331.xml103332urn:oma:lwm2m:ext:3332DirectionThis IPSO object is used to report the direction indicated by a compass, wind vane, or other directional indicator. The units of measure is plane angle degrees.IPSO Alliance11.0version_history/3332-1_0.xml103332urn:oma:lwm2m:ext:3332:1.1DirectionThis IPSO object is used to report the direction indicated by a compass, wind vane, or other directional indicator. The units of measure is plane angle degrees.IPSO Alliance11.13332.xml103333urn:oma:lwm2m:ext:3333TimeThis IPSO object is used to report the current time in seconds since January 1, 1970 UTC. There is also a fractional time counter that has a range of less than one second.IPSO Alliance11.0version_history/3333-1_0.xml103333urn:oma:lwm2m:ext:3333:1.1TimeThis IPSO object is used to report the current time in seconds since January 1, 1970 UTC. There is also a fractional time counter that has a range of less than one second.IPSO Alliance11.13333.xml103334urn:oma:lwm2m:ext:3334GyrometerThis IPSO Object is used to report the current reading of a gyrometer sensor in 3 axes. It provides tracking of the minimum and maximum angular rate in all 3 axes. An example unit of measure is radians per second.IPSO Alliance11.0version_history/3334-1_0.xml103334urn:oma:lwm2m:ext:3334:1.1GyrometerThis IPSO Object is used to report the current reading of a gyrometer sensor in 3 axes. It provides tracking of the minimum and maximum angular rate in all 3 axes. An example unit of measure is radians per second.IPSO Alliance11.13334.xml103335urn:oma:lwm2m:ext:3335ColourThis IPSO object should be used to report the measured value of a colour sensor in some colour space described by the units resource.IPSO Alliance11.0version_history/3335-1_0.xml103335urn:oma:lwm2m:ext:3335:1.1ColourThis IPSO object should be used to report the measured value of a colour sensor in some colour space described by the units resource.IPSO Alliance11.13335.xml103336urn:oma:lwm2m:ext:3336LocationThis IPSO object represents GPS coordinates. This object is compatible with the LWM2M management object for location, but uses reusable resources.IPSO Alliance11.0version_history/3336-1_0.xml103336urn:oma:lwm2m:ext:3336:1.1LocationThis IPSO object represents GPS coordinates. This object is compatible with the LWM2M management object for location, but uses reusable resources.IPSO Alliance11.1version_history/3336-1_1.xml103336urn:oma:lwm2m:ext:3336:2.0LocationThis IPSO object represents GPS coordinates. This object is compatible with the LwM2M management object for location, but uses reusable resources.IPSO Alliance12.03336.xml103337urn:oma:lwm2m:ext:3337PositionerThis IPSO object should be used with a generic position actuator with range from 0 to 100%. This object optionally allows setting the transition time for an operation that changes the position of the actuator, and for reading the remaining time of the currently active transition.IPSO Alliance11.0version_history/3337-1_0.xml103337urn:oma:lwm2m:ext:3337:1.1PositionerThis IPSO object should be used with a generic position actuator with range from 0 to 100%. This object optionally allows setting the transition time for an operation that changes the position of the actuator, and for reading the remaining time of the currently active transition.IPSO Alliance11.13337.xml103338urn:oma:lwm2m:ext:3338BuzzerThis IPSO object should be used to actuate an audible alarm such as a buzzer, beeper, or vibration alarm. There is a dimmer control for setting the relative loudness of the alarm, and an optional duration control to limit the length of time the alarm sounds when turned on. Each time "true" is written to the On/Off resource, the alarm will sound again for the configured duration. If no duration is programmed or the setting is "false", writing a "true" to the On/Off resource will result in the alarm sounding continuously until a "false" is written to the On/Off resource.IPSO Alliance11.0version_history/3338-1_0.xml103338urn:oma:lwm2m:ext:3338:1.1BuzzerThis IPSO object should be used to actuate an audible alarm such as a buzzer, beeper, or vibration alarm. There is a dimmer control for setting the relative level of the alarm, and an optional duration control to limit the length of time the alarm sounds when turned on. Each time "true" is written to the On/Off resource, the alarm will sound again for the configured duration. If no duration is programmed or the setting is "false", writing a "true" to the On/Off resource will result in the alarm sounding continuously until a "false" is written to the On/Off resource.IPSO Alliance11.13338.xml103339urn:oma:lwm2m:ext:3339Audio ClipThis IPSO object should be used for a speaker that plays a pre-recorded audio clip or an audio output that is sent elsewhere. For example, an elevator which announces the floor of the building. A resource is provided to store the clip, a dimmer resource controls the relative sound level of the playback, and a duration resource limits the maximum playback time. After the duration time is reached, any remaining samples in the clip are ignored, and the clip player will be ready to play another clip.IPSO Alliance11.03339.xml103340urn:oma:lwm2m:ext:3340TimerThis IPSO object is used to time events and actions, using patterns common to industrial timers. A write to the trigger resource or On/Off input state change starts the timing operation, and the timer remaining time shows zero when the operation is complete. The patterns supported are One-Shot (mode 1), On-Time or Interval (mode 2), Time delay on pick-up or TDPU (mode 3), and Time Delay on Drop-Out or TDDO (mode 4). Mode 0 disables the timer, so the output follows the input with no delay. A counter is provided to count occurrences of the timer output changing from 0 to 1. Writing a value of zero resets the counter. The Digital Input State resource reports the state of the timer output.IPSO Alliance11.03340.xml103341urn:oma:lwm2m:ext:3341Addressable Text DisplayThis IPSO object is used to send text to a text-only or text mode graphics display. Writing a string of text to the text resource causes it to be displayed at the selected X and Y locations on the display. If X or Y are set to a value greater than the size of the display, the position "wraps around" to the modulus of the setting and the display size. Likewise, if the text string overflows the display size, the text "wraps around" and displays on the next line down or, if the last line has been written, wraps around to the top of the display. Brightness and Contrast controls are provided to allow control of various display types including STN and DSTN type LCD character displays. Writing an empty payload to the Clear Display resource causes the display to be erased.IPSO Alliance11.03341.xml103342urn:oma:lwm2m:ext:3342On/Off switchThis IPSO object should be used with an On/Off switch to report the state of the switch.IPSO Alliance11.0version_history/3342-1_0.xml103342urn:oma:lwm2m:ext:3342:1.1On/Off switchThis IPSO object should be used with an On/Off switch to report the state of the switch.IPSO Alliance11.13342.xml103343urn:oma:lwm2m:ext:3343DimmerThis IPSO object should be used with a dimmer or level control to report the state of the control.IPSO Alliance11.03343.xml103344urn:oma:lwm2m:ext:3344Up/Down ControlThis IPSO object is used to report the state of an up/down control element like a pair of push buttons or a rotary encoder. Counters for increase and decrease operations are provided for counting pulses from a quadrature encoder.IPSO Alliance11.03344.xml103345urn:oma:lwm2m:ext:3345Multiple Axis JoystickThis IPSO object can be used to report the position of a shuttle or joystick control. A digital input is provided to report the state of an associated push button.IPSO Alliance11.03345.xml103346urn:oma:lwm2m:ext:3346RateThis object type should be used to report a rate measurement, for example the speed of a vehicle, or the rotational speed of a drive shaft. It also provides resources for minimum and maximum measured values, as well as the minimum and maximum range that can be measured by the sensor. An example measurement unit is meters per second (m/s).IPSO Alliance11.0version_history/3346-1_0.xml103346urn:oma:lwm2m:ext:3346:1.1RateThis object type should be used to report a rate measurement, for example the speed of a vehicle, or the rotational speed of a drive shaft. It also provides resources for minimum and maximum measured values, as well as the minimum and maximum range that can be measured by the sensor. An example measurement unit is meters per second (m/s).IPSO Alliance11.13346.xml103347urn:oma:lwm2m:ext:3347Push buttonThis IPSO object is used to report the state of a momentary action push button control and to count the number of times the control has been operated since the last observation.IPSO Alliance11.0version_history/3347-1_0.xml103347urn:oma:lwm2m:ext:3347:1.1Push buttonThis IPSO object is used to report the state of a momentary action push button control and to count the number of times the control has been operated since the last observation.IPSO Alliance11.13347.xml103348urn:oma:lwm2m:ext:3348Multi-state SelectorThis IPSO object is used to represent the state of a Multi-state selector switch with a number of fixed positions.IPSO Alliance11.0version_history/3348-1_0.xml103348urn:oma:lwm2m:ext:3348:1.1Multi-state SelectorThis IPSO object is used to represent the state of a Multi-state selector switch with a number of fixed positions.IPSO Alliance11.13348.xml103349urn:oma:lwm2m:ext:3349BitmapSummarize several digital inputs to one value by mapping each bit to a digital input.IPSO Alliance11.0version_history/3349-1_0.xml103349urn:oma:lwm2m:ext:3349:1.1BitmapSummarize several digital inputs to one value by mapping each bit to a digital input.IPSO Alliance11.13349.xml103350urn:oma:lwm2m:ext:3350StopwatchAn ascending timer that counts how long time has passed since the timer was started after reset.IPSO Alliance11.0version_history/3350-1_0.xml103350urn:oma:lwm2m:ext:3350:1.1StopwatchAn ascending timer that counts how long time has passed since the timer was started after reset.IPSO Alliance11.13350.xml103351urn:oma:lwm2m:ext:3351powerupLogOne time event sent by the device at power up.GSMA11.03351.xml103352urn:oma:lwm2m:ext:3352plmnSearchEventList of all PLMNs found during the initial search/scanGSMA11.03352.xml103353urn:oma:lwm2m:ext:3353scellIDserving cell information that the RRC decides to camp onGSMA11.03353.xml103354urn:oma:lwm2m:ext:3354cellReselectionEventcell reselection event informationGSMA11.03354.xml103355urn:oma:lwm2m:ext:3355handoverEventhandover event informationGSMA11.03355.xml103356urn:oma:lwm2m:ext:3356radioLinkFailureEventRadio Link Failure EventGSMA11.03356.xml103357urn:oma:lwm2m:ext:3357rrcStateChangeEventCurrent RRC state change information, including the event that triggered the state changeGSMA11.03357.xml103358urn:oma:lwm2m:ext:3358rrcTimerExpiryEventRRC timer expiry event informationGSMA11.03358.xml103359urn:oma:lwm2m:ext:3359cellBlacklistEventCell blacklist informationGSMA11.03359.xml103360urn:oma:lwm2m:ext:3360esmContextInfoESM context informationGSMA11.03360.xml103361urn:oma:lwm2m:ext:3361emmStateValueEMM context informationGSMA11.03361.xml103362urn:oma:lwm2m:ext:3362nasEmmTimerExpiryEventNAS EMM timer expiry informationGSMA11.03362.xml103363urn:oma:lwm2m:ext:3363nasEsmExpiryEventNAS ESM timer expiry informationGSMA11.03363.xml103364urn:oma:lwm2m:ext:3364emmFailureCauseEventTriggered at EMM failure - failure cause is loggedGSMA11.03364.xml 103365urn:oma:lwm2m:ext:3365rachLatency_delayRACH Latency & delay informationGSMA11.03365.xml103366urn:oma:lwm2m:ext:3366macRachAttemptEventRACH information. Logged at RACH TXGSMA11.03366.xml103367urn:oma:lwm2m:ext:3367macRachAttemptReasonEventRACH Information - reason for initiating RACHGSMA11.03367.xml103368urn:oma:lwm2m:ext:3368macTimerStatusEventMAC timer expiry informationGSMA11.03368.xml103369urn:oma:lwm2m:ext:3369macTimingAdvanceEventTiming advance informationGSMA11.03369.xml103370urn:oma:lwm2m:ext:3370ServingCellMeasurementServing Cell MeasurementGSMA11.03370.xml103371urn:oma:lwm2m:ext:3371NeighborCellMeasurementsNeighbor Cell MeasurementsGSMA11.03371.xml103372urn:oma:lwm2m:ext:3372TimingAdvanceTiming Advance InformationGSMA11.03372.xml103373urn:oma:lwm2m:ext:3373txPowerHeadroomEventTX power headroom informationGSMA11.03373.xml103374urn:oma:lwm2m:ext:3374radioLinkMonitoringRadio Link monitoring information maintained by RRCGSMA11.03374.xml103375urn:oma:lwm2m:ext:3375PagingDRXPaging DRX informationGSMA11.03375.xml103376urn:oma:lwm2m:ext:3376txPowerBackOffEventTX Power backoff informationGSMA11.03376.xml103377urn:oma:lwm2m:ext:3377Message3ReportRACH message 3 report informationGSMA11.03377.xml103378urn:oma:lwm2m:ext:3378PbchDecodingResultsServing cell PBCH decoding informationGSMA11.03378.xml103379urn:oma:lwm2m:ext:3379pucchPowerControlPUCCH TX power control informationGSMA11.03379.xml103380urn:oma:lwm2m:ext:3380PrachReportPRACH report information. Deprecated by v2.0.GSMA11.0version_history/3380-1_0.xml103380urn:oma:lwm2m:ext:3380:2.0PrachReportPRACH report informationGSMA12.03380.xml103381urn:oma:lwm2m:ext:3381VolteCallEventVoLTE call statusGSMA11.03381.xml103382urn:oma:lwm2m:ext:3382SipRegistrationEventSIP Registration statusGSMA11.03382.xml103383urn:oma:lwm2m:ext:3383sipPublishEventSIP Publish statusGSMA11.03383.xml103384urn:oma:lwm2m:ext:3384sipSubscriptionEventSIP Subscription statusGSMA11.03384.xml103385urn:oma:lwm2m:ext:3385volteCallStateChangeEventVoLTE call status changeGSMA11.03385.xml103386urn:oma:lwm2m:ext:3386VoLTErtpPacketLossLog is generated at the receiving end of RTP flow when newReceivedSequenceNumber - lastReceivedSequenceNumber > 1GSMA11.03386.xml103387urn:oma:lwm2m:ext:3387oA Basic ControlThe 'oA Basic Control' represents a common basic interface for a Control Function. This allows to have vendor specific (executing) control functions using diverse object numbers to be interfaced for the basic functionality in a common way. The object provides the basic functionality required for an OpenAIS control object.OpenAIS11.03387.xml103388urn:oma:lwm2m:ext:3388oA DeviceThe 'oA Device' represents the OpenAIS specific parameters of a Device that are necessary in addition to the LWM2M Device.OpenAIS11.03388.xml103389urn:oma:lwm2m:ext:3389oA GroupThe 'oA Group' represents a group. It contains an application group ID, a security group ID and a list of multicast and unicast IP addresses that are used in the group. \nAdditionally it contains a list of all members of the group.OpenAIS11.03389.xml103390urn:oma:lwm2m:ext:3390oA Logical Colour Light-Point ActuatorThe 'oA Logical Colour Light Point Actuator' represents the logical part of an actuator model for a colour light point. The corresponding physical device is a light channel and associated gear (e.g. LED driver).\nThe Object (module) supports several interactions that include absolute and relative colour setting. Several device configuration parameters are mapped, which relate to behaviour or describe device limitations.OpenAIS11.03390.xml103391urn:oma:lwm2m:ext:3391oA Logical Colour Temperature Light-Point ActuatorThe 'oA Logical Colour_Temperature Light Point Actuator' represents the logical part of an actuator model for a tunable white light point. The corresponding physical device is a light channel and associated gear (e.g. LED driver).\nThe Object (module) supports several interactions that include absolute and relative colour temperature setting. Several device configuration parameters are mapped, which relate to behaviour or describe device limitations. Note that the overall intensity is not controlled by this object, it remains controlled by a logical light point object to ease dimming action across tuneable, coloured and non coloured lights. Please note also, that the corresponding executing object does not need to be restricted to tuneable white operation.OpenAIS11.03391.xml103392urn:oma:lwm2m:ext:3392oA Logical Illuminance SensorThe 'oA Logical Illuminance Sensor' represents the logical part of an illuminance sensor. The corresponding physical device is a sensor that detects illuminance in its detection area.OpenAIS11.03392.xml103393urn:oma:lwm2m:ext:3393oA Logical Light-Point ActuatorThe 'oA Logical Light Point Actuator' represents the logical part of an actuator model for a dimmable light point. The corresponding physical device is a light channel and associated gear (e.g. LED driver).\nThe Object (module) supports several interactions that include basic On/Off as well as Up/Down dimming. Several device configuration parameters are mapped, which relate to behaviour or describe device limitations. For multi-channel luminaires where the configuration per channel may vary significantly (e.g. different max/min values), multiple instances of this Object should be used.OpenAIS11.03393.xml103394urn:oma:lwm2m:ext:3394oA Logical Presence SensorThe 'oA Logical Presence Sensor' represents the logical part of a presence sensor. The corresponding physical device is a sensor that detects presence in its detection area. \nThe Object supports two states 'presence' and 'absence'.OpenAIS11.03394.xml103395urn:oma:lwm2m:ext:3395oA Logical Push-Button SensorThe 'oA Logical Push-Button Sensor' represents the logical part of a standard, normally open, push-button input. The corresponding physical device is a button with a spring that returns the button to the un-pushed state once it is released.\nThe Object supports several events such as 'click', 'hold', 'double-click' and 'release'. It also indicates if the button is 'stuck'. For physical devices with multiple push-button inputs, an instance of this Object is required to map each input.OpenAIS11.03395.xml103396urn:oma:lwm2m:ext:3396oA Physical Colour Light-Point ActuatorThe 'oA_Physical_Colour_Light-Point_Actuator' represents a physical colour light-point actuator. It is necessary to map at least on Logical Light Point Actuator to control the intensity and one Logical Colour Light-Point to control the colour to the Physical Colour Light-Point.OpenAIS11.03396.xml103397urn:oma:lwm2m:ext:3397oA Physical Colour Temperature Light-Point ActuatorThe 'oA_Physical_Colour_Temperature_Light-Point_Actuator' represents a physical tunable white light-point actuator. It is necessary to map at least on Logical Light Point Actuator to control the intensity and one Logical Colour Temperature Light-Point to control the colour temperature to the Physical Colour Temperature Light Point.OpenAIS11.03397.xml103398urn:oma:lwm2m:ext:3398oA Physical Illuminance SensorThe 'oA_Physical_Illuminance_Sensor' represents the physical part of an illuminance sensor. All logical illuminance sensors (object instances of 'oA Illuminance Sensor') are mapped to one physical illuminance sensor.OpenAIS11.03398.xml103399urn:oma:lwm2m:ext:3399oA Physical Light-Point ActuatorThe 'oA_Physical_Light-Point_Actuator' represents a physical light-point actuator. All logical light-point actuators (object instances of 'oA Light-Point Actuator') are mapped to one physical light-point actuator.OpenAIS11.03399.xml103400urn:oma:lwm2m:ext:3400oA Physical Presence SensorThe 'oA_Physical_Presence_Sensor' represents the physical part of a presence sensor. All logical presence sensors (object instances of 'oA Presence Sensor') are mapped to one physical presence sensor.OpenAIS11.03400.xml103401urn:oma:lwm2m:ext:3401oA Physical Push-Button SensorThe 'oA_Physical_Push-Button_Sensor' represents the physical part of a push-button sensor. All logical push-button sensors (object instances of 'oA Push-Button Sensor') are mapped to one physical push-button sensor.OpenAIS11.03401.xml103402urn:oma:lwm2m:ext:3402oA Receiving ObjectThe 'oA Receiving Object' provides a resource for sensors/actuators to report their status message to. It is used with control objects as logical object that forwards the sensor and status data to the executing object.\nIt is also used to receive the 'go bootstrap' message, using the Struct-ID 255, in OOTB mode.OpenAIS11.03402.xml103403urn:oma:lwm2m:ext:3403oA Reporting ObjectThe 'oA Reporting Object' packs several status messages available at the node into a single, size optimized message, as e.g. used with data collect or BMS interfacing.OpenAIS11.03403.xml103404urn:oma:lwm2m:ext:3404oA SceneThe 'oA Scene' represents a scene model. The scene holds defined values for each actuator in one group.OpenAIS11.03404.xml103405urn:oma:lwm2m:ext:3405oA OGC-SecurityThe 'OGC Security' provides the appropriate keying material for a specific OGC Application group in the context of OGC. The keying material will be provided by a key distribution server, and must not be readable by any instance outside the local node.OpenAIS11.03405.xml103406urn:oma:lwm2m:ext:3406oA Status Report StructureThe 'oA Status_Report_Structure' describes the content of the status reports. Its ID is always the first byte, the following bytes are defined by Keys.OpenAIS11.03406.xml103407urn:oma:lwm2m:ext:3407Smoke AlarmThis is an alarm that should be raised if the meter detects CO2 concentration above a pre-configured threshold.IoT Connectivity Alliance11.03407.xml103408urn:oma:lwm2m:ext:3408Manhole CoverDescribe the status of a manhole cover.IoT Connectivity Alliance11.03408.xml103409urn:oma:lwm2m:ext:3409TBCTBCTBC11.0003410urn:oma:lwm2m:ext:3410Device ExtensionThe uCIFI device extension is an extension to the standard Lightweight M2M device (object ID 3) using the resource called "ExtDevInfo" (resource ID 22).uCIFI11.03410.xml103411urn:oma:lwm2m:ext:3411BatteryThe uCIFI battery object provides attributes to monitor battery level and activity.uCIFI11.03411.xml103412urn:oma:lwm2m:ext:3412LPWAN CommunicationThe uCIFI communication object provides attributes related to the communication on the LPWAN network, including multicast grouping.uCIFI11.03412.xml103413urn:oma:lwm2m:ext:3413uCIFI Generic ActuatorThe uCIFI generic actuator may be used for any actuator but not to replace Outdoor Lamp Controllers nor for an Irrigation Valves which have a specific device type in the uCIFI data model.uCIFI11.03413.xml103414urn:oma:lwm2m:ext:3414uCIFI data bridgeThe uCIFI data bridge object may be used to transport data from a 3rd party device, operating a proprietary network or protocol, over a LwM2M compliant network.uCIFI11.03414.xml103415urn:oma:lwm2m:ext:3415Time synchronizationThe uCIFI time synchronization object enables a device to sync-up its internal clock with a remote NTP server.uCIFI11.03415.xml103416urn:oma:lwm2m:ext:3416Outdoor lamp controllerThe uCIFI outdoor lamp controller object provides attributes to control, command and monitor outdoor luminaires in streets, in tunnels, on roads and for illumination of park and gardens.uCIFI11.03416.xml103417urn:oma:lwm2m:ext:3417Luminaire assetThe uCIFI luminaire asset is an object that enables outdoor lighting control software to configure outdoor lamp controllers. It also enables outdoor lamp controllers to send Zhaga D4i or DALI attributes read from the control gears, to centrally managed outdoor lighting control software or asset management systems.uCIFI11.03417.xml103418urn:oma:lwm2m:ext:3418Electrical monitorThe uCIFI electrical monitor object provides attributes related to the analysis of electrical consumption in an outdoor luminaire or in a streetlight cabinet. It also identifies electrical anomalies.uCIFI11.03418.xml103419urn:oma:lwm2m:ext:3419PhotocellA uCIFI photocell object is used for lighting control, particularly to identify when light should be switched ON/OFF.uCIFI11.03419.xml103420urn:oma:lwm2m:ext:3420LED color lightThe uCIFI LED color light enables to control light colors of a LED luminaire.uCIFI11.03420.xml103421urn:oma:lwm2m:ext:3421Single-phase electrical meterThe uCIFI single-phase electrical meter measures the electrical consumption of loads on one electrical line, such as electrical cabinets in city infrastructures, street lighting networks, homes and buildings.uCIFI11.03421.xml103422urn:oma:lwm2m:ext:3422TBCTBCTBC11.0003423urn:oma:lwm2m:ext:3423Gas meterThe uCIFI gas meter measures the volume of gas that was distributed through the gas meter, in pulse count and/or in m3. It also detects anomalies in the gas meter.uCIFI11.03423.xml103424urn:oma:lwm2m:ext:3424Water meterThe uCIFI water meter measures water volume that was distributed through a water meter, in pulse count as well as in m3. It also detects anomalies in the water meter.uCIFI11.03424.xml103425urn:oma:lwm2m:ext:3425Irrigation valveThe uCIFI irrigation valve provides a way to control and monitor an irrigation valve.uCIFI11.03425.xml103426urn:oma:lwm2m:ext:3426Water quality sensorThe uCIFI water quality sensor measures the quality of the water in the drinkable water distribution network, in water tanks or in lakes and rivers.uCIFI11.03426.xml103427urn:oma:lwm2m:ext:3427Pressure monitoring sensorThe uCIFI water pressure monitoring sensor measures water pressure and help identify water leaks in water distribution pipelines.uCIFI11.03427.xml103428urn:oma:lwm2m:ext:3428Air qualityThe uCIFI air quality sensor reports measurement required to calculate Air Quality Index (AIQ. It also provides resources for average calculation as per the IQ index calculation.uCIFI11.03428.xml103429urn:oma:lwm2m:ext:3429Tilt sensorThe uCIFI tilt sensor provides the angle between the object's internal vertical and the perpendicular to the earth.uCIFI11.03429.xml103430urn:oma:lwm2m:ext:3430Global Navigation Satellite SystemMore than a positioning object, the uCIFI global navigation satellite system object provides all the information required to calculate a position/location.uCIFI11.03430.xml103431urn:oma:lwm2m:ext:3431Parking SensorThe uCIFI parking sensor provides actual and cumulated occupancy duration as well as forbidden parking detection.uCIFI11.03431.xml103432urn:oma:lwm2m:ext:3432Traffic CounterThe uCIFI traffic counter provides vehicle counting and traffic analysis data. A traffic counting device may implement multiple instances of this traffic counter object, each of them being in charge of counting different categories of vehicles (e.g. bikes, cars, trucks).uCIFI11.03432.xml103433urn:oma:lwm2m:ext:3433Noise sensorThe uCIFI noise sensor reports a noise measurement in decibel. It also provides resources for minimum/maximum measured values and the minimum/maximum range that can be measured by the noise sensor and some specific alarms resulting from noise analysis by the device.uCIFI11.03433.xml103434urn:oma:lwm2m:ext:3434People counterThe uCIFI people counter provides people counting information using Bluetooth beacon or any other method.uCIFI11.03434.xml103435urn:oma:lwm2m:ext:3435Filling levelThe uCIFI filling level sensor measures how full and/or how empty a container (e.g. waste, fuel) is and reports it either in percentage or in centimeters. The filling level sensor may be complemented with a temperature sensor to compose a waste filling sensor that can also identify waste container fire.uCIFI11.03435.xml103436urn:oma:lwm2m:ext:3436Edge computing managerThe uCIFI edge computing manager object defines the capability of a device to run scripts on the device itself.uCIFI11.03436.xml103437urn:oma:lwm2m:ext:3437Edge computing scriptThe uCIFI edge computing scripts object defines a particular script to be executed by a device under a time or any other condition set by a "Edge Computing Time Condition" or "Edge Computing Generic Condition" object.uCIFI11.03437.xml103438urn:oma:lwm2m:ext:3438Edge computing time conditionThe uCIFI edge computing time condition object defines the day/time (defined as a CRON rule) at which a particular script should be executed by a device.uCIFI11.03438.xml103439urn:oma:lwm2m:ext:3439Edge computing generic conditionThe uCIFI edge computing generic condition object defines a vendor-specific condition (e.g. when a resource or an object is equal to a particular value) at which a particular script should be executed by the device.uCIFI11.03439.xml103440urn:oma:lwm2m:ext:3440TBCTBCTBC11.00010241urn:oma:lwm2m:x:10241HostDeviceInfoThis LWM2M Object provides a range of host device related information which can be queried by the LWM2M Server. The host device is any integrated device with an embedded cellular radio module.AT&T21.010241.xml1010242urn:oma:lwm2m:x:102423-Phase Power MeterThis Object provides the information to represent a generic 3-Phase Power Meter.Odins21.010242.xml1010243urn:oma:lwm2m:x:10243Single-Phase Power MeterThis Object provides the information to represent a generic Single-Phase Power Meter.Odins21.0version_history/10243-1_0.xml1010243urn:oma:lwm2m:x:10243:2.0Single-Phase Power MeterThis Object provides the information to represent a generic Single-Phase Power Meter.Odins22.010243.xml1010244urn:oma:lwm2m:x:10244VehicleControlUnitThis Object provides the information to represent a generic VCU(vehicle control unit).Works System21.010244.xml1010245urn:oma:lwm2m:x:10245Relay ManagementThis LWM2M Object provides a range of eNB related measurements and parameters of which several are changeable. Furthermore, it includes Resources to enable/disable the eNB.Vodafone Group Services Ltd21.010245.xml1010246urn:oma:lwm2m:x:10246CrowdBox MeasurementsThis LWM2M Object provides CrowdBox-related measurements such as serving cell parameters, backhaul timing advance, and neighbour cell reports.Vodafone Group Services Ltd21.010246.xml1010247urn:oma:lwm2m:x:10247Neighbour Cell ReportThis LWM2M Object provides the neighbour cell report. The CrowdBox Measurements Object and the Connected UE Report Object have both Objlnk Resources pointing to this Object.Vodafone Group Services Ltd21.010247.xml1010248urn:oma:lwm2m:x:10248Connected UE MeasurementsThis LWM2M Object provides a range of measurements of connected UEs and provides an Object link to the Connected UE report.Vodafone Group Services Ltd21.010248.xml1010249urn:oma:lwm2m:x:10249 Connected UE ReportThis LWM2M Object provides a range of information related to the connected UEs.Vodafone Group Services Ltd21.010249.xml1010250urn:oma:lwm2m:x:10250App Data ContainerThis LWM2M Object is used for reporting application data of a device.Huawei Technologies Co., Ltd.21.010250.xml1010251urn:oma:lwm2m:x:10251AT CommandUsed to execute an AT command on a cellular modemCisco21.010251.xml1010252urn:oma:lwm2m:x:10252ManifestThis object provides a range of information related to updating packages on a deviceARM Limited21.010252.xml1010253urn:oma:lwm2m:x:10253Confidential DataThis LWM2M Object is used for reporting data, but in a confidential wayLab R&D Atos Pessac21.010253.xml1010254urn:oma:lwm2m:x:10254:1.0Current Loop InputThis LWM2M Object provides a representation of a current loop sensor, which indicates the value emitted by a current source.World-Direct eBusiness21.010254.xml1010255urn:oma:lwm2m:x:10255Device MetadataARM Limited21.010255.xml1010256urn:oma:lwm2m:x:10256ECID-Signal Measurement InformationThis LWM2M Object provides ECID signal measurements of a device.Huawei Technologies21.010256.xml1010257urn:oma:lwm2m:x:10257Heat / Cooling meterThis Object provides the information to represent a generic (district) heat or cooling meterComsel System Ltd21.010257.xml1010258urn:oma:lwm2m:x:10258Current Loop OutputThis LWM2M Object provides a representation of a current loop source, which may be used to carry control signals.World-Direct eBusiness21.010258.xml1010259urn:oma:lwm2m:x:10259System LogThis object provides read access to log buffers as well as limited configuration of logging services.Casa Systems21.010259.xml1010260urn:oma:lwm2m:x:10260Runtime DatabaseThis object allows manipulation of Runtime Database variables. Object deprecated with version 2.0 due to incorrect Type/Operation combination.Casa Systems21.0version_history/10260-1_0.xml1010260urn:oma:lwm2m:x:10260:2.0RDBThis object allows manipulation of Runtime Database variables.Casa Systems22.010260.xml1010262urn:oma:lwm2m:x:10262Interval Data DeliveryThe Interval Data Delivery object provides an optimised means for managing the delivery of interval data from multiple Interval Data Object instances. South East Water Corporation21.010262.xml1010263urn:oma:lwm2m:x:10263Event Data DeliveryThe Event Data Delivery object provides a simple means for managing the delivery of event data from multiple Event Data Object instances.South East Water Corporation21.010263.xml1010264urn:oma:lwm2m:x:10264Delivery ScheduleThe Delivery Schedule object provides a means for controlling the periodic delivery of interval and event data to the LwM2M server.South East Water Corporation21.010264.xml1010265urn:oma:lwm2m:x:10265Leakage Detection ConfigurationThe leakage detection configuration object provides a means for configuring the timing and sampling frequency of a vibration based network leak detectorSouth East Water Corporation21.010265.xml1010266urn:oma:lwm2m:x:10266Water Flow ReadingsMeasures the flow of water in regular intervalsSouth East Water Corporation21.010266.xml1010267urn:oma:lwm2m:x:10267Daily Maximum Flow Rate ReadingsMeasures the maximum flow rate and its time stamp for specified periodSouth East Water Corporation21.010267.xml1010268urn:oma:lwm2m:x:10268Temperature ReadingsPeriodic temperature measurementsSouth East Water Corporation21.010268.xml1010269urn:oma:lwm2m:x:10269Pressure ReadingsPeriodic pressure measurementsSouth East Water Corporation21.010269.xml1010270urn:oma:lwm2m:x:10270Battery Level ReadingsPeriodic battery level measurementsSouth East Water Corporation21.010270.xml1010271urn:oma:lwm2m:x:10271Communications Activity Time ReadingsMeasures the total duration that the meter was activating its radio for packet transmission or receipt for the period. Used to monitor for excess poower usage over time.South East Water Corporation21.010271.xml1010272urn:oma:lwm2m:x:10272Water Meter Customer Leakage AlarmA binary flag indicating continual usage (e.g. greater than 5 L/h for 24 hours and the flow never returning to zero at any time).South East Water Corporation21.010272.xml1010273urn:oma:lwm2m:x:10273Water Meter Reverse Flow AlarmAn alarm indicating reverse flow through the pipe. Also supports delivery of the approximate volume of water flowing in the reverse direction in the preceding period.South East Water Corporation21.010273.xml1010274urn:oma:lwm2m:x:10274Water Meter Empty Pipe AlarmAn alarm when meter detects there is no liquid in the pipeSouth East Water Corporation21.010274.xml1010275urn:oma:lwm2m:x:10275Water Meter Tamper AlarmDetects interference from strong magnetic field or other electrical sources. If this is not relevant for ultrasonic meters then the tamper alarm may be used to indicate someone attempting to open the physical enclosure or other options the manufacturer may present.South East Water Corporation21.010275.xml1010276urn:oma:lwm2m:x:10276Water Meter High Pressure AlarmWhere supported by the meter this is an alarm that should be raised if the meter detects pressure above a pre-configured threshold.South East Water Corporation21.010276.xml1010277urn:oma:lwm2m:x:10277Water Meter Low Pressure AlarmWhere supported by the meter this is an alarm that should be raised if the meter detects pressure below a pre-configured threshold.South East Water Corporation21.010277.xml1010278urn:oma:lwm2m:x:10278High Temperature AlarmWhere supported by the meter this is an alarm that should be raised if the meter detects temperature above a pre-configured threshold. When the temperature drops below the clear threshold, the alarm should be cleared.South East Water Corporation21.010278.xml1010279urn:oma:lwm2m:x:10279Low Temperature AlarmWhere supported by the meter this is an alarm that should be raised if the meter detects temperature below a pre-configured threshold. When the temperature rises above the clear threshold, the alarm should be clearedSouth East Water Corporation21.010279.xml1010280urn:oma:lwm2m:x:10280Water Network Leak AlarmAll meters must support the following default configuration. This alarm will be based on the frequency output of the vibration sensor/accelerometer on the SEW Daughter board. When a frequency is identified that has the characteristics of an upstream network leak, and its amplitude is above the defined threshold, the meter will report this as a network leak alarm.South East Water Corporation21.010280.xml1010281urn:oma:lwm2m:x:10281Low Battery Alarm This Alarm is raised when the battery voltage drops below a defined levelSouth East Water Corporation21.010281.xml1010282urn:oma:lwm2m:x:10282Daughter Board Failure AlarmThis binary status should indicate that the meter MCU can no longer communicate with a daughter boardSouth East Water Corporation21.010282.xml1010283urn:oma:lwm2m:x:10283Device Reboot EventThis binary status should indicate that the meter MCU can no longer communicate with a daughter boardSouth East Water Corporation21.010283.xml1010284urn:oma:lwm2m:x:10284Time Synchronisation EventThis event records the fact that the device has rebootedSouth East Water Corporation21.010284.xml1010286urn:oma:lwm2m:x:10286App Fota ContainerThis LWM2M Object is used to download the firmware package of a device's application.Huawei21.010286.xml1010290urn:oma:lwm2m:x:10290Voltage LoggingPeriodic voltage measurements that are logged into CBOR structure payloadSouth East Water Corporation21.010290.xml1010291urn:oma:lwm2m:x:10291Voltage TransientObject for sampling high frequency values (in this case Voltage readings) in order to aggregate them and summarize them (Avg, Max, Min) and to then time-stamp and log these aggregates for packaging and transmission to the server. This allows for efficient data transfer of high frequency data, without the need to send huge amounts of raw data over the air.South East Water Corporation21.010291.xml1010292urn:oma:lwm2m:x:10292Pressure TransientObject for measuring high frequency pressure readings and summarizing/logging them at defined intervals. This way, the raw data does not need to be sent over the air, and instead just the Average , Maximum and Minimum values for the intervalSouth East Water Corporation21.010292.xml1010299urn:oma:lwm2m:x:10299HostDeviceThis LWM2M Object provides a range of host device related information which can be queried by the LWM2M Server. The host device is any integrated device with an embedded cellular radio module.Verizon Wireless21.010299.xml1010300urn:oma:lwm2m:x:10300LWM2M Meta Object Use this meta object to provide one or more locations hosting XML data
model definitions for reusable or private and vendor-specific devices,
such as those in the range 26241-42768.TAU21.010300.xml1010301urn:oma:lwm2m:x:10301TBCTBCTBC21.00010302urn:oma:lwm2m:x:10302TBCTBCTBC21.00010303urn:oma:lwm2m:x:10303TBCTBCTBC21.00010304urn:oma:lwm2m:x:10304TBCTBCTBC21.00010305urn:oma:lwm2m:x:10305TBCTBCTBC21.00010308urn:oma:lwm2m:x:10308AT&T Connectivity ExtensionThe AT&T Connectivity Extension Object will be used to gather information describing the UE and the operating state of the UE. The AT&T Connectivity Extension Object is an open and standard object used by AT&T.AT&T21.0version_history/10308-1_0.xml1010308urn:oma:lwm2m:x:10308:2.0AT&T Connectivity ExtensionThe AT&T Connectivity Extension Object will be used to gather information describing the UE and the operating state of the UE. The AT&T Connectivity Extension Object is an open and standard object used by AT&T.AT&T22.010308.xml1010309urn:oma:lwm2m:x:10309ShareparkinglotThis LwM2M Object provides the keying material of our technology product-ShareParkingLock.XiangYiIOT Technologies21.010309.xml1010310urn:oma:lwm2m:x:10310TBCTBCTBC21.00010311urn:oma:lwm2m:x:10311Solar RadiationThis Object is used to report solar irradiance (SI), i.e. power per unit area received from the Sun in the form of electromagnetic radiation, on a planar surface measured by a pyranometer or similar instrument. A pyranometer measures solar irradiance from the hemisphere above within a wavelength range 0.3 um to 3 um. For example, the application of solar radiation measurement can be meterological networks and solar energy applications.Vaisala21.0version_history/10311-1_0.xml1010311urn:oma:lwm2m:x:10311:1.1Solar RadiationThis Object is used to report solar irradiance (SI), i.e. power per unit area received from the Sun in the form of electromagnetic radiation, on a planar surface measured by a pyranometer or similar instrument. A pyranometer measures solar irradiance from the hemisphere above within a wavelength range 0.3 um to 3 um. For example, the application of solar radiation measurement can be meterological networks and solar energy applications.Vaisala21.110311.xml1010312urn:oma:lwm2m:x:10312TBCTBCTBC21.00010313urn:oma:lwm2m:x:10313Gas ReadingsObject to periodically log readings from any gas sensor (eg H2S, VOCx, methane etc)South East Water21.010313.xml1010314urn:oma:lwm2m:x:10314ParticulatesThis object should be used to report the concentration of particulates, for example a measurement of a particulates air quality sensor. It also provides resources for minimum/maximum measured values and the minimum/maximum range that can be measured by the particulate sensor. An example measurement unit is microgrammes per cubic metre ug/m3.OpenLX SP Ltd21.010314.xml1010315urn:oma:lwm2m:x:10315RobotThis LWM2M Object includes robot information and links to the location object.CloudMinds21.010315.xml1010316urn:oma:lwm2m:x:10316RCUThis LWM2M Object includes RCU(Robotic Control Unit) information and the link to RCU APPs.CloudMinds21.010316.xml1010317urn:oma:lwm2m:x:10317TBCTBCTBC21.00010318urn:oma:lwm2m:x:10318RCU PMThis LWM2M Object includes RCU(Robotic Control Unit) PM information(counter and guage).CloudMinds21.010318.xml1010319urn:oma:lwm2m:x:10319RCU ControlThis LWM2M Object includes all operations on RCUs.CloudMinds21.010319.xml1010320urn:oma:lwm2m:x:10320CCUThis LWM2M Object includes CCU(Central Control Unit) information and the link to CCU APPs.CloudMinds21.010320.xml1010321urn:oma:lwm2m:x:10321TBCTBCTBC21.00010322urn:oma:lwm2m:x:10322CCU PMThis LWM2M Object includes CCU PM(counter and gauge).CloudMinds21.010322.xml1010323urn:oma:lwm2m:x:10323CCU ControlThis LWM2M Object includes all operations on CCUs.CloudMinds21.010323.xml1010324urn:oma:lwm2m:x:10324ECUThis LWM2M Object includes ECU(End Control Unit) information.CloudMinds21.010324.xml1010325urn:oma:lwm2m:x:10325TBCTBCTBC21.00010326urn:oma:lwm2m:x:10326Robot PMThis LWM2M Object includes PM(counter and gauge) supported by all robots.CloudMinds21.010326.xml1010327urn:oma:lwm2m:x:10327CompressorThis LWM2M Object includes the Compressor information.CloudMinds21.010327.xml1010328urn:oma:lwm2m:x:10328SCA PMThis LWM2M Object includes all PM items belongs to a specific SCA.CloudMinds21.010328.xml1010329urn:oma:lwm2m:x:10329Robot ControlThis LWM2M Object includes all operations on robots.CloudMind21.010329.xml1010330urn:oma:lwm2m:x:10330Network InfoThis LWM2M Object includes network status related information.CloudMinds21.010330.xml1010331urn:oma:lwm2m:x:10331Robot Service InfoThis LWM2M Object includes robot service related information.CloudMinds21.010331.xml1010332urn:oma:lwm2m:x:10332Robot Selfcheck InfoThis LWM2M Object includes robot selfcheck result.CloudMinds21.010332.xml1010333urn:oma:lwm2m:x:10333PM ThresholdHere defines all items needed in PM Threshold management.CloudMinds21.010333.xml1010334urn:oma:lwm2m:x:10334Robot AlarmHere lists all items of an alarm reported by the robot.CloudMinds21.010334.xml1010335urn:oma:lwm2m:x:10335EventHere lists all items of an event reported by the robot.CloudMinds21.010335.xml1010336urn:oma:lwm2m:x:10336MICThis LWM2M Object includes MIC array information.CloudMinds21.010336.xml1010337urn:oma:lwm2m:x:10337SCAThis LWM2M Object includes SCA information.CloudMinds21.010337.xml1010338urn:oma:lwm2m:x:10338SpeakerThis LWM2M Object includes speaker information.CloudMinds21.010338.xml1010339urn:oma:lwm2m:x:10339Tripod HeadThis LWM2M Object includes Tripod Head information.CloudMinds21.010339.xml1010340urn:oma:lwm2m:x:10340CameraThis LWM2M Object includes camera information.CloudMinds21.010340.xml1010341urn:oma:lwm2m:x:10341GPSThis LWM2M Object includes GPS information.CloudMinds21.010341.xml1010342urn:oma:lwm2m:x:10342IMUThis LWM2M Object includes IMU(Inertial Measurement Unit) information.CloudMinds21.010342.xml1010343urn:oma:lwm2m:x:10343LiDARThis LWM2M Object includes LiDAR information.CloudMinds21.010343.xml1010344urn:oma:lwm2m:x:10344ArmThis LWM2M Object includes arm information.CloudMinds21.010344.xml1010345urn:oma:lwm2m:x:10345LegThis LWM2M Object includes leg information.CloudMinds21.010345.xml1010346urn:oma:lwm2m:x:10346ServomotorThis LWM2M Object includes Servomotor information.CloudMinds21.010346.xml1010347urn:oma:lwm2m:x:10347ScreenThis LWM2M Object includes robot screen information.CloudMinds21.010347.xml1010348urn:oma:lwm2m:x:10348WheelThis LWM2M Object includes wheel information.CloudMinds21.010348.xml1010349urn:oma:lwm2m:x:10349ChassisThis LWM2M Object includes chassis information.CloudMinds21.010349.xml1010350urn:oma:lwm2m:x:10350LightThis LWM2M Object includes light information.CloudMinds21.010350.xml1010351urn:oma:lwm2m:x:10351DoorThis LWM2M Object includes the door information.CloudMinds21.010351.xml1010352urn:oma:lwm2m:x:10352Thermal ImagerThis LWM2M Object includes the Thermal Imager information.CloudMinds21.010352.xml1010353urn:oma:lwm2m:x:10353Warning LightThis LWM2M Object includes Warning Light information.CoudMinds21.010353.xml1010354urn:oma:lwm2m:x:10354APPThis LWM2M Object includes the APP information.CloudMinds21.010354.xml1010355urn:oma:lwm2m:x:10355General InfoThis LWM2M Object contains the referrence to all general info objects of the robot.CloudMinds21.010355.xml1010356urn:oma:lwm2m:x:10356Service InfoThis LWM2M Object contains the referrence to all objects containing service info.CoudMinds21.010356.xml1010357urn:oma:lwm2m:x:10357PMThis LWM2M Object contains the referrence to all PM objects.CloudMinds21.010357.xml1010358urn:oma:lwm2m:x:10358Fan PMThis LWM2M Object includes all PM items belongs to Fans.CloudMinds21.010358.xml1010359urn:oma:lwm2m:x:10359LockThis LWM2M Object includes the Lock information.CloudMinds21.010359.xml1010360urn:oma:lwm2m:x:10360Ultrasonic SensorThis LWM2M Object includes Ultrasonic Sensor information.CloudMinds21.010360.xml1010361urn:oma:lwm2m:x:10361Collision SensorThis LWM2M Object includes Collision Sensor information.CloudMinds21.010361.xml1010362urn:oma:lwm2m:x:10362Drop SensorThis LWM2M Object includes Drop Sensor information.CloudMinds21.010362.xml1010363urn:oma:lwm2m:x:10363Temperature SensorThis LWM2M Object includes Temperature Sensor information.CloudMinds21.010363.xml1010364urn:oma:lwm2m:x:10364Humidity SensorThis LWM2M Object includes Humidity Sensor information.CloudMinds21.010364.xml1010365urn:oma:lwm2m:x:10365Gas-Dust SensorThis LWM2M Object includes Gas-Dust information.CloudMinds21.010365.xml1010366urn:oma:lwm2m:x:10366FanThis LWM2M Object includes Fan information.CloudMinds21.010366.xml1010367urn:oma:lwm2m:x:10367TBCTBCTBC21.00010368urn:oma:lwm2m:x:10368SpringMotorThis LWM2M Object includes SpringMotor information.CloudMinds21.010368.xml1010369urn:oma:lwm2m:x:10369MCUThis LWM2M Object includes MCU information.CloudMinds21.010369.xml1010370urn:oma:lwm2m:x:10370TBCTBCTBC21.00010371urn:oma:lwm2m:x:10371Reboot StatusThis object provides features allowing to monitor Reboot and Reset Factory operation from LWM2M Device object.Sierra Wireless21.010371.xml1010372urn:oma:lwm2m:x:10372TBCTBCTBC21.00018830urn:oma:lwm2m:x:18830MQTT BrokerThis LwM2M Object provides the information to connect to an MQTT Broker i.e. URI, configuration, and keying material.IoTerop21.018830.xml1018831urn:oma:lwm2m:x:18831MQTT PublicationThis LwM2M Object is used to configure data reporting over MQTT.IoTerop21.018831.xml10