White Paper V600
Feature | Support for WAP |
|
|
|
|
Parameter set list | name, | name, |
| homepage and | homepage, |
| homepage title (1st | proxy/GW address, |
| bookmark element), | CSD phone number, |
| proxy/GW address, | CSD data rate, |
| bookmarks (remaining | CSD dial type, |
| bookmark elements), | CSD response timer, |
| CSD phone number, | GPRS APN, |
| CSD data rate, | protocol authentication, |
| CSD dial type, | GW authentication, |
| GPRS APN, | GPRS QoS |
| protocol authentication, |
|
| GW authentication, |
|
| secure connection on/off |
|
|
| |
Parameter sets include | WAP/CSD, WAP/GPRS (different sets). | |
|
| |
Factory | WAP/CSD (possibility to lock a setting), WAP/GPRS. | |
|
| |
OTA | WAP/CSD, WAP/GPRS configuration possible. | |
|
|
|
Security mechanism |
|
|
|
|
|
Bearer | The | OMA Client |
| solution | Provisioning |
OTA via SMS | Operator verification |
| through a code that can |
| be included in the OTA |
| configuration data. |
| This code is shown to the |
| user who can choose to |
| install or not. |
Uses security mechanism (SEC) methods according to
Interface
Bearer | The | OMA Client |
| solution | Provisioning |
OTA via SMS | A question whether to |
| install, with the code if |
| available is asked. The |
| user may have to choose |
| whether to create a new |
| WAP profile or to replace |
| an existing WAP profile. |
For NETWPIN the user is asked to accept to install received settings. For USERPIN, USERNETWPIN and USERPINMAC the user is subsequently asked to enter a PIN code that is a shared secret between the service provider and the user.
The | OMA Client Provision- | |
| solution | ing |
|
|
|
56 | August 2005 |