Backup Module

The main purpose of the module is backup text file after parsing text file. User use Text Files Path Module save backup folder to the database. The module gets the backup folder from database and verifies the backup folder. If the module doesn’t find the folder, it creates the folder to save backup file. Figure 17 is the concept of the module. When the module backup file, it appends to pervious save text file and separate by days. In order to distinguish different date and station of the backup file, the module provides a mechanism to save backup file. In this module the backup file name distinguish different station name and date. The backup file name for example, chichi_20100520.txt and chichi_20100521.txt. The backup files show in Figure 18.

Figure 17: the concept of Backup Module

Figure 18: the backup files diagram 4.3.6 Display Real-time Data Module

The main purpose of the module provides interface to display real-time data via browsers. The interface has two parts. One part shows every stations and probes real-time monitor information the figure is depicted in Figure 19. In Figure 19, it divided three blocks. The upper block shows the latest update time. When the Parsing Text Files Module parsing the text files and store to database. The Display Real-time

Data Module get the latest time. The middle block shows real-time monitor data. The website establishes the user sessions as well as provides services to validate users’

authentications, authorizations. Therefore, guest can only see following parameter: 1) Temperature, average temperature TDR waveform measurements, e.g., 21.1 ℃; 2) Suspended Sediment Concentration, e.g.,1000 mg/L; 3) Conductivity, e.g., 319.17 us/cm; user and admin show in Figure x can see more than guest monitor system parameter : 1)Voltage, monitor system battery voltage,e.g.,12v; 2) Temperature, average temperature TDR waveform measurements, e.g., 21.1 ℃; 3) Temperature Standard Deviation, e.g., σ = 0.08 ℃; 4) Suspended Sediment Concentration, e.g.,1000 mg/L; 5) Suspended Sediment Concentration Standard Deviation, e.g., σ = 500 mg/L; 6) Conductivity, e.g., 319.17 us/cm; 7) T2, the electromagnetic waves generate wave change range in TDR Sensing Waveguide, e.g., 7.5 ns. The lower one provides latest update time every five minutes.

Another part provides user select specific station and shows the station all probes real-time monitor information the figure is depicted in Figure 20. In Figure 20, user can initiate select the station and following shows the station real-time information. In Figure 21, it divided three blocks. The upper block shows the latest update time. The middle block shows real-time monitor data as well as previous description. The lower one provides latest update time every five minutes.

In order to obtain real-time data effectively and efficiently, the database establish an automatic mechanism and the concept is indicated in Figure 22. The database create hot table to save every station the latest monitor station data. In Parsing Text Files Module parses the text file and save to database. After the Parsing Text Files Module insert the data to database, the database automate trigger a procedure that is called “Trigger” to save the latest data to hot table. When Display Real-time Data

show the latest data.

Figure 19: the user interface of Display Real-time Data Module

Figure 20: the authentication user display user interface

Figure 21: specific station user interface

Figure 22: the trigger concept of the database table 4.3.7 Monitoring Data Query Module

information. The interface can be separated into two blocks. The function of upper block provides user select query parameter and date, and lower one display the query data.

When user click the “@” button form Display Real-time Data Module the parameter can be delivered direct by the standard HTML GET method, i.e., ASP.NET QueryString scheme to Monitoring Data Query Module. The operation procedure is illustrated in Figure 23. In Figure 23, the diagram divide two parts, one part is setting station parameter, such as: station name, e.g., S7, probe name, e.g., ch1, function name, e.g., SSC, factor name, e.g., Concentration, the start date and the end date.

Another part is show Time and factor value. If user clicks “@” from Display Real-time Data Module the start date and the end date are set today by default. If any dropdown menu didn’t select, the module will alert warning message. After user press the query button, the module query database and output Time and factor value. Next, the module triggers Drawing Line Chart Module drawing line chart, the module will be discussed in next section. When user clicks “@” from Manual Input Data Module, the module will query data from different database table and display different user interface as shown in Figure 24.

