JP6663068B1 - Electronic taxi ticket issuing device - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide an electronic taxi ticket issuing device capable of improving convenience by allowing even a delegate participant to use an electronic taxi ticket when a specific user cannot attend an event. SOLUTION: An electronic taxi ticket issuing device (server 40) can access an issuer terminal 10 and a user terminal 20 via a network, and receives event information including an event ID from the issuer terminal 10. .. The server 40 receives from the user terminal 20 the user ID and the event ID included in the identification code read by the user terminal 20 and the individual information that distinguishes it from other identification codes, and the received user ID and event. The ID and the individual information are stored in association with each other, and it is determined whether the received event ID and individual information match the event ID and individual information stored in association with the storage unit 420, and it is determined that they match. At this time, the electronic ticket information that enables the acquisition of the electronic taxi ticket is transmitted to the user terminal 20. [Selection diagram] FIG.

Description

  The present disclosure relates to an electronic taxi ticket issuing device, and more particularly, to an electronic taxi ticket issuing device that issues an electronic taxi ticket to a user participating in an event.

  Conventionally, paper taxi tickets issued by taxi ticket issuing companies have been distributed. A taxi ticket user hands a taxi ticket to a taxi driver when riding a taxi. The taxi company collects a large number of taxi tickets after use, and bills taxi tickets to those who distribute the taxi tickets. Management of such paper taxi tickets is complicated.

  On the other hand, Japanese Patent No. 6387545 discloses an electronic taxi ticket issuance management system (Patent Document 1). This electronic taxi ticket issuance management system includes an issuer who issues a taxi ticket, a contractor who has signed a contract with the issuer for use of a taxi ticket, and a taxi ticket using a taxi ticket provided by the contractor. Used by taxis and taxi operators operating taxis. For example, in a predetermined event, the contractor transmits an invitation to the event to the invitees of the event, and requests a reply of participation / non-participation in the event. The contractor can issue a taxi ticket only to the invitee (user) who has answered that he / she participates in the event. The user presses a “ticket issuance” button displayed on the portable terminal, issues a taxi ticket in which a predetermined event or the like is designated, and then uses a taxi. Thus, the invitee (user) participating in the event can use the electronic taxi ticket when moving to the event site.

Japanese Patent No. 6387545

  However, in the conventional electronic taxi ticket issuance management system, at the time of an event, a specific invitee invited to the event and the event are registered in association with each other in advance, and the specific invitee (user) is registered. Only electronic taxi tickets can be issued. Therefore, only a specific user can use the electronic taxi ticket. For example, when a specific user cannot participate in an event due to sudden illness or urgent business and a substitute participant participates in the event, the electronic taxi ticket cannot be used. Therefore, the conventional electronic taxi ticket issuance management system has a problem that it lacks convenience.

  Accordingly, an object of the present disclosure is to provide an electronic taxi ticket issuing device that is excellent in convenience and can be used by a substitute participant even when a specific user cannot participate in an event. And

In order to solve the above problem, the present disclosure has the following configuration. That is, the electronic taxi ticket issuing device according to the present disclosure includes an issuer terminal used by the electronic taxi ticket issuer, a user terminal used by the electronic taxi ticket user, and a taxi company terminal used by the taxi company. May be accessible via a network. The electronic taxi ticket issuing device may include an event information receiving unit that receives event information including the event ID from the issuer terminal. In the electronic taxi ticket issuing device, the event ID and the identification code including the individual information for distinguishing from the other identification code are read by the user terminal, and the event ID and the individual information included in the read identification code and the user terminal are read. A read information receiving unit that receives the user ID from the user terminal may be provided. The electronic taxi ticket issuing device may include a storage unit that stores the user ID, event ID, and individual information received by the read information receiving unit in association with each other. The electronic taxi ticket issuing device includes an individual information determining unit that determines whether the event ID and the individual information received by the read information receiving unit match the event ID and the individual information stored in association with the storage unit. May be provided. Electronic taxi ticket issuing device, when individual information determination unit determines that mismatch may comprise an electronic ticket information transmitting unit for transmitting electronic ticket information enabling acquisition of an electronic taxi ticket to the user terminal.

  In addition, the electronic taxi ticket issuing device preferably determines whether the user ID and the event ID received by the read information receiving unit match the user ID and the event ID stored in association with the storage unit. A combination determination unit for determining may be provided. The electronic ticket information transmitting unit may transmit the electronic ticket information to the user terminal when the combination determining unit determines that there is no match.

  Further, the electronic taxi ticket issuing device may preferably include a predetermined period during which the event information can use the electronic taxi ticket. The electronic taxi ticket issuing device may further include a date determining unit that determines whether a date when the identification code is read by the user terminal is included in the predetermined period.

  In the electronic taxi ticket issuing device, preferably, the special event information may include an expiration date of the electronic taxi ticket. The electronic taxi ticket issuing device may further include a confirmation request receiving unit that receives a confirmation request for an expiration date from the user terminal. The electronic taxi ticket issuing device may include an expiration date determining unit that determines whether the electronic taxi ticket is within the expiration date. The electronic taxi ticket issuing device may include an expiration date transmitting unit that causes the user terminal to invalidate the electronic taxi ticket when the expiration date determining unit determines that the taxi ticket is not within the expiration date.

  The electronic taxi ticket issuing device preferably further reads the identification code including the taxi company ID and the taxi fare by the user terminal, and receives the read taxi company ID and taxi fare from the user terminal. A taxi fare receiving unit may be provided.

