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

Abstract

This invention provides a taxi information processing method, a taxi information processing system, and a taxi terminal system that are expected to provide users with a sense of security. [Solution] The taxi information processing method according to this embodiment determines a route based on the desired pick-up location and destination of a user who wishes to ride in a taxi, determines the advance fare for the taxi ride based on the determined route, displays the determined 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 route in a database. In addition, the determined advance fare may be displayed on a fare display device installed in the taxi while the user is riding in the taxi.

Description

Technical Field

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

Background Art

[0002] Conventionally, fares for using taxis have been calculated based on the driving distance and driving time of the taxis, etc. When a user uses a taxi, the fare increases as the taxi drives, and when the taxi arrives at the destination, the fare is determined, and the user pays the determined fare to the taxi driver. For the payment of taxi fares, in addition to cash, payments using a credit card or electronic money, etc. can be made.

[0003] In Patent Document 1, a cardless payment system that does not require a credit card payment terminal has been proposed. In this cardless payment system, when a customer wishes to make a card payment to a merchant, the merchant enters the payment amount and the customer terminal's phone number into the merchant terminal and transmits it to the operator server to request payment. The operator server transmits approval information to the customer terminal, and if the customer determines that there is no mistake in the approval information, the customer terminal requests payment from the intermediary server. The intermediary server requests billing from 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

Summary of the Invention

Problems to be Solved by the Invention

[0005] In traditional taxi services, users may feel anxious because they don't know the fare they have to pay until the taxi arrives at their destination.

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

[0007] According to one embodiment, a taxi information processing method determines a route based on the desired pick-up location and destination of a user who wishes to ride in a taxi, determines the advance fare for the taxi ride based on the determined route, displays the determined 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 route in a database. [Effects of the Invention]

[0008] In one embodiment, it is expected to provide users with a sense of security. [Brief explanation of the drawing]

[0009] [Figure 1] Overview of the Taxi Information Processing System [Figure 2] Configuration of the ride-hailing application server device [Figure 3] Price calculation database [Figure 4] User Database [Figure 5] Taxi DB [Figure 6] Order Management Database [Figure 7] Dispatch history database [Figure 8] User terminal device configuration [Figure 9] Configuration of a payment company's payment server equipment [Figure 10]Settlement Company's Settlement DB [Figure 11] Configuration of Taxi Terminal Device [Figure 12] Configuration of Fare Meter and Passenger Terminal Device [Figure 13] Ride Request Processing Diagram [Figure 14] Ride Request Screen on User Terminal Device [Figure 15] Ride Request Acceptance Screen on Taxi Terminal Device [Figure 16] Cancellation Flow from Taxi [Figure 17] Cancellation Reception Screen on Taxi Terminal Device [Figure 18] Settlement Approval Screen [Figure 19] Overall Settlement Processing Flow [Figure 20] Processing Flow of User Terminal Device [Figure 21] Processing Flow of Ride-hailing App Server Device [Figure 22] Processing Flow of Ride-hailing App Server Device[[ID=3,7]] [Figure 23] Processing Flow of Taxi Terminal Device [Figure 24] Processing Flow of Taxi Terminal Device [[ID=4,4]] [Figure 25] Information Storage Processing of Ride-hailing App Server Device <000,0097>Ride History Screen [Figure 27] Fare Calculation DB of Variant 1<OO00100> [Figure 28] Route Selection Screen of Embodiment 2 [Figure 29] Information Display Screen of Embodiment 2 [Figure 30] Information Display Screen of Embodiment 2 [Figure 31] Taxi Selection Screen of Embodiment 2 [Figure 32] Processing Flow of Ride-hailing App Server Device of Embodiment 2

Modes for Carrying Out 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. However, the present invention is not limited to these examples, and is intended to include all modifications within the meaning and scope of the claims, as defined by the claims.

[0011] <Embodiment 1> <System Overview> Figure 1 is a schematic diagram illustrating the overview of the taxi information processing system according to this embodiment. The taxi information processing system according to this embodiment comprises a dispatch application server device 11, a taxi terminal system 20 installed in one or more taxis 2, and a user terminal device 31 used by one or more users 3. Although the taxi information processing system according to this embodiment can process data simultaneously and in parallel for multiple taxis 2 and multiple users 3, Figure 1 only shows one taxi 2 and one user 3.

[0012] The 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, for example, via a network such as the Internet. The dispatch application server device 11 performs taxi dispatch processing and taxi fare calculation processing in cooperation with the information processing device 13 and the payment server device 14. In this embodiment, the dispatch application server device 11 is a single device, but it is not limited to this, and the dispatch application server device 11 may be realized by the cooperation of multiple devices. Furthermore, the dispatch application server device 11 may 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, user 3 can request the dispatch of a taxi 2 using the user terminal device 31. At this time, user 3 can use the user terminal device 31 to specify the desired pick-up location and destination (drop-off location) of the taxi 2. If the desired pick-up location is the user's current location, the user specifies the destination, and the desired pick-up location may be determined based on location information obtained from GPS (Global Positioning System) or the like. The taxi dispatch request from the user is transmitted from the user terminal device 31 to the dispatch application server device 11 via a network such as a mobile phone communication network, wireless LAN (Local Area Network), or the Internet.

[0014] The dispatch application server device 11 determines the route for taxi 2 based on the user 3's desired pick-up location and destination, and calculates the fare for taxi 2 traveling along this route. In the taxi information processing system according to this embodiment, the fare calculated by the dispatch application server device 11 is fixed as the advance fare, and user 3, who uses taxi 2, pays this advance fare. The information on the route determined by the dispatch application server device 11 and the fixed advance fare is transmitted from the dispatch application server device 11 to the user terminal device 31 and presented to user 3. At this time, the dispatch application server device 11 may transmit information on multiple routes and advance fares as candidates, and user 3 may select one of the candidates. In addition, if user 3 has a discount coupon or the like, the dispatch application server device 11 may calculate the advance fare with this discount applied.

[0015] In this embodiment, the amount predetermined by the taxi information processing system is called the "advance fare," but this is just one example, and it may be called by various names such as "advance-determined fare," "advance fare," "determined fare," "advance-determined fee," or "determined fee." The "advance fare" includes the fare for the taxi's journey, and other charges such as highway tolls, pick-up fees, or parking fees may or may not be included in the "advance fare." If highway tolls or other charges are not included in the "advance fare," the amount that the passenger ultimately pays will be the predetermined "advance fare" plus the highway tolls or other charges.

[0016] When user 3 approves the route and pre-paid fare presented on the user terminal device 31, a taxi 2 is dispatched. User 3's approval is sent from the user terminal device 31 to the dispatch application server device 11, and in response, the dispatch application server device 11 processes the data to determine which taxi 2 to dispatch to user 3. The dispatch application server device 11 manages information such as the location and whether or not there are passengers for multiple taxis 2, and selects one taxi 2 from among the multiple taxis 2 that is suitable for the request. For example, the dispatch application server device 11 sends the determined route and confirmed pre-paid fare information to a taxi 2 located near user 3's desired pick-up location and requests dispatch.

[0017] In this embodiment, the taxi terminal system 20 installed in taxi 2 includes devices such as a taxi terminal device 21, a fare meter 22, and a passenger terminal device 23. The taxi terminal device 21 is a terminal device used by the driver of taxi 2, and receives dispatch requests from the dispatch application server device 11, displays information on the route and pre-paid fare, and accepts the driver's choice of whether or not to accept the dispatch request. If the dispatch request is accepted, the taxi terminal device 21 notifies the dispatch application server device 11, and the dispatch application server device 11 further notifies the user terminal device 31. As a result, a dispatch reservation is made between user 3 and taxi 2, and taxi 2 heads to user 3's desired pick-up location, picks up user 3, and then heads to the destination.

[0018] For example, if taxi 2 breaks down or is involved in an accident while en route to user 3's desired pick-up location and is unable to proceed, the driver of taxi 2 can cancel the dispatch using the taxi terminal device 21. Upon receiving the cancellation request, the taxi terminal device 21 notifies the dispatch application server device 11 of the cancellation, and the dispatch application server device 11 notifies the user terminal device 31 of the cancellation. The dispatch application server device 11 may then attempt to dispatch another taxi 2.

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

[0020] After taxi 2 arrives at the destination, user 3 makes the payment (settlement) of the predetermined pre-paid fare. In this embodiment, payment of the pre-paid fare may be made using a credit card registered in advance with the taxi information processing system, or by using a QR (Quick Response) code (registered trademark) or barcode. However, cash payment or payment by electronic money may also be used. During the settlement process, the passenger terminal device 23 of the taxi terminal system 20 displays the same amount as the pre-paid fare displayed on the fare meter 22 as the settlement fare to be paid by user 3, along with information such as the user's name and credit card information. The passenger terminal device 23 is, for example, installed behind the driver's seat of taxi 2 and is a device that displays various information such as settlement information and advertising information to the user sitting in the back seat, and a tablet terminal device or the like may be used. When the passenger terminal device 23 receives an operation from user 3 to approve the payment of the displayed settlement fare, it notifies the settlement server device 14 of this fact via the taxi terminal device 21 and the dispatch application server device 11, etc. The payment server device 14 is a device managed and operated by the payment company, and processes the payment of the taxi fare for user 3 in response to payment notifications from the ride-hailing app server device 11.

[0021] In the taxi information processing system according to this embodiment, the advance fare determined by the dispatch application server device 11 will not be changed by subsequent use of taxi 2. However, for discounts that cannot be applied unless the user presents a certificate or other identification to the taxi driver, such as a disability discount, the discount may be applied to the advance fare at the settlement processing stage, and the advance fare may be changed. In this case, the taxi driver will verify the user's identification and then perform a discount application operation, for example, using the fare meter 22 or the taxi terminal device 21. In response to this operation, the passenger terminal device 23 will display the settlement fare with the discount applied to the advance fare, and settlement will be made at the discounted settlement fare.

[0022] In this embodiment, for example, tolls for toll roads traveled by taxi 2, or parking fees used by taxi 2, are not included in the advance fare. If such additional charges are incurred, the advance fare may be changed. In this case, the driver of taxi 2 can, for example, operate the taxi terminal device 21 to input the additional charges. In response to this operation, the passenger terminal device 23 displays the settlement amount, which is the advance fare plus the additional charges, and payment is made at this settlement amount.

[0023] Furthermore, if user 3 wishes to change their destination after boarding taxi 2 and taxi 2 has started traveling, the taxi information processing system according to this embodiment will process the payment of the advance fare at that point, regardless of the actual distance traveled and travel time of taxi 2. After that, user 3 may use taxi 2 to reach the other destination using the normal fare system in which the fare is added according to the distance traveled and travel time, or they may use taxi 2 after a new advance fare has been determined.

[0024] In the taxi information processing system according to this embodiment, the dispatch application server device 11 stores and accumulates information about taxi 2 in a dispatch history DB (database). The dispatch application server device 11 stores the route and predetermined fare decided by user 3 before boarding taxi 2 in the dispatch history DB, associating them with information such as a user ID to identify user 3, a taxi ID to identify taxi 2, and the date and time. The taxi terminal device 21 has a receiver that receives GPS signals and can obtain the actual route of taxi 2 based on the GPS signals. The dispatch application server device 11 obtains the actual route of taxi 2 from the taxi terminal device 21 and stores it in the dispatch history DB along with the predetermined route. This information stored in the dispatch history DB can be used, for example, to respond to complaints later, to improve the route determination process, or to improve the automated driving process.

[0025] <Device configuration> Figure 2 is a block diagram showing the configuration of the ride-hailing application server device 11 according to this embodiment. The ride-hailing application server device 11 according to this embodiment is configured to include a processing unit 111, a storage unit 112, a communication unit (transceiver) 113, a display unit 114, and an operation unit 115, etc. The processing unit 111 is configured to use a processing unit such as a CPU (Central Processing Unit), an MPU (Micro-Processing Unit), or a GPU (Graphics Processing Unit), ROM (Read Only Memory), and RAM (Random Access Memory), etc. The processing unit 111 reads and executes the server program 112a stored in the storage unit 112, thereby performing various processes such as determining the taxi's route and calculating the taxi's advance fare.

