JP6387545B1 - Electronic taxi ticket issuance management system - Google Patents

Abstract

To improve convenience of a taxi ticket issue management system.
In an electronic taxi ticket issuance management system used by an issuer 200, a contractor 300, a user 400, and a taxi operator 600, a storage unit 110 and a contractor information input by the issuer 200 are stored in the storage unit. The identification information of the taxi ticket is generated and stored based on the user information related to the user 400 and the portable terminal 401 input by the issuer input receiving unit 121 transmitted to 110, the input person who is authenticated based on the contractor information. The contractor input receiving unit 122 that transmits the ticket identification information to the portable terminal 401 by transmitting to the unit 110, the boarding location and / or the getting-off location acquired by the ticket identification information and location information acquisition function, the usage amount, and the boarding date Boarding information reception unit 124 that collects boarding information including the information and transmits it to storage unit 110, ticket identification information and boarding information And a billing information generating section 125 for generating billing information used.
[Selection] Figure 2

Description

  The present invention relates to an electronic taxi ticket issuer, a contractor who has signed a taxi ticket use with the taxi ticket issuer, a user who uses a taxi using a taxi ticket provided by the contractor, and a taxi. The present invention relates to an electronic taxi ticket issuance management system used by taxi operators.

  A taxi ticket is a ticket issued by a taxi ticket issuing company based on a request from a contractor and distributed in advance to users such as employees who use the taxi from the contractor. When a taxi ticket user uses a taxi, he fills in the taxi ticket with the date of use, the section of use, and the amount of money to use, and passes it to the taxi driver. The taxi ticket is collected by a taxi company, and the taxi company issues a usage fee to the taxi ticket issuing company. Taxi ticket issuing companies collect usage fees for a certain period (usually one month) and charge the contractor.

  In addition, a contractor of a company or the like that holds an event may provide a taxi ticket to an invitee to the event. For example, Patent Document 1 includes a taxi ticket that prints the expiration date, usage period, or usage limit of a taxi ticket based on the information entered by the person in charge who received the request from the contractor at the taxi ticket issuing company. A system that can be issued is described.

  However, the system described in Patent Document 1 is a system for issuing a taxi ticket at a taxi ticket issuing company, and it takes a certain number of days for the issued taxi ticket to reach the contractor by mail or the like. Also, even for taxi tickets that are used for a predetermined purpose, it is customary for contractors to obtain more taxi tickets than they actually need in preparation for unexpected situations. It is often disposed of because it expires without being used.

Therefore, the present applicant has proposed a taxi ticket issuance management system in Patent Document 2 in which a contractor can obtain a necessary number of taxi tickets when necessary. This system is a taxi ticket issue management system used by a taxi ticket issuer and a contractor who has contracted with the taxi ticket issuer to use a taxi ticket.
An apparatus used by the taxi ticket issuer, an identifier printing unit for printing a taxi ticket with a predetermined identifier for identifying one or a plurality of taxi tickets, and correspondence between the identifier and the contractor A ticket issuance information creating unit for creating ticket issuance information including an attachment, and a basic ticket issuing device,
A device used by the contractor for accepting input of use restriction information, which is information for restricting use of a taxi ticket, for a part or all of the one or more taxi tickets printed with the identifier. A restriction information input unit; a use restriction information printing unit that prints the use restriction information on a taxi ticket printed with the identifier; and the printed use restriction information and the identifier based on the ticket issuance information received from the issuer. A completion ticket issuing device having a usage management information creating unit that creates usage management information in association with each other.

Japanese Patent Laid-Open No. 11-195143 Japanese Patent No. 5961890 JP 2007-18304 A JP 2017-84151 A

  In the taxi ticket issuance management system described in Patent Document 2, unlike the system described in Patent Document 1, the contractor writes the usage restriction information on the basic ticket created by the taxi ticket issuer and himself creates the taxi ticket himself. Finalize. Therefore, for example, when a contractor holds an event, a required number of taxi tickets can be issued and provided to users such as invitees immediately when necessary.

  In the taxi ticket issuance management system described in Patent Document 2, a taxi ticket is created by a contractor. Thereafter, a paper taxi ticket is handed over from the user to the taxi driver, and further from the taxi driver to the taxi. The taxi tickets of the same taxi ticket issuer are collected and handed over to the company, and the total usage amount is totaled. Paper taxi tickets cannot be strictly checked to see if they comply with restrictions such as date of use and usage section, and there is a problem that unauthorized use and unintended use cannot be prevented. In addition, taxi companies categorize taxi tickets for each taxi ticket issuing company, check the information on boarding places and drop-off places written on each ticket, and calculate the amount of usage. It was.

  The problems to be solved by the present invention are a taxi ticket issuer, a contractor who has signed a contract with the taxi ticket issuer for use of a taxi ticket, and a taxi ticket using a taxi ticket provided by the contractor. It is to improve the convenience of a taxi ticket issue management system used by a taxi operator and a taxi operator.

The present invention, which has been made to solve the above problems, uses an issuer that issues a taxi ticket, a contractor who has signed a contract with the issuer regarding the use of a taxi ticket, and a taxi ticket provided by the contractor. users who use a taxi, there is provided an electronic taxi ticket issue management system used by the taxi service who runs the及beauty taxis,
a) a storage unit for storing information;
b) is input by the issuer, the issuer input receiving unit for transmitting subscriber information on the subscriber in the storage unit,
c) authenticating the input person on the basis of the subscriber information is input by the authenticated inputting person, user information about the portable terminal having the user and the user of the taxi ticket, and the use of the taxi ticket together based on the use restriction information is limited to information to generate the ticket identification information of the taxi ticket transmitted to the storage unit, a subscriber input receiving unit for transmitting the ticket identification information to the movable portable terminal,
d) Collect the ticket identification information, boarding information including at least either the spending of getting-off locations及beauty boarding locations taxis that are utilized with cab ticket having the ticket identification information, associates them A boarding information reception unit to be transmitted to the storage unit,
according to an instruction from e) the issuer, characterized in that it comprises a billing information generator that generates a billing information using the ticket identification information and the boarding information stored in the storage unit.

  The electronic taxi ticket issuance management system according to the present invention is a system that is mainly operated and managed by the issuer. For example, the management server device managed by the issuer can be configured to include the above-described units. Therefore, the issuer input receiving unit is provided, and the contractor input receiving unit authenticates the input person based on the contractor information, and is configured to receive input of information by the authenticated input person. Yes.

