JP6937529B1 - Taxi dispatch system, taxi dispatch management device, taxi vehicle side terminal, taxi dispatch method, taxi dispatch management program, computer-recordable medium, and stored equipment - Google Patents

Abstract

PROBLEM TO BE SOLVED: To improve the convenience of a user with a simple configuration and reduce the possibility that a taxi company cannot collect a taxi fare, a taxi dispatch system, a taxi dispatch management device, a taxi vehicle side terminal, a taxi dispatch method, a taxi. Provide a vehicle allocation management program, a computer-recordable medium, and a stored device. A taxi dispatch system 1000 includes a vehicle dispatch management device 100 and a vehicle-side terminal 200. The vehicle allocation management device 100 includes a customer database 10 that stores customer data 110 including registration information 120 and usage information 130, a management side communication unit 20, a management side control unit 30 that performs credit based on the customer data 110, and a management side control unit 30. A vehicle allocation request generation unit 40 for generating a vehicle allocation request is provided. Further, the vehicle-side terminal 200 acquires the vehicle-side communication unit 210, the vehicle allocation acceptance unit 220 that responds to accept the vehicle allocation request, and the customer data 110, and accepts the customer's authentication when the customer gets on board. A side authentication unit 230 is provided. [Selection diagram] Fig. 1

Description

The present invention relates to a taxi dispatch system, a taxi dispatch management device, a taxi vehicle side terminal, a taxi dispatch method, a taxi dispatch management program, a computer-recordable medium, and a stored device.

In recent years, mainly in urban areas, by requesting a taxi dispatch via a so-called taxi dispatch app and making a payment with a credit card registered in the app, it is easy to eliminate the troublesome cash exchange when getting off the taxi. Taxi dispatch system is becoming widespread. However, since such a system is mainly used by downloading a dedicated vehicle dispatch application to a smartphone in advance, it is used by elderly people who do not have a smartphone or who are unfamiliar with handling even if they have a smartphone. It was difficult to use. In particular, there are many elderly people who use taxis in rural areas, and the reality is that most of them make a request for dispatch by telephone and pay in cash.

In addition, depopulation is progressing in each region of Japan, and there are many regions where public transportation is significantly reduced or disappeared due to the abolition or consolidation of railways and bus routes due to the decrease in users. Under these circumstances, taxis as a means of transportation available to the elderly left in rural areas are said to be the last fort. However, since taxi fares are higher than trains and buses, many elderly people hesitate to use taxis frequently in their daily lives, such as going to hospitals and shopping.

On the other hand, when paying without downloading an application for vehicle dispatch, which is a high hurdle for the elderly, mere credit card payment separated from the taxi dispatch system, Suica (registered trademark, the same applies hereinafter), Line Pay (registered trademark) ) Etc. can also be used. In this case, since the customer makes a payment when getting off the taxi, for example, if the credit card has expired or the smartphone has expired and the electronic money application cannot be used, the pre-charged amount is insufficient. There is a risk that this may occur. In some cases, the taxi fare may not be collected.

Patent Document 1 discloses a taxi wireless system capable of paying a taxi fare by a method different from the conventional payment method using cash, credit card, or electronic money. A customer master as shown in FIG. 7 is stored in the CTI server in this system, and when the fare is postpaid, the postpaid information is transmitted to the mobile station together with the vehicle allocation instruction information. Then, after the mobile station carries the customer and travels to the destination, the usage fee information is transmitted to the CTI server. After that, the CTI server withdraws the usage fee based on the customer's credit card information registered in the customer master. Alternatively, the CTI server charges the customer for the usage fee by a known method such as sending an invoice, and receives the usage fee from the customer by a known method such as bank transfer.

However, even in a system such as Patent Document 1, the fee is settled after the customer uses the mobile station, and the registered customer's credit card information is incorrect, the credit card has expired, or the customer's credit card has expired. We cannot deny the possibility of troubles such as being unable to charge the usage fee because we do not know where we are. Further, the method of accurately authenticating the customer registered in the customer master and the customer who actually uses the mobile station is not disclosed, and there is a possibility that a customer different from the registered customer may be mistakenly placed.

Japanese Patent No. 5823190

The present invention has been made in view of such a background, and one of the purposes thereof is to improve the convenience of the user with a simple configuration and reduce the risk that the taxi company will not be able to collect the boarding fee. It is an object of the present invention to provide a taxi dispatch system, a taxi dispatch management device, a taxi vehicle side terminal, a taxi dispatch method, a taxi dispatch management program, a computer-recordable medium, and a stored device.

Means for Solving Problems and Effects of Invention

According to the taxi dispatch system according to the first aspect of the present invention, a vehicle allocation management device installed in a taxi company and a vehicle-side terminal installed in one or more taxi vehicles communicating with the vehicle allocation management device. A taxi dispatch system to be provided, wherein the vehicle dispatch management device stores customer data including registration information for authentication including a name registered in advance for each customer and tax usage information for each customer. A customer database, a management-side communication unit for communicating with the outside, a management-side control unit for crediting whether taxi can be dispatched based on the customer data obtained from the customer database, and the above-mentioned When receiving a vehicle allocation request from a customer registered in the customer database, if the credit result of crediting the customer is OK, the destination of the customer is determined. A vehicle allocation request generation unit that generates a vehicle allocation request including the vehicle allocation request, and the vehicle side terminal includes a vehicle side communication unit for communicating with the vehicle allocation management device and the vehicle allocation request generated by the vehicle allocation request generation unit. When the vehicle side communication unit receives the data via the management side communication unit, the vehicle allocation acceptance unit that responds to the effect that the vehicle allocation request is accepted and the customer data are transmitted to the vehicle allocation management via the vehicle side communication unit. acquired from the device, while riding in the customer, and a vehicle-side authentication unit that receives authentication of the customer, the customer database, as the customer data, together with the payment history, beating taxi crew from the customer in the past It is possible to register the received case and the case where the customer who requested the vehicle dispatch did not appear at the designated boarding place, and the management side control unit can register the payment history recorded in the customer data and the case of being violent. Credit is given by a comprehensive evaluation of the weighting of the registered items to be included, and if the customer database contains violent acts, the credit result can be configured to be NG. With the above configuration, highly reliable credit can be provided when requesting a vehicle dispatch based on the unique data accumulated by the taxi company. As a result, it is possible to avoid the occurrence of troubles when using a taxi, and it is possible to reduce the risk that the taxi fare cannot be collected. In addition, it is possible to easily and accurately authenticate the customer when boarding the taxi, and it is possible to improve the convenience of the customer when using the taxi. Further, in the above configuration, for example, by registering the presence or absence of past escapes and the existence or nonexistence of unpaid taxi fare, it is possible to effectively determine whether or not to receive a vehicle allocation request.
Further, according to the taxi dispatch system according to the second aspect of the present invention, in the above configuration, the credit result can be configured not to be NG only because the previous boarding fee is still unpaid.

