JP2020077123A - Electronic boarding ticket management server and management method - Google Patents

Abstract

To provide electronic boarding tickets that can be used in various ways.SOLUTION: A management server comprises: a ticket issuing unit for issuing an electronic boarding ticket, adding identification information, and creating a record when receiving an issuance request from a first communication terminal of a boarding ticket provider or a second communication terminal of a contractor; a record storage unit; a ticket management unit for storing the identification information of the provider, the identification information of the contractor, and the identification information of a transportation operator in the record; and an information providing unit for generating and transmitting browsing information from the record in response to a browsing request from the first communication terminal, the second communication terminal, or a third communication terminal. The ticket management unit stores the usage information in the record of the electronic boarding ticket with the matching identification information when receiving from the second communication terminal or the third communication terminal the identification information of the electronic boarding ticket used to pay a vehicle usage fee and vehicle usage information.SELECTED DRAWING: Figure 6

Description

  The present invention relates to an electronic boarding ticket management server and management method.

  Conventionally, boarding tickets have been used to board vehicles such as taxis and buses. A typical example of a boarding ticket is a taxi ticket used to pay a taxi fee. A taxi ticket is usually issued in a paper medium by a taxi company, a credit card company, etc., and is distributed to contractors who have signed a usage contract with companies, card users, and the like. When you give a taxi ticket to a crew member when using a taxi, the crew member writes the date and time of use, the section used, the amount used, the user name, etc. Thereafter, a taxi operator collects taxi tickets, sorts them by contractor, and uses them for billing the contractor.

  Paper taxi tickets require printing and delivery for each contractor. A blank taxi ticket is converted into a cash voucher by entering the amount of money, so proper inventory management is required after printing. Further, the usage fee and the like have to be written by hand at the time of payment, and collection and sorting are manual work, resulting in a heavy burden and cost. Furthermore, the contractor could not understand the usage status of the taxi ticket until it was billed. In order to improve the efficiency of such work, computerization of taxi tickets has been proposed (see, for example, Patent Documents 1 and 2).

JP, 2005-352563, A JP, 2005-135330, A

  However, in the systems of Patent Documents 1 and 2 described above, when a ticket is issued, an application for an expected date of use, a boarding section, etc. is accepted, and an electronic taxi ticket that can be used within the range of the application is issued, so a taxi ticket is suddenly required. It is not possible to deal with cases such as cases where the destination is undecided or the destination is undecided.

  Further, a taxi ticket in a paper medium is transferable. For example, a company as a contractor may assign a taxi ticket to an employee, and the employee may further transfer the taxi ticket to the customer. However, in the systems of Patent Documents 1 and 2 described above, the electronic taxi ticket is downloaded to a portable terminal of a taxi user or a storage medium such as an IC card and used as a substitute for the ticket, so that it corresponds to the usage form to be transferred. Can not do it.

  An object of the present invention is to provide an electronic boarding ticket that can be used in various usage forms.

  According to one aspect of the present invention, a first communication terminal of a passenger of a boarding ticket, a second communication terminal of a contractor who concludes a usage contract with the provider and receives the boarding ticket, and the boarding ticket. A third communication terminal of a transportation company that provides a vehicle that can be boarded by using a management server connected via a network, the management server connecting the first communication terminal or the second communication terminal with the boarding ticket. When the issuance request is received, a ticket issuing unit that issues an electronic boarding ticket and adds identification information to create a record, a storage unit that stores a record of the electronic boarding ticket, and a record of the electronic boarding ticket, A ticket management unit that stores identification information of the provider who has signed a contract for using an electronic boarding ticket, identification information of the contractor, and identification information of the transportation operator that provides a vehicle that can use the electronic boarding ticket, In response to a browsing request from the first communication terminal, the second communication terminal, or the third communication terminal, browsing information of ticket contents is generated from a record of the electronic boarding ticket, and the first communication terminal and the second communication are generated. An information providing unit for transmitting to the terminal or the third communication terminal, wherein the ticket management unit provides identification information of the electronic boarding ticket used for payment of the usage fee of the vehicle and usage contents of the vehicle. A management server is provided that stores the usage information in a record of the electronic boarding ticket with which the identification information matches when receiving the usage information shown.

  According to another aspect of the present invention, there is provided an electronic boarding ticket management method executed by a management server, wherein the management server contracts with the first communication terminal of a boarding ticket provider. Connected via a network to a second communication terminal of a contractor who receives the boarding ticket and a third communication terminal of a transportation company that provides a vehicle that can be boarded using the boarding ticket. When receiving the request for issuing the boarding ticket from the first communication terminal or the second communication terminal, a step of issuing an electronic boarding ticket and adding identification information to create a record; and a record of the electronic boarding ticket in a storage unit Storing the electronic boarding ticket record, providing identification information of the provider who has signed a contract for using the electronic boarding ticket, identification information of the contractor, and a vehicle that can use the electronic boarding ticket. In response to a step of storing identification information of a transportation business operator and a browsing request from the first communication terminal, the second communication terminal or the third communication terminal, browsing information of ticket contents is obtained from the electronic boarding ticket record. Generated and transmitted to the first communication terminal, the second communication terminal or the third communication terminal, and used for payment of the usage fee of the vehicle from the second communication terminal or the third communication terminal When the identification information of the electronic boarding ticket and the usage information indicating the usage content of the vehicle are received, a step of storing the usage information in a record of the electronic boarding ticket having the matching identification information is provided. Provided.

  According to the present invention, it is possible to provide an electronic boarding ticket that can be used in various forms.

It is a figure which shows the structure of the boarding ticket system containing the management server of one Embodiment of this invention. It is a block diagram which shows the structure of a management server for every function. It is a flow chart which shows a processing procedure of a management server at the time of issuing an electronic taxi ticket. It is a figure which shows an example of a record. It is a figure which shows the example of an update of the record by transfer of an electronic taxi ticket. It is a flow chart which shows a processing procedure of a management server at the time of getting on. It is a figure which shows the example of a display of the electronic taxi ticket which can be used. It is a figure which shows the example of a display of the valid notice of an electronic taxi ticket. It is a flow chart which shows a processing procedure of a management server at the time of getting off. It is a figure which shows the example of a display of a usage history notification. It is a flow chart which shows a processing procedure of a management server at the time of boarding when transferring an electronic boarding ticket to a non-user of a boarding ticket system.

  Embodiments of an electronic boarding ticket management server and a management method according to the present invention will be described below with reference to the drawings. The configuration described below is an example (representative example) as one embodiment of the present invention, and the present invention is not limited to the configuration described below.

