Oma Data Synchronization (Syncml™) Technical Data - Sony Ericsson TM506 Product White Paper

Dimension
Power consumption
Data transmission rate
OMA Data Synchronization (SyncML™) technical data
Feature
SyncML compliance
Basic data formats
Possibility for operators to extend
SyncML functionality
Transport method for SyncML
messages
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
Ability to deal with multiple servers Yes
Ability to perform conflict
resolution actions
Support for T-Mobile Mobile
Backup
Support
GSM host processor excluded:
• Standby, Bluetooth On mode: <0.6 mA
• Voice to headset (HV3 master): 11 mA (7 mA with EDR func-
tionality, 2EV3 master). Dependent on various parameters
such as if the phone is master or slave
• Data mode average: 27mA at 172.8 Kbps symmetrical (DH1)
• Data speed at least 800 Kbps on a Dial-up Networking con-
nection (requires access to HSDPA network and may be lim-
ited by capacity situation on the 3G base station)
• Data speed typically 1.0 Mbps on an Object Push connection
between two phones (in case of using similar phones and if
no other Bluetooth devices are connected)
Support for Sync ML
The phone is fully SyncML compliant, having passed SyncML
Conformance testing. OMA DS 1.2 or OMA DS 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
HTTP, HTTPS, OBEX (USB, Bluetooth)
Yes
Server URL, Username, User PWD, Paths to databases (Calendar,
Contacts, Notes, Tasks and Bookmarks), UserID and PWD for
databases, Databases to be synchronized (On/Off), Internet profile,
Synchronization interval, Server ID and Server PWD, permission to
allow server-alerted synchronization and roaming options. Can be
provisioned with OMA Client provisioning v1.1 and OMA Device
Management v1.2
Yes
Yes
46
White paper TM506
August 2008