The electronic taxi ticket issuance management system according to the present invention is used as follows. The taxi includes a hire or a shuttle bus that operates with payment of a fee from a contractor or a user. In the case where the taxi is a higher or shuttle bus, the taxi ticket is a ticket used for getting on the higher or shuttle bus.
First, when an issuer who issues a taxi ticket inputs contractor information related to a contractor who has contracted for use of an electronic taxi ticket, the issuer input reception unit transmits the contractor information to the storage unit. Thereby, the contractor information is stored in the storage unit. The contractor information may be transmitted by either wired communication or wireless communication. Similarly, transmission and collection of various other information may be performed by either wired communication or wireless communication. After that, the contractor input receiving unit authenticates the input person based on the contractor information, and the taxi ticket user (for example, an inviter to an event held by the contractor) is input by the authenticated input person. A storage unit that generates ticket identification information (such as an ID number of an electronic taxi ticket) of a taxi ticket based on user information about the portable terminal possessed by the user and use restriction information that restricts use of the taxi ticket Send to. Further, the ticket identification information is transmitted to the portable terminal. The use restriction information is, for example, at least one of a taxi use section (boarding place and / or alighting place), a use upper limit amount according to a charge assumed for use of the section, a usable period, and an expiration date. This information includes one.

  The user gets on the taxi, reads the identification information received by his portable terminal, gets on the taxi, and gets off at the destination. A boarding place and a destination (alighting place) can be specified by, for example, a position information acquisition function of a taxi. Alternatively, it can be specified by a position information acquisition function of a portable terminal possessed by a user or a position information acquisition function of a taxi terminal provided in a taxi as in the embodiments described later. Further, the usage amount is determined by a taximeter. When these pieces of information are confirmed, the boarding information reception unit collects the taxi ticket identification information, and boarding information including at least one of the taxi boarding area and the boarding area and the usage fee, and associates them with the storage unit. Send to. Such information is collected by, for example, reading the identification information of the electronic taxi ticket from the portable terminal of the user with a terminal provided in the taxi and transmitting it together with the boarding information. Alternatively, it may be performed by inputting and transmitting taxi identification information for identifying a taxi from the portable terminal of the user and transmitting boarding information from the taxi. The identification number and boarding information collected by the boarding information receiving unit are stored in the storage unit. Then, the billing information generating unit generates billing information using the ticket identification information and the boarding information stored in the storage unit according to an instruction from the issuer.

  As described above, in the electronic taxi ticket issuance management system according to the present invention, information on the contractor and the user, input of the portable terminal information of the user, generation of a taxi ticket (taxi ticket identification information), A series of processes of collection and storage and generation of billing information are all performed electronically. For this reason, it is possible to strictly check whether restrictions such as the use date and use section are being observed, and there is no worry of overlooking unauthorized use or unintended use like paper taxi tickets. In addition, since all taxi ticket usage histories are stored as electronic data, it is possible to easily perform operations such as confirming information on boarding places and getting-off places, and summing up usage charges. Thus, when the electronic taxi ticket issuance management system according to the present invention is used, convenience is improved as compared with a conventional system using a paper taxi ticket.

For example, Patent Documents 3 and 4 propose systems that can issue taxi tickets electronically.
Patent Document 3 describes a system for electronically issuing a taxi ticket by determining whether or not a ticket can be issued based on the applicant's ticket application authority and the like when receiving an application for issuing a taxi ticket by the applicant. However, this system is a ticket generation system that is operated and managed by the company to which the applicant belongs, and the taxi person himself performs the necessary procedures for issuing taxi tickets. The configuration is different from that of the present invention which is operated and managed. Specifically, the system described in Patent Document 3 does not have a configuration corresponding to the issuer input reception unit of the electronic taxi ticket issue management system according to the present invention. Patent Document 3 does not describe authenticating an applicant who intends to apply for an electronic taxi ticket.

  Patent Document 4 describes a system used by a first user, a second user, a user company (store, taxi company, etc.), and a credit card company. In this system, an electronic ticket is issued in response to an approximate request including information on the upper limit of use amount, expiration date, and contents of goods / services by the first user, and the second user is assigned based on the transfer request of the first user. Can be changed to user. However, this system mainly relates to an electronic ticket used for purchasing goods at a store, and a taxi ticket is issued as a cash voucher. In other words, it is not possible to obtain information on where to get on and off the taxi when using the ticket.

The electronic taxi ticket issue management system according to the present invention further includes:
f) After authenticating the user information, it is possible to adopt a configuration including a dispatching receiving unit that receives a dispatch request together with the location information of the portable terminal and instructs the taxi to dispatch a vehicle based on the location information. In the electronic taxi ticket issuance management system of this aspect, the user can arrange a taxi to get on using his / her portable terminal, which improves the convenience for the user.

An electronic taxi ticket issuance management system according to the present invention includes:
The billing information generating unit may be configured to bill the contractor for a taxi usage fee based on the billing information. In the electronic taxi ticket issuance management system according to this aspect, the billing information is classified for each contractor, and the processing of summing up the usage amount of taxi tickets issued by each contractor can be electronically performed. Therefore, it is possible to improve the convenience of the issuer related to the charge for the usage amount. Note that the billing information generation unit may charge the contractor for the usage amount when receiving an instruction from the issuer, and automatically charges the contractor for the usage fee at a predetermined cycle (for example, every month). You may make it do.

