Google Fast Pair Service (GFPS)

The Google Fast Pair Service (Fast Pair for short) implements a Bluetooth® Low Energy (LE) GATT Service required for Google Fast Pair integration with the nRF Connect SDK.

Service UUID

The Fast Pair service uses UUID of 0xFE2C.

Characteristics

The Fast Pair GATT characteristics are described in detail in the Fast Pair GATT Characteristics documentation. The implementation in the nRF Connect SDK follows these requirements.

The Fast Pair service also contains additional GATT characteristics under the following conditions:

• The Additional Data GATT characteristic is enabled when an extension requires it. Currently, only the Personalized Name extension (CONFIG_BT_FAST_PAIR_PN) requires this characteristic.

• The Beacon Actions GATT characteristic when the Find My Device Network (FMDN) extension is enabled (CONFIG_BT_FAST_PAIR_FMDN). The characteristic is described in the Fast Pair Find My Device Network extension documentation.

Configuration

The Fast Pair Service is enabled with CONFIG_BT_FAST_PAIR Kconfig option set in the main application image.

Note

When building with sysbuild, value of the CONFIG_BT_FAST_PAIR Kconfig option is overwritten by SB_CONFIG_BT_FAST_PAIR. For more details about enabling Fast Pair for your application, see the Enabling Fast Pair in Kconfig section in the Fast Pair integration guide.

With the CONFIG_BT_FAST_PAIR Kconfig option enabled, the following Kconfig options are available for this service:

• CONFIG_BT_FAST_PAIR_GATT_SERVICE_MODEL_ID - The option adds the Model ID characteristic to the Fast Pair GATT service.

• CONFIG_BT_FAST_PAIR_REQ_PAIRING - The option enforces the requirement for Bluetooth pairing and bonding during the Fast Pair Procedure. See the Procedure without Bluetooth pairing for more details.

• CONFIG_BT_FAST_PAIR_SUBSEQUENT_PAIRING - The option adds support for the Fast Pair subsequent pairing feature.

• CONFIG_BT_FAST_PAIR_STORAGE_USER_RESET_ACTION - The option enables user reset action that is executed together with the Fast Pair factory reset operation. See the Custom user reset action for more details.

• CONFIG_BT_FAST_PAIR_STORAGE_ACCOUNT_KEY_MAX - The option configures maximum number of stored Account Keys.

• CONFIG_BT_FAST_PAIR_CRYPTO_TINYCRYPT, CONFIG_BT_FAST_PAIR_CRYPTO_OBERON, and 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.

• CONFIG_BT_FAST_PAIR_BOND_MANAGER - The option enables the Fast Pair bond management functionality. See Fast Pair bond management functionality for more details.

• CONFIG_BT_FAST_PAIR_PN - The option enables the Fast Pair Personalized Name extension.

  • CONFIG_BT_FAST_PAIR_STORAGE_PN_LEN_MAX - The option specifies the maximum length of a stored Fast Pair Personalized Name.

• CONFIG_BT_FAST_PAIR_BN - The option enables the Fast Pair Battery Notification extension.

