Message Stream
Fast Pair requires an additional channel for a persistent connection with the
Providers to support Fast Pair extensions. When the Provider connects to a
supported Seeker, the Seeker will attempt to connect the message stream.
Supported Implementation
Fast Pair supports two kinds of message stream implementations:
RFCOMM
Use fixed UUID as the endpoint
df21fe2c-2515-4fdb-8886-f12c4d67927c
L2CAP
Use GATT PSM Characteristic to obtain the PSM value for L2CAP connection.
Once connected, messages can be exchanged in the following format:
| Octet |
Data Type |
Description |
Mandatory? |
| 0 |
uint8 |
Message group |
Mandatory |
| 1 |
uint8 |
Message code |
Mandatory |
| 2 - 3 |
uint16 |
Additional data length |
Mandatory |
| 4 - n |
|
Additional data |
Optional |
The additional data length and additional data fields should be big endian.
Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License, and code samples are licensed under the Apache 2.0 License. For details, see the Google Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.
Last updated 2024-10-25 UTC.
[null,null,["Last updated 2024-10-25 UTC."],[[["Fast Pair utilizes a persistent connection with Providers via an additional channel to enable Fast Pair extensions."],["Two message stream implementations are supported: RFCOMM using a fixed UUID and L2CAP using GATT PSM Characteristic for connection."],["Exchanged messages adhere to a specific format containing message group, message code, additional data length, and optional additional data."],["Data length and additional data fields within messages are represented in big endian format."]]],[]]
