Добавил:
kiopkiopkiop18@yandex.ru t.me/Prokururor I Вовсе не секретарь, но почту проверяю Опубликованный материал нарушает ваши авторские права? Сообщите нам.
Вуз: Предмет: Файл:
Ординатура / Офтальмология / Английские материалы / Assistive Technology for Visually Impaired and Blinde People_Hersh,Jonson_2008.pdf
Скачиваний:
0
Добавлен:
28.03.2026
Размер:
12.16 Mб
Скачать

11.4 Developmental Issues

377

Figure 11.9. The address of the bus’s module detected by the server

11.4.2 Bluetooth Client (Mobile Device)

For the client application, there are five main components:

Initialization of the client device.

Device discovery.

Service discovery.

Connection and notification.

User interface.

11.4.2.1 Initialization of Client

The client (mobile devices) needs to be initialized first. This means that the service address (Serial Port Profile service), provided by the bus stop server, is incorporated in the client application. This is to enable the client to search for the correct Bluetooth server and the correct service to initiate connection.

11.4.2.2 Device Discovery

Once the client device is initialised, it starts to carry out device inquiry for the available Bluetooth devices in the vicinity. For every Bluetooth device found, the corresponding name and Bluetooth address of each device is stored in a hash table in the client application. Once the process of device discovery has completed, the client application moves to the next stage—service discovery. The flowchart of this

378 11 Accessible Bus System: A Bluetooth Application

Figure 11.10. Flowchart of device discovery process of client device

Figure 11.11. Screenshot of bus commuter mobile phone that displays the results of the Device Discovery process

process and the screenshot of the client device are shown in Figures 11.10 and 11.11, respectively.

From the screenshot in Figure 11.11 it can be observe that the client device has detected a total of two Bluetooth devices in the vicinity.

11.4.2.3 Service Discovery

After the device discovery process has completed, the service discovery process begins. All the available Bluetooth devices data are now stored in the hash table. The client application will search for each device data: the Bluetooth address, the type of services and corresponding service address offered by each device.

11.4 Developmental Issues

379

Figure 11.12. Flowchart of service discovery process of client device

If the Bluetooth and service addresses correspond to that of bus stop server, the client device will attempt to initiate a Bluetooth connection with the remote device (which is the bus stop server in this case) as shown in the flowchart of Figure 11.12.

11.4.2.4 Connection and Notification

Once a match between the service address of the remote device and that given by the bus stop server is found, the client device will attempt to initiate a connection to the bus stop server. As soon as the connection is successful, the requested bus number keyed in by the bus commuter will be sent via Bluetooth stream connections to the server (Figure 11.13). The server will acknowledge by sending a “RECEIVED” message back to the client to inform it that it has received the requested bus number. The client then waits for the server to check if the requested bus is approaching the bus stop (Figure 11.14).

Once the requested bus is approaching the bus stop, the server will send an “ARRIVED” notification message to the client via Bluetooth to indicate that the requested bus is arriving. The client will read in the message and will play an audio file to alert the bus commuter that their bus is approaching as depicted in Figure 11.15.

11.4.3 User Interface

An assistive feature of the Bluetooth bus notification system is that it incorporates an audio interface for the client application (in the mobile phone). This is especially

380 11 Accessible Bus System: A Bluetooth Application

Figure 11.13. Screenshot showing that requested bus number is 96

Figure 11.14. Screenshot showing that the bus stop server has received the requested bus number and the client is waiting for the bus

Figure 11.15. Screenshot showing that requested bus number is approaching the bus-stop