Bluetooth GATT Service Reference
Transport Discovery (0x1824)
The Transport Discovery Service (TDS) enables a device using Bluetooth low energy wireless technology to expose services that are available on a transport other than Bluetooth low energy.
Quick Summary
No fixed value payload is declared in this XML; this entry defines metadata and profile structure. 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 | Transport Discovery |
| UUID | 0x1824 |
| Type | org.bluetooth.service.transport_discovery |
| XML Root | Service |
| Source File | org.bluetooth.service.transport_discovery.xml |
| Field Count | 0 |
Characteristic List
Characteristics declared by this service profile entry.
| Characteristic | Type | Requirement | Properties |
|---|---|---|---|
| TDS Control Point | org.bluetooth.characteristic.tds_control_point | Optional | Write, Indicate |
Use Cases and Integration Notes
Service Discovery
Use this definition to validate discovered services and expected characteristics during BLE onboarding.
Profile Compliance
Cross-check required characteristics and properties for conformance and QA automation.
App Capability Gating
Drive feature availability in apps based on whether service-level requirements are present.
Implementation Checklist
- Validate the service UUID during discovery before reading characteristic metadata.
- Ensure mandatory characteristics exist and expose expected properties.
- Map declaration data to app feature flags before attempting writes/subscriptions.
- Record mismatches between firmware tables and expected profile definitions in logs.
Dependencies
- This service has no dependencies on other GATT-based services.
FAQ
What is Transport Discovery in Bluetooth GATT?
Transport Discovery is defined as a Bluetooth GATT service entry with type org.bluetooth.service.transport_discovery and UUID 0x1824.
What UUID identifies Transport Discovery?
The UUID for Transport Discovery is 0x1824.
How should I parse Transport Discovery?
Parse the structure and requirements from the XML definition, then enforce format/requirement rules in your BLE stack.
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.