Jin Hyung Park
04/07/2012

In this week, I finished implementing the UDP Incoming test module and
the DNS Query module for the mobile DYSWIS. I ported the desktop DYSWIS
codes.

Porting the DNS Query module was not hard. After porting, I unified
modules that I implemented. There were some problems during unifying the
modules, but I resolved all. Now, our Mobile DYSWIS has 3 modules: TCP
Incoming Test Module, UDP Incoming Test Module, and DNS Query Module.

For the final module, I'm going to implement the Android Push
Notification Test Module. This is because, many people guess their
mobile phone has problems when it cannot receive the push notification,
so this module will be helpful for people to find the problems.

Last week, I discussed Kyung Hwa Kim what problem we can detect with our
Mobile DYSWIS. The problem detection flow is like this:

0. [START] Mobile DYSWIS connects to the desktop DYSWIS via Bluetooth.

1. Mobile DYSWIS asks the desktop DYSWIS to send the push notification.

1-a. If the mobile DYSWIS receives the push notification, another
application provider has a problem. Network and Google Service platform
are fine. [END]

1-b. If the mobile DYSWIS does not receive the push notification, Go to
2.

2. The mobile DYSWIS asks the desktop DYSWIS to check the TCP Incoming
connection. In this stage, the desktop DYSWIS may ask the other desktop
DYSWIS, which is on the p2p, to connect the mobile DYSWIS. By doing
this, we can make it sure that the mobile DYSWIS can accept the incoming
TCP connection.

2-a. If the TCP incoming connection is fine, Google Service platform may
have problems. [END]

2-b. If the TCP incoming connection does not work, Go to 3.

3. The mobile DYSWIS tries to test out-going connections, or send DNS
queries.

3-a. If the results are fine, the incoming connection is blocked by some
reasons. [END]

3-b. If the mobile DYSWIS cannot get the results, Go to 4.

4. The mobile DYSWIS cannot do anything now, so the mobile DYSWIS asks
the desktop DYSWIS to check the current local network via Bluetooth.
After that, reports the result to the user. [END]

Could you give me some advice? Will this scenario be enough for the
mobile DYSWIS?

Additionally, in the next 3 weeks, I'm going to finish implementing the
push notification test modules (one for the mobile DYSWIS, and, I also
need to write the library for the desktop DYSWIS to send the
notification), test this scenario, and write the final reports with the
HOWTO document for writing the mobile DYSWIS module.

I also attached the DNS Query Module screen shots. (Host: text field for
the host name, Serv: text field for the DNS server name field. These
input fields are just for testing the module.)