[0026] The storage unit 112 is configured using a large-capacity storage device such as a hard disk. The storage unit 112 stores various programs executed by the processing unit 111, and various data necessary for processing by the processing unit 111. In this embodiment, the storage unit 112 stores the server program 112a executed by the processing unit 111, and is also provided with multiple 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 of this system, a taxi DB 112d for storing information about taxis that are dispatched by this system, an order management DB 112e for managing orders for taxi dispatch from users, and a dispatch history DB 12 for storing information related to taxi operations.

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

[0028] Figure 3 is a schematic diagram showing one example configuration of the fare calculation DB 112b. The fare calculation DB 112b in this embodiment is a table in which information such as "company ID," "region," "initial fare," "initial distance," "additional unit," "additional fare," and "coefficient" are stored in association with each other. In this embodiment, the dispatch application server device 11 calculates the advance fare for a taxi using the following equation (1), and the value to be substituted into equation (1) is stored in advance in the fare calculation DB 112b. When a user uses a discount coupon, the discount is applied to the advance fare calculated using equation (1) to determine the final advance fare. Note that the calculation formula for the advance fare and the values ​​stored in the fare calculation DB 112b are examples only and are not limited to these.

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

[0030] The "Company ID" in the fare calculation DB112b is identification information that identifies the taxi operating company, and in the illustrated example, IDs such as "Company A" and "Company B" are stored. "Region" is information indicating the region covered by each operating company, and in the illustrated example, regions 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 region covered by each operating company is predetermined. There may be multiple operating companies whose covered regions overlap in part or all. In the illustrated example, the covered region is determined by prefecture, but it may also be determined by city, ward, town or village, or it may be information that identifies a region by combining multiple coordinates such as latitude and longitude.

[0031] The "initial fare" is the minimum fare that a user pays when 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 travels for the "initial fare," and in the illustrated example, distances such as "1500m" and "1800m" are stored. The "additional fare unit" is the distance for which the fare is added after the taxi has traveled the "initial distance," and in the illustrated example, distances such as "200m" and "180m" are stored. The "additional fare" is the fare added for travel exceeding the "additional fare 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 pre-paid fare. In this embodiment, the "coefficient" is predetermined for each day of the week and time slot, such as "Monday 0:00-12:00", "Monday 1:00-12:00", ..., "Monday 23:00-12:00", "Tuesday 0:00-12:00", ..., "Sunday 23:00-12:00", and numerical values ​​such as "1.2", "1.1", "1.5", and "1.4" are stored in the fare calculation DB112b. The "initial fare", "initial distance", "additional unit", "additional fare", and "coefficient" in the fare calculation DB112b are information that defines the pre-paid fare calculation formula (1).

[0033] The fare calculation DB 112b is created in advance and stored in the storage unit 112 of the dispatch application server device 11. The fare calculation DB 112b may be modified or updated at appropriate times, such as when a new operating company enters the market or when fares are revised.

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

[0035] The "User ID" in User DB112c is unique identification information assigned to each user. 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 themselves, or it may be determined automatically by, for example, the dispatch application server device 11. The "User Name," "Telephone Number," and "Email Address" are personal information of each user, and are abbreviated as "..." in this diagram.

[0036] The user DB112c in this embodiment allows for the registration of multiple "payment information" entries for a single user, which are shown in the figure as "payment information 1," "payment information 2," and so on. "Payment information" is information about the payment method used by the user when paying for a taxi fare, and in the illustrated example, information such as "credit card" and "electronic money" is stored. Note that these "credit card" and "electronic money" entries are abbreviated, and in reality, information necessary for payment processing, such as the credit card number and expiration date, is stored.

[0037] In this embodiment, a single user can own multiple coupons. The user DB 112c can store information on multiple "owned coupons" for a single user, which are shown in this figure as "owned coupon 1," "owned coupon 2," "....". "Owned coupons" are information about coupons owned by the user, and in the illustrated example, 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 shown in Figure 4 are examples only and are not limited to them.

[0038] Figure 5 is a schematic diagram showing one example configuration of the taxi DB112d. The taxi DB112d according to this embodiment is a database in which information such as "taxi ID," "company ID," "driver," "current location," and "tariff status" is stored in association with each other. "Taxi ID" is unique identification information assigned to a taxi, and in the illustrated example, information such as "Taxi A01," "Taxi A02," and "Taxi B01" is stored as taxi IDs assigned to the managed taxis. "Company ID" is identification information that identifies the taxi operating company, and in the illustrated example, IDs such as "Company A" and "Company B" are stored. "Driver" is information about the taxi driver, and may include information such as the driver's name and telephone number. Information such as "Taxi ID," "Company ID," and "Driver" can be modified and added as appropriate, for example, in response to the addition or reduction of taxis.

[0039] The "Current Location" in the taxi database 112d is information about the taxi's current location based on GPS. In this diagram, it is abbreviated as "...", but in reality, coordinate information such as latitude and longitude is stored. The "Tariff Status" is information indicating the status of the taxi, such as "Vacant," "On the move," or "On call." The dispatch application server device 11 periodically communicates with the taxi terminal device 21 of the taxi 2 to obtain information such as the taxi 2's current location and status, and stores it in the taxi database 112d.

[0040] Figure 6 is a schematic diagram showing one example configuration of the order management DB 112e. The order management DB 112e is a database that stores information related to taxi dispatch orders received by the dispatch application server device 11 from the user terminal device 31. The order management DB 112e in this embodiment is a database in which information such as "date and time", "user ID", "taxi ID", "pre-booked route", "pre-booked fare", "booked pick-up time", "booked pick-up location", "booked drop-off location", and "booking number" are stored in association with each other.

[0041] The "Date and Time" field in the order management DB112e is the date and time when the user ordered a taxi. In the example shown, 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 example shown, information such as "User 123" and "User 054" is stored. The "Taxi ID" is unique identification information assigned to each taxi. In the example shown, information such as "Taxi A33" and "Taxi D21" is stored as the taxi IDs of the taxis used by the user.

[0042] The "pre-booked route" is information about the taxi's route determined by the dispatch application server device 11 based on the user's entered pick-up location and destination location. If the dispatch application server device 11 presents the user with multiple route options, the "pre-booked route" stores information about the one route selected by the user. In this figure, the route information is abbreviated as "...", but in reality, the route information is stored as multiple coordinate information or vector information connecting, for example, the pick-up location to the destination location. The "pre-booked fare" is the taxi fare calculated and determined by the dispatch application server device 11, and in the illustrated example, information such as "1234 yen" and "3210 yen" is stored. The dispatch application server device 11 calculates the taxi's distance based on the pre-booked route and calculates the pre-booked fare using the information from the fare calculation DB 112b shown in Figure 3 and the above-mentioned equation (1).

[0043] "Pick-up reservation time" is information about the date and time the user wishes to board the taxi. In the example shown, information such as "2020 / 1 / 20 11:20" and "2020 / 1 / 20 13:00" is stored. "Pick-up reservation location" is the desired pick-up location where the user wishes to board the taxi. "Drop-off reservation location" is the desired destination where the user wishes to drop off the taxi. In this diagram, the information for "Pick-up reservation location" and "Drop-off reservation location" is abbreviated as "...", but in reality, coordinate information indicating the location, such as latitude and longitude, is stored.

[0044] The "reservation number" is unique identification information assigned to each user's taxi dispatch request. The dispatch application server device 11 generates a "reservation number" and stores it in the order management DB 112e when it receives, for example, a taxi dispatch request from a user and the taxi's acceptance of the request. 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, when the pre-travel route is determined, when the pre-fare is finalized, or when the request is accepted by the taxi.

[0046] Although not shown in Figure 6, the order management DB112e may also store information such as payment method, coupons used, whether or not advance charges were canceled, boarding date and time, alighting date and time, and payment amount.

[0047] Figure 7 is a schematic diagram showing one example configuration of the dispatch history DB12. The dispatch history DB12 according to this embodiment is a database in which information such as "reservation number," "date and time," "user ID," "taxi ID," "actual route," "payment fare," "actual boarding time," "actual boarding location," "actual alighting location," "cancellation status," "payment method," "coupon," and "discount" are stored in association with each other.

[0048] The "Reservation Number" is unique identification information assigned to each user's taxi dispatch request. The information stored in the Order Management DB112e and the information stored in the Dispatch History DB12 are linked by the "Reservation Number". The "Date and Time" is information such as the date and time when the user requested a taxi dispatch, and in the illustrated example, information such as "2020 / 1 / 20 11:12" and "2020 / 1 / 20 11:26" is stored. The "User ID" is the ID of the user who used the taxi, and in the illustrated example, information such as "User 123" and "User 054" is stored. The "Taxi ID" is unique identification information assigned to each taxi, and in the illustrated example, information such as "Taxi A33" and "Taxi D21" is stored as the taxi ID of the taxi used by the user.

[0049] "Actual route" refers to information about the route actually traveled by the taxi carrying the user. In this diagram, the route information is abbreviated as "...", but "Actual route" can be a set of coordinate information of the taxi's current location transmitted from the taxi terminal device 21. "Payment fare" is the fare that the user ultimately paid (paid) after using the taxi, and in the illustrated example, information such as "1234 yen" and "3210 yen" is stored. Basically, "advance fare" and "payment fare" are the same amount, but if discounts such as disability discounts are applied after the advance fare is determined, or if toll road fees are added, the "advance fare" and "payment fare" may be different amounts.

[0050] "Actual boarding time" refers to information about the time when a user boarded the taxi. For example, when a user boards a taxi and the driver changes the taxi from a pickup state to a fare-driven state using the taxi terminal device 21 or fare meter 22, the taxi terminal device 21 notifies the dispatch application server device 11 of the boarding time, and in response to this notification, the dispatch application server device 11 can store the information in the "Actual boarding time" field of the dispatch history DB 12. "Actual boarding location" is the location where the user actually boarded the taxi. "Actual alighting location" is the location where the user actually alighted from the taxi. The dispatch application server device 11 stores the "Actual boarding location" and "Actual alighting location" information in the dispatch history DB 12 based on the taxi status information and location information obtained from the taxi terminal device 21. In this figure, the "Actual boarding location" and "Actual alighting location" information are abbreviated as "...", but in reality, coordinate information indicating the location, such as latitude and longitude, is stored, respectively. Furthermore, if information on the "actual boarding location" and "actual alighting location" can be obtained from the "actual travel route" mentioned above, the dispatch history DB12 does not need to include the "actual boarding location" and "actual alighting location" fields.

[0051] The "Cancellation Status" field indicates whether the user has canceled the pre-determined "Advance Fee" and "Advance Route." In the example shown, the information "No" is stored, indicating that no cancellation has occurred. For example, if the user changes their destination, the "Advance Fee" and "Advance Route" are canceled, and the information "Yes" is stored in the "Cancellation Status" field.

