Taxi ticket management system

Abstract

To solve the problem of complication in the process of employees receiving taxi ticket allocations.SOLUTION: A taxi ticket management system for managing electronic tickets for receiving taxi service includes: a settlement service server that allocates electronic tickets to employees; and an employee terminal for use of allocated electronic ticket when boarding a taxi. The settlement service server includes a periodic replenishment processing unit configured to compare, at predetermined intervals, the number of possessed tickets authorized for an employee registered in a ticket authorization management table with the number of available tickets in an allocated ticket management table and allocate, to the employee, tickets whose total number is equal to the number obtained by subtracting the number of available tickets from the number of possessed authorized tickets.SELECTED DRAWING: Figure 1

Description

[Technical Field]

[0001] The present invention relates to a taxi ticket management system. [Background technology]

[0002] When employees of a company use taxi services for work, the company's accounting department uses taxi tickets obtained from a ticket company in bulk, so that employees do not have to pay directly when using a taxi.

[0003] Using a taxi ticket can sometimes allow you to use taxi services at a discounted rate compared to the regular rate, which has the advantage of making it easier to manage your transportation budget.

[0004] However, to prevent the fraudulent use of taxi tickets, which are cash vouchers, it is necessary for administrative staff to manually hand over the paper taxi ticket to the employee when using the taxi ticket.

[0005] Additionally, when it comes to transportation tickets that employees hand out to invited guests at irregular events such as large-scale seminars and parties, there are cases where preparations cannot be completed in time due to reasons such as missed applications or the short time until the event.

[0006] Patent Document 1 discloses that the ticket center sets up a website for notifying and obtaining, via a communication line, information used in the procedure for using a taxi ticket, receives an application to use a taxi ticket via the website, notifies via the website of usage permission information specific to that taxi ticket, registers the usage permission for that taxi ticket, and, in response to a payment request for the taxi ticket identified by the usage permission information, verifies the validity of the taxi ticket, determines whether or not the taxi ticket can be paid for, and sends the payment result via a communication line to the taxi ticket payment terminal that made the payment request, and invalidates the used taxi ticket. [Prior art documents] [Patent documents]

[0007] [Patent Document 1] Japanese Patent Application Laid-Open No. 2004-341918 Summary of the Invention [Problem to be solved by the invention]

[0008] The method disclosed in Patent Document 1 above involves receiving an application to use a taxi ticket via the web, notifying dedicated usage permission information for the taxi ticket via the web, registering the usage permission for the taxi ticket, verifying the legitimacy of the taxi ticket in response to a payment request for the taxi ticket identified by the usage permission information, determining whether or not the taxi ticket can be paid for, and transmitting the payment result via a communication line to the taxi ticket payment terminal that made the payment request, and invalidating the used taxi ticket.

[0009] However, even if the web is used, there is a problem that employees cannot use taxi tickets with the required expiration date, maximum amount, and number when they need them.

[0010] When an employee attempts to board a taxi, if the employee is not permitted to use a taxi ticket, the employee must apply for a taxi ticket via the web when boarding the taxi.

[0011] Also, if an employee needs to distribute taxi tickets home to more than 100 guests at an event, there is a risk that the guests will have to wait even if they apply for the taxi tickets via the web. [Means for solving the problem]

[0012] The above problem is achieved by a taxi ticket management system for managing electronic tickets for receiving taxi services, which system comprises a payment service server that allocates electronic tickets to employees, and an employee terminal for use when riding in a taxi with the allocated tickets, and the payment service server comprises a periodic replenishment processing unit that, at predetermined intervals, compares the number of tickets that the employee is permitted to hold, as registered in the holding authority management table, with the number of tickets available in the allocated ticket management table, and allocates to the employee the number of tickets that is calculated by subtracting the number of tickets available from the number of tickets that the employee is permitted to hold. [Effects of the Invention]

[0013] Employees can easily receive taxi ticket allocations. [Brief explanation of the drawings]

