From 4fd2ede1d3da9365fdc6dec89290c346581a03f9 Mon Sep 17 00:00:00 2001 From: Olly Smith Date: Tue, 11 Apr 2017 07:08:14 +0100 Subject: [PATCH] Initial import. - Files mirrored from https://www.bluetooth.com/specifications/gatt - Pretty-printed for easier reading in a terminal --- ...ribute.gatt.characteristic_declaration.xml | 74 + ...oth.attribute.gatt.include_declaration.xml | 21 + ...ibute.gatt.primary_service_declaration.xml | 13 + ...ute.gatt.secondary_service_declaration.xml | 13 + ...haracteristic.Magnetic_flux_density_2D.xml | 37 + ...haracteristic.Magnetic_flux_density_3D.xml | 51 + ...eristic.aerobic_heart_rate_lower_limit.xml | 22 + ...eristic.aerobic_heart_rate_upper_limit.xml | 22 + ...tooth.characteristic.aerobic_threshold.xml | 28 + org.bluetooth.characteristic.age.xml | 17 + org.bluetooth.characteristic.aggregate.xml | 29 + ...tooth.characteristic.alert_category_id.xml | 49 + ...racteristic.alert_category_id_bit_mask.xml | 100 ++ org.bluetooth.characteristic.alert_level.xml | 37 + ...istic.alert_notification_control_point.xml | 55 + org.bluetooth.characteristic.alert_status.xml | 56 + org.bluetooth.characteristic.altitude.xml | 17 + ...istic.anaerobic_heart_rate_lower_limit.xml | 22 + ...istic.anaerobic_heart_rate_upper_limit.xml | 22 + ...oth.characteristic.anaerobic_threshold.xml | 28 + org.bluetooth.characteristic.analog.xml | 22 + ...characteristic.apparent_wind_direction.xml | 31 + ...oth.characteristic.apparent_wind_speed.xml | 18 + ...aracteristic.barometric_pressure_trend.xml | 31 + ...bluetooth.characteristic.battery_level.xml | 25 + ....characteristic.blood_pressure_feature.xml | 75 + ...racteristic.blood_pressure_measurement.xml | 209 +++ ...haracteristic.body_composition_feature.xml | 117 ++ ...cteristic.body_composition_measurement.xml | 280 +++ ...th.characteristic.body_sensor_location.xml | 24 + ...teristic.bond_management_control_point.xml | 97 + ...characteristic.bond_management_feature.xml | 174 ++ ...racteristic.boot_keyboard_input_report.xml | 21 + ...acteristic.boot_keyboard_output_report.xml | 21 + ...characteristic.boot_mouse_input_report.xml | 21 + org.bluetooth.characteristic.cgm_feature.xml | 189 ++ ...uetooth.characteristic.cgm_measurement.xml | 300 ++++ ...th.characteristic.cgm_session_run_time.xml | 35 + ....characteristic.cgm_session_start_time.xml | 44 + ...eristic.cgm_specific_ops_control_point.xml | 260 +++ org.bluetooth.characteristic.cgm_status.xml | 48 + ...ooth.characteristic.cross_trainer_data.xml | 272 +++ org.bluetooth.characteristic.csc_feature.xml | 42 + ...uetooth.characteristic.csc_measurement.xml | 75 + org.bluetooth.characteristic.current_time.xml | 52 + ...acteristic.cycling_power_control_point.xml | 117 ++ ...h.characteristic.cycling_power_feature.xml | 177 ++ ...aracteristic.cycling_power_measurement.xml | 320 ++++ ...th.characteristic.cycling_power_vector.xml | 137 ++ ...aracteristic.database_change_increment.xml | 14 + ...bluetooth.characteristic.date_of_birth.xml | 63 + ...cteristic.date_of_threshold_assessment.xml | 63 + org.bluetooth.characteristic.date_time.xml | 95 + ...bluetooth.characteristic.day_date_time.xml | 22 + org.bluetooth.characteristic.day_of_week.xml | 29 + ...haracteristic.descriptor_value_changed.xml | 11 + org.bluetooth.characteristic.dew_point.xml | 18 + org.bluetooth.characteristic.digital.xml | 31 + org.bluetooth.characteristic.dst_offset.xml | 30 + org.bluetooth.characteristic.elevation.xml | 17 + ...bluetooth.characteristic.email_address.xml | 23 + ...luetooth.characteristic.exact_time_256.xml | 27 + ...ristic.fat_burn_heart_rate_lower_limit.xml | 22 + ...ristic.fat_burn_heart_rate_upper_limit.xml | 22 + ...haracteristic.firmware_revision_string.xml | 19 + org.bluetooth.characteristic.first_name.xml | 22 + ...teristic.fitness_machine_control_point.xml | 12 + ...characteristic.fitness_machine_feature.xml | 12 + ....characteristic.fitness_machine_status.xml | 12 + ...acteristic.five_zone_heart_rate_limits.xml | 56 + org.bluetooth.characteristic.floor_number.xml | 17 + ...luetooth.characteristic.gap.appearance.xml | 147 ++ ...gap.central_address_resolution_support.xml | 38 + ...uetooth.characteristic.gap.device_name.xml | 20 + ...pheral_preferred_connection_parameters.xml | 55 + ...acteristic.gap.peripheral_privacy_flag.xml | 26 + ...haracteristic.gap.reconnection_address.xml | 21 + ...th.characteristic.gatt.service_changed.xml | 28 + org.bluetooth.characteristic.gender.xml | 24 + ...uetooth.characteristic.glucose_feature.xml | 99 ++ ...oth.characteristic.glucose_measurement.xml | 247 +++ ...acteristic.glucose_measurement_context.xml | 236 +++ org.bluetooth.characteristic.gust_factor.xml | 19 + ...haracteristic.hardware_revision_string.xml | 19 + ...haracteristic.heart_rate_control_point.xml | 20 + ...luetooth.characteristic.heart_rate_max.xml | 21 + ....characteristic.heart_rate_measurement.xml | 106 ++ org.bluetooth.characteristic.heat_index.xml | 18 + org.bluetooth.characteristic.height.xml | 20 + ...tooth.characteristic.hid_control_point.xml | 29 + ...uetooth.characteristic.hid_information.xml | 58 + ...tooth.characteristic.hip_circumference.xml | 22 + ...ooth.characteristic.http_control_point.xml | 57 + ...etooth.characteristic.http_entity_body.xml | 21 + org.bluetooth.characteristic.http_headers.xml | 22 + ...etooth.characteristic.http_status_code.xml | 60 + ...luetooth.characteristic.https_security.xml | 25 + org.bluetooth.characteristic.humidity.xml | 17 + ...etooth.characteristic.indoor_bike_data.xml | 219 +++ ...istic.indoor_positioning_configuration.xml | 68 + ...racteristic.intermediate_cuff_pressure.xml | 21 + ...haracteristic.intermediate_temperature.xml | 21 + org.bluetooth.characteristic.irradiance.xml | 18 + org.bluetooth.characteristic.language.xml | 16 + org.bluetooth.characteristic.last_name.xml | 22 + org.bluetooth.characteristic.latitude.xml | 17 + ...etooth.characteristic.ln_control_point.xml | 99 ++ org.bluetooth.characteristic.ln_feature.xml | 167 ++ ...h.characteristic.local_east_coordinate.xml | 19 + ....characteristic.local_north_coordinate.xml | 19 + ....characteristic.local_time_information.xml | 22 + ...ooth.characteristic.location_and_speed.xml | 169 ++ ...bluetooth.characteristic.location_name.xml | 17 + org.bluetooth.characteristic.longitude.xml | 17 + ...th.characteristic.magnetic_declination.xml | 24 + ...haracteristic.manufacturer_name_string.xml | 19 + ...eristic.maximum_recommended_heart_rate.xml | 24 + ...th.characteristic.measurement_interval.xml | 26 + ...oth.characteristic.model_number_string.xml | 20 + org.bluetooth.characteristic.navigation.xml | 120 ++ org.bluetooth.characteristic.new_alert.xml | 66 + ...acteristic.object_action_control_point.xml | 11 + ...luetooth.characteristic.object_changed.xml | 11 + ...th.characteristic.object_first_created.xml | 20 + org.bluetooth.characteristic.object_id.xml | 25 + ...th.characteristic.object_last_modified.xml | 20 + ...aracteristic.object_list_control_point.xml | 11 + ...ooth.characteristic.object_list_filter.xml | 11 + org.bluetooth.characteristic.object_name.xml | 31 + ...tooth.characteristic.object_properties.xml | 10 + org.bluetooth.characteristic.object_size.xml | 24 + org.bluetooth.characteristic.object_type.xml | 32 + org.bluetooth.characteristic.ots_feature.xml | 10 + ...racteristic.plx_continuous_measurement.xml | 319 ++++ org.bluetooth.characteristic.plx_features.xml | 288 +++ ...racteristic.plx_spot_check_measurement.xml | 275 +++ org.bluetooth.characteristic.pnp_id.xml | 56 + ...th.characteristic.pollen_concentration.xml | 19 + ...etooth.characteristic.position_quality.xml | 142 ++ org.bluetooth.characteristic.pressure.xml | 17 + ...bluetooth.characteristic.protocol_mode.xml | 24 + org.bluetooth.characteristic.rainfall.xml | 17 + ...acteristic.record_access_control_point.xml | 110 ++ ...racteristic.reference_time_information.xml | 45 + org.bluetooth.characteristic.report.xml | 21 + org.bluetooth.characteristic.report_map.xml | 25 + ...ristic.resolvable_private_address_only.xml | 30 + ...ooth.characteristic.resting_heart_rate.xml | 21 + ...th.characteristic.ringer_control_point.xml | 34 + ...luetooth.characteristic.ringer_setting.xml | 30 + org.bluetooth.characteristic.rower_data.xml | 220 +++ org.bluetooth.characteristic.rsc_feature.xml | 56 + ...uetooth.characteristic.rsc_measurement.xml | 87 + ...etooth.characteristic.sc_control_point.xml | 102 ++ ...th.characteristic.scan_interval_window.xml | 31 + org.bluetooth.characteristic.scan_refresh.xml | 24 + ...uetooth.characteristic.sensor_location.xml | 38 + ...th.characteristic.serial_number_string.xml | 19 + ...haracteristic.software_revision_string.xml | 19 + ...e_for_aerobic_and_anaerobic_thresholds.xml | 41 + ...ooth.characteristic.stair_climber_data.xml | 174 ++ ...tooth.characteristic.step_climber_data.xml | 168 ++ ...racteristic.supported_heart_rate_range.xml | 36 + ...acteristic.supported_inclination_range.xml | 39 + ...cteristic.supported_new_alert_category.xml | 27 + ...h.characteristic.supported_power_range.xml | 36 + ...istic.supported_resistance_level_range.xml | 40 + ...h.characteristic.supported_speed_range.xml | 39 + ...ristic.supported_unread_alert_category.xml | 28 + org.bluetooth.characteristic.system_id.xml | 57 + ...tooth.characteristic.tds_control_point.xml | 13 + org.bluetooth.characteristic.temperature.xml | 18 + ...characteristic.temperature_measurement.xml | 114 ++ ...etooth.characteristic.temperature_type.xml | 34 + ...cteristic.three_zone_heart_rate_limits.xml | 38 + ...bluetooth.characteristic.time_accuracy.xml | 26 + org.bluetooth.characteristic.time_source.xml | 26 + ...aracteristic.time_update_control_point.xml | 22 + ...tooth.characteristic.time_update_state.xml | 41 + ...bluetooth.characteristic.time_with_dst.xml | 22 + org.bluetooth.characteristic.time_zone.xml | 21 + ...uetooth.characteristic.training_status.xml | 12 + ...luetooth.characteristic.treadmill_data.xml | 242 +++ ...oth.characteristic.true_wind_direction.xml | 27 + ...uetooth.characteristic.true_wind_speed.xml | 18 + ...aracteristic.two_zone_heart_rate_limit.xml | 23 + ...luetooth.characteristic.tx_power_level.xml | 29 + org.bluetooth.characteristic.uncertainty.xml | 57 + ...oth.characteristic.unread_alert_status.xml | 40 + org.bluetooth.characteristic.uri.xml | 20 + ...ooth.characteristic.user_control_point.xml | 10 + org.bluetooth.characteristic.user_index.xml | 18 + org.bluetooth.characteristic.uv_index.xml | 15 + org.bluetooth.characteristic.vo2_max.xml | 19 + ...oth.characteristic.waist_circumference.xml | 22 + org.bluetooth.characteristic.weight.xml | 21 + ...ooth.characteristic.weight_measurement.xml | 115 ++ ...th.characteristic.weight_scale_feature.xml | 69 + org.bluetooth.characteristic.wind_chill.xml | 18 + org.bluetooth.descriptor.es_configuration.xml | 12 + org.bluetooth.descriptor.es_measurement.xml | 11 + ...luetooth.descriptor.es_trigger_setting.xml | 10 + ...h.descriptor.external_report_reference.xml | 23 + ...r.gatt.characteristic_aggregate_format.xml | 38 + ...att.characteristic_extended_properties.xml | 57 + ...att.characteristic_presentation_format.xml | 106 ++ ...r.gatt.characteristic_user_description.xml | 23 + ...tt.client_characteristic_configuration.xml | 58 + ...tt.server_characteristic_configuration.xml | 37 + ...luetooth.descriptor.number_of_digitals.xml | 19 + org.bluetooth.descriptor.report_reference.xml | 34 + ...etooth.descriptor.time_trigger_setting.xml | 52 + org.bluetooth.descriptor.valid_range.xml | 50 + ...tooth.descriptor.value_trigger_setting.xml | 60 + org.bluetooth.service.alert_notification.xml | 163 ++ org.bluetooth.service.automation_io.xml | 355 ++++ org.bluetooth.service.battery_service.xml | 76 + org.bluetooth.service.blood_pressure.xml | 111 ++ org.bluetooth.service.body_composition.xml | 76 + org.bluetooth.service.bond_management.xml | 82 + ....service.continuous_glucose_monitoring.xml | 222 +++ org.bluetooth.service.current_time.xml | 91 + org.bluetooth.service.cycling_power.xml | 167 ++ ...ooth.service.cycling_speed_and_cadence.xml | 159 ++ org.bluetooth.service.device_information.xml | 191 ++ ...luetooth.service.environmental_sensing.xml | 1581 +++++++++++++++++ org.bluetooth.service.fitness_machine.xml | 378 ++++ org.bluetooth.service.generic_access.xml | 104 ++ org.bluetooth.service.generic_attribute.xml | 25 + org.bluetooth.service.glucose.xml | 151 ++ org.bluetooth.service.health_thermometer.xml | 164 ++ org.bluetooth.service.heart_rate.xml | 109 ++ org.bluetooth.service.http_proxy.xml | 141 ++ ...uetooth.service.human_interface_device.xml | 309 ++++ org.bluetooth.service.immediate_alert.xml | 60 + org.bluetooth.service.indoor_positioning.xml | 323 ++++ ...ooth.service.internet_protocol_support.xml | 26 + org.bluetooth.service.link_loss.xml | 62 + ...etooth.service.location_and_navigation.xml | 154 ++ org.bluetooth.service.next_dst_change.xml | 41 + org.bluetooth.service.object_transfer.xml | 311 ++++ org.bluetooth.service.phone_alert_status.xml | 136 ++ org.bluetooth.service.pulse_oximeter.xml | 143 ++ ...luetooth.service.reference_time_update.xml | 61 + ...ooth.service.running_speed_and_cadence.xml | 161 ++ org.bluetooth.service.scan_parameters.xml | 95 + org.bluetooth.service.transport_discovery.xml | 74 + org.bluetooth.service.tx_power.xml | 80 + org.bluetooth.service.user_data.xml | 693 ++++++++ org.bluetooth.service.weight_scale.xml | 75 + 250 files changed, 19149 insertions(+) create mode 100644 org.bluetooth.attribute.gatt.characteristic_declaration.xml create mode 100644 org.bluetooth.attribute.gatt.include_declaration.xml create mode 100644 org.bluetooth.attribute.gatt.primary_service_declaration.xml create mode 100644 org.bluetooth.attribute.gatt.secondary_service_declaration.xml create mode 100644 org.bluetooth.characteristic.Magnetic_flux_density_2D.xml create mode 100644 org.bluetooth.characteristic.Magnetic_flux_density_3D.xml create mode 100644 org.bluetooth.characteristic.aerobic_heart_rate_lower_limit.xml create mode 100644 org.bluetooth.characteristic.aerobic_heart_rate_upper_limit.xml create mode 100644 org.bluetooth.characteristic.aerobic_threshold.xml create mode 100644 org.bluetooth.characteristic.age.xml create mode 100644 org.bluetooth.characteristic.aggregate.xml create mode 100644 org.bluetooth.characteristic.alert_category_id.xml create mode 100644 org.bluetooth.characteristic.alert_category_id_bit_mask.xml create mode 100644 org.bluetooth.characteristic.alert_level.xml create mode 100644 org.bluetooth.characteristic.alert_notification_control_point.xml create mode 100644 org.bluetooth.characteristic.alert_status.xml create mode 100644 org.bluetooth.characteristic.altitude.xml create mode 100644 org.bluetooth.characteristic.anaerobic_heart_rate_lower_limit.xml create mode 100644 org.bluetooth.characteristic.anaerobic_heart_rate_upper_limit.xml create mode 100644 org.bluetooth.characteristic.anaerobic_threshold.xml create mode 100644 org.bluetooth.characteristic.analog.xml create mode 100644 org.bluetooth.characteristic.apparent_wind_direction.xml create mode 100644 org.bluetooth.characteristic.apparent_wind_speed.xml create mode 100644 org.bluetooth.characteristic.barometric_pressure_trend.xml create mode 100644 org.bluetooth.characteristic.battery_level.xml create mode 100644 org.bluetooth.characteristic.blood_pressure_feature.xml create mode 100644 org.bluetooth.characteristic.blood_pressure_measurement.xml create mode 100644 org.bluetooth.characteristic.body_composition_feature.xml create mode 100644 org.bluetooth.characteristic.body_composition_measurement.xml create mode 100644 org.bluetooth.characteristic.body_sensor_location.xml create mode 100644 org.bluetooth.characteristic.bond_management_control_point.xml create mode 100644 org.bluetooth.characteristic.bond_management_feature.xml create mode 100644 org.bluetooth.characteristic.boot_keyboard_input_report.xml create mode 100644 org.bluetooth.characteristic.boot_keyboard_output_report.xml create mode 100644 org.bluetooth.characteristic.boot_mouse_input_report.xml create mode 100644 org.bluetooth.characteristic.cgm_feature.xml create mode 100644 org.bluetooth.characteristic.cgm_measurement.xml create mode 100644 org.bluetooth.characteristic.cgm_session_run_time.xml create mode 100644 org.bluetooth.characteristic.cgm_session_start_time.xml create mode 100644 org.bluetooth.characteristic.cgm_specific_ops_control_point.xml create mode 100644 org.bluetooth.characteristic.cgm_status.xml create mode 100644 org.bluetooth.characteristic.cross_trainer_data.xml create mode 100644 org.bluetooth.characteristic.csc_feature.xml create mode 100644 org.bluetooth.characteristic.csc_measurement.xml create mode 100644 org.bluetooth.characteristic.current_time.xml create mode 100644 org.bluetooth.characteristic.cycling_power_control_point.xml create mode 100644 org.bluetooth.characteristic.cycling_power_feature.xml create mode 100644 org.bluetooth.characteristic.cycling_power_measurement.xml create mode 100644 org.bluetooth.characteristic.cycling_power_vector.xml create mode 100644 org.bluetooth.characteristic.database_change_increment.xml create mode 100644 org.bluetooth.characteristic.date_of_birth.xml create mode 100644 org.bluetooth.characteristic.date_of_threshold_assessment.xml create mode 100644 org.bluetooth.characteristic.date_time.xml create mode 100644 org.bluetooth.characteristic.day_date_time.xml create mode 100644 org.bluetooth.characteristic.day_of_week.xml create mode 100644 org.bluetooth.characteristic.descriptor_value_changed.xml create mode 100644 org.bluetooth.characteristic.dew_point.xml create mode 100644 org.bluetooth.characteristic.digital.xml create mode 100644 org.bluetooth.characteristic.dst_offset.xml create mode 100644 org.bluetooth.characteristic.elevation.xml create mode 100644 org.bluetooth.characteristic.email_address.xml create mode 100644 org.bluetooth.characteristic.exact_time_256.xml create mode 100644 org.bluetooth.characteristic.fat_burn_heart_rate_lower_limit.xml create mode 100644 org.bluetooth.characteristic.fat_burn_heart_rate_upper_limit.xml create mode 100644 org.bluetooth.characteristic.firmware_revision_string.xml create mode 100644 org.bluetooth.characteristic.first_name.xml create mode 100644 org.bluetooth.characteristic.fitness_machine_control_point.xml create mode 100644 org.bluetooth.characteristic.fitness_machine_feature.xml create mode 100644 org.bluetooth.characteristic.fitness_machine_status.xml create mode 100644 org.bluetooth.characteristic.five_zone_heart_rate_limits.xml create mode 100644 org.bluetooth.characteristic.floor_number.xml create mode 100644 org.bluetooth.characteristic.gap.appearance.xml create mode 100644 org.bluetooth.characteristic.gap.central_address_resolution_support.xml create mode 100644 org.bluetooth.characteristic.gap.device_name.xml create mode 100644 org.bluetooth.characteristic.gap.peripheral_preferred_connection_parameters.xml create mode 100644 org.bluetooth.characteristic.gap.peripheral_privacy_flag.xml create mode 100644 org.bluetooth.characteristic.gap.reconnection_address.xml create mode 100644 org.bluetooth.characteristic.gatt.service_changed.xml create mode 100644 org.bluetooth.characteristic.gender.xml create mode 100644 org.bluetooth.characteristic.glucose_feature.xml create mode 100644 org.bluetooth.characteristic.glucose_measurement.xml create mode 100644 org.bluetooth.characteristic.glucose_measurement_context.xml create mode 100644 org.bluetooth.characteristic.gust_factor.xml create mode 100644 org.bluetooth.characteristic.hardware_revision_string.xml create mode 100644 org.bluetooth.characteristic.heart_rate_control_point.xml create mode 100644 org.bluetooth.characteristic.heart_rate_max.xml create mode 100644 org.bluetooth.characteristic.heart_rate_measurement.xml create mode 100644 org.bluetooth.characteristic.heat_index.xml create mode 100644 org.bluetooth.characteristic.height.xml create mode 100644 org.bluetooth.characteristic.hid_control_point.xml create mode 100644 org.bluetooth.characteristic.hid_information.xml create mode 100644 org.bluetooth.characteristic.hip_circumference.xml create mode 100644 org.bluetooth.characteristic.http_control_point.xml create mode 100644 org.bluetooth.characteristic.http_entity_body.xml create mode 100644 org.bluetooth.characteristic.http_headers.xml create mode 100644 org.bluetooth.characteristic.http_status_code.xml create mode 100644 org.bluetooth.characteristic.https_security.xml create mode 100644 org.bluetooth.characteristic.humidity.xml create mode 100644 org.bluetooth.characteristic.indoor_bike_data.xml create mode 100644 org.bluetooth.characteristic.indoor_positioning_configuration.xml create mode 100644 org.bluetooth.characteristic.intermediate_cuff_pressure.xml create mode 100644 org.bluetooth.characteristic.intermediate_temperature.xml create mode 100644 org.bluetooth.characteristic.irradiance.xml create mode 100644 org.bluetooth.characteristic.language.xml create mode 100644 org.bluetooth.characteristic.last_name.xml create mode 100644 org.bluetooth.characteristic.latitude.xml create mode 100644 org.bluetooth.characteristic.ln_control_point.xml create mode 100644 org.bluetooth.characteristic.ln_feature.xml create mode 100644 org.bluetooth.characteristic.local_east_coordinate.xml create mode 100644 org.bluetooth.characteristic.local_north_coordinate.xml create mode 100644 org.bluetooth.characteristic.local_time_information.xml create mode 100644 org.bluetooth.characteristic.location_and_speed.xml create mode 100644 org.bluetooth.characteristic.location_name.xml create mode 100644 org.bluetooth.characteristic.longitude.xml create mode 100644 org.bluetooth.characteristic.magnetic_declination.xml create mode 100644 org.bluetooth.characteristic.manufacturer_name_string.xml create mode 100644 org.bluetooth.characteristic.maximum_recommended_heart_rate.xml create mode 100644 org.bluetooth.characteristic.measurement_interval.xml create mode 100644 org.bluetooth.characteristic.model_number_string.xml create mode 100644 org.bluetooth.characteristic.navigation.xml create mode 100644 org.bluetooth.characteristic.new_alert.xml create mode 100644 org.bluetooth.characteristic.object_action_control_point.xml create mode 100644 org.bluetooth.characteristic.object_changed.xml create mode 100644 org.bluetooth.characteristic.object_first_created.xml create mode 100644 org.bluetooth.characteristic.object_id.xml create mode 100644 org.bluetooth.characteristic.object_last_modified.xml create mode 100644 org.bluetooth.characteristic.object_list_control_point.xml create mode 100644 org.bluetooth.characteristic.object_list_filter.xml create mode 100644 org.bluetooth.characteristic.object_name.xml create mode 100644 org.bluetooth.characteristic.object_properties.xml create mode 100644 org.bluetooth.characteristic.object_size.xml create mode 100644 org.bluetooth.characteristic.object_type.xml create mode 100644 org.bluetooth.characteristic.ots_feature.xml create mode 100644 org.bluetooth.characteristic.plx_continuous_measurement.xml create mode 100644 org.bluetooth.characteristic.plx_features.xml create mode 100644 org.bluetooth.characteristic.plx_spot_check_measurement.xml create mode 100644 org.bluetooth.characteristic.pnp_id.xml create mode 100644 org.bluetooth.characteristic.pollen_concentration.xml create mode 100644 org.bluetooth.characteristic.position_quality.xml create mode 100644 org.bluetooth.characteristic.pressure.xml create mode 100644 org.bluetooth.characteristic.protocol_mode.xml create mode 100644 org.bluetooth.characteristic.rainfall.xml create mode 100644 org.bluetooth.characteristic.record_access_control_point.xml create mode 100644 org.bluetooth.characteristic.reference_time_information.xml create mode 100644 org.bluetooth.characteristic.report.xml create mode 100644 org.bluetooth.characteristic.report_map.xml create mode 100644 org.bluetooth.characteristic.resolvable_private_address_only.xml create mode 100644 org.bluetooth.characteristic.resting_heart_rate.xml create mode 100644 org.bluetooth.characteristic.ringer_control_point.xml create mode 100644 org.bluetooth.characteristic.ringer_setting.xml create mode 100644 org.bluetooth.characteristic.rower_data.xml create mode 100644 org.bluetooth.characteristic.rsc_feature.xml create mode 100644 org.bluetooth.characteristic.rsc_measurement.xml create mode 100644 org.bluetooth.characteristic.sc_control_point.xml create mode 100644 org.bluetooth.characteristic.scan_interval_window.xml create mode 100644 org.bluetooth.characteristic.scan_refresh.xml create mode 100644 org.bluetooth.characteristic.sensor_location.xml create mode 100644 org.bluetooth.characteristic.serial_number_string.xml create mode 100644 org.bluetooth.characteristic.software_revision_string.xml create mode 100644 org.bluetooth.characteristic.sport_type_for_aerobic_and_anaerobic_thresholds.xml create mode 100644 org.bluetooth.characteristic.stair_climber_data.xml create mode 100644 org.bluetooth.characteristic.step_climber_data.xml create mode 100644 org.bluetooth.characteristic.supported_heart_rate_range.xml create mode 100644 org.bluetooth.characteristic.supported_inclination_range.xml create mode 100644 org.bluetooth.characteristic.supported_new_alert_category.xml create mode 100644 org.bluetooth.characteristic.supported_power_range.xml create mode 100644 org.bluetooth.characteristic.supported_resistance_level_range.xml create mode 100644 org.bluetooth.characteristic.supported_speed_range.xml create mode 100644 org.bluetooth.characteristic.supported_unread_alert_category.xml create mode 100644 org.bluetooth.characteristic.system_id.xml create mode 100644 org.bluetooth.characteristic.tds_control_point.xml create mode 100644 org.bluetooth.characteristic.temperature.xml create mode 100644 org.bluetooth.characteristic.temperature_measurement.xml create mode 100644 org.bluetooth.characteristic.temperature_type.xml create mode 100644 org.bluetooth.characteristic.three_zone_heart_rate_limits.xml create mode 100644 org.bluetooth.characteristic.time_accuracy.xml create mode 100644 org.bluetooth.characteristic.time_source.xml create mode 100644 org.bluetooth.characteristic.time_update_control_point.xml create mode 100644 org.bluetooth.characteristic.time_update_state.xml create mode 100644 org.bluetooth.characteristic.time_with_dst.xml create mode 100644 org.bluetooth.characteristic.time_zone.xml create mode 100644 org.bluetooth.characteristic.training_status.xml create mode 100644 org.bluetooth.characteristic.treadmill_data.xml create mode 100644 org.bluetooth.characteristic.true_wind_direction.xml create mode 100644 org.bluetooth.characteristic.true_wind_speed.xml create mode 100644 org.bluetooth.characteristic.two_zone_heart_rate_limit.xml create mode 100644 org.bluetooth.characteristic.tx_power_level.xml create mode 100644 org.bluetooth.characteristic.uncertainty.xml create mode 100644 org.bluetooth.characteristic.unread_alert_status.xml create mode 100644 org.bluetooth.characteristic.uri.xml create mode 100644 org.bluetooth.characteristic.user_control_point.xml create mode 100644 org.bluetooth.characteristic.user_index.xml create mode 100644 org.bluetooth.characteristic.uv_index.xml create mode 100644 org.bluetooth.characteristic.vo2_max.xml create mode 100644 org.bluetooth.characteristic.waist_circumference.xml create mode 100644 org.bluetooth.characteristic.weight.xml create mode 100644 org.bluetooth.characteristic.weight_measurement.xml create mode 100644 org.bluetooth.characteristic.weight_scale_feature.xml create mode 100644 org.bluetooth.characteristic.wind_chill.xml create mode 100644 org.bluetooth.descriptor.es_configuration.xml create mode 100644 org.bluetooth.descriptor.es_measurement.xml create mode 100644 org.bluetooth.descriptor.es_trigger_setting.xml create mode 100644 org.bluetooth.descriptor.external_report_reference.xml create mode 100644 org.bluetooth.descriptor.gatt.characteristic_aggregate_format.xml create mode 100644 org.bluetooth.descriptor.gatt.characteristic_extended_properties.xml create mode 100644 org.bluetooth.descriptor.gatt.characteristic_presentation_format.xml create mode 100644 org.bluetooth.descriptor.gatt.characteristic_user_description.xml create mode 100644 org.bluetooth.descriptor.gatt.client_characteristic_configuration.xml create mode 100644 org.bluetooth.descriptor.gatt.server_characteristic_configuration.xml create mode 100644 org.bluetooth.descriptor.number_of_digitals.xml create mode 100644 org.bluetooth.descriptor.report_reference.xml create mode 100644 org.bluetooth.descriptor.time_trigger_setting.xml create mode 100644 org.bluetooth.descriptor.valid_range.xml create mode 100644 org.bluetooth.descriptor.value_trigger_setting.xml create mode 100644 org.bluetooth.service.alert_notification.xml create mode 100644 org.bluetooth.service.automation_io.xml create mode 100644 org.bluetooth.service.battery_service.xml create mode 100644 org.bluetooth.service.blood_pressure.xml create mode 100644 org.bluetooth.service.body_composition.xml create mode 100644 org.bluetooth.service.bond_management.xml create mode 100644 org.bluetooth.service.continuous_glucose_monitoring.xml create mode 100644 org.bluetooth.service.current_time.xml create mode 100644 org.bluetooth.service.cycling_power.xml create mode 100644 org.bluetooth.service.cycling_speed_and_cadence.xml create mode 100644 org.bluetooth.service.device_information.xml create mode 100644 org.bluetooth.service.environmental_sensing.xml create mode 100644 org.bluetooth.service.fitness_machine.xml create mode 100644 org.bluetooth.service.generic_access.xml create mode 100644 org.bluetooth.service.generic_attribute.xml create mode 100644 org.bluetooth.service.glucose.xml create mode 100644 org.bluetooth.service.health_thermometer.xml create mode 100644 org.bluetooth.service.heart_rate.xml create mode 100644 org.bluetooth.service.http_proxy.xml create mode 100644 org.bluetooth.service.human_interface_device.xml create mode 100644 org.bluetooth.service.immediate_alert.xml create mode 100644 org.bluetooth.service.indoor_positioning.xml create mode 100644 org.bluetooth.service.internet_protocol_support.xml create mode 100644 org.bluetooth.service.link_loss.xml create mode 100644 org.bluetooth.service.location_and_navigation.xml create mode 100644 org.bluetooth.service.next_dst_change.xml create mode 100644 org.bluetooth.service.object_transfer.xml create mode 100644 org.bluetooth.service.phone_alert_status.xml create mode 100644 org.bluetooth.service.pulse_oximeter.xml create mode 100644 org.bluetooth.service.reference_time_update.xml create mode 100644 org.bluetooth.service.running_speed_and_cadence.xml create mode 100644 org.bluetooth.service.scan_parameters.xml create mode 100644 org.bluetooth.service.transport_discovery.xml create mode 100644 org.bluetooth.service.tx_power.xml create mode 100644 org.bluetooth.service.user_data.xml create mode 100644 org.bluetooth.service.weight_scale.xml diff --git a/org.bluetooth.attribute.gatt.characteristic_declaration.xml b/org.bluetooth.attribute.gatt.characteristic_declaration.xml new file mode 100644 index 0000000..b7ce28a --- /dev/null +++ b/org.bluetooth.attribute.gatt.characteristic_declaration.xml @@ -0,0 +1,74 @@ + + + + + + Mandatory + uint8 + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Mandatory + uint16 + + + Mandatory + gatt_uuid + + + diff --git a/org.bluetooth.attribute.gatt.include_declaration.xml b/org.bluetooth.attribute.gatt.include_declaration.xml new file mode 100644 index 0000000..28b7cf8 --- /dev/null +++ b/org.bluetooth.attribute.gatt.include_declaration.xml @@ -0,0 +1,21 @@ + + + + + + Mandatory + uint16 + + + Mandatory + uint16 + + + Mandatory + gatt_uuid + + + diff --git a/org.bluetooth.attribute.gatt.primary_service_declaration.xml b/org.bluetooth.attribute.gatt.primary_service_declaration.xml new file mode 100644 index 0000000..69c4d68 --- /dev/null +++ b/org.bluetooth.attribute.gatt.primary_service_declaration.xml @@ -0,0 +1,13 @@ + + + + + + Mandatory + gatt_uuid + + + diff --git a/org.bluetooth.attribute.gatt.secondary_service_declaration.xml b/org.bluetooth.attribute.gatt.secondary_service_declaration.xml new file mode 100644 index 0000000..889f91d --- /dev/null +++ b/org.bluetooth.attribute.gatt.secondary_service_declaration.xml @@ -0,0 +1,13 @@ + + + + + + Mandatory + gatt_uuid + + + diff --git a/org.bluetooth.characteristic.Magnetic_flux_density_2D.xml b/org.bluetooth.characteristic.Magnetic_flux_density_2D.xml new file mode 100644 index 0000000..e6fb988 --- /dev/null +++ b/org.bluetooth.characteristic.Magnetic_flux_density_2D.xml @@ -0,0 +1,37 @@ + + + + + + Mandatory + sint16 + org.bluetooth.unit.magnetic_flux_density.tesla + This characteristic contains measurements of + magnetic flux density for two orthogonal axes: X and Y. This + characteristic is composed of two fields having the same + format: In order of LSO to MSO, the fields are: X-Axis, + Y-Axis. 1 x 10^-7 Tesla equals 0.001 Gauss. + -7 + + + Mandatory + sint16 + org.bluetooth.unit.magnetic_flux_density.tesla + This characteristic contains measurements of + magnetic flux density for two orthogonal axes: X and Y. This + characteristic is composed of two fields having the same + format: In order of LSO to MSO, the fields are: X-Axis, + Y-Axis. 1 x 10^-7 Tesla equals 0.001 Gauss. + -7 + + + +

The fields in the above table are in the order of LSO to + MSO. Where LSO = Least Significant Octet and MSO = Most + Significant Octet