Further, according to the taxi dispatch system according to the third aspect of the present invention, in addition to the above configuration, the vehicle-side authentication unit reads and reads the customer-provided authentication data presented by the customer to authenticate the customer. A unit and a collating unit that collates the customer data acquired from the vehicle allocation management device via the vehicle-side communication unit with the customer-provided authentication data acquired by the reading unit can be provided. With the above configuration, customer authentication can be performed by collating the customer data registered in advance with the customer-provided authentication data, so that the accuracy of customer authentication can be further ensured.

Furthermore, according to the taxi dispatch system according to the fourth embodiment of the present invention, in addition to any one of the configurations described above, wherein the customer-authentication data, is previously assigned to a customer, QR code (registered holding while riding Trademarks, the same shall apply hereinafter) can be included. With the above configuration, it is possible to easily and accurately confirm whether the registered customer and the customer to be used match by distributing a widely used QR code in advance.

Furthermore, according to the taxi dispatch system according to the fourth aspect of the present invention, in addition to any of the above configurations, the customer data includes pre-registered customer face image data, and the reading unit. However, the customer-provided authentication data includes an image pickup unit that captures a customer's face photograph at the time of boarding, and the collation unit captures the face image data acquired from the vehicle allocation management device and the rider imaged by the image pickup unit. Authentication can be performed by collating with the customer's face photo at the time of. With the above configuration, it is possible to easily and accurately confirm whether or not the registered customer and the customer to be used match by face recognition.

Furthermore, according to the taxi dispatch system according to the sixth aspect of the present invention, in addition to any of the above configurations, the management side communication unit can communicate with an external credit institution. With the above configuration, the taxi company can perform credit by communicating with an external credit institution, for example, the credit system of the credit company, in addition to the credit performed in the taxi dispatch system, and has an advantage of increasing the reliability of the credit.

Furthermore, according to the taxi dispatch system according to the seventh aspect of the present invention, in addition to any of the above configurations, the vehicle allocation management device further receives a customer registration or vehicle allocation request received by the management side communication unit. In response to a call, a microphone and a speaker for having a conversation, an operation unit for inputting or selecting customer information acquired by an operator who performs a vehicle dispatching business by talking with a customer through the microphone and the speaker, and the like. Based on the acquired information, a management side display unit for displaying the customer data can be provided. With the above configuration, customer registration and taxi dispatch requests can be made not only through smartphones and dedicated applications, but also through operators, making the system easy to use even for elderly people who are unfamiliar with handling smartphones. can.

Furthermore, according to the taxi dispatch system according to the eighth aspect of the present invention, in addition to any of the above configurations, the customer database includes payment information regarding a payment method for taxi usage charges as the customer data. Therefore, the vehicle-side terminal can be configured to settle the boarding fee with the customer based on the payment information registered in the customer database when the customer gets off. With the above configuration, taxi fare can be settled by a pre-registered payment method, which saves the troublesome payment process when getting off, improves customer convenience, and also allows taxi drivers to settle payments. It saves labor and leads to improvement of work efficiency.

Furthermore, according to the taxi dispatch system according to the ninth aspect of the present invention, in addition to any of the above configurations, the customer database is an application for registration by a person different from the customer who uses the taxi as the customer data. Can be accepted. In the above configuration, the registration of customer data is often performed mainly via a smartphone, a PC, a dedicated application, or the like. At this time, in particular, many elderly people do not have a smartphone or the like, or even if they do have one, they are unfamiliar with handling, and there is a high possibility that it is difficult to register customer data. Therefore, the difficulty of registration can be reduced by registering by a relative such as a family member instead of such an elderly person.

Furthermore, according to the taxi dispatch system according to the tenth aspect of the present invention, in addition to any of the above configurations, the customer database uses the customer data as the customer data to pay the ride fee with the customer who uses the taxi. It is possible to make it possible to register by making it different from the person who does it. With the above configuration, the fare can be paid to, for example, the family of a customer who uses a taxi. Specifically, by paying the taxi fare for parents living in rural areas where transportation is scarce, it is possible to facilitate parents' hospital visits, shopping, etc., and support their lives. can.

Furthermore, according to the vehicle allocation management device according to the eleventh embodiment of the present invention, the vehicle allocation management device is installed in a taxi company and communicates with vehicle-side terminals installed in one or more taxi vehicles in advance. A customer database for storing customer data including registration information for authentication including the name of each registered customer and taxi usage information for each customer, a management side communication unit for communicating with the outside, and a communication unit on the management side. When receiving a vehicle allocation request from a management side control unit for crediting whether a taxi can be dispatched based on the customer data obtained from the customer database and a customer registered in the customer database. Is it possible to dispatch a vehicle to the customer? When the credit result of crediting by the management side control unit is OK, the vehicle allocation request generation unit that generates a vehicle allocation request including the destination of the customer is provided. The vehicle allocation request generated by the vehicle allocation request generation unit is transmitted to the taxi vehicle side, and the customer data subject to the vehicle allocation request is transmitted to the taxi vehicle side to which the vehicle allocation request is accepted, and the taxi vehicle is concerned. The customer is configured to be able to authenticate the customer when the customer is boarded, and the customer database includes payment history as the customer data, a case where a taxi crew member has been assaulted by the customer in the past, and a vehicle dispatch request. It is possible to register the case where the customer who did not appear at the designated boarding place, and the management side control unit weights the registration items including the payment history recorded in the customer data and the case of being violated. Credit is given by comprehensive evaluation, and if the customer database contains violent acts, the credit result can be configured to be NG. With the above configuration, highly reliable credit can be provided when requesting a vehicle dispatch based on the unique data accumulated by the taxi company. As a result, it is possible to reduce the risk that the taxi fare cannot be collected.

Furthermore, according to the vehicle-side terminal according to the twelfth aspect of the present invention, it is a vehicle-side terminal installed in a taxi vehicle that communicates with a vehicle allocation management device installed in a taxi company, and is the vehicle allocation management device. When the vehicle-side communication unit for communicating with the vehicle and the vehicle allocation request generated by the vehicle allocation request generation unit of the vehicle allocation management device are received by the vehicle-side communication unit via the management-side communication unit, the vehicle allocation request is accepted. It is provided with a vehicle allocation acceptance unit that responds to the effect, and a vehicle-side authentication unit that acquires customer data from the vehicle allocation management device via the vehicle-side communication unit and accepts the customer's authentication when the customer gets on board. Since the customer data is credited by a comprehensive evaluation of the weighting of registered items, the payment history and the boarding location specified by the customer who has requested the taxi to be dispatched or the taxi crew has been beaten by the customer in the past. Can include information as to whether it has never appeared in. With the above configuration, it is possible to easily and accurately authenticate the customer when boarding the taxi, and it is possible to improve the convenience of the customer when using the taxi.

Furthermore, according to the vehicle-side terminal according to the thirteenth aspect of the present invention, in addition to the above configuration, the vehicle-side authentication unit reads the customer-provided authentication data presented by the customer for authenticating the customer. A reading unit, a collating unit that collates the customer data acquired from the vehicle allocation management device via the vehicle-side communication unit, and the customer-provided authentication data acquired by the reading unit can be provided. With the above configuration, customer authentication can be performed by collating the customer data registered in advance with the customer-provided authentication data, so that the accuracy of customer authentication can be further ensured.