An electronic taxi ticket issuance management system according to the present invention includes:
The billing information generation unit can be configured to collate the boarding information with the use restriction information and determine whether or not they match. By using the electronic taxi ticket issuance management system of this aspect, it is possible to easily confirm that the issued electronic taxi ticket has been used for the intended purpose, and the convenience of the contractor is improved.

The contractor input receiving unit
Transmitting the user information to the storage unit;
For a user selected from the users stored in the storage unit, identification information of a taxi ticket can be generated and transmitted to the portable terminal of the selected user. When using the electronic taxi ticket issuance management system of this aspect, it is possible to save the trouble of inputting the same user information each time a taxi ticket is repeatedly provided to the same user. Will improve.

The contractor input receiving unit
Accepts event information, which is information related to the event, and invitee information related to the invitee to the event, asks the portable terminal of the invitee whether to participate / not participate in the event, and answers from each invitee Can be configured to be transmitted to the storage unit. In the electronic taxi ticket issuance management system according to this aspect, not only the electronic taxi ticket issuance management but also information related to responses to participation / nonparticipation in the event can be centrally managed, so the convenience of the contractor is improved. .

In the electronic taxi ticket issue management system of the above aspect,
The contractor input receiving unit
The ticket identification information can be transmitted to the portable terminal of the inviter who has obtained an answer to the participation in the event. In the electronic taxi ticket issuance management system of this aspect, it is possible to reliably issue a taxi ticket to an invitee who has obtained an answer to attendance at an event.

  By using the electronic taxi ticket issuance management system according to the present invention, the convenience can be improved as compared with a conventional system for issuing a paper taxi ticket.

