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

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 server device, a user terminal device, and a computer program for performing processing related to calculation or payment 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 fixed when the taxi arrives at the destination, and the user pays the fixed 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 from a business, the business enters the payment amount and the customer's terminal phone number into the business's terminal, which then transmits the information to an operator server to request payment. 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 sends a payment request to an intermediary server. The intermediary server sends 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] Japanese Patent Application Publication No. 2019-153067 Summary of the Invention [Problem to be solved by the invention]

[0005] When using a traditional taxi, the user may feel uneasy because they do not know the fare they will have to pay until the taxi arrives at their 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 server device, a user terminal device, and a computer program 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 the desired boarding point and 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. [Effects of the Invention]

[0008] In accordance with one embodiment, it is expected that the user will feel at ease. [Brief explanation of the drawings]

[0009] [Figure 1] Overview of the taxi information processing system [Figure 2] Configuration of the ride-hailing app server device [Figure 3] Fee calculation database [Figure 4] User DB [Figure 5] Taxi DB [Figure 6] Order management database [Figure 7] Vehicle dispatch history database [Figure 8] User terminal device configuration [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 terminal device dispatch request acceptance screen [Figure 16] Taxi cancellation flow [Figure 17] Cancellation acceptance screen on 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 [Figure 25] Information storage processing for the ride-hailing app server device [Figure 26] Dispatch history screen [Figure 27] Fee calculation DB for variant 1 [Figure 28] Route selection screen of the second embodiment [Figure 29] Information display screen of embodiment 2 [Figure 30] Information display screen of embodiment 2 [Figure 31] Taxi selection screen according to the second embodiment [Figure 32] Processing flow of the vehicle-dispatch application server device according to the second embodiment DETAILED DESCRIPTION OF THE INVENTION

[0010] Specific examples of a taxi information processing system according to an 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] <First Embodiment> <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 is configured to include 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 simultaneous and parallel processing for multiple taxis 2 and multiple users 3, but Fig. 1 shows only one taxi 2 and one user 3.

[0012] The taxi-dispatch application server device 11 of the taxi information processing system according to this 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, taxi fare calculation processing, and the like, in cooperation with devices such as the information processing device 13 and the payment server device 14. Note that in this embodiment, the taxi-dispatch application server device 11 is a single 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 also be configured to perform some 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 this embodiment, a user 3 can use a user terminal device 31 to request the 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 dispatching a taxi is transmitted from the user terminal device 31 to the taxi-dispatch application server device 11 via a network such as a mobile phone communication network, a wireless LAN (Local Area Network), or the Internet.

[0014] The ride-dispatch application server device 11 determines a route for the taxi 2 based on the desired boarding point and destination point of the user 3, and calculates the fare for the taxi 2 to travel along this route. In the taxi information processing system according to this embodiment, the fare calculated by the ride-dispatch application server device 11 is confirmed as a prepayment fare, and the user 3 who uses the taxi 2 pays this prepayment fare. Information on the route determined by the ride-dispatch application server device 11 and the confirmed prepayment 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 routes and prepayment fare as candidates, and the user 3 may select a desired one from the plurality of candidates. Furthermore, if the user 3 has a discount coupon or the like for the fare, the ride-dispatch application server device 11 may calculate the prepayment fare by applying this discount.

[0015] In this embodiment, the amount determined in advance by the taxi information processing system is called the "advance fare," but this is just one example and may be called by various names, such as a "predetermined fare," "advance fare," "fixed fare," "predetermined fee," or "fixed fee." The "advance fare" includes the fare for the taxi trip, 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 fees such as highway tolls to the previously determined "advance fare."

[0016] A taxi 2 is dispatched when the user 3 performs an operation on the user terminal device 31 to approve the presented driving route and advance fare. The approval operation by the user 3 is transmitted 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 of determining a taxi 2 to be dispatched to the user 3. The vehicle-dispatch application server device 11 manages information on the locations of multiple taxis 2 and the presence or absence of passengers, and selects one taxi 2 that suits the request from the multiple 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 the user 3's desired boarding point, and requests the taxi to be dispatched.

[0017] In this embodiment, the taxi terminal system 20 provided in the taxi 2 is configured to include 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 taxi dispatch application server device 11, displays information on the route and advance fare, and accepts a choice 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 taxi dispatch application server device 11 of this fact, and the taxi dispatch application server device 11 further notifies the user terminal device 31 of this fact. As a result, a taxi dispatch reservation is made between the user 3 and the taxi 2, and the taxi 2 heads to the desired boarding point of the user 3, picks up the user 3, and then heads to the destination point.

[0018] For example, if taxi 2 breaks down or has an accident on the way to a desired boarding point of user 3 and is unable to reach the desired boarding point, the driver of taxi 2 can cancel the dispatch of the taxi at taxi terminal device 21. Upon receiving the cancellation operation, taxi terminal device 21 notifies vehicle dispatch application server device 11 of the cancellation, and vehicle dispatch application server device 11 notifies user terminal device 31 of the cancellation. Thereafter, vehicle dispatch application server device 11 may attempt to dispatch another taxi 2.

[0019] The fare meter 22 of the taxi terminal system 20 is placed, 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 using the taxi 2, and in the normal use of the taxi 2, the fare is added according to the distance traveled, the 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 the confirmed advance fare. In this embodiment, the advance fare can be paid using a credit card pre-registered in the taxi information processing system, or by using a QR (Quick Response) code (registered trademark) or a barcode. However, cash payment or payment by electronic money may also be used. In the payment process, the passenger terminal device 23 of the taxi terminal system 20 displays the amount of the advance fare displayed on the fare meter 22 as the payment amount to be paid by the user 3, along with information such as the user's name and credit card information. The passenger terminal device 23 is installed, for example, behind the driver's seat of the taxi 2 and displays various information such as payment information and advertising information to the user sitting in the back seat. 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 fare, it notifies the payment server device 14 of this via the taxi terminal device 21, the taxi-dispatch application server device 11, etc. The payment server device 14 is a device managed and operated by a payment company, and performs payment processing for the taxi fare of the user 3 in response to a payment notification from the vehicle-dispatch application server device 11.

[0021] In the taxi information processing system according to this embodiment, the advance fare determined by the taxi-dispatch application server device 11 will not change even if the taxi 2 is subsequently used. However, discounts that cannot be applied unless a certificate or the like is presented to the driver of the taxi 2, such as a discount for persons with disabilities, cannot be applied to the advance fare, and therefore the discount may be applied to the advance fare at the payment processing stage, resulting in a change in the advance fare. 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 fee does not include, for example, tolls for toll roads traveled by taxi 2 or fees for parking lots used by taxi 2. If such additional fees are incurred, the advance fee may be changed. In this case, the driver of taxi 2 operates, for example, taxi terminal device 21 to input the additional fee. In response to this operation, passenger terminal device 23 displays the payment fee, which is the advance fee plus the additional fee, and payment is made using this payment fee.

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

[0024] Furthermore, in the taxi information processing system according to this embodiment, the taxi-dispatch application server device 11 stores and accumulates information about the taxi 2 in a taxi-dispatch history DB (database). The taxi-dispatch application server device 11 associates the driving route determined by the user 3 before getting into the taxi 2 and the confirmed advance fare with information such as a user ID that identifies the user 3, a taxi ID that identifies the taxi 2, and date and time in the taxi-dispatch history DB. The taxi terminal device 21 also has a receiver that receives GPS signals and can acquire the actual driving route of the taxi 2 based on the GPS signal. The taxi-dispatch application server device 11 acquires the actual driving route of the taxi 2 from the taxi terminal device 21 and stores it in the taxi-dispatch history DB together with the previously determined driving route. This information stored in the taxi-dispatch history DB can be used, for example, to respond to subsequent complaints, improve the driving route determination process, or improve the automatic driving process.

[0025] <Device configuration> 2 is a block diagram showing the 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 CPU (Central Processing Unit), an MPU (Micro-Processing Unit) or a GPU (Graphics Processing Unit), a ROM (Read Only Memory), and a RAM (Random Access Memory). The processing unit 111 reads and executes a server program 112a stored in the memory unit 112 to perform various processes such as determining a taxi route and calculating a taxi 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 also 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 advance taxi fares, a user DB 112c for storing information about users who use the system, a taxi DB 112d for storing information about taxis to be dispatched by the system, an order management DB 112e for managing orders for taxi dispatch from users, and a dispatch history DB 112 for storing information related to taxi operations.