+ + diff --git a/org.bluetooth.characteristic.Magnetic_flux_density_3D.xml b/org.bluetooth.characteristic.Magnetic_flux_density_3D.xml new file mode 100644 index 0000000..8ccb9c7 --- /dev/null +++ b/org.bluetooth.characteristic.Magnetic_flux_density_3D.xml @@ -0,0 +1,51 @@ + + + + + + Mandatory + sint16 + org.bluetooth.unit.magnetic_flux_density.tesla + This characteristic contains measurements of + magnetic flux density for three orthogonal axes: X, Y and Z. + This characteristic is composed of three fields having the + same format: In order of LSO to MSO, the fields are: X-Axis, + Y-Axis, Z-Axis. 1 x 10^-7 Tesla equals 0.001 + Gauss. + -7 + + + Mandatory + sint16 + org.bluetooth.unit.magnetic_flux_density.tesla + This characteristic contains measurements of + magnetic flux density for three orthogonal axes: X, Y and Z. + This characteristic is composed of three fields having the + same format: In order of LSO to MSO, the fields are: X-Axis, + Y-Axis, Z-Axis. 1 x 10^-7 Tesla equals 0.001 + Gauss. + -7 + + + Mandatory + sint16 + org.bluetooth.unit.magnetic_flux_density.tesla + This characteristic contains measurements of + magnetic flux density for three orthogonal axes: X, Y and Z. + This characteristic is composed of three fields having the + same format: In order of LSO to MSO, the fields are: X-Axis, + Y-Axis, Z-Axis. 1 x 10^-7 Tesla equals 0.001 + Gauss. + -7 + + + +

The fields in the above table are in the order of LSO to + MSO. Where LSO = Least Significant Octet and MSO = Most + Significant Octet

+ + diff --git a/org.bluetooth.characteristic.aerobic_heart_rate_lower_limit.xml b/org.bluetooth.characteristic.aerobic_heart_rate_lower_limit.xml new file mode 100644 index 0000000..a416bdc --- /dev/null +++ b/org.bluetooth.characteristic.aerobic_heart_rate_lower_limit.xml @@ -0,0 +1,22 @@ + + + + + Lower limit of the heart rate where the user enhances + his endurance while exercising + + + + Unit is in beats per minute with a + resolution of 1 + Mandatory + uint8 + org.bluetooth.unit.period.beats_per_minute + 0 + + + diff --git a/org.bluetooth.characteristic.aerobic_heart_rate_upper_limit.xml b/org.bluetooth.characteristic.aerobic_heart_rate_upper_limit.xml new file mode 100644 index 0000000..9fcb4fb --- /dev/null +++ b/org.bluetooth.characteristic.aerobic_heart_rate_upper_limit.xml @@ -0,0 +1,22 @@ + + + + + Upper limit of the heart rate where the user enhances + his endurance while exercising + + + + Unit is in beats per minute with a + resolution of 1 + Mandatory + uint8 + org.bluetooth.unit.period.beats_per_minute + 0 + + + diff --git a/org.bluetooth.characteristic.aerobic_threshold.xml b/org.bluetooth.characteristic.aerobic_threshold.xml new file mode 100644 index 0000000..cda2705 --- /dev/null +++ b/org.bluetooth.characteristic.aerobic_threshold.xml @@ -0,0 +1,28 @@ + + + + + First metabolic threshold. + + + + The Unit is beats per minute with a + resolution of 1 + Mandatory + uint8 + org.bluetooth.unit.period.beats_per_minute + 0 + + + +

Aerobic Threshold and Anaerobic Threshold together with the + Sport Type for Aerobic and Anaerobic Thresholds describe the + metabolic thresholds of the user. The Sport Type for Aerobic + and Anaerobic Thresholds identifies how the measurement was + performed.

+ + diff --git a/org.bluetooth.characteristic.age.xml b/org.bluetooth.characteristic.age.xml new file mode 100644 index 0000000..22bd7e1 --- /dev/null +++ b/org.bluetooth.characteristic.age.xml @@ -0,0 +1,17 @@ + + + + + Age of the User. + + + + Mandatory + uint8 + org.bluetooth.unit.time.year + + + diff --git a/org.bluetooth.characteristic.aggregate.xml b/org.bluetooth.characteristic.aggregate.xml new file mode 100644 index 0000000..f33ef58 --- /dev/null +++ b/org.bluetooth.characteristic.aggregate.xml @@ -0,0 +1,29 @@ + + + + + The Aggregate Input is an aggregate of the Digital + Input Characteristic value (if available) and ALL Analog Inputs + available. + + + + Mandatory + org.bluetooth.characteristic.digital + true + + + Mandatory + org.bluetooth.characteristic.analog + true + + + +

The fields in the above table, reading from top to bottom, + are shown in the order of LSO to MSO, where LSO = Least + Significant Octet and MSO = Most Significant Octet.

+ + diff --git a/org.bluetooth.characteristic.alert_category_id.xml b/org.bluetooth.characteristic.alert_category_id.xml new file mode 100644 index 0000000..1c6cef3 --- /dev/null +++ b/org.bluetooth.characteristic.alert_category_id.xml @@ -0,0 +1,49 @@ + + + + + Categories of alerts/messages. + The value of the characteristic is an unsigned 8 bit + integer that has a fixed point exponent of 0. The Alert + Category ID characteristic defines the predefined categories of + messages as an enumeration. + + The value 0x01 is interpreted as ?Email? + + + + + Mandatory + uint8 + 0 + 255 + + + + + + + + + + + + + + + + + The fields in the above table are in the order of LSO to + MSO. Where LSO = Least Significant Octet and MSO = Most + Significant Octet. + diff --git a/org.bluetooth.characteristic.alert_category_id_bit_mask.xml b/org.bluetooth.characteristic.alert_category_id_bit_mask.xml new file mode 100644 index 0000000..d80d7a8 --- /dev/null +++ b/org.bluetooth.characteristic.alert_category_id_bit_mask.xml @@ -0,0 +1,100 @@ + + + + + Categories of alerts/messages. + The value of the characteristic is a bit mask + implemented as an array of unsigned 8 bit integers. The Alert + Category ID Bit Mask characteristic defines one bit for each + predefined category ID. + + The value 0x03 is interpreted as ?Simple Alert and + Email bits set? + + + + + Mandatory + uint8 + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Optional + uint8 + + + + + + + + + + + + + + + + + + + If second octet is not present it is interpreted as all + 0?es + The fields in the above table are in the order of LSO to + MSO. Where LSO = Least Significant Octet and MSO = Most + Significant Octet. + diff --git a/org.bluetooth.characteristic.alert_level.xml b/org.bluetooth.characteristic.alert_level.xml new file mode 100644 index 0000000..f360557 --- /dev/null +++ b/org.bluetooth.characteristic.alert_level.xml @@ -0,0 +1,37 @@ + + + + + The level of an alert a device is to sound. If this + level is changed while the alert is being sounded, the new + level should take effect. + The value of the characteristic shall be an unsigned 8 + bit integer that has a fixed point exponent of 0. The Alert + Level characteristic defines the level of alert, and is one of + the following three values: +

? Value 0, meaning ?No Alert?

+

? Value 1, meaning ?Mild Alert?

+

? Value 2, meaning ?High Alert?

 + + The value 0x01 is interpreted as ?Mild + Alert? + + + + + Mandatory + uint8 + 0 + 2 + + + + + + + + + diff --git a/org.bluetooth.characteristic.alert_notification_control_point.xml b/org.bluetooth.characteristic.alert_notification_control_point.xml new file mode 100644 index 0000000..4818a88 --- /dev/null +++ b/org.bluetooth.characteristic.alert_notification_control_point.xml @@ -0,0 +1,55 @@ + + + + + Control point of the Alert Notification server. + Client can write the command here to request the several + functions toward the server. + The 1st octet value of the characteristic is an + unsigned 8 bit integer that has a fixed point exponent of 0. + The 1st octet value expresses the command ID that defines the + server?s actions. +

The 2nd octet value of the characteristic is an ?Alert + Category ID? format. This octet shows the target category that + the command ID applies for.

 + + The data 0x02 0x01 interprets ?Disable New Incoming + Notification for Email Category?. + + + + + Mandatory + uint8 + + + + + + + + + + + + Target category that the command applies + to. + Mandatory + + org.bluetooth.characteristic.alert_category_id + + + The fields in the above table are in the order of LSO to + MSO. Where LSO = Least Significant Octet and MSO = Most + Significant Octet. + diff --git a/org.bluetooth.characteristic.alert_status.xml b/org.bluetooth.characteristic.alert_status.xml new file mode 100644 index 0000000..6668b9e --- /dev/null +++ b/org.bluetooth.characteristic.alert_status.xml @@ -0,0 +1,56 @@ + + + + + The Alert Status characteristic defines the Status of + alert. +

Bit 0, meaning ?Ringer State?

+

Bit 1, meaning ?Vibrator State?

+

Bit 2, meaning "Display Alert Status"

 + + Bit 0, 0 meaning ?Ringer State? not active, 1 + meaning ?Ringer State? active + Bit 1, 0 meaning ?Vibrator State? not active, 1 + meaning ?Vibrator State? active + Bit 2, 0 meaning ?Display Alert State? not active, 1 + meaning ?Display Alert State? active + + + + + Mandatory + uint8 + 0 + 2 + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/org.bluetooth.characteristic.altitude.xml b/org.bluetooth.characteristic.altitude.xml new file mode 100644 index 0000000..2bf612b --- /dev/null +++ b/org.bluetooth.characteristic.altitude.xml @@ -0,0 +1,17 @@ + + + + + The Altitude characteristic describes the altitude of + the device. + + + + Mandatory + uint16 + + + diff --git a/org.bluetooth.characteristic.anaerobic_heart_rate_lower_limit.xml b/org.bluetooth.characteristic.anaerobic_heart_rate_lower_limit.xml new file mode 100644 index 0000000..d4c50ef --- /dev/null +++ b/org.bluetooth.characteristic.anaerobic_heart_rate_lower_limit.xml @@ -0,0 +1,22 @@ + + + + + Lower limit of the heart rate where the user enhances + his anaerobic tolerance while exercising. + + + + Unit is in beats per minute with a + resolution of 1 + Mandatory + uint8 + org.bluetooth.unit.period.beats_per_minute + 0 + + + diff --git a/org.bluetooth.characteristic.anaerobic_heart_rate_upper_limit.xml b/org.bluetooth.characteristic.anaerobic_heart_rate_upper_limit.xml new file mode 100644 index 0000000..bd8fb59 --- /dev/null +++ b/org.bluetooth.characteristic.anaerobic_heart_rate_upper_limit.xml @@ -0,0 +1,22 @@ + + + + + Upper limit of the heart rate where the user enhances + his anaerobic tolerance while exercising. + + + + Unit is in beats per minute with a + resolution of 1 + Mandatory + uint8 + org.bluetooth.unit.period.beats_per_minute + 0 + + + diff --git a/org.bluetooth.characteristic.anaerobic_threshold.xml b/org.bluetooth.characteristic.anaerobic_threshold.xml new file mode 100644 index 0000000..95a6e67 --- /dev/null +++ b/org.bluetooth.characteristic.anaerobic_threshold.xml @@ -0,0 +1,28 @@ + + + + + Second metabolic threshold + + + + The Unit is beats per minute with a + resolution of 1 + Mandatory + uint8 + org.bluetooth.unit.period.beats_per_minute + 0 + + + +

Aerobic Threshold and Anaerobic Threshold together with the + Sport Type for Aerobic and Anaerobic Thresholds describe the + metabolic thresholds of the user. The Sport Type for Aerobic + and Anaerobic Thresholds identifies how the measurement was + performed.

+ + diff --git a/org.bluetooth.characteristic.analog.xml b/org.bluetooth.characteristic.analog.xml new file mode 100644 index 0000000..deb85bd --- /dev/null +++ b/org.bluetooth.characteristic.analog.xml @@ -0,0 +1,22 @@ + + + + + The Analog characteristic is used to read or write the + value of one of the IO Module?s analog signals. + + + + Mandatory + uint16 + + + +

The Octet Order in the above table is in the order of LSO to + MSO, where LSO = Least Significant Octet and MSO = Most + Significant Octet.

+ + diff --git a/org.bluetooth.characteristic.apparent_wind_direction.xml b/org.bluetooth.characteristic.apparent_wind_direction.xml new file mode 100644 index 0000000..e9e0bf6 --- /dev/null +++ b/org.bluetooth.characteristic.apparent_wind_direction.xml @@ -0,0 +1,31 @@ + + + + + + Unit is in degrees with a resolution of 0.01 + degrees + Mandatory + uint16 + org.bluetooth.unit.plane_angle.degree + The apparent wind is the wind experienced by an + observer in motion and is the relative velocity of the wind + in relation to the observer. For example, the apparent wind + direction on-board a boat is given in degrees relative to the + heading of the boat. Wind direction is reported by the + direction from which it appears to originate. For example, an + apparent wind coming from a direction that is 45 degrees + clockwise relative to the heading of the observer is given as + 45 degrees; one that is from a direction 45 degrees + anti-clockwise relative to the heading of the observer is + given as 315 degrees. + -2 + 0 + 359.99 + + + diff --git a/org.bluetooth.characteristic.apparent_wind_speed.xml b/org.bluetooth.characteristic.apparent_wind_speed.xml new file mode 100644 index 0000000..26ac919 --- /dev/null +++ b/org.bluetooth.characteristic.apparent_wind_speed.xml @@ -0,0 +1,18 @@ + + + + + + Unit is in meters per second with a + resolution of 0.01 m/s + Mandatory + uint16 + org.bluetooth.unit.velocity.metres_per_second + -2 + + + diff --git a/org.bluetooth.characteristic.barometric_pressure_trend.xml b/org.bluetooth.characteristic.barometric_pressure_trend.xml new file mode 100644 index 0000000..f2e30db --- /dev/null +++ b/org.bluetooth.characteristic.barometric_pressure_trend.xml @@ -0,0 +1,31 @@ + + + + + + Mandatory + uint8 + org.bluetooth.unit.unitless + + + + + + + + + + + + + + + + diff --git a/org.bluetooth.characteristic.battery_level.xml b/org.bluetooth.characteristic.battery_level.xml new file mode 100644 index 0000000..33a293d --- /dev/null +++ b/org.bluetooth.characteristic.battery_level.xml @@ -0,0 +1,25 @@ + + + + + The current charge level of a battery. 100% + represents fully charged while 0% represents fully + discharged. + + + + Mandatory + uint8 + org.bluetooth.unit.percentage + 0 + 100 + + + + + + diff --git a/org.bluetooth.characteristic.blood_pressure_feature.xml b/org.bluetooth.characteristic.blood_pressure_feature.xml new file mode 100644 index 0000000..7c361a3 --- /dev/null +++ b/org.bluetooth.characteristic.blood_pressure_feature.xml @@ -0,0 +1,75 @@ + + + + + The Blood Pressure Feature characteristic is used to + describe the supported features of the Blood Pressure + Sensor. + + + + Mandatory + 16bit + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/org.bluetooth.characteristic.blood_pressure_measurement.xml b/org.bluetooth.characteristic.blood_pressure_measurement.xml new file mode 100644 index 0000000..1a47afc --- /dev/null +++ b/org.bluetooth.characteristic.blood_pressure_measurement.xml @@ -0,0 +1,209 @@ + + + + + The Blood Pressure Measurement characteristic is a + variable length structure containing a Flags field, a Blood + Pressure Measurement Compound Value field, and contains + additional fields such as Time Stamp, Pulse Rate and User ID as + determined by the contents of the Flags field. + + + + These flags define which data fields are + present in the Characteristic value + Mandatory + 8bit + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + C1: Field exists if the key of bit 0 of the + Flags field is set to 0 + C1 + SFLOAT + + org.bluetooth.unit.pressure.millimetre_of_mercury + + + + C1: Field exists if the key of bit 0 of the + Flags field is set to 0 + C1 + SFLOAT + + org.bluetooth.unit.pressure.millimetre_of_mercury + + + + C1: Field exists if the key of bit 0 of the + Flags field is set to 0 + C1 + SFLOAT + + org.bluetooth.unit.pressure.millimetre_of_mercury + + + + C2: Field exists if the key of bit 0 of the + Flags field is set to 1 + C2 + SFLOAT + org.bluetooth.unit.pressure.pascal + 3 + + + + C2: Field exists if the key of bit 0 of the + Flags field is set to 1 + C2 + SFLOAT + org.bluetooth.unit.pressure.pascal + 3 + + + + C2: Field exists if the key of bit 0 of the + Flags field is set to 1 + C2 + SFLOAT + org.bluetooth.unit.pressure.pascal + 3 + + + C3: Field exists if the key of bit 1 of the + Flags field is set to 1 + C3 + org.bluetooth.characteristic.date_time + + + C4: Field exists if the key of bit 2 of the + Flags field is set to 1 + C4 + SFLOAT + org.bluetooth.unit.period.beats_per_minute + + + C5: Field exists if the key of bit 3 of the + Flags field is set to 1 + C5 + uint8 + + + + + + + C6: Field exists if the key of bit 4 of the + Flags field is set to 1 + C6 + 16bit + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + The fields in the above table are in the order of LSO to + MSO. Where LSO = Least Significant Octet and MSO = Most + Significant Octet and MAP = Mean Arterial Pressure. + diff --git a/org.bluetooth.characteristic.body_composition_feature.xml b/org.bluetooth.characteristic.body_composition_feature.xml new file mode 100644 index 0000000..6e43607 --- /dev/null +++ b/org.bluetooth.characteristic.body_composition_feature.xml @@ -0,0 +1,117 @@ + + + + + + Mandatory + 32bit + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/org.bluetooth.characteristic.body_composition_measurement.xml b/org.bluetooth.characteristic.body_composition_measurement.xml new file mode 100644 index 0000000..28770a6 --- /dev/null +++ b/org.bluetooth.characteristic.body_composition_measurement.xml @@ -0,0 +1,280 @@ + + + + + + Mandatory + 16bit + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Unit is in percent with a resolution of + 0.1 + Mandatory + uint16 + org.bluetooth.unit.percentage + -1 + + + Smallest unit in seconds + C3 + org.bluetooth.characteristic.date_time + + + Unit is unitless with a resoluton of + 1 + C4 + uint8 + org.bluetooth.unit.unitless + 0 + + The special value of 0xFF (255 Decimal) + for User ID represents ?unknown user?. + + + + + Unit is in kilo Joules with a resolution of + 1 + C5 + uint16 + org.bluetooth.unit.energy.joule + 3 + + + Unit is in percentage with a resolution of + 0.1 + C6 + uint16 + org.bluetooth.unit.percentage + -1 + + + Unit is in kilograms with resolution 0.005. + Note: Determined when bit 0 of the Flags field is set to + 0. + C1 + C7 + uint16 + org.bluetooth.unit.mass.kilogram + -3 + 5 + + + Unit is in pounds with resolution 0.01. + Note: Determined when bit 0 of the Flags field is set to + 1. + C2 + C7 + uint16 + org.bluetooth.unit.mass.pound + -2 + + + Unit is in kilograms with resolution 0.005. + Note: Determined when bit 0 of the Flags field is set to + 0. + C1 + C8 + uint16 + org.bluetooth.unit.mass.kilogram + -3 + 5 + + + Unit is in pounds with a resolution of 0.01. + Note: Determined when bit 0 of the Flags field is set to + 1. + C2 + C8 + uint16 + org.bluetooth.unit.mass.pound + -2 + + + Unit is in kilograms with a resolution of + 0.005. Note: Determined when bit 0 of the Flags field is set + to 0. + C1 + C9 + uint16 + org.bluetooth.unit.mass.kilogram + -3 + 5 + + + Unit is in pounds with a resolution of 0.01. + Note: Determined when bit 0 of the Flags field is set to + 1. + C2 + C9 + uint16 + org.bluetooth.unit.mass.kilogram + -2 + + + Unit is in kilograms with a resolution of + 0.005. Note: Determined when bit 0 of the Flags field is set + to 0. + C1 + C10 + uint16 + org.bluetooth.unit.mass.kilogram + -3 + 5 + + + Unit is in pounds with a resolution of 0.01. + Note: Determined when bit 0 of the Flags field is set to + 1. + C2 + C10 + uint16 + org.bluetooth.unit.mass.pound + -2 + + + Unit is in Ohms with a resolution of + 0.1 + C11 + uint16 + org.bluetooth.unit.electric_resistance.ohm + -1 + + + Unit is in kilograms with a resolution of + 0.005. Note: Determined when bit 0 of the Flags field is set + to 0. + C1 + C12 + uint16 + org.bluetooth.unit.mass.kilogram + -3 + 5 + + + Unit is in pounds with a resolution of 0.01. + Note: Determined when bit 0 of the Flags field is set to + 1. + C2 + C12 + uint16 + org.bluetooth.unit.mass.pound + -2 + + + Unit is in meters with a resolution of + 0.001. Note: Determined when bit 0 of the Flags field is set + to 0. + C1 + C13 + uint16 + org.bluetooth.unit.length.meter + -3 + + + Unit is in meters with a resolution of 0.1. + Note: Determined when bit 0 of the Flags field is set to + 1. + C2 + C13 + uint16 + org.bluetooth.unit.length.inch + -1 + + + +

The fields in the above table are in the order of LSO to + MSO. Where LSO = Least Significant Octet and MSO = Most + Significant Octet.

+ + diff --git a/org.bluetooth.characteristic.body_sensor_location.xml b/org.bluetooth.characteristic.body_sensor_location.xml new file mode 100644 index 0000000..b6cd551 --- /dev/null +++ b/org.bluetooth.characteristic.body_sensor_location.xml @@ -0,0 +1,24 @@ + + + + + + + Mandatory + 8bit + + + + + + + + + + + + + diff --git a/org.bluetooth.characteristic.bond_management_control_point.xml b/org.bluetooth.characteristic.bond_management_control_point.xml new file mode 100644 index 0000000..1940457 --- /dev/null +++ b/org.bluetooth.characteristic.bond_management_control_point.xml @@ -0,0 +1,97 @@ + + + + + The Bond Management Service Control Point (BMSCP) + encapsulates functionality and mechanisms to control the bonds + of a device. + This control point is used with a service to provide + BMS specific functionality and the ability to manage bonds on + the device. This includes functions like delete the bond + information of the current connection or deletion of the whole + bond information. The criterion in the Operand field is defined + by the service that references this characteristic + + + + + Mandatory + uint8 + + + + + + + + + + + + + + + + Octet Order - LSO-MSO + Conditional + variable + + + + + + + + + + + + + + + +

The fields in the above table are in the order of LSO to + MSO. Where LSO = Least Significant Octet and MSO = Most + Significant Octet

+ + diff --git a/org.bluetooth.characteristic.bond_management_feature.xml b/org.bluetooth.characteristic.bond_management_feature.xml new file mode 100644 index 0000000..6a4a16b --- /dev/null +++ b/org.bluetooth.characteristic.bond_management_feature.xml @@ -0,0 +1,174 @@ + + + + + + Byte Order - LSO...MSO + Mandatory + 24bit + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +

If the Feature Extension bit (bit number 23) is set, an + additional octet is attached (bits 24 ? 31), where bit 31 shall + be used as Feature Extension bit in the same way. If this bit + is set, then another octet is attached (bits 32 ? 39) and so + on. This is defined to allow future extension of the + characteristic.

+ + diff --git a/org.bluetooth.characteristic.boot_keyboard_input_report.xml b/org.bluetooth.characteristic.boot_keyboard_input_report.xml new file mode 100644 index 0000000..3b32a9f --- /dev/null +++ b/org.bluetooth.characteristic.boot_keyboard_input_report.xml @@ -0,0 +1,21 @@ + + + + + The Boot Keyboard Input Report characteristic is used + to transfer fixed format and length Input Report data between a + HID Host operating in Boot Protocol Mode and a HID Service + corresponding to a boot keyboard. + + + + Mandatory + uint8 + true + + + diff --git a/org.bluetooth.characteristic.boot_keyboard_output_report.xml b/org.bluetooth.characteristic.boot_keyboard_output_report.xml new file mode 100644 index 0000000..26a1910 --- /dev/null +++ b/org.bluetooth.characteristic.boot_keyboard_output_report.xml @@ -0,0 +1,21 @@ + + + + + The Boot Keyboard Output Report characteristic is used + to transfer fixed format and length Output Report data between + a HID Host operating in Boot Protocol Mode and a HID Service + corresponding to a boot keyboard. + + + + Mandatory + uint8 + true + + + diff --git a/org.bluetooth.characteristic.boot_mouse_input_report.xml b/org.bluetooth.characteristic.boot_mouse_input_report.xml new file mode 100644 index 0000000..99bef8b --- /dev/null +++ b/org.bluetooth.characteristic.boot_mouse_input_report.xml @@ -0,0 +1,21 @@ + + + + + The Boot Mouse Input Report characteristic is used to + transfer fixed format and length Input Report data between a + HID Host operating in Boot Protocol Mode and a HID Service + corresponding to a boot mouse. + + + + Mandatory + uint8 + true + + + diff --git a/org.bluetooth.characteristic.cgm_feature.xml b/org.bluetooth.characteristic.cgm_feature.xml new file mode 100644 index 0000000..ddb2012 --- /dev/null +++ b/org.bluetooth.characteristic.cgm_feature.xml @@ -0,0 +1,189 @@ + + + + + + Byte Order - LSO...MSO + Mandatory + 24bit + 0 + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + See Note number 2 below. + Mandatory + 4bit + + + + + + + + + + + + + + + + + See Note number 2 below. + Mandatory + 4bit + + + + + + + + + + + + + If the device supports E2E-safety (E2E-CRC + Supported bit is set in CGM Feature), the feature are secured + by a CRC calculated over all data. This field is mandatory in + this characteristic. If the device doesn?t support E2E-safety + the value of the field shall be set to + 0xFFFF. + Mandatory + uint16 + 0 + + + +

1. The fields in the above table are in the order of LSO to + MSO. Where LSO = Least Significant Octet and MSO = Most + Significant Octet

+

2. The CGM Type and CGM Sample Location Fields are each a + nibble (4bit), where the least significant nibble contains the + Type and the most significant nibble contains the Sample + Location. These two nibbles are packed as one single octet, the + Least Significant Nibble means the four bits numbered 0, 1, 2 + and 3 of the octet and the Most Significant Nibble means the + four bits numbered 4, 5, 6 and 7 of that octet

+ + diff --git a/org.bluetooth.characteristic.cgm_measurement.xml b/org.bluetooth.characteristic.cgm_measurement.xml new file mode 100644 index 0000000..86f3411 --- /dev/null +++ b/org.bluetooth.characteristic.cgm_measurement.xml @@ -0,0 +1,300 @@ + + + + + The CGM Measurement characteristic is a variable + length structure containing one or more CGM Measurement + records, each comprising a Size field, a Flags Field, a Glucose + Concentration field, a Time Offset field, a Sensor Status + Annunciation field (optional), a CGM Trend Information Field + (optional), a CGM Quality Field (optional), and an E2E-CRC + Field (mandatory if this feature is supported). + + + + The Size Field represents the size of the + CGM Measurement record. In minimum the size is 6 octets and + is enlarged by more octets indicated by the Flags Field + (Sensor Status Annunciation Field, CGM Trend Information + Field and CGM Quality Field) and the E2E-CRC Supported bit in + CGM Feature. The Size Field itself is included in the overall + length calculation. + Mandatory + uint8 + + + Mandatory + 8bit + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + The CGM Glucose Concetration Field contains + the CGM glucose concentration in mg/dL as a SFLOAT data type. + The SFLOAT-Type is a 16-bit word comprising a signed 4-bit + integer exponent followed by a signed 12-bit Mantissa, each + in twos-complement form. + Mandatory + SFLOAT + + org.bluetooth.unit.mass_density.milligram_per_decilitre + 0 + + + The following values are defined for the + Time Offset Field, specifying the relative time difference of + the single CGM values to the session start time. Value: + (0x0000 - 0xFFFF), Description: (Time offset in minutes as + offset to the Session Start Time). + Mandatory + uint16 + org.bluetooth.unit.time.minute + 0 + + + The Sensor Status Annunciation Field is an + optional field comprising up to three octets. It is only + attached if one or more bits are set to ?1?. Only the + affected octet(s) shall be added and indicated by the Flags + Field. The Sensor Status Annunciation Field shall be attached + to every CGM Measurement Record to which the status + applies. + C4 + variable + The format "Variable" is Defined by the Service + Specification + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + The CGM Trend Information Field contains the + CGM Trend information in (mg/dL)/min as an SFLOAT data type. + This field is optional if the device supports CGM Trend + information (Bit 15 in CGM Feature is set to 1) otherwise + excluded. + C1 + SFLOAT + + org.bluetooth.unit.mass_density.milligram_per_decilitre + 0 + + + This field contains the CGM Quality + information in % as an SFLOAT data type. The SFLOAT-Type is a + 16-bit word comprising a signed 4-bit integer exponent + followed by a signed 12-bit Mantissa, each in twos-complement + form. This field is optional if the device supports CGM + Quality (Bit 16 in CGM Feature is set to 1) otherwise + excluded. + C2 + SFLOAT + org.bluetooth.unit.percentage + 0 + + + If the device supports E2E-safety (E2E-CRC + Supported bit is set in CGM Feature), the measurement is + secured by a CRC calculated over all fields. The computation + of the CRC is done using a CRC-CCITT generator polynomial + g(D)=D16+D12+D5+1 (i.e.210041 in octal representation) with a + seed of 0xFFFF. This field is mandatory if the device + supports E2E-CRC (Bit 12 in CGM Feature is set to 1) + otherwise excluded. + C3 + uint16 + + + +

The fields in the above table are in the order of LSO to + MSO. Where LSO = Least Significant Octet and MSO = Most + Significant Octet

+

C1: Optional if device supports CGM Trend Information (Bit + 15 is set in CGM Feature) otherwise excluded.

+

C2: Optional if device supports CGM Quality (Bit 16 is set + in CGM Feature) otherwise excluded.

+

C3: Mandatory if device supports E2E-CRC (Bit 12 is set in + CGM Feature) otherwise excluded.

+

C4: Optional if bit 5 or bit 6 or bit 7 of the flgas field + is set to ?1?, otherwise excluded.

+ + diff --git a/org.bluetooth.characteristic.cgm_session_run_time.xml b/org.bluetooth.characteristic.cgm_session_run_time.xml new file mode 100644 index 0000000..85fbde3 --- /dev/null +++ b/org.bluetooth.characteristic.cgm_session_run_time.xml @@ -0,0 +1,35 @@ + + + + + + Typically the CGM Sensors have a limited run + time where they are approved for by regulatory bodies. + However this characteristic should enable a prediction of the + run time depending on physiological effects in future + devices. + Mandatory + uint16 + org.bluetooth.unit.time.hour + + + If the device supports E2E-safety + (E2E-CRC-Supported bit is set in CGM Feature), the session + run time is secured by a CRC calculated over all + fields. + C1 + uint16 + + + +

C1: Mandatory if device supports E2E-CRC (Bit 12 is set in + CGM Feature) otherwise excluded.

+

The fields in the above table are in the order of LSO to + MSO. Where LSO = Least Significant Octet and MSO = Most + Significant Octet

+ + diff --git a/org.bluetooth.characteristic.cgm_session_start_time.xml b/org.bluetooth.characteristic.cgm_session_start_time.xml new file mode 100644 index 0000000..9245a73 --- /dev/null +++ b/org.bluetooth.characteristic.cgm_session_start_time.xml @@ -0,0 +1,44 @@ + + + + + + Same format as the Date Time Characteristic, + smallest unit in seconds + Mandatory + org.bluetooth.characteristic.date_time + + + Same format as the Time Zone + Characteristic + Mandatory + org.bluetooth.characteristic.time_zone + + + Same format as the DST Offset + Characteristic + Mandatory + + org.bluetooth.characteristic.dst_offset + + + If the device supports E2E-safety + (E2E-CRC-Supported bit is set in CGM Feature), the session + start time is secured by a CRC calculated over all + fields. + C1 + uint16 + + + +

C1: Mandatory if device supports E2E-CRC (Bit 12 is set in + CGM Feature) otherwise excluded.

+

The fields in the above table are in the order of LSO to + MSO. Where LSO = Least Significant Octet and MSO = Most + Significant Octet

+ + diff --git a/org.bluetooth.characteristic.cgm_specific_ops_control_point.xml b/org.bluetooth.characteristic.cgm_specific_ops_control_point.xml new file mode 100644 index 0000000..c1edd15 --- /dev/null +++ b/org.bluetooth.characteristic.cgm_specific_ops_control_point.xml @@ -0,0 +1,260 @@ + + + + + The CGM Specific Ops Control Point encapsulates all + functionality and mechanisms that are unique to a CGM-device. + This control point is used with a service to provide CGM + specific functionality and the ability to change CGM specific + settings of the device. This includes functions like setting + the CGM Communication Interval or the sending a calibration + value to the device. The criterion in the Operand field is + defined by the service that references this + characteristic + + + + + Mandatory + uint8 + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Mandatory + uint8 + + + + + + + + + + + + Value defined per Service + Mandatory + variable + Defined by the Service + Specification + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + If the device supports E2E-safety + (E2E-CRC-Supported bit is set in CGM Feature), the specific + ops control point is secured by a CRC calculated over all + fields. Refer to CGM Service specification. + C1 + uint16 + + + + See Note number 2 below. + Mandatory + SFLOAT + + org.bluetooth.unit.mass_density.milligram_per_decilitre + 0 + + + See Note number 2 below. + Mandatory + uint16 + org.bluetooth.unit.time.minute + Calibration Time in minutes as offset to the + Session Start Time. Value: 0x0000-0xFFFF + 0 + + + See Note number 2 below. + Mandatory + 4bit + + + See Note number 2 below. + Mandatory + 4bit + + + See Note number 2 below. + Mandatory + uint16 + org.bluetooth.unit.time.minute + Next Calibration Time in minutes as offset to + the Session Start Time. Value: 0x0000-0xFFFF + 0 + + + + See Note number 2 below. + Mandatory + uint16 + + + See Note number 2 below. + Mandatory + 8bit + + + + + + + + + + + + + + + + + + + + + + + + +

1. C1: Mandatory if device supports E2E-CRC (Bit 12 is set + in CGM Feature) otherwise excluded

+

2. Describes the Operand which is used for setting and + getting the calibration value

+

3.The fields in the above table are in the order of LSO to + MSO. Where LSO = Least Significant Octet and MSO = Most + Significant Octet

+ + diff --git a/org.bluetooth.characteristic.cgm_status.xml b/org.bluetooth.characteristic.cgm_status.xml new file mode 100644 index 0000000..cfdea5b --- /dev/null +++ b/org.bluetooth.characteristic.cgm_status.xml @@ -0,0 +1,48 @@ + + + + + The CGM Status allows the Collector to actively + request the current status from the CGM Sensor, particularly + when the CGM measurement is not running and the status cannot + be given in the measurement result in the Status + Annunciation. + + + + The Time Offset Field specifies the actual + relative time difference to the session start + time. + Mandatory + uint16 + org.bluetooth.unit.time.minute + 0 + + + The structure of the CGM Status Field shall + be identical to the structure of the Status Annunciation + Field, as defined in the CGM Measurement Characteristic + "Sensor Status Annunciation Field". It always consists of + three octets regardless the value. + Mandatory + 24bit + + + If the device supports E2E-safety (E2E-CRC + Supported bit is set in CGM Feature), the status is secured + by a CRC calculated over all fields. + C1 + uint16 + + + +

C1: Mandatory if device supports E2E-CRC (Bit 12 is set in + CGM Feature) otherwise excluded.

+

The fields in the above table are in the order of LSO to + MSO. Where LSO = Least Significant Octet and MSO = Most + Significant Octet

