Table of Contents
Advertisement
BLUETOOTH DEVICE IDENTITY
Every Bluetooth device has a unique Bluetooth Device Address (BDA) assigned to it during the
manufacturing process. This address cannot be changed.
The BDA is usually displayed in hexadecimal format; 00:D0:B7:03:2E:9F is a valid BDA.
Each Bluetooth device also has a configurable, user-friendly name to help distinguish it from other
devices.
The user-friendly name may be up to 99 alphanumeric characters in length and may contain
spaces. My Personal Computer is a valid user-friendly name.
ENCRYPTION
Encrypting data translates it into an unreadable format using a secret key or password. Decrypt-
ing the data requires the same key or password that was used to encrypt it.
LINK KEY
A link key is a unique, internally generated access code based on a passkey, the Bluetooth
Device Address, and an internally generated random number. Link keys are generated auto-
matically when devices are paired.
After a link key is generated, manual entry of the passkey is not required.
PAIRING DEVICES
Pairing allows you to avoid manually entering access information each time a connection is
attempted. Paired devices share a unique link key, which they automatically exchange each
time they connect.
Paired devices attempt to determine the feasibility of an operation before actually executing that
operation.
In the following example of a feasibility check, Authorization, which requires the receiving device
to approve the connection (even though the devices are paired), is enabled.
1. A file is selected and sent to a paired remote service.
2. Before actually sending the file, the sending device transparently queries the server.
3. The server transparently replies that it has a file of that name in the folder to which the
sender is attempting to write.
4. The sending device displays a Confirm File Replace window, which the user must acknowl-
edge before the connection can proceed.
5. The server displays an Authorization balloon over the notification area, which is located at
the far right of the taskbar.
The server user must acknowledge the Authorization balloon or the connection will fail and the
file will not be transferred.
If there are no duplicate files, the Authorization balloon is displayed on the server immediately.
44
Advertisement
Table of Contents
