Unit-V Mobile Ticketing
Unit-V Mobile Ticketing
Unit-V Mobile Ticketing
1. One commuter bought a monthly season ticket using the app, but could not access it when he
changed his handset.
2. Another commuter booked a ticket three times; the money was debited from his account
thrice, but no ticket was issued.
3. The UTS app does not work if the user is either less than 30 m away, or beyond a 2-km radius
around railway stations. No pop-up notification indicates range.
4. The app is not available on iOS, which means iPhone users cannot access it.
5. Passengers are charged extra internet handling fees by different gateways for booking tickets.
6. ATVM, CoTVM and Go India smart cards can’t be recharged via the app.
7. R-Wallet has a recharge limit of Rs 5,000 unlike ATVM, which has a limit of Rs 10,000.
The mobile ticketing in public transportation is a
form of electronic ticketing which provides an easy way to
use mobile phone as a travel card in which user can also
purchase tickets anywhere, anytime via mobile internet.
In this technique, travel card readers sense the data inside
mobile phones using RFID or similar technology to validate
the ticket.
Privacy and Security issues
The Near Filed Communication (NFC) or RFID technology is used in such
service which integrates mobile tickets and mobile payments. By using
this technology, travel card readers cannot distinguish the mobile phone
from travel card. Mobile phone works as a travel card even when battery
is depleted.
Several high-end mobile ticketing applications also allow user to access
locations, calendar, and journey planner while integrating them with
ticketing and payment system.
Users can also opt for receiving discount coupons and advertisements
based on their locations or journey route.
Though mobile ticketing makes travel stress-free, certain user privacy and
security concerns should be taken care of.
The mobile phone contains user data and because of this, privacy mechanism
and confidentiality settings are essential while exposing mobile devices to the
card readers.
Also some mobile-ticketing applications provide users with location based
services, journey planner and calendar integration making applications vulnerable
to user privacy breaches.
The payment solution and ticketing mechanism should be secured with powerful
network security techniques while preventing user information leaks.
Business modeling of mobile services is important but most of the time, security
and privacy issues are ignored while designing such models.
In such service designs, trusted parties and security providers should be
engaged throughout the process and service provision
Mobile devices can be used just like the ordinary card even when the
battery of mobile device is depleted.
5. Impersonation Attack:
Unauthorized entities in mobile-ticketing can provoke this attack by faking the user
identity. Underlying protocols may fail to prevent man-in-the-middle as well as replay
attacks on the system and such attacks may lead to the impersonation.
6. Tracing Attack:
This attack can be done to acquire user sensitive information like user’s location,
behavior and preferences. When using authentication mechanism, to-ken can be
identified enabling attackers to trace user movements. If user uses payment method to
purchase online tickets, the issuer can use link token to identify user’s private
information. Also eavesdropping of wireless communication may lead to a complete
loss of user’s privacy.
Privacy Requirements Based upon privacy risk analysis in previous section,
several requirements are gathered and illustrated as below for mobile-ticketing
service:
1. Confidentiality: No unauthorized access to user-sensitive and personal
data.
2. Anonymity: Unauthorized token (NFC Tag) identification should be
impossible.
3. Location Privacy: Unauthorized tracing of user location and movements
should not be allowed.
4. Traceability: Accessing current state of NFC token should not allow tracing
previous as well as future protocol runs.
5. Authentication: No unauthorized users are allowed to
use or access system. Only valid user tokens are accepted by verifier.