In addition, the electronic taxi ticket issuance method is a method in which an issuer terminal used by an electronic taxi ticket issuer, a user terminal used by an electronic taxi ticket user, and a taxi company terminal used by a taxi company via a network. May be accessible. The electronic taxi ticket issuing method may include a step of receiving event information including the event ID from the issuer terminal. According to the electronic taxi ticket issuing method, an event ID and an identification code including individual information to be distinguished from other identification codes are read by a user terminal, and the event ID and the individual information included in the read identification code and the user terminal are read. The method may include a step of receiving the user ID from the user terminal. The electronic taxi ticket issuing method may include a step of storing the received user ID, event ID, and individual information in association with each other. The electronic taxi ticket issuing method may include a step of determining whether the received event ID and the individual information match the event ID and the individual information stored in association with each other. Electronic taxi ticket issuing method, when the special event ID and the individual information is determined to not match, may comprise the step of transmitting electronic ticket information enabling acquisition of an electronic taxi ticket to the user terminal.

  Further, the electronic taxi ticket issuing program may be used to cause a computer to execute the above-described steps.

  According to the electronic taxi ticket issuing device according to the present disclosure, a proxy participant can use an electronic taxi ticket when a specific user cannot participate in an event, and the convenience can be improved.

FIG. 1 is a functional block diagram showing the configuration of the electronic taxi ticket issuing system according to the present embodiment. FIG. 2 is a functional block diagram showing the configuration of the issuer terminal shown in FIG. FIG. 3 is a functional block diagram showing the configuration of the user terminal shown in FIG. FIG. 4 is a functional block diagram showing the configuration of the taxi company terminal shown in FIG. FIG. 5 is a functional block diagram showing the configuration of the server shown in FIG. FIG. 6 is a diagram showing an example of a database of issuer information, user information, and taxi company information in the server shown in FIG. FIG. 7 is a diagram showing an example of a database of event information, electronic ticket information, and billing information in the server shown in FIG. FIG. 8 is a flowchart showing an operation of registering issuer information and the like in the server shown in FIG. FIG. 9 is a flowchart showing the operation of issuing an electronic taxi ticket between the user terminal and the server shown in FIG. FIG. 10 is a flowchart showing the operation of checking the expiration date of the electronic taxi ticket between the user terminal and the server shown in FIG. FIG. 11 is a flowchart showing the operation of using the electronic taxi ticket between the user terminal and the server shown in FIG. FIG. 12 is a flowchart showing an operation of charging a taxi fare between the issuer terminal, the taxi company terminal, and the server shown in FIG. FIG. 13 is a diagram showing an initial screen for issuing an electronic taxi ticket displayed on the display unit of the user terminal. FIG. 14 is a diagram showing a screen for reading the identification code displayed on the user terminal. FIG. 15 is a diagram illustrating an electronic taxi ticket issuance screen displayed on the user terminal. FIG. 16 is a diagram showing an initial screen when an electronic taxi ticket displayed on the user terminal is issued. FIG. 17 is a diagram showing an initial screen for using the electronic taxi ticket displayed on the user terminal. FIG. 18 is a diagram showing an electronic taxi ticket selection screen displayed on the user terminal. FIG. 19 is a diagram showing a screen when using the electronic taxi ticket displayed on the user terminal. FIG. 20 is a diagram showing a screen for reading a taxi fare and the like displayed on the user terminal. FIG. 21 is a diagram showing a taxi payment screen displayed on the user terminal. FIG. 22 is a diagram showing a used screen of the electronic taxi ticket displayed on the user terminal.

  Hereinafter, an electronic taxi ticket issuing system 1 according to an embodiment of the present disclosure will be specifically described with reference to the drawings. As shown in FIG. 1, the electronic taxi ticket issuing system 1 includes an issuer terminal 10, a user terminal 20, a taxi company terminal 30, and a server 40 as an electronic taxi ticket issuing device.

  The issuer terminal 10 is a terminal such as a PC operated by the issuer of the electronic taxi ticket, and can access the server 40 via the network 100. The issuer is, for example, an event invitation (organizer) or the like. The issuer issues an electronic taxi ticket to invitees (users) of the event to be sponsored and pays the taxi fare when the user uses the taxi to the taxi company on behalf of the user.

  The user terminal 20 is a mobile communication terminal such as a mobile phone, a smartphone, and a tablet terminal. In the present embodiment, an example in which the user terminal 20 is a smartphone having an Internet connection and a camera function will be described. The user terminal 20 is operated by the user of the electronic taxi ticket, and is used to use the electronic taxi ticket. The user terminal 20 can access the server 40 via the network 100. The user is, for example, an invitee of the event or a proxy participant who participates in the event on behalf of the invitee.

  The taxi company terminal 30 is a terminal such as a PC operated by the taxi company, and can access the server 40 via the network 100. The taxi company charges a taxi fare to the issuer according to the use of the electronic taxi ticket by the user.

  The server 40 processes various information received from the issuer terminal 10, the user terminal 20, and the taxi company terminal 30. Further, the server 40 processes various kinds of information transmitted to the issuer terminal 10, the user terminal 20, and the taxi company terminal 30. Specifically, an electronic taxi ticket issuing program for causing the server 40 to execute each step described below is installed.

  As shown in FIG. 2, the issuer terminal 10 includes an input unit 110, an issuer information transmitting unit 120 that transmits issuer information input by the input unit 110 to the server 40, and special event information input by the input unit 110. And an event information transmitting unit 130 that transmits the event information to the server 40. Details of the issuer information and the event information will be described later. The input unit 110 is, for example, a keyboard. Note that the issuer terminal 10 includes a display unit such as a display, a CPU, a main storage device, an auxiliary storage device, and the like, similarly to a known PC terminal.

  As shown in FIG. 3, the user terminal 20 includes an input unit 210, a user information transmitting unit 220 that transmits the user information input by the input unit 210 to the server 40, and an identification code reading unit that reads an identification code. A read information transmitting unit that transmits read information read by the identification code reading unit to the server; Details of the user information will be described later. The identification code is, for example, a two-dimensional code, a numeric code, or a character code. When the identification code is a two-dimensional code, the identification code reading unit 230 has a camera function for reading the two-dimensional code. When the identification code is a numeric code or a character code, the identification code reading unit 230 is an input unit 210 for inputting a numeric code or a character code, for example, a touch panel that also serves as a display unit. The code is read into the user terminal 20. As described above, the identification code reading unit 230 is not particularly limited as long as various identification codes can be read into the user terminal 20. In the present embodiment, the identification code will be described as a two-dimensional code, and the identification code reading unit will be described as a camera function. As will be described in detail later, the two-dimensional code includes a serial number (serial number) as individual information for distinguishing the two-dimensional code from other two-dimensional codes.

  The user terminal 20 further includes an electronic ticket information storage unit 250 that stores the electronic ticket information transmitted from the server 40, and a taxi fare reading unit that reads the taxi taxi meter identification and taxi driver identification code installed in the taxi. 260 is provided. The user uses the user terminal 20 to obtain an electronic taxi ticket based on the electronic ticket information transmitted from the server 40. Then, take a taxi and use the electronic taxi ticket. The user terminal 20 includes a touch panel, a CPU, a main storage device, an auxiliary storage device, and the like, similarly to a known smartphone.

  As shown in FIG. 4, the taxi company terminal 30 includes an input unit 310, a taxi company information transmission unit 320 that transmits the taxi company information input by the input unit 310 to the server 40, and taxi fee billing information to the server 40. And a billing information transmitting unit 330 for transmitting. The details of the taxi company information will be described later. The input unit 110 is, for example, a keyboard. The taxi company terminal 30 includes a display unit such as a display, a CPU, a main storage device, an auxiliary storage device, and the like, similarly to a known PC terminal.

  As shown in FIG. 5, the server 40 includes a receiving unit 410 that receives various information from the issuer terminal 10, the user terminal 20, or the taxi company terminal 30, a storage unit 420 that stores various information, and various determinations. And a transmitting unit 440 that transmits various types of information to the issuer terminal 10, the user terminal 20, or the taxi company terminal 30.

  The receiving unit 410 includes an issuer information receiving unit 411 that receives issuer information of a ticket issuer from the issuer terminal 10, and a user information receiving unit 412 that receives user information of a ticket user from the user terminal 20. A taxi company information receiving unit 413 for receiving taxi company information from the taxi company terminal 30; a special event information receiving unit 414 for receiving special event information from the issuer terminal 10; A read information receiving unit 415 received from the terminal 20, a confirmation request receiving unit 416 receiving a request for confirming the expiration date of the electronic taxi ticket from the user terminal 20, a taxi fee information when the user uses the taxi, A taxi fare receiving unit 417 for receiving taxi driver information.

  The storage section 420 stores an issuer information storage section 421 for storing issuer information, a user information storage section 422 for storing user information, a taxi company information storage section 423 for storing taxi company information, and special event information. An event information storage unit 424 for storing information and an electronic ticket information storage unit 425 for storing information on electronic taxi tickets are provided.

  The determination unit 430 includes an individual information determination unit 431 that determines whether a two-dimensional code including the same serial number (individual information) has been read in the past in the same event. A combination determination unit 432 that determines whether a two-dimensional code used in the same event has been read, an expiration date determination unit 433 that determines whether the electronic taxi ticket is within the expiration date, A usage record determination unit 434 that determines whether the electronic taxi ticket acquired by the terminal 20 has been used.

  The transmitting unit 440 uses the electronic ticket information transmitting unit 441 that transmits the electronic ticket information generated by the server 40 to the user terminal 20 and uses the fact that the electronic taxi ticket is not within the validity period by the determination of the validity period determining unit 433. An expiration date transmitting unit 442 for transmitting to the taxi terminal 20 and a billing information transmitting unit 443 for transmitting taxi billing information to the taxi company terminal 30 and the issuer terminal 10.

  Next, examples of various databases stored in the server 40 will be described with reference to FIGS. 6 and 7.

  As described above, the issuer information is received from the issuer terminal 10 at the time of the first account registration, and is stored in the issuer information storage unit 421. As shown in FIG. 6, the issuer information database includes, as shown in FIG. 6, an issuer ID, a password, an issuer name such as the name of a company that organizes the event, and, in the case where the issuer is an organization, a person in charge, a contact, an account, Issuer information such as creation date is stored for each issuer. Note that the account creation date is the date when the publisher information transmitted from the publisher terminal 10 is stored in the publisher information storage unit 421 of the server 40, as described above.

  The user information is received from the user terminal 20 at the time of the first account registration, and is stored in the user information storage unit 422. As shown in FIG. 6, the user information database stores user information such as a ticket user ID, a password, a name, a contact address, or an account creation date for each ticket user. Note that the account creation date is the date when the user information transmitted from the user terminal 20 is stored in the user information storage unit 422 of the server 40, as described above.

  The taxi company information is received from the taxi company terminal 30 at the time of the first account registration, and is stored in the taxi company information storage unit 423. As shown in FIG. 6, the taxi company information database stores taxi company information such as a taxi company ID, a password, a company name, a person in charge, contact information, a driver ID of an associated taxi driver, an account creation date, and a billing closing date. Remember each taxi company. Note that the account creation date is the date when the taxi company information transmitted from the taxi company terminal 30 is stored in the taxi company information storage unit 423 of the server 40, as described above.

  The event information is received from the issuer terminal 20 and stored in the event information storage unit 424 as shown in FIG. The special event information database stores special event information such as special event ID, special event name, date and time of issue, issuer ID, expiration date of electronic taxi ticket, maximum amount of electronic taxi ticket, and number of participants in the special event set by the issuer. I do. A two-dimensional code is generated according to the number of participants in the event. For example, when the number of participants is 30, 30 different two-dimensional codes including the same event ID and different serial numbers are generated.

  The electronic ticket information is generated by the server 40 after receiving the read information read by the user terminal 20 from the user terminal 20 and stored in the electronic ticket information storage unit 426. As shown in FIG. 7, the electronic ticket information database includes a ticket ID, an event ID, a ticket user ID, a serial number, a ticket acquisition date, a validity / invalidity flag of an electronic taxi ticket expiration date, a ticket usage date, a usage amount, The used taxi company ID, driver ID, and the like are stored. If an electronic taxi ticket has been issued and has expired, an invalid flag is set on the electronic taxi ticket.

  The billing information is generated by the server 40 for each billing request received from the taxi company terminal 30. As shown in FIG. 7, the billing information database stores a billing number, a biller (taxi company ID), a payer (issuer ID), and a total billed amount for each taxi company. Based on this bill, the taxi company charges the issuer for the taxi fare.

  The databases shown in FIGS. 6 and 7 are merely examples, and which information is stored in which database may be changed as appropriate.

