# Features Source: [https://docs.qualcomm.com/doc/80-70015-13/topic/bt_ft_overview.html](https://docs.qualcomm.com/doc/80-70015-13/topic/bt_ft_overview.html) The WCN6750, WCN6856, and QCA6698AQ connectivity chipsets comply with the Bluetooth Core specification v5.2. These chipsets have the following controller 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 WCN6750, WCN6856, and QCA6698AQ connectivity chipsets: | Feature | WCN6750 | WCN6856 | QCA6698AQ | | --- | :---: | :---: | :---: | | Bluetooth Low Energy secure connections | ✓ | ✓ | ✓ | | Bluetooth Low Energy privacy 1.2 | ✓ | ✓ | ✓ | | Bluetooth 5.2 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 | ✕ | ✓ | ✓ | ## BlueZ stack Source: [https://docs.qualcomm.com/doc/80-70015-13/topic/bt_ft_overview.html](https://docs.qualcomm.com/doc/80-70015-13/topic/bt_ft_overview.html) BlueZ is a Bluetooth Linux stack that supports the core Bluetooth layers and protocols. BlueZ features are as follows: - Complies with Bluetooth Core specification v5.2 - Supports multiple Bluetooth devices - Implements a socket interface for all layers - Supports multithreaded data processing ## Bluetooth profiles and roles Source: [https://docs.qualcomm.com/doc/80-70015-13/topic/bt_ft_overview.html](https://docs.qualcomm.com/doc/80-70015-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. The BlueZ stack supports the following Bluetooth profiles and roles for connectivity chipsets: | Profile | Role | Version | Support on chipset | Support on chipset | | --- | --- | --- | --- | --- | | Profile | Role | Version | WCN6750/WCN6856 | QCA6698AQ | | General Access Profile (GAP) | Master and slave | | ✓ | ✓ | | Serial Port Profile (SPP) | Client and server | v1.2 | ✓ | ✓ | | Human Interface Device (HID) over GATT Profile (HOGP) | Host | v1 | ✓ | ✓ | | General Attribute Profile (GATT) | Central and peripheral | | ✓ | ✓ | | Advanced Audio Distribution Profile (A2DP) | Source | Nonsplit v1.3 | ✓ | ✕ | | Advanced Audio Distribution Profile (A2DP) | Sink | Nonsplit v1.3 | ✓ | ✕ | | Audio/Video Remote Control Profile (AVRCP) | Target | v1.5 | ✓ | ✕ | | Audio/Video Remote Control Profile (AVRCP) | Controller | v1.5 | ✓ | ✕ | | Hands-Free Profile (HFP) | Audio gateway | Nonsplit v1.7 | ✓ | ✕ | | Hands-Free Profile (HFP) | Client | Nonsplit v1.7 | ✓ | ✕ | | Object Push Profile (OPP) | Client and server | v1.2 | ✓ | ✓ | | File Transfer Protocol (FTP) | Client and server | v1.2 | ✓ | ✓ | | Phone Book Access Profile (PBAP) | Client and server | v1.1 | ✓ | ✓ | | Message Access Profile (MAP) | Client and server | v1.2 | ✓ | ✓ | | | | | | | ### General Access Profile Source: [https://docs.qualcomm.com/doc/80-70015-13/topic/bt_ft_overview.html](https://docs.qualcomm.com/doc/80-70015-13/topic/bt_ft_overview.html) Bluetooth Low Energy 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 for 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 | | | Peripheral | | | Broadcaster | | | Observer | | ### Serial Port Profile Source: [https://docs.qualcomm.com/doc/80-70015-13/topic/bt_ft_overview.html](https://docs.qualcomm.com/doc/80-70015-13/topic/bt_ft_overview.html) 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 for interoperability between Bluetooth devices. ### General Attribute Profile Source: [https://docs.qualcomm.com/doc/80-70015-13/topic/bt_ft_overview.html](https://docs.qualcomm.com/doc/80-70015-13/topic/bt_ft_overview.html) 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. - Specifies how two Bluetooth Low Energy devices exchange data using 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 basic lookup table, with 16‑bit IDs assigned to each entry. ### Human Interface Device over GATT Profile Source: [https://docs.qualcomm.com/doc/80-70015-13/topic/bt_ft_overview.html](https://docs.qualcomm.com/doc/80-70015-13/topic/bt_ft_overview.html) HOGP defines how a Bluetooth Low Energy wireless communications device can support HID services over the Bluetooth Low Energy protocol stack using GATT. ### Advanced Audio Distribution Profile Source: [https://docs.qualcomm.com/doc/80-70015-13/topic/bt_ft_overview.html](https://docs.qualcomm.com/doc/80-70015-13/topic/bt_ft_overview.html) A2DP defines the requirements to transmit or stream high-quality audio from one device to another over a Bluetooth connection. For example, streaming music from a mobile phone, laptop, or desktop to a wireless headset, and streaming audio to a hearing aid, cochlear implant, or car console. A2DP supports the following roles: | Profile role | Description | | --- | --- | | Source | | | Sink | | ### Hands-Free Profile Source: [https://docs.qualcomm.com/doc/80-70015-13/topic/bt_ft_overview.html](https://docs.qualcomm.com/doc/80-70015-13/topic/bt_ft_overview.html) HFP defines how an audio gateway device can connect to a hands-free device for functions like remote control and audio connection. HFP defines and assigns the following profile roles to the devices: | Profile role | Description | | --- | --- | | Client | | | Audio gateway | | ### Object Push Profile Source: [https://docs.qualcomm.com/doc/80-70015-13/topic/bt_ft_overview.html](https://docs.qualcomm.com/doc/80-70015-13/topic/bt_ft_overview.html) OPP defines how two Bluetooth devices can exchange objects, such as business cards, images, wallpapers, ringtones, or videos. It enables a Bluetooth device to: - Pull an object from another Bluetooth device. - Push an object to another Bluetooth device. - Exchange objects with another Bluetooth device. OPP supports client and server roles. ### File Transfer Protocol Source: [https://docs.qualcomm.com/doc/80-70015-13/topic/bt_ft_overview.html](https://docs.qualcomm.com/doc/80-70015-13/topic/bt_ft_overview.html) FTP defines the requirements to exchange files between two Bluetooth devices. FTP supports client and server roles. It enables a Bluetooth device to: - Browse the files and folders of another Bluetooth device. - Exchange files and folders with another Bluetooth device. - Create or delete files and folders on another Bluetooth device. ### Phone Book Access Profile Source: [https://docs.qualcomm.com/doc/80-70015-13/topic/bt_ft_overview.html](https://docs.qualcomm.com/doc/80-70015-13/topic/bt_ft_overview.html) PBAP is a Bluetooth profile that enables exchange of phone book objects between a remote and a local device. It is based on a client-server interaction model where the client device gets the phone book objects from the server device. In the BlueZ stack, PBAP supports the following roles: - Phone book server equipment (PSE): Contains the source phone book objects. - Phone book client equipment (PCE): Retrieves phone book objects from the PSE. The types of phone book objects include: | Phone book object | Description | | --- | --- | | Main phone book | Phone book of the device, such as a mobile phone. | | Incoming call history | List of most recently received calls. | | Outgoing call history | List of most recently made calls. | | Missed call history | List of most recently missed calls. | | Combined call history | List of most recently received, made, or missed calls. | | Speed-dial contacts | List of speed dial entries on the PSE. | | Favorite contacts | List of favorite contacts on the PSE. | PBAP enables the following functions: - Download contacts and call histories from a remote device. - Browse contacts on a remote device. - Select a phone book object. ### Message Access Profile Source: [https://docs.qualcomm.com/doc/80-70015-13/topic/bt_ft_overview.html](https://docs.qualcomm.com/doc/80-70015-13/topic/bt_ft_overview.html) MAP defines the features and procedures that devices use to exchange message objects. It is based on a client-server interaction model where the client initiates the transactions. The types of message objects include electronic messages (Email) and short message service (SMS). MAP combines the messaging capabilities of a messaging server device and the user interface capabilities of a client device to notify, browse, read, delete, generate, and send messages. In the BlueZ stack, MAP supports the following device roles: - Message server equipment (MSE): Provides the message repository engine. - Message client equipment (MCE): Uses the message repository engine of the MSE for MAP functions. Last Published: Oct 14, 2024 [Previous Topic Getting started](https://docs.qualcomm.com/bundle/publicresource/80-70015-13/topics/get-started.md) [Next Topic Architecture](https://docs.qualcomm.com/bundle/publicresource/80-70015-13/topics/bt_architecture_overview.md)