Bluetooth™ Wireless System

Joe Decuir
Microsoft
Chair, Seattle COM-19
[email protected]

Note: Bluetooth™ is a trademark

of Ericsson
 Agenda
• Wireless Overview
– http://www/microsoft.com/hwdev/wireless
• Bluetooth System Overview
– http://www.microsoft.com/winhec
• Windows Bluetooth Stack
– http://www.microsoft.com/hwdev/bluetooth
 Wireless Overview
• Wireless trends
– Wide Area Networks (WAN)
– Local Area Networks (LAN)
– Personal Area Networks (PAN)
• Scenarios
– Adhoc
– Home
– Small business
– Enterprise, ISP
 Wireless Trends
• IP networks
• Always connected (packet vs circuit mode)
• Increased bandwidth
• Convenience
• Moving from vertical market to horizontal markets
• Moving from proprietary to standards based
• Proliferation of smart devices
• New scenarios enabled
• Outsourcing
• Adhoc networks
 Wireless Media
• Infrared: short range and directional
• Personal Area Networks: short range radio
– Bluetooth, IEEE 802.15.1
• Local Area Networks: medium range radio
– IEEE 802.11(a,b), HyperLAN, HomeRF, etc
• Wide Area Networks: long range radio
– Cellular systems: GSM, TDMA, CDMA, “3G”
• Broadband: high speed fixed radio
– IEEE 802.16
 Wide-Area Wireless
Wide Area Wireless 1999 2000 2001 2002 2003
US Summary Q1 Q2 Q3 Q4 Q1 Q2 Q3 Q4 Q1 Q2 Q3 Q4 Q1 Q2 Q3 Q4 Q1 Q2 Q3 Q4

Mobitex 8, DataTAC 19.2 Packet

CDPD 19.2 Packet
GSM 9.6 Circuit-Switched

General Deployment
iDEN - Nextel - 9.6 Packet and
Circuit-Switched
Trials Start

Trials General Deployment

cdmaOne Circuit-Switched
AirTouch
14.4 - IS-95A GTE, Sprint

Limited Deployment
cdma2000 1XRTT Trials
153 Kbps - Packet Start
General Deployment
19.2 Rx/9.6 Tx 57.6 Kbps
GSM GPRS Technologies Trials
Start
38.4 Rx/9.6 Tx
Limited Deployment
EDGE
Trials Start
384 Kbps Packet
General Deployment
 Local-Area Wireless
Local Area Network
1999 2000 2001 2002 2003
Technology Q1 Q2 Q3 Q4 Q1 Q2 Q3 Q4 Q1 Q2 Q3 Q4 Q1 Q2 Q3 Q4 Q1 Q2 Q3 Q4

802.11 (FHSS) 2.4 GHz

1 Mbps
Freq. Hopped Spread Spectrum

802.11 (DSSS) 2.4 GHz

1 or 2 Mbps
Direct Sequence Spread Spectrum

Hiperlan
Initial
23.5 Mbps
Shipments
High Performance Radio LAN

P802.11b (DSSS) 2.4 GHz

Initial
11 Mbps
Shipments
Direct Sequence Spread Spectrum Final
Specification Initial Mobile
P802.11a 5 GHz Specifications Shipments
54 Mbps Approved
Direct Sequence Spread Spectrum
 Personal Area Wireless
Local Area Network 1999 2000 2001 2002 2003
Technology Q1 Q2 Q3 Q4 Q1 Q2 Q3 Q4 Q1 Q2 Q3 Q4 Q1 Q2 Q3 Q4 Q1 Q2 Q3 Q4

IrDA
4Mbps

Computer Integrated Products

Bluetooth Initial Shipments
Integrated Handsets
721 Kbps
PC Card and CF Module
 Ad Hoc Networks
Many diverse
devices to be Desktops,
connected Notebooks
TVs,
games

Books, tablets,
handheld PCs

Phones, Pagers
PC companions
 A Connected Home

1394

STB

IrDA

802.11

Ethernet/1394b

Internet
Bluetooth

PLC

xDSL
Cable
Satellite Phone
POTS, ISDN Residential
Gateway
 A Connected Small Office

Phone

Small 802.11
Business Bluetooth
Internet
Server