The schematic block diagram of one Example of the electronic taxi ticket issue management system which concerns on this invention. The schematic block diagram of the management server apparatus in the electronic taxi ticket issue management system of a present Example. The schematic block diagram of the portable terminal in the electronic taxi ticket issue management system of a present Example. The schematic block diagram of the taxi apparatus in the electronic taxi ticket issue management system of a present Example. An example of the screen which searches special events in the electronic taxi ticket issue management system of a present Example. An example of the screen which displays the details of special event in the electronic taxi ticket issue management system of a present Example. An example of the screen displayed on a user's portable terminal in the electronic taxi ticket issue management system of a present Example. An example of the screen displayed on a taxi terminal in the electronic taxi ticket issue management system of a present Example. An example of the screen which searches a taxi ticket in the electronic taxi ticket issue management system of a present Example.

  An embodiment of an electronic taxi ticket issuance management system according to the present invention will be described below with reference to the drawings. As shown in FIG. 1, the electronic taxi ticket issuance management system according to the present embodiment is a system that is configured with a management server device 100 as a center. The taxi ticket issuer 200, the taxi ticket issuer 200, and the taxi A taxi operator who operates a taxi 500 having a location information acquisition function, a user 400 who uses a taxi using a taxi ticket provided by the contractor 300, and a taxi 500 having a location information acquisition function. Used by drivers and taxi companies 600). Although one person is shown in FIG. 1, each of them may be plural.

  FIG. 2 is a schematic configuration diagram of the management server device 100 used in the electronic taxi ticket issuance management system of the present embodiment. The management server device 100 of the present embodiment is a cloud server, but may be a device owned and managed by the issuer 200, for example. The management server device 100 includes a storage unit 110. The storage unit 110 includes an issuer information storage unit 111, a contractor information storage unit 112, a user information storage unit 113, an event information storage unit 114, and ticket information. A storage unit 115, a boarding information storage unit 116, and a billing information storage unit 117 are provided. The issuer information storage unit 111 stores an issuer ID (email address) and a password of the taxi ticket issuer 200 in advance.

  The management server device 100 also includes an issuer input reception unit 121, a contractor input reception unit 122, a vehicle allocation reception unit 123, a boarding information reception unit 124, and a billing information generation unit 125 as functional blocks. These functional blocks are implemented by executing the management server device program 120 by the CPU. An input unit 130 and a display unit 140 are connected to the management server device 100.

  In the electronic taxi ticket issuance management system of the present embodiment, the taxi ticket issuer 200, the contractor 300, and the taxi company 600 access the management server device 100 from the personal computer possessed by each through the Internet. The user 400 accesses the management server apparatus 100 from the portable terminal 401 possessed by the user 400 via the Internet. The driver of the taxi 500 accesses the management server device 100 from the taxi terminal 501 provided in the taxi 500 via the Internet.

  FIG. 3 is a schematic configuration diagram of a portable terminal 401 (smart phone, tablet terminal, etc.) possessed by the user 400 in the electronic taxi ticket issuance management system of the present embodiment. In addition to the storage unit 410, the position information acquisition unit 420, and the information reading unit 430, the portable terminal 401 includes an event reception unit 441, a dispatch request unit 442, a ticket presentation as functional blocks executed by the user application 440. Part 443 and boarding information transmission part 444 are provided. The information reading unit 430 can read various information stored in the target terminal, such as an imaging unit (camera, scanner, etc.) or a near field communication (NFC) unit. Can take form. In this embodiment, a case where the information reading unit 430 is a camera will be described as an example. The storage unit 410 is provided with a ticket information storage unit 411 and a boarding information storage unit 412. In addition, the portable terminal 401 is provided with an input unit 450 and a display unit 460.

  FIG. 4 is a configuration diagram of a taxi terminal 501 (tablet terminal or the like) installed in the taxi 500 in the electronic taxi ticket issuance management system of the present embodiment. In addition to the storage unit 510, the position information acquisition unit 520, and the information reading unit 530, the taxi terminal 501 includes a vehicle allocation reception unit 541 and a boarding information transmission unit 542 as functional blocks executed by the taxi terminal application 540. Yes. The information reading unit 530 can read various information stored in a target terminal, such as an imaging unit (camera, scanner, etc.) or a near field communication (NFC) unit. Can take form. In this embodiment, a case where the information reading unit 530 is a camera will be described as an example. The storage unit 510 includes a ticket information storage unit 511 and a boarding information storage unit 512. Here, the taxi terminal 501 is configured to include the position information acquisition unit 520 and the dispatching reception unit 541. However, these are configured to be able to communicate between the taxi terminal 501 and the devices conventionally provided in the taxi 500. An existing function of the taxi 500 may be used. The taxi terminal 501 is provided with an input unit 550 and a display unit 560.

  Next, a flow related to issuance of taxi tickets using the electronic taxi ticket issuance management system of the present embodiment will be described.

  In the electronic taxi ticket issuance management system of the present embodiment, as described above, the issuer ID (email address) and password of the issuer 200 that issues the taxi ticket are stored in advance in the issuer information storage unit 111 of the management server device 100. ing. In this embodiment, the mail address of the issuer 200 is used as the issuer ID, but it is also possible to use an ID different from the mail address. The same applies to the IDs of others described later.

  The issuer 200 accesses the management server device 100 via the browser of his computer. When accessed from the outside, the management server apparatus 100 displays a login screen for inputting an ID and a password on the display unit of the accessed computer. When the issuer 200 inputs his / her issuer ID (mail address) and password, the combination is compared with the issuer information stored in the issuer information storage unit 111.

  When it is authenticated that the input ID and password are those of the issuer 200, the issuer input reception unit 121 displays a screen for inputting the name of the contractor and the contractor ID (mail address). When the name of the contractor 300 and the contractor ID are input by the issuer 200, the password of the contractor 300 is automatically generated, and the contractor information storage is associated with the name of the contractor 300 and the contractor ID. Stored in the unit 112. Furthermore, an e-mail describing the URL and password for accessing the management server device 100 is transmitted to the e-mail address used as the contractor ID. At this time, the fact that the contractor ID is an e-mail address is also notified.

  When the contractor 300 accesses the management server apparatus 100 using the received URL, the management server apparatus 100 displays a screen for inputting an ID and a password on the display unit of the contractor 300 computer. When the contractor 300 inputs his / her contractor ID (email address) and the received password, the combination is verified with the contractor information stored in the contractor information storage unit 112.

  When it is authenticated that the input ID and password are those of the contractor 300, the contractor input reception unit 122 can receive the user ID of the user 400 (can be received by the portable terminal 401 possessed by the user 400). A screen for inputting an e-mail address (corresponding to information on the portable terminal in the present invention). When the user ID is input by the contractor 300, the password of the user 400 is automatically generated and stored in the user information storage unit 113 in association with the user ID. Further, an e-mail describing the URL and password for downloading the user application from the management server device 100 is transmitted to the e-mail address input as the user ID. In this embodiment, since the contractor is assumed to manage the personal information (name, etc.) of the user, the contractor inputs only the user ID. You may comprise so that information, such as a name, may be input. In other words, at least the user ID may be input here, and what other information is input may be determined as appropriate.

  The user 400 accesses the URL received by the portable terminal 401 owned by the user 400, downloads the user application, and installs it. When the user 400 executes the user application 440 on the portable terminal 401, each functional block described with reference to FIG. 3 is realized.

  The contractor input receiving unit 122 also receives the event information input by the contractor 300. The event information includes information on the event name, date and location, and location, as well as information on the invitees to the event, the participation / nonparticipation responses from the invitees, and the taxi ticket issuance status for the invitees. It is. The event information input by the contractor 300 is stored in the event information storage unit 114 with an event ID attached to each event. The event information storage unit 114 stores event information input by the contractor 300 for each contractor 300.

  When the contractor 300 instructs the confirmation of the event information by a predetermined operation after the authentication with the ID and the password, the contractor input receiving unit 122 reads the event information corresponding to the authenticated contractor 300 from the event information storage unit 114. A screen as shown in FIG. 5 is displayed on the display unit of the computer of the contractor 300. The upper part of this screen is a search section for searching for events by event name and / or date. Although only the event name and date are displayed here, other items (such as the venue) may be added. When the contractor 300 inputs these items and presses the “Search” button, a search for the event information input by the contractor 300 (here, A) is executed, and the result is displayed at the bottom of the screen. Is displayed. Fig. 5 shows the results of a search for events held between October 1, 2017 and October 31, 2017, when A, a contractor 300, does not specify an event name. It is an example of the shown screen. When the contractor 300 presses the search button without inputting anything, all the event information input by the contractor 300 is displayed. In the search result display column, an “edit” button is displayed together with a list of events, and by pressing this button, information on the event can be changed or deleted.

  When the contractor 300 selects one of the events by pressing an “edit” button in the event list displayed at the bottom of the screen, the details of the event information are displayed. FIG. 6 shows an example of the display screen. The upper part of the screen shows the name of the event, the date and place of the event, and an explanation about the event, and the lower part shows a list of invitees to the event. Participation / non-participation responses, and the status of taxi ticket issuance to invitees who have received participation responses are displayed. When the contractor 300 presses the “registration” button, a list of users input by the contractor 300 is displayed from the user information storage unit 113, and an invitee to this event is selected and added from the list. can do. When the contractor 300 adds an invitee to the event, the contractor 300 transmits an invitation to the event to the portable terminal 401 of the invitee, and inquires whether or not to participate in the event. For example, the event name, date, and location data are added to the invitation template stored in advance in the event information storage unit 114 and transmitted together with buttons and check boxes for answering participation / non-participation. Can be performed. In the list of invitees, a check box is provided for each invitee. For example, if the “Delete” button is pressed after checking a box of an invitee who has received a non-participating answer, the invitee is deleted from the list.

  When the portable terminal 401 of the user 400 receives the invitation to the event and the inquiry about participation / non-participation, the event reception unit 441 displays the name of the event, the date, the place of the event, on the display unit 460 of the portable terminal 401. In addition, the name of the contractor 300 who is an invitation source and buttons of “participation” and “non-participation” are displayed. When the user 400 presses any button, a corresponding answer is transmitted to the management server device 100. Note that the user 400 can also suspend the answer to the inquiry, and can confirm participation / nonparticipation in the event from the user application after confirming his / her schedule.

  In the management server device 100, when a response to participation / non-participation in the event is received from the portable terminal 401, the contractor input reception unit 122 stores the content of the response (participation or non-participation) in the event information storage unit 114. Reflect event information to update information.

