1.

Introduction
In line with the ever-evolving landscape of mobile technology, this concept paper proposes the
implementation of a Mobile USSD Ticketing Service for MetroRail. Leveraging USSD
(Unstructured Supplementary Service Data) technology allows for a simple, accessible, and
efficient ticket purchasing process directly through mobile devices. This innovative approach aims
to provide commuters with a convenient and user-friendly alternative for acquiring MetroRail
tickets.
2. Objectives
The primary objectives of introducing a Mobile USSD Ticketing Service for MetroRail are:
a. Accessibility: Ensure accessibility to the ticketing service for all mobile phone users, regardless
of their device's capabilities.
b. Simplicity: Offer a straightforward ticket purchasing process using USSD menus, making it easy
for users to navigate and complete transactions.
c. Inclusivity: Cater to a diverse user base, including those without smartphones or internet access,
by utilizing the widely available USSD technology.
d. Efficiency: Streamline the ticketing process, reducing the time and effort required for passengers
to purchase MetroRail tickets.
3. Key Features
The proposed Mobile USSD Ticketing Service will incorporate the following key features:
a. USSD Code: Users will access the MetroRail ticketing service by dialing a designated USSD
code on their mobile devices.
b. Menu Navigation: A user-friendly menu system will guide passengers through ticket selection,
payment, and confirmation steps using simple numeric codes.
c. Payment Integration: Implement secure mobile payment options, such as mobile wallets or linked
bank accounts, for seamless and secure transactions.
d. Ticket Confirmation: Users will receive a digital ticket confirmation via USSD, including details
such as journey information, ticket type, and a unique identifier.
4. Benefits
The implementation of Mobile USSD Ticketing for MetroRail offers several benefits:
a. Accessibility: Extends the ticketing service to a broader audience, including users with basic
mobile phones that lack smartphone capabilities.
b. Inclusivity: Provides a ticketing solution for commuters who may not have internet access or
prefer non-app-based services.
c. User-Friendly: Offers a straightforward and familiar interface, making ticket purchases quick and
easy for all users.
d. Cost-Effective: Minimizes the need for physical infrastructure, such as ticket vending machines,
reducing operational costs.
5. Implementation Strategy
a. Technology Integration: Collaborate with mobile service providers to integrate the USSD
ticketing system into their networks.
b. User Education: Conduct comprehensive awareness campaigns to educate MetroRail passengers
on how to use the USSD service for ticket purchases.
c. Security Measures: Implement robust security measures to safeguard user data and transactions
conducted through the USSD service.
d. Collaboration with Mobile Operators: Partner with mobile operators to ensure seamless payment
integration and optimal USSD service performance.
e. Continuous Improvement: Gather user feedback to make necessary adjustments and
improvements to the USSD ticketing service continually.
6. Conclusion
The implementation of a Mobile USSD Ticketing Service for MetroRail aligns with the goal of
providing a simple, accessible, and efficient ticket purchasing experience for all commuters. By
leveraging the widespread availability of USSD technology, MetroRail can enhance inclusivity,
improve accessibility, and contribute to a more seamless and convenient public transportation
system.

Title: Technical Flow Diagram for Mobile USSD Ticketing with Gate Open Feature in
MetroRail
1. Overview
This technical flow diagram outlines the process flow for the implementation of a Mobile USSD
Ticketing Service with a gate open feature for MetroRail. The gate open feature ensures that after a
successful payment transaction, the commuter can access the MetroRail platform seamlessly.
2. Technical Flow Diagram
Diagram Key:
1. Initiate USSD Session:
 Commuter initiates the USSD session by dialing the designated USSD code.
 USSD session is established with the MetroRail server.
2. Main Menu:
 Commuter is presented with the main menu options, including ticket purchase and
other relevant information.
3. Ticket Purchase:
 Commuter selects the option to purchase a ticket.
 USSD prompts the commuter to enter journey details (e.g., start and end stations,
ticket type).
 4. Payment Process:
 USSD prompts the commuter to choose a payment method (e.g., mobile wallet,
linked bank account).
 Commuter enters payment details, and USSD initiates a secure payment transaction
with the payment gateway.
5. Payment Confirmation:
 Upon successful payment, the MetroRail server confirms the transaction and
generates a digital ticket.
6. Gate Open Confirmation:
 MetroRail server sends a gate open command to the station's access control system
upon successful payment.
7. Gate Open Signal:
 Access control system receives the gate open signal and allows the commuter to pass
through the entry gate.
8. Digital Ticket Display:
 Commuter receives a confirmation message via USSD containing the digital ticket
details.
9. Journey Commencement:
 Commuter proceeds to the platform with the digital ticket displayed on their mobile
device.
10. Ticket Validation:
 MetroRail staff or automated systems validate the digital ticket upon entry to the
platform.
11. Journey Completion:
 Commuter completes the journey, and the ticket is archived in the system.
3. Key Features and Components:
 USSD Gateway: Manages the USSD session and communicates with the MetroRail server.
 Payment Gateway: Handles secure payment transactions.
 MetroRail Server: Manages ticketing, payment confirmation, and gate open commands.
 Access Control System: Controls entry gates and receives gate open signals.
 User Mobile Device: Initiates the USSD session, displays digital tickets, and receives
confirmation messages.
4. Conclusion:
The technical flow diagram illustrates the seamless integration of a Mobile USSD Ticketing Service
with a gate open feature for MetroRail. This innovative approach enhances the user experience by
providing a convenient and secure ticketing process while ensuring smooth entry to the MetroRail
platform after a successful payment transaction.
+---------------------+ +-------------------+ +---------------------+
| User's Mobile Device| ----> | USSD Gateway | ---> | MetroRail Server |
+---------------------+ +-------------------+ +---------------------+
 | | |
