Dispatch system, dispatch management method, and program

Abstract

To perform more efficient vehicle allocation.SOLUTION: A vehicle allocation system consists of a vehicle allocation management device, which manages vehicle allocations of a plurality of mobile units, and a terminal device which requests a vehicle allocation to the vehicle allocation management device. The vehicle allocation management device acquires information relating to a current place or a departure place from the terminal device and transmits to the terminal device positional information and business states of one or more mobile units on the basis of the acquired information relating to the current place or the departure place. Based on the positional information and the business states of one or more mobile units transmitted from the vehicle allocation management device, the terminal device causes a display section to display a mobile unit which is positioned within a predetermined range with respect to the current place or the departure place and of which the business state is available, and a mobile unit which is positioned within a predetermined range with respect to the current place or the departure place and of which the business state is in-service or reserved for pick-up. The present technique may be applicable to e.g., a taxi allocation system, etc., which controls the allocation of taxis.SELECTED DRAWING: Figure 1

Description

Technical Field

[0007] ,

[0001] The present technology relates to a vehicle dispatching system, a vehicle dispatching management method, and a program, and particularly to a vehicle dispatching system, a vehicle dispatching management method, and a program that enable more efficient vehicle dispatching.

Background Art

[0002] There is known a vehicle dispatching system that refers to the operation status of taxis, determines a suitable taxi from a plurality of taxis, and dispatches the taxi (see, for example, Patent Document 1).

[0003] Conventionally, a vehicle dispatching system searches for a taxi close to the position of a user who wishes to board from taxis in an empty state and dispatches it.

Prior Art Documents

Patent Documents

[0004]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0005] However, when the demand for taxis is high due to a specific time zone, location, weather, etc., it may be impossible to find an empty taxi, and users may feel inconvenienced.

[0006] The present technology has been made in view of such a situation and enables more efficient vehicle dispatching.

Means for Solving the Problems

[0007] The vehicle dispatching system according to one aspect of the present technology comprises a vehicle dispatching management device that manages the dispatching of a plurality of mobile devices, and a terminal device that requests vehicle dispatching to the vehicle dispatching management device, wherein the vehicle dispatching management device Information regarding the current location or departure point is obtained from the terminal device. Based on the acquired information regarding the current location or departure point, the location information and operating status of one or more mobile devices are transmitted to the terminal device. The aforementioned terminal device is Based on the location information and operating status of the one or more mobile devices transmitted from the dispatch management device, the display unit displays mobile devices that are located within a predetermined range from the current location or departure point and whose operating status is vacant, and mobile devices that are located within a predetermined range from the current location or departure point and whose operating status is occupied or picking up passengers.

[0008] One aspect of this technology is the vehicle dispatch management method, A dispatch system comprising a dispatch management device that manages the dispatch of multiple mobile devices, and a terminal device that requests dispatch from the dispatch management device, The aforementioned dispatch management device Information regarding the current location or departure point is obtained from the terminal device. Based on the acquired information regarding the current location or departure point, the location information and operating status of one or more mobile devices are transmitted to the terminal device. The aforementioned terminal device Based on the location information and operating status of the one or more mobile devices transmitted from the dispatch management device, the display unit displays mobile devices that are located within a predetermined range from the current location or departure point and whose operating status is vacant, and mobile devices that are located within a predetermined range from the current location or departure point and whose operating status is occupied or picking up passengers.

[0009] One aspect of this technology is the program, The dispatch management system's computer, Based on the current location or departure point information obtained from the terminal device, the location information and operating status of one or more mobile devices are transmitted to the terminal device. The terminal device's display unit will show the following: a mobile device located within a predetermined range from the current location or departure point whose operating status is "vacant," and a mobile device located within a predetermined range from the current location or departure point whose operating status is "occupied" or "waiting for a ride." This is for executing a process.

[0010] In one aspect of this technology, in the dispatch management device, information regarding the current location or departure location is acquired from the terminal device, and based on the acquired information regarding the current location or departure location, the location information and operating status of one or more mobile devices are transmitted to the terminal device, and in the terminal device, based on the location information and operating status of the one or more mobile devices transmitted from the dispatch management device, the operating status of mobile devices that are located within a predetermined range from the current location or departure location and are vacant, and the operating status of mobile devices that are located within a predetermined range from the current location or departure location and are occupied or waiting for a vehicle are displayed on the display unit.

[0011] Furthermore, programs to be executed by a computer can be provided by transmitting them via a transmission medium or by recording them on a recording medium. [Brief explanation of the drawing]

[0012] [Figure 1] This block diagram shows an example configuration of a taxi dispatch system, which is an embodiment of the application of this technology. [Figure 2] This is a flowchart illustrating the overall processing flow of the taxi dispatch system. [Figure 3] This flowchart explains the dispatch request process, focusing on the user application. [Figure 4] This diagram shows an example of a user application screen. [Figure 5] This diagram shows other examples of user application screens. [Figure 6] This figure shows an example screen for suggesting a change of boarding location to a user. [Figure 7] This figure shows an example screen for suggesting a change of disembarkation location to a user. [Figure 8] This flowchart explains the dispatch request response process, focusing on the driver app. [Figure 9] This diagram shows an example of a ride request screen in a driver app. [Figure 10] It is a flowchart for explaining the vehicle allocation process focusing on the vehicle allocation integrated management device. [Figure 11] It is a block diagram showing a configuration example of an embodiment of a computer to which this technology is applied.

Embodiments for Carrying Out the Invention

[0013] Hereinafter, embodiments for carrying out this technology (hereinafter referred to as embodiments) will be described with reference to the accompanying drawings. In this specification and the drawings, components having substantially the same functional configuration are denoted by the same reference numerals, and redundant description is omitted. The description will be made in the following order. 1. Configuration example of a taxi allocation system 2. Flow of the entire taxi allocation system 3. Vehicle allocation request processing of the user app 4. Vehicle allocation request response processing of the driver app 5. Vehicle allocation processing of the vehicle allocation integrated management device 6. Computer configuration example

[0014] <1. Configuration example of a taxi allocation system> FIG. 1 is a block diagram showing a configuration example of a taxi allocation system which is an embodiment to which this technology is applied.

[0015] The taxi allocation system 1 in FIG. 1 is a system that allocates a taxi as a moving device to a user based on a request from the user who is a taxi user, and includes vehicle allocation management devices 11A to 11C of taxi companies A, B, and C respectively, and a vehicle allocation integrated management device 12 which is a vehicle allocation management device for integrally managing them.

[0016] The vehicle allocation management device 11A of company A is connected to one or more taxis 21A belonging to company A via a predetermined network, and is also connected to the vehicle allocation integrated management device 12 via a predetermined network.

[0017] Similarly, Company B's dispatch management device 11B is connected to one or more taxis 21B belonging to Company B via a predetermined network, and is also connected to the integrated dispatch management device 12 via a predetermined network.

[0018] Similarly, Company C's dispatch management device 11C is connected to one or more taxis 21C belonging to Company C via a predetermined network, and is also connected to the integrated dispatch management device 12 via a predetermined network.

[0019] Furthermore, individual taxis 21D that do not belong to a designated company are connected directly to the integrated dispatch management device 12 via a designated network, without going through the dispatch management device 11. When no particular distinction is made between taxis 21A to 21C of companies A, B, and C, and individual taxis 21D, they are simply referred to as taxis 21.

[0020] Here, the specified network can be composed of any communication network or communication path conforming to any communication standard, such as the Internet, public telephone network, wide-area communication networks for mobile communication such as so-called 4G and 5G networks, WAN (Wide Area Network), LAN (Local Area Network), wireless communication network conforming to Bluetooth® standard, communication path for short-range wireless communication such as NFC (Near Field Communication), communication path for infrared communication, and wired communication network conforming to standards such as HDMI® (High-Definition Multimedia Interface) and USB (Universal Serial Bus).