[0027] In the present embodiment, server program 112a is provided in a form recorded on recording medium 99 such as a memory card or an optical disc, and ride-dispatch application server device 11 reads server program 112a from recording medium 99 and stores it in storage unit 112. However, server program 112a may also be written to storage unit 112, for example, during the manufacturing stage of ride-dispatch application server device 11. Alternatively, for example, server program 112a may be distributed by another remote server device or the like and acquired by ride-dispatch application server device 11 via communication. For example, server program 112a recorded on recording medium 99 may be read by a writing device and written to storage unit 112 of ride-dispatch application server device 11. Server program 112a may be provided in a form distributed via a network or in a form recorded on 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 this embodiment is a table in which information such as "company ID," "area," "initial fare," "initial distance," "additional unit," "additional fare," and "coefficient" is stored in association with one another. In this 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 pre-stored in the fare calculation DB 112b. If the user uses a discount coupon or the like, the final advance fare is determined by applying a discount to the advance fare calculated by formula (1). The advance fare calculation formula and the values ​​stored in the fare calculation DB 112b are merely examples and are not limited thereto.

[0029] Advance fare = {initial fare + (distance traveled - initial fare) / additional unit × additional fare} × coefficient … (1)

[0030] The "company ID" in the fare calculation DB 112b is identification information that identifies the taxi operating company, and in the illustrated example, IDs such as "Company A" and "Company B" are stored. The "area" is information that indicates 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 this embodiment, taxis operated by multiple operating companies are subject to dispatch, and the area covered by each operating company is predetermined. There may be multiple operating companies whose covered areas overlap in part or in whole. In the illustrated example, the covered area is defined by prefecture, but it may also be by 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 using 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 "additional unit" is the distance to which the fare will be 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 travelling the "additional unit," and in the illustrated example, distances such as "100 yen" and "85 yen" are stored.

[0032] The "coefficient" is a value used to make a final adjustment to the advance fare. In this embodiment, the "coefficient" is predetermined for each day of the week and time period, such as "Monday midnight," "Monday 1:00," "Monday 2:00," ..., "Monday 11:00 PM," "Tuesday midnight," ..., "Sunday 11:00 PM," and values ​​such as "1.2," "1.1," "1.5," and "1.4" 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 equation (1), which is the formula for calculating the advance fare.

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

[0034] 4 is a schematic diagram showing an example of the configuration of the user DB 112c. The user DB 112c according to this 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 system, for example, when installing a taxi dispatch application program (app) in the user terminal device 31. The user DB 112c is modified or added by the taxi dispatch application server device 11, for example, when a user performs new registration or modifies registered information.

[0035] The "user ID" in the user DB 112c is identification information uniquely assigned to each 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 may be determined automatically by, for example, 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 relating to the payment method used by the user when paying for a taxi fare, and in the example shown, information such as "credit card" and "electronic money" is stored. Note that "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] Furthermore, 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 coupons" are information about 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 limiting.

[0038] FIG. 5 is a schematic diagram showing an example of the configuration of the taxi DB 112d. The taxi DB 112d according to this embodiment is a database in which information such as a "taxi ID," a "company ID," a "driver," a "current location," and a "tariff status" is stored in association with each other. The "taxi ID" is identification information uniquely assigned to each taxi. In the illustrated example, information such as "Taxi A01," "Taxi A02," and "Taxi B01" is stored as taxi IDs assigned to taxis under management. The "company ID" is identification information identifying the taxi operating company. In the illustrated example, IDs such as "Company A" and "Company B" are stored. The "driver" is information about the 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 or added depending on, for example, the addition or reduction of taxis.

[0039] The "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 in reality coordinate information such as latitude and longitude is stored. The "tariff status" is information indicating the status of the taxi, and information such as "empty," "for hire," and "pick-up" is stored. 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 taxi dispatch orders received by the taxi dispatch application server device 11 from the user terminal device 31. The order management DB 112e according to this 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" in the order management DB 112e is the date and time when the user ordered 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 IDs of the taxis used by the user.

[0042] The "preliminary driving route" is information about the taxi driving route determined by the taxi-dispatch application server device 11 based on the desired boarding point and destination point input by the user. When the taxi-dispatch application server device 11 presents multiple driving routes as candidate routes to the user, the "preliminary driving route" stores information about one driving route selected by the user. While the driving route information is abbreviated as "..." in the figure, in reality, route information is stored as, for example, multiple pieces of coordinate information or vector information connecting the desired boarding point and the destination point. The "advance fare" is the taxi fare calculated and determined by the taxi-dispatch application server device 11; in the illustrated example, information such as "1,234 yen" and "3,210 yen" is stored. The taxi-dispatch application server device 11 calculates the taxi driving distance based on the preliminarily driving route and calculates the advance fare using the information in the fare calculation DB 112b shown in FIG. 3 and the above-described formula (1).

[0043] The "reserved boarding time" is information regarding the date and time at which 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. The "reserved boarding location" is the desired boarding point at which the user wishes to board a taxi. The "reserved drop-off location" is the destination point at which the user wishes to disembark from the taxi. Note that in this figure, the information for the "reserved boarding location" and the "reserved drop-off 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 vehicle 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 vehicle 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" is stored as the "reservation number."

[0045] The 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 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 Figure 6, the order management DB 112e may store information such as payment method, coupons used, whether the advance fee has been canceled, boarding date and time, disembarking date and time, and payment 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 driving route," "paid fare," "actual boarding time," "actual boarding location," "actual drop-off location," "whether or not there was a 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 taxi dispatch request. The information stored in the order management DB 112e and the information stored in the dispatch history DB 12 are linked by the "reservation number." The "date and time" is information such as the date and time when the user requested a taxi dispatch; 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; 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; in the illustrated example, information such as "taxi A33" and "taxi D21" is stored as the taxi IDs of the taxis used by the user.

[0049] The "actual driving route" is information about the actual driving route taken by the taxi carrying the user. In this figure, the driving route information is abbreviated as "...", but the "actual driving route" can be a collection of coordinate information of the taxi's current location transmitted from the taxi terminal device 21. The "payment fare" is the fare finally paid (paid) by the user after using the taxi, and in the illustrated example, information such as "1,234 yen" and "3,210 yen" is stored. Note that the "advance fare" and the "payment fare" are basically the same amount, but for example, if a discount such as a disability discount is applied after the advance fare is determined, or if toll road fees are added, the "advance fare" and the "payment fare" may be different amounts.

[0050] The "actual boarding time" is information relating to the time when the user boarded a taxi. For example, when a user boards a taxi and the driver changes the taxi from a pick-up state to a hire state using the taxi terminal device 21 or the fare meter 22, the taxi terminal device 21 notifies the ride-hailing application server device 11 of the boarding time, and in response to this notification, the ride-hailing application server device 11 can store the information in the "actual boarding time" field in the ride-hailing history DB 12. The "actual boarding location" is the location where the user actually boarded the taxi. The "actual drop-off location" is the location where the user actually dropped off the taxi. The ride-hailing application server device 11 stores the information on the "actual boarding location" and the "actual drop-off location" in the ride-hailing history DB 12 based on the taxi status information and location information, etc., obtained from the taxi terminal device 21. In this figure, the information on the "actual boarding location" and the "actual drop-off location" is abbreviated as "...", but in reality, coordinate information indicating a location, such as latitude and longitude information, is stored. Furthermore, if information on the "actual boarding location" and "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 example shown, the information "No" is stored, indicating that cancellation has not occurred. For example, if the user changes their 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, indicating that the user paid by credit card. "Coupon" is information about the content of the coupon used by the user to pay the fare. In the illustrated example, "100 yen discount" information, which deducts 100 yen from the fare, and "none" information, indicating that no coupon was used, are stored. In this embodiment, discounts such as coupons are reflected in the "advance fare." "Discount" is information about discounts that are applied after the user boards a taxi, such as a discount for people with disabilities. If a discount is applied, "yes" information is stored, and if a discount is not applied, "none" information is stored.

[0053] The dispatch application server device 11 adds and modifies information to the dispatch history DB 12 at various times, such as when a user requests a taxi dispatch, when the user gets in 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 local area network (LAN), 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 by 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 detachable from the ride-dispatch application server device 11. Furthermore, 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] Note that storage unit 112 may be an external storage device connected to ride-dispatch application server device 11. Furthermore, ride-dispatch application server device 11 may be a multi-computer configured to include multiple computers, or may be a virtual machine virtually constructed by software. Furthermore, ride-dispatch application server device 11 may not be equipped with a user interface such as display unit 114 and operation unit 115. In this case, for example, an administrator or the like may operate 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 according to this embodiment, the processing unit 111 reads out and executes the server program 112a stored in the memory unit 112, whereby a route processing unit 111a, an order processing unit 111b, an advance fee 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, and the like are realized as software functional units.

