azd document

HIDING IN THE MOBILE CROWD LOCATION PRIVACY THROUGH GEO-SOCIAL APPLICATIONS
1. INTRODUCTION
Location-aware smart phones support various location-based services (LBSs): users
query the LBS server and learn on the fly about their surroundings. However, such queries give
away private information, enabling the LBS to track users. A user-collaborative privacy-
preserving approach is proposed for LBSs. This solution does not require changing the LBS
server architecture and does not assume third party servers; yet, it significantly improves users’
location privacy.
The gain stems from the collaboration of mobile devices: they keep their context
information in a buffer and pass it to others seeking such information. Thus, a user remains
hidden from the server, unless all the collaborative peers in the vicinity lack the sought
information. A novel epidemic model is developed to capture possibly time-dependent, dynamics
of information propagation among users. Used in the Bayesian inference framework, this model
helps analyze the effects of various parameters, such as users’ querying rates and the lifetime of
context information, on users’ location privacy.
The results show that our scheme hides a high fraction of location-based queries, thus
significantly enhancing users’ location privacy. Finally, implementation indicates that it is
lightweight and the cost of collaboration is negligible.
We have proposed a novel analytical framework to quantify location privacy of our
distributed protocol. Our epidemic model captures the hiding probability for user locations, i.e.,
the fraction of times when, due to MobiCrowd, the adversary does not observe user queries. By
relying on this model, our Bayesian inference attack estimates the location of users when they
hide. Our extensive joint epidemic/Bayesian analysis shows a significant improvement thanks to
MobiCrowd, across both the individual and the average mobility prior knowledge scenarios for
the adversary. We have demonstrated the resource efficiency of MobiCrowd by implementing it
in portable devices.
Department of CSE 1 TKRCET

2. LITERATURE SURVEY
We propose a novel framework for measuring and evaluating location privacy preserving
mechanisms in mobile wireless networks. Within this framework, we first present a formal
model of the system, which provides an efficient representation of the network users, the
adversaries, the location privacy preserving mechanisms and the resulting location privacy of the
users. This model is general enough to accurately express and analyze a variety of location
privacy metrics that were proposed earlier. By using the proposed model, we provide formal
representations of four metrics among the most relevant categories of location privacy metrics.
We also present a detailed comparative analysis of these metrics based on a set of criteria for
location privacy measurement. Finally, we propose a novel and effective metric for measuring
location privacy, called the distortion-based metric, which satisfies these criteria for privacy
measurement and is capable of capturing the mobile users’ location privacy more precisely than
the existing metrics. Our metric estimates location privacy as the expected distortion in the
reconstructed users’ trajectories by an adversary.
Individuals face privacy risks when providing personal location data to potentially
untrusted location based services (LBSs). We develop and demonstrate Cache Cloak, a system
that enables real time anonymization of location data. In Cache Cloak, a trusted anonymizing
server generates mobility predictions from historical data and submits intersecting predicted
paths simultaneously to the LBS. Each new predicted path is made to intersect with other users’
paths, ensuring that no individual user’s path can be reliably tracked over time. Mobile users
retrieve cached query responses for successive new locations from the trusted server, triggering
new prediction only when no cached response is available for their current locations. A
simulated hostile LBS with detailed mobility pattern data attempts to track users of Cache Cloak,
generating a quantitative measure of location privacy over time. GPS data from a GIS-based
traffic simulation in an urban environment shows that Cache Cloak can achieve real time
location privacy without loss of location accuracy or availability.

2.1. X Share
Loaded with personal data, e.g. photos, contacts, and call history, mobile phones are truly
personal devices. Yet it is often necessary or desirable to share our phones with others. This is
especially true as mobile phones are integrating features conventionally provided by other
dedicated devices, from MP3 players to games consoles. Unfortunately, when we lend our
phones to others, we give away complete access because existing phones assume a single user
and provide little protection for private data and applications. In this work, we present xShare, a
protection solution to address this problem. X Share allows phone owners to rapidly specify what
they want to share and place the phone into a restricted mode where only the data and
applications intended for sharing can be accessed.
We first present findings from two motivational user studies based on which we provide
the design requirements of X Share. We then present the design of X Share based on file level
access control. We describe the implementation of xShare on Windows Mobile and report a
comprehensive usability evaluation of the implementation, including measurements and user
studies. The evaluation demonstrates that our X Share implementation has negligible overhead
for interactive phone usage, is extremely favored by mobile users, and provides robust protection
against attacks by experienced Windows Mobile users and developers.
2.2. De-anonymizing Mobility Traces
Location-based services, which employ data from smartphones, vehicles, etc., are
growing in popularity. To reduce the threat that shared location data poses to a user’s privacy,
some services anonymize or obfuscate this data. In this paper, we show these methods can be
effectively defeated: a set of location traces can be deanonymized given an easily obtained social
network graph. The key idea of our approach is that a user may be identified by those she meets:
a contact graph identifying meetings between anonymized users in a set of traces can be
structurally correlated with a social network graph, thereby identifying anonymized users. We
demonstrate the effectiveness of our approach using three real world datasets: University of St
Andrews mobility trace and social network (27 nodes each), small blue contact trace and
Facebook social network (125 nodes), and Infocom 2006 Bluetooth contact traces and
conference attendees’ DBLP social network (78 nodes). Our experiments show that 80% of users

are identified precisely, while only 8% are identified incorrectly, with the remainder mapped to a
small set of users.
2.3. System Study
The analysis of the existing system has to be carried to learn the details of the existing
system. System analysis is the process of gathering and interpreting facts, diagnosing problems
and using the information to recommend improvements to the system. Only after the system’s
analysis we can begin to determine how and where a computer information system can benefit
all the users of the system. This accumulation of the system called a system’s study.
2.3.1. Existing system
System which is already present in the market is called existing system. To enhance
privacy for LBS users several solutions have been proposed and two main categories are
 Centralized and
 User-centric
2.3.1.1. Centralized approaches
Centralized approaches introduce a third party in the system, which protects users’
privacy by operating between the user and the LBS. Such an intermediary proxy server could
anonymize queries by removing any information that identifies the user or her device.
It could blend a user’s query with those of other users, so that the LBS server always sees a
group of queries.
2.3.1.2. User-centric approaches
User-centric approaches operate on the device. Typically they aim to blur the location
information by, for example, having the user’s smartphone submit inaccurate, noisy GPS
coordinates to the LBS server.

Disadvantages of centralized approaches and user centric approaches
 The threat of an untrustworthy LBS server is addressed by the introduction of a new
third-party server. Additionally, new proxy servers become as attractive for attackers as
centralized LBSs.
 Other centralized approaches require the LBS to change its operation by, for example,
mandating that it process modified queries, or that it store data differently.
 Centralized interventions or substantial changes to the LBS operation would be hard to
adopt, simply because the LBS providers would have little incentive to fundamentally
change their operation.
 Obfuscation approaches that protect user location-privacy can degrade the user
experience if users need high privacy, e.g., LBS responses would be inaccurate or un
time.
2.3.2. Proposed system
Applying a slight modification to the existing System is called proposed system.
 Proposed system avoids the privacy problems of users by collaborate with each other to
jointly improve their privacy, without the need for a trusted third-party (TTP).
 In effect, the mobile crowd acts as a TTP, and the protection mechanism becomes a
distributed protocol among users.
 Mobile users concerned about their location privacy are indeed the most motivated to
engage in protecting themselves.
 MobiCrowd, is that users only contact the LBS server if they cannot find the sought
information among their peers, i.e., other nearby reachable user devices.
 The places where people gather are points of interest, where users are most likely to
query LBS. Thus, MobiCrowd would be used exactly where it is most effective.
Advantages of proposed system
 Users can minimize their location information leakage by hiding in the crowd.
 MobiCrowd would be most effective when there are many peers gathered at the same
location.

3. SYSTEM REQUIREMENT SPECIFICATION
Basically every system needs two types of requirements they are as follows
1. Software requirements
2. Hardware requirements
3.1. Software Requirements
The software requirements are description of features and functionalities of the target
system. Requirements convey the expectations of users from the software product. And our
system software requirements are as follows
 Operating System : Windows Family
 Language : JDK 1.5
 Front End : Java
 Database : My SQL 5.0