[0021] Taxi 21A of Company A has an in-vehicle unit 31 and a communication unit 32. Additionally, Taxi 21A of Company A is equipped with a terminal device 33.

[0022] The in-vehicle unit 31 includes a vehicle movement data generation unit 34 that acquires necessary data from a fare meter, GPS (Global Positioning System) receiver, gyro sensor, speed meter, etc. (all not shown) and generates vehicle movement data representing the movement log of the taxi 21A (vehicle).

[0023] The vehicle movement data generation unit 34 acquires data such as the status ("occupied," "vacant," or "on call") and the fare from, for example, the fare meter. The status represents the operating status of the taxi 21. The vehicle movement data generation unit 34 also acquires information such as the current location, speed, and direction of movement of the taxi 21A from, for example, a GPS receiver, gyro sensor, speedometer, etc.

[0024] The vehicle movement data generation unit 34 periodically or irregularly generates vehicle movement data, including information such as a company ID that identifies the company to which taxi 21A belongs, a radio ID that identifies the vehicle of taxi 21A, a crew ID that identifies the driver operating taxi 21A, a status time that indicates the time the status was generated, the latitude and longitude of taxi 21A's location information, the taxi 21A's speed and direction of travel, the status of "occupied," "vacant," or "on call," and, if the status is "occupied" or "on call," the pick-up location and destination of the taxi 21, and transmits this data to Company A's dispatch management device 11A via the communication unit 32.

[0025] The communication unit 32 transmits the vehicle movement data generated by the vehicle movement data generation unit 34 of the in-vehicle unit 31 to the dispatch management device 11A of Company A. The communication unit 32 is composed of a network interface that performs network communication via a predetermined network.

[0026] The terminal device 33 is composed of an information processing device such as a smartphone or tablet terminal. The terminal device 33 has a driver application program, the driver app 35, installed on it. The driver app 35 acquires data related to dispatch requests from the dispatch management device 12 and displays it on the display, and based on the driver's operation, transmits response data to the dispatch management device 12 to the dispatch management device 12. The driver app 35 communicates directly with the dispatch management device 12 via a network such as a wide-area communication network for mobile communication. Alternatively, the driver app 35 may communicate with the dispatch management device 12 via the communication unit 32 and A company's dispatch management device 11A.

[0027] Taxi 21B from Company B and Taxi 21C from Company C are basically the same as Taxi 21A from Company A, only the company is different, so I will omit their explanation.

[0028] The dispatch management device 11A of Company A collects vehicle movement data for one or more taxis 21A of Company A and transmits it to the integrated dispatch management device 12. It also relays dispatch request data transmitted from the integrated dispatch management device 12 to the taxis 21A of Company A and transmits it to the designated taxis 21A of Company A.

[0029] Company A's dispatch management system 11A includes a vehicle movement data management unit 41, an order information management unit 42, and a communication unit 43. Company A's dispatch management system 11A is composed of, for example, a server device (information processing device) with network connectivity.

[0030] The vehicle movement data management unit 41 manages the vehicle movement data supplied from each of Company A's taxis 21A. Specifically, the vehicle movement data management unit 41 stores the vehicle movement data supplied from each of Company A's taxis 21A in its internal memory and displays the vehicle movement data for each taxi 21A on a display (not shown). The vehicle movement data management unit 41 also transmits the vehicle movement data supplied from each taxi 21A to the integrated dispatch management device 12.

[0031] When a dispatch request is made to Company A by phone or other means, the operator managing the operation of Company A's taxis 21A can check the current location and status (such as "occupied" or "vacant") of each of Company A's taxis 21A stored in the vehicle movement data management unit 41, and then search for or assign a taxi 21A that can respond to the dispatch request.

[0032] The Order Information Management Unit 42 manages information on advance dispatch requests (dispatch reservations) from customers, etc. For example, if an operator of taxi 21A of Company A receives a dispatch reservation call from a customer, the operator inputs the dispatch reservation information, such as the pickup location, pickup time, customer name, destination, etc., into the Order Information Management Unit 42 from the operating terminal. The Order Information Management Unit 42 stores the dispatch reservation information and displays the dispatch request a predetermined time before the reservation time. After the operator confirms the dispatch request display, they make a dispatch request to the designated taxi 21A based on the vehicle movement data stored in the Vehicle Movement Data Management Unit 41. Alternatively, the Order Information Management Unit 42 may search for the most suitable taxi 21A from the vehicle movement data in the Vehicle Movement Data Management Unit 41 a predetermined time before the reservation time and make a dispatch request.

[0033] The communication unit 43 communicates with the dispatch management system 12 and the taxis 21A of Company A, respectively. For example, the communication unit 43 transmits dispatch requests from the dispatch management system 12 to the designated taxis 21A, and transmits vehicle movement data periodically acquired from each taxi 21A to the dispatch management system 12.

[0034] The dispatch management devices 11B and 11C of taxi companies B and C are basically the same as the dispatch management device 11A of company A, differing only in the company, so their explanation will be omitted. In cases where there is no particular distinction between the dispatch management devices 11A to 11C of companies A, B, and C, they may simply be referred to as the dispatch management device 11.

[0035] The integrated dispatch management device 12 transmits and receives data such as vehicle movement data and dispatch requests with the dispatch management devices 11 of companies A, B, and C. The integrated dispatch management device 12 also communicates via a predetermined network with the application program 61 (hereinafter referred to as the user app) installed on the terminal device 13 of the taxi user (hereinafter referred to as the user terminal) for making dispatch requests. The integrated dispatch management device 12 is, for example, composed of a server device with network connectivity.

[0036] The dispatch management device 12 is a dispatch management device that manages the dispatch of all taxis 21. The dispatch management device 12 includes a vehicle movement data management unit 51, a customer data management unit 52, an order information management unit 53, a dispatch management unit 54, a taxi company communication unit 55, and an application communication unit 56.

[0037] The Vehicle Movement Data Management Unit 51 manages vehicle movement data supplied from the dispatch management devices 11 of each taxi company and from each individual taxi 21D. Specifically, the Vehicle Movement Data Management Unit 51 stores the vehicle movement data supplied from the dispatch management devices 11 of each taxi company and from each individual taxi 21D in its internal memory and displays the vehicle movement data on a display (not shown). The vehicle movement data includes information such as the taxi 21's company ID, the taxi 21's radio ID, the driver ID, status time, the taxi 21's location information, the taxi 21's speed and direction of travel, status, and, if the status is "occupied" or "on call," the taxi 21's pick-up location and destination. In addition, each time the "occupied" status ends, the Vehicle Movement Data Management Unit 51 records the taxi 21's company ID, the taxi 21's radio ID, the driver ID, the pick-up location and destination, and the fare in its internal memory as past occupancy data.

[0038] The customer data management unit 52 generates customer data based on data entered by operators or transmitted from the user application 61 and stores it in its internal memory. For example, the customer data management unit 52 stores information such as the customer's name, preferred taxi company or taxi company that the customer wants to be dispatched to preferentially, frequently used taxi stands, and average waiting time for a taxi, along with a customer ID, which is identification information that identifies the customer. The customer data may be data entered (specified) by the user in the user application 61, or it may be data generated by the customer data management unit 52 based on the user's ride history, etc.

[0039] The order information management unit 53 manages information on pre-arranged dispatch requests (dispatch reservations) from customers, etc. While the order information management unit 42 of each dispatch management device 11 manages information on dispatch requests (dispatch reservations) received by each taxi company, the order information management unit 53 manages information on dispatch requests (dispatch reservations) received by the representative reservation center that oversees each taxi company or by the user application 61. When the scheduled time for a dispatch reservation approaches, the order information management unit 53 sends a dispatch request to the dispatch management unit 54.

