Qualification Program Reference
Document
Bluetooth Document▪

Version: r15▪

Version Date: 1/24/2024▪

Feedback Email: bqrb-feedback@bluetooth.org

Abstract:
This Qualification Program Reference Document (QPRD, as referred to in the Bylaws), contains theCompliance Requirements (as referred to in the Bluetooth Patent/Copyright License Agreement (PCLA)), theBluetooth Qualification Process (as referred to in the Bluetooth Patent/Copyright License and Bluetooth
Trademark License), and policies and procedures for Qualified Product database management. This
document supersedes the Compliance Requirements in Volume 0, Part B, Section 3 of the Bluetooth ® Core
Specification Version 5.4 and each earlier version of the Bluetooth Core Specification, the Qualification
Program Reference Document Version 2.3, and the Declaration Process Document Version 1.0.

Bluetooth SIG Proprietary and Confidential

Qualification Program Reference Document / Bluetooth Document
Version History
Version NumberDate(yyyy-mm-dd)

Comments

v1.0

2002-02-07

The initial Qualification Program Reference
Document

v2.1

2008-03-18

Approved by the Bluetooth SIG Board of Directors.

v2.3

2014-05-01

Approved by the Bluetooth SIG Board of Directors.

d3r15

2024-01-30

Authorized and Directed by the Bluetooth SIG
Board of Directors to initiate the steps to prepare
for approval and implementation of Draft QPRD
v3.

Acknowledgements
NameCompany

Alicia Courtney

Broadcom Corporation

Chris Church

Qualcomm Technologies, Inc

Clive Feather

Samsung Cambridge Solution Centre

Magnus Sommansson

Qualcomm Technologies, Inc

Miles Smith

Nordic Semiconductor ASA

Shirin Ebrahimi-Taghizadeh

Microsoft Corporation

Theodora Dimitropoulou

Dialog Semiconductor B.V.

Toby Nixon

Microsoft Corporation

Zhiwei Zhang

China Academy of Information and Communications
Technology

Mark Powell

Bluetooth SIG

Denise Montoya

Bluetooth SIG

Lewis Chan

Bluetooth SIG

Joshua Graham

Bluetooth SIG

Bluetooth SIG Proprietary and Confidential

Page 2 of 23

Qualification Program Reference Document / Bluetooth Document
This document, regardless of its title or content, is not a Bluetooth Specification as defined in the Bluetooth Patent/Copyright
License Agreement (“PCLA”) and Bluetooth Trademark License Agreement. Use of this document by members of Bluetooth
SIG is governed by the membership and other related agreements between Bluetooth SIG Inc. (“Bluetooth SIG”) and its
members, including the PCLA and other agreements posted on Bluetooth SIG’s website located at www.bluetooth.com.
THIS DOCUMENT IS PROVIDED “AS IS” AND BLUETOOTH SIG, ITS MEMBERS, AND THEIR AFFILIATES MAKE NO
REPRESENTATIONS OR WARRANTIES AND DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING ANYWARRANTY OF MERCHANTABILITY, TITLE, NON-INFRINGEMENT, FITNESS FOR ANY PARTICULAR PURPOSE, THAT THE
CONTENT OF THIS DOCUMENT IS FREE OF ERRORS.
TO THE EXTENT NOT PROHIBITED BY LAW, BLUETOOTH SIG, ITS MEMBERS, AND THEIR AFFILIATES DISCLAIM ALL
LIABILITY ARISING OUT OF OR RELATING TO USE OF THIS DOCUMENT AND ANY INFORMATION CONTAINED IN THISDOCUMENT, INCLUDING LOST REVENUE, PROFITS, DATA OR PROGRAMS, OR BUSINESS INTERRUPTION, OR FOR
SPECIAL, INDIRECT, CONSEQUENTIAL, INCIDENTAL OR PUNITIVE DAMAGES, HOWEVER CAUSED AND REGARDLESS OF
THE THEORY OF LIABILITY, AND EVEN IF BLUETOOTH SIG, ITS MEMBERS, OR THEIR AFFILIATES HAVE BEEN ADVISEDOF THE POSSIBILITY OF SUCH DAMAGES.
This document is proprietary to Bluetooth SIG. This document may contain or cover subject matter that is intellectual
property of Bluetooth SIG and its members. The furnishing of this document does not grant any license to any intellectual
property of Bluetooth SIG or its members.
This document is subject to change without notice.
Copyright © 2024 by Bluetooth SIG, Inc. The Bluetooth word mark and logos are owned by Bluetooth SIG, Inc. Other thirdparty brands and names are the property of their respective owners.

Bluetooth SIG Proprietary and Confidential

Page 3 of 23

Qualification Program Reference Document / Bluetooth Document

Contents
1

