Taxi information processing method, taxi information processing system, taxi terminal device, computer program, and taxi terminal system

Abstract

To provide a taxi information processing method, a taxi information processing system and a taxi terminal system, which are expected to make users feel secure.SOLUTION: A taxi information processing method according to an embodiment comprises: determining a travel route based on desired boarding point and destination point of a user wishing to take a taxi; determining an advance fare for a taxi ride based on the determined travel route; displaying the determined travel route and determined advance fare on a user terminal device used by the user and a taxi terminal device used by a driver of a taxi; and storing the determined travel route in a database. The determined advance fare may be displayed on a fare display device provided in the taxi when the user is getting on the taxi.SELECTED DRAWING: Figure 1

Description

[Technical field]

[0001] The present invention relates to a taxi information processing method, a taxi information processing system, a taxi terminal device, a computer program, and a taxi terminal system for performing processing related to calculation or settlement of taxi fares. [Background technology]

[0002] Conventionally, the fare for using a taxi has been calculated based on the distance and time traveled by the taxi. When a user uses a taxi, the fare increases as the taxi travels, and the fare is determined when the taxi arrives at the destination, and the user pays the determined fare to the taxi driver. Taxi fares can be paid using cash, credit cards, electronic money, etc.

[0003] Patent Document 1 proposes a cardless payment system that does not require a credit card payment terminal. In this cardless payment system, when a customer requests a card payment with a business, the business inputs the payment amount and the phone number of the customer's terminal into the business terminal, and transmits them to an operator server to make a payment request. The operator server transmits approval information to the customer's terminal, and if the customer determines that the approval information is correct, the customer terminal makes a payment request to the intermediary server. The intermediary server makes a billing request to the card company server, receives the payment result from the card company server, and notifies the operator server of the payment result. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] JP 2019-153067 A Summary of the Invention [Problem to be solved by the invention]

[0005] When using a traditional taxi, the user may feel uneasy because the user does not know the fare he or she will have to pay until the taxi arrives at the destination.

[0006] The present invention has been made in consideration of the above circumstances, and its purpose is to provide a taxi information processing method, a taxi information processing system, a taxi terminal device, a computer program, and a taxi terminal system that are expected to give users a sense of security. [Means for solving the problem]

[0007] A taxi information processing method according to one embodiment determines a driving route based on a desired boarding point and a destination point of a user wishing to ride in a taxi, determines an advance fare for the taxi ride based on the determined driving route, displays the determined driving route and the determined advance fare on a user terminal device used by the user and a taxi terminal device used by the taxi driver, and stores the determined driving route in a database. Effect of the Invention

[0008] According to one embodiment, it is expected to provide a sense of security to the user. [Brief description of the drawings]

[0009] [Figure 1] Overview of the taxi information processing system [Diagram 2] Configuration of the vehicle dispatch application server device [Diagram 3] Fee calculation database [Figure 4] User DB [Diagram 5] Taxi DB [Figure 6] Order Management DB [Figure 7] Dispatch history DB [Figure 8] Configuration of user terminal device [Figure 9] Configuration of the payment server device of the payment company [Figure 10] Payment company's payment database [Figure 11] Taxi terminal device configuration [Figure 12] Fare meter and passenger terminal device configuration [Figure 13] Vehicle dispatch request processing diagram [Figure 14] Vehicle dispatch request screen on user terminal device [Figure 15] Taxi dispatch request acceptance screen on taxi terminal device [Figure 16] Taxi cancellation flow [Figure 17] Cancellation acceptance screen on the taxi terminal device [Figure 18] Payment approval screen [Figure 19] Overall payment processing flow [Figure 20] User terminal device processing flow [Figure 21] Processing flow of the ride-hailing app server device [Figure 22] Processing flow of the ride-hailing app server device [Figure 23] Taxi terminal device processing flow [Figure 24] Taxi terminal device processing flow [Diagram 25] Information storage processing for the ride-hailing app server device [Figure 26] Dispatch history screen [Figure 27] Fee calculation DB of modification 1 [Figure 28] Route selection screen of the second embodiment [Figure 29] Information display screen of the second embodiment [Diagram 30] Information display screen of the second embodiment [Diagram 31] Taxi selection screen of the second embodiment [Diagram 32] Processing flow of the vehicle-dispatch application server device according to the second embodiment DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0010] Specific examples of the taxi information processing system according to the embodiment of the present invention will be described below with reference to the drawings. Note that the present invention is not limited to these examples, but is defined by the claims, and is intended to include all modifications within the meaning and scope of the claims.

[0011] <Embodiment 1> <System Overview> Fig. 1 is a schematic diagram for explaining an overview of a taxi information processing system according to this embodiment. The taxi information processing system according to this embodiment includes a vehicle dispatch application server device 11, a taxi terminal system 20 provided in one or more taxis 2, and a user terminal device 31 used by one or more users 3. Note that the taxi information processing system according to this embodiment can perform processing simultaneously and in parallel for multiple taxis 2 and multiple users 3, but Fig. 1 illustrates only one taxi 2 and one user 3.

[0012] The taxi-dispatch application server device 11 of the taxi information processing system according to the present embodiment can communicate with external devices, such as an information processing device 13 managed and operated by a taxi company and a payment server device 14 managed and operated by a payment company, via a network such as the Internet. The taxi-dispatch application server device 11 performs taxi dispatch processing and taxi fare calculation processing, etc., in cooperation with devices such as the information processing device 13 and the payment server device 14. Note that in the present embodiment, the taxi-dispatch application server device 11 is one device, but this is not limited thereto, and the taxi-dispatch application server device 11 may be realized by the cooperation of multiple devices. The taxi-dispatch application server device 11 may be configured to perform part or all of the processing performed by the information processing device 13 and the payment server device 14.

[0013] In the taxi information processing system according to the present embodiment, the user 3 can use the user terminal device 31 to request dispatch of a taxi 2. At this time, the user 3 can use the user terminal device 31 to specify a desired boarding point and a destination point (drop-off point) of the taxi 2. If the desired boarding point is the current location of the user 3, the user specifies the destination point, and the desired boarding point can be determined based on location information obtained from a GPS (Global Positioning System) or the like. The user's request for dispatch of a taxi is transmitted from the user terminal device 31 to the dispatch application server device 11 via a network such as a mobile phone communication network, a wireless LAN (Local Area Network), and the Internet.

[0014] The ride-dispatch application server device 11 determines the travel route of the taxi 2 based on the boarding point and the destination point of the user 3, and calculates the fare when the taxi 2 travels along this travel route. In the taxi information processing system according to the present embodiment, the fare calculated by the ride-dispatch application server device 11 is confirmed as the advance fare, and the user 3 who uses the taxi 2 pays this advance fare. Information on the travel route determined by the ride-dispatch application server device 11 and the confirmed advance fare is transmitted from the ride-dispatch application server device 11 to the user terminal device 31 and presented to the user 3. At this time, the ride-dispatch application server device 11 may transmit information on a plurality of travel routes and advance fare as candidates, and the user 3 may select a desired one from the plurality of candidates. In addition, if the user 3 has a discount coupon or the like for the fare, the ride-dispatch application server device 11 may calculate the advance fare to which the discount is applied.

[0015] In this embodiment, the amount determined in advance by the taxi information processing system is called the "advance fare", but this is only one example and may be called by various names such as "pre-determined fare", "advance fare", "fixed fare", "pre-determined fee", or "fixed fee". The "advance fare" includes the fare for the taxi's travel, and other fees such as highway tolls, pick-up fees, or parking fees may or may not be included in the "advance fare". If fees such as highway tolls are not included in the "advance fare", the amount ultimately paid by the passenger is the amount obtained by adding the previously determined "advance fare" to the fees such as highway tolls.

[0016] A taxi 2 is dispatched when the user 3 performs an operation to approve the driving route and advance fare presented on the user terminal device 31. The approval operation by the user 3 is provided from the user terminal device 31 to the vehicle dispatch application server device 11, and in response, the vehicle dispatch application server device 11 performs a process to determine a taxi 2 to be dispatched to the user 3. The vehicle dispatch application server device 11 manages information on the positions and the presence or absence of passengers for a plurality of taxis 2, and selects one taxi 2 that suits the request from among the plurality of taxis 2. For example, the vehicle dispatch application server device 11 transmits information on the determined driving route and the confirmed advance fare to a taxi 2 located near a desired boarding point of the user 3, and requests the taxi to be dispatched.

[0017] In this embodiment, the taxi terminal system 20 provided in the taxi 2 includes devices such as a taxi terminal device 21, a fare meter 22, and a passenger terminal device 23. The taxi terminal device 21 is a terminal device used by the driver of the taxi 2, and receives a dispatch request from the dispatch application server device 11, displays information on a travel route and a prepayment fee, and accepts a selection from the driver as to whether or not to accept the dispatch request. If the dispatch request is accepted, the taxi terminal device 21 notifies the dispatch application server device 11 of the acceptance, and the dispatch application server device 11 notifies the user terminal device 31 of the acceptance. As a result, a reservation for dispatch between the user 3 and the taxi 2 is established, and the taxi 2 heads to a desired boarding point of the user 3, and heads to a destination point after picking up the user 3.

[0018] For example, if a breakdown or accident occurs on the way to a desired boarding point of the user 3 and the taxi 2 is unable to proceed to the desired boarding point, the driver of the taxi 2 can cancel the dispatch of the taxi through the taxi terminal device 21. The taxi terminal device 21 that has accepted the cancellation operation notifies the taxi dispatch application server device 11 of the cancellation, and the taxi dispatch application server device 11 notifies the user terminal device 31 of the cancellation. After that, the taxi dispatch application server device 11 may attempt to dispatch another taxi 2.

[0019] The fare meter 22 of the taxi terminal system 20 is disposed, for example, on the instrument panel of the taxi 2 or nearby, in a position visible to the user 3 sitting in the back seat of the taxi 2. The fare meter 22 is a device that displays the fare to be paid by the user who uses the taxi 2, and in normal use of the taxi 2, the fare is added up according to the traveled distance, travel time, etc. In this embodiment, when the advance fare has been determined as described above, the fare meter 22 displays the advance fare, and the displayed advance fare does not increase or decrease.

[0020] After the taxi 2 arrives at the destination, the user 3 pays (settles) the confirmed advance fee. In the present embodiment, the advance fee can be paid by using a credit card registered in advance in the taxi information processing system, or by using a QR (Quick Response) code (registered trademark) or a barcode. However, a cash payment or a payment method using electronic money may also be used. In the payment process, the passenger terminal device 23 of the taxi terminal system 20 displays the same amount as the advance fee displayed on the fare meter 22 as the payment fee to be paid by the user 3, and also displays, for example, a user name and credit card information. The passenger terminal device 23 is provided, for example, on the back of the driver's seat of the taxi 2, and is a device that displays various information such as payment information and advertisement information to the user sitting in the back seat, and a tablet terminal device or the like is used. When the passenger terminal device 23 receives an operation from the user 3 to approve the payment of the displayed payment fee, it notifies the payment server device 14 of the same via the taxi terminal device 21 and the vehicle dispatch application server device 11. The settlement server device 14 is a device managed and operated by a settlement company, and performs settlement processing for the taxi fare of the user 3 in response to a notice of payment from the vehicle-dispatch application server device 11.

[0021] In the taxi information processing system according to the present embodiment, the advance fare determined by the vehicle-dispatch application server device 11 is not changed by the subsequent use of the taxi 2. However, for example, a discount such as a discount for persons with disabilities, which cannot be applied unless a certificate or the like is presented to the driver of the taxi 2, cannot be applied to the advance fare, and therefore the discount may be applied to the advance fare at the payment processing stage, causing the advance fare to change. In this case, the driver of the taxi 2 checks the user's certificate, and then performs an operation to apply the discount, for example, on the fare meter 22 or the taxi terminal device 21. In response to this operation, the payment fare with the discount applied to the advance fare is displayed on the passenger terminal device 23, and payment is made at the payment fare with the discount applied.

[0022] In this embodiment, the advance fare does not include, for example, the toll of a toll road on which the taxi 2 has traveled or the fee of a parking lot used by the taxi 2. If such additional fees are incurred, the advance fare may be changed. In this case, the driver of the taxi 2 operates, for example, the taxi terminal device 21 to input the additional fee. In response to this operation, the passenger terminal device 23 displays the payment fare with the additional fee added to the advance fare, and payment is made using this payment fare.

[0023] Furthermore, if the user 3 gets in the taxi 2 and wishes to change the destination after the taxi 2 has started traveling, the taxi information processing system according to this embodiment performs a payment process for the advance fare at that point in time, regardless of the actual travel distance and travel time of the taxi 2. After that, the user 3 may use the taxi 2 to a different destination using a normal fare system in which a fare is added according to the travel distance and travel time, or may use the taxi 2 after determining a new advance fare.

[0024] In the taxi information processing system according to the present embodiment, the dispatch application server device 11 stores and accumulates information about the taxi 2 in a dispatch history DB (database). The dispatch application server device 11 stores the travel route determined before the user 3 gets into the taxi 2 and the confirmed advance fare in the dispatch history DB in association with information such as a user ID for identifying the user 3, a taxi ID for identifying the taxi 2, and date and time. The taxi terminal device 21 also has a receiver for receiving GPS signals and can acquire the actual travel route of the taxi 2 based on the GPS signal. The dispatch application server device 11 acquires the actual travel route of the taxi 2 from the taxi terminal device 21 and stores it in the dispatch history DB together with the travel route determined in advance. The information stored in the dispatch history DB can be used, for example, to respond to later complaints, improve the process of determining the travel route, or improve the automatic driving process.

[0025] <Device configuration> 2 is a block diagram showing a configuration of the vehicle-dispatch application server device 11 according to the present embodiment. The vehicle-dispatch application server device 11 according to the present embodiment is configured to include a processing unit 111, a memory unit (storage) 112, a communication unit (transceiver) 113, a display unit (display) 114, and an operation unit 115. The processing unit 111 is configured using an arithmetic processing device such as a central processing unit (CPU), a micro-processing unit (MPU) or a graphics processing unit (GPU), a read only memory (ROM), and a random access memory (RAM). The processing unit 111 reads and executes a server program 112a stored in the storage unit 112 to perform various processes such as a process of determining a taxi's travel route and a process of calculating a taxi's advance fare.