3.1.1. Operating system
The operating system is the most important program that runs on a computer. Every
general-purpose computer must have an operating system to run other programs. Operating
systems perform basic tasks, such as recognizing input from the keyboard, sending output to
the display screen, keeping track of files and directories on the disk, and controlling peripheral
devices such as disk drives and printers.
3.1.2. JDK 1. 5
The Java Development Kit (JDK) is an implementation of either one of the Java SE, Java
EE or Java ME platforms released by Oracle Corporation. The JDK includes a private JVM and a
few other resources to finish the recipe to a Java Application. Since the introduction of the
Java platform, it has been by far the most widely used Software Development Kit.

3.1.3. Java
Java is a high-level programming language developed by Sun Microsystems. Java was
originally called OAK. Java is an object-oriented language similar to C++, but simplified to
eliminate language features that cause common programming errors.
3.1.4. My SQL
My SQL is a relational database management system (RDBMS) based on SQL (structured
query language).it is used in our application to store the details of the requested query
users .
3.2. Hardware Requirements
Hardware requirements are can be defined as minimal requirement parts of the CPU to
run the system. And our minimal hardware requirements are as follows
 Processor : Any Processor above 500 MHz
 Ram : 128 MB.
 Hard Disk : 10 GB.
 Compact Disk : 650 MB
 Input device : Standard Keyboard and Mouse
 Output device : VGA and High Resolution Monitor.
3.2.1. Processor
A processor is the logic circuitry that responds to and processes the basic instructions that
drive a computer. The term processor has generally replaced the term central processing unit, the
processor in a personal computer or embedded in small devices is often called a microprocessor.
3.2.2. RAM
RAM is called as random access memory, it is temporary workspace where instructions
are executed and data is processed.RAM is temporary storage for the software it stores all the
data up to system turn off.

3.2.3. Hard disk
Magnetic disk on which you can store computer data, the term hard is used to distinguish
it from a soft, or floppy, disk. Hard disks hold more data and are faster than floppy disks. A hard
disk, for example, can store anywhere from 10 to more than 100 gigabytes, whereas most
floppies have a maximum storage capacity of 1.4 megabytes.
3.2.4. Compact disk
Compact disc is a polycarbonate with one or more metal layers capable of storing digital
information. The most prevalent types of compact discs are those used by the music industry to
store digital recordings and CD-ROMs used to store computer data. Both of these types of
compact disc are read-only, which means that once the data has been recorded onto them, they
can only be read, or played.
3.3.5. Input devices
An input device for a computer allows you to enter information. The most fundamental
pieces of information are keystrokes on a keyboard and clicks with a mouse. These two input
devices are essential for you to interact with your computer. Many other input devices exist for
entering other types of information, such as images, audio and video. Input devices represent one
type of computer peripheral - the other two types are output devices and storage devices.
3.3.6. Output devices
An output device refers to user-computer communication devices and devices used for
communication between computers, devices and other peripherals, which may be used for
input/output (I/O) purposes, like network interface cards (NIC), modems, IR ports, RFID
systems and wireless networking devices, as well as mechanical output devices, like solenoids,
motors and other electromechanical devices.
3.3. Java
Java is a high level programming language and it is platform independent.java iss
implemented from C++ language has overcame all the errors are exist in the C++ language. And
it is open source language any body can access it and can implement in their own style.

3.3.1. The Java Programming Language
The Java programming language is a high-level language that can be characterized by all
of the following buzzwords:
 Simple
 Architecture neutral
 Object oriented
 Portable
 Distributed
 High performance
 Robust
 Dynamic
 Secure
With most programming languages, you either compile or interpret a program so that you
can run it on your computer. The Java programming language is unusual in that a program is
both compiled and interpreted. With the compiler, first you translate a program into an
intermediate language called Java byte codes the platform-independent codes interpreted by the
interpreter on the Java platform. The interpreter parses and runs each Java byte code instruction
on the computer. Compilation happens just once; interpretation occurs each time the program is
executed. The following figure illustrates how this works.
Fig.3.3.1.1.java compiler

You can think of Java byte codes as the machine code instructions for the Java Virtual
Machine (JVM). Every Java interpreter, whether it’s a development tool or a Web browser that
can run applets, is an implementation of the JVM. Java byte codes help make “write once, run
anywhere” possible. You can compile your program into byte codes on any platform that has a
Java compiler. The byte codes can then be run on any implementation of the JVM. That means
that as long as a computer has a JVM, the same program written in the Java programming
language can run on Windows 2000, a Solaris workstation, or on an iMac.
Fig.3.3.1.2.java virtual machine
3.3.2. The java platform
A platform is the hardware or software environment in which a program runs. We have
already mentioned some of the most popular platforms like Windows 2000, Linux, Solaris, and
Mac OS. Most platforms can be described as a combination of the operating system and
hardware. The Java platform differs from most other platforms in that it’s a software-only
platform that runs on top of other hardware-based platforms.
The Java platform has two components
 The Java Virtual Machine (JVM)
 The Java Application Programming Interface (Java API)
You have already been introduced to the JVM. It is the base for the Java platform and is ported
onto various hardware-based platforms. The Java API is a large collection of ready-made

software components that provide many useful capabilities, such as graphical user interface
(GUI) widgets. The Java API is grouped into libraries of related classes and interfaces; these
libraries are known as packages. The next section, what can java technology do? Highlights what
functionality some of the packages in the Java API provide.
The following figure depicts a program that’s running on the Java platform. As the figure
shows, the Java API and the virtual machine insulate the program from the hardware.
Fig.3.3.2.1.java flatform
Native code is code that after you compile it, the compiled code runs on a specific
hardware platform. As a platform-independent environment, the Java platform can be a bit
slower than native code. However, smart compilers, well-tuned interpreters, and just-in-time byte
code compilers can bring performance close to that of native code without threatening
portability.
3.3.3. What can java technology do?
The most common types of programs written in the Java programming language are
applets and applications. If you have surf the web, you are probably already familiar with
applets. An applet is a program that adheres to certain conventions that allow it to run within a
Java-enabled browser. However, the Java programming language is not just for writing cute,
entertaining applets for the web. The general-purpose, high-level Java programming language is

also a powerful software platform. Using the generous API, you can write many types of
programs.
An application is a standalone program that runs directly on the Java platform. A special
kind of application known as a server serves and supports clients on a network. Examples of
servers are web servers, proxy servers, mail servers, and print servers. Another specialized
program is a servlet. A servlet can almost be thought of as an applet that runs on the server side.
Java Servlets are a popular choice for building interactive web applications, replacing the use of
CGI scripts. Servlets are similar to applets in that they are runtime extensions of applications.
Instead of working in browsers, though, servlets run within Java Web servers, configuring or
tailoring the server.
How does the API support all these kinds of programs? It does so with packages of
software components that provides a wide range of functionality. Every full implementation of
the Java platform gives you the following features:
 The essentials: Objects, strings, threads, numbers, input and output, data
structures, system properties, date and time, and so on.
 Applets: The set of conventions used by applets.
 Networking: URLs, TCP (Transmission Control Protocol), UDP (User Data gram
Protocol) sockets, and IP (Internet Protocol) addresses.
 Internationalization: Help for writing programs that can be localized for users
worldwide. Programs can automatically adapt to specific locales and be displayed
in the appropriate language.
 Security: Both low level and high level, including electronic signatures, public
and private key management, access control, and certificates.
 Software components: Known as Java Beans, can plug into existing component
architectures.
 Object serialization: Allows lightweight persistence and communication via
Remote Method Invocation (RMI).
 Java Database Connectivity (JDBC): Provides uniform access to a wide range
of relational databases.

