Google 快速配對服務
透過集合功能整理內容
你可以依據偏好儲存及分類內容。
Google 快速配對服務 (GFPS) 或快速配對 (FP) 是鄰近平台的元件,可利用傳統藍牙或藍牙低功耗 (BLE) 技術,快速且省電地配對裝置。
GFPS 可支援耳機、喇叭等各種裝置,讓合作夥伴在各系列產品中導入 FP 功能。規格也包含了幾個合作夥伴可導入的擴充功能,為客戶提供額外功能。
您可以使用公開 SDK,將 Fast Pair 整合至應用程式。
總覽
開始使用
合作夥伴如要採用或修改 GFPS,必須向 Google Fast Pair 業務開發 (BD) 團隊提交專案提案表單。合作夥伴必須先取得 BD 核准,才能開始將 GFPS 整合至裝置。在 GFPS 採用過程中,BD 也非常重要,可確保有效溝通。
Google 與 Google 認證快速配對系統整合商 (SI) 合作,為合作夥伴提供常見晶片組的預先建構解決方案。如果合作夥伴想採用現成解決方案,應在 FP 導入過程中與SI 合作夥伴密切合作。
部分合作夥伴 (尤其是不依賴預先建構解決方案的合作夥伴) 可能會在 FP 採用過程中直接與 Google 合作。業務開發人員會在專案提案表單討論中,讓合作夥伴瞭解他們目前的路徑。
最後,裝置必須經過認證,才能在市場上使用 GFPS 功能。合作夥伴在規劃 GFPS 採用時程時,應考量認證程序。
GFPS 採用程序
一般來說,合作夥伴在將 GFPS 納入產品並修改或更新時,會遵循下列程序:

