Oma Data Synchronization (Syncml) Technical Data - Sony Ericsson K800 White Paper

OMA Data Synchronization (SyncML) technical data

Feature
SyncML compliance
Basic data formats
Possibility for operators to extend
SyncML functionality.
Possibility to synchronize other
handsets using SyncML.
Transport method for SyncML
messages.
Synchronization application
placement.
Possibility for the user to configure
login parameters (for example,
username and password) to access
the remote database.
Configuration parameters that can
be entered/modified by the user.
Mechanisms used by the handset
to capture changes made by the
end-user (i.e. how does the SyncML
client in the handset know which
changes were made to the address
book).
Ability to deal with multiple servers. Yes
Ability to perform conflict resolution
actions.
Support for Sync ML
The handset is fully SyncML compliant, having passed SyncML
Conformance testing. SyncML 1.2 or SyncML 1.1.2 is used
depending on configuration and both are supported in Server-
alerted synchronization.
Contacts: vCard 2.1, Calendar: vCalendar 1.0 (vEvent)
Tasks: vCalendar 1.0 (vTodo)
Notes: text/plain, Bookmarks:vBookmark 1.0
The device may be configured to include preset SyncML settings,
and to control whether SyncML 1.1 or SyncML 1.2 will be used.
No
HTTP, OBEX (IR, USB, Bluetooth)
Inside the handset.
Yes
Server URL, Username, User PWD, Paths to databases (Calendar,
Contacts, Tasks, Notes and Bookmarks), UserID and PWD for
Databases, Databases to be synchronized (on/off), Internet profile,
Synchronization interval, Server ID and Server PWD, and permission
to allow server-alerted synchronization.
Can be provisioned with Ericsson Nokia OTA Settings Specification
v7.1, OMA Client provisioning v1.1, and OMA Device Management
1.2
It uses a change log where it marks the contact as updated.
No
43
White Paper K800
June 2006