Transcript XDWE: A prototype to establish XML as a Native Data Source in

XDWE: A prototype to
establish XML as a Native Data
Source in
Wireless Environment
Md. Ershadul H. Chowdhury
Syed Murtuza Baker
Md. Hassan Mahmud
Sharif-Ul-Alam Razib
Muhammad Suhel Hussain
Manzur Ashraf
1
Main Motive
• To establish XML as a data-source integrated
with an WAP-portal. We have developed a
prototype for that purpose, named ‘Mobile Xportal’.
• Our challenge is to develop a native XML
database, in which XML data is stored directly,
retaining its natural tree structure. At the same
time, we would like to obtain all the benefits of
relational database management
2
Benefits of Native-XML
• Data-semantics
• Internationalization due to the fact that it
utilizes Unicode.
• Human readable format makes it easier for
developers to locate and fix errors than
with previous data storage formats.
• Extendibility (integration) & security.
3
Related Work
• Rufus , Lore and Strudel report the development of
research prototype for XML data-storage.
• LOTUS notes was developed as a commercial product
[98].
These are tailored to store & retrieve XML documents
using special purpose indices and techniques of query
optimization
 on-the-fly stage (not persistent)
TIMBER (2002)Native XML (offline)
we propose XML as a native database in WAP environment
to incorporate this technology in M-commerce
application.
4
Traditional multi-tier Internet
Commerce Application Architecture
5
Dynamic Online Site Architecture
6
Using XML in data-centric model
7
Proposed Mobile X-Portal suite
8
9
Some talk on security
• Mobile X-Portal have the support for a
number of specialized access modes for
browsing and authoring. It provides
traditional user-on-demand mode for
document release, a broadcast mode
based on a combination of digital
signature and encryption techniques. It
supports ‘push’ or ‘pull’ technology to
provide user-specific {authorized} xml files.
10
challenges
• Security processing gap: General mobile
handset requires 3.4 minutes to perform 512-bit
RSA key generation, 7 seconds to perform
digital signature generation, and can perform
(single) DES encryption at only 13 kbps, even if
the CPU is completely dedicated to security
processing.
•
Battery gap :21.5mJ (14_3mJ) to transmit
(receive) a 1024-bit message, while encrypting
the same message using RSA imposes an
additional energy overhead of 42mJ.
11