[0026] The storage unit 112 is configured using a large-capacity storage device such as a hard disk. The storage unit 112 stores various programs executed by the processing unit 111 and various data required for the processing of the processing unit 111. In this embodiment, the storage unit 112 stores a server program 112a executed by the processing unit 111, and is provided with a plurality of databases for storing various information. The databases provided in the storage unit 112 include, for example, a fare calculation DB 112b for calculating a taxi advance fare, a user DB 112c for storing information about a user who uses the present system, a taxi DB 112d for storing information about a taxi to be dispatched by the present system, an order management DB 112e for managing orders for taxi dispatch from users, and a dispatch history DB 12 for storing information about taxi operation.

[0027] In the present embodiment, the server program 112a is provided in a form recorded on a recording medium 99 such as a memory card or an optical disk, and the ride-dispatch application server device 11 reads the server program 112a from the recording medium 99 and stores it in the storage unit 112. However, the server program 112a may be written in the storage unit 112, for example, during the manufacturing stage of the ride-dispatch application server device 11. In addition, for example, the server program 112a may be distributed by another remote server device or the like and acquired by the ride-dispatch application server device 11 through communication. For example, the server program 112a may be read from the recording medium 99 by a writing device and written to the storage unit 112 of the ride-dispatch application server device 11. The server program 112a may be provided in a form distributed via a network, or may be provided in a form recorded on the recording medium 99.

[0028] FIG. 3 is a schematic diagram showing an example of the configuration of the fare calculation DB 112b. The fare calculation DB 112b according to the present embodiment is a table in which information such as "company ID", "area", "initial fare", "initial distance", "addition unit", "additional fare", and "coefficient" are stored in association with each other. In the present embodiment, the vehicle-dispatch application server device 11 calculates the advance fare for a taxi using the following formula (1), and values ​​to be substituted into this formula (1) are stored in advance in the fare calculation DB 112b. When a user uses a discount coupon or the like, the advance fare calculated by formula (1) is applied with a discount to become the final advance fare. The calculation formula for the advance fare and the values ​​stored in the fare calculation DB 112b are merely examples, and are not limited thereto.

[0029] Advance fare = {base fare + (mileage - base fare) / additional unit x additional fare} x coefficient … (1)

[0030] The "company ID" in the fare calculation DB 112b is identification information for identifying the taxi operating company, and in the illustrated example, IDs such as "company A" and "company B" are stored. The "area" is information indicating the area covered by each operating company, and in the illustrated example, areas such as "prefecture a" and "prefecture b" are stored. In the taxi information processing system according to the present embodiment, taxis operated by multiple operating companies are dispatched, and the area covered by each operating company is predefined. There may be multiple operating companies whose covered areas overlap in part or in whole. In the illustrated example, the covered area is defined for each prefecture, but it may be for each city, ward, town, or village, for example, or may be information that identifies the area by combining multiple coordinates such as latitude and longitude.

[0031] The "initial fare" is the minimum fare paid by a user who uses a taxi, and in the illustrated example, fares such as "400 yen" and "500 yen" are stored. The "initial distance" is the distance the taxi will travel for the "initial fare", and in the illustrated example, distances such as "1500m" and "1800m" are stored. The "addition unit" is the distance to which the fare is added after the taxi has traveled the "initial distance", and in the illustrated example, distances such as "200m" and "180m" are stored. The "additional fare" is the fare added for travel of the "addition unit", and in the illustrated example, distances such as "100 yen" and "85 yen" are stored.

[0032] The "coefficient" is a value for making a final adjustment to the advance fare. In this embodiment, the "coefficient" is determined in advance for each day of the week and time period, for example, "Monday midnight", "Monday 1:00", "Monday 2:00", ..., "Monday 11:00", "Tuesday midnight", ..., "Sunday 11:00", and values ​​such as "1.2", "1.1", "1.5", "1.4", etc. are stored in the fare calculation DB 112b. The "initial fare", "initial distance", "additional unit", "additional fare", and "coefficient" in the fare calculation DB 112b are information that defines formula (1), which is a calculation formula for the advance fare.

[0033] The fare calculation DB 112b is created in advance and stored in the storage unit 112 of the vehicle-dispatch application server device 11. The fare calculation DB 112b may be modified or supplemented with information at an appropriate timing, for example, when a new operating company enters the market or when a fare is revised.

[0034] 4 is a schematic diagram showing an example of the configuration of the user DB 112c. The user DB 112c according to the present embodiment is a database in which information such as "user ID", "user name", "telephone number", "email address", "payment information", and "owned coupons" are stored in association with each other. Most of the information stored in the user DB 112c is information registered by the user, for example, when starting to use the present system, for example, when installing an application program (app) for dispatching a taxi in the user terminal device 31. The user DB 112c is modified or added by the vehicle dispatch application server device 11, for example, when the user performs new registration or modifies registered information.

[0035] The "user ID" in the user DB 112c is identification information uniquely assigned to a user, and in the illustrated example, IDs such as "user 001," "user 002," and "user 003" are stored. The "user ID" may be determined by the user himself or automatically by the ride-hailing application server device 11. The "user name," "telephone number," and "email address" are personal information of each user, and are abbreviated as "..." in the figure.

[0036] In the user DB 112c according to this embodiment, multiple pieces of "payment information" can be registered for one user, and are shown in the figure as "payment information 1", "payment information 2", "...". "Payment information" is information on the payment method used by the user when paying a taxi fare, and in the example shown in the figure, information such as "credit card" and "electronic money" is stored. Note that these "credit card" and "electronic money" are abbreviated, and in reality, information necessary for payment processing, such as the credit card number and expiration date, is stored.

[0037] In this embodiment, one user can own multiple coupons. The user DB 112c can store information on multiple "owned coupons" for one user, which are shown in the figure as "owned coupon 1", "owned coupon 2", "...". "Owned coupon" is information on coupons owned by the user, and in the example shown in the figure, information such as "10% discount", "100 yen discount", and "none" is stored. Note that the configuration of the user DB 112c and the information stored therein shown in FIG. 4 are merely examples and are not limited to these.

[0038] FIG. 5 is a schematic diagram showing an example of the configuration of the taxi DB 112d. The taxi DB 112d according to the present embodiment is a database in which information such as "taxi ID", "company ID", "driver", "current location", and "tariff status" are stored in association with each other. The "taxi ID" is identification information uniquely assigned to a taxi, and in the illustrated example, information such as "taxi A01", "taxi A02", and "taxi B01" is stored as taxi IDs assigned to managed taxis. The "company ID" is identification information for identifying a taxi operating company, and in the illustrated example, IDs such as "company A" and "company B" are stored. The "driver" is information about a taxi driver, and may include information such as the driver's name and telephone number. Information such as the "taxi ID", "company ID", and "driver" is appropriately modified and added depending on, for example, the addition or reduction of taxis.

[0039] "Current location" in the taxi DB 112d is information on the current location of the taxi based on GPS, and is abbreviated as "..." in the figure, but actually stores coordinate information such as latitude and longitude. "Tariff status" is information indicating the status of the taxi, and stores information such as "empty vehicle", "rented vehicle", and "pick-up". The taxi-dispatch application server device 11 periodically communicates with the taxi terminal device 21 of the taxi 2, acquires information on the current location and status of the taxi 2, and stores it in the taxi DB 112d.

[0040] 6 is a schematic diagram showing an example of the configuration of the order management DB 112e. The order management DB 112e is a database that stores information about an order for dispatching a taxi that the dispatch application server device 11 has received from the user terminal device 31. The order management DB 112e according to the present embodiment is a database that stores information such as "date and time", "user ID", "taxi ID", "preliminary driving route", "preliminary fare", "boarding reservation time", "boarding reservation location", "drop-off reservation location", and "reservation number" in association with each other.

[0041] The "date and time" of the order management DB 112e is the date and time when the user ordered the dispatch of a taxi, and in the illustrated example, information such as "2020 / 1 / 20 11:12" and "2020 / 1 / 20 11:26" is stored. The "user ID" is the ID of the user who used the taxi, and in the illustrated example, information such as "user 123" and "user 054" is stored. The "taxi ID" is identification information uniquely assigned to a taxi, and in the illustrated example, information such as "taxi A33" and "taxi D21" is stored as the taxi ID of the taxi used by the user.

[0042] The "pre-travel route" is information on the taxi travel route determined by the vehicle dispatch application server device 11 based on the desired boarding point and the destination point input by the user. When the vehicle dispatch application server device 11 presents a plurality of travel routes as candidates to the user, the "pre-travel route" stores information on one travel route selected by the user. Note that in this figure, the travel route information is abbreviated as "...", but in reality, the route information is stored as, for example, a plurality of coordinate information or vector information connecting the desired boarding point to the destination point. The "pre-fare" is the taxi usage fee calculated and determined by the vehicle dispatch application server device 11, and in the illustrated example, information such as "1234 yen" and "3210 yen" is stored. The vehicle dispatch application server device 11 calculates the taxi travel distance based on the pre-travel route, and calculates the pre-fare by using the information on the fare calculation DB 112b shown in FIG. 3 and the above-mentioned formula (1).

[0043] "Boarding reservation time" is information regarding the date and time when the user wishes to board a taxi. In the illustrated example, information such as "2020 / 1 / 20 11:20" and "2020 / 1 / 20 13:00" is stored. "Boarding reservation location" is the desired boarding point where the user wishes to board a taxi. "Drop-off reservation location" is the destination point where the user wishes to disembark from the taxi. Note that in this figure, the information for "boarding reservation location" and "drop-off reservation location" is abbreviated as "...", but in reality, coordinate information indicating the location, such as latitude and longitude information, is stored.

[0044] The "reservation number" is identification information uniquely assigned to a user's request for dispatch. For example, when the dispatch application server device 11 receives a request for dispatching a taxi from a user and an acceptance of the request from the taxi, the dispatch application server device 11 generates a "reservation number" and stores it in the order management DB 112e. In the illustrated example, identification information such as "reservation 134" and "reservation 135" are stored as the "reservation number".

[0045] The taxi dispatch application server device 11 adds and modifies information to the order management DB 112e at various times, such as when a user requests a taxi dispatch, when the driving route is determined in advance, when the fare is confirmed in advance, or when the request is accepted by the taxi.

[0046] Although not shown in FIG. 6, the order management DB 112e may store information such as the payment method, coupons used, whether the advance fee has been canceled, boarding date and time, disembarking date and time, and the paid fee.

[0047] 7 is a schematic diagram showing an example of the configuration of the vehicle dispatch history DB 12. The vehicle dispatch history DB 12 according to this embodiment is a database in which information such as "reservation number", "date and time", "user ID", "taxi ID", "actual travel route", "paid fare", "actual boarding time", "actual boarding position", "actual drop-off position", "cancellation", "payment method", "coupon", and "discount" are stored in association with each other.

[0048] The "reservation number" is identification information uniquely assigned to a user's dispatch request. The information stored in the order management DB112e and the information stored in the dispatch history DB12 are linked by the "reservation number". The "date and time" is, for example, information such as the date and time when the user requested a taxi dispatch, and in the illustrated example, information such as "2020 / 1 / 20 11:12" and "2020 / 1 / 20 11:26" is stored. The "user ID" is the ID of the user who used the taxi, and in the illustrated example, information such as "user 123" and "user 054" is stored. The "taxi ID" is identification information uniquely assigned to a taxi, and in the illustrated example, information such as "taxi A33" and "taxi D21" is stored as the taxi ID of the taxi used by the user.

[0049] The "actual driving route" is information about the route actually traveled by the taxi carrying the user. In this figure, the information about the driving route is abbreviated as "...", but the "actual driving route" can be a collection of coordinate information of the current location of the taxi transmitted from the taxi terminal device 21. The "payment fee" is the fee finally paid (paid) by the user after using the taxi, and in the illustrated example, information such as "1234 yen" and "3210 yen" is stored. Note that the "advance fee" and the "payment fee" are basically the same amount, but for example, when a discount such as a discount for the disabled is applied after the advance fee is determined, or when a toll road fee is added, the "advance fee" and the "payment fee" may be different amounts.

[0050] The "actual boarding time" is information about the time when the user boarded the taxi. For example, when the user boards the taxi and the driver performs an operation to change the taxi from a pick-up state to a hire state on the taxi terminal device 21 or the fare meter 22, the taxi terminal device 21 notifies the ride-allocation application server device 11 of the boarding time, and in response to this notification, the ride-allocation application server device 11 can store information in the "actual boarding time" in the ride-allocation history DB 12. The "actual boarding position" is the position where the user actually boarded the taxi. The "actual drop-off position" is the position where the user actually got off the taxi. The ride-allocation application server device 11 stores information about the "actual boarding position" and the "actual drop-off position" in the ride-allocation history DB 12 based on the taxi status information and position information, etc., obtained from the taxi terminal device 21. In this figure, the information about the "actual boarding position" and the "actual drop-off position" is abbreviated as "...", but in reality, coordinate information indicating a point, such as latitude and longitude information, is stored. Furthermore, if information on the "actual boarding location" and the "actual disembarking location" can be obtained from the above-mentioned "actual driving route," the dispatch history DB12 does not need to include the items "actual boarding location" and "actual disembarking location."

[0051] "Cancellation" is information indicating whether the user has cancelled the "advance fare" and "preliminary driving route" that were previously determined. In the illustrated example, the information "No" is stored, indicating that cancellation has not occurred. For example, if the user changes the destination, the "advance fare" and "preliminary driving route" are cancelled, and the information "Yes" is stored in "Cancellation"

[0052] "Payment method" is information about the method used by the user to pay the fare. In the illustrated example, "credit" information is stored, which indicates that the user paid by credit card. "Coupon" is information about the content of the coupon used by the user for the fare. In the illustrated example, "100 yen discount" information, which subtracts 100 yen from the fare, and "none" information, which indicates that the coupon was not used, are stored. In this embodiment, discounts from coupons are reflected in the "advance fare". "Discount" is information about discounts that are applied after the user gets into a taxi, such as a discount for people with disabilities. When a discount is applied, "yes" information is stored, and when a discount is not applied, "none" information is stored.

[0053] The vehicle dispatch application server device 11 adds and modifies information to the vehicle dispatch history DB12 at various times, such as when a user requests a taxi dispatch, when the user gets into the taxi, when the taxi arrives at the destination, or when the fare payment process is performed.

[0054] The communication unit 113 of the ride-dispatch application server device 11 communicates with various devices via a network N including an in-house LAN (Local Area Network), a wireless LAN, the Internet, etc. In the present embodiment, the communication unit 113 communicates with the information processing device 13, the payment server device 14, the taxi terminal device 21, the user terminal device 31, etc. via the network N. The communication unit 113 transmits data provided from the processing unit 111 to other devices, and provides data received from other devices to the processing unit 111.