Introduction ........................................................................................................................................... 5
Definitions ..................................................................................................................................... 5

2

Compliance Requirements .................................................................................................................. 83

The Bluetooth Qualification Process.................................................................................................. 9
Provide Product details ................................................................................................................. 9Specify the Design ........................................................................................................................ 9
3.2.1
3.2.2
3.2.2.1

Option 1: Use a single existing Design ...................................................................................................9
Option 2: Create a new Design ............................................................................................................. 10
Option 2a: Create a New Design that combines multiple existing Designs ..................................... 10

3.2.2.2

Option 2b: Create any other new Design ......................................................................................... 11

3.2.2.3

Complete consistency check ........................................................................................................... 12

3.2.2.4

Generate test plan ........................................................................................................................... 12

3.2.2.5

Complete testing, test declaration, and test report(s) ...................................................................... 12

Pay an administrative fee ........................................................................................................... 13
Submission ................................................................................................................................. 13
3.4.1

Compliance Folder ................................................................................................................................ 14

Verification .................................................................................................................................. 14
4

Qualified Product database ............................................................................................................... 16

5

Acronyms and abbreviations ............................................................................................................ 18

6

References .......................................................................................................................................... 19

Appendix A
A.1
A.2

Test declaration .......................................................................................................................... 21
Test report ................................................................................................................................... 21

Appendix B
B.1
B.2

Test requirements ............................................................................................................. 20

Transition for Products qualified under PRD version 2.3 and earlier .......................... 22

Using DID and QDID going through Option 1 ............................................................................. 22
Using DID and QDID going through Options 2a and 2b ............................................................. 22

Appendix C

TCW policy ......................................................................................................................... 23

Bluetooth SIG Proprietary and Confidential

Page 4 of 23

Qualification Program Reference Document / Bluetooth Document

1 Introduction
This document contains the Compliance Requirements and specifies the Bluetooth Qualification Process,including the policies and procedures for Qualified Product database management.
Table 1.1 defines the terms used in this document. Unless another document expressly references thisdocument and incorporates a term defined in this section, these definitions do not apply and should not
be used to interpret any other document published by the Bluetooth SIG.

Definitions
Term

Definition

Bluetooth Qualification Test
Facility (BQTF)

An accredited test facility that can perform testing and produce test
results for any Member, and Bluetooth SIG will accept the results for the
purposes of the Bluetooth Qualification Process. For more information
about BQTFs, see the BQTF and BRTF Program Overview [4].

Bluetooth Recognized Test
Facility (BRTF)

An accredited test facility that can perform testing and produce test
results for itself, and Bluetooth SIG will accept the results for purposesof the Bluetooth Qualification Process. For more information about
BRTFs, see the BQTF and BRTF Program Overview [4].

Bluetooth SIG

As defined in the Bylaws of Bluetooth SIG Inc., Section 1.1 [3].

Bluetooth Specifications

All specifications and updates to specifications adopted in accordancewith the Bylaws of Bluetooth SIG [3].

Complete Layer

An implementation contains a complete layer if the implementation
includes, for that layer, all mandatory features, all the mandatory
elements of any optional feature that is included, and any features thatare conditionally required. See Volume 0, Part D, Section 1 of theBluetooth Core Specification for more information.

Compliance Folder

Documentation maintained by the Member to demonstrate that a
Product meets all requirements of the Bluetooth Qualification Process,as further described in Section 3.4.1.

Core Configuration

As defined in Volume 0, Part D, Section 3.3 of the Bluetooth Core
Specification, where also the following terms, used in this document, arespecified: Core-Complete Configuration, Core-Controller Configuration,
and Core-Host Configuration.

Core Layer

Any Layer as defined in Volume 0, Part D, Section 3 of the Bluetooth
Core Specification.

DesignAn implementation of one or more Bluetooth Specifications.

Design Number (DN)

A reference number issued for each unique Design that is issued thefirst time a Product using that Design completes the Bluetooth
Qualification Process.

Implementation
Conformance Statement(ICS)

The document produced by the Bluetooth SIG for each BluetoothSpecification that identifies the features of that Bluetooth Specification.

Bluetooth SIG Proprietary and Confidential

Page 5 of 23

Qualification Program Reference Document / Bluetooth Document

Term

Definition

ICS Form

The form completed by a Member for each Design to identify all featuresof the Bluetooth Specifications in that Design.

Implementation eXtra
Information for Testing(IXIT)

The form completed by a Member that provides additional configuration
details to facilitate testing beyond supported features defined in the ICS,
as defined in the Test Strategy and Terminology Overview (TSTO) [7].

LayerCore Layers and X2Core Layers are all layers.

MemberAn entity who has executed the Bluetooth SIG’s membershipagreements and has not withdrawn their membership or otherwise had
their membership terminated.

