Target Audiens
Tetap teratur dengan koleksi
Simpan dan kategorikan konten berdasarkan preferensi Anda.
Halaman ini ditujukan untuk Partner yang bekerja sama dengan Integrator Sistem (SI).
Google sangat merekomendasikan untuk berpartner dengan SI. Pengguna Sambungan Cepat tanpa
partner SI/SOC harus menghubungi Account Manager Teknis Google Anda atau
fast-pair-integrations@google.com untuk mendapatkan dukungan.
Latar belakang
Alur kerja ini, yang diterapkan pada Kuartal 2 2022, mengharuskan partner SoC mengintegrasikan solusi Sambungan Cepat
dan membantu partner OEM dan ODM dalam pengembangan dan
sertifikasi project Sambungan Cepat. Partner Integrator Sistem (SI) utama yang mendukung alur ini
adalah:
- Airoha
- BES
- Qualcomm
- Realtek
Peran dan Tanggung Jawab dalam Ekosistem
Proses integrasi Sambungan Cepat dengan partner mencakup tugas yang tercantum dalam
Gambar 1 dan harus diselesaikan sebelum sertifikasi resmi di Lab
Pihak Ketiga.
OEM bertanggung jawab atas tugas berikut:
Pendaftaran ID Model: Daftarkan perangkat Anda di
Konsol perangkat untuk mendapatkan ID model unik untuk perangkat Anda (project dapat memiliki beberapa ID Model). Hal ini diperlukan untuk meminta pengaktifan
project dalam proposal bisnis sebelum proses integrasi dan pengembangan
untuk Sambungan Cepat. Perangkat Sambungan Cepat (masing-masing dengan ID model unik) harus
dikaitkan dengan satu atau beberapa project Google Cloud. Untuk informasi tambahan, lihat halaman ID Model.
Proposal Bisnis: Anda harus menyelesaikan
pengiriman proposal bisnis untuk memberi tahu tim Pengembangan Bisnis
Google guna mengonfirmasi bahwa kontrak yang diperlukan sudah ada, dan memilih
partner System Integrator (SI) untuk berkolaborasi. Partner SI atau SoC Anda
akan membantu Anda mengirimkan proposal awal pelacak masalah di pelacak masalah
Google untuk mengonfirmasi cakupan project. Untuk informasi tambahan, lihat
bagian proses sertifikasi.
Integrasi Cepat: Bekerja sama dengan partner SI atau SoC Anda dalam pengembangan produk
dan integrasi solusi Sambungan Cepat di firmware Bluetooth (BT). Jika ada
pertanyaan, hubungi partner SI Anda. Untuk informasi selengkapnya, lihat
Panduan teknis Sambungan Cepat.
Pengujian Mandiri: Jalankan dan kirimkan hasil pengujian kalibrasi dan
pengujian integrasi menyeluruh dengan aplikasi Validator. Untuk informasi selengkapnya, lihat
formulir Laporan Pengujian Mandiri BT Classic atau BlueTooth LE Audio, bergantung pada penerapannya. Setelah menyelesaikan
pengujian mandiri, kirimkan Laporan Pengujian Mandiri ke partner SI atau SoC Anda yang akan
mengajukan permohonan persetujuan teknis agar Google dapat mengevaluasi hasil
pengujian mandiri Anda. Lihat proses sertifikasi Sambungan Cepat untuk mengetahui detail
selengkapnya.
Ajukan Permohonan Persetujuan Teknis: Bekerja samalah dengan partner SI atau SoC Anda yang akan
mengirimkan permintaan persetujuan teknis di sistem pelacak masalah Google. Untuk
mengetahui informasi selengkapnya, lihat bagian proses sertifikasi.
Sertifikasi Resmi di Lab Pihak Ketiga: Setelah Google memberi tahu
partner SI atau SoC Anda pada tiket permintaan persetujuan teknis (juga dapat dikenal
sebagai pra-sertifikasi) bahwa project Anda siap untuk memulai proses
sertifikasi, hubungi lab pihak ketiga untuk melanjutkan sertifikasi
resmi. Google dapat meminta Anda untuk mengirimkan sampel ke Google sesuai kebutuhan.
Untuk informasi selengkapnya, lihat halaman
Mengirim Perangkat ke Lab Pihak Ketiga.
Penerimaan Persetujuan Teknis: Anda akan menerima surat Persetujuan Teknis
bersama dengan pengaktifan Sambungan Cepat di konsol Berbagi Langsung.
OTA Pasca Peluncuran: Bekerja sama dengan partner SI atau SoC Anda terkait permintaan update OTA
pasca peluncuran. Untuk informasi selengkapnya, lihat bagian
proses sertifikasi.
Kecuali dinyatakan lain, konten di halaman ini dilisensikan berdasarkan Lisensi Creative Commons Attribution 4.0, sedangkan contoh kode dilisensikan berdasarkan Lisensi Apache 2.0. Untuk mengetahui informasi selengkapnya, lihat Kebijakan Situs Google Developers. Java adalah merek dagang terdaftar dari Oracle dan/atau afiliasinya.
Terakhir diperbarui pada 2025-08-22 UTC.
[null,null,["Terakhir diperbarui pada 2025-08-22 UTC."],[[["\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."]]