The Java platform also has APIs for 2D and 3D graphics, accessibility, servers,
collaboration, telephony, speech, animation, and more. The following figure depicts what is
included in the Java 2 SDK.
Fig.3.3.3.1.java features
3.3.4. How will java technology change my life?
We can’t promise you fame, fortune, or even a job if you learn the Java programming
language. Still, it is likely to make your programs better and requires less effort than other
languages. We believe that Java technology will help you do the following:
 Get started quickly: Although the Java programming language is a powerful
object-oriented language, it’s easy to learn, especially for programmers already
familiar with C or C++.
 Write less code: Comparisons of program metrics (class counts, method counts,
and so on) suggest that a program written in the Java programming language can
be four times smaller than the same program in C++.
 Write better code: The Java programming language encourages good coding
practices, and its garbage collection helps you avoid memory leaks. Its object
orientation, its JavaBeans component architecture, and its wide-ranging, easily
extendible API let you reuse other people’s tested code and introduce fewer bugs.

 Develop programs more quickly: Your development time may be as much as
twice as fast versus writing the same program in C++. Why? You write fewer
lines of code and it is a simpler programming language than C++.
 Avoid platform dependencies with 100% Pure java: You can keep your
program portable by avoiding the use of libraries written in other languages. The
100% Pure Java Product Certification Program has a repository of historical
process manuals, white papers, brochures, and similar materials online.
 Write once, run anywhere: Because 100% Pure Java programs are compiled into
machine-independent byte codes, they run consistently on any Java platform.
 Distribute software more easily: You can upgrade applets easily from a central
server. Applets take advantage of the feature of allowing new classes to be loaded
“on the fly,” without recompiling the entire program.
3.4. ODBC
Microsoft Open Database Connectivity (ODBC) is a standard programming interface for
application developers and database systems providers. Before ODBC became a de facto
standard for Windows programs to interface with database systems, programmers had to use
proprietary languages for each database they wanted to connect to. Now, ODBC has made the
choice of the database system almost irrelevant from a coding perspective, which is as it should
be. Application developers have much more important things to worry about than the syntax that
is needed to port their program from one database to another when business needs suddenly
change.
Through the ODBC Administrator in Control Panel, you can specify the particular
database that is associated with a data source that an ODBC application program is written to
use. Think of an ODBC data source as a door with a name on it. Each door will lead you to a
particular database. For example, the data source named Sales Figures might be a SQL Server
database, whereas the Accounts Payable data source could refer to an Access database. The
physical database referred to by a data source can reside anywhere on the LAN.
The ODBC system files are not installed on your system by Windows 95. Rather, they
are installed when you setup a separate database application, such as SQL Server Client or
Visual Basic 4.0. When the ODBC icon is installed in Control Panel, it uses a file called

ODBCINST.DLL. It is also possible to administer your ODBC data sources through a stand-
alone program called ODBCADM.EXE. There is a 16-bit and a 32-bit version of this program
and each maintains a separate list of ODBC data sources. From a programming perspective, the
beauty of ODBC is that the application can be written to use the same set of function calls to
interface with any data source, regardless of the database vendor. The source code of the
application doesn’t change whether it talks to Oracle or SQL Server. We only mention these two
as an example. There are ODBC drivers available for several dozen popular database systems.
Even Excel spreadsheets and plain text files can be turned into data sources. The operating
system uses the registry information written by ODBC Administrator to determine which low-
level ODBC drivers are needed to talk to the data source (such as the interface to Oracle or SQL
Server). The loading of the ODBC drivers is transparent to the ODBC application program. In a
client/server environment, the ODBC API even handles many of the network issues for the
application programmer.
The advantages of this scheme are so numerous that you are probably thinking there must
be some catch. The only disadvantage of ODBC is that it isn’t as efficient as talking directly to
the native database interface. ODBC has had many detractors make the charge that it is too slow.
Microsoft has always claimed that the critical factor in performance is the quality of the driver
software that is used. In our humble opinion, this is true. The availability of good ODBC drivers
has improved a great deal recently. And anyway, the criticism about performance is somewhat
analogous to those who said that compilers would never match the speed of pure assembly
language. Maybe not, but the compiler (or ODBC) gives you the opportunity to write cleaner
programs, which means you finish sooner. Meanwhile, computers get faster every year.
3.5. JDBC
In an effort to set an independent database standard API for Java; Sun Microsystems
developed Java Database Connectivity, or JDBC. JDBC offers a generic SQL database access
mechanism that provides a consistent interface to a variety of RDBMSs. This consistent interface
is achieved through the use of “plug-in” database connectivity modules, or drivers. If a database
vendor wishes to have JDBC support, he or she must provide the driver for each platform that the
database and Java run on.

To gain a wider acceptance of JDBC, Sun based JDBC’s framework on ODBC. As you
discovered earlier in this chapter, ODBC has widespread support on a variety of platforms.
Basing JDBC on ODBC will allow vendors to bring JDBC drivers to market much faster than
developing a completely new connectivity solution.
JDBC was announced in March of 1996. It was released for a 90 day public review that
ended June 8, 1996. Because of user input, the final JDBC v1.0 specification was released soon
after.
The remainder of this section will cover enough information about JDBC for you to know
what it is about and how to use it effectively. This is by no means a complete overview of JDBC.
That would fill an entire book.
3.5.1. JDBC goals
Few software packages are designed without goals in mind. JDBC is one that, because of
its many goals, drove the development of the API. These goals, in conjunction with early
reviewer feedback, have finalized the JDBC class library into a solid framework for building
database applications in Java.
The goals that were set for JDBC are important. They will give you some insight as to
why certain classes and functionalities behave the way they do. The eight design goals for JDBC
are as follows:
 SQL level API
The designers felt that their main goal was to define a SQL interface for Java. Although
not the lowest database interface level possible, it is at a low enough level for higher-level tools
and APIs to be created. Conversely, it is at a high enough level for application programmers to
use it confidently. Attaining this goal allows vendors to “generate” JDBC code and to hide many
of JDBC’s complexities from the end user.
 SQL conformance
SQL syntax varies as you move from database vendor to database vendor. In an effort to
support a wide variety of vendors, JDBC will allow any query statement to be passed through it

to the underlying database driver. This allows the connectivity module to handle non-standard
functionality in a manner that is suitable for its users.
 JDBC must be implemental on top of common database interfaces
The JDBC SQL API must “sit” on top of other common SQL level APIs. This goal
allows JDBC to use existing ODBC level drivers by the use of a software interface. This
interface would translate JDBC calls to ODBC and vice versa.
 Provide a java interface that is consistent with the rest of the java system
Because of Java’s acceptance in the user community thus far, the designers feel that they
should not stray from the current design of the core Java system.
 Keep it simple
This goal probably appears in all software design goal listings. JDBC is no exception.
Sun felt that the design of JDBC should be very simple, allowing for only one method of
completing a task per mechanism. Allowing duplicate functionality only serves to confuse the
users of the API.
 Use strong, static typing wherever possible
Strong typing allows for more error checking to be done at compile time; also, less error
appear at runtime.
 Keep the common cases simple
Because more often than not, the usual SQL calls used by the programmer are simple
SELECT’s, INSERT’s, DELETE’s and UPDATE’s, these queries should be simple to perform with
JDBC. However, more complex SQL statements should also be possible. Finally we decided to
proceed the implementation using Java Networking. And for dynamically updating the cache
table we go for MS Access database.

Java ha two things: a programming language and a platform. Java is a high-level
programming language that is all of the following
Simple Architecture-neutral
Object-oriented Portable
Distributed High-performance
Interpreted Multithreaded
You can think of Java byte codes as the machine code instructions for the Java Virtual
Machine (Java VM). Every Java interpreter, whether it’s a Java development tool or a Web
browser that can run Java applets, is an implementation of the Java VM. The Java VM can also
be implemented in hardware.
Java byte codes help make “write once, run anywhere” possible. You can compile your
Java program into byte codes on my platform that has a Java compiler.
The byte codes can then be run any implementation of the JVM. For example, the same Java
program can run Windows NT, Solaris, and Macintosh.
3.6. Networking
3.6.1. TCP/IP stack
The TCP/IP stack is shorter than the OSI one. TCP is a connection-oriented protocol;
UDP (User Datagram Protocol) is a connectionless protocol.

