Indication of Read request at application level

RE: Indication of Read request at application level

beemavishnu — Thu, 13 Jun 2019 16:23:17 GMT

Thank you for your inputs

RE: Indication of Read request at application level

Sigurd — Thu, 13 Jun 2019 16:21:22 GMT

1) No you don't need to enable security in order to use authorization.

2) If you are using the function characteristic_add() to add the characteristic, then you need to set this to 1, since this is then used to set the value of attr_md.rd_auth. But if this is for the characteristic user descriptor, then it's optional to use.

RE: Indication of Read request at application level

beemavishnu — Mon, 10 Jun 2019 07:58:00 GMT

Andy thank you for your inputs and different approach.

Sigurd thank you for your inputs.

Just I gave battery as example. But in our case, on read request I need to read Sensor at that instance, timestamp the value and send to Client. So time stamp will be at the instance when read request is received by server.

Already Client is developed and we don’t want to change (Because of this I said not to implement write command).

With respect to “GATTS Read Request without Authorization”, periodically server will read sensor data, timestamp the data and update ‘Characteristic value’ by calling sd_ble_gatts_value_set(). So when there is a read request from Client, shared structure at Server is read and transmitted. So the data read is last but not latest.

To get better understanding, my further queries are:

1) As of now I did not enable any security (read_access = SEC_OPEN). With “GATTS Read Request with Authorization”, do I need to enable any security.

2) To enable ‘rd_auth’ I need to set ‘is_defered_read’ to 1. But as per comments “Indicate if deferred read operations are supported”, please give more inputs on this variable.

Thanks & Regards

Vishnu Beema

RE: Indication of Read request at application level

Sigurd — Tue, 04 Jun 2019 11:04:38 GMT

Here is the MSC for Read Request with Authorization. When you get the event BLE_GATTS_EVT_TW_AUTHORIZE_REQUEST, read the voltage, and use the new value when you call sd_ble_gatts_rw_authorize_reply(). You need to set the rd_auth bit for the battery level characteristic to 1 to enable read request with authorization.

RE: Indication of Read request at application level

Andy — Mon, 03 Jun 2019 14:08:47 GMT

You can also implement authorized reads, but I don't know what kind of operations you need to do in order to get the battery level (i.e. ADC, I2C, etc), and you would probably have to implement some weird handlers to achieve that.

RE: Indication of Read request at application level

Andy — Mon, 03 Jun 2019 14:07:08 GMT

It's not a limitation, it's a product of your requirements.

The way I have it set up in my project is that every time the battery gauge IC detects a change in battery level, the IC pulls a pin down and that triggers a battery level notification. I don't know what kind of setup you have, but this is quite a good approach IMO.

RE: Indication of Read request at application level

beemavishnu — Mon, 03 Jun 2019 13:49:14 GMT

Is there any better approach or is this limitation in BLE specifications. I don't want to implement write command at client. I enabled "READ" option at server and if that read request is known by the application, then server can send the data by reading the latest battery level.

RE: Indication of Read request at application level

Andy — Mon, 03 Jun 2019 12:14:24 GMT

The most straight-forward way I think would be to have the client write to a specific "command" characteristic, telling the server that it wants the current battery level. The server can then read the value and send it with a notification when it's ready.