Google 快速配對服務
透過集合功能整理內容
你可以依據偏好儲存及分類內容。
簡介
Google 快速配對服務 (GFPS) 會使用藍牙低功耗 (BLE) 技術,在不耗用大量手機電力的情況下,探索附近的藍牙裝置,並根據裝置的接近程度提供「神奇」的體驗。
功能
GFPS 旨在協助配對藍牙和 BLE 裝置 (例如喇叭、耳機、車用套件、滑鼠和鍵盤),並盡可能減少使用者互動。透過實作下列規格,Google 將持續發布以此為基礎的其他功能。包括:
- 在裝置處於配對模式時顯示半頁通知,方便輕鬆完成初始配對。此外,隨附應用程式也能輕鬆向使用者行銷。
- 在初始配對完成後,將裝置與使用者帳戶建立關聯。
- 當裝置開啟且靠近使用者擁有的其他手機、平板電腦或電腦時,會顯示後續配對通知,讓使用者不必知道如何將裝置重新設為配對模式,才能與其他裝置配對。
- 將個人化名稱與裝置建立關聯。
- 顯示耳機的電池通知。
- 在 Android 11 以上版本中顯示裝置詳細資料。
- 使用者可找出遺失的耳機或耳塞。
- 在網路連線不佳的情況下,可使用離線配對功能。
- 支援音訊自動切換功能,根據使用者活動 (例如開始播放電影) 和優先事件 (例如來電),在裝置之間流暢切換耳機連線。
- 支援可穿戴式裝置控制項,為重要的可穿戴式裝置功能提供更完善的存取控管機制。
功能需求
這項功能的支援需求會因裝置類型而異。詳情請參閱「裝置功能需求」。
設定檔依附元件
GFPS 實作項目與藍牙核心規格 4.2 以上版本相容。
八位元順序
只要欄位包含多個位元組,位元組排序方式就是大端序,也就是網路位元組排序 (從最高有效八位元到最低有效八位元)。
請注意,雖然這是透過網路傳輸位元組的標準,但與 Bluetooth SIG 規格中多位元組欄位的位元組順序不同 (例如廣告中的服務 UUID 是小端順序)。
除非另有註明,否則本頁面中的內容是採用創用 CC 姓名標示 4.0 授權,程式碼範例則為阿帕契 2.0 授權。詳情請參閱《Google Developers 網站政策》。Java 是 Oracle 和/或其關聯企業的註冊商標。
上次更新時間:2025-08-13 (世界標準時間)。
[null,null,["上次更新時間: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)."]]