Detecting Unwanted Location Trackers (DULT)
The Detecting Unwanted Location Trackers (DULT) library implements a set of functionalities required for Detecting Unwanted Location Trackers (DULT) integration with the nRF Connect SDK. The implementation is based on the official DULT specification, which lists a set of best practices and protocols for products with built-in location tracking capabilities. Following the specification improves the privacy and safety of individuals by preventing the location tracking products from tracking users without their knowledge or consent.
Accessory non-owner service (ANOS)
The DULT library implements the accessory non-owner service (ANOS), which is a GATT service that uses the accessory non-owner characteristic to communicate with other devices.
The ANOS uses UUID of 15190001-12F4-C226-88ED-2AC5579F2A85.
The accessory non-owner characteristic manages the DULT Accessory Information and the DULT Non-owner controls defined in the DULT specification.
Configuration
Set the CONFIG_DULT Kconfig option to enable the module.
This Kconfig option depends on the CONFIG_BT option that enables the Bluetooth® stack.
The following Kconfig options are also available for this module:
CONFIG_DULT_BATTERY- This option enables support for battery information such as battery type and battery level. The battery information is an optional feature in the DULT specification. By default, this option is disabled.CONFIG_DULT_BATTERY_LEVEL_CRITICAL_THR,CONFIG_DULT_BATTERY_LEVEL_LOW_THR, andCONFIG_DULT_BATTERY_LEVEL_MEDIUM_THR- These options allow to configure the mapping between a battery level expressed as a percentage value and battery levels defined in the DULT specification. The default values are set to10,40, and80respectively.CONFIG_DULT_BATTERY_TYPE_POWERED,CONFIG_DULT_BATTERY_TYPE_NON_RECHARGEABLE, andCONFIG_DULT_BATTERY_TYPE_RECHARGEABLE- These options allow to choose the device’s declared battery type. By default, theCONFIG_DULT_BATTERY_TYPE_POWEREDis chosen.
There are following ANOS configuration options for the DULT module:
CONFIG_DULT_BT_ANOS_ID_PAYLOAD_LEN_MAX- This option allows to configure the maximum length of the accessory-locating network identifier. The default value is set to18. The identifier is defined by the accessory-locating network that the accessory belongs to.CONFIG_DULT_BT_ANOS_INDICATION_COUNT- This option allows to configure the number of simultaneously processed GATT indications by the ANOS. The default value is set to2.
CONFIG_DULT_MOTION_DETECTOR- This option enables support for motion detector. The motion detector is an optional feature in the DULT specification. For more details see the DULT motion detector section of the DULT specification. This option is disabled by default.CONFIG_DULT_MOTION_DETECTOR_TEST_MODE- This option allows to configure motion detector parameters for testing purposes. These values are defined in the DULT specification and should not be changed in the production code. This option is disabled by default.CONFIG_DULT_MOTION_DETECTOR_SEPARATED_UT_BACKOFF_PERIOD- This option allows to configure the period in minutes to disable the motion detector if the accessory is in the separated state. If this option is configurable, its default value is set to2. Otherwise, its default value is set to360according to the DULT specification.CONFIG_DULT_MOTION_DETECTOR_SEPARATED_UT_TIMEOUT_PERIOD_MIN- This option allows to configure the minimum time span in minutes in separated state before enabling motion detector. If this option is configurable, its default value is set to3. Otherwise, its default value is set to480according to the DULT specification.CONFIG_DULT_MOTION_DETECTOR_SEPARATED_UT_TIMEOUT_PERIOD_MAX- This option allows to configure the maximum time span in minutes in separated state before enabling motion detector. If this option is configurable, its default value is set to3. Otherwise, its default value is set to1440according to the DULT specification.
See the Kconfig help for details.
Implementation details
The implementation uses BT_GATT_SERVICE_DEFINE to statically define and register the ANOS.
Because of that, the ANOS is still present in the GATT database after the DULT subsystem is disabled.
In the DULT subsystem disabled state, GATT operations on the ANOS are rejected.
The ANOS handles all requests received from the outer world. In case of an application input needed to handle a GATT operation, the DULT subsystem calls the appropriate registered application callback. For more details, see the Integration steps section of the DULT integration guide.
API documentation
include/dult.hsubsys/dult