Tetap teratur dengan koleksi
Simpan dan kategorikan konten berdasarkan preferensi Anda.
Menulis Kunci Akun Secara Retroaktif
Jika Pencari melakukan penyambungan melalui cara tradisional (misalnya, melalui setelan Bluetooth) dan bukan melalui titik entri Sambungan Cepat, tidak akan ada kunci akun yang ditulis ke Penyedia. Dalam hal ini, pengguna tidak akan dapat melihat atau menggunakan fitur Sambungan Cepat apa pun, meskipun memiliki perangkat Sambungan Cepat. Agar pengguna dapat memperoleh manfaat Sambungan Cepat, Penyedia harus mengizinkan Pencari menulis kunci akun secara diam-diam tepat setelah penyambungan terjadi.
- Jika Penyedia terikat tanpa melalui alur Fast Pair, izinkan kunci akun baru ditulis melalui metode Penyandingan Berbasis Kunci hingga satu menit. Hanya terima satu kunci akun untuk ditulis selama waktu ini.
- Setelah saluran RFCOMM dibuat, Penyedia harus mengirimkan ID Model dan alamat BLE ke Pencari melalui Message Stream, Pencari akan membuat koneksi GATT dan memulai prosedur Penyandingan berbasis Kunci.
- Jika Permintaan Mentah dengan bit Flag 3 yang ditetapkan diterima, Penyedia harus memverifikasi bahwa alamat BR/EDR perangkat yang disambungkan sama dengan yang disertakan dalam permintaan. Jika tidak, tolak permintaan.
- Karena perangkat sudah diikat, pengikatan BR/EDR dan verifikasi Kunci Sandi (langkah 8 - 17 dalam prosedur) akan dilewati dan Seeker akan langsung menulis kunci akun ke Provider setelah rahasia bersama dibuat.
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-13 UTC.
[null,null,["Terakhir diperbarui pada 2025-08-13 UTC."],[[["\u003cp\u003eIf a Fast Pair device is paired traditionally (e.g., via Bluetooth settings), it won't have Fast Pair features until an account key is written.\u003c/p\u003e\n"],["\u003cp\u003eProviders should allow Seekers to write an account key for up to a minute after traditional pairing using Key-based Pairing.\u003c/p\u003e\n"],["\u003cp\u003eThis process involves the Provider sending its Model ID and BLE address, the Seeker establishing a GATT connection, and initiating Key-based Pairing.\u003c/p\u003e\n"],["\u003cp\u003eFor security, the Provider verifies the bonded device's address before accepting the account key write request.\u003c/p\u003e\n"],["\u003cp\u003eSince devices are already bonded, the process skips some steps and the Seeker directly writes the account key after a shared secret is established.\u003c/p\u003e\n"]]],[],null,["Retroactively Writing Account Key\n---------------------------------\n\nIf a Seeker performs a pairing through the traditional way (for example, through\nBluetooth settings) instead of through the Fast Pair entrypoint, there will be\nno account key written into the Provider. In this case, the user will not be\nable to see or use any of the Fast Pair features, despite owning a Fast Pair\ndevice. To let users be able to get the benefits of Fast Pair, the Provider\nshall allow the Seeker silently writing account key right after pairing has\noccurred.\n\n1. If the Provider is bonded without going through the Fast Pair flow, allow a new account key to be written through the Key-based Pairing method for up to one minute. Only accept one account key to be written during this time.\n2. After the RFCOMM channel is established, the Provider should send the Model ID and BLE address to the Seeker via [Message Stream](/nearby/fast-pair/specifications/extensions/messagestream#MessageStream \"Message Stream\"), the Seeker will build GATT connection and start [Key-based Pairing procedure](/nearby/fast-pair/specifications/service/gatt#procedure \"GATT Procedure\").\n3. If an [Raw Request](/nearby/fast-pair/specifications/characteristics#table1.2.1 \"Table 1.2.1 Raw Request\") with Flags bit 3 set is received, the Provider should verify the bonded device's BR/EDR address is the same as what is included in the request. If not, reject the request.\n4. Because the devices are already bonded, BR/EDR bonding and Passkey verification (steps 8 - 17 in the [procedure](/nearby/fast-pair/specifications/service/gatt#procedure \"GATT Procedure\")) will be skipped and the Seeker will directly write an [account key](/nearby/fast-pair/specifications/characteristics#AccountKey \"Account Key\") to the Provider after a shared secret is established."]]
