Specifications

18
*) When creating WML applications, it is recommended always to save the page contents as
UTF8, and that this is clearly indicated in the pages before publishing. This ensures that the
contents of the application can be viewed, regardless of character sets used in gateways and the
phone. All characters are not supported in all phones. The software version depends on which
market the phone is associated to. Also, please note that the phone may not support input on a
WAP Service which uses certain characters (languages), even if those characters are supported
for browsing in the phone.
Hyperlinks in Images Yes, indicated by a frame
Image Animation No
Image Formats GIF (interlaced and non-interlaced), WBMP, no transparent
layers.
Network Settings Up to 5 different settings available by selecting WAP proÞle
(Intranet, Internet, Banking, Gateway etc)
OTA Support Yes
PPP Authentication PAP, CHAP and MS-CHAP
Reload page Yes
Tables Yes
User Agent ProÞles Yes, list of client characteristics - e.g. display size
WAP/WML WAP June2000 (WAP 1.2.1)
WAP proÞles 5 WAP proÞles, each with its own settings
WIM on SIM (security) Yes, Storage of Private keys and Client CertiÞcates, execu-
tion of security algorithm
WTLS (security) Yes,
WTLS Class 1 - Encoding
WTLS Class 2 - Encoding + Server Authentication. Root
CertiÞcates needed in phone
WTLS Class 3 - Encoding + Server Authentication, Client
CertiÞcation, Client CertiÞcates needed in phone
Feature Support in the R520 WAP browser