**2.2.5 Smart phone**

Any smart phone which operating system is Windows Mobile 6.1 is suitable for the presented system. The smart phone used in this system is ASUS P552W with built-in GPS. It supports HSDPA 3.6Mbps/EDGE/GPRS/GSM 900/1800/1900. Fig. 10 shows the picture of this smart phone.

Fig. 10. ASUS P552W smart phone

A Mobile-Phone-Based Health Management System 29

Fig. 11. Flowchart of MHMS under normal situation

pressed.

Fig. 12 shows the interactions among the smart phone, RFID reader, and ring Tag for those commands used on smart phone. For instance, the SearchTag command instructs the RFID reader (action 1) to search for available ring Tag (action 2), and the available ring Tag responds Tag ID back to the reader (action 3) and the reader sends the received Tag ID to the smart phone(action 4). Fig. 13 depicts the flow chart of sending SMS text message to the emergency contact's phone under emergency situation when the SOS button on the Tag is

#### **2.3 Software**

The GUI programs developed on the smart phone and on the remote medical station were coded in Visual C#. Microsoft .Net compact framework 3.5 was installed on the smart phone for running the client APs, and Windows Mobile 6 SDK, smart phone emulator, and Cellular Emulator were installed on the PC for developing the client APs.

Several GUIs were developed to communicate with the RFID reader/tag and then were packaged into a DLL file for ARM-based embedded systems (smart phones). The reason of using DLL file is for the security reason so that the physical data format can be hidden in the DLL file. Table 1 shows the commands developed for the APs. The shaded area in Fig. 11 illustrates the flow chart of the AP on the smart phone. After the hardware devices are set up properly, the user is ready to run the developed AP by starting the setup procedures: 1. Open Bluetooth ComPort, 2. Execute ReaderReset command to initialize the RFID reader, 3. Execute ReaderQuery command to search for available RFID Reader, 4. Execute AllReset command, 5. Execute SearchTag command to search for available ring tag. Then, the user can start receiving data from the ring tag to the smart phone by executing the Access command. The GPS data can also be received to the smart phone by executing the "Open" command. These collected data on the smart phone can be transmitted to the remote server through 3.5G Internet communication by performing the following procedures: 1. Check connection manager, 2. Check available network , 3. Establish Internet connection, and 4. Send out data using Socket class.


Table 1. Commands for APs

The GUI programs developed on the smart phone and on the remote medical station were coded in Visual C#. Microsoft .Net compact framework 3.5 was installed on the smart phone for running the client APs, and Windows Mobile 6 SDK, smart phone emulator, and Cellular

Several GUIs were developed to communicate with the RFID reader/tag and then were packaged into a DLL file for ARM-based embedded systems (smart phones). The reason of using DLL file is for the security reason so that the physical data format can be hidden in the DLL file. Table 1 shows the commands developed for the APs. The shaded area in Fig. 11 illustrates the flow chart of the AP on the smart phone. After the hardware devices are set up properly, the user is ready to run the developed AP by starting the setup procedures: 1. Open Bluetooth ComPort, 2. Execute ReaderReset command to initialize the RFID reader, 3. Execute ReaderQuery command to search for available RFID Reader, 4. Execute AllReset command, 5. Execute SearchTag command to search for available ring tag. Then, the user can start receiving data from the ring tag to the smart phone by executing the Access command. The GPS data can also be received to the smart phone by executing the "Open" command. These collected data on the smart phone can be transmitted to the remote server through 3.5G Internet communication by performing the following procedures: 1. Check connection manager, 2. Check available network , 3. Establish Internet connection, and 4.

**(for Reader) Descriptor**

ReaderQuery Search for all available RFID Readers

SearchTag Search for all available ring Tags。

StopAccess Stop reading back data from ring Tag

**(for Reader and Tag) Descriptor**

AllReset Reset both RFID Reader and ring Tag

**(for GPS) Descriptor**

**(for SMS) Descriptor**

Access Read back data from ring Tag

**(for Tag) Descriptor**

ReaderReset Reset RFID Reader

Open Open GPS receiver

SendSMS Send SMS text message

Emulator were installed on the PC for developing the client APs.

**2.3 Software** 

Send out data using Socket class.

**Command** 

**Command** 

**Command** 

**Command** 

**Command** 

Table 1. Commands for APs

Fig. 11. Flowchart of MHMS under normal situation

Fig. 12 shows the interactions among the smart phone, RFID reader, and ring Tag for those commands used on smart phone. For instance, the SearchTag command instructs the RFID reader (action 1) to search for available ring Tag (action 2), and the available ring Tag responds Tag ID back to the reader (action 3) and the reader sends the received Tag ID to the smart phone(action 4). Fig. 13 depicts the flow chart of sending SMS text message to the emergency contact's phone under emergency situation when the SOS button on the Tag is pressed.

A Mobile-Phone-Based Health Management System 31

The hardware is implemented as Fig. 6. The Bluetooth adaptor is connected to the RFID reader and the ring Tag is worn on the user's finger. The setup steps for communication between the smart phone and the RFID reader/Tag can be executed either on the smart phone emulator (on PC) or on the smart phone using the Cellular Emulator. Fig. 14

1 2

3 4

Fig. 14. Setup steps for communication between the smart phone and RFID reader/tag

**3. Physiological data presentation** 

illustrates these steps on the smart phone emulator.

Fig. 12. Interactions among smart phone, Reader, and Tag

Fig. 13. Flow chart of sending SMS text message under emergency situation
