Masabi Rail Ticketing ITS


Published on

Slides from Ben Whitaker's talk about new mobile ticketing approaches for public transport including mobile payments via credit card this month at the UK's ITS Passenger Information Interest Group's seminar on Options for Ticketing and Standards in Ticketing on the 27th May 2009 in London.

Highlights of new features in the UK's Rail Barcode Ticket standard, and a brief summary of the lower capital expenditure soft-rollout of visual barcode ticketing on paper and mobile versus the large up-front costs of smartcard. Finally a summary of selling tickets from the mobile phone, and the benefits it brings to the operator.

Published in: Technology, Business
1 Like
  • Be the first to comment

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Masabi Rail Ticketing ITS

  1. 1.  Masabi build mobile applications  Award winning and certified security  Ticket sales and delivery from mobile  Projects: Consultancy supporting the standards Rail Settlement Plan work on self-print and mobile barcodes mobile tickets for Business Rail ticket sales ticket sales from mobile (’07 – ‘08)
  2. 2.  Contactless RF  Smart-Card ITSO, Oyster, Mi-Fare  NFC Phones Dependant on scanning hardware  Barcodes  Self-print  Mobile Soft rollout option with visual inspection
  3. 3.  Avoid up-front cap-ex on full barcode scanner rollout  Visually inspect at launch  Staff report barcode ticket usage levels each week  Occasional SMS or scan checks (Can add  Staged scanner rollout for an animated watermark to aid routes with significant adoption visual inspection)
  4. 4.  Oyster for London  Price incentives drive public uptake Single Fare: Paper £4; Oyster £1.60  Massive capital expenditure before launch Resistance from overland rail to accept same fees  National Smartcard Questions: ▪ Will tickets be as heavily discounted? ▪ Will it be as widely adopted by public? ▪ How long will it take to recoup Cap-Ex?
  5. 5. RSPS3001 Approved in December 2008 as the UK standard for self print and mobile barcode rail ticketing
  6. 6.  Share self-print and mobile barcodes between TOCs, TIS and 3rd party retailers  Public and open security  Based on PKI, standard SSL certificates  Optional ITSO seal, but not required  Decentralised system - robust  Cheap to implement and use
  7. 7. ITSO and Oyster PKI is Asymmetric are Symmetric =Different Keys =Same Keys Private key to create ticket Private key to create (safe on TIS server) ticket Private key to Public Key to check ticket check ticket (some risk from key theft) (no risk from key theft)
  8. 8.  Traceability, and no security risk from theft of scanning devices  If private keys are leaked, only the vendor that loses the keys is affected  3rd parties and other EPOS vendors can take part, even taxis and coffee shops can scan and validate cross-sale tickets or entitlements
  9. 9.  More free space for single TOC products and extra entitlements “Includes free cup of Costa Coffee and 2 Adults entry to Alton Towers”  ITSO Seals included, but optional  Allows non-ITSO and ITSO enabled TOC’s to inter-operate
  10. 10.  Any barcode scanner, online or off-line, must support: 2D Aztec with CCD imager Basic Advanced  Handheld  Small basic scanners for door staff Bluetooth  Advanced PDA based scanners for service staff  Bluetooth scanner upgrade for Avantix Mobile 2  Cash Register/EPOS Scanners EPOS Scanner  Connect via USB or as “keyboard wedge” in between keyboard and EPOS like a normal scanner Retro-fit  Fixed Scanners for gates or check-outs Fixed / gate scanner  Retro-fit to existing gates, user places phone on rubber face to scan  Or built in at manufacture by gate supplier
  11. 11.  Offline validation from software  Add to existing EPOS or gate systems  No mobile databases required  No synchronisation of valid tickets from one TOC to another (too much data, too unreliable)  Walk-up tickets
  12. 12.  Isn’t it easy to photocopy a self-print paper ticket?  What if a bunch of clever people figure out how to copy mobile tickets?  What if one user copies a ticket, gets onto an off-line train, and his friend gets onto a second off-line train?
  13. 13.  Scanners only accept first seen barcode  On-line scanners can check for previous scans at other locations  Off-line scanners submit scan records back to ticket issuer for post-processing  Post processing identifies dual use, and blocks future purchases from the same credit card until fine paid, limiting fraud
  14. 14.  Only 12% of rail tickets sold on the internet – most bought at station  Over 2/3 of mobile users never complete their sign-up if it’s on the web  So: Sign up the users when they need it  in a queue  in a hurry  next to a broken ticket machine
  15. 15.  WAP / xHTML  Browser based, like on the web  No javascript or Ajax on ~90% of mobiles  Application  Installed on the phone  Dedicated, customised
  16. 16.  Still useful without a continuous data connection  Optimised data entry  Faster responses  Catch mistakes quicker  SMS failover from GPRS  Avoid settings, reception & roaming problems  Cheaper + faster for the user  Send only the data  Flat rate data is still not common
  17. 17.  Early WAP:  WTLS – not true security  New WAP2  Vodafone breaks HTTPS, breaks PCI  Merchant’s policy decision on acceptable level of security  Most agree that credit card sign-up should not happen over broken WTLS or HTTPS  Results in sign-up on WEB only, like Trainline
  18. 18.  No sign-up process  no usernames  no passwords  Mostly off-line interface, SMS backup  Fast repeated regular purchases  Auto-show tickets, full screen barcodes
  19. 19. 95% of trial users said: “better than the IVR system we used until now”  Payments straight from phone  No need for explicit sign-up or passwords  Just type CVV again for future purchases  All user data entry and validation performed off-line by application  Secure SMS for users without data settings or with poor reception  New user can sign-up and pay in just one SMS
  20. 20. Chiltern Railways with YourRail Trial user feedback: “Better than the web!”  Buy anywhere  No paper, no queues - barcode tickets  Tunnels aren’t showstoppers!  Auto-detects SMS or GPRS  1-2 SMS per ticket  Doubles the consumer uptake by removing Data issues  Quick repeat tickets  Customer loyalty and lock-in
  21. 21.  Two snags against mass-adoption of the existing SMS/MMS tickets 1. User delay in finding ticket before gate customers manually searching the phone’s lists of messages/images to find today’s ticket Answer: application auto-shows today’s ticket 2. Some phones don’t scan successfully Guards simply don’t scan certain phones, and customers know the gates won’t let them through without manual intervention Answer: application displays full-screen Aztec for scanner
  22. 22.  Instant sign-up from the queue  Give everyone a personal ticket machine  Soft rollout to avoid cap-ex  Customer behaviour tracking and targeted SMS offers  Cross-sales to raise margins
  23. 23. Masabi Proxy Retailer Web (can be hosted by retailer) Services SMS “Tickets” to 89080 1 2 Auto-Install SMS 3 Purchase Request and Payment Details 4 (sent by encrypted SMS or Data from the mobile application) XML Web Service Requests 5 Success message with content, ticket or code
  24. 24.  Optimise for the regular use cases  Make them fast and obvious  Allow advanced search for users that choose it  Dynamic interface can expand options  Enable goal seeking for ▪ Cheapest Advanced tickets, with maximum date/time range ▪ Off-peak services ▪ Advanced/non advanced
  25. 25.  Full-Screen Barcode Display on Mobile  Size = speed and reliability of scanning  More reliable than SMS, MMS or WAP delivered barcodes  Off-line Scanning  Allows for total loss of site WiFi / Internet connectivity or loss of the central ticket server  Secure Barcodes  PKI barcode signatures prevent modification of tickets by criminals  Public Key Validation allows any 3rd party vendor or EPOS till integrator to scan and check tickets