Table of Contents
Advertisement
OMA Data Synchronisation (SyncML™) technical data
Feature
SyncML compliance
Basic data formats
Option for operators to extend
SyncML functionality
Option to synchronize other
phones using SyncML
Transport method for SyncML
messages
Synchronisation application
placement
Option 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 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)
Ability to deal with multiple servers No
Ability to perform conflict
resolution actions
Browser technical data
Feature
Back to previous page
Bearer type GPRS (IP)
Bearer type GSM data (IP)
Support for SyncML
The phone is fully SyncML compliant, having passed SyncML
conformance testing. SyncML 1.1.2 is used and supported in
Server-alerted synchronisation
Contacts: vCard 2.1, Calendar: vCalendar 1.0 (vEvent), Tasks:
vCalendar 1.0 (vTodo)
The device may be configured to include preset SyncML settings,
and SyncML 1.1.2 is used
No
HTTP
Inside the phone
Yes
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
It uses a change log where it marks the contact as updated.
No
Support in the browser
Yes
Yes
Yes, ISDN and analogue
37
White paper
S312
September 2009
Advertisement
Table of Contents