[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 coupons used by the user for the fare. In the illustrated example, "100 Yen Discount" information, which deducts 100 yen from the fare, and "None" information, which indicates that no coupon was used, are stored. In this embodiment, discounts from coupons are assumed to be reflected in the "Advance Fare". "Discount" is information about discounts applied after the user has boarded the taxi, such as a disability discount. "Yes" information is stored if a discount was applied, and "None" information is stored if no discount was applied.

[0053] The ride-hailing application server device 11 adds and modifies information in the ride-hailing history DB 12 at various times, such as when a user requests a taxi, when a user boards a taxi, when the taxi arrives at the destination, or when payment processing for the fare is completed.

[0054] The communication unit 113 of the ride-hailing application server device 11 communicates with various devices via a network N, which includes the company's LAN (Local Area Network), wireless LAN, or the Internet. In this embodiment, the communication unit 113 communicates with the information processing device 13, payment server device 14, taxi terminal device 21, and user terminal device 31, etc., via the network N. The communication unit 113 transmits data received from the processing unit 111 to other devices and provides data received from other devices to the processing unit 111.

[0055] The display unit 114 is configured using a liquid crystal display or the like, and displays various images and characters based on the processing of the processing unit 111. The operation unit 115 receives user operations and notifies the processing unit 111 of the received operations. For example, the operation unit 115 may be an input device such as a mouse and a keyboard, and these input devices may be configured to be detachable from the dispatch application server device 11. Alternatively, for example, the operation unit 115 may receive user operations via an input device such as a touch panel provided on the surface of the display unit 114.

[0056] The storage unit 112 may be an external storage device connected to the dispatch application server device 11. The dispatch application server device 11 may be a multicomputer system comprising multiple computers, or it may be a virtual machine virtually constructed by software. The dispatch application server device 11 does not necessarily have a user interface such as a display unit 114 and an operation unit 115; in this case, for example, an administrator or the like may operate the dispatch application server device 11 via another terminal device.

[0057] Furthermore, in the dispatch application server device 11 according to this embodiment, the processing unit 111 reads and executes the server program 112a stored in the storage unit 112, thereby realizing the route processing unit 111a, order processing unit 111b, advance fare processing unit 111c, dispatch processing unit 111d, payment processing unit 111e, dispatch history processing unit 111f, and display processing unit 111g as software-based functional units.

[0058] The route processing unit 111a performs the process of determining the route the taxi should take based on the desired pick-up point and destination point entered by the user. The method for determining the route can be the same as the method used by existing car navigation systems, so a detailed explanation is omitted. The route processing unit 111a creates multiple candidate routes from the desired pick-up point to the destination point, and sends the multiple candidates to the user terminal device 31 to accept the user's selection of a route. The route processing unit 111a determines the one route selected by the user as the pre-routed route the taxi should take. However, if it is not possible to create multiple routes, the route processing unit 111a may create only one route.

[0059] The order processing unit 111b processes taxi dispatch orders from users by sending and receiving information with the user terminal device 31. The order processing unit 111b obtains information such as the desired pick-up location and destination from the user via the user terminal device 31. The order processing unit 111b stores the obtained information in the order management DB 112e of the storage unit 112.

[0060] The advance fare processing unit 111c calculates the advance fare that the user should pay for using the taxi, based on the taxi's route determined by the route processing unit 111a and the information in the fare calculation DB 112b stored in the memory unit 112. Since the route processing unit 111a presents the user with multiple route options, the advance fare processing unit 111c calculates the advance fare for each option and presents the user with the advance fare options. When calculating the advance fare, the advance fare processing unit 111c determines, for example, the taxi dispatching company based on the user's desired pick-up location. The advance fare processing unit 111c obtains information such as the initial fare and additional fares for the determined company from the fare calculation DB 112b and substitutes this obtained information into equation (1) above. 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 equation (1) above. As a result, the advance fare processing unit 111c can calculate the advance fare using equation (1). The pre-payment processing unit 111c presents the calculated pre-payment to the user and finalizes the pre-payment when the user approves it. Once the pre-payment is finalized, the user is unable to change the payment.

[0061] The dispatch processing unit 111d dispatches a taxi to the requesting user after the advance fare processing unit 111c has determined the advance fare. The dispatch processing unit 111d refers to the taxi DB 112d in the storage unit 112 and selects a taxi that is, for example, available and whose current location is close to the user's desired pick-up location, and requests the selected taxi to be dispatched to the taxi terminal device 21. The taxi terminal device 21 of this taxi notifies the driver that the dispatch request has been received and accepts the driver's choice of whether or not to accept the request. If the driver chooses to accept the request, 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 the taxi reservation between the taxi and the user, and the taxi picks up the user at the desired pick-up location and transports the user to the destination according to the determined route. If the dispatch request is not accepted, the dispatch processing unit 111d selects another taxi and requests its dispatch. The dispatch processing unit 111d may also request the dispatch of another taxi without waiting for a response, for example, if it does not receive a response from the taxi driver within a predetermined time after the dispatch request.

[0062] The dispatch processing unit 111d also processes cancellations from taxis 2 that have accepted a dispatch request. In the taxi information processing system according to this embodiment, taxi drivers can cancel their acceptance of a dispatch request if, for example, they are unable to go to the pick-up location specified by the user due to various factors such as an accident or breakdown. When the taxi terminal device 21 receives a cancellation operation from the driver, it notifies the dispatch application server device 11 of the cancellation. The dispatch processing unit 111d of the dispatch application server device 11, upon receiving the cancellation notification, notifies the user terminal device 31 of the user to whom the dispatch request was canceled. The user terminal device 31, upon receiving the cancellation notification, displays on the display unit 314 that the dispatch request has been canceled. This cancels the reservation that had been made between the user and the taxi. The user may then make a new dispatch request.

[0063] The payment processing unit 111e processes the payment for taxi fares with users by relaying information between the taxi terminal device 21 and the payment server device 14. The payment processing unit 111e obtains the payment fare, payment method, and other necessary payment information from the taxi terminal device 21 and requests the payment server device 14, which is managed and operated by the payment company, to process the payment. In response to this request, the payment server device 14 processes the payment for the taxi fare for this user and notifies the dispatch application server device 11 of the completion of the payment process. When the payment processing unit 111e receives notification from the payment server device 14 that the payment process has been completed, it sends this notification to the taxi terminal device 21.

[0064] The dispatch history processing unit 111f stores information obtained during a series of events related to a user's use of a taxi in the order management DB 112e or dispatch history DB 12 of the storage unit 112. For example, when a user approves the route and advance fare using the user terminal device 31, the dispatch history processing unit 111f stores the date and time information and user ID, etc., in the order management DB 112e or dispatch history DB 12. The dispatch history processing unit 111f also stores the taxi ID of a taxi in the order management DB 112e or dispatch history DB 12 when a taxi driver accepts a dispatch request using the taxi terminal device 21. The dispatch history processing unit 111f also periodically acquires location information from a taxi carrying a passenger and stores the acquired location information as the actual route. The dispatch history processing unit 111f also stores the fare when the taxi arrives at its destination and payment is completed. The timing of information storage and the content of information stored by the dispatch history processing unit 111f are examples only and are not limited to these examples.

[0065] The display processing unit 111g performs the process of displaying various information stored in the order management DB 112e and the dispatch history DB 12 on the display unit 114. The display processing unit 111g receives, for example, a date and time and a taxi ID from the operation unit 115, and reads information corresponding to the specified date and time and taxi ID from the order management DB 112e and the dispatch history DB 12. Based on the read information, the display processing unit 111g can, for example, display a map image on the display unit 114 and overlay the pre-travel route and the actual travel route on this map image. The display processing unit 111g may also display the pre-fare and the settlement fare along with these travel routes. The display of information stored in the order management DB 112e and the dispatch history DB 12 may be performed in any manner. In this embodiment, the dispatch application server device 11 displays the information stored in the dispatch history DB 12 on its own display unit 114, but it is not limited to this, and information may be displayed on the display unit of another device via communication over a network.

[0066] Figure 8 is a block diagram showing the configuration of the 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 storage unit 312, a communication unit (transceiver) 313, a display unit 314, an operation unit 315, and a GPS receiver unit 316, etc. The processing unit 311 is configured to use a processing unit such as a CPU or MPU, ROM, and RAM, etc. The processing unit 311 performs various processes related to taxi dispatch requests, etc., by reading and executing a program 312a stored in the storage unit 312.

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

[0068] The program 312a in 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 it via communication and stores it in the storage unit 312. However, the program 312a may also be written to the storage unit 312 during the manufacturing stage of the user terminal device 31, for example. For example, the program 312a may be read by the user terminal device 31 from a recording medium such as a memory card or optical disc and stored in the storage unit 312. For example, the program 312a may be read by a writing device from a recording medium and written to the storage unit 312 of the user terminal device 31. The program 312a may be provided by distribution via a network, or by being provided in a form recorded on a recording medium.

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

[0070] The communication unit 313 communicates with various devices via a network N, which includes public mobile phone communication networks and the internet. In this embodiment, the communication unit 313 communicates with the ride-hailing application server device 11 via the network N. The communication unit 313 transmits data provided by the processing unit 311 to the ride-hailing application server device 11 and provides data received from the ride-hailing application server device 11 to the processing unit 311.

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

[0072] Furthermore, 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, thereby realizing the display processing unit 311a, the dispatch request unit 311b, and the approval acceptance unit 311c, etc., as software-based functional units in the processing unit 311. The display processing unit 311a performs the processing of displaying various screens related to taxi dispatch on the display unit 314. For example, the display processing unit 311a displays various screens such as a menu screen, an input screen for the desired pick-up location and destination, a screen that presents information on the taxi's route and advance fare, and a screen that completes the 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 processes requests for taxi dispatch. The dispatch request unit 311b receives the user's specified pick-up location and destination location on an input screen displayed by the display processing unit 311a. The dispatch request unit 311b transmits a taxi dispatch request to the dispatch application server device 11, including the received information on the pick-up location and destination location, and the user ID 312b stored in the storage unit 312. The pick-up location may be, for example, the current location based on the GPS signal received by the GPS receiver unit 316, or it may be a specific place or facility specified by the user. The dispatch application server device 11 determines the taxi's route and calculates the advance fare according to the pick-up location and destination location given along with the dispatch request.

[0074] The approval reception unit 311c processes the user's approval of the taxi route and pre-paid fare determined in response to the taxi dispatch request. Information regarding the taxi route and pre-paid fare determined by the dispatch application server device 11 in response to the 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 reception unit 311c receives the user's approval of the displayed taxi route and pre-paid fare at the operation unit 315 and notifies the dispatch application server device 11 of the approval. If the dispatch application server device 11 has created multiple routes and pre-paid fare options, the display unit 314 will display multiple options, and the approval reception unit 311c will accept the selection of one route and pre-paid fare from the multiple options and notify the dispatch application server device 11 that the selected route and pre-paid fare have been approved. If the user performs an operation indicating that they do not approve the route and pre-paid fare, the approval reception unit 311c notifies the dispatch application server device 11 of the cancellation of the taxi dispatch request. Furthermore, if the user does not approve the pre-arranged route and fare, the system may be configured to allow for taxi dispatch requests using the standard fare calculation method (calculating the fare based on the distance traveled using the taxi meter).

[0075] Figure 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 storage unit 142, a communication unit (transceiver) 143, etc. The processing unit 141 is configured to use a processing unit such as a CPU, MPU or GPU, ROM, etc. The processing unit 141 reads and executes the server program 142a stored in the storage unit 142, thereby performing various processes related to the payment processing of taxi fares by users.

[0076] The storage unit 142 is configured using a large-capacity storage device such as a hard disk. The storage unit 142 stores various programs executed by the processing unit 141, and various data necessary for the processing of the processing unit 141. In this embodiment, the storage unit 142 stores the server program 142a executed by the processing unit 141. The storage unit 142 is also provided with a settlement DB 142b that stores information necessary for settlement 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 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 also be written to the storage unit 142 during the manufacturing stage of the payment server device 14, for example. Alternatively, the server program 142a may be obtained by the payment server device 14 via communication from another remote server device, for example. 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 by distribution via a network, or it may be provided in a form recorded on the recording medium 98.

[0078] Figure 10 is a schematic diagram showing one example configuration of the payment DB 142b. The payment DB 142b in this embodiment is a database in which information such as "credit card ID," "expiration date," "balance," and "credit limit" are stored in association with each other. The "credit card ID" is identification information assigned to a credit card and may be the so-called card number. The "expiration date" is information about the deadline by which the credit card can be used. The "balance" and "credit limit" are information about restrictions on the use of the credit card. For example, a "credit limit" of 300,000 yen per month may be set, and the "balance" is the value obtained by subtracting the amount already used from this credit limit.

[0079] The communication unit 143 of the payment server device 14 communicates with various devices via a network N, including the company LAN, wireless LAN, or the internet. In this embodiment, the communication unit 143 communicates with the ride-hailing application server device 11 and the like 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 multicomputer comprising multiple computers, or it may be a virtual machine virtually constructed by software. Furthermore, the payment server device 14 is not limited to the above configuration and may include, for example, a reading unit that reads information stored on a portable storage medium, an operation unit that accepts operation input, or a display unit that displays images.

[0081] Furthermore, in 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, thereby realizing the confirmation processing unit 141a and the payment processing unit 141b as software-based functional units. The confirmation processing unit 141a performs processing to confirm the information necessary for payment of the fare by a user who has used a taxi, in response to a payment request from the ride-hailing application server device 11. For example, the confirmation processing unit 141a obtains information such as the credit card ID and payment amount provided along with the payment request from the ride-hailing application server device 11, and checks the correctness of the obtained information and whether payment is possible by referring to the payment DB 142b in the storage unit 142. If the confirmation processing unit 141a determines that payment is possible, the payment processing unit 141b performs processing to pay the taxi fare by the user using the registered credit card.

[0082] Figure 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 a device fixed near the driver's seat of the taxi 2, for example, or it may be a device that can be carried by the driver, such as a smartphone or tablet terminal device. The taxi terminal device 21 is composed of a processing unit 211, a storage unit 212, a communication unit (transceiver) 213, a display unit 214, an operation unit 215, and a GPS receiver unit 216, etc. The processing unit 211 is composed of a processing unit such as a CPU or MPU, ROM, and RAM, etc. The processing unit 211 reads and executes a program 212a stored in the storage unit 212, thereby performing various processes such as accepting dispatch requests from users and canceling accepted dispatch requests.

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

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

[0085] Taxi ID 212b is an identifier that uniquely identifies taxi 2, and is predetermined by the operating company or other entity managing taxi 2 and stored in the memory unit 212. In this embodiment, the identifier assigned to taxi 2 is used as taxi ID 212b, but for example, the identifier assigned to the driver of taxi 2 may also be used as taxi ID 212b.

[0086] The communication unit 213 communicates with various devices via a network N, including public mobile phone networks and the internet. In this embodiment, the communication unit 213 communicates with an externally located ride-hailing application server device 11, as well as with a fare meter 22 and a passenger terminal device 23 installed in the taxi 2. The communication unit 213 may use different communication protocols for communication with the ride-hailing application server device 11 and communication with the fare meter 22 and passenger terminal device 23. For example, the communication unit 213 communicates with the ride-hailing application server device 11 via a public mobile phone network. Alternatively, the communication unit 213 may communicate with the fare meter 22 and passenger terminal device 23 via wired communication through communication lines installed in the taxi 2, or via wireless communication such as Bluetooth®.

[0087] The display unit 214 is configured using a liquid crystal display or the like, and displays various images and characters based on the processing of the processing unit 211. The operation unit 215 receives driver operations via input devices such as mechanical buttons or a touch panel provided on the surface of the display unit 214, and notifies the processing unit 211 of the received operations. The GPS receiver unit 216 receives radio waves transmitted from GPS satellites and provides the information contained in the received radio waves to the processing unit 211. Based on the information provided by the GPS receiver unit 216, the processing unit 211 can perform processing to determine the location (e.g., latitude and longitude) of the taxi terminal device 21. The communication unit 213 relays communication between the dispatch application server device 11 and the fare meter 22 and passenger terminal device 23.

[0088] Furthermore, 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, thereby realizing the display processing unit 211a, the acceptance acceptance unit 211b, the cancellation acceptance unit 211c, etc., as software-based functional units in the processing unit 211. The display processing unit 211a performs the processing of displaying various screens related to the dispatch request of taxi 2 on the display unit 214. For example, the display processing unit 211a displays various screens such as a menu screen, a screen that presents information on the travel route and advance fare related to the dispatch request from the user, and a screen that accepts operations such as accepting or canceling the dispatch request. Image data for displaying these screens is stored in the storage unit 212 together with the program 212a.

[0089] Furthermore, the display processing unit 211a communicates with the fare meter 22 and passenger terminal device 23 installed in the taxi 2 via the communication unit 213, causing the fare meter 22 and passenger terminal device 23 to display various information. For example, the display processing unit 211a transmits information regarding the finalized advance fare to the fare meter 22, causing the advance fare to be displayed on the fare meter 22. Also, for example, after the taxi 2 arrives at its destination, the display processing unit 211a transmits information regarding the final fare to the passenger terminal device 23, causing the final fare to be displayed on the passenger terminal device 23.

[0090] The acceptance reception unit 211b processes the operation to accept a dispatch request from a user. The display processing unit 211a of the taxi terminal device 21, which has received a dispatch request from the user from the dispatch application server device 11, displays detailed information about the dispatch request on the display unit 214, namely the user's desired pick-up location and destination, the determined route, and the confirmed advance fare. When this information is displayed, the acceptance reception unit 211b receives a selection from the driver via the operation unit 215, asking whether or not to accept the dispatch request. The acceptance reception unit 211b notifies the dispatch application server device 11 of the selection result of whether or not to accept the dispatch request.

[0091] The cancellation reception unit 211c processes the operation to cancel an accepted dispatch request. After the acceptance reception unit 211b accepts the dispatch request, the display processing unit 211a displays information such as the user's desired pick-up location on the display unit 214 to prompt the driver to send taxi 2 to the desired pick-up location. In this state, the cancellation reception unit 211c accepts the operation to cancel the dispatch request. If the cancellation operation is accepted, the cancellation reception unit 211c notifies the dispatch application server device 11 of the cancellation of the dispatch request.

[0092] Figure 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 a taxi 2, and displays the fare for using the taxi 2. The fare meter 22 is composed of a processing unit 221, a communication unit (transceiver) 222, a display unit (display) 223, and an operation unit 224, etc.

[0093] The processing unit 221 is composed of a processing unit such as a CPU or MPU, ROM, and RAM. The processing unit 221 performs various processes related to displaying fares and receiving driver operations. Although not shown in the diagram, sensors installed in the taxi 2 are connected to the fare meter 22, and the processing unit can calculate the fare for the taxi 2 according to the distance traveled measured by the sensors.

[0094] The communication unit 222 communicates with the taxi terminal device 21 and the passenger terminal device 23 via wired communication through communication lines installed in the taxi 2, or via wireless communication such as Bluetooth. The display unit 223 is configured using an LCD panel or the like and displays various images and characters based on processing by the processing unit 221. The operation unit 224 receives the driver's operations via input devices such as mechanical buttons, and notifies the processing unit 221 of the received operations.

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

[0096] The control unit 224 is equipped with, for example, a switch to accept an operation to switch between displaying the advance fare and the regular fare, a button to start payment processing after arriving at the destination, and a button to apply discounts such as disability discounts. In response to the operation to start payment processing, the payment amount is displayed on the passenger terminal device 23, and in response to the operation of the discount button, the discount is applied and the payment amount 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 rear seat of the taxi 2. The passenger terminal device 23 may be a device fixed to the taxi 2, or it may be a portable device such as a tablet terminal device. In this embodiment, the passenger terminal device 23 is mounted behind the driver's seat of the taxi 2. The passenger terminal device 23 is composed of a processing unit (processor) 231, a communication unit (transceiver) 232, a display unit (display) 233, and an operation unit 234, etc.

[0098] The processing unit 231 is composed of a processing unit such as a CPU or MPU, ROM, and RAM. The processing unit 231 performs various processes such as displaying the fare to the user who used the taxi, receiving the operations necessary for settling the fare, and performing settlement processing according to the received operations.

[0099] The communication unit 232 communicates with the taxi terminal device 21 and the fare meter 22 via wired communication through communication lines installed in the taxi 2, or via wireless communication such as Bluetooth. The display unit 233 is configured using an LCD panel or the like, and displays various images and characters based on processing by the processing unit 231. The operation unit 234 receives 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 received operations.

[0100] Furthermore, the passenger terminal device 23 may display images such as advertisements on its display unit 233 while the user is in the taxi 2 and the taxi 2 is traveling to the destination. After the taxi 2 arrives at the destination, the passenger terminal device 23 displays the payment amount based on the payment amount information provided by the taxi terminal device 21 or the fare meter 22. The payment amount displayed by the passenger terminal device 23 is either a predetermined advance fare or a fare calculated based on the distance traveled and time, etc. If a discount such as a disability discount is applied to these fares, the display is updated to show the discounted payment amount. After displaying the payment amount, the passenger terminal device 23 accepts an approval operation from the user for the payment processing. Upon receiving the approval operation, the passenger terminal device 23 transmits this information to the dispatch application server device 11 via the taxi terminal device 21.

[0101] When taxi 2 arrives at the destination and the payment fare is displayed on the passenger terminal device 23, and the user approves the payment of this fare, the payment server device 14 processes the payment. The passenger terminal device 23, having approved the payment, notifies the dispatch application server device 11 of this fact via the taxi terminal device 21. The dispatch application server device 11 sends the user ID of the user processing the payment 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 dispatch application server device 11, the payment server device 14 processes the payment using credit cards, electronic money, etc.

[0102] <Taxi fare processing> Figure 13 is a schematic diagram illustrating the process from requesting a taxi dispatch to its confirmation using the taxi information processing system according to this embodiment. In the taxi information processing system according to this embodiment, users requesting a taxi dispatch must download program 312a to the user terminal device 31 and complete the necessary procedures for using the system in advance (e.g., agreeing to the terms of service and registering personal information). In the following explanation, it will be assumed that these procedures have been completed, and details of these procedures will be omitted.

[0103] A user who wishes to use a taxi launches program 312a on their user terminal device 31 and selects, for example, the "Request a taxi" item from the menu screen. The user terminal device 31 displays a screen on the display unit 314 for specifying the desired pick-up location and destination location, and accepts input of the desired pick-up location and destination location from the user. The desired pick-up location is initially set to the current location, and 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 pick-up location. The destination location may be entered as the result of a search based on the name of a place or building, for example, as an address or postal code, for example, as a point on a map, or by any other method. If the desired pick-up location is to be specified as something other than the current location, it may be entered in the same way as the destination location. The user terminal device 31 sends a taxi request message, including the entered desired pick-up location and destination location, and the user's user ID 312b, to the taxi dispatch application server device 11.

[0104] Upon receiving a dispatch request message from the user terminal device 31, the dispatch application server device 11 determines which taxi company will dispatch a taxi to the user based on the desired pick-up location and destination location included in the dispatch request message. The dispatch application server device 11 selects a taxi company capable of dispatching a taxi to the desired pick-up location by, for example, comparing the desired pick-up location included in the dispatch request message with the "region" information in the fare calculation DB 112b shown in Figure 3.

[0105] Next, the dispatch application server device 11 determines the taxi's route based on the desired pick-up location and destination location included in the dispatch request message. The dispatch application server device 11 also calculates the advance fare for using the taxi based on the determined route and the fare calculation DB 112b in the storage unit 112. It is preferable that the dispatch application server device 11 presents the user with multiple routes and advance fares as options. For example, the dispatch application server device 11 may determine two routes as options: one that uses toll roads and one that does not. In this embodiment, the toll for using toll roads is not included in the advance fare, but this is not limited to this, and the toll for toll roads may be included in the advance fare. The dispatch application server device 11 also refers to the user DB 112c in the storage unit 112 based on the user ID included in the dispatch request message, and if the user possesses a discount coupon, it obtains information about the coupon and calculates the advance fare with the discount of the obtained coupon applied. The dispatch app server device 11 sends a message containing information about the determined route and the calculated advance fare to the user terminal device 31 of the requesting user.

[0106] When the user terminal device 31 receives a message from the ride-hailing application server device 11, it displays the route and pre-charge information contained in the message on the display unit 314 and accepts the user's request for approval of the route and pre-charge. If there are multiple route and pre-charge options at this time, the user terminal device 31 displays information for all of the options, accepts the user's request to select one of these options, and accepts the user's request for approval of the selected route and pre-charge.

[0107] Figure 14 is a schematic diagram showing an example of a ride request screen displayed by the user terminal device 31. The illustrated ride request screen assumes that the ride request server device 11 has provided the user terminal device 31 with two candidate routes, Route 1 and Route 2, as candidates for the travel route and advance fare. The user terminal device 31 displays a map image on the display unit 314 and overlays the two candidate travel routes as Route 1 and Route 2 on this map image. In this figure, the desired pick-up location is indicated by "S", the destination location is indicated by "G", Route 1, the first candidate travel route, is shown with a solid line, and Route 2, the second candidate, is shown with a dashed line.

[0108] On the ride request screen, information about two possible routes is displayed in the area below the map image, divided into left and right sections. In this example, the left section displays information for "Route 1," and the right section displays information for "Route 2." The left section displays the text "Route 1," and below it, the text "Pre-charge 11,200 yen," indicating the calculated pre-charge, and further below that, a button labeled "Request a ride." The right section displays the text "Route 2," and below it, the text "Pre-charge 13,000 yen," and further below that, a button labeled "Request a ride." By touching either of the two "Request a ride" buttons located side-by-side at the bottom of the ride request screen, the user can select one of the two presented routes.

[0109] When the user terminal device 31 receives a touch operation on either of the two "Request a ride" buttons, it considers that the user has approved the route and pre-paid fare for the corresponding route, and sends a message to the ride-hailing application server device 11 notifying the user that the route and pre-paid fare have been approved. Although the ride-hailing request screen shown in this figure is not intended to accept operations that reject the presented route and pre-paid fare, it may be configured to accept operations that, for example, reject the presented route and pre-paid fare and request a ride using the fare meter.

[0110] Upon receiving a message from the user terminal device 31 approving the route and advance fare, the dispatch application server device 11 selects a taxi from among the multiple taxis registered in the taxi DB 112d of the storage unit 112, for example, one that is available and located closest to the desired pick-up location. The dispatch application server device 11 sends a dispatch request message to the taxi terminal device 21 of the selected taxi, containing information on the route and advance fare, as well as information about the user who made the request.

[0111] When the taxi terminal device 21 receives a dispatch request message from the dispatch application server device 11, it displays the route and pre-paid fare information included in the message on the display unit 214 and accepts the driver's operation to accept the dispatch request with this route and pre-paid fare. Figure 15 is a schematic diagram showing an example of the 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 overlays the route on this map image. In this figure, the user's desired pick-up location is indicated by "S", the destination location by "G", the taxi's current location by "Current", and the route is shown by a solid line.

[0112] The taxi terminal device 21 displays information related to the dispatch request below the map image. In this figure, the taxi terminal device 21 displays information about the user, such as "Requester: User A," information about the payment method, such as "Payment Method: Credit Card," information about applicable coupons, such as "Discount Coupon: 100 Yen Discount," and information about the confirmed advance fare, such as "Advance Fare 11,200 Yen." However, the taxi terminal device 21 does not need to notify the taxi driver of the advance fare. That is, the taxi terminal device 21 may request a dispatch without notifying the taxi driver whether the fare is based on an advance fare or calculated using the fare meter 22.

[0113] The taxi terminal device 21 displays a button labeled "Accept" below this information. The taxi terminal device 21 accepts the driver's acceptance of the user's dispatch request by receiving a touch operation on the "Accept" button. Upon receiving the acceptance, the taxi terminal device 21 sends a message to the dispatch application server device 11 notifying that the dispatch request has been accepted. The dispatch application server device 11 receives the acceptance notification message from the taxi terminal device 21 and sends 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 that the acceptance of the user's dispatch request has been completed. Note that the dispatch request acceptance screen shown in this figure is not intended to accept operations that reject the dispatch request, but it may be configured to accept operations that reject the presented dispatch request, for example. Furthermore, if the taxi driver is not notified of the fare in advance on the dispatch request acceptance screen, the taxi terminal device 21 may, after receiving the acceptance operation from the driver, display information such as whether or not the dispatch request has a predetermined fare, and if so, the amount of the predetermined fare.

[0114] Figure 16 is a schematic diagram illustrating the cancellation process for dispatch requests by the taxi information processing system according to this embodiment. A taxi driver who accepts a dispatch request from a user dispatches the taxi to the pick-up location specified 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 cancellations of the accepted dispatch request before the user boards the taxi. For example, if the taxi driver is unable to go to the pick-up location due to an accident or breakdown, the taxi driver can cancel the request using the taxi terminal device 21. Upon receiving the cancellation request, the taxi terminal device 21 sends a message to the dispatch application server device 11 notifying it that the dispatch request has been canceled. The dispatch application server device 11 receives the cancellation notification message from the dispatch application server device 11 and sends 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 it that the dispatch request has been canceled.

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

[0116] If the dispatch request is not canceled and the taxi arrives at the desired pick-up location, 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 pre-determined fare. The fare meter 22 does not display the fare which is added as needed according to the taxi's distance traveled and time, but displays the pre-determined fare notified by the taxi terminal device 21.

[0117] After the taxi carrying the passenger arrives at the destination, the user needs to pay (settle) the fare for the taxi ride. The taxi's passenger terminal device 23 displays a payment screen and accepts the user's request for payment of the taxi fare. Figure 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 information such as "Payment Method: Credit Card" as the payment method and "Discount Coupon: 100 Yen Discount" as the applicable coupon, and also displays the pre-determined fare as the settlement amount, "Settlement Amount 11,200 Yen". The passenger terminal device 23 may also display the taxi's route overlaid on a map image on the payment screen. The route displayed at this time may be a pre-determined route, the actual route traveled by the taxi, or both may be displayed overlaid.

[0118] The passenger terminal device 23 displays a button labeled "Pay" below this information. The passenger terminal device 23 accepts user approval for payment processing for the displayed payment amount by receiving touch operations on the "Pay" button. After receiving user approval for payment processing, the taxi information processing system performs the payment processing.

[0119] Figure 19 is a schematic diagram illustrating the payment processing by the taxi information processing system according to this embodiment. The dispatch application server device 11 transmits information about the advance fare to the taxi terminal device 21 of the taxi that has accepted the dispatch request. The taxi terminal device 21, upon receiving this information, transmits the advance fare information 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 display the advance fare, respectively. The fare meter 22 and the passenger terminal device 23 continue to display the advance fare until the taxi arrives at its destination.

[0120] When a taxi carrying a passenger arrives at its destination, the taxi driver can initiate the payment process by operating a payment button located on the control panel 224 of the fare meter 22. When the fare meter 22 receives a payment request via the control panel 224, it sends a message to the taxi terminal device 21 notifying the driver of the payment request. The taxi terminal device 21 then notifies the passenger terminal device 23 that the payment request has been received. The passenger terminal device 23 displays the pre-paid fare as the payment amount and also displays a payment screen (see Figure 18) on its display unit, where it accepts the user's approval request for payment.

[0121] Upon receiving payment processing approval from the user on the payment screen, the passenger terminal device 23 sends a message to the taxi terminal device 21 notifying the user that the payment processing has been approved. Upon receiving this message, the taxi terminal device 21 sends a message to the dispatch application server device 11 notifying the user of payment approval, which includes information about the user and payment charges.

[0122] Upon receiving payment approval notification from the taxi terminal device 21, the dispatch application server device 11 refers to the user DB 112c to obtain information regarding the payment method registered for the user paying the fare. For example, the dispatch application server device 11 obtains information such as the credit card company and card number used by the user for payment. The dispatch application server device 11 sends a payment request, including the card number and fare information, to the payment server device 14 of the credit card company used for payment.

[0123] The payment server device 14 processes payment using a credit card or electronic money based on information from the dispatch application server device 11. Details of the payment processing by the payment server device 14 are omitted from this explanation. After the payment processing is completed, the payment server device 14 notifies the dispatch application server device 11 of the completion of the payment. The dispatch application server device 11 notifies the taxi terminal device 21 of the completion of the payment and stores information regarding this dispatch in the order management DB 112e and dispatch history DB 12 of the storage unit 112. The taxi terminal device 21 notifies the passenger terminal device 23 of the completion of the payment processing, and the passenger terminal device 23 displays a message indicating that the payment processing has been completed on the display unit 233.

[0124] In this embodiment, after the taxi arrives at the destination, the user can request the application of a discount, such as a disability discount. After the taxi driver verifies the certificate or other document indicating eligibility for the discount, the driver can apply the discount to the fare by operating the discount application button on the operation unit 224 of the fare meter 22. Although not shown in Figure 19, if additional charges such as toll road fees are required, the taxi driver performs a predetermined operation regarding the additional charges on the taxi terminal device 21 or the fare meter 22. This operation results in the application of a fare that includes the additional charges added to the pre-paid fare.

[0125] In Figure 19, the process for applying this discount (and additional charges, etc.) is shown enclosed in a dashed line. When the fare meter 22 receives a discount request via the operation unit 224, it sends a message to the taxi terminal device 21 notifying the operator of the discount. Upon receiving this message, the taxi terminal device 21 calculates the settlement fare by applying the discount to the pre-determined advance fare and sends a message to the fare meter 22 and the passenger terminal device 23 notifying them of the calculated settlement fare. Upon receiving this message, the fare meter 22 displays the newly calculated settlement fare. Upon receiving this message, the passenger terminal device 23 updates the settlement fare displayed on the settlement screen with the settlement fare included in the newly received message and applies the discount.

[0126] In this embodiment, if, for example, the user requests a change of destination after the fare has been determined in advance and the user has boarded the taxi, but before arriving at the destination, the user will pay the pre-determined fare regardless of whether or not they have arrived at the destination. For example, if the user requests a change of destination verbally, the taxi driver will stop the taxi and operate the control unit 224 of the fare meter 22 to start the pre-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 will start driving to the changed destination, and the fare will be added according to the distance traveled and the time, etc. However, the driving route from the current location to the new destination and the pre-payment may be determined in advance.

[0127] In the case of taxis operating on a pre-paid fare system, changes to the destination or route require agreement between the taxi driver and the passenger. However, there may be situations where agreement cannot be obtained for some reason, making it difficult to settle the pre-paid fare on the spot. In such cases, the pre-paid fare may be canceled, and the fare may be calculated and settled based on, for example, the distance traveled and time spent so far. For this reason, even when the taxi is operating on a pre-paid fare system, the fare meter 22 calculates the fare based on the distance traveled and time spent in the background.

[0128] <Flowchart> Figure 20 is a flowchart showing the processing steps 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 a location input reception screen on the display unit 314 for receiving input of the desired pick-up location and destination location from a user who wishes to dispatch a taxi (step S1). Next, the dispatch request unit 311b of the processing unit 311 receives input of the desired pick-up location and destination location based on the user's operation received by the operation unit 315 while the location input reception screen is displayed (step S2). The dispatch request unit 311b sends a dispatch request message, including the received desired pick-up location and destination location, as well as the user ID 312b stored in the storage unit 312, to the dispatch application server device 11 (step S3).

[0129] The approval receiving unit 311c of the processing unit 311 determines whether it has received a message containing information such as the route and advance fare sent by the dispatch application server device 11 in response to the dispatch request sent in step S3 (step S4). If the message has not been received (S4: NO), the approval receiving unit 311c waits until it receives a message. If a message containing information such as the route and advance fare has been received (S4: YES), the display processing unit 311a displays the dispatch request screen illustrated in Figure 14 on the display unit 314 based on the information contained in the received message (step S5). The approval receiving unit 311c accepts the operation of selecting the taxi route and approving the advance fare based on the user operation received by the operation unit 315 while the dispatch request screen is being displayed (step S6). The approval receiving unit 311c sends a message to the dispatch application server device 11 notifying that approval has been given for the route and advance fare contained in the message received in step S4 (step S7).

[0130] The processing unit 311 determines whether or not it has received a message notifying it that the dispatch request has been received (step S8). If it has not received a message notifying it that the dispatch request has been received (S8: NO), the processing unit 311 waits until it receives a message notifying it that the dispatch request has been received. If it has received a message notifying it that the dispatch request has been received (S8: YES), the display processing unit 311a displays a message on the display unit 314 notifying it that the dispatch request has been received (step S9), and terminates the process.

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

[0132] When a dispatch request message is received (S21: YES), the processing unit 111 checks whether it is possible to use a taxi with a pre-paid fare based on the desired pick-up location or destination location included in the received message (step S22). For example, if the taxi company that serves the desired pick-up location does not support pre-paid fares, the user cannot use a taxi with a pre-paid fare. If it is not possible to use a taxi with a pre-paid fare, the processing unit 111 interrupts the process according to this flowchart and performs the dispatch process for using a taxi with a fare based on the conventional distance traveled. Note that the conventional dispatch process is not shown in this diagram.

[0133] If it is possible to use a taxi with a prepaid fare, the processing unit 111 determines which taxi company will dispatch a taxi based on the desired pick-up location or destination location 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 the taxi's route based on the desired pick-up location and destination location included in the received message (step S24). The route processing unit 111a may determine multiple routes as candidates. Next, the prepaid fare processing unit 111c of the processing unit 111 calculates the prepaid fare for each route based on the taxi's route determined in step S24 and the fare calculation DB 112b of the storage unit 112 (step S25). At this time, the prepaid fare processing unit 111c determines the taxi operating company based on the desired pick-up location, and can calculate the prepaid fare by substituting the numerical value specified in the fare calculation DB 112b associated with the operating company and the distance of the route determined in step S24 into equation (1) above. The advance fare processing unit 111c may also check whether the user who requested the ride has a discount coupon by referring to the user DB 112c, and if the user has a discount coupon, it may obtain information about the discount coupon from the user DB 112c and calculate the advance fare with the discount related to the obtained coupon applied.

[0134] The processing unit 111 sends a message containing information about the travel route determined in step S24 and the advance fare calculated in step S25 to the user terminal device 31 that requested the ride (step S26). The processing unit 111 determines whether or not it has received an approval message from the user terminal device 31 in response to this message (step S27). If it does not receive an approval message (S27: NO), for example, if it receives a message canceling the ride request or if it does not receive an approval message even after a certain period of time has elapsed, the processing unit 111 discards the ride request and terminates processing.

[0135] If an approval message is received (S27: YES), the dispatch processing unit 111d of the processing unit 111 selects one taxi from among the multiple taxis registered in the taxi DB 112d of the storage unit 112 (step S28). At this time, the dispatch processing unit 111d can select a taxi that is closest to the desired pick-up location specified in the received dispatch request message and is also available. The dispatch processing unit 111d sends a dispatch request message containing information such as user information, route and advance fare to the taxi terminal device 21 of the selected taxi (step S29).

[0136] The dispatch processing unit 111d determines whether it has received a message notifying the user that the dispatch request sent in step S29 has been accepted (step S30). If it does not receive a message accepting the dispatch request (S30: NO), for example, if it receives a message notifying the user that the dispatch request has been rejected, or if it does not receive a message accepting the request even after a certain period of time has elapsed, the dispatch processing unit 111d returns to step S28 and repeatedly selects a taxi and sends the dispatch request message. If it receives a message accepting the dispatch request (S30: YES), the dispatch processing unit 111d sends a message to the user terminal device 31 that the dispatch request has been accepted (step S31). The dispatch history processing unit 111f of the processing unit 111 stores information such as the date and time, user ID, taxi ID, route, and advance fare for the accepted dispatch request in the order management DB 112e and dispatch history DB 12 of the storage unit 112 (step S32).

[0137] Subsequently, the processing unit 111 determines whether it has received a message from the taxi terminal device 21 of the taxi that accepted the dispatch request, notifying it that the dispatch request is being canceled (step S33). If a cancellation message is received (S33: YES), the processing unit 111 sends a message notifying the cancellation, including information such as the taxi ID of the taxi involved in the cancellation, to the user terminal device 31 (step S34), and terminates the process.

[0138] If no message notifying cancellation has been received (S33: NO), the processing unit 111 determines whether or not a message notifying payment approval has been received from the taxi terminal device 21 (step S35). If no payment approval message has 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 is received (S35: YES), the payment processing unit 111e of the processing unit 111 sends information regarding the payment fee and user to the payment server device 14 and requests the payment server device 14 to process the payment for the taxi fare (step S36).

[0139] Subsequently, the payment processing unit 111e determines whether or not it has received a payment completion notification from the payment server device 14 (step S37). If it has not received a payment completion notification (S37: NO), the payment processing unit 111e waits until it receives a payment completion notification. If it has received a payment completion notification (S37: YES), the payment processing unit 111e notifies the taxi terminal device 21 of the payment completion (step S38). The dispatch history processing unit 111f of the processing unit 111 stores information such as the actual travel route and payment amount for the user and taxi that performed the payment processing in the order management DB 112e and the dispatch history DB 12 (step S39), and then terminates the process.

[0140] Figures 23 and 24 are flowcharts showing the processing steps performed by the taxi terminal device 21 according to this embodiment. The acceptance reception unit 211b of the processing unit 211 of the taxi terminal device 21 according to this embodiment determines whether or not it has received a dispatch request message from the dispatch application server device 11 (step S71). If it has not received a dispatch request message (S71: NO), the acceptance reception unit 211b waits until it receives a message. If it has received a dispatch request message (S71: YES), the display processing unit 211a of the processing unit 211 displays the dispatch request acceptance screen illustrated in Figure 15 on the display unit 214 based on the information contained in the received dispatch request message (step S72).

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

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

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

[0144] The processing unit 211 communicates with the fare meter 22 to determine whether a discount operation has been performed at 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 settlement amount displayed on the passenger terminal device 23 in step S80 and updates the display to the settlement amount after the discount has been applied (step S82). Although not shown in Figure 24, in the case of additional charges such as toll road fees, the charges can be added to the settlement amount (advance fare) in accordance with the operation performed by the driver at the fare meter 22 or the taxi terminal device 21.

[0145] If no discount operation has been performed (S81: NO), or if the discount has been applied and the payment fee updated in step S82, the processing unit 211 communicates with the passenger terminal device 23 to determine whether the passenger terminal device 23 has accepted the approval operation for payment processing for the displayed payment fee (step S83). If the approval operation has not been accepted (S83: NO), the processing unit 211 returns to step S81. If the approval operation has been accepted (S83: YES), the processing unit 211 sends a message to the dispatch application server device 11 notifying that approval for payment processing for the displayed payment fee has been accepted (step S84), and terminates the process.

[0146] <Information storage and processing> The dispatch application server device 11 according to this embodiment performs the process of storing various information related to taxi dispatch as history in the order management DB 112e and the dispatch history DB 12, for example, in steps S32 and S39 of the flowchart shown in Figures 21 and 22. The dispatch application server device 11 may store information at various other timings besides those mentioned above.

[0147] Furthermore, as shown in Figures 6 and 7, the dispatch application server device 11 stores information such as the date and time related to taxi dispatch (date and time the dispatch request was received, date and time the user boarded the taxi, or date and time the payment processing was completed), user ID, taxi ID, pre-planned route, pre-planned fare, actual route, and payment fare in the order management DB 112e and dispatch history DB 12. However, the information that the dispatch application server device 11 stores in the order management DB 112e and dispatch history DB 12 is not limited to the above, and may also store various other information such as whether or not the taxi driver canceled the reservation, whether or not the user canceled the reservation, or images of the interior and exterior taken by a camera installed in the taxi.

[0148] Figure 25 is a flowchart illustrating an example of the information storage process performed by the dispatch application server device 11 according to this embodiment. When the dispatch history processing unit 111f of the processing unit 111 of the dispatch application server device 11 according to this embodiment receives a taxi dispatch request from the user terminal device 31 (step S101), it stores the date and time the dispatch request was received, the user ID transmitted along with the dispatch request, the time of the taxi ride reservation, the pick-up location and the drop-off location, and the reservation number generated by the dispatch application server device 11 in the order management DB 112e (step S102).

[0149] When the pre-determined fare for the use of a taxi is determined (step S103), the dispatch history processing unit 111f stores the determined pre-determined route and pre-determined fare in the order management DB 112e (step S104). Also, when the dispatch history processing unit 111f receives a dispatch request from a taxi driver (step S105), it stores the reservation number, date and time, user ID, and taxi ID in the dispatch history DB 12 (step S106).

[0150] When the dispatch history processing unit 111f is notified by the taxi terminal device 21 that a 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). Furthermore, when the dispatch history processing unit 111f is notified by the taxi terminal device 21 that the user has arrived at their destination (step S109), it stores the actual route traveled, the fare paid, and the actual drop-off location in the dispatch history DB 12 (step S110).

