Professional Documents
Culture Documents
. INTRODUCTION
Mobile computing represented the
inevitable direction of network development,
which made it true that people used computer
resources according to their wills [1]. Despite
the exponential growth of CPU speed, modern
computers cannot cope with the growing
demand for computational resources that occur
in areas such as bio-informatics [2][3].
Computer models are becoming more refined
and often show an exponential time complexity.
Moreover, the amount of data to be processed is
growing rapidly. At the same time, there is a
huge amount of unused computer power
available on the desks of people, especially after
office hours. The SETI@home project has
demonstrated convincingly the scalability and
feasibility of mobile computing with spare CPU
cycles. At the same time Gnutella, KaZaa and
Morpheus have generated ample interest in
peer-to-peer (P2P) networks and have shown
their utility. Combining these two approaches is
an obvious step. Mobile agents seem the ideal
tools for such unification, because (1) they can
react flexibly on the availability of resources,
1339
Authorized licensed use limited to: Hogskolan Vast. Downloaded on February 2, 2010 at 12:11 from IEEE Xplore. Restrictions apply.
S e rv ic e E n g in e
H u m a n In terfac e
F ailu re M o d u le
N a v ig a tio n M o d u le
S e cu rity M o d u le
C o m m u n ic a tio n M o d u le
S e rv ice E n g in e
A HM Engine
HM Engine is communicating interface
between users and J2ME terminal equipment.
Users use local browser to configure J2ME
terminal equipment, state watching and
harmony controlling by HM Engine, which is
realized by Applet and Servlet technologies.
B MS Engine
MS Engine includes the below six modules:
1) Human Interface
It is used to watch, configure the Mobile
Server interface.
2) Failure Module
It is used to control and watch the terminal
equipment network, deal with network
abnormity, equipment trouble and service
declining and so on.
3) Navigation Module
It is used to assure the relative network
location and realize the connection of
communication.
4) Security Module
It is used to protect host, network resource,
code object and mobile code object.
5) Communication Module
It is used to realize the communication
among terminal equipments.
6) Harmony Module
It is used to harmony the resource among
mobile computing equipments
C Service Engine
Service Engine is the center of mobile
computing platform, which is used to analyze
and find user service. Service Engine adopts
Lookup service mechanism of Jini architecture
to realize searching service, and support
hiberarchy searching.
. A CENTRALIZED DATABASE
ACCESSING TECHNOLOGY BASED ON
MOBILE AGENT
In order to realize centralized database
accessing technology based on Mobile Agent in
mobile computing, mobile terminal equipment
(MH) needs to provide mobile Agent with
database accessing function. Database server
needs to provide running environment of
Mobile Agent and database connection interface
and driver program. But it doesnt need to
provide the support of Mobile Agent to finish
Farther Agent (FA) and Home Agent (HA) of
Mobile IP.
We extend and modify some classes of
IBM Aglets, and realize three components:
Accessing Create Interface (ACI); Accessing
Mobile Agent (AMA) and Accessing Execute
Environment. ACI provides a user interface of
input database accessing request, which
transfers the accessing request to AMA in bite
code, and return the executing result to user.
AMA is used by ACI to execute the database
accessing request of ACI in the remote SQL
database server, accepts results and return to
1340
Authorized licensed use limited to: Hogskolan Vast. Downloaded on February 2, 2010 at 12:11 from IEEE Xplore. Restrictions apply.
Return result
Tahitiz+AEE
HA
Return result
(Block)
FA
Return result
SQLServer
Internet
AMAwith SQLsentence
1341
Authorized licensed use limited to: Hogskolan Vast. Downloaded on February 2, 2010 at 12:11 from IEEE Xplore. Restrictions apply.
B EPM
Events are checked by EPM, EPM is
corresponding to entity Producer. One Producer
is a software module (relative to mobile
environment). In this EAM, it engenders Event
Objects by extending information, which means
when it checks an event, Producer will pack the
relative information into Event Object. This
Event Object will be transferred to one Channel
and transferred to the relative EAM application
system. The Producer and Handler classes are
illustrated in figure 4 as below.
Class Producer{
Channel * channel;
Producer (char * channel);
Void PostEvents (Event *);
.}
Class Handler{
Channel * channel;
Handler (char* channelname);
Void Body();
}
Fig.4. The structural of Producer and Handler classes
C EOM
Though different events are relative to
different information. A kind of information is
public to one or more events. The organization
of Event Object may to be an extend type
arrangement. We define the basic event object,
which is aimed to the given event demands and
function. Each Event Object is the child class of
root class.
The typical events in the mobile computing
application include: Connections Event,
Services Event and so on. The typical
information of Connections Event includes: 1)
network gate ID; 2) connection is UP or DOWN.
The package information of Service Event is the
usable of network service, includes such as
printer, SMTP and NUTP. The common
interface of EOM is showed in figure 5.
Class Event {
Event();
Virtural size_tMarshal (void *, size_t);
Virtural Event * UnMarshal (void * size t);
Virtural void Handle();
}
. EXPERIMENTS
The experiments conducted on WebitAgent
[4] platform and Mobile Server platform. The
running time of a task is showed in table 1.
Tab.1. Time used for two platforms
Number
20,000,000
40,000,000
60,000,000
80,000,000
100,000,000
-0.65
1.46
10.52
21.48
19.96
1342
Authorized licensed use limited to: Hogskolan Vast. Downloaded on February 2, 2010 at 12:11 from IEEE Xplore. Restrictions apply.