Provisioning Content Features
Windows Mobile-based Smartphones and Windows Mobile-based Pocket PCs (GSM) Phone Edition can be provisioned over the air. The content of the provisioning file is encoded through Wireless Application Protocol Binary Extensible Markup Language (WBXML) and interpreted on the device. For detailed information about encoding content, see the Open Mobile Alliance (OMA) Provisioning Content Specification Version 1.1, OMA-WAP-ProvCont-v1_1-20021112-C, available from this OMA website.
The following table shows the Push Message features
| Push Message feature | Description |
|---|---|
| ProvCont-CSE-C-001 UTF-8 Character Encoding | Universal Transformation Format 8 (UTF-8) character encoding is implemented as described in "Connectivity Character Set" in the OMA Provisioning Content specification version 1.1 (OMA-WAP-ProvCont-v1_1-20021112-C). |
| ProvCont-CSE-C-005 Processing Reference Content Type (No Meta-Information) | Reference content is processed on Windows Mobile-based devices as described in "Connectivity Character Set" in the OMA Provisioning Content specification version 1.1 (OMA-WAP-ProvCont-v1_1-20021112-C). |
| ProvCont-CSE-C-006 Character Entities | Character entities of the provisioning XML file are encoded as described in "Connectivity Character Set" in the OMA Provisioning Content specification version 1.1 (OMA-WAP-ProvCont-v1_1-20021112-C). |
| ProvCont-CO-C-001 wap-provisioningdoc DTD Is Used | The wap-provisioningdoc document type definition (DTD) is used with the provisioning XML file as described in "Connectivity Reference Information" in the OMA Provisioning Content specification version 1.1 (OMA-WAP-ProvCont-v1_1-20021112-C). |
| ProvCont-CO-C-002 Textual Form of the wap-provisioningdoc (text/vnd.wap.connectivity-xml) | The textual form of the wap-provisioningdoc DTD is implemented as described in "Overview of Data Model" in the OMA Provisioning Content specification version 1.1 (OMA-WAP-ProvCont-v1_1-20021112-C). |
| ProvCont-CO-C-003 wap-provisioningdoc in Tokenized Form (application/vnd.wap.connectivity-wbxml) | The wap-provisioningdoc DTD can be used in tokenized form, as described in "WBXML Encoding" in the OMA Provisioning Content specification version 1.1 (OMA-WAP-ProvCont-v1_1-20021112-C). |
| ProvCont-CO-C-004 MAC Media Type Parameter | The MAC media type parameter is used in the provisioning XML file for conveying security information as described in "Media Type Parameter" in the OMA Provisioning Content specification version 1.1 (OMA-WAP-ProvCont-v1_1-20021112-C).
Note Windows Mobile-based Pocket PCs do not support the quoted text encoded mac attribute. |
| ProvCont-CO-C-005 SEC Media Type Parameter | The SEC media type parameter is used in the provisioning XML file for conveying security information as described in "Media Type Parameter" in the OMA Provisioning Content specification version 1.1 (OMA-WAP-ProvCont-v1_1-20021112-C). |
The wap-provisioningdoc element (ProvContCEA-C-001) is used in the provisioning XML file, as described in "The WAP-PROVISIONINGDOC element" in the OMA Provisioning Content specification version 1.1 (OMA-WAP-ProvCont-v1_1-20021112-C).
- The version attribute (ProvCont-CEA-C-004) of the wap-provisioningdoc element is used in the provisioning XML file, as described in "The WAP-PROVISIONINGDOC element" in the OMA Provisioning Content specification version 1.1 (OMA-WAP-ProvCont-v1_1-20021112-C).
The characteristic element (ProvCont-CEA-C-002) is used in the provisioning XML file, as described in "The CHARACTERISTIC element" in the OMA Provisioning Content specification version 1.1 (OMA-WAP-ProvCont-v1_1-20021112-C).
- The type attribute (ProvCont-CEA-C-005) of the characteristic element is used in the provisioning XML file, as described in "The CHARACTERISTIC element" in the OMA Provisioning Content specification version 1.1 (OMA-WAP-ProvCont-v1_1-20021112-C).
The parm element (ProvCont-CEA-C-003) is used in the provisioning XML file, as described in "The PARM element" in the OMA Provisioning Content specification version 1.1 (OMA-WAP-ProvCont-v1_1-20021112-C).
- The name attribute (ProvCont-CEA-C-006) of the parm element is used in the provisioning XML file, as described in "The PARM element" in the OMA Provisioning Content specification version 1.1 (OMA-WAP-ProvCont-v1_1-20021112-C).
- The value attribute (ProvCont-CEA-C-007) of the parm element is used in the provisioning XML file, as described in "The PARM element" in the OMA Provisioning Content specification version 1.1 (OMA-WAP-ProvCont-v1_1-20021112-C).
The following table shows the various characteristic elements:
| Characteristic | Description |
|---|---|
| ProvCont-CC-C-001 PXLOGICAL Type for Characteristic Elements | A PXLOGICAL type characteristic element is used in the provisioning XML file, as described in "Characteristics of type PXLOGICAL" in the OMA Provisioning Content specification version 1.1 (OMA-WAP-ProvCont-v1_1-20021112-C). |
| ProvCont-CC-C-002 PXPHYSICAL Type for Characteristic Elements | A PXPHYSICAL type characteristic element is used in the provisioning XML file, as described in "Characteristics of type PXPHYSICAL" in the OMA Provisioning Content specification version 1.1 (OMA-WAP-ProvCont-v1_1-20021112-C). |
| ProvCont-CC-C-004 NAPDEF Type for Characteristic Elements | A NAPDEF type characteristic element is used in the provisioning XML file, as described in "Characteristics of type NAPDEF" in the OMA Provisioning Content specification version 1.1 (OMA-WAP-ProvCont-v1_1-20021112-C). |
| ProvCont-CC-C-005 NAPAUTHINFO Type for Characteristic Elements | A NAPAUTHINFO type characteristic element is used in the provisioning XML file, as described in "Characteristics of type NAPAUTHINFO" in the OMA Provisioning Content specification version 1.1 (OMA-WAP-ProvCont-v1_1-20021112-C). |
| ProvCont-CC-C-006 PORT Type for Characteristic Elements | A PORT type characteristic element is used in the provisioning XML file, as described in "Characteristics of type PORT" and "The Use of PORT Characteristics" in the OMA Provisioning Content specification version 1.1 (OMA-WAP-ProvCont-v1_1-20021112-C). |
| ProvCont-CC-C-008 BOOTSTRAP Type for Characteristic Elements | A BOOTSTRAP type characteristic element is used in the provisioning XML file, as described in "Characteristics of type BOOTSTRAP" in the OMA Provisioning Content specification version 1.1 (OMA-WAP-ProvCont-v1_1-20021112-C). |
The following table shows features in the PXLOGICAL characteristic:
| PXLOGICAL feature | Description |
|---|---|
| ProvCont-CPL-C-001 PROXY-ID Parameter for PXLOGICAL Characteristic Elements | The PROXY-ID parameter for PXLOGICAL characteristic elements is used in the provisioning XML file for defining one logical proxy, as described in "Parameters for PXLOGICAL characteristics" in the OMA Provisioning Content specification version 1.1 (OMA-WAP-ProvCont-v1_1-20021112-C).
Windows Mobile-based devices provide continuous provisioning by allowing PROXY-ID to also be in the Type field of a child characteristic of a PXLOGICAL characteristic element. |
| ProvCont-CPL-C-003 NAME Parameter for PXLOGICAL Characteristic Elements | The NAME parameter for PXLOGICAL characteristic elements is used in the provisioning XML file for indicating an identity of the configuration element, as described in "Parameters for PXLOGICAL characteristics" in the OMA Provisioning Content specification version 1.1 (OMA-WAP-ProvCont-v1_1-20021112-C). |
| ProvCont-CPL-C-004 DOMAIN Parameter for PXLOGICAL Characteristic Elements | The DOMAIN parameter for PXLOGICAL characteristic elements is used in the provisioning XML file for indicating a domain that the proxy supports, as described in "Parameters for PXLOGICAL characteristics" in the OMA Provisioning Content specification version 1.1 (OMA-WAP-ProvCont-v1_1-20021112-C). |
| ProvCont-CPL-C-005 TRUST Parameter for PXLOGICAL Characteristic Elements | The TRUST parameter for PXLOGICAL characteristic elements is used in the provisioning XML file for defining trusted proxies, as described in "Parameters for PXLOGICAL characteristics" in the OMA Provisioning Content specification version 1.1 (OMA-WAP-ProvCont-v1_1-20021112-C). |
| ProvCont-CPL-C-007 STARTPAGE Parameter for PXLOGICAL Characteristic Elements | The STARTPAGE parameter for PXLOGICAL characteristic elements is used in the provisioning XML file for defining a home page, as described in "Parameters for PXLOGICAL characteristics" in the OMA Provisioning Content specification version 1.1 (OMA-WAP-ProvCont-v1_1-20021112-C). |
| ProvCont-CPL-C-008 BASAUTH-ID Parameter for PXLOGICAL Characteristic Elements | The BASAUTH-ID parameter for PXLOGICAL characteristic elements is used in the provisioning XML file for indicating the basic authentication identifier for a home page, as described in "Parameters for PXLOGICAL characteristics" in the OMA Provisioning Content specification version 1.1 (OMA-WAP-ProvCont-v1_1-20021112-C). |
| ProvCont-CPL-C-009 BASAUTH-PW Parameter for PXLOGICAL Characteristic Elements | The BASAUTH-PW parameter for PXLOGICAL characteristic elements is used in the provisioning XML file for indicating the basic authentication password for a home page as described in "Parameters for PXLOGICAL characteristics" in the OMA Provisioning Content specification version 1.1 (OMA-WAP-ProvCont-v1_1-20021112-C). |
| ProvCont-CPL-C-011 PUSHENABLED Parameter for PXLOGICAL Characteristic Elements | The PUSHENABLED parameter for PXLOGICAL characteristic elements is used in the provisioning XML file for identifying whether a proxy supports push, as described in "Parameters for PXLOGICAL characteristics" in the OMA Provisioning Content specification version 1.1 (OMA-WAP-ProvCont-v1_1-20021112-C). |
| ProvCont-CPL-C-012 PORT Characteristic Elements within PXLOGICAL Characteristic Elements | PORT characteristic elements may occur in PXLOGICAL characteristic elements, as described in "Characteristics of type PORT" in the OMA Provisioning Content specification version 1.1 (OMA-WAP-ProvCont-v1_1-20021112-C). |
The following table shows features for the PXPHYSICAL characteristic:
| PXPHYSICAL feature | Description |
|---|---|
| ProvCont-CPP-C-001 PHYSICAL-PROXY-ID Parameter for PXPHYSICAL Characteristic Elements | The PHYSICAL-PROXY-ID parameter for PXPHYSICAL characteristic elements is used in the provisioning XML file for defining one physical WAP proxy entity, as described in "Parameters for PXPHYSICAL characteristics" in the OMA Provisioning Content specification version 1.1 (OMA-WAP-ProvCont-v1_1-20021112-C).
Windows Mobile-based devices provide continuous provisioning by allowing PHYSICAL-PROXY-ID to be in the TYPE field of a child characteristic of a PXPHYSICAL characteristic element. |
| ProvCont-CPP-C-002 PXADDR Parameter for PXPHYSICAL Characteristic Elements | The PXADDR parameter for PXPHYSICAL characteristic elements is used in the provisioning XML file for storing addresses, as described in "Parameters for PXPHYSICAL characteristics" in the OMA Provisioning Content specification version 1.1 (OMA-WAP-ProvCont-v1_1-20021112-C). |
| ProvCont-CPP-C-003 PXADDRTYPE Parameter for PXPHYSICAL Characteristic Elements | The PXADDRTYPE parameter for PXPHYSICAL characteristic elements is used in the provisioning XML file for indicating the format and interpretation of the PXADDR parameter, as described in "Parameters for PXPHYSICAL characteristics" in the OMA Provisioning Content specification version 1.1 (OMA-WAP-ProvCont-v1_1-20021112-C). |
| ProvCont-CPP-C-004 TO-NAPID Parameter for PXPHYSICAL Characteristic Elements | The TO-NAPID parameter for PXPHYSICAL characteristic elements is used in the provisioning XML file for referring to a Network Access Point (NAP), as described in "Parameters for PXPHYSICAL characteristics" in the OMA Provisioning Content specification version 1.1 (OMA-WAP-ProvCont-v1_1-20021112-C). |
| ProvCont-CPP-C-005 DOMAIN Parameter for PXPHYSICAL Characteristic Elements | The DOMAIN parameter for PXPHYSICAL characteristic elements is used in the provisioning XML file for identifying the domain for which a proxy is responsible, as described in "Parameters for PXPHYSICAL characteristics" in the OMA Provisioning Content specification version 1.1 (OMA-WAP-ProvCont-v1_1-20021112-C). |
| ProvCont-CPP-C-007 PUSHENABLED Parameter for PXPHYSICAL Characteristic Elements | The PUSHENABLED parameter for PXPHYSICAL characteristic elements is used in the provisioning XML file for identifying whether a proxy supports push, as described in "Parameters for PXPHYSICAL characteristics" in the OMA Provisioning Content specification version 1.1 (OMA-WAP-ProvCont-v1_1-20021112-C). |
| ProvCont-CPP-C-013 PORT CHARACTERISTIC Elements Within PXPHYSICAL Characteristic Elements | PORT characteristic elements can occur in PXPHYSICAL characteristic elements, as described in "Characteristics of type PORT" in the OMA Provisioning Content specification version 1.1 (OMA-WAP-ProvCont-v1_1-20021112-C). |
The following table shows features for the PXADDRTYPE parameter:
| PXADDRTYPE feature | Description |
|---|---|
| ProvCont-CPP-C-009 IPV4 Value for PXADDRTYPE Parameter | The IPV4 value for the PXADDRTYPE parameter is implemented as described in "Parameters for PXPHYSICAL characteristics" in the OMA Provisioning Content specification version 1.1 (OMA-WAP-ProvCont-v1_1-20021112-C). |
| ProvCont-CPP-C-011 E164 Value for PXADDRTYPE Parameter | The E164 type of physical proxy is used only by the push router. It will not be provisioned as a proxy that Internet Explorer Mobile and The Connection Manager (another Windows Mobile Version 5.0 component) use. The E164 value for the PXADDRTYPE parameter is implemented as described in "Parameters for PXPHYSICAL characteristics" in the OMA Provisioning Content specification version 1.1 (OMA-WAP-ProvCont-v1_1-20021112-C). |
The following table shows features for the PORT characteristic:
| PORT feature | Description |
|---|---|
| ProvCont-CP-C-001 PORTNBR Parameter for PORT Characteristic Elements | The PORTNBR parameter for PORT characteristic elements is used in the provisioning XML file for holding the value of the port number, as described in "Parameters for PORT characteristics" in the OMA Provisioning Content specification version 1.1 (OMA-WAP-ProvCont-v1_1-20021112-C). |
| ProvCont-CP-C-002 SERVICE Parameter for PORT Characteristic Elements | The SERVICE parameter for PORT characteristic elements is used in the provisioning XML file for identifying the service available for the port (PORTNBR), as described in "Parameters for PORT characteristics" in the OMA Provisioning Content specification version 1.1 (OMA-WAP-ProvCont-v1_1-20021112-C). |
The following table shows features for SERVICE parameter:
| SERVICE parameter feature | Description |
|---|---|
| ProvCont-CP-C-004 CO-WSP Value for SERVICE Parameter | The CO-WSP value for the SERVICE parameter is implemented as described in "Parameters for PORT characteristics" in the OMA Provisioning Content specification version 1.1 (OMA-WAP-ProvCont-v1_1-20021112-C). |
| ProvCont-CP-C-006 CO-SEC-WSP Value for SERVICE Parameter | The CO-SEC-WSP value for the SERVICE parameter is implemented as described in "Parameters for PORT characteristics" in the OMA Provisioning Content specification version 1.1 (OMA-WAP-ProvCont-v1_1-20021112-C). |
The following table shows features for NAPDEF characteristic elements:
| NAP-NAPDEF feature | Description |
|---|---|
| ProvCont-CND-C-001 NAPID Parameter for NAPDEF Characteristic Elements | The NAPID parameter for NAPDEF characteristic elements is used in the provisioning XML file for linking to the TO-NAPID parameter of PXPHYSICAL, as described in "Parameters for NAPDEF characteristics" in the OMA Provisioning Content specification version 1.1 (OMA-WAP-ProvCont-v1_1-20021112-C). Windows Mobile-based Pocket PCs provide continuous provisioning by allowing NAPID to also be in the Type field subcharacteristic of a NAPDEF characteristic element.
Note This maximum length for this string is 16 characters. |
| ProvCont-CND-C-002 BEARER Parameter for NAPDEF Characteristic Elements | The BEARER parameter for NAPDEF characteristic elements is used in the provisioning XML file for indicating a network type, as described in "Parameters for NAPDEF characteristics" in the OMA Provisioning Content specification version 1.1 (OMA-WAP-ProvCont-v1_1-20021112-C).
Windows Mobile-based devices can use a Global System for Mobile Communications Phase 2 Circuit Switched Data (GSM-CSD) or a GSM General Packet Radio Service (GSM-GPRS) network. |
| ProvCont-CND-C-003 NAME Parameter for NAPDEF Characteristic Elements | The NAME parameter for NAPDEF characteristic elements is used in the provisioning XML file for indicating a property of the configuration element, as described in "Parameters for NAPDEF characteristics" in the OMA Provisioning Content specification version 1.1 (OMA-WAP-ProvCont-v1_1-20021112-C). |
| ProvCont-CND-C-005 NAP-ADDRESS Parameter for NAPDEF Characteristic Elements | The NAP-ADDRESS parameter for NAPDEF characteristic elements is used in the provisioning XML file for communicating with a remote entity, as described in "Parameters for NAPDEF characteristics" in the OMA Provisioning Content specification version 1.1 (OMA-WAP-ProvCont-v1_1-20021112-C).
Windows Mobile-based devices use only the E164 and the Access Point Name (APN) address type values. |
| ProvCont-CND-C-006 NAP-ADDRTYPE Parameter for NAPDEF Characteristic Elements | The NAP-ADDRTYPE parameter for NAPDEF characteristic elements is used in the provisioning XML file for indicating the format of the address (NAP-ADDRTYPE), as described in "Parameters for NAPDEF characteristics" in the OMA Provisioning Content specification version 1.1 (OMA-WAP-ProvCont-v1_1-20021112-C).
Windows Mobile-based devices use only the E164 and APN address type values. |
| ProvCont-CND-C-007 CALLTYPE Parameter for NAPDEF Characteristic Elements | The CALLTYPE parameter for NAPDEF characteristic elements is used in the provisioning XML file for defining the type of call supported by the bearer, as described in "Parameters for NAPDEF characteristics" in the OMA Provisioning Content specification version 1.1 (OMA-WAP-ProvCont-v1_1-20021112-C). |
| ProvCont-CND-C-008 LOCAL-ADDR Parameter for NAPDEF Characteristic Elements | The LOCAL-ADDR parameter for NAPDEF characteristic elements is used in the provisioning XML file for defining the local address of Windows Mobile-based device, as described in "Parameters for NAPDEF characteristics" in the OMA Provisioning Content specification version 1.1 (OMA-WAP-ProvCont-v1_1-20021112-C). |
| ProvCont-CND-C-009 LOCAL-ADDRTYPE Parameter for NAPDEF Characteristic Elements | The LOCAL-ADDRTYPE parameter for NAPDEF characteristic elements is used in the provisioning XML file for indicating the format of the address in the LOCAL-ADDR parameter, as described in "Parameters for NAPDEF characteristics" in the OMA Provisioning Content specification version 1.1 (OMA-WAP-ProvCont-v1_1-20021112-C). |
| ProvCont-CND-C-010 LINKSPEED Parameter for NAPDEF Characteristic Elements | The LINKSPEED parameter for NAPDEF characteristic elements is used in the provisioning XML file for defining the connection speed, as described in "Parameters for NAPDEF characteristics" in the OMA Provisioning Content specification version 1.1 (OMA-WAP-ProvCont-v1_1-20021112-C). |
| ProvCont-CND-C-015 TRAFFIC-CLASS Parameter for NAPDEF Characteristic Elements | The TRAFFIC-CLASS parameter for NAPDEF characteristic elements is used in the provisioning XML file for defining a type of application, as described in "Parameters for NAPDEF characteristics" in the OMA Provisioning Content specification version 1.1 (OMA-WAP-ProvCont-v1_1-20021112-C). |
| ProvCont-CND-C-018 MAX-BITRATE-DNLINK Parameter for NAPDEF Characteristic Elements | The MAX-BITRATE-DNLINK parameter for NAPDEF characteristic elements is used in the provisioning XML file for defining the maximum number of bits delivered during a session, as described in "Parameters for NAPDEF characteristics" in the OMA Provisioning Content specification version 1.1 (OMA-WAP-ProvCont-v1_1-20021112-C). |
| ProvCont-CND-C-019 RESIDUAL-BER Parameter for NAPDEF Characteristic Elements | The RESIDUAL-BER parameter for NAPDEF characteristic elements is used in the provisioning XML file for indicating the undetected bit error ratio, as described in "Parameters for NAPDEF characteristics" in the OMA Provisioning Content specification version 1.1 (OMA-WAP-ProvCont-v1_1-20021112-C). |
| ProvCont-CND-C-020 SDU-ERROR-RATIO Parameter for NAPDEF Characteristic Elements | The SDU-ERROR-RATIO parameter for NAPDEF characteristic elements is used in the provisioning XML file for indicating the fraction of lost or erroneous Service Data Units (SDUs), as described in "Parameters for NAPDEF characteristics" in the OMA Provisioning Content specification version 1.1 (OMA-WAP-ProvCont-v1_1-20021112-C). |
| ProvCont-CND-C-021 TRAFFIC-HANDL-PRIO Parameter for NAPDEF CHARACTERISTIC Elements | The TRAFFIC-HANDL-PRIO parameter for NAPDEF characteristic elements is used in the provisioning XML file for specifying the priority of SDUs, as described in "Parameters for NAPDEF characteristics" in the OMA Provisioning Content specification version 1.1 (OMA-WAP-ProvCont-v1_1-20021112-C). |
The following table shows features for NAP-ADDRTYPE parameters:
| NAP-ADDRTYPE feature | Description |
|---|---|
| ProvCont-CND-C-028 E164 Value for NAP-ADDRTYPE Parameter | The E164 value for the NAP-ADDRTYPE parameter is implemented as described in "Parameters for NAPDEF characteristics" in the OMA Provisioning Content specification version 1.1 (OMA-WAP-ProvCont-v1_1-20021112-C). |
| ProvCont-CND-C-030 APN Value for NAP-ADDRTYPE Parameter | The APN value for the NAPADDRTYPE parameter is implemented as described in "Parameters for NAPDEF characteristics" in the OMA Provisioning Content specification version 1.1 (OMA-WAP-ProvCont-v1_1-20021112-C). |
The following table shows features for the BEARER parameters:
| BEARER feature | Description |
|---|---|
| ProvCont-CBS-C-009 GSM-CSD Value for BEARER Parameter | The GSM-CSD value for the BEARER parameter is implemented as described in "Parameters for NAPDEF characteristics" in the OMA Provisioning Content specification version 1.1 (OMA-WAP-ProvCont-v1_1-20021112-C). |
| ProvCont-CBS-C-010 GSM-GPRS Value for BEARER Parameter | The GSM-GPRS value for the BEARER parameter is implemented as described in "Parameters for NAPDEF characteristics" in the OMA Provisioning Content specification version 1.1 (OMA-WAP-ProvCont-v1_1-20021112-C). |
The following table shows features for NAPAUTINFO characteristic elements:
| NAPAUTINFO feature | Description |
|---|---|
| ProvCont-CNA-C-001 AUTHTYPE Parameter for NAPAUTHINFO Characteristic Elements | The AUTHTYPE parameter for NAPAUTHINFO characteristic elements is used in the provisioning XML file for indicating the authentication protocol, as described in "Parameters for NAPAUTHINFO characteristics" in the OMA Provisioning Content specification version 1.1 (OMA-WAP-ProvCont-v1_1-20021112-C). |
| ProvCont-CNA-C-002 AUTHNAME Parameter for NAPAUTHINFO Characteristic Elements | The AUTHNAME parameter for NAPAUTHINFO characteristic elements is used in the provisioning XML file for identifying the plain text identifier (ID) for user authentication, as described in "Parameters for NAPAUTHINFO characteristics" in the OMA Provisioning Content specification version 1.1 (OMA-WAP-ProvCont-v1_1-20021112-C). |
| ProvCont-CNA-C-003 AUTHSECRET Parameter for NAPAUTHINFO Characteristic Elements | The AUTHSECRET parameter for NAPAUTHINFO characteristic elements is used in the provisioning XML file for identifying the plain text password for user authentication, as described in "Parameters for NAPAUTHINFO characteristics" in the OMA Provisioning Content specification version 1.1 (OMA-WAP-ProvCont-v1_1-20021112-C). |
The following table shows features for BOOTSTRAP characteristic elements:
| Bootstrap feature | Description |
|---|---|
| ProvCont-CB-C-001 PROVURL Parameter for BOOTSTRAP Characteristic Elements | The PROVURL parameter for BOOTSTRAP characteristic elements is an absolute Uniform Resource Identifier (URI) in the provisioning XML file, as described in "Parameters for BOOTSTRAP characteristics" in the OMA Provisioning Content specification version 1.1 (OMA-WAP-ProvCont-v1_1-20021112-C). |
| ProvCont-CB-C-002 CONTEXT-ALLOW Parameter for BOOTSTRAP Characteristic Elements | The CONTEXT-ALLOW parameter for BOOTSTRAP characteristic elements is used in the provisioning XML file, as described in "Parameters for BOOTSTRAP characteristics" in the OMA Provisioning Content specification version 1.1 (OMA-WAP-ProvCont-v1_1-20021112-C). Windows Mobile-based devices accept only one context. For example, the allowed value is 0. |
| ProvCont-CB-C-006 NAME Parameter for BOOTSTRAP Characteristic Elements | The NAME parameter for BOOTSTRAP characteristic elements is used in the provisioning XML file for indicating an identity (property) of the configuration context, as described in "Parameters for BOOTSTRAP characteristics" in the OMA Provisioning Content specification version 1.1 (OMA-WAP-ProvCont-v1_1-20021112-C). |
The following table describes how minimum lengths are implemented:
| Minimum length feature | Description |
|---|---|
| ProvCont-MLP-C-002 Minimum Length of the NAP-ADDRESS Parameter | The minimum length of the NAP-ADDRESS parameter is implemented as described in "The Length of parameter fields" in the OMA Provisioning Content specification version 1.1 (OMA-WAP-ProvCont-v1_1-20021112-C). |
| ProvCont-MLP-C-010 Minimum Length of the STARTPAGE Parameter | The minimum length of the STARTPAGE parameter is implemented as described in "The Length of parameter fields" in the OMA Provisioning Content specification version 1.1 (OMA-WAP-ProvCont-v1_1-20021112-C). |
| ProvCont-MLP-C-011 Minimum Length of the BASAUTH-ID Parameter | The minimum length of the BASAUTH-ID parameter is implemented as described in "The Length of parameter fields" in the OMA Provisioning Content specification version 1.1 (OMA-WAP-ProvCont-v1_1-20021112-C). |
| ProvCont-MLP-C-012 Minimum Length of the BASAUTH-PW Parameter | The minimum length of the BASAUTH-PW parameter is implemented as described in "The Length of parameter fields" in the OMA Provisioning Content specification version 1.1 (OMA-WAP-ProvCont-v1_1-20021112-C). |
| ProvCont-MLP-C-013 Minimum Length of the PXADDR Parameter | The minimum length of the PXADDR parameter is implemented as described in "The Length of parameter fields" in the OMA Provisioning Content specification version 1.1 (OMA-WAP-ProvCont-v1_1-20021112-C). |
| ProvCont-MLP-C-018 Minimum Length of the PHYSICAL-PROXY-ID Parameter | The minimum length of the PHYSICAL-PROXY-ID parameter is implemented as described in "The Length of parameter fields" in the OMA Provisioning Content specification version 1.1 (OMA-WAP-ProvCont-v1_1-20021112-C). |
| ProvCont-MLP-C-019 Minimum Length of the NAPID Parameter | The minimum length of the NAPID parameter is implemented as described in "The Length of parameter fields" in the OMA Provisioning Content specification version 1.1 (OMA-WAP-ProvCont-v1_1-20021112-C).
Note This maximum length for this string is 16 characters. |
See Also
Microsoft Standards for Provisioning Windows Mobile-Based Devices | OMA Client Provisioning Files
Send Feedback on this topic to the authors