Problem Description:

The following is missing from the GATT builder implementation:

1. INDICATION property for characteristics

2. Option to define service as “Primary” or “Secondary”

3. Let the user to define characteristics authentication/authorization levels. (characteristics on the peripheral DB that the peer device can access only by pairing/bonding) according to the tests we are doing on the GATT DB right now (before this tool) each characteristic has Level of authentication to access it.