[0055] The display unit 114 is configured using a liquid crystal display or the like, and displays various images, characters, and the like based on processing by the processing unit 111. The operation unit 115 accepts user operations and notifies the processing unit 111 of the accepted operations. For example, the operation unit 115 is an input device such as a mouse and a keyboard, and these input devices may be configured to be removable from the ride-hailing app server device 11. In addition, for example, the operation unit 115 may accept user operations via an input device such as a touch panel provided on the surface of the display unit 114.

[0056] The storage unit 112 may be an external storage device connected to the ride-dispatch application server device 11. The ride-dispatch application server device 11 may be a multi-computer including a plurality of computers, or may be a virtual machine virtually constructed by software. The ride-dispatch application server device 11 may not have a user interface such as the display unit 114 and the operation unit 115, and in this case, for example, an administrator or the like may operate the ride-dispatch application server device 11 via another terminal device.

[0057] In addition, in the processing unit 111 of the vehicle dispatch application server device 11 in this embodiment, the processing unit 111 reads out and executes the server program 112a stored in the memory unit 112, so that a route processing unit 111a, an order processing unit 111b, a prepayment processing unit 111c, a vehicle dispatch processing unit 111d, a payment processing unit 111e, a vehicle dispatch history processing unit 111f, a display processing unit 111g, etc. are realized as software functional units.

[0058] The route processing unit 111a performs a process of determining a driving route to be traveled by the taxi based on the desired boarding point and the destination point input by the user. The method of determining the driving route can be the same as the method of determining a driving route by an existing car navigation system, so a detailed description will be omitted. The route processing unit 111a creates multiple driving routes from the desired boarding point to the destination point as candidates, transmits the multiple candidates to the user terminal device 31, and accepts the selection of the driving route from the user. The route processing unit 111a determines one driving route selected by the user as the pre-driving route to be traveled by the taxi. However, if it is impossible to create multiple driving routes, the route processing unit 111a may create only one driving route.

[0059] The order processing unit 111b performs processing to accept a taxi dispatch order from a user by transmitting and receiving information to and from the user terminal device 31. The order processing unit 111b acquires information such as a desired boarding point and a destination point from the user via the user terminal device 31. The order processing unit 111b stores the acquired information in the order management DB 112e of the storage unit 112.

[0060] The advance fee processing unit 111c performs a process of calculating an advance fee to be paid by the user for using a taxi, based on the taxi travel route determined by the route processing unit 111a and the information of the fare calculation DB 112b stored in the storage unit 112. Since the route processing unit 111a presents a plurality of travel routes as candidates to the user, the advance fee processing unit 111c calculates an advance fee for each candidate and presents the advance fee candidates to the user. When calculating the advance fee, the advance fee processing unit 111c determines an operating company that will dispatch a taxi, for example, based on the user's desired boarding point. The advance fee processing unit 111c acquires information such as the base fare and additional fare for the determined operating company from the fare calculation DB 112b, and substitutes the acquired information into the above-mentioned formula (1). The advance fee processing unit 111c also calculates the taxi travel distance based on the travel route determined by the route processing unit 111a, and substitutes the calculated distance into the above-mentioned formula (1). As a result, the advance fee processing unit 111c can calculate the advance fee using formula (1). The advance fee processing unit 111c presents the calculated advance fee to the user, and finalizes the advance fee when the user performs an operation to approve the advance fee, etc. Once the advance fee has been finalized, the user cannot change the fee.

[0061] After the advance fee processing unit 111c has determined the advance fee, the dispatch processing unit 111d performs processing to dispatch a taxi to the requesting user. The dispatch processing unit 111d refers to the taxi DB 112d in the storage unit 112, selects a taxi that is, for example, available and whose current location is close to the user's desired boarding point, and requests dispatch to the taxi terminal device 21 of the selected taxi. The taxi terminal device 21 of the selected taxi notifies the driver that the dispatch request has been received, and accepts from the driver a selection operation of whether or not to accept the request. If the request is accepted, the dispatch processing unit 111d notifies the user terminal device 31 of the user who made the dispatch request that the dispatch request has been accepted. Based on this notification, the user terminal device 31 displays on the display unit 314 that the dispatch request has been accepted. As a result, a reservation for taxi use is established between the taxi and the user, and the taxi picks up the user toward the desired boarding point and transports the user to the destination according to the determined driving route. If the dispatch request is not accepted, the dispatch processing unit 111d selects another taxi and requests the dispatch of the taxi. In addition, the dispatch processing unit 111d may request the dispatch of a taxi to another taxi without waiting for a response to the dispatch request, for example, if the taxi driver does not respond within a predetermined time from the dispatch request.

[0062] The dispatch processing unit 111d also performs processing related to cancellation from the taxi 2 that has accepted the dispatch request. In the taxi information processing system according to the present embodiment, the taxi driver can cancel the acceptance of the dispatch request when it becomes difficult to go to the desired boarding point designated by the user due to various factors such as an accident or breakdown. When the taxi terminal device 21 accepts a cancellation operation from the driver, it notifies the dispatch application server device 11 of the cancellation. The dispatch processing unit 111d of the dispatch application server device 11 that has received the cancellation notification notifies the user terminal device 31 of the user related to the canceled dispatch request of the cancellation. The user terminal device 31 that has received the cancellation notification displays on the display unit 314 that the dispatch request has been canceled. This cancels the reservation that was once established between the user and the taxi. The user may then make a new dispatch request.

[0063] The payment processing unit 111e performs a payment process for the fare between the user who used the taxi by relaying the information exchange between the taxi terminal device 21 and the payment server device 14. The payment processing unit 111e acquires the payment fare, the payment method, and other information necessary for payment from the taxi terminal device 21, and requests the payment server device 14 managed and operated by a payment company to perform the payment process. In response to this request, the payment server device 14 performs a process to settle the taxi usage fare for this user, and notifies the vehicle dispatch application server device 11 of the completion of the payment process. When the payment processing unit 111e is notified of the completion of the payment process by the payment server device 14, it transmits this notification to the taxi terminal device 21.

[0064] The dispatch history processing unit 111f performs a process of storing information obtained in a series of steps related to the user's use of a taxi in the order management DB 112e or the dispatch history DB 12 of the storage unit 112. For example, when a user performs an operation to approve a travel route and a prepayment fee on the user terminal device 31, the dispatch history processing unit 111f stores information such as date and time information and a user ID at that time in the order management DB 112e or the dispatch history DB 12. For example, when a taxi driver performs an operation to accept a dispatch request on the taxi terminal device 21, the dispatch history processing unit 111f stores the taxi ID of the taxi in the order management DB 112e or the dispatch history DB 12. For example, the dispatch history processing unit 111f periodically acquires location information from a taxi carrying a passenger, and stores the acquired location information as an actual travel route. For example, when a taxi arrives at a destination and payment of the fee is completed, the dispatch history processing unit 111f stores the payment fee. The timing of storing information by the dispatch history processing unit 111f and the contents of the stored information are merely examples and are not limiting.

[0065] The display processing unit 111g performs a process of displaying various information stored in the order management DB 112e and the dispatch history DB 12 on the display unit 114. The display processing unit 111g accepts, for example, the designation of date and time and a taxi ID, etc., through the operation unit 115, and reads out information corresponding to the designated date and time and the taxi ID, etc., from the order management DB 112e and the dispatch history DB 12. Based on the read out information, the display processing unit 111g can display, for example, a map image on the display unit 314, and display the preliminary driving route and the actual driving route superimposed on the map image. The display processing unit 111g may also display the advance fee and the payment fee together with these driving routes. The display of the information stored in the order management DB 112e and the dispatch history DB 12 may be performed in any manner. In the present embodiment, the dispatch application server device 11 displays the information stored in the dispatch history DB 12 on its own display unit 314, but is not limited thereto, and may display information on the display unit of another device through communication via a network.

[0066] 8 is a block diagram showing a configuration of a user terminal device 31 according to this embodiment. The user terminal device 31 according to this embodiment is a portable information processing device such as a smartphone or a tablet terminal device. The user terminal device 31 is configured to include a processing unit 311, a memory unit (storage) 312, a communication unit (transceiver) 313, a display unit (display) 314, an operation unit 315, a GPS receiving unit 316, and the like. The processing unit 311 is configured using an arithmetic processing device such as a CPU or MPU, a ROM, and a RAM, and the like. The processing unit 311 reads out and executes a program 312a stored in the storage unit 312 to perform various processes related to a taxi dispatch request, and the like.

[0067] The storage unit 312 is configured using a non-volatile memory element such as a flash memory. The storage unit 312 stores various programs executed by the processing unit 311 and various data required for the processing of the processing unit 311. In this embodiment, the storage unit 312 stores a program 312a executed by the processing unit 311 and a user ID 312b assigned to the user who is the owner of the user terminal device 31.

[0068] The program 312a according to this embodiment is an application program (app) for using a taxi. In this embodiment, the program 312a is distributed by a remote server device or the like, and the user terminal device 31 acquires the program 312 through communication and stores it in the storage unit 312. However, the program 312a may be written in the storage unit 312, for example, during the manufacturing stage of the user terminal device 31. For example, the program 312a may be read by the user terminal device 31 from a recording medium such as a memory card or an optical disk and stored in the storage unit 312. For example, the program 312a may be read by a writing device from a recording medium and written to the storage unit 312 of the user terminal device 31. The program 312a may be provided in a form of distribution via a network, or in a form of being recorded on a recording medium.

[0069] The user ID 312b is an identifier that uniquely identifies the user who owns the user terminal device 31, and is determined, for example, when the user downloads the program 312a to the user terminal device 31 or when the user uses the downloaded program 312a for the first time, and is stored in the storage unit 312. The user ID 312b may be, for example, an ID dedicated to the taxi information processing system according to this embodiment, or may be a general-purpose ID such as the user's email address.

[0070] The communication unit 313 communicates with various devices via a network N including a public mobile phone communication network, the Internet, etc. In the present embodiment, the communication unit 313 communicates with the ride-dispatch application server device 11 via the network N. The communication unit 313 transmits data provided from the processing unit 311 to the ride-dispatch application server device 11, and provides data received from the ride-dispatch application server device 11 to the processing unit 311.

[0071] The display unit 314 is configured using a liquid crystal display or the like, and displays various images, characters, and the like based on processing by the processing unit 311. The operation unit 315 accepts user operations via an input device, such as a mechanical button or a touch panel provided on the surface of the display unit 314, and notifies the processing unit 311 of the accepted operation. The GPS receiving unit 316 receives radio waves transmitted from a GPS satellite, and provides information contained in the received radio waves to the processing unit 311. The processing unit 311 can perform processing to identify the position (e.g., latitude and longitude) of the user terminal device 31 based on the information provided from the GPS receiving unit 316.

[0072] In addition, in the user terminal device 31 according to this embodiment, the processing unit 311 reads and executes the program 312a stored in the storage unit 312, so that the display processing unit 311a, the dispatch request unit 311b, the approval receiving unit 311c, and the like are realized in the processing unit 311 as software-like functional units. The display processing unit 311a performs processing to display various screens related to dispatching a taxi on the display unit 314. For example, the display processing unit 311a performs various screen displays such as a menu screen, a screen for inputting a desired boarding point and a destination point, a screen presenting information on a taxi's travel route and advance fee, and a screen indicating completion of a taxi dispatch request. Image data and the like for displaying these screens are stored in the storage unit 312 together with the program 312a.

[0073] The dispatch request unit 311b performs processing related to a taxi dispatch request. The dispatch request unit 311b accepts the designation of a desired boarding point and a destination point from the user on an input screen displayed by the display processing unit 311a. The dispatch request unit 311b transmits a taxi dispatch request including the accepted information on the desired boarding point and the destination point and the user ID 312b stored in the storage unit 312 to the dispatch application server device 11. The desired boarding point may be, for example, a current position based on a GPS signal received by the GPS receiving unit 316, or may be, for example, a specific place or facility designated by the user. The dispatch application server device 11 determines the taxi travel route and calculates the advance fare according to the desired boarding point and the destination point given together with the dispatch request.

[0074] The approval receiving unit 311c performs a process of receiving the user's approval for the taxi driving route and advance fee determined in response to the taxi dispatch request. Information on the taxi driving route and advance fee determined by the taxi dispatch application server device 11 in response to the taxi dispatch request is received by the user terminal device 31, and is displayed on the display unit 314 by the display processing unit 311a. The approval receiving unit 311c receives the user's approval for the displayed taxi driving route and advance fee through the operation unit 315, and notifies the taxi dispatch application server device 11 of the approval. In addition, when the taxi dispatch application server device 11 has created multiple driving routes and advance fees as candidates, the display unit 314 displays multiple candidates, and the approval receiving unit 311c accepts the selection of one driving route and advance fee from the multiple candidates, and notifies the taxi dispatch application server device 11 of the selected driving route and advance fee as being approved. In addition, when the user performs an operation to not approve the driving route and advance fee, the approval receiving unit 311c notifies the taxi dispatch application server device 11 of the cancellation of the taxi dispatch request. In addition, if the user does not approve the advance driving route and advance fare, the system may be configured to allow a taxi dispatch request to be made using normal fare calculation (calculation of fare based on distance traveled using a taxi meter).

[0075] 9 is a block diagram showing the configuration of the payment server device 14 according to the present embodiment. The payment server device 14 according to the present embodiment is configured to include a processing unit 141, a memory unit (storage) 142, a communication unit (transceiver) 143, and the like. The processing unit 141 is configured using an arithmetic processing device such as a CPU, an MPU, or a GPU, a ROM, and the like. The processing unit 141 reads out and executes a server program 142a stored in the memory unit 142, thereby performing various processes related to the payment processing of the taxi fare by the user.

[0076] The storage unit 142 is configured using a large-capacity storage device such as a hard disk. The storage unit 142 stores various programs executed by the processing unit 141 and various data necessary for the processing of the processing unit 141. In this embodiment, the storage unit 142 stores a server program 142a executed by the processing unit 141. The storage unit 142 also includes a payment DB 142b that stores information necessary for payment processing.

