Table of Contents
Advertisement
Feature
OTA Support
PPP Authentication
Reload page
User Agent Profiles
WAP/WML
Internet profiles
Operator technical data
Feature
WAP Browser
Version
Security mechanism
Bearer
OTA via SMS
Interface
Bearer
OTA via SMS
Re-provisioning Interface
OTA via SMS
Carrier reset/provisioning
Support in the browser
Yes
PAP supported
Yes
Yes, list of client characteristics - for example, screen size
WAP 1.2.1/WML 1.3
Up to 10 Internet profiles, each with its own settings
Support for WAP
2 baseline
The Ericsson-Nokia
solution
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
The Ericsson-Nokia
solution
A question whether to
install, with the code if
available is asked. The user
may have to choose to
create a new profile or to
replace an existing profile
The Ericsson-Nokia
solution
Same interface as above
Yes, but not if the set is pre-configured in the factory and locked
31
White paper
OMA Client Provisioning
Uses security mechanism (SEC)
methods according to WAP-183-
ProvCont-20010724-a. See
www.openmobilealliance.org
OMA Client Provisioning
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
OMA Client Provisioning
If the settings previously installed
were privileged or have higher
priority, the settings might not be
possible to install again unless the
terminal is reset, otherwise as above
R300
May 2008
Advertisement
Table of Contents