Fig.3.6.1.TCP/IP stack
3.6.2. IP datagram’s
The IP layer provides a connectionless and unreliable delivery system. It considers each
datagram independently of the others. Any association between datagram must be supplied by
the higher layers. The IP layer supplies a checksum that includes its own header. The header
includes the source and destination addresses. The IP layer handles routing through an Internet. It
is also responsible for breaking up large datagram into smaller ones for transmission and
reassembling them at the other end.
3.6.3. UDP
UDP is also connectionless and unreliable. What it adds to IP is a checksum for the
contents of the datagram and port numbers. These are used to give a client/server model - see
later.
3.6.4. TCP
TCP supplies logic to give a reliable connection-oriented protocol above IP. It provides a
virtual circuit that two processes can use to communicate.

3.6.5. Internet addresses
In order to use a service, you must be able to find it. The Internet uses an address scheme
for machines so that they can be located. The address is a 32 bit integer which gives the IP
address. This encodes a network ID and more addressing. The network ID falls into various
classes according to the size of the network address.
3.6.6. Network address
Class A uses 8 bits for the network address with 24 bits left over for other addressing.
Class B uses 16 bit network addressing. Class C uses 24 bit network addressing and class D uses
all 32.
3.6.7. Subnet address
Internally, the UNIX network is divided into sub networks. Building 11 is currently on
one sub network and uses 10-bit addressing, allowing 1024 different hosts.
3.6.8. Host address
8 bits are finally used for host addresses within our subnet. This places a limit of 256
machines that can be on the subnet.
3.6.9. Total address
Fig.3.6.9.1.IP address
The 32 bit address is usually written as 4 integers separated by dots.
3.6.10. Port addresses

A service exists on a host, and is identified by its port. This is a 16 bit number. To send a
message to a server, you send it to the port for that service of the host that it is running on. This
is not location transparency! Certain of these ports are "well known".
3.6.11. Sockets
A socket is a data structure maintained by the system to handle network connections. A
socket is created using the call socket. It returns an integer that is like a file descriptor. In fact,
under Windows, this handle can be used with Read File and Write File functions.
#include <sys/types.h>
#include <sys/socket.h>
int socket(int family, int type, int protocol);
Here "family" will be AF_INET for IP communications, protocol will be zero, and type will
depend on whether TCP or UDP is used. Two processes wishing to communicate over a network
create a socket each. These are similar to two ends of a pipe - but the actual pipe does not yet
exist.
3.7. J Free Chart
J Free Chart is a free 100% Java chart library that makes it easy for developers to display
professional quality charts in their applications. J Free Chart's extensive feature set includes
A consistent and well-documented API, supporting a wide range of chart types. A flexible design
that is easy to extend, and targets both server-side and client-side applications, Support for many
output types, including Swing components, image files (including PNG and JPEG), and vector
graphics file formats (including PDF, EPS and SVG).
J Free Chart is "open source" or, more specifically, free software. It is distributed under
the terms of the GNU Lesser General Public License (LGPL), which permits use in proprietary
applications.
3.7.1. Map visualizations

Charts showing values that relate to geographical areas. Some examples include: (a)
population density in each state of the United States, (b) income per capita for each country in
Europe, (c) life expectancy in each country of the world. The tasks in this project include some
Sourcing freely redistributable vector outlines for the countries of the world, states/provinces in
particular countries (USA in particular, but also other areas); Creating an appropriate dataset
interface (plus default implementation), a rendered, and integrating this with the existing XY
Plot class in J Free Chart; Testing, documenting, testing some more, documenting some more.
3.7.2. Time series chart interactivity
Implement a new (to J Free Chart) feature for interactive time series charts --- to display a
separate control that shows a small version of ALL the time series data, with a sliding "view"
rectangle that allows you to select the subset of the time series data to display in the main chart.
3.7.3. Dash boards
dashboard mechanism that supports a subset of J Free Chart types (dials, pies,
thermometers) that can be delivered easily via both Java Web Start and an applet.
3.7.4. Property editors
The property editor mechanism in J Free Chart only handles a small subset of the
properties that can be set for charts, Extend (or re-implement) this mechanism to provide greater
end-user control over the appearance of the charts.
3.8. Tomcat 6.0 Web Server
Tomcat is an open source web server developed by Apache Group. Apache Tomcat is the
servlet container that is used in the official Reference Implementation for the Java Servlet and
Java Server Pages technologies. The Java Servlet and Java Server Pages specifications are
developed by Sun under the Java Community Process. Web Servers like Apache Tomcat support
only web components while an application server supports web components as well as business
components (BEAs Web logic, is one of the popular application server).To develop a web
application with jsp/servlet install any web server like J Run, Tomcat etc. to run your application.

Fig.3.8.Tomcat server
4. ANALYSIS
4.1 Feasibility Analysis
Many feasibility studies are disillusioning for both users and analysts. First, the study
often presupposes that when the feasibility document is being prepared, the analyst is in a
position to evaluate solutions. Second, most studies tend to overlook the confusion inherent in
system development-the constraints and the assumed attitudes. If the feasibility study is to serve
as a decision document, it must answer three key questions
1. Is there a new and better way to do the job that will benefit the user?
2. What are the costs and savings of the alternatives?
3. What is recommended?
The most successful system projects are not necessarily the biggest or most visible in a
business but rather those that truly meet user expectations.
4.1.1. Economic feasibility

Economic analysis is the most frequently used method for evaluating the effectiveness of
a candidate system. More commonly known as cost/benefit analysis, the procedure is to
determine the benefits and savings that are expected from a candidate system and compare them
with costs. If benefits outweigh costs, then the decision is made to design and implement the
system. Otherwise, further justification or alterations in the proposed system will have to be
made if it is to have a chance of being approved. This is an ongoing effort that improves in
accuracy at each phase of the system life cycle.
4.1.2. Technical feasibility
Technical feasibility centers on the existing computer system (hardware, Software, etc.)
and to what extent it can support the proposed addition. For example, if the current computer is
operating at 80 percent capacity-an arbitrary ceiling-then running another application could
overload the system or require additional hardware. This involves financial considerations to
accommodate technical enhancements. If the budget is a serious constraint, then the project is
judged not feasible.
4.1.3. Operational feasibility
Purpose projects are beneficial only if they can be turned into information systems that
will meet the organization’s operating systems.
Some of the conditions are
a) Is there sufficient support for the project from management and users?
b) Are correct business methods acceptable to the users?
c) Have the users been involved in the planning and development of the project?
d) Will the proposed system cause harm?
4.2. External Interface Requirements
External interface requirements are as follows
4.2.1 User interfaces

As the application uses the raw text data in the screens as input and output keyboard can
be used to specify the required information. The mouse can be used to navigate through the
controls and pages by triggering the events on the button controls specified. Additional devices
like monitor can be used to view the input and output screens in the applications.
4.2.2 Hardware interfaces
These requirements are same as in user interfaces and the additional requirements like a
high quality processor with enough RAM space is required to optimize the execution process.
All the above user interfaces can be used for input and output performance and system with good
configuration like virtual memory and process to increase its functionalities.
4.2.3 Software interfaces
As the application is displayed in the user machine it needs to contain the respective
JAVA software, Database provision or data required for inputs. The application is executed
through the command prompt handling the transaction in graphical GUI’s.
4.2.4 Communication interfaces
As the application is going to be executed in multiple systems handling the request and
responses between them the physical communication interfaces like cables, routers, switches and
hubs are required. The failure in the communication interfaces may result in failure of
communication between the nodes resulting in blocking the request and responses.
4.3. Non-Functional Requirements
Let us discuss some non functional requirements for our system.
4.3.1 Performance requirements
The performance of the application depends on the system in which it is executed. If the
system is provided with high speed processor and enough RAM space. The speed of execution of
the application is high. As the data is passed or transforms between the nodes in the network.