v v |
+---------------------+ +-------------------+ |
| Payment Gateway | <--- | Payment Confirmation | <---------+
+---------------------+ +-------------------+ |
| |
v |
+---------------------+ +-------------------+ |
| Access Control System| <-----| Gate Open Command | <-------------+
+---------------------+ +-------------------+
Concept Paper: RCS-Based Ticketing Service for MetroRail
1. Introduction: The proposed RCS-based Ticketing Service for MetroRail aims to revolutionize
the ticketing process by leveraging Rich Communication Services (RCS) technology. This
innovative system provides users with a seamless and efficient ticketing experience, incorporating
advanced features like gate opening after successful payment.
2. Objectives:
 Streamline the ticketing process for MetroRail commuters.
 Enhance user experience through RCS capabilities.
 Enable secure and contactless ticket purchase and validation.
 Integrate a gate open feature for frictionless entry after successful payment.
3. Technical Flow Details:
3.1 User Registration:
 Users download the MetroRail RCS app and register using their mobile number.
 Validate registration through a one-time password (OTP).
3.2 Ticket Purchase:
 Users browse available routes, timings, and fare details within the RCS app.
 Select the desired journey and make payment using integrated payment gateways.
 RCS technology ensures a secure and seamless payment process.
3.3 Ticket Confirmation:
 Upon successful payment, users receive a digital ticket with a unique QR code via RCS.
 The digital ticket serves as proof of purchase and allows entry.
3.4 Gate Opening Feature:
 At the MetroRail station, users approach the gate with the digital ticket displayed on their
mobile device.
 NFC (Near Field Communication) technology integrated into the gate scanners reads the QR
code.
 Upon successful verification, the gate opens automatically, allowing the user entry.
3.5 Real-Time Updates:
 Users receive real-time updates on train schedules, delays, and other relevant information
via RCS notifications.
3.6 Security Measures:
 Implement end-to-end encryption to ensure the security of user data and transactions.
 Utilize multi-factor authentication for enhanced security during the registration process.
4. Benefits:
 Convenience: Users can purchase tickets and enter MetroRail stations with a single mobile
device.
  Contactless Experience: Reduces physical contact during the ticketing and entry process.
 Efficiency: Real-time updates and automatic gate opening streamline the entire commuting
experience.
5. Implementation Challenges:
 Infrastructure Upgrade: Requires integration with existing MetroRail systems and
infrastructure.
 User Education: Communicating the new system and its benefits to users may pose a
challenge initially.
6. Conclusion: The RCS-based Ticketing Service for MetroRail promises to bring significant
improvements to the ticketing process, making it more convenient, secure, and efficient for
commuters. By embracing cutting-edge RCS technology, this system aims to enhance the overall
MetroRail experience and pave the way for future innovations in public transportation.

Technical Service Flow: RCS-Based Ticketing Service for MetroRail

1. User Registration:
 User downloads the MetroRail RCS app and enters their mobile number.
 The RCS app sends a one-time password (OTP) to the user's registered mobile number for
verification.
 Upon successful OTP verification, the user's account is created.
2. Ticket Purchase:
 User logs into the RCS app and selects the desired MetroRail route, date, and time.
 The app displays fare details, and the user proceeds to payment.
 Integrated payment gateways (e.g., credit card, mobile wallets) handle the transaction
securely.
3. Ticket Generation:
 After successful payment, the RCS app generates a digital ticket with a unique QR code.
 The digital ticket contains details such as journey information, date, and time.
4. Notification to Gate System:
 The RCS app sends a notification to the MetroRail gate system, indicating the user's
successful ticket purchase.
 This notification triggers the creation of a temporary access token associated with the user's
mobile device.
5. Gate Entry:
 At the MetroRail station gate, the user approaches with the RCS app open and the digital
ticket visible.
 The gate's NFC scanner reads the QR code on the digital ticket.
  The access token is verified against the server, and if valid, the gate opens automatically.
6. Real-Time Updates:
 The RCS app receives real-time updates on train schedules, delays, or any relevant
information.
 Users are notified promptly through RCS notifications.
7. Security Measures:
 User data is encrypted end-to-end to ensure confidentiality.
 Multi-factor authentication during registration adds an extra layer of security.
 Secure APIs facilitate communication between the RCS app, payment gateways, and the
MetroRail gate system.
8. Integration with MetroRail Systems:
 The RCS-based Ticketing Service integrates with the existing MetroRail ticketing and gate
systems.
 APIs enable seamless communication between the RCS app, payment gateways, and the
MetroRail infrastructure.
9. User Feedback:
 Users can provide feedback on the ticketing experience through the RCS app.
 Feedback is collected and analyzed to continuously improve the system.
10. System Maintenance and Upgrades:
 Regular maintenance ensures the smooth functioning of the RCS-based Ticketing Service.
 Upgrades are implemented to introduce new features, enhance security, and improve overall
performance.
11. Data Privacy Compliance:
 The system complies with data privacy regulations, ensuring that user information is
handled responsibly and ethically.
12. User Support:
 A dedicated support system is in place, offering assistance through the RCS app or other
communication channels.
 User queries, issues, or ticketing problems are addressed promptly.
13. Future Enhancements:
 Continuous research and development efforts aim to introduce additional features such as
loyalty programs, integrated transit planning, and enhanced user customization.
This technical service flow outlines the end-to-end process of the RCS-based Ticketing Service for
MetroRail, emphasizing seamless user experience, security, and integration with existing
infrastructure. It serves as a guide for developers and stakeholders involved in the implementation
of the proposed ticketing solution.