[0058] The route processing unit 111a performs processing to determine a driving route for the taxi based on the desired boarding point and destination point input by the user. The method for determining the driving route can be the same as the method for 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 route candidates from the desired boarding point to the destination point, transmits the multiple candidates to the user terminal device 31, and accepts the selection of a driving route from the user. The route processing unit 111a determines one driving route selected by the user as the preliminary driving route for 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 the desired boarding point and 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 fare processing unit 111c performs processing to calculate the advance fare to be paid by the user for using a taxi based on the taxi route determined by the route processing unit 111a and information in the fare calculation DB 112b stored in the storage unit 112. The route processing unit 111a presents multiple route candidates to the user, and the advance fare processing unit 111c calculates the advance fare for each candidate and presents the candidate advance fare to the user. When calculating the advance fare, the advance fare processing unit 111c determines the operating company that will dispatch the taxi, for example, based on the user's desired boarding point. The advance fare processing unit 111c obtains information such as the base fare and additional fare for the determined operating company from the fare calculation DB 112b and substitutes this information into the above-mentioned formula (1). The advance fare processing unit 111c also calculates the taxi's travel distance based on the route determined by the route processing unit 111a and substitutes the calculated distance into the above-mentioned formula (1). As a result, the advance fare processing unit 111c can calculate the advance fare 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 approves the advance fee, etc. Once the advance fee is finalized, the user will no longer be able to change the fee.

[0061] After the advance fare processing unit 111c determines the advance fare, 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, for example, a taxi that is available and whose current location is close to the user's desired boarding point, and requests dispatch of the selected taxi to the taxi terminal device 21. 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 as to 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. This completes a taxi reservation between the taxi and the user, and the taxi picks up the user to the desired boarding point and transports the user to the destination according to the determined route. If the request for dispatch is not accepted, the dispatch processing unit 111d selects another taxi and requests dispatch of the taxi. In addition, if, for example, no response is received from the taxi driver within a predetermined time from the dispatch request, the dispatch processing unit 111d may request dispatch of another taxi without waiting for a response to the dispatch request.

[0062] The dispatch processing unit 111d also performs processing related to cancellation from a taxi 2 that has accepted a dispatch request. In the taxi information processing system according to this embodiment, the taxi driver can cancel the acceptance of the dispatch request when, for example, various factors such as an accident or breakdown make it difficult for the taxi driver to head to the desired pickup point specified by the user. When the taxi terminal device 21 receives a cancellation operation from the driver, it notifies the dispatch application server device 11 of the cancellation. Upon receiving the cancellation notification, the dispatch processing unit 111d of the dispatch application server device 11 notifies the user terminal device 31 of the user associated with the canceled dispatch request of the cancellation. Upon receiving the cancellation notification, the user terminal device 31 displays on the display unit 314 that the dispatch request has been canceled. This cancels the reservation that was once made 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 and the taxi terminal device 21 by relaying information exchange between the taxi terminal device 21 and the payment server device 14. The payment processing unit 111e acquires the payment fare, payment method, and other information necessary for payment from the taxi terminal device 21, and requests the payment server device 14, which is 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 fare for this user, and notifies the taxi-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 stores information obtained during a series of steps related to a user's taxi use in the order management DB 112e or the dispatch history DB 12 of the storage unit 112. For example, when a user approves a route and advance fare on the user terminal device 31, the dispatch history processing unit 111f stores information such as the date and time information and the user ID in the order management DB 112e or the dispatch history DB 12. For example, when a taxi driver accepts 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 the actual route. For example, when a taxi arrives at a destination and payment is completed, the dispatch history processing unit 111f stores the payment. The timing at which the dispatch history processing unit 111f stores information and the contents of the stored information are merely examples and are not limiting.

[0065] The display processing unit 111g performs processing to display 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 receives, for example, specification of a date and time and a taxi ID via the operation unit 115, and reads information corresponding to the specified date and time, taxi ID, etc. from the order management DB 112e and the dispatch history DB 12. Based on the read 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 the driving route. The information stored in the order management DB 112e and the dispatch history DB 12 may be displayed in any manner. In the present embodiment, the dispatch application server device 11 displays information stored in the dispatch history DB 12 on its own display unit 314. However, this is not limited to this, and information may also be displayed on the display unit of another device via communication via a network.

[0066] 8 is a block diagram showing the 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, etc. The processing unit 311 is configured using an arithmetic processing device such as a CPU or an MPU, a ROM, a RAM, etc. The processing unit 311 reads and executes a program 312a stored in the memory unit 312 to perform various processes related to a taxi dispatch request, etc.

[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 to the storage unit 312, for example, during the manufacturing stage of the user terminal device 31. For example, the program 312a may be recorded on a recording medium such as a memory card or an optical disk, and the user terminal device 31 may read the program 312a and store it in the storage unit 312. For example, the program 312a may be recorded on a recording medium, read by a writing device, and written to the storage unit 312 of the user terminal device 31. The program 312a may be provided in the form of distribution via a network or in the 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] Communication unit 313 communicates with various devices via network N, which includes a public mobile phone communication network and the Internet. In this embodiment, communication unit 313 communicates with ride-dispatch application server device 11 via network N. Communication unit 313 transmits data provided by processing unit 311 to ride-dispatch application server device 11, and provides data received from ride-dispatch application server device 11 to 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 GPS satellites 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 by 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, whereby the display processing unit 311a, the dispatch request unit 311b, the approval receiving unit 311c, and the like are realized as software functional units in the processing unit 311. 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 displays various screens such as a menu screen, a screen for inputting a desired boarding point and a destination point, a screen presenting information about a taxi's route and advance fare, 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 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 a user ID 312b stored in the storage unit 312 to the dispatch application server device 11. The desired boarding point may be, for example, the current location based on a GPS signal received by the GPS receiving unit 316, or may be, for example, a specific location or facility designated by the user. The dispatch application server device 11 determines the taxi's route and calculates the advance fare according to the desired boarding point and the destination point provided together with the dispatch request.

[0074] The approval receiving unit 311c performs a process of receiving user approval for the taxi driving route and advance fare determined in response to a taxi dispatch request. Information regarding the taxi driving route and advance fare determined by the taxi dispatch application server device 11 in response to a taxi dispatch request is received by the user terminal device 31 and 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 fare via the operation unit 315 and notifies the taxi dispatch application server device 11 of the approval. If the taxi dispatch application server device 11 has created multiple candidate driving routes and advance fares, the display unit 314 displays the multiple candidates, and the approval receiving unit 311c accepts the selection of one driving route and advance fare from the multiple candidates and notifies the taxi dispatch application server device 11 that the selected driving route and advance fare have been approved. If the user performs an operation to not approve the driving route and advance fare, 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 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 this embodiment. The payment server device 14 according to this embodiment is configured to include a processing unit 141, a memory unit (storage) 142, a communication unit (transceiver) 143, etc. The processing unit 141 is configured using an arithmetic processing device such as a CPU, an MPU, or a GPU, a ROM, etc. The processing unit 141 reads 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 required 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 has a payment DB 142b that stores information required 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 disc, 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 to the storage unit 142, for example, during the manufacturing stage of the payment server device 14. Alternatively, 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 via 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 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 a "credit card ID," "expiration date," "balance," and "limit" is stored in association with each other. The "credit card ID" is identification information assigned to a credit card and may be a so-called card number. The "expiration date" is information on the period during which the credit card can be used. The "balance" and "limit" are information on credit card usage restrictions; for example, a "limit" is set to 300,000 yen per month, and the "balance" is the value obtained by subtracting the amount already 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 ride-dispatch application server device 11, etc. via the network N. The communication unit 143 transmits data provided by 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 multiple 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] Furthermore, in the processing unit 141 of the payment server device 14 according to this 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 necessary for the user who has used 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 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 payment is possible. If the confirmation processing unit 141a determines that payment is possible, the payment processing unit 141b performs a process of paying the taxi fare by the user with a registered credit card.