[0040] The dispatch management unit 54 controls dispatch based on dispatch requests or dispatch reservations. For example, when the dispatch management unit 54 receives a dispatch request from a user application 61, it extracts a taxi 21 that meets the dispatch request conditions based on the vehicle movement data stored in the vehicle movement data management unit 51 and sends the dispatch request. Also, when the dispatch management unit 54 receives a dispatch request from an order information management unit 53, it extracts a taxi 21 that meets the dispatch request conditions based on the vehicle movement data stored in the vehicle movement data management unit 51 and sends the dispatch request to the driver application 35.

[0041] The taxi company communication unit 55 communicates with each taxi company's dispatch management device 11 as prescribed. For example, the taxi company communication unit 55 receives vehicle movement data periodically transmitted from each taxi 21 and supplies it to the vehicle movement data management unit 51, and transmits dispatch requests from the dispatch management unit 54 to the designated taxi 21 via the dispatch management device 11.

[0042] The taxi company communication unit 55 may also communicate directly with each taxi company's taxis 21 without going through each taxi company's dispatch management device 11, thereby receiving vehicle movement data and transmitting dispatch requests from the dispatch management unit 54 to designated taxis 21.

[0043] The application communication unit 56 communicates with the user application 61 as prescribed. For example, the application communication unit 56 receives a dispatch request from the user application 61 and supplies it to the dispatch management unit 54, and when the dispatch of a designated taxi 21 is confirmed, it sends a dispatch confirmation notification to the user application 61.

[0044] Although Figure 1 only shows a user terminal 13 and user application 61 corresponding to one user for ease of understanding, the vehicle dispatch management device 12 can communicate with user applications 61 of multiple user terminals 13 as needed.

[0045] The user terminal 13 is composed of an information processing device such as a smartphone or tablet, and communicates with the dispatch management device 12. Based on the user's operation, the user application 61 requests the dispatch of a taxi 21 from the dispatch management device 12 and displays a confirmation of the dispatch in response to the request. The user application 61 can also obtain vehicle movement data near the user's current location from the dispatch management device 12 and display the current operating status of the taxis 21 on the display.

[0046] In the taxi dispatch system 1 configured as described above, when a user operates the user application 61 to request the dispatch of a taxi 21, the dispatch integrated management device 12 refers to the vehicle movement data in the vehicle movement data management unit 51 to search for the most suitable taxi 21 and sends the dispatch request to the found taxi 21.

[0047] Here, when the dispatch management device 12 searches for the optimal taxi 21, it can search for taxis 21 that are not only "available" at the time of the search, but also include taxis 21 that are "occupied" or "on call".

[0048] This means that users will have more taxis available to accept their dispatch requests, allowing them to call a taxi with less waiting time. Furthermore, it will reduce the likelihood of being unable to find an available taxi during times of high demand, such as specific times of day, locations, or weather conditions.

[0049] Furthermore, for Taxi 21 drivers, it allows them to shorten the time between picking up passengers and picking up the next passenger, and also reduces the time and travel time between passengers.

[0050] In other words, the taxi dispatch system 1 enables efficient dispatching.

[0051] <2. Overall flow of the taxi dispatch system> First, we will explain the overall processing flow of the taxi dispatch system 1 by referring to the flowchart in Figure 2, and then we will explain the details of the processing of the integrated dispatch management device 12, the taxi 21, and the user terminal 13.

[0052] Figure 2 is a flowchart of the dispatch control process by the taxi dispatch system 1.

[0053] This process assumes a scenario where user A uses user application 61 to board taxi 21A of company A, and while user A is in taxi 21A, user B uses user application 61 to request the dispatch of taxi 21, in which case taxi 21A, which user A is currently riding in, is assigned to user B.

[0054] In addition to the process shown in Figure 2, it is assumed that the dispatch management device 12 is constantly performing a process to periodically or irregularly acquire vehicle movement data from each taxi 21 and update the vehicle movement data in the vehicle movement data management unit 51.

[0055] First, in step S1, user A enters the pick-up location "X" and destination "Y" into the user app 61 and performs the operation to request a ride.

[0056] In step S2, user A's user application 61 sends a dispatch request to the dispatch management device 12 along with information on the pick-up location "X" and destination "Y".

[0057] In step S11, the dispatch management unit 54 of the dispatch integrated management device 12 receives a dispatch request from user A's user application 61 and extracts an available taxi 21 by referring to the current vehicle movement data managed by the vehicle movement data management unit 51. Here, let's assume that taxi 21A of Company A, which is the closest taxi 21 to the pick-up location "X" and has a "vacant" status, is found.

[0058] In step S12, the dispatch management unit 54 sends a dispatch request to the searched taxi 21A of Company A.

[0059] In step S21, the driver app 35 of taxi 21A of Company A acquires data related to the dispatch request from the dispatch management device 12 (for example, the pick-up location "X" and the destination "Y") and displays it on the display. Then, when the driver performs an operation to accept the dispatch request, in step S22, the driver app 35 sends a request acceptance notification to the dispatch management device 12 indicating that the driver has accepted the dispatch request.

[0060] In step S13, the dispatch management unit 54 of the integrated dispatch management device 12 receives a request acceptance notification from taxi 21A, determines that taxi 21A is the taxi to be dispatched, and in step S14, sends a dispatch confirmation notification to the driver application 35 of user A.

[0061] In step S3, when user A's driver app 35 receives a dispatch confirmation notification from the dispatch integrated management device 12, it displays a dispatch confirmation message indicating that the dispatch has been confirmed. Then, when taxi 21A of Company A, which has been assigned to user A, arrives at the pick-up location "X", in step S4, user A gets into taxi 21A and begins traveling to the destination "Y".

[0062] In step S31, user B enters the pickup location "Y'" and destination "Z" into the user app 61 and performs a ride request operation. Here, the pickup location "Y'" is close to user A's destination "Y".

[0063] In step S32, user B's user application 61 sends a dispatch request to the dispatch management device 12 along with information on the pick-up location "Y'" and destination "Z".

[0064] In step S15, the dispatch management unit 54 of the dispatch integrated management device 12 receives a dispatch request from user B's user application 61 and extracts an available taxi 21 by referring to the current vehicle movement data managed by the vehicle movement data management unit 51. Here, taxi 21A of Company A, which is moving to destination "Y" with user A on board, is searched for.

[0065] In step S16, the dispatch management unit 54 sends a dispatch request to taxi 21A of Company A, which is carrying user A.

[0066] In step S23, the driver app 35 of taxi 21A carrying user A acquires data related to the dispatch request from the dispatch management device 12 (for example, the pick-up location "Y'" and destination "Z") and displays it on the display. Then, when the driver performs an operation to accept the dispatch request, in step S24, the driver app 35 sends a request acceptance notification to the dispatch management device 12 indicating that the driver has accepted the dispatch request.

[0067] In step S17, the dispatch management unit 54 of the integrated dispatch management device 12 receives a dispatch acceptance notification from taxi 21A, determines that taxi 21A is the taxi to be dispatched, and in step S18, sends a dispatch confirmation notification to the driver application 35 of user B.

[0068] In step S32, when the driver application 35 of user B receives a dispatch confirmation notification, it displays a dispatch confirmation.

[0069] Taxi 21A, carrying user A, arrives at destination "Y," and user A alights at step S5.

[0070] Taxi 21A travels from destination "Y" to user B's boarding location "Y'". Then, in step S33, user B boards taxi 21A and begins traveling to destination "Z".

[0071] In the process described above, the period enclosed by the dashed line in Figure 2 indicates the time that user A is riding in taxi 21A. Taxi 21A, having picked up user A, can pick up the next passenger, user B, without waiting for user A to drop off and the status to change to "vacant," thus operating efficiently.

[0072] <3. User app's vehicle dispatch request processing> Next, referring to the flowchart in Figure 3, we will explain the dispatch request process focusing on user B's user application 61, which is part of the overall dispatch control process of the taxi dispatch system 1 shown in Figure 2. This process starts, for example, when user B launches user application 61.

