使用集合让一切井井有条
根据您的偏好保存内容并对其进行分类。
追溯写入帐号密钥
如果 Seek 通过传统方式(例如通过蓝牙设置)而不是通过快速配对入口点执行配对,则不会有帐号密钥写入提供程序。在这种情况下,即使拥有快速配对设备,用户也无法查看或使用任何快速配对功能。为了让用户能够享受快速配对的优势,提供程序应允许 Seek 在配对完成后以静默方式写入帐号密钥。
- 如果提供程序在未通过快速配对流程绑定的情况下绑定,则允许通过基于密钥的配对方法写入新的帐号密钥(最多一分钟)。在此期间,只能接受一个帐号密钥。
- 在 RFCOMM 信道建立后,提供程序应通过消息流将型号 ID 和 BLE 地址发送给搜寻器,发现者将构建 GATT 连接并开始基于密钥的配对过程。
- 如果收到设置了标记 3 的原始请求,提供程序应验证绑定设备的 BR/EDR 地址是否与请求中包含的地址相同。否则,请拒绝请求。
- 由于设备已绑定,BR/EDR 绑定和通行密钥验证(过程中的第 8 - 17 步)会被跳过,探索器会在建立共享密钥后直接将帐号密钥写入提供程序。
如未另行说明,那么本页面中的内容已根据知识共享署名 4.0 许可获得了许可,并且代码示例已根据 Apache 2.0 许可获得了许可。有关详情,请参阅 Google 开发者网站政策。Java 是 Oracle 和/或其关联公司的注册商标。
最后更新时间 (UTC):2023-04-20。
[[["易于理解","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"]],["最后更新时间 (UTC):2023-04-20。"],[[["If 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."],["Providers should allow Seekers to write an account key for up to a minute after traditional pairing using Key-based Pairing."],["This process involves the Provider sending its Model ID and BLE address, the Seeker establishing a GATT connection, and initiating Key-based Pairing."],["For security, the Provider verifies the bonded device's address before accepting the account key write request."],["Since devices are already bonded, the process skips some steps and the Seeker directly writes the account key after a shared secret is established."]]],[]]