low connection reliability and high network latency. SyncML supports synchronization over WAP, HTTP or OBEX. As an open,
What information can be synchronized in the phone?
Application | Remote sync | Local sync |
|
|
|
Contacts | Yes | Yes |
|
|
|
Calendar | Yes | Yes |
|
|
|
Tasks | Yes | Yes |
|
|
|
Notes | Yes | Yes |
|
|
|
Benefits of a common synchronization protocol
End users
Today’s user of mobile devices probably uses a different synchronization product with every device. Each technology can synchronize only a few applications, or is limited to a particular type of network connection. This arrangement is expensive to install, confusing to configure and operate, and costly to administer. With SyncML, users will be able to buy devices that synchronize with a broader range of data.
Device manufacturers
Device manufacturers will benefit from a common protocol that will make the device interoperable with a broader range of applications, services, and network and transmission technologies.
Service providers
Service providers moving into the growth arena of application hosting are particularly concerned that a proliferation of synchronization technologies will make it impossible to deploy and support their customers in a
White Paper Z500a
Application developers
Choosing to support multiple synchronization technologies enables an application to support more types of devices and networked data, but that choice comes at a cost. With SyncML, application developers will be able to develop an application that can connect to a more diverse set of devices and network data.
Network operators
As multiple applications that need remote synchronization over WAP are developed, there will be an automatic growth of revenue for network operators.
18 | June 2004 |