[0073] When user B launches user application 61, in step S51, user application 61 displays taxis 21 located near the user's current location.

[0074] Figure 4 shows an example of the user application 61 screen displayed on the user terminal 13 of user B in step S51.

[0075] The screen in Figure 4 includes an area map 81 that displays a map of the vicinity of the current location, a dispatch request operation unit 82 for performing dispatch request operations, a pick-up location input unit 83 for entering the pick-up location, a destination input unit 84 for entering the destination, and a payment setting unit 85 for specifying the payment method.

[0076] Area map 81 displays taxi marks 91A representing taxis 21 with a status of "vacant" and taxi marks 91B representing taxis 21 with a status of "occupied" or "on call," at positions corresponding to the current location of taxis 21. The taxi marks 91A representing "vacant" status and the taxi marks 91B representing "occupied" or "on call" status are displayed in different colors or patterns to distinguish them. In the example in Figure 4, the taxi marks 91A representing "vacant" status are shown in white (plain), while the taxi marks 91B representing "occupied" or "on call" status are shown in gray.

[0077] In the example in Figure 4, the taxi mark 91B with the status "occupied" and the taxi mark 91B with the status "on call" are represented by the same color or pattern without distinction. However, the taxi mark 91B with the status "occupied" and the taxi mark 91B with the status "on call" may be distinguished by different colors or patterns. Furthermore, the method of distinguishing taxis 21 is not limited to color or pattern; they may also be distinguished by text. Alternatively, these methods can be combined; for example, taxis 21 may be distinguished by company using color or pattern, and their status may be distinguished by text. The distinction between company and status may also be reversed. In addition, based on customer data, the customer's preferred taxi company or the taxi company they would like to be dispatched preferentially may be highlighted using color, pattern, or text. Alternatively, only taxis 21 from the customer's preferred taxi company or the taxi company they would like to be dispatched preferentially may be displayed.

[0078] In the following, taxi mark 91A, which represents taxi 21 with the status "vacant," will be referred to as vacant taxi mark 91A, and taxi mark 91B, which represents taxis with the status "occupied" or "on call," will be referred to as occupied / on call taxi mark 91B. When no particular distinction is made between vacant taxi mark 91A and occupied / on call taxi mark 91B, they will simply be referred to as taxi mark 91.

[0079] The area map 81 displays a current location marker 93 indicating the user's current location acquired by the GPS receiver of the user terminal 13, and a boarding location marker 94 corresponding to the boarding location entered by the user in the boarding location input unit 83. The boarding location marker 94 can be freely moved to any desired location on the area map 81 by touch operation, and the address corresponding to the location of the boarding location marker 94 is displayed in the boarding location input unit 83.

[0080] The dispatch request operation unit 82 displays an operation bar 82A, and a dispatch request can be executed by sliding the operation bar 82A to the right.

[0081] The boarding location input field 83 is where the user enters their desired boarding location. The boarding location input field 83 may be left blank when the app is launched, or the current location obtained by the GPS receiver may be entered by default. If the boarding location input field 83 is left blank, the boarding location mark 94 will not be displayed.

[0082] The destination input section 84 is where the user enters their desired destination.

[0083] The payment settings unit 85 allows you to specify the payment method. Payment methods include, for example, cash payment to the driver or card payment using a credit card registered in the user application 61. Figure 4 shows an example of the display when card payment is selected in the payment settings unit 85.

[0084] When the app is launched or when no specific information has been entered in the pick-up location input section 83, the user app 61 displays taxi markers 91 of taxis 21 located within a predetermined range corresponding to the map scale relative to the user's current location on the area map 81. This is regardless of whether the status of the taxi 21 is "vacant," "occupied," or "on call."

[0085] When a pick-up location is entered into the pick-up location input unit 83, the user application 61 displays taxi marks 91 on the area map 81 of taxis 21 that are located within a predetermined range corresponding to the map scale relative to the pick-up location and that can arrive at the pick-up location entered in the pick-up location input unit 83 within a predetermined time. The status of the taxis 21 displayed here does not matter, whether they are "vacant," "occupied," or "on call."

[0086] Specifically, when a passenger's pick-up location is entered into the pick-up location input unit 83, the user application 61 transmits information about the user's pick-up location to the integrated dispatch management device 12. Based on the pick-up location information from the user application 61, the integrated dispatch management device 12 transmits the location information and status of taxis 21 that are located within a predetermined range corresponding to the map scale relative to the pick-up location and that can arrive at the pick-up location within a predetermined time. Based on the location information and status of the taxis 21 transmitted from the integrated dispatch management device 12, the user application 61 displays taxi marks 91 on the area map 81 for taxis 21 that are located within a predetermined range corresponding to the map scale relative to the pick-up location and that can arrive at the pick-up location entered in the pick-up location input unit 83 within a predetermined time. The predetermined time limit for arrival is set in advance by the integrated dispatch management device 12.

[0087] If the user's current location is entered by default in the boarding location input section 83, taxi marks 91 of taxis 21 that can reach the current location within a predetermined time will be displayed on the area map 81.

[0088] The vacant taxi mark 91A or the occupied / on-call taxi mark 91B displayed on the area map 81 may not show all taxis 21 that can arrive within a predetermined time, but rather only the top N taxis (N>0) with the earliest arrival times. Alternatively, if there are taxis 21 with a status of "vacant," only the vacant taxi mark 91A may be displayed, and the occupied / on-call taxi mark 91B may be displayed only if the number of "vacant" taxis 21 is below a predetermined number. Or, depending on the time of day and location (area), it may be possible to control whether to display one or both of the vacant taxi mark 91A or the occupied / on-call taxi mark 91B.

[0089] Figure 5 shows another example of a screen that displays taxi markers 91 of taxis 21 that can reach the pickup location or current location entered by the user in the pickup location input unit 83 within a predetermined time on the area map 81.

[0090] In the example in Figure 5, for a taxi 21 that can arrive at the current location within a predetermined time and whose status is "occupied" or "on call," the occupied / on call taxi mark 91B displays the destination mark 95 indicating the destination of that taxi 21 and the planned route 96 to the destination.

[0091] When the dispatch management device 12 transmits location information and status of taxis 21 that can arrive at the pickup location within a predetermined time based on the pickup location information from the user app 61, for taxis 21 whose status is "on call" or "on call," it also transmits destination information, specifically the destination and the planned route to the destination, to the user app 61. Based on the destination information of the taxis 21 transmitted from the dispatch management device 12, the user app 61 displays the destination mark 95 and the planned route to the destination 96 on the area map 81 for taxis marked "on call" or "on call" 91B.

[0092] In this way, by displaying the destination mark 95, user B can find out the drop-off location of user A, who is currently riding in taxi 21. For example, user B can move to user A's drop-off location themselves, thus reducing the waiting time until boarding. The dispatch management device 12 may also transmit information about the destination to the user application 61, including the destination and the planned route to the destination, as well as the estimated time of arrival at the destination or the estimated time to arrive at the destination. In addition to the destination mark 95 and the planned route 96, the device may further display the estimated time of arrival at the destination or the estimated time to arrive at the destination.

[0093] In addition, if displaying the destination mark 95 and the planned route 96 to the destination for all taxis 21 whose status is "occupied" or "on call" in the screen shown in Figure 5 makes the area map 81 difficult to see, then it is possible to display them only when the scale of the area map 81 is below a certain magnification (low magnification), or to display only taxis 21 whose destination is within the display range of the area map 81.

[0094] In the screen shown in Figure 4 or Figure 5, when User B enters a pick-up location in the pick-up location input unit 83 and a destination in the destination input unit 84, in step S52 of Figure 3, the user application 61 accepts the input of the pick-up location and destination, and in step S53, it determines whether a ride-hailing request operation has been performed and waits until it is determined that a ride-hailing request operation has been performed.