[0082] FIG. 11 is a block diagram showing the configuration of the taxi terminal device 21 according to this embodiment. The taxi terminal device 21 according to this embodiment may be, for example, a device fixed near the driver's seat of the taxi 2, or may be a device that the driver can carry, such as a smartphone or tablet terminal device. The taxi terminal device 21 includes 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, a RAM, and the like. The processing unit 211 reads and executes a program 212a stored in the memory unit 212 to perform various processes related to accepting a vehicle dispatch request from a user and canceling an accepted vehicle 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, program 212a is distributed by a remote server device or the like, and is acquired by taxi terminal device 21 via communication and stored in memory unit 212. However, program 212a may also be written to memory unit 212, for example, during the manufacturing stage of taxi terminal device 21. For example, program 212a may be read by taxi terminal device 21 from a recording medium such as a memory card or optical disk and stored in memory unit 212. For example, program 212a may be read by a writing device from a recording medium and written to memory unit 212 of taxi terminal device 21. Program 212a may be provided in the form of distribution via a network, or may be provided 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 or the like that manages the taxi 2, and is stored in the storage unit 212. In this embodiment, the identifier assigned to the taxi 2 is used as the taxi ID 212b, but for example, the identifier assigned to the driver of the taxi 2 may also 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 the present embodiment, the communication unit 213 communicates with an externally provided vehicle-dispatch application server device 11, and also communicates with the fare meter 22 and the passenger terminal device 23 provided in the taxi 2. The communication unit 213 may use different communication protocols for communication with the vehicle-dispatch application server device 11 and for communication with the fare meter 22 and the passenger terminal device 23. For example, the communication unit 213 communicates with the vehicle-dispatch application server device 11 via a public mobile phone communication network. Furthermore, for example, the communication unit 213 communicates with the fare meter 22 and the passenger terminal device 23 via 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 processing by the processing unit 211. The operation unit 215 accepts operations from the driver using 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 GPS satellites 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 by the GPS receiving unit 216. Furthermore, the communication unit 213 relays communication between the taxi-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, acceptance receiving unit 211b, cancellation receiving unit 211c, and the like are realized as software functional units in the processing unit 211. The display processing unit 211a performs processing to display various screens related to a request to dispatch a taxi 2 on the display unit 214. For example, the display processing unit 211a displays various screens, such as a menu screen, a screen presenting information on a route and advance fee related to a dispatch request from a user, and a screen for accepting operations such as accepting or canceling 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 display various information. For example, the display processing unit 211a performs processing to display the advance fare on the fare meter 22 by transmitting information about the confirmed advance fare to the fare meter 22. The display processing unit 211a also performs processing to display the payment fare on the passenger terminal device 23 by transmitting information about the payment fare to the passenger terminal device 23 after the taxi 2 has arrived at the destination, for example.

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

[0091] The cancellation reception unit 211c performs processing to receive a cancellation operation for an accepted vehicle dispatch request. After the acceptance reception unit 211b accepts the vehicle dispatch request, the display processing unit 211a displays information such as the user's desired boarding point on the display unit 214, and urges the driver to direct the taxi 2 to the desired boarding point. In this state, the cancellation reception unit 211c receives a cancellation operation for the vehicle dispatch request. When the cancellation operation is received, the cancellation reception unit 211c notifies the vehicle dispatch application server device 11 of the cancellation of the vehicle 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 unit such as a CPU or an MPU, a ROM, a RAM, etc. The processing unit 221 performs various processes related to the display of fares and the reception of operations by the driver, etc. Although not shown in the figure, the fare meter 22 is connected to a sensor or the like mounted on the taxi 2, and can perform a process of calculating the fare of the taxi 2 according to the traveling distance measured by the sensor, etc.

[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 installed 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, etc. 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 where a fare is not determined in advance, the fare meter 22 displays on the display unit 223 a fare that is added according to the distance traveled, time, etc. If a fare has been determined in advance, the fare meter 22 does not display a fare that is added according to the distance traveled, time, etc., but displays the previously determined advance fare on the display unit 223. When displaying the advance fare, the fare meter 22 can determine whether a fare has been determined in advance and the determined advance fare by exchanging information with the taxi terminal device 21, for example, via the communication unit 222. When displaying the advance fare, the fare meter 22 may or may not calculate a 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 regular fare, a button for starting the payment process after arriving at the destination, and a button for applying discounts such as a discount for disabled people. 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 the 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 in a location visible to a user sitting in the back seat of the taxi 2. The passenger terminal device 23 may be a device fixed to 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, an operation unit 234, etc.

[0098] The processing unit 231 is configured using an arithmetic processing unit 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 required to pay 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 via wired communication via a communication line installed inside the taxi 2 or wireless communication such as Bluetooth. The display unit 233 is configured using a liquid crystal panel or the like, and displays various images, characters, etc. 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] Furthermore, after the user gets into the taxi 2, the passenger terminal device 23 may display, for example, an advertisement or other image 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 payment fare information 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, time, etc. If a discount such as a disability discount is applied to these fares, the display is updated to show the discounted payment fare. After displaying the payment fare, the passenger terminal device 23 accepts an approval operation for the payment process from the user. If the approval operation is accepted, the passenger terminal device 23 transmits a notification to that effect to the taxi-dispatch app server device 11 via the taxi terminal device 21.

[0101] When the taxi 2 arrives at the destination, the payment fare is displayed on the passenger terminal device 23, and when approval for payment of this payment fare is obtained from the user, the payment server device 14 performs the payment process. Upon obtaining approval for payment, the passenger terminal device 23 notifies the taxi-dispatch application server device 11 of this via the taxi terminal device 21. The taxi-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. Based on the information received from the taxi-dispatch application server device 11, the payment server device 14 performs the payment process using a credit card, electronic money, etc.

[0102] <Taxi fare processing> 13 is a schematic diagram for explaining the processing 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 requesting dispatch must download program 312a to user terminal device 31 and must also complete procedures for using the system in advance (for example, agreeing to terms of use and registering personal information). 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 desiring to use a taxi launches the program 312a on their user terminal device 31 and selects a taxi dispatch request option from, for example, a menu screen. The user terminal device 31 displays a screen on the display unit 314 for specifying the desired boarding point and destination point for the taxi and accepts input of the desired boarding point and destination point from the user. The desired boarding point is initially set to the current location. If the user does not change this, the current location based on the GPS signal received by the GPS receiver unit 316 is accepted as the desired boarding point. The destination point may be accepted as an input result of a search based on, for example, the name of a place or building, or as an address or postal code, or as an input specifying a point on a map, or may be accepted in a manner other than these. When the desired boarding point is specified as a point other than the current location, it may be entered in the same manner as the destination point. The user terminal device 31 transmits a taxi dispatch request message including the entered desired boarding point and destination point and the user's user ID 312b to the taxi dispatch app 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 taxi-dispatch application server device 11 determines a taxi route based on the desired boarding point and the destination included in the dispatch request message. The taxi-dispatch application server device 11 calculates a prepayment fare for using a taxi based on the determined route and the fare calculation DB 112b in the storage unit 112. The taxi-dispatch application server device 11 preferably presents a plurality of route candidates and prepayment fare options to the user. The taxi-dispatch application server device 11 may determine two route candidates, for example, a route that uses a toll road and a route that does not. In this embodiment, the prepayment fare does not include the toll road fee. However, this is not limited to this, and the toll road fee may be included in the prepayment fare. The taxi-dispatch application server device 11 also references the user DB 112c in the storage unit 112 based on the user ID included in the dispatch request message. If the user has a discount coupon or the like, the taxi-dispatch application server device 11 obtains information about the coupon and calculates a prepayment fare that applies the discount provided by the coupon. 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 requesting user.

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