FIG. 1 shows the configuration of a boarding ticket system 100 including a management server 1 according to an embodiment of the present invention.
As shown in FIG. 1, in the boarding ticket system 100, the management server 1 is connected to the first communication terminal 5, the second communication terminal 6, and the third communication terminal 7 via the network N. Further, the management server 1 is connected to the vehicle allocation system 8 and the settlement system 9. 1 is a diagram showing an example of the configuration of the boarding ticket system 100, and the number of terminals, systems, etc. connected to the management server 1 is not limited to the example shown in FIG.

  The first communication terminal 5 is a communication terminal used by a boarding ticket provider. Examples of the provider include transportation companies such as taxi companies and bus companies, and credit card companies that provide boarding tickets for affiliated transportation companies. The second communication terminal 6 is a communication terminal used by a contractor who concludes a usage contract with the provider and receives a boarding ticket. The contractor is a person who is authorized to use the taxi ticket by the provider and is obliged to pay the usage fee. The contractor may be, for example, an individual, a corporation such as a corporation, an individual who owns a credit card, or a corporation. The third communication terminal 7 is a communication terminal used by a transportation company that provides vehicles that can be boarded using boarding tickets. The vehicle is, for example, a taxi or a bus. It may be a vehicle whose usage fee changes depending on the distance traveled, or a vehicle with a fixed fee such as a taxi with a fixed fare in advance and a bus with a fixed fare for a section.

  The first communication terminal 5, the second communication terminal 6, and the third communication terminal 7 are, for example, PCs (Personal Computers), tablets, mobile phones, etc. having a communication function, and may be configured similarly to the management server 1 described later. it can. It is preferable that the second communication terminal 6 and the third communication terminal 7 have a position detection function based on GPS (Global Positioning System) or the like.

  The vehicle allocation system 8 is a system for arranging vehicles provided by a transportation company, and is used by the transportation company. The settlement system 9 is a system that calculates a usage fee of a vehicle for which a boarding ticket is used for payment and bills the contractor. The checkout system 9 is used by the boarding ticket provider.

The management server 1 issues an electronic boarding ticket and manages a record of the electronic boarding ticket.
FIG. 2 is a block diagram showing the configuration of the management server 1 for each function.
As shown in FIG. 2, the management server 1 includes a control unit 11, a storage unit 12, a communication unit 13, an operation unit 14, and a display unit 15.

  The control unit 11 realizes various functions such as the ticket issuing unit 111, the ticket management unit 112, the information providing unit 113, the vehicle allocation management unit 114, and the ticket processing unit 115 by reading the program and data from the storage unit 12 and executing them. To do. The control unit 11 includes a processor such as a CPU (Central Processing Unit), a memory such as a RAM (Random Access Memory), and the like.

  Upon receiving the boarding ticket issuance request from the first communication terminal 5 or the second communication terminal 6, the ticket issuing unit 111 issues an electronic boarding ticket and adds identification information. The ticket issuing unit 111 creates a record of the electronic boarding ticket and stores it in the storage unit 12.

  The ticket management unit 112 records, in the electronic boarding ticket record, the identification information of the provider who has signed the contract for using the electronic boarding ticket, the identification information of the contractor, and the transportation company that provides a vehicle that can use the electronic boarding ticket. Save identification information. Further, the ticket management unit 112 receives, from the second communication terminal 6 or the third communication terminal 7, the identification information of the electronic boarding ticket used to pay the usage fee of the vehicle and the usage information indicating the usage content of the vehicle. Then, the received usage information is stored in the record of the electronic boarding ticket in which the received identification information matches.

  Upon receiving the browsing request from the first communication terminal 5, the second communication terminal 6, or the third communication terminal 7, the information providing unit 113 generates the browsing information of the ticket content from the electronic boarding ticket record and transmits the browsing request. It transmits to the 1st communication terminal 5, the 2nd communication terminal 6, or the 3rd communication terminal 7.

  When the vehicle allocation management unit 114 receives the vehicle allocation request and the identification information of the electronic boarding ticket to be used, the vehicle allocation management unit 114 acquires the identification information of the transportation operator from the record that matches the identification information and allocates the vehicle corresponding to the identification information of the transportation operator. A vehicle dispatch request is transmitted to the system 8.

  The ticket processing unit 115 sorts the electronic boarding ticket records by provider or contractor, generates billing information from the sorted records, and transmits the billing information to the settlement system 9.

  The storage unit 12 is a storage medium that stores a program readable by the control unit 11 and data necessary for executing the program. The storage unit 12 stores, for example, a record of an electronic boarding ticket. A non-volatile memory such as a hard disk or a ROM (Read Only Memory) can be used as the storage unit 12.

  The communication unit 13 communicates with external devices such as the first communication terminal 5, the second communication terminal 6, and the third communication terminal 7, which are connected via the network N. The communication unit 13 transmits or receives various kinds of information between the control unit 11 and an external device according to an instruction from the control unit 11.

  The operation unit 14 outputs an operation signal corresponding to the operation input of the operator to the control unit 11. The operation unit 14 is, for example, a keyboard, a mouse, or the like.

  The display unit 15 displays an operation screen or the like according to an instruction from the control unit 11. The display unit 15 is a display such as an LCD (Liquid Crystal Display).

  Hereinafter, the processing procedure of the management server 1 that electronically manages the boarding ticket will be described by taking the case where the boarding ticket is a taxi ticket as an example, but the same applies even when the boarding ticket is a boarding ticket for another vehicle such as a bus. The boarding ticket can be digitized and managed by the processing procedure. In the following processing procedure, the first communication terminal 5, the second communication terminal 6, and the third communication terminal 7 are installed with a dedicated application that cooperates with the management server 1, and the electronic boarding provided by the management server 1 by the application. Although a ticket service can be used, the electronic boarding ticket service is not limited to this, and may be a web service.

  The taxi ticket can be used, for example, when the provider is a taxi company, the contractor is a company, and the taxi passenger is an employee of a company to whom a taxi ticket is assigned by the company or a taxi ticket is transferred from the employee. For example, if you are a customer. In addition, when the provider is a credit card company and both the contractor and the passenger are individuals who own the credit card, the contractor is an individual but the passenger is a family whose taxi ticket is transferred from the individual. Etc. In the following example, the case where the provider is a taxi company and the contractor is a company will be described.

