Google 快速配对服务
使用集合让一切井井有条
根据您的偏好保存内容并对其进行分类。
简介
Google 快速配对服务 (GFPS) 利用蓝牙低功耗 (BLE) 发现附近的蓝牙设备,而不会耗用大量手机电量,从而实现基于设备接近度的“神奇”场景。
功能
GFPS 旨在简化蓝牙和 BLE 设备(例如音箱、耳机、车载套件、鼠标和键盘)的配对,尽可能减少用户互动。通过实现以下规范,Google 将继续发布基于该规范的其他功能。其中包括:
- 在设备处于配对模式时显示半页通知,以便轻松完成初始配对。此外,您还可以轻松向用户营销配套应用。
- 在初始配对完成后,将设备与用户的账号相关联。
- 当设备处于开启状态且位于用户拥有的其他手机、平板电脑或桌面设备附近时,显示后续配对通知,以便用户无需知道如何将设备重新置于配对模式,即可与其他设备配对。
- 将个性化名称与设备相关联。
- 系统会显示头戴式耳机的电池通知。
- 在 Android 11 及更高版本中显示设备详情。
- 让用户能够定位丢失的耳机或耳机。
- 离线配对适用于网络信号较弱的情况。
- 支持音频切换,以便根据用户活动(例如开始播放电影)和高优先级事件(例如来电)在设备之间无缝切换耳机连接。
- 支持 Hearable Controls,以便更好地控制对重要 Hearable 功能的访问权限。
功能要求
功能支持要求因设备类型而异。如需了解详情,请参阅设备功能要求。
配置文件依赖项
GFPS 实现与蓝牙核心规范 v4.2 或更高版本兼容。
八位字节顺序
无论字段由多少个字节组成,字节顺序都是大端字节顺序,即网络字节顺序(从最有意义的八位字节到最无意义的八位字节)。
请注意,虽然这是通过网络传输的字节的标准顺序,但与 Bluetooth SIG 规范中多字节字段的字节顺序不同(例如,广告中的服务 UUID 采用小端字节顺序)。
如未另行说明,那么本页面中的内容已根据知识共享署名 4.0 许可获得了许可,并且代码示例已根据 Apache 2.0 许可获得了许可。有关详情,请参阅 Google 开发者网站政策。Java 是 Oracle 和/或其关联公司的注册商标。
最后更新时间 (UTC):2025-08-13。
[null,null,["最后更新时间 (UTC):2025-08-13。"],[[["\u003cp\u003eGoogle Fast Pair Service (GFPS) uses Bluetooth Low Energy to easily pair devices like headphones, speakers, and keyboards with minimal user interaction.\u003c/p\u003e\n"],["\u003cp\u003eGFPS allows devices to be automatically paired with other devices logged into the same Google account, simplifying the connection process.\u003c/p\u003e\n"],["\u003cp\u003eThe service offers additional features like personalized device names, battery notifications, and seamless audio switching between devices.\u003c/p\u003e\n"],["\u003cp\u003eGFPS is compatible with Bluetooth 4.2 or later and utilizes a big-endian octet order for data transmission.\u003c/p\u003e\n"],["\u003cp\u003eDevice feature requirements and a reference implementation are available for developers to integrate GFPS functionality.\u003c/p\u003e\n"]]],[],null,["# Google Fast Pair Service\n\nIntroduction\n------------\n\nThe Google Fast Pair Service (*GFPS* ) utilizes Bluetooth Low Energy (*BLE*) to\ndiscover nearby Bluetooth devices without using significant phone battery,\nenabling \"magical\" scenarios based on device proximity.\n\n### Features\n\nGFPS is aimed at facilitating the pairing of Bluetooth and BLE devices, such as\nspeakers, headphones, car kits, mice and keyboards, with as little user\ninteraction required as possible. By implementing the following spec, Google\nwill continue to release additional features that build upon it. This includes:\n\n1. Displaying a half page notification when the device is in pairing mode to facilitate [easy initial pairing](/nearby/fast-pair/specifications/configuration#DeviceDiscovery \"Device Discovery\"). Additionally companion apps are easily marketed to users.\n2. Associating the device with the user's account after the initial pairing has completed.\n3. Displaying a [subsequent pairing notification](/nearby/fast-pair/specifications/service/provider#AdvertisingWhenNotDiscoverable \"Advertizing when not discoverable\") when the device is turned on and near another phone, tablet, or desktop that the user owns, so that the user does not need to know how to put the device back into pairing mode before pairing with their other devices.\n4. Associating a [personalized name](/nearby/fast-pair/specifications/extensions/personalizedname \"Extensions - Personalized name\") with the device.\n5. [Battery notifications](/nearby/fast-pair/specifications/extensions/batterynotification \"Extensions - Battery Notifications\") are displayed for the headphones.\n6. Shows device details in Android 11+.\n7. Ability for users to locate a lost headset or buds.\n8. Offline pairing is available for low-network situations.\n9. Support [Audio switch](/nearby/fast-pair/specifications/extensions/sass \"Audio Switch\") to seamlessly transition headset connections between devices based on user activity (e.g. starting a movie) and prioritized events (e.g. an incoming call).\n10. Support [Hearable Controls](/nearby/fast-pair/specifications/extensions/hearablecontrols \"Hearable Controls\") to provide better access controls for important Hearable features.\n\n### Feature Requirements\n\nBased on the device type , the requirement for feature support would differ.\nSee the [Device Feature Requirements](/nearby/fast-pair/specifications/devicefeaturerequirement \"Link to the Device feature requirement.\") for more\ndetails.\n\n### Profile dependencies\n\nThe GFPS implementation is compatible with the Bluetooth Core\nSpecification v4.2 or later.\n\n### Octet order\n\nWherever a field consists of multiple bytes, the byte ordering is big-endian,\nthat is, network byte order (most-significant octet to least-significant octet).\n\nNote that while this is standard for bytes transferred over networks, it is\ndifferent from the byte ordering for multi-byte fields in Bluetooth SIG\nspecifications (for example, a service UUID in an advertisement is\nlittle-endian)."]]