Manufacturers doing BQB certification know that testing is divided into two core areas: RF conformance and Protocol conformance. The two test systems are independent – standards, methods, and judgement logic are completely different – with dozens of test cases. This article provides a full list of core test standards and items – useful for project planning and pre‑certification self‑checks – helping avoid remediation and timeline delays.
1.1 Bluetooth Core Specification
All BQB testing is based on the Bluetooth SIG's Core Specification. Different versions (4.2, 5.0, 5.3, 5.4) have dedicated test case sets. Before starting, confirm the product's actual Bluetooth version – labs must match the version – otherwise, test results and certification submissions are invalid.
1.2 Dedicated test specifications
RF testing follows the Bluetooth RF Test Specification, while protocol testing follows the Protocol Test Specification. These official documents define test environments, procedures, limits, and pass/fail criteria – they are the sole basis for test results.
1.3 Profile conformance testing
In addition to RF and protocol, if the product claims support for extended Profiles (A2DP, HFP, HID, etc.) – corresponding conformance tests are required. These verify interoperability with phones, computers, and other Bluetooth devices.
Simple rule: the more Profiles you claim – the more test items – the longer the timeline and higher the cost.
2. RF Test Items
2.1 Transmitter tests
Transmitter tests cover output power, frequency range, 20dB bandwidth, modulation characteristics, and carrier offset. Transmit power must be within specified limits – too low means reduced range – too high causes interference – a fundamental RF compliance requirement.
2.2 Receiver tests
Receiver tests focus on receiver sensitivity, maximum input level, and PER (Packet Error Rate). Sensitivity determines signal reception capability – failure causes weak signals and disconnections. Maximum input level tests strong‑signal tolerance – PER tests data‑reception stability and accuracy.
2.3 Out‑of‑band spurious emissions
This checks unwanted radiation outside the operating band – adjacent‑channel leakage and full‑band spurious.
Important: BQB RF limits are Bluetooth SIG‑specific – independent from FCC and CE radio regulations – they cannot be aligned. Failure also blocks national radio approvals.
2.4 Hopping characteristics
The 1600 hops/sec, 79‑channel hopping mechanism applies only to classic BR/EDR Bluetooth – BLE does not have this logic and does not require testing. This verifies hopping sequence compliance, channel‑switch timing accuracy, and adaptive frequency‑avoidance.
2.5 Modulation characteristics
Different Bluetooth modes have dedicated modulation tests. BR/EDR covers GFSK, DQPSK, and 8DPSK. LE Audio's LC3 codec belongs to the core audio specification – not a traditional Profile – verifying underlying audio‑transmission consistency.
3. Protocol Test Items
3.1 L2CAP – link adaptation layer
L2CAP is responsible for data packetisation, reassembly, and channel management. Tests cover link establishment, data transmission, parameter configuration, and abnormal disconnection recovery. Protocol defects here cause packet loss, stutter, and disconnections.
3.2 GAP – general access layer
GAP is the foundation for Bluetooth interoperability – covering broadcasting, scanning, pairing, bonding, and security. Common issues (device not found, pairing failure, bonding failure) often stem from GAP implementation errors – a key protocol focus.
3.3 SDP and GATT
Classic Bluetooth uses SDP for service discovery, while BLE uses GATT for attribute reading/writing, subscription, and notification. Tests cover service registration, device discovery, and data‑interaction timing – anomalies prevent phone apps from reading or controlling the device.
3.4 Link management
This covers link encryption, key negotiation, master/slave role switching, and transmit‑power adjustment. Bluetooth 5.4's new features (PAwR periodic advertising, EAD encrypted advertising) have dedicated test cases – ensuring low‑power and encrypted‑broadcast stability.
4. Test Labs and Equipment
4.1 Lab qualification
BQB testing must be performed at SIG‑authorised labs – known as BQTF/BRTF labs. There is no split between RF and protocol qualifications – authorised labs can handle the full suite – saving sample shipments and communication overhead.
4.2 Core test equipment
RF testing uses Anritsu/Rohde & Schwarz Bluetooth testers, while protocol testing uses dedicated Bluetooth protocol analysers. All equipment must be within calibration validity – reports must include calibration certificates – otherwise SIG review fails.
5. Sample Requirements and Common Failures
5.1 Sample preparation
RF testing requires fixed‑frequency transmit capability and RF direct‑test support. Protocol testing uses normal production samples – able to complete pairing, connection, and data exchange. Typically, 3–5 samples are needed – including one fixed‑frequency sample. Some BLE solutions support alternative test methods.
5.2 Common RF failures
Common RF failures include excessive transmit power due to antenna gain mismatch, spurious emissions due to poor power‑supply filtering, and receiver sensitivity issues due to excessive receive‑chain noise. These are key pre‑test focus areas.
5.3 Common protocol failures
Common protocol failures include GAP pairing timing errors, GATT attribute read/write timing errors, and L2CAP packet length overruns. Most protocol issues are firmware‑related and can be fixed by software debugging – pre‑testing reduces retest costs and timeline.
6. Cost‑Reduction and Timeline‑Acceleration Tips
6.1 Pre‑testing
Run a full pre‑test before formal submission – identifying RF hardware and protocol firmware issues early. Pre‑test costs are far lower than formal retesting – avoiding failures and repeated remediation.
6.2 Trim redundant Profiles
Only declare Profiles actually used – don't add unnecessary features for marketing. Each additional Profile adds test items – cost and timeline increase.
6.3 Reuse module certification
Choose certified Bluetooth modules with valid QDIDs and fixed non‑replaceable antennas – finished products can use Listed simplified certification – skipping full RF and protocol retesting. Modules with replaceable antennas cannot reuse the certification.
7. Timeline and Cost Reference
7.1 Timeline
With RF, protocol, and Profile testing running in parallel, the timeline is typically 3–4 weeks. With document revisions or sample issues, it can extend to 6–8 weeks. The full process including pre‑test, formal testing, and review can be completed within 8 weeks under smooth conditions.
7.2 Cost breakdown
Costs are mainly determined by Bluetooth version and the number of declared Profiles. Higher‑version Bluetooth and LE Audio products cost more. Reusing module QDID can save over 50% of test costs. SIG fees are dynamic – refer to official pricing.
7.3 Lab selection
When selecting a lab, look for SIG official authorisation, full equipment calibration, and experienced engineers who can anticipate issues and provide remediation guidance.
For BQB certification standards, contact BlueAsia at 13534225140 (King) or email king.guo@cblueasia.com.
Related News