T1, T3, … Ethernet

Edge Server
 Enterprise
• Information at
GPRS
GPRS
IrDA
your fingertips
– At meetings, in the office, on the
road
– Reliable, secure, multimedia
GPRS
LAN
Bluetooth

Internet Web Server

802.11

T1, T3, … Ethernet

Proxy Server
 An ISP Connected Public Space
• Discovery of proximity
services (flight schedules at
Bluetooth

Phone
airport, mall directories, …)

GPRS
IrDA

Internet Web Server

802.11

T1, T3, … Ethernet

Proxy Server
 Wireless Architecture
Requirements
• “Just works”
• Always connected
• Unified transport: IP
• Mobility
• Unified security model
• Adhoc
• QoS
• Performance
 Windows Wireless Architecture
Dial-up Network
WinSock 2.0 Routing streaming
Networking
TAPI 3.0 Networking
APIs APIs (DirectX)
APIs
RSVP

Network Networking
UPnP 802.1X DNS DHCP
Location Services

NetBT

IP packet IP TCP/IP Protocol

Route table
filtering forwarder stacks

Packet classifier

Packet scheduler IGMP IRDP

NDIS 5.1

NDIS WAN
Ethernet TR 802.11 Affected by
PPTP Async Bluetooth RNDIS 802.1D Wireless
 Just Works
• No configuration
– Especially when roaming
• CDPD
– Configure Network Equipment Identifier
• 802.11
– Configure network name and security keys
• Per location
• Bluetooth
– Configure PIN numbers
• Per device
 What is an adhoc network?
• No network infrastructure at all
– E.g. back to back Ethernet
– Automatic IP addressing when no DHCP server available
– NetBT broadcast for adhoc name resolution
• Interconnections not managed
– Multiple interconnections to destinations
– Loops in the network
• Home network
– ICS contains DNS proxy and DDNS support for the adhoc home
network
• Service Discovery Protocols
– SSDP protocol enables UPnP discovery
– SDP protocol enables Bluetooth wireless technology discovery
– IrLAP protocol enables IrDA discovery
 IrDA Applications
• File transfer
– Integrated into shell
• Image exchange from camera
• Dial-up networking via cellphone
• Printing
• Synchronization
– E.g. PDA or cell phone to PC
 Bluetooth Applications
• Subset of IrDA
• File transfer
– Integrated into IrDA ftp transfer
• Dial-up Networking via cellphone
• Synchronization
• IrDA and Bluetooth applications are tied to
particular media
– Do not inter-operate
 Bluetooth Overview
• Genesis
• Bluetooth architectural overview
• Bluetooth Program update
 What Does Bluetooth Wireless Technology Do
For You?

Landline

Cable
Replacement

Data/Voice
Access Points

Personal Ad-hoc
Networks
 What does Bluetooth Do?

Topology Supports up to 7 simultaneous links Each link requires another cable

Flexibility Goes through walls, bodies, cloths... Line of sight or modified environment
Data rate 1 MSPS, 720 Kbps Varies with use and cost
Power 0.1 watts active power 0.05 watts active power or higher
Size/Weight 25 mm x 13 mm x 2 mm, several Size is equal to range. Typically 1-2
grams meters. Weight varies with length
(ounces to pounds)
Cost Long-term $5 per endpoint ~ $3-$100/meter (end user cost)
Range 10 meters or less Range equal to size. Typically 1-2
Up to 100 meters with PA meters
Universal Intended to work anywhere in the Cables vary with local customs
world
Security Very, link layer security, SS radio Secure (its a cable)

• Cable Replacement
 Bluetooth Genesis
• Ericsson was a participant in GSM 7.07, a
standard for connecting PCs and mobile
devices through cell phones offering circuit
mode data and fax services.
• This called for adding serial cables to cell
phones: cumbersome, easy to loose, too
many connections.
• Ericsson, a radio company, decided to
replace short cables with short range radios
 Who is Bluetooth?
Harald Blaatand “Bluetooth” II
King of Denmark 940-981
 Son of Gorm the Old (1st King of Denmark) and
Thyra Danebod (daughter of King Ethelred of
England)
This is one of two Runic stones
erected in his capitol city of
Jelling (central Jutland)
 This is the front of the stone depicting the
