OMA DM Standards and Extensions

  • Article

Send Feedback

The following table shows the OMA standards that Windows Mobile Version 5.0 uses:

General area OMA standard that is supported
Data Transportation and Session
  • Remote DM Server initiation notification via WAP Push over Short Message Service (SMS).
  • Remote bootstrap by using WAP Push over SMS.
  • Remote HTTPS DM session over SSL
Bootstrap
  • WAP profile (with the exception of OMA Client Provisioning(CP) XML OTA bootstrap message).
DM protocol commands The following list shows the commands that are used by the device:
  • Add (Implicit Add)..
  • Alert (DM alert):   server-initiated mgmt alert (1200),   session abort (1223)
  • Atomic
  • Delete
  • Exec.
  • Get
  • Replace
  • Result
  • Sequence
  • Status

For more information about these commands, see OMA DM Protocol Command Elements.

If an XML element that is not a valid OMA DM command is under one of the following elements, the status code 400 is returned for that element:

  • SyncBody
  • Atomic
  • Sequence

If no CmdID is provided in the DM command, the client returns blank in the status element and the status code 400.

If Atomic elements are nested, the following status codes are returned:

  • The nested Atomic command returns 500.
  • The parent Atomic command returns 507.

For more information about the Atomic command, see see OMA DM Protocol Command Elements.

The security check for the Add command is done at the child level. This is because access rights can be pre-assigned to nodes that are not created.

LocURI cannot start with "/".

Meta xml tag in SyncHdr is ignored by the device.
OMA DM standard objects
  • OMA DM Server Account (DMAcc) object
  • DevInfo
  • DevDetail
Security
  • Authenticate DM server initiation notification SMS message
  • Application layer Basic and MD5 client authentication
  • Authenticate server with MD5 credential at application level
  • SSL at transport with certificate based server authentication
Format

  • MultipleString data type is treated as chr format in OMA DM. Each string is terminated with Unicode 0xF000.

    For more information, see Metabase Datatypes.

  • When you query a time format node, the Universal Time (UTC, also known as GMT, or Greenwich Mean Time) format is returned regardless whether it is created or replaced with UTC or local time that includes time zone information.
  • Microsoft has extended the datatypes with the following additions:
    • time
    • date
Nodes In the OMA tree, the following rules apply for the node name:
  • "." can be part of the node name.
  • The node name cannot be empty.
  • The node name cannot be only the asterisk (*) character.

For more information about nodes, see OMA Device Management Tree.
Provisioning Files If an XML element that is not a valid OMA DM command is under SyncBody, the status code 400 is returned for that element.

The Device ID used in SyncHdr LocURI and DevID in the DevInfo object is an application-specific global unique device identifier.

Note   To represent a Unicode string as a URI, first encode the string as UTF-8. Then encode each of the UTF-8 bytes using URI encoding.

Microsoft Extensions to OMA Standards

The following list shows the custom properties that Microsoft has added:

Property Description
AccessRole Defines the access role for a node. For information about the possible security roles and corresponding role values, see Security Roles.
RWAccess Defines read/write permissions. This is translated to rw-access in the Metabase. For more information, see Metabase and OMA DM.
MaxValue Defines the maximum value a leaf node integer value, defined in int format. For more information, see Metabase and OMA DM.
MinValue Defines the minimum value a leaf node integer value, defined in int format. For more information, see Metabase and OMA DM.
MaxLength Defines the maximum size of a leaf node text value. For more information, see Metabase and OMA DM.
Multiple Defines whether the user can select multiple options. For more information, see Metabase and OMA DM.

The following table shows how Microsoft extended other OMA DM Standards.

Standard Extension
Bootstrap DM account using the OMA Client Provisioning w7 APPLICATION characteristic Role element has been added under the APPLICATION characteristic. For more information, see w7 APPLICATION Configuration Service Provider.
DDF Windows Mobile Version 5.0 extended the DDF files to include Microsoft custom property descriptions.
DMAcc Configuration Service Provider Added the Ext/Microsoft/Role node. For more information, see DMAcc Configuration Service Provider.

