次の方法で共有

PXLOGICAL Configuration Service Provider

  • [アーティクル]

Send Feedback

The PXLOGICAL Configuration Service Provider adds, removes, and modifies WAP logical and physical proxies by using WAP or the standard Windows Mobile-based device techniques. For more information, see the Update Standard WAP Connectivity Parameters.

Note   The PXLOGICAL and PXPHYSICAL mwid attribute is a Microsoft provisioning XML attribute. The mwid attribute is optional when adding a NAP or a proxy. It is required when updating and deleting existing NAPs and proxies and must have its value set to 1. For more information about this attribute, see characteristic Element and characteristic-query Element.

Note   This Configuration Service Provider is managed over the OMA Client Provisioning (formerly WAP) protocol.

Note   Access to this Configuration Service Provider is determined by Security roles. Because OEMs and Mobile Operators can selectively disallow access, ask them about the availability of this Configuration Service Provider. For more information about roles, see Security Roles and Default Roles for Configuration Service Providers.

The following table shows the default settings for all parameters in this Configuration Service Provider. The default security role maps to each subnode unless specific permission is granted to the subnode.

Permissions Read/write
Roles allowed to query and update setting Manager

Operator

Operator-TPS

Authenticated User

The following image shows the Configuration Service Provider in tree format as used by OMA Client Provisioning for initial bootstrapping of the device.

The following image shows the Configuration Service Provider in tree format as used by OMA Client Provisioning for updating the bootstrapping of the device.

Characteristics

  • PORT
    This characteristic defines the binding between a port number and one or more protocols or services. This Configuration Service Provider can accept a maximum of two ports per physical proxy. A query of this characteristic returns information relating only to the first port.
  • PXPHYSICAL
    This characteristic groups files for a physical proxy. One PXLOGICAL characteristic can contain multiple PXPHYSICAL characteristics.

Parameters

  • BASAUTH-ID
    This parm can be used in all PXLOGICAL characteristics. It contains the user ID of the start page. Query of this parm is not supported.

  • BASAUTH-PW
    This parm can be used in all PXLOGICAL characteristics. It contains the user password of the start page. Query of this parm is not supported.

  • DOMAIN
    This parm is used in the PXLOGICAL and PXPHYSICAL characteristics. A query of this parm returns a semicolon delimited string of all domains.

  • NAME
    This parm can be used in all PXLOGICAL characteristics. It contains the name of the proxy.

    Note   The NAME parm in PXLOGICAL is displayed in one line to the user; the length of this parm should be short for readability.

  • PHYSICAL-PROXY-ID
    This parm is used in the PXPHYSICAL characteristic to identify the physical proxy.

    Note   The PHYSICAL-PROXY-ID parm is displayed in one line to the user; the length of this parm should be short for readability.

  • PORTNBR
    This parm is used in the PXLOGICAL\PORT and PXPHYSICAL\PORT characteristics to identify the port number associated with some services on this proxy.

  • PROXY-ID
    This parm can be used in all PXLOGICAL characteristics. It contains the unique identification of the logical proxy.

  • PUSHENABLED
    This parm is used in the PXLOGICAL and PXPHYSICAL characteristics to determine whether or not push operations are enabled. If the parm is used in PXLOGICAL, it applies to all of the PXPHYSICAL characteristics embedded in the PXLOGICAL characteristic. A value of zero (0) indicates that the proxy does not support push operations. A value of 1 indicates that the proxy supports push operations.

  • PXADDR
    This parm is used in the PXPHYSICAL characteristic to identify the address of the physical proxy.

  • PXADDRTYPE
    This parm is used in the PXPHYSICAL characteristic to determine the address type for PXADDR. Only E164, IPv4, are supported.

  • SERVICE
    This parm is used in the PXLOGICAL\PORT and PXPHYSICAL\PORT characteristics. A query of this parm returns a semicolon-delimited string of services for only the first port. Supported services on the Windows Mobile Web browser (Microsoft Internet Explorer Mobile) include CO-WSP and CO-SEC-WSP. Windows Mobile also supports accepting WAP push connectionless sessions over an Short Message Service (SMS) bearer for WAP push messages.

  • STARTPAGE
    This parm can be used in all PXLOGICAL characteristics. It identifies the start Web page for the proxy.

    Note   If this parm is present, an Internet Explorer Mobile browser favorite will be generated whose name corresponds to the PXLOGICAL NAME parm value (or STARTPAGE value if NAME is not present), and whose URL corresponds to the STARTPAGE parm value. Also, if the URL's scheme is "http" or "https," it will be converted to "wsp" or "wsps," respectively.

  • TO-NAPID
    This parm is used in the PXPHYSICAL characteristic to identify the network access point associated with this physical proxy. Only one per proxy is supported.

    Note   When adding a physical proxy, you must add also the NAP whose NAPID is referred to by TO-NAPID in this same XML document.

  • TRUST
    This parm can be used in all PXLOGICAL characteristics to define whether or not the physical proxies in this logical proxy are trusted. The SECPOLICY_TRUSTED_WAP_PROXY security policy (4121) governs what roles can set this parameter.

    The following table shows the default settings.

    Permissions Read/write
    Roles allowed to query and update setting Manager

    Operator

    Operator-TPS

Microsoft Custom Elements

The parm-query and characteristic-query features are not supported for all PXPHYSICAL proxy parameters for all PXADDR types. All parameters can be queried when the PXPHYSICAL proxy PXADDRType is IPv4. For example, if a mobile operator queries the TO-NAPID parm of a PXPHYSICAL proxy and the PXADDR Type is E164, a noparm is returned.

Note   These features are available only for the device technique.

The following table shows the Microsoft custom elements that this Configuration Service Provider supports for OMA Client Provisioning.

Feature Available
<parm-query> Yes. See also SERVICE, DOMAIN, and BASAUTH-PW.
<noparm> Yes
<nocharacteristic> Yes
<characteristic-query> Yes. See also PORT.

Use these elements to build standard OMA Client Provisioning (formerly WAP) configuration XML. For information about specific elements, see MSPROV DTD Elements. For examples of how to generally use the Microsoft custom elements, see Provisioning XML File Examples.

For information about OMA Client Provisioning, see OMA Client Provisioning Files.

See Also

Configuration Service Provider Reference for Windows Mobile-Based Devices | PXLOGICAL Configuration Service Provider Examples for OMA Client Provisioning| WAP Logical Proxy: PXLOGICAL | Bootstrapping To Use an OMA Client Provisioning Server

Send Feedback on this topic to the authors

Feedback FAQs

© 2006 Microsoft Corporation. All rights reserved.