• CONFIG_BT_FAST_PAIR_FMDN - The option enables the Fast Pair Find My Device Network extension.

  • CONFIG_BT_FAST_PAIR_FMDN_DULT - The option enables the Detecting Unwanted Location Trackers (DULT) support in the FMDN extension (see DULT integration):

    • CONFIG_BT_FAST_PAIR_FMDN_DULT_MANUFACTURER_NAME - The option configures the manufacturer name parameter.

    • CONFIG_BT_FAST_PAIR_FMDN_DULT_MODEL_NAME - The option configures the model name parameter.

    • CONFIG_BT_FAST_PAIR_FMDN_DULT_ACCESSORY_CATEGORY - The option configures the accessory category parameter.

    • CONFIG_BT_FAST_PAIR_FMDN_DULT_FIRMWARE_VERSION_MAJOR, CONFIG_BT_FAST_PAIR_FMDN_DULT_FIRMWARE_VERSION_MINOR and CONFIG_BT_FAST_PAIR_FMDN_DULT_FIRMWARE_VERSION_REVISION - These options configure the firmware version parameter.

    • CONFIG_BT_FAST_PAIR_FMDN_DULT_MOTION_DETECTOR - The option enables the DULT motion detector functionality support in the FMDN extension (see Interacting with the motion detector from DULT).

  • There are following advertising configuration options for the FMDN extension (see FMDN extension):

    • CONFIG_BT_FAST_PAIR_FMDN_TX_POWER - The option sets the TX power (dBm) in the Bluetooth LE controller for FMDN advertising and connections.

    • CONFIG_BT_FAST_PAIR_FMDN_TX_POWER_CORRECTION_VAL - The value of this option is added to the TX power readout from the Bluetooth LE controller to calculate the calibrated TX power reported in the Read Beacon Parameters response.

    • CONFIG_BT_FAST_PAIR_FMDN_MAX_CONN - The option configures a maximum number of FMDN connections. This option is bounded by the CONFIG_BT_MAX_CONN and cannot exceed its value.

    • CONFIG_BT_FAST_PAIR_FMDN_ECC_SECP160R1 and CONFIG_BT_FAST_PAIR_FMDN_ECC_SECP256R1 - These options are used to select the elliptic curve for calculating the FMDN advertising payload. The secp160r1 elliptic curve is enabled by default.

  • There are following battery configuration options for the FMDN extension (see Battery level indication and Battery information with DULT):

    • CONFIG_BT_FAST_PAIR_FMDN_BATTERY_LEVEL_LOW_THR - The option configures the threshold percentage value for entering the low battery state as defined in the FMDN extension.

    • CONFIG_BT_FAST_PAIR_FMDN_BATTERY_LEVEL_CRITICAL_THR - The option configures the threshold percentage value for entering the critically low battery state as defined in the FMDN extension.

    • CONFIG_BT_FAST_PAIR_FMDN_BATTERY_DULT - The option configures the FMDN module to pass the battery information to the DULT module and to support its mechanism for providing battery information to the connected peers. This option can only be used when the CONFIG_BT_FAST_PAIR_FMDN_DULT Kconfig option is enabled.

  • There are following read mode configuration options for the FMDN extension (see Using the read mode callbacks and managing the read mode state):

    • CONFIG_BT_FAST_PAIR_FMDN_READ_MODE_FMDN_RECOVERY_TIMEOUT - The option configures the Ephemeral Identity Key (EIK) recovery mode timeout in minutes.

  • There are following ringing configuration options for the FMDN extension (see Using the ringing callbacks and managing the ringing state):

    • CONFIG_BT_FAST_PAIR_FMDN_RING_COMP_NONE, CONFIG_BT_FAST_PAIR_FMDN_RING_COMP_ONE, CONFIG_BT_FAST_PAIR_FMDN_RING_COMP_TWO, and CONFIG_BT_FAST_PAIR_FMDN_RING_COMP_THREE - These options are used to select the set of ringing components. The option with no ringing component is enabled by default.

    • CONFIG_BT_FAST_PAIR_FMDN_RING_VOLUME - The option enables ringing volume support.

    • CONFIG_BT_FAST_PAIR_FMDN_RING_REQ_TIMEOUT_DULT_BT_GATT - The option configures the ringing timeout for connected peers that use DULT-based ringing mechanism. This option can only be used when the CONFIG_BT_FAST_PAIR_FMDN_DULT is enabled.

    • CONFIG_BT_FAST_PAIR_FMDN_RING_REQ_TIMEOUT_DULT_MOTION_DETECTOR - The option configures the ringing timeout for ringing requests from the DULT motion detector. This option can only be used when the CONFIG_BT_FAST_PAIR_FMDN_DULT is enabled.

  • There are following beacon clock service configuration options for the FMDN extension (see Beacon clock service):

    • CONFIG_BT_FAST_PAIR_FMDN_CLOCK_NVM_UPDATE_TIME - The option configures the time interval (in minutes) of periodic beacon clock writes to the non-volatile memory.

    • CONFIG_BT_FAST_PAIR_FMDN_CLOCK_NVM_UPDATE_RETRY_TIME - The option configures the retry time (in seconds) when the beacon clock write to the non-volatile memory fails.

