蓝牙HID 1.1开发文档：无线通信与HID设备交互指南

5星 · 超过95%的资源需积分: 50 64 浏览量更新于2024-07-23 收藏 1.35MB PDF 举报

蓝牙HID Profile 1.1 是一个与蓝牙开发技术紧密相关的文档，它定义了如何利用蓝牙无线通信技术使设备能够发现并交互蓝牙HID（Human Interface Device，人机接口设备）的功能集。蓝牙HID Profile 主要关注的是在蓝牙协议栈（由 Logical Link Control and Adaptation Protocol, L2CAP 层支持）上实现HID服务的传输。该文档详细阐述了以下几个关键知识点： 1. **目标与目的**：这份文档的目标是规范蓝牙设备如何通过蓝牙连接来识别并建立通信，以便用户可以无缝地控制具有蓝牙功能的外设，如键盘、鼠标、游戏手柄等。 2. **发现过程**：文档强调了蓝牙HID设备的发现机制，这涉及到设备间的配对和交互，确保设备能正确识别对方的身份，并了解彼此支持的功能特性。 3. **L2CAP的应用**：L2CAP层在此场景中起着至关重要的作用，它作为蓝牙协议中的数据链路层，负责在设备间传输HID数据包，提供可靠的数据传输通道。 4. **协议栈结构**：蓝牙HID Profile 1.1定义了如何通过蓝牙协议的逻辑链接控制和适配协议来构建完整的交互流程，包括建立连接、数据交换和断开连接等步骤。 5. **版权与使用许可**：文档明确指出，蓝牙 SIG (Special Interest Group) 的成员拥有此规格的版权，所有使用都必须受《推动者成员协议》（Promoters Membership Agreement）和相关知识产权政策的约束。 6. **准备与修订**：文档最后列出了版本信息，包括批准日期、修订版本号和文档编号，以及由哪个工作组（HIDWG）准备和维护，以及联系邮箱，便于开发者查询和获取更新。蓝牙HID Profile 1.1 是蓝牙技术生态系统中的一个重要组成部分，它为蓝牙设备之间的HID交互提供了标准化的指导，有助于开发者创建兼容性强、用户体验良好的蓝牙外设产品。

BLUETOOTH SPECIFICATION Page 16 of 123

Human Interface Device (HID) Profile

Boot Protocol Mode Only Bluetooth HID Host – A Bluetooth HID Host that

implements only the Boot Protocol Mode capability outlined in this specification.

HID – Human Interface Device. This term is commonly used to refer both to the USB

data reporting protocol for Human Interface Devices, and to the devices themselves.

This document, when referring to the devices themselves, uses "Bluetooth HID device"

or "Bluetooth HID Host.” When referring to the protocol, this document uses "Bluetooth

HID Specification."

Bluetooth HID Connection – A Bluetooth HID connection is considered to exist when

HID L2CAP interrupt and Control channels are open between a Bluetooth HID device

and a Bluetooth HID Host.

Bluetooth HID Keyboard – A Bluetooth HID device with a HIDDeviceSubclass SDP

attribute indicating Keyboard or Combo Keyboard/Pointing. See section 5.3.4.3.

Bluetooth HID Pointing Device – A Bluetooth HID device with a HIDDeviceSubclass

SDP attribute indicating Pointing Device or Combo Keyboard/Pointing. See section

5.3.4.3.

Connectable – A device is said to be connectable if page-scan is enabled and the

device allows the creation of an ACL link.

Discoverable – A device is said to be discoverable if inquiry scan is enabled allowing

the device to be discovered by another device performing the inquiry procedure.

eSCO – Extended Synchronous Connection Oriented. A type of data link supported by

the Bluetooth baseband. eSCO links are not utilized by this profile, but may operate

concurrently with this profile on either a Bluetooth HID Host or Bluetooth HID device.

General Bluetooth HID Host - A host which is designed to support a wide variety of

Bluetooth HID devices and which supports the addition of applications to support new

devices.

L2CAP – Logical Link Control and Adaptation Protocol. The Bluetooth communications

layer in the host which multiplexes logical channels onto a single baseband connection

