Bluetooth GATT Service Reference
Heart Rate (0x180D)
The HEART RATE Service exposes heart rate and other data related to a heart rate sensor intended for fitness applications.
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 | Heart Rate |
| UUID | 0x180D |
| Type | org.bluetooth.service.heart_rate |
| XML Root | Service |
| Source File | org.bluetooth.service.heart_rate.xml |
| Field Count | 0 |
Characteristic List
Characteristics declared by this service profile entry.
| Characteristic | Type | Requirement | Properties |
|---|---|---|---|
| Heart Rate Measurement | org.bluetooth.characteristic.heart_rate_measurement | Mandatory | Notify |
| Body Sensor Location | org.bluetooth.characteristic.body_sensor_location | Optional | Read |
| Heart Rate Control Point | org.bluetooth.characteristic.heart_rate_control_point | Conditional | Write |
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 is not dependent upon any other services.
FAQ
What is Heart Rate in Bluetooth GATT?
Heart Rate is defined as a Bluetooth GATT service entry with type org.bluetooth.service.heart_rate and UUID 0x180D.
What UUID identifies Heart Rate?
The UUID for Heart Rate is 0x180D.
How should I parse Heart Rate?
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.