Bluetooth GATT Service Reference
Cycling Power (0x1818)
The Cycling Power (CP) Service exposes power- and force-related data and optionally speed- and cadence-related data from a Cycling Power sensor (Server) intended for sports and 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 | Cycling Power |
| UUID | 0x1818 |
| Type | org.bluetooth.service.cycling_power |
| XML Root | Service |
| Source File | org.bluetooth.service.cycling_power.xml |
| Field Count | 0 |
Characteristic List
Characteristics declared by this service profile entry.
| Characteristic | Type | Requirement | Properties |
|---|---|---|---|
| Cycling Power Measurement | org.bluetooth.characteristic.cycling_power_measurement | Mandatory | Notify, Broadcast |
| Cycling Power Feature | org.bluetooth.characteristic.cycling_power_feature | Mandatory | Read |
| Sensor Location | org.bluetooth.characteristic.sensor_location | Mandatory | Read |
| Cycling Power Vector | org.bluetooth.characteristic.cycling_power_vector | Optional | Notify |
| Cycling Power Control Point | org.bluetooth.characteristic.cycling_power_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 Cycling Power in Bluetooth GATT?
Cycling Power is defined as a Bluetooth GATT service entry with type org.bluetooth.service.cycling_power and UUID 0x1818.
What UUID identifies Cycling Power?
The UUID for Cycling Power is 0x1818.
How should I parse Cycling Power?
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.