Table of Contents
Advertisement
Dimension
Coverage area
Transmission power
Frequency band
Power consumption
OMA Data Synchronization (SyncML™) technical data
Feature
SyncML compliance
Basic data formats
Option for operators to extend
SyncML functionality
Transport method for SyncML
messages
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
Ability to deal with multiple servers Yes
Ability to perform conflict
resolution actions
Support
Varies due to radio performance between the connected
devices and the occurrence of obstacles. Up to 10 metres (33
feet)
Class 1, typical +3 dBm or 2 mW
2.4 GHz
the unlicensed ISM band
–
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: 27 mA at 172.8 Kbps symmetrical (DH1)
Support for Sync ML
The phone 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 is 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
No
45
White paper
T700
November 2008
Advertisement
Table of Contents
