This parameter determines how long time passed from either connection or CCCD write (depending on the value used for start_on_notify_cccd_handle) it will take before a Connection Parameter Update Request is sent, if the initial connection parameters of the Central are not within the Peripheral's requirements.
If the start_on_notify_cccd_handle is set to BLE_GATT_HANDLE_INVALID, the time will be measured from the CONNECTED event. If the start_on_notify_cccd_handle is set to the value of a CCCD, time will be measured from that specific CCCD is written by the GATT Client.
it seems I have had a better understanding about it now.
And I get a futher question:
Assuming that the start_on_notify_cccd_handle is set to BLE_GATT_HANDLE_INVALID, is that means the device can only connect again after FIRST_CONN_PARAMS_UPDATE_DELAY?(even if i have disconnected my device during the peroid)?
it seems I have had a better understanding about it now.
And I get a futher question:
Assuming that the start_on_notify_cccd_handle is set to BLE_GATT_HANDLE_INVALID, is that means the device can only connect again after FIRST_CONN_PARAMS_UPDATE_DELAY?(even if i have disconnected my device during the peroid)?
