1-i2ct_submission_1036

Suburban Bus Ticketing System using QR Code
Sayali R. Bhojane1
,Vikrant P. Sapkal2
, Sagar A. Bandekar3
Prof. Pramod Patil, Assistant Professor, NMIET, Talegaon Dabhade, University of Pune.
Prof. Shweta Bhandakkar, Assistant Professor, NMIET, Talegaon Dabhade, University of Pune.
1
Student, NMIET Talegaon Dabhade, Pune, sayalibhojane2511@gmail.com.
2
Student, NMIET Talegaon Dabhade, Pune, vikrantsapkal2403@gmail.com.
3
Student, NMIET Talegaon Dabhade, Pune, sagar.bandekar16@gmail.com.
Abstract- In the fast technological world the fast paced life needs
quick and fast ticketing system. But the existing system does not
provide much of the facilities to the people. While travelling
through the public transit systems people have to wait in the
queues and also wait for long time in buying the tickets and
sometimes validating the tickets from the ticket checker. The
present system provides tickets for long and local tickets through
the traditional systems like paper tickets and through the mobile
ticketing system. In the proposed system the GPS helps to
allocate the end points of the destinations and helps to assist them
to reach the particular destination. The system also helps to
provide a backup system which is dynamic to the user and the
checker also. In case of some time that user’s mobile phone is
switched off the user can validate the ticket through the user id
provided to him. The system also helps to the curb the theft full
activities that some of the customers carry out in local areas. The
proposed system also gives the user friendly interface for quick
and comfortable usability.
Keywords: Android; SQLite; Cloud Database; QR code;
I. INTRODUCTION
Now days we are all in hurry and we almost travel by buses
once or more than once. The main problem adheres at the peak
hours. During peak hours we are in a hurry and we are not
able to buy tickets due to crowd through the conductor. Many
a times we are unable to buy the tickets and may fall into the
hands of the ticket checker which might make the situation
undesirable . There many other problems that includes taking
undue advantage of the rush and traveling without ticket by
the commuters. In order to curb such activities and to provide
a proper smooth flow, the proposed system helps to overcome
such issues.
The system firstly provides to a registration system that is
carried out by the server. After registration the user may
choose the tickets. The server provides each user with a
separate account to make the payment for the tickets. While
buying the ticket the user has to choose the destination
previously before boarding the bus. The QR code gets
generated from the server after the request is sent by the user
for the ticket. If the user provides with a fake ticket then he
would get the star strikes. Making a Five star strike then he
would have pay fine and then he may continue. The
application would provide a timer after which the ticket is
being received by the user. After the particular time span the
ticket would become useless and would get automatically
deleted from the application. If there a problem of the mobile
device being getting low battery then a particular message
would be sent to the server about the information about the
battery and it would be kept in the database. When the ticket
checker comes for checking the ticket the user just has to
provide up the user Id then the checker would get the
information about all the past three tickets purchased by the
user. In this way it would save the time of checking the ticket
and validating it. The server is governed by the administrator
which is capable of adding routes and the locations in to the
system. The system is quick and effective in providing the
services.
II. LITERATURE SURVEY
The system prevailing in the society for as now are the paper
tickets, mobile bookings and online reservations. Even though
such systems are prevailing in the present era issues related to
the system as such are many. Considering the following
mentioned systems, we can brief as follows.
A. Paper tickets
This kind of ticketing system is the most prevalent in the
existence but the main drawback relies in the form of presence
of the ticket which is the paper. Paper is perishable and any
one can manipulate the ticket and can present it and can fool
the control structure. They are also small in size and can get
lost easily and also any one can travel through the ticket and
can transfer to the other person.
B. Smart cards
Smart cards are yet another form of the ticketing system better
than the paper tickets. These could be used any time and
dynamic ticketing could be done. The problem that even this is
also not much prevalent in the market is that there is a need to
recharge the smart card from regular intervals and also at
specific stations only which are tedious and static in nature.
Also the card may get lost as the size is small.
C. Online tickets
Online booking of the tickets is a major and effective way of
buying the tickets but this is not compatible with the fast
paced life of the people where he has to go on the net for the
tickets to be booked and also the system is for the local transit
where dynamic ticket booking is needed. This system is best
suited for the areas where long distance tickets could be
booked.
International Conference on Convergence of Technology - 2014
978-1-4799-3759-2/14/$31.00©2014 IEEE 1

