Bluetooth GATT Descriptor Reference
Report Reference (0x2908)
Mapping information in the form of a Report ID and Report Type which maps the current parent characteristic to the Report ID(s) and Report Type (s) defined within the Report Map characteristic.
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 | Report Reference |
| UUID | 0x2908 |
| Type | org.bluetooth.descriptor.report_reference |
| XML Root | Descriptor |
| Source File | org.bluetooth.descriptor.report_reference.xml |
| Field Count | 2 |
Field Specification
Parsed field definitions from the source XML value structure.
| Field | Requirement | Format | Unit | Exponent | Notes |
|---|---|---|---|---|---|
| Report ID | Mandatory | uint8 | - | - | - |
| Report Type | Mandatory | uint8 | - | - | - |
Byte Layout and Decode
Payload length is 2 bytes.
function decodePayload(dataView, offset = 0) {
const report_id = dataView.getUint8(offset + 0);
const report_type = dataView.getUint8(offset + 1);
return { report_id, report_type };
}
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 Report Reference in Bluetooth GATT?
Report Reference is defined as a Bluetooth GATT descriptor entry with type org.bluetooth.descriptor.report_reference and UUID 0x2908.
What UUID identifies Report Reference?
The UUID for Report Reference is 0x2908.
How should I parse Report Reference?
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.