Specifications

Windows Embedded Automotive 7 Deep Dive: Phone Core and Media Core 38
The enhanced POOM contains the following features:
• The AUTOPOOM schema, with support for Bluetooth addresses and the Bluetooth
SyncIndex
• Support for image files (for example, images of email recipients)
• Significantly increased contact search speed
Applications can access the contacts database and read and write to it when using POOM
storage. However, the Sync Manager service assumes that other applications will only read from
the contacts database. Therefore, other applications writing to POOM storage may cause errors
in Sync Manager operations.
The following are differences in how Sync Manager handles vCard information when using
POOM storage:
• If the address is identified as a business address, then the office location is saved in the
office location field. The office location field is attached to the street field.
• The first number retrieved is saved as a mobile number. Subsequent numbers are saved
as additional mobile numbers separated by semicolons. Numbers that exceed the length
of the POOM field are discarded. The same behavior occurs with home numbers, work
numbers, and other number fields.
• When the cache is populated from the POOM storage, vCard fields in the following table
are mapped to the corresponding HFP service-defined fields.
Table 13 enumerates the vCard to HFP field mappings.
Table 13: vCard field to HFP field mappings
vCard Field
HFP Field
BusinessTelephoneNumber
HFP_PNTYPE_LOC_WORK
HomeTelephoneNumber
HFP_PNTYPE_LOC_HOME
OtherTelephoneNumber
HFP_PNTYPE_UNKNOWN
MobileTelephoneNumber
HFP_PNTYPE_LOC_MOBILE
Applications can save multiple records into POOM that contain the same contact name. To
ensure the best user experience when the user does this, consider the following items when
designing applications:
• When using the POOM synchronization manager with cache implementation, which is
the default setting, the name of the contact should serve as the unique identifier for
each record in your UI. The APIs are designed using this assumption and combine all
phone numbers that are listed under a first name and last name pair when queried.
Contact names and phone numbers should be retrieved through the HFP APIs to take
advantage of the cache when retrieval time is important (for example, during an
incoming call). Contact names, phone numbers, and all other contact fields can be
retrieved when contacts are accessed by using the POOM APIs.
• When retrieving data from the POOM based on a first name and last name combination,
the application should continue to search even after a single entry is found in the