目标受众群体
使用集合让一切井井有条
根据您的偏好保存内容并对其进行分类。
本页面适用于与系统集成商 (SI) 合作的合作伙伴。Google 强烈建议您与 SI 合作。如果快速配对采用者没有 SI/SOC 合作伙伴,则应与您的 Google 技术支持客户经理或 fast-pair-integrations@google.com 联系以寻求支持。
背景
此工作流程于 2022 年第 2 季度实施,SoC 合作伙伴可集成快速配对解决方案,并帮助 OEM 和 ODM 合作伙伴进行快速配对项目开发和认证。支持此流程的主要系统集成商 (SI) 合作伙伴包括:
- Airoha
- BES
- Qualcomm
- Realtek
在生态系统中的角色和职责

与合作伙伴的快速配对集成流程包括图 1 中列出的任务,必须先完成这些任务,然后才能在第三方实验室获得正式认证。
OEM 负责以下任务:
模型 ID 注册:在设备控制台上注册您的设备,以获取设备的唯一模型 ID(一个项目可以有多个模型 ID)。在开始快速配对的集成和开发流程之前,您必须先在业务提案中请求项目激活。快速配对设备(每个设备都有唯一的型号 ID)需要与一个或多个 Google Cloud 项目相关联。如需了解详情,请参阅“模型 ID”页面。
商业提案:您需要完成提交商业提案,以通知 Google 业务发展团队,确认已签订必要的合同,并选择要与之合作的系统集成商 (SI) 合作伙伴。您的 SI 或 SoC 合作伙伴将帮助您在 Google 问题跟踪器中提交问题跟踪器启动提案,以确认项目范围。如需了解详情,请参阅认证流程部分。
快速集成:与 SI 或 SoC 合作伙伴合作,在蓝牙 (BT) 固件中进行产品开发和快速配对解决方案集成。如果您有任何疑问,请与您的 SI 合作伙伴联系。如需了解详情,请参阅快速配对技术指南。
自测:使用 Validator 应用运行并提交校准测试和端到端集成测试的结果。如需了解详情,请参阅 BT Classic 或 BlueTooth LE Audio 自测报告表单,具体取决于实现方式。完成自测后,请将自测报告提交给 SI 或 SoC 合作伙伴,由其申请技术审批,以便 Google 评估您的自测结果。如需了解详情,请参阅快速配对认证流程。
申请技术审批:与您的 SI 或 SoC 合作伙伴合作,由他们在 Google 问题跟踪器系统中提交技术审批请求。如需了解详情,请参阅认证流程部分。
在第三方实验室进行正式认证:在 Google 通过技术审批请求工单(也称为预认证)告知您的 SI 或 SoC 合作伙伴您的项目已准备好开始认证流程后,请与第三方实验室联系以继续进行正式认证。Google 可能会要求您根据需要将样品寄送给 Google。如需了解详情,请参阅将设备寄送到第三方实验室页面。
收到技术审批:您将收到技术审批函,并在附近分享控制台上启用快速配对。
发布后 OTA:与 SI 或 SoC 合作伙伴合作处理发布后 OTA 更新请求。如需了解详情,请参阅认证流程部分。
如未另行说明,那么本页面中的内容已根据知识共享署名 4.0 许可获得了许可,并且代码示例已根据 Apache 2.0 许可获得了许可。有关详情,请参阅 Google 开发者网站政策。Java 是 Oracle 和/或其关联公司的注册商标。
最后更新时间 (UTC):2025-08-22。
[null,null,["最后更新时间 (UTC):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."]]