[0151] When payment processing is completed (step S111), the dispatch history processing unit 111f stores in the dispatch history DB 12 whether the transaction was canceled, the payment method, whether a coupon was used, and whether a discount was applied (step S112), and then terminates the process.

[0152] Note that the timing of information storage by the dispatch application server device 11, and the types of information stored, are not limited to those shown in this figure. The dispatch application server device 11 may store appropriate information in the order management DB 112e or dispatch history DB 12 at appropriate times.

[0153] The dispatch application server device 11 according to this embodiment performs the process of displaying information stored in the order management DB 112e and the dispatch history DB 12 on the display unit 114. For example, an administrator managing this system can operate the operation unit 115 of the dispatch application server device 11 to select one of several histories stored in the dispatch history DB 12 and display the information of the selected history on the display unit 114. Alternatively, for example, an employee of a taxi company can access the dispatch application server device 11 using the information processing device 13 and have similar history information displayed on the display unit of the information processing device 13.

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

[0155] In the dispatch history screen of this example, the information processing device 13 displays the string "January 20, 2020, 11:12" as the title at the top as the date and time information of the history. Below this title, the information processing device 13 displays the pre-determined taxi route and the actual route the taxi traveled, overlaid on a map image. In this figure, the pick-up location where the user boarded the taxi is indicated by "S," and the drop-off location is indicated by "G." The pick-up location may be either the desired pick-up location entered by the user, or the actual location where the user boarded the taxi. If these are different, they may be displayed overlaid on the map image in a way that allows them to be distinguished. Similarly, the drop-off location may be either the destination location entered by the user, or the actual location where the user got out of the taxi. If these are different, they may be displayed overlaid on the map image in a way that allows them to be distinguished. In this figure, the pre-determined taxi route is shown as a solid line labeled "pre-determined route," and the actual route the taxi traveled that differs from the pre-determined route is shown as a dashed line labeled "actual route."

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

