Applying for qualification of a Bluetooth® wireless product
1 Introduction
An application for qualification of a Bluetooth wireless product or
component must be made by submitting a Compliance Folder (CF) to a Bluetooth
Qualification
Body (BQB). The folder contains many documents that must be prepared
by the manufacturer in a consistent manner, particularly with regard
to terminology
used in documents and test reports. The items required in the folder
are basically the same whether applying for a product or component listing,
and the main difference relates to the use of pre-qualified components.
The qualification program is still at an early stage and many BQBs have
little experience of the process. It is therefore essential to discuss
at an early stage with the BQB exactly what documents are required and
particularly what evidence is required for pre-qualified components.
Many of the documents can be prepared and approved in advance by the
BQB so
that the only evidence awaiting review is the test reports for tested
functionality.
One of the areas most prone to cause confusion is the fact that various
qualification documents produced by SIG and test houses do not use terminology
consistently. A cross-reference chart is provided to help customers apply
naming and marketing information consistently. This is to ensure that
when the product or component is listed by the BQB he uses the trade name,
part numbers as intended by the manufacturer. This is particularly important
for components, because the manufacturer's customers will need to be able
to apply for pre-qualified status using correct names and version information.
An example is included of how terms used in the application for listing
of the CSR Casira Bluetooth Development kit appear on the Bluetooth website
in the Bluetooth Qualified Products List (BQPL), and of a Qualified Product
page.
A CF checklist is provided, together with a brief description of each
item.
A desirable goal for any application process is to use only electronic
documents. Electronically signed test reports are acceptable (i.e. scan
a signature and insert into the document), and generally .pdf files is
the most compact and secure form for transmitting and archiving documents.
The only documents that cannot be electronically signed are the Declaration
of Compliance and Adopters Agreement.
2 Qualification terminology
Table 1 lists terms used in various documents or on the Bluetooth technology
website. The four sources listed at the head of the columns are described
below:
DoC - Declaration of Compliance This is where the manufacturer
must declare that the product or component is compliant to the Bluetooth
Core Specification, and signature to be bound by the terms of the Adopters
Agreement. This can be filled in electronically, but must be signed in
paper form.
BQPL - Bluetooth Qualified Product List This is the list on the
Bluetooth technology website where a product or component is listed.
BPLN/BCLN - BT Product Listing Notice / BT Component Listing Notice
This is the document given by the BQB to the applicant when the product
or component has qualified. An electronic copy is linked to the qualified
product entry on the Bluetooth technology website. It lists all test
cases passed at categories A or B.
BQB Application This is a form generated by a BQB that requests
complete details of the applicant and product or component.
| DoC |
BQPL |
BPLN
/ BCLN |
BQB
Application |
| Product |
Product Name |
Brand Name |
Brand Name |
| (not named but required) |
Product ID |
Identifier |
Identifier |
| |
Product Category |
|
Product designation |
| |
Product Type |
Product Type |
Product Type |
| Software Version |
Software Version |
Software Version |
Software Status |
| Hardware Version |
Hardware Version |
Hardware Version |
Hardware Status |
| |
|
SW/HW reference platform |
|
| |
(not named but required for listing on web
- 20 words) |
|
Product Description |
| |
Reference design application |
|
|
| |
Table 1 Cross-Reference
Chart for Qualification Terminology
|
3 Compliance folder checklist
| Compliance
Folder Checklist |
Description |
| Documents for Listing |
Required for both product and component
applications |
| BQB Application Form |
Specific to each test house
or BQB, generally asks for manufacturer’s details, name and
type of device, version information etc. |
| Reference Design Application |
This is the document that
appears on the BT website. It should contain all interface information
required by a user of the product or component |
| Cat C declaration |
This is required if qualifying
software components alone or as part of a product application. The
declaration must identify the test specs used, name all cat C test
cases, and declare that all cat C test cases have been performed.
No evidence of tests performed is required. |
| Declaration of Compliance |
This is where the manufacturer
must declare and sign that the product or component is compliant
to the Bluetooth Core Specification |
| Copy of Adopters Agreement |
A paper copy of Adopters
Agreement can be lodged with any BQBs used, so does not need to
be re-submitted for each application |
| |
|
| Technical documentation |
May be required for products, required
for components |
| User Manual |
Required for products, may be required
for component if reference design application does not include sufficient
information |
| Block Diagrams |
Required for products and components.
Block diagrams of component modules using Bluecore01 may be able
to use block diagrams from data sheet. Products may be able to treat
components as single blocks in overall diagram. |
| Functional Description |
Required for products and components.
Full description of hardware and software functions required. |
| Circuit diagrams |
Required for any circuits in components,
products should not require circuits of components |
| Parts list |
Complete required for components. Products
may list component as single part |
| PCB layout |
Required for components, for products
only for circuits not part of components |
| Interface description |
Required if non-standard interfaces present
in product or component, and description insufficient in Reference
Design Application is insufficient. Standard interfaces such as
HCI do not need to be described. |
| |
|
| Test Documentation |
Required for components and for products
with tested functionality |
| BT ICS |
Summary ICS, should list all protocols
and profiles being supported in product or components (including
pre-qualified component functionality) |
| RF ICS |
Required for products and components
supporting RF (including pre-qualified component functionality) |
| BB. LM, L2CAP, RFCOMM ICS |
Required for products and components
supporting any protocol (including pre-qualified component functionality) |
| SDP, SPP etc ICS |
Required for products and components
supporting any profile (including pre-qualified component functionality) |
| Generated Test Plan |
This is generated from ICS. Test house
use a database to generate the test plan automatically. The plan
should list all cat A or B test cases that need to be passed. Pass
can be gained by testing or use of pre-qualified components |
| |
|
| Test Reports |
|
| Test Report from test house |
All test house will produce fairly standard
report formats that should be acceptable to any BQB |
| Test Report from manufacturer or third
party (CSR) |
Manufacturer can present own test reports
for cat B test cases. CSR will produce test report for modulation
tests made at CSR |
| |
|
| Change History |
|
| Change History |
This is required if hardware or software
changes are made during the course of testing. Manufacturer must
declare changes and their impact on Bluetooth functionality and
previous test results. If the BQB is not satisfied with the explanations
he can require that some test cases are re-tested. |
4 Example of bqpl product listing on bluetooth website
Two extracts are show below from the Bluetooth Website,
starting from Qualification page, selecting link to BQPL:
• Example Listing on Bluetooth Qualified Product List, found by searching for Casira product name
• Example Qualified Product page, found by selecting "details" link on BQPL listing
|
