You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: applications/nrf_desktop/doc/ble_discovery.rst
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -59,7 +59,7 @@ The |ble_discovery| implementation is tasked with peripheral discovery and verif
59
59
Peripheral discovery
60
60
====================
61
61
62
-
The module starts the peripheral device discovery when it receives :c:struct:`ble_peer_event` with :c:member:`ble_peer_event.state` set to :c:enumerator:`PEER_STATE_SECURED`.
62
+
The module starts the peripheral device discovery when it receives :c:struct:`ble_peer_event` with :c:member:`ble_peer_event.state` set to :c:enumerator:`PEER_STATE_CONNECTED`.
63
63
64
64
The peripheral discovery consists of the following steps:
Copy file name to clipboardExpand all lines: applications/nrf_desktop/doc/ble_scan.rst
-1Lines changed: 0 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -129,7 +129,6 @@ After the scan filter match, the following happens:
129
129
130
130
a. The scanning is stopped and the |NCS|'s :ref:`nrf_bt_scan_readme` automatically establishes the Bluetooth connection with the peripheral.
131
131
The initial Bluetooth connection interval is set by default to 7.5 ms, that is to the shortest connection interval allowed by the Bluetooth specification.
132
-
#. The connection is secured.
133
132
#. The peer discovery is started.
134
133
#. After the :ref:`nrf_desktop_ble_discovery` completes the peer discovery, the :ref:`nrf_desktop_ble_conn_params` receives the ``ble_discovery_complete_event`` and updates the Bluetooth connection interval.
Copy file name to clipboardExpand all lines: doc/nrf/libraries/caf/ble_state.rst
+3-4Lines changed: 3 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -27,7 +27,6 @@ To use the module, you must enable the following Kconfig options:
27
27
28
28
* :kconfig:option:`CONFIG_BT`
29
29
* :kconfig:option:`CONFIG_BT_SMP` - This option enables Security Manager Protocol support.
30
-
The |ble_state| on Bluetooth Peripheral requires at least the connection security level 2 (encryption).
31
30
* :kconfig:option:`CONFIG_CAF_BLE_STATE` - This option enables the |ble_state| and selects the :kconfig:option:`CONFIG_CAF_BLE_COMMON_EVENTS` Kconfig option, which enables Bluetooth LE common events in CAF.
32
31
33
32
The following Kconfig options are also available for this module:
@@ -36,6 +35,9 @@ The following Kconfig options are also available for this module:
36
35
This option is enabled by default.
37
36
* :kconfig:option:`CONFIG_CAF_BLE_USE_LLPM` - This option enables the Low Latency Packet Mode (LLPM).
38
37
This option is enabled by default and depends on :kconfig:option:`CONFIG_BT_CTLR_SDC_LLPM` and :kconfig:option:`CONFIG_BT_LL_SOFTDEVICE`.
38
+
* :kconfig:option:`CONFIG_CAF_BLE_STATE_SECURITY_REQ` - This option enables setting the security level 2 for a Bluetooth LE connection automatically, right after the connection is established.
39
+
The security level 2 or higher enables connection encryption.
40
+
The device disconnects if establishing the connection security level 2 fails.
39
41
40
42
Implementation details
41
43
**********************
@@ -66,9 +68,6 @@ The connection state can be set to one of the following values:
66
68
Other application modules can call :c:func:`bt_conn_disconnect` to disconnect the remote peer.
67
69
The application module can submit a :c:struct:`ble_peer_event` with :c:member:`ble_peer_event.state` set to :c:enum:`PEER_STATE_DISCONNECTING` to let other application modules prepare for the disconnection.
68
70
69
-
On Bluetooth Peripheral, the |ble_state| requires the connection security level 2.
70
-
If the connection security level 2 is not established, the Peripheral disconnects.
* nRF Desktop peripherals no longer automatically send security request right after Bluetooth LE connection is established.
105
+
The feature can be turned on using :kconfig:option:`CONFIG_CAF_BLE_STATE_SECURITY_REQ`.
106
+
* nRF Desktop dongles start peripheral discovery right after Bluetooth LE connection is established.
107
+
The dongles no longer wait until the connection is secured.
108
+
104
109
|no_changes_yet_note|
105
110
106
111
Thingy:53 Zigbee weather station
@@ -220,6 +225,10 @@ Other libraries
220
225
Common Application Framework (CAF)
221
226
----------------------------------
222
227
228
+
* :ref:`caf_ble_state` running on Bluetooth Peripheral no longer automatically sends security request right after Bluetooth LE connection is established.
229
+
The :kconfig:option:`CONFIG_CAF_BLE_STATE_SECURITY_REQ` can be used to enable this feature.
230
+
The option can be used for both Bluetooth Peripheral and Bluetooth Central.
0 commit comments