Personalized Name
The Seeker can write a personalized name to the Provider during the first pairing and when the user edits the name on the Seeker side. The Provider shall allocate space, at least 64 bytes, to store the personalized name.
Writes to Additional Data characteristic with personalized name may happen in 2 flows:
- After initial pairing, the Seeker may write a personalized name to the Provider after writing the account key.
- After a user modifies the personalized name on the Seeker, the Seeker will
write the new name to the Provider:
- handshake from step 1 to step 4 in the above 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:
- Set Message type to 0x10
- Set Flag Bit 1 to 1 to indicate it will be followed by Data characteristic.
- Set Data ID of Table 1.2.2 to 0x01 as personalized name.
- write the name to Data characteristic
FE2C1237-8366-4814-8EB0-01DE32100BEA.
- handshake from step 1 to step 4 in the above 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:
The Provider should notify to Additional Data characteristic with personalized name when it is requested via Bit 2 in Table 1.2.1.