ADMT PRESENTATION

BY
Girish Salunke -117
Anjali Save -118
Amruta Sajnani-116
Thackur Sahijwaala-11x
 What is a Mobile Database?

 It is either a stationary database that can be connected to
mobile computing devices such as smart phones or PDAs
over mobile network, or a database which is actually
carried by the mobile device. This could be a list of contacts,
price information, distance travelled, or any other
information.
 A mobile database can be connected to a mobile computing
device over a mobile network. The client and server have
wireless connections.
 A cache is maintained to hold frequent data and
transactions so that they are not lost due to connection
failure.
 What is a Mobile Database?

Mobile databases:
 Physically separate from the central database
server.
 Reside on mobile devices.
 Capable of communicating with a central
database server or other mobile clients from
remote sites.
 Handle local queries without connectivity.
 Why Mobile Databases?

 Mobile devices are gradually becoming commonplace. The
computational and networking power of mobile devices is
constantly increasing and new technologies are integrated
into them to support new functionalities and services. On
the other hand, the field of data management is also
expanding with new services and applications
 With these new developments the business data of an
enterprise can be made available to an even larger number
of users and a wider range of applications than before.
 To work on business data anytime and anywhere is the
major goal pursued by developing mobility support in
database context. Confidentiality of data must be ensured,
even though most mobile devices do not provide a secure
environment for storage of such data.
 Why Mobile Databases?

 Mobile data-driven applications enable us to access any
data from anywhere, anytime.
Examples:
 Salespersons can update sales records on the move.
 Reporters can update news database anytime.
 Doctors can retrieve patient’s medical history from
anywhere.
 Mobile DBMSs are needed to support these applications
data processing capabilities.
 Motivation

 In a mobile database application a part or a replica of the
database is locally installed on the mobile device.
 This is a significant difference compared to a conventional
client-server application where all data is centrally stored in a
database server.
 The approach with a mobile database provides the necessary
autonomy to the mobile device to work independently from the
central database.
 The client application can work with the mobile database
asynchronously, and needs to connect to the central database
only when it is necessary to synchronize.
 Advantages

 Flexibility and Reliability: Asynchronous operation makes the
application more flexible and tolerant to network failures.
 – Efficiency: Except the synchronization steps, for all other
operations the client has immediate access to the data since it is
locally stored on the mobile device.
 – Enhanced security: Disconnected computing reduces the total
time that the mobile device is exposed to potential attacks over
the network.
 – Energy efficiency: The mobile device has to operate its
network system, hardware and software, only during the
synchronization operations.
 – Reduced fees for network usage: This holds in the case where
the usage of the communication link is charged. If the network
link up-time is charged.
 Concepts and the Mobile
Platform

 We define a mobile
database as a small-
footprint database that
is installed on a mobile
device.
 Most commonly the
local database is a
replica of a part of a
central database that is
installed at a server
computer.
Client-Server Mobile Database

 Client-Server Mobile Database

Client-server model is the traditional model
of information systems.
It is the dominant model for existing mobile
databases.
The server can become a single point of
failure and performance bottleneck.
Even storing data on a cluster of machines to
backup central database might cause
performance bottleneck and data
inconsistency.
Peer-to-Peer Mobile Database.

 Peer-to-Peer Mobile Database

 In P2P mobile databases, the database
maintenance activities are distributed among
clients.
 Every process plays part of the role of the server,
besides its client role.
 A client that wants to access a piece of data,
sends a request to other peer clients and they
forward the request until the data is found.
 The major problem in this model is ensuring the
availability of data.
 Requirements of Mobile Database

Mobile DBMSs should satisfy the following
requirements :
Small memory footprint.
Flash-optimized storage system.
Data synchronization.
Security.
Low power consumption.
Self-management.
Embeddable in applications.
 Data Synchronization

 Portable devices cannot stay
connected all the time.
 Users can access and
manipulate data on their
devices.
 They are also unable to store
a large amount of data due
to lack of storage capacity.
 Mobile DBMSs should have
the synchronize
functionality to integrate
different versions of data
into a consistent version.
 Data Security

 Security is very important for data-
centric mobile applications.
 It is more important when the
application works with critical data
that its disclosure results in potential
loss or damage.
 Data that are transmitted over a
wireless network are more prone to
security issues.
 Mobile DBMSs should implement a
complete end-to-end security to
ensures the secure transfer of data.
 Low Power Consumption

 Portable devices have limited
power supplies.
 Battery life of mobile phones is
expected to increase only 20%
over the next 10 years.
 Processor, display and network
connectivity are the main power
consumers in a mobile device.
 Mobile DBMSs need to be
optimized for efficient power
consumption.
 Self Management

 In traditional databases, the database
administrator (DBA) is responsible
for databases maintenance.
 In mobile DBMSs there can be no
DBA to manage the database.
 Mobile DBMSs need to support self-
management and automatically
perform the DBA tasks.
 Some mobile DBMSs allow remote
management that enables a DBA to
manage the mobile databases from a
remote location.
 Embeddable In Applications

 Administrators does not have
direct access to mobile devices.
 Mobile DBMSs should be an
integral part of the application
that can be delivered as a part of
the applications.
 The database must be
embeddable as a DLL file in the
applications.
 It must be also possible to deploy