(Operation when registering various information such as issuer)
The operation of registering account information of the issuer, user, and taxi company of an electronic taxi ticket and event information in the server 40 will be described with reference to FIG.

  As shown in FIG. 8, when publisher information is input from the input unit 110 and, for example, a “send button” displayed on the display unit of the publisher terminal 10 is pressed, the publisher information transmitting unit The issuer information is transmitted from 120 to the server 40 (S1001). Upon receiving the issuer information by the issuer information receiving unit 411, the server 40 registers the issuer information in the issuer information storage unit 421 (S1002). The issuer information input from the input unit 110 includes, for example, an issuer ID, a password, a company name of an issuer such as an event invitee (organizer), a person in charge, a contact address, and the like. The issuer information storage unit 421 also registers the date on which the issuer information was registered (account creation date). Since this operation is a so-called issuer account registration, it is processed only at the first account registration unless the account information is changed.

  When user information is input from the input unit 210 and, for example, a “send button” displayed on the display unit of the user terminal 20 is pressed, the user terminal 20 sends the user information from the user information transmitting unit 220 to the server 40. The information is transmitted (S1003). When the user information is received by the user information receiving unit 412, the server 40 registers the user information in the user information storage unit 422 (S1004). The user information input from the input unit 210 is, for example, a user ID, a password, a name, a contact, and the like. In addition, the user information storage unit 422 also registers the date when the user information was registered (account creation date). Since this operation is a so-called user account registration, it is processed only at the first account registration unless the account information is changed. Note that the user has installed an application for obtaining an electronic taxi ticket on the user terminal 20 in advance.

  The taxi company terminal 30 receives taxi company information from the input unit 310 and, for example, when a “send button” displayed on the display unit of the taxi company terminal 30 is pressed, a taxi is sent from the taxi company information transmission unit 320 to the server 40. The company information is transmitted (S1005). When the taxi company information is received by the taxi company information receiving unit 413, the server 40 registers the taxi company information in the taxi company information storage unit 423 (S1006). The taxi company information input from the input unit 310 is, for example, a taxi company ID, a password, a company name, a person in charge, a contact address, a driver ID of a taxi driver belonging to the taxi company, a taxi billing closing date, and the like. is there. The taxi company information storage unit 423 also stores the date when the taxi company information was registered (account creation date). Since this operation is a so-called taxi company account registration, it is processed only at the first account registration unless the account information is changed. However, when there is a change in the personnel of the taxi driver to which the taxi driver belongs, such as when a new taxi driver enters the company or a taxi driver who is currently working retires, based on the taxi driver change information input from the taxi company terminal 30, A process of changing the driver ID in the taxi company information storage unit 423 is required.

  When the event information is input from the input unit 110 and, for example, a “send button” displayed on the display unit of the issuer terminal 10 is pressed, the event information transmission unit 130 sends the event information to the server 40. Is transmitted (S1007). When the special event information is received by the special event information receiving unit 414, the server 40 registers the special event information in the special event information storage unit 424 (S1008). The event information includes, for example, the event ID, the event name, the date and time of the event, the issuer ID, the expiration date for using the electronic taxi ticket, the upper limit for the use of the electronic taxi ticket, and the number of participants in the event. This operation is processed for each event in various events held by the issuer. In addition, a plurality of the above-described two-dimensional codes are issued according to the number of participants in the event, and individual information (serial number) is given to each two-dimensional code. The event includes various events, such as various events, meetings, meetings, and gatherings of circles.