[0157] The information processing device 13 also displays a button labeled "Contact Customer" in the lower right corner of the dispatch history screen. This button is used to send a message via email or other means to the user who used the taxi. When the information processing device 13 receives a mouse click or touch operation on this button, it displays a message input screen (not shown in the diagram) and accepts the message. The information processing device 13 sends the entered message to the dispatch application server device 11. Based on the user ID stored in the dispatch history DB 12 and the email address stored in the user DB 112c, the dispatch application server device 11 sends the message received by the information processing device 13 to the user terminal device 31 of the user who used the taxi. The 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 dispatch history DB 12, etc.

[0158] The dispatch application server device 11 according to this embodiment stores various information related to taxi dispatch in the order management DB 112e and the dispatch history DB 12, and can display the stored information on the display unit 114. This allows, for example, information on locations where discrepancies frequently occur between the predetermined driving route and the actual driving route to be used as a reference for considering improvements to the method of determining the driving route in advance. Furthermore, it is expected that appropriate responses can be made to questions or complaints from users who have used a taxi, based on the stored history information. Note that the dispatch history screen shown in Figure 26 is just an example and is not limited to this; the information to be displayed and the manner in which the information is displayed can be changed as appropriate.

[0159] <Summary> The dispatch application server device 11 of the taxi information processing system according to this embodiment, configured as described above, determines a route based on the desired pick-up location and destination of a user who wishes to ride a taxi, and determines the advance fare for the taxi ride based on the determined route. The dispatch application server device 11 transmits the determined route and the determined advance fare information to the user terminal device 31 and the taxi terminal device 21, so that the route and advance fare are displayed on the user terminal device 31 and the taxi terminal device 21. The dispatch application server device 11 also stores information including the determined route and the determined advance fare in the order management DB 112e and the dispatch history DB 12.