• CONFIG_BT_FAST_PAIR_USE_CASE_UNKNOWN, CONFIG_BT_FAST_PAIR_USE_CASE_INPUT_DEVICE, CONFIG_BT_FAST_PAIR_USE_CASE_LOCATOR_TAG`and :kconfig:option:`CONFIG_BT_FAST_PAIR_USE_CASE_MOUSE - These options are used to select the Fast Pair use case and configure the Fast Pair library according to the Fast Pair Device Feature Requirements for the chosen use case. The CONFIG_BT_FAST_PAIR_USE_CASE_UNKNOWN Kconfig option is used by default.

See the Kconfig help for details.

Override of default Kconfig values

To simplify the configuration process, the GFPS modifies the default values of related Kconfig options to meet the Fast Pair requirements. The service also enables some of the functionalities using Kconfig select statement.

Bluetooth privacy

The service selects Bluetooth privacy (CONFIG_BT_PRIVACY).

During not discoverable advertising, the Resolvable Private Address (RPA) rotation must be done together with the Fast Pair payload update. Because of this, the RPA cannot be rotated by Zephyr in the background.

During discoverable advertising session, the Resolvable Private Address (RPA) rotation must not happen. Therefore, consider the following points:

• Make sure that your advertising session is shorter than the value in the CONFIG_BT_RPA_TIMEOUT option.

• Call the bt_le_oob_get_local() function to trigger RPA rotation and reset the RPA timeout right before advertising starts.

Note

If you use the FMDN extension, and your Provider is provisioned as an FMDN beacon, do not use the bt_le_oob_get_local() function. For more details, see the Setting up Bluetooth LE advertising section of the Fast Pair integration guide.

Bluetooth Security Manager Protocol (SMP)

The service selects the Kconfig options CONFIG_BT_SMP, CONFIG_BT_SMP_APP_PAIRING_ACCEPT, and CONFIG_BT_SMP_ENFORCE_MITM. The Fast Pair specification requires support for Bluetooth® Low Energy pairing and enforcing Man-in-the-Middle (MITM) protection during the Fast Pair procedure.

Firmware Revision characteristic

The Fast Pair specification requires enabling GATT Device Information Service and the Firmware Revision characteristic for selected Fast Pair use cases (for example, the input device use case).

For this reason, the relevant use case Kconfig options (for example, the CONFIG_BT_FAST_PAIR_USE_CASE_INPUT_DEVICE Kconfig option) select the CONFIG_BT_DIS and CONFIG_BT_DIS_FW_REV Kconfig options. If the target project uses Zephyr’s application version management, the default value of the CONFIG_BT_DIS_FW_REV_STR Kconfig option is set according to the versioning information found in the VERSION file. Otherwise, it is set to 0.0.0+0.

MTU configuration

The Fast Pair specification suggests using ATT maximum transmission unit (MTU) value of 83 if possible. Because of this requirement, the default values of the following Kconfig options are modified by the GFPS Kconfig:

• CONFIG_BT_L2CAP_TX_MTU

• CONFIG_BT_BUF_ACL_TX_SIZE

• CONFIG_BT_BUF_ACL_RX_SIZE

• CONFIG_BT_CTLR_DATA_LENGTH_MAX

Tip

When using nRF53 Series devices, this part of the configuration cannot be automatically updated for the network core and you must manually align it. The listed options must be set on the network core to the default values specified by the GFPS Kconfig options.

Security re-establishment

By default, the Fast Pair service disables the automatic security re-establishment request as a peripheral (CONFIG_BT_GATT_AUTO_SEC_REQ). This allows a Fast Pair Seeker to control the security re-establishment.