chivalry of Harald.
 The stone’s inscription (“runes”) say:
 Harald christianized the Danes
 Harald controlled Denmark and Norway
 Harald thinks notebooks and cellular phones
should seamlessly communicate
 What is Bluetooth?
Applications
TCP/IP HID RFCOMM Application Framework
and Support

Data Host Controller Interface

L2CAP Link Manager and

Audio
Link Manager LMP L2CAP

Baseband
Radio & Baseband
RF
Latest Version on
• A hardware description Bluetooth Website:
• An application framework www.Bluetooth.com
 What is Bluetooth?
Software
Applications
TCP/IP HID RFCOMM

Data

L2CAP
Audio
Link Manager LMP
Baseband
RF

• A hardware description
Modules
• An application framework
 Testing to Specification T e c h n o l o g y

Certification
T e c h n o l o g y

Applications Application Layer

Certification Framework Application Framework
Certification
Certification Classes
Lower Interface
TCP/IP HID RFCOMM
vCard vCal UDP
Service
Type Application Framework Certification Class
Class
vCard
vCal
IrOBEX
IrOBEX
Layer Certification Classes BT.vCard
BT.OBEX
BT.OBEX BT.vCal
UDP PPP BT.PPP BT.UDP
Service
PPP RFCOMM Lower Interface
BT.TS0710 Certification
BT.PPPClass
vCard vCal UDP IrOBEX Type
RFCOMM BT.TS0710 Class BT.OBEX
Still vCard
WAP IrOBEX
TCP/IP BT.OBEX
BT.TCP/IP BT.vCard
BT.WAP
IrOBEX PPP WAP vCalImages
Still IrOBEX
HID BT.OBEX
BT.HID BT.vCal
BT.SImg
Img
Data UDP
PPP Ctrl
Audio
IrOBEX
PPP
RFCOMM
L2CAP
RFCOMM
2
BT.PPP
BT.TS0710
BT.L2
CAP-A
BT.TS0710
2
BT.UDP
BT.PPP
BT.AudioCtrl
BT.OBEX
RFCOMM L CAP BT.L CAP-D BT.TS0710
Still WAP
TCP/IP TCP/IP
2
L CAP BT.TCP/IP
BT.L
2
CAP-D BT.WAP
BT.TCP/IP
IrOBEX PPP WAP Still Images
Audio
TS0710 TCP/IP
Img
HID HID L2HID
CAP BT.HID
BT.L2
CAP-D BT.SImg
BT.HID
Ctrl 2 2
Audio Ctrl L CAP BT.L CAP-A BT.AudioCtrl
2 2
RFCOMM L CAP BT.L CAP-D BT.TS0710
L2CAPAudio TS0710 L2CAP
TCP/IP HID
TCP/IP
HID
2
L CAP
L2CAP
2
BT.L CAP-D
Basic Layer Certification Classes
BT.L2CAP-D
BT.TCP/IP
BT.HID

Audio A Ctrl
U Service Lower Interface Certification Class

Link Manager
D
I
LM
L2CAP
LMP Basic Layer
2
Certification Audio
Type
Basic Layer Certification Classes Audio
Class
Data Data
L CAP LM BT.LM-A BT.LM-D BT.L2CAP-A BT.L2CAP-D
O
A LM BB BT.BB-A BT.BB-D BT.LM-A BT.LM-D
BB Lower Interface Certification Class
U BBService RF BT.RF BT.RF BT.BB-A BT.BB-D
BasebandD
I
LM
RF
RF Type
Air -
Audio
Class -
Data
A unit that supports both audio and data gets the certification class
2
L CAP
Example: BT.BB-A,D LM BT.LM-A BT.LM-D
A and D.
BT.RF
Audio
2
BT.L CAP-A
BT.RF
Data
BT.L2CAP-D
O LM BB BT.BB-A BT.BB-D BT.LM-A BT.LM-D
BB
BB RF BT.RF BT.RF BT.BB-A BT.BB-D
RF RF
RF Air - -
A unit that supports both audio and data gets the certification class A and D.
Example: BT.BB-A,D
BT.RF BT.RF

• Bluetooth devices will be tested against the specification