[0160] This allows users to use taxis for a predetermined fare, rather than a fare that is added based on distance traveled and time. Users can check the taxi's route and fare in advance on their own user terminal device 31. Taxi drivers can check the route and fare in advance on the taxi terminal device 21 and accept the dispatch request. In addition, since the dispatch application server device 11 stores information about taxi dispatches in the order management DB 112e and the dispatch history DB 12, information such as the route the taxi traveled and the fare paid can be checked afterward.

[0161] Furthermore, the fare meter 22 of the taxi terminal system 20 installed in the taxi 2 according to this embodiment displays the predetermined fare while the user is riding in the taxi. This allows the user to easily confirm the fare to be paid while riding in the taxi.

[0162] Furthermore, the dispatch application server device 11 according to this embodiment stores the pre-determined travel route and the actual travel route taken by the taxi in the order management DB 112e and the dispatch history DB 12, associating them. This allows system administrators to later verify whether or not the taxi traveled the pre-determined route.

[0163] Furthermore, the dispatch application server device 11 in this embodiment obtains information about discount coupons owned by the user from the user DB 112c and determines the advance fare based on the obtained discount coupon information and the determined travel route. The taxi terminal device 21 of the taxi terminal system 20 obtains information about the presence or absence of discounts such as disability discounts by accepting discount operations at the operation unit 224 of the fare meter 22, and calculates the settlement fare with the discount applied to the advance fare. As a result, for discount coupons that do not require verification of certificates, etc., the advance fare with the discount applied in advance can be presented to the user, and for discounts such as disability discounts that require verification of certificates, etc., the taxi 2 can apply them.