Furthermore, according to the taxi dispatch method according to the fourteenth aspect of the present invention, the vehicle allocation management device installed in the taxi company communicates with the vehicle side terminals installed in each of one or more taxi vehicles, and the taxi In a taxi dispatch method for dispatching a vehicle, the management side control unit of the vehicle allocation management device manages customer data including registration information for authentication including a name for each customer and tax usage information for each customer. The process of prompting the customer to register in the customer database via the display unit, the process of receiving the vehicle allocation request from any of the customers registered in the customer database by the management side control unit, and the process of receiving the vehicle allocation request to the customer. On the other hand, the payment history included in the customer database and whether the taxi crew has been beaten by the customer in the past or the customer who requested the dispatch has not appeared at the designated boarding place. Based on the information included, the management side control unit performs credit by comprehensive evaluation of weighting of registered items, and if the customer database contains violent acts, the process of dismissing the credit result and the customer. Based on the credit result of whether the taxi can be dispatched using the customer data obtained from the database, the management side control unit rejects the vehicle dispatch request when the credit result is NG, and the credit result is OK. In the case of, the process of accepting the vehicle allocation request, the process of generating the vehicle allocation request including the destination of the customer who accepted the vehicle allocation request, and the process of transmitting the vehicle allocation request to the vehicle side terminal by the management side communication unit. A process in which the vehicle allocation acceptance unit prompts the vehicle-side terminal that receives the vehicle allocation request by the vehicle-side communication unit to respond whether or not to accept the vehicle allocation request, and the customer data when the vehicle allocation request is accepted. Is obtained from the vehicle allocation management device via the vehicle-side communication unit, and when the customer gets on board, the vehicle-side authentication unit authenticates the data by comparing it with the information provided by the customer. can. With the above configuration, highly reliable credit can be provided when requesting a vehicle dispatch based on the unique data accumulated by the taxi company. As a result, it is possible to avoid the occurrence of troubles when using a taxi, and it is possible to reduce the risk that the taxi fare cannot be collected. In addition, it is possible to easily and accurately authenticate the customer when boarding the taxi, and it is possible to improve the convenience of the customer when using the taxi.

Furthermore, according to the taxi dispatch method according to the fifteenth aspect of the present invention, in addition to the above configuration, the step of registering the customer data in the customer database includes registration of payment information regarding the payment method of the taxi usage fee. , the taxi dispatch method, further, after the authentication of the customer, a taxi vehicle to transfer the customer to the destination, at the time of drop-off, between the customer, the payment information that has been registered in the customer database based on the step of the vehicle-side terminals perform settlement of fare, can contain. With the above configuration, taxi fare can be settled by a pre-registered payment method, which saves the troublesome payment process when getting off, improves customer convenience, and also allows taxi drivers to settle payments. It saves labor and leads to improvement of work efficiency.

Furthermore, according to the vehicle allocation management program according to the sixteenth aspect of the present invention, it is a vehicle allocation management program installed in a taxi company and communicating with vehicle-side terminals installed in one or more taxi vehicles, respectively, and is a customer. A function to register customer data including registration information for authentication including each name and taxi usage information for each customer in the customer database, and a vehicle dispatch request from any of the customers registered in the customer database. The function to accept, the payment history obtained from the customer database for the customer who received the vehicle dispatch request, and the customer who has been beaten by the taxi crew in the past or who requested the vehicle dispatch is specified. Based on the customer data including information on whether it has never appeared at the boarding place, credit is given whether taxi can be dispatched by comprehensive evaluation of weighting of registered items, and violent acts are found in the customer database. If it is included, a function to make the credit result NG, and a function to reject the vehicle allocation request if the credit result is NG and accept the vehicle allocation request if the credit result is OK based on the credit result. A function of generating a vehicle allocation request including the destination of the customer who accepted the vehicle allocation request and transmitting the vehicle allocation request to the vehicle side terminal by the management side communication unit and a vehicle side terminal receiving the vehicle allocation request by the vehicle side communication unit. To the function of receiving a response as to whether or not to accept the vehicle allocation request, and to the taxi vehicle side to which the vehicle allocation request has been accepted, the customer data of the customer who is the target of the vehicle allocation request is transmitted to the taxi. On the vehicle side, when the customer gets on board, the computer can execute a function of authenticating the customer.

Furthermore, a computer-readable recording medium or storage device that records the program according to the seventeenth embodiment can store the taxi dispatch program. Recording media include CD-ROM, CD-R, CD-RW, flexible disc, magnetic tape, MO, DVD-ROM, DVD-RAM, DVD-R, DVD + R, DVD-RW, DVD + RW, Blu-ray, HD. A medium capable of storing a magnetic disk such as a DVD (AOD), an optical disk, a magneto-optical disk, a semiconductor memory, or other programs is included. Further, the program includes a program stored in the above-mentioned recording medium and distributed, and a program distributed by download through a network line such as the Internet. Further, the stored device includes a general-purpose or dedicated device in which the above program is implemented in a state in which it can be executed in the form of software, firmware, or the like. Furthermore, each process and function included in the program may be executed by program software that can be executed by a computer, and each part of the process may be executed by hardware such as a predetermined gate array (FPGA, ASIC), or program software. It may be realized in a form in which and a partial hardware module that realizes a part of the hardware are mixed.

It is a block diagram which shows the taxi dispatch system which concerns on Embodiment 1 of this invention. It is an image diagram which shows an example of the customer data stored in a customer database. It is an image diagram which shows an example of the registration information included in the customer data. It is an image diagram which shows an example of the usage information included in the customer data. It is an image diagram which shows an example of the vehicle allocation acceptance screen displayed on the vehicle side display part. It is a block diagram which shows the taxi dispatch system which concerns on Embodiment 2 of this invention. It is a figure which shows the conventional customer master.

Hereinafter, embodiments of the present invention will be described with reference to the drawings. However, the embodiments shown below exemplify a taxi dispatching device for embodying the technical idea of the present invention, and the present invention does not specify the taxi dispatching device to the following. Further, the present specification does not specify the members shown in the claims as the members of the embodiment. In particular, the dimensions, materials, shapes, relative arrangements, etc. of the components described in the embodiments are not intended to limit the scope of the present invention to the specific description, and are merely explanatory examples. It's just that. The size and positional relationship of the members shown in each drawing may be exaggerated to clarify the explanation. Further, in the following description, members having the same or the same quality are shown with the same name and reference numeral, and detailed description thereof will be omitted as appropriate. Further, each element constituting the present invention may be configured such that a plurality of elements are composed of the same member and the plurality of elements are combined with one member, or conversely, the function of one member is performed by the plurality of members. It can also be shared and realized.
[Embodiment 1]

Hereinafter, the taxi dispatch system 1000 according to the first embodiment of the present invention is shown in the block diagram of FIG. The taxi dispatch system 1000 shown in this figure includes a vehicle allocation management device 100 installed in a taxi company and vehicle-side terminals 200 installed in one or more taxi vehicle TXIs that communicate with the vehicle allocation management device 100. The taxi dispatch system 1000 provides credit based on the customer data 110 held by the taxi company, and for a customer whose credit result is OK, the taxi vehicle TXI receives a request for dispatch from the customer. This is a system for allocating a taxi and certifying the customer on the taxi vehicle side when the customer CST gets on the taxi.

