OMA Client Provisioning User Agent Profile Features

Article
11/18/2015

4/8/2010

The User Agent Profile (UAProf) defines user agent behavior in the course of OMA Client Provisioning. This document lists the UAProf features available for OMA Client Provisioning of Windows Mobile devices.

For more information about User Agents, see the Open Mobile Alliance documents Provisioning User Agent Behaviour, (OMA-WAP-ProvUAB-v1_1-20050428-C and OMA-WAP-ProvBoot-v1_1-20021112-C), available from this OMA Web site.

The following table lists the general UAProf features supported in Windows Mobile.

General User Agent Behavior Features	Description
ProvUAB-U-C-001 Support for the wap-provisioningdoc	Bootstrap sessions are initiated by the server with a bootstrap document sent over WAP connectionless push with the default push port, the default application ID and the provisioning MIME-type.
ProvUAB-U-C-002 Support for Proxy Selection	Proxy selection uses the network address and the path of the request encoded in the Uniform Resource Identifier (URI). These are compared to the domain information in the proxy definition, and a single proxy is selected.
ProvUAB-U-C-003 Support for Over the Air Bootstrap	Windows Mobile supports Over the Air (OTA) Bootstrap. For more information see Bootstrapping a Device. > [!NOTE] > OTA bootstrapping is disabled by default in Windows Mobile devices. It must be enabled before it can be used. For more information see Enabling OTA Bootstrapping.
ProvUAB-U-C-005 Support for provisioning document conflict resolution.	Conflicts between configuration documents are resolved by following two rules: Always Append - add the parameters in new provisioning documents to the existing set. Never Overwrite parameters in the existing set - discard any parameter that is already configured.

The following table lists the proxy selection features supported by UAProf in Windows Mobile.

Proxy Selection Features	Description
ProvUAB-UPS-C-001 Support for authority match	A Uniform Resource Identifier (URI) matches a domain parameter on the authority (network location) part if any of the following conditions is met (all matches are case insensitive): The authority part of the URI and the authority part of the domain parameter are both fully qualified host names and match. The authority part of the URI is a fully qualified host name and has the form X followed by the authority part of the domain parameter (a fully qualified host name), and the authority part of the domain parameter has the form .b and b conforms to the form of a fully qualified domain name. The authority part of the domain parameter is an empty string. The authority part of the URI and the authority part of the domain parameter are both complete IP addresses and they are equal.
ProvUAB-UPS-C-002 Support for path match	A URI matches a domain parameter on the path if either of the following conditions is met: The path part of the domain parameter is empty. The path part of the domain parameter matches the beginning of the path part of the URI exactly according to a case sensitive string match.
ProvUAB-UPS-C-003 Support for best match	The proxy giving the best authority match and path match, according to the following rules, is selected: 1) If, according to an authority match, match A is better than match B, match B is discarded; otherwise 2) If, according to a path match, match A is better than match B, match B is discarded. If, during authority match or path match, the list of selected proxies becomes empty, or if the URI does not contain a fully qualified domain name as specified in [RFC2396], the match process stops. At this point, an implementation-dependent algorithm may be used to choose a proxy.

ProvUAB-UPS-C-001 Support for authority match

A Uniform Resource Identifier (URI) matches a domain parameter on the authority (network location) part if any of the following conditions is met (all matches are case insensitive):

The authority part of the URI and the authority part of the domain parameter are both fully qualified host names and match.
The authority part of the URI is a fully qualified host name and has the form X followed by the authority part of the domain parameter (a fully qualified host name), and the authority part of the domain parameter has the form .b and b conforms to the form of a fully qualified domain name.
The authority part of the domain parameter is an empty string.
The authority part of the URI and the authority part of the domain parameter are both complete IP addresses and they are equal.

ProvUAB-UPS-C-002 Support for path match

A URI matches a domain parameter on the path if either of the following conditions is met:

The path part of the domain parameter is empty.
The path part of the domain parameter matches the beginning of the path part of the URI exactly according to a case sensitive string match.