[0164] Furthermore, in this embodiment, the taxi terminal system 20 displays the payment fare calculated by the taxi terminal device 21 with the discount applied on the passenger terminal device 23 located at the rear of the taxi. This allows users who board the taxi to easily confirm the payment fare with the discount applied.

[0165] Furthermore, the dispatch application server device 11 according to this embodiment stores the fare calculation standards for each taxi operating company in the fare calculation DB 112b of the storage unit 112. The dispatch application server device 11 determines which taxi operating company to dispatch based on the desired pick-up location entered by the user, and determines the advance fare based on the fare calculation standards 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, if a user requests a change to a pre-determined route after boarding a taxi, the system processes the payment of the pre-determined fare, and after the payment process is completed, the taxi proceeds to the changed destination. This ensures that the pre-determined fare is paid reliably.

[0167] Furthermore, in the taxi information processing system according to this embodiment, the taxi driver can cancel the dispatch request using the taxi terminal device 21 between the time the fare is determined in advance and the time the user boards the taxi. When the taxi terminal device 21 receives the cancellation request, the taxi terminal device 21 notifies the user terminal device 31 of the cancellation via the dispatch application server device 11. This ensures that the user terminal device 31 reliably informs the user that the dispatch request has been canceled.

[0168] (Variation 1) Figure 27 is a schematic diagram showing one example configuration of the fare calculation DB112b according to Modification 1. The fare calculation DB112b according to Modification 1 is the same as the fare calculation DB112b shown in Figure 3, but with the addition of information regarding long-distance discounts. The fare calculation DB112b according to Modification 1 stores information such as a "criterion" and a "coefficient" as information regarding long-distance discounts, associated with the taxi operating company. In this embodiment, the long-distance discount is applied, for example, when the taxi's mileage exceeds a predetermined distance or the fare exceeds a predetermined amount, by multiplying the fare added thereafter by a predetermined coefficient. The "criterion" in the fare calculation DB112b is a predetermined distance or predetermined amount used to determine whether or not to apply the long-distance discount. The "coefficient" is the value multiplied by the fare added after the criterion is exceeded.

[0169] The ride-hailing app server device 11 in the modified example 1 determines the route based on the desired pick-up location and destination location entered by the user, and calculates the advance fare based on the determined route. At this time, if the distance of the determined 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-hailing app server device 11 calculates an advance fare with a long-distance discount applied.

[0170] The information stored in the fee calculation DB112b is not limited to what is shown in Figures 3 and 27; various types of information used for fee calculation can also be stored.

