| T68i | |
| White Paper, April 2002 | |
SyncML technical data |
|
|
|
|
|
Feature | Support for Sync ML in the T68i | |
|
|
|
SyncML compliance | The handset is fully SyncML compliant (it passed both | |
| SyncML Conformance and Interoperability testing [SyncFest]) | |
|
|
|
Basic data formats | Contacts: vCard 2.1, Calendar: vCalendar 1.0, Tasks: vTodo | |
| 1.0. |
|
|
|
|
Possibility for operators to extend | No | |
SyncML functionlity |
|
|
|
|
|
Possibility to synchronize other | No | |
handsets using SyncML |
|
|
|
|
|
Transport method for SyncML | WSP (i.e. using a WAP connection) | |
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 synced (on/off), WAP Account, Sync Sound | |
|
|
|
Mechanisms used by the handset to | It uses a changelog 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 |
|
|
ware made to the address book) |
|
|
|
|
|
Ability to deal with multiple servers | No | |
|
|
|
Ability to perform conflict resolution | No | |
actions |
|
|
|
|
|
68