Further, the taxi dispatch system 1000 can also register the payment information 120a regarding the payment method of the taxi usage fee in the customer database 10 in advance. By doing so, when the customer CST uses a taxi, the customer is authenticated when getting on the taxi vehicle TXI, and after moving to the destination, when getting off, the customer is registered in the customer database 10 with the customer. The boarding fee can be settled based on the settlement information 120a. As a result, the taxi fare can be settled by the pre-registered payment method, and it is possible to save the troublesome settlement time when getting off the taxi, which improves the convenience of the customer. For example, by designating credit card payment as the payment method and registering the credit card number in the customer database 10 in advance, the customer does not have to submit a credit card or enter a signature or PIN when getting off. , A usage environment that seems to be payment-less is realized. In addition, the taxi driver DRV also saves labor in the settlement work, which leads to improvement in work efficiency.

Specifically, the customer data 110 includes registration information 120 for authentication of the customer CST and usage information 130 indicating the status of taxi use by the customer CST. The taxi customer CST registers the registration information 120 in advance via a vehicle dispatch application, a telephone, or the like. The taxi company side accumulates usage information 130 for each customer registered in this way. The customer data 110 including the registration information 120 and the usage information 130 is stored in the customer database 10. Then, when a vehicle dispatch request is received from any of the registered customer CSTs, is it possible to dispatch a taxi to the customer CST who received the vehicle dispatch request based on the customer data 110 obtained from the customer database 10. Credit. If the credit result is OK, the vehicle allocation request is accepted, a vehicle allocation request including the destination of the customer who has accepted the vehicle allocation request is generated, and the vehicle allocation request is transmitted to the vehicle side terminal 200. The vehicle-side terminal 200 that has received the vehicle allocation request responds as to whether or not to accept the vehicle allocation request. Then, when the vehicle allocation request is accepted, the customer data 110 is acquired from the vehicle allocation management device 100, and when the customer gets on board, authentication is performed by comparing with the information provided by the customer.

When the taxi dispatch system 1000 also includes the settlement process, the customer data 110 registered in the customer database 10 includes the settlement information 120a as the registration information 120. The payment information 120a is information regarding the payment method selected by the customer. For example, in the case of credit card payment, information such as the credit card company name, credit card number, holder, and expiration date can be mentioned. In addition, David card payment, bank account debit, total mobile phone charges, Osaifu-Keitai (registered trademark) such as Edy (registered trademark) and Suica , QR code payment such as PayPay (registered trademark) and AU Pay (registered trademark) For example , an existing payment method can be specified, and information corresponding to each specified payment method is registered in advance as payment information 120a. Then, when the customer uses a taxi, the customer is authenticated as described above when the taxi vehicle is boarded, and then the passenger is transported to the destination by the taxi vehicle. Then, when it arrives at the destination, the fare is settled with this customer. Here, the vehicle-side communication unit 210 of the vehicle-side terminal 200 performs data communication with the management-side communication unit 20 of the vehicle allocation management device 100 to acquire the payment information 120a registered in the customer database 10. Then, the fixed amount of the boarding fee is charged. For example, the amount will be deducted by the specified method. When the payment is confirmed, the taxi driver will open the automatic door by calling out to the customer, "The payment has been completed successfully. Thank you for using the service." , Drop the customer from the taxi. In this way, it is preferable that the taxi vehicle opens the door after confirming the payment. As a result, in the unlikely event that payment cannot be made, it is possible to explain to the customer to that effect. In other words, it is possible to avoid the situation where the customer leaves the taxi vehicle when the payment cannot be made. Of course, as with ordinary taxi vehicles, it is okay to open the automatic door before payment at the discretion of the taxi driver.

The settlement process itself may be performed on the vehicle side terminal 200 or on the vehicle allocation management device 100 side. For example, the vehicle-side terminal 200 can notify the vehicle allocation management device 100 of the amount of the boarding fee, and the vehicle allocation management device 100 can charge the amount according to the payment information 120a. In this case, the taxi driver can confirm that the payment has been completed successfully by notifying the vehicle side terminal 200 of the notification that the payment processing has been completed on the vehicle allocation management device 100 side, and opens the automatic door. , It becomes possible to perform the necessary operations.

Such a taxi dispatch system 1000 uses the unique data accumulated by the taxi company to provide credit to the taxi company when requesting a taxi, as compared with the case where only the credit of an external credit institution is used. By improving the accuracy of the taxi and ensuring that the taxi vehicle authenticates the customer when the taxi is boarded, the taxi company can identify the customer and reduce the risk of disagreement between the requester and the user. This is to improve the convenience of customers when using a taxi, while reducing the possibility that the fare will not be collected.
(Vehicle allocation management device 100)

The vehicle allocation management device 100 shown in FIG. 1 is typically installed in a taxi company. The vehicle allocation management device 100 includes a customer database 10 for storing customer data, a management side communication unit 20 for communicating with the outside, a management side control unit 30 for crediting whether a taxi can be dispatched, and a credit result. It is provided with a vehicle allocation request generation unit 40 that generates a vehicle allocation request when is OK.

Further, the vehicle allocation management device 100 may include a management side display unit 50 for displaying customer data 110, a management side operation unit 60 operated by the operator OP, a microphone MIC, and a speaker SPK. In this case, the operator ORG can request vehicle allocation, register customer data, and the like, and can make the system easy to use for customers who are not good at handling smartphones and the like.
(Customer database 10)

The customer database 10 is a member for storing customer data 110. As shown in FIG. 2, the customer data 110 includes registration information 120 for authentication including a name for each customer and taxi usage information 130 for each customer. The customer data 110 may further include a fare input field 160 for inputting a fare for a customer who has used a taxi, which will be described later.
(Registration information 120)

The customer CST registers the registration information 120 in advance via a vehicle dispatch application or a telephone. FIG. 3 shows one aspect of the registration information 120. In this example, an example in which the taxi user who is the customer CST and the registrant who performs the registration procedure are different will be described. The registration information 120 includes a user name column 121 for displaying the user's name, a user furigana column 121a for displaying the user's name, and a user address column 122 for displaying the user's address. The user telephone number column 123 that displays the user's telephone number, the user payment method column 124 that displays the user's payment method, and the user's face image data for authentication when using a taxi, which will be described later, are displayed. It is provided with a user face image data field 125.

The registration information 120 further includes a registrant name field 126 for displaying the registrant's name, a registrant's furigana field 126a for displaying the registrant's name, and a registrant address field 127 for displaying the registrant's address. It includes a registrant telephone number field 128 for displaying the registrant's telephone number and a registrant payment method field 129 for displaying the registrant's payment method. When the registrant pays the user's boarding fee with a credit card, for example, select "registrant payment" in the user payment method field 124, select the credit card in the registrant payment method field 129, and use the card. I try to enter the number. Here, as described above, when the taxi dispatch system 1000 also includes the settlement process, the user settlement method column 124 and the registrant settlement method column 129 become the settlement information 120a.

