学步园

Two roles are defined for Bluetooth-enabled devices that support DUN:

• Data Terminal (DT) role: this role is for the device that requires access to the data network; for example, a portable navigation device (PND).
• Gateway role: this role is for the device that serves as modem. It enables the Data Terminal device to connect to a public network such as the Internet; for example, a mobile phone.

A Windows Embedded NavReady powered device supports the Data Terminal (DT) role only.

The following illustration shows the Bluetooth DUN architecture:

With support for DUN, a Windows Embedded NavReady powered device can create a connection to a data network by using the capabilities of a paired Bluetooth-enabled device that supports Bluetooth DUN. The Windows Embedded NavReady powered device can use that
paired device as a wireless modem.

An application that requires Internet connectivity can use Connection Manager to establish a dial-up networking connection.
Dial-up networking enables a Windows Embedded NavReady powered device to access network resources from a remote location, such as a car environment.

When the application sends a connection request, Connection Manager uses the CSPRas connection service provider (CSP) to establish a dial-up networking connection. The Windows Embedded NavReady powered device internally calls
ActivateBTDevice in order to first establish the Bluetooth DUN connection to the paired device.

The DUN profile is dependent on Serial Port Profile (SPP), which creates a Bluetooth link to another Bluetooth-enabled device. This Bluetooth link acts like a wireless serial cable.

Once the Bluetooth DUN link is established, the paired device serves as a modem for the Windows Embedded NavReady powered device that is in the Data Terminal (DT) role. At this point, the paired device has a connection to the Internet, and a Windows Embedded
CE application can access this Internet connection through the Bluetooth link, thereby using the Gateway device as a wireless modem.

When the DUN profile is included in a run-time image and you use Connection Manager to create a data connection, the DUN profile is automatically utilized. For more information about how to connect by using Connection Manager, see
How to Make a Data Connection by Using Connection Manager.

Alternately, you can create the connection manually. For more information about how to connect manually, see
Creating a Data Connection That Uses Bluetooth DUN.

To include support for the DUN profile, you must include the Pairing Service Catalog item (SYSGEN_BTH_PAIRSVC) in your OS design.