[0077] In this embodiment, the server program 142a is provided in a form recorded on a recording medium 98 such as a memory card or an optical disk, and the payment server device 14 reads the server program 142a from the recording medium 98 and stores it in the storage unit 142. However, the server program 142a may be written in the storage unit 142, for example, during the manufacturing stage of the payment server device 14. In addition, for example, the server program 142a may be distributed by another remote server device or the like and acquired by the payment server device 14 through communication. For example, the server program 142a may be read from the recording medium 98 by a writing device and written to the storage unit 142 of the payment server device 14. The server program 142a may be provided in a form distributed via a network, or may be provided in a form recorded on the recording medium 98.

[0078] FIG. 10 is a schematic diagram showing an example of the configuration of the payment DB 142b. The payment DB 142b according to this embodiment is a database in which information such as "credit card ID", "expiration date", "balance", and "limit" are stored in association with each other. "Credit card ID" is identification information given to a credit card, and may be a so-called card number. "Expiration date" is information on the period during which a credit card can be used. "Balance" and "limit" are information on credit card usage restrictions, and for example, a "limit" is set to 300,000 yen per month, and the "balance" is the value obtained by subtracting the amount used from this limit.

[0079] The communication unit 143 of the payment server device 14 communicates with various devices via a network N including an in-house LAN, a wireless LAN, the Internet, etc. In the present embodiment, the communication unit 143 communicates with the vehicle-dispatch application server device 11, etc. via the network N. The communication unit 143 transmits data provided from the processing unit 141 to other devices, and provides data received from other devices to the processing unit 141.

[0080] The storage unit 142 may be an external storage device connected to the payment server device 14. The payment server device 14 may be a multi-computer including a plurality of computers, or may be a virtual machine virtually constructed by software. The payment server device 14 is not limited to the above configuration, and may include, for example, a reading unit that reads information stored in a portable storage medium, an operation unit that accepts operation input, or a display unit that displays images.

[0081] In addition, in the processing unit 141 of the payment server device 14 according to the present embodiment, the processing unit 141 reads and executes the server program 142a stored in the storage unit 142, whereby the confirmation processing unit 141a, the payment processing unit 141b, and the like are realized as software functional units. The confirmation processing unit 141a performs a process of confirming information required for the user who uses a taxi to pay the fare in response to a payment request from the ride-dispatch application server device 11. The confirmation processing unit 141a acquires information such as a credit card ID and a payment fee provided together with the payment request from the ride-dispatch application server device 11, and refers to the payment DB 142b in the storage unit 142 to confirm whether the acquired information is correct and whether the payment can be made. The payment processing unit 141b performs a process of paying the taxi fare by the user with a registered credit card when the confirmation processing unit 141a determines that the payment is possible.

[0082] FIG. 11 is a block diagram showing the configuration of the taxi terminal device 21 according to the present embodiment. The taxi terminal device 21 according to the present embodiment may be, for example, a device fixed near the driver's seat of the taxi 2, or may be, for example, a device that the driver can carry, such as a smartphone or a tablet-type terminal device. The taxi terminal device 21 is configured to include a processing unit 211, a memory unit (storage) 212, a communication unit (transceiver) 213, a display unit (display) 214, an operation unit 215, a GPS receiving unit 216, and the like. The processing unit 211 is configured using an arithmetic processing device such as a CPU or MPU, a ROM, and a RAM, and the like. The processing unit 211 reads out and executes a program 212a stored in the storage unit 212 to perform various processes related to the acceptance of a dispatch request from a user and the cancellation of an accepted dispatch request.

[0083] The storage unit 212 is configured using a non-volatile memory element such as a flash memory. The storage unit 212 stores various programs executed by the processing unit 211 and various data required for the processing of the processing unit 211. In this embodiment, the storage unit 212 stores a program 212a executed by the processing unit 211 and a taxi ID 212b assigned to the taxi 2.

[0084] In this embodiment, the program 212a is distributed by a remote server device or the like, and the taxi terminal device 21 acquires the program 212 through communication and stores it in the storage unit 212. However, the program 212a may be written in the storage unit 212, for example, during the manufacturing stage of the taxi terminal device 21. For example, the program 212a may be read by the taxi terminal device 21 from a recording medium such as a memory card or an optical disk and stored in the storage unit 212. For example, the program 212a may be read by a writing device from a recording medium and written to the storage unit 212 of the taxi terminal device 21. The program 212a may be provided in the form of distribution via a network, or in the form of being recorded on a recording medium.

[0085] The taxi ID 212b is an identifier that uniquely identifies the taxi 2, and is determined in advance by an operating company that manages the taxi 2, and is stored in the storage unit 212. In this embodiment, an identifier given to the taxi 2 is used as the taxi ID 212b, but, for example, an identifier given to the driver of the taxi 2 may be used as the taxi ID 212b.

[0086] The communication unit 213 communicates with various devices via a network N including a public mobile phone communication network and the Internet. In this embodiment, the communication unit 213 communicates with the vehicle dispatch application server device 11 provided externally, and also communicates with the fare meter 22 and the passenger terminal device 23 provided in the taxi 2. The communication unit 213 may communicate with the vehicle dispatch application server device 11 and with the fare meter 22 and the passenger terminal device 23 according to different communication protocols. For example, the communication unit 213 communicates with the vehicle dispatch application server device 11 through communication via a public mobile phone communication network. For example, the communication unit 213 communicates with the fare meter 22 and the passenger terminal device 23 through wired communication via a communication line provided in the taxi 2, or wireless communication such as Bluetooth (registered trademark).

[0087] The display unit 214 is configured using a liquid crystal display or the like, and displays various images, characters, and the like based on the processing of the processing unit 211. The operation unit 215 accepts the driver's operation through an input device such as a mechanical button or a touch panel provided on the surface of the display unit 214, and notifies the processing unit 211 of the accepted operation. The GPS receiving unit 216 receives radio waves transmitted from a GPS satellite, and provides information contained in the received radio waves to the processing unit 211. The processing unit 211 can perform processing to identify the position (e.g., latitude and longitude) of the taxi terminal device 21 based on the information provided from the GPS receiving unit 216. In addition, the communication unit 213 relays communication between the vehicle dispatch application server device 11 and the fare meter 22 and passenger terminal device 23.

[0088] In addition, in the taxi terminal device 21 according to this embodiment, the processing unit 211 reads and executes the program 212a stored in the storage unit 212, whereby the display processing unit 211a, the acceptance receiving unit 211b, the cancellation receiving unit 211c, and the like are realized in the processing unit 211 as software-like functional units. The display processing unit 211a performs processing to display various screens related to the dispatch request for the taxi 2 on the display unit 214. For example, the display processing unit 211a performs various screen displays such as a menu screen, a screen presenting information on a travel route and an advance fee related to the dispatch request from the user, and a screen for accepting operations such as the acceptance or cancellation of the dispatch request. Image data and the like for displaying these screens are stored in the storage unit 212 together with the program 212a.

[0089] The display processing unit 211a also communicates with the fare meter 22 and the passenger terminal device 23 provided in the taxi 2 via the communication unit 213, thereby causing the fare meter 22 and the passenger terminal device 23 to perform various displays. The display processing unit 211a performs a process of displaying the advance fare on the fare meter 22, for example, by transmitting information about the confirmed advance fare to the fare meter 22. The display processing unit 211a also performs a process of displaying the payment fare on the passenger terminal device 23, for example, by transmitting information about the payment fare to the passenger terminal device 23 after the taxi 2 has arrived at the destination.

[0090] The acceptance reception unit 211b performs a process of receiving an operation related to the acceptance of a vehicle dispatch request from a user. The display processing unit 211a of the taxi terminal device 21 that receives a vehicle dispatch request from a user from the vehicle dispatch application server device 11 displays detailed information related to the vehicle dispatch request, i.e., information such as the user's desired boarding point and destination point, the determined driving route, and the confirmed advance fare, on the display unit 214. While this information is being displayed, the acceptance reception unit 211b receives a selection of whether or not to accept the vehicle dispatch request from the driver via the operation unit 215. The acceptance reception unit 211b notifies the vehicle dispatch application server device 11 of the selection result of whether or not to accept the vehicle dispatch request.

[0091] The cancellation reception unit 211c performs a process of receiving a cancellation operation for the accepted dispatch request. After the acceptance reception unit 211b accepts the dispatch request, the display processing unit 211a displays information such as the user's desired boarding point on the display unit 214, and prompts the driver to drive the taxi 2 to the desired boarding point. In this state, the cancellation reception unit 211c receives a cancellation operation for the dispatch request. When the cancellation operation is received, the cancellation reception unit 211c notifies the dispatch application server device 11 of the cancellation of the dispatch request.

[0092] 12 is a block diagram showing the configuration of the fare meter 22 and passenger terminal device 23 according to this embodiment. The fare meter 22 according to this embodiment is a device mounted, for example, near the driver's seat of the taxi 2, and displays the fare for using the taxi 2. The fare meter 22 is configured to include a processing unit 221, a communication unit (transceiver) 222, a display unit (display) 223, and an operation unit 224.

[0093] The processing unit 221 is configured using an arithmetic processing device such as a CPU or an MPU, a ROM, and a RAM. The processing unit 221 performs various processes related to the display of fares and the reception of operations by the driver. Although not shown, a sensor mounted on the taxi 2 is connected to the fare meter 22, and the fare of the taxi 2 can be calculated according to the travel distance measured by the sensor.

[0094] The communication unit 222 communicates with the taxi terminal device 21 and the passenger terminal device 23 by wired communication via a communication line arranged in the taxi 2 or by wireless communication such as Bluetooth. The display unit 223 is configured using a liquid crystal panel or the like, and displays various images, characters, and the like based on the processing of the processing unit 221. The operation unit 224 accepts operations by the driver using an input device such as a mechanical button, and notifies the processing unit 221 of the accepted operation.

[0095] In this embodiment, in the case of normal operation in which a pre-determined fare is not determined, the fare meter 22 displays on the display unit 223 the fare that is added according to the distance traveled, time, etc. When a pre-determined fare is determined, the fare meter 22 does not display the fare that is added according to the distance traveled, time, etc., but displays the pre-determined advance fare on the display unit 223. When displaying the advance fare, the fare meter 22 can determine whether or not a pre-determined fare has been determined and the determined advance fare, for example, by exchanging information with the taxi terminal device 21 via the communication unit 222. When displaying the advance fare, the fare meter 22 may or may not calculate the fare according to the distance traveled, time, etc.

[0096] The operation unit 224 is provided with, for example, a switch for switching between displaying the advance fare and the normal fare, a button for starting the payment process after arriving at the destination, and a button for applying discounts such as a discount for persons with disabilities. In response to an operation to start the payment process, the payment fare is displayed on the passenger terminal device 23, and in response to an operation of a discount button, the discount is applied and the payment fare displayed on the passenger terminal device 23 is updated.

[0097] The passenger terminal device 23 according to this embodiment is a terminal device mounted at a location visible to a user sitting in the back seat of the taxi 2. The passenger terminal device 23 may be a device fixedly provided in the taxi 2, or may be a portable device such as a tablet terminal device. In this embodiment, the passenger terminal device 23 is provided on the back of the driver's seat of the taxi 2. The passenger terminal device 23 is configured to include a processing unit (processor) 231, a communication unit (transceiver) 232, a display unit (display) 233, and an operation unit 234.

[0098] The processing unit 231 is configured using an arithmetic processing device such as a CPU or an MPU, a ROM, a RAM, etc. The processing unit 231 performs various processes such as displaying the fare to the user who used the taxi, accepting operations necessary for payment of this fare, and performing payment processing according to the accepted operations.

[0099] The communication unit 232 communicates with the taxi terminal device 21 and the fare meter 22 by wired communication via a communication line provided in the taxi 2, or by wireless communication such as Bluetooth. The display unit 233 is configured using a liquid crystal panel or the like, and displays various images, characters, and the like based on the processing of the processing unit 231. The operation unit 234 accepts user operations via an input device such as a touch panel provided on the surface of the display unit 233, and notifies the processing unit 231 of the accepted operation.

[0100] After the user gets in the taxi 2, the passenger terminal device 23 may display, for example, an image such as an advertisement on the display unit 233 while the taxi 2 arrives at the destination. After the taxi 2 arrives at the destination, the passenger terminal device 23 displays the payment fare based on the information on the payment fare provided by the taxi terminal device 21 or the fare meter 22. The payment fare displayed by the passenger terminal device 23 is either a pre-determined advance fare or a fare calculated according to the distance traveled and time, and when a discount such as a discount for a person with a disability is applied to these fares, the display is updated to the discounted payment fare. After displaying the payment fare, the passenger terminal device 23 accepts an operation of approval for the payment process from the user. When the approval operation is accepted, the passenger terminal device 23 transmits the approval operation to the vehicle dispatch application server device 11 via the taxi terminal device 21.

[0101] When the taxi 2 arrives at the destination and the payment fee is displayed on the passenger terminal device 23, and the payment fee is approved by the user, the payment server device 14 performs the payment process. When the passenger terminal device 23 obtains the approval of the payment, it notifies the ride-dispatch application server device 11 of the approval via the taxi terminal device 21. The ride-dispatch application server device 11 transmits the user ID of the user performing the payment process and the information stored in the "payment information" of the user DB 112c to the payment server device 14. The payment server device 14 performs the payment process by credit card, electronic money, etc. based on the information received from the ride-dispatch application server device 11.

[0102] <Taxi fare processing> Fig. 13 is a schematic diagram for explaining the process from requesting dispatch to confirming dispatch by the taxi information processing system according to this embodiment. In the taxi information processing system according to this embodiment, a user who requests dispatch must download the program 312a to the user terminal device 31 and must also complete procedures for using this system (such as agreeing to the terms of use and registering personal information) in advance. In the following description, it is assumed that these procedures have been completed, and detailed explanations of these procedures will be omitted.

[0103] A user who wishes to use a taxi starts the program 312a on his / her user terminal device 31 and selects an item for requesting a vehicle dispatch from, for example, a menu screen. The user terminal device 31 displays a screen for specifying a desired boarding point and a destination point for using a taxi on the display unit 314, and accepts input of the desired boarding point and the destination point from the user. The desired boarding point is set to the current location as an initial value, and if the user does not change it, the current location based on the GPS signal received by the GPS receiving unit 316 is accepted as the desired boarding point. The destination point may be, for example, a result of a search based on the name of a place or building, or may be, for example, an address or a postal code, or may be, for example, an input specifying a point on a map, or may be accepted in a manner other than these. When a desired boarding point other than the current location is specified, it may be input in the same manner as the destination point. The user terminal device 31 transmits a message of a vehicle dispatch request including the input desired boarding point and destination point and the user ID 312b of the user to the vehicle dispatch application server device 11.

