Filter
Top Products
White paper W580
48 June 2008
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 WAP-183-
ProvCont-20010724-a (see
www.openmobilealliance.org).
Interface
Bearer The Ericsson-Nokia
solution
OMA Client 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.
OTA via Cell Broadcast - The user is asked whether to accept
the received settings or not.
Re-provisioning Interface The Ericsson-Nokia
solution
OMA Client Provisioning
OTA via SMS Same interface as above. 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.
OTA via Cell Broadcast - 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.
Carrier reset/provisioning Yes, but not if the set is pre-configured in the factory and locked.
SWIM Not used for provisioning.
The SWIM is only used for WAP security, digital signatures.
SWIM certificate Both client and trusted certificates can be used for digital
signatures.
Application provisioning
Preferred bearer customization Yes
Email provisioning Yes, through Smart Messaging or OMA Client Provisioning.
Other applications/features Yes (MMS, SyncML, Wireless Village).
Technologies
OMA Client provisioning Yes, WAP provisioning document v1.0.
Feature Support for WAP