Update Standard WAP Connectivity Parameters
This section describes the rearranged data model for updating Wireless Application Protocol connectivity data. While Windows Mobile Version 5.0 was under development, the PROV DTD defined in the OMA Client Provisioning Content Specification, OMA-WAP-ProvCont-v1_1-20021112-C, was used as a guideline.
The rearranged model more clearly reflects the hierarchical structure of Wireless Access Protocol (WAP) connectivity data, as described in the following list:
PROXY-ID, PHYSICAL-PROXY-ID, and NAPID parms in the PXLOGICAL, PXPHYSICAL, and NAPDEF characteristic elements are converted to sub-characteristic elements whose type value is the value of these parms.
Because of this translation process, they must be found by using PROXY-ID, PHYSICAL-PROXY-ID, NAPID, or the value of the name attribute of the parm before taking certain actions on them.
Use the Microsoft extended provisioning document type definition (DTD) to change, add, or delete the parameters.
Note This XML file can be sent directly to Windows Mobile-based devices by means of over-the-air Wireless Access Protocol (WAP) push over the Global System for Mobile Communications (GSM) Short Message Service (SMS) network.
See PXLOGICAL Configuration Service Provider Examples for OMA Client Provisioning and NAPDEF Configuration Service Provider Examples for OMA Client Provisioning for examples showing how to apply the rearranged data model for updating Wireless Access Protocol (WAP) connectivity data.
See Also
OMA Client Provisioning XML File Examples | WAP Connectivity Parameters Processed by the Device | WAP Connectivity Bootstrap Message Example | PXLOGICAL Configuration Service Provider | PXLOGICAL Configuration Service Provider Examples for OMA Client Provisioning | NAPDEF Configuration Service Provider | NAPDEF Configuration Service Provider Examples for OMA Client Provisioning
Send Feedback on this topic to the authors