For Bluetooth products seeking BQB certification, understanding the standard hierarchy and test scope is critical. Misjudging the boundaries often leads to missing items or redundant testing. This article outlines the complete test framework and common failure points based on actual lab experience.

1. Four‑Layer Standard Hierarchy

BQB certification rests on four interdependent layers – they are not parallel.

·Bottom layer: Bluetooth Core Specification – defines RF hardware and protocol stack fundamentals.

·Second layer: Profiles – define interaction rules for different usage scenarios.

·Third layer: Test specifications – extract standardised test cases from the Core and Profiles.

·Top layer: QPRD v2 (Qualification Program Reference Document) – governs application, document review, and database listing.
Most scope errors come from mixing up these layers, leading to incorrect ICS (Implementation Conformance Statement) declarations.

1.1 Current QPRD Version

The officially effective version is QPRD v2. Many online sources still reference draft QPRD v3 content as current rules – this causes misjudgements. All sample testing, document submission, and SIG review must follow QPRD v2.

  2. RF Test Items

2.1 General RF Requirements

RF testing is mandatory for all Bluetooth products, regardless of version or profiles – no exemptions. Tests follow SIG’s official RF test specification, aligned with the Core Specification’s physical‑layer metrics.
Key parameters: transmit power, frequency offset, modulation accuracy, receiver sensitivity, and spurious emissions – all have defined limits and standardised methods – cannot be judged by engineer experience alone.

2.2 BR/EDR vs. BLE Differences

Classic Bluetooth (BR/EDR) and BLE RF metrics are not interchangeable.

·BR/EDR: tests GFSK, DPSK/π/4‑DQPSK modulations – power spectral density, 20 dB bandwidth, adjacent‑channel power.

·BLE: only GFSK – transmit power, frequency deviation, modulation index.
Dual‑mode products must run both sets – test man‑hours double. A single‑mode BLE product has roughly half the RF workload of a dual‑mode one.

2.3 Common RF Failures

Excessive transmit power is the most frequent issue – manufacturers boost power for range, but Bluetooth has defined power classes – exceeding limits = immediate failure.
Spurious emissions are the second most common – tied to PCB layout and shielding. Software alone cannot fix inadequate shielding – requires hardware rework.

  3. Protocol Stack Conformance Testing

3.1 PTS Automated Testing

Protocol conformance is tested using SIG’s official PTS (Profile Tuning Suite) – all BQTF‑accredited labs must use PTS‑generated reports. In‑house scripts or simple capture logs are not accepted by SIG review.
PTS covers L2CAP, HCI, ATT, GATT – with automated cases focusing on state‑machine transitions and exception handling.

3.2 GATT – Most Common Failure Area

GATT is the foundation for BLE application‑layer communication – directly affects interoperability with phones and is the lowest‑pass‑rate protocol module.
Typical failures: missing service discovery info, incorrect characteristic notification behaviour, wrong attribute‑access permissions. Root cause is usually GATT table definition deviating from Core Specification during firmware development.

3.3 HCI Testing Scope

HCI handles host‑controller communication. HCI conformance defects cause packet loss and parsing errors between the upper stack and RF. Test cases verify HCI command/event formats, timing, and standard error‑code returns.

  4. Profile Testing

4.1 Tests Match Declared Profiles

Only the profiles your product actually implements are tested – strictly aligned with the ICS declaration – no arbitrary addition/removal of test cases.
Common automotive profiles: A2DP (stereo audio), HFP (hands‑free), AVRCP (remote control), SPP (serial data). Headphones/speakers focus on A2DP + HFP. Head units add full AVRCP cases.

4.2 Profile Test Case Characteristics

Each profile has its own test specification.

·A2DP: audio link establishment, codec negotiation, flow control.

·HFP: call setup, voice‑channel switching, noise‑reduction logic.
Many failures only occur under specific device states – requiring repeated firmware debugging.

4.3 Interoperability Testing Rules

After profile conformance, interoperability verification is required – pairing with mainstream phones in real‑use scenarios.
Interoperability is not mandatory for every certification:

·New hardware designs – full test.

·Derivative changes that do not affect the interaction layer may qualify for exemption.

  5. LE Audio and Channel Sounding – Special Tests

5.1 LE Audio Triggers

Whether LE Audio is tested depends on actual enabled functions – not simply the Bluetooth version printed on the chip. If the firmware enables LC3 codec, BIS broadcast, or Auracast – corresponding tests are required. The decision is based on firmware capability, not chip version.
LE Audio adds substantial new content – LC3 quality evaluation, BIS timing, Auracast group management. By 2026, all major BQTF labs routinely handle commercial LE Audio certifications.

5.2 Channel Sounding

Channel Sounding is a new Core 6.0 feature – achieves centimetre‑level ranging via phase measurement. Only devices that enable this ranging function require testing. Even with a 6.0‑capable chip, if the feature is not enabled – no testing required.
In 2026, labs have opened commercial acceptance – tests cover phase measurement accuracy, ranging range, and stability under multipath interference.

  6. Test Reports, DN Listing, and Change Control

6.1 Submission and Listing Process

After BQTF lab tests, the formal report is uploaded to SIG’s Qualification Workspace. Staff verify that test results match the ICS declaration. Upon approval, a DN (Design Number – formerly QDID) is assigned and the product is listed in the database.

6.2 When Changes Trigger Retesting

·Cosmetic/UI changes with no RF or protocol impact – only change notification required – no retest.

·Audio algorithm or connection‑logic changes – even without hardware changes – require lab evaluation for possible retesting.

·Antenna or transmit‑power changes – RF retesting mandatory.

·Full Bluetooth SoC replacement – full RF + protocol retesting.

6.3 Pre‑Certification Advice

Before starting BQB, agree with your BQTF lab on the exact test scope – protocol layers, all profiles, and whether LE Audio/Channel Sounding are enabled. Accurate scope prevents extra costs and avoids missing tests.

For BQB certification, contact BlueAsia at 13534225140 (King) or king.guo@cblueasia.com.