[0095] In the screen shown in Figure 4, for example, if the pick-up location "Y'" is entered in the pick-up location input section 83 and the destination "Z" is entered in the destination input section 84, and user B slides the operation bar 82A to the right, the user application 61 determines in step S53 that a ride-hailing request operation has been performed and proceeds to step S54.

[0096] In step S54, the user application 61 sends a dispatch request to the dispatch management device 12 along with information on the pick-up location "Y'" and destination "Z".

[0097] In step S55, the user application 61 waits until it receives a dispatch confirmation notification from the dispatch management device 12, and when it receives the dispatch confirmation notification, it receives the dispatch confirmation notification.

[0098] In step S56, the user application 61 displays the dispatch confirmation based on the received dispatch confirmation notification. For example, the user application 61 displays the identification number of the dispatched taxi 21A, the taxi company name, the radio number, and the estimated arrival time. Information such as the number, taxi company name, radio number, and estimated arrival time is transmitted from the dispatch integrated management device 12 along with the dispatch confirmation notification. The estimated arrival time is the estimated time when the dispatched taxi 21A will arrive at the pick-up location "Y'". In addition, the estimated fare and estimated arrival time (estimated travel time) from the pick-up location "Y'" to the destination "Z" may also be displayed.

[0099] Furthermore, if the dispatched taxi 21A is a taxi 21 that is currently in service, the area map 81 of user B's user application 61 will display the service / pickup taxi mark 91B for the dispatched taxi 21A, the destination mark 95, and the planned route 96 to the destination, as shown in the example screen in Figure 5.

[0100] The dispatch request process by user application 61 is executed as described above.

[0101] <Example of a change request screen> As explained with reference to Figure 2, if taxi 21, which was assigned in response to user B's dispatch request, is taxi 21A carrying user A, and user A's destination "Y" and user B's pick-up location "Y'" are somewhat far apart, then if user B changes their pick-up location from Y' to Y, user B can get in immediately after user A gets out.

[0102] For example, if the assignment of taxi 21 to user B's ride request is confirmed and the assigned taxi 21 is a taxi that is currently in use, the user application 61 can suggest to user B whether to change user B's pick-up location to the destination of user A, who is currently in the ride.

[0103] Figure 6 shows an example screen of the user application 61 that suggests a change of boarding location to the user.

[0104] The screen in Figure 6 displays the area map 101. The area map 101 also displays a taxi marker 91B indicating a taxi 21 currently in service assigned to user B, a destination marker 95 indicating the destination of that taxi 21, and a planned route 96 to the destination. This display is achieved by transmitting information about the current location and destination of the taxi 21 currently in service assigned to user B from the dispatch management device 12 to the user application 61, similar to the taxi marker 91B, destination marker 95, and planned route 96 explained in Figure 5.

[0105] Additionally, the area map 101 also displays a boarding location marker 102 indicating the boarding location specified by user B, and a boarding location marker 103 indicating the changed boarding location.

[0106] Then, for example, a message 104 is displayed that says, "The current passenger's disembarking location is 1. Would you like to change your boarding location to 3?" Along with this, a change button 105 is displayed to be operated if you wish to make a change, and a do not change button 106 is displayed to be operated if you do not wish to make a change.

[0107] The user app 61 can offer an incentive to user B if user B wishes to change their pick-up location. For example, the incentive could be a discount coupon that can be used on the next taxi ride, a coupon for free pick-up, or a free or discount coupon for shops that can be used near the current location or destination.

[0108] By offering incentives for changing the pick-up location, users can be motivated to change their pick-up location, and for Taxi 21, this allows for shorter waiting times and distances between passengers, thus enabling more efficient operations.

[0109] In the example shown in Figure 6, the proposed modified boarding location by the user application 61 is set to a location midway between user A's disembarking location and user B's boarding location. However, the proposed modified boarding location by the user application 61 may also be set to the same location as user A's disembarking location. In this case, any gap time or distance between the previous and next passengers can be eliminated.

[0110] The example in Figure 6 shows a process that proposes a change of pick-up location to user B, who is scheduled to board taxi 21 while it is in use. Conversely, it may also be possible to propose a change of drop-off location to user A, who is currently using taxi 21 while it is in use, to the pick-up location of user B.

[0111] Figure 7 shows an example screen when suggesting to user A of taxi 21, which is currently in operation, that they change their drop-off location to the pick-up location of the next user B.

[0112] While Figure 6 shows an example screen of user application 61 for user B, Figure 7 shows an example screen of user application 61 for user A.

[0113] In the screen shown in Figure 7, an area map 101, an actual taxi / pickup taxi mark 91B indicating user A's taxi 21, a destination mark 95 indicating the destination of that taxi 21, and a planned route 96 to the destination are displayed on the area map 101.

[0114] Furthermore, the area map 101 also displays a boarding location marker 102 indicating the boarding location specified by the next passenger, user B, and a disembarking location marker 111 indicating the changed disembarking location. The changed disembarking location is the boarding location marker 103 on the screen of user B's user app 61 shown in Figure 6, but it is the disembarking location marker 111 on the screen of user A's user app 61 shown in Figure 7.

[0115] Then, for example, a message 112 is displayed saying, "The next passenger's boarding location is number 2. Do you want to change the disembarking location to number 3?" Along with this, a change button 113 is displayed to be operated if you wish to make a change, and a non-change button 114 is displayed to be operated if you do not wish to make a change.

[0116] The user application 61 can provide an incentive to user A if user A wishes to change their disembarkation location.

[0117] In the process of suggesting a change of drop-off location to user A, who is using taxi 21 while it is in operation, if the change is implemented, it will enable more efficient operations.

[0118] <4. Driver app's dispatch request response processing> Next, referring to the flowchart in Figure 8, we will explain the dispatch request response process focusing on the driver application 35 within the overall dispatch control process of the taxi dispatch system 1 shown in Figure 2. This process starts, for example, when a driver launches the driver application 35 on the terminal device 33.

[0119] The scenario in which the dispatch request response process shown in Figure 8 is executed is assumed to be the situation in the overall dispatch control process of the taxi dispatch system 1 shown in Figure 2, where a dispatch request is sent from user B while user A is already in the taxi.

[0120] First, in step S71, the driver application 35 determines whether it has received a dispatch request from the dispatch management device 12 and waits until it is determined that it has received a dispatch request. If a dispatch request is sent from the dispatch management device 12 and it is determined in step S71 that the dispatch request has been received, the process proceeds to step S72.

[0121] In step S72, the driver application 35 acquires data related to the dispatch request from the dispatch integrated management device 12 (for example, the pick-up location "Y'" and the destination "Z"), and displays a dispatch request screen on the display based on the acquired data.

[0122] Figure 9 shows an example of a dispatch request screen displayed on the terminal device 33 in step S72.

[0123] The screen in Figure 9 displays the area map 121. The area map 121 also displays the taxi marker 91B indicating the taxi 21 driven by user A, the destination marker 95 indicating the destination of that taxi 21, and the planned route 96 to the destination.

[0124] Additionally, the area map 121 also displays a pick-up location marker 122 indicating the pick-up location specified by user B. As part of user B's ride request information, additional information such as user B's planned pick-up time and destination may also be displayed.

[0125] Then, for example, a message 131 appears saying, "You are 5 minutes away from your destination. You can accept the next ride request. Would you like to accept it?" Along with this, an accept button 132 is displayed, which is operated if the user wishes to accept the request, and a rejection button 133 is displayed, which is operated if the user does not wish to accept the request.

