NAPDEF Configuration Service Provider

  • Article

Send Feedback

Use the NAPDEF Configuration Service Provider to add, modify, and delete Wireless Application Protocol (WAP) network access points (NAPs) — for example, remote access. For complete information about these settings, see the standard WAP specification WAP-183-ProvCont-20010724-a. For a detailed description of how the device processes these parameters, see the WAP Connectivity Bootstrap Message Example.

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

Note   The Microsoft format for NAPDEF contains the provisioning XML attribute mwid. This custom 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 the mwid attribute, see characteristic Element and characteristic-query Element.

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

AuthenticatedUser

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

  • NAPAUTHINFO
    Authentication information within a network access point.

Parameters

  • AUTHNAME
    This parm is used in the NAPAUTHINFO characteristic to identify the ID needed to authenticate the user.

  • AUTHSECRET
    This parm is used in the NAPAUTHINFO characteristic to identify the password needed to authenticate the user. A query of this parm results in asterisks (*).

  • AUTHTYPE
    This parm is used in the NAPAUTHINFO characteristic to identify the authentication protocol. Only Password Authentication Protocol (PAP) and Challenge Handshake Authentication Protocol (CHAP) authentication protocols are supported.

    Note   AuthName and AuthSecret are not created if AuthType is not included in the initial device configuration. AuthName and AuthSecret cannot be changed if AuthType is not included in the provisioning xml used to make the change.

  • BEARER
    This parm identifies the type of bearer. Only Global System for Mobile Communication (GSM)-circuit-switched data (CSD) and GSM-General Packet Radio Services (GPRS) are supported.

  • CALLTYPE
    This is a GSM-CSD parm, which identifies the protocol that will be used for data exchange.

  • LINKSPEED
    This is a GSM-CSD parm, which identifies the speed on the uplink channel and optionally the downlink channel.

  • LOCAL-ADDR
    This is a GPRS parm, which identifies the local address of the WAP client.

  • LOCAL-ADDRTYPE
    This is a GPRS-related parm, which indicates the address format in the LOCAL-ADDR parm. LOCAL-ADDR provides the device's GPRS IP address. The value of LOCAL-ADDRTYPE can be either IPv4 or IPv6.

    Note   Windows Mobile 2003 provides support for IPv6 only in IPv4/IPv6 mixed-mode environments.

  • NAME
    This parm identifies the logical, user-readable identity of the NAP.

  • NAP-ADDRESS
    This parm identifies the address of the NAP.

  • NAP-ADDRTYPE
    This parm identifies the protocol of NAP-ADDRESS. Only Access Point Name (APN) and E164 are supported.

  • NAPID
    This parm identifies the NAP. This maximum length for this string is 16 characters.

Microsoft Custom Elements

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

Elements Available
parm-query Yes. See also the parm AUTHSECRET.
Note   GPRS parameters will not necessarily contain the exact same value as was set.
noparm Yes
nocharacteristic Yes
characteristic-query Yes

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 | NAPDEF Configuration Service Provider Examples for OMA Client Provisioning| WAP NAPDEF

Send Feedback on this topic to the authors

Feedback FAQs

© 2006 Microsoft Corporation. All rights reserved.