透過集合功能整理內容
你可以依據偏好儲存及分類內容。
個人化名稱
在首次配對期間,以及使用者在 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 要求時,供應商應通知額外資料特徵,並提供個人化名稱。
除非另有註明,否則本頁面中的內容是採用創用 CC 姓名標示 4.0 授權,程式碼範例則為阿帕契 2.0 授權。詳情請參閱《Google Developers 網站政策》。Java 是 Oracle 和/或其關聯企業的註冊商標。
上次更新時間:2025-08-13 (世界標準時間)。
[null,null,["上次更新時間: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\")."]]