Specifications

Windows Embedded Automotive 7 Deep Dive: Phone Core and Media Core 40
Phonebook Implementations
Automotive 7 provides modern phonebook implementation types while remaining compatible
with prior Microsoft Auto phonebook types. All elements of pre-Microsoft Auto 4.0 phonebook
types are statically built into the HFP service.
Microsoft recommends using the Sync Manager because it can manage multiple download
types, it is extensible to providing new services and it can handle phonebook, calendar, and
email synchronizations. Table 15 lists the supported phonebook implementation types.
Table 15: Supported phonebook implementation types
Phonebook Implementation Type
Description
Sync Manager
Windows Embedded Automotive 7 Sync Manager provides phonebook
synchronization between Windows Embedded Automotive 7 systems
and Bluetooth devices. Sync Manager calls the various APIs for PBAP,
SyncML, ATCmd, SYNC, and OBEX to coordinate the download of
calendar and contact information from Bluetooth phones. By default,
Sync Manager automatically downloads vCard calendar and
phonebook information from Bluetooth devices. Sync Manager is fully
tested with devices for complete legacy phonebook compatibility. It
utilizes both POOM and a cache mechanism for improved speed. It
also includes RAM budgeting, multi-number handling, and command
and private OBEX store strategies. If POOM storage is used, all
information is downloaded, including appointments. Recursion and
notifications are supported.
Legacy phonebook
The legacy phonebook type, used in Microsoft Automotive version 4.0
and earlier, uses a memory structure and flat flash file to store
phonebook contacts. Phonebooks downloaded using this method are
stored in a structure written to a persistent flat file structure in flash
memory and then read into memory as cache.
If file storage is used, only names and phone numbers are saved; no
calendar information is downloaded.
OBEX Phonebook Stores
Windows Embedded Automotive 7 supports two OBEX storage methods: the common OBEX
phonebook method and the private OBEX phonebook method.
The common OBEX phonebook method assigns a phonebook to the car, which is available to all
of the car’s users. Any contact received via OBEX is stored in a common phonebook.
The private OBEX phonebook method maintains a relationship with the last connected phone
such that any contact received from any previously paired device is saved to the phonebook of
the most recently connected phone. A sophisticated merging mechanism allows the HFPAPI to
view the private auto-downloaded and private OBEX stores as a single phonebook location.
Depending on the application UI, this method can be used to allow users to download the
private phonebook associated with their individual phone with contacts from a laptop computer
or personal digital assistant (PDA) device.