WBXML and OMA DM
4/8/2010
OMA DM messages transferred between the DM server and client can be encoded and decoded by using WAP Binary XML (WBXML). WBXML compression during the transfer reduces over-the-air (OTA) time.
Windows Mobile 6.5 supports transferring messages in XML or in WBXML. By default, XML is used.
Whether the DM client should use WBXML or XML for the DM package when it communicates with the server is configured during the bootstrap process. It is configured by using the Microsoft custom parameter DefaultEncoding in the following Configuration Service Providers:
- w7 APPLICATION Configuration Service Provider
- DMS Configuration Service Provider
- DMAcc Configuration Service Provider
The OMA DM WBXML token table is defined in the Device Management Representation Protocol specification (OMA-TS-DM_RepPro-V1_2-20060602-C) at this OMA Web site. The SyncML XML tokens are defined in code page 0. The Meta attribute tokens are defined in code page 1.
For backward compatibility, the client supports both OMA DM version 1.1 and OMA DM version 1.2 WBXML token tables. The following table shows the specifications for each OMA DM protocol.
| Protocol | Specifications |
|---|---|
OMA DM version 1.1.2 |
SyncML Representation Protocol, version 1.1.2 (OMA-SyncML-RepPro-V1_1_2-20030612-A) SyncML Meta Information (OMA-SyncML-MetaInfo-V1_1_2-20030612-A[1]) |
OMA DM version 1.2 |
SyncML Representation Protocol (OMA-TS-SyncML-RepPro-V1_2-20050509-C) SyncML Meta Information (OMA-SyncML-MetaInfo-V1_2-20050509-C[1]) |
The public identifier differs between the WBXML for these two protocol versions.
Token assignment for the mapping of the SyncML-related DTDs and element types into WBXML are described in OMA DM specifications. These specifications are available from this OMA Web site.
For more information about WBXML, see WAP Binary XML Content Format Features.
For information about WBXML and custom tokens used in Windows Mobile devices, see WBXML and Windows Mobile Devices.
OMA DM WBXML version support
For WBXML encoding, the public identifier should be consistent with the protocol version that it sets in the DM package:
- For an OMA DM version 1.1 package, use the 1.1 public identifier and token table.
- For an OMA DM version 1.2 package, use the 1.2 public identifier and token table.
For WBXML decoding, the client decodes both versions of OMA DM WBXML token tables, depending on the version of the DM package.
WBXML Encoding and Decoding support
The client supports sending WBXML 1.3 encoded WBXML. The device supports receiving WBXML 1.1, 1.2, and 1.3.
See Also
Concepts
WBXML and Windows Mobile Devices
WAP Binary XML Content Format Features