Product

Includes only one Design, is sold as a single item, and is marketed
under a name or trademark that uniquely identifies the Member who isthe source of the product.

Inter-Layer Dependency(ILD)

A Bluetooth Specification requirement in one Layer that is dependent on
one or more features or elements of a feature implemented in another
Layer. For more information, see the TSTO [7].

Interoperability Testing(IOPT)A collection of test cases, based on the ICS Form for the Design
intended to verify interoperability for X2Core Layers.

Product Publication Date

The date requested by the Member, when the Qualified Product details
are visible to the public and other Members in the Qualified Productdatabase, which may not be later than 90 days after submission.

Product Qualification Date

The date that the Bluetooth SIG notifies the Member that the Producthas successfully completed the Bluetooth Qualification Process.

Qualified Product

A Product that has successfully completed the Bluetooth Qualification
Process.

Receipt Number

A unique reference number issued as proof of payment of an
administrative fee paid by a Member to complete the Bluetooth
Qualification Process.

TCRL Package

The collection of files maintained by Bluetooth SIG that contains all the
TCRLs for all active Bluetooth Specifications.

Test Case Reference List
(TCRL)For each Bluetooth Specification, the sheet within the TCRL Packagethat identifies the applicable versions of the TS and ICS to be used in
the Bluetooth Qualification Process for Designs that implement that
Bluetooth Specification. For more information, see the TSTO [7].

Test Coverage Waiver(TCW)

A waiver of one or more Bluetooth Qualification Process requirements
granted by Bluetooth SIG. See Appendix C for more information.

Test Set Erratum (TSE)A report that tracks an error in the Bluetooth Qualification Process
requirements (including a published test document) and any relevant
fixes implemented to resolve the error. For more information on theerrata process, see the EPD [8].

Bluetooth SIG Proprietary and Confidential

Page 6 of 23

Qualification Program Reference Document / Bluetooth Document

Term

Definition

Test Suite (TS)For each Bluetooth Specification, the document that contains the test
cases for each Bluetooth Specification. For more information, see the
TSTO [7].

Test System

A system to be used by a Member to perform the specific tests asoutlined in the test plan.

X2Core Layer

A single Bluetooth Specification that is not a Bluetooth Core
Specification.

Table 1.1: Definitions

Bluetooth SIG Proprietary and Confidential

Page 7 of 23

Qualification Program Reference Document / Bluetooth Document

2 Compliance Requirements
This section defines the Compliance Requirements referred to in Section 1(i) of the Bluetooth
Patent/Copyright License Agreement (PCLA) [1].
To demonstrate that a Product complies with the Bluetooth® Specification(s), each Member must for eachof its Products:•

Identify the Product, the Design included in the Product, the Bluetooth Specifications that the Design
implements, and each of the features of each Bluetooth Specification that the Design implements.

•

Complete the Bluetooth Qualification Process (see Section 3).

For a Product to complete the Bluetooth Qualification Process, the Member must submit the required
documentation for the Product under a Bluetooth SIG user account belonging to the same Member
completing the Bluetooth Qualification Process.
Each Member is responsible for ensuring that the information they submit is complete and accurate andtheir Products comply with the Bluetooth Specifications.
A supplier or other Member cannot complete the Bluetooth Qualification Process for any other company’s
Product.

Bluetooth SIG Proprietary and Confidential

Page 8 of 23

Qualification Program Reference Document / Bluetooth Document

3 The Bluetooth Qualification Process
The Bluetooth Qualification Process promotes Product interoperability and reinforces the strength of theBluetooth® brand and ecosystem to the benefit of all Members.
To complete the Bluetooth Qualification Process, a Product must include a Design that implements atleast one Complete Layer.
The Bluetooth Qualification Process consists of the phases shown in Figure 3.1.

Figure 3.1: Bluetooth Qualification Process

Provide Product details
For each Product, a Member must provide the following information:•

Product name•Product description•

Model number•

Product Publication Date•

If the Product will be visible for other users with a user account issued under the same Member toview before the Product Publication Date

A Member may include additional details, such as the Product website.
The Product name and model number provided by the Member during the Bluetooth Qualification
Process must match the Product name and model number used by the Member when marketing,advertising, distributing, and selling the Product.

Specify the Design
A Member has several options for specifying the Design.

3.2.1

Option 1: Use a single existing Design

This option applies to a Member qualifying a Product that includes an existing Design that has a DN andthat Design has not been modified (e.g., rebranding a Qualified Product from another Member). The
Design identified by the DN may only implement Bluetooth Specifications that are active or deprecated at
the time of Submission. No modifications may be made to the Design, including changes to the ICS Form.
Changes to the Product outside the Design are allowed, including:•Enabling technologies•

Changes to the industrial design