(Operation when issuing an electronic taxi ticket)
The flow of acquiring an electronic taxi ticket at the user terminal 20 will be described with reference to the flowchart shown in FIG. 9 and the screen transition diagrams of the display unit 21 of the user terminal 20 shown in FIGS. The invitee (user) invited to the event receives the paper on which the two-dimensional code 21a is displayed at the event site. Alternatively, the invitee receives the paper on which the two-dimensional code 21a is displayed by mail to the invitee's home or the like. Further, the two-dimensional code 21a may be received by e-mail at the user terminal 20 of the invitee. As long as the invitee can receive the identification code, the sending method is not limited. The two-dimensional code (identification code) 21a includes an event ID and a serial number (individual information) for distinguishing the two-dimensional code 21a from other two-dimensional codes. As shown in FIG. 13, the user activates an application for obtaining an electronic taxi ticket, and selects a “code reading” button 21b from the initial screen. As shown in FIG. 14, the two-dimensional code 21a is read by the identification code reading unit 230 of the user terminal 20 held by the user (S1101). Then, the user terminal 20 transmits the user ID stored in the user terminal 20, the event ID and the serial number included in the two-dimensional code 21a from the read information transmitting unit 240 to the server 40 (S1102). At this time, when communication between the user terminal 20 and the server 40 cannot be performed due to, for example, out of service area, the read information transmitting unit 20 temporarily stores the read information including the event ID and the serial number in the user terminal 20, Transmission is periodically attempted until transmission to the server 40 becomes possible. If the transmission to the server 40 fails, the user terminal 20 displays “communication failure error” on the display unit 21 (S1103).

  In the server 40, the read information receiving unit 415 receives the user ID, the event ID, and the serial number from the user terminal 20 (S1104). The server 40 stores the user ID, the event ID, and the serial number in the electronic ticket information storage unit 425. Then, the server 40 determines whether the user who has read the two-dimensional code on the user terminal 20 has already registered an account (S1105). Specifically, it is determined whether or not a user ID that matches the user ID received together with the read information exists in the user information storage unit 422. When determining that the account has not been registered, the server 40 notifies the user terminal 20 that the account has not been registered. The user terminal 20 displays “account not registered” on the display unit 21 (S1106).

  When determining that the user has already registered the account, the server 40 determines whether the issuer has already registered the event information corresponding to the received event ID (S1107). Specifically, it is determined whether or not an event ID that matches the event ID received as the read information exists in the event information storage unit 424. When determining that the event information is not registered, the server 40 notifies the user terminal 20 that the event information is not registered. The user terminal 20 displays “event not registered” on the display unit 21 (S1108).

  Next, the server 40 determines whether the two-dimensional code 21a including the same serial number has been read in the past by the individual information determination unit 431. Specifically, the individual information determination unit 431 determines whether the event ID and the serial number of the combination that matches the combination of the event ID and the serial number included in the two-dimensional code 21a are present in the electronic ticket information storage unit 425 ( S1109). In other words, the individual information determination unit 431 stores the event ID and the individual information in which the event ID and the individual information received by the read information receiving unit 415 are stored in association with the storage unit 420 (the electronic ticket information storage unit 425). It is determined whether or not it matches (S1109). If the event ID and the serial number of the same combination are stored in the past, that is, if the two-dimensional code 21a including the same serial number and the event ID has already been used, the server 40 determines that the two-dimensional code 21a has already been used. Is notified to the user terminal 20. The user terminal 20 displays “two-dimensional code used error” on the display unit 21 (S1110). As a result, the same two-dimensional code 21a can be used only once. In other words, it is possible to prevent a plurality of users from reading the same two-dimensional code 21a, and prevent a plurality of users from each obtaining an electronic taxi ticket from the same two-dimensional code 21a.

  When the individual information determination unit 431 determines that the same two-dimensional code 21a has not been used in the past, the server 40 determines whether or not the same user has acquired an electronic taxi ticket in the same event in the past by the combination determination unit 432. judge. Specifically, it is determined whether or not the event ID and the user ID of the combination that matches the combination of the event ID and the user ID included in the two-dimensional code 21a are present in the electronic ticket information storage unit 425 (S1111). . In other words, the combination determination unit 432 determines the user ID and the event whose user ID and event ID received by the read information receiving unit 415 are stored in association with the storage unit 420 (the electronic ticket information storage unit 425). It is determined whether it matches the ID (S1111). When the combination determining unit 432 determines that there is a user ID and an event ID of the same combination in the past, the server 40 notifies the user terminal 20 that the user ID and the event ID of the same combination are present. The user terminal 20 displays “Ticket Acquired Error” on the display unit 21 (S1112). Thus, the same user can use only one electronic taxi ticket. That is, it is possible to prevent the same user from acquiring a plurality of electronic taxi tickets from the plurality of two-dimensional codes 21a.

  When the combination determination unit 432 determines that there is no user ID and event ID of the same combination, the server 40 generates electronic ticket information and transmits electronic ticket information to the user terminal 20 that has read the two-dimensional code 21a. The electronic ticket information is transmitted from the unit 441 (S1113).

  The electronic ticket information transmitted here includes the ticket ID, event ID, and user ID read from the electronic ticket information storage unit 425, the expiration date of the electronic taxi ticket read from the event information storage unit 424, and the electronic ticket information. Includes the maximum amount of money that can be used with taxi tickets. The electronic ticket information enables acquisition of an electronic taxi ticket.

  In the present embodiment, the determination by the individual information determination unit 431 and then the determination by the combination determination unit 432 are performed. However, the present invention is not limited to this determination procedure. The individual information determination unit 431 may make the determination. Either the individual information determination unit 431 or the combination determination unit 432 may be provided depending on the event type, the number of participants, and the like.

  The user terminal 20 that has received the electronic ticket information stores the electronic ticket information in the electronic ticket information storage unit 250 (S1114). At the same time, the user terminal 20 displays a “ticket acquisition” button 21c on the display unit 21 based on the electronic ticket information, as shown in FIG. When the reading of the two-dimensional code 21a or the like succeeds, the screen shown in FIG. The user can acquire an electronic taxi ticket by pressing the “acquire ticket” button 21c (S1115). The user terminal 20 notifies the server 40 that the electronic taxi ticket has been acquired. The server 40 adds and updates the ticket acquisition date in the electronic ticket information storage unit 425 (S1116). When the acquisition of the electronic taxi ticket is completed, the user terminal 20 displays the toast message 21d of "Ticket has been issued" in the lower part of the display unit 21 and the "use ticket" as shown in the screen of FIG. The number of available tickets ("1" in FIG. 14) is displayed at the upper left of the "" button 21e. If a plurality of electronic taxi tickets have been acquired, the number of tickets according to the number is displayed.

  As a result, even when the invitee invited to the event cannot participate in the event due to sudden illness or urgent business, the substitute participant (user) reads the two-dimensional code 21a into its own user terminal 20. By doing so, you can use electronic taxi tickets. Therefore, the electronic taxi ticket issuing system 1 can improve user convenience. Further, by providing the individual information determination unit 431, it is possible to prevent the injustice that the same two-dimensional code 21a is read many times and a plurality of electronic taxi tickets are obtained from the same two-dimensional code 21a. Also, by providing the combination determination unit 432, for example, when a plurality of sheets displaying the two-dimensional code are distributed in the same event, an unauthorized user may use a plurality of electronic taxi tickets by the same user. Can be prevented.

  In the present embodiment, the user information is stored in the user information storage unit 220 of the server 40 in advance, that is, the account of the user is registered in advance. The user information may be transmitted from the user information transmitting unit 220 of the user terminal 20 to the server 40 at the same time that the user terminal 21 is read. Alternatively, when the server 40 determines that the user's account has not been registered, the server 40 may transmit the user information to the user terminal 20, that is, prompt the user to register the account.