Figure 23: the operation procedure of Monitoring Data Query Module from Display Real-time Data Module

Figure 24: the operation procedure of Monitoring Data Query Module from Manual Input Data Module

4.3.8 Drawing Line Chart Module

The main purpose of the module provides user visualize tool to display query history monitor information. After user query the history monitor data form Monitoring Data Query Module, the Monitoring Data Query Module will integrate query data to XML and transmit to Drawing Line Chart Module. Next, the module retrieve the XML data and draw line chart as shown in Figure x. In the figure 25, the diagram divided three parts, the upper part shows the station name, the start time and the end time. The middle part shows the line chart. In the line chart, the x-axis displays time and the y-axis displays the factor values. When user move mouse to every point above the diagram, it shows detail information, the factor name, time and the factor value, for examples, Concentration, 08:00, 3.3. The lower one shows the factor name, such as: Concentration.

Figure 25: the user interface of Drawing Line Chart Module

4.3.9 Monitoring Data Export Module

The main purpose of the module provides user output monitor data to excel. The

module has two kinds of export mode. One is for user export specific factor value, another one is for admin export the file more information. It can export the station every probe, function and factor data. In the user export user use Monitoring Data Query Module select station parameter, start date and end date, and press “export”

button, the module use Monitoring Data Query Module query data and export excel file as indicated in Figure 26. The export file format has two parameters: 1) Time, e.g., 2010/5/29 12:00; 2) user select factor parameter, e.g., Concentration, 1.9 mg/L. The admin export user only need select station name parameter, other dropdown menus are not necessary to be selected. Later, user select start date and end date, the module provides more dynamic export monitoring system data. The export excel file is depicted in Figure 27. In Figure 27, user can export more information such as, every probe, function and factor values.

Figure 26: the user export user interface

Figure 27: the admin export user interface

4.3.10 Manual Input Data Module

The main purpose of the module provides user input monitor data by manual.

There are two parts of the modules; one provide user manual input user interface;

another is display user input.

When user wants to manual input monitor data as shown in figure x, they need first authentication. After user authentication, user can select station location. Then, user can setting monitor date and time, user press “select” it will pop out AJAX (Asynchronous JavaScript and XML) calendar. When user selects a date, the calendar will automate close and setting the date without refresh the page. Next, user can select time and input concentration or flow. If user only input concentration or flow, the module allows user input only one value and press “Summit”. After the module inserts user input data to database, the database automate trigger a procedure to save the latest data to hot table. When the module displays user input as shown in Figure 28, the module will select the hot table to display the latest data. The concept is depicted in Figure 29.

Figure 28: the operation procedure of Manual Input Data Module

Figure 29: the concept of Manual Input Data Module

4.3.11 Remote Control Monitor System Module

The main purpose of the module provides user remote control monitoring system.

There are two approaches to measure and collect monitor data, i.e., interactively or automatically. In this section we discuss SSC parameter, the other parameter is the same as SSC parameter. The interactive one, as indicated in Figure 30.a, initially we need to either setup temperature parameters manually or obtain the values from DAQ automatically. The temperature values will be utilized while measuring SSC and TDR waveforms calibration. After enter additional parameters in the diagram, as illustrated in section 4.2.7.1, the waveforms can be obtained via the TDR device. Later, the Embedded System calculates and transforms the waveforms into SSC displayed in the diagram. Similarly, the automate interface is depicted in Figure 30.b. Users can initiate the TDR server application remotely by selecting “Open Station Setting” and following the instructions as indicated at the top of the diagram. After entering acquisition, processing, threshold, as well as scheduling parameters, the SSC outputs can be generated in an ASCII formatted text file as described in Figure x.

The sequence diagram of the scenario is clearly depicted in Figure 30.c. In the diagram, at beginning, the TDR and probe acquisition parameters entered at console via Embedded System. The scheduling, threshold and backup settings are inputted as well. After configured the TDR device, the device acquires the probe to collect data according to the scheduling. If any threshold reaches, the SMS (Short Message Service) will be generated and delivered the alerts to a cell phone by GPRS. The Embedded System retrieves and transforms TDR waveform outputs into ASCII formatted data and delivers them to Clients by Internet.