D. Mobile tickets
Mobile tickets can be an option for booking of the tickets.
These are much more proper than the existing ones. They
provide tickets through the mobile phones only and it is a
thing that can’t be lost. The reason that it could not be used
that even after manipulation of the ticket trough the ticket the
ticket checker can’t make out whether the ticket can be valid
and authorized or no and in the later sense the if the mobile
phone’s battery dies out then the person can’t show his ticket
and is left stranded.
III. FEATURES
A. QR Code
A QR code (“Quick Response”) is a two dimensional matrix
code designated for the industry due to its fast readability and
large storage capacity.
Table 1: Main QR Code Specification
Item Specifications
RS code Data
Error correcting Formation
information
code BCH code
Version
information
10 bits coding
Number Per 3 Number
digits
Characters Alphanumeric
11 bits coding
per 2 characters
8 bit byte 8 bits coding
Kanji
13 bits coding
per 2 characters
1 21×21 modules
Version
2 25×25 modules
40
177 × 177
modules
Error correcting
L about 7%
M about 15%
level Q about 25%
H about 30%
3 cocentric
Finder pattern 1 :1 :3 :1 :1
squares
7×7, 5×5, 3×3
modules
3 cocentric
Alignment pattern
squares
1 :1 :1 :1 :1 Higher version 2
5×5, 3 ×3
modules
It consists of black modules arranged in a square pattern one
white background. Pattern like finder pattern, separators,
timing pattern, alignment pattern, format information, data,
error correction, reminder bits etc.
If higher error correction level, then it increase the percentage
of codeword used for error correction.
Fig 1: QR code
B.C2DM Service
The Android Cloud to Device Messaging Framework (C2DM)
Service is a communication mechanism which is interface
between server and mobile application. The C2DM handles
queuing of messages and delivery to its client Android mobile
application. The application must register with C2DM servers
before service becomes active for updated application or user
data.
C. SQLite Database
SQLite is a relational database management system contained
in a small C programming library. SQLite is not a separate
process that is accessed from the client application, but an
integral part of it. SQLite stores the entire database
(definitions, tables, indices, and the data itself) as a single
cross-platform file on a host machine. A standalone program
called sqlite3 is provided that can be used to create a database,
define tables within it, insert and change rows, run queries and
manage an SQLite database file. This program is a single
executable file on the host machine. It also serves as an
example for writing applications that use the SQLite library.
IV. ARCHITECTURE
Fig 2: Architecture
978-1-4799-3759-2/14/$31.00©2014 IEEE 2