On the screen shown in FIG. 6, among the invitees who have answered to participate, an “ticket issue” button is displayed in the ticket ticket type column for those invitees who have not yet issued a taxi ticket. When the contractor 300 presses this button, a pop-up screen for inputting a taxi ticket ticket type (upper limit), the number of sheets, and a use date provided to the invitee is displayed. When the user inputs such information, a taxi ticket identification number is generated, and a taxi ticket specifying the event name, ticket type (upper limit), number of sheets, and date of use is issued. These pieces of information are stored in the ticket information storage unit 115. In addition, the contents related to the ticket issue status of the event information stored in the event information storage unit 114 are updated. Here, as an example of setting the ticket type (upper limit) and the date of use as information that restricts the use of taxi tickets, a taxi ticket that sets the boarding location and the departure location can also be issued. . The date of use may be one that designates only one day, which is the date of the event, or may be an expiration date or a usable period.

  When the contractor input reception unit 122 issues a taxi ticket, the taxi ticket identification number, ticket type, number of pieces, and use date information are issued to the portable terminal 401 of the user 400 who is the target of the taxi ticket. Send.

  Next, the flow at the time of using the taxi ticket issued in the electronic taxi ticket issue management system of a present Example is demonstrated.

  An example of a screen displayed on the display unit 460 when the user application 440 is executed in the portable terminal 401 of the user 400 will be described with reference to FIG. FIG. 7A shows a login screen that is displayed first when the user application 440 is executed. On this screen, the user 400 logs in by entering the notified user ID (mail address) and password. When the user 400 forgets the password, when the user 400 clicks the display, the management server apparatus 100 is inquired about the password. The management server device 100 transmits an email describing the password to the email address registered as the user ID.

  FIG. 7B shows a menu screen displayed after login, and two buttons “call a taxi” and “use ticket” are displayed. When the “call a taxi” button is pressed, the vehicle allocation request unit 442 operates the location information acquisition unit 420 to acquire the current location information of the portable terminal 401, and requests the management server device 100 to allocate the vehicle along with the information. .

  When the management server device 100 receives the current location information and the vehicle allocation request from the portable terminal 401, the vehicle allocation reception unit 123 of the management server device 100 identifies the user 400 of the portable terminal 401 that has received the vehicle allocation request, and the user The ID and current location information are transmitted and the taxi company 600 is requested to dispatch. The taxi company 600 determines a taxi that can be dispatched to the current location of the received taxi 500 (typically the empty taxi closest to that point) from the taxi 500 in operation, and heads for the taxi 500 to the current location. To instruct. In addition, identification information (for example, vehicle number and number plate information) of the taxi 500 that has instructed the vehicle allocation is transmitted to the vehicle allocation reception unit 123. The vehicle allocation reception unit 123 transmits the received information to the portable terminal 401. When the taxi 500 receives a dispatch instruction from the taxi company 600 and the location information of the dispatch destination, the dispatch acceptance unit 541 operates a car navigation system (not shown) to guide the taxi 500 to that position.

  When the portable terminal 401 receives the identification information of the taxi 500, the vehicle allocation request unit 442 displays the identification information on the display unit 460 of the portable terminal 401. When the user 400 presses the “use ticket” button on the menu screen of FIG. 7B while waiting for the arrival of the taxi displayed on the display unit 460, the ticket presenting unit 443 displays information on the received taxi ticket. (Including a used taxi ticket) is displayed on the display unit 460. In the present embodiment, as shown in FIG. 7 (c), taxi tickets are listed on this screen for each provider (corporations A, B, C). When the user 400 selects one of the providers on this screen, as shown in FIG. 7 (d), the taxi ticket provided by the provider (here, A) is displayed. When the user 400 further selects one of the displayed taxi tickets, as shown in FIG. 7 (e), detailed information on the taxi ticket and a two-dimensional code describing the information are displayed on the display unit 460. Is displayed (an example of presentation in a predetermined format).

  When the driver of the taxi 500 starts a taxi application installed in the taxi terminal 501 in advance, a menu screen shown in FIG. 8A is displayed. Here, when the “ticket use” button is pressed, the information reading unit 530 is activated, and a screen for reading the two-dimensional code is displayed (FIG. 8B). When the taxi driver places the two-dimensional code displayed on the display unit 460 of the portable terminal 401 of the user 400 within the frame displayed on the display unit 560, the two-dimensional code is photographed. Subsequently, the boarding information transmission unit 542 acquires taxi ticket information from the two-dimensional code and displays the information on the display unit 560 of the taxi terminal 501 (FIG. 8C).

  Here, the example in which the two-dimensional code is photographed by the camera that is the information reading unit 530 has been described. However, predetermined image processing is performed on the image data acquired by photographing the character information of the taxi ticket displayed on the display unit 460 by the camera. It is also possible to apply a technique such as acquiring taxi ticket information. In addition, since the information reading unit 530 is a camera in the present embodiment, a configuration in which taxi ticket information is extracted by photographing a two-dimensional code displayed on the display unit of the portable terminal 401 of the user 400 is taken as an example. However, a short-range wireless communication unit is used as the information reading unit 530, and is stored in a predetermined format in the portable terminal 401 of the user 400, and a predetermined operation by the user 400 (for example, in the information reading unit 430 of the portable terminal 400) It is also possible to adopt a configuration such as acquiring information on a taxi ticket presented so as to be readable by an operation that enables short-range wireless communication with the taxi terminal 500 by activating a short-range wireless communication unit or the like. .

  The driver of the taxi 500 confirms the detailed information (usage date, etc.) of the displayed taxi ticket, and determines whether the taxi ticket can be used. Alternatively, the date information of the taxi terminal 501 itself and the position information acquired by the position information acquisition unit 520 are collated with the information of the taxi ticket extracted from the two-dimensional code, and the availability of the taxi terminal is displayed on the display unit 560. You can also

  When the user 400 gets on the taxi 500 and arrives at the destination, the driver determines the amount of use by the meter mounted on the taxi 500. When the driver presses an “amount input” button displayed at the bottom of the ticket detail screen in FIG. 8C, an amount input screen shown in FIG. 8D is displayed. At this time, the boarding information transmission unit 542 operates the position information acquisition unit 520 to acquire the current position of the taxi 500. And the point (boarding place) and the alighting place where the user 400 got on the taxi 500 are displayed on the display unit 560. When the user 400 confirms the boarding location, the getting-off location, and the usage amount displayed on the display unit 560 and presses the “OK” button, the taxi ticket identification information, the boarding date and time, the boarding location, the getting-off location, and The boarding information including the usage amount information is transmitted to the management server device 100. Further, the information is stored in the boarding information storage unit 512 of the taxi terminal 501. When “ticket history” is selected on the screen shown in FIG. 8A, the used taxi ticket identification information and boarding information are read from the boarding information storage unit 512, and the ticket usage as shown in FIG. The history is displayed.

  In the management server device 100, when the ticket identification information and the boarding information are received from the taxi terminal 501, the boarding information receiving unit 124 identifies the taxi ticket used, and information on the taxi ticket stored in the ticket information storage unit 115 is stored. Change to used. Further, the billing information generating unit 125 generates billing information associated with the identification information of the taxi ticket used and the boarding information such as the boarding place, the getting-off place, the usage fee, and the taxi company. Also, it is determined whether or not the information (use date, etc.) that restricts the use of the ticket set by the contractor 300 for the taxi ticket and the actual use contents (use date, etc.) match / disagree. Saved in the billing information storage unit 117. Further, the information is transmitted to the portable terminal 401. When the portable terminal 401 receives these pieces of information, the taxi ticket stored in the ticket information storage unit 411 is changed to used, and the ticket information and the boarding information are associated with the boarding information storage unit 412. Saved.

  FIG. 9 shows an example of a screen when the taxi ticket issuer 200 logs in to the management server device 100 with his / her issuer ID and password and inquires for ticket information. On this screen, the issuer 200 can confirm the taxi ticket issued by the contractor 300, bill the usage fee to the contractor 300, and the like. The search condition input field is arranged at the top of this screen, and the ticket number, contractor name, event name, user name, ticket ticket type, taxi company, usage status, usage date, and usage date are used as search items. be able to. Of course, among all these items, the search condition may be input only for the necessary items, and the search may be executed for all the items.

  In the example of FIG. 9, in the search item, the first digit of the ticket identification number is 1 (all "*" is entered except for the highest digit), and the contractor name is A Co., Ltd. , And when the usage date is set between October 1, 2017 and May 31, 2018, as a search condition. The search results are listed at the bottom of the screen. The issuer 200 can output a list display of tickets as a search result in a predetermined file format (for example, csv format) by pressing an “output” button displayed at the bottom of the screen. The output file can be suitably used for creating a bill for a contractor, for example. When the issuer 200 instructs the usage fee to be charged by a predetermined operation, the billing information generation unit 125 calculates the total amount of the usage fee included in the output file and charges the contractor 300 for the fee. . Furthermore, by pressing the “verification” button, the billing information generation unit 125 can display the determination result regarding the match / mismatch between the information for restricting the use of the taxi ticket and the use contents. Here, the usage fee is charged to the contractor 300 based on the operation by the issuer 200, but the usage fee is automatically charged to each contractor 300 at a predetermined cycle (for example, every month). It is also possible to adopt a billing configuration.

  The example of FIG. 9 is a screen displayed when the issuer 200 searches for a taxi ticket, but the contractor 300 can also check the taxi ticket issued by himself / herself. However, in that case, the name of the contractor 300 is fixedly input in the contractor name column in the screen example of FIG.

  In the above description, the two-dimensional code displayed on the portable terminal 401 of the user 400 is photographed by the information reading unit 530 of the taxi terminal 501 provided in the taxi 500. There may be a case where is not provided. In that case, information for identifying the taxi 500 is read by the information reading unit 430 of the portable terminal 401 of the user 400. For example, a printed two-dimensional code on which taxi identification information including a taxi company and a vehicle number is printed is pasted on the back side of the passenger seat of the taxi 500, and the information reading unit 430 of the portable terminal 401 (this The two-dimensional code is read by a camera in the example. Thereby, taxi identification information is acquired. Alternatively, an IC tag in which taxi identification information including a taxi company and a vehicle number is recorded at a predetermined position in the taxi 500, and the IC is read by the information reading unit 430 (a short-range wireless communication unit in this example) of the portable terminal 401. It is also possible to adopt a configuration such as obtaining taxi identification information recorded on a tag. When the taxi identification information is acquired by such a method, the screen shown in FIG. 7F is displayed on the display unit 460 by the boarding information transmission unit 444 of the portable terminal 401. In this aspect, the position information acquisition unit 420 of the portable terminal 401 acquires the position information of the boarding place and the getting-off place. After getting in the taxi 500 and arriving at the destination, when the amount determined by the taximeter is entered and the “OK” button is pressed, the boarding information transmission unit 444 sends the ticket identification information and boarding information to the management server device 100. Sent.

  In the above embodiment, the case where the taxi 500 is driven by the driver has been described. However, the electronic taxi ticket issuance management system according to the present invention can also be used in the taxi 500 that is automatically driven. One modified example that can be suitably used when using a taxi 500 that is automatically operated will be described. Also in this modified example, since the flow until the taxi ticket issuance and the user 400 requests the dispatch is the same as that in the above embodiment, the description is omitted.

  In the modified example, the procedure regarding the use of the taxi ticket is displayed on the display unit 560 of the taxi terminal 501 provided in the taxi 500. After boarding the taxi 500, the user 400 causes the display unit 460 of his portable terminal 401 to display a screen including the two-dimensional code described with reference to FIG. Hold it over a predetermined position on the display unit 560 of the taxi terminal 501 provided. Subsequently, when the user 400 performs a predetermined operation such as pressing a “shoot” button displayed on the display unit 560 of the taxi terminal 501, the information reading unit 530 (camera in this example) of the taxi terminal 501 performs two-dimensional operation. The code is photographed. Subsequently, the taxi ticket information is extracted from the two-dimensional code by the boarding information transmission unit 542, and the information is displayed on the display unit 560 of the taxi terminal 501 (see FIG. 8C). Here, the example in which the information reading unit 530 is used as a camera to capture a two-dimensional code has been described. However, the information reading units 430 and 530 each use a short-range wireless communication unit, and transmit and receive taxi ticket information between them. It is also possible to adopt such a configuration. The user 400 confirms the detailed information of the displayed taxi ticket (the event name, the maximum amount, the date of use, etc.), confirms that the taxi ticket is correct, and presses the “confirm” button on the display unit 560. When the operation is performed, the taxi ticket is used. If the taxi ticket includes information on the place of getting off in advance, the taxi 500 starts to be driven automatically based on the information.

  On the other hand, when the taxi ticket does not include information on the alighting location, a map centering on the current location and a column for inputting the destination are displayed on the display unit 560. The user 400 determines the getting-off place by scrolling the map or the like, or specifying the getting-off place on the map, or inputting the name or address of the destination. In addition, when there is a waypoint, it is also possible to additionally input information about the waypoint. When the user inputs information about the alighting place, the taxi 500 starts to operate automatically.

  When the user gets on the taxi 500 and arrives at the destination, the screen described with reference to FIG. 8D is displayed on the display unit 560 of the taxi terminal 501. In the above embodiment, the driver inputs the usage fee, but in the case of automatic driving, the amount of usage fee read from the taximeter is displayed. At this time, the boarding information transmission unit 542 operates the position information acquisition unit 520 to acquire the current position of the taxi 500. And the point (boarding place) and the alighting place where the user 400 got on the taxi 500 are displayed on the display unit 560. When the user 400 confirms the boarding location, the getting-off location, and the usage amount displayed on the display unit 560 and presses the “OK” button, the taxi ticket identification information, the boarding date and time, the boarding location, the getting-off location, and The boarding information including the usage amount information is transmitted to the management server device 100. That is, in this modification, the user 400 is caused to perform a part of the operation performed by the driver of the taxi 500 in the above embodiment. Subsequent processing is the same as that in the above embodiment, and thus description thereof is omitted.

  In the above embodiment, the portable terminal 401 of the user 400 requests the management server device 100 to dispatch the vehicle, and the management server device 100 requests the taxi company 600 to dispatch the vehicle. It is also possible to install a taxi dispatch application on the portable terminal 401 and request the dispatch by the taxi dispatch application. Such modifications will be described below.

  In this modification, when the user ID is input by the contractor 300, in addition to the URL and password for downloading the user application from the management server device 100 to the mail address input as the user ID. An e-mail that includes a URL for downloading the taxi dispatch application is also transmitted. As the taxi dispatch application, for example, an application provided by a taxi company 600 that is in business partnership with a taxi ticket issuer 200 is used.

  The user 400 accesses the URL received by the portable terminal 401 owned by the user 400, downloads the user application and the taxi dispatching application, and installs it.

  When the user 400 presses the “call a taxi” button on the menu screen described with reference to FIG. 7B, the taxi dispatch application is activated, and the user 400 instructs the taxi company 600 according to the instructions of the taxi dispatch application. Request a dispatch. In other words, in this modified example, the user application and the taxi dispatch application are linked, and the taxi company 600 is directly requested for dispatch without going through the management server device 100. Since each function of the taxi dispatch application is the same as that conventionally used, the description thereof is omitted. Further, since the processes other than taxi dispatch in this modification are the same as those in the above embodiment, the description thereof is omitted. Naturally, in addition to the above-described embodiments and modifications, the user 400 can request the taxi company 600 to dispatch a car using the taxi dispatching application separately from the taxi ticket issuing management system according to the present invention.

  In the above embodiment, the case where a taxi ticket is provided to an invitee to an event or the like held by the contractor has been described as an example. However, the electronic taxi ticket issuance management system according to the present invention is the It can be used for various purposes, such as when requesting a business trip to another place, or when a travel agency as a contractor uses a taxi as a travel means for travel participants. For example, if the contractor is a travel agency and the user is a participant in a trip sponsored by the travel agency, the issued taxi ticket can be used not only for taxi use but also for accommodation at a predetermined hotel. It can be configured to be usable for eating and drinking at a restaurant or purchasing goods at a souvenir shop. In this case, a terminal similar to the taxi terminal 501 described in the above embodiment is provided in a predetermined hotel, restaurant, or souvenir shop. Then, salesclerks at various places use the terminal to obtain the taxi ticket information by photographing the two-dimensional code in the same manner as in the above embodiment, and use the accommodation information corresponding to the boarding information after using the ticket. Information may be transmitted to the boarding information reception unit 124. However, the terminal provided in the hotel or the like does not have to have the function of the position information acquisition unit. In addition, the usage information preferably includes the use contents of the ticket, such as the name of the purchased product, instead of including the information on the position where the ticket was used. Here, as described above, it is also possible to adopt a method such as short-range wireless communication in addition to photographing a two-dimensional code.

DESCRIPTION OF SYMBOLS 100 ... Management server apparatus 110 ... Memory | storage part 111 ... Issuer information memory | storage part 112 ... Contractor information memory | storage part 113 ... User information memory | storage part 114 ... Event information memory | storage part 115 ... Ticket information memory | storage part 116 ... Boarding information memory | storage part 117 ... Billing information storage unit 120 ... Management server device program 121 ... Issuer input reception unit 122 ... Contractor input reception unit 123 ... Vehicle allocation reception unit 124 ... Boarding information reception unit 125 ... Billing information generation unit 130 ... Input unit 140 ... Display unit DESCRIPTION OF SYMBOLS 200 ... Issuer 300 ... Contractor 400 ... User 401 ... Portable terminal 410 ... Storage part 411 ... Ticket information storage part 412 ... Boarding information storage part 420 ... Position information acquisition part 430 ... Information reading part 440 ... User application 441 ... event reception part 442 ... dispatch request part 443 ... ticket presentation part 444 ... boarding information transmission part 4 DESCRIPTION OF SYMBOLS 0 ... Input part 460 ... Display part 500 ... Taxi 501 ... Taxi terminal 510 ... Memory | storage part 511 ... Ticket information memory | storage part 512 ... Boarding information memory | storage part 520 ... Position information acquisition part 530 ... Information reading part 540 ... Application for taxi terminals 541 ... Dispatching reception part 542 ... Riding information transmission part 550 ... Input part 560 ... Display part 600 ... Taxi company

Claims (10)

The issuer to issue a taxi ticket, subscribers who signed a contract for the use of emitting ascetic and the taxi ticket, a user who uses a taxi using the taxi ticket provided by the contractor, to navigate the及beauty taxis An electronic taxi ticket issuance management system used by taxi operators,
a) a storage unit for storing information;
b) is input by the issuer, the issuer input receiving unit for transmitting subscriber information on the subscriber in the storage unit,
c) authenticating the input person on the basis of the subscriber information is input by the authenticated inputting person, user information about the portable terminal having the user and the user of the taxi ticket, and the use of the taxi ticket together based on the use restriction information is limited to information to generate the ticket identification information of the taxi ticket transmitted to the storage unit, a subscriber input receiving unit for transmitting the ticket identification information to the movable portable terminal,
d) Collect the ticket identification information, boarding information including at least either the spending of getting-off locations及beauty boarding locations taxis that are utilized with cab ticket having the ticket identification information, associates them A boarding information reception unit to be transmitted to the storage unit,
according to an instruction from e) the issuer, an electronic taxi ticket issuing, characterized in that it comprises a billing information generator that generates a billing information using the ticket identification information and the boarding information stored in the storage unit Management system. further,
2. The vehicle dispatching unit according to claim 1, further comprising: a vehicle dispatching reception unit that receives a vehicle dispatch request together with location information of the portable terminal after the authentication of the user information and instructs a taxi to dispatch a vehicle based on the location information. Electronic taxi ticket issuance management system. The electronic taxi ticket issuance management system according to claim 1, wherein the billing information generation unit bills the contractor based on the billing information for a taxi usage fee. The contractor input accepting unit accepts input of usage restriction information for further restricting the use of a taxi ticket,
The electronic taxi ticket issuance according to any one of claims 1 to 3, wherein the billing information generation unit collates the boarding information with the use restriction information and determines whether or not they match. Management system. The contractor input reception unit
Transmitting the user information to the storage unit;
The taxi ticket identification information is generated and transmitted to the portable terminal of the selected user for the user selected from the users stored in the storage unit. 4. The electronic taxi ticket issuance management system according to any one of 4 above. The contractor input reception unit
Accepts event information, which is information related to the event, and invitee information related to the invitee to the event, asks the portable terminal of the invitee whether to participate / not participate in the event, and answers from each invitee The electronic taxi ticket issuance management system according to claim 1, wherein the electronic taxi ticket issuance management system is transmitted to the storage unit. The contractor input reception unit
The electronic taxi ticket issuance management system according to claim 6, wherein the ticket identification information is transmitted to the portable terminal of an inviter who has obtained an answer to participation in an event. A program for a user installed in the portable terminal in the electronic taxi ticket issuing management system according to any one of claims 1 to 7,
A program for a user, which causes the ticket identification information transmitted from the contractor input reception unit to be presented in a predetermined format. The electronic taxi ticket issuance management system according to any one of claims 1 to 7, wherein the taxi terminal provided in the taxi is used together with the portable terminal in which the user program according to claim 8 is installed. A taxi terminal program to be installed,
The taxi terminal having an information reading unit,
Read the ticket identification information presented in the predetermined format by the information reading unit,
Accept input of usage charges,
A taxi terminal program that functions as a boarding information transmission unit that transmits the boarding information to the boarding information reception unit. A program for a user installed in the portable terminal in the electronic taxi ticket issuing management system according to any one of claims 1 to 7,
The taxi identification information is presented to the taxi in a predetermined format,
The portable terminal provided with an information reading unit,
Read the taxi identification information presented in the predetermined format by the information reading unit,
Accept input of usage charges,
A program for a user that causes the boarding information to function as a boarding information transmission unit that transmits the boarding information to the boarding information reception unit.

Images