This section describes the rearranged data model for updating WAP connectivity data. The provisioning document type definition (PROV DTD) that this model is based on is defined in the OMA Client Provisioning specification, Provisioning Content (OMA-WAP-ProvCont-v1_1-20050428-C), available from this OMA Web site .

The rearranged model more clearly reflects the hierarchical structure of WAP connectivity data, as described in the following list:

• PROXY-ID, PHYSICAL-PROXY-ID, and NAPIDparms in the PXLOGICAL, PXPHYSICAL, and NAPDEFcharacteristic elements are converted to sub-characteristic elements whose type value is the value of these parms.
  
  
• Because of the translation process, the data must be found by using PROXY-ID, PHYSICAL-PROXY-ID, NAPID, or the value of the nameattribute of the parm before certain actions can be taken on them.
  
  
• Use the Microsoft extended provisioning DTD to change, add, or delete the parameters.
  
  

  Note:
  This XML file can be sent directly to Windows Mobile devices by means of an over-the-air (OTA) WAP push over the Global System for Mobile Communications (GSM) Short Message Service (SMS) network.

For examples of how to apply the rearranged data model for updating WAP connectivity data, see PXLOGICAL Configuration Service Provider Examples for OMA Client Provisioningand NAPDEF Configuration Service Provider Examples for OMA Client Provisioning.

See Also