[0126] If a driver accepts a dispatch request, they press the accept button 132. On the other hand, if a driver does not wish to accept a dispatch request, they press the reject button 133. If neither the accept button 132 nor the reject button 133 is pressed within a predetermined time after the dispatch request screen shown in Figure 9 is displayed, the driver application 35 can perform the same processing as if the reject button 133 had been pressed. As a result, if there is no action from the driver within a certain period of time, the dispatch management device 12 can send the dispatch request to the next candidate taxi 21.

[0127] When a dispatch request is received, the driver app 35 may simply display the dispatch request screen on the display if the taxi 21 is carrying a passenger (is in use), or it may output a voice message such as "A dispatch request has been received" along with the dispatch request screen if the taxi 21 is not carrying a passenger (is empty).

[0128] In step S73 of Figure 8, the driver application 35 determines whether or not the request acceptance operation has been performed.

[0129] In the dispatch request screen shown in Figure 9, if the driver presses the order button 132, it is determined in step S73 that the request acceptance operation has been performed, and the process proceeds to step S74.

[0130] On the other hand, if the driver presses the "cannot accept order" button 133, or if there is no operation by the driver within a certain period of time, it is determined in step S73 that the request acceptance operation was not performed, and the process proceeds to step S76.

[0131] In step S74, when it is determined that a request acceptance operation has been performed, the driver application 35 sends a request acceptance notification to the dispatch integrated management device 12 indicating that it has accepted the dispatch request.

[0132] Then, in step S75, the driver application 35 displays the dispatch reservation information on the terminal device 33's display, showing information about the next dispatch request that has been received. The dispatch reservation display screen shows, for example, the name of user B, the pick-up location, the pick-up time, and the destination, which are the next dispatch requests.

[0133] On the other hand, if the driver presses the "cannot accept order" button 133, or if there is no operation from the driver within a certain period of time, in step S76, the driver application 35 sends a request rejection notification to the dispatch management device 12 indicating that the dispatch request is being rejected.

[0134] After step S75 or S76, the process returns to step S71, and the process described above is repeated.

[0135] <5. Dispatch processing of the integrated dispatch management system> Next, referring to the flowchart in Figure 10, we will explain the dispatch process focusing on the integrated dispatch management device 12 within the overall dispatch control process of the taxi dispatch system 1 shown in Figure 2. This process starts, for example, when the program for the server device acting as the integrated dispatch management device 12 is started. It should be assumed that the collection and recording of vehicle movement data in the vehicle movement data management unit 51 of the integrated dispatch management device 12 is performed separately.

[0136] First, in step S101, the dispatch management unit 54 of the dispatch integrated management device 12 determines whether it has received a dispatch request from the user application 61 on the user terminal 13 of a designated user, and waits until it is determined that a dispatch request has been received.

[0137] If it is determined in step S101 that a ride request has been received, the process proceeds to step S102. The ride request sent from the user application 61 includes information such as the pick-up location, destination, and payment method entered on the ride request screen in Figure 4, as well as information such as the user ID and name that identify the user.

[0138] In step S102, the dispatch management unit 54 refers to the vehicle movement data stored in the vehicle movement data management unit 51 and extracts taxis 21 that can arrive at the pickup location for the dispatch request within a predetermined time from among the taxis 21 whose status is "vacant," "occupied," or "on call." For taxis 21 whose status is "vacant," it is determined whether they can arrive at the pickup location for the dispatch request within a predetermined time based on the travel time from the taxi 21's current location to the pickup location. For taxis 21 whose status is "occupied," it is determined whether they can arrive at the pickup location for the dispatch request within a predetermined time based on the travel time from the taxi 21's destination and arrival time to the pickup location for the dispatch request. For taxis 21 whose status is "on call," after the taxi 21 has picked up a user and arrived at the destination, it is determined whether they can arrive at the pickup location for the dispatch request within a predetermined time based on the travel time from the destination and arrival time to the pickup location for the dispatch request.

[0139] Furthermore, the dispatch management unit 54 may, from the outset, extract available taxis 21 from among all taxis 21 whose status is "vacant," "occupied," or "on call," or, if there are fewer than a predetermined number of "vacant" taxis 21, it may extract available taxis 21 including those "occupied" or "on call."

[0140] In step S103, the dispatch management unit 54 selects the taxi 21 that can reach the pick-up location fastest from among the one or more taxis 21 that have been selected as the dispatch candidate, and in step S104, it sends a dispatch request to the taxi 21 that has been selected as the dispatch candidate.

[0141] In step S105, the dispatch management unit 54 determines whether or not it has received a request acceptance notification from the taxi 21 that sent the dispatch request.

[0142] In step S105, if the dispatch management unit 54 does not receive a request acceptance notification from the taxi 21 that sent the dispatch request within a certain time (for example, 15 seconds), or if a request rejection notification is sent, the dispatch management unit 54 determines that there is no request acceptance notification and returns to step S103. This determines the next available dispatch candidate that can respond to the dispatch request.

[0143] On the other hand, if the dispatch management unit 54 receives a request acceptance notification from the taxi 21 that sent the dispatch request, in step S105 the unit determines that a request acceptance notification has been received from the taxi 21 that sent the dispatch request, and proceeds to step S106.

[0144] In step S106, the dispatch management unit 54 determines which taxi 21 has sent the request acceptance notification to be dispatched, and sends dispatch reservation information to the selected taxi 21. The dispatch reservation information includes, for example, the name of user B who made the dispatch request, the pick-up location, the pick-up time, and the destination.

[0145] Then, in step S107, the dispatch management unit 54 sends a dispatch confirmation notification to the user application 61 of user B who made the dispatch request.

[0146] In step S108, the dispatch management unit 54 determines whether the taxi 21 whose dispatch has been decided is a taxi with the status of "occupied" or "on call".

[0147] If, in step S108, it is determined that the taxi 21 whose dispatch was decided is not a taxi with a status of "occupied" or "on call," that is, if it is determined to be a taxi with a status of "available," the process returns to step S101 and waits until the next dispatch request is received.

[0148] On the other hand, if in step S108 the dispatched taxi 21 is determined to be a taxi with a status of "occupied" or "on call", the process proceeds to step S109, where the dispatch management unit 54 executes a pick-up location change process, as explained with reference to Figure 6, which changes the pick-up location of the next passenger, user B, to be closer to the destination (drop-off location) of the currently riding user A. Alternatively, it may also be a drop-off location change process, as explained in Figure 7, which changes the destination (drop-off location) of the currently riding user A to be closer to the pick-up location of the next passenger, user B. Note that the process in step S109 may be omitted if the distance between the destination (drop-off location) of the currently riding user A and the pick-up location of the next passenger, user B, is short, or if the time until user B's pick-up time is short.

[0149] After processing in step S109, the process returns to step S101 and waits until the next dispatch request is received.

[0150] As described above, the dispatch process allows the system to determine which taxis 21 are available to handle a dispatch request sent from a user's user application 61. This includes not only taxis 21 whose status at the time of the search is "available," but also taxis 21 whose status is "occupied" or "on call."

[0151] This means that users will have more taxis available to accept their dispatch requests, allowing them to call a taxi with less waiting time. Furthermore, it reduces the likelihood of users being unable to find an available taxi, especially during times of high demand due to specific conditions such as rainy mornings, locations, or weather. For example, even when no taxi markers are displayed on the area map 81 upon launching the user app 61, the user's success rate in dispatching a taxi will increase, thereby enhancing their trust in the user app 61.

[0152] Furthermore, for Taxi 21 drivers, the opportunity to acquire the next passenger while the vehicle is still carrying an existing passenger can be shortened, reducing the time spent between passengers and minimizing travel time between passengers.

[0153] Therefore, the taxi dispatch system 1 enables efficient dispatching.

[0154] Furthermore, in order to extract taxis 21 that can respond to dispatch requests, including taxis 21 whose status is "occupied," the destinations of the occupied taxis 21 must be known. In the example above, we described the case where a dispatch is requested using the user application 61, but there are also cases where taxis 21 pick up passengers through "cruising," a method of acquiring passengers while driving around as an "empty" taxi. In such cases, the driver should input the passenger's destination into the driver application 35 after picking up the passenger. Alternatively, the driver application 35 may input the driver's voice saying "(destination)" or the user's voice saying "(destination), please" using voice recognition.

