Filter
Top Products
T600/T602
White Paper, September 2002
7
Technical specifications of the WAP browser
*) When creating WML applications, it is recom-
mended always to save the page contents as
UTF8, and 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 the market the
phone is intended for. Also, please note that the
phone may not support input on a WAP Service
which uses certain characters (MMI languages),
even if those characters are supported for brows-
ing in the phone.
Feature Support in the T600/T602 WAP browser
Authentication WAP 1.2.1 Server applications may request Basic Authentication.
Gateway may request Authentication during connection setup.
Back to previous page Yes
Bearer type GSMData (IP) Yes, ISDN and analog
Bearer type SMS No
Bookmarks Yes, up to 8 named bookmarks for easy access to frequently visited
pages
Cache Yes
Character sets* UTF8 (Default), USAASCII, Latin 1, UCS2
Colour 1 bit (b/w)
Homepage Yes, up to 8 different, one for each WAP profile
Hyperlinks in Text Yes, highlighted by inverse video
Hyperlinks in Images Yes, indicated by a frame
Image Animation No
Image Formats WBMP, no transparent layers
Network Settings Up to 8 different settings available by selecting WAP profile (Intranet,
Internet, Banking, Gateway etc.)
OTA Support Yes
PPP Authentication PAP
Reload page Yes
Speed 9.6 kbit/s or 14.4 kbit/s
Tables Yes
WAP/WML WAP 1.1 & 1.2.1 compliant, WMLScript
Layers implemented: WAE, WSP, WDP, WTLS, WTP
WAP profiles 8 WAP profiles, each with its own settings