Documente Academic
Documente Profesional
Documente Cultură
Authorized licensed use limited to: Chaitanya Bharathi Institute of Technology. Downloaded on November 24, 2009 at 00:24 from IEEE Xplore. Restrictions apply.
uses DB4O[6] as database engine. DB4O is a pure object- and equally. Mobile nodes are divided into two roles: pub-
oriented embedded database and also open-source software. lisher and subscriber, as shown in Figure 2, a cluster header
OODS adopts Publication/Subscription mode[8], it treats is often chosen as publisher while cluster members as sub-
everything as an object. Publishing schema is defined as scribers, because cluster header usually has more powerful
a Class and can be inherited by new publishing schema. CPU, energy and storage resource. A publisher can also be
This paper is organized as follows. Section 2 describes a subscriber in upper cluster networks, only if it is a cluster
the OODS schema. Section 3 presents our implementation member in the upper cluster.
and experimental results of OODS, respectively. Section 4 In OODS, everything is an object, including our applica-
summarizes this paper and outlines our future work. Finally, tions, data records and publications. Data and Publications
section 5 gives an acknowledgement. are both stored in the publishers’ local database, so that,
publication object and data have a uniform access and man-
agement interface. To simplify publishing management,
each publication can have many subscribers. These sub-
scribers make a group to share one publication object. This
is also accord with the real application scenario in which a
few mobile nodes usually have the same business logic or
computing work. A publication has the definition of pub-
lishing strategies for a subscriber group while each sub-
scriber in the group can has its own data filters to reduce
database file’s size.
Figure 3 illustrates the architecture of OODS. It is de-
signed with two parts: publisher and subscriber, they com-
Figure 1. Classical architecture of MDB municate over WiFi, Bluetooth, or other wireless ad-hoc
network protocols which support TCP link.
Mobile applications must be scalable and easy-updated On the publisher, mobile application can access pub-
to catch up with changefully business logic. Publi- lisher database directly or as a subscriber through the
cation/Subscription framework satisfies this requirement Publisher-Agent. The core part is Pub-Update module
well[8]. When the business logic has changed, only pub- which is in charge of publishing schema managing, conflict
lishing schema has to be changed instead of redeploy- resolving and subscriber group managing. Publisher must
ing updated application copies on a number of mobile authenticate each subscriber, so an access control list is
nodes, each subscriber can synchronize hotspot data ac- maintained by Subscriber Group Manager object which also
cording to new publishing schema. So, we employ Publica- cooperates with Schema Manager to authenticate coming-in
tion/Subscription mode in OODS. In a MANET, each mo- subscribers. When many subscribers update the same data
bile node maintains a local DB4O database independently object, conflicts will occur, Schema Manager object mes-
134
Authorized licensed use limited to: Chaitanya Bharathi Institute of Technology. Downloaded on November 24, 2009 at 00:24 from IEEE Xplore. Restrictions apply.
sages to Conflict Resolver object which resolves the con- ferent synchronizing strategies have to be satisfied.
flicts according to predefined strategies. Schema Manager
defines and maintains every publishing schema with the
help of Subscriber Group Manager and Conflict Resolver,
it also communicates with Publisher-Agent for publishing
data objects to subscribers.
On the subscribers, mobile applications access their lo-
cal database when they are off line. Once they go back to
the network or up to date data are required, data synchro-
nization starts. Subscriber-Agent first sends a subscribe re-
quest to the Publisher-Agent. Then the publisher responses
subscribers with their publishing schema instead of dataset,
which unlike other synchronizing technologies such as MR
that sends data directly to the subscribers. This design strat-
egy eases the burden on publishers, because their limited
hardware resources and they may have to deal with many
Figure 4. Class diagrams of PubSchema & Subscriber
synchronizing jobs at the same time. OODS puts part of
the synchronizing works onto the subscribers. When the
subscribers receives publishing schema which is an object,
Publishing schema management is the core part of pub-
they compare with the old schema to find changes. If the
lishing process. It affects application’s efficiency and deter-
schema has changed, Subscriber-Agent will request a snap-
mines what dataset will be published. Figure 5 illustrates
shot dataset according to the new schema, otherwise, only
the activity diagram of schema management.
an increment-update dataset will be requested. When the
required data objects arrived, Data Filter only saves inter-
ested data according to use-defined strategies to reduce the
database file’s size.
135
Authorized licensed use limited to: Chaitanya Bharathi Institute of Technology. Downloaded on November 24, 2009 at 00:24 from IEEE Xplore. Restrictions apply.
2.3. Synchronization process
136
Authorized licensed use limited to: Chaitanya Bharathi Institute of Technology. Downloaded on November 24, 2009 at 00:24 from IEEE Xplore. Restrictions apply.
table Stu Cous to create the multiple-to-multiple relation.
In both two Tables, we assume that each student has ten
courses in his schedule and the number ’n’ has integer value
from 1 to 5 for evaluating OODS’s performance with differ-
ent synchronizing data quantity.
137
Authorized licensed use limited to: Chaitanya Bharathi Institute of Technology. Downloaded on November 24, 2009 at 00:24 from IEEE Xplore. Restrictions apply.
[5] Y. Min and Q. Xiong. Study of synchronization technology
in mobile database. Journal of Wuhan University of Tech-
nology, 32:156–159, 2 2008.
[6] J. Paterson and S. Edlich. The Definitive Guide to db4o.
Apress, 2006.
[7] B. Tavli and W. Heinzelman. Mobile Ad Hoc Net-
works: Energy-Efficient Real-Time Data Communications.
Springer, 06 2006.
[8] A. Wigley and D. Moth. Microsoft Mobile Development
Handbook. Microsoft Press, Redmond, Washington, 2007.
[9] J. Xu. Object-oriented Database System and Application.
Science Press, Beijing, 2003.
[10] W. G. Yee and O. Frieder. Scalable synchronization of in-
termittently connected database clients. MDM 2005 05 Ayia
Napa Cyprus, ACM 1-59593-041-8/05/05.
Figure 9. Download-sync response time [11] A. Yeung and P. Stephenson. Oracle9i Mobile. McGraw-
Hill, 2002.
[12] X. Zhang and X. Meng. Kingbase lite: A smart mobile em-
bedded database system. IEEE, 0-7695-0589-2/00, 2000.
5. Acknowledgement
References
138
Authorized licensed use limited to: Chaitanya Bharathi Institute of Technology. Downloaded on November 24, 2009 at 00:24 from IEEE Xplore. Restrictions apply.