w7 APPLICATION Characteristic Features
The w7 APPID in the APPLICATION characteristic is used for bootstrapping a device with an OMA DM account. The following list shows the OMA documents that were referenced:
- "SyncML DM Tree and Description" specification (OMA-SyncML-DMTND-V1_1_2-20030508-C)
- "SyncML DM Security" specification (OMA-SyncML-DMSecurity-V1_1_2-20030508-C)
- "SyncML Representation Protocol" specification (OMA-SyncML-RepPro-V1_1_2-20030505-C)
The following table shows the features in the APPLICATION characteristic.
| Parameter | Description |
|---|---|
| APPLICATION/APPID | The APPID parameter for Application characteristic elements is used in the provisioning XML file to indicate the type of application service available as described in "Parameters for APPLICATION characteristics" in the OMA Provisioning Content specification version 1.1 (OMA-WAP-ProvCont-v1_1-20021112-C).
OMA considers each transport to be an application and requires a corresponding APPLICATION Configuration Service Provider. For information of the supported transports, see APPLICATION Characteristic Features. |
| APPLICATION/INIT | This is an application-specific parameter.
The INIT parameter for the APPLICATION characteristic elements is used in the provisioning XML file to indicate that the management server wants the client to initiate a management session immediately after settings approval. This parameter forces the device to attempt to connect with the OMA DM sever. |
| APPLICATION/NAME | The NAME parameter for APPLICATION characteristic elements is used in the provisioning XML file to specify a user readable identity as described in "Parameters for APPLICATION characteristics" in the OMA Provisioning Content specification version 1.1 (OMA-WAP-ProvCont-v1_1-20021112-C).
In Windows 5.0-based devices it is used to specify the user displayable name for the management server. |
| APPLICATION/PROVIDER-ID | The PROVIDER-ID parameter for APPLICATION characteristic elements is used in the provisioning XML file to differentiate OMA DM servers.
It specifies the server identifier for management server used in the management sessions as described in "Parameters for APPLICATION characteristics" in the OMA Provisioning Content specification version 1.1 (OMA-WAP-ProvCont-v1_1-20021112-C) and "SyncML DM Tree and Description" specification (OMA-SyncML-DMTND-V1_1_2-20030508-C). |
| APPLICATION/TO-NAPID | The TO-NAPID parameter for APPLICATION characteristic elements is used in the provisioning XML file to specify the specific GPRS connection the client will use to connect to the OMA DM server as described in "Parameters for APPLICATION characteristics" in the OMA Provisioning Content specification version 1.1 (OMA-WAP-ProvCont-v1_1-20021112-C).
In Windows Mobile-based devices, only the first TO-NAPID will be stored. TO-PROXY is ignored. |
The following table shows the features in the APPADDR characteristic.
| Parameter | Description |
|---|---|
| APPADDR/ADDR | The ADDR parameter for APPADDR characteristic elements is used in the provisioning XML file to provide the address of the application server as described in "Parameters for APPADDR characteristics" in the OMA Provisioning Content specification version 1.1 (OMA-WAP-ProvCont-v1_1-20021112-C). |
| APPADDR/ADDRTYPE | The parameter for APPADDR characteristic elements is used in the provisioning XML file to indicate the format of the ADDR parameter as described in "Parameters for APPADDR characteristics" in the OMA Provisioning Content specification version 1.1 (OMA-WAP-ProvCont-v1_1-20021112-C). |
The following table shows the features in the APPAUTH characteristic.
| Parameter | Description |
|---|---|
| APPAUTH/AAUTHDATA | The AAUTHDATA parameter for APPAUTH characteristic elements is used in the provisioning XML file to provide additional parameters used in authentication the user as described in "Parameters for APPAUTH characteristics" in the OMA Provisioning Content specification version 1.1 (OMA-WAP-ProvCont-v1_1-20021112-C).
In Windows Mobile-based devices, when this parameter is used to convey the nonce for digest authentication type, the nonce must be encoded in b64 in the XML provisioning file. |
| APPAUTH/AAUTHLEVEL | The AAUTHLEVEL parameter for APPAUTH characteristic elements is used in the provisioning XML file to indicate whether the credentials client authenticates itself at the DM server or client level as described in "Parameters for APPAUTH characteristics" in the OMA Provisioning Content specification version 1.1 (OMA-WAP-ProvCont-v1_1-20021112-C). |
| APPAUTH/AAUTHLEVEL/APPSRV | The APPSRV parameter for the AUTHLEVEL characteristic element is used in the provisioning XML file to indicate the group credentials the client uses to authenticate itself to the OMA DM Server at the DM protocol level as described in "Parameters for APPAUTH characteristics" in the OMA Provisioning Content specification version 1.1 (OMA-WAP-ProvCont-v1_1-20021112-C). |
| APPAUTH/AAUTHLEVEL/CLIENT | The CLIENT parameter for the AUTHLEVEL characteristic element is used in the provisioning XML file indicate the group credentials that the server uses to authenticate itself to the OMA DM Client at the DM protocol level as described in "Parameters for APPAUTH characteristics" in the OMA Provisioning Content specification version 1.1 (OMA-WAP-ProvCont-v1_1-20021112-C). |
| APPAUTH/AAUTHNAME | The AAUTHNAME parameter for APPAUTH characteristic elements is used in the provisioning XML file to provide the ID used to authenticate the user as described in "Parameters for APPAUTH characteristics" in the OMA Provisioning Content specification version 1.1 (OMA-WAP-ProvCont-v1_1-20021112-C).
In Windows Mobile-based devices this parameter used in the following APPIDs:
|
| APPAUTH/AAUTHSECRET | The AAUTHSECRET parameter for APPAUTH characteristic elements is used in the provisioning XML file to provide the authentication secret used to authenticate the user as described in "Parameters for APPAUTH characteristics" in the OMA Provisioning Content specification version 1.1 (OMA-WAP-ProvCont-v1_1-20021112-C). |
| APPAUTH/AAUTHTYPE | The AAUTHTYPE parameter for APPAUTH characteristic elements is used in the provisioning XML file to provide information about the authentication type as described in "Parameters for APPAUTH characteristics" in the OMA Provisioning Content specification version 1.1 (OMA-WAP-ProvCont-v1_1-20021112-C).
Windows Mobile-based devices support BASIC and DIGEST for client authentication. DIGEST is supported for server authentication |
| APPAUTH/AAUTHTYPE/BASIC | The BASIC parameter for the AUTHTYPE characteristic element is used in the provisioning XML file indicate the SyncML DM 'syncml:auth-basic' authentication as specified in the "SyncML DM Security" specification (OMA-SyncML-DMSecurity-V1_1_2-20030508-C) |
| APPAUTH/AAUTHTYPE/DIGEST | The DIGEST parameter for the AUTHTYPE characteristic element is used in the provisioning XML file SyncML DM 'syncml:auth-md5' authentication as specified in the "SyncML DM Security" specification (OMA-SyncML-DMSecurity-V1_1_2-20030508-C) |
The following table shows the features in the PORT characteristic.
| Parameter | Description |
|---|---|
| PORT/PORTNBR | The PORTNBR parameter for PORT characteristic elements is used in the provisioning XML file to identify the port number to connect to as described in "Parameters for APPAUTH characteristics" in the OMA Provisioning Content specification version 1.1 (OMA-WAP-ProvCont-v1_1-20021112-C). |
See Also
APPLICATION Characteristic Features | APPLICATION Configuration Service Provider
Send Feedback on this topic to the authors