Part B. Bluetooth Compliance Requirements
vAtlanta r00
This Part specifies the requirements for Bluetooth compliance.
1. Introduction
The Bluetooth Qualification Program Reference Document (PRD) is the primary reference document for the Bluetooth Qualification Program and defines its requirements, functions, and policies. The PRD is available on the Bluetooth Web site.
Passing the Bluetooth Qualification Process demonstrates a certain measure of compliance and interoperability, but because products are not tested for every aspect of this Bluetooth Specification, qualification does not guarantee compliance. Passing the Bluetooth Qualification Process only satisfies one condition of the license grant. The Member has the ultimate responsibility to ensure that the qualified product complies with this Bluetooth Specification and interoperates with other products.
2. Scope
This Part of the specification defines some fundamental concepts used in the Bluetooth Qualification Program.
3. Definitions
Bluetooth Qualification Process – The process defined in the Bluetooth Qualification Program Reference Document (PRD) to qualify a design used in implementations of Bluetooth wireless technology.
Bluetooth Qualification Program – The Bluetooth Qualification Process together with other related requirements and processes.
3.1. Types of Bluetooth Products
Bluetooth Product — Any product containing an implementation of Bluetooth wireless technology. Bluetooth Products as defined herein may require enabling technology external to Bluetooth Scope, as defined by the Patent and Copyright License Agreement, to become functional (e.g. power supply, technology capable of running executable code, etc.). Enabling technology is not part of any of the Bluetooth Product type definitions and is not included in the Bluetooth License grant.
All Bluetooth Products shall be one of the following:
Bluetooth End Product
Bluetooth Host Subsystem Product
Bluetooth Controller Subsystem Product
Bluetooth Profile Subsystem Product
Bluetooth Component Product
Bluetooth Development Tool
Bluetooth Test Equipment.
Table 3.1 defines abbreviations for the different Core Configurations defined in Section 4.
Abbreviation | Explanation | Section Reference |
|---|---|---|
BR CC | Bluetooth Basic Rate Core Configuration | |
EDR CC | Bluetooth Enhanced Data Rate Core Configuration | |
LE CC | Bluetooth Low Energy Core Configuration | |
BR and LE Combined CC | Bluetooth Basic Rate and Low Energy Combined Core Configuration | |
HCI CC | Host Controller Interface Core Configuration |
Table 3.2, Table 3.3, and Table 3.4 define Bluetooth product types in terms of Core Configurations, using the abbreviations in Table 3.1. For the respective Core Configuration, the letter “M” indicates that it is mandatory to claim support, “O” indicates that it is optional to claim support, “P” indicates that it is optionally permitted to claim only partial support of the Core Configuration, “I” indicates that the Core Configuration is inherently included in the combined Core Configuration, “E” indicates that support for the Core Configuration shall not be claimed.
3.1.1. Bluetooth End Product
A Bluetooth End Product is a Bluetooth product that claims to implement one or more Core Configurations, in compliance with the required parts of the specification, and in accordance with the mandatory requirements as defined herein. Complementary products for Bluetooth End Products are limited to only Bluetooth Profile Subsystem Products.
The Bluetooth End Product types are defined in Table 3.2.
BR CC | EDR CC | BR and LE Combined CC | LE CC | HCI CC | |
|---|---|---|---|---|---|
BR End Product | M | P | E | E | O |
EDR End Product | M | M | E | E | O |
LE End Product | E | E | E | M | O |
BR and LE End Product | I | P | M | I | O |
EDR and LE End Product | I | M | M | I | O |
3.1.2. Bluetooth Subsystem Product
A Bluetooth Subsystem Product is a Bluetooth product that claims to implement only a portion of the specification, in compliance with such portion of the specification, and in accordance with the mandatory requirements as defined herein. Bluetooth Subsystem Products can be qualified solely for distribution; the use of Bluetooth wireless technology in Bluetooth Subsystem Products requires such Bluetooth Subsystem Products to be combined with one or more complementary products such that the resulting combination satisfies the requirements of a Bluetooth End Product. Complementary products used in combinations are limited to those complementary products specified in each of the product definitions.
There are three types of Bluetooth Subsystem Products defined:
Bluetooth Host Subsystem Product
Bluetooth Controller Subsystem Product
Bluetooth Profile Subsystem Product.
A Bluetooth Subsystem Product shall be one of these types.
3.1.2.1. Bluetooth Host Subsystem Product
The required configuration for each Bluetooth Host Subsystem Product type is listed in Table 3.3.
BR CC Host Parts | BR and LE Combined CC Host Parts | LE CC Host Parts | HCI CC | |
|---|---|---|---|---|
BR/EDR Host Subsystem Product | M | E | E | M |
LE Host Subsystem Product | E | E | M | M |
BR/EDR and LE Host Subsystem Product | I | M | I | M |
A Bluetooth Host Subsystem Product may contain, in addition to the required Core Configuration Host parts (as defined in Table 3.3), at a minimum, all the mandatory requirements defined in one or more of the protocols above HCI, profiles, services, models, and codecs. Protocols below HCI required by the Core Configuration Controller parts (as defined in Table 3.4) shall be excluded from the Host Subsystem Product. Complementary products for Bluetooth Host Subsystem Products are limited to:
Bluetooth Controller Subsystem Products that implement and use the HCI ([Vol 4] Part E) for communication between the subsystems; and
Bluetooth Profile Subsystem Products when the Bluetooth Host Subsystem is combined with a Bluetooth Controller Subsystem Product.
3.1.2.2. Bluetooth Controller Subsystem Product
The required configuration for each Bluetooth Controller Subsystem Product type is listed in Table 3.4.
BR CC Controller Parts | EDR CC Controller Parts | BR and LE Combined CC Controller Parts | LE CC Controller Parts | HCI CC | |
|---|---|---|---|---|---|
BR Controller Subsystem Product | M | P | E | E | M |
EDR Controller Subsystem Product | M | M | E | E | M |
LE Controller Subsystem Product | E | E | E | M | M |
BR and LE Controller Subsystem Product | I | P | M | I | M |
EDR and LE Controller Subsystem Product | I | M | M | I | M |
A Bluetooth Controller Subsystem Product shall be limited to the Controller parts of the Core Configurations and may also contain, at a minimum, all the mandatory requirements defined in one or more codec specifications. Protocols, profiles, services, and models above HCI (whether or not required by the Core Configuration Host parts as defined in Table 3.3) shall be excluded from the Controller Subsystem Product. Complementary products for Bluetooth Controller Subsystem Products are limited to Bluetooth Host Subsystem Products that implement and use the HCI ([Vol 4] Part E) for communication between the subsystems.
3.1.2.3. Bluetooth Profile Subsystem Product
A Bluetooth Profile Subsystem Product is a Bluetooth product that claims to implement, at a minimum, all the mandatory requirements defined in one or more of the profile, service, or model specifications. Complementary products for Bluetooth Profile Subsystem Products are limited to:
Bluetooth Host Subsystem Products when combined with a Bluetooth Controller Subsystem Product; and
Bluetooth End Products.
3.1.3. Bluetooth Component Product
A Bluetooth Component Product is a Bluetooth product that claims to implement, at a minimum, all the mandatory requirements, if any, of one or more of any of the protocol, profile, service, model, or codec parts of the specification in compliance with such portion of the specification. Bluetooth Component Products can be qualified solely for distribution and the use of the Bluetooth wireless technology in Bluetooth Component Products require such Bluetooth Component Products to be incorporated in Bluetooth End Products or Bluetooth Subsystem Products. A product that meets the requirements of a Bluetooth End Product or Bluetooth Subsystem product may be qualified as a Bluetooth Component Product if a manufacturer determines that further integration is necessary prior to qualifying the product as a Bluetooth End Product or Bluetooth Subsystem Product.
3.1.4. Bluetooth Development Tool
A Bluetooth Development Tool is a Bluetooth product intended to facilitate the development of new Bluetooth designs. Bluetooth Development Tools can be qualified solely for distribution and the use of the Bluetooth wireless technology in development of new Bluetooth Products.
3.1.5. Bluetooth Test Equipment
A Bluetooth Test Equipment is a Bluetooth product intended to facilitate the testing of new Bluetooth Products. Bluetooth Test Equipment can be qualified solely for distribution and the use of the Bluetooth wireless technology in testing of new Bluetooth Products. Where necessary, Bluetooth Test Equipment may deviate from the specification in order to fulfill the test purposes in the Bluetooth Test specifications.
4. Core Configurations
This section defines the set of features that are required for a product to be qualified to a specification name. The Core Specification version number is simply the version number of the specification itself.
Specification names differ from Core Specification version numbers in that products are marked based on meeting requirements for a Core Configuration together with the mixing requirements (see [Vol 1] Part D, Section 1).
Each Core Configuration is defined by a set of parts and individual features of the Core Specification that shall be supported to allow the configuration name to be used. The configuration requirements imposed on a device may depend on the profiles that it supports.
4.1. Basic Rate Core Configuration
This section specifies compliance requirements for the “Basic Rate” Core Configuration.
To claim support to the “Basic Rate” Core Configuration, an implementation shall support a set of Required Features as specified in Table 4.1 and Table 4.2.
Host Part:
Layer | Required Features |
|---|---|
L2CAP ([Vol 3] Part A) | L2CAP Signaling channel (CID 0x0001) and all mandatory features associated with it |
SDP ([Vol 3] Part B) | All mandatory features |
ATT ([Vol 3] Part F) | ATT may be supported. If ATT is supported, all mandatory features |
GATT ([Vol 3] Part G) | GATT is mandatory when ATT is supported, otherwise GATT is excluded. When supported, all mandatory features |
GAP ([Vol 3] Part C) | All mandatory features in sections 2 to 8, section 12, section 15, and appendix A |
Controller Part:
Layer | Required Features |
|---|---|
RF ([Vol 2] Part A) | All mandatory features |
BB ([Vol 2] Part B) | All mandatory features |
LMP ([Vol 2] Part C) | All mandatory features |
4.2. Enhanced Data Rate Core Configurations
This section specifies compliance requirements for the “Enhanced Data Rate” Core Configuration.
Table 4.3 defines three categories of Transport Requirements that shall be satisfied subject to the following rules:
A Bluetooth product shall support category 1 whenever it supports asynchronous transports for the profiles it incorporates.
A Bluetooth product shall support category 2 whenever it supports asynchronous transports with multislot ACL packets for the profiles it incorporates.
A Bluetooth product shall support category 3 whenever it supports eSCO synchronous transports for the profiles it incorporates.
A multi-profile product shall support all applicable categories in order to claim support for the Enhanced Data Rate Core Configuration.
Category No. | Transport Requirements | Controller Part | Host Part |
|---|---|---|---|
LMP Features Supported | L2CAP Feature Bits Required | ||
1 | EDR for asynchronous transports (single slot) | Enhanced Data Rate ACL 2 Mb/s mode (25) AND Enhanced Data Rate ACL 3 Mb/s mode (26) | None |
2 | EDR for asynchronous transports (multi-slot) | 3-slot Enhanced Data Rate ACL packets (39) AND 5-slot Enhanced Data Rate ACL packets (40) | None |
3 | EDR for synchronous transports | Enhanced Data Rate eSCO 2 Mb/s mode (45) | None |
Note
Note: No additional requirements are stated on the support of 3-EV3, 2-EV5 and 3-EV5 packets.
4.3. [This section is no longer used]
4.4. Low Energy Core Configuration
This section specifies compliance requirements for the “Low Energy” Core Configuration.
To claim support to the “Low Energy” Core Configuration, an implementation shall support a set of Required Features as specified in Table 4.4 and Table 4.5.
Host Part:
Layer | Required Features |
|---|---|
L2CAP ([Vol 3] Part A) | If the GAP Peripheral or Central role is supported, L2CAP LE Signaling channel (CID 0x0005) and all mandatory features associated with it. Otherwise L2CAP is excluded |
GAP ([Vol 3] Part C) | All mandatory features for at least one of the LE GAP roles (Broadcaster, Observer, Peripheral or Central) in sections 2 to 3, sections 9 to 12, section 15, and appendix A |
ATT ([Vol 3] Part F) | If the GAP Peripheral or Central role is supported, all mandatory features. Otherwise ATT is excluded |
GATT ([Vol 3] Part G) | GATT is mandatory when ATT is supported, otherwise GATT is excluded. When supported, all mandatory features |
SM ([Vol 3] Part H) | If the GAP Peripheral or Central role is supported, all mandatory features. Otherwise SM is excluded |
Controller Part:
Layer | Required Features |
|---|---|
RFPHY ([Vol 6] Part A) | All mandatory features |
LL ([Vol 6] Part B) | All mandatory features |
ISOAL ([Vol 6] Part G) | ISOAL is mandatory when the LL supports Isochronous Channels, otherwise ISOAL is excluded. When supported, all mandatory features. |
4.5. Basic Rate and Low Energy Combined Core Configuration
This section specifies compliance requirements for the “Basic Rate and Low Energy Combined” Core Configuration.
To claim support for the “Basic Rate and Low Energy Combined” Core Configuration, an implementation shall support the following set of Required Features.
Host Part:
All mandatory requirements in the Host part of the BR/EDR CC
All mandatory requirements in the Host part of the LE CC
All requirements in [Vol 3] Part C, Section 13 and [Vol 3] Part C, Section 14.
Controller Part:
All mandatory requirements in the Controller part of the BR/EDR CC
All mandatory requirements in the Controller part of the LE CC
LMP feature bits 38 and 65 shall be set.
Requirements in the BR/EDR CC are only mandatory on the BR/EDR transport. Requirements in the LE CC are only mandatory on the LE transport.
4.6. Host Controller Interface Core Configuration
This section specifies compliance requirements for the “Host Controller Interface” Core Configuration.
To claim support for the “Host Controller Interface” Core Configuration, an implementation shall support a set of Required Features as specified in Table 4.6.
Layer | Required Features |
|---|---|
HCI ([Vol 4] Part E) | All the supported features in the implementation shall be compliant to the Host Controller Interface. |