使用集合让一切井井有条
根据您的偏好保存内容并对其进行分类。
个性化名称
在首次配对期间以及用户在 Seeker 端修改名称时,Seeker 可以向 Provider 写入个性化名称。提供方应分配至少 64 字节的空间来存储个性化名称。
在以下 2 个流程中,可能会向具有个性化名称的附加数据特征写入数据:
- 初始配对后,在写入账号密钥后,Seeker 可能会向 Provider 写入个性化名称。
- 用户在 Seeker 上修改个性化名称后,Seeker 会将新名称写入 Provider:
- 上述流程中的第 1 步到第 4 步的握手,以相互识别并了解将使用哪个账号密钥来加密和解密名称。在表 1.2.2 中:
- 将消息类型设置为 0x10
- 将标志位 1 设置为 1,以表明后面将跟有数据特征。
- 将表 1.2.2 的数据 ID 设置为 0x01 作为个性化名称。
- 将名称写入数据特征
FE2C1237-8366-4814-8EB0-01DE32100BEA
。
当通过表 1.2.1 中的位 2 请求时,提供方应通过个性化名称通知附加数据特征。
如未另行说明,那么本页面中的内容已根据知识共享署名 4.0 许可获得了许可,并且代码示例已根据 Apache 2.0 许可获得了许可。有关详情,请参阅 Google 开发者网站政策。Java 是 Oracle 和/或其关联公司的注册商标。
最后更新时间 (UTC):2025-08-13。
[null,null,["最后更新时间 (UTC):2025-08-13。"],[[["\u003cp\u003eSeekers can personalize the name of their Provider device during initial pairing and anytime after.\u003c/p\u003e\n"],["\u003cp\u003eThe Provider device securely stores the personalized name, allocating at least 64 bytes for it.\u003c/p\u003e\n"],["\u003cp\u003eName updates are communicated via the Additional Data characteristic following a secure handshake process.\u003c/p\u003e\n"],["\u003cp\u003eProviders can be prompted to share the personalized name using a specific flag in the data exchange.\u003c/p\u003e\n"]]],[],null,["Personalized Name\n-----------------\n\nThe Seeker can write a personalized name to the Provider during the first\npairing and when the user edits the name on the Seeker side. The Provider shall\nallocate space, at least 64 bytes, to store the personalized name.\n\nWrites to [Additional Data characteristic](/nearby/fast-pair/specifications/characteristics#AdditionalData \"Characteristic: Addiitonal Data\") with personalized\nname may happen in 2 flows:\n\n1. After initial pairing, the Seeker may write a personalized name to the Provider after writing the account key.\n2. After a user modifies the personalized name on the Seeker, the Seeker will write the new name to the Provider:\n 1. handshake from step 1 to step 4 in the above [procedure](/nearby/fast-pair/specifications/service/gatt#procedure \"GATT Procedure\") to identify each other and know which account key will be used for the encryption and decryption of the name. In [Table 1.2.2](/nearby/fast-pair/specifications/characteristics#table1.2.2 \"Table 1.2.2\"):\n 1. Set Message type to 0x10\n 2. Set Flag Bit 1 to 1 to indicate it will be followed by Data characteristic.\n 3. Set Data ID of [Table 1.2.2](/nearby/fast-pair/specifications/characteristics#table1.2.2 \"Table 1.2.2\") to 0x01 as personalized name.\n 2. write the name to Data characteristic `FE2C1237-8366-4814-8EB0-01DE32100BEA`.\n\nThe Provider should notify to [Additional Data characteristic](/nearby/fast-pair/specifications/characteristics#AdditionalData \"Characteristic: Addiitonal Data\")\nwith personalized name when it is requested via Bit 2 in\n[Table 1.2.1](/nearby/fast-pair/specifications/characteristics#table1.2.1 \"Table 1.2.1\")."]]