(Operation to check ticket expiration date)
Next, an operation for confirming whether or not the electronic taxi ticket that can be issued by the user terminal 20 has expired will be described with reference to FIG.

  First, the user terminal 20 checks the presence or absence of electronic ticket information stored in the electronic ticket information storage unit 250. If the electronic ticket information is stored, the user terminal 20 validates the electronic taxi ticket based on the electronic ticket information. A confirmation request is sent to the server 40 for the time limit (S1201). At the time of the confirmation request, the user terminal 20 transmits the user ID stored in the user terminal 20 at the same time. When the server 40 receives the confirmation request for the expiration date by the confirmation request receiving unit 416, the server 40 confirms the user ID received at the same time (S1202), and the user of the user terminal 20 that has made the confirmation request is registered in the account. Is determined. Specifically, the server 40 determines whether the same user ID is stored in the user information storage unit 422 (S1203). When determining that there is no user ID, the server 40 notifies the user terminal 20 that there is no user ID. The user terminal 20 displays “account not registered” on the display unit 21 (S1204).

  When the server 40 determines that the user ID is present in the user information storage unit 422, that is, the server 40 determines that the account is registered, the expiration date determination unit 433 stores the expiration date of the electronic ticket information in the event information storage unit 424. It is determined whether the stored electronic taxi ticket has not expired (S1205). Specifically, the date and time set in the server 40 and the expiration date stored in the event information storage unit 424 are compared to determine whether the expiration date of the electronic taxi ticket has expired. When the expiration date determination unit 433 determines that the electronic taxi ticket is not within the expiration date, the server 40 notifies the user terminal 20 from the expiration date transmission unit 442 that the electronic taxi ticket is not within the expiration date. The user terminal 20 displays "expiration date expired" on the display unit 21 and invalidates the electronic taxi ticket so that it cannot be used (S1206). On the other hand, when the expiration date determining unit 433 determines that the electronic taxi ticket is within the expiration date, the server 40 notifies the user terminal 20 from the expiration date transmitting unit 442 that the electronic taxi ticket is within the expiration date. The user terminal 20 holds the electronic ticket information as it is (S1207).

  By performing this operation periodically, that is, by managing the expiration date of the electronic taxi ticket based on the date and time set in the server 40, the user can change the date and time set in the user terminal 20 to the actual date and time. It is possible to prevent fraud such as changing the date and time and extending the expiration date of the electronic taxi ticket.