Bluetooth SIG Proprietary and Confidential

Page 9 of 23

Qualification Program Reference Document / Bluetooth Document•

Changes to the communication technology other than Bluetooth•

Changes to the features that are unrelated to Bluetooth, branding, packaging, color, shape,
Product name, or Model number

Members are responsible for assessing that modifications to the Product outside of the Design do notaffect compliance with Bluetooth Specifications or result in a change to the ICS Form.

3.2.2 Option 2: Create a new Design
For each new Design, a Member must provide the following information:•

Design name (Optional, the Bluetooth SIG online tools will default to the Product name if the Member
does not specify a Design name)•If other Members are allowed to include the new Design in their Product (after it has been publishedin the Qualified Product database)•If other users with accounts issued under the same Member are allowed to include the new Design intheir Product (after it has been published in the Qualified Product database)

3.2.2.1 Option 2a: Create a New Design that combines multiple existing Designs
For a Product that includes a new Design created by combining two or more unmodified Designs thathave DNs into one of the permitted combinations in Table 3.1, a Member must also provide the following
information:•

The DN of each of the Designs used•

The desired Core Configuration of the new Design (if applicable, see Table 3.1 below)•

The active TCRL Package version used for checking the applicable Core Configuration (includingtransport compatibility) and evaluating test requirements

When creating a new Design, the ILDs between Layers included in the Design will be checked based on
the latest TCRL Package version used among the included Designs.
Permitted Combinations

Creating

Requirements
Core
IOPT
Config.
RequiredCheckfor Layers
added by

Design 1 has

Design 2 has

Designs 3+
have(optional,
additional
Designs)

New Design
has

ILD
Check

Core-Complete
Configuration

X2Core Layers
only

X2CoreLayers only

CoreComplete
Configuration

Required

Required

Design 2
andDesign 3+

Core-Controller
Configuration

Core-Host
Configuration-

CoreComplete
Configuration

Required

RequiredNoneCore-Controller
Configuration

Core-Host
Configuration

X2CoreLayers only

CoreComplete
Configuration

Required

Required

Design 3+

Bluetooth SIG Proprietary and Confidential

Page 10 of 23

Qualification Program Reference Document / Bluetooth Document
Permitted Combinations

Creating

Requirements
Core
IOPT
Config.
RequiredCheckfor Layers
added by

Design 1 has

Design 2 has

Designs 3+
have(optional,
additional
Designs)

New Design
has

ILD
Check

Core-Host
Configuration

X2Core Layers
only

X2CoreLayers only

Core-Host
Configuration

RequiredNot
required

Design 2
andDesign 3+

Core-Controller
Configuration

X2Core Layers
implementing LC3
specification only-

CoreController
Configuration

RequiredNot
required

None

X2Core Layers
only

X2Core Layers
only

X2CoreLayers only

X2CoreLayers only

RequiredNot
required

None

Table 3.1: Permitted Combinations

3.2.2.2 Option 2b: Create any other new Design
A Member must provide the following information:•

DN(s) for any Design(s) included in the new Design (if applicable)•

An active TCRL Package version•

An ICS Form

An ICS Form is filled out for each new Layer implemented in the new Design and for each modified Layer
based on an included Design using the active TCRL Package version.
A new Design must not implement any Layers using withdrawn specification(s). Implemented Layers
using withdrawn specification(s) must be either completely removed or modified to implement an active
specification and assessed against the active TCRL Package version.
For each unmodified Layer from an included Design, the Member may use the TCRL Package version
selected when the included Design completed the Bluetooth Qualification Process or use the active TCRL
Package version.
A Member may remove Layer(s) from included Design(s) that are not implemented in the new Design.
A Member must specify the new Design and complete the consistency check before submission.

3.2.2.2.1 Create a subset of a Member’s own Design
A Member can use Option 2b to identify that they want to create a subset of their existing Design that has
a DN, provided that the existing Design does not include a DN from other Members. The subset Design iscreated by removing one or more Layers or optional features. The subset Design must still meet therequirements of the same Core Configuration (if applicable). A subset Design cannot add Layers orfeatures, and the TCRL Package versions cannot be changed. All other requirements from Section
3.2.2.2 also apply.

Bluetooth SIG Proprietary and Confidential

Page 11 of 23

Qualification Program Reference Document / Bluetooth Document

3.2.2.2.2 Reassess Member’s own Design
A Member can use Option 2b to identify that they want to reassess their existing Design that has a DN
against an active TCRL Package version. The Member can modify the ICS Form only if any ICS selectionchanges are caused by the TCRL Package version update. Otherwise, the Member cannot modify the
ICS Form or any other Design details. The reassessed Design must still meet the requirements of thesame Core Configuration (if applicable). All other requirements from Section 3.2.2.2 also apply.