Table 2: Abbreviations
Meaning
MEI H(PN+ID)
PN The user’s phone number registered in server
ID The user’s ID registered in the device
PW The user’s password registered in the device
RSN Random Serial number
Key AES 128 bit key
H() Hash function
TS Time stamp
QR code Generating Protocol
Through the following processes, creation and transmission of
QR code is done.
Step 1. A user requests access from outside. The server
acquires the user's general information (User name, Password,
Name, Address, etc). The acquired user information is
processed to form a CI.
CI : H(Client Information)
(1) After the initialization of the device it request for
authentication, a RSN (Random Serial Number) is generated
to match it (user name and password), and a key is created to
encode or decode the QR code's content by using AES
algorithm. AES (Advanced Encryption Standard) is based on
a design principle known as a substitution-permutation
network, and is fast in both software and hardware. It has
block and key sizes that may be any multiple of 32 bits, both
with a minimum of 128 and a maximum of 256 bits. When a
QR code is created, its Encryption_Value should be encrypted
with a key by using XOR of RSN and CI so as to keep the user
information unchanged.
Encryption_Value :
EKEY(H(RSN XOR CI))
(2) After all the values as data are created; a QR code is
generated by using Encryption_Value, RSN, TS, and CI.
QR code : Encryption_Value||RSN||TS||CI
(3) Step 2. The generated QR code is transmitted to the user.
Step 3. The user requests the server, through the device, to
check out whether the ticket verification is done via ticket
checker.
V. SYSTEM DESIGN
A. Subjective Data
During first time installation of application user must submits
basic information like name, address, mobile number, etc. and
it will be stored in database for user authentication. So when
user wants to buy the ticket this customer information is sent
to the cloud database for security purpose.
B. Ticket Buying
Whenever user wants to buy the ticket he/she selects source,
destination, class, number of children’s and adults, ticket type
like single or return, etc. After that user buy the ticket by using
credit cards. Once the user selects the buy option it moves on
to the pin code validation.
C. Code validation
Once user selects buy option then server validates the pin
number and passwords. If it authenticated then it saves both
the travelling details and user information in the server’s
database. After that ticket number is generated and balance
value is displayed on user’s application.
D. Generating QR Code
Once the code generates ticket number and other details saved
in the database are sent to Google Chart API engine for
generating QR Code. In the QR code, all the user’s and ticket
information are stored in the form of matrix which is
unreadable. QR Code sent to user mobile as HTTP response
and saved in the Mobile/Application memory.
E. Checking QR Code with QR Reader
By using QR code reader checks ticket and scan the QR code
to verify authenticate user. It validates QR code and verifies
all information related with user and ticket
F. Checking with database
If there is any problem occurs related with mobile like
damaged, battery failure in that case user requests to the server
database by using ticket number and gets all information for
validation process.
ANALYSIS OF SECURITY FACTOR
Authentication
The user checks the integrity of the QR code, generated by the
server, through a RSN and key values. Since the server uses
the user’s device information which is registered in advance,
only authorized users can access the service.
Confidentiality
The data to be sent or received are completely safe from
attacks. As a series of data is consecutively transmitted
through concatenated hash functions, the transmission is safe
from sniffing and user information leakage.
Integrity
All the data are transmitted through hash processes, so the data
is prevented from being altered. The integrity is tested through
the RSN and key values to enhance reliability.
Availability
This process does not require complicated calculation or
numerous certificate authorities. It is instead fast employing
only simple hash and AES calculations. In addition, replay or
978-1-4799-3759-2/14/$31.00©2014 IEEE 3

denial of service (DOS) attacks can be solved quickly by
means of RSN and key's effective access time, having
High availability.
VI. FUTURE SCOPE
In the near future we can provide bus stop level security using
hardware devices to validate QR code. We can help user to
have navigation and real time guidance via GPS. The System
could be applicable to Local Train Transits, cabs and taxis too.
VII. CONCLUSION
In this paper we have described new ticketing system with QR
code security which can change the way of buying tickets in
future. QR code is used for storing user’s database while using
this application first time. QR code become validate using
user’s device when user enter or leaves his stop/station and
where the user can have access as user’s identification after
buying tickets. In this system the time stamp makes user start
his/her journey from source to destination and automatically
deleting ticket from user’s device (mobile) after reaching
given destination in expected time interval.
REFERENCES
[1] Karthick S and Velmurugan A (2012) “Android Suburban Railway
Ticketing System with GPS as Ticket Checker” -ICACCCT
publications.
[2] Peter Kieseberg, Manuel Liethner, Martin Mulazzani, Lindsay Munroe,
Sebastian Schrittwieser, Mayank Sinha and Edgar Weippl (2010) “QR
Code Security".
[3] N. Harini and Dr. T. R. Padmanabhan (2013) “2C Auth: A New Two
Factor Authentication Scheme Using QR Code” IJET publications.
[4] David Conde-Lagoa, Enrique Costa-Montenegro, Francisco J. Graonzalez-
Castano, and Filipe Gil-Castinei (2010) “Secure eTicket Based on QR-
Codes with User-Encrypted Content” IEEE publications.
[5] Kyeongwon Choi, Changbin Lee, Woongryul Jeon, Kwangwoo Lee and
Dongho Won (2011) “A Mobile based Anti-Phishing Authentication
Scheme using QR code”
978-1-4799-3759-2/14/$31.00©2014 IEEE 4

1-i2ct_submission_1036

More Related Content

What's hot (20)

Viewers also liked (20)

Similar to 1-i2ct_submission_1036 (20)

1-i2ct_submission_1036