(Operation when using an electronic taxi ticket)
Next, an operation at the time of using an electronic taxi ticket will be described with reference to a flowchart shown in FIG. 11 and screen transition diagrams shown in FIGS.

  When the user gets on the taxi and arrives at the destination, the user activates an electronic taxi ticket acquisition application and presses a “use ticket” button 21e displayed on the display unit 21, as shown in FIG. Then, as shown in FIG. 18, the electronic taxi ticket to be used this time is selected from the electronic taxi ticket list displayed on the user terminal 20 (S1301). When the electronic taxi ticket to be used this time is selected and the “ticket use” button 21f is pressed as shown in FIG. 19, the user terminal 20 uses whether or not the electronic taxi ticket has expired. The determination is made by comparing the expiration date of the electronic taxi ticket of the electronic ticket information stored in the user terminal 20 with the date and time set in the user terminal 20 (S1302). If the user terminal 20 determines that the electronic taxi ticket is not within the expiration date, the user terminal 20 displays an “expiration date error” on the display unit 21 so that the electronic taxi ticket cannot be used (S1303). As described above, when the electronic taxi ticket is used, the expiration date of the electronic taxi ticket may be confirmed at the user terminal 20, but as described above, even when the electronic taxi ticket is used, the expiration date is confirmed by the server 40. You may make a request.

  If the user terminal 20 determines that the electronic taxi ticket has expired, the user terminal 20 can read the taxi fare boarded from the taxi fare reading unit 260. As shown in FIG. 20, the taxi fare reading unit 260 is a camera function of the user terminal 20. The taxi fare reading section 260 recognizes the numerical value of the fare displayed on the taxi fare meter 21g mounted in the taxi, and reads the taxi fare as fare information. A two-dimensional code 21h (identification code) for identifying a taxi company is displayed near the taxi fare meter 21g. The taxi fare reading unit 260 reads the two-dimensional code 21h simultaneously with the reading of the taxi fare (S1304). The two-dimensional code 21h includes taxi driver information such as a taxi company ID and a taxi driver ID. If the taxi fare reading unit 260 fails to read, the user terminal 20 displays “read error” on the display unit (S1305). Thus, the user terminal 20 prompts the user to read the taxi fare and the two-dimensional code 21g again.

  When the taxi fare reading unit 260 succeeds in reading the taxi fare and the two-dimensional code 21h, the user terminal 20 determines that the taxi fare is within the upper limit of the electronic taxi ticket stored in the electronic ticket information storage unit 250 of the user terminal 20. Is determined (S1306). Specifically, the user terminal 20 determines whether the taxi fare is within the upper limit by comparing the taxi fare in the fare information with the upper limit amount stored in the electronic ticket information storage unit 250. If it is determined that the taxi fare is within the upper limit, the user terminal 20 displays a “pay with ticket” button 21i on the display unit 21, as shown in FIG. When the user presses the "pay with ticket" button 21i, the payment of the taxi fare is completed. On the other hand, if the taxi fare exceeds the upper limit, although not shown, the user terminal 20 pays the electronic taxi ticket up to the upper limit, and pays the cash or credit card for the fee exceeding the upper limit. A display prompting the user to pay the taxi fare by a payment method other than the electronic taxi ticket is displayed on the display unit 21 (S1307).

  When the payment of the taxi fare is completed in this way, the user terminal 20 transmits the taxi usage fee information and the taxi driver information including the taxi company ID and the driver ID to the server 40. When the server 40 receives the information from the user terminal 20 by the taxi fare receiving unit 417, the server 40 adds and updates the information to the electronic ticket information storage unit 425 (S1308). When the update of the electronic ticket information storage unit 425 is completed, the server 40 notifies the user terminal 20 of the completion of the update. Then, the user terminal 20 also updates the electronic ticket information in the electronic ticket information storage unit 250 (S1309). As shown in FIG. 22, the user terminal 20 displays that the electronic taxi ticket has been used on the electronic taxi ticket list screen, so that the user cannot use the same electronic taxi ticket. If the communication environment is poor outside the service area and the usage fee, taxi company ID, and driver ID cannot be transmitted to the server 40, or if the electronic ticket information of the server 40 cannot be updated for any reason, the user terminal 20 transmits the electronic ticket information. Records that the update has failed, and periodically attempts to transmit such information until the transmission is successful (S1310).

