In our safe tourister application we aims to outsource the lbs data from the lbs provider to the cloud and from the cloud to the lbs provider which protects the privacy related issues of the lbs data. Initially lbs user query for a place to the lbs provider, lbs provider in turn upload the details to the cloud but in the form of encrypted text to prevent the cloud from stealing the data. Lbs users in turn decrypt the details by the personal password send by the lbs provider to the lbs user. When the query of the lbs user matches the details in the cloud the lbs user will retrieve the details and make use of it. In this application it is shown with the demo of a tourist requesting for tourist places tourist is the lbs user and admin is the lbs provider .With the pervasiveness of smart phones, location based services (LBS) have received considerable attention and become more popular and vital recently. However, the use of LBS also poses a potential threat to user’s location privacy. In this paper, aiming at spatial range query, popular LBS providing information About POIs (Points of Interest), we present an efficient and privacy-preserving location based query solution, called EPLQ. To reduce query latency, we further design a privacy-preserving tree index structure in EPLQ. Detailed security analysis confirms the security properties of EPLQ. In addition, extensive experiments are conducted, and the results demonstrate that EPLQ is very efficient in privacy preserving spatial range query over outsourced encrypted data. In particular, for a mobile LBS user using an Android phone, around 0.9 second is needed to generate a query; and it also only requires a commodity workstation, which plays the role of the cloud in our experiments, a few seconds to search POIs.
OSVC_Meta-Data based Simulation Automation to overcome Verification Challenge...
EPLQ: Efficient Privacy for Location Queries
1. EPLQ: Efficient Privacy-Preserving Location-based
Query over Outsourced Encrypted Data
ABSTRACT:
In our safe tourister application we aims to outsource the lbs data
from the lbs provider to the cloud and from the cloud to the lbs provider
which protects the privacy related issues of the lbs data. Initially lbs user
query for a place to the lbs provider, lbs provider in turn upload the
details to the cloud but in the form of encrypted text to prevent the cloud
from stealing the data. Lbs users in turn decrypt the details by the
personal password send by the lbs provider to the lbs user. When the
query of the lbs user matches the details in the cloud the lbs user will
retrieve the details and make use of it. In this application it is shown
with the demo of a tourist requesting for tourist places tourist is the lbs
user and admin is the lbs provider .With the pervasiveness of smart
phones, location based services (LBS) have received considerable
attention and become more popular and vital recently. However, the use
of LBS also poses a potential threat to user’s location privacy. In this
paper, aiming at spatial range query, popular LBS providing information
About POIs (Points of Interest), we present an efficient and privacy-
preserving location based query solution, called EPLQ. To reduce query
latency, we further design a privacy-preserving tree index structure in
EPLQ. Detailed security analysis confirms the security properties of
EPLQ. In addition, extensive experiments are conducted, and the results
demonstrate that EPLQ is very efficient in privacy preserving spatial
range query over outsourced encrypted data. In particular, for a mobile
LBS user using an Android phone, around 0.9 second is needed to
generate a query; and it also only requires a commodity workstation,
which plays the role of the cloud in our experiments, a few seconds to
search POIs.
2. The safe tourister consists of two modules they are:
LBS provider.
LBS user.
LBS provider in turn consists of three modules. They are:
User Details.
View Query.
Send Password.
LBS user consists of three modules. They are:
View Details.
Send Query.
Route.
In the lbs user module send query category consist of the list of tourist
spots, on choosing the tourist spot the user will be directed to the query
sending module in which the has to generate their id and send that to
admin to view details .In turn the admin (LBS provider) will see to the
user details in the user details module of the lbs provider and their query
in the view query module. After viewing the query the lbs provider will
encrypt the details and send it to the cloud and the password to decrypt
the encrypted text to the user through personal mail. Again in the lbs
user module the user have to enter their id to get the details from the
cloud but the received data will be encrypted and at that time the user
has to use the personal key send to him through the mail service by the
lbs provider. After successfully decrypting the results, the user can see a
list of tourist spots in the queried place and on choosing the place he will
be able to receive the hotels around the place in turn he also find the
distance and time taken to reach the hotel.
3. EXISTING SYSTEM:
The LBS provider is not willing to disclose its valuable LBS data to the
cloud. The LBS provider encrypts and outsources private LBS data to
the cloud, and LBS users query the encrypted data in the cloud. As a
result, querying encrypted LBS data without privacy breach is a big
challenge, and we need to protect not only the user locations from the
LBS provider and cloud, but also LBS data from the cloud. Privacy-
preserving query usually result in high computational cost and/or storage
cost at user side. Spatial range query is an online service, and LBS users
are sensitive to query latency. To provide good user experiences, the
POI search performing at the cloud side must be done in a short time
(e.g. a few seconds at most). Again, the techniques used to realize
privacy-preserving query usually increase the search latency.
DISADVANTAGE:
Challenge on querying encrypted LBS data
Challenge on the resource consumption in mobile devices
Challenge on the efficiency of POI searching
Challenge on security
Lack of accuracy. It is very burden to Users.
Lot of paper works.
PROPOSED SYSTEM:
The LBS provider has abundant of LBS data, which are POI records.
The LBS provider allows authorized users (i.e. LBS users) to utilize its
data through location-based queries. Because of the financial and
operational benefits of data outsourcing, the LBS provider offers the
query services via the cloud. However, the LBS provider is not willing
to disclose the valuable LBS data to the cloud. LBS users have the
information of their own locations, and query the encrypted records of
nearby POIs in the cloud. Cryptographic or privacy-enhancing
4. techniques are usually utilized to hide the location information in the
queries sent to the cloud. To decrypt the encrypted records received
from the cloud, LBS users need to obtain the decryption key from the
LBS provider in advance. The cloud has rich storage and computing
resources. It stores the encrypted LBS data from the LBS provider, and
provides query services for LBS users. So the cloud has to search the
encrypted POI records in local storage to find the ones matching the
queries from LBS users
ADVANTAGE:
Efficiency, many resources of mobile LBS users, and the POI
search latency should be acceptable for online query.
Accuracy, desirable that a query result contains exact the records
matching the query.
Security, Lbs data from the lbs provider is secured by means of
encryption.
Reduce time for searching the route between the locations. Gives
accurate details about the current location.
ARCHITECTURE DIAGRAM:
5. MODULES:
The safe tourister application consists of two modules .They are:
LBS provider.
LBS User
ADMIN:
The LBS provider module consists of three categories they are:
User details
View query
Sending password
User details:
In the user details category the Lbs provider can view the user details
that registered and can use the details to send password.
View query:
In viewing query the admin will view the query send by the user and
encrypt the data and send it to the cloud and in turn lbs user will retrieve
the information from there.
Sending password:
By verifying the details of the user from the user details the admin will
send the decryption password to the user personal mail id. From where
user can decrypt the details.
USER:
The LBS user module consists of three categories they are:
View details
Send query
6. Route
Send query:
In the lbs user module send query category consist of the list of tourist
spots, on choosing the tourist spot the user will be directed to the query
sending module in which the has to generate their id and send that to
admin to view details .In turn the admin (LBS provider) will see to the
user details in the user details module of the lbs provider and their query
in the view query module.
Route:
Finding route the user can find his route with distance to reach his
destination along with the time taken to reach the distance.
View details:
In the lbs user module the user have to enter their id to get the details
from the cloud but the received data will be encrypted and at that time
the user has to use the personal key send to him through the mail service
by the lbs provider. After successfully decrypting the results, the user
can see a list of tourist spots in the queried place and on choosing the
place he will be able to receive the hotels around the place in turn he
also find the distance and time taken to reach the hotel.
ALGORITHM TECHNIQUES:
Encryption algorithm:
A mathematical procedure for performing encryption on data. Through
the use of an algorithm, information is made into meaningless cipher
text and requires the use of a key to transform the data back into its
original form.
7. Decryption algorithm:
Decryption is the process of taking encoded or encrypted text or other
data and converting it back into text that you or the computer can read
and understand. This term could be used to describe a method of un-
encrypting the data manually or with un-encrypting the data using the
proper codes or keys.
Encrypted key verifying algorithm:
Encrypted key verification algorithm is one aspect of
testing a product's fitness for purpose. Validation is the complementary
aspect. Often one refers to the overall checking process. Verification
algorithm for any valid input it produces the result required by the
algorithm’s specification.
Time complexity algorithm:
The time complexity of an algorithm quantifies the amount of time taken
by an algorithm to run as a function of the length of the string
representing the input :226. The time complexity of an algorithm is
commonly expressed using big O notation, which excludes coefficients
and lower order terms
SYSTEM SPECIFICATION:
HARDWARE REQUIREMENTS:
System : Pentium IV 2.4 GHz.
Hard Disk : 40 GB.
Floppy Drive : 1.44 Mb.
Monitor : 14’ Colour Monitor.
8. Mouse : Optical Mouse.
Ram : 512 Mb.
SOFTWARE REQUIREMENTS:
Operating system : Windows 7 Ultimate.
Coding Language : Java.
Front-End : Eclipse.
Data Base : SQLite Manger.
CONCLUSION:
Thus the safe tourister application we explained the EPLQ technique
that is the lbs user querying the poi to the lbs provider the lbs provider in
turn issue the result to the cloud but the provider don’t want to share the
raw information so he encrypt the information and share it to the cloud
in turn the lbs user query when matches the information the cloud will
issue the result to the user. The cloud has rich storage and computing
resources. It stores the encrypted LBS data from the LBS provider, and
provides query services for LBS users. So the cloud has to search the
encrypted POI records in local storage to find the ones matching the
queries from LBS users. The user will decrypt the data by the private
key shared by the admin. And see to the nearby hotels in the tourist spots
and also the distance between him and the hotel.