[0171] (Modification 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's taxi they use.

[0172] Furthermore, some of the "initial fare," "initial distance," "additional unit," "additional fare," and "coefficient" included in the fare calculation DB112b shown in Figures 3 and 27 may be standardized across multiple operating companies. For example, the same value for the "coefficient" may be used by multiple taxi operating companies, while different values ​​may be used for other items such as the "initial fare" for each operating company.

[0173] <Embodiment 2> The taxi information processing system according to Embodiment 2 is a system that allows a user to select a taxi when multiple taxis are available for pre-paid service. The dispatch application server device 11 of the taxi information processing system according to Embodiment 2 receives input of the desired pick-up location and destination location from the user terminal device 31, and then determines the route from the desired pick-up location to the destination location. At this time, the dispatch application server device 11 calculates multiple candidate routes based on different conditions, such as distance priority and highway priority, and accepts the user's selection of a route via the user terminal device 31.

[0174] Figure 28 is a schematic diagram showing an example of a route selection screen displayed by the user terminal device 31 according to Embodiment 2. The route selection screen shown in Figure 28, similar to the dispatch request screen shown in Figure 14, presents the user with two route options, for example, a route calculated prioritizing general roads as "Route 1 (General Road Priority)" and a route calculated prioritizing expressways as "Route 2 (Expressway Priority)".

[0175] Furthermore, the dispatch application server device 11 determines which taxi companies (taxi operating companies) can dispatch to the user based on information such as the desired pick-up location and destination location entered by the user, the "region" information included in the fare calculation DB 112b, and information on available taxis located near the desired pick-up location, and determines the advance fare based on the fare calculation standards of the determined taxi company. In the taxi information processing system according to Embodiment 2, it is permissible that taxis from multiple taxi companies operate in one region, and that the advance fare calculation standards differ for each taxi company. Therefore, for each candidate route, the dispatch application server device 11 calculates the advance fare for all taxi companies available to the user, and transmits the minimum (lowest price) and maximum (highest price) information of the multiple calculated advance fares to the user terminal device 31, presenting the user with a range of advance fares. In the example shown in Figure 28, the advance fare for Route 1 is shown to be in the range of 11,200 yen to 11,800 yen, and the advance fare for Route 2 is shown to be in the range of 11,600 yen to 12,000 yen. In this example, if Route 2 is selected, the text "Additional toll road fees apply" is displayed along with the advance fare for Route 2, indicating that additional fees for using toll roads such as expressways will be required. Although not illustrated in this example, further information such as estimated travel time or arrival time at the destination may be displayed for each route. For Route 2, an estimated amount for toll road fees may be displayed, or the advance fare including toll road fees may be displayed.

[0176] The user can select one of several route options displayed on the user terminal device 31. In the lower area of ​​the illustrated route selection screen, information about the route options, Route 1 and Route 2, is displayed separately on the left and right, and below the information for each route, there is a button labeled "Select this route". The user can select the corresponding route by touching or tapping one of the "Select this route" buttons. The user terminal device 31 accepts the user's route selection by receiving an operation on one of the buttons and notifies the dispatch application server device 11 of the selection result.

[0177] The dispatch application server device 11, which receives the user's selection of a travel route via the user terminal device 31, transmits information regarding the selected travel route and the calculated advance fare to the user terminal device 31 for display. Figures 29 and 30 are schematic diagrams showing an example of the information display screen displayed by the user terminal device 31 according to Embodiment 2. Figure 29 shows the case where Route 1 is selected in 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 overlays the user's selected route onto this map image. In this figure, the user's desired pick-up location is indicated by "S", the destination is indicated by "G", and the route is shown 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 information such as the amount of the advance fare and information about any additional charges that may be added. In Figure 29, the information "11,200 yen to 11,800 yen, separate pick-up fee applies" is displayed. In Figure 30, the information "11,600 yen to 12,000 yen, separate toll road fee and pick-up fee apply" is displayed. ru.

[0179] Furthermore, a button labeled "Route Selection" is provided in the lower right corner of the map image. When the "Route Selection" button is clicked, the user terminal device 31 displays the route selection screen shown in Figure 28 and accepts the user's selection of a route. This allows the user to re-select their route.

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

[0181] Furthermore, if a user wishes to use a specific taxi company, they can pre-select and set the taxi company for which they will calculate the advance fare and request a dispatch. When the user terminal device 31 receives an operation on a button labeled "Specify Taxi Company," it displays a taxi company selection screen (not shown in the diagram) and accepts the selection of a taxi company. The taxi company selection screen can, for example, display a list of taxi company names, and the user terminal device 31 accepts the selection of one taxi company from the list and notifies the dispatch application server device 11 of the selected taxi company. In addition, each taxi company displayed in the list on the taxi company selection screen also displays information indicating whether or not taxis can be used with an advance fare, such as a label or icon with the string "Advance Fare Supported." This allows the user to easily determine which taxi companies support the advance fare system. When the dispatch application server device 11 accepts the user's selection of a taxi company, it limits the calculation of the advance fare and dispatch to the selected taxi company. Furthermore, the dispatch app server device 11 may set the default setting for calculating advance fares and dispatching taxis for this user to the selected taxi company.

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

[0183] The user terminal device 31 displays a button labeled "Select Taxi" below this information. When the user terminal device 31 receives an operation on the "Select Taxi" button, it notifies the dispatch application server device 11 of this. In response, the dispatch application server device 11 sends information about available taxis to the user terminal device 31 and displays a taxi selection screen on the user terminal device 31 that allows the user to select a taxi.

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

[0185] In this example, the top area of ​​the taxi selection screen displays messages such as "Which taxi would you like to call?", "Fares may vary due to additional charges and discounts," and "Coupons will be applied upon alighting." These messages are merely examples and are not exhaustive; any message may be displayed on the taxi selection screen. Furthermore, coupon application may occur at a different time, such as upon boarding.

[0186] Each rectangular area on the taxi selection screen contains information such as the advance fare, estimated time until boarding, icons for one or more taxi companies, and radio buttons to accept 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, or four or more.

[0187] In the illustrated example, after the advance fare for each option, information regarding the estimated time until boarding the taxi is displayed, for example, "Boarding in approximately 2-5 minutes," "Boarding in approximately 2-7 minutes," and "Boarding in approximately 1 minute." For example, the dispatch application server device 11 obtains information about taxis located near the user's desired boarding location from the information processing device 13 of each taxi company, and calculates the estimated time until boarding the taxi based on the distance between the location of each taxi and the user's desired boarding location. The dispatch application server device 11 transmits the calculated estimated time information for each taxi to the user terminal device 31, and the user terminal device 31 can receive this information and display the estimated time until boarding the taxi 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 set for each taxi company, and there may be multiple taxis with the same calculated advance fare. In this case, multiple taxi companies with the same advance fare are grouped together and displayed as a single option on the taxi selection screen. In the illustrated example, one or more icons (shown as roughly square shapes with rounded corners) are displayed below the advance fare for each option. Each icon represents one taxi company. In this example, the first option with an advance fare of 11,200 yen has two taxi companies grouped together, the second option with an advance fare of 11,500 yen has three taxi companies grouped together, and the third option with an advance fare of 11,800 yen has one taxi company grouped together. In this figure, each icon is represented as a plain shape, but in reality, each icon displays information such as the taxi company's logo or name.

[0189] Although not shown in the diagram, when a user terminal device 31 receives a touch operation or similar response for any of the options, it displays detailed information regarding the calculation of the corresponding advance fare. This detailed information may include, for example, whether there are any applicable discounts to the advance fare, their type, and the amount. It may also include information such as pickup charges, toll road charges, and late-night / early-morning surcharges that may be added to the advance fare. The displayed detailed information may also include, for example, information such as the initial fare and late-night surcharge coefficients used when calculating the advance fare.

[0190] The radio buttons provided for each option on the taxi selection screen are for accepting the operation of selecting one of multiple options. When a touch operation or other action is received for any one of the radio buttons, the user terminal device 31 recognizes that the corresponding option has been selected and highlights the selected option to indicate that it is selected. In the illustrated example, the option with a prepaid fare of 11,200 yen is selected, which is indicated by the highlighting of the rectangular area with a thick line.

[0191] The "Call a Taxi" button located at the bottom of the taxi selection screen is used to notify the dispatch application server device 11 of the taxi selection result. This button accepts operation only when any option on the taxi selection screen is selected, and does not accept operation when all options are unselected. When an operation is received on the "Call a Taxi" button, the user terminal device 31 sends information to the dispatch application server device 11 indicating which option was selected.

[0192] In this embodiment, the dispatch application server device 11 determines which taxi company's taxi to dispatch from among the grouped taxi companies in the selection. Therefore, in the taxi information processing system according to Embodiment 2, the user indirectly selects a taxi by selecting the advance fare, and the final taxi selection is left to the dispatch application server device 11. If the advance fares are the same for taxis from multiple taxi companies, the dispatch application server device 11 can, for example, attempt to dispatch a taxi to the user by selecting taxis in order of proximity to the user's desired pick-up location. The selection of a taxi company by the dispatch application server device 11 may be made based on any criteria. Alternatively, the user may further accept an operation from the user at the user terminal device 31 to select one taxi company from among multiple taxi companies.

[0193] Furthermore, the processing of taxi dispatch and other related operations by the dispatch application server device 11 after the user terminal device 31 has sent the result of taxi selection to the dispatch application server device 11 is the same as the processing described in the previous embodiment, so a detailed explanation of the processing will be omitted in Embodiment 2.

[0194] Figure 32 is a flowchart showing the processing steps performed by the dispatch application server device 11 according to Embodiment 2. The processing unit 111 of the dispatch application server device 11 according to Embodiment 2 receives input from the user regarding the desired pick-up location and destination location via the user terminal device 31 (step S201). Based on the input of the desired pick-up location and destination location, and map information, the processing unit 111 calculates candidate taxi routes from the desired pick-up location to the destination location (step S202). The processing unit 111 also calculates advance fares for each taxi company that can dispatch taxis to this area, based on the fare calculation DB 112b (step S203).

[0195] The processing unit 111 transmits information regarding the calculated travel route and advance toll to the user terminal device 31, causing the user terminal device 31 to display a travel route selection screen (see Figure 28) (step S204). The processing unit 111 accepts the user's selection of a travel route via the user terminal device 31 displaying the travel route selection screen (step S205). The processing unit 111 displays an information display screen (see Figures 29 and 30) on the user terminal device 31, showing information regarding the selected travel route and advance toll (step S206).

[0196] The processing unit 111 determines whether or not a user has requested a route change based on whether or not the "Route Selection" button on the information display screen has been operated (step S207). If a route change request has been made (S207: YES), the processing unit 111 returns to step S204 and displays the route selection screen on the user terminal device 31 and performs the above-described process.

[0197] If no request for a route change has been made (S207: NO), the processing unit 111 displays a taxi selection screen (see Figure 31) on the user terminal device 31 in response to the operation of the "Select Taxi" button (step S208). The processing unit 111 receives a selection of one advance fare from the user via the user terminal device 31 displaying the taxi selection screen, from among the one or more advance fares displayed as options on the taxi selection screen (step S209). The processing unit 111 determines a taxi company according to the advance fare selected by the user, requests a taxi dispatch from the information processing device 13 of this taxi company (step S210), and terminates the process.

[0198] Subsequently, the user boards the taxi at the desired pick-up location and, upon alighting at the destination, completes the payment process based on the predetermined fare. However, in the taxi information processing system according to this embodiment, from the moment the user boards the taxi at the desired pick-up location until the taxi arrives at the destination, the pre-paid taxi service can be canceled and the service can be changed to one based on the fare calculated by the taxi's fare meter.

[0199] This change may occur, for example, if the taxi driver changes the destination due to their own circumstances and the user does not agree to the taxi operating at the predetermined fare. It may also occur, for example, if the user arrives late at the desired pick-up location and the taxi driver charges an additional fee for the waiting time. The change from a predetermined fare to a fare meter may occur for various other reasons, including when the passenger (user) requests the change, or when the taxi driver requests the change.

[0200] If the fare is changed from a pre-determined fare to a metered fare after the taxi has started traveling from the desired pick-up point to the destination, the user will pay the fare for the distance traveled up to that point. At this time, the user may pay, for example, the amount to be paid by the user may be calculated based on the distance traveled up to that point and the pre-determined fare, or the user may pay a flat cancellation fee, or any other amount. Furthermore, the amount to be paid by the user when the fare is changed from a pre-determined fare to a metered fare may be calculated using different criteria depending on whether the change was made at the user's request or by the taxi driver.

[0201] The taxi information processing system according to Embodiment 2, configured as described above, stores the fare calculation criteria 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 fares, and confirms the selected advance fare as the advance fare for the taxi. This allows the user to compare the different advance fares for each taxi operating company and choose the advance fare that suits them best to use the taxi.

[0202] Furthermore, the taxi information processing system according to Embodiment 2 displays a selection of advance fares on the taxi selection screen, grouping together operating companies with the same calculated advance fare, and accepts the selection of an advance fare. The displayed selection is also accompanied by information such as an icon that identifies one or more operating companies included in this group. This simplifies the selection when there are many operating companies, and allows the user to easily recognize which operating company the selected advance fare is from.

[0203] Furthermore, the taxi information processing system according to Embodiment 2 displays multiple route options on the route selection screen, accepts the selection of a route based on the selection of an option, and attaches information on the minimum and maximum pre-paid fares to the displayed options. This allows the user to check the approximate fare and select a route.

[0204] In Embodiment 2, the screen configurations shown in Figures 28 to 30, etc., are merely examples and are not limited to these; modifications may be made as appropriate.

[0205] Furthermore, since the other components of the taxi information processing system according to Embodiment 2 are the same as those of the taxi information processing system according to Embodiment 1, the same reference numerals are used for the same parts, and detailed explanations are omitted.

[0206] The embodiments disclosed herein should be considered in all respects to be illustrative and not restrictive. The scope of the invention is indicated by the claims, not in the sense described above, and all modifications within the sense and scope equivalent to the claims are intended. [Explanation of Symbols]

[0207] 2 Taxi 3 users 11. Ride-hailing application server device 12. Dispatch History Database 13 Information Processing Devices 14 Payment Server Device 20 Taxi terminal system 21 Taxi terminal device 22 Fare meter 23 Passenger terminal equipment 31 User terminal device 98,99 recording media 111 Processing Unit 111a Route Processing Unit 111b Order Processing 111c Advance Payment Processing 111d Dispatch Processing Unit 111e Payment Processing Unit 111f Dispatch History Processing Unit 111g Display processing unit 112 Storage section 112a Server Program 112b Price Calculation Database 112c User DB 112d Taxi DB 112e Order Management DB 113 Communications Department 114 Display section 115 Operation section 211 Processing Unit 211a Display Processing Unit 211b Acceptance Department 211c Cancellation Department 212 Storage section 212a Program 212b Taxi ID 213 Communications Department 214 Display section 215 Operation section 216 GPS receiver 221 Processing Unit 222 Communications Department 223 Display section 224 Operation section 231 Processing Unit 232 Communications Department 233 Display section 234 Operation section 311 Processing Unit 311a Display Processing Unit 311b Vehicle 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 that determines a pre-route for a taxi and a pre-fare for the taxi ride corresponding to the pre-route based on the desired pick-up location and destination location received from a user terminal device used by the user, displays the determined pre-route and pre-fare on the user terminal device, receives a dispatch request from the user terminal device based on the pre-route and pre-fare displayed on the user terminal device, and processes a dispatch request based on the received dispatch request, The user terminal device stores in a database the pre-trip route used when it made the dispatch request and the actual route taken by the taxi in association with each other. The pre-trip route and the actual trip route stored in the database are displayed on a predetermined display unit. Taxi information processing method.

2. A taxi information processing method that determines a pre-route for a taxi and a pre-fare for the taxi ride corresponding to the pre-route based on the desired pick-up location and destination location received from a user terminal device used by the user, displays the determined pre-route and pre-fare on the user terminal device, receives a dispatch request from the user terminal device based on the pre-route and pre-fare displayed on the user terminal device, and processes a dispatch request based on the received dispatch request, When a user who has boarded the taxi performs payment processing based on the pre-paid fare, the passenger terminal device installed in the taxi displays the pre-paid route and the actual route traveled by the taxi. Taxi information processing method.

3. A user terminal device having a reception section that accepts input information regarding the desired pick-up location and destination of a user who wishes to take a taxi, A server device that determines a pre-route for a taxi and a pre-fare for the taxi ride corresponding to the pre-route based on the desired pick-up location and destination location received from the user terminal device used by the user, displays the determined pre-route and pre-fare on the user terminal device, receives a dispatch request from the user terminal device based on the pre-route and pre-fare displayed on the user terminal device, and processes the dispatch of a taxi based on the received dispatch request. Equipped with, The server device is The user terminal device stores in a database the pre-trip route used when it made the dispatch request and the actual route taken by the taxi in association with each other. The pre-trip route and the actual trip route stored in the database are displayed on a predetermined display unit. Taxi information processing system.

4. A user terminal device having a reception section that accepts input information regarding the desired pick-up location and destination of a user who wishes to take a taxi, A server device that determines a pre-route for a taxi and a pre-fare for the taxi ride corresponding to the pre-route based on the desired pick-up location and destination location received from the user terminal device used by the user, displays the determined pre-route and pre-fare on the user terminal device, receives a dispatch request from the user terminal device based on the pre-route and pre-fare displayed on the user terminal device, and processes the dispatch of a taxi based on the received dispatch request, A passenger terminal device installed in the aforementioned taxi and Equipped with, The server device is When a user who has boarded the taxi performs payment processing based on the pre-paid fare, the passenger terminal device displays the pre-paid route and the actual route traveled by the taxi. Taxi information processing system.

5. The system includes a processing unit that determines the taxi's pre-route and the pre-fare for the taxi ride corresponding to the pre-route based on the desired pick-up location and destination location received from the user's terminal device, displays the determined pre-route and pre-fare on the user's terminal device, receives a dispatch request from the user's terminal device based on the pre-route and pre-fare displayed on the user's terminal device, and performs dispatch processing based on the received dispatch request. The aforementioned processing unit, The user terminal device stores in a database the pre-trip route used when it made the dispatch request and the actual route taken by the taxi in association with each other. The pre-trip route and the actual trip route stored in the database are displayed on a predetermined display unit. Server device.

6. The system includes a processing unit that determines the taxi's pre-route and the pre-fare for the taxi ride corresponding to the pre-route based on the desired pick-up location and destination location received from the user's terminal device, displays the determined pre-route and pre-fare on the user's terminal device, receives a dispatch request from the user's terminal device based on the pre-route and pre-fare displayed on the user's terminal device, and performs dispatch processing based on the received dispatch request. The aforementioned processing unit, When a user who has boarded the taxi performs payment processing based on the pre-paid fare, the passenger terminal device installed in the taxi displays the pre-paid route and the actual route traveled by the taxi. Server device.

7. Based on the desired pick-up location and destination received from the user's terminal device, the pre-determined taxi route and the pre-determined fare for the taxi ride corresponding to the said pre-determined route are determined. The determined pre-travel route and pre-charge are displayed on the user terminal device. The user terminal device receives a dispatch request based on the pre-arranged route and pre-arranged fare displayed on the user terminal device. Based on the dispatch request received, the dispatch process will be carried out. The user terminal device stores in a database the pre-trip route used when it made the dispatch request and the actual route taken by the taxi in association with each other. The pre-trip route and the actual trip route stored in the database are displayed on a predetermined display unit. A computer program that instructs a computer to perform a process.

8. Based on the desired pick-up location and destination received from the user's terminal device, the pre-determined taxi route and the pre-determined fare for the taxi ride corresponding to the said pre-determined route are determined. The determined pre-travel route and pre-charge are displayed on the user terminal device. The user terminal device receives a dispatch request based on the pre-arranged route and pre-arranged fare displayed on the user terminal device. Based on the dispatch request received, the dispatch process will be carried out. When a user who has boarded the taxi processes a payment based on the pre-paid fare, the passenger terminal device installed in the taxi displays the pre-paid route and the actual route traveled by the taxi. A computer program that instructs a computer to perform a process.

Images