Taxi ticket management device and taxi ticket management program
The taxi ticket management system addresses the inconvenience of carrying physical cards by issuing electronic tickets linked to magnetic cards, enabling convenient group travel and accurate billing through QR code payments.
Patent Information
- Application Number
- JP2022110339
- Authority / Receiving Office
- JP · JP
- Patent Type
- Patents
- Current Assignee / Owner
- Filing Date
- 2022-07-08
- Publication Date
- 2026-11-19
- Estimated Expiration
- 2042-07-08
AI Technical Summary
Existing taxi ticket systems require users to carry physical cards for payment, which is cumbersome and limits their use to single passengers, especially when multiple individuals need to pay for separate taxis.
A taxi ticket management system that issues electronic taxi tickets linked to magnetic cards, allowing users to ride and pay without carrying the physical card, with the system aggregating sales and providing real-time payment processing through QR codes and smartphone applications.
Enables passengers to use taxis without carrying physical tickets, facilitating group travel and enhancing convenience by allowing electronic payment through smartphones, while maintaining accurate billing for the taxi operating company.
Smart Images

Figure 0007954020000001 
Figure 0007954020000002 
Figure 0007954020000003
Abstract
Description
Technical Field
[0001] The present invention relates to a taxi ticket management device and a taxi ticket management program, and pertains to, for example, the operation of taxi tickets issued under a contract with a taxi operating company.
Background Art
[0002] Taxis are widely used as a means of public transportation, and taxi tickets exist as a mechanism where taxi fares are collectively billed to a contractor on a postpaid basis. In addition to being issued in paper form, taxi tickets may also be issued in the form of magnetic cards as described in Patent Document 1. For taxi tickets, terms such as the expiration date, the maximum amount per ride, and the total maximum monthly amount are defined by contract between the contractor and the issuer.
[0003] Besides use by the contractor, taxi tickets can also be used by persons other than the contractor to take a taxi. For example, there is a case where guests at a seminar hosted by the contractor are asked to use taxi tickets to return home. In this case, if the taxi ticket is in paper form, the taxi ticket is handed over to the user for use. On the other hand, if the taxi ticket is a magnetic card or an IC card, it is a single physical card. For this reason, when a user takes a taxi, a reading process is required in which the holder of the magnetic card or the like accompanies the user to the taxi and causes the payment terminal to read the magnetic card or the like. Therefore, when a large number of users use separate taxis, the holder of the magnetic card or IC card needs to perform the reading process at the payment terminal for all taxis, which is very cumbersome. In addition, in the case of a magnetic card or IC card, since the accompaniment of the card holder is required, the card can only be used for returning home, and cannot be used when inviting people to visit the venue.
Prior Art Documents
Patent Documents
[0004] [Patent Document 1] Japanese Patent Publication No. 2004-78661 [Overview of the Initiative] [Problems that the invention aims to solve]
[0005] The present invention aims to enable passengers to ride in taxis without having to carry a taxi ticket. [Means for solving the problem]
[0006] This invention enables the use of taxis with payment made after the ride. , magnetic cards, IC cards, or paper cards that have already been issued The present invention provides a taxi ticket management device comprising: an acquisition means for acquiring identification information and usage conditions specified for a taxi ticket; a storage means for storing the acquired identification information and usage conditions of the taxi ticket; an electronic taxi ticket issuing means for issuing an electronic taxi ticket linked to the stored taxi ticket, within the scope of the usage conditions of the taxi ticket, based on an issuance request from the holder of the stored taxi ticket; and an electronic taxi ticket providing means for providing the issued electronic taxi ticket. [Effects of the Invention]
[0007] The present invention issues an electronic taxi ticket linked to a taxi ticket, based on a request from the holder of the taxi ticket, within the scope of the usage conditions of the taxi ticket. Therefore, by using the electronic taxi ticket, it is possible to ride in a taxi without having to carry the taxi ticket with you. [Brief explanation of the drawing]
[0008] [Figure 1] This is a diagram illustrating the configuration of a taxi ticket system to which the taxi ticket management device of this embodiment is applied. [Figure 2] This is an explanatory diagram showing the data stored in the taxi ticket management system's taxi ticket database. [Figure 3] This flowchart illustrates the overall process for using electronic taxi tickets linked to magnetic taxi tickets via the taxi ticket system. [Figure 4] This is a conceptual diagram illustrating the state in which registration information is stored in the taxi ticket database. [Figure 5] This image shows the screen used when registering a magnetic taxi ticket to a smartphone taxi ticket app. [Figure 6] This is an explanatory diagram showing the display screen when issuing an electronic taxi ticket. [Figure 7] This is an explanatory diagram showing the updated status of the taxi ticket database following the issuance of electronic taxi tickets. [Figure 8] This is an explanatory diagram showing the content displayed on the payment screen shown on the front seat tablet. [Figure 9] This is an explanatory diagram regarding the presentation of a QR code (registered trademark). [Figure 10] This is an explanatory diagram showing the content displayed on the front seat tablet when a payment request is made. [Figure 11] This is an explanatory diagram showing the status of the taxi ticket database as updated by a payment request. [Figure 12] This is an explanatory diagram showing the status of the Takuticket DB during maintenance. [Modes for carrying out the invention]
[0009] Hereinafter, preferred embodiments of the taxi ticket management device and taxi ticket management program of the present invention will be described in detail with reference to Figures 1 to 12. In this embodiment, "taxi ticket" will be abbreviated as "takuchike". (1) Outline of the Embodiment The taxi ticket management device 60 of this embodiment links and issues electronic taxi tickets to magnetic taxi tickets 12 issued on magnetic cards based on a contract with a taxi operating company 20. With this electronic taxi ticket, the holder 10 themselves or a third party (such as the user 40) can ride in a taxi without carrying the physical magnetic taxi ticket 12, and perform settlement (payment) within the contract scope of the magnetic taxi ticket 12 and within the issuance conditions of the electronic taxi ticket.
[0010] When issuing an electronic taxi ticket linked to the magnetic taxi ticket 12, the taxi ticket management device 60 issues identification information for uniquely identifying the electronic taxi ticket in the same format (member number system) as the identification information of the magnetic taxi ticket 12 (n digits representing the member number and 1 digit representing the type). As a result, by only adding a configuration for reading the electronic taxi ticket inside the taxi, it becomes possible to ride in the taxi using the electronic taxi ticket in the same manner as in the case of the magnetic taxi ticket 12. In addition, the taxi ticket management device 60 aggregates the sales from the electronic taxi ticket as the sales of the linked original magnetic taxi ticket 12, and transmits the aggregated sales of the magnetic taxi ticket 12 to the taxi operating company 20. This allows the taxi operating company 20 to charge the holder 10 as if the magnetic taxi ticket 12 was used. However, the taxi ticket management device 60 can also add distinction information indicating whether the usage mode is the magnetic taxi ticket 12 or the electronic taxi ticket as a breakdown of the sales of the magnetic taxi ticket 12, and provide it to the taxi operating company 20. This enables the holder 10 to confirm the usage mode of the magnetic taxi ticket 12.
[0011] (2) Details of the Embodiment Figure 1 is a configuration diagram of a taxi ticket system to which the taxi ticket management device 60 of the present embodiment is applied. As shown in Figure 1, the taxi ticket system is composed of a smartphone 11, a taxi operating company 20, a smartphone application server 30, a smartphone 41, on-board equipment of a taxi 50, and a taxi ticket management device 60. Each unit constituting the taxi ticket system is provided with a communication function, and is configured to be capable of communicating with each other via a communication network such as the Internet.
[0012] The smartphone 11 is a smartphone owned by the holder 10. Note that although the smartphone 11 is used in the present embodiment, it is also possible to use various electronic devices such as personal computers, in addition to various mobile terminals such as mobile phones, tablets, and notebook personal computers, other than smartphones. The electronic device in this case requires a communication function with the smartphone 41, the taxi ticket management device 60, etc., a function for operating the later-described smartphone application 13, various input operation functions by screen operation, a screen display function based on input operations, etc., but does not need to have a call function like a smartphone.
[0013] The holder 10 is a contractor who has been issued a magnetic taxi ticket 12 under a contract with the taxi operating company 20, or a person who holds the magnetic taxi ticket 12. On the smartphone 11, an application 13 is downloaded from the smartphone application server 30 based on the operation of the holder 10, and an electronic taxi ticket issued by the taxi ticket management device 60 is stored. The taxi ticket application is an application program downloaded by the smartphone 11, and is a program that performs processes such as a registration request for the magnetic taxi ticket 12 to the taxi ticket management device 60, an issuance request for an electronic taxi ticket, and provision of the issued electronic taxi ticket to the user 40.
[0014] The taxi operating company 20 performs operations such as taxi arrangement, and issues the magnetic taxi ticket 12 as a magnetic card based on the contract with the holder 10 and delivers it to the holder 10. The taxi operating company 20 functions as an issuer that issues magnetic taxi tickets. In this magnetic taxi ticket 12, a membership number that is assigned by the taxi operating company 20 and uniquely identifies the magnetic taxi ticket 12 is magnetically recorded. Furthermore, the taxi operating company 20 stores registration information such as the membership number assigned to the issued magnetic taxi ticket 12, usage conditions, and contractor (holder) information in the magnetic taxi ticket DB 21, and also provides the registration information to the taxi ticket management device 60. The taxi operating company 20 is equipped with a computer system that includes a control unit that performs various controls related to the issuance of these magnetic taxi tickets 12 and the storage and provision of registration information. The taxi operating companies 20 include taxi operators that provide taxi service, and ticket issuing companies that issue and bill for magnetic taxi tickets 12 that can be used in common with taxis from multiple taxi operators.
[0015] The smartphone application server 30 is a server that provides the taxi ticket application 13 based on a request from the smartphone 11 of the holder 10 who possesses the magnetic taxi ticket 12, and also notifies the holder 10 of the results of using the electronic taxi ticket. The smartphone app server 30 is operated independently of the taxi operating company 20 and the taxi ticket management device 60, however, the functions performed by the smartphone server 30 may also be provided by the taxi operating company 20 and the taxi ticket management device 60.
[0016] Smartphone 41 is a mobile terminal device owned by user 40, which shares electronic taxi tickets with owner 10's smartphone 11 and displays a QR code 42 corresponding to the electronic taxi ticket on its screen when using the electronic taxi ticket in a taxi. Unlike smartphone 11, smartphone 41 allows the use of electronic taxi tickets without the need for a taxi ticket app 13. The smartphone 41 can be brought into a taxi and is any mobile device equipped with communication functions such as email and a QR code display function 42; it does not require downloading a taxi ticket app 13 like the smartphone 11.
[0017] Taxi 50 is a taxi that accepts magnetic taxi tickets 12 issued by magnetic taxi ticket DB21. The taxi 50 is equipped with a meter 51, a rear-seat tablet 52, and a front-seat tablet 54, all of which are capable of sharing data with each other. Meter 51 is a meter installed in all taxis that displays the fare based on the distance traveled, etc., and displays the fare on the front seat tablet 54. The rear-seat tablet 52 is a payment device positioned for the rear seats and equipped with the function of acquiring various data according to the payment method presented by the passenger. The rear seat tablet 52 in this embodiment is equipped with a camera 53 for reading a QR code 42 presented on the user's smartphone 41, and is also equipped with a display that shows a screen prompting the user to hold the QR code 42 up to the camera 53.
[0018] The rear seat tablet 52 is equipped with a display and a touch panel for passengers to operate. It displays selection buttons for credit cards, electronic money, and electronic taxi tickets to allow passengers to choose their payment method, as well as the fare and advice for passengers. The front seat tablet 54 is positioned for the driver's seat and, based on the QR code 42 read by the rear seat tablet 52, requests payment from the taxi ticket management device 60 and receives the payment result. Furthermore, the front seat tablet 54 transmits the received payment result to the smartphone app server 30.
[0019] The taxi ticket management device 60 is comprised of a server system and includes a control unit that functions as a taxi ticket management unit 61 and a taxi ticket settlement unit 62 by executing a taxi ticket program, as well as a taxi ticket DB 63 that stores taxi ticket information related to magnetic taxi tickets 12 and electronic taxi tickets. The Taxi Ticket Management Department 61 stores registration information provided by taxi operating companies 20, registers magnetic taxi tickets 12 for holders 10 and issues electronic taxi tickets, and also provides QR codes 42 for electronic taxi tickets to users' smartphones 41. The taxi ticket payment unit 62 determines whether to approve or reject payment requests from the front seat tablet 54 of the taxi 50, and creates monthly sales data to send to the taxi operating company 20.
[0020] The taxi ticket DB 63 of the taxi ticket management device 60 is configured using one or more large-capacity storage media, such as a hard disk, and stores taxi ticket information related to magnetic taxi tickets 12 and electronic taxi tickets. Figure 2 shows the taxi ticket information stored in the taxi ticket DB63. As shown in Figure 2, the TaxiTicket DB63 stores ticket inspection information 631, ticket management information 632, electronic ticket management information 633, ticket transaction information 634, and other data. Of this taxi ticket information, the stored items for taxi tickets other than the electronic ticket management information 633 added for electronic taxi tickets are the same as the stored items for magnetic taxi tickets 12 in systems that do not issue electronic taxi tickets. In other words, the contents of the same stored items are stored in ticket inspection information 631, ticket management information 632, and ticket transaction information 634 for both magnetic taxi tickets 12 and electronic taxi tickets. This helps to minimize system changes.
[0021] The ticket inspection information 631 in Figure 2 is a table used to determine whether a taxi ticket is valid or not, and stores information such as the member number. Ticket inspection information 631 is used as one of the validity determination pieces of information to determine whether the taxi ticket presented by taxi 50 is valid or not. If the membership number of the presented taxi ticket is registered in ticket inspection information 631, it will be determined to be valid. Here, the membership number refers to the membership number for the taxi ticket, and includes the membership number assigned to the magnetic taxi ticket 12 issued by the taxi operating company 20, and the membership number for the electronic taxi ticket issued and assigned by the taxi ticket management device 60.
[0022] Both magnetic taxi tickets (Type 12) and electronic taxi tickets use the same n-digit membership number system. For example, both membership numbers consist of 16 digits, with digits 1-15 representing a unique number that identifies the member, and the last digit (16th digit) representing the type of taxi ticket. "0" indicates a magnetic taxi ticket 12 using a magnetic card, and "1" indicates an electronic taxi ticket 42 using a QR code. Furthermore, as long as a single digit representing the membership type is specified in one of the designated places, the total number of digits in the membership number is arbitrary. Also, although the explanation has used the example of a membership number (identification information) consisting entirely of numbers, it is also possible to use letters (including uppercase and lowercase letters). In this embodiment, to simplify the display, the membership number is represented by a total of 8 digits, including one digit representing the type of taxi ticket.
[0023] The ticket management information 632 in Figure 2 is a table for managing various information about taxi tickets (taxi ticket information), and stores the membership number, taxi ticket usage conditions (expiration date, maximum amount, maximum number of uses, maximum total amount), number of uses, and total amount used. The taxi ticket information stored in ticket management information 632 is updated only for the number of uses and total amount spent; other information such as the membership number and usage conditions are not updated. The number of uses and total amount spent may be updated the same number of times as the number of uses specified in the limit, as taxi tickets (magnetic taxi tickets, electronic taxi tickets) are used up to the number of times specified in the limit. The taxi ticket information (membership number and usage conditions) stored in the ticket management information 632 includes information on magnetic taxi tickets 12 provided as registration information by the taxi operating company 20, and information on electronic taxi tickets issued by the taxi ticket management device 60 linked to the magnetic taxi tickets 12. Electronic taxi tickets can be issued multiple times for a single magnetic taxi ticket 12, within the limits of the number of uses specified for that magnetic taxi ticket 12.
[0024] The membership number is the same as the membership number for taxi tickets (magnetic taxi ticket 12, electronic taxi ticket). The expiration date is the expiration date of the taxi ticket. The maximum amount is the maximum amount that can be settled per taxi ticket transaction (taxi ride using a taxi ticket). The maximum number of uses is the maximum number of times that can be paid for with a taxi ticket; if there is no limit, it will be set to "0". The maximum total amount is the maximum amount that can be paid with Takuticket; if there is no limit, it will be set to "0". The number of uses is recorded based on the number of transactions made using Takuticket, regardless of whether there is a usage limit or not. The total amount used is the total amount of transactions made using Takuticket, and is recorded regardless of whether or not there is a maximum limit on the total amount.
[0025] The electronic ticket management information 633 in Figure 2 is an information table for linking the magnetic taxi ticket 12 held by holder 10 with the electronic taxi ticket issued by the taxi ticket management device 60 based on this magnetic taxi ticket 12. It is not possible to manage the link between magnetic taxi tickets 12 and electronic taxi tickets without changing the contents of the existing information tables, namely ticket inspection information 631, ticket management information 632, and ticket transaction information 634. Therefore, by creating a new electronic ticket management information 633 for linking, it can be used without changing the existing information table.
[0026] The electronic ticket management information 633 stores the parent member number, child member number, etc. The parent membership number is the membership number of magnetic taxi ticket 12 held by holder 10. As mentioned above, the last digit of the parent membership number is "0", which represents magnetic taxi ticket 12. The child member number is the membership number of the electronic taxi ticket issued by the taxi ticket management device 60, linked to the parent member number (the membership number from which it was linked). As mentioned above, the last digit of the child member number is "1" to indicate an electronic taxi ticket. The electronic ticket management information 633 also stores other data, such as the electronic taxi ticket membership number and the holder information of the holder 10 who issued the electronic taxi ticket, as well as a URL (not shown) for displaying the information on the smartphone 41 via a QR code 42. The holder information of holder 10 contained in the QR code 42 is provided from the smartphone 41 to the smartphone application server 30 via the front seat tablet 54 of the taxi 50, and the smartphone application server 30 notifies holder 10 of the result of using the electronic taxi ticket. In this embodiment, a one-time QR code may be used as the QR code.
[0027] The ticket transaction information 634 in Figure 2 is a table that stores taxi ticket transaction information received along with payment requests from the payment terminal (front seat tablet 54) of the taxi 50. It stores information such as the terminal identification number, slip number, fare, advance payment, and membership number (membership number for magnetic taxi ticket 12, membership number for electronic taxi ticket). The terminal identification number is a number used to uniquely identify the front seat tablet 54 (and / or meter 51) installed in taxi 50, and functions as terminal identification information. The slip number is the slip number for the relevant transaction (taxi fare payment). The fare is the taxi charge, which is the total amount paid by the user, including any advance payments. The reimbursement amount is the portion of the fare that the taxi driver has paid in advance, such as toll road fees. The membership number is the membership number for your taxi ticket (magnetic taxi ticket 12 or electronic taxi ticket).
[0028] Takuticket DB63 also stores other data, such as sales data. The sales data consists of usage details for each owner, which are sent monthly to the taxi operating companies 20. In this embodiment, sales data is included in the data to be saved, but it may be configured to be deleted after a predetermined retention period has elapsed. Alternatively, by sending the usage details compiled on RAM to the taxi operating company 20, the sales data may be excluded from storage in the taxi ticket DB 63.
[0029] Next, the operation of the embodiment configured as described above will be explained. Figure 3 shows the overall flow (taxi processing) of using an electronic taxi ticket linked to a magnetic taxi ticket 12 by the taxi ticket system in this embodiment. In Figure 3, the procedure for processing taxi tickets is shown on the left, and on the right, the entities that perform operations and processes at each step are represented by thick horizontal lines and arrows. Note that the step numbers in Figure 3 correspond to the circled numbers in the system configuration diagram shown in Figure 1.
[0030] The taxi ticket processing shown in Figure 3 involves processing in four stages: pre-issuance processing of electronic taxi tickets, issuance processing of electronic taxi tickets, usage processing of electronic taxi tickets, and usage details processing. In the following taxi ticket processing, we will focus on explaining a single magnetic taxi ticket 12 newly issued to holder 10.
[0031] (a) Processing before issuing electronic taxi tickets (Steps 1 to 4) Step 1, "Magnetic Taxi Ticket Issuance," is an action performed by the holder 10 and the taxi operating company 20. In other words, when holder 10 enters into a usage agreement with the taxi operating company 20 regarding the issuance and use of magnetic taxi tickets 12, the taxi operating company 20 provides holder 10 with magnetic taxi tickets 12 in the form of a magnetic card. This service agreement specifies the validity period, maximum amount, maximum number of uses, and maximum total amount of the magnetic taxi tickets 12 issued. The taxi operating company 20 then stores the membership number assigned to the issued magnetic taxi ticket 12, the contract information stipulated in the usage agreement, and the contract holder's information such as address, name, telephone number, and email address provided by the holder (contract holder) in accordance with the contract, as registered information in the magnetic taxi ticket DB 21.
[0032] Step 2, "Provision of Registration Information," involves the actions of the taxi operating company 20 and the taxi ticket management device 60. In other words, the taxi operating company 20 provides the taxi ticket management device 60 with the registration information of the magnetic taxi tickets 12 stored in the magnetic taxi ticket DB 21. In this embodiment, the taxi operating company 20 provides registration information to the taxi ticket management device 60 each time it issues a magnetic taxi ticket 12, but it is also possible to provide multiple magnetic taxi tickets 12 issued before the contract start date all at once. Alternatively, the taxi operating company 20 may provide registration information only when requested by the taxi ticket management device 60, rather than providing registration information each time it issues a magnetic taxi ticket 12. In this case, when the taxi ticket management device 60 receives a request to issue an electronic taxi ticket (step 5 described later), if the membership number of the magnetic taxi ticket 12 is not registered in the taxi ticket DB 63 (in the case of the first issuance request), it requests registration information for that membership number from the taxi operating company 20. In response to this request, the taxi operating company 20 transmits the registration information for the relevant magnetic taxi ticket 12, and the taxi ticket management device 60 registers the provided registration information in the taxi ticket DB 63. With this modification, the registration information of the holder 10 of the magnetic taxi ticket 12 is provided to the taxi ticket management device 60 only when using an electronic taxi ticket, and not when not using an electronic taxi ticket.
[0033] Meanwhile, in the taxi ticket management device 60, the taxi ticket management unit 61 stores the registration information of the magnetic taxi tickets 12 provided by the taxi operating company 20 in the ticket management information 632. Figure 4 conceptually represents the state in which registration information is stored in the TaxiTicket DB63. As mentioned above, Figure 4 focuses on the newly issued magnetic taxi ticket 12, and therefore omits information on previously issued magnetic taxi tickets 12 and electronic taxi tickets (the same applies to other figures). Furthermore, in Figures 4, 7, 11, and 12, which show the update information for Takuticket DB63, the updated sections are distinguished by color within the frame.
[0034] As shown in Figure 4, the taxi ticket management unit 61 stores the contents of the registered information (member number of the magnetic taxi ticket 12, contract information, and subscriber information) in the ticket inspection information 631 and ticket management information 632 fields. In other words, the Taxi Ticket Management Unit 61 stores the membership number "12345670" of the newly registered magnetic Taxi Ticket 12 in the ticket inspection information 631. The first seven digits of the membership number (digits higher than the last digit) are a unique number that identifies the member, and the last digit representing the type is "0", which represents the magnetic Taxi Ticket 12. The Taxi Ticket Management Unit 61 also stores the following information from the Ticket Management Information Unit 632: Membership number "12345670", Expiration date "2023 / 12 / 31", Maximum amount "10,000", Maximum number of uses "5", and Maximum total amount "50,000". In addition to this contract information, the Taxi Ticket Management Unit 61 also stores subscriber information (not shown) in the Ticket Management Information Unit 632. However, subscriber information may be stored separately from the Ticket Management Information Unit 632 along with the membership number of the magnetic Taxi Ticket 12. However, at this point, neither the magnetic taxi ticket 12 nor the electronic taxi ticket linked to the magnetic taxi ticket 12 has been used, so there is no data stored in the ticket management information 632, such as the number of uses and total amount used, nor in the electronic ticket management information 633 or the ticket transaction information 634.
[0035] Step 3, "Save App," involves the actions of smartphone 11 and smartphone app server 30. The holder 10 operates their smartphone 11 to download a taxi ticket app 13 from the smartphone app server 30 for issuing an electronic taxi ticket linked to the issued magnetic taxi ticket 12. However, the method and source of obtaining the taxi ticket app 13 are not limited to this; it may also be obtained via various storage media such as a USB memory stick, or downloaded from a taxi operating company 20, a taxi ticket management device 60, or a server providing various smartphone apps.
[0036] Step 4, "Pre-registration," is an action performed on the smartphone (11). Figure 5 shows the screen displayed when registering a magnetic taxi ticket 12 to the taxi ticket app 13 on a smartphone 11. As shown in Figure 5, when the owner 10 launches the taxi ticket app 13 downloaded to their smartphone 11, the registration screen is displayed first. On this registration screen, when holder 10 enters the membership number "12345670" printed on the back of the magnetic taxi ticket 12 into the membership number input field 111 and then selects the registration button 112, the smartphone 11 saves the entered membership number to its memory. Each of the above steps 1 to 4 is performed once for each magnetic taxi ticket 12, and subsequent processes are repeated.
[0037] (b) Processing of issuing electronic taxi tickets (Steps 5 and 6) Step 5, "Issuing Electronic Taxi Tickets," involves the operation of the smartphone 11 and the taxi ticket management device 60. After the holder 10 completes the registration in step 4, and again after registering, when they launch the taxi ticket app 13, the electronic taxi ticket issuance screen will be displayed on the smartphone 11. Figure 6 shows the display screen when issuing an electronic taxi ticket. Figure 6(a) shows the issuance conditions input screen where the conditions for issuing the electronic taxi ticket are entered, and Figure 6(b) shows the sharing screen for sharing the issued electronic taxi ticket.
[0038] As shown in Figure 6(a), the issuance conditions screen displays the registration information field 113, the issuance conditions field 114, and the issuance button 115. The registration information field 113 displays some of the registration information for the magnetic taxi ticket 12 linked to the electronic taxi ticket, including the membership number "12345670", the limit "50,000 yen, 10,000 yen / ride, 5 rides", and the expiration date "2023 / 12 / 31". Specifically, in step 4, the smartphone 11 sends the membership number "12345670" stored in its memory to the taxi ticket management device 60. Based on the received membership number, the taxi ticket management device 60 reads the maximum total amount, maximum amount, maximum number of uses, and expiration date for the corresponding membership number from the ticket management information 632 (see Figure 4) and sends it to the smartphone 11, thereby displaying the registration information field 113. The Taxi Ticket Management Unit 61 sends the number of uses obtained by subtracting the number of uses from the maximum number of uses in the ticket management information 632 as the upper limit. For example, if the ticket management information 632 is in the state shown in Figure 4, it sends 5-0=5, which is the upper limit of 5 uses minus the number of uses of 0.
[0039] Holder 10 enters the following information in the issuance conditions field 114 of the issuance conditions input screen, as illustrated in Figure 6(a): maximum usage limit per use for electronic taxi tickets: "5,000 yen", number of uses: "1", expiration date: "2022 / 05 / 30", and number of tickets: "2". Here, the example in Figure 6(a) shows the case where the number of uses is 1, but it is also possible to set it to 2 or more times (however, within the limit of the number of uses of the linked magnetic taxi ticket 12). For example, by setting the number of uses to 2, the user who receives (shares) the electronic taxi ticket can use the electronic taxi ticket not only when returning home from a specific venue, but also when arriving at that venue.
[0040] Smartphone 11 checks whether the input in the issuance conditions field 114 is within the upper limit displayed in the registration information field 113. If it is within the range, the issuance button 115 is made selectable. If it exceeds the range, it is made selectable, and the exceeded items are explicitly displayed. When holder 10 selects the available issue button 115, smartphone 11 sends the entered issuance conditions along with the membership number of the magnetic taxi ticket 12 to the taxi ticket management device 60 to request issuance.
[0041] When the taxi ticket management device 60 receives an issuance request from the smartphone 11, it issues an electronic taxi ticket linked to the magnetic taxi ticket 12 of the requested member number and updates the taxi ticket database 63. Figure 7 shows the state of the TaxiTicket DB63 after it has been updated by the issuance of an electronic taxi ticket. Figure 7 shows the state after issuing an electronic taxi ticket based on the issuance conditions entered in Figure 6(a), with Figure 4 being the state before the update. The data updated by the issuance of electronic taxi tickets includes ticket inspection information 631, ticket management information 632, and electronic ticket management information 633. In other words, the taxi ticket management unit 61 assigns a number of membership numbers for electronic taxi tickets corresponding to the requested number of tickets to be issued, and links the two membership numbers by storing the membership number of the magnetic taxi ticket 12 as the parent membership number and the membership number of the electronic taxi ticket as the child membership number in the electronic ticket management information 633. Specifically, as shown in Figure 7, the Taxi Ticket Management Unit 61 stores the membership number "12345670" of the magnetic Taxi Ticket 12 as the parent membership number, and the membership numbers "34567891" and "56789011" of the electronic Taxi Tickets as child membership numbers.
[0042] Furthermore, the Taxi Ticket Management Department 61 stores the membership numbers "34567891" and "56789011" of the issued electronic taxi tickets in the ticket inspection information 631.
[0043] Furthermore, the Taxi Ticket Management Department 61 registers the issued electronic taxi tickets in the Ticket Management Information 632. In other words, for each of the electronic taxi tickets with membership numbers "34567891" and "56789011", the issuance conditions for the electronic taxi tickets are set to a usage limit of "5,000 yen" per use, a usage limit of "1 time", and an expiration date of "2022 / 05 / 30". Furthermore, the Taxi Ticket Management Unit 61 calculates the usage limit per use multiplied by the number of uses (= 5,000) and stores it in the total limit amount. Please note that since this is the issuance stage of the electronic taxi ticket, the number of uses and total amount spent will be recorded as zero (0).
[0044] Furthermore, the Taxi Ticket Management Unit 61 estimates that the electronic taxi tickets have been used based on the issuance of the two electronic taxi tickets, and updates the ticket management information 632 of the linked magnetic taxi ticket 12. In other words, the Taxi Ticket Management Unit 61 stores the total number of uses for each electronic taxi ticket issued this time (1 time + 1 time = 2 times) in the usage count for the linked member number "12345670" in the ticket inspection information 631, and also stores the total amount of the upper limit (5,000 yen + 5,000 yen = 10,000 yen) in the total usage amount.
[0045] In this way, the issuance of an electronic taxi ticket is presumed to indicate that the electronic taxi ticket has been used, and the number of uses and total amount used for the magnetic taxi ticket 12 are updated accordingly. This prevents the issuance of electronic taxi tickets exceeding the maximum total amount stipulated in the contract for the linked magnetic taxi ticket 12. When issuing the next electronic taxi ticket, it will be possible to issue an electronic taxi ticket within the range of 40,000 yen (= 50,000 yen - 10,000 yen) in the state shown in Figure 7, which is the amount obtained by subtracting the total amount used from the maximum total amount of the magnetic taxi ticket 12. However, there are cases where the electronic taxi ticket is actually used but the fare is lower than the maximum limit, or where the electronic taxi ticket is not used within its validity period. In such cases, the maximum limit, etc., of the magnetic taxi ticket 12 linked to the electronic taxi ticket will be corrected in the maintenance process (step 14) described later.
[0046] Furthermore, in ticket management information 632, the number of uses and total amount spent for magnetic taxi tickets whose membership number ends in "0" will be updated according to the taxi ticket transaction information received from taxi 50, even if the magnetic taxi ticket (magnetic card) with the relevant membership number is used.
[0047] After issuing the electronic taxi ticket and updating the taxi ticket DB63 as described above, the taxi ticket management unit 61 notifies the smartphone 11 that the issuance is complete by sending the membership numbers of the issued electronic taxi tickets, "34567891" and "56789011," and the URL (not shown) for the QR code 42 stored in the electronic ticket management information 633.
[0048] Meanwhile, the smartphone 11, upon receiving the issuance completion notification, stores all the received information, such as the membership number and URL of the electronic taxi ticket, received from the taxi ticket management device 60, in its storage unit. Then, the smartphone 11 displays the shared screen shown in Figure 6(b), with a registration information field 113 at the top, and below that, electronic taxi ticket information 117 and its sharing button 118, and electronic taxi ticket information 119 and its sharing button 120. Information 117 and 119 for the electronic taxi ticket displays the issued electronic taxi ticket membership number "34567891" and "56789011", the limit "5,000 yen, 5,000 yen / ride, 1 ride", and the expiration date "2020 / 05 / 30". The details of this limit correspond to the maximum amount, maximum total amount, and maximum number of uses stored in ticket management information 632 (see Figure 7). The share buttons 118 and 120 are for providing the two issued electronic taxi tickets to a third party (user).
[0049] Step 6, "Sharing Electronic Taxi Tickets," involves actions performed by smartphones 11 and 41. Holder 10 selects one of the two share buttons 118 and 120 displayed on the sharing screen in Figure 6(b) in order to provide the issued electronic taxi ticket to user 40. The smartphone 11 reads from its memory unit a URL for displaying the electronic taxi ticket corresponding to the selected share buttons 118 and 120 as a QR code 42. Then, the owner 10 is prompted to select from the selection screen of the smartphone 11 the functions to be provided, such as email, SMS (Short Message Service), and SNS (Social Networking Service), and the person to share with (smartphone 41 in this embodiment). Smartphone 11 uses the provided function selected by owner 10 to share the retrieved URL with the selected user 40's smartphone 41. Smartphone 41 stores the URL for the electronic taxi ticket provided by owner 10 in its memory unit.
[0050] Next, we will explain situations in which shared electronic taxi tickets are used. When taxi 50, carrying passenger 40, arrives at the drop-off point, the front seat tablet 54 displays the payment screen. Figure 8 shows the contents of the payment screen displayed on the front seat tablet 54. The main menu screen shown in Figure 8(a) displays the payment amount (fare) supplied from the meter 51, a fare column 541 for advance payments, an explanation column 542 for displaying operating instructions and comments for passengers, and selection buttons. The selection buttons include a cash selection button, a credit card selection button, an electronic money selection button, and a taxi ticket selection button 543.
[0051] If the taxi driver confirms with the passenger (user 40) that they will be using a taxi ticket (magnetic taxi ticket 12 or electronic taxi ticket), the taxi driver (50) selects the taxi ticket selection button 543. Then, the front seat tablet 54 displays the taxi ticket sales screen shown in Figure 8(b), with touch buttons and a QR code button 544 corresponding to the taxi ticket reading method. In this embodiment, the electronic taxi ticket membership number is read using the QR code 42. Therefore, once the taxi driver 50 confirms with the user 40 that they are using the electronic taxi ticket, they select the QR code button 544. As a result, the explanatory display area 542 of the front seat tablet 54 displays a comment prompting the user 40 to scan the QR code 42 with the camera 53 of the rear seat tablet 52, as shown in Figure 8(c), and the taxi driver 50 informs the user 40 of this. In this embodiment, the taxi driver 50 selects the payment method, etc., on the front seat tablet 54 according to the response from the passenger user 40. However, the series of selection (input) items described above may also be displayed on the rear seat tablet 52, allowing the passenger 40 in the rear seat to make the selection. In this case, the selection made on the rear seat tablet 52 will be provided and displayed on the front seat tablet 54 in conjunction with the selection made on the rear seat tablet 52, so that the driver can recognize the payment method, etc.
[0052] (c) Processing of electronic taxi tickets (Steps 7-14) Step 7, "Displaying the Electronic Taxi Ticket," involves the operation of the smartphone 41 and the taxi ticket management device 60. User 40, having received instructions from the taxi driver 50 to scan the QR code 42, accesses the URL stored in the memory of smartphone 41 during the sharing process with smartphone 11 (step 6). As a result, the taxi ticket management unit 61 of the taxi ticket management device 60 displays the electronic taxi ticket membership number as a QR code 42 to the smartphone 41 in response to the accessed URL, and the QR code 42 is displayed on the screen of the smartphone 41.
[0053] Step 8, "Electronic Taxi Ticket Reading," involves the operation of the smartphone 41 and the rear seat tablet 52. Figure 9 is an explanatory diagram of the presentation state of QR code 42. Following the driver's instructions, user 40 holds the QR code 42 displayed on smartphone 41 up to the camera 53 of rear seat tablet 52, as shown in Figure 9. The rear seat tablet 52 then reads the QR code 42 held up to the camera 53, reads the electronic taxi ticket membership number (for example, "34567891") and the holder information of holder 10, and provides this information to the front seat tablet 54.
[0054] Step 9, "Payment Request," involves the operation of the taxi ticket management device 60 and the front seat tablet 54. When the front seat tablet 54 receives the membership number from the rear seat tablet 52, it transmits payment request information, including the membership number, the meter amount provided by the meter 51, the amount advanced by the driver entered into the front seat tablet 54, the terminal identification number, and the slip number, to the taxi ticket management device 60 to request payment via electronic taxi ticket. Figure 10 shows the content displayed on the front seat tablet 54 when a payment request is made. When the front seat tablet 54 requests payment from the taxi ticket management device 60, as shown in Figure 10(a), the explanatory display area 542 displays that the payment is being inquired about at the payment center (taxi ticket management device 60).
[0055] Step 10, "Approval / Rejection Determination and Update," is an operation performed within the taxi ticket management device 60. Meanwhile, in the taxi ticket management device 60, when the taxi ticket payment unit 62 receives a payment request, it determines whether the electronic taxi ticket can be used, updates the taxi ticket DB 63, and sends a payment response to the rear seat tablet 52. First, the taxi ticket payment unit 62 determines whether the electronic taxi ticket for member number "3456789011" is usable by checking whether the fare (total of metered fare and advance payment) exceeds the upper limit for that member number stored in the ticket management information 632. In this case, the fare is 3,500 yen and the upper limit is 5,000 yen, so the taxi ticket payment unit 62 determines that the electronic taxi ticket is usable.
[0056] Figure 11 shows the status of the taxi ticket DB63 after it has been updated by a payment request. When the taxi ticket payment unit 62 determines that an electronic taxi ticket is available, it saves the payment request information obtained from the front seat tablet 54 to the ticket transaction information 634 and updates the ticket management information 632. The fare is the sum of the meter amount and the advance payment from the payment request information. In other words, the taxi ticket payment unit 62 stores the terminal identification number "999996661", the slip number "123", the fare "3,500", the advance payment "0", and the member number "34567891" in the ticket transaction information 634. Furthermore, the Taxi Ticket Payment Unit 62 updates the usage count for member number "34567891" in the ticket management information 632 from 0 to 1, and the total usage amount from 0 to 3,500. Here, the total usage amount of 3,500 yen is the fare amount, which is the sum of the metered amount and the advance payment. Furthermore, the usage count and total amount spent on magnetic taxi ticket 12, to which the electronic taxi ticket is linked, have already been updated to 2 uses and 10,000 yen, based on the assumption that it was used in step 5 when the electronic taxi ticket was issued. Therefore, these will not be updated when the electronic taxi ticket is used for payment.
[0057] Step 11, "Payment Response," involves the operation of the taxi ticket management device 60 and the front seat tablet 54. If the taxi ticket management device 60 determines that the electronic taxi ticket can be used, it notifies the front seat tablet 54 of the taxi 50 that payment has been completed as a response to the payment request. Upon receiving this payment completion notification, the front seat tablet 54 displays a message in the explanation display area 542 indicating that the payment has been completed, as well as a message prompting the user to select a confirmation button, as shown in Figure 10(b).
[0058] Step 12, "Result Notification," involves the operation of the front seat tablet 54 and the smartphone app server 30. When the driver of taxi 50 checks the display in the explanation section 542 of the front seat tablet 54 and selects the confirmation button, the front seat tablet 54 notifies the smartphone app server 30 of the membership number "34567891" of the electronic taxi ticket used and the holder information of holder 10 read from the QR code 42, as a notification that the electronic taxi ticket has been used.
[0059] Step 13, "Result Notification," involves the actions of the smartphone app server 30 and the owner 10. When the smartphone app server 30 receives a result notification from the front seat tablet 54, it identifies the holder 10 corresponding to the holder information and notifies the smartphone 11 that the electronic taxi ticket with membership number "34567891" has been used (result notification). This result notification allows the holder 10 to confirm that the electronic taxi ticket has been used by checking the result notification received on their smartphone 11.
[0060] Step 14, "Maintenance," is an operation within the taxi ticket management device 60 and is performed by batch processing at predetermined intervals. In this embodiment, it is performed once a day. In other words, the taxi ticket settlement unit 62 performs maintenance on the ticket management information 632 by restoring the number of uses and total amount used for electronic taxi tickets used within the upper limit and electronic taxi tickets not used within their validity period to the magnetic taxi ticket 12 to which the electronic taxi ticket is linked. Figure 12 shows the status of the Takuticket DB63 during maintenance. The Taxi Ticket Settlement Unit 62 retrieves all electronic Taxi Ticket membership numbers whose last digit is "1" and whose ticket transaction information 634 was updated (newly added) between the previous maintenance and the current maintenance. Furthermore, the Taxi Ticket Settlement Unit 62 retrieves the membership numbers of the magnetic Taxi Tickets 12 to which each retrieved membership number is linked from the electronic ticket management information 633. The taxi ticket payment unit 62 then calculates an amount for each member number subject to maintenance (one entry, "34567891" in the example in Figure 12) by subtracting the total amount used, "3,500", from the upper limit total amount "5,000" in the ticket management information 632 (unused amount = 1,500), and uses this amount as the amount to be deducted from the total amount used, "10,000", of the linked magnetic taxi ticket 12.
[0061] Furthermore, the taxi ticket payment unit 62 retrieves all unused electronic taxi tickets from the ticket management information 632 for member numbers whose validity period has expired between the previous maintenance and the current maintenance, and whose last digit is "1". In addition, the taxi ticket payment unit 62 retrieves from the electronic ticket management information 633 the member numbers of the magnetic taxi tickets 12 to which each retrieved member number's electronic taxi ticket is linked. The Taxi Ticket Payment Unit 62 then subtracts the total amount of the maximum total for all member numbers of unused electronic taxi tickets subject to maintenance (in the example in Figure 12, the total for one transaction, "56789011", is 5,000 yen). The taxi ticket payment unit 62 calculates the total amount to be deducted for each magnetic taxi ticket linked to partially used and unused electronic taxi tickets (in the example in Figure 12, the total amount is 6,500 yen), and deducts this amount from the total amount used in the ticket management information 632 (10,000 yen in Figure 11) to return to the actual total amount used (3,500 yen in Figure 12).
[0062] Furthermore, the taxi ticket settlement unit 62 subtracts the number of unused electronic taxi tickets linked to the magnetic taxi ticket 12 from the number of uses of the magnetic taxi ticket 12. In the example in Figure 12, there is one unused electronic taxi ticket for member number "56789011", so the number of uses for member number "12345670" is changed from 2 to 1.
[0063] (d) Processing of usage details (Steps 15 and 16) This usage details processing is performed at predetermined intervals (monthly in this embodiment). Step 15, "Transmission of Sales," is an operation performed by the taxi ticket management device 60 and the taxi operating company 20. The taxi ticket settlement unit 62 creates a usage statement for each magnetic taxi ticket 12, summarizing the ticket transaction information 634 at predetermined intervals. The usage details generated will list the transaction information for each magnetic taxi ticket 12 when it was used, as well as the transaction information for the electronic taxi ticket linked to that magnetic taxi ticket 12 when it was used, and will also calculate the total fare (including advance payments). The taxi ticket payment unit 62 sends the usage details for each magnetic taxi ticket 12 created to the taxi operating company 20 as sales data.
[0064] After sending the usage details, the taxi ticket payment unit 62 extracts the management information of magnetic taxi tickets 12 whose membership number ends in "0" and which have not yet reached their expiration date from the ticket management information 632, resets the number of uses and total amount used, and saves it in the ticket management information 632 for the next predetermined period. Furthermore, the ticket management information 632 may be newly created at each predetermined period for which usage details are generated.
[0065] Step 16, "Details and Invoice," is an action performed by the owner 10 and the taxi operating company 20. When the taxi ticket management device 60 receives usage details for each magnetic taxi ticket 12, the taxi operating company 20's taxi ticket issuance and sales management department stores the received usage details in the magnetic taxi ticket DB 21 and also sends the usage details and invoice for each magnetic taxi ticket 12 to the holder 10 of that ticket. [Examples]
[0066] The taxi ticket system described above can be applied to the following embodiment. (a) Use of electronic taxi tickets by seminar guests When having guests of a seminar with dozens of participants use electronic taxi tickets, the tickets can be distributed in advance, allowing guests to use them as users when traveling to the seminar venue. Furthermore, while it was impractical for dozens of guests to use separate magnetic taxi tickets (Magnet Taxi Ticket 12) when boarding different taxis, this becomes possible through the sharing of electronic taxi tickets.
[0067] (b) Use of electronic taxi tickets by talents belonging to talent agencies The talent agency holds the magnetic taxi ticket 12, and the affiliated talent uses electronic taxi tickets. For example, an entertainment agency can provide (share) electronic taxi tickets to the smartphones of its talent's managers, who can then provide them to the talent's smartphones, allowing the talent to use taxi tickets. In this case, electronic taxi tickets are provided to affiliated talents by transferring a URL from the manager's smartphone to the talent's smartphone. Even for this type of usage, the regulations regarding the maximum amount and billing can be consolidated under the talent agency.
[0068] (c) Use of electronic taxi tickets by company employees on business trips to regional areas A company that possesses magnetic taxi tickets (Type 12) will use electronic taxi tickets for employees on business trips to regional areas. For example, if the magnetic taxi ticket 12 is located at the head office, and the business trip destination is far from the head office, an electronic taxi ticket can be easily provided to and used by the employee on the business trip. In the case of the magnetic ticket 12, which is a physical magnetic card, there is a risk of loss or theft if the employee carries the magnetic ticket 12 with them on a business trip. However, employees on business trips can use the electronic ticket without worrying about loss or theft.
[0069] (d) In addition, electronic taxi tickets will be usable in situations where it was difficult to use magnetic taxi tickets 12, such as for entertaining clients or at weddings.
[0070] Although one embodiment of a taxi ticket system utilizing the taxi ticket management device 60 of the present invention has been described above, the present invention is not limited to the embodiment described above, and various modifications can be made within the scope of each claim. For example, the embodiments and examples described above described a case in which a user 40 other than the holder 10 uses the QR code 42 to obtain an electronic taxi ticket. However, a modified example will be described in which the holder 10 himself uses the electronic taxi ticket. (i) Variation 1 In this modified example 1, the holder 10 uses the electronic taxi ticket using the QR code 42, just like the user 40. In other words, when the holder 10 selects the share buttons 118 and 120 shown in Figure 6(b), the smartphone 41 (taxi app 13) displays a holder button and a third-party button on the selection screen for selecting the user of the electronic taxi ticket. If the third-party button is selected, the screen transitions to the screen prompting the user to select a share, as described in the embodiment. On the other hand, if the owner button is selected, the owner's smartphone 11 displays a QR code 42 using the URL stored in the device corresponding to the selected share buttons 118 and 120, and has the rear seat tablet 52 of the taxi 50 read it. This allows holder 10 to use the electronic taxi ticket on their smartphone 11 without having to carry the magnetic taxi ticket 12.
[0071] (b) Variation 2 The embodiments and modifications described above describe the case in which holder 10 uses an electronic taxi ticket using a QR code 42. In contrast, in Modification 2, the near-field communication (NFC) of the smartphone 11 is used to provide the electronic taxi ticket membership number and the holder information of holder 10 to the payment terminal conventionally installed in the taxi 50. The payment terminal, having read the electronic taxi ticket membership number and holder information, sends the read information to the taxi ticket management device 60, similar to step 9, to request payment. The subsequent processing is the same as in the embodiment. In this modified example 2, the holder 10 can ride in the taxi 50 using the electronic taxi ticket without having to carry the magnetic taxi ticket 12, which may be lost or stolen.
[0072] (h) Other tortures The embodiments and modifications described above describe the case in which the taxi operating company 20 provides the registration information (membership number, contract information, and subscriber information) of the magnetic taxi ticket 12 to the taxi ticket management device 60 (Step 2). Alternatively, the owner's smartphone 11 may provide the registration information to the taxi ticket management device 60. In other words, when the holder 10 pre-registers the smartphone app 13 on the smartphone 11 (step 4), they transmit the registration information of the magnetic taxi ticket 12 to the taxi ticket management device 60.
[0073] Furthermore, the smartphone 11 may be configured to transmit only the membership number of the magnetic taxi ticket 12 that has been pre-registered to the taxi ticket management device 60. In this case, the taxi ticket management device 60 may request the taxi operating company 20 to provide registration information for the membership number of the magnetic taxi ticket 12 obtained from the smartphone 11, and in response to this request, obtain the registration information of the magnetic taxi ticket 12 provided by the taxi operating company 20.
[0074] The explanation described how the taxi ticket management device 60 issues electronic taxi tickets linked to magnetic taxi tickets 12 and handles payment, but it is also possible to perform these tasks in cooperation with separate servers (devices). In other words, the issuance process for electronic taxi tickets is handled by the electronic taxi ticket server, and the payment processing for the use of electronic taxi tickets is handled by the payment server. In this case, the electronic taxi ticket server stores ticket inspection information 631, ticket management information 632, and electronic ticket management information 633 in the magnetic taxi ticket DB. Meanwhile, the payment server stores the electronic ticket management information 633 and the ticket transaction information 634 in the payment database. The payment server obtains the linking information (parent member number and corresponding child member number) to be stored in the electronic ticket management information 633 from the electronic taxi ticket server.
[0075] Furthermore, the embodiments and modifications described above describe the case where the taxi ticket management device 60 issues an electronic taxi ticket to the smartphone 11 that has made an issuance request. Alternatively, in response to an issuance request from the owner's (owner's) In this case, the taxi ticket management device 60 obtains the access method (such as email or text message) for the smartphone 41 from the smartphone 11 along with the request to issue an electronic taxi ticket. The taxi ticket management device 60 then directly provides the smartphone 41 with a URL for displaying the QR code described in the embodiment. As a result, holder 10 can provide the electronic taxi ticket to user 40 in a single process of requesting the issuance of an electronic taxi ticket, without having to perform two separate operations (issuing the electronic taxi ticket in step 5 and sharing the electronic taxi ticket in step 6).
[0076] In this embodiment and modification, the holder 10 can freely decide when to share the issued electronic taxi ticket with the holder 10. However, in this modification, the electronic taxi ticket is issued to the smartphone 41 at the same time as the operation to request the issuance of the electronic taxi ticket. Therefore, the holder 10 cannot adjust the time between the request for the issuance of the electronic taxi ticket and its provision to the smartphone 41. Therefore, when a request for the issuance of an electronic taxi ticket is made, it is possible to specify the date and time on which the electronic taxi ticket will be provided from the taxi ticket management device 60 to the smartphone 41. In other words, the taxi ticket management device 60 manages the time for electronic taxi tickets by registering the date and time specified on the smartphone 11, issues electronic taxi tickets when requested, and provides electronic taxi tickets at the specified date and time.
[0077] Furthermore, in the embodiments and modifications described, the magnetic taxi ticket 12 on a magnetic card was used as the issuer of the electronic taxi ticket and the taxi ticket to which the electronic taxi ticket is linked. However, if identification information (membership number) is defined, it is also possible to target taxi tickets on other media. For example, electronic taxi tickets may be issued using media other than magnetic taxi tickets 12, such as IC cards or paper taxi tickets. In any case, the membership number is printed (as specified) on the surface of the taxi ticket in a manner that is recognizable to the holder 10.
[0078] Furthermore, in the embodiment and modifications described above, the terminal identification number that identifies the payment terminal of the taxi 50 is included in the storage of the ticket transaction information 634, and in step 9, it is described as being transmitted from the front seat tablet 54 to the taxi ticket payment unit 62. However, the terminal identification number may be excluded from the items to be stored and transmitted. By excluding the terminal identification number, the usage details created by the Taxi Ticket Payment Unit 62 in step 15 and sent to the taxi operating company 20 will not include the terminal identification number. However, it is still possible to identify the taxi 50 (payment terminal) on which the Taxi Ticket was used by the slip number.
[0079] Furthermore, the embodiments and modifications described above also included a case where the QR code provided to the smartphone 41 by the taxi ticket management unit 61 of the taxi ticket server 60 includes holder information in addition to the electronic taxi ticket membership number. As a result, the membership number and holder information are provided to the smartphone application server 30 via the front seat tablet 54, and the smartphone application server 30 notifies the holder 10 of the results of using the electronic taxi ticket. In response to this, the Taxi Ticket Management Department 61 may send a QR code to the smartphone 41 that includes the electronic Taxi Ticket membership number but does not include the holder's information. In this case, the notification of the results of using the electronic taxi ticket can also be done as shown in the following variations 1 to 3.
[0080] In the first variation 1, in step 5, after issuing an electronic taxi ticket on the smartphone 11, the taxi ticket app 13 sends the electronic taxi ticket membership number and the recipient information (email address, etc.) of the smartphone 11 to the smartphone app server 30, and the smartphone app server 30 registers the received electronic taxi ticket membership number and recipient information. Then, when the result is notified from the front seat tablet 54 (step 12), the smartphone app server 30 searches for the corresponding smartphone 11 destination information from the electronic taxi ticket membership number that is also notified, and notifies the smartphone 11 of the searched destination information of the usage result (step 13).
[0081] In the following variation 2, the results of using the electronic taxi ticket are notified to the smartphone 11 from the front seat tablet 54 via the smartphone app server 30, but rather from the taxi ticket server 60 to the smartphone 11. In other words, after the taxi ticket payment unit 62 of the taxi ticket server 60 sends a payment notification (step 11) to the front seat tablet 54, or in parallel with the payment notification, the taxi ticket management unit 61 reads the communication destination information corresponding to the electronic taxi ticket's membership number and notifies the smartphone 11 of the result. Here, the taxi ticket management unit 61 reads the communication destination information contained in the subscriber information stored in the taxi ticket DB 63 from the membership number of the magnetic taxi ticket 12, which is linked to the electronic taxi ticket's membership number and is stored in the taxi ticket DB 63.
[0082] In the following variation 3, steps 12 and 13 are eliminated, so that the results of using the electronic taxi ticket are not notified to the smartphone 11 (owner 10). In this case, the owner 10 of the smartphone 11 can find out through the usage details of the magnetic taxi ticket 12 sent from the taxi operating company 20 (step 16). In these usage details, the use of the electronic taxi ticket is recorded as the use of the magnetic taxi ticket 12, but the owner 10 can verify this from the usage date and time, amount, etc. in the usage details. However, by combining the previously described modified version, in which the taxi ticket management device 60 adds and transmits information distinguishing the usage type (magnetic taxi ticket 12, electronic taxi ticket) as a breakdown of sales of magnetic taxi tickets 12, with this modified version 3, the holder 10 can easily confirm the use of the electronic taxi ticket. This modified version eliminates the inconvenience of having to receive a notification on your smartphone 41 every time an electronic taxi ticket is used.
[0083] As described above, according to the taxi ticket system to which this embodiment and modified taxi ticket management device 60 are applied, by issuing electronic taxi tickets linked to the magnetic taxi tickets 12, the relationship between the holder 10 (contractor) of the magnetic taxi ticket and the user becomes less close, and the convenience of the magnetic taxi ticket 12 is improved. In other words, since the electronic taxi ticket can be provided (shared) to the user 40 on their smartphone 41 before the user boards the taxi 50, there is no need to have the user accompany the user when they board the taxi 50 to scan the magnetic taxi ticket 12. Therefore, even if more electronic taxi tickets are issued, the increase in the burden on holders can be kept to a minimum. Furthermore, since electronic taxi tickets are issued within the scope of the magnetic taxi ticket 12 contract, no new contract is required for the issuance of electronic taxi tickets.
[0084] Furthermore, it is possible to set a limit on the number of times the electronic taxi ticket can be used. For example, by setting the limit to two uses, user 40 can use the electronic taxi ticket not only when returning home from the designated venue, but also when arriving at the designated venue.
[0085] Furthermore, the membership number for electronic taxi tickets has the same structure as the membership number for magnetic taxi tickets 12. This means that taxi companies 20 that issue magnetic taxi tickets 12 only need to change a part of their processing program, etc., without having to change the hardware such as the rear seat tablets 52 and front seat tablets 54 already installed in each taxi 50, thus reducing the burden associated with introducing electronic taxi tickets.
[0086] Furthermore, this embodiment can also be configured as follows. (1) The embodiment described in Configuration 1 provides a taxi ticket management device comprising: an acquisition means for acquiring identification information and usage conditions specified for a taxi ticket that enables the use of a taxi with deferred payment of the usage fee; a storage means for storing the acquired identification information and usage conditions of the taxi ticket; an electronic taxi ticket issuing means for issuing an electronic taxi ticket linked to the stored taxi ticket, within the scope of the usage conditions of the taxi ticket, based on an issuance request from the holder of the stored taxi ticket; and an electronic taxi ticket providing means for providing the issued electronic taxi ticket. (2) The embodiment described in Configuration 2 provides a taxi ticket management device according to Configuration 1, which includes a payment request receiving means that receives payment information having identification information and fare for an electronic taxi ticket transmitted from equipment installed in a taxi, along with a payment request, and a payment means that performs payment by storing the received payment information in ticket transaction information. (3) In the embodiment described in Configuration 3, the storage means stores identification information of a taxi ticket or electronic taxi ticket, the number of uses, and the total amount used, and when a payment request is received, it adds 1 to the number of uses of the received identification information and adds the fare to the total amount used, thereby providing a taxi ticket management device as described in Configuration 1 or Configuration 2. (4) In the embodiment described in Configuration 4, the taxi ticket management device described in Configuration 1, Configuration 2, or Configuration 3 is provided, characterized in that the electronic taxi ticket issuing means issues an electronic taxi ticket by assigning the identification information of the electronic taxi ticket to the same identification code system as the identification information of the taxi ticket. (5) The embodiment described in Configuration 5 provides a taxi ticket management device according to any one of Configurations 1 to 4, characterized in that the identification information of the taxi ticket and the electronic taxi ticket is defined by a predetermined number of digits, the predetermined digit being a distinguishing number that distinguishes the taxi ticket and the electronic taxi ticket. (6) The embodiment described in configuration 6 further stores identification information and usage conditions of the issued electronic taxi ticket, and the present invention provides a taxi ticket management device according to any one of configurations 1 to 5. (7) The embodiment described in Configuration 7 provides a taxi ticket management device according to any one of Configurations 1 to 6, characterized in that the storage means stores the identification information, expiration date, maximum amount, maximum number of uses, and maximum total amount of a taxi ticket or electronic taxi ticket as the usage conditions. (8) The embodiment described in Configuration 8 provides a taxi ticket management device according to any one of Configurations 1 to 7, characterized in that the acquisition means acquires the identification information and usage conditions of the taxi ticket from the issuer of the taxi ticket or the mobile terminal of the holder of the issued taxi ticket. (9) The embodiment described in configuration 9 is characterized in that the taxi ticket is a magnetic card, IC card, or paper card on which identification information is defined, and the taxi ticket management device is described in any one of configurations 1 to 8. (10) In the embodiment described in configuration 10, the electronic taxi ticket providing means provides a URL for displaying identification information of an electronic taxi ticket issued by the electronic taxi ticket issuing means, and the taxi ticket management device is described in any one of configurations 1 to 9. (11) The invention described in configuration 11 provides a taxi ticket management program that enables a computer to implement the following: an acquisition function for acquiring identification information and usage conditions specified for a taxi ticket that allows the use of a taxi with deferred payment of the usage fee; a storage function for storing the usage conditions and identification information of the acquired taxi ticket in a storage means; an electronic taxi ticket issuance function for issuing an electronic taxi ticket linked to the stored taxi ticket, within the scope of the usage conditions of the taxi ticket, based on an issuance request from the holder of the stored taxi ticket; and an electronic taxi ticket provision function for providing the issued electronic taxi ticket. [Explanation of symbols]
[0087] 10 Holders 11 Smartphone 12 Magnetic Taxi Tickets 13 Taxi Ticket App 20 Taxi operating companies 21 Magnetic Taxi Ticket DB 30 Smartphone app server 40 users 41 Smartphone 42 QR codes 50 Taxi 51 meters 52 Rear seat tablet 53 Cameras 54 Front seat tablet 60 Taxi ticket management device 61 Taxi Ticket Management Department 62 Taxi Ticket Payment Department 63 Taxi Ticket DB 111 Membership number input field 112 Register button 113 Registration Information Section 114 Issuance Conditions Section 115 Issue button 117, 119 Electronic Taxi Ticket Information 118, 120 Share button 541 Fare column 542 Description Display Field 543 Taxi ticket selection button 544 QR code button 631 Ticket Inspection Information 632 Ticket Management Information 633 Electronic Ticket Management Information 634 Ticket Transaction Information
Claims
1. A means for acquiring identification information and usage conditions specified for already issued taxi tickets (magnetic cards, IC cards, or paper cards) that enable taxi use with deferred payment of the fare, A storage means for storing the identification information and usage conditions of the acquired taxi ticket, An electronic taxi ticket issuing means that issues an electronic taxi ticket linked to the stored taxi ticket, based on an issuance request from the holder of the stored taxi ticket, within the scope of the usage conditions of the taxi ticket, An electronic taxi ticket providing means for providing the issued electronic taxi ticket, A taxi ticket management device characterized by being equipped with the following.
2. A payment request receiving means that receives payment information containing the identification information and fare of an electronic taxi ticket transmitted from the equipment installed in the taxi, along with a payment request. A payment method that performs payment by saving the received payment information in the ticket transaction information, The taxi ticket management device according to claim 1, characterized by having the following features.
3. The aforementioned storage means stores the identification information, number of uses, and total amount of the taxi ticket or electronic taxi ticket. Upon receiving the aforementioned payment request, one is added to the number of times the received identification information has been used, and the fare is added to the total amount used. The taxi ticket management device according to feature 2.
4. The aforementioned electronic taxi ticket issuing means issues electronic taxi tickets by assigning a number to the identification information of the electronic taxi ticket using the same identification code system as the identification information of the taxi ticket. The taxi ticket management device according to feature 1.
5. The identification information for the aforementioned taxi ticket and electronic taxi ticket is defined by a predetermined number of digits, where a predetermined digit is a distinguishing number that differentiates the taxi ticket from the electronic taxi ticket. The taxi ticket management device according to feature 4.
6. The storage means further stores the identification information and usage conditions of the issued electronic taxi ticket. The taxi ticket management device according to feature 4.
7. The storage means stores the identification information of the taxi ticket or electronic taxi ticket, and the usage conditions, including the expiration date, maximum amount, maximum number of uses, and maximum total amount. The taxi ticket management device according to feature 6.
8. The acquisition means acquires the identification information and usage conditions of the taxi ticket from the issuer of the taxi ticket or the mobile device of the holder of the issued taxi ticket. The taxi ticket management device according to feature 1.
9. The electronic taxi ticket providing means provides a URL for displaying the identification information of the electronic taxi ticket issued by the electronic taxi ticket issuing means. The taxi ticket management device according to feature 1.
10. A function to acquire identification information and usage conditions specified for already issued magnetic card, IC card, or paper card taxi tickets, enabling taxi use with deferred payment of the fare, A memory function that stores the usage conditions and identification information of the acquired taxi ticket in a memory means, An electronic taxi ticket issuance function that issues an electronic taxi ticket linked to the stored taxi ticket, based on an issuance request from the holder of the stored taxi ticket, within the scope of the usage conditions of the stored taxi ticket. The electronic taxi ticket provision function provides the electronic taxi tickets that have been issued, A taxi ticket management program characterized by enabling a computer to implement this functionality.
Citation Information
Patent Citations
Method for processing taxi ticket
JP2003296767A
Settlement card, settlement permission deciding device and its method
JP2004078661A
Ticket issuing device, server, ticket management system, ticket issuing method, and program
JP2020003927A
Electronic boarding ticket management server and management method
JP2020077123A
Taxi ticket operation system
JP2020112904A
