| White Paper T610/612 |
|
|
Feature | Support in the T610/612 for WAP |
|
|
SWIM certificate | Both client and trusted certificates can be used for WTLS connections |
| and digital signatures. |
| No new certificates can be stored and no old ones can be removed by the |
| terminal. |
|
|
Applicative provisioning |
|
|
|
Preferred bearer customization | Yes |
|
|
No | |
|
|
Other applications/features | Yes. MMS, SyncML |
|
|
Technologies |
|
|
|
WAP Forum OTA provisioning | No |
|
|
Openwave OTA | No |
|
|
Other | Yes. The |
|
|
Provisioning bearer | SMS |
|
|
Parameter sets available | 5 |
|
|
Parameter sets for OTA modification | 5 |
|
|
|
|
PUSH |
|
|
|
Content types |
|
|
|
Service Indication (SI) | Yes |
|
|
Service Loading (SL) | Yes |
|
|
Cache Operation (CO) content type | Yes |
|
|
Session Initiation Application (SIA) | Yes |
|
|
Man Machine Interface |
|
|
|
SI/content retrieval postponing | Yes |
|
|
SI menu structure accessability | WAP services, Push inbox |
|
|
SL reception warning | The user can make a choice if a dialog is wanted or not before loading |
| the SL. |
| WAP services/options/common/Push access/prompt |
|
|
SIA reception warning | Yes |
|
|
Cache size limitations | If the inbox is full and a new push is received, the oldest push in the |
| inbox will be discarded. |
|
|
Number of push messages | Depending on the size of the push messages. Around 20 push messages |
| with a size of 500 bytes can be stored. |
|
|
Push | Yes. WAP services/options/common/Push access/Off |
|
|
63
