Bluetooth – Technology and Compliance
This page offers a structured overview of Bluetooth technology with a focus on regulatory and SIG qualification requirements—helping you understand what’s needed to bring compliant, interoperable products to global markets.
Need support with Bluetooth testing or qualification?
Explore our services:
→ Bluetooth Regulatory Testing
→ Bluetooth SIG Certification Support
Key Takeaways
Operates in the globally harmonized 2.4 GHz ISM band (2400–2483.5 MHz)
Covers multiple variants: BR/EDR (Classic), Low Energy (LE), Mesh, and LE Audio
Subject to regulatory approval under regional short-range device (SRD) frameworks (e.g., CE, FCC, ANATEL, SRRC)
Requires Bluetooth SIG qualification for trademark use, interoperability assurance, and listing in the SIG database
Requires both regulatory and SIG testing to verify spectrum compliance, RF performance, and protocol conformance
Key RF test parameters include transmit power, bandwidth, spurious emissions, and TRP for OTA-only designs
Real-world examples show how design choices influence certification and market access
Technology Overview
Bluetooth is a short-range wireless standard designed for license-exempt use in the 2.4 GHz ISM band. It enables robust device-to-device communication using Frequency Hopping Spread Spectrum (FHSS) and supports several protocol variants:
Bluetooth Classic (BR/EDR): Continuous data and audio transmission with legacy profile support
Bluetooth Low Energy (LE): Optimized for low power consumption and short data bursts
Bluetooth Mesh: Many-to-many communication architecture based on BLE, suitable for scalable device networks
Bluetooth LE Audio: Next-generation audio transmission over BLE, including broadcast and multi-stream features
All variants operate in the same frequency band and typically implement Adaptive Frequency Hopping (AFH) to minimize interference. Devices are classified by transmit power levels (e.g., Class 1, 2, or 3), depending on range and application.
Regulatory Requirements by Region
The table below summarizes key Bluetooth certification requirements across major regulatory jurisdictions.
Region / Authority | Details |
---|---|
EU – CE / RED |
Max. EIRP: 100 mW Certification Path: EN 300 328 (Self-Declaration) Remarks: AFH required >10 dBm; otherwise ≤10 % duty cycle1 |
USA – FCC |
Max. EIRP: 1 W (≥75 channels) Certification Path: FCC §15.247 via TCB Remarks: FHSS rules apply; FCC ID labeling mandatory2 |
Canada – ISED |
Max. EIRP: 1 W (≥75 channels) Certification Path: RSS-247 + IC ID Remarks: Follows FCC model; bilingual user info required |
Brazil – ANATEL |
Max. EIRP: up to 1 W Certification Path: ANATEL SRD Remarks: Local testing/MRA; ANATEL ID required |
Japan – MIC |
Max. EIRP: ~10 mW/MHz Certification Path: MIC / Telec certification Remarks: Extended band 2471–2497 MHz under PSD limits³ |
China – SRRC |
Max. EIRP: 100 mW Certification Path: SRRC SRD / CMIIT ID Remarks: Local lab required; no modular approval |
South Korea – RRA |
Max. EIRP: 100 mW Certification Path: KC Certification Remarks: CE-like approach; KC mark required |
Region / Authority | Max. EIRP | Certification Path | Remarks |
---|---|---|---|
EU – CE / RED | 100 mW | EN 300 328 (Self-Declaration) | AFH required >10 dBm; otherwise ≤10 % duty cycle1 |
USA – FCC | 1 W (≥75 channels) | FCC §15.247 via TCB | FHSS rules apply; FCC ID labeling mandatory2 |
Canada – ISED | 1 W (≥75 channels) | RSS-247 + IC ID | Follows FCC model; bilingual user info required |
Brazil – ANATEL | up to 1 W | ANATEL SRD | Local testing/MRA; ANATEL ID required |
Japan – MIC | ~10 mW/MHz | MIC / Telec certification | Extended band 2471–2497 MHz under PSD limits³ |
China – SRRC | 100 mW | SRRC SRD / CMIIT ID | Local lab required; no modular approval |
South Korea – RRA | 100 mW | KC Certification | CE-like approach; KC mark required |
Notes:
1 AFH (Adaptive Frequency Hopping) is mandatory for devices transmitting above 10 dBm in the EU; otherwise, duty cycle must not exceed 10 %.
2 FCC requires ≥75 hopping channels and a dwell time ≤0.4 s per channel within any 30 s period to qualify for 1 W EIRP.
3 Japan permits an extended frequency band of 2471–2497 MHz under strict power spectral density (PSD) limits. Bluetooth must comply with ARIB STD-T66: typically 10 mW/MHz across the band, with 3 mW/MHz limits in sensitive sub-bands (e.g. 2427–2471 MHz). ARIB is Japan’s standardization body for radio systems.
Bluetooth SIG Qualification
Bluetooth-enabled products must be qualified through the Bluetooth Special Interest Group (SIG) if they use the Bluetooth logo, claim interoperability, or implement official Bluetooth profiles and protocols. This process is mandatory in addition to regulatory testing and ensures trademark compliance and cross-device compatibility.
The qualification is based on protocol conformance, profile support, and RF-PHY (radio frequency physical layer) performance.
Qualification Details by Step
Need a quick overview? The table below summarizes each step of the Bluetooth SIG qualification process as outlined in the detailed section that follows.
Step | Details |
---|---|
1 |
SIG Membership Required for Launch Studio access. Adopter (free) or Contributor. |
2 |
Launch Studio Project Choose design type, declare version and feature set. |
3 |
QDID Reference or Creation Enables reuse of qualified designs; saves test effort. |
4 |
Testing (BQTF / self) Based on the current TCRL (Test Case Reference List): Category A = BQTF, B/C = optional or self-declared. |
5 |
BQC Involvement Optional but recommended for complex designs or faster review. |
6 |
Compliance Declaration (DoC) Mandatory even if QDID is reused. Uploaded via Launch Studio. |
7 |
Listing Fee Adopter: fee per design; Contributor: reduced or waived. |
Step | Description | Notes |
---|---|---|
1 | SIG Membership | Required for Launch Studio access. Adopter (free) or Contributor. |
2 | Launch Studio Project | Choose design type, declare version and feature set. |
3 | QDID Reference or Creation | Enables reuse of qualified designs; saves test effort. |
4 | Testing (BQTF / self) | Based on the current TCRL (Test Case Reference List): Category A = BQTF, B/C = optional or self-declared. |
5 | BQC Involvement | Optional but recommended for complex designs or faster review. |
6 | Compliance Declaration (DoC) | Mandatory even if QDID is reused. Uploaded via Launch Studio. |
7 | Listing Fee | Adopter: fee per design; Contributor: reduced or waived. |
Step-by-Step Qualification Process
The Bluetooth qualification workflow follows a standardized sequence. Even when using a pre-certified module, each manufacturer must complete their own declaration and listing.
SIG Membership
Join the Bluetooth SIG (Adopter or Contributor level) to gain access to Launch Studio and listing rights.Create a project in the Launch Studio
Define the product, select the appropriate design type (e.g., End Product, Controller Subsystem), and declare Bluetooth version and features.Reference or create a Qualified Design ID (QDID)
Reference a QDID for existing modules (simplified) or create a new one if implementing your own Bluetooth stack.Perform required testing
Conduct required protocol and RF-PHY testing at a Bluetooth Qualified Test Facility (BQTF) or under manufacturer responsibility, depending on the test category defined in the current TCRL (Test Case Reference List).(Optional) Work with a Bluetooth Qualification Consultant (BQC)
A BQC can review the setup and speed up acceptance. Listings involving a BQC are often exempt from audits for up to three years.Submit Declaration of Compliance and documentation
Complete the listing via Launch Studio. Upload logs, reports, and the official Declaration of Compliance (DoC).Pay listing fees
Adopter members must pay a per-design listing fee (typically around USD 8,000), while Contributor members benefit from reduced or waived fees depending on their membership level.
Tip:
Qualification requirements may vary depending on Bluetooth version and feature set. Always consult the latest Test Case Reference List (TCRL) and Launch Studio guidance before listing.
Qualification listings remain valid as long as the product implementation does not change significantly. However, updates such as firmware modifications, antenna changes, or version upgrades may require requalification. These cases must be evaluated carefully based on current SIG rules and the design type used.→ See also: Design Types and Qualification Paths
Bluetooth Design Types and Qualification Paths
To manage the diversity of Bluetooth implementations, the Bluetooth SIG defines specific design types. These define how a product must be qualified and whether it can reuse previously tested components via QDID referencing.
A device can consist of multiple subsystems. Depending on the design path, some components may be reused, while others require new testing and listing.
Common Design Types
The table below summarizes the common design types in the Bluetooth qualification process and their key characteristics.
Design Type | Details |
---|---|
End Product |
Description: A final product for end users, e.g. smartphone, speaker Can Reuse QDID? ✔ (subsystems) Requires Testing? Only for non-referenced parts |
Controller Subsystem |
Description: Implements low-level radio stack (Link Layer, PHY) Can Reuse QDID? ✔ Requires Testing? Required if newly developed |
Host Subsystem |
Description: Contains upper-layer Bluetooth stack (L2CAP, SDP, GATT, etc.) Can Reuse QDID? ✔ Requires Testing? Only if implementation is new |
Profile Subsystem |
Description: Implements specific Bluetooth profiles or services Can Reuse QDID? ✔ Requires Testing? As required by TCRL |
Component |
Description: Standalone chip, antenna, or module not tested as subsystem Can Reuse QDID? ✖ Requires Testing? Not eligible for listing directly |
Design Type | Description | Can Reuse QDID? | Requires Testing? |
---|---|---|---|
End Product | A final product for end users, e.g. smartphone, speaker | ✔ (subsystems) | Only for non-referenced parts |
Controller Subsystem | Implements low-level radio stack (Link Layer, PHY) | ✔ | Required if newly developed |
Host Subsystem | Contains upper-layer Bluetooth stack (L2CAP, SDP, GATT, etc.) | ✔ | Only if implementation is new |
Profile Subsystem | Implements specific Bluetooth profiles or services | ✔ | As required by TCRL |
Component | Standalone chip, antenna, or module not tested as subsystem | ✖ | Not eligible for listing directly |
Example: Module Integration
If a product integrates a pre-qualified module (e.g. a certified Host + Controller subsystem), only the remaining parts—such as custom profiles—must be tested. The final product must still be listed as an End Product under the manufacturer's name, including a new Declaration of Compliance (DoC).
Every Bluetooth-enabled product must be listed in the SIG database under the actual manufacturer—even when using fully qualified subsystems. This ensures correct linkage in the SIG database and authorizes Bluetooth logo usage.
Interoperability Testing (IOP)
Bluetooth SIG qualification ensures protocol compliance and authorizes use of the Bluetooth trademark. However, it does not guarantee real-world interoperability with third-party devices or replace regional regulatory approvals such as CE, FCC, or ANATEL certification. These requirements must be addressed separately to ensure full market access and reliable product performance.
To ensure a seamless user experience, manufacturers are encouraged to conduct interoperability testing as part of their development and validation process—especially when custom profiles, new Bluetooth versions, or unique device combinations are involved.
Typical IOP activities include:
Testing against reference implementations or widely used Bluetooth chipsets
Verifying key use cases with smartphones, headsets, medical devices, or automotive systems
Participating in Bluetooth SIG UnPlugFest events for collaborative interoperability testing
Note:
Even if a product meets all formal qualification requirements, poor interoperability may result in support issues, customer dissatisfaction, or market rejection.
For support with interoperability evaluation and Bluetooth SIG coordination, see our Bluetooth SIG Qualification Services.
Bluetooth Testing: Parameters and Setup
For the development and market approval of Bluetooth products, a solid understanding of typical test parameters and measurement setups is essential. This section outlines key characteristics of Bluetooth radio testing—both from a regulatory compliance perspective and in the context of Bluetooth SIG qualification.
Note on Coexistence:
Bluetooth radios are often integrated alongside other wireless technologies such as Wi-Fi, GNSS, or cellular modules. To ensure reliable performance, coexistence must be considered early in the design and verified during RF testing—especially in shared or adjacent frequency bands.
RF Test Parameters – Overview
Need a quick reference? The table below summarizes the most common RF parameters tested during Bluetooth certification.
Parameter | Details |
---|---|
Transmit Power |
Purpose: Determines maximum radiated or conducted signal strength Relevant Frameworks1: CE, FCC, SIG |
Frequency Accuracy |
Purpose: Ensures carrier stability relative to nominal frequency Relevant Frameworks: FCC, CE |
Occupied Bandwidth |
Purpose: Confirms signal remains within allowed spectral range Relevant Frameworks: CE, FCC, SIG |
Spurious Emissions |
Purpose: Limits unwanted emissions outside the designated band Relevant Frameworks: CE, FCC, ANATEL |
Hopping Behavior |
Purpose: Validates spread spectrum operation (e.g. min. 75 channels, dwell time) Relevant Frameworks: FCC, CE (FHSS), ANATEL |
Duty Cycle |
Purpose: Restricts transmission time per interval (typically if AFH not used) Relevant Frameworks: CE (if >10 dBm, no AFH)2 |
EIRP / ERP |
Purpose: Confirms compliance with regional radiated power limits Relevant Frameworks: CE, FCC, MIC (Japan), ANATEL |
TRP (OTA Testing) |
Purpose: Assesses total radiated power across all directions (OTA) Relevant Frameworks: SIG (if RF-PHY testing required), CE (OTA fallback)3 |
Parameter | Purpose | Relevant Frameworks1 (examples) |
---|---|---|
Transmit Power | Determines maximum radiated or conducted signal strength | CE, FCC, SIG |
Frequency Accuracy | Ensures carrier stability relative to nominal frequency | FCC, CE |
Occupied Bandwidth | Confirms signal remains within allowed spectral range | CE, FCC, SIG |
Spurious Emissions | Limits unwanted emissions outside the designated band | CE, FCC, ANATEL |
Hopping Behavior | Validates spread spectrum operation (e.g. min. 75 channels, dwell time) | FCC, CE (FHSS), ANATEL |
Duty Cycle | Restricts transmission time per interval (typically if AFH not used) | CE (if >10 dBm, no AFH)2 |
EIRP / ERP | Confirms compliance with regional radiated power limits | CE, FCC, MIC (Japan), ANATEL |
TRP (OTA Testing) | Assesses total radiated power across all directions (OTA) | SIG (if RF-PHY testing required), CE (OTA fallback)3 |
Notes:
- Relevant Frameworks: The entries reflect common certification contexts and test obligations but may vary depending on region, product class, and feature set. Always consult the applicable regulatory rules (e.g., RED, FCC Part 15, ANATEL Act 14448) and the Bluetooth SIG’s TCRL.
- AFH: Adaptive Frequency Hopping exempts devices from duty cycle limits in the EU. Without AFH, a limit of ≤10 % duty cycle applies to transmit power above 10 dBm.
- TRP: Total Radiated Power is typically required for devices without antenna connectors or when only OTA testing is feasible. It is mandatory for some SIG RF-PHY test categories.
Bluetooth RF Test Parameters in Detail
Transmit Power
Measures the maximum signal level emitted by the device, either at the antenna connector (conducted) or over-the-air (radiated). It is subject to limits under CE (e.g., 20 dBm), FCC (30 dBm for FHSS), and other regional rules. Also used for SIG conformance.Frequency Accuracy
Assesses how closely the transmitted carrier aligns with the declared center frequency. Required to ensure stability across different environments. Especially relevant for CE and FCC compliance.Occupied Bandwidth
Defines the bandwidth in which 99% of the signal power resides. Verifies spectrum efficiency and containment. Typically required for CE, FCC, and SIG qualification.
→ Glossary: Occupied BandwidthSpurious Emissions
Evaluates out-of-band and harmonic emissions that may interfere with adjacent systems. Strict limits apply across all major regulatory regimes (e.g., ≤ –30 dBm at band edges).
→ Glossary: Spurious EmissionsHopping Behavior
Applies to Bluetooth Classic (BR/EDR), which uses frequency hopping. Key parameters include the number of hopping channels (≥75 for FCC) and dwell time (≤0.4 s per channel within 30 s). Evaluated for FCC, CE (FHSS), and ANATEL.
→ Glossary: FHSS (Frequency Hopping Spread Spectrum)Duty Cycle
Relevant in the EU for devices that do not implement AFH and transmit above 10 dBm. Limits the proportion of time a device may occupy a channel (e.g., ≤10%).EIRP / ERP
Equivalent Isotropically Radiated Power (EIRP) and Effective Radiated Power (ERP) are used to express radiated output relative to antenna type. Limits vary by region and band (e.g., 100 mW in EU, 1 W in US).
→ Glossary: EIRP and Glossary: ERPTRP (Total Radiated Power)
Used when conducted measurements are not feasible (e.g., integrated antennas). Required in SIG RF-PHY qualification and sometimes for CE if OTA-only testing is applied. Assesses cumulative radiated energy in all directions.
Measurement Setup and Test Modes
To ensure valid and repeatable test results, Bluetooth devices must be evaluated using standardized setups. The choice between conducted and radiated (OTA) measurement depends on antenna accessibility, certification framework, and product design.
Conducted Setup
The DUT is connected via coaxial interface or PCB pad to lab equipment. This method minimizes variation and is preferred for power and modulation measurements.
Common for: SIG RF-PHY, CE modular, FCC Part 15Radiated (OTA) Setup
Used when RF ports are not accessible or to verify real-world emissions. Measurement occurs in shielded chambers using antennas and reference methods.
Common for: CE spurious/OTA, SIG fallback, FCC radiated
Typical Measurement Elements
Element | Details |
---|---|
1. Test Mode Activation |
Purpose: Enables controlled or continuous TX/RX for measurement Common Applications: SIG RF-PHY, CE, FCC, ISED |
2. RF Test Port Access |
Purpose: Connects DUT directly to analyzer via RF pad or U.FL/SMA Common Applications: SIG (conducted), CE, FCC |
3. OTA Chamber |
Purpose: Measures TRP, spurious emissions in radiated setup Common Applications: CE, FCC, SIG OTA fallback |
4. Load Simulator |
Purpose: Reproduces real-world power draw or output state Common Applications: CE EMC (EN 301 489-x), FCC |
5. Custom Firmware / CLI |
Purpose: Sets fixed channel, disables AFH, enables worst-case test mode Common Applications: All regimes |
6. Shielded Enclosure |
Purpose: Prevents external RF from affecting sensitive tests Common Applications: Pre-compliance (spurious), CE EMC |
7. Reference Antenna |
Purpose: Normalizes ERP/EIRP; calibrates OTA emissions Common Applications: CE, FCC, SIG TRP |
8. Switch Matrix / Combiner |
Purpose: Selects RF path in MIMO or diversity systems Common Applications: OTA testing, SIG RF-PHY, CE dual-path |
Element | Purpose / Function | Common Applications (examples) |
---|---|---|
1. Test Mode Activation | Enables controlled or continuous TX/RX for measurement | SIG RF-PHY, CE, FCC, ISED |
2. RF Test Port Access | Connects DUT directly to analyzer via RF pad or U.FL/SMA | SIG (conducted), CE, FCC |
3. OTA Chamber | Measures TRP, spurious emissions in radiated setup | CE, FCC, SIG OTA fallback |
4. Load Simulator | Reproduces real-world power draw or output state | CE EMC (EN 301 489-x), FCC |
5. Custom Firmware / CLI | Sets fixed channel, disables AFH, enables worst-case test mode | All regimes |
6. Shielded Enclosure | Prevents external RF from affecting sensitive tests | Pre-compliance (spurious), CE EMC |
7. Reference Antenna | Normalizes ERP/EIRP; calibrates OTA emissions | CE, FCC, SIG TRP |
8. Switch Matrix / Combiner | Selects RF path in MIMO or diversity systems | OTA testing, SIG RF-PHY, CE dual-path |
Bluetooth Test Setup – Details by Element
Test Mode Activation
Required by CE, FCC, and SIG to generate fixed-pattern emissions. Often configured via HCI or vendor CLI.RF Test Port Access
For conducted testing, devices must expose RF outputs. May involve shield removal or testpad activation.OTA Chamber
Required for spurious, TRP, or fallback RF-PHY. Must include calibrated reference antennas and absorber lining.Load Simulator
Replaces dynamic components (e.g., speakers, batteries) with stable resistive loads. Needed for EMC stability.Custom Firmware / CLI
Required to fix parameters (e.g., TX power, hopping behavior) and support manual test mode selection.Shielded Enclosure
Ensures clean test environment without ambient interference. Often paired with LISN and bonding fixtures.Reference Antenna
Ensures measurement traceability when calculating ERP/EIRP or comparing emission levels.Switch Matrix / Combiner
Allows seamless port selection when multiple antennas are present—especially important in automated RF chains.
Worst-Case Configuration for Bluetooth Testing
Tests must be conducted under worst-case RF conditions to simulate maximum regulatory load. These include:
Maximum transmit power
Fixed channel (low/mid/high)
Continuous or highest allowed duty cycle
Disabled AFH (Adaptive Frequency Hopping) and power-saving modes
Longest PDU (Protocol Data Unit) or highest modulation rate
All radios active (if dual-radio system, e.g. Wi-Fi + Bluetooth)
Note: All test modes must be available via firmware or CLI and documented in the test report.
Test Sample Preparation and Configuration
Before testing begins, the device under test (DUT) must be configured according to applicable requirements:
Firmware
Must reflect the final product state or be a test version with identical radio frequency (RF) behavior.Hardware
Include housing unless the test requires direct access to the printed circuit board (PCB).Power Supply
Use a stable laboratory power source or a fully charged battery. Any deviations must be documented.RF Access / Connectors
Provide test connectors or enable test mode with Over-the-Air (OTA) fallback justification, if no conducted access is available.Antenna Configuration
The antenna path must be clearly defined and fixed. For products using antenna diversity or Multiple Input, Multiple Output (MIMO) technology, the test configuration must specify which path is active.Multi-Radio Behavior
If the Bluetooth device includes additional radios (e.g., Wi-Fi, GNSS, LTE), all interfaces must be active during testing unless otherwise justified. This is critical for assessing coexistence behavior and interference susceptibility—especially when multiple radios operate simultaneously in adjacent or overlapping bands (e.g., Bluetooth and Wi-Fi in 2.4 GHz). Improper coexistence handling may lead to degraded performance or failed compliance under real-world conditions.Bluetooth Test Mode
To enable standardized testing, Bluetooth devices must support a dedicated test mode that allows direct control of transmission and reception behavior. This mode is used during certification and production testing and is typically activated via HCI or vendor-specific interfaces. For Bluetooth LE, the Direct Test Mode (DTM) allows measurement of RF parameters without normal protocol operation.
Reporting Tip: The test documentation must include the firmware version, antenna configuration, transmit (TX) path used, and any commands or procedures required to activate the test mode. For a complete checklist of sample preparation, firmware settings, and test workflows, see the Radio Compliance Preparation Guide.
Testing Labs and Conformity Assessment
Accredited testing laboratories and recognized conformity assessment bodies play a critical role in the development and approval of Bluetooth-enabled products. Their expertise supports both regulatory compliance and Bluetooth SIG qualification—particularly when navigating complex market requirements or preparing products for international distribution.
Typical responsibilities include:
Performing standardized RF and EMC tests under CE (RED), FCC, ISED, ANATEL, or MIC frameworks
Supporting Bluetooth SIG qualification (e.g., RF-PHY testing at a BQTF)
Assisting with sample preparation, firmware configuration, and test mode activation
Providing accredited test reports for type approval, self-declaration, or SIG listings
Advising on interoperability, regional restrictions, and product adaptations
Note: While self-declaration may be acceptable in some regions (e.g., under CE), many certification schemes require formal test reports from accredited laboratories. Early consultation and pre-compliance testing can reduce delays, ensure correct setups, and streamline approval across multiple markets.
Real-World Examples
The following case studies illustrate how Bluetooth technologies are implemented across different industries—and how specific use cases affect regulatory testing, SIG qualification, and integration workflows. Each example highlights key parameters, approval strategies, and lessons learned from practical certification scenarios.
Automotive Application: BLE Car Access System
A vehicle manufacturer implemented a Bluetooth Low Energy (BLE)-based access system that uses the driver’s smartphone as a digital key. BLE modules installed in the vehicle continuously advertise their presence and unlock the doors based on signal proximity.
Key Parameters
Technology: Bluetooth Low Energy (BLE), fixed beaconing
Output Power: Very low transmit power (≤ 0 dBm)
Hardware: Automotive-grade, pre-certified BLE module (AEC-Q100)
Installation: Permanently embedded in the vehicle body (e.g. door handle or ECU)
Certification Strategy
Market Classification: Treated as a standard short-range radio device, despite being vehicle-integrated
Target Regions: CE, FCC, ISED, MIC (Japan), ANATEL, SRRC
SIG Qualification: OEM lists the product as a Bluetooth End Product and references the pre-qualified Host + Controller subsystem (QDID)
Regulatory Testing: No additional RF retesting required for the module, but full compliance documentation and separate approval needed
Aftermarket Option
Product may be offered as a retrofit kit depending on platform strategy
Separate labelling or EMC documentation may be required for aftermarket versions
May trigger automotive EMC evaluation depending on integration depth
For OEM integration, additional support may be needed for documentation under automotive EMC directives (e.g., vehicle type approval)
Components installed in vehicles may be subject to ECE-R-10 requirements for electromagnetic compatibility. See also: ECE-R-10 – EMC in Vehicles
Lessons Learned
Even fully embedded systems often require standalone SRD approval.
A pre-certified module and proper SIG referencing simplify global market access.
Future upgrades (e.g., with UWB) would require full re-evaluation under frameworks like EN 302 065 or FCC Part 15 Subpart F.
Close cooperation with an accredited testing laboratory supports long-term success—especially when planning multi-radio extensions or platform variants.
Consumer Application: Bluetooth Mesh Wristband
A compact wearable device was developed for indoor localization and emergency signaling in assisted living environments. The product communicates via Bluetooth Mesh and acts as a relay node within a multi-node BLE network.
Application Context
Technology: Bluetooth Low Energy (BLE) with Mesh Profile
Use Case: Continuous presence detection and message relaying
Power Level: Low transmit power (–5 to 0 dBm)
Form Factor: Ultra-compact wristband with integrated chip antenna
Firmware: Fixed advertising and mesh relaying with configurable UUID
Installation: Worn on the body; no conducted test port available
Compliance Strategy
Test Method: Over-the-Air (OTA) testing due to lack of RF connector
CE (EU): Adaptivity required due to frequent transmissions
AFH active by default, exempting from 10 % duty cycle limit
FCC/ISED: Standard BLE procedures applied
EMC/Safety: Assessed under CE and FCC frameworks
Labeling: CE and SIG labeling provided via e-label in companion app
Bluetooth SIG Qualification
Design Type: End Product
Qualification Method:
Referenced a certified subsystem QDID
Completed mesh profile testing using the PTS Tool
Result: Fully listed in the SIG database with mesh profile version and BLE version noted
Lessons Learned
Even compact OTA-only products must meet full RF and EMC requirements
Mesh behavior increases transmission frequency but does not fundamentally change the regulatory test scope
Proper antenna layout and early lab consultation help avoid certification delays
SIG mesh testing introduces additional qualification effort
Early AFH validation simplifies CE compliance
Consumer Application: Smart Speaker with LE Audio & Wi-Fi
A premium audio manufacturer introduced a next-generation smart speaker supporting classic Bluetooth audio, LE Audio (incl. Auracast), and dual-band Wi-Fi. The device is designed for wireless pairing with headphones and smart home integration—requiring advanced coexistence handling and qualification under multiple regimes.
Application Context
The product combines multiple wireless technologies and aims to support emerging audio standards:
Technologies: Bluetooth Classic (BR/EDR), Bluetooth LE Audio with Auracast, Wi-Fi (2.4 GHz / 5 GHz)
Use Case: High-quality wireless audio streaming and future-ready headphone broadcasting
Output Power: Class 1 (up to ~20 dBm for Classic Bluetooth)
Installation: Fixed indoor use; operates as audio source and broadcasting node
Antenna Setup: Shared or co-located antennas for Wi-Fi and Bluetooth
Regulatory Considerations
Due to simultaneous use of Bluetooth and Wi-Fi in the 2.4 GHz band, the speaker was subject to advanced regulatory checks:
EU (CE):
Adaptive Frequency Hopping (AFH) must remain permanently enabled to permit full 100 mW transmission
The lab validated AFH via controlled interference (Wi-Fi traffic simulation)
USA (FCC):
Coexistence testing with concurrent 2.4 GHz operation
Cumulative emission and intermodulation measurements were required
Outcome: Passed CE and FCC compliance through coordinated test scenarios
Bluetooth SIG Qualification
As a LE Audio device, the speaker underwent extended Bluetooth SIG testing:
Profiles Covered: A2DP, AVRCP, HFP (Classic); BAP (LE Audio)
Conformance Elements:
RF-PHY tests for isochronous channels (Auracast support)
LC3 codec implementation and broadcast features verified
Test Category: Several functions fell under Category A, requiring BQTF execution
Support: The manufacturer used BQE services for profile registration and Launch Studio listing
Result: Qualified listing with Auracast logo usage rights
Lessons Learned
Multi-radio products face elevated certification complexity—especially in the 2.4 GHz band
Early coexistence testing helps identify critical emission and coordination issues
AFH enforcement in firmware is essential for CE compliance at higher power levels
SIG qualification for LE Audio involves new profiles and tools; Category A test cases require a BQTF
Collaboration with a test lab offering combined regulatory, interoperability, and SIG services streamlines market access
FAQ – Practical Questions
How do regulatory approval and SIG certification differ?
Regulatory approval (e.g., CE, FCC) is a legal requirement for market access. It ensures that a device complies with key criteria for safety, electromagnetic compatibility (EMC), and efficient spectrum use.
Bluetooth SIG certification, by contrast, is a contractual obligation governed by the Bluetooth Special Interest Group. It is required to use the Bluetooth logo and guarantees interoperability through defined protocol and profile conformance testing.
While separate in scope, both processes are complementary: one ensures legal compliance, the other guarantees Bluetooth compatibility and brand legitimacy.
Do I need Bluetooth SIG certification if I use a pre-certified module?
Using a pre-certified module simplifies the process—but it doesn’t eliminate the need for Bluetooth SIG qualification.
The module vendor typically provides a Qualified Design ID (QDID) for the certified subsystem. As the device manufacturer, you must still complete an End Product Listing via the Bluetooth Launch Studio, referencing the QDID. No additional RF-PHY testing is required as long as the module is used unchanged (same firmware, same antenna layout).
However, a formal Declaration of Compliance and payment of a listing fee are still required to legally market the product as a Bluetooth device. A pre-qualified module saves time and testing effort, but SIG listing is still mandatory—just significantly easier.
Do I need to retest a certified Bluetooth module in my product?
FCC / ISED (North America):
If the Bluetooth module has valid Modular Approval, it usually doesn't require full RF retesting—as long as integration conditions are met, such as:
Antenna type and gain match the original module approval
The module is shielded and installed as an independent unit
The FCC ID is labeled on the final product
You still need:
An SDoC for the host device (to cover unintentional emissions)
Final product documentation including the module’s FCC ID
EU (RED):
There’s no formal modular approval concept. The entire product must meet RED compliance, including emissions and immunity. However, you may reuse the module’s test report to reduce effort. At minimum, perform radiated emission tests on the final product to ensure compliant integration.
Bluetooth SIG Reminder and Summary:
Even if the module is already SIG-qualified, you must submit your own listing under your company name. No full retesting needed—but integration checks, documentation, and proper declarations are still required.
Do I need a Notified Body for Bluetooth under the RED?
In most cases: No.
Bluetooth operates in the harmonized 2.4 GHz SRD band and falls under the harmonized standard EN 300 328. If your product fully complies with this standard—including adaptivity and duty cycle limits—you may use the self-declaration route for CE marking.
A Notified Body (NB) is only required if:
You deviate from the requirements of the harmonized standard
No applicable harmonized standard exists for your use case
Optional:
Some manufacturers voluntarily involve a Notified Body to obtain a Certificate of Opinion for added assurance or marketing purposes—but this is not mandatory.
Summary:
For standard Bluetooth products using EN 300 328, self-declaration is sufficient under the RED.
Is separate approval needed for LE Audio if Classic Bluetooth is already certified?
Regulatory: No. LE Audio operates in the same 2.4 GHz band using the same RF parameters. As long as your device meets existing Bluetooth test limits, no new approval is needed. Just ensure that Adaptive Frequency Hopping (AFH) is enabled—especially in the EU, where continuous streaming may otherwise exceed duty cycle limits.
Bluetooth SIG: Yes. LE Audio introduces new profiles (e.g., BAP, PAC) and features like isochronous channels. These are not covered by earlier Classic Bluetooth qualifications.
To add LE Audio, you must:
Perform a supplemental qualification
Reference existing QDIDs where applicable
Run additional profile and protocol tests (e.g., RF-PHY for LE Audio)
If your chipset is already qualified for LE Audio, you can reuse parts of the qualification—but you must still declare and list your own product.
Summary:
No new regulatory approval required, but a Bluetooth SIG update is mandatory for LE Audio support.
Can I certify my Bluetooth product globally with a single test?
Not directly—there is no universal certification accepted worldwide. However, many countries recognize overlapping technical standards or accept test data via mutual recognition agreements (MRAs).
Key Points:
EN 300 328 (EU) and FCC Part 15 (USA) share many technical requirements
Test labs can generate combined reports to reduce duplication
MRAs exist between regions such as EU–USA/Canada, EU–Japan, and USA–Japan
Countries like Brazil or China often accept CE/FCC reports but may require local testing
Best Practice:
Plan your testing campaign to meet the strictest common requirements (usually EU + FCC). From there, have your lab format the results into region-specific reports (e.g., EN 300 328 for CE, FCC/IC report, ARIB report for Japan).
A coordinated global test strategy—backed by an experienced lab—can minimize redundancy and help you gain worldwide approval efficiently.
How long does Bluetooth certification and approval take?
The timeline depends on product type, target markets, and lab availability. Typical durations are:
CE / FCC testing:
Lab testing and reporting: 1–2 weeks
FCC certification (TCB Grant): 2–5 days after report submission
CE Declaration of Conformity: Can be issued immediately once tests and documentation are complete
Bluetooth SIG qualification:
Straightforward End Product Listing using a certified module: 1 day
With new RF-PHY testing or profile qualification: Several weeks, depending on test results and debugging effort
Total expected timeframe:
If all steps go smoothly, the entire process—from initial testing to final certificates—typically takes 4 to 8 weeks.
Best practice:
Start pre-compliance testing early to detect issues before final approval. This reduces risk and keeps your project on schedule.
Looking for Support?
Need help with Bluetooth testing, SIG qualification, or multi-market certification?
Our accredited labs provide regulatory testing, profile validation, and qualification support for Classic Bluetooth, LE Audio, Mesh, and more.→ Bluetooth Regulatory Testing
→ Bluetooth SIG Certification Support
Further Reading & Official Resources
Selected Bluetooth Regulations and Standards
-
EU – ETSI EN 300 328
Harmonized standard for 2.4 GHz SRDs under RED: https://www.etsi.org/ (PDF)
-
USA – FCC Part 15.247
Technical rules for frequency hopping and digital modulation: https://www.ecfr.gov/
-
Canada – ISED RSS-247
Certification standard for 2.4 GHz devices: https://ised-isde.canada.ca/
-
Japan – ARIB STD-T66
Bluetooth requirements and band limits in Japan: https://www.arib.or.jp/
Bluetooth SIG Resources
-
Bluetooth Launch Studio
Product listing and qualification management: https://launchstudio.bluetooth.com/
-
Bluetooth Qualification Process Overview
Official guide to qualification and design types: https://www.bluetooth.com/
-
Bluetooth Test Specifications (TCRL)
Test Case Reference List (TCRL) and RF-PHY requirements: https://www.bluetooth.com/
Additional Resource
-
TAMSys by IB-Lenhardt AG – Type Approval Management System
A centralized compliance platform for managing radio certification, regulatory data, and certificate tracking across major markets including the EU, USA, China, Japan, Brazil, and more. → TAMSys – Type Approval Management System
This is a curated selection of key sources. For full and up-to-date regulatory documentation, please refer to the official portals of the relevant authorities. All references were verified as of May 2025.