SYSTEMS AND METHODS FOR TRANSIT-RELATED TRANSACTIONS

• US 20170124671A1
• Filed: 11/03/2016
• Published: 05/04/2017
• Est. Priority Date: 11/03/2015
• Status: Abandoned Application

• Current Assignee: Transportation Technology Partners, LLC
• Original Assignee: Transportation Technology Partners, LLC
• Inventors: Tam, Chung Chung, Svanascini, Michael, Perkaus, John
• Application Number:
  US15/343,155
• Publication Number:
  US 20170124671A1
• Time in Patent Office: Days
• CPC Class Codes: G06F 3/0346 with detection of the device orientation or free movement in a 3D space, e.g. 3D mice, 6-DOF [six degrees of freedom] pointers using gyroscopes, accelerometers or tilt-sensors
• CPC Class Codes: G06F 3/0482 Interaction with lists of selectable items, e.g. menus
• CPC Class Codes: G06F 3/0488 using a touch-screen or digitiser, e.g. input of commands through traced gestures
• CPC Class Codes: G06F 3/167 Audio in a user interface, e.g. using voice commands for navigating, audio feedback
• CPC Class Codes: G06Q 10/02 Reservations, e.g. for tickets, services or events
• CPC Class Codes: G06Q 20/0457 the tickets being sent electronically
• CPC Class Codes: G06Q 20/047 using payment protocols involving electronic receipts
• CPC Class Codes: G06Q 20/322 Aspects of commerce using mobile devices [M-devices]
• CPC Class Codes: G06Q 50/14 Travel agencies

Abstract

A device for transit-related transactions includes processor(s) that control a user interface to send/receive information to/from a user and control a communication interface to communicate wirelessly with one or more external systems. The device includes storage device(s) storing data and program instructions. The program instructions cause the processor(s) to execute a ticketing procedure for a selected transit service. The ticketing procedure includes: receiving a ticket purchase request from the user; processing payment for the ticket purchase request; and storing an electronic ticket associated with the ticket purchase request after payment approval. The ticketing procedure may include establishing wireless communications with a ticketing system associated with the selected transit service; and in response to the payment approval, receiving the electronic ticket from the ticketing system. The ticketing procedure may also include receiving a ticket activation request from the user; and presenting the electronic ticket via the user interface for validation.

Claims

1. A device for transit-related transactions, comprising:

one or more processors;

a user interface coupled to the one or more processors, the one or more processors controlling the user interface to send information to a user or to receive input from the user;

a communication interface coupled to the one or more processors, the one or more processors controlling the communication interface to communicate wirelessly with one or more external systems;

one or more storage devices coupled to the one or more processors and storing data and program instructions, the program instructions causing the one or more processors to execute a ticketing procedure for a selected transit service, the ticketing procedure including;

receiving, via the user interface, a ticket purchase request from the user;

processing payment for the ticket purchase request; and

storing, on the one or more storage devices, an electronic ticket associated with the ticket purchase request after approval of the payment.

2. The device according to claim 1, wherein the ticketing procedure further includes:

establishing wireless communications, via the communication interface, with a ticketing system associated with the selected transit service; and

in response to the approval of the payment, receiving, via the communication interface, the electronic ticket from the ticketing system.

3. The device according to claim 1, wherein the ticketing procedure further includes:

receiving, via the user interface, a ticket activation request from the user; and

in response to the ticket activation request, presenting the electronic ticket via the user interface for validation.

4. The device according to claim 3, wherein the ticketing procedure further includes expiring the electronic ticket after the validation.

5. The device according to claim 3, wherein the user interface includes an accelerometer for motion input from the user, and receiving the ticket activation request via the user interface includes detecting, with the accelerometer, the motion input.

6. The device according to claim 3, wherein the user interface includes a touch display for touch input from the user, and receiving the ticket activation request via the user interface includes detecting, via the touch screen, the touch input.

7. The device according to claim 3, wherein the user interface includes a display and the electronic ticket is presented at least visually on the display.

8. The device according to claim 3, wherein the user interface includes a speaker and the electronic ticket is presented at least aurally via the speaker.

9. The device according to claim 3, wherein the ticketing procedure further includes, in response to receiving, via the user interface, a modification request from the user, modifying the electronic ticket presented via the user interface for validation.

10. The device according to claim 1, wherein the one or more processors are configured to detect, via the communication interface, a wireless activation signal associated with the transit service, and the ticketing procedure further includes:

detecting, via the communication interface, the wireless activation signal; and

