Symbian
Symbian Developer Library

SYMBIAN OS V9.4

Feedback

[Index] [Previous] [Next]


Phone book synchroniser overview

[Top]


Purpose

The Phonebook Synchroniser synchronises the two stores of address information on a Symbian OS phone, the phonebooks on the phone's ICC (on GSM phones called the SIM card), and the Contacts Database.

To do this, the Phonebook Synchroniser monitors the ICC phonebook, and dynamically maintains a cache of its entries in the Contacts Database. Applications can then access this cache through the Contacts Model API. Applications can also use the Contacts Model API to add and change ICC phonebook entries: the Contacts Model passes such requests to the Phonebook Synchroniser, which handles the interfacing to the phonebook itself.

This architecture gives a unified and simple-to-use approach to accessing all address information on the device. The underlying ETel phonebook interface returns entries as tagged byte-streams, which require considerable parsing effort, which would not be simple for each application to code itself.

[Top]


Architectual relationships

The Phonebook Synchroniser uses the ETel Server in order to read, write and delete the ICC phonebook entries. ETel will also provide phone or network driven notifications of changes in ICC phonebook entries.

The Phonebook Synchroniser also uses the Contacts Model in order to read, write and delete contacts items from the Contacts Database.

The diagram below shows the Phonebook Synchroniser and related components.

Phonebook Synchroniser and related     c...


Phonebook Synchroniser and related components

Note that:

[Top]


Description

The Phonebook Synchroniser API has a single client class RPhoneBookSession. This is a session to the Phonebook Synchroniser server, and provides functions to:

The Contacts Model class that allows access to ICC entries is CContactICCEntry.

[Top]


See also

Using Contacts Model