between two Bluetooth devices.

Legacy Bluetooth HID devices – Bluetooth HID devices qualified to the Bluetooth HID

Profile Specification 1.0 or prior.

Legacy Bluetooth HID Hosts – Bluetooth HID Hosts qualified to the Bluetooth HID

Profile Specification 1.0 or prior.

Limited Bluetooth HID Host – A host which is designed to support a limited set of

specific Bluetooth HID devices. Boot Mode Only Hosts are also a type of Limited

Bluetooth HID Host.

Limited Connectable Mode – Mode in which a Bluetooth device is performing page-

scan and is hence connectable but is not discoverable, not pairable and not bondable.

Pairable – A device is said to be pairable if it is in a state in which it will allow a remote

device to initiate and complete pairing with it.

BLUETOOTH SPECIFICATION Page 17 of 123

Human Interface Device (HID) Profile

Pairing - The process of establishing a link key between two Bluetooth devices. In most

HID usage models the Bluetooth HID Host normally initiates pairing.

Passkey – A 6-digit number either typed or compared by the user and used during the

Secure Simple Pairing process as defined in the Bluetooth Core Specification v2.1 +

EDR or later [6].

PIN – Personal Identification Number. Also referred to as the Bluetooth passcode at the

user interface.

PSM – Protocol/Service Multiplexer. A protocol identifier used by the L2CAP layer to

support multiple protocols.

QoS – Quality of Service. A general term that refers to the ability of a data channel to

provide guaranteed data bandwidth and/or latency to a device or service.

SCO – Synchronous Connection Oriented. A type of data link supported by the

Bluetooth baseband. SCO links are not utilized by this profile, but may operate

concurrently with this profile on either a Bluetooth HID Host or Bluetooth HID device.

SDP – Service Discovery Protocol.

USB – Universal Serial Bus.

Virtual Cable – The Virtual Cable defines the relationship between a Bluetooth HID

device and a particular Bluetooth HID Host. A Bluetooth HID device may support

multiple Virtual Cables, though only one Virtual Cable may be connected at any given

time. When a Bluetooth HID device is Virtually Cabled and connected to a given

Bluetooth HID Host, data flows exclusively between the Bluetooth HID device and the

currently connected Bluetooth HID Host.

1.5 Bluetooth HID Profile Change History

1.5.1 Changes from 1.0 to 1.1

 General Changes

 Extensive re-organization to reduce repeated requirements and improve

readability

 Improved consistency with IEEE Standards Style Manual guidelines for

requirement

 Requirement to support Core Specification 2.1 + EDR or later

 New Features

 Explicit guidance on use of Secure Simple Pairing introduced in the Bluetooth

Core Specification 2.1 + EDR

 Formal support for Sniff Subrating introduced in the Bluetooth Core Specification

2.1 + EDR including new HID SDP attributes:

o HIDSSRHostMaxLatency

o HIDSSRHostMinTimeout

BLUETOOTH SPECIFICATION Page 19 of 123

Human Interface Device (HID) Profile

2 Bluetooth HID Profile Architecture

This section provides an architectural overview of the Bluetooth HID Profile. It provides

background information on USB HID as well as explanations for important high level

concepts in the Bluetooth HID Profile.

2.1 Introduction to the USB and Bluetooth HID Specifications

This document defines an adaptation of the USB Device Class Definition for Human

Interface Devices (HID) [5] for use over a Bluetooth wireless link. Concepts from the

USB Specification [2] are used but may not be explained in this document. The USB

Specification [2] and USB HID Specifications [4], [5] are recommended pre-reading for

understanding the content of this document. See the Referenced Documents section at

the beginning of this document.

Though the HID class was originally targeted at human interface devices, the HID

Specification is very useful for any application that requires low-latency input-output

operations to an external interface.

The Universal Serial Bus Specification [2] defines the powerful concept of a “device

class”. Devices that have similar reporting characteristics are grouped together into a

“device class”. Instead of requiring a separate software driver for each new type of

computer peripheral device, a single class driver is provided for each device class. The

“HID class” is one such group, and these devices further have the capability to describe

