Device Management

OMA Device Management Working Group


The Device Management (DM) Working Group (WG) specifies protocols and mechanisms to achieve the management of mobile devices, services access and software on connected devices for mobile networks and the Internet of Things (IoT).

See the OMA DM Q&A Document

Bringing Value to the Mobile Industry

Since 2002, OMA DM Working Group has released a suite of specifications which includes 20+ mobile service enablers and more than 60 Management Objects providing simple, reliable and cost effective ways to deploy new applications and services minimizing the risk. An additional 20+ Management Objects have been defined by other standards organizations, which cooperate with OMA to avoid fragmentation and duplication.

OMA DM technologies easily manage converged and multi-mode devices on any network, including devices that do not have a SIM card, as well as resource constrained devices. This extensibility is one of the key benefits of OMA DM, making it ideal for M2M communication scenarios.

Device Management Technologies

OMA DM Specification work started in June 2002 and successfully evolved up to version v1.3 in 2011.
The OMA DM specifications define the protocols and the mechanisms allowing an OMA DM Server to deliver configuration parameters to an OMA DM Client, by using a defined set of “DM Commands” for various management procedures to be executed inside a well-defined and secure environment (the “DM Session”).

The OMA DM Client exposes the device internal data to the OMA DM Server in the form of a hierarchic tree known as the “DM Tree”: it is made up of different building blocks (or sub-trees) called Management Objects providing specific functionality in the management of devices. In other words, the management of a device feature consists of the management of the DM Tree, which virtualizes the device features and functionalities.

Device Management

Through OMA Device Management, a Management Authority can remotely set parameters, conduct troubleshooting servicing of terminals, install or upgrade software among others.

By using the interfaces specified by the OMA DM Client Framework API, applications running on the device can access the DM Tree and interact with Management Objects and the DM Server, in order to obtain configurations or report data. The DM Server itself, thanks to OMA DM Smartcard specification, may run directly on the Smartcard inserted into the device, saving network bandwidth and connections.

Currently the OMA DM Working Group is finalizing the most recent version of the OMA DM specification, the 2.0 release; this version introduces a significant improvement in terms of complexity, interoperability and cost efficiency to meet the expected market needs. This is achieved by an innovative new protocol, which adopts a number of technologies borrowed from Web Environment (HTTP RESTful methods, JSON serialization and Web Browser Components, for example) plus a simplification in DM Tree access and organization and DM Session transactions.


The OMA DM Working Groups specified a number of Management Objects implementing specific management functions: the most market diffused is certainly the Firmware Update Management Object (FUMO) with over 1.4 billion deployments[2].

Other Management Objects have been specified to support additional functionalities:

  • Software Management (OMA DM SCOMO) allowing not only the installation and the removal of applications on the mobile, but also the retrieval of the inventory of software components already installed on the device
  • Diagnostics and Monitoring (OMA DM DiagMon MO), which enables remote diagnostic, for example to query the device for memory and battery status or to collect radio measures and QoS parameters, and remote monitoring, by defining trap and reports
  • Connectivity (OMA DM ConnMO), which allows the configuration of bearers and proxies
  • Device Capabilities (OMA DM DCMO), which allows a Management Authority to remotely enable and disable device peripherals like cameras, Bluetooth, USB, etc
  • Lock and Wipe (OMA DM LAWMO), which allows to remotely lock and/or wipe the device, for instance when the device is stolen or sold, or when personal or enterprise data are compromised
  • Browser (OMA DM BMO), which allows remote management of browser favorites and settings
  • Virtualization (OMA DM VirMO), which enables remote management of virtual machines running on the device (expected for 3Q 2013)
  • Management Policy (OMA DM Management Policy MO), which allows the deployment on the device of policies which the DM Client can execute and enforce independently: if some events happen, then perform some operations (expected for 2Q 2014)

OMA DM WG also specified Gateway functionality (OMA DM GwMO v1.0), which allows an OMA DM Server to manage devices that:

  • are not directly accessible, for example, because they are deployed behind a firewall
  • can be clustered in a group, for instance when they are deployed in a very large number (like sensors), using fan out mechanisms
  • support other Management protocols than OMA DM

Currently the OMA DM Working group is finalizing the new release of OMA DM GwMO (v1.1), which specifies the Gateway Hierarchical Architecture and Protocol Adaptation for devices supporting Bluetooth, KNX, OpenWebNet, and ZigBee protocols (expected for 3Q 2013).

M2M Technology

Facing the new challenges offered by the market, the DM Working Group with its expertise in remote management addressed the M2M environment with OMA Lightweight M2M protocol, which focuses on constrained cellular and sensor network M2M devices.

Device Management


This enabler[3] specifies simple management interfaces based on IETF standards (CoAP and DTLS with UDP and SMS bindings), with plain text, TLV and JSON serialization for data payload and an Object Model based on manageable Resources (accessible via URI) and Instances concepts (borrowed by OMA DM technology).

OMA LightweightM2M 1.0 was released in 3Q 2013.

OMA Device Management Specifications

EnablerRelease TypeVersionOMA Phase
ProtocolDevice ManagementEnabler Release1.1.2Approved
Client Side Enabler APIReference Release1.0Approved
Device Management Smart CardEnabler Release1.0Approved
Client ProvisioningEnabler Release1.1Approved
White PaperM2M Device ClassificationReference Release1.0Approved
Management Object Design GuidelinesReference Release1.0Approved
Provisioning Objects - Device Management Application Characteristics Management ObjectReference Release1.0.1Approved
Management ObjectBrowserReference Release1.0Approved
ConnectivityReference Release1.0Approved
Device CapabilityEnabler Release1.0Approved
Delta RecordEnabler Release1.0Approved
Diagnostics and MonitoringEnabler Release1.0Approved
Firmware Update Enabler Release1.0.4Approved
Gateway Enabler Release1.0Approved
List of supported MOEnabler Release1.0Approved
Lock And WipeEnabler Release1.0Approved
Management PolicyEnabler Release1.0Draft
SchedulingEnabler Release1.0Approved
Software ComponentEnabler Release1.0Approved
Software and Application ControlEnabler Release1.0Candidate
Virtualization MOEnabler Release1.0Candidate

OMA LightweightM2M (LwM2M) Specifications

EnablerRelease TypeVersionOMA Phase
ProtocolLightweightM2MEnabler Release1.0Candidate


[1] “Studio, progettazione e prototipazione di un protocollo per il Remote Device Management di dispositivi connessi” – Marco Sapienza, University of Catania, April 2013