Communicating Supported Bluetooth^® Functionality

It offers a framework that defines Bluetooth communication elements, preferred terminology, and usage criteria established by the Bluetooth SIG for each element. The intended audiences include members developing end-use products (e.g., mice, headphones, electronic shelf labels) and enabling technology products (e.g., chipsets, stacks, modules). The Bluetooth SIG advises members to refer to this guidance when publicly communicating supported Bluetooth functionality.

This section provides guidance on communicating supported Bluetooth functionality in end-use products. It outlines the Bluetooth elements that members are encouraged to convey and offers examples of how to effectively communicate those selected elements.  

2.1 Communication Elements

End-use product companies are encouraged to utilize the communication elements listed below. Please note that while members often combine the Bluetooth wordmark with the Bluetooth® Core Specification version against which they qualified their product (e.g., Bluetooth 5.4) to indicate support for Bluetooth technology, the SIG does not endorse this, as it may lead to incorrect assumptions about supported Bluetooth functionality. 

	Communication Elements Recommended terminology for use in promotional materials.	Communication Criteria Product has completed the Bluetooth® Qualification Process and includes:
Bluetooth® Technology  For communicating support for Bluetooth® technology.	Bluetooth®1	= No criteria beyond qualification
Bluetooth® Applications2  For communicating supported Bluetooth® applications as needed.	Classic Audio LE Audio AuracastTM  ESL NLC	= Layer: A2DP or HFP = Layer: TMAP or HAP = Layer: PBP3  = Layer: ESLP = Layer: ALSNLCP, BLCNLCP, BSSNLCP, DICNLCP, ENMNLCP, or OCSNLCP
Bluetooth® Core Version4 For communicating the Bluetooth® Core Specification against which the product was qualified, if applicable.	Bluetooth® Core 5.0 Bluetooth® Core 5.1 Bluetooth® Core 5.2 Bluetooth® Core 5.3 Bluetooth® Core 5.4 Bluetooth® Core 6.0	= ICS: CORE 1/50 or 2/50 = ICS: CORE 1/51 or 2/51 = ICS: CORE 1/52 or 2/52 = ICS: CORE 1/53 or 2/53 = ICS: CORE 1/54 or 2/54 = ICS: CORE 1/60 or 2/60

¹Per the Brand Guide for Bluetooth® Trademarks, the term “technology” should directly follow “Bluetooth®” if it is unclear that “Bluetooth®” refers to a wireless technology.
²When referring to an application outside of any Bluetooth context, use “Bluetooth®” before the name (e.g., Bluetooth® ESL).
³In addition to supporting PBP, the Auracast Trademarks have additional usage requirements outlined in the Brand Guide for Bluetooth® Trademarks.
⁴The Bluetooth® Core version should not be included in product names or used as the sole method for communicating support for Bluetooth technology.

2.2 Communication Example

Below is an example of a web page showcasing a product’s technical specifications section, where Bluetooth® functionality support is typically highlighted. While formats may vary, this provides an accurate representation of how relevant communication elements should be displayed when the communication criteria for each element are met. 

After reviewing the example, if your team has specific questions about communicating supported Bluetooth functionality in your products, please contact the Brand Management Team at the Bluetooth SIG.

Note: If none of the Bluetooth applications listed in the communications elements table (Section 2.1) are supported, the Bluetooth SIG recommends displaying only “Bluetooth®” without additional details. The Bluetooth SIG also advises against specifying the Bluetooth® Core version at this communication level, as it may confuse end users. If you choose to include this information, it should be displayed as: “Qualified against Bluetooth® Core 5.4″ (for example). 

2.3 Communicating Future Support

Members may communicate future support for Bluetooth applications in end-use products listed in the communication elements table by using the phrase “Ready for”, provided that the member has qualified (or intends to requalify) the product with Bluetooth specification support for the defined application (e.g., PBP for Auracast™), and intends to provide an update to products already in the field that are marketed as having future support. An example is provided below. 

 

3. Enabling Technology Product guidance

This section provides guidance on communicating supported Bluetooth functionality in enabling technology products. It outlines the Bluetooth elements that members are encouraged to convey and offers examples of how to effectively communicate those selected elements. 

3.1 Communication Elements