[0104] The vehicle dispatch application server device 11, which has received a vehicle dispatch request message from the user terminal device 31, determines a taxi company that will dispatch a taxi to the user based on the desired boarding point and destination point included in the vehicle dispatch request message. The vehicle dispatch application server device 11 selects a taxi company that can dispatch a taxi to the desired boarding point by, for example, comparing the desired boarding point included in the vehicle dispatch request message with the "area" information in the fare calculation DB 112b shown in FIG. 3.

[0105] Next, the vehicle dispatch application server device 11 determines the driving route of the taxi based on the desired boarding point and the destination point included in the message of the vehicle dispatch request. The vehicle dispatch application server device 11 also calculates the advance fee for using a taxi based on the determined driving route and the fee calculation DB 112b of the storage unit 112. It is preferable that the vehicle dispatch application server device 11 presents a plurality of driving routes and advance fees as candidates to the user. For example, the vehicle dispatch application server device 11 may determine two driving routes as candidates, a driving route using a toll road and a driving route not using a toll road. In the present embodiment, the fee for using a toll road is not included in the advance fee, but this is not limited thereto, and the fee for the toll road may be included in the advance fee. The vehicle dispatch application server device 11 also refers to the user DB 112c of the storage unit 112 based on the user ID included in the message of the vehicle dispatch request, and if the user has a discount coupon or the like, obtains information on the coupon and calculates the advance fee to which the discount of the obtained coupon is applied. The vehicle-dispatch application server device 11 transmits a message including information on the determined travel route and the calculated advance fare to the user terminal device 31 of the user who made the request.

[0106] The user terminal device 31, which has received the message from the ride-dispatch application server device 11, displays the information on the driving route and the advance fare included in the message on the display unit 314, and accepts an operation of approval for the driving route and the advance fare from the user. At this time, if there are multiple candidates for the driving route and the advance fare, the user terminal device 31 displays information on the multiple candidates, accepts an operation from the user to select one of these candidates, and accepts an operation of approval for the selected candidate driving route and advance fare from the user.

[0107] 14 is a schematic diagram showing an example of a vehicle dispatch request screen displayed by the user terminal device 31. The illustrated vehicle dispatch request screen is based on the assumption that two candidates, route 1 and route 2, are provided to the user terminal device 31 from the vehicle dispatch application server device 11 as candidates for the driving route and advance fee. The user terminal device 31 displays a map image on the display unit 314, and also displays two candidates for the driving route as route 1 and route 2 superimposed on the map image. In this figure, the desired boarding point is indicated by "S", the destination point is indicated by "G", route 1, which is the first candidate for the driving route, is indicated by a solid line, and route 2, which is the second candidate, is indicated by a dashed line.

[0108] In the area below the map image on the dispatch request screen, information on two candidates is displayed on the left and right. In this example, information on "route 1" is displayed on the left area, and information on "route 2" is displayed on the right area. In the left area, the character string "route 1" is displayed, and below this character string, the character string "advance fee 11200 yen" indicating the calculated advance fee, and further below that, a button labeled "request dispatch" is displayed. In addition, in the right area, the character string "route 2" is displayed, and below this character string, the character string "advance fee 13000 yen" is displayed, and further below that, a button labeled "request dispatch". By performing a touch operation or the like on either one of the two "request dispatch" buttons provided side by side at the bottom of the dispatch request screen, the user can select one of the two presented routes.

[0109] When the user terminal device 31 receives a touch operation on either of the two "Request a vehicle dispatch" buttons, it determines that the user has approved the driving route and advance fee for the corresponding route, and transmits a message notifying the user that the driving route and advance fee have been approved to the vehicle dispatch application server device 11. Note that the vehicle dispatch request screen shown in the figure does not assume that an operation to not approve the presented driving route and advance fee is accepted, but it may be configured to accept, for example, an operation to reject the presented driving route and advance fee and request a vehicle dispatch at a fee using a fare meter.

[0110] The vehicle-dispatch application server device 11, which has received a message approving the travel route and the advance fare from the user terminal device 31, selects, for example, a taxi that is available and located closest to the desired boarding point from among a plurality of taxis registered in the taxi DB 112d of the storage unit 112. The vehicle-dispatch application server device 11 transmits a vehicle-dispatch request message including information on the travel route and the advance fare, and information on the user who is the requester, to the taxi terminal device 21 of the selected taxi.

[0111] The taxi terminal device 21, which has received a dispatch request message from the dispatch application server device 11, displays the information on the driving route and advance fee included in this message on the display unit 214, and accepts an operation from the driver to accept the dispatch request for this driving route and advance fee. FIG. 15 is a schematic diagram showing an example of a dispatch request acceptance screen displayed by the taxi terminal device 21. The taxi terminal device 21 displays a map image on the display unit 214, and also displays the driving route superimposed on this map image. In this figure, the user's desired boarding point is indicated by "S", the destination point is indicated by "G", the current location of the taxi is indicated by "current", and the driving route is indicated by a solid line.

[0112] The taxi terminal device 21 displays information regarding the dispatch request below the map image. In this figure, the taxi terminal device 21 displays the following information regarding the user: "Requester: User A", the following information regarding the payment method of the fare: "Payment method: Credit card", the following information regarding the discount coupon: "Discount coupon: 100 yen discount", and the following information regarding the confirmed advance fare: "Advance fare 11,200 yen". However, the taxi terminal device 21 does not have to notify the taxi driver of the advance fare. In other words, the taxi terminal device 21 may request dispatch without notifying the taxi driver whether the advance fare is based on the advance fare or the fare is calculated using the fare meter 22.

[0113] The taxi terminal device 21 displays a button labeled "Accept" below these pieces of information. The taxi terminal device 21 accepts the driver's acceptance of the user's dispatch request by accepting a touch operation or the like on the "Accept" button. The taxi terminal device 21 that has accepted the acceptance transmits a message notifying the driver that the dispatch request is accepted to the dispatch application server device 11. The dispatch application server device 11 receives the message notifying the acceptance from the taxi terminal device 21 and transmits a similar message to the user terminal device 31. The user terminal device 31 that has received this message displays a message notifying the user that the dispatch request made by the user has been accepted on the display unit 314. Note that the dispatch request acceptance screen shown in this figure is not intended to accept an operation not to accept the dispatch request, but may be configured to be capable of accepting, for example, an operation to reject the presented dispatch request. In addition, if the advance fare is not notified to the taxi driver on the dispatch request acceptance screen, the taxi terminal device 21 may display information such as whether the dispatch request has a confirmed advance fare or not, and if the advance fare has been confirmed, the amount, after receiving the acceptance operation from the driver.

[0114] FIG. 16 is a schematic diagram for explaining the cancellation process of a dispatch request by the taxi information processing system according to the present embodiment. The driver of the taxi who accepted the dispatch request from the user drives the taxi to the desired boarding point designated by the user. In the present embodiment, after accepting the dispatch request from the user, the taxi terminal device 21 displays a screen for accepting the cancellation of the accepted dispatch request on the display unit 214 before getting the user into the taxi. For example, if the taxi driver is unable to head to the desired boarding point due to an accident or breakdown, the taxi terminal device 21 can perform a cancellation operation. The taxi terminal device 21 that has accepted the cancellation operation transmits a message to the dispatch application server device 11 notifying the user that the dispatch request is to be cancelled. The dispatch application server device 11 receives the message notifying the user of the cancellation from the dispatch application server device 11 and transmits a similar message to the user terminal device 31. The user terminal device 31 that has received this message displays a message notifying the user that the dispatch request has been cancelled on the display unit 314.

[0115] FIG. 17 is a schematic diagram showing an example of a cancellation acceptance screen displayed by the taxi terminal device 21. In this embodiment, the configuration of the cancellation acceptance screen displayed by the taxi terminal device 21 is almost the same as the configuration of the dispatch request acceptance screen shown in FIG. 15. The cancellation acceptance screen displays, as information related to the accepted dispatch request, a map image showing the travel route, information related to the user, information related to the payment method, information related to discount coupons, and information related to the advance fee. However, as shown in FIG. 17, at the bottom of the cancellation acceptance screen, a button labeled "Cancel" is provided instead of the "Accept" button on the dispatch request acceptance screen shown in FIG. 15. The taxi driver can cancel the accepted dispatch request by performing a touch operation on this button. The taxi terminal device 21 accepts the cancellation of the accepted dispatch request in response to a touch operation on the "Cancel" button on the cancellation acceptance screen.

[0116] After the taxi arrives at the desired boarding point without canceling the dispatch request, the user gets into the taxi, and the driver drives the taxi to the destination. At this time, the driver may perform a predetermined operation on the taxi terminal device 21 or the fare meter 22, for example, to notify the dispatch application server device 11 that the user has boarded the taxi. The taxi terminal device 21 notifies the fare meter 22 of the advance fare determined in advance. The fare meter 22 does not display the fare that is added at any time depending on the taxi's travel distance, time, etc., but displays the advance fare notified by the taxi terminal device 21.

[0117] After the taxi carrying the passenger arrives at the destination, the user needs to pay (settle) the taxi fare. The passenger terminal device 23 of the taxi displays a payment screen and accepts a process related to the payment of the taxi fare from the user. FIG. 18 is a schematic diagram showing an example of a payment screen displayed by the passenger terminal device 23. On the payment screen, the passenger terminal device 23 displays, for example, information on "Payment method: Credit card" as the payment method of the fare and information on "Discount coupon: 100 yen discount" as the applied coupon, and also displays "Payment fee 11200 yen" as the payment fee, which is the advance fee determined in advance. The passenger terminal device 23 may also display the taxi's travel route on the payment screen by superimposing it on a map image. The travel route displayed at this time may be a travel route determined in advance, may be a travel route actually traveled by the taxi, or may display both of them superimposed.

[0118] The passenger terminal device 23 displays a button labeled "Pay" below this information. The passenger terminal device 23 receives a touch operation or the like on the "Pay" button, thereby receiving approval for the payment process for the displayed payment fare from the user. After receiving approval for the payment process from the user, the taxi information processing system performs the payment process.

[0119] 19 is a schematic diagram for explaining the payment process by the taxi information processing system according to this embodiment. The vehicle dispatch application server device 11 transmits information about the advance fare to the taxi terminal device 21 of the taxi that accepted the dispatch request, and the taxi terminal device 21, which receives this information, transmits the information about the advance fare to the fare meter 22 and the passenger terminal device 23. Based on the information received from the taxi terminal device 21, the fare meter 22 and the passenger terminal device 23 each display the advance fare. The fare meter 22 and the passenger terminal device 23 continue to display the advance fare until the taxi arrives at the destination.

[0120] When a taxi carrying a passenger arrives at the destination, the taxi driver can start the payment process by operating a payment button provided on the operation unit 224 of the fare meter 22. When the fare meter 22 accepts the payment operation on the operation unit 224, it transmits a message notifying the same to the taxi terminal device 21. The taxi terminal device 21 notifies the passenger terminal device 23 that the payment operation has been accepted. The passenger terminal device 23 displays the advance fare as the payment fare, and displays a payment screen (see FIG. 18) on the display unit to accept an approval operation for the payment from the user.

[0121] The passenger terminal device 23, which has received approval of the payment process from the user on the payment screen, transmits a message notifying approval of the payment process to the taxi terminal device 21. The taxi terminal device 21, which has received this message, transmits a message notifying approval of the payment, including information on the user and information such as the payment fee, to the vehicle-dispatch application server device 11.

[0122] The ride-dispatch application server device 11, which has been notified of the payment approval from the taxi terminal device 21, refers to the user DB 112c to acquire information on the payment method and the like registered for the user who will pay the fare. For example, the ride-dispatch application server device 11 acquires information on the company and card number of the credit card used by the user for payment. The ride-dispatch application server device 11 transmits a payment request including information on the card number, the fare, and the like to the payment server device 14 of the company of the credit card used for payment.

[0123] The payment server device 14 performs a payment process using a credit card, electronic money, or the like, based on information from the ride-dispatch application server device 11. Details of the payment process by the payment server device 14 will not be described here. After the payment process is completed, the payment server device 14 notifies the ride-dispatch application server device 11 of the completion of payment. The ride-dispatch application server device 11 notifies the taxi terminal device 21 of the completion of payment, and stores information about this ride-dispatch in the order management DB 112e and the ride-dispatch history DB 12 of the storage unit 112. The taxi terminal device 21 notifies the passenger terminal device 23 of the completion of the payment process, and the passenger terminal device 23 displays a message or the like indicating that the payment process has been completed on the display unit 233.

[0124] In this embodiment, the user can request the application of a discount, such as a discount for persons with disabilities, after the taxi arrives at the destination. After checking a certificate or the like showing eligibility for the discount, the taxi driver can apply the discount to the payment fare by operating a discount application button provided on operation unit 224 of fare meter 22. Although not shown in FIG. 19, if an additional fee, such as a toll road fee, is required, the taxi driver performs a predetermined operation related to the additional fee on taxi terminal device 21 or fare meter 22. This operation applies the payment fare in which the additional fee has been added to the advance fee.

[0125] In Figure 19, the processing for applying this discount (and additional charges, etc.) is shown surrounded by a dashed line. When the fare meter 22 accepts a discount operation at the operation unit 224, it sends a message to the taxi terminal device 21 informing that effect. Upon receiving this message, the taxi terminal device 21 calculates the payment fare by applying the discount to the advance fare that has been determined in advance, and sends a message informing the calculated payment fare to the fare meter 22 and the passenger terminal device 23. Upon receiving this message, the fare meter 22 displays the newly calculated payment fare. Upon receiving this message, the passenger terminal device 23 updates the payment fare that was displayed on the payment screen to the payment fare included in the newly received message, and applies the discount.

[0126] In this embodiment, for example, if the user requests a change of destination point before arriving at the destination point after the advance fare has been confirmed and the user gets into the taxi, the user pays the advance fare that was confirmed in advance regardless of whether the user has arrived at the destination point or not. For example, when the user verbally requests a destination point, the taxi driver stops the taxi and operates the operation unit 224 of the fare meter 22 to start the advance fare payment process. The payment procedure in this case is the same as that shown in Figures 18 and 19. After the payment process is completed, the taxi driver starts driving to the changed destination point, and the fare at this time is added according to the travel distance, time, etc. However, the driving route from the current location to the new destination point and the advance fare may be confirmed.

