Glucose profile

Tip / Sign in to post questions, reply, level up, and achieve exciting badges. Know more

cross mob
Anonymous
Not applicable

Is there any documents on the glucose profile software flow provided as part of the SDK?

Seems that an explanation of some sort could be useful.

A search on the forum doesnt yield much info related to this


0 Likes
1 Solution
Anonymous
Not applicable

Hello vsesto,

Broadcom followed the Glucose Profile listed in the Bluetooth Specification with respect to the BLE Profile found at: English Specification | Adopted Documents

We don't have an explanation as such, but you might find the GLP_SPEC_V10.pdf Section 9 useful for the flow of the Notifications and Indications along with the Characteristics used.

An excerpt from the Access Point Use Case provided in the Profile below:

Below is an informative example showing the use of the RACP in the context of the Glucose Profile:

1. At 04 October 2011 12:40:00 pm (user-facing time internal to the Server i.e., Base Time + Time Offset), the Client requests records for the first time and requests the number of all records stored in the device.
      a. The Client writes Op Code 0x04 to request number of records with an Operator of 0x01 meaning “all records”           and no Operand.
      b. The Server indicates back Op Code 0x05, an Operator of 0x00 (meaning “Null”) and Operand containing the           number of all records (0x00F7 in this example)
2. Immediately after that, the Client requests a report of stored records.
      a. The Client writes Op Code 0x01 to request all records with an Operator of 0x01 meaning “all records” and no           Operand.
      b. The Server notifies all records (Series of Glucose Measurement characteristics followed sometimes by           Glucose Measurement Context characteristics) where the total number of Glucose Measurement           characteristics totals 0x00F7.
      c. The Server indicates Op Code 0x06 with an Operator of 0x00 (meaning “Null”) and Operand of 0x01, 0x01           meaning “successful response to Op Code 0x01”.
      d. The Client stores the Sequence Number of the last received record for future use (0x00F7 since this was the           first use and with the assumption in this example that the sequence number of the first record is 0x0001).
      e. Since this is a critical application, the Client performs some post-processing checks to make sure no major           inconsistencies to the Base Time or Time Offset occurred. The Client also checks to see if any numbers in the           sequence are missing.
3. Several days later, the Client requests a report of records since the last update.
      a. The Client writes Op Code 0x01 to request records with an Operator of 0x03 meaning “greater than or equal           to” and an Operand set to Filter Type 0x01, 0x00F8) that is one number in the sequence more than the           Sequence Number from the last record it received.
      b. The Server notifies all records that have accrued since the last request.
      c. The Server indicates Op Code 0x06 with an Operator of 0x00 (meaning “Null”) and Operand of 0x05, 0x01           meaning “successful response to Op Code 0x05”.

Hopefully this can get you started

JT

View solution in original post

2 Replies
Anonymous
Not applicable

Hello vsesto,

Broadcom followed the Glucose Profile listed in the Bluetooth Specification with respect to the BLE Profile found at: English Specification | Adopted Documents

We don't have an explanation as such, but you might find the GLP_SPEC_V10.pdf Section 9 useful for the flow of the Notifications and Indications along with the Characteristics used.

An excerpt from the Access Point Use Case provided in the Profile below:

Below is an informative example showing the use of the RACP in the context of the Glucose Profile:

1. At 04 October 2011 12:40:00 pm (user-facing time internal to the Server i.e., Base Time + Time Offset), the Client requests records for the first time and requests the number of all records stored in the device.
      a. The Client writes Op Code 0x04 to request number of records with an Operator of 0x01 meaning “all records”           and no Operand.
      b. The Server indicates back Op Code 0x05, an Operator of 0x00 (meaning “Null”) and Operand containing the           number of all records (0x00F7 in this example)
2. Immediately after that, the Client requests a report of stored records.
      a. The Client writes Op Code 0x01 to request all records with an Operator of 0x01 meaning “all records” and no           Operand.
      b. The Server notifies all records (Series of Glucose Measurement characteristics followed sometimes by           Glucose Measurement Context characteristics) where the total number of Glucose Measurement           characteristics totals 0x00F7.
      c. The Server indicates Op Code 0x06 with an Operator of 0x00 (meaning “Null”) and Operand of 0x01, 0x01           meaning “successful response to Op Code 0x01”.
      d. The Client stores the Sequence Number of the last received record for future use (0x00F7 since this was the           first use and with the assumption in this example that the sequence number of the first record is 0x0001).
      e. Since this is a critical application, the Client performs some post-processing checks to make sure no major           inconsistencies to the Base Time or Time Offset occurred. The Client also checks to see if any numbers in the           sequence are missing.
3. Several days later, the Client requests a report of records since the last update.
      a. The Client writes Op Code 0x01 to request records with an Operator of 0x03 meaning “greater than or equal           to” and an Operand set to Filter Type 0x01, 0x00F8) that is one number in the sequence more than the           Sequence Number from the last record it received.
      b. The Server notifies all records that have accrued since the last request.
      c. The Server indicates Op Code 0x06 with an Operator of 0x00 (meaning “Null”) and Operand of 0x05, 0x01           meaning “successful response to Op Code 0x05”.

Hopefully this can get you started

JT

Anonymous
Not applicable

From the Bluetooth SIG:

Bluetooth_SIG_Glucose.PNG