Bluetooth GATT Descriptor Reference
Client Characteristic Configuration (0x2902)
This descriptor shall be persistent across connections for bonded devices. The Client Characteristic Configuration descriptor is unique for each client. A client may read and write this descriptor to determine and set the configuration for that client. Authentication and authorization may be required by the server to write this descriptor. The default value for the Client Characteristic Configuration descriptor is 0x00. Upon connection of non-binded clients, this descriptor is set to the default value.
Quick Summary
Payload length is 2 bytes. This page is generated from official GATT XML and presented as implementation-ready guidance.
At a Glance
Key reference details for BLE implementation, interoperability testing, and AI-assisted troubleshooting.
| Property | Value |
|---|---|
| Name | Client Characteristic Configuration |
| UUID | 0x2902 |
| Type | org.bluetooth.descriptor.gatt.client_characteristic_configuration |
| XML Root | Descriptor |
| Source File | org.bluetooth.descriptor.gatt.client_characteristic_configuration.xml |
| Field Count | 1 |
Field Specification
Parsed field definitions from the source XML value structure.
| Field | Requirement | Format | Unit | Exponent | Notes |
|---|---|---|---|---|---|
| Properties | Mandatory | 16bit | - | - | - |
Bit Map
Bit-level enumerations extracted from the XML BitField definition.
| Field | Bit | Size | Name | 0 Means | 1 Means |
|---|---|---|---|---|---|
| Properties | 0 | 1 | Bit | Notifications disabled | Notifications enabled |
| Properties | 1 | 1 | Bit | Indications disabled | Indications enabled |
Byte Layout and Decode
Payload length is 2 bytes.
function decodePayload(dataView, offset = 0) {
// Parse properties (16bit) according to Bluetooth format rules.
return { properties };
}
Use Cases and Integration Notes
Descriptor Validation
Verify descriptor presence and format during integration and interoperability testing.
Client Configuration
Use descriptor semantics to configure notifications, indications, or presentation metadata.
Debug Diagnostics
Capture descriptor values alongside characteristic data for deeper BLE troubleshooting.
Implementation Checklist
- Read descriptor metadata after characteristic discovery to confirm behavior contracts.
- Respect descriptor read/write requirements before ATT operations.
- Document descriptor values in exported BLE session logs for reproducibility.
- Keep descriptor handling aligned with Bluetooth SIG format definitions.
FAQ
What is Client Characteristic Configuration in Bluetooth GATT?
Client Characteristic Configuration is defined as a Bluetooth GATT descriptor entry with type org.bluetooth.descriptor.gatt.client_characteristic_configuration and UUID 0x2902.
What UUID identifies Client Characteristic Configuration?
The UUID for Client Characteristic Configuration is 0x2902.
How should I parse Client Characteristic Configuration?
Payload length is 2 bytes.
Where does this definition come from?
This page is generated from the Bluetooth SIG mirror XML in the oesmith/gatt-xml repository.
How does this page support BLE implementation?
The page combines structured tables, practical Q&A, and JSON-LD metadata to help teams validate integrations and troubleshoot consistently.