Partition Manager

The Fast Pair provisioning data is preprogrammed to a dedicated flash memory partition. The GFPS selects the CONFIG_PM_SINGLE_IMAGE Kconfig option to enable the Partition Manager.

Settings

The GFPS uses Zephyr’s Settings to store Account Keys and the Personalized Name. With the FMDN extension enabled, it additionally stores the Owner Account Key, the EIK and the Beacon Clock. Because of this, the GFPS selects the CONFIG_SETTINGS Kconfig option.

Bluetooth LE extended advertising for the FMDN extension

The FMDN extension (see CONFIG_BT_FAST_PAIR_FMDN) selects the CONFIG_BT_EXT_ADV Kconfig option. The extension uses the Bluetooth LE Extended Advertising Zephyr API to support simultaneous broadcast of multiple advertising sets. In the simplest scenario, you should have the following two advertising sets in your application:

• The application-specific advertising set with the Fast Pair payload.

• The FMDN advertising set for the FMDN extension.

For more details regarding the advertising policy of the FMDN extension, see the Setting up Bluetooth LE advertising section of the Fast Pair integration guide.

DULT module for the FMDN extension

The CONFIG_BT_FAST_PAIR_FMDN_DULT of the FMDN extension selects the CONFIG_DULT Kconfig option to enable the DULT module. The FMDN extension implementation also acts as middleware between the user application and the DULT module. The DULT module integration is required for small and not easily discoverable accessories. The CONFIG_BT_FAST_PAIR_FMDN_DULT is enabled by default.

The CONFIG_BT_FAST_PAIR_FMDN_DULT_MOTION_DETECTOR of the FMDN extension selects the CONFIG_DULT_MOTION_DETECTOR Kconfig option to enable the motion detector feature of the DULT module. With this option enabled, the FMDN extension passes the DULT motion detector callbacks from the DULT module to application. To learn more about the DULT motion detector, see Interacting with the motion detector.

The CONFIG_BT_FAST_PAIR_FMDN_BATTERY_DULT of the FMDN extension selects the CONFIG_DULT_BATTERY Kconfig option to enable the battery support in the DULT module. With this option enabled, the FMDN extension passes the battery information also to the DULT module.

For more details on the DULT module, see the Detecting Unwanted Location Trackers (DULT) module documentation.

Implementation details

The implementation uses BT_GATT_SERVICE_DEFINE to statically define and register the Fast Pair GATT service. The Fast Pair service automatically handles all requests received from the Fast Pair Seeker except for operations on the Beacon Actions characteristic that is part of the FMDN extension. For more details, see the Setting up GATT service section of the Fast Pair integration guide.

Bluetooth authentication

The Bluetooth pairing is handled using a set of Bluetooth authentication callbacks (bt_conn_auth_cb). The pairing flow and the set of Bluetooth authentication callbacks in use depend on whether the connected peer follows the Fast Pair pairing flow:

• If the peer follows the Fast Pair pairing flow, the Fast Pair service calls the bt_conn_auth_cb_overlay() function to automatically overlay the Bluetooth authentication callbacks. The function is called while handling the Key-based Pairing request. Overlying callbacks allow the GFPS to take over Bluetooth authentication during the Fast Pair Procedure and perform all of the required operations without interacting with the application.

• If the peer does not follow the Fast Pair pairing flow, normal Bluetooth LE pairing and global Bluetooth authentication callbacks are used.

API documentation

Header file: include/bluetooth/services/fast_pair/fast_pair.h

Source files: subsys/bluetooth/services/fast_pair

Fast Pair API

FMDN extension

Header file: include/bluetooth/services/fast_pair/fmdn.h

Source files: subsys/bluetooth/services/fast_pair/fmdn

Fast Pair FMDN API

Fast Pair UUID API

Header file: include/bluetooth/services/fast_pair/uuid.h

Source files: subsys/bluetooth/services/fast_pair

Fast Pair UUID API