• Bluetooth Qualified Test Facilities (BQTF)
 Bluetooth Core Specifications
• A: Radio
• B: Baseband
• C: Link Manager
• D: Logical Link Control
• E: Service Discovery
• F: RFCOMM, IrDA, Telephony, WAP
• H: Host Controllers, USB, Serial, UART
• I: Compliance: Test modes, Test control interfaces
 Bluetooth RF Specifications
Specified for low cost, single chip implementation
– Noise floor margin for substrate noise and low current Low
Noise Amplifier (LNA)
– Linearity set by near-far problem
– In-band image allows low-cost low IF
– VCO phase noise enables integrated VCO
– TX-RX turn around time enables single synthesizer
– 2.4 ISM band chosen for global use and process capabilities

Sensitivity traded for low cost integration of

transceiver and baseband
 Basic Baseband Protocol Frame
Frame
fk fk+1 fk fk+1

One
Master Slot Three Slot Packet
Packet Master

One
Slave Slot
Packet Slave
One
Slot
Packet

625 us
625 us
One Slot
One Slot

• Spread spectrum frequency hopping radio

– 79 or 23* one MHz channels (*country dependent)
– Hops every packet
• Packets are 1, 3, or 5 slots long
– Frame consists of two packets
• Transmit followed by receive
– Nominally hops at 1600 times a second (1 slot packets)
 Network Topology
• Radio Designation
– Connected radios can be master or slave
– Radios are symmetric (same radio can be master or slave)
• Piconet
– Master can connect to 7 simultaneous or 200+ active slaves per piconet
– Each piconet has maximum capacity (1 MSPS)
• Unique hopping pattern/ID
• Scatternet
– High capacity system
• Minimal impact with S
up to 10 piconets
P
within range M M
– Radios can
share piconets! sb P

S
sb
P S S
 The Piconet IDa
IDd IDd

IDa D IDa P

A M
IDe
IDe
sb
E
IDa
IDb B IDb S IDa
IDc C IDc S

• All devices in a piconet hop together

– In forming a piconet, master gives slaves its clock and device ID
• Hopping pattern determined by device ID (48-bit) IDa
• Phase in hopping pattern determined by Clock
• Non-piconet devices are in standby sb
• Piconet Addressing M or S
– Active Member Address (AMA, 3-bits)
– Parked Member Address (PMA, 8-bits)
P
 Functional Overview
• Standby
Unconnected Standby
– Waiting to join a piconet Standby

• Inquire
– Ask about radios to connect
to Ttypical=2s

• Page Connecting Inquiry Page

– Connect to a States

specific radio
Ttypical=0.6s
• Connected Transmit
Connected
– Actively on a piconet Active
States
data
AMA
AMA
(master or slave)
• Park/Hold/Sniff Ttypical=2 ms Ttypical=2 ms Ttypical=2 ms
– Low Power
connected states Releases
Low Power PARK SNIFF HOLD
AMA
PMA AMA AMA
States Address
 Packet Types/Data Rates
Packet Types Data Rates (Kbps)
SEGMENT SCO link ACL link symmetric
TYPE TYPE asymmetric

0000 NULL NULL DM1 108.8 108.8 108.8

0001 POLL POLL
1
0010 FHS FHS DH1 172.8 172.8 172.8
0011 DM1 DM1
DM3 256.0 384.0 54.4
0100 DH1
0101 HV1 DH3 384.0 576.0 86.4
0110 HV2
2
0111 HV3 DM5 286.7 477.8 36.3
1000 DV
1001 AUX1 DH5 432.6 721.0 57.6
1010 DM3
1011 DH3
3
1100
1101
1110 DM5
4
1111 DH5

• ASL –Packet like behavior

• SCO – Circuit like behavior
 Mobile = Battery Life
• Low power consumption*
– Standby current < 0.3 mA
• Þ 3 months
– Voice mode 8-30 mA
• Þ 75 hours
– Data mode average 5 mA
– (0.3-30mA, 20 kbit/s, 25%)
• Þ 120 hours
• Low Power Architecture
– Programmable data length (else radio sleeps)
– Hold and Park modes 60 µA
• Devices connected but not participating
• Hold retains AMA address, Park releases AMA, gets PMA address
• Device can participate within 2 ms
– *Estimates calculated with 600 mAh battery and internal amplifier, power
will vary with implementation
 Error Handling