By registering in advance so that the user and the payer are different from each other in this way, the payment of the fare can be made to, for example, the family of the taxi user. Specifically, by paying the taxi fare for parents living in rural areas where transportation is scarce, it is possible to facilitate parents' hospital visits, shopping, etc., and support their lives. can.

Further, the registration of the registration information 120 is often performed mainly via a smartphone, a PC, a dedicated vehicle dispatch application, or the like. In particular, many elderly people do not have smartphones or the like, or even if they do, they are unfamiliar with handling, and there is a high possibility that it will be difficult to register the registration information 120. Therefore, it is possible to reduce the difficulty of registration by having a relative such as a family member register instead of such an elderly person as described above. That is, elderly people and the like who are users can use the taxi dispatch system 1000 without downloading a dedicated taxi dispatch application.

However, the taxi dispatch system 1000 of the present embodiment is not limited to a mode in which the user and the registrant are different persons and the registrant pays. If the user and the registrant are the same, the registration may be performed by omitting the input of the registrant's information. In addition, if the registrant performs the registration procedure but the user pays, the user payment method may be the user payment, or the input of the registrant information may be omitted.
(Usage information 130)

The usage information 130 is for showing the taxi usage status for each customer registered in the registration information 120. FIG. 4 shows one aspect of the usage information 130. In this example, the usage information 130 includes a vehicle allocation history 140 and a payment history 150. The vehicle allocation history 140 includes a usage date and time column 141 for displaying the date and time of use, a boarding place / destination column 142 for displaying the boarding place and destination of the user, and a vehicle allocation memo display column 143 when there are special notes. In the vehicle dispatch memo display column 143, for example, an act that is likely to cause trouble such as a taxi crew being assaulted by a customer or a customer who requested a vehicle dispatch not appearing at a designated boarding place, a customer's comment, etc. Can be described. By including the vehicle allocation history 140 in the customer data 110, it is possible to grasp the place where the customer frequently visits, the frequency of use, the time zone of frequent use, etc., and avoid troubles such as a vehicle allocation error or the customer incorrectly instructing the destination. obtain. In addition, an act that is likely to cause trouble can be an important judgment material when performing credit, which will be described later.

The payment history 150 includes a usage date and time column 151 that displays the date and time of use, an amount column 152 that displays the billed amount, a payment method column 153 that displays the payment method, and a billing date column that displays the billing date of the boarding fee. It includes 154, a payment deadline column 155 for displaying the payment deadline, and a payment memo display column 156 when there are special notes.

Further, in the payment method column 153, it is described whether or not the payment has been made together with the payment method. Further, in the payment memo display field 156, important information regarding the collection of the invoiced fare, such as the fact that the passenger has escaped, the payment after the payment deadline, the shortage of payment, and the expiration of the credit card, is entered. .. By including the payment history 150 in the customer data 110 in this way, the payment status of the customer can be grasped, which can be an important factor for determining whether or not to receive a vehicle allocation request in the credit described later.
(Management side communication unit 20)

The management side communication unit 20 is a member for communicating with the outside. The management-side communication unit 20 of FIG. 1 includes a management-side reception unit 21 and a management-side transmission unit 22. When the customer CST intends to register the registration information 120, the management side receiving unit 21 receives the registration information 120 via the telephone line if it is a telephone or via the Internet if it is a vehicle dispatch application. The registration information 120 is stored in the customer database 10. Further, when the customer CST makes a vehicle allocation request, the vehicle allocation request is received via the management side receiving unit 21. At this time, the registration information 120 may be registered and the vehicle allocation request may be automatically handled by the vehicle allocation management device 100, or may be performed by the operator OPR.

Here, the microphone MIC and the speaker SPK are members for the operator OPR operating the vehicle allocation management device 100 to have a conversation with the customer CST and the crew member DRV of the taxi vehicle TXI. Further, the management side operation unit 60 is a member for inputting or selecting the registration information 120 acquired by the operator OPR by talking with the customer CST through the microphone MIC and the speaker SPK. For example, the operator OVER responds to the call of the registration request from the customer CST received by the management side receiving unit 21, and registers the registration information 120 of the customer CST. In addition, the operator ORG responds to a call from the customer CST requesting vehicle allocation. Further, in response to this vehicle allocation request, the operator OVER transmits the vehicle allocation request, which will be described later, to the crew member DRV. The vehicle dispatch request is made by text message, but it can also be contacted wirelessly or by telephone if necessary.
(Management side control unit 30)

The management side control unit 30 is a member for crediting whether a taxi can be dispatched based on the customer data 110 obtained from the customer database 10. This credit may be given when the customer CST registers the registration information, or may be given each time the customer CST requests vehicle allocation. Alternatively, it may be performed at the time of registration and each time a vehicle dispatch request is made.

First, when the management side receiving unit 21 receives the vehicle allocation request, the management side control unit 30 performs credit based on the customer data 110 of the customer CST who made the vehicle allocation request. The method of performing credit may be a known method, and in the present embodiment, for example, the information included in the usage information 130 is weighted and a reference value is set. In this way, if the standard value is exceeded, taxi dispatch will be refused, and it will be easier to make a decision when crediting.

Specifically, the act that is likely to cause a trouble entered in the vehicle allocation memo display field 143 of the vehicle allocation history 140 in FIG. 4, and the boarding fee entered in the payment method field 153 and the payment memo display field 156 of the payment history 150. Weights such as 53.1 are given according to the importance of the material for judging whether or not the vehicle can be dispatched, such as actions that are likely to be unable to be collected, and the total evaluation is calculated. For example, the heaviest 5 is given to the fact of escape or violence, 3 is given if the previous fare is still unpaid, credit is OK if the overall evaluation is less than 5, and credit is OK if it is 5 or more. Credit is provided by setting a standard that credit is NG. After that, the customer CST who requested the vehicle allocation is notified that if the credit result is NG, the vehicle allocation request is rejected, and if the credit result is OK, the vehicle allocation request is accepted.

When such credit is performed by the operator OVER, the management side control unit 30 causes the management side display unit 50 to display the customer data 110. The operator OVER performs credit as described above based on the displayed customer data 110. After that, the operator OPR notifies the customer CST who requested the vehicle allocation that the vehicle allocation request is rejected if the credit result is NG and that the vehicle allocation request is accepted if the credit result is OK.

In this way, the unique customer information accumulated by the taxi company includes fairly personal information such as the customer's behavior and behavior patterns, so it is compared to the information used in the credit of ordinary credit institutions, for example. As a result, it more reflects the characteristics of each customer. When a vehicle dispatch request is made based on the customer data 110 including such information, the taxi company can make the credit result more reliable. As a result, it is possible to avoid the occurrence of troubles when using a taxi, and it is possible to reduce the risk that the taxi fare cannot be collected.

In addition, when the customer CST registers the registration information 120 or when the vehicle dispatch request is made, the credit is given, as compared with the case where the payment is made at the time of getting off by a credit card, electronic money, etc. without registering in advance. It reduces the risk of troubles such as the card has expired, the smartphone has expired, the electronic money cannot be used, and the pre-charged amount is insufficient, and the boarding fee is more reliable. There is also the advantage of being able to collect.