The following table shows how Microsoft extended the OMA DM tree to contain Microsoft custom objects. These objects are in addition to the OMA DM objects DevDetail, DevInfo, DMAcc, and FwUpdate.

Object Description
Access Configures network connections on the device and configures the URL mapping table that determines the network where the URL resides. For more information, see ACCESS Configuration Service Provider.
Bluetooth Enables the server to remotely configure the Bluetooth operation mode.
Note   This is supported for Windows Mobile-based Smartphones only.

For more information, see Bluetooth Configuration Service Provider.
CertificateStore Enables the server to remotely add security certificates and role masks to the device's certificate store.

For more information, see CertificateStore Configuration Service Provider.
Clock Enables the server to remotely set the time and date on the device.
Note   This is supported for Windows Mobile-based Smartphones only.

For more information, see Clock Configuration Service Provider.
CMPLANNER Enables the server to remotely configure Connection Planner settings, including cache time, retry count and connection preferences for each destination network.

For more information, see CMPLANNER Configuration Service Provider.
DeviceInformation Enables the server to query general device information, such as the OS version and usage of memory.
Note   This is supported for Windows Mobile-based Smartphones only.

For more information, see DeviceInformation Configuration Service Provider.
Email2 Enables the server to remotely configure the email settings

For more information, see EMAIL2 Configuration Service Provider.
Home Enables the server to remotely configure the Home screen on the device.
Note   This is supported for Windows Mobile-based Smartphones only.

For more information, see Home Configuration Service Provider.
LoaderRevocation Enables the server to remotely add, remove, and query certificate or binary hashes in the revocation list.

For more information, see LoaderRevocation Configuration Service Provider.
Locale Enables the server to remotely configure regional settings on the device.
Note   This is supported for Windows Mobile-based Smartphones only.

For more information, see Locale Configuration Service Provider.
NAP Configures the data and cellular connections on the device.

For more information, see NAP Configuration Service Provider.
Obex Enables the server to remotely configure the Obex server, which performs Bluetooth and infrared beaming.
Note   This is supported for Windows Mobile-based Smartphones only.

For more information, see Obex Configuration Service Provider.
Proxy Enables the server to configure proxy networks. Each numbered proxy node configures a proxy connection.

For more information, see PROXY Configuration Service Provider.
Registry Enables the server to remotely configure the registry on the device.

For more information, see Registry Configuration Service Provider.
ROMPackage Used by the server to query the device ROM packages current version that is used by firmware update.

For more information, see ROMPackage Configuration Service Provider.
SecurityPolicy Enables the OMA DM server to remotely manage device security policies

For more information, see SecurityPolicy Configuration Service Provider.
Sounds Enables the server to remotely configure the sounds associated with various events on the device.
Note   This is supported for Windows Mobile-based Smartphones only.

For more information, see Sounds Configuration Service Provider.
SpeedDial Enables the server to remotely populate the speed dial entries prior to end user delivery for Windows Mobile-based devices.

For more information, see SpeedDial Configuration Service Provider.
Sync Enables the server to remotely configure Microsoft Server Sync settings

For more information, see Sync Configuration Service Provider.
VPN Enables the server to remotely configure the Virtual Private Network (VPN) entries on the device. Users can use VPN to connect to a corporate network using an Internet.

For more information, see VPN Configuration Service Provider.
Wi-Fi Enables the server to remotely configure or query Wi-Fi settings.

For more information, see Wi-Fi Configuration Service Provider.

For more information about how the associated configuration service providers are supported, see Configuration Service Providers Managed over OMA DM.

See Also

OMA Device Management | Configuration Service Providers Managed over OMA DM

Send Feedback on this topic to the authors

Feedback FAQs

© 2006 Microsoft Corporation. All rights reserved.