[0127] In addition, when operating a taxi with a prepaid fare, consent is required between the taxi driver and the passenger user when changing the destination or route. However, for some reason, consent cannot be obtained, and a situation may arise in which it is difficult to settle the prepaid fare on the spot. In such a case, the prepaid fare may be cancelled, and a fare based on, for example, the distance traveled and time traveled so far may be calculated and settled. For this reason, even when the taxi is traveling with a prepaid fare, the fare meter 22 calculates the fare based on the distance traveled and time traveled by the taxi in the background.

[0128] <Flowchart> Fig. 20 is a flowchart showing the procedure of the process performed by the user terminal device 31 according to the present embodiment. The display processing unit 311a of the processing unit 311 of the user terminal device 31 according to the present embodiment displays a location input reception screen for receiving input of a desired boarding location and a destination from a user who wishes to dispatch a taxi on the display unit 314 (step S1). Next, the dispatch request unit 311b of the processing unit 311 receives input of the desired boarding location and the destination based on the user's operation received by the operation unit 315 while the location input reception screen is displayed (step S2). The dispatch request unit 311b transmits a dispatch request message including the received desired boarding location and the destination, and the user ID 312b stored in the storage unit 312 to the dispatch application server device 11 (step S3).

[0129] The approval receiving unit 311c of the processing unit 311 judges whether or not a message including information such as a driving route and an advance fee, which is sent by the vehicle dispatch application server device 11 in response to the vehicle dispatch request sent in step S3, has been received (step S4). If a message has not been received (S4: NO), the approval receiving unit 311c waits until a message is received. If a message including information such as a driving route and an advance fee has been received (S4: YES), the display processing unit 311a displays the vehicle dispatch request screen illustrated in FIG. 14 on the display unit 314 based on the information included in the received message (step S5). The approval receiving unit 311c accepts an operation to select a taxi driving route and approve the advance fee based on a user operation accepted by the operation unit 315 while the vehicle dispatch request screen is displayed (step S6). The approval receiving unit 311c transmits a message to the vehicle dispatch application server device 11 notifying that the driving route and the advance fee included in the message received in step S4 have been approved (step S7).

[0130] The processing unit 311 determines whether or not a message notifying the completion of acceptance of the dispatch request has been received (step S8). If the acceptance completion notification has not been received (S8: NO), the processing unit 311 waits until the acceptance completion notification is received. If the acceptance completion message has been received (S8: YES), the display processing unit 311a displays a message notifying the completion of acceptance of the dispatch request on the display unit 314 (step S9), and ends the process.

[0131] 21 and 22 are flowcharts showing the procedure of processing performed by the vehicle dispatch application server device 11 according to this embodiment. The processing unit 111 of the vehicle dispatch application server device 11 according to this embodiment determines whether or not a message requesting dispatch of a taxi has been received from the user terminal device 31 (step S21). If the message requesting dispatch has not been received (S21: NO), the processing unit 111 waits until the message requesting dispatch is received.

[0132] When a message for requesting dispatch is received (S21: YES), the processing unit 111 checks whether or not a taxi can be used with a prepaid fare based on the desired boarding point or destination point included in the received message (step S22). For example, if the taxi company that has jurisdiction over the desired boarding location does not support prepaid fare, the user cannot use a taxi with a prepaid fare. If a taxi cannot be used with a prepaid fare, the processing unit 111 interrupts the processing according to this flowchart and performs a conventional dispatch process for using a taxi with a fare according to the distance traveled. Note that the conventional dispatch process is not shown in this figure.

[0133] If a taxi can be used with a prepayment fare, the processing unit 111 determines a taxi company to dispatch a taxi based on the desired boarding point or destination point included in the dispatch request message received from the user terminal device 31 (step S23). Next, the route processing unit 111a of the processing unit 111 determines a taxi driving route based on the desired boarding point and destination point included in the received message (step S24). The route processing unit 111a may determine a plurality of driving routes as candidates. Next, the prepayment processing unit 111c of the processing unit 111 calculates a prepayment fare for each driving route based on the taxi driving route determined in step S24 and the fare calculation DB 112b of the storage unit 112 (step S25). At this time, the prepayment processing unit 111c determines a taxi operating company based on the desired boarding point, and can calculate the prepayment fare by substituting a numerical value determined in the fare calculation DB 112b in association with the operating company and the distance of the driving route determined in step S24 into the above-mentioned formula (1). In addition, the advance fare processing unit 111c may check whether the user who requested the vehicle dispatch has a discount coupon by referring to the user DB 112c, and if the user has a discount coupon, may obtain information regarding the discount coupon from the user DB 112c and calculate the advance fare applying the discount related to the obtained coupon.

[0134] The processing unit 111 transmits a message including information on the travel route determined in step S24 and the advance fee calculated in step S25 to the user terminal device 31 that made the dispatch request (step S26). The processing unit 111 judges whether or not an approval message for this message has been received from the user terminal device 31 (step S27). If the approval message is not received (S27: NO), for example, if a message to cancel the dispatch request is received or if an approval message is not received even after a certain period of time has passed, the processing unit 111 discards the dispatch request and ends the process.

[0135] When the approval message is received (S27: YES), the dispatch processing unit 111d of the processing unit 111 selects one taxi from among the multiple taxis registered in the taxi DB 112d of the storage unit 112 (step S28). At this time, the dispatch processing unit 111d can select a taxi that is located closest to the desired boarding point included in the received dispatch request message and is available. The dispatch processing unit 111d transmits a dispatch request message including information on the user, the travel route, the advance fare, and the like to the taxi terminal device 21 of the selected taxi (step S29).

[0136] The dispatch processing unit 111d judges whether or not a message notifying the acceptance of the dispatch request transmitted in step S29 has been received (step S30). If the message accepting the dispatch request is not received (S30: NO), for example, if a message notifying the rejection of the dispatch request is received, or if the message accepting is not received even after a certain time has passed, the dispatch processing unit 111d returns the process to step S28 and repeats the selection of a taxi and the transmission of the dispatch request message. If a message accepting the dispatch request is received (S30: YES), the dispatch processing unit 111d transmits a message notifying the acceptance of the dispatch request to the user terminal device 31 that made the dispatch request (step S31). The dispatch history processing unit 111f of the processing unit 111 stores information such as date and time, user ID, taxi ID, driving route, and advance fee for the accepted dispatch request in the order management DB 112e and the dispatch history DB 12 of the storage unit 112 (step S32).

[0137] After that, the processing unit 111 judges whether or not a message notifying the cancellation of the dispatch request has been received from the taxi terminal device 21 of the taxi that accepted the dispatch request (step S33). If a cancellation message has been received (S33: YES), the processing unit 111 transmits a message notifying the cancellation, including information such as the taxi ID of the taxi related to the cancellation, to the user terminal device 31 (step S34), and ends the process.

[0138] If a message notifying cancellation has not been received (S33: NO), the processing unit 111 judges whether or not a message notifying approval of payment has been received from the taxi terminal device 21 (step S35). If a message of payment approval has not been received (S35: NO), the processing unit 111 returns the process to step S33 and waits until a message of cancellation or payment approval is received. If a message of payment approval has been received (S35: YES), the payment processing unit 111e of the processing unit 111 transmits the payment fee and information related to the user to the payment server device 14, and requests the payment server device 14 to perform payment processing for the taxi fare (step S36).

[0139] Thereafter, the payment processing unit 111e judges whether or not a notice of payment completion has been received from the payment server device 14 (step S37). If the notice of payment completion has not been received (S37: NO), the payment processing unit 111e waits until the notice of payment completion is received. If the notice of payment completion is received (S37: YES), the payment processing unit 111e notifies the taxi terminal device 21 of the completion of payment (step S38). The dispatch history processing unit 111f of the processing unit 111 stores information on the user and taxi who performed the payment process, such as the actual driving route and the payment fee, in the order management DB 112e and the dispatch history DB 12 (step S39), and ends the process.

[0140] 23 and 24 are flowcharts showing the procedure of the process performed by the taxi terminal device 21 according to the present embodiment. The acceptance receiving unit 211b of the processing unit 211 of the taxi terminal device 21 according to the present embodiment judges whether or not a message of a dispatch request has been received from the dispatch application server device 11 (step S71). If a message of a dispatch request has not been received (S71: NO), the acceptance receiving unit 211b waits until a message is received. If a message of a dispatch request has been received (S71: YES), the display processing unit 211a of the processing unit 211 displays the dispatch request acceptance screen exemplified in FIG. 15 on the display unit 214 based on the information included in the received message of the dispatch request (step S72).

[0141] The acceptance reception unit 211b judges whether the dispatch request has been accepted based on the operation received by the operation unit 215 while the dispatch request acceptance screen is displayed (step S73). If the dispatch request has not been accepted (S73: NO), that is, if the dispatch request has been rejected, the acceptance reception unit 211b transmits a message to the dispatch application server device 11 notifying that the dispatch request has been rejected (step S74) and ends the process. If the dispatch request has been accepted (S73: YES), the acceptance reception unit 211b transmits a message to the dispatch application server device 11 notifying that the dispatch request has been accepted (step S75).

[0142] The display processing unit 211a displays a cancellation reception screen on the display unit 214 to receive an operation to cancel the dispatch request (step S76). The cancellation reception unit 211c of the processing unit 211 determines whether the dispatch request has been canceled based on an operation received by the operation unit 215 while the cancellation reception screen is displayed (step S77). If the dispatch request has been canceled (S77: YES), the cancellation reception unit 211c transmits a message to the dispatch application server device 11 notifying that the dispatch request has been canceled (step S78), and ends the process.

[0143] If the dispatch request has not been canceled (S77: NO), the processing unit 211 determines, through communication with the fare meter 22, whether or not an operation to start the payment process has been performed on the operation unit 224 of the fare meter 22 (step S79). If an operation to start the payment process has not been performed (S79: NO), the processing unit 221 waits until this operation is performed. If an operation to start the payment process has been performed (S79: YES), the display processing unit 211a causes the passenger terminal device 23 to display the payment fare by transmitting information on the payment fare (advance fare) to the passenger terminal device 23 (step S80).

[0144] The processing unit 211 determines whether or not a discount operation has been performed on the operation unit 224 of the fare meter 22 through communication with the fare meter 22 (step S81). If a discount operation has been performed (S81: YES), the processing unit 211 applies the discount to the payment fare displayed on the passenger terminal device 23 in step S80, and updates the display to the payment fare after the discount has been applied (step S82). Although not shown in Fig. 24, when adding toll road tolls, etc., the fare can be added to the payment fare (advance fare) in a similar manner in response to an operation performed by the driver on the fare meter 22 or taxi terminal device 21.

[0145] If no discount operation has been performed (S81: NO), or after updating the payment fare by applying the discount in step S82, the processing unit 211 determines, through communication with the passenger terminal device 23, whether or not the passenger terminal device 23 has accepted an approval operation for the payment process for the displayed payment fare (step S83). If the approval operation has not been accepted (S83: NO), the processing unit 211 returns the process to step S81. If the approval operation has been accepted (S83: YES), the processing unit 211 transmits a message to the ride-dispatch application server device 11 notifying that approval for the payment process for the displayed payment fare has been accepted (step S84), and ends the process.

[0146] <Information storage processing> The vehicle-dispatch application server device 11 according to the present embodiment performs a process of storing and accumulating various information related to dispatching of a taxi as history in the order management DB 112e and the vehicle-dispatch history DB 12, for example, in steps S32 and S39 of the flowcharts shown in Figures 21 and 22. The vehicle-dispatch application server device 11 may accumulate information at various times other than the above.

[0147] 6 and 7, the vehicle-dispatch application server device 11 stores information such as the date and time related to the dispatch of a taxi (the date and time when the dispatch request was accepted, the date and time when the user got into the taxi, or the date and time when the payment process was completed, etc.), the user ID, the taxi ID, the advance driving route, the advance fare, the actual driving route, and the payment fare in the order management DB 112e and the vehicle-dispatch history DB 12. However, the information stored by the vehicle-dispatch application server device 11 in the order management DB 112e and the vehicle-dispatch history DB 12 is not limited to the above, and may store various information such as, for example, whether or not the taxi driver canceled the taxi, whether or not the user canceled the taxi, or images of the inside and outside of the taxi taken by a camera mounted on the taxi.

[0148] 25 is a flowchart for explaining an example of information accumulation processing performed by the vehicle-dispatch application server device 11 according to the present embodiment. When a vehicle-dispatch history processing unit 111f of the processing unit 111 of the vehicle-dispatch application server device 11 according to the present embodiment receives a taxi dispatch request from the user terminal device 31 (step S101), the vehicle-dispatch history processing unit 111f stores the date and time of receiving the vehicle-dispatch request, the user ID transmitted together with the vehicle-dispatch request, the taxi boarding reservation time, the boarding reservation location, and the disembarking reservation location, and the reservation number generated by the vehicle-dispatch application server device 11 in the order management DB 112e (step S102).

[0149] When the advance fee for the use of a taxi is determined (step S103), the dispatch history processing unit 111f stores the determined advance route and advance fee in the order management DB 112e (step S104). When the dispatch request is accepted by the taxi driver (step S105), the dispatch history processing unit 111f stores the reservation number, date and time, user ID, and taxi ID in the dispatch history DB 12 (step S106).

[0150] When the dispatch history processing unit 111f is notified by the taxi terminal device 21 that the user has boarded a taxi (step S107), it stores the actual boarding time and actual boarding position in the dispatch history DB 12 (step S108). When the dispatch history processing unit 111f is notified by the taxi terminal device 21 that the user has arrived at the destination (step S109), it stores the actual driving route, the paid fare, and the actual drop-off position in the dispatch history DB 12 (step S110).

[0151] When the payment process is performed (step S111), the dispatch history processing unit 111f stores the cancellation or non-cancellation, the payment method, the use or non-use of a coupon, and the discount or non-discount in the dispatch history DB 12 (step S112), and ends the process.

[0152] The timing of storing information by the vehicle-dispatch application server device 11 and the type of information to be stored are not limited to those shown in the figure. The vehicle-dispatch application server device 11 may store appropriate information in the order management DB 112e or the vehicle-dispatch history DB 12 at appropriate timing.