Further, the taxi dispatch system 1000 of the present embodiment can use not only the credit provided by the taxi company but also the credit system of an external credit institution or the like as shown in FIG. For example, when the customer CST pays the boarding fee with a credit card, the customer CST can communicate with the external credit system SOC of the credit card company via the management side communication unit 20 to perform credit. Furthermore, the credit system of platformers such as Google and Apple, the credit system of financial institutions, and the like can also be used. In this way, by using the credit of an external credit institution in addition to the credit unique to the taxi company, there is an advantage that more reliable credit can be performed.
(Vehicle allocation request generation unit 40)

When the vehicle allocation request generation unit 40 receives a vehicle allocation request from the customer CST registered in the customer database 10, it is OK to give credit to the customer CST by the management side control unit 30. In the case of, a vehicle allocation request including the destination of the customer CST is generated. Then, the management side transmission unit 22 of the management side communication unit 20 transmits a vehicle allocation request to the vehicle side terminal 200 installed in the taxi vehicle.
(Vehicle side terminal 200)

The vehicle-side terminals 200 are installed in one or more taxi vehicles TXI that communicate with the vehicle allocation management device 100, respectively. The vehicle-side terminal 200 receives the vehicle-side communication unit 210 for communicating with the vehicle allocation management device 100, the vehicle allocation acceptance unit 220 for responding to accept the vehicle allocation request, and the customer's authentication when the customer gets on board. It includes a vehicle-side authentication unit 230, and a vehicle-side display unit 240 that switches and displays a vehicle allocation consent screen 220a and an authentication data image 110a, which will be described later.
(Vehicle dispatch acceptance department 220)

The vehicle allocation acceptance unit 220 is a member that notifies the vehicle allocation management device 100 whether the taxi crew DRV refuses or accepts the vehicle allocation request. A known vehicle can be used for the vehicle allocation acceptance unit 220. As an example, as shown in FIG. 5, the vehicle allocation approval unit 220 uses a vehicle allocation approval screen 220a that displays information including a vehicle allocation request transmitted from the vehicle allocation management device 100. The vehicle allocation consent screen 220a includes, for example, a boarding place column 221 that displays the boarding location of the customer, a destination column 222 that displays the destination, and a user name column 223 that displays the name of the taxi user. Further, the vehicle allocation consent screen 220a includes a "decline" button 224 when rejecting the vehicle allocation and an "acknowledgement" button 225 when accepting the vehicle allocation. The vehicle allocation consent screen 220a is displayed on the vehicle side display unit 240.

The taxi crew DRV confirms this vehicle allocation acceptance screen 220a, presses the "decline" button 224 to refuse the vehicle allocation, and presses the "acknowledge" button 225 to approve the vehicle allocation, thereby causing the vehicle allocation management device. You can notify 100.
(Vehicle side certification unit 230)

The vehicle-side authentication unit 230 is a member that acquires customer data 110 from the vehicle allocation management device 100 via the vehicle-side communication unit 210 and accepts the authentication of the customer CST when the customer CST is boarded. The vehicle-side authentication unit 230 is included in the vehicle-side calculation unit 250. The vehicle-side authentication unit 230 has an authentication data image 110a displayed on the vehicle-side display unit 240, a reading unit 232 that reads customer-provided authentication data presented by the customer for authenticating the customer, and authentication data 110a. And a collation unit 233 for collating the customer-provided authentication data acquired by the reading unit 232.

The customer data 110 acquired from the vehicle allocation management device 100 shown in FIG. 2 may be used as it is for the authentication data image 110a, or is composed of only the registration information 120 required for authentication and the boarding fee input field 160. May be good. When the crew member DRV approves the vehicle allocation request, the customer data 110 is acquired from the vehicle allocation management device 110 via the vehicle side communication unit 210, and the vehicle side display unit 240 displays the authentication data image 110a based on the customer data 110. Let me. Then, when the customer CST gets on board, the reading unit 232 reads the customer-provided authentication data presented by the customer CST for authenticating the customer.

Here, the customer-provided authentication data may be arbitrary, but in the first embodiment, since the face authentication is performed, the customer-provided authentication data includes the face image data at the time of boarding the customer CST. In this case, the reading unit 232 includes an imaging unit 232a that captures a photograph of the customer's face at the time of boarding, for example, a digital camera.

Then, the collation unit 233 collates the face image data 125 of the authentication data image 110a with the face image data of the customer CST captured by the digital camera at the time of boarding, and actually uses the taxi with the registered user. Authenticate whether the person who does this is the same. In this way, by authenticating the customer by face authentication, it is possible to easily and accurately authenticate, and it is possible to avoid troubles such as accidentally placing a customer different from the registered user. In addition, by accurately authenticating the customer who actually boarded the taxi and linking it with the customer data 110 stored by the taxi company, there is a risk that the boarding fee, which tends to occur especially when the fee is postpaid, cannot be collected. Can be reduced.

After authenticating the customer CST as described above, the crew member DRV puts the customer CST on the taxi vehicle TXI and drives it to the destination instructed by the customer CST. Upon arriving at the destination specified by the customer CST, the fare will be fixed. The crew member DRV inputs the fixed boarding fee into the boarding fee input field 160 and transmits the fixed boarding fee to the vehicle allocation management device 100 via the vehicle side communication unit 210.

Then, the vehicle allocation management device 100 performs processing according to the payment method of the customer CST. For example, when the payment method of the customer CST is cash, it is recorded in the payment history 150, and the payment method column 153 is regarded as paid. On the other hand, when the payment method of the customer CST is a credit card, it communicates with the external system SOC which is the credit system of the credit card company to deal with it. The customer CST will be billed for the boarding fee by the credit card company at a later date.
[Embodiment 2]

In the first embodiment, an example in which the customer-provided authentication data provided by the customer CST at the time of boarding is the face image data at the time of boarding of the customer CST has been described. However, the taxi dispatch system of the present invention is not limited to the case where the customer-provided authentication data is the face image data at the time of boarding the customer CST. The customer-provided authentication data need only be information unique to the customer. As an example, symbols such as QR codes and barcodes distributed in advance to customers can be used. The symbol may be delivered to the customer in advance in a physical medium such as a business card-sized card so that the customer presents the symbol to the taxi crew when using the taxi. Further, not limited to such a physical medium, a QR code may be displayed on the display screen of a customer's information communication terminal such as a smartphone, tablet, or mobile phone, and the QR code may be read when using a taxi. .. Alternatively, if the customer's information communication terminal such as a smartphone has a communication function such as NFC or Bluetooth (registered trademark) , the information communication terminal is linked to the customer in advance, and when using a taxi, this information communication terminal and the taxi By communicating with and, the authentication of the information communication terminal can be treated as the authentication of the customer.

Such an example is shown in the block diagram of FIG. 6 as the taxi dispatch system 2000 according to the second embodiment. Here, a taxi use application is installed on the smartphone owned by the customer in advance, and the customer-provided authentication is performed by displaying the customer-specific QR code on the smartphone screen with this taxi use application. It is used as data. In the example of FIG. 6, the QR code reader 232b can be used as the reading unit of the vehicle-side authentication unit 230b. If the face image data is not used for the authentication on the vehicle side, the user face image data field 125 may be omitted from the registration information 120 included in the customer data 110. By omitting the user face image data field 125, it is possible to save the trouble of registering the registration information of the customer CST.

