The fields in the above table are in the order of LSO to + MSO. Where LSO = Least Significant Octet and MSO = Most + Significant Octet
+The fields in the above table are in the order of LSO to + MSO. Where LSO = Least Significant Octet and MSO = Most + Significant Octet
+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.
+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.
+? Value 0, meaning ?No Alert?
+? Value 1, meaning ?Mild Alert?
+? Value 2, meaning ?High Alert?
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.
Bit 0, meaning ?Ringer State?
+Bit 1, meaning ?Vibrator State?
+Bit 2, meaning "Display Alert Status"
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.
+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.
+The fields in the above table are in the order of LSO to + MSO. Where LSO = Least Significant Octet and MSO = Most + Significant Octet.
+The fields in the above table are in the order of LSO to + MSO. Where LSO = Least Significant Octet and MSO = Most + Significant Octet
+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.
+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
+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.
+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
+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
+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
+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
+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.
+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.
+The fields in the above table are in the order of LSO to + MSO. Where LSO = Least Significant Octet and MSO = Most + Significant Octet.
+The fields in the above table are in the order of LSO to + MSO. Where LSO = Least Significant Octet and MSO = Most + Significant Octet.
+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.
+The length of the utf8s-based UDS Characteristic is variable + and may exceed the default ATT_MTU defined in the Core + Specification.
+The length of the utf8s-based UDS Characteristics is + variable and may exceed the default ATT_MTU defined in the Core + 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.
+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.
+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.
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.
The fields in the above table are in the order of LSO to + MSO. Where LSO = Least Significant Octet and MSO = Most + Significant Octet.
+? 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
The length of the utf8s-based UDS Characteristic is variable + and may exceed the default ATT_MTU defined in the Core + Specification.
+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
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
+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 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
+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.
+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 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 >>
+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 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.
+Only a single instance of this characteristic exists as part + of a HID Service.
Value 1, meaning ?Silent Mode"
+Value 2, meaning ?Mute Once?
+Value 3, meaning ?Cancel Silent Mode?
Value 0, meaning ?Ringer Silent"
+Value 1, meaning ?Ringer Normal?
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).
+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).
+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.
+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.
+The fields in the above table are in the order of LSO to + MSO. Where LSO = Least Significant Octet and MSO = Most + Significant Octet.
+If the value is 255, it means Unread count is greater than + 254.
The fields in the above table are in the order of LSO to + MSO. Where LSO = Least Significant Octet and MSO = Most + Significant Octet.
+? 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.
- 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.
+ 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
++ 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). +
++ 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). +
++ 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
++ 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). +
++ 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). +
++ 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
+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.
+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.
+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)
+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.
+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.
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. +
+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.
+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.
+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.
+? 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.? Ringer State
+? Vibrator State
+? Display Alert State
The Alert Status characteristic + returns the current value of Phone Alert Status when + read.? 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.
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.
+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.
+