Bluetooth PC Stacks

Agenda

Design guidelines
User experience
Bluetooth™ architecture in Windows® XP
Hardware

Design Guidelines

Must be robust and reliable
A bus is a

User Experience

Modems
Use Add Modem Wizard
Discoverability is an issue
IPv6

User Experience

Printers
Use Add Printer Wizard
No authentication

Bluetooth™ Developers Conference, December

User Experience

HID
Automatic detection of keyboards
Add Hardware Wizard
Keyboard must

User Experience

Control panel
Geek “tool” not intended for your mother

User Experience

Summary:
Experience should not be Bluetooth specific
Need to work

Windows XP Bluetooth Architecture

Top scenarios:
Scenario #1: Always connected
- DUN, PAN

Windows XP Bluetooth Architecture

Profile support
HCRP
DUN
HID
PAN (IPv6

Windows XP Bluetooth Architecture

Why IP?
A Bluetooth device talking over IP

Windows XP Bluetooth Architecture

Bluetooth™ Developers Conference, December 11-13, 2001, a Key3Studios

Windows XP Bluetooth Architecture

Standard SIG-defined miniports
Transparent pass-thru
Lowers development costs

Windows XP Bluetooth Architecture

BTHPORT
L2CAP, HCI and SDP
No SCO

Bluetooth™

Windows XP Bluetooth Architecture

Windows XP Application API set
Winsock

Windows XP Bluetooth Architecture

Windows XP release plans:
Next beta in Q1

Hardware Design Issues

Sideband power management
USB bus reset by device

General Hardware Logo Requirements

System Testing
Currently a system can get the

Bluetooth Logo Program - System

Logo Requirements
Bluetooth Qualification to v1.1
HCI

Bluetooth Logo Program - Peripherals

Hardware Compatibility Tests
Device Class Tests –

Bluetooth PC Stacks - Summary

Bluetooth can be a very compelling

Microsoft Resources

General
http://www.microsoft.com/hwdev/
WHQL
http://www.microsoft.com/hwtest/
Windows Logo Program
http://www.microsoft.com/winlogo/

Bluetooth™ Developers Conference, December