This article breaks down every test item in BQB certification one by one. Let's establish the baseline first: all tests below apply only to self-developed Bluetooth solutions going through full qualification. If you're purchasing off-the-shelf BQB-certified modules and going through EPL simplified listing, you don't need any lab testing at all — you directly reference the module's certification.
For self-developed solutions, the overall testing structure consists of four mandatory core modules, plus two categories of specialized feature-specific testing, and supplementary interoperability verification as a lab value-add service.
1. RF Conformance Testing: The Physical Foundation Every Bluetooth Device Must Pass
RF testing is BQB certification's first gate — and the one you absolutely cannot skip. It validates whether your Bluetooth RF hardware chain — chip, matching network, antenna — meets Core specification Radio Layer parameters for transmit and receive performance. Sample units must support RF engineering test mode. Mass-production units without reserved engineering interfaces cannot be directly placed on the test bench — this must be planned during hardware design with test points or engineering command access.
Specific Test Items:
Output Power. Differentiated across Class 1, Class 2, and Class 3 power levels. Consumer electronics and automotive products typically use Class 2 with a 4 dBm upper limit. Too much power wastes energy and creates interference; too little and connections fail. Both ends must stay within spec.
Frequency Offset and Drift. Governing 2.4 GHz carrier precision. The 2.4 GHz ISM band is extremely congested — if your frequency drifts, you interfere with Wi-Fi and other Bluetooth devices, causing frequent disconnections.
Modulation Characteristics. Validating GFSK and PSK modulation waveforms and frequency deviation values. Modulation distortion directly increases communication bit error rate, degrading Bluetooth connection quality.
Receiver Sensitivity. Maintaining bit error rate within specification thresholds under extremely weak signal conditions — 0.1% for BR/EDR, with BLE having independent thresholds. This parameter directly determines Bluetooth connection range. Many customer complaints about disconnection through a single wall trace back to receiver sensitivity issues, not insufficient transmit power.
Spurious Emissions. Detecting unwanted RF leakage outside the 2.4 GHz band. Spurious emissions that exceed limits not only affect other devices but also fail your certification — conceptually similar to EMC radiated emissions but technically a separate measurement.
Beyond these five core items, RF testing also includes supplementary checks for channel isolation, power control, and frequency-hopping performance. These run as part of the overall RF test flow — they're not independent optional items.
2. Protocol Stack Consistency Testing: PTS Automated Suite for Link Layer and Transport Layer Software Compliance
RF tests the physical layer hardware; protocol stack consistency tests the software implementation. All testing relies on SIG's official PTS (Protocol Test Suite) automated tool, verifying protocol state machines and command interaction logic item by item. All BQTF-authorized labs must use PTS to produce compliant reports — custom test scripts are not accepted.
A practical note: if you're using a chip vendor's SDK protocol stack, this testing typically doesn't reveal major issues. If you've built your own protocol stack, there are significantly more pitfalls, and rework often requires multiple rounds.
Universal Base Protocols (All Dual-Mode Devices; Single-Mode Tests Corresponding Subset Only)
HCI (Host Controller Interface). Validates UART or USB communication command delivery, event reporting, and data exchange formats. If you're running a discrete AP processor + Bluetooth chip via UART communication, HCI compliance directly impacts the entire Bluetooth subsystem's stability.
L2CAP (Logical Link Control and Adaptation Protocol). Tests data packet segmentation/reassembly, connection establishment and release, service multiplexing, and QoS negotiation. L2CAP is the foundational channel for upper-layer Profiles — problems here cascade upward.
SDP (Service Discovery Protocol). Tests Classic Bluetooth SPP and audio device service broadcast and identification procedures.
RFCOMM. Tests serial port communication multiplexing procedures. Data transmission between car head units and OBD diagnostic devices relies on this protocol.
BLE-Specific Core Protocols (Only for Products with BLE)
ATT (Attribute Protocol). Tests the full interaction logic for read, write, notify, indicate, and error code handling.
GATT (Generic Attribute Profile). Tests complete interaction procedures for services, characteristics, and descriptors. GATT has the highest error rate among all BLE certification test modules. Every data communication between your device and phone app runs through GATT — a single characteristic permission misconfiguration can break the entire connection.
GAP (Generic Access Profile). Tests device advertising, scanning, pairing, connection management, and security encryption procedures.
3. Profile Application-Layer Scenario Verification: Selective Testing Based on Actual Supported Features
Protocol stack testing verifies the lower layers work; Profile testing verifies the application layer works in practice. Unlike the previous sections, this one isn't fully automated — many scenarios require manual operation and real-time observation of device status and interaction flows.
Testing scope is strictly governed by the ICS checklist — you test whichever Profiles you've declared as supported. Undeclared items aren't tested, provided your hardware genuinely doesn't integrate the corresponding functionality (not concealment).
Common automotive product Profiles:
A2DP (Advanced Audio Distribution Profile). Tests audio stream establishment, codec negotiation, sample rate switching, and streaming stability. In-car Bluetooth music and Bluetooth headphone audio use this protocol.
HFP (Hands-Free Profile). Tests incoming call alerts, answer/hang up, volume adjustment, call audio switching, and noise reduction link validation. During testing, the engineer places a call from a phone to the device under test and observes every interaction step for anomalies.
AVRCP (Audio/Video Remote Control Profile). Tests track skip, pause, next/previous, playback status synchronization, and volume remote control.
SPP (Serial Port Profile). Tests bidirectional data transmission, flow control, and long-connection keepalive.
HID (Human Interface Device Profile). Tests button and coordinate reporting for Bluetooth keyboards, mice, and controllers, plus pairing and wake procedures.
Beyond these high-frequency Profiles, MAP (Message Access), PBAP (Phone Book Access), PAN (Personal Area Networking), and others are niche — only test these if your product actually implements them.
4. LE Audio Dedicated Testing: Independent Audio System, Only If Feature Is Implemented
LE Audio and traditional A2DP/HFP are two completely independent audio systems. Whether you need LE Audio testing doesn't depend on your chip's Bluetooth version label (5.2, 5.3, or 5.4) — it depends solely on whether you've implemented LC3 codec, BIS broadcast sync stream, and Auracast broadcast audio features. If you haven't built these features, you don't test them. Not a single one.
Three Core LE Audio Tests:
·LC3 Low-Latency Audio Codec Compliance: Validates audio quality, packet loss tolerance, and transmission latency within specification requirements.
·BIS (Broadcast Isochronous Stream) Testing: Validates single-source multi-device synchronized broadcast audio scenarios.
·Auracast Public Broadcast Testing: Validates receiver access to public Bluetooth broadcasts, channel switching, and volume sync control.
LE Audio dedicated testing takes significantly more bench time than traditional A2DP/HFP items. Factor this additional time into your certification project schedule.
5. Channel Sounding Centimeter-Level Ranging: Only for Core 6.0 Devices with Ranging Enabled
Bluetooth Core 6.0's headline feature is Channel Sounding — phase-based ranging and round-trip time measurement for centimeter-level high-precision positioning, primarily targeting digital car keys, asset tracking tags, and smart lock applications.
What Gets Tested:
·Phase-based ranging accuracy validation
·Round-trip time calculation error validation
·Ranging stability testing under multi-obstruction multipath environments
·Dedicated validation for ranging broadcast and pairing security links
Compared to standard Bluetooth certification testing, Channel Sounding has significantly more complex equipment requirements and test procedures. Timeline-wise, 2025 was the phase for BQTF lab equipment debugging and small-scale pilots; 2026 marks the full commercial certification opening. The number of authorized labs currently capable of running Channel Sounding formal certification testing is limited, test slots are tight, and fees run higher than standard Bluetooth items. If you have ranging functionality certification needs, lock in lab scheduling early.
Devices with a 6.0 chip but ranging functionality not enabled don't need this testing.
6. Supplementary: Cross-Device Interoperability Verification — Lab Value-Add, Not SIG Mandatory
After completing all the standardized tests above, labs typically offer an additional verification: connecting your product with mainstream-brand Android phones, iPhones, car head units, Bluetooth earbuds, and other devices to verify normal pairing, connection, and communication.
This is not part of BQB certification's formal pass/fail criteria and doesn't generate an official audit report. But it's far from unnecessary — it can proactively catch cross-brand disconnection, pairing freezes, and audio silence issues that rank high in post-sale complaints. The cost of discovering these after market launch far exceeds the cost of running an interoperability check at the lab stage.
Need details on BQB test items for your product? Contact BlueAsia Testing & Certification — Consultant: 13534225140 (Benson)
相关新闻