Enabling technology product companies are encouraged to utilize the following communication elements listed below. Please note that while members often combine the Bluetooth wordmark with the Bluetooth® Core Specification version against which they qualified their product (e.g., Bluetooth 6.0) to indicate support for Bluetooth technology, the SIG does not endorse this, as it may lead to incorrect assumptions about supported Bluetooth functionality. 

	Communication Elements Recommended terminology for use in promotional materials.	Communication Criteria Product has completed the Bluetooth® Qualification Process and includes:
Bluetooth® Technology  For communicating support for Bluetooth® technology.	Bluetooth®1  Bluetooth® Classic  Bluetooth® LE  Bluetooth® Dual-Mode	= No criteria beyond qualification = ICS: CORE 30/1 or 30/3 = ICS: CORE 30/2 or 30/3 = ICS: CORE 30/3
Bluetooth® Features2 3  For communicating supported Bluetooth® features as needed.	Channel Sounding LE 2M  LE Coded  Direction Finding LE Power Control Isochronous Channels Extended Advertising Periodic Advertising Periodic Advertising with Responses LE Secure Connections Classic Audio LE Audio Mesh Networking	= ICS: CS 1/1 or 1/2 = ICS: RFPHY 1/4 = ICS: RFPHY 1/7 = ICS: RFPHY 1/9 or 1/11 = ICS: LL 9/37 = ICS: LL 9/31, 9/32, or 9/33 = ICS: LL 9/41 = ICS: LL 9/42 = ICS: LL 9/49 or 9/50 = ICS: GAP 27b/5 or 37b/5 = Layer: A2DP or HFP = Layer: BAP = Layer: MESH or MMDL
Bluetooth® Profiles4 5   For communicating supported Bluetooth® profiles as needed.	Advanced Audio Distribution Profile Hands-Free Profile Telephony and Media Audio Profile Hearing Access Profile Public Broadcast Profile Ranging Profile Generic Health Sensor Profile Electronic Shelf Label Profile Ambient Light Sensor NLC Profile Basic Lightness Controller NLC Profile Basic Scene Selector NLC Profile Dimming Control NLC Profile Energy Monitor NLC Profile Occupancy Sensor NLC Profile	= Layer: A2DP = Layer: HFP = Layer: TMAP = Layer: HAP = Layer: PBP = Layer: RAP = Layer: GHSP = Layer: ESLP = Layer: ALSNLCP = Layer: BLCNLCP = Layer: BSSNLCP = Layer: DICNLCP = Layer: ENMNLCP = Layer: OCSNLCP
Bluetooth® Core Version6   For communicating the Bluetooth® Core Specification against which the product was qualified, if applicable.	Bluetooth® Core 5.0 Bluetooth® Core 5.1 Bluetooth® Core 5.2 Bluetooth® Core 5.3 Bluetooth® Core 5.4 Bluetooth® Core 6.0	= ICS: CORE 1/50 or 2/50 = ICS: CORE 1/51 or 2/51 = ICS: CORE 1/52 or 2/52 = ICS: CORE 1/53 or 2/53 = ICS: CORE 1/54 or 2/54 = ICS: CORE 1/60 or 2/60

¹Per the Brand Guide for Bluetooth® Trademarks, the term “technology” should directly follow “Bluetooth®” if it is unclear that “Bluetooth®” refers to a wireless technology.
²When referring to a feature outside of any Bluetooth context, use “Bluetooth®” before the name (e.g., Bluetooth® Channel Sounding).
³This table outlines key Bluetooth features; members may also communicate additional features that have qualified support.
⁴When referring to a profile, it is acceptable to use the layer acronym if needed (e.g., “RAP” instead of “Ranging Profile”).
⁵This table outlines key Bluetooth profiles; members may also communicate additional profiles that have qualified support.
⁶The Bluetooth® Core version should not be included in product names or used as the sole method for communicating support for Bluetooth technology.

3.2 Communication Example

Below is an example of a web page showcasing a product’s features section, where Bluetooth® functionality support is typically highlighted. While formats may vary, this provides an accurate representation of how all communication elements should be displayed when the communication criteria are met for each element.

After reviewing the example, if your team has specific questions about communicating supported Bluetooth functionality in your products, please contact the Brand Management Team at the Bluetooth SIG.  

3.3 Communicating Early Support

Members may communicate early support for pre-adopted Bluetooth features (and profiles) in enabling technology products listed in the communication elements table, provided they clearly indicate “early support” and acknowledge that such support is “based on a working draft of a potential Bluetooth Specification subject to change.” An example is provided below.