[0153] The vehicle-dispatch application server device 11 according to the present embodiment performs a process of displaying information stored in the order management DB 112e and the vehicle-dispatch history DB 12 on the display unit 114. For example, an administrator who manages this system can operate the operation unit 115 of the vehicle-dispatch application server device 11 to select one of the multiple histories stored in the vehicle-dispatch history DB 12 and display the information of the selected history on the display unit 114. In addition, for example, an employee of a taxi company can access the vehicle-dispatch application server device 11 using the information processing device 13 to display the same history information on the display unit of the information processing device 13.

[0154] Fig. 26 is a schematic diagram showing an example of a dispatch history screen displayed by the information processing device 13 of a taxi company, which is displayed based on information acquired by the information processing device 13 from the dispatch application server device 11. The illustrated dispatch history screen assumes that the history for 11:12 on January 20, 2020, included in the order management DB 112e shown in Fig. 6 and the dispatch history DB 12 shown in Fig. 7 has been selected by the administrator.

[0155] In the dispatch history screen of this example, the information processing device 13 displays the character string "January 20, 2020 11:12" as the date and time information of the history as the title at the top. The information processing device 13 displays the predetermined taxi driving route and the route actually traveled by the taxi superimposed on the map image below this title. In this figure, the boarding point where the user boarded the taxi is indicated by "S", and the disembarking point is indicated by "G". The boarding point may be either the desired boarding point input by the user or the point where the user actually boarded the taxi, and if these are different, they may be displayed superimposed on the map image so as to be distinguishable from each other. The disembarking point may be either the destination point input by the user or the point where the user actually disembarked from the taxi, and if these are different, they may be displayed superimposed on the map image so as to be distinguishable from each other. In this figure, the predetermined taxi driving route is indicated by a solid line as a "pre-planned route", and the route actually traveled by the taxi that is different from the pre-planned route is indicated by a dashed line as an "actual route".

[0156] The information processing device 13 displays various information related to dispatching a taxi next to a map image showing a travel route. In this example, information on "Taxi A33" as the taxi ID of the taxi, information on "User 123" as the user ID of the passenger, information on "Discount coupon 100 yen discount" as the coupon used, information on "Advance fee 1234 yen" as the advance fee determined in advance, information on "Payment method credit card" as the payment processing method, and information on "Payment fee 1134 yen" as the paid fee are displayed in a vertical line.

[0157] The information processing device 13 also displays a button labeled "Contact Customer" at the bottom right of the dispatch history screen. This button is for sending a message by e-mail or the like to the user who used the taxi. When a mouse click operation or a touch operation on a touch panel or the like is received on this button, the information processing device 13 displays a message input screen (not shown) and receives the input of the message. The information processing device 13 transmits the input message to the dispatch application server device 11. The dispatch application server device 11 transmits the message received by the information processing device 13 to the user terminal device 31 of the user who used the taxi, based on information such as the user ID stored in the dispatch history DB 12 and the e-mail address stored in the user DB 112c. The dispatch application server device 11 also stores information such as the content of the message sent to the user and the transmission date and time in the dispatch history DB 12 or the like.

[0158] The vehicle dispatch application server device 11 according to the present embodiment can store various information related to dispatching a taxi in the order management DB 112e and the dispatch history DB 12, and display the stored information on the display unit 114. This allows, for example, information on a location where a difference between a previously determined driving route and an actually traveled driving route frequently occurs to be used as a reference for improving a method of determining a previous driving route. In addition, for example, it is expected that an appropriate response can be made based on the stored history information in response to questions or complaints from a user who has used a taxi. Note that the vehicle dispatch history screen shown in FIG. 26 is an example, and is not limited thereto, and the information to be displayed and the display mode of the information can be appropriately changed.

[0159] <Summary> The vehicle-dispatch application server device 11 of the taxi information processing system according to the present embodiment configured as described above determines a driving route based on a desired boarding point and a destination point of a user who wishes to board a taxi, and determines an advance fare for a taxi ride based on the determined driving route. The vehicle-dispatch application server device 11 transmits information on the determined driving route and the determined advance fare to the user terminal device 31 and the taxi terminal device 21, thereby causing the user terminal device 31 and the taxi terminal device 21 to display the driving route and the advance fare. The vehicle-dispatch application server device 11 also stores information including the determined driving route and the determined advance fare in the order management DB 112e and the vehicle-dispatch history DB 12.

[0160] This allows the user to use a taxi at a fare determined in advance, rather than a fare that is added up depending on the distance traveled and time, etc. The user can check the taxi's travel route and advance fare in advance on the user terminal device 31 that the user owns. The taxi driver can accept the dispatch request after checking the travel route and advance fare on the taxi terminal device 21. In addition, since the dispatch application server device 11 stores and accumulates information regarding taxi dispatch in the order management DB 112e and the dispatch history DB 12, the information regarding the route traveled by the taxi and the paid fare, etc. can be confirmed after the fact.

[0161] In addition, the fare meter 22 of the taxi terminal system 20 provided in the taxi 2 according to this embodiment displays the confirmed advance fare while the user is in the taxi. This allows the user to easily check the fare to be paid while in the taxi.

[0162] Furthermore, the vehicle-dispatch application server device 11 according to the present embodiment stores a predetermined driving route and a driving route actually traveled by a taxi in association with each other in the order management DB 112e and the vehicle-dispatch history DB 12. This allows a system administrator or the like to later confirm whether or not a taxi has traveled the predetermined driving route.

[0163] Furthermore, the vehicle-dispatch application server device 11 according to this embodiment acquires information on discount coupons owned by the user from the user DB 112c, and determines the advance fare based on the acquired information on the discount coupons and the determined travel route. The taxi terminal device 21 of the taxi terminal system 20 acquires information on the presence or absence of discounts such as a discount for persons with disabilities by accepting a discount operation at the operation unit 224 of the fare meter 22, and calculates a payment fare with the discount applied to the advance fare. As a result, for discount coupons that do not require confirmation of a certificate or the like, the advance fare with the discount applied in advance can be presented to the user, and for discounts such as a discount for persons with disabilities that require confirmation of a certificate or the like, the taxi 2 can apply them.

[0164] Furthermore, the taxi terminal system 20 according to this embodiment displays the payment fare calculated by the taxi terminal device 21 after applying the discount on the passenger terminal device 23 provided at the rear of the taxi. This allows the user who gets in the taxi to easily check the payment fare after applying the discount.

[0165] Furthermore, the vehicle-dispatch application server device 11 according to this embodiment stores the fare calculation standard for each taxi operating company in the fare calculation DB 112b of the storage unit 112. The vehicle-dispatch application server device 11 determines the operating company of the taxi to be dispatched according to the desired boarding point input by the user, and determines the advance fare based on the fare calculation standard of the determined operating company. This makes it possible to dispatch taxis of multiple operating companies with different fare calculation standards to the user.

[0166] In addition, in the taxi information processing system according to the present embodiment, when a request to change the previously determined driving route is received from the user after the user gets in the taxi, a payment process for the previously determined advance fare is performed, and the taxi heads to the changed destination after the payment process is completed. This makes it possible to reliably pay the previously determined advance fare.

[0167] Furthermore, in the taxi information processing system according to the present embodiment, the taxi driver can cancel the dispatch request at the taxi terminal device 21 during the period from after the advance fare has been determined until the user gets into the taxi. When the taxi terminal device 21 accepts a cancellation operation, the taxi terminal device 21 notifies the user terminal device 31 of the cancellation via the dispatch application server device 11. This allows the user terminal device 31 to reliably inform the user that the dispatch request has been canceled.

[0168] (Variation 1) FIG. 27 is a schematic diagram showing an example of the configuration of the fare calculation DB 112b according to the first modification. The fare calculation DB 112b according to the first modification is obtained by adding information on a long-distance discount to the fare calculation DB 112b shown in FIG. 3. The fare calculation DB 112b according to the first modification stores information on the long-distance discount, such as a "criterion" and a "coefficient", in association with a taxi operating company. In the present embodiment, the long-distance discount is performed by multiplying the fare added thereafter by a predetermined coefficient when the mileage of the taxi exceeds a predetermined distance or the fare exceeds a predetermined amount. The "criterion" of the fare calculation DB 112b is a predetermined distance or a predetermined amount for determining whether or not to apply the long-distance discount. The "coefficient" is a value by which the fare added after the fare exceeds the criteria.

[0169] The ride-dispatch application server device 11 according to the first modification determines a travel route from the desired boarding point and the destination point input by the user, and calculates an advance fare based on the determined travel route. At this time, when the distance of the determined travel route exceeds a predetermined distance set as a "standard", or when the calculated advance fare exceeds a predetermined amount set as a "standard", the ride-dispatch application server device 11 calculates an advance fare to which a long-distance discount is applied.

[0170] The information stored in the fee calculation DB 112b is not limited to that shown in FIG. 3 and FIG. 27, and various information used for fee calculation may be stored.

[0171] (Variation 2) In the taxi information processing system according to the above-described embodiment, for example, as shown in Fig. 3 and Fig. 27, different fare calculation standards are used for each taxi operating company, but this is not limited to this. For example, the same fare calculation standard may be used for multiple taxi operating companies, and in this case, the user will pay the same advance fare regardless of which operating company the user uses for the taxi.

[0172] In addition, some of the "minimum fare," "minimum distance," "additional unit," "additional fare," and "coefficient" included in the fare calculation DB 112b shown in Fig. 3 and Fig. 27 may be the same among multiple operating companies. For example, the same value of "coefficient" may be used among multiple taxi operating companies, and different values ​​may be used for the other items such as the "minimum fare."

[0173] <Embodiment 2> The taxi information processing system according to the second embodiment is a system that allows a user to select a taxi when there are multiple taxis available for a prepaid fee. The vehicle dispatch application server device 11 of the taxi information processing system according to the second embodiment accepts an input of a desired boarding point and a destination point at a user terminal device 31, and then determines a driving route from the desired boarding point to the destination point. At this time, the vehicle dispatch application server device 11 calculates multiple driving route candidates under different conditions, such as distance priority and expressway priority, and accepts the selection of the driving route from the user via the user terminal device 31.

[0174] Fig. 28 is a schematic diagram showing an example of a driving route selection screen displayed by the user terminal device 31 according to the embodiment 2. As with the dispatch request screen shown in Fig. 14, the driving route selection screen shown in Fig. 28 presents two driving route candidates to the user, for example, a driving route candidate calculated with priority given to general roads as "Route 1 (general dominance)" and a driving route candidate calculated with priority given to expressways as "Route 2 (highway priority)".

[0175] The vehicle dispatch application server device 11 determines a taxi company (taxi operating company) that can be dispatched to the user based on information such as the desired boarding point and destination point input by the user, information on the "area" included in the fare calculation DB 112b, and information on vacant taxis located near the desired boarding point, and determines the advance fare based on the fare calculation standard of the determined taxi company. In the taxi information processing system according to the second embodiment, it is permitted that taxis of multiple taxi companies run in one area and that the advance fare calculation standard differs for each taxi company. Therefore, the vehicle dispatch application server device 11 calculates advance fares for all taxi companies available to the user for each candidate travel route, transmits information on the minimum (lowest price) and maximum (highest price) of the calculated advance fares to the user terminal device 31, and causes the user to present the range of advance fares. In the example shown in FIG. 28, a range of 11200 yen to 11800 yen is shown as the advance fare for route 1, and a range of 11600 yen to 12000 yen is shown as the advance fare for route 2. In this example, when route 2 is selected, the text "separate toll passage fee applies", indicating that a separate fee is required for using toll roads such as expressways, is displayed together with the advance fee for route 2. Although not shown in the example, information such as the expected travel time or arrival time at the destination for each route may be further displayed. In addition, for route 2, an approximate fee for using toll roads, for example, may be displayed, or an advance fee including the toll road fee, for example, may be displayed.

[0176] The user can select one of multiple candidate driving routes displayed on the user terminal device 31. In the lower area of ​​the illustrated driving route selection screen, information on route 1 and route 2, which are candidate driving routes, are displayed on the left and right, and a button labeled "Select this route" is provided below the information on each route. The user can select the corresponding driving route by performing an operation such as touching or tapping on any of the "Select this route" buttons. The user terminal device 31 accepts the user's selection of a driving route by accepting an operation on any of the buttons, and notifies the vehicle dispatch application server device 11 of the selection result.

[0177] The vehicle-dispatch application server device 11, which has accepted the selection of a driving route by the user via the user terminal device 31, transmits information relating to the selected driving route and the calculated advance fare, etc. to the user terminal device 31 to display it. Figures 29 and 30 are schematic diagrams showing examples of information display screens displayed by the user terminal device 31 according to the second embodiment. Note that Figure 29 shows a case where route 1 is selected on the screen in Figure 28, and Figure 30 shows a case where route 2 is selected.

[0178] The user terminal device 31 displays a map image on the top of the information display screen, and displays the driving route selected by the user superimposed on this map image. In this figure, the user's desired boarding point is indicated by "S", the destination point is indicated by "G", and the driving route is indicated by a solid line. The user terminal device 31 also displays a substantially rectangular message display area on the top of the map image. In this message display area, the user terminal device 31 displays, for example, the amount of the advance fee and information on fees that may be added other than the advance fee. In FIG. 29, information "11200 yen to 11800 yen, additional pick-up fee" is displayed. In FIG. 30, information "11600 yen to 12000 yen, additional paid passage fee and pick-up fee" is displayed.

[0179] Also, a button labeled "route selection" is provided in the lower right corner of the map image. When an operation on the "route selection" button is accepted, the user terminal device 31 displays the driving route selection screen shown in Fig. 28 and accepts the selection of a driving route by the user. This allows the user to reselect a driving route.

[0180] The user terminal device 31 displays, below the map image, for example, information about the taxi company, information about the destination, information about the payment method, etc. In this example, the user terminal device 31 displays that "all taxis" that can be dispatched are set as the information about the taxi company, and that the taxi is scheduled to arrive in about 1 to 3 minutes.

[0181] In addition, when the user wants to use a specific taxi company, the taxi company that calculates the advance fare and requests dispatching can be specified and set in advance. When the user terminal device 31 accepts an operation on a button labeled "Specify taxi company", it displays a taxi company selection screen (not shown) and accepts the selection of a taxi company. The taxi company selection screen can be, for example, a list of taxi company names, and the user terminal device 31 accepts the selection of one taxi company from the list and notifies the taxi dispatch application server device 11 of the accepted taxi company. In addition, each taxi company listed on the taxi company selection screen is displayed with information indicating whether or not a taxi can be used with an advance fare, for example, a label or icon with the character string "Advance fare compatible". This allows the user to easily determine which taxi company is compatible with the advance fare system. When the taxi dispatch application server device 11 accepts the selection of a taxi company by the user, it limits the targets of the advance fare calculation and dispatching to the selected taxi company. The vehicle-dispatch application server device 11 may set the selected taxi company as a default setting for the target of future advance fare calculation, vehicle dispatch, and the like for this user.