[0014] [Figure 1] An example of a system configuration diagram of a taxi ticket management system according to an embodiment of the present invention. [Figure 2] FIG. 1 is a block diagram illustrating a configuration of a payment service server according to an embodiment of the present invention. [Figure 3] An example of a table diagram of a retained authority management table in an embodiment of the present invention. [Figure 4] An example of a table diagram of an assigned ticket management table in an embodiment of the present invention. [Figure 5] An example of a table diagram of a ticket usage schedule management table according to an embodiment of the present invention. [Figure 6] Example of ticket information display screen (1) in an embodiment of the present invention [Figure 7] Example of ticket information display screen (2) in the embodiment of the present invention [Figure 8] 1 is a flowchart illustrating a regular replenishment process according to an embodiment of the present invention; [Figure 9] 1 is a flowchart illustrating a process for replenishment of planned use according to an embodiment of the present invention; [Figure 10]An example of a flowchart showing a usage process in an embodiment of the present invention. DETAILED DESCRIPTION OF THE INVENTION

[0015] Hereinafter, embodiments of the present invention will be described with reference to the drawings. In each drawing for explaining the embodiments, the same components are given the same names and reference numerals as much as possible, and repeated explanations thereof will be omitted.

[0016] The present invention is not limited to the following examples, and includes various modifications and equivalent configurations within the spirit and scope of the appended claims. For example, the above examples have been described in detail to clearly explain the present invention, and the present invention is not necessarily limited to those including all of the described configurations.

[0017] Furthermore, the processing units and processing modules described in the embodiments may be realized in part or in whole in hardware, for example by designing them as integrated circuits, or may be realized in software by having a processor interpret and execute a program that realizes each function.

[0018] The information explained in the embodiment may be a table, a database (DB), or data stored in the main memory. [Example]

[0019] FIG. 1 is a diagram showing an example of the system configuration of a taxi ticket management system according to an embodiment of the present invention.

[0020] The payment service server 2 receives electronic tickets from a ticket business server 7 that handles taxi tickets (hereinafter simply referred to as tickets) for receiving taxi services.

[0021] If the electronic ticket is not received directly from the ticket provider server 7, a contract can be concluded with the ticket provider, and information including the ticket ID for electronically using the ticket can be received by email, post, or other means, and the administrator 8 can register it with the payment service server using the administrator terminal 3 connected to the payment service server 2.

[0022] The payment service server 2 is connected to an employee terminal 4 such as a smartphone, and employees 9 can access the network-connected payment service server 2 via the employee terminal 4 and check the tickets assigned to them.

[0023] If the employee has been assigned a ticket, he or she can obtain the payment destination by photographing the two-dimensional barcode 6 displayed inside the taxi when getting in the taxi, and can receive taxi service by sending a payment request together with the amount to the payment service server 2.

[0024] In addition, when an employee needs to transport a guest to an event, etc., the employee can send the ticket ID of the electronic ticket from the employee terminal 4 to the guest terminal such as a smartphone, and the guest 10 can request payment of the taxi fare from the payment service server 2 using the guest terminal 5 in the same procedure as the employee.

[0025] FIG. 2 is a block diagram illustrating an example of the configuration of a payment service server according to an embodiment of the present invention.

[0026] The payment service server 2 is realized by a computer that includes a CPU (Central Processing Unit) 20, memory including RAM (Random Access Memory) and ROM (Read Only Memory), an external storage device 31 including SSD (Solid State Drive) and HDD (Hard Disk Drive), and an input / output unit 32 including a NIC (Network Interface Card).

[0027] In this embodiment, an example will be described in which the system is implemented using a standalone computer. However, if the system is implemented using a cloud system that provides computer resources as a service, system maintenance and management will become easier.

[0028] The memory 30 includes a periodic replenishment processing unit 33 that periodically allocates tickets to employees, a planned use replenishment processing unit 34 that allocates tickets that are scheduled for use to employees, a ticket use processing unit 35 that processes ticket payment requests, and a ticket transfer processing unit 36 ​​that processes the transfer of tickets to guests, etc.

[0029] The external storage device 31 includes a holding authority management table 37 for registering how many tickets an employee has the authority to hold, an assigned ticket management table 38 for managing tickets assigned to employees, and a ticket use schedule management table 39 for registering tickets to be used and requesting allocation to employees.

