Macros

Pattern that matches an unknown PairingProperties member.

Structs

A Stream of incoming requests for Access
Represents the bonding data for a single peer.
A Stream of incoming requests for Bootstrap
A Stream of incoming requests for Configuration
Represents persistent local host data.
Information about a Bluetooth controller and its associated host-subsystem state.
A Stream of incoming requests for HostWatcher
Represents the persistent configuration of a single host-subsystem instance. This is used for identity presentation (inquiry, inquiry response, and advertisement) and for bonding secrets recall (encrypting link data to peers associated with this identity).
Represents a 128-bit secret key.
The preferred LE connection parameters of the peer.
Represents a LE Long-Term peer key used for link encyrption. The ediv and rand fields are zero if distributed using LE Secure Connections pairing.
A Stream of incoming requests for PairingDelegate2
A Stream of incoming requests for PairingDelegate
Parameters that give a caller more fine-grained control over the pairing process. All of the fields of this table are optional and pairing can still succeed if none of them are set.
A Stream of incoming requests for PairingRequest
A Stream of incoming requests for Pairing
Represents a remote BR/EDR, LE, or dual-mode BR/EDR/LE peer.
Represents a key that was received from a peer.
A Stream of incoming requests for ProcedureToken
Represents the Bluetooth Host Subsystem parameters available for configuration. Each parameter is set to a default upon Bluetooth system initialization. The default values for each parameter can be found in //src/connectivity/bluetooth/core/bt-gap/config/default.js.

Enums

Protocol that abstracts the operational modes and procedures defined in the Bluetooth Generic Access Profile (see Core Specification v5.1, Vol 3, Part C).
Whether or not the device should form a bluetooth bond during the pairing prodecure. As described in Core Spec v5.2 | Vol 3, Part C, Sec 4.3
Protocol used to initialize persistent core Bluetooth data. This protocol populates data that determine the identity of this device as perceived by other Bluetooth devices.
Protocol to configure parameters and features for the core Bluetooth system. These settings apply to all bt-host drivers known to the system.
Protocol used to observe and manage the Bluetooth controllers on the system.
Input Capabilities for pairing exchanges. These should be set based on the ability of the local system to enter responses to pairing requests. See Volume 3, Part C, Table 5.3 for more information.
The LE Security Mode of a BLE device determines the possible security properties of the device. The security mode does not make specific guarantees about the current security properties of a device’s connections; it sets restrictions on the allowable security properties. See Core Spec v5.2 Vol. 3, Part C 10.2 for more details.
Output Capabilities for pairing excanges. These should be set based on the ability of the local system to display information to the user initiating or accepting a Bluetooth pairing. See Volume 3, Part C, Table 5.4 for more information.
A Bluetooth Pairing Delegate is responsible for confirming or denying pairing requests received from Bluetooth peers that connect or are being connected to the local device.
A Bluetooth Pairing Delegate is responsible for confirming or denying pairing requests received from Bluetooth peers that connect or are being connected to the local device.
Used to convey information to the peer on progress typing a passkey. The various types of keypresses can be used to customize what is communicated to the user requesting a pairing.
Different types required by the Security Manager for pairing methods. Bluetooth SIG has different requirements for different device capabilities.
Allows system clients to enable Bluetooth pairing.
This protocol is active when a pairing is in progress, and provided to the PairingDelegate via the PairingDelegate.StartRequest The server will close this protocol with an epitaph if the pairing process completes early without success:
The security level required for this pairing - corresponds to the security levels defined in the Security Manager Protocol in Vol 3, Part H, Section 2.3.1
Represents an active procedure. The validity of a handle that supports this protocol is tied to the activity of the procedure that it is attached to. To elaborate:

Constants

Maximum number of discovered services for each transport. Currently set to the number of valid 16-bit handles or PSMs used to access services.

Traits

Type Definitions