Central Disconnecting Inactive Peripheral

I have confirmed that even when the peripheral device is notifying once every ten seconds the BLE central will issue a disconnection event after aproximatly 90 seconds of connection. Once the disconnection event is recieved connection can be re-established by beginning the discovery process again.

the peripheral device is using an nRF5182 BLE core.

First thing to check would be the connection parameters used by the peripheral.

These are the constraints:

Interval Max * (***** Latency + 1) ≤ 2 seconds

Interval Min ≥ 20 ms

Interval Min + 20 ms ≤ Interval Max

***** Latency ≤ 4

SupervisionTimeout ≤ 6 seconds

Interval Max * (***** Latency + 1) * 3 < SupervisionTimeout

Values outside these constraints will cause connection stability issues like you are seeing.

Also, my general recommendation is to keep the Max Interval closer to 1 second rather than the 2 second maximum for better results.

The peripheral needs to respond to link level data within the effective connection interval to maintain a connection. The effective interval is the current connection interval * the ***** Lantency value.

I don't know how you have implemeted your peripheral, but if the peripheral is sleeping for 10 seconds and then sending a notification, and going back to sleep again (and not responding to link level requests) , that would cause timeouts.