The performance of the application resides on the type of nodes that are been used (The
availability of virtual memory and the processors speed) And the mode of network that is used
for communicating.
4.3.2 Safety Requirements
The user in the application is provided with user name and password for authenticating
before the login process. Invalid users are blocked from logging in. As the application is
deployed in user machine each user can be provided with a login facility authenticates with the
set of username and password for restricting the unauthorized users from logging in to increase
the strength of the passwords the process of encryption and decryption can also be applied.
4.3.3 Security Requirements
As the source code or software is deployed under the user machine. No security is
provided to the user code. The system security itself is the security i.e. applied to the application.

5. SYSTEM DESIGN
Software design sits at the technical kernel of the software engineering process and is
applied regardless of the development paradigm and area of application. Design is the first step
in the development phase for any engineered product or system. The designer’s goal is to
produce a model or representation of an entity that will later be built. Beginning, once system
requirement have been specified and analyzed, system design is the first of the three technical
activities design, code and test that is required to build and verify software.
The importance can be stated with a single word “Quality”. Design is the place where
quality is fostered in software development. Design provides us with representations of software
that can assess for quality. Design is the only way that we can accurately translate a customer’s
view into a finished software product or system. Software design serves as a foundation for all
the software engineering steps that follow. Without a strong design we risk building an unstable
system one that will be difficult to test, one whose quality cannot be assessed until the last stage.
5.1 System Architecture
This system is an approach to enhance the privacy of LBS users, to be used against
service providers who could extract information from their LBS queries and misuse it. The
mobile crowd acts as a TTP, mobile Crowd is that users only contact the LBS server if they
cannot find the sought information among their peers, i.e., other nearby reachable user devices.
Users can minimize their location information leakage by hiding in the crowd. MobiCrowd
would be most effective when there are many peers gathered at the same location.
In the below system architecture we can see the different types objects and their
relationship transactions .in our system we has four objects and they are user , informed user ,
proxy server, main server .when a user send a query it goes in to insider query processing i.e.
proxy checks the query in the informed user whether it is available or not unless proxy sends the
query to server then query goes in to outsider process i.e. server checks if any new sources
available for query if found it redirect it to the proxy server and proxy sends it to informed user
then informed sends reply to user of what he or she requested.

Fig.5.1.system architecture
5.2 Modules
Our system has four modules and they are as follows
 Mobile Users
 Location Based Server (LBS)
 User Query
 Check authenticity
5.2.1. Mobile user
Consider N users who move in an area split into M discrete regions/locations. The
mobility of each user u is a discrete-time Markov chain on the set of regions: The probability that
user u, currently in region ri, will next visit region rj is denoted by pu(rj |ri). Let πu(ri) be the
probability that user u is in region ri. Each user possesses a location-aware wireless device,
capable of ad hoc device-to-device communication and of connecting to the wireless
infrastructure (e.g., cellular and Wi-Fi networks).

5.2.2. Location based server (LBS)
As users move between regions, they leverage the infrastructure to submit local-search
queries to LBS. The information that the LBS provides expires periodically, in the sense that it is
no longer valid. Note that information expiration is not equivalent to the user accessing the LBS:
A user accesses the LBS when her information has expired and she wishes to receive the most
up-to-date version of it.
5.2.3. User query
A seeker, essentially a user who does not have the sought information in her buffer, first
broadcasts her query to her neighbors through the wireless ad hoc interface of the device. This a
local query. Each user with valid information about a region is termed informed user for that
region. Users interested in getting location-specific information about a region are called
information seekers of that region.
5.2.4. Check authenticity
The information the LBS provides is self-verifiable, i.e., users can verify the integrity and
authenticity of the server responses. This can be done in different ways; in our system, the user
device verifies a digital signature of the LBS on each reply by using the LBS provider’s public
key. As a result, a compromised access point or mobile device cannot degrade the experience of
users by altering replies or disseminating expired information.
5.3 Data Dictionary
5.3.1 Data base design
A database model is a collection of logical constructs used to represent the data in data
structures and data relationships with in the database. Basically, the database models may be
grouped into two categories: conceptual model and implementation models. The conceptual
model focuses on the logical nature of that data presentation. Therefore the conceptual model is
concerned with what is representing in the database and the implementation model is concerned
with how it is represented.

5.3.2 Conceptual model
The conceptual model represents data present in the entities as well the relations present
is the entities. All the strong entities and weak entities are identified here and it mainly focuses
on the Model logical nature of that data presentation.
5.3.3. General access
General access model is used to convert the ER model into the relation model. Here we
can identify the references to the other entities and the nature of the each attribute. But, A
network model’s record can have more than one parent.
5.3.4. Relation model
The relational model is represented as tables. The columns of each table are attributes
that define the data or value domain for entities in that column. The rows of each table are tuples
representing individual data objects being stored. A relational table should have only one
primary key. A Primary key is a combination of one or more attributes whose value
unambiguously locates each row in the table. Database normalization is a design technique by
which relational database tables are structured in such a way as to make them invulnerable to
certain types of logical inconsistencies and anomalies.
Tables can be normalized to varying digress: relational database theory defines “normal
forms” of successively higher degrees of stringency, so, for example, a table in third normal form
is less open to logical inconsistencies and anomalies than a tale that is only in second normal
form. Although the normal forms are after defined (informally) in terms of the characteristics of
tables, rigorous definitions of the normal forms are concerned with the characteristics of
mathematical constructs known as relations. Whenever information is represented relationally
that is, roughly speaking, as values within rows beneath fixed column headings it makes sense to
ask to what extent the representation is normalized.
5.4 Normal Forms
The normal forms (abbrev. NF) of relational database theory provide criteria for
determining a table’s degree of vulnerability to logical inconsistencies and anomalies. The higher
the normal form applicable to a table, the vulnerable it is to such inconsistencies and anomalies.

Each table has a “highest normal form” (HNF): by definition, a table always meets the
requirements of its HNF; also by definition, a table fails to meet the requirements of any normal
form higher than its HNF. The normal forms are applicable to individual tables; to say that and
entire database is in normal form n is to say that all of its tables are in normal form n.
Newcomers to database design sometimes suppose that normalization proceeds in an
iterative fashion. I.e. a 1NF design is first normalized to 2NF, then to 3NF, and so on. This is not
an accurate description of how normalization typically works. A sensibly designed table is likely
to be in 3NF on the first attempt; furthermore, if it is 3NF, it is overwhelmingly likely to have an
HNF of 5NF. Achieving the “higher” normal forms (above 3NF) does not usually require an
extra expenditure of effort on the part of the designer, because 3NF tables usually need no
modification to meet the requirements of these higher normal forms Edgar F. Cod originally
defined the first three normal forms (1NF, 2NF and 3NF). These normal forms have been
summarized as requiring that all non-key attributes be dependent on “the key, the whole key and
nothing but the key”.
The fourth and fifth normal forms (4NF and 5NF) deal specifically with the
representation of many-to-many and one-to-many relationships among attributes. Sixth normal
form (6NF) incorporates considerations relevant to temporal databases.
5.4.1 First normal form
The criteria for first normal form (1NF) are:
 A table must be guaranteed not to have any duplicate records; therefore it must have at
least one candidate key.
 There must be no repeating groups, i.e. no attributes which occur a different number of
times on different records. For example, suppose that an employee can have multiple
skills: a possible representation of employees’ skills is {Employee ID, Skill1, Skill2,
Skill3…….}, where {Employee ID} is the unique identifier for a record. This
representation would not be in 1NF.
Note that all relations are in 1NF. The question of whether a given representation is in
1NF is equivalent to the question of whether it is a relation.

5.4.2 Second normal form
The criteria for second normal form (2NF) are: The table must be in 1NF.
 None of the non-prime attributes of the table are functionally dependent on a part (proper
subset) of a candidate key; in other words, all functional dependencies of non-prime
attributes on candidate keys are full functional dependencies. For example, consider a
“Department Members” table whose attributes are Department ID, Employee ID, and
Employee Date of Birth; and suppose that an employee works in one or more
departments. The combination of Department ID and Employee ID and Employee ID
uniquely identifies records within the table. Given that Employee Date of Birth depends
on only one of those attributes – namely, Employee ID – the table is not in 2NF.
5.4.3 Third normal form
The criteria for third normal form (3NF) are:
 The table must be in 2NF.
 There are no non-trivial functional dependencies between non-prime attribute is only