[0155] In the embodiment described above, the dispatch management device 12 extracted taxis 21 that could arrive at the pick-up location within a predetermined time based on the pick-up location and destination information transmitted from the user application 61 along with the pick-up request.

[0156] However, the process of extracting taxis 21 that can arrive at the pick-up location within a predetermined time may be performed by the user application 61. When the user application 61 performs the process of extracting taxis 21, all or part of the vehicle movement data stored in the vehicle movement data management unit 51 is transmitted from the dispatch integrated management device 12 to the user application 61, and the user application 61 extracts taxis 21 that can arrive at the pick-up location from which the dispatch request was made within a predetermined time, from among the taxis 21 whose status is "vacant," "occupied," or "on call," based on the received vehicle movement data. Part of the vehicle movement data transmitted to the user application 61 may be, for example, vehicle movement data for taxis 21 that are within a predetermined range of the pick-up location.

[0157] The above-described embodiment illustrates an example of controlling taxi dispatch as a mobility device, but it can also be applied to mobility devices similar to taxi services such as ride-sharing, other mobility devices that carry passengers (people), specifically buses, trains, airplanes, ships, helicopters, and mobility devices that carry goods (luggage), such as trucks and dump trucks. Furthermore, the mobility device may be an unmanned device such as a drone.

[0158] Furthermore, while the above-described embodiments used "occupied," "vacant," or "receiving" as examples of statuses indicating the operational status, other similar operational statuses such as "out of service," "charging," "payment," "surcharge," "reservation," "highway," "charter," "sightseeing," "flat rate," "agency service," and "rescue" may also be used. Moreover, they are not limited to those stipulated by law.

[0159] <6. Computer Configuration Examples> The series of processes described above can be executed by hardware or by software. When the series of processes are executed by software, the programs that make up the software are installed on a computer. Here, a computer includes microcomputers built into dedicated hardware, as well as general-purpose personal computers that can perform various functions by installing various programs.

[0160] Figure 11 is a block diagram showing an example of the hardware configuration of a computer when the computer executes each process performed by the vehicle dispatch integrated management device 12, the user terminal 13, or the terminal device 33 using a program.

[0161] In a computer, the CPU (Central Processing Unit) 201, ROM (Read Only Memory) 202, and RAM (Random Access Memory) 203 are interconnected by a bus 204.

[0162] An input / output interface 205 is further connected to bus 204. An input / output interface 205 is connected to an input unit 206, an output unit 207, a storage unit 208, a communication unit 209, and a drive 210.

[0163] The input unit 206 consists of operation buttons, a keyboard, a mouse, a microphone, a touch panel, input terminals, etc. The output unit 207 consists of a display, speakers, output terminals, etc. The storage unit 208 consists of a hard disk, a RAM disk, non-volatile memory, etc. The communication unit 209 consists of a network interface, etc. The drive 210 drives a removable recording medium 211 such as a magnetic disk, optical disk, magneto-optical disk, or semiconductor memory.

[0164] In a computer configured as described above, the CPU 201 loads, for example, a program stored in the memory unit 208 into the RAM 203 via the input / output interface 205 and the bus 204, and executes it, thereby performing the series of processes described above. The RAM 203 also stores data necessary for the CPU 201 to perform various processes as appropriate.

[0165] The program executed by the computer (CPU 201) can be provided by recording it on a removable recording medium 211, such as a packaged media. The program can also be provided via wired or wireless transmission media, such as a local area network, the internet, or digital satellite broadcasting.

[0166] In a computer, a program can be installed in the storage unit 208 via the input / output interface 205 by inserting the removable recording medium 211 into the drive 210. Alternatively, a program can be received by the communication unit 209 via a wired or wireless transmission medium and installed in the storage unit 208. Furthermore, programs can be pre-installed in the ROM 202 or the storage unit 208.

[0167] In this specification, a system means a collection of multiple components (devices, modules (parts), etc.), regardless of whether all components are located in the same enclosure. Therefore, multiple devices housed in separate enclosures and connected via a network, and a single device containing multiple modules in one enclosure, are both considered systems.

[0168] Furthermore, in this specification, the steps described in the flowchart may be performed chronologically in the order they are described, but they may also be performed in parallel or at any necessary time, such as when a call is made, even if they are not necessarily processed chronologically.

[0169] The embodiments of this technology are not limited to those described above, and various modifications are possible without departing from the spirit of this technology.

[0170] For example, a combination of all or part of the embodiments described above can be adopted.

[0171] For example, this technology can be configured as cloud computing, where a single function is shared and processed collaboratively by multiple devices via a network.

[0172] Furthermore, each step described in the flowchart above can be performed by a single device, or it can be divided and performed by multiple devices.

[0173] Furthermore, if a single step includes multiple processes, those processes can be executed by a single device or shared among multiple devices.

[0174] Furthermore, the effects described herein are merely illustrative and not limiting, and other effects may also occur.

