Priority-Based Connections in Connection Manager for Portable Navigation Devices
.gif "A hyphen indicates that the information in this topic is not relevant for this platform, or that the platform does not support the API that is listed.")
.gif "A checkmark indicates that the information in this topic is relevant for this platform, and that any API listed is also supported on this platform.")
10/16/2008
Applies to Windows Embedded NavReady
Connection Manager supports establishing connections based on the priority of the connection requests.
Priority Levels
The relative priority levels for connections in Windows Embedded NavReady are as follows:
| Priority level | Connection type |
|---|---|
Priority 1 |
Bluetooth Hands-Free Profile (HFP) voice calls. |
Priority 2 |
Data connections such as Bluetooth Dial-up Networking (DUN) data connections and ActiveSync Desktop Pass-through (DTPT) data connections. |
Scenarios
The following list describes some of the scenarios that show how Connection Manager manages connection requests based on priority:
- Multiple connection requests: if Connection Manager receives multiple connection requests, Connection Manager adds each request to a list, and then establishes the connection that has the highest priority.
- Handling a connection request while a lower-priority connection is active: if a lower-priority data connection is active and a higher-priority voice connection is requested, such as when an incoming voice call arrives from Bluetooth Hands-Free Profile (HFP), the lower-priority data connection is disconnected. For more information about how to configure a connection as more secure, see Connection Manager Security for Portable Navigation Devices and Configuring a Portable Navigation Device by using OMA Client-based XML.
- Handling a connection request while a higher-priority connection is active: if a higher-priority connection is already active and Connection Manager receives a lower-priority connection request for a different destination network, the active connection remains connected and the lower-priority connection is not established. However, the requesting application can subsequently modify the priority of the connection request, for example, by setting the dwPriority member of the CONNMGR_CONNECTIONINFO structure. If the application increases the priority of the requested connection to one that is higher than the priority of the existing active connection, Connection Manager disconnects the active connection and establishes a new connection for the requesting application.
- Cached connections: if an application requests a low-background connection, which is the lowest-priority connection, and a cached connection to the same destination exists, the low-background connection uses the cached connection. The connection remains active as long as the low-background application uses it, even after the caching timer expires.
See Also
Other Resources
Connection Manager Application Development for Portable Navigation Devices