3.2.2.3 Complete consistency check
When a Member creates a new Design, the ICS Form for the new Design must pass the consistency
check performed by the tools provided by the Bluetooth SIG.
The consistency check determines whether the ICS Form is consistent with the requirements of thecorresponding Bluetooth Specification(s) and any applicable deprecation and withdrawal policies andwhether the ICS Form correctly shows support for:•One or more Complete Layers.

•

The ILDs between Layers included in the Design, based on the latest TCRL Package version usedamong the included Designs.

•

Applicable Core Configuration (including transport compatibility).

If the Bluetooth SIG tool identifies any inconsistencies, then the Member must address theinconsistencies by correcting the ICS Form so that it passes the consistency check or by providing a TCW
that indicates the requirement has been waived before submission (see Section 3.4). If the new Design
follows Option 2a, then correction of inconsistencies must be by removal of ICS selections. The Bluetooth
SIG tool may assist the Member in resolving the inconsistencies.

3.2.2.4 Generate test planIf, based on the ICS Form, testing is required, then the Bluetooth SIG tool will generate a test plan, which
includes all test cases for the new and modified Layers and any applicable IOPT test cases. The
generated test plan will be based on the ICS Form and test case mapping table of the TCRL Package
version specified by the Member for each Layer.
If no test plan is generated, then the Member will skip testing, test declaration, and test reports (seeSection 3.2.2.5).

3.2.2.5 Complete testing, test declaration, and test report(s)When a Test Plan is generated, the Member must:•

Follow the test requirements defined in Appendix A.

•

For a Design with one or more new Layers, execute each mandatory test case according to the test
case category requirements specified in the test plan.

•

Test ILDs between Layers not included in the Product by using the test setup specified in the test
plan that supports the Layers not included in the Product (to demonstrate application interoperability
as defined in Volume 1, Part A, Section 6 of the Bluetooth Core Specification).

•

For a Design that has a DN with one or more Layers that have been modified and the modification
requires a change to the ICS Form, execute each mandatory test case according to the test case
category requirements specified in the test plan.

Bluetooth SIG Proprietary and Confidential

Page 12 of 23

Qualification Program Reference Document / Bluetooth Document•

For a Design that has a DN with one or more Layers that have been modified, but the modification
does not require a change to the ICS Form, use good engineering practices to determine which
mandatory test cases are impacted by the modifications and execute those test cases. The Member
may use previous test evidence for non-impacted mandatory test cases. When a Member uses
previous test evidence, the Member is still responsible for ensuring that the Design complies with theBluetooth Specifications.

•

Receive a pass verdict for each test case executed, except for test cases where an inconclusive
verdict is permitted as defined in the TS.

The active date specified in the test plan is the date the test case takes effect.
In any case where a pass verdict cannot be obtained, then the Member must either:•

Update the Product and successfully complete retesting.

•

Provide a TCW for that test case.

If a Member finds an error with the Test Plan, the test case, or the Test System that is used, then theMember must submit a TSE via the Bluetooth SIG errata system. In this case, it may be possible to waive
test requirements by using an approved TCW.

Pay an administrative fee
Members are required to pay an administrative fee to complete the Bluetooth Qualification Process. For
administrative fee rules, see [5].
If an administrative fee is required, then the Bluetooth SIG issues a Receipt Number upon payment by theMember. The Member will provide the Receipt Number as proof of payment with their submission. Afterall necessary documentation is prepared and the administrative fee is paid, then the Member may
proceed to submission (see Section 3.4).
Members who require the Bluetooth SIG to issue an invoice for an administrative fee will need to take into
account the additional time it takes to issue an invoice.

Submission
Members use the Bluetooth SIG online tool to upload and submit the required documentation and to signrequired declarations and attestations. The declarations and attestations include those regarding
accuracy and completeness of information, authority to bind the Member, and agreement to andcompliance with policies of and agreements with the Bluetooth SIG.
Documentation Submission
Requirements

Use a single existing Design(Section 3.2.1)

Create a new Design (Section
3.2.2)

Product details

Required (provided in Section
3.1)

Required (provided in Section
3.1)

Design details

Required (the DN is provided in
Section 3.2.1)

Required (the DN(s) areprovided in Section 3.2.2.1 or
3.2.2.2)

ICS Form

N/A

Required (specified in Section
3.2.2.2)

Bluetooth SIG Proprietary and Confidential

Page 13 of 23

Qualification Program Reference Document / Bluetooth Document
Documentation Submission
Requirements

Use a single existing Design(Section 3.2.1)

Create a new Design (Section
3.2.2)

Test declaration

N/A

Required (specified in Section
3.2.2.5) if test plan is generated

Test report(s)N/ARequired (specified in Section
3.2.2.5) if test plan is generated