72b 54b 0-2745b

access code header payload

• Forward-error correction (FEC)

– headers are protected with 1/3 rate FEC and HEC
– payloads may be FEC protected
• 1/3 rate: simple bit repetition (SCO packets only)
• 2/3 rate: (10,15) shortened Hamming code
• 3/3 rate: no FEC

• ARQ (ACL packets only)

– 16-bit CRC (CRC-CCITT) & 1-bit ACK/NACK
– 1-bit sequence number
®
Bluetooth Security Model
 Bluetooth Security Features
• Fast Frequency Hopping (79 channels)
• Low Transmit Power (range <= 10m)
• Authentication of remote device
– Based on link key (128 Bit)
– May be performed in both directions
• Encryption of payload data
– Stream cipher algorithm ( 128 Bit)
– Affects all traffic on a link
• Initialization
– PIN entry by user
 Application Level Security
• Builds on-top of link-level security
– Creates trusted device groups
• Security levels for services
– Authorization required
– Authentication required
– Encryption required
• Different or higher security requirements could
be added:
– Personal authentication
– Higher security level
– Public key
 Bluetooth Is Global
• One version for the world
– Architecture compliant with global
emission rules
(2.4 GHz ISM band)
• Working through FCC, EC,
MPT for spectrum, and
power harmonization
– Architecture compliant and safe for
use on airlines
• Working with FAA, JAA, FCC, airplane
manufacturers, and airlines
– Reviewing security architecture with
affected countries
 Bluetooth Radio Modules
• Complete radio on a module
– Designed to meet “Limited Module Compliance”
(LMA) requirements
• Pre-certified to meet global regulatory requirements
• Allows devices assembled with modules to be “self-certified”
– USB Interface
– Solder-ball connections
– External Antennae

Compact
FLASH
Card

25 mm dia 17x33mm 36x43mm

 Bluetooth Protocols
WAE vCard/vCal Audio

Still Image Printing

WAP OBEX

HID TCP/UDP RFCOMM

Service Discovery IP TCS

L2CAP

Host Controller Interface

- Bluetooth Specific - Reused Spec - Modified

 Bluetooth protocols
• Host Controller Interface (HCI)
– provides a common interface between the
Bluetooth host and a Bluetooth module
• Interfaces in spec 1.0: USB; UART; RS-232
• Link Layer Control & Adaptation (L2CAP)
– A simple data link protocol over baseband
• connection-oriented & connectionless
• protocol multiplexing
• segmentation & reassembly
• QoS flow specification per connection (channel)
• group abstraction
 Bluetooth protocols
• Service Discovery Protocol (SDP)
– Defines a service record format
• Information about services provided by attributes
• Attributes composed of an ID (name) and a value
• IDs may be universally unique identifiers (UUIDs)
– Defines a inquire/response protocol for discovering
services
• Searching for and browsing services
 Bluetooth protocols
• RFCOMM (based on GSM TS 07.10)
– emulates a serial-port to support a large base of legacy
(serial-port-based) applications
– allows multiple “ports” over a single physical channel
between two devices
• Telephony Control Protocol Spec (TCS)
– call control (setup & release)
– group management for gateway serving multiple devices
• Legacy protocol reuse
– Re-use existing protocols, e.g., IrDA’s OBEX, or WAP for
interacting with applications on phones
 Interoperability And Profiles
• Represents default solution Applications
for usage model
• Vertical slice through
the protocol stack

Protocols
• Basis for
interoperability and
logo requirements
• Each Bluetooth device
supports one or Profiles
more profiles
 Bluetooth Profile Specifications
• K:1 Generic Access • K:8 Fax
• K:2 Service Discovery • K:9 LAN Access
• K:3 Cordless • K:10 Generic Object
Telephony Exchange
• K:4 Intercom
• K:11 Object Push
• K:5 Serial Port
• K:12 File Transfer
• K:6 Headset
• K:7 Dial Up • K:13 Synchronization
Networking
 Bluetooth Program Update