As an example, when registering the registration information 120 or accepting a vehicle allocation request, the customer CST operates his / her smartphone to activate the taxi use application so that the QR code can be obtained from the vehicle allocation management device 100. back. At the time of boarding, the customer CST presents the QR code acquired to the crew member DRV in a state of being displayed on the screen of the smartphone. The crew member DRV reads this QR code with the QR code reader 232b. By using the widely used QR code for authentication in this way, it is possible to easily and reliably authenticate the customer.

As for the QR code, a unique symbol is generated for each customer. This QR code is generated by the vehicle allocation management device 100 and distributed to the vehicle side terminal 200. In addition to fixing the QR code for each customer and displaying a common QR code each time, the security may be enhanced by issuing a different QR code each time.

In the above, the authentication on the vehicle side, the face authentication and the authentication using the QR code have been described. However, the certification on the vehicle side of the present invention is not limited to the above aspect, and any one can be used. For example, it is also possible to use BLE (Bluetooth Low Energy) (product or service name) on the reading unit 232 to authenticate the taxi customer CST touchlessly. In this case, since the customer CST can authenticate on the vehicle side only by getting on the taxi vehicle TXI, the trouble of capturing the face image data and presenting the QR code can be saved, and the convenience can be improved.

Furthermore, the certification on the vehicle side can be verbal. For example, the crew member DRV asks a question verbally when the customer CST gets on board, based on the customer data 110 acquired from the vehicle allocation management device 100. Then, it is confirmed whether or not the information of the customer data 110 and the response of the customer CST match. The content of the question may include the customer's name and destination, as well as information that is difficult to guess, such as a secret word. In this case, a system for using face recognition and a QR code becomes unnecessary, and a taxi dispatch system can be introduced more easily.

Furthermore, a plurality of the above authentication modes may be used in combination. For example, while using face recognition, verbal authentication is also performed. Alternatively, authentication can be performed in any combination, such as oral authentication while authenticating with a QR code. By authenticating in such a different manner, there is an advantage that more accurate authentication can be performed as compared with the case where only face authentication is used, for example.

According to the taxi dispatch system, the taxi dispatch management device, the taxi vehicle side terminal, the taxi dispatch method, the taxi dispatch management program, the medium that can be recorded by a computer, and the stored device of the present invention, it can be suitably used for the taxi company's dispatch business. ..

1000, 2000 ... Taxi dispatch system 100 ... Vehicle allocation management device 10 ... Customer database 20 ... Management side communication unit 21 ... Management side reception unit 22 ... Management side transmission unit 30 ... Management side control unit 40 ... Vehicle allocation request generation unit 50 ... Management side Display unit 60 ... Management side operation unit 110 ... Customer data 110a ... Authentication data image 120 ... Registration information 120a ... Payment information 121 ... User name field 121a ... User pretending field 122 ... User address field 123 ... User phone number Column 124 ... User payment method column 125 ... User face image data column 126 ... Registrant name column 126a ... Registrant Furigana column 127 ... Registrant address column 128 ... Registrant phone number column 129 ... Registrant payment method column 130 ... Usage information 140 ... Vehicle allocation history 141 ... Usage date and time column 142 ... Boarding location / destination column 143 ... Vehicle allocation memo display column 150 ... Payment history 151 ... Usage date and time column 152 ... Amount column 153 ... Payment method column 154 ... Billing date column 155 ... Payment Deadline column 156 ... Payment memo display column 160 ... Boarding fee input field 200 ... Vehicle side terminal 210 ... Vehicle side communication unit 220 ... Vehicle dispatch acceptance unit 220a ... Vehicle allocation consent screen 221 ... Boarding location column 222 ... Destination column 223 ... User name column 224 ... Reject button 225 ... OK button 230, 230b ... Vehicle side authentication unit 232 ... Reading unit 232a ... Imaging unit 232b ... QR code reader 233 ... Verification unit 240 ... Vehicle side display unit 250 ... Vehicle side calculation unit CST ... Customer OPR ... Operator TXI ... Taxi vehicle DRV ... Taxi vehicle crew MIC ... Mike SPK ... Speaker SOC ... External credit system

Claims (17)