Receipt Number

See Fee Rules [5]See Fee Rules [5]

TCW

N/A

Required if TCW is used

Declarations and Attestations

Required

Required

Table 3.2: Documentation submission requirements

3.4.1 Compliance Folder
For all Qualified Products, Members must maintain documentation listed in Table 3.3 in a single location(commonly referred to as the "Compliance Folder"). Documentation must be stored at the time theMember submits the Product to the Bluetooth Qualification Process and be retained for no less than one
year after the Member stops offering the Product for sale or distribution. The Member must makedocumentation available to the Bluetooth SIG for inspection if requested.
Compliance Folder
Requirements

Use a single existing Design(Section 3.2.1)

Create a new Design (Section
3.2.2)

Product details

Required

Required

Design details

Required

Required

Test declaration

N/A

Required if test plan is generated

Test report(s)N/ARequired if test plan is generated

Test logs

N/A

Required if test plan is generated

TCW

N/A

As required

Table 3.3: Compliance Folder requirements

Verification
The Bluetooth SIG will review the submitted materials. Most reviews are approved within one businessday. The Bluetooth SIG will make a best effort to complete the review of more complex submissions
within five business days.
During the verification, the Bluetooth SIG will typically evaluate the following criteria:•

Check that a valid and approved TCW has been provided to address any inconsistencies identified
during the consistency check.

•

Check the authenticity of the test reports provided by the Member.

•

Verify that the Product matches the Core Configuration specified by the Member.

Bluetooth SIG Proprietary and Confidential

Page 14 of 23

Qualification Program Reference Document / Bluetooth Document
If the submission is approved by the Bluetooth SIG, then the Product has successfully completed theBluetooth Qualification Process and is a Qualified Product. The Qualified Product will be listed in the
Qualified Product database (see Section 3.4.1), and the Member will be notified at the user account thatmade the submission. The notice will include the Product name and model number from the Member’s
submission. If the Product includes a new Design (including subset Design and reassessed Design), thena unique DN will also be assigned to the new Design.
If the submission is rejected by the Bluetooth SIG, then the Product has not successfully completed theBluetooth Qualification Process, and the Member will be notified at the user account that made thesubmission and is provided an explanation for rejection. The Member must resolve the reason forrejection before submitting the materials again.
The following is a non-exhaustive list of examples of why submissions may be rejected by the Bluetooth
SIG:
•

•

A Product submission via the “creating a new Design” option may be rejected if:-

The consistency check indicates that there are inconsistencies and the TCW provided by theMember does not waive the requirement. The Member must correct the ICS Form either bychanging the specified Design so that it passes the consistency check or by providing a TCW thatwaives the corresponding requirement.

-

The test reports are incorrect. The Member must resubmit the Product with corrected test reports.

A Product submission via the “using a single existing Design” option may be rejected if:-

The Core Configuration is determined to be incorrect (e.g., a speaker that does not contain aCore-Complete Configuration). The Member may need to contact their supplier to inquire about
the correct DN for the Design or provide an explanation that establishes that their Product has thecorrect Core Configuration.

If the Member is not satisfied with the explanation for the rejection, then the Member may appeal therejection to the Bluetooth SIG. The Bluetooth SIG will review the disputed rejection with BQRB.

Bluetooth SIG Proprietary and Confidential

Page 15 of 23

Qualification Program Reference Document / Bluetooth Document

4 Qualified Product database
Each Qualified Product will be added to the Qualified Product database. The visibility of the Productdetails fields is shown in Table 4.. The database is accessible via the Bluetooth SIG website.
Product Detail Fields

Public(From ProductPublication Date)

Available Information View
All Users Accounts ofMember Qualifying the
Other Members
Product(From Product(From Product Qualification
Publication Date) Date or Product Publication
Date, depending on theselection)

DN of new Design created aspart of Product Submission

No

Yes

Yes

Member Name

Yes

Yes

Yes

Submitted By User Account

No

No

Yes

Product Contact

No

No

Yes

Product Name

Yes

Yes

Yes

Product Website

Yes

Yes

Yes

Product Qualification Date

No

Yes

Yes

Product Publication Date

No

No

Yes

Model Number

Yes

Yes

Yes

Product Description

Yes

Yes

Yes

Included DN(s) (if applicable)

No

Yes

Yes

Design Name

No

Yes

Yes

Design Contact

No

No

Yes

Design available for otherMembers to use

No

Yes

Yes

Design available for otherusers within the same Member
to use

No

No

Yes

ICS Form and the TCRL
Package Version

No

Yes

Yes

Table 4.1: Qualified Product database fields

Updates to Product details may be possible and the details are in Table 4.2.

Bluetooth SIG Proprietary and Confidential

Page 16 of 23

