Rail Ticketing System (RTS) is the base application system for Ticketing Service Provison where other application software(s) can be built around it. In the core of the RTS, a data aware executable component (a custom built Servlet) named “Core Ticketing Engine (CTE)” resides as memory resident program (TSR). The CTE takes care of accepting (or rejecting) ticket issue/refund/reservation requests, validating the same and storing the values into resident database instance over the cloud only to retrieve the same upon similar request. There being no other interface than a specially built API (Application Programming Interface), it can only listen to a secured port after Diffie–Hellman Key Challenge and Necessary key exchanges between the client and the server (the caller and the responder) has been performed appropriately as per set protocol. The session would be necessarily encrypted with DES3 Algorithm and this would provide brick solid security at network and software level abstracting database with the API and would also provide security against phishing and packet sniffing by intruders.
The innovative technology enables Railway Operator Company or the Cleint to use the CTE as a web service secured enough to be used as a servlet to cater any and all requests using industry standard JSON/SOAP data structure. To Bangladesh Railway, in plain English, this means that any standard device, application, software, database or web service can consumethe core ticketing engine service’s data providing endless possibilities to include mobile ticketing, internet based ticketing and of course traditional ticketing from POS counters from application software built around the core ticketing engine. Messaging, Storage and Web platforms can also be pushed through the API to host the entire system on top of the Cloud Computing Platform.
The importance of having a core ticketing engine adaptable to industry standard generic web service is enormous. Rapidly changing technology is a challenge for most of the large investment projects where technology limits itself to adaptation impairments. Use of RESTful API with well perceived data consumption ecology enables the Clients to introduce any newer technology on top of the core ticketing engine. This will also enable general public to discover the services being provided through popular social networking sites like Facebook or simply through an app downloadable from Android Marketplace. On top of that, with the increasing popularity of Cloud Computing, the entire system can be hosted over the cloud providing platform, protocol and storage to the users in Client Users.
The System has four major aspects :
- Counter Based Point of Sales (POS) Application in Railway Counters
- Mobile Based Ticketing (mTicketing) System (Click Here to Download White Paper)
- Web Based eTicketing System (Click Here to Download White Paper)
- Single Point Reconciliation and Back Office System for Railway Ticketing