indirectly dependent (transitively dependent) on a candidate key, by virtue of being
functionally dependent on another nonprime attribute. For example, consider a
“Departments” table whose attributes are Department ID, Department Name, Manager
ID, and Manager Hire Date; and suppose that each manager can manage one or more
departments.
5.4.4 Boyce-codd normal form
The criteria for Boyce-codd Normal Form (BCNF) are:
 The table must be in 3NF. Every non-trivial functional dependency must be a dependency
on a super key.
5.5 Data Base Tables
The following tables are some data base tables which are used to store the data base of
requested users in the back end by our application. Our system has four data base tables
and they are as follows
 Register table

 Proxy table
 Index server table
 Server table
Table name: register
Id Username Password DOB Phone Address Email
Fig.5.5.1.register table
 Whenever a user registers in the application then data base server stores all the register
user details in the registration table.
Table name: proxy
Id Usernam
e
Email Location Latitude Longitude Date
Fig.5.5.2. proxy table
 When a user request the proxy server for a query then proxy stores his/her id, username,
email, location, latitude, longitude values and date when he/she requested the it.
Table Name: index-server
Id Username Email Location Latitude Longitude Request
Fig.5.5.3. index-server table

 After receiving a query request from user proxy send the request to the index server and
then index server send the query to main server by storing all the user details in its data
base.
Table name: server
Id Usernam
e
Email Location D name File Reply
Fig.5.5.4. server table
 Server stores the user id, his/her user name ,email, location ,domain name what he/she
provided in the process and which file he/she used in procedure of getting the result after
giving the reply to the user.
5.6 Data Flow Diagrams
A Data Flow Diagram (DFD) is a diagrammatic representation of the information flows
within a system, showing:
 How information enters and leaves the system,
 What changes the information,
 Where information is stored.
In SSADM a DFD model includes supporting documentation describing the information
shown in the diagram. DFDs are used not only in structured system analysis and design, but also
as a general process modeling tool. There are a number of commercial tools in the market today
which are based on DFD modeling.
SSADM uses DFDs in three stages of the development process:
 Current Physical DFDs. These record the results of conventional fact finding.
 Current Logical DFDs. The logical information processing of the current system.
 Required Logical DFDs. The logical information processing requirements of the
proposed system.

Data Flow Diagram
Fig.5.6.data flow diagram
1. Above data flow datagram shows how the data flows in our application. It begins with start
after that user login into his/her account and makes a query.
2. If that query is un expired it goes to proxy server then using the collaboration process proxy
sends the query to informed user after the completion of this process informed user sends the
result to requested user.
3. If query is expired it goes to server and server sends the requested location result to the user.

5.7 UML Diagrams
Diagrams are graphical presentation of set of elements. Diagrams project a system, or
visualize a system from different angles and perspectives. The UML has nine diagrams these
diagrams can be classified into the following groups.
Static diagrams
Class diagrams.
Object diagrams.
Component diagrams.
Deployment diagrams
Dynamic diagrams
Use case diagram.
Sequence diagram.
State chart diagram.
Activity diagram.
Collaboration diagram.
5.7.1. Static Or Structural diagrams
A detailed explanation of static diagrams is given below.
Class diagram
This shows a set of classes, interfaces, collaborations and their relationships. There are
the most common diagrams in modeling the object oriented systems and are used to give the
static view of a system.
Object diagram
Shows a set of objects and their relationships and are used to show the data structures, the
static snapshots of instances of the elements in a class diagram. Like class diagram, the object
diagrams also address the static design view or process view of a system.

Component diagram
Shows a set of components and their relationships and are used to illustrate the static
implementation view of a system. They are related to class diagrams where in components map
to one or more classes, interfaces of collaborations.
Deployment diagram
Deployment diagram shows a set of nodes and their relationships. They are used to show
the static deployment view of the architecture of a system. They are related to the component
diagrams where a node encloses one or more components.
5.7.2. Dynamic or Behavioral diagram
Explanation of dynamic or behavioral diagrams is given below
Use case diagram
Use case diagram shows a set of use cases and actors and their relationships. These
diagrams illustrate the static use case view of a system and are important in organizing and
modeling the behaviors of a system.
Sequence diagram
Sequence diagram is an interaction diagram which focuses on the time ordering of
messages it shows a set of objects and messages exchange between these objects. This diagram
illustrates the dynamic view of a system.
Activity diagram
Activity diagram shows the flow from one activity to another within a system. The
activities may be sequential or branching objects that act and are acted upon. These also show
the dynamic view of the system.

UML Diagrams
Use Case Diagram
Fig.5.7.2.1. use case diagram
1. Use case diagram shows a set of use cases and actors and their relationships. Server, user,
informed users are actors and their relation is shown in above figure.
2. First user sends a query to the server and then server process the query and checks the
user region and gives the reply.
3. Else with the collaboration process user gets the reply from the informed user.
Informed
user

Sequence Diagram
Fig.5.7.2.2.sequence diagram
1. Sequence diagram is an interaction diagram which focuses on the time ordering of messages it
shows a set of objects and messages exchange between these objects.
2. User, proxy, informed, user, server are four objects of our sequence diagram.
3. In the first step user sends a query to proxy server ,next proxy checks the availability of the
query if it expires proxy send it to server unless it send the query to informed user.
4. If the query is expired user get the result from the server unless he get the result from informed
through collaboration.

Class diagram
Fig.5.7.2.3.class diagram
1. Class diagram shows a set of classes, interfaces, collaborations and their relationships.
2. In our class diagram we has five classes, they are user, informed user, query, proxy, server.
3.user and informed user has their names and public key as their arguments, query has expired or
unexpired as its arguments, proxy server and server has different services as their arguments.
.

Collaboration Diagram
Fig.5.7.2.4.collaboration diagram
1. Collaboration diagram shows the step by step procedure of user transaction with the system.
2. After the login user sends a query to the proxy and proxy sends it to the server for the
processing of query if query is available server sends a reply to user.
3. If the query is unavailable proxy sends the query to informed user and informed user send a
reply to the requested user.

Activity Diagram
Fig.5.7.2.5.activity diagram
1. Activity diagram shows the flow from one activity to another within a system. In the
above diagram user sends a query to proxy server after his/his login into the application.
2. In the next step proxy verifies the query whether it is available or expired.
3. If query is available, proxy sends query to informed user and user gets his query reply
from informed user.
4. If query is not available proxy sends it to main server for new source of the query after
checking pubic key of the user server replies to proxy and then proxy sends the result to
the user

6. IMPLEMENTATION
Implementation is nothing but what we are newly implementing in our new system from
the existed system in order to provide a better accurate result with out loosing user private
information to un-trusted third parties.
The following code is implemented by introducing a mobi-crowd schema which deletes
the user private information whenever he/she use the service for accessing his/her required
information.
Logic To Access Data Base To Create Connection
public static Connection getconnection()
{
try
{
Class.forName("com.mysql.jdbc.Driver");
con=DriverManager.getConnection
("jdbc:mysql://localhost:3306/geolocation","root","root");
}
Catch (Exception e)
{
System.out.println ("class error");
}
return con;
}
Logic to Send Email From Our Application
String host="", user="", pass="";
host ="smtp.gmail.com"; //"smtp.gmail.com";
user ="cloudtestprojects@gmail.com"; //"YourEmailId@gmail.com"
pass ="cloudtest@123"; //Your gmail password
String SSL_FACTORY = "javax.net.ssl.SSLSocketFactory";
String to =emailid; // out going email id
String from ="cloudtestprojects@gmail.com"; //Email id of the recipient

