Bluetooth GATT Descriptor Reference
Server Characteristic Configuration (0x2903)
Only one Server Characteristic Configuration descriptor exists in a characteristic definition. A client may write this configuration descriptor to control the configuration of the characteristic on the server for all clients. There is a single instantiation of this descriptor for all clients. Authentication and authorization may be required by the server to write this descriptor.
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 | Server Characteristic Configuration |
| UUID | 0x2903 |
| Type | org.bluetooth.descriptor.gatt.server_characteristic_configuration |
| XML Root | Descriptor |
| Source File | org.bluetooth.descriptor.gatt.server_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 | uint16 | - | - | - |
Bit Map
Bit-level enumerations extracted from the XML BitField definition.
| Field | Bit | Size | Name | 0 Means | 1 Means |
|---|---|---|---|---|---|
| Properties | 0 | 1 | Bit | Broadcasts disabled | Broadcasts enabled |
Byte Layout and Decode
Payload length is 2 bytes.
function decodePayload(dataView, offset = 0) {
const properties = dataView.getUint16(offset + 0, true);
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 Server Characteristic Configuration in Bluetooth GATT?
Server Characteristic Configuration is defined as a Bluetooth GATT descriptor entry with type org.bluetooth.descriptor.gatt.server_characteristic_configuration and UUID 0x2903.
What UUID identifies Server Characteristic Configuration?
The UUID for Server Characteristic Configuration is 0x2903.
How should I parse Server 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.