Bluetooth Driver
Bluetooth driver also known as profile driver is written by independent hardware vendors (in short, IHVs) to support various protocols defined in the Bluetooth specifications. Profile drivers should follow the Windows Driver Model (WDM) architectureÂ
To support the Bluetooth protocol, Microsoft supplies several Bluetooth drivers and support files, including:
BthPort.sys
BthEnum.sys
BthUsb.sys
BthProps.cpl
IHVs must use Windows Vista or later to develop their profile drivers because earlier versions of Windows, including Windows XP with SP2, do not support profile driver development.
The Bluetooth driver stack provides device driver interfaces (DDIs) that enable profile drivers to access Synchronous Connection-Oriented (SCO) links and Logical Link Controller and Adaptation Protocol (L2CAP) links between the local system and remote Bluetooth devices
SCO
Synchronous connection-oriented (SCO) links are point-to-point connections between two Bluetooth devices. They are defined primarily to support time-bounded information like voice.
L2CAP and SDP
The L2CAP is designed to support asynchronous connectionless link (ACL) Bluetooth links. The Bluetooth driver stack provides support for connection-oriented services. Profile drivers use the Bluetooth L2CAP DDIs to open, update, and close L2CAP connections, as well as to perform read and write operations over an open L2CAP connection. Â
There are two installation types for Bluetooth driver:
Client-side installation
Server-side installation
Categories: Bluetooth Driver Tags: Adaptation, Bluetooth Devices, Bluetooth Profile, Ddis, Device Driver Interfaces, Driver Stack, Earlier Versions Of Windows, Independent Hardware Vendors, Installation Server, Link Controller, Local System, Logical Link, Microsoft Support, Oriented Services, Profile Drivers, Protocol, Protocols, Server Side, Windows Driver Model, Windows Xp