String subject=(String)session.getAttribute("subject");
StringmessageText="<b>"+emailid+"</b><br>MyId:"+mid+"<br>Index
KeyWord:"+c+"<br>Friend Id:"+idd+"<br>Message:"+oo+"";
boolean sessionDebug = true;
Properties props = System.getProperties();
props.put("mail.host", host);
props.put("mail.transport.protocol.", "smtp");
props.put("mail.smtp.auth", "true");
props.put("mail.smtp.", "true");
props.put("mail.smtp.port", "465");
props.put("mail.smtp.socketFactory.fallback", "false");
props.put("mail.smtp.socketFactory.class", SSL_FACTORY);
Session mailSession = Session.getDefaultInstance(props, null);
mailSession.setDebug(sessionDebug);
Message msg = new MimeMessage(mailSession);
msg.setFrom(new InternetAddress(from));
InternetAddress[] address = {new InternetAddress(to)};
msg.setRecipients(Message.RecipientType.TO, address);
msg.setSubject(subject);
msg.setContent(messageText, "text/html"); // use setText if you want to send text
Transport transport = mailSession.getTransport("smtp");
transport.connect(host, user, pass);
try
{
transport.sendMessage(msg, msg.getAllRecipients());
transport.close();
}
catch (Exception err)
{
out.println("message not successfully sended"); // assume it’s a fail
}