Figure 30.a SSC scenarios interactive approach

Figure 30.b SSC scenarios automatic approach

Figure 30.c SSC scenarios sequence diagram

Chapter 5 Conclusions and Future Work

The Data Center integrates every location monitor system and it separates web-base user interface and windows-base retrieve text file user interface. Therefore, the supervisor can adjust monitor systems setting and it can not affect user interface.

In particular, the system provides user easy way to observe real-time data, draw line chart, and export history monitor data. If field doesn’t have automated monitoring system, the Data Center also provides manual input to insert data by manual. When engineers setting monitor system, user only use windows-base retrieve text file user interface setting destination path and backup path. The system can auto retrieve text file and backup text file. The web-base user interface can update real-time data regularly. The database schema considers more flexible when the monitor system function expand. Overall we establish the Data Center provides quick, easy start up, no IT involvement, and no hardware and software to install. We believe this study could serve as a basis for further integrate embedded systems and data centers.

This work needs more user provides many opinion to improve Data Center. No matter the user interface or the retrieve text file user interface. It can help the system more user friendly and easy to use.

Reference

[1] A. Turner, Tcpreplay, http://tcpreplay.synfin.net/trac/.

[2] W. Feng, A. Goel, A. Bezzaz, W. Feng, J. Walpole, "TCPivo: A High-Performance Packet Replay Engine,” ACM SIGCOMM 2003 Workshop on Models, Methods, and Tools for Reproducible Network Research (MoMeTools), August 2003.

[3] Tomahawk, http://www.tomahawktesttool.org/, 2005.

[4] G. H. Hong and S. F. Wu., “On interactive internet traffic replay,” in 8th Symposium on Recent Advanced Intrusion Detection (RAID), LNCS, Seattle, September 2005.

[5] Y.-C. Cheng, U. Holzle, N. Cardwell, S. Savage, and G. Voelker, “Monkey see, monkey do: A tool for tcp tracing and replaying,” In Proceedings of the 2004 USENIX Annual Technical Conference, June 2004.

[6] A. Turner, “Flowreplay design notes,” http://synfin.net/papers/flowreplay.pdf.

[7] Weidong Cui, Vern Paxson, Nick C. Weaver, and Randy H. Katz.,

“Protocol-Independent Adaptive Replay of Application Dialog,” in Proceedings of the 13th Annual Network and Distributed System Security Symposium (NDSS), Feb 2006.

[8] James Newsome, David Brumley, Jason Franklin, and Dawn Song, “Replayer:

Automatic Protocol Replay by Binary Analysis,” ACM Conference on Computer and Communications Security, October 2006.

[9] F. Schneider, J. Wallerich, A Feldmann, “Packet Capture in 10-Gigabit Ethernet Environments Using Contemporary Commodity Hardware,” Passive and Active Measurement Conference , April 2007.

[10] S. Kornexl, V. Paxson, H. Dreger, A. Feldmann and R. Sommer, “Building a Time Machine for Efficient Recording and Retrieval of High-Volume Network Traffic,” in Proceedings of ACM Internet Measurement Conference, October 2005.

[11] G. Maier, R. Sommer, H. Dreger, A. Feldmann, V. Paxson and F. Schneider,

“Enriching Network Security Analysis with Time Travel,” in Proceedings of ACM SIGCOMM, August 2008.

[12] T. Karagiannis, A. Broido, M. Faloutsos, and K. Claffy, “Transport Layer Identification of P2P Traffic”, In Proceedings of the 4th ACM SIGCOMM conference on internet measurement 2004.

[13] L. Bernaille, R. Teixeira, I. Akodjenou, A. Soule, K. Salamatian, “Traffic

Classification On The Fly”, ACM SIGCOMM Computer Communication Review 2006.