+ + diff --git a/org.bluetooth.characteristic.cross_trainer_data.xml b/org.bluetooth.characteristic.cross_trainer_data.xml new file mode 100644 index 0000000..afd2d3b --- /dev/null +++ b/org.bluetooth.characteristic.cross_trainer_data.xml @@ -0,0 +1,272 @@ + + + + + The Cross Trainer Data characteristic is used to send + training-related data to the Client from a cross trainer + (Server). + + + + Mandatory + 24bit + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Kilometer per hour with a resolution of + 0.01 + C1 + uint16 + org.bluetooth.unit.velocity.kilometre_per_hour + -2 + + + Kilometer per hour with a resolution of + 0.01 + C2 + uint16 + org.bluetooth.unit.velocity.kilometre_per_hour + -2 + + + Meters with a resolution of + 1 + C3 + uint24 + org.bluetooth.unit.length.metre + + + Step/minute with a resolution of + 1 + C4 + uint16 + org.bluetooth.unit.step_per_minute + + + Step/minute with a resolution of + 1 + C4 + uint16 + org.bluetooth.unit.step_per_minute + + + Unitless with a resolution of + 0.1 + C5 + uint16 + -1 + org.bluetooth.unit.unitless + + + Meters with a resolution of + 1 + C6 + uint16 + org.bluetooth.unit.length.metre + + + Meters with a resolution of + 1 + C6 + uint16 + org.bluetooth.unit.length.metre + + + Percent with a resolution of + 0.1 + C7 + sint16 + org.bluetooth.unit.percentage + -1 + + + Degree with a resolution of + 0.1 + C7 + sint16 + org.bluetooth.unit.plane_angle.degree + -1 + + + Unitless with a resolution of + 0.1 + C8 + sint16 + -1 + org.bluetooth.unit.unitless + + + Watts with a resolution of + 1 + C9 + sint16 + org.bluetooth.unit.power.watt + + + Watts with a resolution of + 1 + C10 + sint16 + org.bluetooth.unit.power.watt + + + Kilo Calorie with a resolution of + 1 + C11 + uint16 + org.bluetooth.unit.energy.kilogram_calorie + + + Kilo Calorie with a resolution of + 1 + C11 + uint16 + org.bluetooth.unit.energy.kilogram_calorie + + + Kilo Calorie with a resolution of + 1 + C11 + uint8 + org.bluetooth.unit.energy.kilogram_calorie + + + Beats per minute with a resolution of + 1 + C12 + uint8 + org.bluetooth.unit.period.beats_per_minute + + + Metabolic Equivalent with a resolution of + 0.1 + C13 + uint8 + -1 + org.bluetooth.unit.metabolic_equivalent + + + Second with a resolution of + 1 + C14 + uint16 + org.bluetooth.unit.time.second + + + Second with a resolution of + 1 + C15 + uint16 + org.bluetooth.unit.time.second + + + The fields in the above table, reading from top to bottom, + are shown in the order of LSO to MSO, where LSO = Least + Significant Octet and MSO = Most Significant Octet. The Least + Significant Octet represents the eight bits numbered 0 to + 7. + diff --git a/org.bluetooth.characteristic.csc_feature.xml b/org.bluetooth.characteristic.csc_feature.xml new file mode 100644 index 0000000..43f97d8 --- /dev/null +++ b/org.bluetooth.characteristic.csc_feature.xml @@ -0,0 +1,42 @@ + + + + + The CSC (Cycling Speed and Cadence) Feature + characteristic is used to describe the supported features of + the Server. + + + + Mandatory + 16bit + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/org.bluetooth.characteristic.csc_measurement.xml b/org.bluetooth.characteristic.csc_measurement.xml new file mode 100644 index 0000000..a39c60e --- /dev/null +++ b/org.bluetooth.characteristic.csc_measurement.xml @@ -0,0 +1,75 @@ + + + + + The CSC Measurement characteristic (CSC refers to + Cycling Speed and Cadence) is a variable length structure + containing a Flags field and, based on the contents of the + Flags field, may contain one or more additional fields as shown + in the tables below. + + + + These flags define which data fields are + present in the Characteristic value. + Mandatory + 8bit + + + + + + + + + + + + + + + + + + C1: Field exists if the key of bit 0 of the + Flags field is set to 1. + C1 + uint32 + org.bluetooth.unit.unitless + + + Unit has a resolution of 1/1024s. +
C1: Field exists if the key of bit 0 of the Flags field + is set to 1.
 + C1 + uint16 + org.bluetooth.unit.time.second + -10 + + + C2: Field exists if the key of bit 1 of the + Flags field is set to 1. + C2 + uint16 + org.bluetooth.unit.unitless + + + C2: Field exists if the key of bit 1 of the + Flags field is set to 1. +
Unit has a resolution of 1/1024s.
 + C2 + uint16 + org.bluetooth.unit.time.second + -10 + + + The fields in the above table are in the order of LSO to + MSO. Where LSO = Least Significant Octet and MSO = Most + Significant Octet. + diff --git a/org.bluetooth.characteristic.current_time.xml b/org.bluetooth.characteristic.current_time.xml new file mode 100644 index 0000000..eb3d4fb --- /dev/null +++ b/org.bluetooth.characteristic.current_time.xml @@ -0,0 +1,52 @@ + + + + + + + Mandatory + + org.bluetooth.characteristic.exact_time_256 + + + Mandatory + 8bit + + + + + + + + + + + + + + + + + + + + + + + + + + + + + The fields in the above table are in the order of LSO to + MSO. Where LSO = Least Significant Octet and MSO = Most + Significant Octet. + diff --git a/org.bluetooth.characteristic.cycling_power_control_point.xml b/org.bluetooth.characteristic.cycling_power_control_point.xml new file mode 100644 index 0000000..f80ba61 --- /dev/null +++ b/org.bluetooth.characteristic.cycling_power_control_point.xml @@ -0,0 +1,117 @@ + + + + + + The Cycling Power Control Point characteristic is used + to request a specific function to be executed on the receiving + device. + + + + Mandatory + uint8 + + + + + + + + + + + + + + + + + + + + + + + + + + Optional + variable + Defined per Service specification. + + + The Request Op Code is a sub field of the + Parameter Value for "Response Code" Op Code. +
C1: This Field is Mandatory for "Response Code" Op Code, + otherwise this field is Excluded.
 + C1 + uint8 + Refer to the Op Code table above for additional + information on the possible values for this + field. + + + The Response Value is a sub field of the + Parameter Value for "Response Code" Op Code +
C1: This Field is Mandatory for "Response Code" Op Code, + otherwise this field is Excluded.
 + C1 + uint8 + + + + + + + + + + + The Response Parameter is a sub field of the + Parameter Value for "Response Code" Op Code. +
C2:This Field is Optional for "Response Code" Op Code, + otherwise this field is Excluded.
 + C2 + variable + Note: The Response Parameter Value of the + response to the Control Point is a variable length field to + allow a list of different values defined by the Service + Specification + + + The fields in the above table, reading from top to bottom, + are shown in the order of LSO to MSO, where LSO = Least + Significant Octet and MSO = Most Significant Octet. The Least + Significant Octet represents the eight bits numbered 0 to + 7. + diff --git a/org.bluetooth.characteristic.cycling_power_feature.xml b/org.bluetooth.characteristic.cycling_power_feature.xml new file mode 100644 index 0000000..52c2679 --- /dev/null +++ b/org.bluetooth.characteristic.cycling_power_feature.xml @@ -0,0 +1,177 @@ + + + + + + The CP Feature characteristic is used to report a list + of features supported by the device. + + + + Mandatory + 32bit + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + The fields in the above table, reading from top to bottom, + are shown in the order of LSO to MSO, where LSO = Least + Significant Octet and MSO = Most Significant Octet. The Least + Significant Octet represents the eight bits numbered 0 to + 7. + diff --git a/org.bluetooth.characteristic.cycling_power_measurement.xml b/org.bluetooth.characteristic.cycling_power_measurement.xml new file mode 100644 index 0000000..1568d3a --- /dev/null +++ b/org.bluetooth.characteristic.cycling_power_measurement.xml @@ -0,0 +1,320 @@ + + + + + The Cycling Power Measurement characteristic is a + variable length structure containing a Flags field, an + Instantaneous Power field and, based on the contents of the + Flags field, may contain one or more additional fields as shown + in the table below. + + + + Mandatory + 16bit + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + C1:These Fields are dependent upon the Flags field +

+ + + Unit is in watts with a resolution of + 1. + Mandatory + sint16 + org.bluetooth.unit.power.watt + 0 + + + Unit is in percentage with a resolution of + 1/2. + Optional + uint8 + org.bluetooth.unit.percentage + -1 + + + Unit is in newton metres with a resolution + of 1/32. + Optional + uint16 + org.bluetooth.unit.moment_of_force.newton_metre + -5 + + + + Unitless +
C1:When present, these fields are always present as a + pair.
 + C1 + uint32 + org.bluetooth.unit.unitless + 0 + + + Unit is in seconds with a resolution of + 1/2048. +
C1:When present, these fields are always present as a + pair.
 + C1 + uint16 + org.bluetooth.unit.time.second + -11 + + + + Unitless +
C2:When present, these fields are always present as a + pair.
 + C2 + uint16 + org.bluetooth.unit.unitless + 0 + + + Unit is in seconds with a resolution of + 1/1024. +
C2:When present, these fields are always present as a + pair.
 + C2 + uint16 + org.bluetooth.unit.time.second + -10 + + + + Unit is in newtons with a resolution of 1. +
C3:When present, these fields are always present as a + pair.
 + C3 + sint16 + org.bluetooth.unit.force.newton + 0 + + + + Unit is in newtons with a resolution of 1. +
C3:When present, these fields are always present as a + pair.
 + C3 + sint16 + org.bluetooth.unit.force.newton + 0 + + + + Unit is in newton metres with a resolution + of 1/32. +
C4:When present, these fields are always present as a + pair.
 + C4 + sint16 + org.bluetooth.unit.moment_of_force.newton_metre + -5 + + + + Unit is in newton metres with a resolution + of 1/32. +
C4:When present, these fields are always present as a + pair.
 + C4 + sint16 + org.bluetooth.unit.moment_of_force.newton_metre + -5 + + + Unit is in degrees with a resolution of 1 +
C5: When present, this field and the "Extreme Angles - + Minimum Angle" field are always present as a pair and are + concatenated into a UINT24 value (3 octets). As an example, + if the Maximum Angle is 0xABC and the Minimum Angle is 0x123, + the transmitted value is 0x123ABC.
 + C5 + uint12 + org.bluetooth.unit.plane_angle.degree + + When observed with the front wheel to the right + of the pedals, a value of 0 degrees represents the angle when + the crank is in the 12 o'clock position and a value of 90 + degrees represents the angle, measured clockwise, when the + crank points towards the front wheel in a 3 o'clock position. + The left crank sensor (if fitted) detects the 0? when the + crank it is attached to is in the 12 o'clock position and the + right sensor (if fitted) detects the 0? when the crank it is + attached to is in its 12 o'clock position; thus, there is a + constant 180? difference between the right crank and the left + crank position signals. + 0 + + + Unit is in degrees with a resolution of 1. +
C5: When present, this field and the "Extreme Angles - + Maximum Angle" field are always present as a pair and are + concatenated into a UINT24 value (3 octets). As an example, + if the Maximum Angle is 0xABC and the Minimum Angle is 0x123, + the transmitted value is 0x123ABC.
 + C5 + uint12 + org.bluetooth.unit.plane_angle.degree + + When observed with the front wheel to the right + of the pedals, a value of 0 degrees represents the angle when + the crank is in the 12 o'clock position and a value of 90 + degrees represents the angle, measured clockwise, when the + crank points towards the front wheel in a 3 o'clock position. + The left crank sensor (if fitted) detects the 0? when the + crank it is attached to is in the 12 o'clock position and the + right sensor (if fitted) detects the 0? when the crank it is + attached to is in its 12 o'clock position; thus, there is a + constant 180? difference between the right crank and the left + crank position signals. + 0 + + + Unit is in degrees with a resolution of + 1. + Optional + uint16 + org.bluetooth.unit.plane_angle.degree + + When observed with the front wheel to the right + of the pedals, a value of 0 degrees represents the angle when + the crank is in the 12 o'clock position and a value of 90 + degrees represents the angle, measured clockwise, when the + crank points towards the front wheel in a 3 o'clock position. + The left crank sensor (if fitted) detects the 0? when the + crank it is attached to is in the 12 o'clock position and the + right sensor (if fitted) detects the 0? when the crank it is + attached to is in its 12 o'clock position; thus, there is a + constant 180? difference between the right crank and the left + crank position signals. + 0 + + + Unit is in degrees with a resolution of + 1. + Optional + uint16 + org.bluetooth.unit.plane_angle.degree + + When observed with the front wheel to the right + of the pedals, a value of 0 degrees represents the angle when + the crank is in the 12 o'clock position and a value of 90 + degrees represents the angle, measured clockwise, when the + crank points towards the front wheel in a 3 o'clock position. + The left crank sensor (if fitted) detects the 0? when the + crank it is attached to is in the 12 o'clock position and the + right sensor (if fitted) detects the 0? when the crank it is + attached to is in its 12 o'clock position; thus, there is a + constant 180? difference between the right crank and the left + crank position signals. + 0 + + + Unit is in kilojoules with a resolution of + 1. + Optional + uint16 + org.bluetooth.unit.energy.joule + 3 + + + +

The fields in the above table, reading from top to bottom, + are shown in the order of LSO to MSO, where LSO = Least + Significant Octet and MSO = Most Significant Octet. The Least + Significant Octet represents the eight bits numbered 0 to + 7.

+ + diff --git a/org.bluetooth.characteristic.cycling_power_vector.xml b/org.bluetooth.characteristic.cycling_power_vector.xml new file mode 100644 index 0000000..e71b5e8 --- /dev/null +++ b/org.bluetooth.characteristic.cycling_power_vector.xml @@ -0,0 +1,137 @@ + + + + + The Cycling Power Vector characteristic is a variable + length structure containing a Flags fieldand based on the + contents of the Flags field, may contain one or more additional + fields as shown in the table below. + + + + Mandatory + 8bit + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
C1:These Fields are dependent upon the Flags field
+

+ + + + Unitless +
C1:When present, these fields are always present as a + pair.
 + C1 + uint16 + org.bluetooth.unit.unitless + 0 + + + Unit is in seconds with a resolution of + 1/1024. +
C1:When present, these fields are always present as a + pair.
 + C1 + uint16 + org.bluetooth.unit.time.second + -10 + + + Unit is in degrees with a resolution of + 1. + Optional + uint16 + org.bluetooth.unit.plane_angle.degree + + When observed with the front wheel to the right + of the pedals, a value of 0 degrees represents the angle when + the crank is in the 12 o'clock position and a value of 90 + degrees represents the angle, measured clockwise, when the + crank points towards the front wheel in a 3 o'clock position. + The left crank sensor (if fitted) detects the 0? when the + crank it is attached to is in the 12 o'clock position and the + right sensor (if fitted) detects the 0? when the crank it is + attached to is in its 12 o'clock position; thus, there is a + constant 180? difference between the right crank and the left + crank position signals. + 0 + + + The unit is in newtons with a resolution of + 1 +
Array Order - Older is towards the LSO and Newer is + towards the MSO
+
C2: These fields are mutually exclusive. When this field + is present, the presence of the Instantaneous Torque + Magnitude Array is excluded.
 + C2 + sint16 + org.bluetooth.unit.force.newton + 0 + 1 + + + Unit is in newton/meter with a resolution of + 1/32 +
Array Order - Older is towards the LSO and Newer is + towards the MSO
+
C2: These fields are mutually exclusive. When this field + is present, the presence of the Instantaneous Force Magnitude + Array is excluded.
 + C2 + sint16 + org.bluetooth.unit.moment_of_force.newton_metre + -5 + 1 + + + +

The fields in the above table, reading from top to bottom, + are shown in the order of LSO to MSO, where LSO = Least + Significant Octet and MSO = Most Significant Octet. The Least + Significant Octet represents the eight bits numbered 0 to + 7.

+ + diff --git a/org.bluetooth.characteristic.database_change_increment.xml b/org.bluetooth.characteristic.database_change_increment.xml new file mode 100644 index 0000000..dbea94b --- /dev/null +++ b/org.bluetooth.characteristic.database_change_increment.xml @@ -0,0 +1,14 @@ + + + + + + Mandatory + uint32 + + + diff --git a/org.bluetooth.characteristic.date_of_birth.xml b/org.bluetooth.characteristic.date_of_birth.xml new file mode 100644 index 0000000..d6168d7 --- /dev/null +++ b/org.bluetooth.characteristic.date_of_birth.xml @@ -0,0 +1,63 @@ + + + + + + Year as defined by the Gregorian + calendar. + Mandatory + uint16 + org.bluetooth.unit.time.year + 1582 + 9999 + + + + + + Month of the year as defined by the + Gregorian calendar. + Mandatory + uint8 + org.bluetooth.unit.time.month + 0 + 12 + + + + + + + + + + + + + + + + + + Day of the month as defined by the Gregorian + calendar. + Mandatory + uint8 + org.bluetooth.unit.time.day + 0 + 31 + + + + + + +

The fields in the above table are in the order of LSO to + MSO. Where LSO = Least Significant Octet and MSO = Most + Significant Octet.

+ + diff --git a/org.bluetooth.characteristic.date_of_threshold_assessment.xml b/org.bluetooth.characteristic.date_of_threshold_assessment.xml new file mode 100644 index 0000000..b77414e --- /dev/null +++ b/org.bluetooth.characteristic.date_of_threshold_assessment.xml @@ -0,0 +1,63 @@ + + + + + + Year as defined by the Gregorian + calendar. + Mandatory + uint16 + org.bluetooth.unit.time.year + 1582 + 9999 + + + + + + Month of the year as defined by the + Gregorian calendar. + Mandatory + uint8 + org.bluetooth.unit.time.month + 0 + 12 + + + + + + + + + + + + + + + + + + Day of the month as defined by the Gregorian + calendar. + Mandatory + uint8 + org.bluetooth.unit.time.day + 1 + 31 + + + + + + +

The fields in the above table are in the order of LSO to + MSO. Where LSO = Least Significant Octet and MSO = Most + Significant Octet.

+ + diff --git a/org.bluetooth.characteristic.date_time.xml b/org.bluetooth.characteristic.date_time.xml new file mode 100644 index 0000000..15a2d18 --- /dev/null +++ b/org.bluetooth.characteristic.date_time.xml @@ -0,0 +1,95 @@ + + + + + The Date Time characteristic is used to represent + time. + The Date Time characteristic contains fields for year, + month, day, hours, minutes and seconds. Calendar days in Date + Time are represented using Gregorian calendar. Hours in Date + Time are represented in the 24h system. + + + + Year as defined by the Gregorian + calendar. + Mandatory + uint16 + org.bluetooth.unit.time.year + 1582 + 9999 + + + + + + Month of the year as defined by the + Gregorian calendar. + Mandatory + uint8 + org.bluetooth.unit.time.month + 0 + 12 + + + + + + + + + + + + + + + + + + Day of the month as defined by the Gregorian + calendar. + Mandatory + uint8 + org.bluetooth.unit.time.day + 1 + 31 + + + + + + Number of hours past + midnight. + Mandatory + uint8 + org.bluetooth.unit.time.hour + 0 + 23 + + + Number of minutes since the start of the + hour. + Mandatory + uint8 + org.bluetooth.unit.time.minute + 0 + 59 + + + Number of seconds since the start of the + minute. + Mandatory + uint8 + org.bluetooth.unit.time.second + 0 + 59 + + + The fields in the above table are in the order of LSO to + MSO. Where LSO = Least Significant Octet and MSO = Most + Significant Octet. + diff --git a/org.bluetooth.characteristic.day_date_time.xml b/org.bluetooth.characteristic.day_date_time.xml new file mode 100644 index 0000000..7a8c8be --- /dev/null +++ b/org.bluetooth.characteristic.day_date_time.xml @@ -0,0 +1,22 @@ + + + + + + + Mandatory + org.bluetooth.characteristic.date_time + + + Mandatory + + org.bluetooth.characteristic.day_of_week + + + The fields in the above table are in the order of LSO to + MSO. Where LSO = Least Significant Octet and MSO = Most + Significant Octet. + diff --git a/org.bluetooth.characteristic.day_of_week.xml b/org.bluetooth.characteristic.day_of_week.xml new file mode 100644 index 0000000..074a03a --- /dev/null +++ b/org.bluetooth.characteristic.day_of_week.xml @@ -0,0 +1,29 @@ + + + + + + + Mandatory + uint8 + org.bluetooth.unit.time.day + 0 + 7 + + + + + + + + + + + + + + + diff --git a/org.bluetooth.characteristic.descriptor_value_changed.xml b/org.bluetooth.characteristic.descriptor_value_changed.xml new file mode 100644 index 0000000..814d748 --- /dev/null +++ b/org.bluetooth.characteristic.descriptor_value_changed.xml @@ -0,0 +1,11 @@ + + + + This definition is shown in the Environmental + Sensing Service Section 3.2 and its + subsections. + diff --git a/org.bluetooth.characteristic.dew_point.xml b/org.bluetooth.characteristic.dew_point.xml new file mode 100644 index 0000000..d06abea --- /dev/null +++ b/org.bluetooth.characteristic.dew_point.xml @@ -0,0 +1,18 @@ + + + + + + Unit is in degrees celsius with a resolution + of 1 degree Celsius + Mandatory + sint8 + + org.bluetooth.unit.thermodynamic_temperature.degree_celsius + 0 + + + diff --git a/org.bluetooth.characteristic.digital.xml b/org.bluetooth.characteristic.digital.xml new file mode 100644 index 0000000..cc8eef5 --- /dev/null +++ b/org.bluetooth.characteristic.digital.xml @@ -0,0 +1,31 @@ + + + + + The Digital characteristic is used to expose and + change the state of an IO Module?s digital signals. + + + + The Digital characteristic is an array of n + 2-bit values in a bit field + Mandatory + 2bit + + + + + + + true + + + +

The Octet Order in the above table is in the order of LSO to + MSO, where LSO = Least Significant Octet and MSO = Most + Significant Octet.

+ + diff --git a/org.bluetooth.characteristic.dst_offset.xml b/org.bluetooth.characteristic.dst_offset.xml new file mode 100644 index 0000000..4300859 --- /dev/null +++ b/org.bluetooth.characteristic.dst_offset.xml @@ -0,0 +1,30 @@ + + + + + + + Mandatory + uint8 + 0 + 8 + + + + + + + + + + + + + + + + diff --git a/org.bluetooth.characteristic.elevation.xml b/org.bluetooth.characteristic.elevation.xml new file mode 100644 index 0000000..2f1ad9e --- /dev/null +++ b/org.bluetooth.characteristic.elevation.xml @@ -0,0 +1,17 @@ + + + + + + Unit is in meters with a resolution of 0.01 + m + Mandatory + sint24 + org.bluetooth.unit.length.meter + -2 + + + diff --git a/org.bluetooth.characteristic.email_address.xml b/org.bluetooth.characteristic.email_address.xml new file mode 100644 index 0000000..a3e464b --- /dev/null +++ b/org.bluetooth.characteristic.email_address.xml @@ -0,0 +1,23 @@ + + + + + Email address of the user. See Note below. + + + + Mandatory + utf8s + org.bluetooth.unit.unitless + + + +

The length of the utf8s-based UDS Characteristic is variable + and may exceed the default ATT_MTU defined in the Core + Specification.

+ + diff --git a/org.bluetooth.characteristic.exact_time_256.xml b/org.bluetooth.characteristic.exact_time_256.xml new file mode 100644 index 0000000..379aa35 --- /dev/null +++ b/org.bluetooth.characteristic.exact_time_256.xml @@ -0,0 +1,27 @@ + + + + + + + Reference the Time + Characteristic + Mandatory + + org.bluetooth.characteristic.day_date_time + + + 1/256th of a second + Mandatory + uint8 + 0 + 255 + + + The fields in the above table are in the order of LSO to + MSO. Where LSO = Least Significant Octet and MSO = Most + Significant Octet. + diff --git a/org.bluetooth.characteristic.fat_burn_heart_rate_lower_limit.xml b/org.bluetooth.characteristic.fat_burn_heart_rate_lower_limit.xml new file mode 100644 index 0000000..f2203b6 --- /dev/null +++ b/org.bluetooth.characteristic.fat_burn_heart_rate_lower_limit.xml @@ -0,0 +1,22 @@ + + + + + Lower limit of the heart rate where the user + maximizes the fat burn while exersizing + + + + Unit is in beats per minute with a + resolution of 1 + Mandatory + uint8 + org.bluetooth.unit.period.beats_per_minute + 0 + + + diff --git a/org.bluetooth.characteristic.fat_burn_heart_rate_upper_limit.xml b/org.bluetooth.characteristic.fat_burn_heart_rate_upper_limit.xml new file mode 100644 index 0000000..efb9f44 --- /dev/null +++ b/org.bluetooth.characteristic.fat_burn_heart_rate_upper_limit.xml @@ -0,0 +1,22 @@ + + + + + Upper limit of the heart rate where the user + maximizes the fat burn while exersizing + + + + Unit is in beats per minute with a + resolution of 1 + Mandatory + uint8 + org.bluetooth.unit.period.beats_per_minute + 0 + + + diff --git a/org.bluetooth.characteristic.firmware_revision_string.xml b/org.bluetooth.characteristic.firmware_revision_string.xml new file mode 100644 index 0000000..2a5449e --- /dev/null +++ b/org.bluetooth.characteristic.firmware_revision_string.xml @@ -0,0 +1,19 @@ + + + + + The value of this characteristic is a UTF-8 string + representing the firmware revision for the firmware within the + device. + + + + Mandatory + utf8s + + + diff --git a/org.bluetooth.characteristic.first_name.xml b/org.bluetooth.characteristic.first_name.xml new file mode 100644 index 0000000..6de411b --- /dev/null +++ b/org.bluetooth.characteristic.first_name.xml @@ -0,0 +1,22 @@ + + + + + First name of the user. See Note below. + + + + Mandatory + utf8s + org.bluetooth.unit.unitless + + + +

The length of the utf8s-based UDS Characteristics is + variable and may exceed the default ATT_MTU defined in the Core + Specification.

+ + diff --git a/org.bluetooth.characteristic.fitness_machine_control_point.xml b/org.bluetooth.characteristic.fitness_machine_control_point.xml new file mode 100644 index 0000000..0e68404 --- /dev/null +++ b/org.bluetooth.characteristic.fitness_machine_control_point.xml @@ -0,0 +1,12 @@ + + + + + The Fitness Machine Control Point characteristic is + defined in the Fitness Machine Service Specification. + + diff --git a/org.bluetooth.characteristic.fitness_machine_feature.xml b/org.bluetooth.characteristic.fitness_machine_feature.xml new file mode 100644 index 0000000..3b5bdd2 --- /dev/null +++ b/org.bluetooth.characteristic.fitness_machine_feature.xml @@ -0,0 +1,12 @@ + + + + + The Fitness Machine Feature characteristic is defined + in the Fitness Machine Service Specification. + + diff --git a/org.bluetooth.characteristic.fitness_machine_status.xml b/org.bluetooth.characteristic.fitness_machine_status.xml new file mode 100644 index 0000000..5a1af23 --- /dev/null +++ b/org.bluetooth.characteristic.fitness_machine_status.xml @@ -0,0 +1,12 @@ + + + + + The Fitness Machine Status characteristic is defined + in the Fitness Machine Service Specification. + + diff --git a/org.bluetooth.characteristic.five_zone_heart_rate_limits.xml b/org.bluetooth.characteristic.five_zone_heart_rate_limits.xml new file mode 100644 index 0000000..e9102f7 --- /dev/null +++ b/org.bluetooth.characteristic.five_zone_heart_rate_limits.xml @@ -0,0 +1,56 @@ + + + + + Data structure containing the limits between the + heart rate zones for the 5-zone heart rate definition (Maximum, + Hard, Moderate, Light and Very Light). + + + + + Unit is in beats per minute with a + resolution of 1 + Mandatory + uint8 + org.bluetooth.unit.period.beats_per_minute + 0 + + + + Unit is in beats per minute with a + resolution of 1 + Mandatory + uint8 + org.bluetooth.unit.period.beats_per_minute + 0 + + + + Unit is in beats per minute with a + resolution of 1 + Mandatory + uint8 + org.bluetooth.unit.period.beats_per_minute + 0 + + + + Unit is in beats per minute with a + resolution of 1 + Mandatory + uint8 + org.bluetooth.unit.period.beats_per_minute + 0 + + + +

The fields in the above table are in the order of LSO to + MSO. Where LSO = Least Significant Octet and MSO = Most + Significant Octet.

+ + diff --git a/org.bluetooth.characteristic.floor_number.xml b/org.bluetooth.characteristic.floor_number.xml new file mode 100644 index 0000000..3056a39 --- /dev/null +++ b/org.bluetooth.characteristic.floor_number.xml @@ -0,0 +1,17 @@ + + + + + The Floor Number characteristic describes in which + floor the device is installed. + + + + Mandatory + uint8 + + + diff --git a/org.bluetooth.characteristic.gap.appearance.xml b/org.bluetooth.characteristic.gap.appearance.xml new file mode 100644 index 0000000..2881290 --- /dev/null +++ b/org.bluetooth.characteristic.gap.appearance.xml @@ -0,0 +1,147 @@ + + + + + The external appearance of this device. The values + are composed of a category (10-bits) and sub-categories + (6-bits). + + + + + Mandatory + 16bit + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/org.bluetooth.characteristic.gap.central_address_resolution_support.xml b/org.bluetooth.characteristic.gap.central_address_resolution_support.xml new file mode 100644 index 0000000..55ac146 --- /dev/null +++ b/org.bluetooth.characteristic.gap.central_address_resolution_support.xml @@ -0,0 +1,38 @@ + + + + + + + + + The Peripheral checks if the peer device supports + address resolution by reading the Central Address Resolution + characteristic before using directed advertisement where the + initiator address is set to a Resolvable Private Address + (RPA). + + + + Mandatory + uint8 + + + + + + + + +

A device has only one instance of the Central Address + Resolution characteristic. If the Central Address Resolution + characteristic is not present, then it is assumed that Central + Address Resolution is not supported.

+ + diff --git a/org.bluetooth.characteristic.gap.device_name.xml b/org.bluetooth.characteristic.gap.device_name.xml new file mode 100644 index 0000000..eb17324 --- /dev/null +++ b/org.bluetooth.characteristic.gap.device_name.xml @@ -0,0 +1,20 @@ + + + + + + + + + + + + Mandatory + utf8s + + + diff --git a/org.bluetooth.characteristic.gap.peripheral_preferred_connection_parameters.xml b/org.bluetooth.characteristic.gap.peripheral_preferred_connection_parameters.xml new file mode 100644 index 0000000..7276ba7 --- /dev/null +++ b/org.bluetooth.characteristic.gap.peripheral_preferred_connection_parameters.xml @@ -0,0 +1,55 @@ + + + + + + + + + + + + connInterval_min = Minimum Connection + Interval * 1.25 ms + Mandatory + uint16 + 6 + 3200 + + + + + + connInterval_max = Maximum Connection + Interval * 1.25 ms. and is equal or greater than the Minimum + Connection Interval + Mandatory + uint16 + 6 + 3200 + + + + + + Mandatory + uint16 + 0 + 1000 + + + Mandatory + uint16 + 10 + 3200 + + + + + + diff --git a/org.bluetooth.characteristic.gap.peripheral_privacy_flag.xml b/org.bluetooth.characteristic.gap.peripheral_privacy_flag.xml new file mode 100644 index 0000000..17727f0 --- /dev/null +++ b/org.bluetooth.characteristic.gap.peripheral_privacy_flag.xml @@ -0,0 +1,26 @@ + + + + + + + + + + + + Mandatory + boolean + + + + + + + diff --git a/org.bluetooth.characteristic.gap.reconnection_address.xml b/org.bluetooth.characteristic.gap.reconnection_address.xml new file mode 100644 index 0000000..21864c5 --- /dev/null +++ b/org.bluetooth.characteristic.gap.reconnection_address.xml @@ -0,0 +1,21 @@ + + + + + The Information included in this page is informative. + The normative descriptions are contained in the applicable + specification. + + + + This is a non-resolvable private + address + Mandatory + uint48 + + + diff --git a/org.bluetooth.characteristic.gatt.service_changed.xml b/org.bluetooth.characteristic.gatt.service_changed.xml new file mode 100644 index 0000000..5bdb1db --- /dev/null +++ b/org.bluetooth.characteristic.gatt.service_changed.xml @@ -0,0 +1,28 @@ + + + + + + + + + + + + Mandatory + uint16 + 1 + 65535 + + + Mandatory + uint16 + 1 + 65535 + + + diff --git a/org.bluetooth.characteristic.gender.xml b/org.bluetooth.characteristic.gender.xml new file mode 100644 index 0000000..1723285 --- /dev/null +++ b/org.bluetooth.characteristic.gender.xml @@ -0,0 +1,24 @@ + + + + + Gender of the user. The value of the Gender + characteristic are defined below: 0:male,1:female, + 2:Unspecified,3-225: RFU + + + + Mandatory + uint8 + + + + + + + + + diff --git a/org.bluetooth.characteristic.glucose_feature.xml b/org.bluetooth.characteristic.glucose_feature.xml new file mode 100644 index 0000000..670bd27 --- /dev/null +++ b/org.bluetooth.characteristic.glucose_feature.xml @@ -0,0 +1,99 @@ + + + + + + The Glucose Feature characteristic is used to describe + the supported features of the Server. When read, the Glucose + Feature characteristic returns a value that is used by a Client + to determine the supported features of the Server. + + + + Mandatory + 16bit + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/org.bluetooth.characteristic.glucose_measurement.xml b/org.bluetooth.characteristic.glucose_measurement.xml new file mode 100644 index 0000000..81a5815 --- /dev/null +++ b/org.bluetooth.characteristic.glucose_measurement.xml @@ -0,0 +1,247 @@ + + + + + + The Glucose Measurement characteristic is a variable + length structure containing a Flags field, a Sequence Number + field, a Base Time field and, based upon the contents of the + Flags field, may contain a Time Offset field, Glucose + Concentration field, Type-Sample Location field and a Sensor + Status Annunciation field. + + + + These flags define which data fields are + present in the Characteristic value + Mandatory + 8bit + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Mandatory + uint16 + + + Mandatory + org.bluetooth.characteristic.date_time + + + C1: Field exists if the key of bit 0 of the + Flags field is set to 1 + C1 + sint16 + org.bluetooth.unit.time.minute + + + + C2: Field exists if the key of bit 1 of the + Flags field is set to 1, C3: Field exists if the key of bit 2 + of the Flags field is set to 0 + C2 + C3 + SFLOAT + + org.bluetooth.unit.mass_density.kilogram_per_litre + + + C2: Field exists if the key of bit 1 of the + Flags field is set to 1, C4: Field exists if the key of bit 2 + of the Flags field is set to 1 + C2 + C4 + SFLOAT + org.bluetooth.unit.mass_density.mole_per_litre + + + C2: Field exists if the key of bit 1 of the + Flags field is set to 1 + C2 + nibble + + + + + + + + + + + + + + + + + C2: Field exists if the key of bit 1 of the + Flags field is set to 1 + C2 + nibble + + + + + + + + + + + + C5: Field exists if the key of bit 3 of the + Flags field is set to 1 + C5 + 16bit + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + The fields in the above table, reading from top to bottom, + are shown in the order of LSO to MSO, where LSO = Least + Significant Octet and MSO = Most Significant Octet. +

Where fields with the format ?nibble? have been defined in the + above table, the fields are shown in the order of Least + Significant Nibble first, when reading the table from top to + bottom. Where the characteristic definition contains two adjacent + nibbles and the service specification has defined that that pair + of nibbles comprise a single octet, the Least Significant Nibble + means the four bits numbered 0, 1, 2 and 3 of the octet and the + Most Significant Nibble means the four bits numbered 4, 5, 6 and + 7 of that octet.

 + diff --git a/org.bluetooth.characteristic.glucose_measurement_context.xml b/org.bluetooth.characteristic.glucose_measurement_context.xml new file mode 100644 index 0000000..afd9581 --- /dev/null +++ b/org.bluetooth.characteristic.glucose_measurement_context.xml @@ -0,0 +1,236 @@ + + + + + + The Glucose Measurement Context characteristic is a + variable length structure containing a Flags field, a Sequence + Number field and, based upon the contents of the Flags field, + may contain a Carbohydrate ID field, Carbohydrate field, Meal + field, Tester-Health field, Exercise Duration field, Exercise + Intensity field, Medication ID field, Medication field and a + HbA1c field. + + + + These flags define which data fields are + present in the Characteristic value + Mandatory + 8bit + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Mandatory + uint16 + + + C1: Field exists if the key of bit 7 of the + Flags field is set to 1 + C1 + 8bit + + + + + + C2: Field exists if the key of bit 0 of the + Flags field is set to 1 + C2 + uint8 + + + + + + + + + + + + + + C2: Field exists if the key of bit 0 of the + Flags field is set to 1 + C2 + SFLOAT + org.bluetooth.unit.mass.kilogram + -3 + + + C3: Field exists if the key of bit 1 of the + Flags field is set to 1 + C3 + uint8 + + + + + + + + + + + + C4: Field exists if the key of bit 2 of the + Flags field is set to 1 + C4 + nibble + + + + + + + + + + + C4: Field exists if the key of bit 2 of the + Flags field is set to 1 + C4 + nibble + + + + + + + + + + + + + C5: Field exists if the key of bit 3 of the + Flags field is set to 1 + C5 + uint16 + org.bluetooth.unit.time.second + + + + + + + C5: Field exists if the key of bit 3 of the + Flags field is set to 1 + C5 + uint8 + org.bluetooth.unit.percentage + + + C6: Field exists if the key of bit 4 of the + Flags field is set to 1 + C6 + uint8 + + + + + + + + + + + + C6: Field exists if the key of bit 4 of the + Flags field is set to 1, C8: Field exists if the key of bit 5 + of the Flags field is set to 0 + C6 + C8 + SFLOAT + org.bluetooth.unit.mass.kilogram + -6 + + + C6: Field exists if the key of bit 4 of the + Flags field is set to 1, C9: Field exists if the key of bit 5 + of the Flags field is set to 1 + C6 + C9 + SFLOAT + org.bluetooth.unit.volume.litre + -3 + + + C7: Field exists if the key of bit 6 of the + Flags field is set to 1 + C7 + SFLOAT + org.bluetooth.unit.percentage + + + The fields in the above table, reading from top to bottom, + are shown in the order of LSO to MSO, where LSO = Least + Significant Octet and MSO = Most Significant Octet. +

