White Paper Z500a
Dimension | Support |
|
|
SIM | EDGE/GPRS aware, as well as |
| supported. |
|
|
AT commands supported | AT+CGDCONT - define PDP context |
| AT+CGQREQ - Quality of Service Profile (requested) |
| AT+CGQMIN - Quality of Service Profile (Minimum Acceptable) |
| AT+CGATT - packet domain service attach or detach |
| AT+CGACT - PDP context activate or deactivate |
| AT+CGDATA - enter data state |
| AT+CGCLASS - GPRS mobile station class |
|
|
SyncML technical data
Feature | Support for Sync ML |
|
|
SyncML compliance | The handset is fully SyncML compliant. |
|
|
Basic data formats | Contacts: vCard 2.1, Calendar: vCalendar 1.0, Tasks: vTodo 1.0, |
| Notes: text/plain. |
|
|
Possibility for operators to extend | No |
SyncML functionality |
|
|
|
Possibility to synchronize other | No |
handsets using SyncML |
|
|
|
Transport method for SyncML | WSP (i.e. using a WAP connection), HTTP, OBEX (RS232, USB). |
messages |
|
|
|
Synchronization application | Inside the handset |
placement |
|
|
|
Possibility for the user to configure | Yes |
login parameters (e.g. username and |
|
password) to access the remote |
|
database |
|
|
|
Configuration parameters that can be | Server URL, Server UserID, Server PWD, Paths to databases |
entered/modified by the user | (Calendar, Contacts, Tasks) UserID and PWD for Databases, |
| Databases to be synched (on/off), WAP Account. |
|
|
Mechanisms used by the handset to | It uses a change log where it marks the contact as updated |
capture changes made by the end user |
|
(i.e. how does the SyncML client in |
|
your handset know which changes |
|
were made to the address book) |
|
|
|
Ability to deal with multiple servers | Yes |
|
|
Ability to perform conflict resolution | No |
actions |
|
|
|
52 | June 2004 |
