Specifications

Windows Embedded Automotive 7 Deep Dive: Phone Core and Media Core 52
Key Value
Description
eCallerIDSupport
Phone supports AT+CLIP.
eSMSCmdSupport
This setting can have three values:
• 2 – unknown
• 1 – supported
• 0 – not supported
This value is initially it is set to 2. At the first connection, this value gets set to
either 0 or 1 depending on whether or not the phone passes the SMS scan. In
some application designs, if this value is 0, users cannot enter the SMS
application. A value of 0 should not get changed to 1 via the API unless the
phone passes SMS scan. A value of 1 should never get changed to 0 even if the
phone later fails SMS scan.
eSMSOffsetMEIndex
On some phones the ME index is incorrectly reported by the handset. This
value notifies the application of the offset should the phone exhibit this issue.
dwRingEventAgedoutPeriod
This is the maximum ring period of the phone as learned by the software. This
is used internally in multi-call scenarios to improve accuracy.
ePBAPSupport
Phone supports PBAP as indicated by the existence of a PSE port.
dwBRSFSupport dwCHLDSupport
These values are pass throughs for the phones BRSF and CHLD responses.
Connection Manager
The Connection Manager is the central component for managing connections on the
Windows Embedded Automotive 7 platform. Connection Manager provides an API to let
applications request connections, specify priorities, and close connections after use. It can be
configured to manage platform network connections including embedded and Bluetooth-
connected phones, wireless connections (WLAN), and Wi-Fi. In the Automotive 7 default
configuration the Connection Manager is used to manage voice and data calls on the embedded
phone, and voice and data calls on the Bluetooth-connected phone.
When an application requests a network connection, the following steps occur:
1. The Connection Manager first retrieves all the possible connections from a set of
connection service providers (CSPs).
2. The Connection Manager then associates a set of costs with these routes and ultimately
determines the optimal connection based on cost, latency, bandwidth, and other
factors.
3. The Connection Manager queues the requested connection and uses the CSP to
establish the connection at the appropriate time.
Figure 14 provides a schematic of the Connection Manager.