TELINK SEMICONDUCTOR TLSR8232 - Read by Group Type Request, Read by Group Type Response

Telink TLSR8232 BLE SDK Developer Handbook
AN-19112700-E1 100 Ver.1.0.0
2) Responses：Data response sent by Server after it receives request from Client.
3) Commands：Command sent from Client to Server.
4) Notifications: Data sent from Server to Client.
5) Indications: Data sent from Server to Client.
6) Confirmations: Confirmation sent from Client after it receives data from Server.
The subsections below will introduce all ATT PDUs in ATT layer. Please refer to structure
of Attribute and Attribute Table to help understanding.
3.4.3.1 Read by Group Type Request, Read by Group Type Response
Please refer to Core_v5.0 (Vol 3/Part F/3.4.4.9 and 3.4.4.10) for details of Read by
Group Type Request and Read by Group Type Response.
The “Read by Group Type Request” command sent by Master specifies starting and
ending attHandle, as well as attGroupType. After the request is received, Slave will check
through current Attribute Table according to the specified starting and ending attHandle,
and find the Attribute Group that matches the specified attGroupType. Then Slave will
respond to Master with Attribute Group information via the “Read by Group Type
Response” command.
Figure 3-35 Read by Group Type Request/Read by Group Type Response
As shown above, Master requests from Slave for Attribute Group information of the
“primaryServiceUUID” with UUID being 0x2800.
#define GATT_UUID_PRIMARY_SERVICE 0x2800
const u16 my_primaryServiceUUID = GATT_UUID_PRIMARY_SERVICE;