ProvUAB-UPS-C-003 Support for best match

The proxy giving the best authority match and path match, according to the following rules, is selected:

1) If, according to an authority match, match A is better than match B, match B is discarded; otherwise

2) If, according to a path match, match A is better than match B, match B is discarded.

If, during authority match or path match, the list of selected proxies becomes empty, or if the URI does not contain a fully qualified domain name as specified in [RFC2396], the match process stops. At this point, an implementation-dependent algorithm may be used to choose a proxy.

The following table lists the conflict resolution features supported by UAProf in Windows Mobile.

Conflict Resolution Features	Description
ProvUAB-UCR-C-001 Redundant characteristics ignored	A characteristic that is redefined (as opposed to given an alternative value) is ignored. The original definition is retained.
ProvUAB-UCR-C-002 Redundant parameters ignored	A parameter that is redefined (as opposed to given an alternative value) is ignored. The original definition is retained.
ProvUAB-UCR-C-003 Unknown characteristics ignored	If a characteristic's name is unknown then the characteristic is ignored.
ProvUAB-UCR-C-004 Unknown parameters ignored	If a parameter's name is unknown then the characteristic is ignored.
ProvUAB-UCR-C-005 Unknown values ignored	If a parameter value is unknown then the parameter is ignored.
ProvUAB-UCR-C-006 Discard redundant NAP definitions but continue to process document	Only the first NAP-ID value (to define a NAP) within a document is valid. Any latter definition is illegal.

The following table lists the features that support use of provisioning document parameters by UAProf in Windows Mobile.

Use of Provisioning Document Parameters Features	Description
ProvUAB-UDP-C-001 Ignore NAP definition when bearer not supported	A network access point definition for a bearer that is not supported is ignored.
ProvUAB-UDP-C-002 Ignore physical proxy definitions containing only unsupported protocols	If none of the protocol stack configurations in a physical proxy definition are supported, the definition is ignored.
ProvUAB-UDP-C-003 Ignore physical proxy definitions without a valid NAP	Any physical proxy definition that does not include a valid network access point definition is ignored.
ProvUAB-UDP-C-004 Ignore logical proxy definitions without a valid physical proxy	Any logical proxy definition that does not include a valid physical proxy definition is ignored.
ProvUAB-UDP-C-006 Use of PORT characteristic	Port bindings for a physical proxy are available from two sources - the port bindings defined for the logical proxy, and the port bindings in the PXPHYSICAL characteristic. If this set of port bindings is empty, then the device uses a port and service according to its preferences.

The following table lists the error handling features supported by UAProf in Windows Mobile.

Error Handling Features	Description
ProvUAB-UEH-C-001 Ignore unknown tags and attributes in provisioning document	Provisioning documents encoded with alternative Document Type Definitions (DTD) might include elements or attributes that are not recognized. As long as the major version number of the provisioning document is supported, the configuration is used, but the unrecognized tags and attributes are ignored.
ProvUAB-UEH-C-002 Ignore document with unsupported major version number	If the major version number of a provisioning document isn't supported then the entire provisioning document is ignored.
ProvUAB-UEH-C-003 Ignore parameters and values that are unrecognized	A provisioning document encoded with an alternative version might include parameters that are not recognized. As long as the major version number of the provisioning document is supported, the configuration is used, but the unrecognized tags and attributes are ignored.
ProvUAB-UEH-C-004 Ignore corrupt document	If a provisioning document is found to be corrupt, then the User Agent will ignore the document.

The following table lists the GSM bootstrap feature supported by UAProf in Windows Mobile.

GSM Bootstrap Features	Description
ProvUAB-UGSM-C-001 Support for bootstrap in GSM	Windows Mobile devices accept WAP Push bootstrap messages sent over SMS channels using Wireless Session Protocol (WSP). For more information see OTA Provisioning Considerations.

OMA Client Provisioning User Agent Profile Features

See Also

Other Resources

Additional resources