The vehicle allocation management device installed in the taxi company and
A taxi dispatch system including vehicle-side terminals installed on one or more taxi vehicles that communicate with the vehicle allocation management device.
The vehicle allocation management device is
A customer database for storing customer data including pre-registered registration information for authentication including a name for each customer and taxi usage information for each customer, and
The management side communication unit for communicating with the outside,
Based on the customer data obtained from the customer database, a management side control unit for crediting whether a taxi can be dispatched and
When receiving a vehicle allocation request from a customer registered in the customer database, if the credit result of crediting to the customer is OK, the destination of the customer. A vehicle allocation request generator that generates a vehicle allocation request including
With
The vehicle-side terminal
A vehicle-side communication unit for communicating with the vehicle allocation management device,
When the vehicle allocation request generated by the vehicle allocation request generation unit is received by the vehicle side communication unit via the management side communication unit, a vehicle allocation acceptance unit that responds to accept the vehicle allocation request and a vehicle allocation acceptance unit.
A vehicle-side authentication unit that acquires the customer data from the vehicle allocation management device via the vehicle-side communication unit and accepts the customer's authentication when the customer gets on board.
With
The customer database can register, as the customer data, a case where a taxi crew member was assaulted by a customer in the past and a case where a customer who requested a vehicle dispatch did not appear at a designated boarding place, together with a payment history.
The management side control unit provides credit based on a comprehensive evaluation of the payment history recorded in the customer data and the weighting of registered items including cases of violence, and if the customer database contains violence, the management side control unit provides credit. A taxi dispatch system that is configured so that the credit result is NG. The taxi dispatch system according to claim 1.
A taxi dispatch system that is configured so that the credit result is not NG just because the previous boarding fee is still unpaid. Claim 1 or a taxi dispatch system according to 2,
The vehicle side certification unit
A reader that reads the customer-provided authentication data presented by the customer to authenticate the customer,
A collation unit that collates the customer data acquired from the vehicle allocation management device via the vehicle-side communication unit with the customer-provided authentication data acquired by the reading unit.
Taxi dispatch system equipped with. The taxi dispatch system according to claim 3.
A taxi dispatch system in which the customer-provided authentication data includes a QR code (registered trademark) that is given to the customer in advance and held at the time of boarding. The taxi dispatch system according to claim 3 or 4.
The customer data includes pre-registered customer face image data.
The reading unit includes an imaging unit that captures a photograph of the customer's face at the time of boarding as the customer-provided authentication data.
A taxi dispatch system configured such that the collation unit authenticates by collating the face image data acquired from the vehicle allocation management device with a face photograph of a customer at the time of boarding captured by the imaging unit. The taxi dispatch system according to any one of claims 1 to 5.
The management side communication unit is a taxi dispatch system capable of communicating with an external credit institution. The taxi dispatch system according to any one of claims 1 to 6.
The vehicle allocation management device further
A microphone and a speaker for having a conversation in response to a customer registration or vehicle allocation request call received by the management side communication unit.
An operation unit for inputting or selecting customer information acquired by a vehicle dispatching operator talking with a customer through the microphone and speaker.
Based on the acquired information, the management side display unit for displaying the customer data and
Taxi dispatch system equipped with. The taxi dispatch system according to any one of claims 1 to 7.
The customer database includes payment information regarding a taxi usage fee payment method as the customer data.
The vehicle-side terminal is a taxi dispatch system configured to settle a fare with a customer based on the payment information registered in the customer database when the customer gets off. The taxi dispatch system according to any one of claims 1 to 8.
The customer database is a taxi dispatch system that can accept registration applications by a person different from a customer who uses a taxi as the customer data. The taxi dispatch system according to any one of claims 1 to 9.
The customer database is a taxi dispatch system that allows a customer who uses a taxi and a person who pays a fare to be registered as the customer data differently. A vehicle allocation management device installed in a taxi company that communicates with vehicle-side terminals installed in one or more taxi vehicles.
A customer database for storing customer data including pre-registered registration information for authentication including a name for each customer and taxi usage information for each customer, and
The management side communication unit for communicating with the outside,
Based on the customer data obtained from the customer database, a management side control unit for crediting whether a taxi can be dispatched and
When receiving a vehicle allocation request from a customer registered in the customer database, if the credit result of crediting to the customer is OK, the destination of the customer. A vehicle allocation request generator that generates a vehicle allocation request including
With
The vehicle allocation request generated by the vehicle allocation request generation unit is transmitted to the taxi vehicle side, and the vehicle allocation request is transmitted to the taxi vehicle side.
The taxi vehicle side that has received the vehicle allocation request is configured to transmit the customer data that is the target of the vehicle allocation request so that the taxi vehicle side can authenticate the customer when the customer gets on board. death,
The customer database can register, as the customer data, a case where a taxi crew member was assaulted by a customer in the past and a case where a customer who requested a vehicle dispatch did not appear at a designated boarding place, together with a payment history.
The management side control unit provides credit based on a comprehensive evaluation of the payment history recorded in the customer data and the weighting of registered items including cases of violence, and if the customer database contains violence, the management side control unit provides credit. A vehicle allocation management device configured to make the credit result NG. It is a vehicle-side terminal installed in a taxi vehicle that communicates with the vehicle allocation management device installed in the taxi company.
A vehicle-side communication unit for communicating with the vehicle allocation management device,
When the vehicle allocation request generated by the vehicle allocation request generation unit of the vehicle allocation management device is received by the vehicle side communication unit via the management side communication unit, the vehicle allocation acceptance unit responds to the effect that the vehicle allocation request is accepted.
A vehicle-side authentication unit that acquires customer data from the vehicle allocation management device via the vehicle-side communication unit and accepts the customer's authentication when the customer gets on board.
With
Since the customer data is credited by a comprehensive evaluation of the weighting of registered items, the payment history and the taxi crew have been assaulted by the customer in the past, or the customer who requested the dispatch to the designated boarding place. A vehicle-side terminal that includes information on whether it has never appeared. The vehicle-side terminal according to claim 12,
The vehicle side certification unit
A reader that reads the customer-provided authentication data presented by the customer to authenticate the customer,
A collation unit that collates the customer data acquired from the vehicle allocation management device via the vehicle-side communication unit with the customer-provided authentication data acquired by the reading unit.
Vehicle-side terminal with. A taxi dispatching method in which a taxi dispatch management device installed in a taxi company communicates with a vehicle-side terminal installed in one or more taxi vehicles to dispatch a taxi.
The management side control unit of the vehicle allocation management device registers the registration information for authentication including the name of each customer and the customer data including the taxi usage information for each customer in the customer database via the management side display unit. And the process of encouraging
A process in which the management side control unit receives a vehicle allocation request from any of the customers registered in the customer database.
For the customer who received the vehicle dispatch request, the payment history included in the customer database and the taxi crew have been assaulted by the customer in the past, or the customer who requested the vehicle dispatch is at the designated boarding location. Based on the information including whether it has never appeared, the management side control unit credits by the comprehensive evaluation of the weighting of the registered items, and if the customer database contains violent acts, the credit result is given. The process of NG and
Based on the credit result of whether the taxi can be dispatched using the customer data obtained from the customer database, the management side control unit rejects the vehicle dispatch request when the credit result is NG, and the credit result. If is OK, the process of accepting the vehicle dispatch request and
A process in which the vehicle allocation request generation unit generates a vehicle allocation request including the destination of the customer who has accepted the vehicle allocation request, and the management side communication unit transmits the vehicle allocation request to the vehicle side terminal.
A process in which the vehicle allocation acceptance unit prompts the vehicle-side terminal that receives the vehicle allocation request by the vehicle-side communication unit to respond whether or not to accept the vehicle allocation request.
When the vehicle allocation request is accepted, the customer data is acquired from the vehicle allocation management device via the vehicle side communication unit, and when the customer gets on board, the vehicle side authentication is compared with the information provided by the customer. The process of certification by the department and
Taxi dispatch methods including. The taxi dispatch method according to claim 14.
The process of registering the customer data in the customer database includes registration of payment information regarding the payment method of the taxi usage fee.
The taxi dispatch method further
After authenticating the customer, the taxi vehicle transfers the customer to the destination, and when getting off, the vehicle-side terminal gets on the vehicle based on the payment information registered in the customer database with the customer. Taxi dispatch methods, including the process of making payments. It is a vehicle allocation management program that is installed in a taxi company and communicates with the vehicle side terminals installed in each of one or more taxi vehicles.
A function to register customer data including authentication registration information including the name of each customer and taxi usage information for each customer in the customer database, and
A function to accept vehicle dispatch requests from any of the customers registered in the customer database,
For the customer who received the vehicle dispatch request, the payment history obtained from the customer database and the taxi crew have been beaten by the customer in the past, or the customer who requested the vehicle dispatch appears at the designated boarding place. Based on the customer data including information on whether or not it has never been done, credit is given as to whether or not a taxi can be dispatched by a comprehensive evaluation of weighting of registered items , and the customer database contains violent acts. In the case, the function to make the credit result NG and
Based on the credit result, if the credit result is NG, the vehicle allocation request is rejected, and if the credit result is OK, the vehicle allocation request is accepted.
A function of generating a vehicle allocation request including the destination of the customer who accepted the vehicle allocation request and transmitting it to the vehicle side terminal by the management side communication unit.
A function of receiving a response as to whether or not to accept the vehicle allocation request from the vehicle side terminal that has received the vehicle allocation request in the vehicle side communication unit.
A function of transmitting customer data of a customer who is the target of the vehicle allocation request to the taxi vehicle side to which the vehicle allocation request is accepted, and causing the taxi vehicle side to authenticate the customer when the customer gets on board. When,
A vehicle allocation management program that allows a computer to execute. A computer-readable recording medium or device that records the program according to claim 16.

Images