FIG. 3 shows a processing procedure when the management server 1 issues an electronic taxi ticket.
In FIG. 3, the second communication terminal 6a is a second communication terminal used by a company that is a contractor, and the second communication terminal 6b is a second communication terminal used by an employee of the company. In addition, taxi companies (providers and transportation companies) using the first communication terminal 5, companies (contractors) using the second communication terminal 6a, and employees (passengers) using the second communication terminal 6b Is previously provided with identification information such as an ID and authentication information such as a password. When communicating with the first communication terminal 5 and the second communication terminals 6a and 6b, the management server 1 authenticates the user of each terminal with the identification information and the authentication information.

  After the conclusion of the usage contract, the taxi company transmits a taxi ticket issuance request by the first communication terminal 5. If the taxi company permits the company to issue taxi tickets in advance, the company can send a taxi ticket issuance request using the second communication terminal 6a.

  As shown in FIG. 3, an issuance request is transmitted from the first communication terminal 5 (step S11) or an issuance request is transmitted from the second communication terminal 6a (step S12), and the management server 1 receives the issuance request. Then, the ticket issuing unit 111 issues an electronic taxi ticket (step S13). The ticket issuing unit 111 adds identification information such as a ticket ID to the electronic taxi ticket, creates a record of the electronic taxi ticket including the identification information, and saves the record in the storage unit 12.

  Next, the ticket management unit 112 provides a taxi company (provider) that has signed a taxi ticket usage contract, a company (contractor), and a taxi company that provides a taxi that can be boarded using the taxi ticket (transportation business). Each person's identification information (for example, ID, name, address, telephone number, etc.) is acquired from the first communication terminal 5 or the second communication terminal 6a and stored in the electronic taxi ticket record (step S14). For example, the ticket management unit 112 may display the input screen of the above information on the first communication terminal 5 or the second communication terminal 6a that has transmitted the issuance request, and acquire the information input on this input screen. If the electronic taxi ticket has additional conditions, such as an expiration date, the ticket management unit 112 can also acquire information about the additional conditions and store the information in a record.

