White Paper T630/T628
SyncML technical data
Feature | Support for Sync ML in the T630/T628 |
|
|
SyncML compliance | The handset is fully SyncML compliant (it passed both Syn- |
| cML Conformance and Inter operability testing [SyncFest]) |
|
|
Basic data formats | Contacts: vCard 2.1, Calendar: vCalendar 1.0, Tasks: vTodo |
| 1.0. |
|
|
Possibility for operators to extend | No |
SyncML functionality |
|
|
|
Possibility to synchronize other hand- | No |
sets using SyncML |
|
|
|
Transport method for SyncML mes- | WSP (i.e. using a WAP connection) |
sages |
|
|
|
Synchronization application place- | Inside the handset |
ment |
|
|
|
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 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 | No |
|
|
Ability to perform conflict resolution | No |
actions |
|
|
|
Infrared transceiver technical data
Signal in | Support in |
|
|
CD (Carrier | No. Set stati- |
Detect) | cally |
|
|
CTS (Clear To | Yes |
Send) |
|
|
|
83 | October 2003 |
