Constructor.

This function opens a RMobilePhoneBookStore sub-session from a previously opened RMobilePhone sub-session. The name of the phone book to open is passed in the aStore parameter. The type of valid phone books can be obtained by RMobilePhone::GetPhoneStoreInfo().

This method opens a RMobilePhoneBookStore subsession from RMobilePhone.

This API method overloads the normal RMobilePhoneBookStore::Open. The phonebook mode is indicated by the aMode parameter, which allows the client to distinguish between the different sets of phonebooks that can be present on the ICC or ME side. E.g. a client can open both the GSM ADN phonebook and the USIM ADN phonebook on a UICC. The client would then be able to switch on the fly between the GSM/global phonebook and the (active) USIM Application phonebook.

A UICC can comprise of many USIM applications and a GSM application. Only one of application can be active at any one point. The USIM applications contain their own phonebooks (ADN, FDN, etc..). To open a USIM Application phonebook, the USIM Application must be active. It is not possible to access a phonebook of a USIM Application that is not currently active.

This API method opens a RMobilePhoneBookStore sub-session from a previously opened RMobilePhone sub-session. The name of the phone book to open is passed in the aStore parameter. The names of known and valid phone books for this API methods are listed in the table below. The phone may not support all of these phone books so clients should check which are available using the method in the previous section 4.8.1.

Note for the TSY development: Internally ETel will pass to the TSY one TDesC variable containing: the phonebookname as defined in 8.4.1 for GSM and CDMA ICCs or the phonebookname followed by a delimiting character (i.e. the PHBOOK_DELIMITER defined in ETelMM.h) and the ICC type (i.e. UICC) for UMTS.

This method reads one or more entries from a phonebook store. The reading will start at the slot specified by aIndex and will stop either after aNumSlots of slots have been read or no more whole phonebook entries can fit in the size of the supplied aPBData parameter.

If there are no used entries in the slots requested then KErrNotFound will be returned.

Example: If aIndex=1 and aNumSlots=1 then one slot (slot number 1) will be read and if used, this entry will be returned within aPBData.

This member function writes one phonebook entry to the store. This member function is a specialised version of the base class RMobilePhoneStore::Write() and all clients of RMobilePhoneBookStore should use this specialised version rather than the base class version. The phonebook data will be in aPBData which will contain the encoded byte stream of a TLV format phonebook entry.

Note:

Use RTelSubSessionBase::CancelAsyncRequest(EMobilePhoneStoreWrite) to cancel a previously placed asynchronous Write request.

The following Tag IDs are used to encode/decode the phonebook entries to/from the TLV format. Each field will have a unique identifier and will be followed by the field length. The type of data associated with the field is also specified below.

Modes: Common

Describes the specialized phone book capabilities.

Modes: Common

Described the location of the phone book.

Modes: Common for all

Defines a modifiable buffer descriptor to contain the phone book identity. Used in TMobilePhoneBookInfoV1.

Packages the TMobilePhoneBookInfoV1 into a TMobilePhoneBookInfoV1Pckg.

Packages the TMobilePhoneBookInfoV2 into a TMobilePhoneBookInfoV1Pckg.

Packages the TMobilePhoneBookInfoV5 into a TMobilePhoneBookInfoV5Pckg.