White Paper J200
Feature | Support for WAP in the J200 |
|
|
Carrier reset/provisioning | Yes, but not if the set is |
|
|
Applicative provisioning |
|
|
|
Preferred bearer customization | Yes |
|
|
Other applications/features | No |
|
|
Technologies |
|
|
|
Openwave OTA | No |
|
|
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 | No |
|
|
Session Initiation Application (SIA) | No |
|
|
Man Machine Interface |
|
|
|
SI/content retrieval postponing | Yes |
|
|
SI menu structure accessibility | WAP services, Push inbox. |
|
|
SL reception warning | The user can make a choice if a dialogue is wanted or not before |
| loading the SL. |
| WAP services/options/common/Push access/prompt. |
|
|
SIA reception warning | No |
|
|
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 250 bytes can be stored. |
|
|
Push | Yes. WAP services/options/common/Push access/Off. |
|
|
Dynamic push menu changes | No. There are no changes in the menus when activating/deactivat- |
| ing push. |
|
|
Security |
|
|
|
Mechanisms for push | None |
|
|
Trust with PPG | Only |
|
|
WSP push sessions | 1 |
|
|
Denial of service/spoofing | Yes |
|
|
32 | November 2004 |
