Bluetooth Profiles and Use Cases

Bluetooth Profiles and Their Functional Scope

A Bluetooth radio in two devices makes a radio connection possible, but the connection alone does not define the meaning of the exchanged data. The devices need shared roles, procedures, and data formats. This is where Bluetooth Profiles come in. A Bluetooth Profile provides that shared set of rules. It is an explicitly defined collection of procedures and protocols that describes how two devices cooperate on a task such as streaming music, making a phone call, or controlling a computer mouse.

A profile can be viewed as a slice through the complex Bluetooth protocol stack. The lower layers establish the radio link, provide transport, and manage the flow of data. The profile connects those mechanisms with behavior required by an application. It specifies which procedures and protocols are used, which commands are available, and how devices format data for the particular function.

Standard profiles support Bluetooth interoperability for a specified service and use case. For example, Sony headphones, a Google smartphone, and a Ford car can cooperate for hands-free calls or music playback when they implement the required profile and compatible procedure versions. Without profiles, each manufacturer would need a separate data format and command set for every device, increasing the risk of incompatibility. When two devices claim to support a function such as "Advanced Audio," the profile gives that claim a defined meaning and describes the behavior expected on both sides of the connection.

Bluetooth Classic and LE Profile Families

Bluetooth includes two radio systems: Bluetooth Classic, also called BR/EDR, and Bluetooth Low Energy, or LE. They have different controllers, procedures, and profile families because they support different communication models. A device operating only with a Classic profile does not implement a profile intended only for LE merely by establishing a radio connection. Dual-mode devices, common in smartphones, support both systems and can separately connect to Classic and LE devices. Compatibility therefore depends on the supported system, profile, and roles at both ends.

Selected Bluetooth Classic Profiles

These profiles defined many of the most common Bluetooth Classic use cases and are still used in audio, telephony, and input devices.

A2DP: Stereo Audio Distribution

The Advanced Audio Distribution Profile (A2DP) defines interoperability requirements and procedures for one-way stereo audio distribution from a source to a sink. Playback quality also depends on the selected codec, stream parameters, and device implementations.

• Purpose: Streaming music, podcasts, and other stereo audio.
• Roles: It defines two roles. The Source is the device that sends the audio (e.g., a smartphone, laptop, or MP3 player). The Sinkis the device that receives and plays the audio (e.g., wireless headphones, a portable speaker, or a car's stereo system).
• Mechanism: A2DP takes the digital audio stream from the Source, compresses it using an audio codec to limit its bit rate, and transmits it over the packet-based ACL (Asynchronous Connection-Less) transport. In the applicable A2DP profile version, SBC is the required baseline codec. Devices may also support optional codecs such as AAC, aptX, or LDAC, but their availability, parameters, and effect on playback depend on compatible implementations at both ends.

AVRCP: Media Playback Control

The Audio/Video Remote Control Profile (AVRCP) often works together with A2DP. It provides a standard way to control media playback on the source device while A2DP carries the audio stream.

• Purpose: Sending playback commands.
• Functionality:When you press pause on your headphones or select "skip track" in a car's infotainment system, AVRCP carries the command to the source device. Later profile versions also support metadata exchange, allowing the current song and artist to appear on a car's dashboard or in a headphone companion app.
• Roles: The device sending the commands is the Controller (e.g., the headphones). The device receiving and acting on the commands is the Target (e.g., the smartphone).

HFP and HSP: Voice Call Profiles

The Hands-Free Profile (HFP) and its older, simpler predecessor, the Headset Profile (HSP), are designed for two-way voice communication.

• Purpose: Enabling hands-free phone calls through wireless headsets and car kits.
• Mechanism: These profiles use synchronous voice transports such as SCO or eSCO to provide a channel intended for real-time voice data. HFP is the newer profile and provides functions beyond the simpler HSP, including redialing, call waiting, and voice dialing.

HID: Input Devices

The Human Interface Device (HID) Profile is a Bluetooth standard for wireless input devices. It is based on the USB HID specification, so an operating system can use a familiar report model and device interface.

• Purpose: Connecting wireless peripherals like keyboards, mice, gamepads, presentation remotes, and joysticks.
• Mechanism:It standardizes how input data is reported to a host device. For example, a report can describe that the "G" key was pressed or that the mouse cursor moved 20 pixels to the left and 5 pixels down. Compatibility still depends on HID support and the correct report descriptor at the computer, but the shared format removes the need for a separate protocol for each keyboard.

Selected Bluetooth Low Energy Profiles and GATT Services

Classic Bluetooth profiles refer to procedures for a particular use model, while LE profiles often use the common GATT framework. A "GATT-based profile" is a standardized definition of one or more GATT Services and their Characteristics to fulfill a specific use case. This modular structure makes it easier to reuse services and combine functions in one device.

HRP: Heart Rate Profile

The Heart Rate Profile (HRP) defines how a heart rate sensor provides data to a Collector. An implementation uses the standard Heart Rate Service, where the Heart Rate Measurement characteristic is required. The measurement provides the beats-per-minute value, while fields such as sensor contact status and energy expended data are present according to flags and supported features.

PXP: Proximity Profile

The Proximity Profile (PXP) monitors proximity between two devices. It can support simple "find me" applications, including item finders attached to keys or a wallet. It uses the Link Loss Service to trigger an alert when the connection breaks and may use the Immediate Alert Serviceto request an alert on the peer device. An item finder is an example of the profile's use, not its complete normative scope.

BAS: Battery Service

The Battery Service (BAS) defines a standard way for a device to report battery level. Its basic characteristic is Battery Level, which exposes a value from 0 to 100 representing the remaining battery percentage. BAS 1.1 also adds characteristics for battery status, health, and identifying information, so the single-characteristic description applies to the basic service variant. A heart rate monitor may implement both HRP and BAS so a connected app can display the heart rate and the sensor's battery status.

HOGP: HID over GATT

The HID over GATT Profile (HOGP) is the Bluetooth Low Energy counterpart of the classic HID profile. It enables keyboards, mice, and other wireless input devices to use the power-efficient LE radio. HOGP 1.2 specifies HID services over GATT and LE Isochronous Channels. Operation for many months or years can result from a particular connection interval, report rate, and current budget; it is an implementation result rather than a guarantee of the profile. HOGP maps traditional HID data reports into the GATT service and characteristic structure.