[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 assumes that two candidates, Route 1 and Route 2, are provided to the user terminal device 31 by the vehicle dispatch application server device 11 as candidates for the driving route and advance fare. The user terminal device 31 displays a map image on the display unit 314, and also displays the two candidate driving routes, Route 1 and Route 2, superimposed on the map image. In this diagram, the desired boarding point is indicated by "S," the destination point is indicated by "G," Route 1, which is the first candidate driving route, is indicated by a solid line, and Route 2, which is the second candidate driving route, is indicated by a dashed line.

[0108] In the area below the map image on the vehicle dispatch request screen, information about two candidates is displayed on the left and right. In this example, information about "Route 1" is displayed in the left area, and information about "Route 2" is displayed in the right area. In the left area, the character string "Route 1" is displayed, and below this character string, the character string "Advance Fee 11,200 yen" indicating the calculated advance fee, and further below that, a button labeled "Request a vehicle dispatch." In addition, in the right area, the character string "Route 2" is displayed, and below this character string, the character string "Advance Fee 13,000 yen" is displayed, and further below that, a button labeled "Request a vehicle dispatch." The user can select one of the two presented routes by performing an operation such as a touch operation on either of the two "Request a vehicle dispatch" buttons provided side by side at the bottom of the vehicle dispatch request screen.

[0109] When the user terminal device 31 receives a touch operation on either of the two "Request a Vehicle" buttons, it determines that the user has approved the driving route and advance fee for the corresponding route, and sends 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 is not intended to accept an operation to not approve the presented driving route and advance fee, but it may be configured to accept an operation to reject the presented driving route and advance fee and request a vehicle to be dispatched at a fare using a fare meter, for example.

[0110] The vehicle-dispatch application server device 11, which has received a message approving the route and 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 to the taxi terminal device 21 of the selected taxi, which includes information on the route and advance fare, and information on the user who made the request.

[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 the message on the display unit 214 and accepts an operation from the driver to accept the dispatch request for the 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 diagram, the user's desired boarding point is indicated by "S," the destination point by "G," the current location of the taxi by "current," and the driving route by a solid line.

[0112] The taxi terminal device 21 displays information about the dispatch request below the map image. In this figure, the taxi terminal device 21 displays the following information about the user: "Requester: User A," "Payment Method: Credit Card" as the payment method for the fare, "Discount Coupon: 100 Yen Discount" as the applicable coupon, and "Advance Fee 11,200 Yen" as the confirmed advance fee. However, the taxi terminal device 21 does not have to notify the taxi driver of the advance fee. In other words, the taxi terminal device 21 may request dispatch without notifying the taxi driver whether the advance fee is based on a prepayment or whether the fare will be calculated using the fare meter 22.

[0113] The taxi terminal device 21 displays a button labeled "Accept" below this information. By accepting a touch operation or the like on the "Accept" button, the taxi terminal device 21 accepts the driver's acceptance of the user's dispatch request. Upon accepting the acceptance, the taxi terminal device 21 transmits a message to the dispatch application server device 11 notifying the driver that the dispatch request has been accepted. 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. Upon receiving this message, the user terminal device 31 displays on the display unit 314 a message notifying that the dispatch request made by the user has been accepted. 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 able to accept, 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 illustrating the process of canceling a dispatch request by the taxi information processing system according to this embodiment. A taxi driver who accepts a dispatch request from a user sends a taxi to the desired boarding point designated by the user. In this embodiment, after accepting the user's dispatch request, the taxi terminal device 21 displays a screen on the display unit 214 that accepts the cancellation of the accepted dispatch request 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 on the taxi terminal device 21. Upon receiving the cancellation operation, the taxi terminal device 21 transmits a message to the taxi dispatch application server device 11 notifying the user that the dispatch request will be canceled. The taxi dispatch application server device 11 receives the message notifying the cancellation from the taxi dispatch application server device 11 and transmits a similar message to the user terminal device 31. Upon receiving this message, the user terminal device 31 displays a message on the display unit 314 notifying the user that the dispatch request has been canceled.

[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 substantially the same as the configuration of the dispatch request acceptance screen shown in FIG. 15. The cancellation acceptance screen displays information about the accepted dispatch request, such as a map image showing the travel route, information about the user, information about the payment method, information about discount coupons, and information about 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 or the like on this button. The taxi terminal device 21 accepts the cancellation of the accepted dispatch request in response to a touch operation or the like 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, for example, perform a predetermined operation on the taxi terminal device 21 or the fare meter 22 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 as needed depending on the taxi's travel distance, time, etc., but displays the advance fare notified by the taxi terminal device 21.

[0117] After a taxi carrying a passenger arrives at a destination, the user must pay (settle) the taxi fare. The passenger terminal device 23 of the taxi displays a payment screen and accepts a process related to the taxi fare payment from the user. FIG. 18 is a schematic diagram showing an example of the payment screen displayed by the passenger terminal device 23. On the payment screen, the passenger terminal device 23 displays, for example, information on the payment method of the fare, such as "Payment Method: Credit Card," and information on the applicable coupon, such as "Discount Coupon: 100 Yen Discount," and also displays the pre-determined advance fee as the payment fee, such as "Payment Fee: 11,200 Yen." The passenger terminal device 23 may also display the taxi's travel route superimposed on a map image on the payment screen. The displayed travel route may be a predetermined travel route, the actual travel route of the taxi, or both of these may be displayed 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 to receive approval from the user for the payment process for the displayed payment fare. 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 processing by the taxi information processing system according to this embodiment. The taxi 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, having received 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 operation unit 224 accepts the payment operation, the fare meter 22 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 also 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. Upon receiving this message, the taxi terminal device 21 transmits a message notifying approval of the payment, including information about the user and the payment fee, to the vehicle-dispatch application server device 11.

[0122] Upon receiving the payment approval from the taxi terminal device 21, the vehicle-dispatch application server device 11 refers to the user DB 112c to acquire information on the payment method and the like registered for the user paying the fare. For example, the vehicle-dispatch application server device 11 acquires information on the company and card number of the credit card used by the user for payment. The vehicle-dispatch application server device 11 transmits a payment request including information on the card number, 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 payment processing using a credit card, electronic money, or the like, based on information from the vehicle-dispatch application server device 11. Details of the payment processing by the payment server device 14 will not be explained here. After the payment processing is completed, the payment server device 14 notifies the vehicle-dispatch application server device 11 of the completion of payment. The vehicle-dispatch application server device 11 notifies the taxi terminal device 21 of the completion of payment, and stores information about this vehicle dispatch in the order management DB 112e and the vehicle dispatch history DB 12 of the memory unit 112. The taxi terminal device 21 notifies the passenger terminal device 23 of the completion of the payment processing, and the passenger terminal device 23 displays a message or the like on the display unit 233 indicating that the payment processing has been completed.

[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 other document showing eligibility for the discount, the taxi driver can apply the discount to the payment fare by operating the discount application button on the operation unit 224 of the 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 the taxi terminal device 21 or the fare meter 22. This operation applies the payment fare, which is the additional fee added to the advance fare.

[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 notifying that fact to the taxi terminal device 21. 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 notifying 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 after the advance fare has been confirmed and the user boards a taxi, but before arriving at the destination, the user pays the pre-confirmed advance fare regardless of whether the user arrives at the destination. For example, if the user verbally requests a destination, 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 begins traveling to the changed destination, and the fare at this time is added according to the distance traveled, time, etc. However, the travel route and advance fare from the current location to the new destination may also 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, making it difficult to pay the prepaid fare on the spot. In such cases, the prepaid fare can be canceled and a fare calculated based on, for example, the distance traveled and the time traveled so far can be used for payment. 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 the time traveled in the background.

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

[0129] The approval receiving unit 311c of the processing unit 311 determines whether a message including information such as a driving route and an advance fee, which is sent from 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 completion of acceptance of the vehicle 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 completion of acceptance of the vehicle dispatch request on the display unit 314 (step S9), and ends the processing.

[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 the dispatch of a taxi has been received from the user terminal device 31 (step S21). If the message requesting the dispatch of a taxi has not been received (S21: NO), the processing unit 111 waits until the message requesting the dispatch of a taxi is received.

[0132] When a message requesting a taxi dispatch is received (S21: YES), the processing unit 111 checks whether a taxi can be used with a prepaid fare based on the desired boarding point or destination 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 suspends the processing according to this flowchart and performs a conventional taxi dispatch process for using a taxi with a fare based on the distance traveled. Note that the conventional taxi dispatch process is not shown in this figure.

[0133] If a taxi is available for advance payment, the processing unit 111 determines a taxi company to dispatch a taxi based on the desired boarding point or destination 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 route based on the desired boarding point and destination included in the received message (step S24). Note that the route processing unit 111a may determine multiple routes as candidates. Next, the advance fare processing unit 111c of the processing unit 111 calculates an advance fare for each route based on the taxi route determined in step S24 and the fare calculation DB 112b of the storage unit 112 (step S25). At this time, the advance fare processing unit 111c determines a taxi operating company based on the desired boarding point, and can calculate the advance fare by substituting the value associated with the operating company in the fare calculation DB 112b and the distance of the route determined in step S24 into the above-mentioned equation (1). The advance fee processing unit 111c may also refer to the user DB 112c to check whether the user who requested the vehicle dispatch has a discount coupon, and if the user has a discount coupon, may obtain information about the discount coupon from the user DB 112c and calculate the advance fee applying the discount related to the obtained coupon.

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

[0135] If an approval message is received (S27: YES), the vehicle 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 vehicle dispatch processing unit 111d can select an available taxi that is located closest to the desired boarding point included in the received vehicle dispatch request message. The vehicle dispatch processing unit 111d transmits a vehicle dispatch request message including information about the user, the driving route, the advance fare, and the like to the taxi terminal device 21 of the selected taxi (step S29).

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

[0137] Thereafter, the processing unit 111 determines whether or not a message notifying that the dispatch request is canceled 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 processing.

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

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

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

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

[0142] The display processing unit 211a displays a cancellation acceptance screen on the display unit 214 to accept an operation to cancel the vehicle dispatch request (step S76). The cancellation acceptance unit 211c of the processing unit 211 determines whether the vehicle dispatch request has been canceled based on an operation accepted by the operation unit 215 while the cancellation acceptance screen is displayed (step S77). If the vehicle dispatch request has been canceled (S77: YES), the cancellation acceptance unit 211c transmits a message to the vehicle dispatch application server device 11 notifying that the vehicle 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 such an operation is performed. If an operation to start the payment process has been performed (S79: YES), the display processing unit 211a transmits information about the payment fee (advance fee) to the passenger terminal device 23, thereby causing the passenger terminal device 23 to display the payment fee (step S80).

[0144] The processing unit 211 determines, through communication with the fare meter 22, whether a discount operation has been performed on the operation unit 224 of 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 Figure 24, when adding toll road fees or the like, the fee can be similarly added to the payment fare (advance fee) in accordance with the driver's operation 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 accumulation processing> 21 and 22, the vehicle-dispatch application server device 11 according to the present embodiment performs processing to store and accumulate various pieces of information related to the dispatch of taxis as history in the order management DB 112e and the vehicle-dispatch history DB 12. Note that the vehicle-dispatch application server device 11 may accumulate information at various times other than those described 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), 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 various other information may be stored, such as whether or not the taxi driver canceled the taxi, whether or not the user canceled the taxi, or images of the interior and exterior 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 vehicle-dispatch application server device 11 according to the present embodiment. When a vehicle-dispatch history processing unit 111f of processing unit 111 of vehicle-dispatch application server device 11 according to the present embodiment receives a taxi dispatch request from 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 vehicle-dispatch application server device 11 in order management DB 112e (step S102).

[0149] When the advance fare for using a taxi is determined (step S103), the dispatch history processing unit 111f stores the determined advance route and advance fare in the order management DB 112e (step S104). Also, when the taxi driver accepts the dispatch request (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 112e (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 location 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 location 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-use 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 times.

[0153] The vehicle-dispatch application server device 11 according to the present embodiment performs processing to display 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 the present 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. Furthermore, for example, an employee of a taxi company can access the vehicle-dispatch application server device 11 using the information processing device 13 and display the same history information on the display unit of the information processing device 13.

[0154] 26 is a schematic diagram showing an example of a vehicle 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 vehicle dispatch application server device 11. The illustrated vehicle dispatch history screen assumes that the administrator has selected the history for 11:12 on January 20, 2020, which is included in the order management DB 112e shown in FIG. 6 and the vehicle dispatch history DB 12 shown in FIG. 7.

[0155] In this example, the information processing device 13 displays the text string "January 20, 2020, 11:12" as the date and time information of the history as a title at the top. Below this title, the information processing device 13 displays the predetermined taxi route and the route actually traveled by the taxi superimposed on a map image. 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. If these are different, they may be superimposed on the map image so that they can be distinguished. The disembarking point may be either the destination input by the user or the point where the user actually disembarked from the taxi. If these are different, they may be superimposed on the map image so that they can be distinguished. In this figure, the predetermined taxi route is indicated by a solid line as the "pre-planned route," and the route actually traveled by the taxi that differs from the pre-planned route is indicated by a dashed line as the "actual route."

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

[0157] The information processing device 13 also displays a button labeled "Contact Customer" in the lower right corner of the vehicle dispatch history screen. This button is for sending a message by email 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 vehicle dispatch application server device 11. Based on information such as the user ID stored in the vehicle dispatch history DB 12 and the email address stored in the user DB 112c, the vehicle 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. The vehicle dispatch application server device 11 also stores information such as the content of the message sent to the user and the date and time of transmission in the vehicle dispatch history DB 12 or the like.

[0158] The taxi-dispatch application server device 11 according to the present embodiment can store various information related to taxi dispatch 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 about locations where differences frequently occur between a predetermined driving route and an actually driven driving route to be used as a reference for studying ways to improve a method for determining a predetermined driving route. Furthermore, 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 users who have used a taxi. Note that the dispatch history screen shown in FIG. 26 is an example and is not limited thereto, and the displayed information and the display mode of the information can be changed as appropriate.

[0159] <Summary> The taxi-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 the desired boarding point and destination point of a user wishing to board a taxi, and determines an advance fare for the taxi ride based on the determined driving route. The taxi-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 displaying the driving route and the advance fare on the user terminal device 31 and the taxi terminal device 21. The taxi-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 taxi-dispatch history DB 12.

[0160] This allows the user to use a taxi at a pre-determined fare rather than a fare that is calculated based on the distance traveled and the time taken. The user can check the taxi's route and advance fare in advance on the user terminal device 31 that the user owns. The taxi driver can confirm the route and advance fare on the taxi terminal device 21 and accept the dispatch request. In addition, since the dispatch application server device 11 stores and accumulates information related to taxi dispatch in the order management DB 112e and the dispatch history DB 12, the user can check information such as the route traveled by the taxi and the paid fare after the fact.

[0161] Furthermore, 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, allowing 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 associates a predetermined driving route with a driving route actually traveled by a taxi and stores the association information 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 the taxi traveled the predetermined driving route.

[0163] Furthermore, the taxi-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. Furthermore, the taxi terminal device 21 of the taxi terminal system 20 acquires information on the availability 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 the payment fare with the discount applied to the advance fare. This allows the advance fare with the discount applied in advance to be presented to the user for discount coupons that do not require verification of a certificate or the like, and allows the taxi 2 to apply discounts, such as a discount for persons with disabilities, that require verification of a certificate or the like.

[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 installed at the rear of the taxi. This allows the user riding in the taxi to easily check the payment fare with the discount applied.

[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 from multiple operating companies with different fare calculation standards to the user.

[0166] Furthermore, in the taxi information processing system according to this embodiment, when a request to change the predetermined route is received from the user after the user gets in the taxi, the system performs a payment process for the predetermined advance fare, and the taxi heads to the changed destination after the payment process is completed. This ensures that the predetermined advance fare is paid.

[0167] Furthermore, in the taxi information processing system according to this embodiment, the taxi driver can cancel the dispatch request at the taxi terminal device 21 during the period from when the advance fare is determined until the user gets into the taxi. When the taxi terminal device 21 accepts the 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 notify 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 Modification 1. The fare calculation DB 112b according to Modification 1 is obtained by adding information about a long-distance discount to the fare calculation DB 112b shown in FIG. 3. The fare calculation DB 112b according to Modification 1 stores information about the long-distance discount, such as a "criterion" and a "coefficient," in association with the taxi operating company. In this embodiment, the long-distance discount is achieved by multiplying the fare added thereafter by a predetermined coefficient, for example, when the taxi's travel distance exceeds a predetermined distance or the fare exceeds a predetermined amount. The "criterion" in the fare calculation DB 112b is the predetermined distance or a predetermined amount that determines whether or not to apply the long-distance discount. The "coefficient" is a value by which the fare added after the reference distance is exceeded.

[0169] The ride-dispatch application server device 11 according to the first modification determines a travel route from the desired boarding point and destination point input by the user, and calculates an advance fare based on the determined travel route. At this time, if the distance of the determined travel route exceeds a predetermined distance set as a "standard," or if 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 FIGS. 3 and 27, and various other information used for fee calculation may be stored.

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

[0172] In addition, some of the "initial fare," "initial distance," "additional unit," "additional fare," and "coefficient" contained in the fare calculation DB 112b shown in Figures 3 and 27 may be the same across multiple operating companies. For example, multiple taxi operating companies may use the same value for the "coefficient," and each operating company may use different values ​​for the other items such as the "initial 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 fare. After receiving input of a desired boarding point and a destination point via a user terminal device 31, the taxi dispatch application server device 11 of the taxi information processing system according to the second embodiment determines a driving route from the desired boarding point to the destination point. At this time, the taxi dispatch application server device 11 calculates multiple driving route candidates based on different conditions, such as distance priority and expressway priority, and receives a driving route selection 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 embodiment 2. As with the vehicle 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 dominant)" and a driving route candidate calculated with priority given to expressways as "Route 2 (highway dominant)."

[0175] The taxi-dispatch application server device 11 also determines a taxi company (taxi operating company) that can dispatch a taxi to the user based on information such as the desired boarding point and destination entered by the user, information on the "area" contained in the fare calculation DB 112b, and information on available taxis located near the desired boarding point, and determines the advance fare based on the fare calculation standard of the determined taxi company. The taxi information processing system according to the second embodiment allows taxis from multiple taxi companies to operate in one area, and each taxi company is allowed to use a different advance fare calculation standard. Therefore, the taxi-dispatch application server device 11 calculates advance fares for each candidate travel route for all taxi companies available to the user, transmits information on the minimum (lowest price) and maximum (highest price) of the calculated advance fares to the user terminal device 31, and displays the range of advance fares to the user. In the example shown in FIG. 28, the advance fare for Route 1 is displayed in the range of 11,200 yen to 11,800 yen, and the advance fare for Route 2 is displayed in the range of 11,600 yen to 12,000 yen. 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 along with the advance fee for Route 2. Although not shown in the figure in this example, further information such as the estimated travel time for each route or the arrival time at the destination may be displayed. Furthermore, for Route 2, an approximate fee for using toll roads may be displayed, or an advance fee including the toll road fee 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, is 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 one 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 one 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 travel route by the user via the user terminal device 31, transmits information relating to the selected travel 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 the case where route 1 is selected on the screen of Figure 28, and Figure 30 shows the case where route 2 is selected.

[0178] The user terminal device 31 displays a map image at the top of the information display screen, and also displays the travel 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 travel route is indicated by a solid line. The user terminal device 31 also displays a roughly rectangular message display area at 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 regarding any other fees that may be added. In Figure 29, the information displayed is "11,200 yen to 11,800 yen, plus a separate pick-up fee." In Figure 30, the information displayed is "11,600 yen to 12,000 yen, plus a separate toll passage fee and pick-up fee."

[0179] In addition, a button labeled "Select Route" is provided in the lower right corner of the map image. When an operation on the "Select Route" button is accepted, the user terminal device 31 displays the travel route selection screen shown in FIG. 28 and accepts the user's selection of a travel route. This allows the user to reselect a travel route.

[0180] Below the map image, the user terminal device 31 displays, for example, information about taxi companies, information about destinations, information about payment methods, etc. In this example, the user terminal device 31 displays information about taxi companies that indicates that "all taxis" are available for dispatch and that the taxi is scheduled to arrive in approximately 1 to 3 minutes.

[0181] If the user wishes to use a specific taxi company, the user can specify and set in advance the taxi company that will calculate the advance fare and dispatch the taxi. 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 may, for example, display a list of taxi company names. 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 selected taxi company. Each taxi company listed on the taxi company selection screen also displays information indicating whether or not the taxi can be used with an advance fare, such as a label or icon with the text "Advance fare support." This allows the user to easily determine which taxi companies support the advance fare system. When the user selects a taxi company, the taxi-dispatch application server device 11 limits the taxi companies that will be used for advance fare calculation and dispatch to the selected taxi companies. Furthermore, the vehicle-dispatch application server device 11 may set the selected taxi company as a default setting for the target of subsequent 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 is set in advance.

[0183] The user terminal device 31 displays a button labeled "Select a taxi" below this information. When the user terminal device 31 receives 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 at the top for displaying messages to the user, one or more areas below that for providing options for selecting a taxi, and a button labeled "Call a taxi" 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 "Coupon will be applied when you get off the taxi" are displayed in the top 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, estimated time until boarding, icons of one or more taxi companies, and radio buttons for accepting selections. In this example, three advance fare options are shown: 11,200 yen, 11,500 yen, and 11,800 yen, but the number of options displayed may be one, two, four, or more.

[0187] In the illustrated example, after the advance fare for each option, information regarding the estimated time until the taxi ride is displayed, such as "board in approximately 2 to 5 minutes," "board in approximately 2 to 7 minutes," and "board in approximately 1 minute." For example, the ride-hailing application server device 11 acquires information about taxis located near the user's desired boarding point from the information processing device 13 of each taxi company, and calculates the estimated time until the taxi ride based on the distance between the location of each taxi and the user's desired boarding point, etc. 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 the taxi ride on the taxi selection screen. Note that the estimated time information does not necessarily have to be displayed on the taxi selection screen.

[0188] In the taxi information processing system according to this embodiment, advance fares are calculated according to calculation standards established for each taxi company, and there may be multiple taxi companies with the same calculated advance fares. In this case, multiple taxi companies with the same advance fares are grouped together and displayed as a single option on the taxi selection screen. In the illustrated example, one or more icons (shown as a roughly square shape with rounded corners) are displayed below the advance fares for each option. Each icon represents one taxi company. In this example, two taxi companies are grouped under the first option with an advance fares of 11,200 yen, three taxi companies are grouped under the second option with an advance fares of 11,500 yen, and one taxi company is grouped under the third option with an advance fares of 11,800 yen. Note that although each icon is represented by a solid color in this figure, in reality, each icon displays information such as the logo or name of the taxi company.

[0189] Although not shown in the drawings, 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. For example, the detailed information may display the presence, type, and amount of discounts that can be applied 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, the initial fare and late-night surcharge coefficient used in 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 an operation such as a touch on one of the radio buttons is accepted, the user terminal device 31 assumes that the corresponding option is selected and highlights the selected option to indicate that it is selected. In the illustrated example, the selected state of the option for advance fare of 11,200 yen is indicated by highlighting the rectangular area with a thick border.

[0191] The "Call a taxi" button provided at the bottom of the taxi selection screen is used to notify the taxi selection result to the vehicle-dispatch application server device 11. This button accepts operation when any option on the taxi selection screen is selected, and does not accept operation when all options are unselected. 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 the present embodiment, it is vehicle-dispatch application server device 11 that determines which of the multiple taxi companies grouped in the options to dispatch a taxi from. Therefore, in the taxi information processing system according to the second embodiment, the user indirectly selects a taxi by selecting a taxi advance fare, and the final selection of the taxi is left to vehicle-dispatch application server device 11. When the advance fare for taxis from multiple taxi companies is the same, 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 vehicle-dispatch application server device 11 may be based on any criteria. Alternatively, an operation to select one taxi company from multiple taxi companies may be further received from the user at user terminal device 31.

[0193] In addition, the processing of dispatching a taxi by the taxi dispatch application server device 11 after the result of taxi selection is transmitted from the user terminal device 31 to the taxi dispatch application server device 11 is the same as the processing described in the previous embodiment, so a detailed description of the processing will be 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 input of a desired boarding point and a destination point by the 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 dispatch vehicles to this region (step S203).

[0195] The processing unit 111 transmits information relating to the calculated 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 user's selection of a driving route 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 relating to the selected driving route, advance fee, etc. (step S206).

[0196] The processing unit 111 determines whether or not the user has performed a route change request operation based on whether or not the "route selection" button provided on the information display screen has been operated (step S207). If a route change request operation has been performed (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 performs the above-mentioned process.

[0197] If a route change request operation has not 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 from the user, via the user terminal device 31 that displays the taxi selection screen, a selection of one advance fare from one or more advance fare options displayed on the taxi selection screen (step S209). The processing unit 111 determines a taxi company based on the advance fare selected by the user, and makes a taxi dispatch request to the information processing device 13 of this taxi company (step S210), thereby terminating the processing.

[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 service 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 service based on the fare calculated by the taxi meter.

[0199] This change may occur, for example, when the taxi driver changes the destination point for personal reasons and the user does not agree to the taxi operation at the pre-determined advance fare. It may also occur, for example, when the user arrives late at the desired pickup point and the taxi driver charges an additional fee for waiting time. The change from the advance fare to the metered fare may occur 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 metered fare after the taxi has started traveling from the desired pickup point to the destination, the user pays the fare for the trip up to that point. At this time, for example, the user may pay the predetermined advance fare, or the amount to be paid by the user may be calculated based on the distance traveled up to that point and the advance fare, or the user may pay a flat cancellation fee, or an amount other than these. Furthermore, the amount to be paid by the user when changing from the advance fare to the metered fare may be calculated based on different criteria depending on whether the change is at the user's request or the taxi driver's request.

[0201] The taxi information processing system according to the second embodiment configured as described 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 user's selection of an advance fare from among multiple advance fare options, 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 select the advance fare that is most suitable for them when using a taxi.

[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, and accepts the selection of an advance fare, and also affixes information such as an icon that identifies one or more operating companies included in the group to the displayed options. This simplifies the options when there are many operating companies, and also enables the user to easily recognize which operating company provides the advance fare they are selecting.

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

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

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

[0206] The embodiments disclosed herein are illustrative in all respects and should not be considered 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 meaning and scope of the claims. [Explanation of symbols]

[0207] 2. Taxi 3 users 11. Ride-hailing app server device 12 Vehicle 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 Dispatch Processing Department 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. A taxi information processing method in which a computer determines a travel route based on a desired boarding point and a destination point of a user who wishes to ride in a taxi, and determines a prepayment fare for the taxi ride based on the determined travel route, The computer outputting a combination of the travel route and the advance fee as a plurality of options; Accepting a selection of a travel route based on the selection of the option by the user; Remember the fare calculation standards for each taxi operating company, Calculating advance fees for a plurality of operating companies based on the stored fee calculation criteria; Outputs advance fee options that group together operating companies with the same calculated advance fee, The options are provided with information identifying the operating companies included in the group; Accepting an advance fee selection based on the selection of said option; Confirm your selection at the pre-paid rate, Taxi information processing method.

2. A taxi information processing method in which a computer determines a travel route based on a desired boarding point and a destination point of a user who wishes to board a taxi, and determines a prepayment fare for the taxi ride based on the determined travel route, The computer Output multiple driving route options, The options are provided with minimum and maximum advance fees calculated for a plurality of operating companies; Accepting a selection of a travel route based on the selection of the option by the user; Remember the fare calculation standards for each taxi operating company, Calculating advance fees for a plurality of operating companies based on the stored fee calculation criteria; Output the calculated multiple advance fee options, Accepting an advance fee selection based on the selection of said option; Confirm your selection at the pre-paid rate, Taxi information processing method.

3. If multiple travel routes cannot be determined based on the user's desired boarding point and destination point, determine one travel route.

3. The taxi information processing method according to claim 1 or 2.

4. determining multiple driving routes according to multiple different priority conditions; 4. A taxi information processing method according to claim 1.

5. When determining a plurality of different driving routes, the plurality of driving routes include a driving route that uses a toll road and a driving route that does not use a toll road, 4. The taxi information processing method according to claim 1, wherein the taxi information processing method comprises:

6. 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 travel route determination unit that determines a taxi travel route based on information related to the desired boarding point and the destination point received by the user terminal device, and an advance fare determination unit that determines an advance fare related to the taxi ride based on the determined travel route; Equipped with The user terminal device outputting a combination of the travel route and the advance fee as a plurality of options; Accepting a selection of a travel route based on the selection of the option by the user; The advance fee determination unit of the server device Remember the fare calculation standards for each taxi operating company, Calculating advance fees for a plurality of operating companies based on the stored fee calculation criteria; The user terminal device Outputs advance fee options that group together operating companies with the same calculated advance fee, The options are provided with information identifying the operating companies included in the group; Accepting an advance fee selection based on the selection of said option; the advance fee determination unit of the server device determines the selected advance fee as the accepted fee; Taxi information processing system.

7. 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 travel route determination unit that determines a taxi travel route based on information related to the desired boarding point and the destination point received by the user terminal device, and an advance fare determination unit that determines an advance fare related to the taxi ride based on the determined travel route; Equipped with The user terminal device Output multiple driving route options, The options are provided with minimum and maximum advance fees calculated for a plurality of operating companies; Accepting a selection of a travel route based on the selection of the option by the user; The advance fee determination unit of the server device Remember the fare calculation standards for each taxi operating company, Calculating advance fees for a plurality of operating companies based on the stored fee calculation criteria; The user terminal device The server device outputs a plurality of options for advance fees calculated; Accepting an advance fee selection based on the selection of said option; the advance fee determination unit of the server device determines the advance fee selected by the user terminal device; Taxi information processing system.

8. A server device comprising: a communication unit that communicates with 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; and a processing unit that determines a plurality of travel routes based on the desired boarding point and the destination point of the user who wishes to board a taxi, and determines a prepayment fare for the taxi ride based on the determined travel routes, Remember the fare calculation standards for each taxi operating company, The processing unit outputting a plurality of combinations of the travel route and the advance fee to a user terminal device as options; Accepting a selection of a travel route based on the selection of the option by the user via the user terminal device; Calculating advance fees for a plurality of operating companies based on the stored fee calculation criteria; outputting to the user terminal device advance fee options that group together operating companies that have the same calculated advance fee; The options are provided with information identifying the operating companies included in the group; Accepting a selection of an advance fee based on the selection of the option via the user terminal device; Confirm your selection at the pre-paid rate, Server device.

9. A server device comprising: a communication unit that communicates with a user terminal device having a reception unit that receives input of information relating to a desired boarding point and destination point of a user who wishes to board a taxi; and a processing unit that determines a plurality of driving routes based on the desired boarding point and destination point of a user who wishes to board a taxi, and determines an advance fare for the taxi ride based on the determined driving routes, Remember the fare calculation standards for each taxi operating company, The processing unit outputting a plurality of travel route options to a user terminal device; The options are provided with minimum and maximum advance fees calculated for a plurality of operating companies; accepting a selection of a travel route based on a selection of the option by the user via the user terminal device; Calculating advance fees for a plurality of operating companies based on the stored fee calculation criteria; outputting the calculated plurality of advance fee options to the user terminal device; Accepting a selection of an advance fee based on the selection of the option via the user terminal device; Confirm your selection at the pre-paid rate, Server device.

10. A user terminal device comprising: a reception unit that receives input of information relating to a desired boarding point and a destination point of a user who wishes to board a taxi; a travel route determination unit that determines a taxi travel route based on the information relating to the desired boarding point and the destination point received by the reception unit; a communication unit that communicates with a server device having a pre-payment fare determination unit that determines a pre-payment fare for the taxi ride based on the determined travel route; and a processing unit; The processing unit outputting a combination of the travel route and the advance fee as a plurality of options; Accepting a selection of a travel route based on the selection of the option by the user; outputting advance fare options that group together operating companies with the same advance fare calculated by the advance fare determination unit of the server device based on the fare calculation standard for each taxi operating company; The options are provided with information identifying the operating companies included in the group; accepting a selection of an advance fee based on the selection of said option; User terminal equipment.

11. A user terminal device comprising: a reception unit that receives input of information relating to a desired boarding point and a destination point of a user wishing to board a taxi; a driving route determination unit that determines a driving route for the taxi based on the information relating to the desired boarding point and the destination point received by the reception unit; a communication unit that communicates with a server device having an advance fare determination unit that determines an advance fare for the taxi ride based on the determined driving route; and a processing unit, The processing unit Output multiple driving route options, The options are provided with minimum and maximum advance fees calculated for a plurality of operating companies; Accepting a selection of a travel route based on the selection of the option by the user; outputting a plurality of advance fare options for a plurality of operating companies calculated by the advance fare determination unit of the server device based on the fare calculation standard for each taxi operating company; accepting a selection of an advance fee based on the selection of said option; User terminal equipment.

12. A computer program that causes a computer to execute a process of determining a plurality of travel routes based on a desired boarding point and a destination point of a user who wishes to board a taxi, and determining a prepayment fare for the taxi ride based on the determined travel routes, outputting a plurality of combinations of the travel route and the advance fee to a user terminal device as options; Accepting a selection of a travel route based on the selection of the option by the user via the user terminal device; Calculate advance fares for multiple taxi operating companies based on the fare calculation standards for each operating company, outputting to the user terminal device advance fee options that group together operating companies that have the same calculated advance fee; The options are provided with information identifying the operating companies included in the group; Accepting a selection of an advance fee based on the selection of the option via the user terminal device; Confirm your selection with the pre-selected price A computer program that causes the computer to execute a process.

13. A computer program that causes a computer to execute a process of determining a plurality of driving routes based on a desired boarding point and a destination point of a user who wishes to ride in a taxi, and determining an advance fare for the taxi ride based on the determined driving routes, outputting a plurality of travel route options to a user terminal device; The options are provided with minimum and maximum advance fees calculated for a plurality of operating companies; accepting a selection of a travel route based on a selection of the option by the user via the user terminal device; Calculate advance fares for multiple taxi operating companies based on the fare calculation standards for each operating company, outputting the calculated plurality of advance fee options to the user terminal device; Accepting a selection of an advance fee based on the selection of the option via the user terminal device; Confirm your selection with the pre-selected price A computer program that causes a computer to perform a process.

Images