Qualification Program Reference Document / Bluetooth Document
Product Detail Fields

Correction Allowed

Update Method

Product Contact

Yes

Self-Serve

Included DN(s) (if applicable)

No*

N/A

Design NameYes

SIG-Assisted

Design Contact

Yes

SIG-Assisted

Design available for other Members to use

Yes

SIG-Assisted

Design available for other users within the same Member to
use

Yes

SIG-Assisted

ICS Form and the TCRL Package Version

Yes*

SIG-Assisted

Test Declaration

Yes*

SIG-Assisted

Test ReportYes*

SIG-Assisted

Table 4.2: Qualified Product correction*These fields are only allowed to be updated before the Product Publication Date. If a Member
wants to change these fields before the Product Publication Date, then the Member must request
to withdraw the original submission and restart the Bluetooth Qualification Process for this
Product. If the request to withdraw is received before the Product Publication Date, then theMember may reuse the administrative fee by providing the existing Receipt Number in theirresubmission.
A Member who identifies an error in the following database fields, Product name, model number, Productdescription, Product website, Product Qualification Date, or Product Publication Date, must first qualify a
new Product as described in Section 3.2.1 with the corrected information, and then the Member may
request that the Bluetooth SIG withdraw the original (incorrect) Product from the Qualified Productdatabase; provided that the original Product has never been sold or distributed.
A Member may request withdrawal of a Qualified Product from the database if the Product has neverbeen sold or distributed. If a Product is withdrawn and is the only Product that uses the Design that was
included in the submission, then the Bluetooth SIG will delete the DN for that Design.
If a Member transfers ownership of a Qualified Product to another Member as part of a merger or
acquisition, then the Member who submitted the Product to the Bluetooth Qualification Process mustcomplete and submit the assignment agreement form [6] to the Bluetooth SIG.

Bluetooth SIG Proprietary and Confidential

Page 17 of 23

Qualification Program Reference Document / Bluetooth Document

5 Acronyms and abbreviations
Acronym/Abbreviation

Meaning

BQTF

Bluetooth Qualified Test Facility

BRTF

Bluetooth Recognized Test Facility

BTLA

Bluetooth Trademark License Agreement

DID

Declaration ID

DN

Design Number

HCI

Host Controller Interface (Volume 4, Part E in the Bluetooth Core
Specification)

ICS

Implementation Conformance Statement

IOPT

Interoperability Testing

IXIT

Implementation eXtra Information for Testing

PCLA

Bluetooth Patent/Copyright License Agreement

QDID

Qualified Design ID

QPRD

Qualification Program Reference Document

TCRL

Test Case Reference List

TCW

Test Coverage WaiverTS

Test Suite

TSE

Test Set Erratum

TSTO

Test Strategy and Terminology Overview

Table 5.5.1: Acronyms and abbreviations

Bluetooth SIG Proprietary and Confidential

Page 18 of 23

Qualification Program Reference Document / Bluetooth Document

6 References[1] Bluetooth Patent/Copyright License Agreement
https://www.bluetooth.com/wp-content/uploads/2019/03/PCLA-ESign-Version-Version-11.pdf[2] Bluetooth Trademark License Agreement
https://www.bluetooth.com/wp-content/uploads/2023/08/BTLA_w_Brand_Guide.pdf[3] Bylaws of Bluetooth SIG, Inc.
https://www.bluetooth.org/DocMan/handlers/DownloadDoc.ashx?doc_id=556688[4] BQTF and BRTF Program Overview
https://www.bluetooth.com/develop-with-bluetooth/qualification-listing/qualification-testfacilities/qualification-test-facilities-program-overview/[5] Fee Rules
https://www.bluetooth.com/fee-schedule/[6] Assignment Agreement Form
https://support.bluetooth.com/hc/enus/article_attachments/6059031981453/Form3200_TransferAssignmentAgrmntEN.pdf[7] Test Strategy and Terminology Overview
https://www.bluetooth.org/docman/handlers/DownloadDoc.ashx?doc_id=40500[8] Errata Process Document
https://www.bluetooth.org/docman/handlers/DownloadDoc.ashx?doc_id=25352

Bluetooth SIG Proprietary and Confidential

Page 19 of 23

Qualification Program Reference Document / Bluetooth Document

Appendix A Test requirements
Test System Requirements
Test Case Category

Performed
by

Test
Declaration[Appendix
A.1]

Test
Report[Appendix
A.2]

Validated

Non-validated orMember-Defined

AllowedNot allowed

BQTF or
BRTF

Required

Required

AllowedNot allowed

Member or
BQTF/BRTF
or third party

Required

RequiredCategory B:
Mandatory

AllowedAllowedMember or
BQTF/BRTF
or third party

Required

RequiredCategory C: Optional(Recommended)