in response to the wireless activation signal, presenting the electronic ticket via the user interface for validation.

11. The device according to claim 1, wherein the program instructions further cause the one or more processors to:

receive, via the user interface, user account information from the user, the user account information including payment information for the payment of the ticket purchase request; and

store the user account information on the one or more storage devices,

wherein processing payment for the ticket purchase request includes;

establishing wireless communications, via the communication interface, with a payment processing system;

sending, via the communication interface, the payment information to the payment processing system, the payment processing system determining the approval of the payment for the ticker purchase request; and

receiving, via the communication interface, the approval of the payment for the ticker purchase request from the payment processing system.

12. The device according to claim 1, wherein the program instructions further cause the one or more processors to:

receive, via the user interface, user account information from the user, the user account information including payment information for the payment of the ticket purchase request;

store the user account information in the one or more storage devices;

send, via the communications interface, the user account information to a ticketing system associated with the selected transit service, the ticketing system storing the user account information,

wherein processing payment for the ticket purchase request includes;

establishing wireless communications, via the communication interface, with the ticketing system; and

sending, via the communication interface, a request to the ticketing system for approval of the payment for the ticker purchase request, the ticketing system determining the approval of the payment according to the payment information; and

wherein the ticketing procedure further includes receiving from the ticketing system, via the communication interface, the electronic ticket associated with the ticket purchase request.

13. The device according to claim 1, wherein the program instructions further cause the one or more processors to execute a trip planning procedure including:

receiving, via the user interface, destination information from the user;

determining one or more travel plans for transporting the user according to the destination information, each travel plan designating one or more transit services; and

presenting, via the user interface, the one or more travel plans to the user.

14. The device according to claim 13, wherein the trip planning procedure further includes:

receiving, via the user interface, a selection of one of the travel plans;

in response to the selection of one of the travel plans, identifying the corresponding one or more transit services associated with the selected travel plan requiring a ticket; and

prompting, via the user interface, the user to select one of the transit services requiring a ticket and to make the ticket purchase request for the selected transit service, and

wherein the ticketing procedure correspondingly receives the ticket purchase request.

15. The device according to claim 14, wherein the program instructions further cause the one or more processors to execute a purchase procedure for goods or services of one or more third parties, the purchase procedure including:

presenting, via the user interface, one or more offers for goods or services from respective third parties according to the selected travel plan;

receiving, via the user interface, a selection of one of the offers by the user;

in response to the selection of one of the offers, establishing wireless communication, via the communication interface, with the respective third party;

sending to the respective third-party vendor, via the communication interface, a purchase request based on the selected offer; and

processing payment for the purchase request based on the selected offer.

16. The device according to claim 15, wherein the program instructions further cause the one or more processors to determine a location of the user relative to the selected travel plan, and the purchase procedure further includes sending to the third party, via the communication interface, an estimated arrival time that indicates when the user will arrive to receive the goods or services from the third party, the estimated arrival time based on the location of the user and the selected travel plan.

17. The device according to claim 16, wherein the program instructions further cause the one or more processors to:

establish wireless communication, via the communication interface, with one or more travel data sources associated with the corresponding one or more transit services associated with the selected travel plan;

receiving, via the communication interface, updates relating to the one or more transit services, and

determine the location of the user according to updates relating to the one or more transit services.

18. The device according to claim 13, wherein the program instructions further cause the one or more processors to:

receive, via the user interface, user account information from the user, the user account information including trip planning preferences; and

store the user account information in the one or more storage devices, and

wherein the one or more travel plans are further determined or presented according to the trip planning preferences.

19. The device according to claim 13, wherein the trip planning procedure further includes:

receiving, via the user interface, a selection of one of the travel plans;

in response to the selection of one of the travel plans, identifying the corresponding one or more transit services associated with the selected travel plan;

establishing wireless communication, via the communication interface, with one or more travel data sources associated with the corresponding one or more transit services;

receiving, via the communication interface, updates relating to the one or more transit services, and

presenting, via the user interface, modifications to the selected travel plan according to the updates relating to the one or more transit services.

20. The device according to claim 19, wherein the modifications to the selected travel plan include one or more alternative transit services, and the trip planning procedure further includes:

identifying the one or more alternative transit services requiring a ticket;

prompting, via the user interface, the user to select one of the alternative transit services requiring a ticket and to make the ticket purchase request for the selected alternative transit service, and

wherein the ticketing procedure correspondingly receives the ticket purchase request.