以下是文字版的 GFPS 採用程序:
提交前
- 如果尚未建立 Google Cloud 專案,請為裝置建立Google Cloud 專案。
- 為特定裝置建立裝置頁面。
- 如要進一步瞭解這項程序,請參閱「模型 ID」頁面。
- 在裝置頁面中記下裝置的型號 ID。
- 提交專案提案表單,說明您的專案。
- 簽署 GFPS 規格 (例如搶先體驗) 所需的任何保密協議。
- 與合作夥伴建立關係。
- 如果您與 SI 合作,請與對方討論SI 程序。
- 開始整合,並請合作夥伴提供協助。
認證
- 在合作夥伴的協助下,在裝置上整合及驗證 GFPS。
- 請準備 BT Classic 或 BT LE Audio 自測報告表單。
- 您可能需要根據功能提供額外的自檢測報表,例如音訊切換器 BT Classic 或 BT LE Audio 自檢測報表表單。
- 提交裝置進行認證。
- Google 強烈建議您使用驗證應用程式執行認證測試。
- 獲得 Google 的正式認證,並取得啟用 GFPS 的權限。
FP DevSite 總覽
Fast Pair DevSite 分為多個部分,以便協助合作夥伴開發、採用及將 GFPS 整合至自家系統。
- FP 規格說明正式的 GFPS 規定。
- 「extensions」部分說明瞭 GFPS 可用的各種擴充功能。
- 「認證」一節說明如何為正式認證準備裝置,包括任何認證前步驟。
- 與 Google 和合作夥伴合作一節說明開發和整合程序的詳細資訊。
- 附錄會說明其他實用資訊,例如各種晶片組支援的 FP 版本,以及 FP 常見問題。
除非另有註明,否則本頁面中的內容是採用創用 CC 姓名標示 4.0 授權,程式碼範例則為阿帕契 2.0 授權。詳情請參閱《Google Developers 網站政策》。Java 是 Oracle 和/或其關聯企業的註冊商標。
上次更新時間:2025-08-22 (世界標準時間)。
[[["容易理解","easyToUnderstand","thumb-up"],["確實解決了我的問題","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["缺少我需要的資訊","missingTheInformationINeed","thumb-down"],["過於複雜/步驟過多","tooComplicatedTooManySteps","thumb-down"],["過時","outOfDate","thumb-down"],["翻譯問題","translationIssue","thumb-down"],["示例/程式碼問題","samplesCodeIssue","thumb-down"],["其他","otherDown","thumb-down"]],["上次更新時間:2025-08-22 (世界標準時間)。"],[[["\u003cp\u003eGoogle Fast Pair Service (GFPS) enables quick and power-efficient device pairing using Bluetooth Classic or BLE.\u003c/p\u003e\n"],["\u003cp\u003ePartners must submit a Project Proposal Form and receive approval before integrating GFPS.\u003c/p\u003e\n"],["\u003cp\u003eGoogle Certified Fast Pair System Integrators provide pre-built solutions for common chipsets.\u003c/p\u003e\n"],["\u003cp\u003eDevice certification is required before utilizing GFPS features in the market.\u003c/p\u003e\n"],["\u003cp\u003eThe Fast Pair DevSite provides resources on specifications, extensions, certification, and working with Google.\u003c/p\u003e\n"]]],["Google Fast Pair Service (GFPS) enables quick device pairing via Bluetooth. Partners must submit a Project Proposal Form for Google's approval before integration. The process involves creating a Google Cloud Project, defining a device Model ID, signing NDAs, and collaborating with a System Integrator (SI) or Google directly. Partners integrate GFPS, verify functionality, and complete Self-Test Reports. Certification is mandatory and includes submitting the device for testing, after which Google grants permission to enable GFPS features.\n"],null,["# The Google Fast Pair Service\n\n\u003cbr /\u003e\n\nThe Google Fast Pair Service (GFPS), or Fast Pair (FP), is a component of the\n[Nearby Platform](/nearby \"Link to the Nearby Platform page.\") that enables quick and power-efficient device\npairing utilizing BlueTooth Classic or BlueTooth Low Energy (BLE).\n\nThe GFPS is designed to accommodate a wide range of devices, from earbuds to\nspeakers, enabling Partners to implement FP features across families of\nproducts. The specification also includes several [extensions](/nearby/fast-pair/specifications/extensions/batterynotification \"Link to the Fast Pair Extensions page.\") Partners\ncan implement to provide customers with additional capabilities.\n\nYou can integrate Fast Pair into your app by using the [public SDK](https://github.com/google/nearby/releases \"Link to the FP Release Binaries.\").\n\nOverview\n--------\n\nGetting Started\n---------------\n\nPartners planning to adopt or modify the GFPS must submit a\n[Project Proposal Form](https://docs.google.com/forms/d/1-QLoVRkxZQQtk14lGvgs88laM9zC1p35pzYwXBLosFk/viewform \"Link to the Business Proposal submission form.\") to the Google Fast Pair Business Development\n(BD) team. BD's approval is required before Partners can begin integrating the\nGFPS into their device. BD is also critical of ensuring effective communication\nthrough the GFPS adoption process.\n\nGoogle works with Google Certified Fast Pair System Integrators (SIs) to provide\nPartners with prebuilt solutions to common [chipsets](/nearby/fast-pair/chipsets \"Link to the list of supported Chipsets.\"). Partners\nseeking ready-made solutions should work closely with their [SI partner](/nearby/fast-pair/system-integrator-roles-and-responsibilities \"Link to the Roles and Responsibilities page.\")\nthroughout the FP adoption process.\n\nSome Partners, particularly those who don't rely on prebuilt solutions, may work\ndirectly with Google during the FP adoption process. BD ensures Partners know\nwhich path they're on as part of the [Project Proposal Form](https://docs.google.com/forms/d/1-QLoVRkxZQQtk14lGvgs88laM9zC1p35pzYwXBLosFk/viewform \"Link to the Business Proposal submission form.\") discussion.\n\nFinally, a device must be [certified](/nearby/fast-pair/certification-process \"Link to the Certification Process page.\") before it can utilize GFPS\nfeatures in the market. Partners should account for the certification process\nwhen planning GFPS adoption schedules.\n\n### The GFPS Adoption Process\n\nIn general, Partners follow this process when adopting and modifying or updating\nthe GFPS into a product:\n\nTextually, the GFPS adoption process is described in the following steps:\n\n#### Pre-submission\n\n1. Create a [Google Cloud Project](https://cloud.google.com/docs/overview/#projects \"Link to the Google Cloud projects page.\") for your devices if one does not exist.\n 1. Create a device page for your specific device.\n 2. See [the Model ID page](/nearby/fast-pair/specifications/service/modelregistration#CreateModelId \"How to register a Fast Pair Model ID.\") for details on this process.\n 3. Record the Model ID of your device from the device page.\n2. Submit a [Project Proposal Form](https://docs.google.com/forms/d/1-QLoVRkxZQQtk14lGvgs88laM9zC1p35pzYwXBLosFk/viewform \"Link to the Business Proposal submission form.\") describing your project.\n3. Sign any NDAs required for the GFPS specification (such as early access).\n4. Establish a relationship with your Partner.\n 1. If working with an SI, discuss the [SI Process](/nearby/fast-pair/system-integrator-roles-and-responsibilities \"Link to the Roles and Responsibilities page.\") with them.\n5. Start Integrating with help from your Partner.\n\n#### Certification\n\n1. Integrate and verify the GFPS on your device with help from your Partner.\n2. Prepare either the [BT Classic](/static/nearby/fast-pair/downloads/self-test-reports/Bluetooth_Classic_-_Google_Fast_Pair_Self_Test_Report_10142020.zip \"Link to the Fast Pair Bluetooth Classic Self-Test Report sheet.\") or [BT LE Audio](/static/nearby/fast-pair/downloads/self-test-reports/LE_Audio_Dual_mode_-_Google_Fast_Pair_Self_Test_Report_2024_Q4.zip \"Link to the Fast Pair LE Audio Self-Test Report sheet.\") Self-Test Report form.\n 1. You may need additional Self-Test Reports based on your features, like the Audio switch [BT Classic](/static/nearby/fast-pair/downloads/self-test-reports/Bluetooth_Classic_SASS_Certification_Test_Report.zip \"Link to the Bluetooth Classic Audio switch Self-Test Report sheet.\") or [BT LE Audio](/static/nearby/fast-pair/downloads/self-test-reports/SASS_Certification_Test_Report_2024_Q3.zip \"Link to the LE Audio Audio switch Self-Test Report sheet.\") Self- Test Report forms.\n3. Submit your device for [Certification](/nearby/fast-pair/certification-process \"Link to the Certification Process page.\").\n 1. Google strongly recommends using the [Validator App](https://play.google.com/apps/testing/com.google.location.nearby.apps.fastpair.validator \"Link to the Validator App on the Google Play Store.\") for running certification tests.\n4. Receive official Certification from Google and permission to enable GFPS.\n\nFP DevSite Overview\n-------------------\n\nThe Fast Pair DevSite is divided into sections to better assist Partners in\ndeveloping, adopting, and integrating the GFPS into their system.\n\n- The [FP Specification](/nearby/fast-pair/specifications/introduction \"Link to the FP Specification.\") describes the formal GFPS requirements.\n- The [extensions](/nearby/fast-pair/specifications/extensions/batterynotification \"Link to the Fast Pair Extensions page.\") section describes various extensions available for the GFPS.\n- The [certification](/nearby/fast-pair/certification-process \"Link to the Certification Process page.\") section describes how to prepare a device for formal certification, including any pre-certification steps.\n- The [Working with Google and Partners](/nearby/fast-pair/system-integrator-roles-and-responsibilities \"Link to the Roles and Responsibilities page.\") section describes process details for development and integration.\n- The Appendix describes other useful information, such as the version of FP supported by various [chipsets](/nearby/fast-pair/chipsets \"Link to the list of supported Chipsets.\") and [FP FAQs](/nearby/fast-pair/fast-pair-faq \"Link to the Fast Pair FAQ page.\")."]]