• 1.0 specifications published in July of 1999
– Core technology specs and Profile requirements
– Currently at 1.1
• Bluetooth membership exceeds 2,000 companies!
– Full list of member companies on www.bluetooth.com Web site
• Bluetooth program on track for products available in 2000
– Products available this year and early 2001
– Next big step is qualification program, to ensure interoperability
• Bluetooth qualification program started
• Bluetooth wireless technology is the basis for the IEEE
802.15.1 standard work
• Bluetooth SIG has expanded
– New contracts and membership types
 The SIG Formally Known As
Bluetooth ; )
• New Contracts
– Adopter/Early Adopter = Early Adopter
• Early Adopter Contract
– Early Adopter in working group = Associate
• Early Adopter Contract, Associate Amendment
• Open IP license to Bluetooth wireless technology
– Original “Foundation Specifications”
– New technology in and around the 12 specification
working groups
• Only need to sign 1 contract to use any Bluetooth wireless
technology (the new one)
 Future Directions for Bluetooth
1. Bluetooth Second Generation Radio
2. Bluetooth Personal Area Networking
3. Bluetooth in and around the Car
4. Bluetooth “Wake-up”
5. Bluetooth Human Interface Devices (HID)
6. Bluetooth Audio/Visual
7. Bluetooth ISM interference/Interoperability
8. Bluetooth Printing
9. Bluetooth Still Image
10. Bluetooth Extended Service Discovery Protocols
11. Bluetooth Local Positioning
12. Bluetooth UDI
 Summary
• Bluetooth is a global, RF-based (ISM: 2.4GHz band),
short-range, connectivity technology and solution for
portable, personal devices
– It is not just a radio
– Create piconets on-the-fly (approximately 1Mbps)
• Piconets may overlap in time and space for high
aggregate bandwidth
• The Bluetooth spec comprises
– A hardware and software protocol specification
– Usage case scenario profiles and
interoperability requirements
• To learn more: http://www.bluetooth.com
Windows 2000 Bluetooth Stack
• Bluetooth Architecture in Windows
– Goals
– Components of the Stack
– Functionality
• Opportunities for IHVs and ISVs
– Applications
– Services
– Devices
 High Level Goals
• PC work with all devices
– Bluetooth Devices as PC peripherals
– Bluetooth Devices as PC companions
– Bluetooth Devices bridge to network
resources through a PC
• Easy to configure and operate
• Extensible architecture
– Platform for third parties to add value
 Scenarios
• Device configuration:
– Discovery
– Bonding
• Syncing and transfer through OBEX
– Files
– Pictures
– Vcards
• Dial up Networking
– Cell as modem
– Null Modem for Peer to peer
• Generic RFComm applications
– Non-OBEX synchronization
– Other serial-type applications
 Technical Requirements
• Bluetooth 1.0 Type II device classification supported
• Required profiles
• Bus Management Infrastructure
– Device and radio configuration
– Control panels
– System Trays
• Extensible framework for value adds
– Devices
– Profiles
– Bus mgmt software
– RFComm applications
– Object Exchange and special object handling
– RAS and TAPI over Unimodem
 Bluetooth Stack Diagram
OBEX.DLL TAPI

WinSock2 UNIMODEM.TSP
SDP/Advisor

MODEM.SYS

AFD.SYS BTHMODEM.SYS

HID AUDIO RFCOMM.SYS

BTHPORT.SYS
 Stack Components
• BthPort
– L2Cap / HCI
– Hardware abstraction: Serial, USB…
– Enumeration of Found Bound Services
• SDP/Management UI
– Bus management:
• User notification of newly discovered devices
• User assisted Configuration and Bonding
• Configuration of radio
– Local Service Exposure and Publication
 Stack Components
• RFCOMM
– RFComm Profile
– TDI interface for WinSock (AFD)
– Bus enumeration for Dial Up Networks
• BthModem (a WDM modem)
• OBEX.DLL
– Object Exchange 1.2
– Bus Agnostic
 BthPort
• Support Currently Defined buses:
– USB
– Serial (if hardware available)
– UART/16550
– Possible PCI HCI (investigating in committee)
• Plug and Play events
• Bluetooth Request Blocks
 Service Discovery Protocol