[0175] Furthermore, this technology can take the following configuration. (1) It consists of a dispatch management device that manages the dispatch of multiple mobile devices, and a terminal device that requests dispatch from the dispatch management device. The aforementioned dispatch management device is Information regarding the current location or departure point is obtained from the terminal device. Based on the acquired information regarding the current location or departure point, the location information and operating status of one or more mobile devices are transmitted to the terminal device. The aforementioned terminal device is Based on the location information and operating status of the one or more mobile devices transmitted from the dispatch management device, the display unit displays mobile devices located within a predetermined range relative to the current location or departure point that are in the status of being vacant, and mobile devices located within a predetermined range relative to the current location or departure point that are in the status of being occupied or waiting for a pickup. Ride-hailing system. (2) Based on the acquired information regarding the current location or departure location, the dispatch management device further extracts a vehicle whose operating status is either occupied or picking up a vehicle, and which can arrive at the current location or departure location within a predetermined time. The terminal device further displays on the display unit a mobile device that can reach the current location or departure point within the specified time frame. The dispatch system described in (1) above. (3) Based on the location information and operating status of the one or more mobile devices transmitted from the dispatch management device, the terminal device further extracts mobile devices whose operating status is either an active vehicle or a vehicle picking up a vehicle, and which can arrive at the current location or departure location within a predetermined time, and displays the extracted mobile devices that can arrive at the current location or departure location within a predetermined time on the display unit. The dispatch system described in (1) above. (4) The dispatch management device, when the number of available vehicles is below a predetermined number, extracts vehicles that are either occupied or picking up passengers and that can arrive at the current location or departure location within a predetermined time. The dispatch system described in (2) above. (5) When the dispatch management device transmits the location information and operating status of the one or more mobile devices to the terminal device, it also transmits information regarding the destination of the mobile device if the operating status is that of a mobile device that is in use. The terminal device also displays information on the display unit indicating the destination of the vehicle's mobile device, based on the operating status. A dispatch system as described in any of (1) to (4) above. (6) The dispatch management device transmits to the terminal device, as information regarding the destination, the destination and the arrival time or the time required to reach the destination. The terminal device displays information indicating the destination of the vehicle's moving device, along with the arrival time or the duration of travel, on the display unit. The dispatch system described in (5) above. (7) The dispatch management device obtains a dispatch request from the terminal device along with information about the current location or departure location, extracts mobile vehicles that can arrive at the current location or departure location within a predetermined time from among mobile vehicles whose operating status is either vacant, occupied, or on call, and transmits the dispatch request to the extracted mobile vehicles. A dispatch system as described in any of (1), (2), (4) through (6) above. (8) If the dispatch management device does not receive a response within a certain period of time from the mobile device that sent the dispatch request, it extracts the next mobile device that can reach the current location or departure point within a predetermined time, and sends a dispatch request to the extracted mobile device. The dispatch system described in (7) above. (9) The dispatch management device, when the mobile device that sent the dispatch request accepts the request and the dispatch is confirmed, and the operating status of the confirmed mobile device is that it is in service, executes a change process to bring the destination of the confirmed mobile device in service closer to the current location or departure point of the terminal device. The dispatch system described in (7) above. (10) The aforementioned modification process is a process of bringing the confirmed destination of the mobile device in the actual vehicle closer to the current location or departure point of the terminal device. The dispatch system described in (9) above. (11) The aforementioned modification process is a process that brings the current location or departure point of the terminal device closer to the confirmed destination of the mobile device in the actual vehicle. The dispatch system described in (9) above. (12) The dispatch management device transmits to the terminal device information regarding the destination of the mobile device in the actual vehicle whose dispatch has been confirmed after the mobile device that sent the dispatch request has accepted the request. The terminal device displays information regarding the destination of the mobile device in the actual vehicle on the display unit. The dispatch system described in (9) above. (13) The dispatch management device transmits the destination and the planned route to the destination to the terminal device as information regarding the destination. The terminal device displays the confirmed destination of the mobile device in the actual vehicle and the planned route to the destination on the display unit. The dispatch system described in (12) above. (14) The terminal device displays, on its display unit, a distinction between a mobile device whose operating status is vacant and a mobile device whose operating status is occupied or picking up a vehicle. The dispatch system described in any of (1) to (13) above. (15) The terminal device displays, on its display unit, the operational status of a vehicle being moved and the operational status of a vehicle being picked up, distinguishing between them. A dispatch system as described in any of (1) to (14) above. (16) A dispatch system comprising a dispatch management device that manages the dispatch of multiple mobile devices, and a terminal device that requests dispatch from the dispatch management device, The aforementioned dispatch management device Information regarding the current location or departure point is obtained from the terminal device. Based on the acquired information regarding the current location or departure point, the location information and operating status of one or more mobile devices are transmitted to the terminal device. The aforementioned terminal device Based on the location information and operating status of the one or more mobile devices transmitted from the dispatch management device, the display unit displays mobile devices located within a predetermined range relative to the current location or departure point that are in the status of being vacant, and mobile devices located within a predetermined range relative to the current location or departure point that are in the status of being occupied or waiting for a pickup. Vehicle dispatch management method. (17) The dispatch management system's computer, Based on the current location or departure point information obtained from the terminal device, the location information and operating status of one or more mobile devices are transmitted to the terminal device. The terminal device's display unit will show the following: a mobile device located within a predetermined range from the current location or departure point whose operating status is "vacant," and a mobile device located within a predetermined range from the current location or departure point whose operating status is "occupied" or "waiting for a ride." A program to execute a process. [Explanation of symbols]

[0176] 1 Taxi dispatch system, 11 Dispatch management device, 12 Integrated dispatch management device, 13 Terminal device (user terminal), 21 Taxi, 31 In-vehicle device, 33 Terminal device, 34 Vehicle movement data generation unit, 35 Driver application, 41 Vehicle movement data management unit, 42 Order information management unit, 51 Vehicle movement data management unit, 52 Customer data management unit, 53 Order information management unit, 54 Dispatch management unit, 61 User application, 201 CPU, 202 ROM, 203 RAM, 206 Input unit, 207 Output unit, 208 Storage unit, 209 Communication unit, 210 Drive

Claims

1. It consists of a dispatch management device that manages the dispatch of multiple mobile devices, and a terminal device that requests dispatch from the dispatch management device. The aforementioned dispatch management device is Information regarding the current location or departure point is obtained from the terminal device. Based on the acquired information regarding the current location or departure point, the system extracts mobile devices whose operating status is either "on-board" or "on-call" and which can arrive at the current location or departure point within a predetermined time. The terminal device is provided with location information and operating status of one or more mobile devices located within a predetermined range from the current location or departure point, and capable of arriving at the current location or departure point within the predetermined time. The aforementioned location information includes information regarding the current location and destination of the mobile device whose operating status is either an active vehicle or a vehicle being picked up. The aforementioned terminal device is Based on the location information and operating status of the one or more mobile devices transmitted from the dispatch management device, the current location and destination of a mobile device located within a predetermined range from the current location or departure point and capable of arriving at the current location or departure point within the predetermined time are displayed on the display unit. Dispatch system.

2. It consists of a dispatch management device that manages the dispatch of multiple mobile devices, and a terminal device that requests dispatch from the dispatch management device. The aforementioned dispatch management device is Information regarding the current location or departure point is obtained from the terminal device. Based on the acquired information regarding the current location or departure point, the location information and operating status of one or more mobile devices are transmitted to the terminal device. The aforementioned location information includes information regarding the current location and destination of the mobile device whose operating status is either an active vehicle or a vehicle being picked up. The aforementioned terminal device is Based on the location information and operating status of the one or more mobile devices transmitted from the dispatch management device, the system extracts mobile devices whose operating status is either an active vehicle or a vehicle picking up a vehicle, and which can arrive at the current location or departure location within a predetermined time. The current location and destination of a mobile device located within a predetermined range relative to the current location or departure point, and capable of arriving at the current location or departure point within the predetermined time, are displayed on the display unit. Dispatch system.

3. The terminal device displays a predetermined number of mobile devices on its display unit that can arrive at the current location or departure point within the predetermined time, according to their arrival time. The dispatch system according to claim 1 or 2.

4. The terminal device, when the operating status of the mobile vehicle whose dispatch has been confirmed is that it is in service, displays a screen on the display unit that suggests to the user that they change their boarding location. The dispatch system according to claim 1 or 2.

5. The terminal device provides an incentive to the user if the user wishes to change their boarding location. The dispatch system according to claim 4.

6. The terminal device displays, on its display unit, a distinction between a mobile device whose operating status is vacant and a mobile device whose operating status is occupied or picking up a vehicle. The dispatch system according to claim 1 or 2.

7. The terminal device displays, on its display unit, the operational status of a vehicle being moved and the operational status of a vehicle being picked up, distinguishing between them. The dispatch system according to claim 1 or 2.

8. A dispatch system comprising a dispatch management device that manages the dispatch of multiple mobile devices, and a terminal device that requests dispatch from the dispatch management device, The aforementioned dispatch management device Information regarding the current location or departure point is obtained from the terminal device. Based on the acquired information regarding the current location or departure point, the system extracts mobile devices whose operating status is either "on-board" or "on-call" and which can arrive at the current location or departure point within a predetermined time. The terminal device is provided with location information and operating status of one or more mobile devices located within a predetermined range from the current location or departure point, and capable of arriving at the current location or departure point within the predetermined time. The aforementioned location information includes information regarding the current location and destination of the mobile device whose operating status is either an active vehicle or a vehicle being picked up. The aforementioned terminal device Based on the location information and operating status of the one or more mobile devices transmitted from the dispatch management device, the current location and destination of a mobile device located within a predetermined range from the current location or departure point and capable of arriving at the current location or departure point within the predetermined time are displayed on the display unit. Vehicle dispatch management method.

9. The dispatch management system's computer, Based on information about the current location or departure point obtained from the terminal device, the system extracts mobile devices whose operating status is either "on-site" or "on-call" and which can arrive at the current location or departure point within a predetermined time. The terminal device is provided with location information and operating status of one or more mobile devices located within a predetermined range from the current location or departure point, and capable of arriving at the current location or departure point within the predetermined time. The aforementioned location information includes information regarding the current location and destination of the mobile device whose operating status is either an active vehicle or a vehicle being picked up. The terminal device's display unit will show the current location and destination of a mobile device that is located within a predetermined range from the current location or departure point and can reach the current location or departure point within the predetermined time. A program to execute a process.

Images