fast_pair: Add bond management documentation

Jira: NCSDK-29580

Signed-off-by: Aleksander Strzebonski <[email protected]>

Author: alstrzebonski

doc/nrf/external_comp/bt_fast_pair.rst

@@ -632,6 +632,25 @@ In the Fast Pair not discoverable advertising mode, the Provider informs the lis
 You can also use the :c:func:`bt_fast_pair_has_account_key` function to check whether your Provider has any Account Keys.
 This API is especially useful after a system reboot when some Account Keys may already be stored in non-volatile memory.
 
+.. _ug_bt_fast_pair_gatt_service_bond_management:
+
+Fast Pair bond management functionality
+=======================================
+
+To enable the Fast Pair bond management functionality, use the :kconfig:option:`CONFIG_BT_FAST_PAIR_BOND_MANAGER` Kconfig option.
+When this functionality is enabled, the Fast Pair subsystem tracks the Bluetooth bonds created through the Fast Pair Procedure and unpairs them if the procedure is incomplete or the Account Key associated with the bonds is removed.
+It also unpairs the Fast Pair Bluetooth bonds on Fast Pair factory reset, because the factory reset removes all Account Keys stored on device.
+Enabling the functionality imposes additional limitations related to enabling Fast Pair in runtime (:c:func:`bt_fast_pair_enable`).
+See the :kconfig:option:`CONFIG_BT_FAST_PAIR_BOND_MANAGER` Kconfig option help for more datails about using the functionality.
+
+The Fast Pair bond management functionality is disabled by default.
+Make sure that it is enabled for the following use cases of the Google Fast Pair application as it is highly recommended:
+
+* Input device
+* Mouse
+
+See :ref:`ug_bt_fast_pair_use_case` for more details about the use cases of the Google Fast Pair application.
+
 FMDN extension
 ==============
 

doc/nrf/libraries/bluetooth_services/services/fast_pair.rst

@@ -47,6 +47,8 @@ With the :kconfig:option:`CONFIG_BT_FAST_PAIR` Kconfig option enabled, the follo
 * :kconfig:option:`CONFIG_BT_FAST_PAIR_STORAGE_ACCOUNT_KEY_MAX` - The option configures maximum number of stored Account Keys.
 * :kconfig:option:`CONFIG_BT_FAST_PAIR_CRYPTO_TINYCRYPT`, :kconfig:option:`CONFIG_BT_FAST_PAIR_CRYPTO_OBERON`, and :kconfig:option:`CONFIG_BT_FAST_PAIR_CRYPTO_PSA` - These options are used to select the cryptographic backend for Fast Pair.
   The Oberon backend is used by default.
+* :kconfig:option:`CONFIG_BT_FAST_PAIR_BOND_MANAGER` - The option enables the Fast Pair bond management functionality.
+  See :ref:`ug_bt_fast_pair_gatt_service_bond_management` for more details.
 * :kconfig:option:`CONFIG_BT_FAST_PAIR_PN` - The option enables the `Fast Pair Personalized Name extension`_.
 
   * :kconfig:option:`CONFIG_BT_FAST_PAIR_STORAGE_PN_LEN_MAX` - The option specifies the maximum length of a stored Fast Pair Personalized Name.

doc/nrf/releases_and_maturity/releases/release-notes-changelog.rst

@@ -748,6 +748,10 @@ Bluetooth libraries and services
     * The :kconfig:option:`CONFIG_BT_FAST_PAIR_SUBSEQUENT_PAIRING` Kconfig option allowing the user to control the support for the Fast Pair subsequent pairing feature.
     * The :kconfig:option:`CONFIG_BT_FAST_PAIR_USE_CASE` Kconfig choice option allowing the user to select their target Fast Pair use case.
       The :kconfig:option:`CONFIG_BT_FAST_PAIR_USE_CASE_UNKNOWN`, :kconfig:option:`CONFIG_BT_FAST_PAIR_USE_CASE_INPUT_DEVICE`, :kconfig:option:`CONFIG_BT_FAST_PAIR_USE_CASE_LOCATOR_TAG` and :kconfig:option:`CONFIG_BT_FAST_PAIR_USE_CASE_MOUSE` Kconfig options represent the supported use cases that can be selected as part of this Kconfig choice option.
+    * The :kconfig:option:`CONFIG_BT_FAST_PAIR_BOND_MANAGER` Kconfig option that enables the Fast Pair bond management functionality.
+      If this option is enabled, the Fast Pair subsystem tracks the Bluetooth bonds created through the Fast Pair Procedure and unpairs them if the procedure is incomplete or the Account Key associated with the bonds is removed.
+      It also unpairs the Fast Pair Bluetooth bonds on Fast Pair factory reset.
+      The option is enabled by default for Fast Pair use cases that are selected using :kconfig:option:`CONFIG_BT_FAST_PAIR_USE_CASE_INPUT_DEVICE` and :kconfig:option:`CONFIG_BT_FAST_PAIR_USE_CASE_MOUSE` Kconfig options.
 
   * Removed:
 

subsys/bluetooth/services/fast_pair/Kconfig.fast_pair

@@ -177,16 +177,25 @@ config BT_FAST_PAIR_BOND_MANAGER
 	select EXPERIMENTAL
 	select BT_FAST_PAIR_STORAGE_AK_BOND
 	help
-	  If this option is enabled, the Fast Pair subsystem tracks the Bluetooth bonds created
-	  through the Fast Pair Procedure and unpairs them if the Fast Pair Procedure is incomplete
-	  or the Account Key associated with the bonds is removed. It also unpairs the Fast Pair
-	  Bluetooth bonds on Fast Pair factory reset. Keep in mind that when the Fast Pair subsystem
-	  is disabled, the Bluetooth bonds are not tracked. Do not perform operations on the Fast
-	  Pair Bluetooth bonds apart from the Fast Pair factory reset when the Fast Pair subsystem
-	  is disabled. When this option is enabled, non-volatile storage is used to store the bond
-	  information. You can enable this option during DFU, but you cannot disable it during DFU
-	  if you used it earlier unless you erase whole Fast Pair non-volatile storage. Otherwise,
-	  the Fast Pair enable operation will fail.
+	  When this functionality is enabled, the Fast Pair subsystem tracks the Bluetooth bonds
+	  created through the Fast Pair Procedure and unpairs them if the procedure is incomplete or
+	  the Account Key associated with the bonds is removed. It also unpairs the Fast Pair
+	  Bluetooth bonds on Fast Pair factory reset, because the factory reset removes all Account
+	  Keys stored on device.
+
+	  When the Fast Pair subsystem is disabled, the Bluetooth bonds are not tracked. Do not
+	  perform operations on Fast Pair Bluetooth bonds, except for the Fast Pair factory reset
+	  when the Fast Pair subsystem is disabled. Additionally, do not perform Bluetooth bonding
+	  when the Fast Pair subsystem is disabled and bond management functionality is enabled, as
+	  this could cause the subsystem to incorrectly identify new bonds as Fast Pair bonds. To
+	  conclude, the easiest and safest option is to keep the Fast Pair enabled while using
+	  Bluetooth to ensure proper behavior.
+
+	  With this functionality, the non-volatile storage is used to store the bond information.
+	  You can enable the functionality during DFU, but if you used it earlier, you cannot
+	  disable it during DFU unless you erase the entire Fast Pair non-volatile storage before
+	  the DFU. You can erase it by performing the Fast Pair factory reset. Otherwise, the Fast
+	  Pair enable operation will fail.
 
 module = BT_FAST_PAIR
 module-str = Fast Pair Service