Where fields with the format ?nibble? have been defined in the + above table, the fields are shown in the order of Least + Significant Nibble first, when reading the table from top to + bottom. Where the characteristic definition contains two adjacent + nibbles and the service specification has defined that that pair + of nibbles comprise a single octet, the Least Significant Nibble + means the four bits numbered 0, 1, 2 and 3 of the octet and the + Most Significant Nibble means the four bits numbered 4, 5, 6 and + 7 of that octet.

 + diff --git a/org.bluetooth.characteristic.gust_factor.xml b/org.bluetooth.characteristic.gust_factor.xml new file mode 100644 index 0000000..1aaf666 --- /dev/null +++ b/org.bluetooth.characteristic.gust_factor.xml @@ -0,0 +1,19 @@ + + + + + + + The factor has a fixed-point representation, + where the actual factor is (attribute value * + 0.1) + Mandatory + uint8 + org.bluetooth.unit.unitless + -1 + + + diff --git a/org.bluetooth.characteristic.hardware_revision_string.xml b/org.bluetooth.characteristic.hardware_revision_string.xml new file mode 100644 index 0000000..55320d9 --- /dev/null +++ b/org.bluetooth.characteristic.hardware_revision_string.xml @@ -0,0 +1,19 @@ + + + + + The value of this characteristic is a UTF-8 string + representing the hardware revision for the hardware within the + device. + + + + Mandatory + utf8s + + + diff --git a/org.bluetooth.characteristic.heart_rate_control_point.xml b/org.bluetooth.characteristic.heart_rate_control_point.xml new file mode 100644 index 0000000..6bf578a --- /dev/null +++ b/org.bluetooth.characteristic.heart_rate_control_point.xml @@ -0,0 +1,20 @@ + + + + + + + Mandatory + 8bit + + + + + + + + diff --git a/org.bluetooth.characteristic.heart_rate_max.xml b/org.bluetooth.characteristic.heart_rate_max.xml new file mode 100644 index 0000000..eea1d8d --- /dev/null +++ b/org.bluetooth.characteristic.heart_rate_max.xml @@ -0,0 +1,21 @@ + + + + + Maximum heart rate a user can reach. + + + + Unit is in beats per minute with a + resolution of 1. + Mandatory + uint8 + org.bluetooth.unit.period.beats_per_minute + 0 + + + diff --git a/org.bluetooth.characteristic.heart_rate_measurement.xml b/org.bluetooth.characteristic.heart_rate_measurement.xml new file mode 100644 index 0000000..77ba8b5 --- /dev/null +++ b/org.bluetooth.characteristic.heart_rate_measurement.xml @@ -0,0 +1,106 @@ + + + + + + + Mandatory + 8bit + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Note: The format of the Heart Rate + Measurement Value field is dependent upon bit 0 of the Flags + field. + C1 + uint8 + org.bluetooth.unit.period.beats_per_minute + + + Note: The format of the Heart Rate + Measurement Value field is dependent upon bit 0 of the Flags + field. + C2 + uint16 + org.bluetooth.unit.period.beats_per_minute + + + The presence of the Energy Expended field is + dependent upon bit 3 of the Flags field. + C3 + uint16 + org.bluetooth.unit.energy.joule + + + + + + C4 + uint16 + org.bluetooth.unit.time.second + Resolution of 1/1024 second + + + +

The fields in the above table are in the order of LSO to + MSO. Where LSO = Least Significant Octet and MSO = Most + Significant Octet.

+ + diff --git a/org.bluetooth.characteristic.heat_index.xml b/org.bluetooth.characteristic.heat_index.xml new file mode 100644 index 0000000..8c7758f --- /dev/null +++ b/org.bluetooth.characteristic.heat_index.xml @@ -0,0 +1,18 @@ + + + + + + Unit is in degrees celsius with a resolution + of 1 degree Celsius + Mandatory + sint8 + + org.bluetooth.unit.thermodynamic_temperature.degree_celsius + 0 + + + diff --git a/org.bluetooth.characteristic.height.xml b/org.bluetooth.characteristic.height.xml new file mode 100644 index 0000000..3d6a1c8 --- /dev/null +++ b/org.bluetooth.characteristic.height.xml @@ -0,0 +1,20 @@ + + + + + Height of the User + + + + Unit is in meters with a resolution of 0.01 + . + Mandatory + uint16 + org.bluetooth.unit.length.meter + -2 + + + diff --git a/org.bluetooth.characteristic.hid_control_point.xml b/org.bluetooth.characteristic.hid_control_point.xml new file mode 100644 index 0000000..7fb4459 --- /dev/null +++ b/org.bluetooth.characteristic.hid_control_point.xml @@ -0,0 +1,29 @@ + + + + + The HID Control Point characteristic is a + control-point attribute that defines the following HID Commands + when written: +

