TI BLE-Stack for Bluetooth 4.2 API Documentation
3.01.00.07
|
Parameter Structure used for SNP_addCharValueDecl / SNP_ADD_CHAR_VAL_DECL_REQ. More...
Data Fields | |
uint16_t | charValMaxLen |
uint8_t | charValPerms |
1 Byte permissions of the value attribute, see GATT Attribute Access Permissions Bit Fields | |
uint16_t | charValProps |
2 Byte property of the value attribute, see GATT Characteristic Properties Bit Fields | |
uint8_t | mgmtOption |
1 Byte Reserved for future use | |
uint8_t | UUID [16] |
Parameter Structure used for SNP_addCharValueDecl / SNP_ADD_CHAR_VAL_DECL_REQ.
Characteristic Value is managed by the AP.
snpAddCharValueDeclReq_t::charValPerms are defined by a profile or are implementation specific. TI BLE-Stack has define its own permissions: GATT Attribute Access Permissions Bit Fields.
Basic filtering is done using those values For example, a read request on a characteristic value which does not permit reading will be rejected by the stack without AP interaction.
snpAddCharValueDeclReq_t::charValProps are defined by the BLE specification, GATT Characteristic Properties Bit Fields. TI BLE-Stack expect the properties to be align logically with the permission. For example, a read permission on an attribute should also have a read property.
snpAddCharValueDeclReq_t::UUID refer to dealing with UUID
This is a packed structure. see Dealing with Parameters and Packed Structures for more information.
uint16_t charValMaxLen |
1 Byte Reserved for future use Range: 0-512
Since for now the characteristic value is managed only by the AP, this length field is not useful. Reserve for future use.
uint8_t UUID[16] |
16 Bytes UUID of the characteristic. see dealing with UUID
UUID can be 2 bytes only. at reception of this request, the length of the UUID can be deduce from the NPI frame length. at transmission of this request, the length of UUID will need to be indicated outside of this structure.