The name does not uniquely
identify a Bluetooth device but provides a name of a device that can be
displayed to a user instead of a device??™s Bluetooth address. For example, a
user named Bob may assign his phone the friendly name ??????Bob??™s Cell.??™??™
3.2.3 User Interaction
Certain operations within Bluetooth security may require input from the
user of a device outside the scope of the application. The BCC is responsible
for retrieving this information from the user and injecting the
Bluetooth Control Center 43
information into the Bluetooth security process. What type of information
can the BCC retrieve from the user? It can range from a PIN to
simply responding to a permission request.
3.2.4 BCC on Devices with No User Interface
Because JABWT is based on CLDC, there is no guarantee that a user
interface (UI) is available on the device. In this situation, the OEM or
device manufacturer is expected to set the BCC configuration in the
device. Actions that require user interaction are more complicated.
A BCC on a non??“graphical user interface (GUI) device might not support
these types of actions or can specify the responses to these actions when
the device is manufactured.
3.3 Simple JABWT Application
Before describing the details of the classes and methods de?¬?ned in
JABWT, the traditional ??????Hello, World??™??™ application is shown.
Pages:
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86