28.10.2014 Views

IEDC-2010 Conference Proceedings (Download ... - NED University

IEDC-2010 Conference Proceedings (Download ... - NED University

IEDC-2010 Conference Proceedings (Download ... - NED University

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Distributed Data Collection System (DDCS) followed by Section four on setting up for evaluating DDCS.<br />

Conclusions and future work are described in the section five of this paper.<br />

2. Data Transmission Scheme<br />

GPRS being an ETSI (European Telecommunications Standard Institute) standard for data transmission<br />

uses GSM (Global System for Mobile Communications) network (Chen et al., 2002) and provides an<br />

―always-on‖ connection, where the resources are consumed only when the data packets are actually<br />

transmitted (Brasche, and Walke, 1997). To a globally distributed traffic company, employing this<br />

technology as their data transmission scheme is useful as it provides all time connectivity while the only<br />

charges incurred are when the data is transmitted or received with a minimal on-line charge (McKitterick<br />

and Dowling, 2003). It becomes very expensive to utilise a data scheme which charges based on time<br />

connectivity (e.g. GSM) rather than amount of data transmitted or received.<br />

Some of the advantages identified from the literature of GPRS scheme includes; improved utilization of<br />

radio resources, offering volume-based billing, higher data transfer rates, shorter access times, and<br />

simplification of the access to the packet data networks (Brasche, and Walke, 1997, Bettstetter et al.,<br />

1999). These led to the selection of GPRS data scheme for transmitting vehicle traffic data packets from<br />

multiple remote sites to in-stations.r.<br />

3. Software Architecture<br />

DDCS is an integrated Software for collecting, formatting, sorting and then storing the vehicle traffic data<br />

from multiple remote sites. It can either exist as a complete Software toolset in a single in-station<br />

collecting data from single/multiple site(s), or a distributed Software toolset installed at various instations<br />

(globally) collecting data from single/multiple site(s). DDCS has been designed using the Unified<br />

Modelling Language (UML) (Booch et al., 1999) to specify the requirements capture and the architecture<br />

of the system. It has been developed to execute on a Microsoft Windows .NET platform as a set of<br />

business objects that communicate with each other using the Web services technology (Schall et al.,<br />

2006).<br />

UML is a graphical language for visualising, specifying, constructing and documenting the artefacts of a<br />

Software-intensive system (Booch et al., 1999). In this study, it allowed to cover the conceptual things<br />

such as business processes and system functions. Furthermore, it also provided the coverage of concrete<br />

things, such as classes written in a specific object-oriented programming environment (.NET framework),<br />

database schemas and reusable Software components. DDCS architecture is such that, it supports the<br />

system being suitably distributed across a network where required for data collection. The gathered<br />

vehicle data within the DDCS can be further broadcasted to other locations (example PDA, Mobile<br />

Phones) via internet based technologies such as web services (Schall et al., 2006). Web services can also<br />

be used to analyse and monitor vehicle data collected by DDCS from globally distributed multiple servers<br />

(Casati et al., 2003).<br />

DDCS is constructed from a container Multi Document Interface (MDI) shell environment using the<br />

.NET Asynchronous Socket technology for effective handling of multiple connections from multiple sites<br />

all at once, all within one process / thread. As shown in fig1, DDCS scales very well as it allows<br />

thousands of concurrent connections i.e. only thousands of nonblocking socket objects (Welsh et al.,<br />

2001) are used, and not thousands of threads / processes. When a new site makes a GPRS connection to<br />

an in-station, the DDCS Server (within that in-station) raises a socket event (i.e. worker socket) from the<br />

thread pool. The responsibility is transferred to the worker socket which in turn has to make sure that the<br />

data gets collected, formatted, sorted and then stored in a particular user-described location. Once all or<br />

some of the vehicle data from a site (for example Site 1) is collected, an appropriate location is<br />

automatically selected by DDCS to store all the data from the Site 1. Under no circumstances, is the data<br />

<strong>Proceedings</strong> of <strong>IEDC</strong> <strong>2010</strong>, 1-3 July, <strong>2010</strong><br />

390<br />

<strong>IEDC</strong>-4352-113

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!