Java Script Logic to Display Google Map in to Find The User Location:
<script type="text/javascript" src="http://maps.google.com/maps/api/js?sensor=false"></script>
<script type="text/javascript">
var map;
var marker=false;
function initialize()
{
var myLatlng = new google.maps.LatLng(13.053721679021347,80.22521737216266);
varmyOptions={zoom:16,center: myLatlng,mapTypeId: google.maps.MapTypeId.ROADMAP}
map = new google.maps.Map(document.getElementById("gmap"), myOptions);
marker = new google.maps.Marker({position: myLatlng, map: map});
google.maps.event.addListener(map, 'center_changed', function()
{
var location = map.getCenter();
document.getElementById("lat").innerHTML = location.lat();
document.getElementById("lon").innerHTML = location.lng();
placeMarker(location);
});
google.maps.event.addListener(map, 'zoom_changed', function()
{
zoomLevel = map.getZoom();
document.getElementById("zoom_level").innerHTML = zoomLevel;
};
google.maps.event.addListener(marker, 'dblclick', function()
{
zoomLevel = map.getZoom()+1;
if (zoomLevel == 20) {
zoomLevel = 10;
}
document.getElementById("zoom_level").innerHTML = zoomLevel;
map.setZoom(zoomLevel);

});
document.getElementById("zoom_level").innerHTML = 16;
document.getElementById("lat").innerHTML = 13.053721679021347;
document.getElementById("lon").innerHTML = 80.22521737216266;
}
function placeMarker(location)
{
var clickedLocation = new google.maps.LatLng(location);
marker.setPosition(location);
}
window.onload = function(){initialize();
};
</script>
Logic to Download the File Form Server
Blob file1= null;
Connection con = null;
PreparedStatement ps = null;
ResultSet rs = null;
try
{
con=databasecon.getconnection();
ps = con.prepareStatement("select * from server where uid ='"+id+"'");
rs = ps.executeQuery();
while(rs.next())
{
file1=rs.getBlob(6);
}
int len1=(int)file1.length();
//session.setAttribute("resumeBlob1",file1);
byte[] ba = file1.getBytes(1, (int)file1.length());
String filename="File";

response.setContentType("application/mswords");
response.setHeader("Content-Disposition","attachment; filename=""+filename+""");
OutputStream os = response.getOutputStream();
os.write(ba);
os.close();
//response.sendRedirect("index.html");
}

7. TESTING
Introduction
Testing is the process of detecting errors for which the required open web application
secure employment portal specifications stated. Testing performs a very critical role for quality
assurance and for ensuring the reliability of software. The results of testing are used later on
during the software maintenance. The aim of testing is often used to demonstrate that a program
works by showing that it has no errors. The basic purpose of testing phase is to detect the errors
that may be present in the program. Hence one should not start testing with the intent of showing
that a program works, but the intent should be to show that a program doesn’t work. The main
objective of testing is to uncover an error in systematic way with minimum effort and time.
System testing is series of different tests whose primary purpose is to fully exercise the
computer based system. Although each test has a different purpose, all the work should verify
that all system element have been properly integrated and perform allocated functions.
System Implementation is the process of having systems personnel check out and put newly
developed package into use, train users how to interact with it, install the new application and
construct any files of data needed to use the package. While installation the system requirement
where the package is going to be installed is to be checked, whether it has the sufficient for the
software to run the package. The user must be given the manual regarding the installation and the
errors frequently occurred, and how to deal with those errors, and the manner in which to
proceed during data entry.
7.1. Testing Types
The different types of testing are:
 Unit testing
 Integration testing
 System testing
 Acceptance testing

7.1.1. Unit testing
This test focuses on verification effort on the smallest unit of software module. Using the
detailed design and the process specifications testing is done to uncover errors within the
boundary of the module. All the modules must be successful in the unit test before the start of the
integration testing begins. In this project each service is a module like Login, Forms etc. Each
module has to be tested by giving different sets of inputs. The inputs are validated when
accepting from user.
7.1.2. Integration testing
After the unit testing the integration of modules has to be done and then integration
testing can be done. The goal here is to see if modules can be integrated properly, the emphasis
being on testing interfaces between different modules.
7.1.3. System testing
In the system testing the entire web portal is tested according the software requirement
specifications document.
7.1.4. Acceptance testing
The acceptance testing is performed with realistic data of the client, which focus on the
external behavior of the system; the internal logic of the program is emphasized.
Software testing is a critical element of software quality assurance and represents the ultimate
review of specification, design and coding. Testing is the exposure of the system to trial input to
see whether it produces correct output.
7.2. Testing Phases
Software testing phases include the following:
 Test activities are determined and test data selected.
 The test is conducted and test results are compared with the expected results.

7.3. Testing Methods
Testing is a process of executing a program to find out errors. If testing is conducted
successfully, it will uncover all the errors in the software.
Any testing can be done basing on two ways:
 White Box Testing
 Black Box Testing
7.3.1. White box testing
It is a test case design method that uses the control structures of the procedural design to
derive test cases.
Using white box testing a software Engineer can derive the following test cases:
 Exercise all the logical decisions on either true or false sides.
 Execute all loops at their boundaries and within their operational boundaries.
 Exercise the internal data structures to assure their validity.
7.3.2. Black box testing
It is a test case design method used on the functional requirements of the software. It will
help a software engineer to derive sets of input conditions that will exercise all the functional
requirements of the program.
Black Box testing attempts to find errors in the following categories:
 Incorrect or missing functions
 Interface errors
 Errors in data structures
 Performance errors
 Initialization and termination errors
By black box testing we derive a set of test cases that satisfy the following criteria:
 Test cases that reduce by a count that is greater than one
 The number of additional test cases that must be designed to achieve reasonable testing.

7.4. Testing Plans
Testing can be done in two ways:
 Bottom up approach
 Top down approach
7.4.1. Bottom up approach
Testing can be performed starting from smallest and lowest level modules and proceeding
one at a time. For each module in bottom up testing a short program executes the module and
provides the needed data so that the module is asked to perform the way it will when embedded
within the larger system. When bottom level modules are tested attention turns to those on the
next level that use the lower level ones they are tested individually and then linked with the
previously examined lower level modules.
7.4.2. Top down approach
This type of testing starts from upper level modules. Since the detailed activities usually
performed in the lower level routines are not provided stubs are written. A stub is a module shell
called by upper level module and that when reached properly will return a message to the calling
module indicating that proper interaction occurred. No attempt is made to verify the correctness
of the lower level module.
7.5. Test Cases
Module: Existing user
File name: User
Test
Case
Input Login Output Desc
Valid
login
Username
, pwd.
Success Success Test Passed. Control
transferred to menu.
Invalid Username, Failed Failed Test Passed. Try again.

Login pwd.
Fig.7.5.1.user test case
 User test case shows us the various tests of user login when he or she enter user name
and password server checks entered values with registered values of users if it match
with registration data base values control menu will transfer to user.
 If user enter a invalid user name and password then user get a page that shows try again
 Control menu cannot send to the user unless he or she enters a correct user name and
password.
Module: Multiple times accessing
File name: Informed user
Test Case Input Exp output Act output Desc
Single User
with many
privileges
User Info. Execute
according to no.
of privileges
Execute
according to no.
of privileges
Test Passed.
Client
registered.
User with one
privilege
User Info. More than one
time fails
More than one
time fails
Test Passed for
one time.
Fig.7.5.2.informed user test case
 Informed user has two test cases first one is user with many rights and user with
one right.
 This two users give their information to the server as input and server executes
With their privileges and register the users.

8. SCREEN SHOTS
1. Home Page
Fig.8.1. home page of the application
1. The above figure is home page of the application whenever we open the application first we
see this page.
2. This home page has some contents they are Login, Proxy, Server, About.
3. content “About” descript the details of developers, the purpose of the application.
4. By clicking on login user can log into his/her account.
5. Proxy Server are the data providers to the requested user’s.

2. User Registration Page
Fig.8.2. user registration page
1. This is user registration page before using this service user has to register.
2. In the registration page user has to provide some his/her details to overcome the complication
situations while transmitting the results.

3. User Login Page
Fig.8.3. user login page
1. In this page user has to enter his/her unique user name and password to run the application.
2. User name and password are user dependent values , this values can changeable.
3. After the registration user can login into his/her account by entering his/her user name and
password.

4. User View Page
Fig.8.4. user page
1. After login user get above page and user provided with some operations they are shown in
above figure.
2. User can share his location with collaboration user by clicking on secret share.
3. User can send queries to proxy and to data server and get response from the server by
provided operations.

5. Share The Secret Message With Friends
Fig.8.5.secret messaging page
1. The above page is user secret location sharing page with another user who is also called as
informed user.
2. By sending a secret message user get a secret key from informed user.
3. My id is the present user registration id ,friend id is nothing but id of the informed user id,
And user send’s a random message from his/her Email to the informed user to get collaborate
with another user.

6. Proxy Login
Fig.8.6. proxy login page
1. Proxy server log’s into its account automatically in the background process after user put a
query to it.
2. Proxy does this by entering its proxy name and password, proxy name is just like a user name
to it.

7. Proxy Send The Index To Index Server
Fig.8.7. proxy sending page
1. The above pictures show the details of different users who are sent a query request to proxy
server.
2. Whenever proxy receives a query request from user then it sends the user details to the index-
server.

8. Index Server Login
Fig.8.8. index server login
1. This page shows the login details of index-server, index server is also logs into its service by
entering the user name and password.
2. Index server is the intermediate server between proxy server and main server which transmits
data between proxy and main server.

9. Server Login
Fig.8.9.server login page
1. Server automatically logs into its account whenever it receives a query of user request from
index server.
2. Server also has its unique user name and password like proxy and index server.
3. After login server sends a secret key of the collaboration user to the user’s mail.

10.User Secret Key
Fig.8.10. user secret key page
1. The above figure is the mail picture of the user which he/she gets from the main server.
2. In that mail user gets a secret key to collaborate with informed user and to access his required
location without revealing his private data from informed user account.

11. Request for getting index from proxy
Fig.8.11. request for getting index from proxy page
1. This figure shows the secret login of the user to request for getting index of requested query
from the proxy.
2. Main user gets the secret key from the server and logs into informed user account using secret
key and he request the proxy for getting the index of his/her requested query.

12. Proxy View The Request From User And Forward That Request To Index
Server
Fig.8.12.proxy forward the user request to index server page
1. The above page shows the request of the various users who are sent a request to the proxy.
2. In the next step proxy view the user’s queries and it sends those requests to index server.
3. By clicking on send to server proxy forwards the user request to index server.

13. Index Server Login And View The Details For User Request And Provide
The Index Details To Proxy
Fig.8.13.index server providing user request details to proxy server page
1. It is the index server reply page to the proxy server of respected user queries.
2. Index server forwards the received query from proxy to server and server replies to the index
server and index server sends the received information to proxy.
3. By clicking on send to proxy, index server provides the request details to the proxy.

14. Proxy Login And Give The Response To Requested User
Fig.8.14.proxy sending response to requested user page
1. After getting reply of the query from the index server, proxy server sends the final location
result to the user of his/her request.
2. On clicking send to user, proxy sends the all requested details to user.

15. User result
Fig.8.15.user result page
1. It is the user required location which user gets from the proxy through collaboration without
reveling his/her private details.

9. CONCLUSION
We have proposed a novel approach to enhance the privacy of LBS users, to be used
against service providers who could extract information from their LBS queries and misuse it.
We have developed and evaluated MobiCrowd, a scheme that enables LBS users to hide in the
crowd and to reduce their exposure while they continue to receive the location context
information they need. MobiCrowd achieves this by relying on the collaboration between users,
who have the incentive and the capability to safeguard their privacy. We have proposed a novel
analytical framework to quantify location privacy of our distributed protocol. Our epidemic
model captures the hiding probability for user locations, i.e., the fraction of times when, due to
MobiCrowd, the adversary does not observe user queries. By relying on this model, our Bayesian
inference attack estimates the location of users when they hide. Our extensive joint
epidemic/Bayesian analysis shows a significant improvement thanks to MobiCrowd, across both
the individual and the average mobility prior knowledge scenarios for the adversary. We have
demonstrated the resource efficiency of MobiCrowd by implementing it in portable devices.
Future Enhancement
We have developed a secured process for the users to get required information from the
location based service with out using the trusted third parties and introduced a mobi crowd
schema that deletes all the private information of registered users when they request the proxy
server for a query. It is a easy process to get effective results of our proposed system. And this
entire proposed system is developed with java language .java is object oriented language and
platform independent that can any operating system.
Basically this application developed only for the android users and we can easily
implement it for windows users and for Mac users. For this java has packages by using this java
packages every one can implement this secure service to the all type of users i.e. windows, Mac,
recently Microsoft released MS-DOS mobile so who has basic knowledge in java they could be
develop this for all types of operating system.

10. REFERENCES
URL:
1. http://www.pleaserobme.com.
Articles:
1. J. Meyerowitz and R. Roy Choudhury, “Hiding stars with fireworks: location privacy through
camouflage,” in MobiCom ’09: Proceedings of the 15th annual international conference on
Mobile computing and networking, 2009.
2. F. Olumofin, P. K. Tysowski, I. Goldberg, and U. Hengartner, “Achieving efficient query
privacy for location based services,” in Privacy Enhancement Technologies (PETS), 2010.
3. G. Ghinita, P. Kalnis, A. Khoshgozaran, C. Shahabi, and K.-L. Tan, “Private queries in
location based services: anonymizers are not necessary,” in Proceedings of the ACM SIGMOD
international conference on Management of data, 2008.
4. R. Anderson and T. Moore, “Information Security Economics– and Beyond,” Advances in
Cryptology-CRYPTO, 2007.
5. R. Shokri, J. Freudiger, M. Jadliwala, and J.-P. Hubaux, “A distortion-based metric for
location privacy,” in WPES ’09: Proceedings of the 8th ACM workshop on Privacy in the
electronic society. New York, NY, USA: ACM, 2009, pp. 21–30.
6. M. Piorkowski, N. Sarafijanovic-Djukic, and M. Grossglauser, “A parsimonious model of
mobile partitioned networks with clustering,” in Proceedings of the First international conference
on Communication Systems And NETworks, 2009.
Text Books:
1. R. Shokri, G. Theodorakopoulos, J.-Y. Le Boudec, and J.-P. Hubaux, “Quantifying location
privacy,” in IEEE Symposium on Security and Privacy, Oakland, CA, USA, 2011.
2. J. Krumm, “A survey of computational location privacy,” Personal Ubiquitous Comput., vol.
13, no. 6, pp. 391–399, 2009.
3. R. Shokri, J. Freudiger, and J.-P. Hubaux, “A unified framework for location privacy,” in
HotPETs, 2010.

azd document

More Related Content

What's hot (18)

Similar to azd document (20)

azd document