White paper
S312
37
September 2009
OMA Data Synchronisation (SyncML™) technical data
Browser technical data
Feature
Support for SyncML
SyncML compliance
The phone is fully SyncML compliant, having passed SyncML
conformance testing. SyncML 1.1.2 is used and supported in
Server-alerted synchronisation
Basic data formats
Contacts: vCard 2.1, Calendar: vCalendar 1.0 (vEvent), Tasks:
vCalendar 1.0 (vTodo)
Option for operators to extend
SyncML functionality
The device may be configured to include preset SyncML settings,
and SyncML 1.1.2 is used
Option to synchronize other
phones using SyncML
No
Transport method for SyncML
messages
HTTP
Synchronisation application
placement
Inside the phone
Option for the user to configure
login parameters (for example,
username and password) to
access the remote database
Yes
Configuration parameters that can
be entered/modified by the user
Server URL, Username, User PWD, Paths to databases (Calendar,
Contacts, Tasks and Notes), Username and PWD for Databases,
Databases to be synchronized (on/off), Internet profile,
Synchronisation interval, Server ID and Server PWD, and
permission to allow server-alerted synchronisation. Can be
provisioned with OMA Client provisioning v1.1
Mechanisms used by the phone to
capture changes made by the end
user (that is how does the SyncML
client in the phone know which
changes were made to the address
book)
It uses a change log where it marks the contact as updated.
Ability to deal with multiple servers
No
Ability to perform conflict
resolution actions
No
Feature
Support in the browser
Back to previous page
Yes
Bearer type GPRS (IP)
Yes
Bearer type GSM data (IP)
Yes, ISDN and analogue
