Share via

Putting the Provisioning XML on an OMA Client Provisioning Server

  • Article

6/2/2010

You can push a provisioning XML file over-the-air (OTA) to Windows Mobile-based devices using a one-way Wireless Application Protocol (WAP) push and the OMA Client Provisioning protocol.

You will perform the following steps:

  1. Create an OMA Client Provisioning XML file
  2. Push the XML OTA Using an OMA Client Provisioning Server

Assumptions

XML file must be UTF-8 encoded.

Step 1: Create an OMA Client Provisioning XML File

To Create an OMA Client Provisioning XML file

  1. Copy the following information into a text editor:

    <wap-provisioningdoc>
  <characteristic type="Sync">
    <characteristic type="Settings">
      <parm name="HeartbeatDefault " value="480"/>
      <parm name="HeartbeatIncrement" value="300"/>
      <parm name="HeartbeatMax" value="1680"/>
      <parm name="HeartbeatMin " value="480"/>
    </characteristic>
  </characteristic>
</wap-provisioningdoc>

  2. Change the values to the appropriate setting. For more information, see Parameters Used for Dynamically Adjusting the Heartbeat Interval section in Heartbeat Interval Adjustment.

  3. Save the XML document as an ASCII file named <filename>.provxml. For example, directpush_300.provxml

Note

Microsoft recommends that you use a three-digit number in the name of your .provxml files in ROM, so that there are an adequate number of ordinals to identify successive versions of the file.

  1. You should test that the provisioning XML makes the desired changes to a Windows Mobile-based device similar to the ones that you want to update.

Step 2: Push the XML OTA Using an OMA Client Provisioning Server

To Push the XML OTA Using an OMA Client Provisioning Server

  1. Put the provisioning XML file on the OMA Client Provisioning Server to be ready for download.

  2. For security, depending on how OTA bootstrap is enabled, sign the message with the appropriate security method as defined in the OMA Provisioning Bootstrap Specification Version 1.1. For Global System for Mobile Communications (GSM) Short Message Service (SMS), the network PIN is the International Mobile Subscriber Identity (IMSI) number on the Subscriber Identity Module (SIM) card.

  3. Send the XML file to the Push Proxy Gateway through a Password Authentication Protocol (PAP) constructed as a WAP push message.

  4. At the Push Proxy Gateway, use the WAP push OTA protocol to send the message to the device over the air through the appropriate OTA bearer — for example, GSM SMS. The device supports a WAP non-secure connectionless push.

  5. The device initiates a DM session with the OMA Client Provisioning Server and downloads the Provisioning XML.

  6. The customer will receive a configuration update success message in Inbox.

See Also

Concepts

How to Configure the Device