[0030] Each processing unit stored in the memory 30 is realized as a software module, and is executed by the CPU 20 by referring to information in the memory and each table stored in the external storage device 31 .

[0031] FIG. 3 is a table diagram showing an example of a retained authority management table in an embodiment of the present invention.

[0032] The number 40, employee name 41, and ticket count 42, which is the number of tickets the employee has the authority to hold, are stored in association with each other. The ticket count 42 is connected to the payment service server 2, and the administrator 8 sets the number of tickets that each employee thinks are necessary from the administrator terminal 3.

[0033] FIG. 4 is a table diagram showing an example of an assigned ticket management table in an embodiment of the present invention.

[0034] The ticket ID 51 identifies the ticket, the employee name 52 identifies the employee, the status 53 indicates the status of the ticket such as whether the ticket is available for use, whether it has been transferred, whether it has been assigned to an employee, the attribute 54 stores "planned" if the ticket has been assigned by the scheduled use replenishment processing unit and has a set usage schedule, or "regular" if the ticket has been assigned by the regular replenishment processing unit and has no set usage schedule, the ticket expiration date 55, and the maximum amount that can be used 56 are stored in association with each other.

[0035] FIG. 5 is a table diagram showing an example of a ticket use schedule management table in an embodiment of the present invention.

[0036] The number 60, the expected ticket use date 61, the name of the employee to whom the ticket is to be assigned 62, the ticket expiration date 63, and the maximum amount that can be used 64 are stored in association with each other.

[0037] Employees can use this table to request tickets for events etc. in excess of the number determined in the authority holding management table 37.

[0038] Furthermore, the settlement service server 2 performs allocation processing of the required number of tickets, the required expiration date, and the required upper limit amount based on this table.

[0039] FIG. 6 shows an example of a ticket information display screen (1) in an embodiment of the present invention.

[0040] This is information about assigned tickets that can be viewed on employee terminal 4. In this example, a total of 12 tickets have been assigned, and the ticket displayed includes ticket number AAA1234 with a maximum amount of 10,000 yen and an expiration date of June 30, 2023, and ticket number AAA5678 with an unlimited maximum amount and an expiration date of June 30, 2023.

[0041] FIG. 7 shows an example of a ticket information display screen (2) in an embodiment of the present invention.

[0042] In this example, in addition to the information in Figure 6, a transfer button 71 for transferring each ticket to a guest, a return button 72 for returning the ticket to the payment service server 2, and a withdrawal button 73 for getting back a ticket that has already been transferred are displayed.

[0043] FIG. 8 is an example of a flowchart showing a regular replenishment process in an embodiment of the present invention.

[0044] The number of unallocated tickets that have already been acquired is obtained from the ticket business server (S1).

[0045] An employee is selected from the authority management table 37 (S2), and the number of tickets for which the employee has authority is found.

[0046] Next, the number of tickets with the commuter attribute that can be used and assigned to the employee is obtained from the assigned ticket management table 38 (S3). The number of tickets that can be held is compared with the number of tickets with the commuter attribute that can be used (S4), and whether or not there is a shortage of tickets is determined based on whether the number of tickets with the commuter attribute that can be used is less than the number of tickets that can be held (S5).

[0047] If there are no tickets in short supply, the process moves to S10, and if there are tickets in short supply, it is determined whether the number of tickets that can be allocated but are not yet allocated is equal to or greater than the shortfall (S6).

[0048] If there are not enough unallocated tickets, the output unit 32 outputs a message indicating that there are not enough tickets, and the process ends.

[0049] If there are enough unallocated tickets, the shortage of tickets is allocated to the employee and registered in the allocated ticket table (S8), and the number of allocated tickets is subtracted from the number of unallocated tickets for the employee.

[0050] Next, it is determined whether processing has been completed for all employees registered in the authority management table 37 (S10), and if there are any employees remaining, the process returns to S2. If there are no employees remaining, the process ends.

[0051] This process can be performed at a set interval such as daily, every other day, or weekly, to allocate the necessary tickets to employees.

[0052] FIG. 9 is an example of a flowchart showing a process for replenishment of planned use in an embodiment of the present invention.

