Page 3 of 13

FUNDAMENTAL DESIGN

The architecture is based on the notion of treating the radio interface as a logical bus in the PC. Devices dynamically come into or go out of communication range of the Bluetooth module built into the notebook computer. This is analogous to hardware being plugged into or taken out of a physical bus inside the PC. The differences are in terms of the frequency with which Bluetooth devices transition into or out of communication range, and the large number (potentially) of Bluetooth devices that get virtually plugged into the PC when compared to a physical bus.

The responsibility of enumerating devices that are in range of the Bluetooth bus rests with an RF Bus Driver (RFBD). In addition to WDM bus driver functionality, RFBD processes the results of the inquiry process for discovering Bluetooth devices in range: the user drives this inquiry process. This is followed by discovery of services within these devices using Bluetooth SDP. The protocol part of SDP is implemented by RFBD. The top-level searches are handled in the Bluetooth Executive (described in the next section).

The Bluetooth usage models are supported by RFBD loading the appropriate client drivers based on device and service information obtained above.

Custom drivers can be loaded in response to devices discovery using Bluetooth Plug and Play [7]. This provides a framework for third parties to leverage unique features in their devices while reusing the Intel stack.