(Operation from billing to deposit)
Next, with reference to FIG. 12, an operation from when the taxi company charges the taxi fare to the issuer until the taxi is paid will be described.

  The person in charge of the taxi company logs in the billing management screen on the taxi company terminal 30. For example, when the person in charge presses a “bill issue” button displayed on the bill management screen, the taxi company terminal 30 transmits a bill issue request to the server 40 (S1401). This billing request is made periodically according to the closing date of each taxi company. For example, if the closing date of a certain taxi company is the end of the month, the invoicing request for the previous month is made on the day following the closing date (the first day of the month following the closing date). When the server 40 receives the billing request, the usage record determination unit 435 of the server 40 uses the ticket issuance date and the ticket usage date stored in the electronic ticket information storage unit 425 to issue the ticket but not use it. It is determined whether there is electronic ticket information (S1402). When the usage record determination unit 434 determines that there is no such electronic ticket information, the server 40 transmits the billing information from the billing information transmitting unit 443 to the taxi company terminal 30. The taxi company terminal 30 receiving the billing information displays the billing information on the display unit according to the billing closing date (S1403). The person in charge confirms the billing information and, if there is no problem, presses the “confirm billing” button displayed on the billing management screen to confirm the billing (S1404). The billing information includes a billing number for identifying the billing information, a biller (taxi company ID), a payer (issuer ID), and a ticket usage date included in the electronic ticket information and a total billing amount calculated from the usage fee. Information is included. The billing information is stored in the billing information storage unit 426.

  On the other hand, when the usage record determination unit 435 determines that there is electronic ticket information that has been issued and has no usage record, the expiration date determination unit 434 sets the expiration date included in the event information stored in the event information storage unit 424 to the expiration date. Then, it is determined whether the issued electronic taxi ticket has expired (S1405). If the expiration date determination unit 434 determines that the expiration date has not expired, the server 40 notifies the taxi company terminal 30 that there is an electronic taxi ticket that has been issued and has not been used. Upon receiving this notification, the taxi company terminal 30 displays a "warning" on the display unit (S1406). This warns that the user may have issued an electronic taxi ticket, and that the electronic taxi ticket use record may not have been transmitted due to obstacles such as communication conditions, even though the electronic taxi ticket was used. To do that.

  If the expiration date determination unit 434 determines that the expiration date has expired, the server 40 determines that the electronic taxi ticket has been issued by the user but has not been used, and the billing information transmission unit 442. Send billing information from. The taxi company terminal 30 that has received the billing information displays the billing information on the display unit. The taxi company terminal 30 determines that there is no problem in the billing information by the person in charge, and presses the “confirm billing” button displayed on the billing management screen to finalize the billing information (S1404).

  When the billing information is determined in this manner, the taxi company terminal 30 transmits the determined billing information from the billing information transmitting unit 330 to the server 40. When the server 40 receives the billing information from the taxi company terminal 30, the billing information transmitting unit 443 transmits the billing information to the issuer terminal 10 (S1407).

  The issuer terminal 10 receives the billing information from the billing information transmitting unit 443 (S1408). After that, the issuer terminal 10 displays the billing information on the display unit (S1409). The person in charge of the issuer checks this billing information. Thereafter, the person in charge pays the amount of the invoice to the taxi company by, for example, the payment method displayed together with the invoice information (S1410). The person in charge of the taxi company checks the amount of the deposit (S1411).

  Note that the taxi company can grasp the monthly sales of each driver by checking the usage amount and the driver ID stored in the electronic ticket information.

