# Features

Source: [https://docs.qualcomm.com/doc/80-70014-13/topic/bt_ft_overview.html](https://docs.qualcomm.com/doc/80-70014-13/topic/bt_ft_overview.html)

The WCN6856 and WCN6750 connectivity chipsets comply with <cite class="cite">Bluetooth Core
                specification v5.0</cite>. These chipsets have the following features and
            capabilities:

- A Bluetooth Low Energy data rate of up to 2 Mbps
- A long range mode with better sensitivity at two new lower bit rates, 500 kbps and
                125 kbps
- An 8x improvement in broadcast capability with the use of advertising
                extensions
- An improved channel selection algorithm (CSA #2), which enables improved channel
                coordination and coexistence efficiency with other Bluetooth and non-Bluetooth
                traffic

The following table lists the Bluetooth specifications and features supported by the
            WCN6856 and WCN6750 connectivity chipsets:

| Feature | Supported on WCN6856 | Supported on WCN6750 |
| --- | :---: | :---: |
| Bluetooth Low Energy secure connections | ✓ | ✓ |
| Bluetooth Low Energy privacy 1.2 | ✓ | ✓ |
| Bluetooth 5.0 Core specification | ✓ | ✓ |
| Data length extensions | ✓ | ✓ |
| 2 Mbps PHY | ✓ | ✓ |
| Advertising extensions | ✓ | ✓ |
| Bluetooth Low Energy long range | ✓ | ✓ |
| Channel selection algorithm (CSA #2) | ✓ | ✓ |
| USB 1.1 interface support | ✓ | ✕ |

## Bluetooth profiles and roles

Source: [https://docs.qualcomm.com/doc/80-70014-13/topic/bt_ft_overview.html](https://docs.qualcomm.com/doc/80-70014-13/topic/bt_ft_overview.html)

The Bluetooth profiles define the specifications, requirements, and roles of devices to
            establish a Bluetooth connection. The profile also determines the communication protocol
            used between devices.

Qualcomm Linux supports the following Bluetooth profiles:

### General Access Profile

Source: [https://docs.qualcomm.com/doc/80-70014-13/topic/bt_ft_overview.html](https://docs.qualcomm.com/doc/80-70014-13/topic/bt_ft_overview.html)

Bluetooth Low Energy General Access Profile (GAP) is an extension of the existing BR/EDR
            GAP. It handles the following basic operations of a device:

- Discover a device
- Establish a connection
- Bond multiple devices
- Establish a private connection
- Resolve private addresses

All Bluetooth devices must implement a basic level of functionality that GAP
            defines. GAP ensures that all Bluetooth devices can establish baseband connections,
            regardless of the higher-level functionality they support. GAP is responsible for the
            following functions:

- Generic procedures for discovering Bluetooth devices
- Link-management aspects of connecting to Bluetooth devices
- Procedures related to security levels
- Common formats for user interface-level parameters such as naming conventions

GAP defines and assigns the following profile roles to the devices: 

| Profile role | Description |
| --- | --- |
| Central | <ul class="ul" id="bt_gap_op__ul_g25_4mf_41c"><br>                                    <li class="li">A device with relatively greater processing power and<br>                                            memory.<p class="p">For example, a mobile phone or a<br>                                        tablet.</p><br></li><br><br>                                    <li class="li">Always a master</li><br><br>                                    <li class="li">It does not advertise</li><br><br>                                    <li class="li">Must support active or passive scanning and all link layer<br>                                        (LL) control procedures</li><br><br>                                </ul> |
| Peripheral | <ul class="ul" id="bt_gap_op__ul_ekp_dsy_zbc_navyanka_07-10-24-1221-15-452"><br>                                    <li class="li">A small, low-power, and resource-contained device that can<br>                                        connect to a much more powerful central device. <p class="p">For<br>                                            example, an instrument like a heart rate monitor, or a<br>                                            Bluetooth Low Energy enabled proximity tag.</p><br></li><br><br>                                    <li class="li">Always a slave</li><br><br>                                    <li class="li">Connectable advertising</li><br><br>                                    <li class="li">Must support all LL control procedures</li><br><br>                                </ul> |
| Broadcaster | <ul class="ul" id="bt_gap_op__ul_d25_4mf_41c"><br>                                <li class="li">Sends nonconnectable advertising events including<br>                                        characteristics and service data</li><br><br>                                <li class="li">It does not require a receiver</li><br><br>                            </ul> |
| Observer | <ul class="ul" id="bt_gap_op__ul_e25_4mf_41c"><br>                                <li class="li">Receives advertising events and listens for characteristics and<br>                                    service data</li><br><br>                                <li class="li">It does not require a transmitter</li><br><br>                            </ul> |

### Serial Port Profile

Source: [https://docs.qualcomm.com/doc/80-70014-13/topic/bt_ft_overview.html](https://docs.qualcomm.com/doc/80-70014-13/topic/bt_ft_overview.html)

Serial Port Profile (SPP) is a Bluetooth profile that enables wireless communication
            between devices over a virtual serial port. It supports client and server roles.

SPP defines the following elements:

- Requirements of Bluetooth devices to set up emulated serial cable connections using
                Radio Frequency Communication (RFCOMM) between two peer devices
- Terms of services provided to applications
- Features and procedures that are required for interoperability between Bluetooth
                devices

### General Attribute Profile

Source: [https://docs.qualcomm.com/doc/80-70014-13/topic/bt_ft_overview.html](https://docs.qualcomm.com/doc/80-70014-13/topic/bt_ft_overview.html)

General Attribute Profile (GATT) is a service framework that uses the Attribute Protocol
            (ATT) to discover services, and to read and write characteristic values on a peer
            device. It supports client and server roles.

GATT performs the following functions:

- Interfaces with the application through application profiles. 
    The application
                    profile defines the collection of attributes and any permissions required for
                    the attributes used in communication between devices.
- Defines the way two Bluetooth Low Energy devices transfer data back and forth using
                concepts called services or declarations, characteristics, and descriptors. 
    It
                    does not define rules for attribute use. The upper-layer applications derive
                    functionality by using these concepts.
- Stores services, characteristics, and related data in a simple lookup table with
                16‑bit IDs for each entry in the table.

### Human Interface Device over GATT Profile

Source: [https://docs.qualcomm.com/doc/80-70014-13/topic/bt_ft_overview.html](https://docs.qualcomm.com/doc/80-70014-13/topic/bt_ft_overview.html)

Human Interface Device (HID) over GATT Profile (HOGP) defines how a Bluetooth Low Energy
            wireless communications device can support HID services over the Bluetooth Low Energy
            protocol stack using GATT.

Note: The test procedure for HOGP will be provided in future releases.

Last Published: Jul 12, 2024

[Previous Topic
Getting started](https://docs.qualcomm.com/bundle/publicresource/80-70014-13/topics/get-started.md) [Next Topic
Architecture](https://docs.qualcomm.com/bundle/publicresource/80-70014-13/topics/bt_architecture_overview.md)