Specifications

Windows Embedded Automotive 7 Deep Dive: Phone Core and Media Core 37
Figure 8 shows the phonebook architecture.
Figure 8: Phonebook architecture
Phonebooks are stored on a per-phone basis. Automotive 7 provides the following high-level
phonebook storage functions:
• When a phone is first paired the phonebook is downloaded from the phone and stored
locally.
• When a paired phone is reconnected, Automotive 7 refreshes the stored phonebook.
• When a paired phone is disconnected, Automotive 7 does not delete the phonebook,
but keeps it in storage.
• When a paired phone is deleted, the stored phonebook associated with that phone is
also deleted.
Phonebook Text Storage
Windows Embedded Automotive 7 can store phonebooks in flash storage as simple text files.
The maximum text file size is 384 KB, which allows approximately 2,000 contact names with an
average of four phone numbers per name to be stored. Note that the total number of contact
names cannot exceed 2,000. Contacts can have more than four phone numbers, but the
additional space usage may reduce the number of contacts available as the storage space
cannot exceed the 384 KB limit.
Phonebook Storage Using the Pocket Outlook Object Model
The Pocket Outlook Object Model (POOM) is a Component Object Model (COM)-based library
that provides access to personal information manager (PIM) data on mobile devices.
Automotive 7 includes a customized version of the POOM component that is optimized for use
in automotive applications.