themselves to the class driver, e.g., what types of data they can send and exactly how

they report data. This enables future devices to be developed without the need to

modify the host software.

Though defined by specifications released by the USB Implementers Forum, Inc., the

USB HID protocols are not specific to USB or any other type of physical data transport.

It is the intention of this document to describe how to use the USB HID protocols over

the Bluetooth wireless communications system, allowing manufacturers of input devices

to produce high performance, interoperable, and secure wireless input devices.

Information about a HID device is stored in segments of its non-volatile memory called

descriptors. For USB devices, device and interface descriptors identify a device as

belonging to one of a finite number of classes. The HID class is the primary focus of this

document. Other types of device classes described by USB specifications include

display, audio, communication, and data storage.

Report descriptors describe a set of reports and items within reports. The descriptors

also describe the range of permissible values for and the meaning of each data item

within the reports. By examining the report descriptor of a HID Device, the HID Class

software is able to determine the size and composition of data reports from the HID

Class device.

Physical descriptor sets are optional descriptors that provide information about the part

or parts of the human body used to activate the controls on a device.

BLUETOOTH SPECIFICATION Page 20 of 123

Human Interface Device (HID) Profile

“Application collections” are collections of reports that may be defined and associated

with general application types, for example a mouse pointer, a keyboard, a game

controller, etc. Collections enable report data to be routed to appropriate applications.

For example, a game application may request to have report data which are part of a

joystick or game controller collection routed to it to control the position of an on-screen

virtual tank. Likewise, an operating system with a graphical user interface may request

to have reports which are part of pointer collections and keyboard collections routed to

it.

For Bluetooth HIDs, the Service Discovery Protocol (SDP) records serve a similar

purpose to the device and interface descriptors used by USB. Service records identify

the services which Bluetooth devices provide. HID service records identify whether a

device supports the Bluetooth HID device service role, the Bluetooth HID Host service

role, or both. The HID service record of a Bluetooth HID device contains the report

descriptor for the device and optionally may contain a physical descriptor. The formats

for the report and physical descriptors are identical to that used for USB. Figure 2.1

illustrates the flow of descriptor and report information in the Bluetooth HID system.

Figure 2.1: How Descriptors and Data are transferred from the HID Class Device

2.1.1 HID Reports

Bluetooth HID devices support three report types: Input, Output, and Feature. Input and

Output reports typically contain low latency information. Input reports are generated by

the Bluetooth HID device and sent to the Bluetooth HID Host. Output reports are

generated by the Bluetooth HID Host and sent to the Bluetooth HID device. Feature

reports are bi-directional, and typically contain information that is not intended to be

seen or generated by the user, and hence is not time-critical. A Bluetooth HID device

shall contain at least one report type in its report descriptor.

Two logical channels are created between the Bluetooth HID device and Bluetooth HID

Host: the Control channel and the Interrupt Channel. Reports may be carried on either

the Interrupt channel or the Control channel. Report data carried on the Interrupt

channel is sent without a request and is not acknowledged and these transfers are

referred to as “asynchronous reports”. Report data transferred on the Control channel is

always initiated by a SET_REPORT or GET_REPORT request (see sections 3.1.2.3

and 3.1.2.4) and these transfers are referred to as “synchronous reports”.

SDP Transactions

Bluetooth

HID

Device

Bluetooth

HID

Host

(HID Class Software)

HID Interrupt and Control Channels

HID Descriptor

Information

HID Input,

Output, and

Feature Data

剩余122页未读，继续阅读

u014155519

粉丝: 0
资源: 2

蓝牙HID 1.1开发文档：无线通信与HID设备交互指南

bluetooth core 5.0 spec

bluetooth_test.zip，目前功能强大的蓝牙调试工具！！！APP包直接安装即可！

蓝牙核心规范5.1版本

bluetooth协议（2.1~5.1）及常用profile协议

蓝牙 core1.1核心协议

蓝牙HID人机接口规范

蓝牙HID协议

Bluetooth PROFILE SPECIFICATIONS

bluetooth外围设备驱动程序中文安装免费版

蓝牙5.0核心规范 bluetooth spec V5.0

最新资源