AllowedAllowedMember or
BQTF/BRTF
or third party

RequiredNot
RequiredCategory D: Optional(Informational)

AllowedAllowedMember or
BQTF/BRTF
or third party

If performed,
thenrequiredNot
RequiredCategory X: Optional(Recommended)

AllowedAllowedMember or
BQTF/BRTF
or third party

If performed,
thenrequiredNot
RequiredCategory A:
Mandatory(Test cases in theRF, RFPHY, BB, LL,
ISOAL, LMP, and theLower HCI role
Layers)Category A:
Mandatory(Test Cases in other
Layers)

These aresupplementaryinteroperability tests
aimed at scenariosthat do not have a
direct specificationreference. The tests
are recommended by
the Bluetooth SIG to
be run for improved
interoperability, butthey are not required
to be executed aspart of the Bluetooth
Qualification
Program.

Bluetooth SIG Proprietary and Confidential

Page 20 of 23

Qualification Program Reference Document / Bluetooth Document

A.1

Test declaration

A Member must provide a test declaration by filling out the test plan to include the following:•

Test Case Verdict (pass, inconclusive, waived, or not required)•

Test Execution Date•

Test System details•

Test Report Reference (file name)•

TCW (when applicable)

A.2

Test report

A Member must provide a test report for all Category A or B test cases in the test plan. A test report must
contain:•

Identification of the test facility that conducted the tests.

•

Identification of the Member providing the Product for testing.

•Identification of the Product including hardware and software version numbers.

•

A reference to the TS version.

•

A reference to the utilized Test System including the version.

•

IXIT values required by test cases executed.

•

For all test cases performed using a Member-defined test setup, information regarding test set up,
execution, and results.

•

A summary list of all performed test cases with the test case identifier, date of test, and the verdict(pass, fail, or inconclusive)

Bluetooth SIG Proprietary and Confidential

Page 21 of 23

Qualification Program Reference Document / Bluetooth Document

Appendix B Transition for Products qualified under
PRD version 2.3 and earlier
Bluetooth Product types defined in Volume 0, Part B of the Bluetooth Core Specification Version 5.4 orearlier are no longer supported. Instead, Volume 0, Part D of the Bluetooth Core Specification defines
Core Configurations. Bluetooth Product types will map to the definitions in the following table:
Controller Subsystem

A Core-Controller configuration
The Bluetooth SIG tools will automatically select the SEC and LESEC Layers,
Lower HCI role, and associated features based on the selected active TCRL
Package version and supported features in the used Designs.

Host Subsystem

A Core-Host configuration
The Bluetooth SIG tools will automatically select the Upper HCI role, based on
the selected active TCRL Package version and supported features in the used
Designs.

End Product

A Core-Complete configuration
The Bluetooth SIG tools will automatically select the Core-Complete
configuration, SEC and LESEC Layers, and associated features based on theselected active TCRL Package version and supported features in the used
Design.

Profile Subsystem

X2Core Layer(s)ComponentCore Layer(s) or X2Core Layer(s)Can be used to create a new Design according to Section 3.2.2, even if the
QDID was last assessed three or more years ago.
Table B.1: Bluetooth Product type mapping

Other Bluetooth Product types such as Development Tool, Test Equipment, and Component (non-tested)
are not supported.

B.2

Using DID and QDID going through Option 1

When submitting a Product using Option 1, a Member can use that DID or QDID as the DN.

B.3

Using DID and QDID going through Options 2a and 2b

When submitting a Product using Options 2a and 2b, a Member must use QDID(s) as DN(s).

Bluetooth SIG Proprietary and Confidential

Page 22 of 23

Qualification Program Reference Document / Bluetooth Document

Appendix C TCW policy
A Member may request a TCW using the process in the EPD [8].
When a TCW is granted, the TCW applies to all Members where the error is applicable.
A TCW remains valid until it is terminated. A TCW is terminated when the associated TSE indicates thatthe errors in the test documents or Test Systems have been fixed and the TSE has been incorporated ina new TCRL Package, if required.
The reasons a TCW may be granted include:•

An error in the test case mapping table.

•

An error in ICS conditionals.

•

An error in a test case initial condition, procedure, or pass verdict.

•An error in test case category in the TCRL Package.

•An error in a Test System.

•

An error in the Bluetooth SIG online tool’s interface or generated test plan.

•

No commercially available Test System can perform the test case, and it is not feasible to implement
the test case in-house.

•

A request to use a newly validated Test System (i.e., when the validation is not yet referenced in a
TCRL).

•A request to apply the corrections from a TSE (e.g., modify a part of the test case) before the TSE is
published in the applicable test document and referenced in a TCRL Package.

Bluetooth SIG Proprietary and Confidential

Page 23 of 23