? Suspend ( Refer to Section 7.4.2, Bluetooth HID Profile + Specification 1.0

+

? Exit Suspend (Refer to Section 7.4.2, Bluetooth HID + Profile Specification 1.0

 + + + + There are no response codes defined for the + Suspend and Exit Suspend commands. + Mandatory + uint8 + + + + + + + + diff --git a/org.bluetooth.characteristic.hid_information.xml b/org.bluetooth.characteristic.hid_information.xml new file mode 100644 index 0000000..e49374c --- /dev/null +++ b/org.bluetooth.characteristic.hid_information.xml @@ -0,0 +1,58 @@ + + + + + The HID Information Characteristic returns the HID + attributes when read. + The HID Information Characteristic contains the HID + attributes. The value of this Characteristic is static and can + be cached for the lifetime of the bond between the HID device + and the HID host. + + + + 16-bit unsigned integer representing version + number of base USB HID Specification implemented by HID + Device + Mandatory + uint16 + + + Identifies which country the hardware is + localized for. Most hardware is not localized and thus this + value would be zero (0). + Mandatory + 8bit + + + Mandatory + 8bit + + + + + + + + + + + + + + + + + + + The fields in the above table are in the order of LSO to + MSO. Where LSO = Least Significant Octet and MSO = Most + Significant Octet. + diff --git a/org.bluetooth.characteristic.hip_circumference.xml b/org.bluetooth.characteristic.hip_circumference.xml new file mode 100644 index 0000000..4836a97 --- /dev/null +++ b/org.bluetooth.characteristic.hip_circumference.xml @@ -0,0 +1,22 @@ + + + + + Used with the Waist Circumference value to calculate + the Waist to Hip Ratio (WHR) + + + + Unit is in meters with a resoluton of + 0.01 + Mandatory + uint16 + org.bluetooth.unit.length.meter + -2 + + + diff --git a/org.bluetooth.characteristic.http_control_point.xml b/org.bluetooth.characteristic.http_control_point.xml new file mode 100644 index 0000000..2c71811 --- /dev/null +++ b/org.bluetooth.characteristic.http_control_point.xml @@ -0,0 +1,57 @@ + + + + + The HTTP Control Point is used to initiate a request + to send an HTTP request message from the device contgaining the + HTTP Proxy Service, acting as an HTTP Client, and an HTTP + Server. + + + + Mandatory + uint8 + + + + + + + + + + + + + + + + + + diff --git a/org.bluetooth.characteristic.http_entity_body.xml b/org.bluetooth.characteristic.http_entity_body.xml new file mode 100644 index 0000000..e40826f --- /dev/null +++ b/org.bluetooth.characteristic.http_entity_body.xml @@ -0,0 +1,21 @@ + + + + + The HTTP Entity Body Characteristic contains the + contents of the message body after any Transfer Encoding has + been applied. + + + + The HTTP entity body used in the HTTP + request. + Mandatory + utf8s + + + diff --git a/org.bluetooth.characteristic.http_headers.xml b/org.bluetooth.characteristic.http_headers.xml new file mode 100644 index 0000000..748a583 --- /dev/null +++ b/org.bluetooth.characteristic.http_headers.xml @@ -0,0 +1,22 @@ + + + + + The HTTP Headers Characteristic is used to hold the + headers that would be sent to the HTTP Request or the headers + contained within an HTTP response message from the HTTP + Server. + + + + The HTTP headers to be used in the HTTP + request. + Mandatory + utf8s + + + diff --git a/org.bluetooth.characteristic.http_status_code.xml b/org.bluetooth.characteristic.http_status_code.xml new file mode 100644 index 0000000..53df1e0 --- /dev/null +++ b/org.bluetooth.characteristic.http_status_code.xml @@ -0,0 +1,60 @@ + + + + + The HTTP Status Code characteristic contains the + Status-Code from the Status-Line of the first line of the HTTP + Response Message, followed by one octet indicating the Data + Status Bit Field indicating the status of the data + received. + + + + Mandatory + uint16 + + + Mandatory + uint8 + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/org.bluetooth.characteristic.https_security.xml b/org.bluetooth.characteristic.https_security.xml new file mode 100644 index 0000000..0e601c4 --- /dev/null +++ b/org.bluetooth.characteristic.https_security.xml @@ -0,0 +1,25 @@ + + + + + The HTTPS Security characteristic contains the known + authenticity of the HTTPS Server certificate for the + URI. + + + + The known authenticity of the HTTP Server + certificate for the URI. + Mandatory + boolean + + + + + + + diff --git a/org.bluetooth.characteristic.humidity.xml b/org.bluetooth.characteristic.humidity.xml new file mode 100644 index 0000000..2867ebd --- /dev/null +++ b/org.bluetooth.characteristic.humidity.xml @@ -0,0 +1,17 @@ + + + + + + Unit is in percent with a resolution of 0.01 + percent + Mandatory + uint16 + org.bluetooth.unit.percentage + -2 + + + diff --git a/org.bluetooth.characteristic.indoor_bike_data.xml b/org.bluetooth.characteristic.indoor_bike_data.xml new file mode 100644 index 0000000..4c45963 --- /dev/null +++ b/org.bluetooth.characteristic.indoor_bike_data.xml @@ -0,0 +1,219 @@ + + + + + The Indoor Bike Data characteristic is used to send + training-related data to the Client from an indoor bike + (Server). + + + + Mandatory + 16bit + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Kilometer per hour with a resolution of + 0.01 + C1 + uint16 + -2 + org.bluetooth.unit.velocity.kilometre_per_hour + + + Kilometer per hour with a resolution of + 0.01 + C2 + uint16 + -2 + org.bluetooth.unit.velocity.kilometre_per_hour + + + 1/minute with a resolution of + 0.5 + C3 + -1 + uint16 + + org.bluetooth.unit.angular_velocity.revolution_per_minute + + + 1/minute with a resolution of + 0.5 + C4 + -1 + uint16 + + org.bluetooth.unit.angular_velocity.revolution_per_minute + + + Meters with a resolution of + 1 + C5 + uint24 + org.bluetooth.unit.length.metre + + + Unitless with a resolution of + 1 + C6 + sint16 + org.bluetooth.unit.unitless + + + Watts with a resolution of + 1 + C7 + sint16 + org.bluetooth.unit.power.watt + + + Watts with a resolution of + 1 + C8 + sint16 + org.bluetooth.unit.power.watt + + + Kilo Calorie with a resolution of + 1 + C9 + uint16 + org.bluetooth.unit.energy.kilogram_calorie + + + Kilo Calorie with a resolution of + 1 + C9 + uint16 + org.bluetooth.unit.energy.kilogram_calorie + + + Kilo Calorie with a resolution of + 1 + C9 + uint8 + org.bluetooth.unit.energy.kilogram_calorie + + + Beats per minute with a resolution of + 1 + C10 + uint8 + org.bluetooth.unit.period.beats_per_minute + + + Metabolic Equivalent with a resolution of + 0.1 + C11 + uint8 + -1 + org.bluetooth.unit.metabolic_equivalent + + + Second with a resolution of + 1 + C12 + uint16 + org.bluetooth.unit.time.second + + + Second with a resolution of + 1 + C13 + uint16 + org.bluetooth.unit.time.second + + + The fields in the above table, reading from top to bottom, + are shown in the order of LSO to MSO, where LSO = Least + Significant Octet and MSO = Most Significant Octet. The Least + Significant Octet represents the eight bits numbered 0 to + 7. + diff --git a/org.bluetooth.characteristic.indoor_positioning_configuration.xml b/org.bluetooth.characteristic.indoor_positioning_configuration.xml new file mode 100644 index 0000000..8e55890 --- /dev/null +++ b/org.bluetooth.characteristic.indoor_positioning_configuration.xml @@ -0,0 +1,68 @@ + + + + + The Indoor Positioning Configuration describes the + set of characteristic values included in the Indoor Positioning + Service AD type. + + + + Mandatory + uint8 + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/org.bluetooth.characteristic.intermediate_cuff_pressure.xml b/org.bluetooth.characteristic.intermediate_cuff_pressure.xml new file mode 100644 index 0000000..db870b0 --- /dev/null +++ b/org.bluetooth.characteristic.intermediate_cuff_pressure.xml @@ -0,0 +1,21 @@ + + + + This characteristic has the same format as the + Blood Pressure Measurement characteristic. However, due to a + different context, the Blood Pressure Measurement Compound Value + field becomes the Intermediate Cuff Pressure Compound Value + field, the Systolic sub-field becomes the Current Cuff Pressure + sub-field and the Diastolic and MAP fields are + unused. + + + Mandatory + + org.bluetooth.characteristic.blood_pressure_measurement + + + diff --git a/org.bluetooth.characteristic.intermediate_temperature.xml b/org.bluetooth.characteristic.intermediate_temperature.xml new file mode 100644 index 0000000..d348250 --- /dev/null +++ b/org.bluetooth.characteristic.intermediate_temperature.xml @@ -0,0 +1,21 @@ + + + + + The Intermediate Temperature characteristic has the + same format as the Temperature Measurement characteristic. + However, due to a different context, the Value field is + referred to as the Intermediate Temperature Value + field. + + + + Mandatory + + org.bluetooth.characteristic.temperature_measurement + + + diff --git a/org.bluetooth.characteristic.irradiance.xml b/org.bluetooth.characteristic.irradiance.xml new file mode 100644 index 0000000..92edc35 --- /dev/null +++ b/org.bluetooth.characteristic.irradiance.xml @@ -0,0 +1,18 @@ + + + + + + Unit is in watt per square meter with a + resolution of 0.1 W/m^2 + Mandatory + uint16 + + org.bluetooth.unit.irradiance.watt_per_square_metre + -1 + + + diff --git a/org.bluetooth.characteristic.language.xml b/org.bluetooth.characteristic.language.xml new file mode 100644 index 0000000..c943c55 --- /dev/null +++ b/org.bluetooth.characteristic.language.xml @@ -0,0 +1,16 @@ + + + + + + The Language definition is based on + ISO639-1. + Mandatory + utf8s + org.bluetooth.unit.unitless + + + diff --git a/org.bluetooth.characteristic.last_name.xml b/org.bluetooth.characteristic.last_name.xml new file mode 100644 index 0000000..e8969de --- /dev/null +++ b/org.bluetooth.characteristic.last_name.xml @@ -0,0 +1,22 @@ + + + + + Last name of the user. See Note below. + + + + Mandatory + utf8s + org.bluetooth.unit.unitless + + + +

The length of the utf8s-based UDS Characteristic is variable + and may exceed the default ATT_MTU defined in the Core + Specification.

+ + diff --git a/org.bluetooth.characteristic.latitude.xml b/org.bluetooth.characteristic.latitude.xml new file mode 100644 index 0000000..65568f3 --- /dev/null +++ b/org.bluetooth.characteristic.latitude.xml @@ -0,0 +1,17 @@ + + + + + The Latitude characteristic describes the WGS84 North + coordinate of the device. + + + + Mandatory + sint32 + + + diff --git a/org.bluetooth.characteristic.ln_control_point.xml b/org.bluetooth.characteristic.ln_control_point.xml new file mode 100644 index 0000000..97749e9 --- /dev/null +++ b/org.bluetooth.characteristic.ln_control_point.xml @@ -0,0 +1,99 @@ + + + + + + + The LN Control Point characteristic is used to request + a specific function to be executed on the receiving + device. + + + + Mandatory + uint8 + + + + + + + + + + + + + + + + + + Optional + variable + Defined per Service specification. + + + The Request Op Code is a sub field of the + Parameter Value for "Response Code" Op Code. +
C1: This Field is Mandatory for "Response Code" Op Code, + otherwise this field is Excluded.
 + C1 + uint8 + Refer to the Op Code table above for additional + information on the possible values for this + field. + + + The Response Value is a sub field of the + Parameter Value for "Response Code" Op Code +
C1: This Field is Mandatory for "Response Code" Op Code, + otherwise this field is Excluded.
 + C1 + uint8 + + + + + + + + + + + The Response Parameter is a sub field of the + Parameter Value for "Response Code" Op Code. +
C2:This Field is Optional for "Response Code" Op Code, + otherwise this field is Excluded.
 + C2 + variable + Note: The Response Parameter Value of the + response to the Control Point is a variable length field to + allow a list of different values defined by the Service + Specification. + + + The fields in the above table, reading from top to bottom, + are shown in the order of LSO to MSO, where LSO = Least + Significant Octet and MSO = Most Significant Octet. The Least + Significant Octet represents the eight bits numbered 0 to + 7. + diff --git a/org.bluetooth.characteristic.ln_feature.xml b/org.bluetooth.characteristic.ln_feature.xml new file mode 100644 index 0000000..c6ac7d7 --- /dev/null +++ b/org.bluetooth.characteristic.ln_feature.xml @@ -0,0 +1,167 @@ + + + + + + + The LN Feature characteristic is used to report a list + of features supported by the device. + + + + Mandatory + 32bit + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + The fields in the above table, reading from top to bottom, + are shown in the order of LSO to MSO, where LSO = Least + Significant Octet and MSO = Most Significant Octet. The Least + Significant Octet represents the eight bits numbered 0 to + 7. + diff --git a/org.bluetooth.characteristic.local_east_coordinate.xml b/org.bluetooth.characteristic.local_east_coordinate.xml new file mode 100644 index 0000000..0cd2369 --- /dev/null +++ b/org.bluetooth.characteristic.local_east_coordinate.xml @@ -0,0 +1,19 @@ + + + + + The Local East characteristic describes the East + coordinate of the device using local coordinate + system. + + + + Mandatory + sint16 + + + diff --git a/org.bluetooth.characteristic.local_north_coordinate.xml b/org.bluetooth.characteristic.local_north_coordinate.xml new file mode 100644 index 0000000..1b806ad --- /dev/null +++ b/org.bluetooth.characteristic.local_north_coordinate.xml @@ -0,0 +1,19 @@ + + + + + The Local North characteristic describes the North + coordinate of the device using local coordinate + system. + + + + Mandatory + sint16 + + + diff --git a/org.bluetooth.characteristic.local_time_information.xml b/org.bluetooth.characteristic.local_time_information.xml new file mode 100644 index 0000000..82cc2b3 --- /dev/null +++ b/org.bluetooth.characteristic.local_time_information.xml @@ -0,0 +1,22 @@ + + + + + + + Mandatory + org.bluetooth.characteristic.time_zone + + + Mandatory + + org.bluetooth.characteristic.dst_offset + + + The fields in the above table are in the order of LSO to + MSO. Where LSO = Least Significant Octet and MSO = Most + Significant Octet. + diff --git a/org.bluetooth.characteristic.location_and_speed.xml b/org.bluetooth.characteristic.location_and_speed.xml new file mode 100644 index 0000000..203bab6 --- /dev/null +++ b/org.bluetooth.characteristic.location_and_speed.xml @@ -0,0 +1,169 @@ + + + + + + + The Location and Speed characteristic is a variable + length structure containing a Flags field and, based on the + contents of the Flags field, may contain a combination of data + fields listed below. Note that it is possible for this + characteristic to exceed the default LE MTU size. + + + + Mandatory + 16bit + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Unit is in meters per second with a + resolution of 1/100 + Optional + uint16 + org.bluetooth.unit.velocity.metres_per_second + -2 + + + Unit is in meters with a resolution of + 1/10 + Optional + uint24 + org.bluetooth.unit.length.meter + -1 + + + Unit is in degrees with a resolution of + 1/(10^7) +
C1: When present, these fields are always present as a + pair.
 + C1 + sint32 + org.bluetooth.unit.plane_angle.degree + -7 + + + Unit is in degrees with a resolution of + 1/(10^7) +
C1:When present, these fields are always present as a + pair.
 + C1 + sint32 + org.bluetooth.unit.plane_angle.degree + -7 + + + Unit is in meters with a resolution of + 1/100 + Optional + sint24 + org.bluetooth.unit.length.meter + -2 + + + Unit is in degrees with a resolution of + 1/100 + Optional + uint16 + org.bluetooth.unit.plane_angle.degree + -2 + + + Unit is in seconds with a resolution of 1 + second + Optional + uint8 + org.bluetooth.unit.time.second + 0 + + + Smallest units in seconds + Optional + org.bluetooth.characteristic.date_time + + + The fields in the above table, reading from top to bottom, + are shown in the order of LSO to MSO, where LSO = Least + Significant Octet and MSO = Most Significant Octet. The Least + Significant Octet represents the eight bits numbered 0 to + 7. + diff --git a/org.bluetooth.characteristic.location_name.xml b/org.bluetooth.characteristic.location_name.xml new file mode 100644 index 0000000..a6799e1 --- /dev/null +++ b/org.bluetooth.characteristic.location_name.xml @@ -0,0 +1,17 @@ + + + + + The Location Name characteristic describes the name + of the location the device is installed in. + + + + Mandatory + utf8s + + + diff --git a/org.bluetooth.characteristic.longitude.xml b/org.bluetooth.characteristic.longitude.xml new file mode 100644 index 0000000..f17cf40 --- /dev/null +++ b/org.bluetooth.characteristic.longitude.xml @@ -0,0 +1,17 @@ + + + + + The Longitude characteristic describes the WGS84 East + coordinate of the device. + + + + Mandatory + sint32 + + + diff --git a/org.bluetooth.characteristic.magnetic_declination.xml b/org.bluetooth.characteristic.magnetic_declination.xml new file mode 100644 index 0000000..67530ad --- /dev/null +++ b/org.bluetooth.characteristic.magnetic_declination.xml @@ -0,0 +1,24 @@ + + + + + + Unit is in degrees with a resolution of 0.01 + degrees + Mandatory + uint16 + org.bluetooth.unit.plane_angle.degree + The magnetic declination is the angle on the + horizontal plane between the direction of True North + (geographic) and the direction of Magnetic North, measured + clockwise from True North to Magnetic North. + -2 + 0 + 359.99 + + + diff --git a/org.bluetooth.characteristic.manufacturer_name_string.xml b/org.bluetooth.characteristic.manufacturer_name_string.xml new file mode 100644 index 0000000..51cd489 --- /dev/null +++ b/org.bluetooth.characteristic.manufacturer_name_string.xml @@ -0,0 +1,19 @@ + + + + + The value of this characteristic is a UTF-8 string + representing the name of the manufacturer of the + device. + + + + Mandatory + utf8s + + + diff --git a/org.bluetooth.characteristic.maximum_recommended_heart_rate.xml b/org.bluetooth.characteristic.maximum_recommended_heart_rate.xml new file mode 100644 index 0000000..1fbc2f8 --- /dev/null +++ b/org.bluetooth.characteristic.maximum_recommended_heart_rate.xml @@ -0,0 +1,24 @@ + + + + + Maximum recommended heart rate is a threshold that + may be set to limit exertion. The maximum recommended heart + rate is smaller or equal to the maximal heart rate a user can + reach. + + + + The Unit is beats per minute with a + resolution of 1 + Mandatory + uint8 + org.bluetooth.unit.period.beats_per_minute + 0 + + + diff --git a/org.bluetooth.characteristic.measurement_interval.xml b/org.bluetooth.characteristic.measurement_interval.xml new file mode 100644 index 0000000..e4c7584 --- /dev/null +++ b/org.bluetooth.characteristic.measurement_interval.xml @@ -0,0 +1,26 @@ + + + + + The Measurement Interval characteristic defines the + time between measurements. + This characteristic is capable of representing values + from 1 second to 65535 seconds which is equal to 18 hours, 12 + minutes and 15 seconds. + + + + Mandatory + uint16 + org.bluetooth.unit.time.second + 1 + 65535 + + + + + + diff --git a/org.bluetooth.characteristic.model_number_string.xml b/org.bluetooth.characteristic.model_number_string.xml new file mode 100644 index 0000000..26835ae --- /dev/null +++ b/org.bluetooth.characteristic.model_number_string.xml @@ -0,0 +1,20 @@ + + + + + + The value of this characteristic is a UTF-8 string + representing the model number assigned by the device + vendor. + + + + Mandatory + utf8s + + + diff --git a/org.bluetooth.characteristic.navigation.xml b/org.bluetooth.characteristic.navigation.xml new file mode 100644 index 0000000..27d508d --- /dev/null +++ b/org.bluetooth.characteristic.navigation.xml @@ -0,0 +1,120 @@ + + + + + + + The Navigation characteristic is a variable length + structure containing a Flags field, a Bearing field, a Heading + field and, based on the contents of the Flags field, may + contain a combination of data fields listed below. + + + + Mandatory + 16bit + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Unit is in degrees with a resolution of + 1/100 + Mandatory + uint16 + org.bluetooth.unit.plane_angle.degree + -2 + + + Unit is in degrees with a resolution of + 1/100 + Mandatory + uint16 + org.bluetooth.unit.plane_angle.degree + -2 + + + Unit is in meters with a resolution of + 1/10 + Optional + uint24 + org.bluetooth.unit.length.meter + -1 + + + Unit is in meters with a resolution of + 1/100 + Optional + sint24 + org.bluetooth.unit.length.meter + -2 + + + Smallest units in seconds + Optional + org.bluetooth.characteristic.date_time + + + The fields in the above table, reading from top to bottom, + are shown in the order of LSO to MSO, where LSO = Least + Significant Octet and MSO = Most Significant Octet. The Least + Significant Octet represents the eight bits numbered 0 to + 7. + diff --git a/org.bluetooth.characteristic.new_alert.xml b/org.bluetooth.characteristic.new_alert.xml new file mode 100644 index 0000000..9e21d41 --- /dev/null +++ b/org.bluetooth.characteristic.new_alert.xml @@ -0,0 +1,66 @@ + + + + + This characteristic defines the category of the alert + and how many new alerts of that category have occurred in the + server device. Brief text information may also be included for + the last alert in the category. + This characteristic consists of ?Category ID?, + ?uint8?, and ?UTF-8 string? fields. The size of this + characteristic is dynamic because of the variable length text + (?UTF-8?) field. The minimum length of ?UTF-8 string? is 0 + octets and maximum length of ?UTF-8 string? is 18 + octets. + + The value 0x01, 0x04, 0x52, 0x69, 0x63, 0x68, 0x61, + 0x72, 0x64 are interpreted that the server has 4 new email + messages and the last message was sent by + ?Richard?. + + + + + This field shows the category of the new + alert. + Mandatory + + org.bluetooth.characteristic.alert_category_id + + + This field provides the number of new alerts + in the server. + Mandatory + uint8 + 0 + 255 + + + The field provides brief text information + for the last alert. + Optional + utf8s + + + The fields in the above table are in the order of LSO to + MSO. Where LSO = Least Significant Octet and MSO = Most + Significant Octet. + Recommended Usage for Text String Information Field in New + Incoming Alert: +

The usage of this text is up to the implementation, but the + recommended text for the category is defined as following for + best user experience:

+

Category: Simple Alert - The title of the alert

+

Category: Email - Sender name

+

Category: News - Title of the news feed

+

Category: Call - Caller name or caller ID

+

Category: Missed call - Caller name or caller ID

+

Category: SMS - Sender name or caller ID

+

Category: Voice mail - Sender name or caller ID

+

Category: Schedule - Title of the schedule

+

Category Hig:h Prioritized Aler - Title of the alert

+

Category: Instant Messaging - Sender name

 + diff --git a/org.bluetooth.characteristic.object_action_control_point.xml b/org.bluetooth.characteristic.object_action_control_point.xml new file mode 100644 index 0000000..108ed5e --- /dev/null +++ b/org.bluetooth.characteristic.object_action_control_point.xml @@ -0,0 +1,11 @@ + + + + The Object Action Control Point (OACP) + characteristic is defined in the Object Transfer Service Section + 3.3 and its sub-sections. + diff --git a/org.bluetooth.characteristic.object_changed.xml b/org.bluetooth.characteristic.object_changed.xml new file mode 100644 index 0000000..cb5e3f0 --- /dev/null +++ b/org.bluetooth.characteristic.object_changed.xml @@ -0,0 +1,11 @@ + + + + The Object Changed characteristic is defined in + the Object Transfer Service Section 3.6 and its + sub-sections. + diff --git a/org.bluetooth.characteristic.object_first_created.xml b/org.bluetooth.characteristic.object_first_created.xml new file mode 100644 index 0000000..285286c --- /dev/null +++ b/org.bluetooth.characteristic.object_first_created.xml @@ -0,0 +1,20 @@ + + + + + + Mandatory + org.bluetooth.characteristic.date_time + + + +

The fields in the above table, reading from top to bottom, + are shown in the order of LSO to MSO, where LSO = Least + Significant Octet and MSO = Most Significant Octet. Data Type: + Same format as the Date Time characteristic

+ + diff --git a/org.bluetooth.characteristic.object_id.xml b/org.bluetooth.characteristic.object_id.xml new file mode 100644 index 0000000..c57a8b3 --- /dev/null +++ b/org.bluetooth.characteristic.object_id.xml @@ -0,0 +1,25 @@ + + + + + + Mandatory + uint48 + 0 + + + + + + + + +

The fields in the above table, reading from top to bottom, + are shown in the order of LSO to MSO, where LSO = Least + Significant Octet and MSO = Most Significant Octet.

+ + diff --git a/org.bluetooth.characteristic.object_last_modified.xml b/org.bluetooth.characteristic.object_last_modified.xml new file mode 100644 index 0000000..5a4dd0b --- /dev/null +++ b/org.bluetooth.characteristic.object_last_modified.xml @@ -0,0 +1,20 @@ + + + + + + Mandatory + org.bluetooth.characteristic.date_time + + + +

The fields in the above table, reading from top to bottom, + are shown in the order of LSO to MSO, where LSO = Least + Significant Octet and MSO = Most Significant Octet. Data Type: + Same format as the Date Time characteristic

+ + diff --git a/org.bluetooth.characteristic.object_list_control_point.xml b/org.bluetooth.characteristic.object_list_control_point.xml new file mode 100644 index 0000000..9b9aafa --- /dev/null +++ b/org.bluetooth.characteristic.object_list_control_point.xml @@ -0,0 +1,11 @@ + + + + The Object List Control Point (OLCP) + characteristic is defined in the Object Transfer Service Section + 3.4 and its sub-sections. + diff --git a/org.bluetooth.characteristic.object_list_filter.xml b/org.bluetooth.characteristic.object_list_filter.xml new file mode 100644 index 0000000..572fb30 --- /dev/null +++ b/org.bluetooth.characteristic.object_list_filter.xml @@ -0,0 +1,11 @@ + + + + The Object List Filter characteristic is defined + in the Object Transfer Service Section 3.5 and its + sub-sections. + diff --git a/org.bluetooth.characteristic.object_name.xml b/org.bluetooth.characteristic.object_name.xml new file mode 100644 index 0000000..8ba91af --- /dev/null +++ b/org.bluetooth.characteristic.object_name.xml @@ -0,0 +1,31 @@ + + + + + + The length of the field value is variable + from 0 octets to 120 octets. + Mandatory + utf8s + The length of the field value is variable from 0 + octets to 120 octets. + 0 + + + +

Characters which require more than one octet when encoded in + UTF-8 are transmitted with the leading byte first, followed by + the continuation bytes ordered in accordance with UTF-8 + encoding. In UTF-8, the leading byte is identified by + possessing two or more high-order 1?s followed by a 0 while + continuation bytes all have '10' in the high-order position. + Strings which consist of more than one character are + transmitted in the following order: the character which appears + furthest to the left when the string is presented in its + written form shall be sent first, followed by the remaining + characters in order.

+ + diff --git a/org.bluetooth.characteristic.object_properties.xml b/org.bluetooth.characteristic.object_properties.xml new file mode 100644 index 0000000..8ec0bdf --- /dev/null +++ b/org.bluetooth.characteristic.object_properties.xml @@ -0,0 +1,10 @@ + + + + The Object Properties characteristic is defined + in the Object Transfer Service Section 3.2.8 + diff --git a/org.bluetooth.characteristic.object_size.xml b/org.bluetooth.characteristic.object_size.xml new file mode 100644 index 0000000..ad878d8 --- /dev/null +++ b/org.bluetooth.characteristic.object_size.xml @@ -0,0 +1,24 @@ + + + + + + Mandatory + uint32 + 0 + + + Mandatory + uint32 + 0 + + + +

The fields in the above table, reading from top to bottom, + are shown in the order of LSO to MSO, where LSO = Least + Significant Octet and MSO = Most Significant Octet.

+ + diff --git a/org.bluetooth.characteristic.object_type.xml b/org.bluetooth.characteristic.object_type.xml new file mode 100644 index 0000000..954a48e --- /dev/null +++ b/org.bluetooth.characteristic.object_type.xml @@ -0,0 +1,32 @@ + + + + + + Refer to note below for 16-bit + values + Mandatory + gatt_uuid + + 0 + + + +

The fields in the above table, reading from top to bottom, + are shown in the order of LSO to MSO, where LSO = Least + Significant Octet and MSO = Most Significant Octet.

+ + +

Description: Unspecified Object Type, 16-bit UUID: << + Unspecified Object Type >>

+

Description: Firmware, 16-bit UUID: << Firmware + >>

+

Description: Route Object in GPS eXchange Format v1.1, + 16-bit UUID: << Route GPX >>

+

Description: Track Object in GPS eXchange Format v1.1, + 16-bit UUID: << Track GPX >>

+ + diff --git a/org.bluetooth.characteristic.ots_feature.xml b/org.bluetooth.characteristic.ots_feature.xml new file mode 100644 index 0000000..a4e382d --- /dev/null +++ b/org.bluetooth.characteristic.ots_feature.xml @@ -0,0 +1,10 @@ + + + + The OTS Feature characteristic is defined in the + Object Transfer Service Section 3.1 and its + sub-sections. + diff --git a/org.bluetooth.characteristic.plx_continuous_measurement.xml b/org.bluetooth.characteristic.plx_continuous_measurement.xml new file mode 100644 index 0000000..b27d6e4 --- /dev/null +++ b/org.bluetooth.characteristic.plx_continuous_measurement.xml @@ -0,0 +1,319 @@ + + + + + The PLX Continuous Measurement characteristic, if + supported, is used to send periodic pulse oximetry + measurements. This characteristic is a variable length + structure containing the Flags field (to indicate presence of + optional fields), the SpO2PR-Normal field, and depending on the + contents of the Flags field, the SpO2PR-Fast field, the + SpO2PR-Slow field, the Measurement Status field, the Device and + Sensor Status field, and/or the Pulse Amplitude Index + field. + + + + Mandatory + 8bit + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Unit is percentage with a resolution of + 1 + Mandatory + SFLOAT + org.bluetooth.unit.percentage + 0 + + + Unit is beats per minute with a resolution + of 1 + Mandatory + SFLOAT + org.bluetooth.unit.period.beats_per_minute + 0 + + + Unit is percentage with a resolution of + 1 + C1 + SFLOAT + org.bluetooth.unit.percentage + 0 + + + Unit is beats per minute with a resolution + of 1 + C1 + SFLOAT + org.bluetooth.unit.period.beats_per_minute + 0 + + + Unit is percentage with a resolution of + 1 + C2 + SFLOAT + org.bluetooth.unit.percentage + 0 + + + Unit is beats per minute with a resolution + of 1 + C2 + SFLOAT + org.bluetooth.unit.period.beats_per_minute + 0 + + + C3 + 16bit + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + C4 + 24bit + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Unit is percentage with a resolution of + 1 + C5 + SFLOAT + org.bluetooth.unit.percentage + 0 + + + +

The fields in the above table, reading from top to bottom, + are shown in the order of LSO to MSO, where LSO = Least + Significant Octet and MSO = Most Significant Octet.

+ + diff --git a/org.bluetooth.characteristic.plx_features.xml b/org.bluetooth.characteristic.plx_features.xml new file mode 100644 index 0000000..f43023f --- /dev/null +++ b/org.bluetooth.characteristic.plx_features.xml @@ -0,0 +1,288 @@ + + + + + The PLX Features characteristic is used to describe + the supported features of the Server. Included in the + characteristic is a PLX Features field, and, depending on the + contents of the PLX Features field, the Measurement Status + Support field, and the Device and Sensor Status Support + field. + + + + Mandatory + 16bit + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + C1 + 16bit + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + C2 + 24bit + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +

The fields in the above table, reading from top to bottom, + are shown in the order of LSO to MSO, where LSO = Least + Significant Octet and MSO = Most Significant Octet.

+ + diff --git a/org.bluetooth.characteristic.plx_spot_check_measurement.xml b/org.bluetooth.characteristic.plx_spot_check_measurement.xml new file mode 100644 index 0000000..f7aa836 --- /dev/null +++ b/org.bluetooth.characteristic.plx_spot_check_measurement.xml @@ -0,0 +1,275 @@ + + + + + The PLX Spot-check Measurement characteristic, if + supported, is used to send Spot-check measurements of SpO2 + (Percent oxygen saturation of hemoglobin) and PR (pulse rate). + This characteristic is a variable length structure containing + the Flags field, the SpO2PR-Spot-Check field, and depending on + the contents of the Flags field, the Timestamp field, the + Measurement Status field, the Device and Sensor Status field, + and/or the Pulse Amplitude Index field. + + + + These flags define which data fields are + present in the Characteristic value + Mandatory + 8bit + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Unit is percentage with a resolution of + 1 + Mandatory + SFLOAT + org.bluetooth.unit.percentage + 0 + + + Unit is beats per minute with a resolution + of 1 + Mandatory + SFLOAT + org.bluetooth.unit.period.beats_per_minute + 0 + + + Unit is smallest unit in seconds with a + resolution of 1 + C1 + org.bluetooth.characteristic.date_time + + + C2 + 16bit + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + C3 + 24bit + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Unit is percentage with a resolution of + 1 + C4 + SFLOAT + org.bluetooth.unit.percentage + 0 + + + diff --git a/org.bluetooth.characteristic.pnp_id.xml b/org.bluetooth.characteristic.pnp_id.xml new file mode 100644 index 0000000..44258c9 --- /dev/null +++ b/org.bluetooth.characteristic.pnp_id.xml @@ -0,0 +1,56 @@ + + + + + The PnP_ID characteristic returns its value when read + using the GATT Characteristic Value Read procedure. + The PnP_ID characteristic is a set of values that used + to create a device ID value that is unique for this device. + Included in the characteristic is a Vendor ID Source field, a + Vendor ID field, a Product ID field and a Product Version + field. These values are used to identify all devices of a given + type/model/version using numbers. + + + + Identifies the source of the Vendor ID + field + Mandatory + uint8 + 1 + 2 + + + + + + + + + Identifies the product vendor from the + namespace in the Vendor ID Source + Mandatory + uint16 + + + Manufacturer managed identifier for this + product + Mandatory + uint16 + + + Manufacturer managed version for this + product + Mandatory + uint16 + + + The fields in the above table are in the order of LSO to + MSO. Where LSO = Least Significant Octet and MSO = Most + Significant Octet + diff --git a/org.bluetooth.characteristic.pollen_concentration.xml b/org.bluetooth.characteristic.pollen_concentration.xml new file mode 100644 index 0000000..c90a9db --- /dev/null +++ b/org.bluetooth.characteristic.pollen_concentration.xml @@ -0,0 +1,19 @@ + + + + + + Unit is in concentration count per cubic + meter with a resolution of 1/m^3 + Mandatory + uint24 + + org.bluetooth.unit.concentration.count_per_cubic_metre + 0 + + + diff --git a/org.bluetooth.characteristic.position_quality.xml b/org.bluetooth.characteristic.position_quality.xml new file mode 100644 index 0000000..e4ab17b --- /dev/null +++ b/org.bluetooth.characteristic.position_quality.xml @@ -0,0 +1,142 @@ + + + + + + + The Position Quality characteristic is a variable + length structure containing a Flags field and at least one of + the optional data fields listed below + + + + Mandatory + 16bit + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Unitless with a resolution of + 1 + Optional + uint8 + org.bluetooth.unit.unitless + 0 + + + Unitless with a resolution of + 1 + Optional + uint8 + org.bluetooth.unit.unitless + 0 + + + Unit is in seconds with a resolution of + 1/10 + Optional + uint16 + org.bluetooth.unit.time.second + -1 + + + Unit is in meters with a resolution of + 1/100 + Optional + uint32 + org.bluetooth.unit.length.meter + -2 + + + Unit is in meters with a resolution of + 1/100 + Optional + uint32 + org.bluetooth.unit.length.meter + -2 + + + Unitless with a resolution of + 2/10 + Optional + uint8 + org.bluetooth.unit.unitless + -1 + 2 + + + Unitless with a resolution of + 2/10 + Optional + uint8 + org.bluetooth.unit.unitless + -1 + 2 + + + The fields in the above table, reading from top to bottom, + are shown in the order of LSO to MSO, where LSO = Least + Significant Octet and MSO = Most Significant Octet. Where a field + with the format ?16bits? or ?32bits? is used, the Least + Significant Octet represents the eight bits numbered 0 to + 7. + diff --git a/org.bluetooth.characteristic.pressure.xml b/org.bluetooth.characteristic.pressure.xml new file mode 100644 index 0000000..244286f --- /dev/null +++ b/org.bluetooth.characteristic.pressure.xml @@ -0,0 +1,17 @@ + + + + + + Unit is in pascals with a resolution of 0.1 + Pa + Mandatory + uint32 + org.bluetooth.unit.pressure.pascal + -1 + + + diff --git a/org.bluetooth.characteristic.protocol_mode.xml b/org.bluetooth.characteristic.protocol_mode.xml new file mode 100644 index 0000000..f1a9946 --- /dev/null +++ b/org.bluetooth.characteristic.protocol_mode.xml @@ -0,0 +1,24 @@ + + + + + The Protocol Mode characteristic is used to expose the + current protocol mode of the HID Service with which it is + associated, or to set the desired protocol mode of the HID + Service. + + + + Mandatory + uint8 + + + + + + + + diff --git a/org.bluetooth.characteristic.rainfall.xml b/org.bluetooth.characteristic.rainfall.xml new file mode 100644 index 0000000..7f01b20 --- /dev/null +++ b/org.bluetooth.characteristic.rainfall.xml @@ -0,0 +1,17 @@ + + + + + + Unit is in meters with a resolution of + 1mm + Mandatory + uint16 + org.bluetooth.unit.length.meter + -3 + + + diff --git a/org.bluetooth.characteristic.record_access_control_point.xml b/org.bluetooth.characteristic.record_access_control_point.xml new file mode 100644 index 0000000..8a422f1 --- /dev/null +++ b/org.bluetooth.characteristic.record_access_control_point.xml @@ -0,0 +1,110 @@ + + + + + + This control point is used with a service to provide + basic management functionality for the Glucose Sensor patient + record database. This enables functions including counting + records, transmitting records and clearing records based on + filter criterion. The filter criterion in the Operand field is + defined by the service that references this characteristic as + is the format of a record (which may be comprised of one or + more characteristics) and the sequence of transferred + records. + + + + Mandatory + uint8 + + + + + + + + + + + + + Mandatory + uint8 + + + + + + + + + + + + + The operands correspond to the Op Code + values (Keys 0 to 255) defined in the Op Code Field + above + Mandatory + variable + + Op Code / Operand Value + Correspondence + + + + + + + + + + + Response Code Values + + + + + + + + + + + + + + + The fields in the above table are in the order of LSO to + MSO. Where LSO = Least Significant Octet and MSO = Most + Significant Octet. + diff --git a/org.bluetooth.characteristic.reference_time_information.xml b/org.bluetooth.characteristic.reference_time_information.xml new file mode 100644 index 0000000..a249b82 --- /dev/null +++ b/org.bluetooth.characteristic.reference_time_information.xml @@ -0,0 +1,45 @@ + + + + + + + Mandatory + + org.bluetooth.characteristic.time_source + + + Mandatory + + org.bluetooth.characteristic.time_accuracy + + + Mandatory + uint8 + org.bluetooth.unit.time.day + 0 + 254 + + + + + + If Days Since Update = 255, then Hours Since + Update shall also be set to 255 + Mandatory + uint8 + org.bluetooth.unit.time.hour + 0 + 23 + + + + + + The fields in the above table are in the order of LSO to + MSO. Where LSO = Least Significant Octet and MSO = Most + Significant Octet. + diff --git a/org.bluetooth.characteristic.report.xml b/org.bluetooth.characteristic.report.xml new file mode 100644 index 0000000..973f740 --- /dev/null +++ b/org.bluetooth.characteristic.report.xml @@ -0,0 +1,21 @@ + + + + + The Report characteristic is used to exchange data + between a HID Device and a HID Host. + The Report characteristic value contains Input Report, + Output Report or Feature Report data to be transferred between + the HID Device and HID Host. + + + + Mandatory + uint8 + true + + + diff --git a/org.bluetooth.characteristic.report_map.xml b/org.bluetooth.characteristic.report_map.xml new file mode 100644 index 0000000..d46cdd1 --- /dev/null +++ b/org.bluetooth.characteristic.report_map.xml @@ -0,0 +1,25 @@ + + + + + The Report Map characteristic is used to define + formatting information for Input Report, Output Report, and + Feature Report data transferred between a HID Device and HID + Host, information on how this data can be used, and other + information regarding physical aspects of the device (i.e. that + the device functions as a keyboard, for example, or has + multiple functions such as a keyboard and volume controls). +

Only a single instance of this characteristic exists as part + of a HID Service.

 + + + + Mandatory + uint8 + true + + + diff --git a/org.bluetooth.characteristic.resolvable_private_address_only.xml b/org.bluetooth.characteristic.resolvable_private_address_only.xml new file mode 100644 index 0000000..5fec880 --- /dev/null +++ b/org.bluetooth.characteristic.resolvable_private_address_only.xml @@ -0,0 +1,30 @@ + + + + + The Resolvable Private Address Only characteristic + defines whether the device will only use Resolvable Private + Addresses (RPAs) as local addresses. + + + + Mandatory + uint8 + org.bluetooth.unit.unitless + + + + + + + A device shall have only one instance of the Resolvable + Private Address Only characteristic. If the Resolvable Private + Address Only characteristic is not present, then it cannot be + assumed that only Resolvable Private Addresses will be used over + the air. + diff --git a/org.bluetooth.characteristic.resting_heart_rate.xml b/org.bluetooth.characteristic.resting_heart_rate.xml new file mode 100644 index 0000000..579073c --- /dev/null +++ b/org.bluetooth.characteristic.resting_heart_rate.xml @@ -0,0 +1,21 @@ + + + + + Lowest Heart Rate a user can reach + + + + Unit is in beats per minute with a + resolution of 1 + Mandatory + uint8 + org.bluetooth.unit.period.beats_per_minute + 0 + + + diff --git a/org.bluetooth.characteristic.ringer_control_point.xml b/org.bluetooth.characteristic.ringer_control_point.xml new file mode 100644 index 0000000..8e5de68 --- /dev/null +++ b/org.bluetooth.characteristic.ringer_control_point.xml @@ -0,0 +1,34 @@ + + + + + The Ringer Control Point characteristic defines the + Control Point of Ringer. +

Value 1, meaning ?Silent Mode"

+

Value 2, meaning ?Mute Once?

+

Value 3, meaning ?Cancel Silent Mode?

 + + The value 0x01 shall be interpreted as ?Silent + Mode? + + + + + Mandatory + uint8 + 1 + 3 + + + + + + + + + + diff --git a/org.bluetooth.characteristic.ringer_setting.xml b/org.bluetooth.characteristic.ringer_setting.xml new file mode 100644 index 0000000..f58f115 --- /dev/null +++ b/org.bluetooth.characteristic.ringer_setting.xml @@ -0,0 +1,30 @@ + + + + + The Ringer Setting characteristic defines the Setting + of the Ringer. +

Value 0, meaning ?Ringer Silent"

+

Value 1, meaning ?Ringer Normal?

 + + The value 0x01 shall be interpreted as ?Ringer + Normal? + + + + + Mandatory + 8bit + 0 + 1 + + + + + + + + diff --git a/org.bluetooth.characteristic.rower_data.xml b/org.bluetooth.characteristic.rower_data.xml new file mode 100644 index 0000000..dc28121 --- /dev/null +++ b/org.bluetooth.characteristic.rower_data.xml @@ -0,0 +1,220 @@ + + + + + The Rower Data characteristic is used to send + training-related data to the Client from a rower + (Server). + + + + Mandatory + 16bit + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + stroke/minute with a resolution of + 0.5 + C1 + uint8 + -1 + org.bluetooth.unit.stroke_per_minute + + + Unitless with a resolution of + 1 + C1 + uint16 + org.bluetooth.unit.unitless + + + 1/minute with a resolution of + 0.5 + C2 + uint8 + -1 + org.bluetooth.unit.stroke_per_minute + + + Meters with a resolution of + 1 + C3 + uint24 + org.bluetooth.unit.length.metre + + + Second with a resolution of + 1 + C4 + uint16 + org.bluetooth.unit.time.second + + + Second with a resolution of + 1 + C5 + uint16 + org.bluetooth.unit.time.second + + + Watts with a resolution of + 1 + C6 + sint16 + org.bluetooth.unit.power.watt + + + Watts with a resolution of + 1 + C7 + sint16 + org.bluetooth.unit.power.watt + + + Unitless with a resolution of + 1 + C8 + sint16 + org.bluetooth.unit.unitless + + + Kilo Calorie with a resolution of + 1 + C9 + uint16 + org.bluetooth.unit.energy.kilogram_calorie + + + Kilo Calorie with a resolution of + 1 + C9 + uint16 + org.bluetooth.unit.energy.kilogram_calorie + + + Kilo Calorie with a resolution of + 1 + C9 + uint8 + org.bluetooth.unit.energy.kilogram_calorie + + + Beats per minute with a resolution of + 1 + C10 + uint8 + org.bluetooth.unit.period.beats_per_minute + + + Metabolic Equivalent with a resolution of + 0.1 + C11 + uint8 + -1 + org.bluetooth.unit.metabolic_equivalent + + + Second with a resolution of + 1 + C12 + uint16 + org.bluetooth.unit.time.second + + + Second with a resolution of + 1 + C13 + uint16 + org.bluetooth.unit.time.second + + + The fields in the above table, reading from top to bottom, + are shown in the order of LSO to MSO, where LSO = Least + Significant Octet and MSO = Most Significant Octet. The Least + Significant Octet represents the eight bits numbered 0 to + 7. + diff --git a/org.bluetooth.characteristic.rsc_feature.xml b/org.bluetooth.characteristic.rsc_feature.xml new file mode 100644 index 0000000..ff3c479 --- /dev/null +++ b/org.bluetooth.characteristic.rsc_feature.xml @@ -0,0 +1,56 @@ + + + + + The RSC (Running Speed and Cadence) Feature + characteristic is used to describe the supported features of + the Server. + + + + Mandatory + 16bit + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/org.bluetooth.characteristic.rsc_measurement.xml b/org.bluetooth.characteristic.rsc_measurement.xml new file mode 100644 index 0000000..faeb764 --- /dev/null +++ b/org.bluetooth.characteristic.rsc_measurement.xml @@ -0,0 +1,87 @@ + + + + + The RSC Measurement characteristic (RSC refers to + Running Speed and Cadence) is a variable length structure + containing a Flags field, an Instantaneous Speed field and an + Instantaneous Cadence field and, based on the contents of the + Flags field, may contain a Stride Length field and a Total + Distance field. + + + + These flags define which data fields are + present in the Characteristic value. + Mandatory + 8bit + + + + + + + + + + + + + + + + + + + + + + + + Unit is in m/s with a resolution of 1/256 + s + Mandatory + uint16 + org.bluetooth.unit.velocity.metres_per_second + + + Unit is in 1/minute (or RPM) with a + resolutions of 1 1/min (or 1 RPM) + Mandatory + uint8 + + org.bluetooth.unit.angular_velocity.revolution_per_minute + + + +

C1: Field exists if the key of bit 0 of the Flags field + is set to 1.

+

- Unit is in meter with a resolution of 1/100 m (or + centimeter).

+ + C1 + uint16 + org.bluetooth.unit.length.meter + + + +

C2: Field exists if the key of bit 1 of the Flags field + is set to 1.

+

- Unit is in meter with a resolution of 1/10 m (or + decimeter).

+ + C2 + uint32 + org.bluetooth.unit.length.meter + + + The fields in the above table are in the order of LSO to + MSO. Where LSO = Least Significant Octet and MSO = Most + Significant Octet. + diff --git a/org.bluetooth.characteristic.sc_control_point.xml b/org.bluetooth.characteristic.sc_control_point.xml new file mode 100644 index 0000000..513cf53 --- /dev/null +++ b/org.bluetooth.characteristic.sc_control_point.xml @@ -0,0 +1,102 @@ + + + + + The SC Control Point characteristic is used to request + a specific function to be executed on the receiving + device. + + + + Mandatory + uint8 + + + + + + + + + + + + + Parameter Value for "Set Cumulative Value" + Op Code + C3 + variable + + + Parameter Value for "Update Sensor Location" + Op Code + C1 + uint8 + Refer to the Sensor Location characteristic + (org.bluetooth.characteristic.sensor_location) for additional + information on the possible values for this + field. + + + Parameter Value for "Response Code" Op + Code + C2 + uint8 + Refer to the Op Code table above for additional + information on the possible values for this + field. + + + Parameter Value for "Response Code" Op + Code + C2 + uint8 + + Response Values + + + + + + + + + + Parameter Value for "Response Code" Op + Code + C2 + variable + Note: Response Parameter for Op Code 4 or 0x04 + in Hex: The Parameter Value of the response to the Control + Point 0x04 (Request Supported Sensor Locations) is a variable + length to allow a list of different sensor locations as + defined by the Service Specification. + + + The fields in the above table are in the order of LSO to + MSO. Where LSO = Least Significant Octet and MSO = Most + Significant Octet. + diff --git a/org.bluetooth.characteristic.scan_interval_window.xml b/org.bluetooth.characteristic.scan_interval_window.xml new file mode 100644 index 0000000..41d7af7 --- /dev/null +++ b/org.bluetooth.characteristic.scan_interval_window.xml @@ -0,0 +1,31 @@ + + + + + The Scan Interval Window characteristic is used to + store the scan parameters of the GATT Client. Included in this + characteristic are the Scan Interval and Scan Window of the + GATT Client device. + The Scan Interval Window characteristic is used to + store the scan parameters of the GATT Client. The GATT Server + can use these values to optimize its own advertisement rate and + to minimize the rate of its own advertisements while also + minimizing the latency of reconnections. + + + + + Mandatory + uint16 + + + + Mandatory + uint16 + + + diff --git a/org.bluetooth.characteristic.scan_refresh.xml b/org.bluetooth.characteristic.scan_refresh.xml new file mode 100644 index 0000000..4903afb --- /dev/null +++ b/org.bluetooth.characteristic.scan_refresh.xml @@ -0,0 +1,24 @@ + + + + + The Scan Refresh characteristic is used to notify the + Client that the Server requires the Scan Interval Window + characteristic to be written with the latest values upon + notification. + + + + Mandatory + uint8 + + + + + + + diff --git a/org.bluetooth.characteristic.sensor_location.xml b/org.bluetooth.characteristic.sensor_location.xml new file mode 100644 index 0000000..7a8f95b --- /dev/null +++ b/org.bluetooth.characteristic.sensor_location.xml @@ -0,0 +1,38 @@ + + + + + The Sensor Location characteristic is used to expose + the location of the sensor. + + + + Mandatory + uint8 + + + + + + + + + + + + + + + + + + + + + + + diff --git a/org.bluetooth.characteristic.serial_number_string.xml b/org.bluetooth.characteristic.serial_number_string.xml new file mode 100644 index 0000000..b56dc46 --- /dev/null +++ b/org.bluetooth.characteristic.serial_number_string.xml @@ -0,0 +1,19 @@ + + + + + The value of this characteristic is a variable-length + UTF-8 string representing the serial number for a particular + instance of the device. + + + + Mandatory + utf8s + + + diff --git a/org.bluetooth.characteristic.software_revision_string.xml b/org.bluetooth.characteristic.software_revision_string.xml new file mode 100644 index 0000000..e8d1b48 --- /dev/null +++ b/org.bluetooth.characteristic.software_revision_string.xml @@ -0,0 +1,19 @@ + + + + + The value of this characteristic is a UTF-8 string + representing the software revision for the software within the + device. + + + + Mandatory + utf8s + + + diff --git a/org.bluetooth.characteristic.sport_type_for_aerobic_and_anaerobic_thresholds.xml b/org.bluetooth.characteristic.sport_type_for_aerobic_and_anaerobic_thresholds.xml new file mode 100644 index 0000000..081a8e8 --- /dev/null +++ b/org.bluetooth.characteristic.sport_type_for_aerobic_and_anaerobic_thresholds.xml @@ -0,0 +1,41 @@ + + + + + Sport type enumeration(See note below). The values of + the Sport Type for Aerobic and Anaerobic Thresholds + characteristic are defined below + + + + Mandatory + uint8 + + + + + + + + + + + + + + + + + + +

Aerobic Threshold and Anaerobic Threshold together with the + Sport Type for Aerobic and Anaerobic Thresholds describe the + metabolic thresholds of the user. The Sport Type for Aerobic + and Anaerobic Thresholds identifies how the measurement was + performed.

+ + diff --git a/org.bluetooth.characteristic.stair_climber_data.xml b/org.bluetooth.characteristic.stair_climber_data.xml new file mode 100644 index 0000000..632507c --- /dev/null +++ b/org.bluetooth.characteristic.stair_climber_data.xml @@ -0,0 +1,174 @@ + + + + + The Stair Climber Data characteristic is used to send + training-related data to the Client from a stair climber + (Server). + + + + Mandatory + 16bit + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Unitless with a resolution of + 1 + C1 + uint16 + org.bluetooth.unit.unitless + + + Step/minute with a resolution of + 1 + C2 + uint16 + org.bluetooth.unit.step_per_minute + + + Step/minute with a resolution of + 1 + C3 + uint16 + org.bluetooth.unit.step_per_minute + + + Meters with a resolution of + 1 + C4 + uint16 + org.bluetooth.unit.length.metre + + + Unitless with a resolution of + 1 + C5 + uint16 + org.bluetooth.unit.unitless + + + Kilo Calorie with a resolution of + 1 + C6 + uint16 + org.bluetooth.unit.energy.kilogram_calorie + + + Kilo Calorie with a resolution of + 1 + C6 + uint16 + org.bluetooth.unit.energy.kilogram_calorie + + + Kilo Calorie with a resolution of + 1 + C6 + uint8 + org.bluetooth.unit.energy.kilogram_calorie + + + Beats per minute with a resolution of + 1 + C7 + uint8 + org.bluetooth.unit.period.beats_per_minute + + + Metabolic Equivalent with a resolution of + 0.1 + C8 + uint8 + -1 + org.bluetooth.unit.metabolic_equivalent + + + Second with a resolution of + 1 + C9 + uint16 + org.bluetooth.unit.time.second + + + Second with a resolution of + 1 + C10 + uint16 + org.bluetooth.unit.time.second + + + The fields in the above table, reading from top to bottom, + are shown in the order of LSO to MSO, where LSO = Least + Significant Octet and MSO = Most Significant Octet. The Least + Significant Octet represents the eight bits numbered 0 to + 7. + diff --git a/org.bluetooth.characteristic.step_climber_data.xml b/org.bluetooth.characteristic.step_climber_data.xml new file mode 100644 index 0000000..dbf07f0 --- /dev/null +++ b/org.bluetooth.characteristic.step_climber_data.xml @@ -0,0 +1,168 @@ + + + + + The Step Climber Data characteristic is used to send + training-related data to the Client from a step climber + (Server). + + + + Mandatory + 16bit + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Unitless with a resolution of + 1 + C1 + uint16 + org.bluetooth.unit.unitless + + + Unitless with a resolution of + 1 + C1 + uint16 + org.bluetooth.unit.unitless + + + Step/minute with a resolution of + 1 + C2 + uint16 + org.bluetooth.unit.step_per_minute + + + Step/minute with a resolution of + 1 + C3 + uint16 + org.bluetooth.unit.step_per_minute + + + Meters with a resolution of + 1 + C4 + uint16 + org.bluetooth.unit.length.metre + + + Kilo Calorie with a resolution of + 1 + C5 + uint16 + org.bluetooth.unit.energy.kilogram_calorie + + + Kilo Calorie with a resolution of + 1 + C5 + uint16 + org.bluetooth.unit.energy.kilogram_calorie + + + Kilo Calorie with a resolution of + 1 + C5 + uint8 + org.bluetooth.unit.energy.kilogram_calorie + + + Beats per minute with a resolution of + 1 + C6 + uint8 + org.bluetooth.unit.period.beats_per_minute + + + Metabolic Equivalent with a resolution of + 0.1 + C7 + uint8 + -1 + org.bluetooth.unit.metabolic_equivalent + + + Second with a resolution of + 1 + C8 + uint16 + org.bluetooth.unit.time.second + + + Second with a resolution of + 1 + C9 + uint16 + org.bluetooth.unit.time.second + + + The fields in the above table, reading from top to bottom, + are shown in the order of LSO to MSO, where LSO = Least + Significant Octet and MSO = Most Significant Octet. The Least + Significant Octet represents the eight bits numbered 0 to + 7. + diff --git a/org.bluetooth.characteristic.supported_heart_rate_range.xml b/org.bluetooth.characteristic.supported_heart_rate_range.xml new file mode 100644 index 0000000..1bfef17 --- /dev/null +++ b/org.bluetooth.characteristic.supported_heart_rate_range.xml @@ -0,0 +1,36 @@ + + + + + The Supported Heart Rate Range characteristic is used + to send the supported Heart Rate range as well as the minimum + Heart Rate increment supported by the Server. + + + + Beats per minute with a resolution of + 1 + Mandatory + uint8 + org.bluetooth.unit.period.beats_per_minute + + + Beats per minute with a resolution of + 1 + Mandatory + uint8 + org.bluetooth.unit.period.beats_per_minute + + + Beats per minute with a resolution of + 1 + Mandatory + uint8 + org.bluetooth.unit.period.beats_per_minute + + + diff --git a/org.bluetooth.characteristic.supported_inclination_range.xml b/org.bluetooth.characteristic.supported_inclination_range.xml new file mode 100644 index 0000000..7828d95 --- /dev/null +++ b/org.bluetooth.characteristic.supported_inclination_range.xml @@ -0,0 +1,39 @@ + + + + + The Supported Inclination Range characteristic is used + to send the supported inclination range as well as the minimum + inclination increment supported by the Server. + + + + Percent with a resolution of + 0.1 + Mandatory + sint16 + org.bluetooth.unit.percentage + -1 + + + Percent with a resolution of + 0.1 + Mandatory + sint16 + org.bluetooth.unit.percentage + -1 + + + Percent with a resolution of + 0.1 + Mandatory + uint16 + org.bluetooth.unit.percentage + -1 + + + diff --git a/org.bluetooth.characteristic.supported_new_alert_category.xml b/org.bluetooth.characteristic.supported_new_alert_category.xml new file mode 100644 index 0000000..565d7a2 --- /dev/null +++ b/org.bluetooth.characteristic.supported_new_alert_category.xml @@ -0,0 +1,27 @@ + + + + + Category that the server supports for new + alert. + This characteristic uses the Alert Category ID Bit + Mask Characteristic. If bit(s) is/are set, it means the server + supports the corresponded categories for new incoming + alert. + + The value 0x0a is interpreted that this server + supports ?Call? and ?Email? categories. + + + + + Mandatory + + org.bluetooth.characteristic.alert_category_id_bit_mask + + + diff --git a/org.bluetooth.characteristic.supported_power_range.xml b/org.bluetooth.characteristic.supported_power_range.xml new file mode 100644 index 0000000..0961a42 --- /dev/null +++ b/org.bluetooth.characteristic.supported_power_range.xml @@ -0,0 +1,36 @@ + + + + + The Supported Power Range characteristic is used to + send the supported power range as well as the minimum power + increment supported by the Server. + + + + Watt with a resolution of + 1 + Mandatory + sint16 + org.bluetooth.unit.power.watt + + + Watt with a resolution of + 1 + Mandatory + sint16 + org.bluetooth.unit.power.watt + + + Watt with a resolution of + 1 + Mandatory + uint16 + org.bluetooth.unit.power.watt + + + diff --git a/org.bluetooth.characteristic.supported_resistance_level_range.xml b/org.bluetooth.characteristic.supported_resistance_level_range.xml new file mode 100644 index 0000000..aa7c2a2 --- /dev/null +++ b/org.bluetooth.characteristic.supported_resistance_level_range.xml @@ -0,0 +1,40 @@ + + + + + The Supported Resistance Level Range characteristic is + used to send the supported resistance level range as well as + the minimum resistance increment supported by the + Server. + + + + Unitless with a resolution of + 0.1 + Mandatory + sint16 + org.bluetooth.unit.unitless + -1 + + + Unitless with a resolution of + 0.1 + Mandatory + sint16 + org.bluetooth.unit.unitless + -1 + + + Unitless with a resolution of + 0.1 + Mandatory + uint16 + org.bluetooth.unit.unitless + -1 + + + diff --git a/org.bluetooth.characteristic.supported_speed_range.xml b/org.bluetooth.characteristic.supported_speed_range.xml new file mode 100644 index 0000000..39ab923 --- /dev/null +++ b/org.bluetooth.characteristic.supported_speed_range.xml @@ -0,0 +1,39 @@ + + + + + The Supported Speed Range characteristic is used to + send the supported speed range as well as the minimum speed + increment supported by the Server. + + + + Kilometer per hour with a resolution of + 0.01 + Mandatory + uint16 + org.bluetooth.unit.velocity.kilometre_per_hour + -2 + + + Kilometer per hour with a resolution of + 0.01 + Mandatory + uint16 + org.bluetooth.unit.velocity.kilometre_per_hour + -2 + + + Meters per second with a resolution of + 0.01 + Mandatory + uint16 + org.bluetooth.unit.velocity.kilometre_per_hour + -2 + + + diff --git a/org.bluetooth.characteristic.supported_unread_alert_category.xml b/org.bluetooth.characteristic.supported_unread_alert_category.xml new file mode 100644 index 0000000..fcc39c3 --- /dev/null +++ b/org.bluetooth.characteristic.supported_unread_alert_category.xml @@ -0,0 +1,28 @@ + + + + + Category that the server supports for unread + alert. + This characteristic uses the Alert Category ID Bit + Mask Characteristic. If bit(s) is/are set, it means the server + supports the corresponded categories for unread + alert. + + The value 0x03 is interpreted that this server + supports ?Simple Alert? and ?Email? categories for unread + alert. + + + + + Mandatory + + org.bluetooth.characteristic.alert_category_id_bit_mask + + + diff --git a/org.bluetooth.characteristic.system_id.xml b/org.bluetooth.characteristic.system_id.xml new file mode 100644 index 0000000..652eee9 --- /dev/null +++ b/org.bluetooth.characteristic.system_id.xml @@ -0,0 +1,57 @@ + + + + + +

The SYSTEM ID characteristic consists of a structure with + two fields. The first field are the LSOs and the second field + contains the MSOs. This is a 64-bit structure which consists + of a 40-bit manufacturer-defined identifier concatenated with + a 24 bit unique Organizationally Unique Identifier (OUI). The + OUI is issued by the IEEE Registration Authority + (http://standards.ieee.org/regauth/index.html) and is + required to be used in accordance with IEEE Standard + 802-2001.6 while the least significant 40 bits are + manufacturer defined.

+

If System ID generated based on a Bluetooth Device + Address, it is required to be done as follows. System ID and + the Bluetooth Device Address have a very similar structure: a + Bluetooth Device Address is 48 bits in length and consists of + a 24 bit Company Assigned Identifier (manufacturer defined + identifier) concatenated with a 24 bit Company Identifier + (OUI). In order to encapsulate a Bluetooth Device Address as + System ID, the Company Identifier is concatenated with 0xFFFE + followed by the Company Assigned Identifier of the Bluetooth + Address. For more guidelines related to EUI-64, refer to + http://standards.ieee.org/develop/regauth/tut/eui64.pdf.

+ + + If the system ID is based of a Bluetooth Device + Address with a Company Identifier (OUI) is 0x123456 and the + Company Assigned Identifier is 0x9ABCDE, then the System + Identifier is required to be 0x123456FFFE9ABCDE. + + + + + + Mandatory + uint40 + 0 + 1099511627775 + + + + Mandatory + uint24 + 0 + 16777215 + + + The fields in the above table are in the order of LSO to + MSO. Where LSO = Least Significant Octet and MSO = Most + Significant Octet. + diff --git a/org.bluetooth.characteristic.tds_control_point.xml b/org.bluetooth.characteristic.tds_control_point.xml new file mode 100644 index 0000000..9bdf8e4 --- /dev/null +++ b/org.bluetooth.characteristic.tds_control_point.xml @@ -0,0 +1,13 @@ + + + + + The TDS Control Point characteristic is defined in the + Transport Discovery Service, Section 4.1 and its + sub-sections. + + diff --git a/org.bluetooth.characteristic.temperature.xml b/org.bluetooth.characteristic.temperature.xml new file mode 100644 index 0000000..cd106f2 --- /dev/null +++ b/org.bluetooth.characteristic.temperature.xml @@ -0,0 +1,18 @@ + + + + + + Unit is in degrees Celsius with a resolution + of 0.01 degrees Celsius + Mandatory + sint16 + + org.bluetooth.unit.thermodynamic_temperature.degree_celsius + -2 + + + diff --git a/org.bluetooth.characteristic.temperature_measurement.xml b/org.bluetooth.characteristic.temperature_measurement.xml new file mode 100644 index 0000000..afb0279 --- /dev/null +++ b/org.bluetooth.characteristic.temperature_measurement.xml @@ -0,0 +1,114 @@ + + + + + + The Temperature Measurement characteristic is a + variable length structure containing a Flags field, a + Temperature Measurement Value field and, based upon the + contents of the Flags field, optionally a Time Stamp field + and/or a Temperature Type field. + The flags is the first field sent followed by the + Temperature Measurement Value. + + If the value of bit 1 of the Flags field is 0 and + bit 2 is 0, the structure of the Temperature Measurement + characteristic consists of two fields in this order; Flags + and Temperature Measurement Value. + If the value of bit 1 of the Flags field is 1 (Time + Stamp) and bit 2 is 0, the structure of the Temperature + Measurement characteristic consists of three fields in this + order: Flags, Temperature Measurement Value and Time + Stamp. + If the value of bit 1 of the Flags field is 1 and + bit 2 is 1 (Time Stamp and Temperature Type), the structure + of the Temperature Measurement characteristic consists of + four fields in this order: Flags, Temperature Measurement + Value, Time Stamp and Temperature Type. + If the value of bit 1 of the Flags field is 0 and + bit 2 is 1 (Temperature Type), the structure of the + Temperature Measurement characteristic consists of three + fields in this order: Flags, Temperature Measurement Value + and Temperature Type. + + + + + + Mandatory + 8bit + + + + + + + + + + + + + + + + + + + + + + + + + + + + This field is only included if the flags bit + 0 is 0. + C1 + FLOAT + + org.bluetooth.unit.thermodynamic_temperature.degree_celsius + + + This field is only included if the flags bit + 0 is 1. + C2 + FLOAT + + org.bluetooth.unit.thermodynamic_temperature.degree_fahrenheit + + + If the flags bit 1 is 1 this field is + included. If it is 0, this field is not + included + C3 + org.bluetooth.characteristic.date_time + + + If the flags bit 2 is set to 1 this field is + included. If it is 0, this field is not + included + C4 + + org.bluetooth.characteristic.temperature_type + + + + The fields in the above table are in the order of LSO to + MSO. Where LSO = Least Significant Octet and MSO = Most + Significant Octet. + + diff --git a/org.bluetooth.characteristic.temperature_type.xml b/org.bluetooth.characteristic.temperature_type.xml new file mode 100644 index 0000000..5c1ad96 --- /dev/null +++ b/org.bluetooth.characteristic.temperature_type.xml @@ -0,0 +1,34 @@ + + + + + + The Temperature Type characteristic is an enumeration + that indicates where the temperature was measured. + These Temperature Type values correspond to the + Temperature Type descriptions used in ISO/IEEE + 11073-10408-2008. + + + + Mandatory + 8bit + + + + + + + + + + + + + + + + diff --git a/org.bluetooth.characteristic.three_zone_heart_rate_limits.xml b/org.bluetooth.characteristic.three_zone_heart_rate_limits.xml new file mode 100644 index 0000000..b2a7f49 --- /dev/null +++ b/org.bluetooth.characteristic.three_zone_heart_rate_limits.xml @@ -0,0 +1,38 @@ + + + + + Data structure containing the limits between the + heart rate zones for the 3-zone heart rate definition (Hard, + Moderate and Light). + + + + + Unit is in beats per minute with a + resolution of 1 + Mandatory + uint8 + org.bluetooth.unit.period.beats_per_minute + 0 + + + + Unit is in beats per minute with a + resolution of 1 + Mandatory + uint8 + org.bluetooth.unit.period.beats_per_minute + 0 + + + +

The fields in the above table are in the order of LSO to + MSO. Where LSO = Least Significant Octet and MSO = Most + Significant Octet.

+ + diff --git a/org.bluetooth.characteristic.time_accuracy.xml b/org.bluetooth.characteristic.time_accuracy.xml new file mode 100644 index 0000000..82ceb24 --- /dev/null +++ b/org.bluetooth.characteristic.time_accuracy.xml @@ -0,0 +1,26 @@ + + + + + + + Accuracy (drift) of time information in + steps of 1/8 of a second (125ms) compared to a reference time + source. Valid range from 0 to 253 (0s to 31.5s). A value of + 254 means Accuracy is out of range (> 31.5s). A value of + 255 means Accuracy is unknown. + Mandatory + uint8 + -3 + 0 + 253 + + + + + + + diff --git a/org.bluetooth.characteristic.time_source.xml b/org.bluetooth.characteristic.time_source.xml new file mode 100644 index 0000000..8c24513 --- /dev/null +++ b/org.bluetooth.characteristic.time_source.xml @@ -0,0 +1,26 @@ + + + + + + + Mandatory + 8bit + 0 + 7 + + + + + + + + + + + + + diff --git a/org.bluetooth.characteristic.time_update_control_point.xml b/org.bluetooth.characteristic.time_update_control_point.xml new file mode 100644 index 0000000..688a6fb --- /dev/null +++ b/org.bluetooth.characteristic.time_update_control_point.xml @@ -0,0 +1,22 @@ + + + + + + + Mandatory + uint8 + 1 + 2 + + + + + + + + + diff --git a/org.bluetooth.characteristic.time_update_state.xml b/org.bluetooth.characteristic.time_update_state.xml new file mode 100644 index 0000000..29743ff --- /dev/null +++ b/org.bluetooth.characteristic.time_update_state.xml @@ -0,0 +1,41 @@ + + + + + + + Mandatory + uint8 + 0 + 1 + + + + + + + + Mandatory + uint8 + 0 + 4 + + + + + + + + + + + + The fields in the above table are in the order of LSO to + MSO. Where LSO = Least Significant Octet and MSO = Most + Significant Octet. + diff --git a/org.bluetooth.characteristic.time_with_dst.xml b/org.bluetooth.characteristic.time_with_dst.xml new file mode 100644 index 0000000..dde1dfa --- /dev/null +++ b/org.bluetooth.characteristic.time_with_dst.xml @@ -0,0 +1,22 @@ + + + + + + + Mandatory + org.bluetooth.characteristic.date_time + + + Mandatory + + org.bluetooth.characteristic.dst_offset + + + The fields in the above table are in the order of LSO to + MSO. Where LSO = Least Significant Octet and MSO = Most + Significant Octet. + diff --git a/org.bluetooth.characteristic.time_zone.xml b/org.bluetooth.characteristic.time_zone.xml new file mode 100644 index 0000000..247b3b1 --- /dev/null +++ b/org.bluetooth.characteristic.time_zone.xml @@ -0,0 +1,21 @@ + + + + + + + Mandatory + sint8 + -48 + 56 + Offset from UTC in number of 15 minutes + increments. A value of -128 means that the time zone offset + is not known. The offset defined in this characteristic is + constant, regardless whether daylight savings is in + effect. + + + diff --git a/org.bluetooth.characteristic.training_status.xml b/org.bluetooth.characteristic.training_status.xml new file mode 100644 index 0000000..d50179d --- /dev/null +++ b/org.bluetooth.characteristic.training_status.xml @@ -0,0 +1,12 @@ + + + + + The Training Status characteristic is defined in the + Fitness Machine Service Specification. + + diff --git a/org.bluetooth.characteristic.treadmill_data.xml b/org.bluetooth.characteristic.treadmill_data.xml new file mode 100644 index 0000000..4b2eaf2 --- /dev/null +++ b/org.bluetooth.characteristic.treadmill_data.xml @@ -0,0 +1,242 @@ + + + + + The Treadmill Data characteristic is used to send + training-related data to the Client from a treadmill + (Server). + + + + Mandatory + 16bit + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Kilometer per hour with a resolution of + 0.01 + C1 + uint16 + org.bluetooth.unit.velocity.kilometre_per_hour + -2 + + + Kilometer per hour with a resolution of + 0.01 + C2 + uint16 + org.bluetooth.unit.velocity.kilometre_per_hour + -2 + + + Meters with a resolution of + 1 + C3 + uint24 + org.bluetooth.unit.length.metre + + + Percent with a resolution of + 0.1 + C4 + sint16 + org.bluetooth.unit.percentage + -1 + + + Degree with a resolution of + 0.1 + C4 + sint16 + org.bluetooth.unit.plane_angle.degree + -1 + + + Meters with a resolution of + 0.1 + C5 + uint16 + org.bluetooth.unit.length.metre + -1 + + + Meters with a resolution of + 0.1 + C5 + uint16 + org.bluetooth.unit.length.metre + -1 + + + Kilometer per minute with a resolution of + 0.1 + C6 + uint8 + org.bluetooth.unit.velocity.kilometre_per_minute + -1 + + + Kilometer per minute with a resolution of + 0.1 + C7 + uint8 + org.bluetooth.unit.velocity.kilometre_per_minute + -1 + + + Kilo Calorie with a resolution of + 1 + C8 + uint16 + org.bluetooth.unit.energy.kilogram_calorie + + + Kilo Calorie with a resolution of + 1 + C8 + uint16 + org.bluetooth.unit.energy.kilogram_calorie + + + Kilo Calorie with a resolution of + 1 + C8 + uint8 + org.bluetooth.unit.energy.kilogram_calorie + + + Beats per minute with a resolution of + 1 + C9 + uint8 + org.bluetooth.unit.period.beats_per_minute + + + Metabolic Equivalent with a resolution of + 0.1 + C10 + uint8 + org.bluetooth.unit.metabolic_equivalent + + + Second with a resolution of + 1 + C11 + uint16 + org.bluetooth.unit.time.second + + + Second with a resolution of + 1 + C12 + uint16 + org.bluetooth.unit.time.second + + + Newton with a resolution of + 1 + C13 + sint16 + org.bluetooth.unit.force.newton + + + Watts with a resolution of + 1 + C13 + sint16 + org.bluetooth.unit.power.watt + + + The fields in the above table, reading from top to bottom, + are shown in the order of LSO to MSO, where LSO = Least + Significant Octet and MSO = Most Significant Octet. The Least + Significant Octet represents the eight bits numbered 0 to + 7. + diff --git a/org.bluetooth.characteristic.true_wind_direction.xml b/org.bluetooth.characteristic.true_wind_direction.xml new file mode 100644 index 0000000..c2b7046 --- /dev/null +++ b/org.bluetooth.characteristic.true_wind_direction.xml @@ -0,0 +1,27 @@ + + + + + + Unit is in degrees with a resolution of 0.01 + degrees + Mandatory + uint16 + org.bluetooth.unit.plane_angle.degree + Wind direction is reported by the direction from + which it originates and is an angle measured clockwise + relative to Geographic North. For example, a wind coming from + the north is given as 0 degrees, a wind coming from the south + is given as 180 degrees, a wind coming from the east is given + as 90 degrees and a wind coming from the west is given as 270 + degrees. + -2 + 0 + 359.99 + + + diff --git a/org.bluetooth.characteristic.true_wind_speed.xml b/org.bluetooth.characteristic.true_wind_speed.xml new file mode 100644 index 0000000..b34614f --- /dev/null +++ b/org.bluetooth.characteristic.true_wind_speed.xml @@ -0,0 +1,18 @@ + + + + + + Unit is in meters per second with a + resolution of 0.01 m/s + Mandatory + uint16 + org.bluetooth.unit.velocity.metres_per_second + -2 + + + diff --git a/org.bluetooth.characteristic.two_zone_heart_rate_limit.xml b/org.bluetooth.characteristic.two_zone_heart_rate_limit.xml new file mode 100644 index 0000000..84a83bc --- /dev/null +++ b/org.bluetooth.characteristic.two_zone_heart_rate_limit.xml @@ -0,0 +1,23 @@ + + + + + Heart rate limit between the heart rate zones for the + 2-zone heart rate definition (Fitness and Fat Burn). + + + + + Unit is in beats per minute with a + resolution of 1 + Mandatory + uint8 + org.bluetooth.unit.period.beats_per_minute + 0 + + + diff --git a/org.bluetooth.characteristic.tx_power_level.xml b/org.bluetooth.characteristic.tx_power_level.xml new file mode 100644 index 0000000..46705ef --- /dev/null +++ b/org.bluetooth.characteristic.tx_power_level.xml @@ -0,0 +1,29 @@ + + + + + + The Transmit Power Level characteristic represents + the current transmit power level in dBm, and the level ranges + from -100 dBm to +20 dBm to a resolution of 1 dBm. + The value of the characteristic is a signed 8 bit + integer that has a fixed point exponent of 0. + + The value 0x12 is interpreted as +18dBm + The value 0xEE is interpreted as -18dBm + + + + + Mandatory + sint8 + + org.bluetooth.unit.logarithmic_radio_quantity.decibel + -100 + 20 + + + diff --git a/org.bluetooth.characteristic.uncertainty.xml b/org.bluetooth.characteristic.uncertainty.xml new file mode 100644 index 0000000..864ee6a --- /dev/null +++ b/org.bluetooth.characteristic.uncertainty.xml @@ -0,0 +1,57 @@ + + + + + The Uncertainty characteristic describes the + uncertainty of the location information the device + exposes. + + + + Mandatory + uint8 + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/org.bluetooth.characteristic.unread_alert_status.xml b/org.bluetooth.characteristic.unread_alert_status.xml new file mode 100644 index 0000000..d28a9df --- /dev/null +++ b/org.bluetooth.characteristic.unread_alert_status.xml @@ -0,0 +1,40 @@ + + + + + This characteristic shows how many numbers of unread + alerts exist in the specific category in the device. + This characteristic consists of ?Category ID? and + ?uint8? which shows the number of unread + alerts/messages. + + The value 0x01, 0x04 are interpreted that the server + has 4 unread messages in Email category. + + + + + The value shows the category for unread + alert count + Mandatory + + org.bluetooth.characteristic.alert_category_id + + + How many unread alerts exist on the server. +

If the value is 255, it means Unread count is greater than + 254.

 + Mandatory + uint8 + 0 + 255 + + + The fields in the above table are in the order of LSO to + MSO. Where LSO = Least Significant Octet and MSO = Most + Significant Octet. + diff --git a/org.bluetooth.characteristic.uri.xml b/org.bluetooth.characteristic.uri.xml new file mode 100644 index 0000000..39a88fb --- /dev/null +++ b/org.bluetooth.characteristic.uri.xml @@ -0,0 +1,20 @@ + + + + + The Uniform Resource Identifier (URI) Characteristic + is used to configure the URI for a subsequent + request. + + + + The URI to be used in the HTTP + request. + Mandatory + utf8s + + + diff --git a/org.bluetooth.characteristic.user_control_point.xml b/org.bluetooth.characteristic.user_control_point.xml new file mode 100644 index 0000000..44439f5 --- /dev/null +++ b/org.bluetooth.characteristic.user_control_point.xml @@ -0,0 +1,10 @@ + + + + This definition is shown in the User Data + Service Section 3.4 and its subsections. + diff --git a/org.bluetooth.characteristic.user_index.xml b/org.bluetooth.characteristic.user_index.xml new file mode 100644 index 0000000..02e668f --- /dev/null +++ b/org.bluetooth.characteristic.user_index.xml @@ -0,0 +1,18 @@ + + + + + + Mandatory + uint8 + + The special value of 0xFF is used for + ?Unknown User?. + + + + + diff --git a/org.bluetooth.characteristic.uv_index.xml b/org.bluetooth.characteristic.uv_index.xml new file mode 100644 index 0000000..744b3e5 --- /dev/null +++ b/org.bluetooth.characteristic.uv_index.xml @@ -0,0 +1,15 @@ + + + + + + Mandatory + uint8 + org.bluetooth.unit.unitless + 0 + + + diff --git a/org.bluetooth.characteristic.vo2_max.xml b/org.bluetooth.characteristic.vo2_max.xml new file mode 100644 index 0000000..89e0d31 --- /dev/null +++ b/org.bluetooth.characteristic.vo2_max.xml @@ -0,0 +1,19 @@ + + + + + Maximal Oxygen uptake of a user + + + + Unit is in Milliliter per kilogram per + minutes with a resolution of 1 . + Mandatory + uint8 + 0 + + + diff --git a/org.bluetooth.characteristic.waist_circumference.xml b/org.bluetooth.characteristic.waist_circumference.xml new file mode 100644 index 0000000..a03e2fb --- /dev/null +++ b/org.bluetooth.characteristic.waist_circumference.xml @@ -0,0 +1,22 @@ + + + + + Used with the Hip Circumference value to calculate + the Waist to Hip Ratio (WHR) + + + + Unit is in meters with a resolution of + 0.01 + Mandatory + uint16 + org.bluetooth.unit.length.meter + -2 + + + diff --git a/org.bluetooth.characteristic.weight.xml b/org.bluetooth.characteristic.weight.xml new file mode 100644 index 0000000..25cc550 --- /dev/null +++ b/org.bluetooth.characteristic.weight.xml @@ -0,0 +1,21 @@ + + + + + Weight of the User + + + + Unit is in kilograms with a resolution of + 0.005. + Mandatory + uint16 + org.bluetooth.unit.mass.kilogram + -3 + 5 + + + diff --git a/org.bluetooth.characteristic.weight_measurement.xml b/org.bluetooth.characteristic.weight_measurement.xml new file mode 100644 index 0000000..2519ea3 --- /dev/null +++ b/org.bluetooth.characteristic.weight_measurement.xml @@ -0,0 +1,115 @@ + + + + + + Mandatory + 8bit + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Unit is in kilograms with a resolution of + 0.005, and determined when bit 0 of the Flags field is set to + 0. + C1 + uint16 + org.bluetooth.unit.mass.kilogram + -3 + 5 + + + Unit is in pounds with a resolution of 0.01, + and determined when bit 0 of the Flags field is set to + 1. + C2 + uint16 + org.bluetooth.unit.mass.pound + -2 + + + Smallest unit in seconds + C3 + org.bluetooth.characteristic.date_time + + + Unit is unitless with a resolution of + 1 + C4 + uint8 + org.bluetooth.unit.unitless + 0 + + The special value of 0xFF (255 Decimal) + for User ID represents ?unknown user?. + + + + + Unit is unitless with a resolution of + 0.1 + C5 + uint16 + org.bluetooth.unit.unitless + -1 + + + Unit is in meters with a resolution of + 0.001, and determined when bit 0 of the Flags field is set to + 0. + C1 + C5 + uint16 + org.bluetooth.unit.length.meter + -3 + + + Unit is in inches with a resolution of 0.1, + and determined when bit 0 of the Flags field is set to + 1 + C2 + C5 + uint16 + org.bluetooth.unit.length.inch + -1 + + + +

The fields in the above table are in the order of LSO to + MSO. Where LSO = Least Significant Octet and MSO = Most + Significant Octet.

+ + diff --git a/org.bluetooth.characteristic.weight_scale_feature.xml b/org.bluetooth.characteristic.weight_scale_feature.xml new file mode 100644 index 0000000..2220a29 --- /dev/null +++ b/org.bluetooth.characteristic.weight_scale_feature.xml @@ -0,0 +1,69 @@ + + + + + + Mandatory + 32bit + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/org.bluetooth.characteristic.wind_chill.xml b/org.bluetooth.characteristic.wind_chill.xml new file mode 100644 index 0000000..5ea783f --- /dev/null +++ b/org.bluetooth.characteristic.wind_chill.xml @@ -0,0 +1,18 @@ + + + + + + Unit is in degrees Celsius with a resolution + of 1 degree Celsius + Mandatory + sint8 + + org.bluetooth.unit.thermodynamic_temperature.degree_celsius + 0 + + + diff --git a/org.bluetooth.descriptor.es_configuration.xml b/org.bluetooth.descriptor.es_configuration.xml new file mode 100644 index 0000000..5e32253 --- /dev/null +++ b/org.bluetooth.descriptor.es_configuration.xml @@ -0,0 +1,12 @@ + + + + + This definition is shown in the Environmental Sensing + Service Section 3.1.2.3 + + diff --git a/org.bluetooth.descriptor.es_measurement.xml b/org.bluetooth.descriptor.es_measurement.xml new file mode 100644 index 0000000..1949af8 --- /dev/null +++ b/org.bluetooth.descriptor.es_measurement.xml @@ -0,0 +1,11 @@ + + + + This definition is shown in the Environmental + Sensing Service Section 3.1.2.1 and its + subsections. + diff --git a/org.bluetooth.descriptor.es_trigger_setting.xml b/org.bluetooth.descriptor.es_trigger_setting.xml new file mode 100644 index 0000000..00c58e1 --- /dev/null +++ b/org.bluetooth.descriptor.es_trigger_setting.xml @@ -0,0 +1,10 @@ + + + + This definition is shown in the Environmental + Sensing Service Section 3.1.2.2 + diff --git a/org.bluetooth.descriptor.external_report_reference.xml b/org.bluetooth.descriptor.external_report_reference.xml new file mode 100644 index 0000000..abc5e27 --- /dev/null +++ b/org.bluetooth.descriptor.external_report_reference.xml @@ -0,0 +1,23 @@ + + + + + The External Report Reference characteristic + descriptor allows a HID Host to map information from the Report + Map characteristic value for Input Report, Output Report or + Feature Report data to the Characteristic UUID of external + service characteristics used to transfer the associated + data. + + + + Characteristic UUID for externally + referenced characteristic + Mandatory + gatt_uuid + + + diff --git a/org.bluetooth.descriptor.gatt.characteristic_aggregate_format.xml b/org.bluetooth.descriptor.gatt.characteristic_aggregate_format.xml new file mode 100644 index 0000000..21a56e4 --- /dev/null +++ b/org.bluetooth.descriptor.gatt.characteristic_aggregate_format.xml @@ -0,0 +1,38 @@ + + + + + The Characteristic Aggregate Format descriptor + defines the format of an aggregated Characteristic + Value. + + Only one Characteristic Aggregate Format descriptor + exists in a characteristic definition. This descriptor consists + of a list of Attribute Handles pointing to Characteristic + Presentation Format declarations. This descriptor is read only + and does not require authentication or authorization. The list + of Attribute Handles is the concatenation of multiple 16-bit + Attribute Handle values into a single Attribute Value. If more + than one Characteristic Presentation Format declarations exist, + then there is one Characteristic Aggregate Format declaration. + However, a Characteristic Aggregate Format descriptor can be + present even if there aren't any Presentation Format + descriptors in the characteristic definition. The order of the + Attribute Handles in the list is significant. + + If 3 Characteristic Presentation Format declarations + exist at Attribute Handles 0x40, 0x50 and 0x60, the + Characteris Aggregate Format Value is 0x405060. + + + + + Mandatory + uint16 + true + + + diff --git a/org.bluetooth.descriptor.gatt.characteristic_extended_properties.xml b/org.bluetooth.descriptor.gatt.characteristic_extended_properties.xml new file mode 100644 index 0000000..8f273cb --- /dev/null +++ b/org.bluetooth.descriptor.gatt.characteristic_extended_properties.xml @@ -0,0 +1,57 @@ + + + + + + The Characteristic Extended Properties descriptor + defines additional Characteristic Properties. + + If the Characteristic Extended Properties bit of the + Characteristic Properties is set, then this descriptor exists. + The Characteristic Extended Properties descriptor is a bit + field defining Reliable Write and Writeable Auxiliaries are + enabled for the Characteristic. This descriptor is readable + without authentication and authorization being + required. + + + + Mandatory + 16bit + 0 + 3 + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/org.bluetooth.descriptor.gatt.characteristic_presentation_format.xml b/org.bluetooth.descriptor.gatt.characteristic_presentation_format.xml new file mode 100644 index 0000000..e375692 --- /dev/null +++ b/org.bluetooth.descriptor.gatt.characteristic_presentation_format.xml @@ -0,0 +1,106 @@ + + + + + The Characteristic Presentation Format descriptor + defines the format of the Characteristic Value. + + One or more Characteristic Presentation Format + descriptors may be present. If multiple of these descriptors + are present, then a Aggregate Formate descriptor is present. + This descriptor is read only and does not require + authentication or authorization to read. This descriptor is + composed of five parts: format, exponent, unit, name space and + description. The Format field determines how a single value + contained in the Characteristic Value is formatted. The + Exponent field is used with interger data types to determine + how the Characteristic Value is furhter formatted. The actual + value = Characteristic Value * 10^Exponent. + + When encoding an IPv4 address, the uint32 Format + type is used. + When encoding an IPv6 address, the uint128 Format + type is used. + When encoding a Bluetooth address (BD_ADDR), the + uint48 Format type is used. + For a Characteristic Value of 23 and an Exponent of + 2, the actual value is 2300 + For a Characteristi Value of 3892 and an Exponent of + -3, the actual value is 3.892 + + + + + Mandatory + 8bit + 0 + 27 + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Mandatory + sint8 + + + The Unit is a UUID. + Mandatory + uint16 + + + The Name Space field is used to indentify + the organization that is responsible for defining the + enumerations for the description field. + Mandatory + 8bit + 0 + 1 + + + + + + + The Description is an enumerated value from + the organization identified by the Name Space + field. + Mandatory + 16bit + + + diff --git a/org.bluetooth.descriptor.gatt.characteristic_user_description.xml b/org.bluetooth.descriptor.gatt.characteristic_user_description.xml new file mode 100644 index 0000000..8a0e5ba --- /dev/null +++ b/org.bluetooth.descriptor.gatt.characteristic_user_description.xml @@ -0,0 +1,23 @@ + + + + + The Characteristic User Description descriptor + provides a textual user description for a characteristic + value. + + If the Writable Auxiliary bit of the Characteristics + Properties is set then this descriptor is written. Only one + User Description descriptor exists in a characteristic + definition. + + + + Mandatory + utf8s + + + diff --git a/org.bluetooth.descriptor.gatt.client_characteristic_configuration.xml b/org.bluetooth.descriptor.gatt.client_characteristic_configuration.xml new file mode 100644 index 0000000..df3d4cb --- /dev/null +++ b/org.bluetooth.descriptor.gatt.client_characteristic_configuration.xml @@ -0,0 +1,58 @@ + + + + + The Client Characteristic Configuration descriptor + defines how the characteristic may be configured by a specific + client. + + This descriptor shall be persistent across connections + for bonded devices. The Client Characteristic Configuration + descriptor is unique for each client. A client may read and + write this descriptor to determine and set the configuration + for that client. Authentication and authorization may be + required by the server to write this descriptor. The default + value for the Client Characteristic Configuration descriptor is + 0x00. Upon connection of non-binded clients, this descriptor is + set to the default value. + + + + Mandatory + 16bit + 0 + 3 + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/org.bluetooth.descriptor.gatt.server_characteristic_configuration.xml b/org.bluetooth.descriptor.gatt.server_characteristic_configuration.xml new file mode 100644 index 0000000..436df83 --- /dev/null +++ b/org.bluetooth.descriptor.gatt.server_characteristic_configuration.xml @@ -0,0 +1,37 @@ + + + + + + The Server Characteristic Configuration descriptor + defines how the characteristic descriptor is associated with + may be configured for the server. + Only one Server Characteristic Configuration + descriptor exists in a characteristic definition. A client may + write this configuration descriptor to control the + configuration of the characteristic on the server for all + clients. There is a single instantiation of this descriptor for + all clients. Authentication and authorization may be required + by the server to write this descriptor. + + + + Mandatory + uint16 + 0 + 1 + + + + + + + + + + + + diff --git a/org.bluetooth.descriptor.number_of_digitals.xml b/org.bluetooth.descriptor.number_of_digitals.xml new file mode 100644 index 0000000..c61bb4e --- /dev/null +++ b/org.bluetooth.descriptor.number_of_digitals.xml @@ -0,0 +1,19 @@ + + + + + The Characteristic Number of Digitals descriptor is + used for defining the number of digitals in a + characteristic. + + + + Mandatory + uint8 + + + diff --git a/org.bluetooth.descriptor.report_reference.xml b/org.bluetooth.descriptor.report_reference.xml new file mode 100644 index 0000000..66ec553 --- /dev/null +++ b/org.bluetooth.descriptor.report_reference.xml @@ -0,0 +1,34 @@ + + + + + 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. + + + + Mandatory + uint8 + 0 + 255 + + + Mandatory + uint8 + 1 + 3 + + + + + + + + + + diff --git a/org.bluetooth.descriptor.time_trigger_setting.xml b/org.bluetooth.descriptor.time_trigger_setting.xml new file mode 100644 index 0000000..416987c --- /dev/null +++ b/org.bluetooth.descriptor.time_trigger_setting.xml @@ -0,0 +1,52 @@ + + + + + The value of the descriptor has two parts. Part one + is a condition field and occupies one octet, and part two is + the comparison value (trigger point) that the characteristic + value is checked against. + + + + Mandatory + uint8 + + Available Conditions + + + + + + + + + No comparison value + required + C1 + uint8 + + + C2 + uint24 + org.bluetooth.unit.time.second + 0 + + + C3 + uint16 + + + diff --git a/org.bluetooth.descriptor.valid_range.xml b/org.bluetooth.descriptor.valid_range.xml new file mode 100644 index 0000000..4710248 --- /dev/null +++ b/org.bluetooth.descriptor.valid_range.xml @@ -0,0 +1,50 @@ + + + + + The Characteristic Valid Range descriptor is used for + defining the range of a characteristics. Two mandatory fields + are contained (upper and lower bounds) which define the + range. + If the Characteristic Value to which this descriptor + is attached has a fixed exponent, then the values in this + descriptor have the same exponent. The first value in the Valid + Range descriptor represents the lower inclusive value of the + range. The second value represents the higher inclusive value + of the range. The data type and units for lower inclusive value + and the upper inclusive value are identical to the data type + and units of the characteristic for which it is used. + + When used with the Measurement Interval + characteristic, the Valid Range descriptor is formatted using + a uint16. If the valid range has a Minimum Value of 10 + minutes (600 seconds) and a Maximum Value of 2 hours (7200 + seconds) the value of the Valid Range descriptor would be + expressed as: 0x58 0x02 0x20 0x1C + A characteristic that is formatted using a nibble + with a fixed decimal-exponent that has a Valid Range of 2 to + 13 has a Valid Range descriptor defined as: 0x02 + 0x0D + A characteristic value that is formatted using an + sint16 with a fixed exponent of -1 that has a Valid Range of + -40 to +85 is expressed as: 0x70 0xFE 0x52 0x03 + + + + + The lower bound is the same format as the + characteristic the descriptor describes. + Mandatory + characteristic + + + The upper bound is the same format as the + characteristic the descriptor describes. + Mandatory + characteristic + + + diff --git a/org.bluetooth.descriptor.value_trigger_setting.xml b/org.bluetooth.descriptor.value_trigger_setting.xml new file mode 100644 index 0000000..ba38274 --- /dev/null +++ b/org.bluetooth.descriptor.value_trigger_setting.xml @@ -0,0 +1,60 @@ + + + + + The value of the descriptor has two parts. Part one + is a condition field and occupies one octet, and part two is + the comparison value (trigger point) that the characteristic + value is checked against. + + + + Mandatory + uint8 + + Available Conditions + + + + + + + + + + + + + C2 + uint16 + + + C3 + org.bluetooth.characteristic.digital + + + Analog One (uint16), Analog Two + (uint16) + C4 + uint32 + + + diff --git a/org.bluetooth.service.alert_notification.xml b/org.bluetooth.service.alert_notification.xml new file mode 100644 index 0000000..6a05dc8 --- /dev/null +++ b/org.bluetooth.service.alert_notification.xml @@ -0,0 +1,163 @@ + + + + + Alert Notification service exposes: +

? The different types of alerts with the short text + messages.

+

? The information how many count of new alert messages.

+

? The information how many count of unread + alerts.

 + The Alert Notification service exposes alert + information in a device. This information includes the + following: +

- Type of alert occuring in a device.

+

- Additional text information such as caller ID or sender + ID

+

- Count of new alerts.

+

- Count of unread alert items.

 + + + This service has no dependencies on other + GATT-based services. + + + + Mandatory + + Mandatory + + Mandatory + + Mandatory + + + false + true + + + + + + + + + This characteristic exposes what categories + of new alert are supported in the server. + Mandatory + + Mandatory + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + + + + This characteristic exposes information + about the count of new alerts (for a given + category). + Mandatory + + Excluded + Excluded + Excluded + Excluded + Excluded + Mandatory + Excluded + Excluded + Excluded + + + + + Mandatory + + Mandatory + Mandatory + + + + + + + This characteristic exposes what categories + of unread alert are supported in the + server. + Mandatory + + Mandatory + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + + + + This characteristic exposes the count of + unread alert events existing in the server + Mandatory + + Excluded + Excluded + Excluded + Excluded + Excluded + Mandatory + Excluded + Excluded + Excluded + + + + + Mandatory + + Mandatory + Mandatory + + + + + + + This characteristic allows the peer device + to enable/disable the alert notification of new alert and + unread event more selectively than can be done by setting or + clearing the notification bit in the Client Characteristic + Configuration for each alert + characteristic. + Mandatory + + Excluded + Mandatory + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + + + + diff --git a/org.bluetooth.service.automation_io.xml b/org.bluetooth.service.automation_io.xml new file mode 100644 index 0000000..724d8d8 --- /dev/null +++ b/org.bluetooth.service.automation_io.xml @@ -0,0 +1,355 @@ + + + + + The Automation IO service is used to expose the + analog inputs/outputs and digital input/outputs of a generic IO + module (IOM). + + + This service has no dependencies on other + GATT-based services. + + + C1: + Mandatory if Digital or Analog with Write property is + supported. + C2: + Mandatory if the ?write without response? characteristic + property is supported for either the Digital or Analog + characteristics (if any available). + C3: Mandatory if the + ?indicate? or ?notify? characteristic property respectively is + supported for either the Digital, Analog or Aggregate + characteristic. + C3:Mandatory if the + ?indicate? or ?notify? characteristic property respectively is + supported for either the Digital, Analog or Aggregate + characteristic. + + C4: Mandatory if indications or notification is supported or if + writable characteristics descriptors are supported for at least + one supported characteristics. + C5: + Mandatory if a Digital characteristic is present. + + + true + true + + + + + + + + The Digital characteristic is used to expose + and change the state of an IOM?s digital + signals. + Conditional + + +

+ C1:At least one instance of either Digital or + Analog characteristics shall be supported

+

+ C3:The Indicate and Notify properties are excluded + for the Digital and Analog characteristics if the + Aggregate characteristic is supported

+

+ C4:The Indicate and Notify properties shall not be + permitted simultaneously for any supported + characteristic

+

+ C5:Indicate or Notify property shall be supported + only if the Read property is supported for the + characteristic

+ + Optional + Optional + Optional + Excluded + Excluded + Optional + Optional + Excluded + Excluded + Excluded + + + + + + if_notify_or_indicate_supported + + Mandatory + Mandatory + + + + + + if_multiple_instances_of_same_characteristic + + Mandatory + Excluded + + + + + + C2:Write permitted if ?writable auxiliaries? is + supported in the Characteristic Extended Properties + descriptor otherwise read-only. + Optional + + Mandatory + C2 + + + + + Optional + + Mandatory + Excluded + + + + +

+ C3: Excluded if a custom condition is available, + otherwise Optional. +

+

+ C5: Excluded if Indicate or Notify not is defined + for the characteristic or for the Aggregate + characteristic (if it is used). +

+ + Conditional + + Mandatory + Mandatory + + + + +

+ C3: Excluded if a custom condition is available, + otherwise Optional. +

+

+ C4: Excluded if a Value Trigger Descriptor not is + defined for the characteristic. +

+

+ C5: Excluded if Indicate or Notify not is defined + for the characteristic or for the Aggregate + characteristic (if it is used). +

+ + Conditional + + Mandatory + Mandatory + + + + Mandatory + + Mandatory + Excluded + + + + + + The Analog characteristic is used to read or + write the value of one of the IOM?s analog + signals. + Conditional + + +

+ C1:At least one instance of either Digital or + Analog characteristics shall be supported

+

+ C3:The Indicate and Notify properties are excluded + for the Digital and Analog characteristics if the + Aggregate characteristic is supported

+

+ C4:The Indicate and Notify properties shall not be + permitted simultaneously for any supported + characteristic

+

+ C5:Indicate or Notify property shall be supported + only if the Read property is supported for the + characteristic

+ + Optional + Optional + Optional + Excluded + Excluded + Optional + Optional + Excluded + Excluded + Excluded + + + + + + if_notify_or_indicate_supported + + Mandatory + Mandatory + + + + + + if_multiple_instances_of_same_characteristic + + Mandatory + Excluded + + + + + + C2:Write permitted if ?writable auxiliaries? is + supported in the Characteristic Extended Properties + descriptor otherwise read-only. + Optional + + Mandatory + C2 + + + + + Optional + + Mandatory + Excluded + + + + +

+ C4: Excluded if a custom condition is available + otherwise Optional. +

+

+ C6: Excluded if Indicate or Notify not is defined + for the characteristic or for the Aggregate + characteristic (if it is used). +

+ + Conditional + + Mandatory + Mandatory + + + + +

+ C4: Excluded if a custom condition is available + otherwise Optional. +

+

+ C5: Excluded if a Value Trigger Setting descriptor + not is defined for the characteristic. +

+

+ C6: Excluded if Indicate or Notify not is defined + for the characteristic or for the Aggregate + characteristic (if it is used). +

+ + Conditional + + Mandatory + Mandatory + + + + Optional + + Mandatory + Excluded + + + + + + Conditional + + +

+ C2:Only one instance of the Aggregate + characteristic shall exist if the Aggregate + characteristic is supported.

+

+ C4:The Indicate and Notify properties shall not be + permitted simultaneously for any supported + characteristic

+

+ C5:Indicate or Notify property shall be supported + only if the Read property is supported for the + characteristic

+ + Optional + Excluded + Excluded + Excluded + Excluded + Optional + Optional + Excluded + Excluded + Excluded + + + + + + if_notify_or_indicate_supported + + Mandatory + Mandatory + + + + + + diff --git a/org.bluetooth.service.battery_service.xml b/org.bluetooth.service.battery_service.xml new file mode 100644 index 0000000..dc86222 --- /dev/null +++ b/org.bluetooth.service.battery_service.xml @@ -0,0 +1,76 @@ + + + + + The Battery Service exposes the state of a battery + within a device. + The Battery Service exposes the Battery State and + Battery Level of a single battery or set of batteries in a + device. + + + This service has no dependencies on other + GATT-based services. + + + + Mandatory + C1: Mandatory if the + Battery Level characteristic properties supports notification, + otherwise excluded. + + C1: Mandatory if the Battery Level characteristic properties + supports notification, otherwise excluded. + + + true + true + + + + + The Battery Level characteristic is read + using the GATT Read Characteristic Value sub-procedure and + returns the current battery level as a percentage from 0% to + 100%; 0% represents a battery that is fully discharged, 100% + represents a battery that is fully charged. + Mandatory + + Mandatory + Excluded + Excluded + Excluded + Excluded + Optional + Excluded + Excluded + Excluded + + + + + if_multiple_service_instances + + Mandatory + Excluded + + + + + + if_notify_or_indicate_supported + + Mandatory + Mandatory + + + + + + diff --git a/org.bluetooth.service.blood_pressure.xml b/org.bluetooth.service.blood_pressure.xml new file mode 100644 index 0000000..c27aca4 --- /dev/null +++ b/org.bluetooth.service.blood_pressure.xml @@ -0,0 +1,111 @@ + + + + + This service exposes blood pressure and other data + from a blood pressure monitor intended for healthcare + applications. + The BLOOD PRESSURE Service exposes blood pressure and + other data related to a blood pressure monitor. + + + This service has no dependencies on other + GATT-based services. + + + Mandatory if the + Intermediate Cuff Pressure characteristic is supported, + otherwise excluded for this service. + Mandatory + + Mandatory + + Mandatory + + + false + true + + + + The BLOOD PRESSURE MEASUREMENT + characteristic is used to send a Blood Pressure + measurement. + Mandatory + + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + Mandatory + Excluded + Excluded + + + + + Mandatory + + Mandatory + Mandatory + + + + + + The INTERMEDIATE CUFF PRESSURE + characteristic is used to send intermediate Cuff Pressure + values to a device for display purposes while the measurement + is in progress. + Optional + + Excluded + Excluded + Excluded + Excluded + Excluded + Mandatory + Excluded + Excluded + Excluded + + + + + Mandatory + + Mandatory + Mandatory + + + + + + The Blood Pressure Feature characteristic is + used to describe the supported features of the Blood Pressure + Sensor. + Mandatory + + Mandatory + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + + + + diff --git a/org.bluetooth.service.body_composition.xml b/org.bluetooth.service.body_composition.xml new file mode 100644 index 0000000..a7abbaa --- /dev/null +++ b/org.bluetooth.service.body_composition.xml @@ -0,0 +1,76 @@ + + + + + This service exposes data related to body composition + from a body composition analyzer intended for consumer + healthcare and sports/fitness applications. + The Body Composition Service (BCS) exposes data + related to body composition from a body composition analyzer + (Server) intended for consumer healthcare as well as + sports/fitness applications. + + + This service is not dependent upon any other + services. + + + Mandatory + + Mandatory + + Mandatory + + + true + true + true + + + + + Mandatory + + Mandatory + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + + + + Mandatory + + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + Mandatory + Excluded + Excluded + + + + Mandatory + + Mandatory + Mandatory + + + + + + diff --git a/org.bluetooth.service.bond_management.xml b/org.bluetooth.service.bond_management.xml new file mode 100644 index 0000000..7719c8f --- /dev/null +++ b/org.bluetooth.service.bond_management.xml @@ -0,0 +1,82 @@ + + + + + This Specification proposes that this service will + enable users to manage their bonds on devices with a limited + user interface. + This service defines how a peer Bluetooth device can + manage the storage of bond information, especially the deletion + of it, on the Bluetooth device supporting this + service. + + + This Service has no dependencies to other + GATT-based services. + + + + Mandatory + + C1 + + Optional + + C1: Mandatory if operand longer than MTU is requested, else + optional + + true + true + true + + + + + + + + Mandatory + + Excluded + Mandatory + Excluded + Excluded + Optional + Excluded + Excluded + Excluded + Excluded + Excluded + + + Authentication + + + + Mandatory + + Mandatory + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + + + Authentication + + + + diff --git a/org.bluetooth.service.continuous_glucose_monitoring.xml b/org.bluetooth.service.continuous_glucose_monitoring.xml new file mode 100644 index 0000000..f2505fc --- /dev/null +++ b/org.bluetooth.service.continuous_glucose_monitoring.xml @@ -0,0 +1,222 @@ + + + + + This service exposes glucose and other data from a + personal Continuous Glucose Monitoring (CGM) sensor for use in + consumer healthcare applications. + The Continuous Glucose Monitoring (CGM) Service + exposes glucose measurement and other data related to a + personal CGM sensor for healthcare applications. + + + This Service has no dependencies to other + GATT-based services. + + + + Mandatory + + Mandatory + Mandatory + + Mandatory + + Mandatory + + + true + true + true + + + + + + + + Mandatory + + Excluded + Excluded + Excluded + Excluded + Excluded + Mandatory + Excluded + Excluded + Excluded + Excluded + + + Authentication + + + + + Read Property: Readable with no + authentication or authorization already defined in + Bluetooth Core Specification v4.0 as amended by CSA3 and + CSS v2 or later + Mandatory + + Mandatory + Mandatory + + + + + + Mandatory + + Mandatory + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + + + Authentication + + + + Mandatory + + Mandatory + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + + + Authentication + + + + Mandatory + + Mandatory + Mandatory + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + + + Authentication + + + + Mandatory + + Mandatory + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + + + Authentication + + + + Mandatory + + Excluded + Mandatory + Excluded + Excluded + Excluded + Excluded + Mandatory + Excluded + Excluded + Excluded + + + Authentication + + + + + Read Property: Readable with no + authentication or authorization already defined in + Bluetooth Core Specification v4.0 as amended by CSA3 and + CSS v2 or later + Mandatory + + Mandatory + Mandatory + + + + + + Mandatory + + Excluded + Mandatory + Excluded + Excluded + Excluded + Excluded + Mandatory + Excluded + Excluded + Excluded + + + Authentication + + + + + Read Property: Readable with no + authentication or authorization already defined in + Bluetooth Core Specification v4.0 as amended by CSA3 and + CSS v2 or later + Mandatory + + Mandatory + Mandatory + + + + + + diff --git a/org.bluetooth.service.current_time.xml b/org.bluetooth.service.current_time.xml new file mode 100644 index 0000000..c54c60f --- /dev/null +++ b/org.bluetooth.service.current_time.xml @@ -0,0 +1,91 @@ + + + + + This service defines how the current time can be + exposed using the Generic Attribute Profile (GATT). + Many Bluetooth devices have the ability to store and + show time information. This service defines how a Bluetooth + device can expose time information to other Bluetooth + devices. + + + This service has no dependencies on other + GATT-based services. + + + + Mandatory + + Mandatory + + Mandatory + + + false + true + + + + + Mandatory + + Mandatory + Optional + Excluded + Excluded + Excluded + Mandatory + Excluded + Excluded + Excluded + + + + + Mandatory + + Mandatory + Mandatory + + + + + + Optional + + Mandatory + Optional + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + + + + Optional + + Mandatory + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + + + + diff --git a/org.bluetooth.service.cycling_power.xml b/org.bluetooth.service.cycling_power.xml new file mode 100644 index 0000000..c31ad67 --- /dev/null +++ b/org.bluetooth.service.cycling_power.xml @@ -0,0 +1,167 @@ + + + + + + This service exposes power- and force-related data + and optionally speed- and cadence-related data from a Cycling + Power sensor intended for sports and fitness + applications. + 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. + + + This service has no dependencies on other + GATT-based services. + + + + C.1 + + Mandatory + C.1 + + Mandatory + + Mandatory + + + C1: Mandatory if the Cycling Power Control Point + characteristic is supported, otherwise excluded for this + service. + + true + true + true + + + The notifications of the Cycling Power Vector + characteristic cannot be sent due to inappropriate connection + parameters. + + + + Mandatory + + Excluded + Excluded + Excluded + Excluded + Excluded + Mandatory + Excluded + Excluded + Optional + + + + + Mandatory + + Mandatory + Mandatory + + + + + if_broadcast_supported + + Mandatory + Mandatory + + + + + + Mandatory + + Mandatory + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + + + + Mandatory + + Mandatory + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + + + + Optional + + Excluded + Excluded + Excluded + Excluded + Excluded + Mandatory + Excluded + Excluded + Excluded + + + + + Mandatory + + Mandatory + Mandatory + + + + + + Optional + + Excluded + Mandatory + Excluded + Excluded + Excluded + Excluded + Mandatory + Excluded + Excluded + + + + + Mandatory + + Mandatory + Mandatory + + + + + + diff --git a/org.bluetooth.service.cycling_speed_and_cadence.xml b/org.bluetooth.service.cycling_speed_and_cadence.xml new file mode 100644 index 0000000..b72426d --- /dev/null +++ b/org.bluetooth.service.cycling_speed_and_cadence.xml @@ -0,0 +1,159 @@ + + + + + This service exposes speed-related and + cadence-related data from a Cycling Speed and Cadence sensor + intended for fitness applications. + The Cycling Speed and Cadence (CSC) Service exposes + speed-related data and/or cadence-related data while using the + Cycling Speed and Cadence sensor (Server). + + + This service is not dependent upon any other + services. + + + + C1 + + Mandatory + C1 + + Mandatory + + Mandatory + + C1: Mandatory if the SC Control Point characteristic is + supported, otherwise excluded for this service. + + true + true + + + A + SC Control Point request cannot be serviced because a + previously triggered SC Control Point operation is still in + progress. + The Client Characteristic Configuration descriptor + is not configured according to the requirements of the + service. + + + + The CSC Measurement characteristic is used + to send speed-related data and/or cadence-related + data. + Mandatory + + Excluded + Excluded + Excluded + Excluded + Excluded + Mandatory + Excluded + Excluded + Excluded + + + + + Mandatory + + Mandatory + Mandatory + + + + + + The CSC Feature characteristic is used to + describe the supported features of the Server. Reserved for + Future Use (RFU) bits in the CSC Feature characteristic value + are set to 0. + Mandatory + + Mandatory + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + + + + +

The Sensor Location characteristic of the device is used + to describe the physical location of the Server when + correctly fitted.

+

+ C1:Mandatory if the Multiple Sensor Location feature + is supported, otherwise optional.

+ + C1 + + Mandatory + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + + + + +

If the SC Control Point is supported, profiles utilizing + this service are required to ensure that the Client + configures the SC Control Point characteristic for + indications (i.e. via the Client Characteristic + Configuration descriptor) at the first connection.

+

Support for this characteristic is mandatory if the + Server supports Wheel Revolution Data or Multiple Sensor + Locations features, otherwise it is excluded.

+

+ C2:Mandatory if at least one SC Control Point + procedure is supported, otherwise excluded.

+ + C2 + + Excluded + Mandatory + Excluded + Excluded + Excluded + Excluded + Mandatory + Excluded + Excluded + + + + + if_characteristic_supported + + Mandatory + Mandatory + + + + + + diff --git a/org.bluetooth.service.device_information.xml b/org.bluetooth.service.device_information.xml new file mode 100644 index 0000000..c81d622 --- /dev/null +++ b/org.bluetooth.service.device_information.xml @@ -0,0 +1,191 @@ + + + + + The Device Information Service exposes manufacturer + and/or vendor information about a device. + This service exposes manufacturer information about a + device. The Device Information Service is instantiated as a + Primary Service. Only one instance of the Device Information + Service is exposed on a device. + + + This service is not dependent upon any other + services. + + + true + true + + + + + This characteristic represents the name of + the manufacturer of the device. + Optional + + Mandatory + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + + + + This characteristic represents the model + number that is assigned by the device + vendor. + Optional + + Mandatory + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + + + + This characteristic represents the serial + number for a particular instance of the + device. + Optional + + Mandatory + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + + + + This characteristic represents the hardware + revision for the hardware within the + device. + Optional + + Mandatory + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + + + + This characteristic represents the firmware + revision for the firmware within the + device. + Optional + + Mandatory + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + + + + This characteristic represents the software + revision for the software within the + device. + Optional + + Mandatory + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + + + + This characteristic represents a structure + containing an Organizationally Unique Identifier (OUI) + followed by a manufacturer-defined identifier and is unique + for each individual instance of the + product. + Optional + + Mandatory + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + + + + + This characteristic represents regulatory + and certification information for the product in a list + defined in IEEE 11073-20601. + Optional + + Mandatory + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + + + + The PnP_ID characteristic is a set of values + used to create a device ID value that is unique for this + device. + Optional + + Mandatory + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + + + + diff --git a/org.bluetooth.service.environmental_sensing.xml b/org.bluetooth.service.environmental_sensing.xml new file mode 100644 index 0000000..dcfadac --- /dev/null +++ b/org.bluetooth.service.environmental_sensing.xml @@ -0,0 +1,1581 @@ + + + + + This service exposes measurement data from an + environmental sensor intended for sports and fitness + applications. A wide range of environmental parameters is + supported. + The Environmental Sensing Service (ESS) exposes + measurement data from an environmental sensor intended for + sports and fitness applications. A wide range of environmental + parameters is supported. + + + This service is not dependent upon any other + services. + + + Mandatory if the + Server supports the ES Trigger Setting descriptor; excluded + otherwise. + Mandatory if the + Descriptor Value Changed characteristic is supported; optional + otherwise. + + Mandatory + + Mandatory if the Server supports reading a Characteristic User + Description descriptor string length that exceeds the capacity + of the default ATT_MTU; optional otherwise. + + Mandatory if the Server supports the Descriptor Value Changed + characteristic or notification of the ESS Characteristic or + writing to the Characteristic User Description descriptor, ES + Trigger Setting descriptor or ES Configuration descriptor; + optional otherwise. + + Mandatory if the Server supports writing a Characteristic User + Description descriptor string length that exceeds the capacity + of the default ATT_MTU; optional otherwise. + + + true + true + true + + + + + + + + C.2: Mandatory if any of the following + descriptors can be changed by the Server: ES Measurement, ES + Trigger Setting, ES Configuration, Characteristic User + Description. C.3: Mandatory if the write property is + supported for the Characteristic User Description + descriptor. + C2 or C3 + + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + Mandatory + Optional + Excluded + Optional + + + + C1: At least one ESS Characteristic is + exposed. + C1 + + Mandatory + Excluded + Excluded + Excluded + Excluded + Optional + Excluded + Optional + Excluded + Optional + + + + + if_multiple_instances_of_same_characteristic_optional_otherwise + + Mandatory + Excluded + + + + C1: If Write is supported, bonding is + mandatory as described in Section 3.1.2.3.1 of the + Service Specification. If the ES Trigger Setting + descriptor is writable, an ES Configuration descriptor, + if present, is also writable. Otherwise, both are + read-only. + if_notify_supported + + Mandatory + C1 + + + + C1: If Write is supported, bonding is + mandatory as described in Section 3.1.2.3.1 of the + Service Specification. If the ES Trigger Setting + descriptor is writable, an ES Configuration descriptor, + if present, is also writable. Otherwise, both are + read-only. C2: Mandatory if there is more than one ES + Trigger Setting Descriptor + C2 + + Mandatory + C1 + + + + + Optional + + Mandatory + Optional + + + + Optional + + Mandatory + Excluded + + + + + + C1: At least one ESS Characteristic is + exposed. + C1 + + Mandatory + Excluded + Excluded + Excluded + Excluded + Optional + Excluded + Optional + Excluded + Optional + + + + + if_multiple_instances_of_same_characteristic_optional_otherwise + + Mandatory + Excluded + + + + C1: If Write is supported, bonding is + mandatory as described in Section 3.1.2.3.1 of the + Service Specification. If the ES Trigger Setting + descriptor is writable, an ES Configuration descriptor, + if present, is also writable. Otherwise, both are + read-only. + if_notify_supported + + Mandatory + C1 + + + + C1: If Write is supported, bonding is + mandatory as described in Section 3.1.2.3.1 of the + Service Specification. If the ES Trigger Setting + descriptor is writable, an ES Configuration descriptor, + if present, is also writable. Otherwise, both are + read-only. C2: Mandatory if there is more than one ES + Trigger Setting Descriptor + C2 + + Mandatory + C1 + + + + + Optional + + Mandatory + Optional + + + + Optional + + Mandatory + Excluded + + + + + + C1: At least one ESS Characteristic is + exposed. + C1 + + Mandatory + Excluded + Excluded + Excluded + Excluded + Optional + Excluded + Optional + Excluded + Optional + + + + + if_multiple_instances_of_same_characteristic_optional_otherwise + + Mandatory + Excluded + + + + C1: If Write is supported, bonding is + mandatory as described in Section 3.1.2.3.1 of the + Service Specification. If the ES Trigger Setting + descriptor is writable, an ES Configuration descriptor, + if present, is also writable. Otherwise, both are + read-only. + if_notify_supported + + Mandatory + C1 + + + + C1: If Write is supported, bonding is + mandatory as described in Section 3.1.2.3.1 of the + Service Specification. If the ES Trigger Setting + descriptor is writable, an ES Configuration descriptor, + if present, is also writable. Otherwise, both are + read-only. C2: Mandatory if there is more than one ES + Trigger Setting Descriptor + C2 + + Mandatory + C1 + + + + + Optional + + Mandatory + Optional + + + + Optional + + Mandatory + Excluded + + + + + + C1: At least one ESS Characteristic is + exposed. + C1 + + Mandatory + Excluded + Excluded + Excluded + Excluded + Optional + Excluded + Optional + Excluded + Optional + + + + + if_multiple_instances_of_same_characteristic_optional_otherwise + + Mandatory + Excluded + + + + C1: If Write is supported, bonding is + mandatory as described in Section 3.1.2.3.1 of the + Service Specification. If the ES Trigger Setting + descriptor is writable, an ES Configuration descriptor, + if present, is also writable. Otherwise, both are + read-only. + if_notify_supported + + Mandatory + C1 + + + + C1: If Write is supported, bonding is + mandatory as described in Section 3.1.2.3.1 of the + Service Specification. If the ES Trigger Setting + descriptor is writable, an ES Configuration descriptor, + if present, is also writable. Otherwise, both are + read-only. C2: Mandatory if there is more than one ES + Trigger Setting Descriptor + C2 + + Mandatory + C1 + + + + + Optional + + Mandatory + Optional + + + + Optional + + Mandatory + Excluded + + + + + + C1: At least one ESS Characteristic is + exposed. + C1 + + Mandatory + Excluded + Excluded + Excluded + Excluded + Optional + Excluded + Optional + Excluded + Optional + + + + + if_multiple_instances_of_same_characteristic_optional_otherwise + + Mandatory + Excluded + + + + C1: If Write is supported, bonding is + mandatory as described in Section 3.1.2.3.1 of the + Service Specification. If the ES Trigger Setting + descriptor is writable, an ES Configuration descriptor, + if present, is also writable. Otherwise, both are + read-only. + if_notify_supported + + Mandatory + C1 + + + + C1: If Write is supported, bonding is + mandatory as described in Section 3.1.2.3.1 of the + Service Specification. If the ES Trigger Setting + descriptor is writable, an ES Configuration descriptor, + if present, is also writable. Otherwise, both are + read-only. C2: Mandatory if there is more than one ES + Trigger Setting Descriptor + C2 + + Mandatory + C1 + + + + + Optional + + Mandatory + Optional + + + + Optional + + Mandatory + Excluded + + + + + + C1: At least one ESS Characteristic is + exposed. + C1 + + Mandatory + Excluded + Excluded + Excluded + Excluded + Optional + Excluded + Optional + Excluded + Optional + + + + + if_multiple_instances_of_same_characteristic_optional_otherwise + + Mandatory + Excluded + + + + C1: If Write is supported, bonding is + mandatory as described in Section 3.1.2.3.1 of the + Service Specification. If the ES Trigger Setting + descriptor is writable, an ES Configuration descriptor, + if present, is also writable. Otherwise, both are + read-only. + if_notify_supported + + Mandatory + C1 + + + + C1: If Write is supported, bonding is + mandatory as described in Section 3.1.2.3.1 of the + Service Specification. If the ES Trigger Setting + descriptor is writable, an ES Configuration descriptor, + if present, is also writable. Otherwise, both are + read-only. C2: Mandatory if there is more than one ES + Trigger Setting Descriptor + C2 + + Mandatory + C1 + + + + + Optional + + Mandatory + Optional + + + + Optional + + Mandatory + Excluded + + + + + + C1: At least one ESS Characteristic is + exposed. + C1 + + Mandatory + Excluded + Excluded + Excluded + Excluded + Optional + Excluded + Optional + Excluded + Optional + + + + + if_multiple_instances_of_same_characteristic_optional_otherwise + + Mandatory + Excluded + + + + C1: If Write is supported, bonding is + mandatory as described in Section 3.1.2.3.1 of the + Service Specification. If the ES Trigger Setting + descriptor is writable, an ES Configuration descriptor, + if present, is also writable. Otherwise, both are + read-only. + if_notify_supported + + Mandatory + C1 + + + + C1: If Write is supported, bonding is + mandatory as described in Section 3.1.2.3.1 of the + Service Specification. If the ES Trigger Setting + descriptor is writable, an ES Configuration descriptor, + if present, is also writable. Otherwise, both are + read-only. C2: Mandatory if there is more than one ES + Trigger Setting Descriptor + C2 + + Mandatory + C1 + + + + + Optional + + Mandatory + Optional + + + + Optional + + Mandatory + Excluded + + + + + + C1: At least one ESS Characteristic is + exposed. + C1 + + Mandatory + Excluded + Excluded + Excluded + Excluded + Optional + Excluded + Optional + Excluded + Optional + + + + + if_multiple_instances_of_same_characteristic_optional_otherwise + + Mandatory + Excluded + + + + C1: If Write is supported, bonding is + mandatory as described in Section 3.1.2.3.1 of the + Service Specification. If the ES Trigger Setting + descriptor is writable, an ES Configuration descriptor, + if present, is also writable. Otherwise, both are + read-only. + if_notify_supported + + Mandatory + C1 + + + + C1: If Write is supported, bonding is + mandatory as described in Section 3.1.2.3.1 of the + Service Specification. If the ES Trigger Setting + descriptor is writable, an ES Configuration descriptor, + if present, is also writable. Otherwise, both are + read-only. C2: Mandatory if there is more than one ES + Trigger Setting Descriptor + C2 + + Mandatory + C1 + + + + + Optional + + Mandatory + Optional + + + + Optional + + Mandatory + Excluded + + + + + + C1: At least one ESS Characteristic is + exposed. + C1 + + Mandatory + Excluded + Excluded + Excluded + Excluded + Optional + Excluded + Optional + Excluded + Optional + + + + + if_multiple_instances_of_same_characteristic_optional_otherwise + + Mandatory + Excluded + + + + C1: If Write is supported, bonding is + mandatory as described in Section 3.1.2.3.1 of the + Service Specification. If the ES Trigger Setting + descriptor is writable, an ES Configuration descriptor, + if present, is also writable. Otherwise, both are + read-only. + if_notify_supported + + Mandatory + C1 + + + + C1: If Write is supported, bonding is + mandatory as described in Section 3.1.2.3.1 of the + Service Specification. If the ES Trigger Setting + descriptor is writable, an ES Configuration descriptor, + if present, is also writable. Otherwise, both are + read-only. C2: Mandatory if there is more than one ES + Trigger Setting Descriptor + C2 + + Mandatory + C1 + + + + + Optional + + Mandatory + Optional + + + + Optional + + Mandatory + Excluded + + + + + + C1: At least one ESS Characteristic is + exposed. + C1 + + Mandatory + Excluded + Excluded + Excluded + Excluded + Optional + Excluded + Optional + Excluded + Optional + + + + + if_multiple_instances_of_same_characteristic_optional_otherwise + + Mandatory + Excluded + + + + C1: If Write is supported, bonding is + mandatory as described in Section 3.1.2.3.1 of the + Service Specification. If the ES Trigger Setting + descriptor is writable, an ES Configuration descriptor, + if present, is also writable. Otherwise, both are + read-only. + if_notify_supported + + Mandatory + C1 + + + + C1: If Write is supported, bonding is + mandatory as described in Section 3.1.2.3.1 of the + Service Specification. If the ES Trigger Setting + descriptor is writable, an ES Configuration descriptor, + if present, is also writable. Otherwise, both are + read-only. C2: Mandatory if there is more than one ES + Trigger Setting Descriptor + C2 + + Mandatory + C1 + + + + + Optional + + Mandatory + Optional + + + + Optional + + Mandatory + Excluded + + + + + + C1: At least one ESS Characteristic is + exposed. + C1 + + Mandatory + Excluded + Excluded + Excluded + Excluded + Optional + Excluded + Optional + Excluded + Optional + + + + + if_multiple_instances_of_same_characteristic_optional_otherwise + + Mandatory + Excluded + + + + C1: If Write is supported, bonding is + mandatory as described in Section 3.1.2.3.1 of the + Service Specification. If the ES Trigger Setting + descriptor is writable, an ES Configuration descriptor, + if present, is also writable. Otherwise, both are + read-only. + if_notify_supported + + Mandatory + C1 + + + + C1: If Write is supported, bonding is + mandatory as described in Section 3.1.2.3.1 of the + Service Specification. If the ES Trigger Setting + descriptor is writable, an ES Configuration descriptor, + if present, is also writable. Otherwise, both are + read-only. C2: Mandatory if there is more than one ES + Trigger Setting Descriptor + C2 + + Mandatory + C1 + + + + + Optional + + Mandatory + Optional + + + + Optional + + Mandatory + Excluded + + + + + + C1: At least one ESS Characteristic is + exposed. + C1 + + Mandatory + Excluded + Excluded + Excluded + Excluded + Optional + Excluded + Optional + Excluded + Optional + + + + + if_multiple_instances_of_same_characteristic_optional_otherwise + + Mandatory + Excluded + + + + C1: If Write is supported, bonding is + mandatory as described in Section 3.1.2.3.1 of the + Service Specification. If the ES Trigger Setting + descriptor is writable, an ES Configuration descriptor, + if present, is also writable. Otherwise, both are + read-only. + if_notify_supported + + Mandatory + C1 + + + + C1: If Write is supported, bonding is + mandatory as described in Section 3.1.2.3.1 of the + Service Specification. If the ES Trigger Setting + descriptor is writable, an ES Configuration descriptor, + if present, is also writable. Otherwise, both are + read-only. C2: Mandatory if there is more than one ES + Trigger Setting Descriptor + C2 + + Mandatory + C1 + + + + + Optional + + Mandatory + Optional + + + + Optional + + Mandatory + Excluded + + + + + + C1: At least one ESS Characteristic is + exposed. + C1 + + Mandatory + Excluded + Excluded + Excluded + Excluded + Optional + Excluded + Optional + Excluded + Optional + + + + + if_multiple_instances_of_same_characteristic_optional_otherwise + + Mandatory + Excluded + + + + C1: If Write is supported, bonding is + mandatory as described in Section 3.1.2.3.1 of the + Service Specification. If the ES Trigger Setting + descriptor is writable, an ES Configuration descriptor, + if present, is also writable. Otherwise, both are + read-only. + if_notify_supported + + Mandatory + C1 + + + + C1: If Write is supported, bonding is + mandatory as described in Section 3.1.2.3.1 of the + Service Specification. If the ES Trigger Setting + descriptor is writable, an ES Configuration descriptor, + if present, is also writable. Otherwise, both are + read-only. C2: Mandatory if there is more than one ES + Trigger Setting Descriptor + C2 + + Mandatory + C1 + + + + + Optional + + Mandatory + Optional + + + + Optional + + Mandatory + Excluded + + + + + + C1: At least one ESS Characteristic is + exposed. + C1 + + Mandatory + Excluded + Excluded + Excluded + Excluded + Optional + Excluded + Optional + Excluded + Optional + + + + + if_multiple_instances_of_same_characteristic_optional_otherwise + + Mandatory + Excluded + + + + C1: If Write is supported, bonding is + mandatory as described in Section 3.1.2.3.1 of the + Service Specification. If the ES Trigger Setting + descriptor is writable, an ES Configuration descriptor, + if present, is also writable. Otherwise, both are + read-only. + if_notify_supported + + Mandatory + C1 + + + + C1: If Write is supported, bonding is + mandatory as described in Section 3.1.2.3.1 of the + Service Specification. If the ES Trigger Setting + descriptor is writable, an ES Configuration descriptor, + if present, is also writable. Otherwise, both are + read-only. C2: Mandatory if there is more than one ES + Trigger Setting Descriptor + C2 + + Mandatory + C1 + + + + + Optional + + Mandatory + Optional + + + + Optional + + Mandatory + Excluded + + + + + + C1: At least one ESS Characteristic is + exposed. + C1 + + Mandatory + Excluded + Excluded + Excluded + Excluded + Optional + Excluded + Optional + Excluded + Optional + + + + + if_multiple_instances_of_same_characteristic_optional_otherwise + + Mandatory + Excluded + + + + C1: If Write is supported, bonding is + mandatory as described in Section 3.1.2.3.1 of the + Service Specification. If the ES Trigger Setting + descriptor is writable, an ES Configuration descriptor, + if present, is also writable. Otherwise, both are + read-only. + if_notify_supported + + Mandatory + C1 + + + + C1: If Write is supported, bonding is + mandatory as described in Section 3.1.2.3.1 of the + Service Specification. If the ES Trigger Setting + descriptor is writable, an ES Configuration descriptor, + if present, is also writable. Otherwise, both are + read-only. C2: Mandatory if there is more than one ES + Trigger Setting Descriptor + C2 + + Mandatory + C1 + + + + + Optional + + Mandatory + Optional + + + + Optional + + Mandatory + Excluded + + + + + + C1: At least one ESS Characteristic is + exposed. + C1 + + Mandatory + Excluded + Excluded + Excluded + Excluded + Optional + Excluded + Optional + Excluded + Optional + + + + + if_multiple_instances_of_same_characteristic_optional_otherwise + + Mandatory + Excluded + + + + C1: If Write is supported, bonding is + mandatory as described in Section 3.1.2.3.1 of the + Service Specification. If the ES Trigger Setting + descriptor is writable, an ES Configuration descriptor, + if present, is also writable. Otherwise, both are + read-only. + if_notify_supported + + Mandatory + C1 + + + + C1: If Write is supported, bonding is + mandatory as described in Section 3.1.2.3.1 of the + Service Specification. If the ES Trigger Setting + descriptor is writable, an ES Configuration descriptor, + if present, is also writable. Otherwise, both are + read-only. C2: Mandatory if there is more than one ES + Trigger Setting Descriptor + C2 + + Mandatory + C1 + + + + + Optional + + Mandatory + Optional + + + + Optional + + Mandatory + Excluded + + + + + + C1: At least one ESS Characteristic is + exposed. + C1 + + Mandatory + Excluded + Excluded + Excluded + Excluded + Optional + Excluded + Optional + Excluded + Optional + + + + + if_multiple_instances_of_same_characteristic_optional_otherwise + + Mandatory + Excluded + + + + C1: If Write is supported, bonding is + mandatory as described in Section 3.1.2.3.1 of the + Service Specification. If the ES Trigger Setting + descriptor is writable, an ES Configuration descriptor, + if present, is also writable. Otherwise, both are + read-only. + if_notify_supported + + Mandatory + C1 + + + + C1: If Write is supported, bonding is + mandatory as described in Section 3.1.2.3.1 of the + Service Specification. If the ES Trigger Setting + descriptor is writable, an ES Configuration descriptor, + if present, is also writable. Otherwise, both are + read-only. C2: Mandatory if there is more than one ES + Trigger Setting Descriptor + C2 + + Mandatory + C1 + + + + + Optional + + Mandatory + Optional + + + + Optional + + Mandatory + Excluded + + + + + + C1: At least one ESS Characteristic is + exposed. + C1 + + Mandatory + Excluded + Excluded + Excluded + Excluded + Optional + Excluded + Optional + Excluded + Optional + + + + + if_multiple_instances_of_same_characteristic_optional_otherwise + + Mandatory + Excluded + + + + C1: If Write is supported, bonding is + mandatory as described in Section 3.1.2.3.1 of the + Service Specification. If the ES Trigger Setting + descriptor is writable, an ES Configuration descriptor, + if present, is also writable. Otherwise, both are + read-only. + if_notify_supported + + Mandatory + C1 + + + + C1: If Write is supported, bonding is + mandatory as described in Section 3.1.2.3.1 of the + Service Specification. If the ES Trigger Setting + descriptor is writable, an ES Configuration descriptor, + if present, is also writable. Otherwise, both are + read-only. C2: Mandatory if there is more than one ES + Trigger Setting Descriptor + C2 + + Mandatory + C1 + + + + + Optional + + Mandatory + Optional + + + + Optional + + Mandatory + Excluded + + + + + + C1: At least one ESS Characteristic is + exposed. + C1 + + Mandatory + Excluded + Excluded + Excluded + Excluded + Optional + Excluded + Optional + Excluded + Optional + + + + + if_multiple_instances_of_same_characteristic_optional_otherwise + + Mandatory + Excluded + + + + C1: If Write is supported, bonding is + mandatory as described in Section 3.1.2.3.1 of the + Service Specification. If the ES Trigger Setting + descriptor is writable, an ES Configuration descriptor, + if present, is also writable. Otherwise, both are + read-only. + if_notify_supported + + Mandatory + C1 + + + + C1: If Write is supported, bonding is + mandatory as described in Section 3.1.2.3.1 of the + Service Specification. If the ES Trigger Setting + descriptor is writable, an ES Configuration descriptor, + if present, is also writable. Otherwise, both are + read-only. C2: Mandatory if there is more than one ES + Trigger Setting Descriptor + C2 + + Mandatory + C1 + + + + + Optional + + Mandatory + Optional + + + + Optional + + Mandatory + Excluded + + + + + + C1: At least one ESS Characteristic is + exposed. + C1 + + Mandatory + Excluded + Excluded + Excluded + Excluded + Optional + Excluded + Optional + Excluded + Optional + + + + + if_multiple_instances_of_same_characteristic_optional_otherwise + + Mandatory + Excluded + + + + C1: If Write is supported, bonding is + mandatory as described in Section 3.1.2.3.1 of the + Service Specification. If the ES Trigger Setting + descriptor is writable, an ES Configuration descriptor, + if present, is also writable. Otherwise, both are + read-only. + if_notify_supported + + Mandatory + C1 + + + + C1: If Write is supported, bonding is + mandatory as described in Section 3.1.2.3.1 of the + Service Specification. If the ES Trigger Setting + descriptor is writable, an ES Configuration descriptor, + if present, is also writable. Otherwise, both are + read-only. C2: Mandatory if there is more than one ES + Trigger Setting Descriptor + C2 + + Mandatory + C1 + + + + + Optional + + Mandatory + Optional + + + + Optional + + Mandatory + Excluded + + + + + + diff --git a/org.bluetooth.service.fitness_machine.xml b/org.bluetooth.service.fitness_machine.xml new file mode 100644 index 0000000..d5f3727 --- /dev/null +++ b/org.bluetooth.service.fitness_machine.xml @@ -0,0 +1,378 @@ + + + + + This service exposes training-related data in the + sports and fitness environment, which allows a Server (e.g., a + fitness machine) to send training-related data to a + Client. + The Fitness Machine Service (FTMS) exposes + training-related data in the sports and fitness environment, + which allows a Client to collect training data while a user is + exercising with a fitness machine (Server). + + + This service has no dependencies on other + GATT-based services. + + + + Mandatory + + Mandatory + C.1 + Optional + + C1: Mandatory if the Fitness Machine Control Point is + supported, otherwise Optional. + + true + true + true + + + + Mandatory + + Mandatory + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + + + + Optional + + Excluded + Excluded + Excluded + Excluded + Excluded + Mandatory + Excluded + Excluded + Excluded + + + + + Mandatory + + Mandatory + Mandatory + + + + + + Optional + + Excluded + Excluded + Excluded + Excluded + Excluded + Mandatory + Excluded + Excluded + Excluded + + + + + Mandatory + + Mandatory + Mandatory + + + + + + Optional + + Excluded + Excluded + Excluded + Excluded + Excluded + Mandatory + Excluded + Excluded + Excluded + + + + + Mandatory + + Mandatory + Mandatory + + + + + + Optional + + Excluded + Excluded + Excluded + Excluded + Excluded + Mandatory + Excluded + Excluded + Excluded + + + + + Mandatory + + Mandatory + Mandatory + + + + + + Optional + + Excluded + Excluded + Excluded + Excluded + Excluded + Mandatory + Excluded + Excluded + Excluded + + + + + Mandatory + + Mandatory + Mandatory + + + + + + Optional + + Excluded + Excluded + Excluded + Excluded + Excluded + Mandatory + Excluded + Excluded + Excluded + + + + + Mandatory + + Mandatory + Mandatory + + + + + + Optional + + Mandatory + Excluded + Excluded + Excluded + Excluded + Mandatory + Excluded + Excluded + Excluded + + + + + Mandatory + + Mandatory + Mandatory + + + + + + C1 + + C1: Mandatory if the Speed Target Setting + feature is supported; otherwise Optional. + Mandatory + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + + + + C2 + + C2: Mandatory if the Inclination Target + Setting feature is supported; otherwise + Optional. + Mandatory + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + + + + C3 + + C3: Mandatory if the Resistance Target + Setting feature is supported; otherwise + Optional. + Mandatory + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + + + + C4 + + C4: Mandatory if the Power Target Setting + feature is supported; otherwise Optional. + Mandatory + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + + + + C5 + + C5: Mandatory if the Heart Rate Target + Setting feature is supported; otherwise + Optional. + Mandatory + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + + + + Optional + + Excluded + Mandatory + Excluded + Excluded + Excluded + Excluded + Mandatory + Excluded + Excluded + + + + + Mandatory + + Mandatory + Mandatory + + + + + + C6 + + C6: Mandatory if the Fitness Machine + Control Point is supported; otherwise + Optional. + Excluded + Excluded + Excluded + Excluded + Excluded + Mandatory + Excluded + Excluded + Excluded + + + + + Mandatory + + Mandatory + Mandatory + + + + + + diff --git a/org.bluetooth.service.generic_access.xml b/org.bluetooth.service.generic_access.xml new file mode 100644 index 0000000..44819c6 --- /dev/null +++ b/org.bluetooth.service.generic_access.xml @@ -0,0 +1,104 @@ + + + + + The generic_access service contains generic + information about the device. All available Characteristics are + readonly. + + + + Mandatory + + Mandatory + Optional + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + + + + Mandatory + + Mandatory + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + + + + + Optional + + C1: Optional if supports only 1 bond, + excluded if the device supports more than one + bonding + Mandatory + C1 + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + + + + Conditional + + Excluded + Mandatory + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + + + + + Optional + + Mandatory + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + + + + + + If the Peripheral Privacy Flag + Characteristic is implemented, then the Reconnection Address + Characteristic must also be implemented + + org.bluetooth.characteristic.peripheral_privacy_flag + Reconnection Address + + + diff --git a/org.bluetooth.service.generic_attribute.xml b/org.bluetooth.service.generic_attribute.xml new file mode 100644 index 0000000..3525f06 --- /dev/null +++ b/org.bluetooth.service.generic_attribute.xml @@ -0,0 +1,25 @@ + + + + + + + Optional + + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + Mandatory + Excluded + Excluded + + + + diff --git a/org.bluetooth.service.glucose.xml b/org.bluetooth.service.glucose.xml new file mode 100644 index 0000000..9044eeb --- /dev/null +++ b/org.bluetooth.service.glucose.xml @@ -0,0 +1,151 @@ + + + + + This service exposes glucose and other data from a + glucose sensor for use in consumer and professional healthcare + applications. + The Glucose Service exposes glucose and other data + related to a glucose sensor for consumer and professional + healthcare applications. + + + This service has no dependencies on other + GATT-based services. + + + + Manadatory + + Mandatory + Mandatory + + Mandatory + + Mandatory + + + false + true + + + + The Glucose Measurement characteristic is + used to send glucose measurements. + Mandatory + + Excluded + Excluded + Excluded + Excluded + Excluded + Mandatory + Excluded + Excluded + Excluded + + + + + Mandatory + + Mandatory + Mandatory + + + + + + + The Glucose Measurement Context + characteristic is used to send additional contextual + information relative to a Glucose Measurement + characteristic. + Optional + + Excluded + Excluded + Excluded + Excluded + Excluded + Mandatory + Excluded + Excluded + Excluded + + + + + if_characteristic_supported + + Mandatory + Mandatory + + + + + + The Glucose Feature characteristic is used + to describe the supported features of the + Server. + Mandatory + + Mandatory + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + + + + + +

This Record Access Control Point (RACP) characteristic + value consists of the following fields to use for patient + record access management.

+

? Op Code (Request/Response code)

+

? Operator (specifies how the Operand is applied)

+

? Operand (parameters)

+ + Mandatory + + Excluded + Mandatory + Excluded + Excluded + Excluded + Excluded + Mandatory + Excluded + Excluded + + + Writable With Authentication + + + + + Mandatory + + Mandatory + Mandatory + + + + + + diff --git a/org.bluetooth.service.health_thermometer.xml b/org.bluetooth.service.health_thermometer.xml new file mode 100644 index 0000000..3c15a98 --- /dev/null +++ b/org.bluetooth.service.health_thermometer.xml @@ -0,0 +1,164 @@ + + + + + The Health Thermometer service exposes temperature + and other data from a thermometer intended for healthcare and + fitness applications. + The Health Thermometer service is instantiated as a + Primary Service. There are one or more instantiations of the + Health Thermometer service per device claiming conformance with + this specification. + + + This service is not dependent upon any other + services. + + + + Mandatory if the Write property for the Measurement Interval + characteristic is supported, otherwise excluded for this + service. + Mandatory if the + Intermediate Temperature characteristic is supported, otherwise + excluded for this service. + Mandatory + + Mandatory + + Mandatory + + + false + true + + + The value is + considered invalid and outside of the range allowed by the + characteristic. + + + + This characteristic is used to send a + temperature measurement. + Mandatory + + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + Mandatory + Excluded + Excluded + + + + + Mandatory + + Mandatory + Mandatory + + + + + + This characteristic is used to describe the + type of temperature measurement in relation to the location + on the human body at which the temperature was + measured. + Optional + + Mandatory + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + + + + This characteristic is used to send + intermediate temperature values to a device for display + purposes while the measurement is in + progress. + Optional + + Excluded + Excluded + Excluded + Excluded + Excluded + Mandatory + Excluded + Excluded + Excluded + + + + + if_characteristic_supported + + Mandatory + Mandatory + + + + + + This characteristic is used to enable and + control the interval between consecutive temperature + measurements. + Optional + + Mandatory + Optional + Excluded + Excluded + Excluded + Excluded + Optional + Excluded + Excluded + + + Writable With Authentication + + + + + + if_notify_or_indicate_supported + + Mandatory + Mandatory + + + + + if_characteristic_write_supported + + Mandatory + Excluded + + + + + + diff --git a/org.bluetooth.service.heart_rate.xml b/org.bluetooth.service.heart_rate.xml new file mode 100644 index 0000000..9b630f0 --- /dev/null +++ b/org.bluetooth.service.heart_rate.xml @@ -0,0 +1,109 @@ + + + + + This service exposes heart rate and other data from a + Heart Rate Sensor intended for fitness applications. + The HEART RATE Service exposes heart rate and other + data related to a heart rate sensor intended for fitness + applications. + + + This service is not dependent upon any other + services. + + + + Mandatory if the Heart Rate Control Point characteristic is + supported, otherwise excluded for this service. + + Mandatory + + Mandatory + + Mandatory + + + false + true + + + Heart rate Control Point value not + supported. + + + + This characteristic is used to send a heart + rate measurement. + Mandatory + + Excluded + Excluded + Excluded + Excluded + Excluded + Mandatory + Excluded + Excluded + Excluded + + + + + Mandatory + + Mandatory + Mandatory + + + + + + The Body Sensor Location characteristic of + the device is used to describe the intended location of the + heart rate measurement for the device. + Optional + + Mandatory + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + + + + +

The Heart Rate Control Point characteristic is used to + enable a Client to write control points to a Server to + control behavior.

+

Note: This charateristic is conditional. The + charatersitic is Mandatory if the Energy Expended feature + is supported, otherwise excluded.

+ + Conditional + + Excluded + Mandatory + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + + + + diff --git a/org.bluetooth.service.http_proxy.xml b/org.bluetooth.service.http_proxy.xml new file mode 100644 index 0000000..97a2c11 --- /dev/null +++ b/org.bluetooth.service.http_proxy.xml @@ -0,0 +1,141 @@ + + + + + This service allows a Client device, typically a + sensor, to communicate with a Web Server through a gateway + device. The gateway device implements the HTTP Proxy Service + and therefore provides the services available through the + Internet to the Client sensor device. + The HTTP Proxy Service (HPS) allows a device to expose + HTTP Web Services to a client. This enables an HPS client + device to program a set of characteristics that configures a + Hyper Text Transfer Protocol (HTTP) request, initiate this, + request, and then read the response. + + + This service is not dependent upon any other + services. + + + + Mandatory + + Mandatory + + Mandatory + + Mandatory + + Mandatory + + Mandatory + + + true + true + true + + + + + + + + + Mandatory + + Excluded + Mandatory + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + + + + Mandatory + + Mandatory + Mandatory + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + + + + Mandatory + + Mandatory + Mandatory + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + + + + Mandatory + + Excluded + Mandatory + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + + + + Mandatory + + Excluded + Excluded + Excluded + Excluded + Excluded + Mandatory + Excluded + Excluded + Excluded + + + + Mandatory + + Mandatory + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + + + + diff --git a/org.bluetooth.service.human_interface_device.xml b/org.bluetooth.service.human_interface_device.xml new file mode 100644 index 0000000..28cab78 --- /dev/null +++ b/org.bluetooth.service.human_interface_device.xml @@ -0,0 +1,309 @@ + + + + + + This service exposes the HID reports and other HID + data intended for HID Hosts and HID Devices. + The HID Service exposes characteristics required for a + HID Device to transfer HID report descriptors and reports to a + HID Host. This also exposes the characteristics for a HID Host + to write to a Device. The Human Interface Device Service is + instantiated as a Primary Service. + + + This service has no dependencies on other + GATT-based services. + + + + Mandatory + + Mandatory + + Mandatory + + Mandatory + + Mandatory + + Mandatory + + + false + true + + + + + The Protocol Mode characteristic is used to + expose the current protocol mode of the HID Service with + which it is associated, or to set the desired protocol mode + of the HID Service +

Only a single instance of this characteristic shall exist + as part of the HID Service.

+

+ C4:Mandatory for HID Devices supporting Boot Protocol + Mode, otherwise optional.

 + C4 + + Mandatory + Excluded + Mandatory + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + + + + +

The Report characteristic is used to exchange data + between a HID Device and a HID Host.

+

+ Note: Mandatory to support at least one Report Type + (Input Report, Output Report, or Feature Report) if the + Report characteristic is supported. +

+ + Optional + + For Input Reports: + Mandatory + Optional + Excluded + Excluded + Excluded + Mandatory + Excluded + Excluded + Excluded + + + For Output Reports: + Mandatory + Mandatory + Mandatory + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + + + For Feature Reports: + Mandatory + Mandatory + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + + + + + + if_notify_or_indicate_supported + + Mandatory + Mandatory + + + + The Report Reference characteristic + descriptor is used to provide the Report ID and Report + Type for the Report characteristic + value. + if_characteristic_supported + + Mandatory + Excluded + + + + + + The Report Map characteristic value contains + formatting and other information for Input Report, Output + Report and Feature Report data transferred between a HID + Device and HID Host. + Mandatory + + Mandatory + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + + + + Optional + + Mandatory + Excluded + + + + + + +

The Boot Report Reference characteristic is used to + provide HID Hosts operating in Boot Protocol Mode with a + simplified method of discovering certain HID Service + characteristics. Only a single instance of this + characteristic exists as part of the HID Service.

+

+ C2:Mandatory for HID Devices operating as keyboards, + else excluded.

+ + C2 + + Mandatory + Optional + Excluded + Excluded + Excluded + Mandatory + Excluded + Excluded + Excluded + + + + + Mandatory + + Mandatory + Mandatory + + + + + + + +

The Boot Report Reference characteristic is used to + provide HID Hosts operating in Boot Protocol Mode with a + simplified method of discovering certain HID Service + characteristics. Only a single instance of this + characteristic exists as part of the HID Service.

+

+ C2:Mandatory for HID Devices operating as keyboards, + else excluded.

+ + C2 + + Mandatory + Mandatory + Mandatory + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + + + + +

The Boot Report Reference characteristic is used to + provide HID Hosts operating in Boot Protocol Mode with a + simplified method of discovering certain HID Service + characteristics. Only a single instance of this + characteristic exists as part of the HID Service.

+

+ C3:Mandatory for HID Devices operating as mice, else + excluded.

+ + C3 + + Mandatory + Optional + Excluded + Excluded + Excluded + Mandatory + Excluded + Excluded + Excluded + + + + + Mandatory + + Mandatory + Mandatory + + + + + + The HID Information characteristic is used + to hold a set of values known as the HID Device?s HID + Attributes + Mandatory + + Mandatory + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + + + + The HID Control Point characteristic is a + control-point attribute that defines the following HID + Commands when written: +

? Suspend ( Refer to Section 7.4.2, Bluetooth HID Profile + Specification 1.0)

+

? Exit Suspend (Refer to Section 7.4.2, Bluetooth HID + Profile Specification 1.0)

There are no response codes + defined for the Suspend and Exit Suspend + commands. + Mandatory + + Excluded + Excluded + Mandatory + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + + + + diff --git a/org.bluetooth.service.immediate_alert.xml b/org.bluetooth.service.immediate_alert.xml new file mode 100644 index 0000000..dcbd136 --- /dev/null +++ b/org.bluetooth.service.immediate_alert.xml @@ -0,0 +1,60 @@ + + + + + This service exposes a control point to allow a peer + device to cause the device to immediately alert. + The Immediate Alert service is instantiated as a + Primary Service. There is only one instance of the Immediate + Alert service on a device. There is only one instance of the + Alert Level characteristic in an Immediate Alert service. This + alert continues until one of following conditions occurs: ? An + implementation specific timeout ? User interaction on this + device ? A new alert level is written ? The physical link is + disconnected + + If the written alert level is ?No Alert?, no + alerting is done on this device. + If the written alert level is ?Mild Alert?, the + device alerts. + If the written alert level is ?High Alert?, the + device alerts in the strongest possible way. + + + + This service has no dependencies on other + GATT-based services + + + + Mandatory + + + true + true + + + + + The Alert Level characteristic is a control + point that allows a peer to command this device to alert to a + given level. + Mandatory + + Excluded + Excluded + Mandatory + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + + + + diff --git a/org.bluetooth.service.indoor_positioning.xml b/org.bluetooth.service.indoor_positioning.xml new file mode 100644 index 0000000..36e173e --- /dev/null +++ b/org.bluetooth.service.indoor_positioning.xml @@ -0,0 +1,323 @@ + + + + + The Indoor Positioning Service exposes location + information to support e.g. mobile handsets to position + themselves in an environment where GPS signal is not available, + like indoor premises. + The service shall be either a Primary Service or + Secondary Service and the service UUID set to Indoor + Positioning Service. + + + This service has no dependencies on other + GATT-based services. + + + + Mandatory + + Mandatory + + Mandatory + + C1 + + C1: Mandatory if location name size greater than ATT_MTU-1 + is supported by the device + C2: Mandatory: If Characteristic is configurable via an ATT + bearer, else optional + + false + true + + + An attempt + was made to write a value to the descriptor that is invalid + (e.g. out of range) or not supported by this + Server. + + + + + The Indoor Positioning Configuration + characteristic describes the set of characteristic values + included in the Indoor Positioning Service AD + type. + Mandatory + + Mandatory + C2 + Optional + Excluded + Optional + Excluded + Excluded + Excluded + Excluded + + + Writable With Authentication + + + + The Latitude characteristic describes the + WGS84 North coordinate of the device. + Mandatory + + Mandatory + C2 + Optional + Excluded + Optional + Excluded + Excluded + Excluded + Optional + + + Writable With Authentication + + + + + if_broadcast_supported + + Mandatory + Mandatory + + + + + + The Longitude characteristic describes the + WGS84 East coordinate of the device. + Mandatory + + Mandatory + C2 + Optional + Excluded + Optional + Excluded + Excluded + Excluded + Optional + + + Writable With Authentication + + + + + if_broadcast_supported + + Mandatory + Mandatory + + + + + + The Local North Coordinate characteristic + describes the North coordinate of the device using local + coordinate system. + Optional + + Mandatory + C2 + Optional + Excluded + Optional + Excluded + Excluded + Excluded + Optional + + + Writable With Authentication + + + + + if_broadcast_supported + + Mandatory + Mandatory + + + + + + The Local East Coordinate characteristic + describes the East coordinate of the device using local + coordinate system. C3: Mandatory if Local North is present + else excluded. + C3 + + Mandatory + C2 + Optional + Excluded + Optional + Excluded + Excluded + Excluded + Optional + + + Writable With Authentication + + + + + if_broadcast_supported + + Mandatory + Mandatory + + + + + + The Floor Number characteristic describes in + which floor the device is installed in. + Optional + + Mandatory + C2 + Optional + Excluded + Optional + Excluded + Excluded + Excluded + Optional + + + Writable With Authentication + + + + + if_broadcast_supported + + Mandatory + Mandatory + + + + + + The Altitude characteristic describes the + altitude of the device. + Optional + + Mandatory + C2 + Optional + Excluded + Optional + Excluded + Excluded + Excluded + Optional + + + Writable With Authentication + + + + + if_broadcast_supported + + Mandatory + Mandatory + + + + + + The Uncertainty characteristic describes the + uncertainty of the location information the device + exposes. + Optional + + Mandatory + C2 + Optional + Excluded + Optional + Excluded + Excluded + Excluded + Optional + + + Writable With Authentication + + + + + if_broadcast_supported + + Mandatory + Mandatory + + + + + + The Location Name characteristic describes + the name of the location the device is installed + in. + Optional + + Mandatory + C2 + Optional + Excluded + Optional + Excluded + Excluded + Excluded + Optional + + + Writable With Authentication + + + + + if_broadcast_supported + + Mandatory + Mandatory + + + + + + diff --git a/org.bluetooth.service.internet_protocol_support.xml b/org.bluetooth.service.internet_protocol_support.xml new file mode 100644 index 0000000..4de44e0 --- /dev/null +++ b/org.bluetooth.service.internet_protocol_support.xml @@ -0,0 +1,26 @@ + + + + + When in a GAP Discoverable Mode for an initial + connection to a Router, the Node will include the IP Support + Service UUID 0x1820 in the Service UUIDs AD type field of the + advertising data. This enhances the user experience as a Node + may be identified by the Router before initiating a + connection. + This service does not define any + characteristics + + + This service has no dependencies on other + GATT-based services. + + + false + true + + diff --git a/org.bluetooth.service.link_loss.xml b/org.bluetooth.service.link_loss.xml new file mode 100644 index 0000000..59abd60 --- /dev/null +++ b/org.bluetooth.service.link_loss.xml @@ -0,0 +1,62 @@ + + + + + This service defines behavior when a link is lost + between two devices. + The LINK LOSS Service is instantiated as a Primary + Service. There is only one instance of the Link Loss Service on + a device. There is only one instance of the Alert Level + characteristic in a Link Loss Service. This alert continues + until one of following conditions occurs: ? An implementation + specific timeout ? User interaction on this device ? A new + alert level is written ? The physical link is + disconnected + + If the current link loss alert level is ?No Alert?, + no alerting is done on this device. + If the current link loss alert level is ?Mild + Alert?, the device alerts. + If the current link loss alert level is ?High + Alert?, the device alerts in the strongest possible + way. + + + + This service has no dependencies on other + GATT-based services. + + + + Mandatory + + + true + true + + + + + The Alert Level characteristic is used to + expose the current link loss alert level that is used to + determine how the device alerts when the link is + lost. + Mandatory + + Mandatory + Mandatory + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + + + + diff --git a/org.bluetooth.service.location_and_navigation.xml b/org.bluetooth.service.location_and_navigation.xml new file mode 100644 index 0000000..c72204f --- /dev/null +++ b/org.bluetooth.service.location_and_navigation.xml @@ -0,0 +1,154 @@ + + + + + This service exposes location and navigation-related + data from a Location and Navigation sensor intended for outdoor + activity applications. + The Location and Navigation Service (LN Service) + exposes location and navigation-related data from a Location + and Navigation sensor (Server) intended for outdoor activity + applications. + + + This service has no dependencies on other + GATT-based services. + + + + C.1 + + Mandatory + C.1 + + Mandatory + + Mandatory + + C.1: Mandatory if the LN Control Point characteristic is + supported, otherwise excluded for this service. + + true + true + true + + + + Mandatory + + Mandatory + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + + + + Mandatory + + Excluded + Excluded + Excluded + Excluded + Excluded + Mandatory + Excluded + Excluded + Excluded + + + + + Mandatory + + Mandatory + Mandatory + + + + + + Optional + + Mandatory + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + + + + + Optional + + Excluded + Mandatory + Excluded + Excluded + Excluded + Excluded + Mandatory + Excluded + Excluded + + + + + if_characteristic_supported + + Mandatory + Mandatory + + + + + + C2: Mandatory if the Navigation feature is + supported, otherwise excluded. + C2 + + Excluded + Excluded + Excluded + Excluded + Excluded + Mandatory + Excluded + Excluded + Excluded + + + + + if_characteristic_supported + + Mandatory + Mandatory + + + + + + diff --git a/org.bluetooth.service.next_dst_change.xml b/org.bluetooth.service.next_dst_change.xml new file mode 100644 index 0000000..be6df80 --- /dev/null +++ b/org.bluetooth.service.next_dst_change.xml @@ -0,0 +1,41 @@ + + + + + This service defines how the information about an + upcoming DST change can be exposed using the Generic Attribute + Profile (GATT). + This service enables a Bluetooth device that has + knowledge about the next occurrence of a DST change to expose + this information to another Bluetooth device. + + + This service has no dependencies on other + GATT-based services. + + + false + true + + + + + Mandatory + + Mandatory + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + + + + diff --git a/org.bluetooth.service.object_transfer.xml b/org.bluetooth.service.object_transfer.xml new file mode 100644 index 0000000..f8460d8 --- /dev/null +++ b/org.bluetooth.service.object_transfer.xml @@ -0,0 +1,311 @@ + + + + + This service provides management and control features + supporting bulk data transfers which occur via a separate L2CAP + connection oriented channel. The Client is enabled to create + and delete objects and to execute an action using the currently + selected object. The selected object can be written, updated or + read via an Object Transfer Channel opened by the Client. The + generation of a checksum covering a part or the whole of the + object contents is included as an optional feature. This + service provides a general method for a Client to select and + initiate the transfer of any type of object. + . + + + This service is not dependent upon any other + services. + + + + Mandatory + + Mandatory + + Mandatory + Mandatory + + C1 + + C2 + + C1: Mandatory if the Server supports an Object Name + characteristic value that may exceed (ATT_MTU-1) octets in + length, where ATT_MTU is the default size for the transport being + used; optional otherwise. C2: Mandatory if the Server supports an + Object Name characteristic value that may exceed (ATT_MTU-3) + octets in length, where ATT_MTU is the default size for the + transport being used, and the characteristic is writable; + optional otherwise. + + true + true + true + + + + + + + + + + Mandatory + + Mandatory + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + + + Encryption is mandatory + + + + C1:Mandatory if the Server is capable of + storing more than one object within the context of this + instance of the service; optional otherwise. C3:Mandatory if + the OACP Create op code is supported; optional + otherwise. + C1 + + Mandatory + C3 + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + + + Encryption is mandatory + + + + Mandatory + + Mandatory + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + + + Encryption is mandatory + + + + Mandatory + + Mandatory + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + + + Encryption is mandatory + + + + C3: Mandatory if the OACP Create op code is + supported; optional otherwise. + Optional + + Mandatory + C3 + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + + + Encryption is mandatory + + + + C4: Mandatory if the Server does not have + access to a real time clock; excluded + otherwise. + Optional + + Mandatory + C4 + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + + + Encryption is mandatory + + + + C1: Mandatory if the Server is capable of + storing more than one object; excluded + otherwise. + C1 + + Mandatory + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + + + Encryption is mandatory + + + + Mandatory + + Mandatory + Optional + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + + + Encryption is mandatory + + + + Mandatory + + Excluded + Mandatory + Excluded + Excluded + Excluded + Excluded + Mandatory + Excluded + Excluded + Excluded + + + Encryption is mandatory + + + + C1:Mandatory if the Server is capable of + storing more than one object within the context of this + instance of the service; optional + otherwise. + C1 + + Excluded + Mandatory + Excluded + Excluded + Excluded + Excluded + Mandatory + Excluded + Excluded + Excluded + + + Encryption is mandatory + + + + C2:Optional if the Server is capable of + storing more than one object; excluded + otherwise. + C2 + + Mandatory + Mandatory + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + + + Encryption is mandatory + + + + Optional + + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + Mandatory + Excluded + Excluded + Excluded + + + Encryption is mandatory + + + + diff --git a/org.bluetooth.service.phone_alert_status.xml b/org.bluetooth.service.phone_alert_status.xml new file mode 100644 index 0000000..6aa5adc --- /dev/null +++ b/org.bluetooth.service.phone_alert_status.xml @@ -0,0 +1,136 @@ + + + + + This service dexposes the phone alert status when in + a connection. + The Phone Alert Status service uses the Alert Status + characteristic, Ringer Setting characteristic to expose the + phone alert status and Ringer Control Point characteristic to + control phone into mute or enable. + + + This service has no dependencies on other + GATT-based services. + + + + Mandatory + + Mandatory + + Mandatory + + Mandatory + + + false + true + + + + + The Alert Status Characteristic includes + three fields of information to express the alerting status as + follows. +

? Ringer State

+

? Vibrator State

+

? Display Alert State

The Alert Status characteristic + returns the current value of Phone Alert Status when + read. + Mandatory + + Mandatory + Excluded + Excluded + Excluded + Excluded + Mandatory + Excluded + Excluded + Excluded + + + + + Mandatory + + Mandatory + Mandatory + + + + + + The Ringer Setting characteristic returns + the current value of the Ringer Setting when + read. + Mandatory + + Mandatory + Excluded + Excluded + Excluded + Excluded + Mandatory + Excluded + Excluded + Excluded + + + + + Mandatory + + Mandatory + Mandatory + + + + + + When the Ringer Control Point characteristic + is written, the server device performs an action based on the + value (command). +

? The server device implements a state machine with two + states, ?Ringer Silent? and ?Ringer Normal?.

+

? The command ?Set Silent Mode? sets the state to ?Ringer + Silent?.

+

? The command ?Cancel Silent Mode? sets the state to + ?Ringer Normal?.

+

? The command ?Mute Once? silences the server device?s + ringer.

+

? The server device?s ringer is silenced when the state is + ?Ringer Silent? and act according to phone settings when the + state is ?Ringer Normal?.

+

Note: The Alert Status and Ringer Setting characteristics + reflects the state of the alerting and ringer setting of the + server device. These states normally change when the state + machine changes or other events (like incoming call or user + interaction) happens on the server device. However there is + no direct coupling from writing to the control point to the + values of Phone Alert Status and Ringer + Setting.

 + Mandatory + + Excluded + Excluded + Mandatory + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + + + + diff --git a/org.bluetooth.service.pulse_oximeter.xml b/org.bluetooth.service.pulse_oximeter.xml new file mode 100644 index 0000000..c736790 --- /dev/null +++ b/org.bluetooth.service.pulse_oximeter.xml @@ -0,0 +1,143 @@ + + + + + This Service specification proposes a pulse oximetry + server for use in consumer and professional healthcare + applications. + The Pulse Oximeter Service exposes pulse oximetry data + related to a non-invasive pulse oximetry sensor for consumer + and professional healthcare applications. + + + This service has no dependencies on other + GATT-based services. + + + + Mandatory if spot-check measurement storage is supported, + otherwise optional + Mandatory if the PLX + Continuous Measurement characteristic is supported, otherwise + optional + Mandatory if the PLX + Continuous Measurement characteristic is supported, otherwise + optional + + Mandatory + + Mandatory + + + true + true + true + + + + + C1 + + C1: Mandatory to support at least one of + these characteristics + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + Mandatory + Excluded + Excluded + + + + + Mandatory + + Mandatory + Mandatory + + + + + + C1 + + C1: Mandatory to support at least one of + these characteristics + Excluded + Excluded + Excluded + Excluded + Excluded + Mandatory + Excluded + Excluded + Excluded + + + + + Mandatory + + Mandatory + Mandatory + + + + + + Mandatory + + Mandatory + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + + + + + C2 + + C2: Mandatory if measurement storage is + supported for Spot-check measurements + Excluded + Mandatory + Excluded + Excluded + Excluded + Excluded + Mandatory + Excluded + Excluded + + + + + Mandatory + + Mandatory + Mandatory + + + + + + diff --git a/org.bluetooth.service.reference_time_update.xml b/org.bluetooth.service.reference_time_update.xml new file mode 100644 index 0000000..3f90a7d --- /dev/null +++ b/org.bluetooth.service.reference_time_update.xml @@ -0,0 +1,61 @@ + + + + + This service defines how a client can request an + update from a reference time source from a time server using + the Generic Attribute Profile (GATT) + This service enables a Bluetooth device that can + update the system time using reference time such as GPS to + expose the control point and the accuracy (drift) of the local + system time compared to the reference time source. + + + This service has no dependencies on other + GATT-based services. + + + + Mandatory + + + false + true + + + + + Mandatory + + Excluded + Excluded + Mandatory + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + + + + Mandatory + + Mandatory + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + + + + diff --git a/org.bluetooth.service.running_speed_and_cadence.xml b/org.bluetooth.service.running_speed_and_cadence.xml new file mode 100644 index 0000000..afe721b --- /dev/null +++ b/org.bluetooth.service.running_speed_and_cadence.xml @@ -0,0 +1,161 @@ + + + + + This service exposes speed, cadence and other data + from a Running Speed and Cadence Sensor intended for fitness + applications. + 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). + + + This service has no dependencies on other + GATT-based services. + + + + C1 + + Mandatory + C1 + + Mandatory + + Mandatory + + C1: Mandatory if the SC Control Point characteristic is + supported, otherwise excluded for this service. + + true + true + + + A + SC Control Point request cannot be serviced because a + previously triggered SC Control Point operation is still in + progress. + The Client Characteristic Configuration descriptor + is not configured according to the requirements of the + service. + + + + The RSC Measurement characteristic is used + to send speed and cadence measurements. + Mandatory + + Excluded + Excluded + Excluded + Excluded + Excluded + Mandatory + Excluded + Excluded + Excluded + + + + + Mandatory + + Mandatory + Mandatory + + + + + + The RSC Feature characteristic is used to + describe the supported features of the Server. Reserved for + Future Use (RFU) bits in the SC Feature characteristic value + are set to 0. + Mandatory + + Mandatory + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + + + + +

The Sensor Location characteristic of the device is used + to describe the physical location of the Server when + correctly fitted.

+

+ C1:Mandatory if the Multiple Sensor Location feature + is supported, otherwise optional.

+ + C1 + + Mandatory + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + + + + +

If the SC Control Point is supported, profiles utilizing + this service are required to ensure that the Client + configures the SC Control Point characteristic for + indications (i.e. via the Client Characteristic + Configuration descriptor) at the first connection.

+

Support for this characteristic is mandatory if the + Server supports Calibration Procedure, Total Distance or + Multiple Sensor Locations features, otherwise it is + excluded.

+

+ C2:Mandatory if at least one SC Control Point + procedure is supported, otherwise excluded.

+ + C2 + + Excluded + Mandatory + Excluded + Excluded + Excluded + Excluded + Mandatory + Excluded + Excluded + + + + + if_characteristic_supported + + Mandatory + Mandatory + + + + + + diff --git a/org.bluetooth.service.scan_parameters.xml b/org.bluetooth.service.scan_parameters.xml new file mode 100644 index 0000000..f279a6f --- /dev/null +++ b/org.bluetooth.service.scan_parameters.xml @@ -0,0 +1,95 @@ + + + + + This service enables a GATT Client to store the LE + scan parameters it is using on a GATT Server device so that the + GATT Server can utilize the information to adjust behavior to + optimize power consumption and/or reconnection + latency + The Scan Parameters Service enables a GATT Server + device to expose a characteristic for the GATT Client to write + its scan interval and scan window on the GATT Server + device. + + + This service has no dependencies on other + GATT-based services. + + + + Excluded + + Excluded + + Mandatory + + Excluded + C1 + + Excluded + + C1 + + C1: Mandatory if Scan Refresh characteristic is supported, + otherwise optional. + + false + true + + + + + The Scan Interval Window characteristic is + used to store the scan parameters of the Client. Included in + this characteristic are the Scan Interval and Scan Window of + the Client. + Mandatory + + Excluded + Excluded + Mandatory + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + + + + The Scan Refresh characteristic is used to + notify the Client that the Server requires the Scan Interval + Window characteristic to be written with the latest values + upon notification. + Optional + + Excluded + Excluded + Excluded + Excluded + Excluded + Mandatory + Excluded + Excluded + Excluded + + + + + if_characteristic_supported + + Mandatory + Mandatory + + + + + + diff --git a/org.bluetooth.service.transport_discovery.xml b/org.bluetooth.service.transport_discovery.xml new file mode 100644 index 0000000..1683dea --- /dev/null +++ b/org.bluetooth.service.transport_discovery.xml @@ -0,0 +1,74 @@ + + + + + This service enables a device using Bluetooth low + energy wireless technology to expose services that are + available on a transport other than Bluetooth low energy. When + used together with a higher level specification (e.g., a + specification which references and makes use of TDS), the + information provided by this service can be used to facilitate + discovery and utilization of BR/EDR or transports not defined + by the Bluetooth SIG such as those defined by the Wi-Fi + Alliance? or other organizations. + 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. + + + This service has no dependencies on other + GATT-based services. + + + + C.1 + C.1 + + C.1 + + C.1 + + C.1: Mandatory if the Server supports the TDS Control Point + characteristic; optional otherwise. + + true + true + true + + + + + The TDS Control Point characteristic is used + to request activation of a transport. + Optional + + Excluded + Mandatory + Excluded + Excluded + Excluded + Excluded + Mandatory + Excluded + Excluded + + + + + if_indicate_supported + + Mandatory + Mandatory + + + + + + diff --git a/org.bluetooth.service.tx_power.xml b/org.bluetooth.service.tx_power.xml new file mode 100644 index 0000000..30930fa --- /dev/null +++ b/org.bluetooth.service.tx_power.xml @@ -0,0 +1,80 @@ + + + + + This service exposes a device?s current transmit + power level when in a connection. + The Tx Power service is instantiated as a Primary + Service. There is only one instance of the Tx Power service on + a device. There is exactly one instance of the Tx Power Level + characteristic + + + This service has no dependencies on other + GATT-based services. + + + + false + true + + Replace table by: This service does not define any + application error codes that are used in Attribute + Protocol. + + + The Tx Power Level characteristic represents + the current transmit power level of a physical layer for + which the characteristic is associated. + Mandatory + + Mandatory + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + + + + + + diff --git a/org.bluetooth.service.user_data.xml b/org.bluetooth.service.user_data.xml new file mode 100644 index 0000000..f57aaa1 --- /dev/null +++ b/org.bluetooth.service.user_data.xml @@ -0,0 +1,693 @@ + + + + + This service exposes user-related data in the sports + and fitness environment. This allows remote access and update + of user data by a Client as well as the synchronization of user + data between a Server and a Client. + The User Data Service (UDS) exposes user-related data + in the sports and fitness environment. This allows remote + access and update of user data by a Client as well as the + synchronization of user data between a Server and a + Client. + + + This service is not dependent upon any other + services. + + + + Mandatory + + C.1 + + C.1 + C.2 + Mandatory + + C.1: Mandatory if the Server exposes at least one + characteristic with a size that may exceed the available space + needed for the GATT operations of the minimum default ATT_MTU, + otherwise optional (e.g. utf8-based characteristics). C.2: + Mandatory if the Server supports the update of one or more UDS + Characteristic values (e.g. through its User Interface or any + other out-of-band mechanism), otherwise, excluded from this + version of the service. + + true + true + true + + + + + + + + C.1:At least one UDS Characteristic shall be + exposed. + C1 + + Mandatory + Mandatory + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + + + Encryption is mandatory + + + + C.1:At least one UDS Characteristic shall be + exposed. + C1 + + Mandatory + Mandatory + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + + + Encryption is mandatory + + + + C.1:At least one UDS Characteristic shall be + exposed. + C1 + + Mandatory + Mandatory + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + + + Encryption is mandatory + + + + C.1:At least one UDS Characteristic shall be + exposed. + C1 + + Mandatory + Mandatory + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + + + Encryption is mandatory + + + + C.1:At least one UDS Characteristic shall be + exposed. + C1 + + Mandatory + Mandatory + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + + + Encryption is mandatory + + + + C.1:At least one UDS Characteristic shall be + exposed. + C1 + + Mandatory + Mandatory + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + + + Encryption is mandatory + + + + C.1:At least one UDS Characteristic shall be + exposed. + C1 + + Mandatory + Mandatory + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + + + Encryption is mandatory + + + + C.1:At least one UDS Characteristic shall be + exposed. + C1 + + Mandatory + Mandatory + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + + + Encryption is mandatory + + + + C.1:At least one UDS Characteristic shall be + exposed. + C1 + + Mandatory + Mandatory + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + + + Encryption is mandatory + + + + C.1:At least one UDS Characteristic shall be + exposed. + C1 + + Mandatory + Mandatory + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + + + Encryption is mandatory + + + + C.1:At least one UDS Characteristic shall be + exposed. + C1 + + Mandatory + Mandatory + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + + + Encryption is mandatory + + + + C.1:At least one UDS Characteristic shall be + exposed. + C1 + + Mandatory + Mandatory + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + + + Encryption is mandatory + + + + C.1:At least one UDS Characteristic shall be + exposed. + C1 + + Mandatory + Mandatory + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + + + Encryption is mandatory + + + + C.1:At least one UDS Characteristic shall be + exposed. + C1 + + Mandatory + Mandatory + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + + + Encryption is mandatory + + + + C.1:At least one UDS Characteristic shall be + exposed. + C1 + + Mandatory + Mandatory + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + + + Encryption is mandatory + + + + C.1:At least one UDS Characteristic shall be + exposed. + C1 + + Mandatory + Mandatory + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + + + Encryption is mandatory + + + + C.1:At least one UDS Characteristic shall be + exposed. + C1 + + Mandatory + Mandatory + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + + + Encryption is mandatory + + + + C.1:At least one UDS Characteristic shall be + exposed. + C1 + + Mandatory + Mandatory + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + + + Encryption is mandatory + + + + C.1:At least one UDS Characteristic shall be + exposed. + C1 + + Mandatory + Mandatory + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + + + Encryption is mandatory + + + + C.1:At least one UDS Characteristic shall be + exposed. + C1 + + Mandatory + Mandatory + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + + + Encryption is mandatory + + + + C.1:At least one UDS Characteristic shall be + exposed. + C1 + + Mandatory + Mandatory + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + + + Encryption is mandatory + + + + C.1:At least one UDS Characteristic shall be + exposed. + C1 + + Mandatory + Mandatory + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + + + Encryption is mandatory + + + + C.1:At least one UDS Characteristic shall be + exposed. + C1 + + Mandatory + Mandatory + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + + + Encryption is mandatory + + + + C.1:At least one UDS Characteristic shall be + exposed. + C1 + + Mandatory + Mandatory + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + + + Encryption is mandatory + + + + C.1:At least one UDS Characteristic shall be + exposed. + C1 + + Mandatory + Mandatory + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + + + Encryption is mandatory + + + + C.1:At least one UDS Characteristic shall be + exposed. + C1 + + Mandatory + Mandatory + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + + + Encryption is mandatory + + + + C.1:At least one UDS Characteristic shall be + exposed. + C1 + + Mandatory + Mandatory + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + + + Encryption is mandatory + + + + C.3: The Notify property is Mandatory if the + Server supports the update of one or more UDS Characteristic + values (e.g. through its User Interface or any other + out-of-band mechanism), otherwise, excluded from this version + of the service. + Mandatory + + Mandatory + Mandatory + Excluded + Excluded + Excluded + C3 + Excluded + Excluded + Excluded + + + Encryption is mandatory when written + + + + + if_characteristic_supported + + Mandatory + Mandatory + + + + + + Mandatory + + Mandatory + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + + + Encryption is mandatory + + + + Mandatory + + Excluded + Mandatory + Excluded + Excluded + Excluded + Excluded + Mandatory + Excluded + Excluded + + + Encryption is mandatory + + + + + if_characteristic_supported + + Mandatory + Mandatory + + + + + + C.1:At least one UDS Characteristic shall be + exposed. + C1 + + Mandatory + Mandatory + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + + + Encryption is mandatory + + + + diff --git a/org.bluetooth.service.weight_scale.xml b/org.bluetooth.service.weight_scale.xml new file mode 100644 index 0000000..6f85b03 --- /dev/null +++ b/org.bluetooth.service.weight_scale.xml @@ -0,0 +1,75 @@ + + + + + This service exposes weight and related data from a + weight scale intended for consumer healthcare and + sports/fitness applications. + The Weight Scale (WS) Service exposes weight and + related data from a weight scale (Server) intended for consumer + healthcare as well as sports/fitness applications. + + + This service is not dependent upon any other + services. + + + Mandatory + + Mandatory + + Mandatory + + + true + true + true + + + + + Mandatory + + Mandatory + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + + + + Mandatory + + Excluded + Excluded + Excluded + Excluded + Excluded + Excluded + Mandatory + Excluded + Excluded + + + + + if_indicate_supported + + Mandatory + Mandatory + + + + + +