[0053] The number of unallocated tickets that have been acquired is obtained from the ticket business server (S30).

[0054] A ticket usage schedule is selected from the ticket usage schedule management table (S31), and it is determined whether or not there is an unallocated ticket (S32).

[0055] If there are no unallocated tickets, a message indicating that there is a shortage of tickets is output from the output unit 32, and the process ends (S33).

[0056] If there are any unallocated tickets, the tickets to be used are allocated to the employee and registered in the allocated ticket table (S34), and the number of allocated tickets is subtracted from the number of unallocated tickets (S35).

[0057] Next, it is determined whether or not all scheduled uses have been processed, and if there are any scheduled uses remaining, the process returns to S31 and is repeated, whereas if there are no scheduled uses remaining, the process ends.

[0058] FIG. 10 is an example of a flowchart showing a usage process in an embodiment of the present invention.

[0059] The administrator 8 assigns a ticket to an employee 9 using the authority management table 37 (S40), and the employee receives a ticket notification on the employee terminal 4 (S41) and displays the ticket status (S42).

[0060] The employee terminal accepts the selection of the ticket to be used (S43) and accepts the input of the PIN number set on the ticket (S44).

[0061] It is determined whether the PIN numbers match (S45), and if they do, the ticket is taken out (S46), and payment destination information for the fare is read from the two-dimensional barcode on the taxi (S47).

[0062] Next, input of the amount to be used is accepted (S48), and the payee and amount to be used are sent to the settlement service server 2, and if the personal identification numbers do not match, the process ends.

[0063] If the amount used does not exceed the upper limit set for each ticket, the accepted amount is transmitted, and if it exceeds the upper limit, the upper limit amount is transmitted. [Explanation of symbols]

[0064] 1 Taxi ticket management system, 2 Payment service server, 3 Administrator terminal, 4 Employee terminal, 5 Guest terminal, 6 Taxi two-dimensional barcode, 7 Ticket business server, 8 Administrator, 9 Employee, 10 Guest, 20 CPU, 30 Memory, 31 External storage device, 32 Input / output unit, 33 Regular replenishment processing unit, 34 Planned use replenishment processing unit, 35 Ticket use processing unit, 36 Ticket transfer processing unit, 37 Holding authority management table, 38 Allocated ticket management table, 39 Planned ticket use management table

Claims

1. A taxi ticket management system for managing electronic tickets for receiving taxi services, a payment service server that allocates electronic tickets to employees; and an employee terminal for using the allocated ticket when boarding a taxi, The payment service server compares the number of tickets that the employee is permitted to hold, which is registered in the holding authority management table, with the number of tickets that can be used, which is registered in the allocated ticket management table, at predetermined intervals; A periodic replenishment processing unit that allocates tickets to employees in the number calculated by subtracting the number of available tickets from the number of tickets permitted to be held. A taxi ticket management system equipped with:

2. In the taxi ticket management system according to claim 1, The periodic replenishment processing unit determines whether there are any tickets available for allocation when allocating tickets to employees, and outputs a message indicating a shortage of tickets if there are no tickets available for allocation. A taxi ticket management system equipped with:

3. In the taxi ticket management system according to claim 2, The settlement service server refers to the tickets scheduled for use and the assigned employee names registered in the ticket usage schedule management table, and allocates the registered tickets to the registered assigned employees. A taxi ticket management system equipped with:

4. In the taxi ticket management system according to claim 3, The regular replenishment processing unit refers to an attribute included in the allocated ticket management table that indicates whether or not a ticket is scheduled for use, and does not count tickets scheduled for use in the number of available tickets.

5. In the taxi ticket management system according to claim 1, A taxi ticket management system that sends the ticket ID, amount, and payment destination information of the ticket assigned from the employee terminal to the payment service server, enabling payment of the taxi fare.

6. In the taxi ticket management system according to claim 1, a ticket transfer processing unit that assigns a ticket ID of the assigned ticket to a guest terminal; A taxi ticket management system that sends the assigned ticket ID, amount, and payment destination information from the guest terminal to the payment service server, enabling payment of the taxi fare.

Images