• Provide a “builder” interface to easily create a service
record
• Kernel mode
– Client drivers can submit a list of UUIDs to search for on all
newly discovered devices or initiate a SDP search outside of
device discovery
– BThPort will search for all the services in the browse group
hierarchy
• User mode
– Initiate searches
– Browse service records
 Management UI
• Present user with devices in range and bound devices
• Allows the user to easily change the relationship with remote
devices
• Provide unobtrusive PIN and authorization notifications
• UI is accessible from third-party applications for a standard
user experience
• Advanced features
– Filter devices based on COD or address
– Local radio settings
– Manage power policies
 OBEX
• Full OBEX 1.2 implementation:
– Put
– Get
– SetPath
– Definable transactions
• COM API
• Extensible to other media
and transports
 OBEX
OBEX.DLL

OBEXBT.DLL OBEXIrDA.DLL OBEXIP.DLL ?

SDP WINSOCK 2
 RFCOMM
Modem.SYS OBEX

BTHSER.SYS WINSOCK/AFD/TDI

FDO PDO RFCOMM.SYS Socket FDO

PDO BTHPORT.SYS PDO

DUN/Lan Access File Transfer/OBEX

 Opportunities To Add Value
in Windows 2000 environment
• RF comm applications
• OBEX applications/extensions
• Bluetooth management application
• New device types and/or class drivers
• Radios on new hardware buses
 RF Comm Applications
• Applications looking for virtual serial ports not
supported
• Legacy TAPI/Unimodem applications see peer
devices as NULL Modems
• Applications enumerate Modem/Serial Devices
through Unimodem

TAPI = Telephony API

Unimodem = Universal Modem Driver, a TAPI service
provider
 RF Comm Applications
• Winsock allows for dynamic discovery and
communication
– Talk to the device, not to the conduit (“My
Laserjet” versus “LPT2” or “COM23”)
– Once bonded device is in range the application
can find and use it
– Allows for multiple remote connection to same
service
– Not necessary to manage multiple virtual
COMx ports
 OBEX Applications
• Examples
– Photos
– Vcards (not “in the box”)
– Simple databases
• Server
– Registration
– New Obex Commands and types
– Application can register as handler for custom commands
• Client
– Discovery
– Navigate directory structure (enumerate objects)
– Push Pull objects
 Other OS support
• Microsoft is only planning to support Windows
2000 and its successors for general purpose PCs.
• Intel and many other third parties are producing
stacks for older Windows versions (e.g. Windows
98, which had USB support).
• Intel, IBM and some other parties are producing
stacks for use on Linux and other Unix versions
• Several embedded OS vendors will support
Bluetooth
• Microsoft is providing support for Windows CE
 Call To Action
• Join the SIG if you haven't already
– Help advance Bluetooth functionality by supporting the working groups
committees
– Got a new usage model? Submit a request
• Learn how Bluetooth wireless technology works NOW!
– See Microsoft's presentation on Bluetooth wireless technology
– Bluetooth Developers Conference, December 4th , San Jose CA
– Bluetooth Developers Seminar, December 8th, San Jose, CA
– More information: http://www.Bluetooth.com
• Implement Bluetooth software and hardware in your products
and systems
– Insure interoperability via Un-plugfests
• Help support native operating system development
– Provide test hardware to Microsoft
 Resources, 1of2
• http://www.bluetooth.com
Bluetooth home page, main resource
• http://developer.intel.com/technology/itj/q22000/a
rticles/art_1.htm
Intel white paper on Bluetooth
• http://www.microsoft.com/hwdev/bluetooth
Microsoft Bluetooth™ developer resources
• http://www.microsoft.com/hwdev/wireless
Microsoft wireless developer resources
 Resources, 2of2
• http://developer.axis.com/software/bluetooth
Bluetooth on Linux homepage
• http://mobilix.org/bluetooth_linux.html
Laptops, Bluetooth™ and Linux (draft)
• http://www.idgnet.com/crd_linux_223446.html
IBM Linking Linux to Wireless Devices
• http://www.alphaworks.ibm.com/tech/BlueDrekar
BlueDrekar – a Bluetooth protocol driver from IBM
• http://www.upside.com/Ebiz/397f47ae0.html
IBM toasts Linux, Bluetooth marriage