Bluetooth GATT Service Reference
Running Speed and Cadence (0x1814)
The Running Speed and Cadence (RSC) Service exposes speed, cadence and other data related to fitness applications such as the stride length and the total distance the user has traveled while using the Speed and Cadence Sensor (Server).
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 | Running Speed and Cadence |
| UUID | 0x1814 |
| Type | org.bluetooth.service.running_speed_and_cadence |
| XML Root | Service |
| Source File | org.bluetooth.service.running_speed_and_cadence.xml |
| Field Count | 0 |
Characteristic List
Characteristics declared by this service profile entry.
| Characteristic | Type | Requirement | Properties |
|---|---|---|---|
| RSC Measurement | org.bluetooth.characteristic.rsc_measurement | Mandatory | Notify |
| RSC Feature | org.bluetooth.characteristic.rsc_feature | Mandatory | Read |
| Sensor Location | org.bluetooth.characteristic.sensor_location | C1 | Read |
| SC Control Point | org.bluetooth.characteristic.sc_control_point | C2 | 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 Running Speed and Cadence in Bluetooth GATT?
Running Speed and Cadence is defined as a Bluetooth GATT service entry with type org.bluetooth.service.running_speed_and_cadence and UUID 0x1814.
What UUID identifies Running Speed and Cadence?
The UUID for Running Speed and Cadence is 0x1814.
How should I parse Running Speed and Cadence?
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.