FIG. 4 shows an example of a record.
As shown in FIG. 4, the record indicates a ticket ID given to the electronic taxi ticket, a provider of the electronic taxi ticket, a contractor who has a contract with the provider, and a taxi that can be boarded using the electronic taxi ticket. It includes each piece of identification information (for example, name, ID, etc.) of the transportation company to be provided. The record also includes identification information (for example, name, user ID, etc.) of the owner and the assignee of the electronic taxi ticket. The owner and the transferee will be described later. The record includes the identification information of the vehicle in which the electronic taxi ticket is used (for example, a taxi ID unique to all vehicles, the vehicle number used inside the taxi company, etc.), the identification information of the passenger (for example, a user ID, etc.) ), The location information of the boarding place and the getting-off place (for example, GPS coordinates, an address, etc.), the usage fee, and the date and time of use (for example, the date and time of getting on and off the vehicle).

  As shown in FIG. 4, the record can also include an expiration date and a use prohibition item. If a date is stored in the expiration date item, the electronic taxi ticket becomes invalid after the stored date. The electronic taxi ticket is also invalidated when the prohibition flag is stored in the prohibited use item.

  The provider and the contractor can view the records of all the electronic taxi tickets issued by the contract between them. In the management server 1, when the browsing request is transmitted from the first communication terminal 5 or the second communication terminal 6a (step S15 or S16), the information providing unit 113 causes the first communication terminal 5 or the second communication terminal 6a to perform authentication. A record of the electronic taxi ticket that matches the received identification information of the provider or the contractor is read from the storage unit 12. The information providing unit 113 generates browsing information from the read record and transmits the browsing information to the first communication terminal 5 or the second communication terminal 6a that transmitted the browsing request (step S17). The browsing information includes information indicating ticket contents, for example, a ticket ID that is identification information of an electronic taxi ticket, information about a provider, a contractor, a transportation company, and the like.

  The contractor can register the owner of the issued electronic taxi ticket in the management server 1. The owner has the right to use the electronic taxi ticket as a member of the contractor. For example, a company that is a contractor can assign an issued electronic taxi ticket to an employee by registering the employee as the owner. The contractor transmits the identification request such as the ticket ID of the electronic taxi ticket for registering the owner and the identification information of the owner to the management server 1 together with the owner registration request by the second communication terminal 6a (step S18). .. The ticket management unit 112 of the management server 1 saves the identification information (for example, the name of the owner, the user ID, the department name, etc.) of the registration-requested owner in the record of the electronic taxi ticket having the matching ticket ID (step). S19).

  The owner can view the record of the electronic taxi ticket owned by the owner, like the contractor. When the management server 1 receives the browsing request from the second communication terminal 6b whose owner has been authenticated in advance (step S20), the information providing unit 113 receives the browsing request from the second communication terminal 6b by the owner. The record of the electronic taxi ticket that matches the identification information is read from the storage unit 12. The information providing unit 113 generates browsing information such as a ticket ID, which is identification information of the electronic taxi ticket, from the read record, and transmits the browsing information to the owner's second communication terminal 6b (step S21).

  The owner has the right not only to use the electronic taxi ticket in his possession, but also to transfer it. The assignee to whom the electronic taxi ticket is assigned is a person who has authorized the contractor or owner to use the electronic taxi ticket in the same manner as the contractor. For example, the employee who is the owner can transfer it to another employee, a customer, or the like. The owner can register the transferee in the management server 1. When registering, the owner transmits identification information such as the ticket ID of the electronic taxi ticket for registering the transferee and the transferee identification information to the management server 1 together with the transferee registration request by the second communication terminal 6b. (Step S22). The ticket management unit 112 of the management server 1 identifies the transferee requested to be registered (for example, the transferee's name, user ID, and department) in the electronic taxi ticket record that matches the ticket ID received from the second communication terminal 6b. The name etc.) is stored (step S23).

FIG. 5 shows an example of saving a record of an electronic taxi ticket.
As shown in FIG. 5, when the provider ABC requests the contractor AAA to issue three electronic taxi tickets, three electronic taxi ticket records 91 are created. In the record 91, the ticket ID is stored as the identification information of the electronic taxi ticket, and the name of the provider ABC, the name of the contractor AAA, and the name of the taxi company ABC are the identification information of the provider, the contractor, and the transportation company, respectively. Is stored as. The record 91 has items of identification information of the owner and the transferee, but since the owner and the transferee are not registered at this point, the names of all the contractors are stored.

  Thereafter, when the contractor AAA allocates two electronic taxi tickets to the owner X and a registration request for the owner X is made, the record 91 is updated to the record 92. In the record 92, the names of the owners of two of the three electronic taxi tickets are updated from AAA to X. Since the transferee is not registered at this point, the name X of the owner is stored in all the items of the transferee.

  Further, when one electronic taxi ticket is transferred from the owner X to the transferee Y and a request for registration of the transferee Y is made, the record 92 is updated to the record 93. In the record 93, the name of the assignee of one of the two electronic taxi tickets owned by the owner X is updated from X to Y.

  In addition, the provider, the contractor, and the owner can prohibit the use of the electronic taxi ticket. In this case, the first communication terminal 5, the second communication terminal 6a, or the third communication terminal 7 selects an electronic taxi ticket whose use is prohibited from among the browsed electronic taxi tickets, and issues a use prohibition registration request to the management server 1 Send to. The ticket management unit 112 of the management server 1 stores a prohibition flag in the use prohibition item of the record of the selected electronic taxi ticket.

  Next, a processing procedure of the management server 1 when a contractor, an owner, or a transferee gets on a taxi will be described. Hereinafter, a case where the transferee gets on a taxi will be described as an example, but the same processing procedure applies to the contractor or the owner.

(Processing when boarding)
FIG. 6 shows a processing procedure of the management server 1 at the time of boarding. In FIG. 6, the second communication terminal 6c is a second communication terminal used by a taxi passenger (transferee). In advance, the assignee of the electronic taxi ticket activates a dedicated application on the second communication terminal 6c, inputs the assignee's identification information (user ID, etc.), authentication information, etc., and performs a login operation. On the other hand, the taxi crew starts a dedicated application by the third communication terminal 7, inputs the identification information (taxi ID, etc.) of the taxi on which the third communication terminal 7 is mounted, the authentication information, etc., and performs the login operation. To do. The management server 1 authenticates the transferee or a taxi crew member by the identification information, the authentication information, etc. transmitted from the second communication terminal 6c or the third communication terminal 7 by the login operation.

  As shown in FIG. 6, when the browsing request is transmitted from the second communication terminal 6c (step S31), the information providing unit 113 of the management server 1 can use an electronic taxi ticket for the transferee to the second communication terminal 6c. Browse information is transmitted (step S32). For example, the information providing unit 113 acquires the ticket ID, the name of the taxi company, the name of the contractor, and the like from the electronic taxi ticket record corresponding to the identification information of the transferee, and transmits the information as browsing information.

FIG. 7 shows a display example of browsing information on the second communication terminal 6c.
As shown in FIG. 7, on the second communication terminal 6c, the electronic taxi ticket available to the transferee is selectively displayed based on the browsing information from the management server 1. In each electronic taxi ticket column, ticket contents such as a ticket ID of the electronic taxi ticket, a contractor name, and a name of a taxi company who can use the electronic taxi ticket are displayed.

  The transferee can determine the taxi to be boarded by the displayed name of the taxi company, but the taxi to be boarded on the management server 1 by the second communication terminal 6c is a vehicle for which an electronic taxi ticket can be used. You can also inquire whether or not. When making an inquiry, the transferee selects an electronic taxi ticket to be used for payment on the display screen shown in FIG. 7, and then inputs identification information of a taxi to be boarded, for example, a taxi ID, to the second communication terminal 6c. Although it may be input to the second communication terminal 6c by the input operation of the transferee, in order to facilitate the input of the taxi ID, the taxi ID is encoded into a QR code (registered trademark) or the like and displayed inside or outside the vehicle, It is preferable that the displayed code be read by the second communication terminal 6c. The code may be displayed by the third communication terminal 7 used by a crew member of a taxi who is planning to board.

  The second communication terminal 6c selects the electronic taxi ticket to be used according to the operation of the transferee (step S33). In addition, the second communication terminal 6c acquires the taxi ID of the taxi scheduled to board (step S34), and acquires the current position information (eg GPS coordinates). The second communication terminal 6c transmits the ticket ID of the selected electronic taxi ticket, the acquired taxi ID, the user ID of the transferee authenticated at the time of login, and the position information to the management server 1 (step S35).

  In the management server 1, the ticket management unit 112 collates the received ticket ID, taxi ID and user ID of the transferee with the record, and if they match, validates the electronic taxi ticket with the ticket ID to the second communication terminal 6c. It is notified, and when they do not match, it is notified that they are invalid (step S36). Specifically, the ticket management unit 112 searches for a record that matches the ticket ID received from the second communication terminal 6c and the user ID of the transferee, and if there is no matching record, determines that the electronic taxi ticket is invalid. .. If there is a matched record, the ticket management unit 112 acquires the identification information (for example, ID, name, etc.) of a taxi company (transport company) that provides a taxi that can be boarded from the record. In addition, the ticket management unit 112 acquires the identification information of the taxi company that provides the taxi to be boarded by the received taxi ID. For example, if the taxi ID is a combination of the vehicle number and the identification information of the taxi company, the ticket management unit 112 can acquire the identification information of the taxi company from the taxi ID. Further, by storing a table in the storage unit 12 in which the identification information of each taxi company and the taxi ID of a taxi that each taxi company can provide are stored in the storage unit 12, the ticket management unit 112 converts the taxi ID into the taxi ID. It is also possible to obtain the identification information of the corresponding taxi company. The ticket management unit 112 determines that the electronic taxi ticket to be used is valid when the identification information of the taxi business operator acquired from the record and the identification information of the taxi business operator acquired from the ticket ID match, and invalid if they do not match. It is determined that

Even if the identification information of the taxi company matches, the ticket management unit 112 stores the expiration date in the record and the current date and time is over the expiration date, or the prohibition flag is set in the prohibition item. If it is saved, it will be notified that it is invalid.
The second communication terminal 6c displays the notification transmitted from the management server 1 (step S37).

FIG. 8 shows a display example of the notification on the second communication terminal 6c.
As shown in FIG. 8, the second communication terminal 6c displays a notification that the selected electronic taxi ticket is valid and that the electronic taxi ticket can be used. With this display, the transferee can confirm whether or not the selected electronic taxi ticket can be used for the taxi scheduled to board. On the second communication terminal 6c, buttons d1 and d2 are displayed together with the notification so that the user can choose to board or to end without boarding. When the button d1 for selecting to board is operated, the second communication terminal 6c transmits the boarding notification information to the management server 1. Upon receiving the boarding notification information, the ticket management unit 112 of the management server 1 stores the position information received from the second communication terminal 6c in the record as the boarding location position information, and stores the current date and time as the boarding date and time in the record. To do. Note that the above-described use prohibition registration can be performed immediately before boarding, specifically, until the button d1 is operated.

  When the electronic taxi ticket is valid and the boarding notification information is received, the management server 1 sends the notification information including the ticket ID acquired from the second communication terminal 6c and the user ID of the transferee to the third communication terminal 7. It is transmitted (step S38). The third communication terminal 7 displays the notification of the electronic taxi ticket to be used based on the transmitted notification information (step S39). From this display, the taxi crew can understand the electronic taxi ticket used for payment and the information of the passenger (transferee).

  In the processing procedure described above, the transferee confirms the browsing request and the availability of the electronic taxi ticket using the second communication terminal 6c. However, the taxi crew requested by the transferee uses the third communication terminal 7 A browsing request or confirmation may be made. That is, in step S31, the browsing request may be transmitted from the third communication terminal 7 to the management server 1, and the information providing unit 113 of the management server 1 may transmit the browsing information to the third communication terminal 7. Further, the third communication terminal 7 may perform the processing of steps S33 to S35 so that the availability can be confirmed. Accordingly, even a passenger who cannot use the application can use the electronic taxi ticket by requesting a taxi crew member. The third communication terminal 7 may be acquired by reading a QR code or the like that encodes the user ID and the ticket ID, or may be acquired by communication such as Bluetooth (registered trademark) or RFID. It is preferable that the third communication terminal 7 has a configuration in which the third communication terminal 7 reads or obtains it by communication because the operation of the crew and the transferee becomes easy. The code may be displayed by the second communication terminal 6 or may be printed and displayed on a medium such as a card. Further, the third communication terminal 7 can acquire the taxi ID input at the time of login as the taxi ID of the boarding schedule, and can acquire the current position detected by the third communication terminal 7 as the position information of the boarding place.

(Processing when boarding when requesting dispatch)
At the time of boarding, it is possible to make a request for vehicle allocation in parallel with the confirmation of availability of the electronic taxi ticket. For example, a button for requesting a vehicle allocation may be provided on the display screen shown in FIG. 7, and an operation of the button may allow selection of an electronic taxi ticket to be used and input of an instruction for a vehicle allocation request. Upon receiving the input of the vehicle allocation request instruction, the second communication terminal 6c transmits the vehicle allocation request to the management server 1 together with the ticket ID of the selected electronic taxi ticket.

  When the vehicle allocation management unit 114 of the management server 1 receives the vehicle allocation request and the ticket ID of the electronic taxi ticket to be used from the second communication terminal 6c, the identification information of the taxi company (transport company) is acquired from the record with the matching ticket ID. To get. The vehicle allocation management unit 114 transmits the ticket ID of the electronic taxi ticket to be used, which is received from the second communication terminal 6c, together with the vehicle allocation request, to the vehicle allocation system 8 corresponding to the acquired identification information of the taxi company. The vehicle allocation management unit 114 may transmit the identification information of the contractor and the identification information of the passenger (the transferee who is the user of the second communication terminal 6c) acquired from the record of the ticket ID.

In the vehicle allocation system 8, when a taxi is allocated in response to a vehicle allocation request, identification information of the allocated taxi (for example, taxi ID, vehicle number, etc.) is transmitted to the management server 1 together with the ticket ID received from the management server 1.
The ticket management unit 112 of the management server 1 stores the identification information of the dispatched taxi in the boarded vehicle item of the ticket ID record received from the dispatch system 8. As a result, the electronic taxi ticket with the ticket ID becomes valid only for the taxi to which the taxi is dispatched. The information providing unit 113 of the management server 1 transmits the identification information of the taxi dispatched to the second communication terminal 6c. The second communication terminal 6c displays the identification information of the dispatched taxi. The transferee can identify the taxi dispatched by the identification information.

  When boarding a taxi, it is possible to make an inquiry as to whether or not an electronic taxi ticket can be used in a taxi scheduled to board by the processing procedure shown in FIG. 6 described above. In this case, when determining whether the electronic taxi ticket is valid or invalid in step S36, it is also determined whether the identification information such as the taxi ID matches. That is, it is not determined that the ticket ID and the taxi company of the taxi to be boarded are the same, and it is valid when the taxi ID of the taxi to be boarded is the same as the taxi ID stored in the record by the dispatch. Is judged. As a result, it is possible to prevent a wrong taxi from being taken by a taxi other than the allocated taxi even if the taxi is the same.

(Processing when getting off)
FIG. 9 shows a processing procedure of the management server 1 when getting off the vehicle.
When getting off, the usage fee is calculated from the travel distance and displayed by an in-vehicle device such as a taxi fare meter. As shown in FIG. 9, the third communication terminal 7 acquires the usage fee calculated by the in-vehicle device (step S51). When the in-vehicle device is a device compatible with the boarding ticket system 100, the in-vehicle device may transmit the usage fee to the third communication terminal 7, or the in-vehicle device encodes the usage fee into a QR code or the like. It may be configured to be displayed as. The third communication terminal 7 can acquire the usage fee by reading the code. When the in-vehicle device does not support the boarding ticket system 100, the third communication terminal 7 may acquire the usage charge by an input operation by the crew member. Further, the third communication terminal 7 may acquire the usage fee by photographing the usage fee displayed on the in-vehicle device and recognizing the number indicating the usage fee from the obtained captured image.

  In addition, the third communication terminal 7 acquires the current position information and the current date and time as the departure date and time. The third communication terminal 7 indicates the usage contents of the taxi such as the acquired usage charge, location information and getting-off date and time, taxi ID input at the time of login, ticket ID transmitted from the management server 1 at the time of boarding, and user ID of the passenger. It is transmitted to the management server 1 as usage information (step S52). In the management server 1, the ticket management unit 112 stores the received usage information in the record that matches the ticket ID received from the third communication terminal 7. Specifically, the ticket management unit 112 stores the usage fee, the taxi ID, and the user ID received together with the ticket ID, as the identification information of the boarding vehicle and the identification information of the passenger. Further, the ticket management unit 112 stores the received position information as the position information of the disembarking place (step S53).

  After the saving, the information providing unit 113 of the management server 1 acquires the ticket ID, the boarding place, the getting-off place, the usage fee, and the like from the corresponding record to generate the payment completion notification information, and the second communication terminal 6c and the third communication. It is transmitted to the terminal 7 (step S54). The second communication terminal 6c and the third communication terminal 7 display the payment completion notification based on the received notification information (steps S57 and S58). This allows the transferee and the taxi crew to confirm the completion of payment. To prevent fraud, an approval button is provided on the payment completion notification screen, and when this button is operated on the second communication terminal 6c or the third communication terminal 7, the ticket management unit 112 of the management server 1 Records approved for approval by the assignee or crew may be stored. Instead of the button, the voice of the assignee or the crew member who approves or acknowledges may be input by the second communication terminal 6c or the third communication terminal 7, and the management server 1 may store the voice in the record.

  In addition, the information providing unit 113 generates notification information of the usage history from the record of the electronic taxi ticket used for payment, and transmits the notification information to the second communication terminal 6b of the owner (step S55). For example, the information providing unit 113 acquires a ticket ID, a taxi ID of a boarding vehicle, a taxi company, a boarding place, a getting-off place, and the like from the record, and transmits the information as usage history notification information. The second communication terminal 6a displays the usage history notification based on the sent notification information (step S56). As a result, the owner can confirm how the transferred electronic taxi ticket was used, whether it was illegally used, and the like.

FIG. 10 shows an example of the usage history notification.
As shown in FIG. 10, the usage history notification includes a taxi company, a contractor's name, a ticket ID, etc. as information on the used electronic taxi ticket. Further, the usage history notification includes a taxi ID and a name of a transportation company as information on the taxi that has been boarded, and usage information such as a boarding place and a getting-off place and a usage charge as the usage content.

  In the processing procedure described above, the third communication terminal 7 transmits the usage information including the usage fee, but the second communication terminal 6c can also perform the proxy information. In this case, the second communication terminal 6c may read a code such as a QR code displayed by the in-vehicle device, or the code displayed by the third communication terminal 7 may be read by the second communication terminal 6c. Thereby, even when the third communication terminal 7 cannot be used, the payment can be completed by the second communication terminal 6c.

  Thereafter, when the transportation operator charges the taxi usage fee to the contractor, the third communication terminal 7 transmits a settlement request to the management server 1. In response to a request from the third communication terminal 7, in the management server 1, the ticket processing unit 115 sorts the electronic boarding ticket records for each provider or each contractor, and generates and provides billing information from the sorted records. It transmits to the person's settlement system 9. The billing information is a list of usage information such as usage fees sorted for each contractor. The settlement system 9 can perform the settlement process based on the billing information received from the management server 1.

(When transferring to a non-user of the boarding ticket system)
The owner should transfer the electronic taxi ticket to the non-user of the boarding ticket system 100, such as when the passenger of the taxi cannot use the dedicated app or when the passenger who does not use the dedicated app is the transferee. You can also
FIG. 11 shows a processing procedure at the time of boarding when the transferee is not registered.

  As shown in FIG. 11, when the browsing request is transmitted from the second communication terminal 6b to the management server 1 (step S71), the management server 1 transmits the browsing information to the second communication terminal 6b (step S72). On the second communication terminal 6b, an electronic taxi ticket that can be used by the owner is selectively displayed based on the browse information, as shown in FIG. The owner selects the electronic taxi ticket as well as the option to declare the transfer. When the transfer declaration option is selected, the second communication terminal 6b selects the electronic taxi ticket to be used according to the selection operation (step S73), and the transfer declaration is managed together with the ticket ID of the selected electronic taxi ticket on the management server. Send to 1.

  Upon receiving the transfer declaration, the management server 1 collates the ticket ID received by the ticket issuing unit 111 with the identification information of the owner acquired from the second communication terminal 6b at the time of login with the record. Issue transferee authentication information such as number and reservation number. The ticket management unit 112 stores the authentication information issued to the matched record. The information providing unit 113 acquires the transferee authentication information from the record and transmits it to the second communication terminal 6b (step S75).

  The second communication terminal 6b displays the transferee authentication information. The owner is the owner's identification information or the ticket of the electronic taxi ticket that has been notified as valid, such as "Please use the ticket of owner X and tell the crew the password ****" The transferee is informed so that the crew member can be informed of the ID and the authentication information displayed on the second communication terminal 6b.

  When the transferee takes a taxi, the taxi crew who receives the transferee's authentication information and the owner's identification information or the ticket ID of the electronic taxi ticket from the transferee is notified by the third communication terminal 7 of the electronic taxi ticket. Inquire. The inquiry process is the same process as steps S33 to S35 shown in FIG. That is, the third communication terminal 7 transmits the ticket ID or the identification information of the owner and the authentication information of the transferee input by the crew together with the taxi ID and the current position information of the taxi acquired at the time of login to the management server 1 ( Step S77).

  As in step S36 shown in FIG. 6, the ticket management unit 112 of the management server 1 determines whether the ticket ID or the identification information of the owner matches the record, and whether the identification information of the taxi operator matches. In addition to the determination, the validity or invalidity of the electronic taxi ticket is determined depending on whether the transferee authentication information also matches the record. The taxi company identification information acquired from the taxi ID and the taxi company identification information acquired from the record in which the ticket ID or the owner identification information match, and the transferee authentication information acquired from the record When the authentication information received from the third communication terminal 7 matches, the ticket management unit 112 sends a notification of validity to the third communication terminal 7. If any of them do not match, the transferee is not authenticated, and the ticket management unit 112 transmits an invalid notification to the third communication terminal 7 (step S78). The third communication terminal 7 displays the notification transmitted from the management server 1 (step S79). The crew member informs the transferee of the displayed notification content, and the transferee can decide whether or not to board.

  If the owner can be present at the time of getting on the transferee, the processing of steps S31 to S37 shown in FIG. 6 is executed between the owner's second communication terminal 6b and the management server 1 to determine whether the electronic taxi ticket is valid or invalid. The notification may be displayed on the second communication terminal 6b.

  The process procedure at the time of getting off the vehicle is as follows: In step S52 shown in FIG. 9, the ticket ID of the electronic taxi ticket for which the third communication terminal 7 has received the valid notification at the time of boarding is transmitted to the management server 1, and in steps S54 and S55 the management server 9 is the same as the processing procedure shown in FIG. 9, except that the payment completion and usage history notification information transmitted from No. 1 are both transmitted to the owner's second communication terminal 6b. The owner can grasp the taxi usage status and payment status by the transferee from the notification information from the management server 1.

  According to the above processing procedure, even if the passenger is not the passenger of the boarding ticket system 100, such as when it becomes necessary to suddenly transfer the electronic taxi ticket to the customer or when the passenger cannot use the application. , Electronic taxi tickets can be transferred and used.

  As described above, the management server 1 of the present embodiment creates a record of an electronic boarding ticket, and uses the first communication terminal 5, the second communication terminal 6 and the third communication terminal 7 to provide a provider, a contractor, a transportation operator. , Get information such as usage fees and save it in a record. Further, the management server 1 provides the browsing information, the notification information, and the like generated from the record according to the request transmitted from the first communication terminal 5, the second communication terminal 6, and the third communication terminal 7. In this way, the management server 1 manages the electronic boarding ticket by the record, so that the electronic boarding ticket can be used by communicating with the management server 1 without downloading the electronic boarding ticket to the second communication terminal 6. Also, the identification information or authentication information of the owner and the transferee can be stored in the record, and the electronic boarding ticket can be transferred. Therefore, it is possible to provide an electronic boarding ticket that can be used in various usage forms.

  Since the electronic boarding ticket of this embodiment does not require a medium such as a special paper or an IC card from issuance to settlement, it is possible to omit human work such as printing, distribution, collection, and sorting of the boarding ticket. In addition, the management server 1 acquires the usage information such as the usage amount, the usage date and time, the occupant, and the boarding section from the boarding point to the boarding point from the first communication terminal 5, the second communication terminal 6, and the third communication terminal 7. Since it is saved in a record as a record, the work of filling out these on a paper medium at the time of payment can be omitted. Since the usage information is automatically saved, it is possible to prevent unauthorized use due to false entry. In addition, the electronic boarding ticket can be issued immediately, and it is not necessary to have a physical inventory, so that the theft or loss of the boarding ticket can be reduced, and the management cost can be reduced.

  Further, according to the browsing information transmitted from the management server 1, the provider can easily grasp the issuing destination, the issuing amount, etc. of the electronic boarding ticket, so that it is easy to detect an abnormal use, and if it is detected, the management is performed. By registering the use prohibition in the server 1, the use of the electronic boarding ticket can be easily stopped. In addition, the contractor can easily grasp the use status of the electronic boarding ticket and can detect the illegal use at an early stage.

Although the preferred embodiments of the present invention have been described above, the present invention is not limited to these embodiments, and various modifications and changes can be made within the scope of the gist thereof.
For example, when the boarding date and time, the boarding place, the getting-off place, and the like are determined in advance, the ticket management unit 112 of the management server 1 provides the information from the first communication terminal 5 or the second communication terminal 6 when the electronic taxi ticket is issued. It may be retrieved and saved in a record. When boarding, the ticket management unit 112 can determine that the electronic taxi ticket is invalid if the boarding date and time, the boarding place, and the like acquired from the second communication terminal 6 or the third communication terminal 7 do not match the record. When the user of the second communication terminal 6 is the contractor or the owner, the ticket management unit 112 does not determine that the ticket is invalid, and the boarding date and time, the boarding place, and the like saved at the time of the issuance are determined by the second communication terminal 6 or The electronic taxi ticket may be used by overwriting the boarding date and time, boarding place, etc. newly acquired from the communication terminal 7.

  Further, the method of acquiring the position information of the boarding place or the getting-off place is not limited to the GPS described above. For example, the position information of a predetermined position such as a bus stop, a station ticket gate, and a facility is coded into a QR code or the like and displayed at each predetermined position, and the displayed code is read by Beacon, RFID, Felica (registered trademark), or the like. You can also get information.

  Further, in the above-described embodiment, an example in which the passenger is boarded after confirming the use of the electronic taxi ticket has been described, but the passenger may board the passenger without confirming the use. In this case, the second communication terminal 6 or the third communication terminal 7 transmits the location information of the boarding place to the management server 1 at the time of boarding, and the ticket ID of the electronic taxi ticket used when getting off, the taxi ID of the boarded passenger, and the passenger The user ID, the location information of the disembarking place, and the like may be transmitted.

1 Management Server 111 Ticket Issuing Unit 112 Ticket Management Unit 113 Information Providing Unit 114 Vehicle Distributing Management Unit 115 Ticket Processing Unit 12 Storage Unit 5 First Communication Terminal 6, 6a, 6b, 6c Second Communication Terminal 7 Third Communication Terminal 8 Vehicle Distributing System 9 settlement system

Claims (12)

A first communication terminal of a boarding ticket provider, a second communication terminal of a contractor who concludes a usage contract with the boarder to receive the boarding ticket, and a vehicle that can be boarded using the boarding ticket. A management server connected via a network to a third communication terminal of a transportation company to be provided,
A ticket issuing unit that issues an electronic boarding ticket, adds identification information, and creates a record when receiving the boarding ticket issuing request from the first communication terminal or the second communication terminal.
A storage unit for storing a record of the electronic boarding ticket;
In the record of the electronic boarding ticket, the identification information of the provider who has signed the contract for using the electronic boarding ticket, the identification information of the contractor, and the identification of the transportation company that provides a vehicle that can use the electronic boarding ticket. A ticket management department that stores information,
In response to a browsing request from the first communication terminal, the second communication terminal, or the third communication terminal, browsing information of ticket contents is generated from a record of the electronic boarding ticket, and the first communication terminal and the second communication terminal are generated. An information providing unit for transmitting to a communication terminal or the third communication terminal,
The ticket management unit provides, from the second communication terminal or the third communication terminal, identification information of the electronic boarding ticket used for payment of the usage fee of the vehicle and usage information indicating usage content of the vehicle. When received, the usage information is stored in a record of the electronic boarding ticket with which the identification information matches,
Management server. When the ticket management unit receives from the second communication terminal or the third communication terminal the identification information of the vehicle to be boarded and the identification information of the electronic boarding ticket to be used, each of the identification information is set to the electronic boarding board. By comparing with the record of the ticket, if the coincidence is found, the validity of the electronic boarding ticket is notified to the second communication terminal or the third communication terminal, and if not coincident, the invalidity is notified.
The management server according to claim 1. The ticket management unit,
Upon receiving a registration request for the owner of the electronic boarding ticket from the first communication terminal or the second communication terminal, the identification information of the owner is stored in a record of the electronic boarding ticket,
When the identification information of the electronic boarding ticket to be used, the identification information of the vehicle to be boarded, and the identification information of the owner are received from the second communication terminal or the third communication terminal, each of the identification information is acquired by the electronic device. By collating with the record of the boarding ticket, if the two match, the electronic communication ticket is notified of the validity to the second communication terminal or the third communication terminal, and if they do not match, the invalidity is notified.
The management server according to claim 1. The ticket management unit,
When a registration request for a transferee to whom the electronic boarding ticket is transferred from the owner is received from the first communication terminal or the second communication terminal, the record of the electronic boarding ticket includes the identification information of the owner and the Save the transferee identification information,
When the identification information of the electronic boarding ticket to be used, the identification information of the vehicle to be boarded, and the identification information of the transferee are received from the second communication terminal or the third communication terminal, each of the identification information is acquired by the electronic device. By collating with the record of the boarding ticket, if the two match, the electronic communication ticket is notified of the validity to the second communication terminal or the third communication terminal, and if they do not match, the invalidity is notified.
The management server according to claim 3. When the ticket issuing unit receives from the first communication terminal or the second communication terminal the identification information of the electronic boarding ticket transferred from the owner to the transferee and the identification information of the owner, the identification information If the information matches the record of the electronic boarding ticket, issue the transferee authentication information,
The ticket management unit,
Save the transferee authentication information in the electronic boarding ticket record,
When the identification information of the electronic boarding ticket to be used, the identification information of the vehicle to be boarded, and the authentication information of the transferee are received from the second communication terminal or the third communication terminal, the identification information and the authentication information. Is compared with the record of the electronic boarding ticket, and when the two match, the second communication terminal or the third communication terminal is notified of the validity of the electronic boarding ticket, and when they do not match, the invalidity is notified.
The management server according to claim 3. When the identification information of the electronic boarding ticket to be used is received together with the vehicle allocation request from the second communication terminal, the identification information of the transportation operator is acquired from the record that matches the identification information, and the identification of the transportation operator is performed. Further comprising a vehicle allocation management unit for transmitting the vehicle allocation request to the vehicle allocation system corresponding to the information,
The management server according to claim 1. The ticket management unit,
When the identification information of the vehicle dispatched in response to the vehicle dispatch request is received from the vehicle dispatch system, the vehicle identification information is stored in the record,
When the identification information of the vehicle to be boarded and the identification information of the electronic boarding ticket to be used are received from the second communication terminal or the third communication terminal, each of the identification information is collated with the record of the electronic boarding ticket, If they match, the electronic communication ticket is notified of the validity of the second communication terminal or the third communication terminal, and if they do not match, the invalidity is notified.
The management server according to claim 6. When the ticket management unit receives the position information of the boarding place and the getting-off place of the vehicle from the second communication terminal or the third communication terminal, the ticket management unit stores the position information in the record.
The management server according to any one of claims 1 to 7. The ticket management unit receives, from the second communication terminal or the third communication terminal, the usage information including the usage fee calculated by an in-vehicle device of the vehicle.
The management server according to claim 1. The information providing unit generates notification information of a usage history from a record of the electronic boarding ticket in which the usage information is stored, and transmits the usage history notification information to the second communication terminal.
The management server according to claim 9. The electronic boarding ticket records are sorted by the provider or the contractor, billing information is generated from the sorted records, and the ticket processing unit is further provided for transmitting the billing information to the settlement system.
The management server according to claim 1. A method of managing an electronic boarding ticket executed by a management server, comprising:
The management server is capable of boarding by using a first communication terminal of a boarding ticket provider, a second communication terminal of a contractor who contracts with the boarding party to receive the boarding ticket, and the boarding ticket. It is connected to the third communication terminal of a transportation company that provides vehicles via a network,
Receiving a request to issue the boarding ticket from the first communication terminal or the second communication terminal, issuing an electronic boarding ticket, adding identification information, and creating a record;
Storing a record of the electronic boarding ticket in a storage unit;
In the record of the electronic boarding ticket, the identification information of the provider who has signed the contract for using the electronic boarding ticket, the identification information of the contractor, and the identification of the transportation company that provides a vehicle that can use the electronic boarding ticket. Saving information,
In response to a browsing request from the first communication terminal, the second communication terminal, or the third communication terminal, browsing information of ticket contents is generated from a record of the electronic boarding ticket, and the first communication terminal and the second communication terminal are generated. Transmitting to a communication terminal or the third communication terminal,
When the identification information of the electronic boarding ticket used for payment of the usage fee of the vehicle and the usage information indicating the usage content of the vehicle are received from the second communication terminal or the third communication terminal, the identification information is received. Storing the usage information in a record of the electronic boarding ticket that matches
Management method including.

Images