the database as a stand-alone
DBMS with support of multiple
transaction.
Usage Distribution

 Sybase SQL Anywhere

 Initially created by Watcom as Watcom
SQL.
 SQL Anywhere was launched in in 1995.
 It dominates the mobile-database field,
with about 68% of the mobile database
market.
 Database files are independent of the
operating system and transferable
between supported platforms.
 Strong encryption is supported for both
database files and client-server
communication.
 Oracle Lite

 Omniscience Object Technology, Inc. was
acquired by Oracle Corporation in November
1996 .
 Oracle Lite runs in under 1 MB of memory,
and can be installed in 3 MB of hard disk
space.
 Personal Oracle Lite (POL) is a lightweight,
single-user relational database that runs on
desktops, laptops, down to the smallest hand
help devices.
 Their product (Omniscience ORDBMS)
became the first version of Oracle Lite.
 Microsoft SQL Server
Compact

 Formerly known as SQL Server Mobile
Edition.
 SQL Server Compact is free to download
and redistribute.
 SQL CE runs in-process with the application
which is hosting it.
 It has a memory footprint of approximately 5
MB and disk footprint of less than 2 MB .
 It is optimized for an architecture where all
applications share the same memory pool.
 IBM DB2 Everyplace

 DB2e has been discontinued and April
2013 is the end of support date.
 It had the biggest market share after
SQL Anywhere.
 It had the smallest memory footprint
(350 KB) in compare to other
commercial mobile databases.
 IBM has replaced DB2e with IBM
solidDB family.
 SolidDB is a in-memory MDBMS with
robust data catching features.
 SQLite

 SQLite is an open source mobile
database engine.
 It is a server-less database engine that
needs zero-configuration.
 SQLite is a popular choice as mobile
database for local storage in mobile
applications.
 SQLite engine has no standalone
processes with which the application
program communicates.
 SQLite implements most of the SQL-92
standard.
 Embedded Databases

 Embedded database systems are tightly integrated with
an application that requires access to stored data.
 They are hidden from the application’s end-user and
requires little or no ongoing maintenance.
 Embedded databases need less resources in compare
with mobile databases.
 They are optimized for specific devices such as
smartcards and sensors.
 They support limited and specified functionalities of the
standard SQL.
 Case Study: Proposed Work

A. SECURITY STRATEGY TO MOBILE DATABASE.
 Further Strengthen Storage Access Control
If users need to access the resources of mobile database, it must register to the user assign a
password and grant their visit corresponding system resources rights.
 Strengthen the Encryption of Data
Access control alone is not enough to enhance privacy, and the mobile database system
stored data is very important, Therefore it need to be encrypted to prevent leakage.
 To Improve the Backup and Recovery Capabilities of Mobile Database
The data of mobile database are usually very important, therefore the tape backup, hot
backup, manual backup methods have to be used for safety backup of the database
 The Security of Wireless Communication Path
The safety of mobile database has great relevance with the use of mobile technology, so the
relevant mobile technologies in the implementation should be taken safety measures
 Case Study: Proposed Work

B.SECURITY RELATED TECHNIQUES
 Secure network connection :
The mobile database and the central database have to be synchronized at specific times.
The synchronization is implemented in the system software of the mobile database and is
performed over the http protocol
 Encrypted local database
The local database on the mobile device is encrypted and each time the user opens the
mobile database, he has to enter his password.
 User authentication at the database server :
The synchronization of the small-footprint database that is installed on the mobile device
with the central database is performed with database replication technology.
 Authentication at the web server :
At the server side the communication link is handled by a web server. Hence, it is possible
to take advantage of standard web server authentication and require the user to
authenticate at the web interface level.
 Case Study: Proposed Work

B.SECURITY RELATED TECHNIQUES
 Separate user accounts for the authoring and the read-only application :
The mobile database and the central database have to be synchronized at specific times. The
synchronization is implemented in the system software of the mobile database and is
performed over the http protocol
 Application provided security :
For authoring operations, each user has access only to his own data. A set of database triggers
implemented in the database server, check that the data manipulation operations of the user
are valid.
 The read-only client :
The read-only part of the MDA is implemented as a separate client application. The read-only
client provides access for viewing all announcements.
 Client-side data encryption:
The user gives a password to the client application and all his critical data is
encrypted at the client-side before it is permanently stored in the database. This
encryption guarantees the confidentiality of the data against any database user
including the local database administrators.
 Case Study: Proposed Work

C. Major issues in multilevel security on Distributed Security
Manager
 Authentication

 Data confidentiality

 Identification

 Access control
 Conclusion

With the continuous promotion of mobile computing technology and use of mobile
database technology, the data security becomes an issue. The security policy of mobile
database described in this preposition can guarantee safety in practical application, but
security strategy also requires a specific treatment based on the actual issues. So it's
important to continue to explore the security issues of database system in the mobile
environment The emerging trend is to make all service providing disciplines, such as
web, E-commerce, workflow systems, etc., fully mobile and secure so that any service
can be provided from any place. Customer can surf the information space from any
location at any time and do their shopping, make flight reservation, open bank account,
attend lectures, and so on.
 Trust assumptions are different in the Internet
 Enhanced levels of security services may be necessary
 Public-key cryptography can provide effective solutions
 Try not to preclude future provision of improved security services Finally, an
important issue is the lack of appropriate documentation for certain encryption
algorithms that are used within the system software of mobile platforms.