[0182] The user terminal device 31 also displays destination information, such as the address of the destination entered by the user, for example, "Destination: Shibuya-ku, Tokyo...." The user terminal device 31 also displays payment method information, such as the fact that a credit card is set as the payment method, and that payment of the fee in advance is set.

[0183] The user terminal device 31 displays a button labeled "Select a taxi" below this information. When the user terminal device 31 accepts an operation on the "Select a taxi" button, it notifies the ride-dispatch application server device 11 of this fact. In response, the ride-dispatch application server device 11 transmits information about dispatchable taxis to the user terminal device 31, and causes the user terminal device 31 to display a taxi selection screen that accepts the user's selection of a taxi.

[0184] 31 is a schematic diagram showing an example of a taxi selection screen displayed by the user terminal device 31 according to embodiment 2. The taxi selection screen of this example has an area for displaying a message to the user at the top, one or more areas for options for selecting a taxi are provided below that, and a button labeled "Call a taxi" is provided at the bottom.

[0185] In this example, messages such as "Which taxi would you like to call?", "Fare may vary due to additional charges or discounts", and "Coupons are applied when you get off the taxi" are displayed in the topmost area of ​​the taxi selection screen. Note that these messages are merely examples and are not limiting, and any message may be displayed on the taxi selection screen. Coupons may also be applied at other times, such as when getting on the taxi.

[0186] Each rectangular area provided as an option on the taxi selection screen contains information such as the advance fare, the estimated time until the ride, one or more taxi company icons, and radio buttons for accepting selections. In this example, three options are shown for the advance fare: 11,200 yen, 11,500 yen, and 11,800 yen, but the number of options displayed may be one, two, or four or more.

[0187] In the illustrated example, information on the estimated time until boarding a taxi is displayed after the advance fare in each option, for example, "Board in about 2 to 5 minutes", "Board in about 2 to 7 minutes", and "Board in about 1 minute". For example, the ride-hailing application server device 11 acquires information on taxis existing near the user's desired boarding point from the information processing device 13 of each taxi company, and calculates the estimated time until boarding a taxi based on the distance between the location of each taxi and the user's desired boarding point. The ride-hailing application server device 11 transmits the calculated estimated time information for each taxi to the user terminal device 31, and the user terminal device 31 can receive this information and display the estimated time until boarding a taxi on the taxi selection screen. Note that the estimated time information does not have to be displayed on the taxi selection screen.

[0188] In the taxi information processing system according to the present embodiment, the advance fare is calculated according to a calculation standard determined for each taxi company, and there may be a plurality of taxi companies with the same calculated advance fare. In this case, a plurality of taxi companies with the same advance fare are grouped and displayed as one option on the taxi selection screen. In the illustrated example, one or more icons (shown as a substantially square shape with rounded corners) are displayed below the advance fare for each option. One icon represents one taxi company, and in this example, two taxi companies are grouped into the first option with an advance fare of 11,200 yen, three taxi companies are grouped into the second option with an advance fare of 11,500 yen, and one taxi company is grouped into the third option with an advance fare of 11,800 yen. In this figure, each icon is represented by a plain shape, but in reality, information such as the logo or name of the taxi company is displayed on each icon.

[0189] Although not shown in the figures, when a touch operation or the like is received for any of the options, the user terminal device 31 displays detailed information regarding the calculation of the corresponding advance fare. The detailed information may, for example, display the presence or absence, type, and amount of discounts applicable to the advance fare. The detailed information may also display pick-up fees, toll passage fees, and late-night / early-morning surcharges that may be added to the advance fare. The displayed detailed information may include, for example, information such as the minimum fare and late-night surcharge coefficient used when calculating the advance fare.

[0190] The radio buttons provided for each option on the taxi selection screen are for accepting an operation to select one of the multiple options. When accepting a touch operation or the like on any one of the radio buttons, the user terminal device 31 assumes that the corresponding option has been selected and highlights the selected option to indicate that it is in a selected state. In the illustrated example, the selection of the option for advance fare of 11,200 yen is indicated by highlighting the rectangular area framed with a thick line.

[0191] The "Call a Taxi" button provided at the bottom of the taxi selection screen is for notifying the vehicle-dispatch application server device 11 of the taxi selection result. This button accepts operation when any option on the taxi selection screen is in a selected state, and does not accept operation when all options are in a non-selected state. When an operation on the "Call a Taxi" button is accepted, the user terminal device 31 transmits information on which option was selected to the vehicle-dispatch application server device 11.

[0192] In this embodiment, the vehicle-dispatch application server device 11 determines which of the multiple taxi companies grouped in the options to dispatch. For this reason, in the taxi information processing system according to the second embodiment, the user indirectly selects a taxi by selecting the advance fare for the taxi, and the final selection of the taxi is left to the vehicle-dispatch application server device 11. When the advance fare for taxis from multiple taxi companies is the same, the vehicle-dispatch application server device 11 can select taxis in order of proximity to the user's desired boarding point and attempt to dispatch the taxi to the user. The selection of a taxi company by the vehicle-dispatch application server device 11 may be based on any criteria. Alternatively, an operation to select one taxi company from the multiple taxi companies may be further received from the user at the user terminal device 31.

[0193] In addition, the processing of dispatching a taxi by the ride-dispatch application server device 11 after the result of the taxi selection is transmitted from the user terminal device 31 to the ride-dispatch application server device 11 is similar to the processing described in the previous embodiment, and therefore a detailed description of the processing is omitted in embodiment 2.

[0194] 32 is a flowchart showing the procedure of processing performed by the vehicle-dispatch application server device 11 according to the second embodiment. The processing unit 111 of the vehicle-dispatch application server device 11 according to the second embodiment accepts an input of a desired boarding point and a destination point by a user via the user terminal device 31 (step S201). The processing unit 111 calculates candidates for a taxi driving route from the desired boarding point to the destination point based on the accepted input of the desired boarding point and the destination point and map information, etc. (step S202). The processing unit 111 also calculates advance fares based on the fare calculation DB 112b for each of the taxi operating companies that can be dispatched to this region (step S203).

[0195] The processing unit 111 transmits the calculated information on the driving route and advance fee to the user terminal device 31, thereby causing the user terminal device 31 to display a driving route selection screen (see FIG. 28) (step S204). The processing unit 111 accepts the selection of a driving route by the user via the user terminal device 31 displaying the driving route selection screen (step S205). The processing unit 111 causes the user terminal device 31 to display an information display screen (see FIGS. 29 and 30) that displays information on the selected driving route, advance fee, etc. (step S206).

[0196] The processing unit 111 judges whether or not the user has requested a route change based on the presence or absence of an operation on a "route selection" button provided on the information display screen (step S207). If a route change request has been made (S207: YES), the processing unit 111 returns the process to step S204 and causes the user terminal device 31 to display a route selection screen and perform the above-mentioned process.

[0197] If no operation to request a route change has been performed (S207: NO), the processing unit 111 causes the user terminal device 31 to display a taxi selection screen (see FIG. 31) in response to an operation on the "select a taxi" button (step S208). The processing unit 111 accepts a selection of one advance fare from one or more advance fare options displayed on the taxi selection screen via the user terminal device 31 that has displayed the taxi selection screen (step S209). The processing unit 111 determines a taxi company according to the advance fare selected by the user, and makes a taxi dispatch request to the information processing device 13 of the taxi company (step S210), and ends the process.

[0198] The user then boards a taxi at the desired boarding point, and when getting off at the destination point, payment processing is performed based on the pre-determined fare. However, in the taxi information processing system according to this embodiment, the user can cancel the taxi operation based on the pre-determined fare between the time when the user boards a taxi at the desired boarding point and the time when the taxi arrives at the destination point, and change to operation based on the fare calculated by the taxi meter.

[0199] This change may be made, for example, when the taxi driver changes the destination point for his convenience and the user does not agree to operate the taxi at the pre-determined advance fare, or when the user arrives late at the desired pick-up point and the taxi driver charges an additional fee for waiting time. The change from the advance fare to the meter may be made for various other reasons, including when the passenger user requests a change or when the taxi driver requests a change.

[0200] When the advance fare is changed to the meter fare after the taxi starts traveling from the desired boarding point to the destination, the user pays the fare for the travel so far. At this time, for example, the user may pay the amount of the advance fare that was determined in advance, or the amount to be paid by the user may be calculated based on the distance traveled so far and the advance fare, or the user may pay a flat cancellation fee, or an amount other than these. In addition, the amount to be paid by the user when changing from the advance fare to the meter fare may be calculated based on different criteria depending on whether the change is at the request of the user or the driver of the taxi.

[0201] The taxi information processing system according to the second embodiment configured as above stores the fare calculation standard for each taxi operating company in the fare calculation DB 112b, calculates the advance fare for each operating company, accepts the selection of an advance fare by the user from among multiple advance fare, and determines the selected advance fare as the taxi advance fare. This allows the user to compare advance fares that differ for each taxi operating company and to use a taxi by selecting an advance fare that is suitable for the user.

[0202] Furthermore, the taxi information processing system according to the second embodiment displays advance fare options on the taxi selection screen, grouping operating companies with the same calculated advance fare amount, and accepts the selection of the advance fare, and also attaches information such as an icon that identifies one or more operating companies included in the group to the displayed options. This makes it possible to simplify the options when there are many operating companies, and allows the user to easily recognize which operating company the advance fare to be selected is from.

[0203] The taxi information processing system according to the second embodiment displays a plurality of route options on the route selection screen, accepts the selection of a route based on the selection of an option, and adds information on the minimum and maximum advance fare to the displayed options, allowing the user to select a route after checking the approximate fare.

[0204] In the second embodiment, the screen configurations and the like shown in FIGS. 28 to 30 are merely examples and are not limiting, and may be modified as appropriate.

[0205] Moreover, other configurations of the taxi information processing system according to the second embodiment are similar to those of the taxi information processing system according to the first embodiment, so the same reference numerals are used for similar parts and detailed description is omitted.

[0206] The embodiments disclosed herein are illustrative in all respects and should not be considered as limiting. The scope of the present invention is defined by the claims, not by the above meaning, and is intended to include all modifications within the scope and meaning equivalent to the claims. [Explanation of symbols]

[0207] 2. Taxi 3 Users 11. Vehicle dispatch application server device 12 Dispatch history DB 13. Information processing equipment 14 Payment server device 20 Taxi terminal system 21 Taxi terminal equipment 22 Fare Meter 23 Passenger terminal equipment 31 User terminal equipment 98,99 Recording media 111 Processing section 111a Route processing unit 111b Order Processing Unit 111c Advance Fee Processing Unit 111d Vehicle Dispatch Processing Unit 111e Payment Processing Unit 111f dispatch history processing unit 111g Display processing section 112 Storage section 112a Server Program 112b Fee calculation DB 112c User DB 112d Taxi DB 112e Order Management DB 113 Communications Department 114 Display section 115 Operation section 211 Processing section 211a Display processing unit 211b Acceptance Department 211c Cancellation Desk 212 Storage section 212a Program 212b Taxi ID 213 Communications Department 214 Display section 215 Operation section 216 GPS receiver 221 Processing section 222 Communications Department 223 Display section 224 Operation section 231 Processing section 232 Communications Department 233 Display section 234 Operation section 311 Processing section 311a Display processing unit 311b Dispatch Request Department 311c Approval Reception Department 312 Storage section 312a Program 312b User ID 313 Communications Department 314 Display section 315 Operation section 316 GPS receiver

Claims

1. Determine a route based on a desired boarding point and a destination point of a user who wishes to board a taxi; determining a pre-payment fare for the taxi ride based on the determined travel route; When a request to change the determined travel route is received after the user gets in the taxi, a payment process for the determined advance fee is performed. A method for processing taxi information.

2. Calculate the taxi fare based on the distance traveled, When the advance fee is cancelled, a payment process for the fee based on the calculated mileage is performed. The taxi information processing method according to claim 1.

3. Calculate the payment fee based on the confirmed advance fee, displaying the calculated payment fare on an information display device provided at the rear of the taxi; The taxi information processing method according to claim 1 or 2.

4. when a cancellation of dispatch of a taxi is received from a taxi terminal device of the taxi during the period from after the advance fare is determined until the user gets into the taxi, a cancellation is notified to a user terminal device of the user; A taxi information processing method according to any one of claims 1 to 3.

5. A user terminal device having a reception unit that receives input of information related to a desired boarding point and a destination point of a user who wishes to board a taxi; a server device having a driving route determination unit that determines a driving route of a taxi based on information related to the desired boarding point and the destination point received by the user terminal device, and a pre-payment fare determination unit that determines a pre-payment fare for the taxi ride based on the determined driving route; A taxi terminal device used by taxi drivers; Equipped with The taxi terminal device Obtaining the determined travel route and the confirmed advance fee from the server device; When a request to change the determined travel route is received after the user gets in the taxi, a payment process for the determined advance fee is performed. Taxi information processing system.

6. A taxi terminal device including a communication unit that communicates with a server device having a travel route determination unit that determines a taxi travel route based on information related to a user's desired boarding point and a destination point received by a user terminal device, and a pre-payment fare determination unit that determines a pre-payment fare related to the taxi ride based on the determined travel route, and a processing unit, The processing unit includes: Obtaining the determined travel route and the confirmed advance fee from the server device; When a request to change the determined travel route is received after the user gets in the taxi, a payment process for the determined advance fee is performed. Taxi terminal device.

7. Obtaining from the server device a route determined based on a desired boarding point and a destination point of a user who wishes to board a taxi and a confirmed advance fare; When a request to change the determined driving route is received after the user gets in the taxi, the determined advance fee is paid. A computer program that causes a computer to carry out processing.

8. A taxi terminal device having a display processing unit that displays on a display unit a travel route and a confirmed advance fare based on a desired boarding point and a destination point of a user who wishes to board a taxi; a fare display device provided in the taxi for displaying the confirmed advance fare while the user is in the taxi; an information display device provided at the rear of the taxi for displaying a payment fare calculated based on the advance fare; Equipped with the taxi terminal device performs a payment process for the confirmed advance fare when a request for changing the determined travel route is received after the user gets into the taxi; Taxi terminal system.

Images