(Modification)
In the above embodiment, the invitee of the event or the participant on behalf of the invitee reads the identification code using his / her own user terminal 20 and obtains one electronic taxi ticket. There are cases where two electronic taxi tickets are required: an electronic taxi ticket to be used on the return trip and an electronic taxi ticket to be used on the return trip from the event venue. In that case, the user can receive two identification codes of the same event. The user reads the first identification code and uses the first electronic taxi ticket on the outward route, and reads the second identification code and uses the second electronic taxi ticket on the return route. As a result, the user can use two electronic taxi tickets. Separate individual information (serial numbers) are assigned to the two identification codes. Therefore, it is possible to prevent unauthorized use in which two or more users repeatedly use one electronic taxi ticket.

  When the first identification code is read, the user ID and the event ID are stored in the storage unit 420 (electronic ticket information storage unit 425) in association with each other. Therefore, when the second identification code is read, the user cannot acquire the second electronic taxi ticket due to the determination (S1111) by the combination determination unit 432 according to the flowchart shown in FIG. Therefore, when two identification codes are read into the user terminal 20 in the same event, the determination (S1111) by the combination determination unit 432 may be omitted. Further, three or more identification codes may be read in accordance with the scene.

  Alternatively, two or more electronic taxi tickets may be issued by reading one identification code.

  Although the embodiments have been described above, the present disclosure is not limited to the embodiments described above, and various modifications can be made without departing from the gist of the embodiments.

1 electronic taxi ticket issuing system 10 issuer terminal 20 user terminal 30 taxi company terminal 40 server (electronic taxi ticket issuing device)
410 reception unit, 414 event information reception unit, 415 read information reception unit, 416 confirmation request reception unit, 417 taxi fee reception unit 420 storage unit 430 determination unit, 431 individual information determination unit, 432 combination determination unit, 433 expiration date determination unit 440 transmission unit, 441 electronic ticket information transmission unit

Claims (6)

An electronic taxi ticket issuing device accessible via a network from an issuer terminal used by an electronic taxi ticket issuer, a user terminal used by an electronic taxi ticket user, and a taxi company terminal used by a taxi company. And
An event information receiving unit that receives event information including an event ID from the issuer terminal;
An identification code including individual information to be distinguished from the event ID and other identification codes is read by the user terminal, and the event ID and individual information included in the read identification code, the user ID of the user terminal, Read information receiving unit for receiving from the user terminal,
A storage unit that stores the user ID, event ID, and individual information received by the read information receiving unit in association with each other;
An individual information determining unit that determines whether the event ID and the individual information received by the read information receiving unit match the event ID and the individual information stored in association with the storage unit,
The individual when the information determination unit determines that mismatch comprises an electronic ticket information transmitting unit for transmitting electronic ticket information enabling acquisition of an electronic taxi ticket to the user terminal, the electronic taxi ticket issuing device. The electronic taxi ticket issuing device according to claim 1, further comprising:
A combination determining unit that determines whether the user ID and the event ID received by the read information receiving unit match the user ID and the event ID stored in association with the storage unit,
The electronic taxi ticket issuing device, wherein the electronic ticket information transmitting unit transmits the electronic ticket information to the user terminal when the combination determining unit determines that there is no match. The electronic taxi ticket issuing device according to claim 1 or 2,
The event information includes an expiration date of the electronic taxi ticket,
The electronic taxi ticket issuing device further includes:
A confirmation request receiving unit that receives the expiration date confirmation request from the user terminal;
An expiration date determining unit that determines whether the electronic taxi ticket is within the expiration date,
An electronic taxi ticket issuing device, comprising: an expiration date transmitting unit that causes the user terminal to invalidate the electronic taxi ticket when the expiration date determining unit determines that the taxi ticket is not within the expiration date. The electronic taxi ticket issuing device according to any one of claims 1 to 3, further comprising:
An electronic taxi ticket issuance including a taxi fare receiving unit for reading an identification code including a taxi company ID and a taxi fare by the user terminal and receiving the read taxi company ID and taxi fare from the user terminal. apparatus. An electronic taxi ticket issuing method accessible via a network from an issuer terminal used by an electronic taxi ticket issuer, a user terminal used by an electronic taxi ticket user, and a taxi company terminal used by a taxi company. And
Receiving event information including an event ID from the issuer terminal;
An identification code including individual information to be distinguished from the event ID and other identification codes is read by the user terminal, and the event ID and individual information included in the read identification code, the user ID of the user terminal, Receiving from the user terminal;
Storing the received user ID, event ID, and individual information in association with each other;
Determining whether the received event ID and the individual information match the event ID and the individual information stored in association with each other;
When the special event ID and the individual information is determined to not match, comprising the steps of transmitting an electronic ticket information enabling acquisition of an electronic taxi ticket to the user terminal, the electronic taxi ticket issuing method.   An electronic taxi ticket issuing program for causing a computer to execute the steps according to claim 5.

Images