Is sending advertisements required even when notifications are registered?

[sushant_shidore]

I've a scenario where BLE central has registered for notifications on some characteristic of a BLE peripheral. The frequency of change in data of this characteristic is very low, may be once in 10 minutes meaning that this BLE peripheral will send notifications quite rarely. Now, say if the central device got reset and now wants data from the peripheral immediately.

What should be done here since the peripheral could be in sleep mode and would wake up and advertise for the notification only when its characteristic data changes?

Do I need to make the peripheral send periodic advertisements even when it has seen no change in its data, just to give an opportunity to the central device for making a connection and reading the data?

Won't these 'dummy' advertisements affect the peripheral's battery life?

What is the standard practice followed in such kind of scenarios?

[RK]

This seems remarkably similar to your last question

devzone.nordicsemi.com/.../

"the peripheral could be in sleep mode and would wake up and advertise for the notification only when its characteristic data changes" shows you're somewhat confused about advertising mode vs connection mode. Advertisements are done before connection, after connection there are no advertisements, just read/write/notify/indicate and the devices exchange constant connection packets.

[RK]

You don't seem to have read what I wrote. If you are in connection there are no advertisements. The connection stays up because it regularly exchanges packets. If you are not in connection then you advertise at whatever frequency you like so things can connect to you. Those are they only two states.

No advertisements --> no connection connection --> no more advertisements.