目標對象
透過集合功能整理內容
你可以依據偏好儲存及分類內容。
本頁面適用於與系統整合商 (SI) 合作的合作夥伴。Google 強烈建議您與 SI 合作。如果您沒有 SI/SOC 合作夥伴,但採用了快速配對功能,請與 Google 技術客戶經理或 fast-pair-integrations@google.com 聯絡以取得支援。
背景
這項流程於 2022 年第 2 季實施,讓 SoC 合作夥伴整合快速配對解決方案,並協助原始設備製造商 (OEM) 和原始設計製造商 (ODM) 合作夥伴進行快速配對專案開發和認證。支援這項流程的主要系統整合商 (SI) 合作夥伴如下:
- Airoha
- BES
- Qualcomm
- Realtek
生態系統中的角色和責任

與合作夥伴進行 Fast Pair 整合程序時,請完成圖 1 所列的任務,並在第三方實驗室進行正式認證。
原始設備製造商 (OEM) 負責執行下列工作:
型號 ID 註冊:在裝置主控台註冊裝置,取得裝置的專屬型號 ID (專案可有多個型號 ID)。在進行快速配對的整合和開發程序之前,您必須在業務提案中要求啟用專案。快速配對裝置 (每個裝置都有專屬型號 ID) 必須與一或多個 Google Cloud 專案建立關聯。如需更多資訊,請參閱 「Model Id」頁面。
商業提案:您必須完成提交商業提案,通知 Google 業務發展團隊確認已簽訂必要合約,並選擇合作的系統整合 (SI) 合作夥伴。SI 或 SoC 合作夥伴會協助您在 Google 問題追蹤器中提交問題追蹤器啟動提案,以便確認專案範圍。詳情請參閱「認證程序」一節。
快速整合:與 SI 或 SoC 合作夥伴合作,在藍牙 (BT) 韌體中整合產品開發和快速配對解決方案。如有任何問題,請與 SI 合作夥伴聯絡。詳情請參閱快速配對技術規範。
自測:使用驗證器應用程式執行並提交校正測試和端對端整合測試的結果。如需更多資訊,請根據實作方式查看 BT Classic 或 BlueTooth LE Audio 自測報告表單。完成自測後,請將自測報告提交給 SI 或 SoC 合作夥伴,由他們申請技術核准,以便 Google 評估您的自測結果。詳情請參閱 Fast Pair 認證程序。
申請技術核准:請與 SI 或 SoC 合作夥伴合作,由他們在 Google 問題追蹤系統中提交技術核准要求。詳情請參閱「認證程序」一節。
第三方實驗室的官方認證:Google 在技術核准要求 (也稱為預認證) 的支援單中通知 SI 或 SoC 合作夥伴,您的專案已準備好開始認證程序,請與第三方實驗室聯絡,以便繼續進行官方認證。Google 可能會要求你視需要將樣本寄送給 Google。詳情請參閱「將裝置運送至第三方實驗室」頁面。
收到技術核准通知:您會收到技術核准通知信,並在鄰近裝置主控台上啟用快速配對功能。
OTA 後續更新:請與 SI 或 SoC 合作夥伴合作,處理 OTA 後續更新要求。詳情請參閱「認證程序」一節。
除非另有註明,否則本頁面中的內容是採用創用 CC 姓名標示 4.0 授權,程式碼範例則為阿帕契 2.0 授權。詳情請參閱《Google Developers 網站政策》。Java 是 Oracle 和/或其關聯企業的註冊商標。
上次更新時間:2025-08-22 (世界標準時間)。
[null,null,["上次更新時間:2025-08-22 (世界標準時間)。"],[[["\u003cp\u003eThis guide is for Original Equipment Manufacturers (OEMs) partnering with a System Integrator (SI) to implement Google Fast Pair in their devices.\u003c/p\u003e\n"],["\u003cp\u003eOEMs need to register their device model, submit a business proposal, and work with their SI on Fast Pair integration and self-testing before applying for technical approval.\u003c/p\u003e\n"],["\u003cp\u003eAfter Google grants technical approval, OEMs must undergo official certification at a third-party lab, obtain final approval, and then manage post-launch updates with their SI.\u003c/p\u003e\n"],["\u003cp\u003eGoogle strongly encourages OEMs to collaborate with an SI for Fast Pair adoption, and those without an SI should contact Google directly for support.\u003c/p\u003e\n"],["\u003cp\u003eThe primary SI partners supporting this workflow are Airoha, BES, Qualcomm, and Realtek.\u003c/p\u003e\n"]]],[],null,["# Target Audience\n\n\u003cbr /\u003e\n\nThis page is intended for Partners who work with a System Integrator (SI).\nGoogle strongly recommends partnering with an SI. Fast Pair adopters without a\nSI/SOC partner should contact your Google Technical Account Manager or\n[fast-pair-integrations@google.com](mailto:fast-pair-integrations@google.com \"MailTo link for the Support group.\") for support.\n\nBackground\n----------\n\nThis workflow, implemented Q2 2022, has SoC partners integrate Fast Pair\nsolutions and help OEM and ODM partners on Fast Pair project development and\ncertification. The primary System Integrator (SI) partners supporting this flow\nare:\n\n- Airoha\n- BES\n- Qualcomm\n- Realtek\n\nRole and Responsibilities in the Ecosystem\n------------------------------------------\n\nThe Fast Pair integration process with partners includes the tasks listed in\nFigure 1 and must be completed before official certification in 3rd\nParty Labs.\n\nOEMs are responsible for the following tasks:\n\n- **Model ID Registration** : Register your device on the\n [Device console](/nearby/devices \"Link to the Nearby console.\") to obtain a unique model ID for your device (a\n project can have multiple Model IDs). This is required to request project\n activation in the business proposal before the integration and development\n process for Fast Pair. Fast Pair devices (each with a unique model ID) need to\n be associated with one or more Google Cloud projects. For additional\n information, see the [the Model Id page](/nearby/fast-pair/specifications/service/modelregistration#CreateModelId \"How to register a Fast Pair Model ID.\").\n\n- **Business Proposal** : You will need to complete a\n [business proposal submission](https://docs.google.com/forms/d/1-QLoVRkxZQQtk14lGvgs88laM9zC1p35pzYwXBLosFk/viewform \"Link to the Business Proposal submission form.\") to notify the Google Business\n Development team to confirm the necessary contracts are in place, and choose\n System Integrator (SI) partners to collaborate with. Your SI or SoC partners\n will help you submit an issue tracker kickoff proposal in the Google issue\n tracker to confirm the project scope. For additional information, see the\n [certification process](/nearby/fast-pair/certification-process#preparing_for_certification_via_self_testing \"Link to the self-test section.\") section.\n\n- **Fast Integration** : Work with your SI or SoC partners on product development\n and Fast Pair solution integration in Bluetooth (BT) firmware. If you have any\n questions, reach out to your SI partner. For more information, see the\n [Fast Pair technical guidelines](/nearby/fast-pair/fast-pair-certification-guideline \"Link to the Fast Pair Certification Guidelines page.\").\n\n- **Self-Test** : Run and submit the results of the calibration test and\n end-to-end integration test with the Validator app. For more information, see\n 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 [BlueTooth 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.\")\n Self-Test Report forms, depending on implementation. Once you have completed\n the self-test, submit the Self-Test Report to your SI or SoC partner who will\n apply for technical approval so that Google can evaluate your self-test\n results. See the Fast Pair [certification process](/nearby/fast-pair/certification-process#preparing_for_certification_via_self_testing \"Link to the self-test section.\") for more\n details.\n\n- **Apply for Technical Approval** : Work with your SI or SoC partners who will\n submit the technical approval request in the Google issue tracker system. For\n more information, see the [certification process](/nearby/fast-pair/certification-process#preparing_for_certification_via_self_testing \"Link to the self-test section.\") section.\n\n- **Official Certification at a Third-Party Lab** : Once Google has informed your\n SI or SoC partner on the technical approval request ticket (also can be known\n as pre-certification) that your project is ready to start the certification\n process, contact a third-party lab in order to proceed with the official\n certification. Google may request for you to ship samples to Google as needed.\n For more information, see the\n [Shipping Devices to 3rd Party Labs](/nearby/fast-pair/shipping-devices-to-3pl \"Link to the page for shipping devices to 3rd Party Labs.\") page.\n\n- **Receipt of Technical Approval** : You will receive a Technical Approval\n letter along with Fast Pair enablement on the [Nearby console](/nearby/devices \"Link to the Nearby console.\").\n\n- **Post Launch OTA** : Work with your SI or SoC partner on post-launch OTA\n update requests. For more information, see the\n [certification process](/nearby/fast-pair/certification-process#preparing_for_certification_via_self_testing \"Link to the self-test section.\") section."]]