WAP NAPDEF
4/8/2010
The WAP NAPDEF characteristic and its parms are sent to the remote access or General Packet Radio Services (GPRS) configuration of Connection Manager. For more information see NAPDEF Configuration Service Provider.
The following table shows the NAP parms that are supported on Windows Mobile devices.
| Characteristic | Parm | Comments |
|---|---|---|
NAPDEF |
|
A network GUID will be generated for each acceptable NAPDEF. A network entry will be sent to the Connection Manager network configuration. The format of the network name is:#NAME + "@" + NAPID + "@NAPDEF" |
|
NAPID |
The name of WAP PPP/GPRS entry is a combination of NAPID and a predefined word "WAP":#NAPID + "@WAP" > [!NOTE] > This maximum length for this string is 16 characters. |
|
NAME |
Set as part of the name of the created network. |
|
BEARER |
GSM-circuit-switched data (CSD) and GSM-GPRS are supported. Other bearer settings will be discarded. |
|
NAP-ADDRESS |
|
|
NAP-ADDRTYPE |
E164 and Access Point Name (APN) are supported. |
|
CALLTYPE |
CALLTYPE and LINKSPEED are used together to set the BearerInfoSpeed parm under the DevSpecificCellular characteristic in the CM_PPPEntries in the Connection Manager Configuration Service Provider. |
|
LINKSPEED |
|
|
LINGER |
This parm is not used. |
|
LOCAL-ADDR |
If BEARER= "GSM-GPRS" and LOCAL-ADDRTYPE = "IPV4", LOCAL-ADDR is used by Windows Mobile devices to provision a client static GPRS IP address — DevSpecificCellular/GPRSInfoAddress. Provisioning the GPRS IPV6 address is supported. |
|
LOCAL-ADDRTYPE |
If BEARER= "GSM-GPRS" and LOCAL-ADDRTYPE = "IPV4", LOCAL-ADDR is used by Windows Mobile devices to provision the client static GPRS IP address — DevSpecificCellular/GPRSInfoAddress. |
NAPDEF/ NAPAUTHINFO |
|
|
NAPDEF/ NAPAUTHINFO |
AUTHTYPE (PAP, CHAP) |
|
NAPDEF/ NAPAUTHINFO |
AUTHNAME |
|
NAPDEF/ NAPAUTHINFO |
AUTHSECRET |
|
|
TRAFFIC-CLASS |
A mapping table is required to translate WAP GPRS quality of service (QoS) (3GPP R99) settings to GPRS QoS (GSM -GPRS) settings supported on Windows Mobile devices. The mapping table that follows lists all parms that can be converted to supported QoSparms. The entire mapping table is listed in 3GPP TS 23.107 V3.5.0 (2000-12). |
|
TRAFFIC-HANDL-PRIO |
|
|
SDU-ERROR-RATIO |
|
|
RESIDUAL-BER |
|
See Also
Reference
NAPDEF Configuration Service Provider
Concepts
Standard OMA Client Provisioning Parameters Processed by the Device